Octomerger Bot
@@ -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
|
||||
|
||||
|
@@ -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
|
||||
|
||||
|
@@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
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).
|
||||
|
||||
@@ -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)."
|
||||
|
||||
{% 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 |
|
||||
| --- | --- |
|
||||
|
||||
@@ -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" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
## 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" %}. <br> <br> 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" %}. <br> <br> 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.
|
||||
|
||||
|
||||
|
||||
|
||||
## 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.
|
||||
|
||||
|
||||
|
||||
|
||||
## 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)."
|
||||
|
||||
|
||||
|
||||
|
||||
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 %}
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% 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)."
|
||||
|
||||
|
||||
|
||||
|
||||
{% 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 %}
|
||||
|
||||
|
||||
|
||||
|
||||
### 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)."
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
## 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)."
|
||||
|
||||
|
||||
@@ -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, <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
|
||||
You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. <a href="https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch" data-proofer-ignore>https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch</a>:
|
||||
|
||||
```
|
||||
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)"
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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/)"
|
||||
|
||||
@@ -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'
|
||||
---
|
||||
|
||||
|
||||
@@ -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
|
||||
<em>YOUR_USERNAME</em>
|
||||
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 <em>YOUR_REPOSITORY</em>
|
||||
$ cd YOUR_REPOSITORY
|
||||
# Change directories to the initialized Git repository
|
||||
$ git remote -v
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.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 %}
|
||||
|
||||
@@ -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 <code><em>ID+username</em>@users.noreply.github.com</code>. 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 %} é <code><em>username</em>@users.noreply.github.com</code>. 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 <code>ID+USERNAME@users.noreply.github.com</code>. 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 <code>USERNAME@users.noreply.github.com</code>. 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 "<em>email@example.com</em>"
|
||||
$ 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 "<em>email@example.com</em>"
|
||||
$ git config user.email "YOUR_EMAIL"
|
||||
```
|
||||
4. {% data reusables.user-settings.confirm_git_email_address_correct %}
|
||||
```shell
|
||||
|
||||
@@ -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**.
|
||||
{% 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**.
|
||||
|
||||
5. Digite um novo nome de usuário.
|
||||
|
||||
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.
|
||||
 {% 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**.
|
||||
{% 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**.
|
||||
|
||||
5. Type a new username.
|
||||
|
||||
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.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
@@ -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 <kbd>Control</kbd> ou <kbd>Comando</kbd>, 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 <kbd>Control</kbd> or <kbd>Command</kbd>, 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 %}
|
||||
|
||||
@@ -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**.
|
||||
|
||||
4. Digite o nome-padrão que você gostaria de usar para novos branches.
|
||||
|
||||
5. Clique em **Atualizar**.
|
||||
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.repo-tab %}
|
||||
3. Under "Repository default branch", click **Change default branch name now**.
|
||||
|
||||
4. Type the default name that you would like to use for new branches.
|
||||
|
||||
5. Click **Update**.
|
||||
|
||||
|
||||
## 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)"
|
||||
|
||||
@@ -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 <em>work_directory</em>
|
||||
$ rm -rf WORK_DIRECTORY
|
||||
```
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
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 %}
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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=<output name>::<value>"`. 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 "<output name>=<value>" >> $GITHUB_OUTPUT`{% else %}use a workflow command in a specific syntax: `echo "::set-output name=<output name>::<value>"`{% 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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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_<VARIABLE_NAME>`. 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_<VARIABLE_NAME>`. 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_<VARIABLE_NAME>`. 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:
|
||||
|
||||
<!--
|
||||
<!--
|
||||
This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
|
||||
To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo.
|
||||
To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo.
|
||||
-->
|
||||
|
||||
<table>
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 \
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
|
||||
|
||||
## 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:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Compreendendo o exemplo
|
||||
## Understanding the example
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Código</b></th>
|
||||
<th style="width:40%"><b>Explicação</b></th>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
<th style="width:40%"><b>Explanation</b></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@@ -238,7 +244,7 @@ on:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -250,7 +256,7 @@ A palavra-chave `on` permite definir os eventos que são disparados quando o flu
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -262,7 +268,7 @@ Adicione o evento `workflow_dispatch` se você quiser a capacidade de executar m
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -276,7 +282,7 @@ Adicione o evento `pull_request` para que o fluxo de trabalho seja executado aut
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -290,7 +296,7 @@ permissions:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -304,7 +310,7 @@ concurrency:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -316,7 +322,7 @@ Cria um grupo de simultaneidade para eventos específicos e usa o operador `||`
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -328,7 +334,7 @@ jobs:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho.
|
||||
Groups together all the jobs that run in the workflow file.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -340,7 +346,7 @@ Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -352,7 +358,7 @@ Define um trabalho com a ID `test` que é armazenada na chave `jobs`.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -364,7 +370,7 @@ Configura o trabalho a ser executado em um executor hospedado no {% data variabl
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -375,7 +381,7 @@ Define o número máximo de minutos para permitir que o trabalho seja executado
|
||||
```
|
||||
</td>
|
||||
<td>
|
||||
Esta seção define a matriz de build dos trabalhos.
|
||||
This section defines the build matrix for your jobs.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -387,7 +393,7 @@ Define o número máximo de minutos para permitir que o trabalho seja executado
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -410,7 +416,7 @@ A configuração de `fail-fast` como `false` impede que o {% data variables.prod
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -422,7 +428,7 @@ Cria uma matriz chamada `test-group`, com uma matriz de grupos de teste. Esses v
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -438,7 +444,7 @@ Agrupa todas as etapas que serão executadas durante o trabalho `test`. Cada tra
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -478,7 +484,7 @@ A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `a
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -497,7 +503,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa usará a ação
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</tr>
|
||||
<tr>
|
||||
<td>
|
||||
@@ -514,7 +520,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa verificará o b
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -527,7 +533,7 @@ Se o repositório atual for o `github/docs-internal`, esta etapa usará a palavr
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -546,7 +552,7 @@ Esta etapa executa um comando para fazer check-out de objetos LFS do repositóri
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -560,7 +566,7 @@ Esta etapa usa a ação `trilom/file-changes-action` para reunir os arquivos alt
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -576,7 +582,7 @@ Esta etapa executa um comando do shell que usa uma saída da etapa anterior para
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -589,7 +595,7 @@ Essa etapa usa a ação `actions/setup-node` para instalar a versão especificad
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -605,7 +611,7 @@ Esta etapa executa o comando do shell `npm ci` para instalar os pacotes de softw
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -618,7 +624,7 @@ Esta etapa usa a ação `actions/cache` para armazenar em cache o build Next.js,
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Esta etapa executa o script de build.
|
||||
This step runs the build script.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -634,12 +640,12 @@ Esta etapa executa o script de build.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Próximas etapas
|
||||
## Next steps
|
||||
|
||||
{% data reusables.actions.learning-actions %}
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
|
||||
|
||||
## 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:
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Compreendendo o exemplo
|
||||
## Understanding the example
|
||||
|
||||
{% data reusables.actions.example-explanation-table-intro %}
|
||||
|
||||
<table style="table-layout: fixed;">
|
||||
<thead>
|
||||
<tr>
|
||||
<th style="width:60%"><b>Código</b></th>
|
||||
<th style="width:40%"><b>Explicação</b></th>
|
||||
<th style="width:60%"><b>Code</b></th>
|
||||
<th style="width:40%"><b>Explanation</b></th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
@@ -204,10 +214,10 @@ on:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -221,7 +231,7 @@ permissions:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -233,7 +243,7 @@ jobs:
|
||||
</td>
|
||||
<td>
|
||||
|
||||
Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho.
|
||||
Groups together all the jobs that run in the workflow file.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -246,7 +256,7 @@ Agrupa todos os trabalhos executados no arquivo de fluxo de trabalho.
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -258,7 +268,7 @@ if: github.repository == 'github/docs-internal'
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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_.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -270,7 +280,7 @@ runs-on: ubuntu-latest
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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)."
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -286,7 +296,7 @@ Configura o trabalho a ser executado em um executor do Ubuntu Linux. Isto signif
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -298,7 +308,7 @@ Cria variáveis de ambiente personalizadas e redefine a variável interna `GITHU
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -311,7 +321,7 @@ Agrupa todas as etapas que serão executadas durante o trabalho `check_all_engli
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -327,7 +337,7 @@ A palavra-chave `uses` informa que o trabalho deve recuperar a ação chamada `a
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -342,7 +352,7 @@ Essa etapa usa a ação `actions/setup-node` para instalar a versão especificad
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -356,7 +366,7 @@ A palavra-chave `run` instrui o trabalho a executar um comando no executor. Ness
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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`.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -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 %}
|
||||
```
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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).
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -393,7 +407,7 @@ Se o script `check-english-links.js` detectar links desfeitos e retornar um stat
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -421,9 +435,9 @@ Usa a ação `peter-evans/create-issue-from-file` para criar um problema do {% d
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -441,7 +455,7 @@ Depois, [`gh issue comment`](https://cli.github.com/manual/gh_issue_comment) é
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@@ -462,16 +476,16 @@ Se um problema de uma execução anterior estiver aberto e atribuído a alguém,
|
||||
</td>
|
||||
<td>
|
||||
|
||||
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.
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
## Próximas etapas
|
||||
## Next steps
|
||||
|
||||
{% data reusables.actions.learning-actions %}
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
@@ -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 <em>https://github.com/octo-org/octo-repo</em> --pat <em>ghp_abcd1234</em>
|
||||
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 <em>https://github.com/octo-org/octo-repo</em> --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.<org>-<repo>.<runnerName>.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.<org>-<repo>.<runnerName>.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.<org>-<repo>.<runnerName>.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.<org>-<repo>.<runnerName>.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.<org>-<repo>.<runnerName>`. 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.<org>-<repo>.<runnerName>`. 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.<repoName>.<runnerName>.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.<repoName>.<runnerName>.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 (<org>-<repo>.<runnerName>)`. 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 (<org>-<repo>.<runnerName>)`. 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
|
||||
```
|
||||
|
||||
@@ -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)."
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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).
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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)."
|
||||
|
||||
@@ -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)."
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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)".
|
||||
|
||||
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)."
|
||||
|
||||
|
||||
{% 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 %}
|
||||
|
||||
@@ -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:
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -115,7 +115,7 @@ For more information, see "[Reusing workflows](/actions/learn-github-actions/reu
|
||||
|
||||
#### `on.workflow_call.inputs.<input_id>.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.
|
||||
|
||||
|
||||
@@ -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)."
|
||||
|
||||
|
||||
@@ -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 %}** .
|
||||
 {% 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 %}**.
|
||||
|
||||
{% 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 %}** .
|
||||
 {% 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 %}**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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.
|
||||
 {% 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.
|
||||
|
||||
{% 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 %}{% else %}{% endif %}{% else %}
|
||||
1. Em "{% data variables.product.prodname_advanced_security %}", clique em **{% data variables.product.prodname_code_scanning_capc %}** .
|
||||
{% 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 %}{% else %}{% endif %}{% else %}
|
||||
1. Under "{% data variables.product.prodname_advanced_security %}," click **{% data variables.product.prodname_code_scanning_capc %}**.
|
||||
{% 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
|
||||
|
||||
@@ -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)."
|
||||
|
||||
@@ -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'
|
||||
---
|
||||
## <a name="about-the-dependency-graph"></a>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)."
|
||||
|
||||
## <a name="enabling-the-dependency-graph-via-the--data-variablesenterprisemanagement_console-"></a>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**.
|
||||
 {% 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)."
|
||||
|
||||
## <a name="enabling-the-dependency-graph-via-the-administrative-shell"></a>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**.
|
||||
|
||||
{% 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 %}.
|
||||
|
||||
@@ -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**.
|
||||
|
||||
3. Para sincronizar dados de vulnerabilidade, clique em **Sincronizar Vulnerabilidades agora**.
|
||||
|
||||
2. In the left sidebar, click **Vulnerabilities**.
|
||||
|
||||
3. To sync vulnerability data, click **Sync Vulnerabilities now**.
|
||||
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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**.
|
||||
|
||||
{% 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**.
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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**.
|
||||
|
||||
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**.
|
||||
|
||||
|
||||
@@ -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**.
|
||||
{% 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**.
|
||||
{% 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 %}
|
||||
|
||||
@@ -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**.
|
||||
|
||||
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**.
|
||||
|
||||
1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
|
||||
|
||||
1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**.
|
||||
|
||||
|
||||
@@ -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'
|
||||
---
|
||||
|
||||
|
||||
@@ -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 "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">Termos de Produtos e Recursos Adicionais do {% data variables.product.prodname_dotcom %}</a>".
|
||||
{% ifversion ghes %} {% else %}  {% endif %}
|
||||
1. Ao lado da conta corporativa ou de organização que deseja conectar, clique em **Conectar**.
|
||||
|
||||
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 "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features</a>."
|
||||
{% ifversion ghes %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Next to the enterprise account or organization you'd like to connect, click **Connect**.
|
||||
|
||||
|
||||
## 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 %} 
|
||||
1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** .
|
||||
|
||||
{% else %} 
|
||||
1. Leia as informações sobre como desconectar e clique em **Desabilitar o {% data variables.product.prodname_github_connect %}** .
|
||||
 {% 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 %}
|
||||
|
||||
1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
|
||||
|
||||
{% else %}
|
||||
|
||||
1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -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 %}.
|
||||
|
||||
5. Para testar as configurações de DNS e SSL para o novo nome do host, clique em **Testar configurações de domínio**.
|
||||
 {% 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 %}.
|
||||
|
||||
5. To test the DNS and SSL settings for the new hostname, click **Test domain settings**.
|
||||
|
||||
{% 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/)."
|
||||
|
||||
@@ -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.
|
||||
|
||||
{% 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.
|
||||
|
||||
|
||||
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`
|
||||
|
||||
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`
|
||||
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
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*.
|
||||
|
||||
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*.
|
||||
|
||||
{% 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.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
{% 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**.
|
||||
 {% data reusables.enterprise_management_console.save-settings %} {% data reusables.enterprise_management_console.privacy %}
|
||||
7. Clique em **Solicitar certificado TLS**.
|
||||
|
||||
8. Espere o "Status" mudar de "INICIADO" para "Concluído".
|
||||
|
||||
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**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
{% data reusables.enterprise_management_console.privacy %}
|
||||
7. Click **Request TLS certificate**.
|
||||
|
||||
8. Wait for the "Status" to change from "STARTED" to "DONE".
|
||||
|
||||
9. Click **Save configuration**.
|
||||
|
||||
@@ -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)** .
|
||||
 {% 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)**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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)"
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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.
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% data reusables.enterprise_management_console.test-domain-settings-failure %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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@<em>hostname</em>
|
||||
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 <em>hostname</em>
|
||||
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.
|
||||
|
||||
@@ -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)."
|
||||
|
||||
@@ -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 <em>QUEUE</em>
|
||||
$ ghe-aqueduct queue_depth --queue QUEUE
|
||||
# lists the number of currently queued jobs for the specified queue
|
||||
$ ghe-aqueduct pause --queue <em>QUEUE</em>
|
||||
$ ghe-aqueduct pause --queue QUEUE
|
||||
# pauses the specified queue
|
||||
$ ghe-aqueduct resume --queue <em>QUEUE</em>
|
||||
$ 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 <em>core.github-hostname</em>
|
||||
$ ghe-config core.github-hostname
|
||||
# Gets the configuration value of `core.github-hostname`
|
||||
$ ghe-config <em>core.github-hostname</em> <em>'example.com'</em>
|
||||
# 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 <em>HOSTNAME</em>.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 "<em>hubot</em> <em>github-actions</em>"
|
||||
$ 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 <em>REPOSITORY_ID</em>
|
||||
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 <em>USERNAME</em> -o <em>ORGANIZATION</em>
|
||||
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 <em>USERNAME</em>
|
||||
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 <em>ORGANIZATION</em>
|
||||
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 <new_password>
|
||||
@@ -348,31 +345,31 @@ ghe-set-password <new_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 <em>/path/to/certificate</em>
|
||||
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 <em>YYYY-MM-DD</em>
|
||||
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 <em>YYYYMMDD</em>
|
||||
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 <em>delivery-guid</em>
|
||||
ghe-webhook-logs -g DELIVERY_GUID
|
||||
```
|
||||
{% else %}
|
||||
```shell
|
||||
ghe-webhook-logs -g <em>delivery-guid</em> -v
|
||||
ghe-webhook-logs -g DELIVERY_GUID -v
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
@@ -528,7 +527,7 @@ ghe-webhook-logs -g <em>delivery-guid</em> -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@<em>hostname</em> -- '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@<em>hostname</em> -- '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@<em>hostname</em> -- '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@<em>hostname</em> -- 'ghe-cluster-support-bundle -t <em>ticket-id</em>'
|
||||
$ 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-<em>UUID</em>
|
||||
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-<em>UUID</em>
|
||||
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-<em>UUID</em>
|
||||
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 [ <port number> | --help | --usage ]
|
||||
@@ -634,7 +633,7 @@ ghe-btop [ <port number> | --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 <subcommand> <column> [options]
|
||||
@@ -659,33 +658,33 @@ Try ghe-governor <subcommand> --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 <em>username</em>/<em>reponame</em>
|
||||
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 <em>username</em>/<em>reponame</em>
|
||||
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 [<em>provider</em>] -cs ["<em>connectionstring</em>"]
|
||||
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@<em>hostname</em> -- '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@<em>hostname</em> -- '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@<em>hostname</em> -- '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@<em>hostname</em> -- 'ghe-support-bundle -t <em>ticket-id</em>'
|
||||
$ 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 <em>path/to/your/file</em> -t <em>ticket-id</em>
|
||||
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
|
||||
<em>ghe-repl-status -vv</em> | ghe-support-upload -t <em>ticket-id</em> -d "<em>Verbose Replication Status</em>"
|
||||
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 <em>UPGRADE-PACKAGE-FILENAME</em>
|
||||
ghe-upgrade --verify UPGRADE-PACKAGE-FILENAME
|
||||
```
|
||||
|
||||
Para instalar um pacote de atualização:
|
||||
To install an upgrade package:
|
||||
```shell
|
||||
ghe-upgrade <em>UPGRADE-PACKAGE-FILENAME</em>
|
||||
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 *" <em>UPGRADE-PACKAGE-FILENAME</em>
|
||||
$ 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 <em>UPGRADE PACKAGE FILENAME</em>
|
||||
> 0 2 15 12 * /usr/local/bin/ghe-upgrade -y -s <em>UPGRADE-PACKAGE-FILENAME</em> > /data/user/common/<em>UPGRADE-PACKAGE-FILENAME</em>.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 <em>UPGRADE PACKAGE FILENAME</em>
|
||||
$ 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@<em>hostname</em> -- '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=<em>SETTING</em>
|
||||
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 <em>some-user-name</em>
|
||||
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 <em>some-user-name</em>
|
||||
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 <em>some-user-name</em>
|
||||
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 <em>some-user-name</em>
|
||||
ghe-user-unsuspend USERNAME
|
||||
```
|
||||
|
||||
@@ -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**.
|
||||
|
||||
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.
|
||||
 {% 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**.
|
||||
|
||||
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.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
|
||||
@@ -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 %}
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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 %}** .
|
||||
 {% 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 %}**.
|
||||
|
||||
{% 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.
|
||||
 {% 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.
|
||||
|
||||
{% 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 %}
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 %}.
|
||||
|
||||
|
||||
@@ -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.
|
||||
|
||||
<pre>
|
||||
$ ghe-config app.gitauth.rsa-sha1 <em>RFC-3339-UTC-TIMESTAMP</em>
|
||||
$ ghe-config app.gitauth.rsa-sha1 RFC-3339-UTC-TIMESTAMP
|
||||
</pre>
|
||||
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
|
||||
|
||||
@@ -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**.
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
|
||||
{% 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**.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
{% 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**.
|
||||
|
||||
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**.
|
||||
|
||||
- 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.
|
||||
|
||||
4. Selecione **Habilitar modo de manutenção**.
|
||||
 {% 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**.
|
||||
|
||||
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**.
|
||||
|
||||
- To schedule a maintenance window for a future time, use the drop-down menu and click a start time.
|
||||
|
||||
4. Select **Enable maintenance mode**.
|
||||
|
||||
{% 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.
|
||||
|
||||
1. Selecione **Habilitar lista de exceções de IP**.
|
||||
|
||||
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 %}.
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
|
||||
{% 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.
|
||||
|
||||
1. Select **Enable IP exception list**.
|
||||
|
||||
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 %}.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
|
||||
{% 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
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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**.
|
||||
|
||||
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**.
|
||||
|
||||
|
||||
## 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**.
|
||||
|
||||
1. Em "URL de logon", copie e cole a URL no seu IdP do SAML.
|
||||
|
||||
1. Em "Emissor", copie e cole a URL do emissor para o seu IdP do SAML.
|
||||
|
||||
1. Em "Certificado público, copie e cole o certificado público no seu IdP do SAML.
|
||||
|
||||
1. Clique em **Testar configuração do SAML** para garantir que as informações inseridas estejam corretas.
|
||||
|
||||
1. Clique em **Salvar**.
|
||||
|
||||
1. To the right of "Set up your identity provider", click **Configure**.
|
||||
|
||||
1. Under "Sign on URL", copy and paste the URL for your SAML IdP.
|
||||
|
||||
1. Under "Issuer", copy and paste the issuer URL for your SAML IdP.
|
||||
|
||||
1. Under "Public certificate", copy and paste the public certificate for your SAML IdP.
|
||||
|
||||
1. Click **Test SAML configuration** to ensure that the information you've entered is correct.
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
|
||||
## 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**.
|
||||
|
||||
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**
|
||||
|
||||
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**.
|
||||
|
||||
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**
|
||||
|
||||
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**
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
8. Em "Pushes forçados", use o menu suspenso e escolha se deseja permitir ou bloquear pushes forçados.
|
||||
|
||||
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.
|
||||
|
||||
10. Clique em **Salvar**
|
||||
|
||||
11. Opcionalmente, para redefinir todas as seleções, clique em "Redefinir para as políticas padrão".
|
||||
|
||||
1. To the right of "Set your enterprise policies", click **Configure**.
|
||||
|
||||
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**
|
||||
|
||||
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**.
|
||||
|
||||
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**
|
||||
|
||||
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**
|
||||
|
||||
6. Under "Default repository visibility", use the drop-down menu and click the default visibility setting for new repositories.
|
||||
|
||||
7. Under "Users can create organizations", use the drop-down menu to enable or disable organization creation access for members of the enterprise.
|
||||
|
||||
8. Under "Force pushes", use the drop-down menu and choose whether to allow or block force pushes.
|
||||
|
||||
9. Under "Git SSH access", use the drop-down menu and choose whether to enable Git SSH access for all repositories in the enterprise.
|
||||
|
||||
10. Click **Save**
|
||||
|
||||
11. Optionally, to reset all selections, click "Reset to default policies".
|
||||
|
||||
|
||||
## 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**.
|
||||
|
||||
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.
|
||||
|
||||
3. Clique em **Salvar**.
|
||||
|
||||
1. To the right of "Internal support contact", click **Configure**.
|
||||
|
||||
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.
|
||||
|
||||
3. Click **Save**.
|
||||
|
||||
|
||||
## 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**.
|
||||
|
||||
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)".
|
||||
|
||||
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**.
|
||||
|
||||
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)."
|
||||
|
||||
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**.
|
||||
|
||||
5. Clique em **Configurações de email de teste**.
|
||||
|
||||
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**.
|
||||
|
||||
7. Clique em **Salvar**.
|
||||
|
||||
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**.
|
||||
|
||||
5. Click **Test email settings**.
|
||||
|
||||
6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**.
|
||||
|
||||
7. Click **Save**.
|
||||
|
||||
|
||||
@@ -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**.
|
||||
|
||||
1. Em "GitHub Mobile", marque ou desmarque a opção **Habilitar o GitHub Mobile Apps**.
|
||||
 {% 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**.
|
||||
|
||||
1. Under "GitHub Mobile", select or deselect **Enable GitHub Mobile Apps**.
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
@@ -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).
|
||||
|
||||
@@ -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)."
|
||||
|
||||
@@ -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**.
|
||||
|
||||
{% 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**.
|
||||
|
||||
|
||||
## 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)." |
|
||||
|
||||
@@ -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"
|
||||
</Plugin>
|
||||
|
||||
## 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 %}.
|
||||
|
||||
@@ -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**.
|
||||
|
||||
|
||||
|
||||
|
||||
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**.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
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**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
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 %}.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -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'
|
||||
---
|
||||
|
||||
|
||||
@@ -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.
|
||||
 {% 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`.
|
||||
|
||||
{% 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 <em>community-string</em> -O e <em>hostname</em> 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**.
|
||||
|
||||
5. Em "Username" (Nome de usuário), digite o nome exclusivo do seu usuário SNMP v3.
|
||||
|
||||
6. No menu suspenso **Nível de segurança**, clique no nível de segurança do seu usuário do SNMP v3.
|
||||
|
||||
7. Para usuários do SNMP v3 com o nível de segurança `authnopriv`: 
|
||||
{% 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**.
|
||||
|
||||
5. In "Username", type the unique username of your SNMP v3 user.
|
||||
|
||||
6. In the **Security Level** dropdown menu, click the security level for your SNMP v3 user.
|
||||
|
||||
7. For SNMP v3 users with the `authnopriv` security level:
|
||||
|
||||
- {% 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`: 
|
||||
8. For SNMP v3 users with the `authpriv` security level:
|
||||
|
||||
- {% 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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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 <em>community-string</em> -O e <em>hostname</em>
|
||||
$ 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 <em>username</em> -l authPriv \
|
||||
-A "<em>auth password</em>" -a SHA \
|
||||
-X "<em>privacy password</em>" -x AES \
|
||||
-O e <em>hostname</em> 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 <em>community-string</em> <em>hostname</em> 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)".
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -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**.
|
||||
 {% 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**.
|
||||
|
||||
{% 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.
|
||||
|
||||
|
||||
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -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: 
|
||||
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:
|
||||
|
||||
5. To start the virtual machine, click **OK**.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user