From 8a59dec094e84e2914de03552a535ac601c848a5 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Fri, 17 Dec 2021 11:59:44 -0600 Subject: [PATCH] New translation batch for pt (#23830) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check parsing * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt * run script/i18n/reset-known-broken-translation-files.js * Check in pt CSV report --- translations/log/pt-resets.csv | 111 ++++- .../content/actions/creating-actions/index.md | 2 +- .../deploying-docker-to-azure-app-service.md | 153 +++++++ .../deploying-java-to-azure-app-service.md | 134 ++++++ .../deploying-net-to-azure-app-service.md | 144 ++++++ .../deploying-nodejs-to-azure-app-service.md | 141 ++++++ .../deploying-php-to-azure-app-service.md | 155 +++++++ .../deploying-python-to-azure-app-service.md | 151 +++++++ .../deploying-to-azure-kubernetes-service.md | 126 ++++++ .../deploying-to-azure-static-web-app.md | 113 +++++ .../deploying-to-azure/index.md | 19 + .../deploying-to-your-cloud-provider/index.md | 11 +- translations/pt-BR/content/actions/guides.md | 9 +- translations/pt-BR/content/actions/index.md | 6 +- .../actions/learn-github-actions/contexts.md | 2 +- .../actions/learn-github-actions/index.md | 2 +- .../learn-github-actions/reusing-workflows.md | 27 +- .../using-workflow-templates.md | 8 +- .../migrating-to-github-actions/index.md | 2 +- .../using-saml.md | 9 + ...-enterprise-server-with-a-load-balancer.md | 4 +- .../site-admin-dashboard.md | 4 +- ...rise-account-to-github-enterprise-cloud.md | 11 +- ...dabot-alerts-on-your-enterprise-account.md | 2 + ...rise-server-with-github-actions-enabled.md | 51 ++- ...lling-github-enterprise-server-on-azure.md | 2 +- .../content/admin/overview/about-github-ae.md | 35 +- ...bout-alerts-for-vulnerable-dependencies.md | 7 +- ...ilities-in-the-github-advisory-database.md | 120 +++-- .../about-wikis.md | 2 +- .../adding-or-editing-wiki-pages.md | 64 +-- ...ating-a-footer-or-sidebar-for-your-wiki.md | 40 +- .../editing-wiki-content.md | 63 +-- .../index.md | 10 +- ...imiting-interactions-in-your-repository.md | 2 +- ...munity-profiles-for-public-repositories.md | 40 +- .../index.md | 8 +- ...-guidelines-for-repository-contributors.md | 60 +-- .../index.md | 8 +- ...ngle-issue-template-for-your-repository.md | 58 +-- .../authenticating-with-github-apps.md | 4 +- .../creating-a-github-app.md | 64 +-- ...g-and-authorizing-users-for-github-apps.md | 4 +- .../apps/building-github-apps/index.md | 6 +- .../rate-limits-for-github-apps.md | 6 +- .../setting-permissions-for-github-apps.md | 11 +- .../authorizing-oauth-apps.md | 10 +- .../creating-an-oauth-app.md | 31 +- .../apps/building-oauth-apps/index.md | 6 +- .../scopes-for-oauth-apps.md | 4 +- .../getting-started-with-apps/about-apps.md | 6 +- ...nces-between-github-apps-and-oauth-apps.md | 4 +- .../using-the-github-api-in-your-app.md | 191 ++++---- .../pt-BR/content/developers/apps/index.md | 14 +- .../deleting-a-github-app.md | 17 +- .../editing-a-github-apps-permissions.md | 27 +- .../apps/managing-github-apps/index.md | 6 +- .../making-a-github-app-public-or-private.md | 8 +- .../modifying-a-github-app.md | 11 +- .../transferring-ownership-of-a-github-app.md | 22 +- .../deleting-an-oauth-app.md | 14 +- .../apps/managing-oauth-apps/index.md | 6 +- .../modifying-an-oauth-app.md | 7 +- .../transferring-ownership-of-an-oauth-app.md | 22 +- ...leshooting-authorization-request-errors.md | 30 +- ...g-oauth-app-access-token-request-errors.md | 34 +- .../requirements-for-listing-an-app.md | 10 +- .../security-best-practices-for-apps.md | 78 ++-- .../viewing-metrics-for-your-listing.md | 48 +- .../about-github-marketplace.md | 2 +- .../developers/github-marketplace/index.md | 6 +- ...a-webhook-to-notify-you-of-plan-changes.md | 39 +- .../drafting-a-listing-for-your-app.md | 63 +-- .../index.md | 20 +- .../setting-pricing-plans-for-your-listing.md | 87 ++-- ...ting-a-listing-description-for-your-app.md | 14 +- .../billing-customers.md | 45 +- .../index.md | 16 +- ...icing-plans-for-github-marketplace-apps.md | 2 +- .../handling-new-purchases-and-free-trials.md | 67 ++- .../handling-plan-cancellations.md | 31 +- .../handling-plan-changes.md | 49 +-- .../index.md | 10 +- ...ndpoints-for-the-github-marketplace-api.md | 29 +- .../testing-your-app.md | 37 +- ...k-events-for-the-github-marketplace-api.md | 85 ++-- .../overview/managing-deploy-keys.md | 2 +- .../overview/replacing-github-services.md | 72 +-- .../secret-scanning-partner-program.md | 144 +++--- .../overview/using-ssh-agent-forwarding.md | 82 ++-- .../webhooks/webhook-events-and-payloads.md | 11 +- .../about-discussions.md | 56 +-- .../pt-BR/content/get-started/index.md | 1 + .../about-versions-of-github-docs.md | 56 +++ .../learning-about-github/githubs-products.md | 2 + .../learning-about-github/index.md | 3 +- .../getting-started-with-github-ae.md | 7 +- ...ng-started-with-github-enterprise-cloud.md | 10 +- ...g-started-with-github-enterprise-server.md | 10 +- .../getting-started-with-github-team.md | 9 +- ...etting-started-with-your-github-account.md | 10 +- ...g-up-a-trial-of-github-enterprise-cloud.md | 2 + ...-up-a-trial-of-github-enterprise-server.md | 1 + translations/pt-BR/content/issues/index.md | 12 +- .../about-project-boards.md | 70 +-- .../closing-a-project-board.md | 31 +- .../creating-a-project-board.md | 37 +- .../deleting-a-project-board.md | 24 +- .../editing-a-project-board.md | 26 +- ...es-and-pull-requests-to-a-project-board.md | 70 +-- .../adding-notes-to-a-project-board.md | 76 ++-- .../about-issues.md | 45 +- .../linking-a-pull-request-to-an-issue.md | 4 +- ...milestones-for-issues-and-pull-requests.md | 46 +- .../managing-labels.md | 75 ++-- ...e-to-delete-issues-in-your-organization.md | 13 +- ...-your-organizations-dependency-insights.md | 15 +- .../converting-an-organization-into-a-user.md | 30 +- .../deleting-an-organization-account.md | 17 +- ...e-for-repositories-in-your-organization.md | 27 +- ...pproving-a-domain-for-your-organization.md | 40 +- .../index.md | 4 +- ...-security-managers-in-your-organization.md | 8 +- .../about-github-pages.md | 12 +- ...ithub-pages-site-with-the-theme-chooser.md | 49 ++- ...shing-source-for-your-github-pages-site.md | 39 +- ...tom-404-page-for-your-github-pages-site.md | 19 +- .../creating-a-github-pages-site.md | 39 +- .../index.md | 8 +- .../unpublishing-a-github-pages-site.md | 27 +- .../using-submodules-with-github-pages.md | 20 +- .../about-github-pages-and-jekyll.md | 84 ++-- ...yll-build-errors-for-github-pages-sites.md | 23 +- ...reating-a-github-pages-site-with-jekyll.md | 65 +-- .../index.md | 8 +- ...r-github-pages-site-locally-with-jekyll.md | 42 +- .../addressing-merge-conflicts/index.md | 9 +- ...a-merge-conflict-using-the-command-line.md | 97 ++-- .../about-status-checks.md | 53 ++- .../about-pull-request-merges.md | 53 ++- .../index.md | 9 +- .../about-branches.md | 2 +- .../about-pull-requests.md | 2 +- ...eleting-branches-within-your-repository.md | 2 +- .../index.md | 9 +- ...ery-parameters-to-create-a-pull-request.md | 32 +- .../commenting-on-a-pull-request.md | 48 +- .../filtering-files-in-a-pull-request.md | 27 +- .../index.md | 9 +- .../guides/best-practices-for-integrators.md | 115 ++--- .../rest/guides/building-a-ci-server.md | 114 +++-- .../rest/guides/delivering-deployments.md | 130 ++++-- .../discovering-resources-for-a-user.md | 2 +- .../getting-started-with-the-rest-api.md | 2 +- .../rest/guides/rendering-data-as-graphs.md | 112 +++-- .../rest/guides/traversing-with-pagination.md | 2 +- .../rest/guides/working-with-comments.md | 2 +- .../pt-BR/content/rest/overview/libraries.md | 156 +++---- .../overview/resources-in-the-rest-api.md | 414 ++++++++++-------- .../rest/reference/enterprise-admin.md | 2 +- .../pt-BR/content/rest/reference/orgs.md | 36 +- .../about-searching-on-github.md | 10 +- ...rom-your-private-enterprise-environment.md | 6 +- .../understanding-the-search-syntax.md | 117 +++-- .../pt-BR/content/search-github/index.md | 10 +- .../searching-for-repositories.md | 2 +- .../searching-issues-and-pull-requests.md | 2 +- .../features/actions-starter-template-ui.yml | 6 + .../actions/create-azure-app-plan.md | 17 + .../actions/create-azure-publish-profile.md | 5 + .../you-can-read-docs-for-your-product.md | 1 + .../dormant-user-activity-threshold.md | 2 +- .../locking-repositories.md | 2 +- ...ng-access-to-repositories-projects-apps.md | 2 +- .../getting-started/managing-team-settings.md | 2 +- .../new-repo-permissions-more-info.md | 2 +- .../reusables/pages/check-workflow-run.md | 8 + ...-builds-with-github-actions-public-beta.md | 5 + .../pages/twenty-minutes-to-publish.md | 2 +- .../data/reusables/saml/saml-accounts.md | 8 +- .../partner-secret-list-private-repo.md | 2 + translations/pt-BR/data/ui.yml | 1 + translations/pt-BR/data/variables/product.yml | 5 +- 183 files changed, 4112 insertions(+), 2346 deletions(-) create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md create mode 100644 translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md create mode 100644 translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md create mode 100644 translations/pt-BR/data/features/actions-starter-template-ui.yml create mode 100644 translations/pt-BR/data/reusables/actions/create-azure-app-plan.md create mode 100644 translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md create mode 100644 translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md create mode 100644 translations/pt-BR/data/reusables/pages/check-workflow-run.md create mode 100644 translations/pt-BR/data/reusables/pages/pages-builds-with-github-actions-public-beta.md diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv index b1645c8f87..f47ca601c9 100644 --- a/translations/log/pt-resets.csv +++ b/translations/log/pt-resets.csv @@ -62,8 +62,17 @@ translations/pt-BR/content/actions/creating-actions/setting-exit-codes-for-actio 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,rendering error 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-app-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 +translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,rendering error +translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,rendering error +translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,rendering error +translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,rendering error +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-azure/index.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/deploying-to-your-cloud-provider/index.md,rendering error translations/pt-BR/content/actions/deployment/deploying-xcode-applications/installing-an-apple-certificate-on-macos-runners-for-xcode-development.md,rendering error translations/pt-BR/content/actions/deployment/index.md,rendering error translations/pt-BR/content/actions/deployment/managing-your-deployments/viewing-deployment-history.md,rendering error @@ -227,6 +236,7 @@ translations/pt-BR/content/admin/enterprise-support/overview/about-github-premiu translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/index.md,rendering error translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/providing-data-to-github-support.md,rendering error translations/pt-BR/content/admin/enterprise-support/receiving-help-from-github-support/reaching-github-support.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,rendering error translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,rendering error translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.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-ae.md,rendering error @@ -256,6 +266,7 @@ translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-ser translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,rendering error translations/pt-BR/content/admin/overview/about-enterprise-accounts.md,rendering error +translations/pt-BR/content/admin/overview/about-github-ae.md,rendering error translations/pt-BR/content/admin/overview/about-the-github-enterprise-api.md,rendering error translations/pt-BR/content/admin/overview/about-upgrades-to-new-releases.md,rendering error translations/pt-BR/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error @@ -411,6 +422,7 @@ translations/pt-BR/content/code-security/security-overview/about-the-security-ov translations/pt-BR/content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates.md,rendering error +translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md,rendering error translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error @@ -448,10 +460,19 @@ translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/set translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces.md,rendering error translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,rendering error translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error +translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md,rendering error +translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md,rendering error +translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error +translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md,rendering error translations/pt-BR/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md,rendering error translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md,rendering error translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md,rendering error translations/pt-BR/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md,rendering error +translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md,rendering error +translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md,rendering error +translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error +translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md,rendering error +translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md,rendering error translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,rendering error translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/managing-branches.md,rendering error translations/pt-BR/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request.md,rendering error @@ -460,27 +481,65 @@ translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/ove 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/creating-a-github-app-from-a-manifest.md,rendering error translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md,rendering error +translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md,rendering error translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error +translations/pt-BR/content/developers/apps/building-github-apps/index.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,rendering error translations/pt-BR/content/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens.md,rendering error +translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md,rendering error translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md,rendering error +translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md,rendering error +translations/pt-BR/content/developers/apps/building-oauth-apps/index.md,rendering error translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md,rendering error translations/pt-BR/content/developers/apps/getting-started-with-apps/migrating-oauth-apps-to-github-apps.md,rendering error translations/pt-BR/content/developers/apps/guides/index.md,rendering error translations/pt-BR/content/developers/apps/guides/using-content-attachments.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/apps/index.md,rendering error +translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md,rendering error +translations/pt-BR/content/developers/apps/managing-github-apps/index.md,rendering error translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md,rendering error +translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md,rendering error +translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md,rendering error translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,rendering error +translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md,rendering error translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md,rendering error +translations/pt-BR/content/developers/github-marketplace/index.md,rendering error +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md,rendering error +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md,rendering error +translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md,rendering error translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md,rendering error +translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md,rendering error translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/receiving-payment-for-app-purchases.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md,rendering error +translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md,rendering error translations/pt-BR/content/developers/overview/managing-deploy-keys.md,rendering error +translations/pt-BR/content/developers/overview/replacing-github-services.md,rendering error +translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md,rendering error +translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md,rendering error translations/pt-BR/content/developers/webhooks-and-events/events/issue-event-types.md,rendering error translations/pt-BR/content/developers/webhooks-and-events/webhooks/securing-your-webhooks.md,rendering error 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/about-discussions.md,rendering error translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,rendering error translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,rendering error translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,rendering error @@ -508,6 +567,7 @@ translations/pt-BR/content/get-started/getting-started-with-git/managing-remote- translations/pt-BR/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error translations/pt-BR/content/get-started/index.md,rendering error 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/about-versions-of-github-docs.md,rendering error translations/pt-BR/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error translations/pt-BR/content/get-started/learning-about-github/githubs-products.md,rendering error translations/pt-BR/content/get-started/learning-about-github/index.md,rendering error @@ -599,6 +659,15 @@ translations/pt-BR/content/graphql/guides/migrating-graphql-global-node-ids.md,r translations/pt-BR/content/graphql/index.md,rendering error translations/pt-BR/content/graphql/reference/mutations.md,rendering error translations/pt-BR/content/issues/guides.md,rendering error +translations/pt-BR/content/issues/index.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md,rendering error +translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md,rendering error +translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/about-task-lists.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/creating-an-issue.md,rendering error translations/pt-BR/content/issues/tracking-your-work-with-issues/deleting-an-issue.md,rendering error @@ -616,6 +685,8 @@ translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managin translations/pt-BR/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md,rendering error translations/pt-BR/content/issues/trying-out-the-new-projects-experience/quickstart.md,rendering error translations/pt-BR/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,rendering error +translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md,rendering error +translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md,rendering error translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-organizations.md,rendering error translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error translations/pt-BR/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md,rendering error @@ -651,14 +722,22 @@ translations/pt-BR/content/organizations/managing-membership-in-your-organizatio translations/pt-BR/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error 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/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/renaming-an-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/setting-permissions-for-deleting-or-transferring-repositories.md,rendering error translations/pt-BR/content/organizations/managing-organization-settings/transferring-organization-ownership.md,rendering error +translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md,rendering error +translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md,rendering error translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md,rendering error +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-peoples-access-to-your-organization-with-roles/roles-in-an-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,rendering error translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md,rendering error @@ -707,17 +786,33 @@ translations/pt-BR/content/pages/configuring-a-custom-domain-for-your-github-pag 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/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md,rendering error translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/index.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error +translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error translations/pt-BR/content/pages/index.md,rendering error +translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error +translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error +translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/index.md,rendering error translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,rendering error +translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md,rendering error translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/index.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/getting-started/index.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md,rendering error @@ -725,6 +820,11 @@ translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/propos 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,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request.md,rendering error 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/index.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md,rendering error +translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.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,rendering error translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/working-with-forks/index.md,rendering error @@ -780,13 +880,19 @@ translations/pt-BR/content/repositories/working-with-files/managing-large-files/ translations/pt-BR/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error translations/pt-BR/content/repositories/working-with-files/using-files/navigating-code-on-github.md,rendering error translations/pt-BR/content/repositories/working-with-files/using-files/tracking-changes-in-a-file.md,rendering error +translations/pt-BR/content/rest/guides/best-practices-for-integrators.md,rendering error +translations/pt-BR/content/rest/guides/building-a-ci-server.md,rendering error +translations/pt-BR/content/rest/guides/delivering-deployments.md,rendering error translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md,rendering error translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md,rendering error translations/pt-BR/content/rest/guides/index.md,rendering error +translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md,rendering error translations/pt-BR/content/rest/guides/traversing-with-pagination.md,rendering error translations/pt-BR/content/rest/guides/working-with-comments.md,rendering error translations/pt-BR/content/rest/index.md,rendering error translations/pt-BR/content/rest/overview/api-previews.md,rendering error +translations/pt-BR/content/rest/overview/libraries.md,rendering error +translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md,rendering error translations/pt-BR/content/rest/reference/actions.md,rendering error translations/pt-BR/content/rest/reference/activity.md,rendering error translations/pt-BR/content/rest/reference/branches.md,rendering error @@ -798,6 +904,7 @@ translations/pt-BR/content/rest/reference/enterprise-admin.md,rendering error translations/pt-BR/content/rest/reference/gists.md,Listed in localization-support#489 translations/pt-BR/content/rest/reference/gists.md,rendering error translations/pt-BR/content/rest/reference/index.md,rendering error +translations/pt-BR/content/rest/reference/orgs.md,rendering error translations/pt-BR/content/rest/reference/packages.md,rendering error translations/pt-BR/content/rest/reference/pages.md,rendering error translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md,rendering error @@ -812,6 +919,8 @@ translations/pt-BR/content/rest/reference/teams.md,rendering error translations/pt-BR/content/rest/reference/webhooks.md,rendering error translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,rendering error translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error +translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md,rendering error +translations/pt-BR/content/search-github/index.md,rendering error translations/pt-BR/content/search-github/searching-on-github/searching-commits.md,rendering error translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md,rendering error translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md,rendering error diff --git a/translations/pt-BR/content/actions/creating-actions/index.md b/translations/pt-BR/content/actions/creating-actions/index.md index 7ed06229d7..1d91ced73d 100644 --- a/translations/pt-BR/content/actions/creating-actions/index.md +++ b/translations/pt-BR/content/actions/creating-actions/index.md @@ -6,7 +6,7 @@ redirect_from: - /github/automating-your-workflow-with-github-actions/building-actions - /actions/automating-your-workflow-with-github-actions/building-actions - /actions/building-actions - - /articles/creating-a-github-action/ + - /articles/creating-a-github-action versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md new file mode 100644 index 0000000000..8133adef88 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md @@ -0,0 +1,153 @@ +--- +title: Deploying Docker to Azure App Service +intro: You can deploy a Docker container to Azure App Service as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Containers + - Docker + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +1. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --deployment-container-image-name nginx:latest + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +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)." + + 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: + + ```shell + az webapp config appsettings set \ + --name MY_WEBAPP_NAME \ + --resource-group MY_RESOURCE_GROUP \ + --settings DOCKER_REGISTRY_SERVER_URL=https://ghcr.io DOCKER_REGISTRY_SERVER_USERNAME=MY_REPOSITORY_OWNER DOCKER_REGISTRY_SERVER_PASSWORD=MY_PERSONAL_ACCESS_TOKEN +``` + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a Docker container to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy a container to an Azure Web App + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + +on: + push: + branches: + - main + +permissions: + contents: 'read' + packages: 'write' + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Set up Docker Buildx + uses: docker/setup-buildx-action@v1 + + - name: Log in to GitHub container registry + uses: docker/login-action@v1.10.0 + with: + registry: ghcr.io + username: {% raw %}${{ github.actor }}{% endraw %} + password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %} + + - name: Lowercase the repo name + run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV} + + - name: Build and push container image to registry + uses: docker/build-push-action@v2 + with: + push: true + tags: ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %} + file: ./Dockerfile + + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Lowercase the repo name + run: echo "REPO=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV} + + - name: Deploy to Azure Web App + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} + images: 'ghcr.io/{% raw %}${{ env.REPO }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %}' +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-container-webapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-container-webapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md new file mode 100644 index 0000000000..7959f41764 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md @@ -0,0 +1,134 @@ +--- +title: Deploying Java to Azure App Service +intro: You can deploy your Java project to Azure App Service as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Java + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +1. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app with a Java runtime: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "JAVA|11-java11" + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +1. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a Java project to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you want to use a Java version other than `11`, change `JAVA_VERSION`. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy JAR app to Azure Web App + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + JAVA_VERSION: '11' # set this to the Java version to use + +on: + push: + branches: + - main + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Set up Java version + uses: actions/setup-java@v2.3.1 + with: + java-version: {% raw %}${{ env.JAVA_VERSION }}{% endraw %} + cache: 'maven' + + - name: Build with Maven + run: mvn clean install + + - name: Upload artifact for deployment job + uses: actions/upload-artifact@v2 + with: + name: java-app + path: '{% raw %}${{ github.workspace }}{% endraw %}/target/*.jar' + + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Download artifact from build job + uses: actions/download-artifact@v2 + with: + name: java-app + + - name: Deploy to Azure Web App + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} + package: '*.jar' +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-webapps-java-jar.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-java-jar.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md new file mode 100644 index 0000000000..2da7e39ce0 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md @@ -0,0 +1,144 @@ +--- +title: Deploying .NET to Azure App Service +intro: You can deploy your .NET project to Azure App Service as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +2. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app with a .NET runtime: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "DOTNET|5.0" + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a .NET project to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH`. If you use a version of .NET other than `5`, change `DOTNET_VERSION`. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy ASP.Net Core app to an Azure Web App + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root + DOTNET_VERSION: '5' # set this to the .NET Core version to use + +on: + push: + branches: + - main + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Set up .NET Core + uses: actions/setup-dotnet@v1 + with: + dotnet-version: {% raw %}${{ env.DOTNET_VERSION }}{% endraw %} + + - name: Set up dependency caching for faster builds + uses: actions/cache@v2 + with: + path: ~/.nuget/packages + key: {% raw %}${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}{% endraw %} + restore-keys: | + {% raw %}${{ runner.os }}-nuget-{% endraw %} + + - name: Build with dotnet + run: dotnet build --configuration Release + + - name: dotnet publish + run: dotnet publish -c Release -o {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp + + - name: Upload artifact for deployment job + uses: actions/upload-artifact@v2 + with: + name: .net-app + path: {% raw %}${{env.DOTNET_ROOT}}{% endraw %}/myapp + + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Download artifact from build job + uses: actions/download-artifact@v2 + with: + name: .net-app + + - name: Deploy to Azure Web App + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} + package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %} +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-webapps-dotnet-core.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-dotnet-core.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md new file mode 100644 index 0000000000..e6f8f08b7c --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -0,0 +1,141 @@ +--- +title: Deploying Node.js to Azure App Service +intro: You can deploy your Node.js project to Azure App Service as part of your continuous deployment (CD) workflows. +redirect_from: + - /actions/guides/deploying-to-azure-app-service + - /actions/deployment/deploying-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure-app-service +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Node + - JavaScript + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +2. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app with a Node.js runtime: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "NODE|14-lts" + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build, test, and deploy the Node.js project to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to your project path. If you use a version of Node.js other than `10.x`, change `NODE_VERSION` to the version that you use. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +on: + push: + branches: + - main + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root + NODE_VERSION: '14.x' # set this to the node version to use + +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v2 + + - name: Set up Node.js + uses: actions/setup-node@v2 + with: + node-version: {% raw %}${{ env.NODE_VERSION }}{% endraw %} + cache: 'npm' + + - name: npm install, build, and test + run: | + npm install + npm run build --if-present + npm run test --if-present + - name: Upload artifact for deployment job + uses: actions/upload-artifact@v2 + with: + name: node-app + path: . + + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Download artifact from build job + uses: actions/download-artifact@v2 + with: + name: node-app + + - name: 'Deploy to Azure WebApp' + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} + package: {% raw %}${{ env.AZURE_WEBAPP_PACKAGE_PATH }}{% endraw %} +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-webapps-node.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-node.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the +[actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. +* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice). diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md new file mode 100644 index 0000000000..3931a1c6eb --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md @@ -0,0 +1,155 @@ +--- +title: Deploying PHP to Azure App Service +intro: You can deploy your PHP project to Azure App Service as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +2. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app with a PHP runtime: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "php|7.4" + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a PHP project to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If the path to your project is not the repository root, change `AZURE_WEBAPP_PACKAGE_PATH` to the path to your project. If you use a version of PHP other than `8.x`, change`PHP_VERSION` to the version that you use. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy PHP app to Azure Web App + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root + PHP_VERSION: '8.x' # set this to the PHP version to use + +on: + push: + branches: + - main + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Setup PHP + uses: shivammathur/setup-php@v2 + with: + php-version: {% raw %}${{ env.PHP_VERSION }}{% endraw %} + + - name: Check if composer.json exists + id: check_files + uses: andstor/file-existence-action@v1 + with: + files: 'composer.json' + + - name: Get Composer Cache Directory + id: composer-cache + if: steps.check_files.outputs.files_exists == 'true' + run: | + echo "::set-output name=dir::$(composer config cache-files-dir)" + + - name: Set up dependency caching for faster installs + uses: actions/cache@v2 + if: steps.check_files.outputs.files_exists == 'true' + with: + path: {% raw %}${{ steps.composer-cache.outputs.dir }}{% endraw %} + key: {% raw %}${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}{% endraw %} + restore-keys: | + {% raw %}${{ runner.os }}-composer-{% endraw %} + + - name: Run composer install if composer.json exists + if: steps.check_files.outputs.files_exists == 'true' + run: composer validate --no-check-publish && composer install --prefer-dist --no-progress + + - name: Upload artifact for deployment job + uses: actions/upload-artifact@v2 + with: + name: php-app + path: . + + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Download artifact from build job + uses: actions/download-artifact@v2 + with: + name: php-app + + - name: 'Deploy to Azure Web App' + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} + package: . +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-webapps-php.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-php.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md new file mode 100644 index 0000000000..f7001b459c --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md @@ -0,0 +1,151 @@ +--- +title: Deploying Python to Azure App Service +intro: You can deploy your Python project to Azure App Service as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Python + - Azure App Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +{% data reusables.actions.create-azure-app-plan %} + +1. Create a web app. + + For example, you can use the Azure CLI to create an Azure App Service web app with a Python runtime: + + ```bash{:copy} + az webapp create \ + --name MY_WEBAPP_NAME \ + --plan MY_APP_SERVICE_PLAN \ + --resource-group MY_RESOURCE_GROUP \ + --runtime "python|3.8" + ``` + + In the command above, replace the parameters with your own values, where `MY_WEBAPP_NAME` is a new name for the web app. + +{% data reusables.actions.create-azure-publish-profile %} + +1. Add an app setting called `SCM_DO_BUILD_DURING_DEPLOYMENT` and set the value to `1`. + +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +5. Optionally, configure a deployment environment. {% data reusables.actions.about-environments %} +{% endif %} + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a Python project to Azure App Service when there is a push to the `main` branch. + +Ensure that you set `AZURE_WEBAPP_NAME` in the workflow `env` key to the name of the web app you created. If you use a version of Python other than `3.8`, change `PYTHON_VERSION` to the version that you use. + +{% data reusables.actions.delete-env-key %} + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy Python app to Azure Web App + +env: + AZURE_WEBAPP_NAME: MY_WEBAPP_NAME # set this to your application's name + PYTHON_VERSION: '3.8' # set this to the Python version to use + +on: + push: + branches: + - main + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v2 + + - name: Set up Python version + uses: actions/setup-python@v2.2.2 + with: + python-version: {% raw %}${{ env.PYTHON_VERSION }}{% endraw %} + + - name: Create and start virtual environment + run: | + python -m venv venv + source venv/bin/activate + + - name: Set up dependency caching for faster installs + uses: actions/cache@v2 + with: + path: ~/.cache/pip + key: {% raw %}${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}{% endraw %} + restore-keys: | + {% raw %}${{ runner.os }}-pip-{% endraw %} + + - name: Install dependencies + run: pip install -r requirements.txt + + # Optional: Add a step to run tests here (PyTest, Django test suites, etc.) + + - name: Upload artifact for deployment jobs + uses: actions/upload-artifact@v2 + with: + name: python-app + path: | + . + !venv/ + deploy: + runs-on: ubuntu-latest + needs: build + environment: + name: 'production' + url: {% raw %}${{ steps.deploy-to-webapp.outputs.webapp-url }}{% endraw %} + + steps: + - name: Download artifact from build job + uses: actions/download-artifact@v2 + with: + name: python-app + path: . + + - name: 'Deploy to Azure Web App' + id: deploy-to-webapp + uses: azure/webapps-deploy@0b651ed7546ecfc75024011f76944cb9b381ef1e + with: + app-name: {% raw %}${{ env.AZURE_WEBAPP_NAME }}{% endraw %} + publish-profile: {% raw %}${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }}{% endraw %} +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-webapps-python.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-webapps-python.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md new file mode 100644 index 0000000000..f6ab7573d2 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md @@ -0,0 +1,126 @@ +--- +title: Deploying to Azure Kubernetes Service +intro: You can deploy your project to Azure Kubernetes Service (AKS) as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Azure Kubernetes Service +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +1. Create a target AKS cluster and an Azure Container Registry (ACR). For more information, see "[Quickstart: Deploy an AKS cluster by using the Azure portal - Azure Kubernetes Service](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough-portal)" and "[Quickstart - Create registry in portal - Azure Container Registry](https://docs.microsoft.com/azure/container-registry/container-registry-get-started-portal)" in the Azure documentation. + +1. Create a secret called `AZURE_CREDENTIALS` to store your Azure credentials. For more information about how to find this information and structure the secret, see [the `Azure/login` action documentation](https://github.com/Azure/login#configure-a-service-principal-with-a-secret). + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy a project to Azure Kubernetes Service when code is pushed to your repository. + +Under the workflow `env` key, change the the following values: +- `AZURE_CONTAINER_REGISTRY` to the name of your container registry +- `PROJECT_NAME` to the name of your project +- `RESOURCE_GROUP` to the resource group containing your AKS cluster +- `CLUSTER_NAME` to the name of your AKS cluster + +This workflow uses the `helm` render engine for the [`azure/k8s-bake` action](https://github.com/Azure/k8s-bake). If you will use the `helm` render engine, change the value of `CHART_PATH` to the path to your helm file. Change `CHART_OVERRIDE_PATH` to an array of override file paths. If you use a different render engine, update the input parameters sent to the `azure/k8s-bake` action. + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Build and deploy to Azure Kubernetes Service + +env: + AZURE_CONTAINER_REGISTRY: MY_REGISTRY_NAME # set this to the name of your container registry + PROJECT_NAME: MY_PROJECT_NAME # set this to your project's name + RESOURCE_GROUP: MY_RESOURCE_GROUP # set this to the resource group containing your AKS cluster + CLUSTER_NAME: MY_CLUSTER_NAME # set this to the name of your AKS cluster + REGISTRY_URL: MY_REGISTRY_URL # set this to the URL of your registry + # If you bake using helm: + CHART_PATH: MY_HELM_FILE # set this to the path to your helm file + CHART_OVERRIDE_PATH: MY_OVERRIDE_FILES # set this to an array of override file paths + +on: [push] + +jobs: + build: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@master + + - name: Azure Login + uses: azure/login@89d153571fe9a34ed70fcf9f1d95ab8debea7a73 + with: + creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %} + + - name: Build image on ACR + uses: azure/CLI@7378ce2ca3c38b4b063feb7a4cbe384fef978055 + with: + azcliversion: 2.29.1 + inlineScript: | + az configure --defaults acr={% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %} + az acr build -t -t {% raw %}${{ env.REGISTRY_URL }}{% endraw %}/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %} + + - name: Gets K8s context + uses: azure/aks-set-context@4e5aec273183a197b181314721843e047123d9fa + with: + creds: {% raw %}${{ secrets.AZURE_CREDENTIALS }}{% endraw %} + resource-group: {% raw %}${{ env.RESOURCE_GROUP }}{% endraw %} + cluster-name: {% raw %}${{ env.CLUSTER_NAME }}{% endraw %} + id: login + + - name: Configure deployment + uses: azure/k8s-bake@773b6144a3732e3bf4c78b146a0bb9617b2e016b + with: + renderEngine: 'helm' + helmChart: {% raw %}${{ env.CHART_PATH }}{% endraw %} + overrideFiles: {% raw %}${{ env.CHART_OVERRIDE_PATH }}{% endraw %} + overrides: | + replicas:2 + helm-version: 'latest' + id: bake + + - name: Deploys application + - uses: Azure/k8s-deploy@c8fbd76ededaad2799c054a9fd5d0fa5d4e9aee4 + with: + manifests: {% raw %}${{ steps.bake.outputs.manifestsBundle }}{% endraw %} + images: | + {% raw %}${{ env.AZURE_CONTAINER_REGISTRY }}{% endraw %}.azurecr.io/{% raw %}${{ env.PROJECT_NAME }}{% endraw %}:{% raw %}${{ github.sha }}{% endraw %} + imagepullsecrets: | + {% raw %}${{ env.PROJECT_NAME }}{% endraw %} +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-kubernetes-service.yml `](https://github.com/actions/starter-workflows/blob/main/deployments/azure-kubernetes-service.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The actions used to in this workflow are the official Azure [`Azure/login`](https://github.com/Azure/login),[`Azure/aks-set-context`](https://github.com/Azure/aks-set-context), [`Azure/CLI`](https://github.com/Azure/CLI), [`Azure/k8s-bake`](https://github.com/Azure/k8s-bake), and [`Azure/k8s-deploy`](https://github.com/Azure/k8s-deploy)actions. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md new file mode 100644 index 0000000000..cc6a363133 --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md @@ -0,0 +1,113 @@ +--- +title: Deploying to Azure Static Web App +intro: You can deploy your web app to Azure Static Web App as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - CD + - Azure Static Web Apps +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + + +## Introduction + +This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/). + +{% ifversion fpt or ghec or ghae-issue-4856 %} + +{% note %} + +**Note**: {% data reusables.actions.about-oidc-short-overview %} and "[Configuring OpenID Connect in Azure](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure)." + +{% endnote %} + +{% endif %} + +## Prerequisites + +Before creating your {% data variables.product.prodname_actions %} workflow, you will first need to complete the following setup steps: + +1. Create an Azure Static Web App using the 'Other' option for deployment source. For more information, see "[Quickstart: Building your first static site in the Azure portal](https://docs.microsoft.com/azure/static-web-apps/get-started-portal)" in the Azure documentation. + +2. Create a secret called `AZURE_STATIC_WEB_APPS_API_TOKEN` with the value of your static web app deployment token. For more information about how to find your deployment token, see "[Reset deployment tokens in Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/deployment-token-management)" in the Azure documentation. + +## Creating the workflow + +Once you've completed the prerequisites, you can proceed with creating the workflow. + +The following example workflow demonstrates how to build and deploy an Azure static web app when there is a push to the `main` branch or when a pull request targeting `main` is opened, synchronized, or reopened. The workflow also tears down the corresponding pre-production deployment when a pull request targeting `main` is closed. + +Under the workflow `env` key, change the following values: +- `APP_LOCATION` to the location of your client code +- `API_LOCATION` to the location of your API source code. If `API_LOCATION` is not relevant, you can delete the variable and the lines where it is used. +- `APP_ARTIFACT_LOCATION` to the location of your client code build output + +For more information about these values, see "[Build configuration for Azure Static Web Apps](https://docs.microsoft.com/azure/static-web-apps/build-configuration?tabs=github-actions)" in the Azure documentation. + +```yaml{:copy} +{% data reusables.actions.actions-not-certified-by-github-comment %} + +name: Deploy web app to Azure Static Web Apps + +env: + APP_LOCATION: "/" # location of your client code + API_LOCATION: "api" # location of your api source code - optional + APP_ARTIFACT_LOCATION: "build" # location of client code build output + + on: + push: + branches: + - main + pull_request: + types: [opened, synchronize, reopened, closed] + branches: + - main + +permissions: + issues: write + +jobs: + build_and_deploy: + if: github.event_name == 'push' || (github.event_name == 'pull_request' && github.event.action != 'closed') + runs-on: ubuntu-latest + name: Build and Deploy + steps: + - uses: actions/checkout@v2 + with: + submodules: true + - name: Build And Deploy + uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9 + with: + azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %} + repo_token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %} + action: "upload" + app_location: {% raw %}${{ env.APP_LOCATION }}{% endraw %} + api_location: {% raw %}${{ env.API_LOCATION }}{% endraw %} + app_artifact_location: {% raw %}${{ env.APP_ARTIFACT_LOCATION }}{% endraw %} + + close: + if: github.event_name == 'pull_request' && github.event.action == 'closed' + runs-on: ubuntu-latest + name: Close + steps: + - name: Close + uses: Azure/static-web-apps-deploy@1a947af9992250f3bc2e68ad0754c0b0c11566c9 + with: + azure_static_web_apps_api_token: {% raw %}${{ secrets.AZURE_STATIC_WEB_APPS_API_TOKEN }}{% endraw %} + action: "close" +``` + +## Additional resources + +The following resources may also be useful: + +* For the original starter workflow, see [`azure-staticwebapp.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure-staticwebapp.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository. +* The action used to deploy the web app is the official Azure [`Azure/static-web-apps-deploy`](https://github.com/Azure/static-web-apps-deploy) action. +* For more examples of GitHub Action workflows that deploy to Azure, see the [actions-workflow-samples](https://github.com/Azure/actions-workflow-samples) repository. diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md new file mode 100644 index 0000000000..293638875e --- /dev/null +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/index.md @@ -0,0 +1,19 @@ +--- +title: Deploying to Azure +shortTitle: Deploy to Azure +intro: Learn how to deploy to Azure App Service, Azure Kubernetes, and Azure Static Web App as part of your continuous deployment (CD) workflows. +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +children: + - /deploying-nodejs-to-azure-app-service + - /deploying-python-to-azure-app-service + - /deploying-java-to-azure-app-service + - /deploying-net-to-azure-app-service + - /deploying-php-to-azure-app-service + - /deploying-docker-to-azure-app-service + - /deploying-to-azure-static-web-app + - /deploying-to-azure-kubernetes-service +--- diff --git a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md index ab1075cbf0..cf77b48a2c 100644 --- a/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md +++ b/translations/pt-BR/content/actions/deployment/deploying-to-your-cloud-provider/index.md @@ -1,14 +1,13 @@ --- -title: Fazendo a implantação no seu provedor de nuvem -shortTitle: Fazendo a implantação no seu provedor de nuvem -intro: 'Você pode fazer a implantação em vários provedores de nuvem como, por exemplo, AWS, Azure e GKE.' +title: Deploying to your cloud provider +shortTitle: Deploying to your cloud provider +intro: 'You can deploy to various cloud providers, such as AWS, Azure, and GKE.' versions: fpt: '*' - ghae: issue-4856 + ghae: 'issue-4856' ghec: '*' children: - /deploying-to-amazon-elastic-container-service - - /deploying-to-azure-app-service + - /deploying-to-azure - /deploying-to-google-kubernetes-engine --- - diff --git a/translations/pt-BR/content/actions/guides.md b/translations/pt-BR/content/actions/guides.md index 2c15577f19..3a445c387b 100644 --- a/translations/pt-BR/content/actions/guides.md +++ b/translations/pt-BR/content/actions/guides.md @@ -43,7 +43,6 @@ includeGuides: - /actions/using-containerized-services/creating-redis-service-containers - /actions/using-containerized-services/creating-postgresql-service-containers - /actions/deployment/deploying-to-amazon-elastic-container-service - - /actions/deployment/deploying-to-azure-app-service - /actions/deployment/deploying-to-google-kubernetes-engine - /actions/learn-github-actions/essential-features-of-github-actions - /actions/security-guides/security-hardening-for-github-actions @@ -64,5 +63,13 @@ includeGuides: - /actions/managing-issues-and-pull-requests/removing-a-label-when-a-card-is-added-to-a-project-board-column - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app + - /actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service --- diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index 5eff35a61d..874053eb2b 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -30,10 +30,10 @@ changelog: examples_source: data/product-examples/actions/code-examples.yml product_video: 'https://www.youtube-nocookie.com/embed/cP0I9w2coGU' redirect_from: - - /articles/automating-your-workflow-with-github-actions/ - - /articles/customizing-your-project-with-github-actions/ + - /articles/automating-your-workflow-with-github-actions + - /articles/customizing-your-project-with-github-actions - /github/automating-your-workflow-with-github-actions - - /actions/automating-your-workflow-with-github-actions/ + - /actions/automating-your-workflow-with-github-actions - /categories/automating-your-workflow-with-github-actions - /marketplace/actions - /actions/reference diff --git a/translations/pt-BR/content/actions/learn-github-actions/contexts.md b/translations/pt-BR/content/actions/learn-github-actions/contexts.md index 88c17692f1..6fd4f39039 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -221,7 +221,7 @@ The following table indicates where each context and special function can be use | Path | Context | Special functions | | ---- | ------- | ----------------- | -| concurrency | github | | +| concurrency | github, inputs | | | env | github, secrets, inputs | | | jobs.<job_id>.concurrency | github, needs, strategy, matrix, inputs | | | jobs.<job_id>.container | github, needs, strategy, matrix, inputs | | diff --git a/translations/pt-BR/content/actions/learn-github-actions/index.md b/translations/pt-BR/content/actions/learn-github-actions/index.md index f69e68338e..e45322bcff 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/index.md +++ b/translations/pt-BR/content/actions/learn-github-actions/index.md @@ -11,7 +11,7 @@ redirect_from: - /actions/getting-started-with-github-actions/overview - /actions/getting-started-with-github-actions/getting-started-with-github-actions - /actions/configuring-and-managing-workflows/configuring-a-workflow - - /articles/creating-a-workflow-with-github-actions/ + - /articles/creating-a-workflow-with-github-actions - /articles/configuring-a-workflow - /github/automating-your-workflow-with-github-actions/configuring-a-workflow - /actions/automating-your-workflow-with-github-actions/configuring-a-workflow diff --git a/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md index 02d81d360f..9bf5bb7bdf 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md +++ b/translations/pt-BR/content/actions/learn-github-actions/reusing-workflows.md @@ -18,9 +18,9 @@ topics: ## Overview -Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. +Rather than copying and pasting from one workflow to another, you can make workflows reusable. You and anyone with access to the reusable workflow can then call the reusable workflow from another workflow. -Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. +Reusing workflows avoids duplication. This makes workflows easier to maintain and allows you to create new workflows more quickly by building on the work of others, just as you do with actions. Workflow reuse also promotes best practice by helping you to use workflows that are well designed, have already been tested, and have been proved to be effective. Your organization can build up a library of reusable workflows that can be centrally maintained. The diagram below shows three build jobs on the left of the diagram. After each of these jobs completes successfully a dependent job called "Deploy" runs. This job calls a reusable workflow that contains three jobs: "Staging", "Review", and "Production." The "Production" deployment job only runs after the "Staging" job has completed successfully. Using a reusable workflow to run deployment jobs allows you to run those jobs for each build without duplicating code in workflows. @@ -67,7 +67,6 @@ Called workflows can access self-hosted runners from caller's context. This mean * Reusable workflows can't call other reusable workflows. * Reusable workflows stored within a private repository can only be used by workflows within the same repository. * Any environment variables set in an `env` context defined at the workflow level in the caller workflow are not propagated to the called workflow. For more information about the `env` context, see "[Context and expression syntax for GitHub Actions](/actions/reference/context-and-expression-syntax-for-github-actions#env-context)." -* You can't set the concurrency of a called workflow from the caller workflow. For more information about `jobs..concurrency`, see "[Workflow syntax for GitHub Actions](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idconcurrency)." * The `strategy` property is not supported in any job that calls a reusable workflow. ## Creating a reusable workflow @@ -77,13 +76,13 @@ Reusable workflows are YAML-formatted files, very similar to any other workflow For a workflow to be reusable, the values for `on` must include `workflow_call`: ```yaml -on: +on: workflow_call: ``` ### Using inputs and secrets in a reusable workflow -You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow. +You can define inputs and secrets, which can be passed from the caller workflow and then used within the called workflow. There are three stages to using an input or a secret in a reusable workflow. 1. In the reusable workflow, use the `inputs` and `secrets` keywords to define inputs or secrets that will be passed from a caller workflow. {% raw %} @@ -112,10 +111,10 @@ You can define inputs and secrets, which can be passed from the caller workflow - uses: ./.github/actions/my-action@v1 with: username: ${{ inputs.username }} - token: ${{ secrets.envPAT }} + token: ${{ secrets.envPAT }} ``` {% endraw %} - In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job. + In the example above, `envPAT` is an environment secret that's been added to the `production` environment. This environment is therefore referenced within the job. {% note %} @@ -153,7 +152,7 @@ jobs: - uses: ./.github/actions/my-action@v1 with: username: ${{ inputs.username }} - token: ${{ secrets.token }} + token: ${{ secrets.token }} ``` {% endraw %} @@ -163,7 +162,7 @@ You call a reusable workflow by using the `uses` keyword. Unlike when you are us [`jobs..uses`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_iduses) -You reference reusable workflow files using the syntax: +You reference reusable workflow files using the syntax: `{owner}/{repo}/{path}/{filename}@{ref}` @@ -191,7 +190,7 @@ When you call a reusable workflow, you can only use the following keywords in th {% note %} - **Note:** + **Note:** * If `jobs..permissions` is not specified in the calling job, the called workflow will have the default permissions for the `GITHUB_TOKEN`. For more information, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)." * The `GITHUB_TOKEN` permissions passed from the caller workflow can be only downgraded (not elevated) by the called workflow. @@ -226,7 +225,7 @@ jobs: ## Using outputs from a reusable workflow -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. +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. 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`. @@ -243,12 +242,12 @@ on: value: ${{ jobs.example_job.outputs.output1 }} secondword: description: "The second output string" - value: ${{ jobs.example_job.outputs.output2 }} - + value: ${{ jobs.example_job.outputs.output2 }} + jobs: example_job: name: Generate output - runs-on: ubuntu-latest + runs-on: ubuntu-latest # Map the job outputs to step outputs outputs: output1: ${{ steps.step1.outputs.firstword }} diff --git a/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md b/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md index 8bdb52e763..f7685fa3f0 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md +++ b/translations/pt-BR/content/actions/learn-github-actions/using-workflow-templates.md @@ -25,9 +25,9 @@ topics: ## About workflow templates -{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests. +{% data variables.product.product_name %} offers workflow templates for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a template file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant workflow templates.{% endif %} -You can also create your own workflow templates to share with your organization. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." +You can also create your own workflow templates to share with your organization. These templates will appear alongside the {% data variables.product.product_name %} workflow templates. For more information, see "[Creating workflow templates](/actions/learn-github-actions/creating-workflow-templates)." ## Using workflow templates @@ -36,8 +36,8 @@ Anyone with write permission to a repository can set up {% data variables.produc {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} 1. If you already have a workflow in your repository, click **New workflow**. -1. Find the template that you want to use, then click **Set up this workflow**. -1. If the workflow template contains comments detailing additional setup steps, follow these steps. +1. Find the template that you want to use, then click **Set up this workflow**.{% if actions-starter-template-ui %} To help you find the template that you want, you can search for keywords or filter by category.{% endif %} +1. If the workflow template contains comments detailing additional setup steps, follow these steps. Many of the templates have corresponding guides. For more information, see [the {% data variables.product.prodname_actions %} guides](/actions/guides)." 1. Some workflow templates use secrets. For example, {% raw %}`${{ secrets.npm_token }}`{% endraw %}. If the workflow template uses a secret, store the value described in the secret name as a secret in your repository. For more information, see "[Encrypted secrets](/actions/reference/encrypted-secrets)." 1. Optionally, make additional changes. For example, you might want to change the value of `on` to change when the workflow runs. 1. Click **Start commit**. diff --git a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md index b4dbec7116..54a6cff1d2 100644 --- a/translations/pt-BR/content/actions/migrating-to-github-actions/index.md +++ b/translations/pt-BR/content/actions/migrating-to-github-actions/index.md @@ -9,7 +9,7 @@ versions: ghec: '*' redirect_from: - /actions/migrating-to-github-actions - - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax/ + - /articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax children: - /migrating-from-azure-pipelines-to-github-actions - /migrating-from-circleci-to-github-actions diff --git a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md index 33cd83f62b..e3c6192362 100644 --- a/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ b/translations/pt-BR/content/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md @@ -71,6 +71,15 @@ These attributes are available. You can change the attribute names in the [manag | `public_keys` | Optional | The public SSH keys for the user. More than one can be specified. | | `gpg_keys` | Optional | The GPG keys for the user. More than one can be specified. | +To specify more than one value for an attribute, use multiple `` elements. + +``` + + ssh-rsa LONG KEY + ssh-rsa LONG KEY 2 + +``` + ## Configuring SAML settings {% data reusables.enterprise_site_admin_settings.access-settings %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md index b720b6c9a0..35573b2ad4 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md @@ -31,6 +31,8 @@ Because client connections to {% data variables.product.prodname_ghe_server %} c {% data reusables.enterprise_clustering.proxy_xff_firewall_warning %} +{% data reusables.enterprise_installation.terminating-tls %} + ### Enabling PROXY protocol support on {% data variables.product.product_location %} We strongly recommend enabling PROXY protocol support for both your appliance 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). @@ -50,8 +52,6 @@ We strongly recommend enabling PROXY protocol support for both your appliance an {% data reusables.enterprise_clustering.x-forwarded-for %} -{% data reusables.enterprise_installation.terminating-tls %} - {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.privacy %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md index 36e474e3e2..9cb3ba1b65 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md +++ b/translations/pt-BR/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md @@ -56,8 +56,8 @@ If you need to get information on the users, organizations, and repositories in Specifically, you can download CSV reports that list - all users -- all users who have been active within the last month -- all users who have been inactive for one month or more +- all active users +- all [dormant users](/admin/user-management/managing-dormant-users) - all users who have been suspended - all organizations - all repositories diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md index ac01707283..19a5c2f5bb 100644 --- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md @@ -10,7 +10,6 @@ redirect_from: - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud -permissions: 'Enterprise owners who are also owners of a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable {% data variables.product.prodname_github_connect %}.' versions: ghes: '*' ghae: '*' @@ -60,6 +59,12 @@ Enabling {% data variables.product.prodname_github_connect %} will not allow {% For more information about managing enterprise accounts using the GraphQL API, see "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)." ## Enabling {% data variables.product.prodname_github_connect %} +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.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is not owned by an enterprise account, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the organization. + +If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_dotcom_the_website %} that is owned by an enterprise account or to an enterprise account itself, you must enable {% data variables.product.prodname_github_connect %} with a personal account on {% data variables.product.prodname_dotcom_the_website %} that is an owner of the enterprise account. + {% ifversion ghes %} 1. Sign in to {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} @@ -73,7 +78,9 @@ For more information about managing enterprise accounts using the GraphQL API, s 1. Next to the enterprise account or organization you'd like to connect, click **Connect**. ![Connect button next to an enterprise account or business](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png) -## Disconnecting a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account from your enterprise account +## Disabling {% data variables.product.prodname_github_connect %} + +Enterprise owners can disable {% data variables.product.prodname_github_connect %}. When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.product.product_location %} are deleted. diff --git a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md index cc41266506..27ad1a6dcc 100644 --- a/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md +++ b/translations/pt-BR/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account.md @@ -37,6 +37,8 @@ For more information about these features, see "[About the dependency graph](/gi You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. You can also choose to manually sync vulnerability data at any time. No code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. +Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %} + ### About generation of {% data variables.product.prodname_dependabot_alerts %} If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}. diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md index e7288474e9..203f3fa1fb 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md @@ -1,7 +1,7 @@ --- -title: Fazer backup e restaurar o GitHub Enterprise Server com o GitHub Actions habilitado -shortTitle: Backup e restauração -intro: 'Os dados de {% data variables.product.prodname_actions %} no seu provedor de armazenamento externo não estão incluídos em backups regulares de {% data variables.product.prodname_ghe_server %} e precisam ser salvos separadamente.' +title: Backing up and restoring GitHub Enterprise Server with GitHub Actions enabled +shortTitle: Backing up and restoring +intro: '{% data variables.product.prodname_actions %} data on your external storage provider is not included in regular {% data variables.product.prodname_ghe_server %} backups, and must be backed up separately.' versions: ghes: '*' type: how_to @@ -13,18 +13,43 @@ topics: redirect_from: - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled --- - {% data reusables.actions.enterprise-storage-ha-backups %} -Se você usar {% data variables.product.prodname_enterprise_backup_utilities %} para fazer backup de {% data variables.product.product_location %}, é importante observar que os dados de {% data variables.product.prodname_actions %} armazenados no seu provedor de armazenamento externo não serão incluídos no backup. +If you use {% data variables.product.prodname_enterprise_backup_utilities %} to back up {% data variables.product.product_location %}, it's important to note that {% data variables.product.prodname_actions %} data stored on your external storage provider is not included in the backup. -Esta é uma visão geral das etapas necessárias para restaurar {% data variables.product.product_location %} com {% data variables.product.prodname_actions %} para um novo dispositivo: +This is an overview of the steps required to restore {% data variables.product.product_location %} with {% data variables.product.prodname_actions %} to a new appliance: -1. Confirme se o dispositivo original está off-line. -1. Defina manualmente as configurações de rede no dispositivo de {% data variables.product.prodname_ghe_server %}. As configurações de rede são excluídas do instantâneo de backup e não são substituídas por `ghe-restore`. -1. Configurar o dispositivo de substituição para usar a mesma configuração de armazenamento externo de {% data variables.product.prodname_actions %} do dispositivo original. -1. Habilite {% data variables.product.prodname_actions %} no dispositivo de substituição. Isto conectará o dispositivo de substituição ao mesmo armazenamento externo para {% data variables.product.prodname_actions %}. -1. Depois que {% data variables.product.prodname_actions %} estiver configurado com o provedor de armazenamento externo, use o comando `ghe-restore` para restaurar o restante dos dados do backup. Para obter mais informações, consulte "[Restaurar um backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)". -1. Registre novamente seus executores auto-hospedados no dispositivo de substituição. Para obter mais informações, consulte [Adicionar executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners). +1. Confirm that the original appliance is offline. +1. Manually configure network settings on the replacement {% data variables.product.prodname_ghe_server %} appliance. Network settings are excluded from the backup snapshot, and are not overwritten by `ghe-restore`. +1. To configure the replacement appliance to use the same {% data variables.product.prodname_actions %} external storage configuration as the original appliance, from the new appliance, set the required parameters with `ghe-config` command. + + - Azure Blob Storage + ```shell + ghe-config secrets.actions.storage.blob-provider "azure" + ghe-config secrets.actions.storage.azure.connection-string "_Connection_String_" + ``` + - Amazon S3 + ```shell + ghe-config secrets.actions.storage.blob-provider "s3" + ghe-config secrets.actions.storage.s3.bucket-name "_S3_Bucket_Name" + ghe-config secrets.actions.storage.s3.service-url "_S3_Service_URL_" + ghe-config secrets.actions.storage.s3.access-key-id "_S3_Access_Key_ID_" + ghe-config secrets.actions.storage.s3.access-secret "_S3_Access_Secret_" + ``` + - Optionally, to enable S3 force path style, enter the following command: + ```shell + ghe-config secrets.actions.storage.s3.force-path-style true + ``` + -Para obter mais informações sobre backup e restauração de {% data variables.product.prodname_ghe_server %}, consulte "[Configurar backups no seu dispositivo](/admin/configuration/configuring-backups-on-your-appliance)". +1. Enable {% data variables.product.prodname_actions %} on the replacement appliance. This will connect the replacement appliance to the same external storage for {% data variables.product.prodname_actions %}. + + ```shell + ghe-config app.actions.enabled true + ghe-config-apply + ``` + +1. After {% data variables.product.prodname_actions %} is configured and enabled, use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)." +1. Re-register your self-hosted runners on the replacement appliance. For more information, see [Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners). + +For more information on backing up and restoring {% data variables.product.prodname_ghe_server %}, see "[Configuring backups on your appliance](/admin/configuration/configuring-backups-on-your-appliance)." diff --git a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md index 514b440f73..748685a4e0 100644 --- a/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md +++ b/translations/pt-BR/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-azure.md @@ -62,7 +62,7 @@ Before launching {% data variables.product.product_location %} on Azure, you'll {% data reusables.enterprise_installation.necessary_ports %} -4. Create and attach a new unencrypted data disk to the VM, and configure the size based on your user license count. For more information, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation. +4. Create and attach a new managed data disk to the VM, and configure the size based on your license count. All Azure managed disks created since June 10, 2017 are encrypted at rest by default with Storage Service Encryption (SSE). For more information about the `az vm disk attach` command, see "[az vm disk attach](https://docs.microsoft.com/cli/azure/vm/disk?view=azure-cli-latest#az_vm_disk_attach)" in the Microsoft documentation. Pass in options for the name of your VM (for example, `ghe-acme-corp`), the resource group, the premium storage SKU, the size of the disk (for example, `100`), and a name for the resulting VHD. diff --git a/translations/pt-BR/content/admin/overview/about-github-ae.md b/translations/pt-BR/content/admin/overview/about-github-ae.md index bb598d72da..62d5fcf17b 100644 --- a/translations/pt-BR/content/admin/overview/about-github-ae.md +++ b/translations/pt-BR/content/admin/overview/about-github-ae.md @@ -1,6 +1,6 @@ --- -title: Sobre o GitHub AE -intro: '{% data variables.product.prodname_ghe_managed %} é uma forma de segurança aprimorada e compatível de usar {% data variables.product.prodname_dotcom %} na nuvem.' +title: About GitHub AE +intro: '{% data variables.product.prodname_ghe_managed %} is a security-enhanced and compliant way to use {% data variables.product.prodname_dotcom %} in the cloud.' versions: ghae: '*' type: overview @@ -9,32 +9,33 @@ topics: - Fundamentals --- -## Sobre o {% data variables.product.prodname_ghe_managed %} +## About {% data variables.product.prodname_ghe_managed %} -{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} é totalmente gerenciada, confiável e escalável, o que permite que você acelere a entrega sem sacrificar a gestão de risco. +{% data reusables.github-ae.github-ae-enables-you %} {% data variables.product.prodname_ghe_managed %} is fully managed, reliable, and scalable, allowing you to accelerate delivery without sacrificing risk management. -{% data variables.product.prodname_ghe_managed %} oferece uma plataforma de desenvolvedor da ideia à produção. Você pode aumentar a velocidade do desenvolvimento com as ferramentas que as equipes conhecem e gostam, ao mesmo tempo em que você mantém a conformidade com o setor e com os regulamentos com controles únicos de segurança e acesso, automação de fluxo de trabalho e aplicação da política. +{% data variables.product.prodname_ghe_managed %} offers one developer platform from idea to production. You can increase development velocity with the tools that teams know and love, while you maintain industry and regulatory compliance with unique security and access controls, workflow automation, and policy enforcement. -## Uma nuvem de alta disponibilidade e escala planetária +## A highly available and planet-scale cloud -{% data variables.product.prodname_ghe_managed %} é um serviço totalmente gerenciado, hospedado em uma arquitetura de alta disponibilidade. {% data variables.product.prodname_ghe_managed %} está hospedado globalmente em uma nuvem que pode ser escalada para ser compatível com todo o seu ciclo de vida de desenvolvimento sem limites. {% data variables.product.prodname_dotcom %} gerencia totalmente os backups, failover e recuperação de desastres para que você nunca tenha que se preocupar com o seu serviço ou dados. +{% data variables.product.prodname_ghe_managed %} is a fully managed service, hosted in a high availability architecture. {% data variables.product.prodname_ghe_managed %} is hosted globally in a cloud that can scale to support your full development lifecycle without limits. {% data variables.product.prodname_dotcom %} fully manages backups, failover, and disaster recovery, so you never need to worry about your service or data. -## Residência dos dados +## Data residency -Todos os seus dados são armazenados na região geográfica da sua escolha. Você pode cumprir os padrões de proteção de dados e o RGPD global mantendo todos os seus dados na sua região escolhida. +All of your data is stored within the geographic region of your choosing. You can comply with GDPR and global data protection standards by keeping all of your data within your chosen region. -## Contas isoladas +## Isolated accounts -Todas as contas de desenvolvedor são completamente isoladas em {% data variables.product.prodname_ghe_managed %}. Você pode controlar totalmente as contas por meio do seu provedor de identidade, com o logon único SAML como obrigatório. O SCIM permite que você garanta que os funcionários só têm acesso aos recursos que deveriam, conforme definido no seu sistema central de gestão de identidades. Para obter mais informações, consulte "[Gerenciar identidade e acesso para sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise)". +All developer accounts are fully isolated in {% data variables.product.prodname_ghe_managed %}. You can fully control the accounts through your identity provider, with SAML single sign on as mandatory. SCIM enables you to ensure that employees only have access to the resources they should, as defined in your central identity management system. For more information, see "[Managing identity and access for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise)." -## Acesso restrito às redes +## Restricted network access -Acesso seguro à sua empresa em {% data variables.product.prodname_ghe_managed %} com acesso restrito à rede, para que seus dados possam ser acessados somente de dentro da sua rede. Para obter mais informações, consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)". +Secure access to your enterprise on {% data variables.product.prodname_ghe_managed %} with restricted network access, so that your data can only be accessed from within your network. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise)." -## Ambientes comercial e governamental +## Commercial and government environments -{% data variables.product.prodname_ghe_managed %} está disponível na nuvem do Azure Government, na nuvem de confiança das agências governamentais dos EUA e seus parceiros. {% data variables.product.prodname_ghe_managed %} também está disponível na nuvem comercial. Portanto, você pode escolher o ambiente de hospedagem correto para a sua organização. +{% data variables.product.prodname_ghe_managed %} is available in the Azure Government cloud, the trusted cloud for US government agencies and their partners. {% data variables.product.prodname_ghe_managed %} is also available in the commercial cloud, so you can choose the hosting environment that is right for your organization. -## Leia mais +## Further reading -- "[Recebendo ajuda do suporte de {% data variables.product.company_short %}](/admin/enterprise-support/receiving-help-from-github-support)" +- "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" +- "[Receiving help from {% data variables.product.company_short %} Support](/admin/enterprise-support/receiving-help-from-github-support)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md index 4a20954bbf..1312ef64f1 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies.md @@ -35,8 +35,13 @@ When your code depends on a package that has a security vulnerability, this vuln {% data variables.product.prodname_dependabot %} detects vulnerable dependencies and sends {% data variables.product.prodname_dependabot_alerts %} when: {% ifversion fpt or ghec %} -- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %} +- A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."{% else %} - New advisory data is synchronized to {% data variables.product.product_location %} each hour from {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} + {% note %} + + **Note:** Only advisories that have been reviewed by {% data variables.product.company_short %} will trigger {% data variables.product.prodname_dependabot_alerts %}. + + {% endnote %} - The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on{% ifversion fpt or ghec %}, or when the code of one of the dependencies changes{% endif %}. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)." {% data reusables.repositories.dependency-review %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md index ebee136e51..34a478356c 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -1,7 +1,8 @@ --- -title: Pesquisar vulnerabilidades de segurança no banco de dados de consultoria do GitHub -intro: 'O {% data variables.product.prodname_advisory_database %} permite que você pesquise vulnerabilidades que afetam projetos de código aberto no {% data variables.product.company_short %}.' -shortTitle: Procurar banco de dados consultivo +title: Browsing security vulnerabilities in the GitHub Advisory Database +intro: 'The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects on {% data variables.product.company_short %}.' +shortTitle: Browse Advisory Database +miniTocMaxHeadingLevel: 3 redirect_from: - /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database - /code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database @@ -16,78 +17,103 @@ topics: - Vulnerabilities - CVEs --- - -## Sobre vulnerabilidades de segurança +## About security vulnerabilities {% data reusables.repositories.a-vulnerability-is %} -O {% data variables.product.product_name %} enviará {% data variables.product.prodname_dependabot_alerts %} se detectarmos que qualquer uma das vulnerabilidades do {% data variables.product.prodname_advisory_database %} afetam os pacotes dos quais seu repositório depende. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" +## About the {% data variables.product.prodname_advisory_database %} -## Sobre o {% data variables.product.prodname_advisory_database %} +The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities, grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories. -O {% data variables.product.prodname_advisory_database %} contém uma lista curada de vulnerabilidades de segurança que foram mapeadas para pacotes monitorados pelo gráfico de dependências de {% data variables.product.company_short %}. {% data reusables.repositories.tracks-vulnerabilities %} +{% data reusables.repositories.tracks-vulnerabilities %} -Cada consultoria de segurança contém informações sobre a vulnerabilidade, incluindo descrição, gravidade, pacote afetado. ecossistema de pacote, versões afetadas e versões de patch, impacto e informações opcionais como, por exemplo, referências, soluções alternativas e créditos. Além disso, a consultoria da lista de Bancos de Vulnerabilidade Nacional contêm um link para o registro CVE, onde você pode ler mais detalhes sobre a vulnerabilidade, suas pontuações CVSS e seu nível de gravidade qualitativa. Para obter mais informações, consulte a "[Base de Dados de Vulnerabilidade Nacional](https://nvd.nist.gov/)" do Instituto Nacional de Padrões e Tecnologia. +### About {% data variables.product.company_short %}-reviewed advisories -O nível de gravidade é um dos quatro níveis possíveis definidos no [ Sistema de Pontuação de vulnerabilidade Comum (CVSS), Seção 5](https://www.first.org/cvss/specification-document)". -- Baixo -- Médio/Moderado -- Alto -- Crítico +{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph. -O {% data variables.product.prodname_advisory_database %} usa os níveis de CVSS descritos acima. Se {% data variables.product.company_short %} obtiver um CVE, o {% data variables.product.prodname_advisory_database %} usará a versão 3.1 do CVSS. Se o CVE for importado, o {% data variables.product.prodname_advisory_database %} será compatível com as versões 3.0 e 3.1 do CVSS. +We carefully review each advisory for validity. Each {% data variables.product.company_short %}-reviewed advisory has a full description, and contains both ecosystem and package information. + +If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory affects packages you depend on. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." + +### About unreviewed advisories + +Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed. + +{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion. + +## About security advisories + +Each security advisory contains information about the vulnerability, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology. + +The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)." +- Low +- Medium/Moderate +- High +- Critical + +The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1. {% data reusables.repositories.github-security-lab %} -## Acessar uma consultoria no {% data variables.product.prodname_advisory_database %} +## Accessing an advisory in the {% data variables.product.prodname_advisory_database %} -1. Navegue até https://github.com/advisories. -2. Opcionalmente, para filtrar a lista, use qualquer um dos menus suspensos. ![Filtros do menu suspenso](/assets/images/help/security/advisory-database-dropdown-filters.png) -3. Clique em qualquer consultoria para visualizar as informações. +1. Navigate to https://github.com/advisories. +2. Optionally, to filter the list, use any of the drop-down menus. + ![Dropdown filters](/assets/images/help/security/advisory-database-dropdown-filters.png) + {% tip %} + + **Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately. + + {% endtip %} +3. Click on any advisory to view details. {% note %} -O banco de dados também pode ser acessado usando a API do GraphQL. Para obter mais informações, consulte "[ evento de webhook `security_advisory`](/webhooks/event-payloads/#security_advisory)." +The database is also accessible using the GraphQL API. For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)." {% endnote %} -## Pesquisar em {% data variables.product.prodname_advisory_database %} +## Searching the {% data variables.product.prodname_advisory_database %} -Você pode procurar no banco de dados e usar qualificadores para limitar sua busca. Por exemplo, você pode procurar consultorias criadas em uma determinada data, em um ecossistema específico ou em uma biblioteca em particular. +You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -| Qualifier | Exemplo | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `GHSA-ID` | [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) mostrará a consultoria com o ID de {% data variables.product.prodname_advisory_database %}. | -| `CVE-ID` | [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) mostrará a consultoria com este ID de CVE. | -| `ecosystem:ECOSYSTEM` | [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) mostrará apenas as consultorias que afetam os pacotes NPM. | -| `severity:LEVEL` | [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) mostrará apenas as consultorias com um alto nível de gravidade. | -| `affects:LIBRARY` | [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) mostrará apenas as consultorias que afetam a biblioteca de lodash. | -| `cwe:ID` | [**cwe:352**](https://github.com/advisories?query=cwe%3A352) mostrará apenas as consultorias com este número de CWE. | -| `credit:USERNAME` | [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) mostrará apenas as consultorias creditadas na conta de usuário "octocat". | -| `sort:created-asc` | [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) classificará os resultados, mostrando as consultorias mais antigas primeiro. | -| `sort:created-desc` | [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) classificará os resultados mostrando as consultorias mais novas primeiro. | -| `sort:updated-asc` | [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) classificará os resultados, mostrando os menos atualizados primeiro. | -| `sort:updated-desc` | [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) classificará os resultados, mostrando os mais atualizados primeiro. | -| `is:withdrawn` | [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) mostrará apenas as consultorias que foram retiradas. | -| `created:YYYY-MM-DD` | [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) mostrará apenas as consultorias criadas nessa data. | -| `updated:YYYY-MM-DD` | [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) mostrará somente as consultorias atualizadas nesta data. | +| Qualifier | Example | +| ------------- | ------------- | +| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories. | +| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. | +| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | +| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | +| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | +| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | +| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | +| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | +| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | +| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | +| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | +| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | +| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | +| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | +| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | +| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. | -## Visualizar seus repositórios vulneráveis +## Viewing your vulnerable repositories -Para qualquer vulnerabilidade em {% data variables.product.prodname_advisory_database %}, você pode ver qual dos seus repositórios tem um alerta {% data variables.product.prodname_dependabot %} para essa vulnerabilidade. Para ver um repositório vulnerável, você deve ter acesso a {% data variables.product.prodname_dependabot_alerts %} para esse repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)" +For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)." -1. Navegue até https://github.com/advisories. -2. Clique em uma consultoria. -3. Na parte superior da página da consultoria, clique em **Alertas do dependabot**. ![Alertas do Dependabot](/assets/images/help/security/advisory-database-dependabot-alerts.png) -4. Opcionalmente, para filtrar a lista, use a barra de pesquisa ou os menus suspensos. O menu suspenso "Organização" permite filtrar {% data variables.product.prodname_dependabot_alerts %} por proprietário (organização ou usuário). ![Barra de pesquisa e menus suspensos para filtrar alertas](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) -5. Para mais detalhes sobre a vulnerabilidade e para aconselhamento sobre como corrigir o repositório vulnerável clique no nome do repositório. +1. Navigate to https://github.com/advisories. +2. Click an advisory. +3. At the top of the advisory page, click **Dependabot alerts**. + ![Dependabot alerts](/assets/images/help/security/advisory-database-dependabot-alerts.png) +4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user). + ![Search bar and drop-down menus to filter alerts](/assets/images/help/security/advisory-database-dependabot-alerts-filters.png) +5. For more details about the vulnerability, and for advice on how to fix the vulnerable repository, click the repository name. -## Leia mais +## Further reading -- [Definição de "vulnerabilidade"](https://cve.mitre.org/about/terminology.html#vulnerability) da MITRE +- MITRE's [definition of "vulnerability"](https://cve.mitre.org/about/terminology.html#vulnerability) diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md index 9d6ac99ff3..a92278ed72 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -2,7 +2,7 @@ title: About wikis intro: 'You can host documentation for your repository in a wiki, so that others can use and contribute to your project.' redirect_from: - - /articles/about-github-wikis/ + - /articles/about-github-wikis - /articles/about-wikis - /github/building-a-strong-community/about-wikis product: '{% data reusables.gated-features.wikis %}' diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md index 3ef6497488..9051feb405 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages.md @@ -1,11 +1,11 @@ --- -title: Adicionar ou editar páginas wiki -intro: 'Você pode adicionar e editar páginas wiki diretamente no {% data variables.product.product_name %} ou localmente usando a linha de comando.' +title: Adding or editing wiki pages +intro: 'You can add and edit wiki pages directly on {% data variables.product.product_name %} or locally using the command line.' redirect_from: - - /articles/adding-wiki-pages-via-the-online-interface/ - - /articles/editing-wiki-pages-via-the-online-interface/ - - /articles/adding-and-editing-wik-pages-locally/ - - /articles/adding-and-editing-wiki-pages-locally/ + - /articles/adding-wiki-pages-via-the-online-interface + - /articles/editing-wiki-pages-via-the-online-interface + - /articles/adding-and-editing-wik-pages-locally + - /articles/adding-and-editing-wiki-pages-locally - /articles/adding-or-editing-wiki-pages - /github/building-a-strong-community/adding-or-editing-wiki-pages product: '{% data reusables.gated-features.wikis %}' @@ -16,47 +16,55 @@ versions: ghec: '*' topics: - Community -shortTitle: Gerenciar páginas wiki +shortTitle: Manage wiki pages --- -## Adicionar páginas wiki +## Adding wiki pages {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %} -3. No canto superior direito da página, clique em **New Page** (Nova página). ![Botão Wiki new page (Nova página wiki)](/assets/images/help/wiki/wiki_new_page_button.png) -4. Se preferir escrever em um formato diferente do markdown, use o menu suspenso Edite mode (Editar modo) e clique em outro formato. ![Seleção de markup do wiki](/assets/images/help/wiki/wiki_dropdown_markup.gif) -5. Use o editor de texto para adicionar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki_wysiwyg.png) -6. Digite uma mensagem do commit descrevendo o novo arquivo que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png) -7. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página). +3. In the upper-right corner of the page, click **New Page**. + ![Wiki new page button](/assets/images/help/wiki/wiki_new_page_button.png) +4. Optionally, to write in a format other than Markdown, use the Edit mode drop-down menu, and click a different format. + ![Wiki markup selection](/assets/images/help/wiki/wiki_dropdown_markup.gif) +5. Use the text editor to add your page's content. + ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) +6. Type a commit message describing the new file you’re adding. + ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png) +7. To commit your changes to the wiki, click **Save Page**. -## Editar páginas wiki +## Editing wiki pages {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %} -4. Usando a barra lateral do wiki, navegue até a página que deseja alterar. No canto superior direito da página, clique em **Edit** (Editar). ![Botão Wiki edit page (Editar página wiki)](/assets/images/help/wiki/wiki_edit_page_button.png) -5. Use o editor de texto para editar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki_wysiwyg.png) -6. Digite uma mensagem do commit descrevendo as alterações. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png) -7. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página). +4. Using the wiki sidebar, navigate to the page you want to change. In the upper-right corner of the page, click **Edit**. + ![Wiki edit page button](/assets/images/help/wiki/wiki_edit_page_button.png) +5. Use the text editor edit the page's content. + ![Wiki WYSIWYG](/assets/images/help/wiki/wiki_wysiwyg.png) +6. Type a commit message describing your changes. + ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png) +7. To commit your changes to the wiki, click **Save Page**. -## Adicionar ou editar páginas wiki localmente +## Adding or editing wiki pages locally -Os wikis fazem parte dos repositórios Git, de modo que é possível fazer alterações localmente e fazer push delas no seu repositório usando o fluxo de trabalho Git. +Wikis are part of Git repositories, so you can make changes locally and push them to your repository using a Git workflow. -### Clonar wikis para seu computador +### Cloning wikis to your computer -Cada wiki fornece uma maneira fácil de clonar o respectivo conteúdo para seu computador. Você pode clonar o repositório no seu computador com a URL fornecida: +Every wiki provides an easy way to clone its contents down to your computer. +You can clone the repository to your computer with the provided URL: ```shell $ git clone https://github.com/YOUR_USERNAME/YOUR_REPOSITORY.wiki.git -# Clona o wiki localmente +# Clones the wiki locally ``` -Depois de clonar o wiki, é possível adicionar novos arquivos, editar os existentes e fazer commit das alterações. Você e seus colaboradores podem criar branches ao trabalhar em wikis, mas somente as alterações enviadas por push ao branch-padrão serão ativadas e disponibilizadas para os seus leitores. +Once you have cloned the wiki, you can add new files, edit existing ones, and commit your changes. You and your collaborators can create branches when working on wikis, but only changes pushed to the default branch will be made live and available to your readers. -## Sobre nomes de arquivo de wiki +## About wiki filenames -O nome de arquivo determina o título da sua página wiki e a extensão do arquivo determina como o conteúdo do wiki será renderizado. +The filename determines the title of your wiki page, and the file extension determines how your wiki content is rendered. -Os wikis usam [nossa biblioteca de markup de código aberto](https://github.com/github/markup) para converter o markup e determinam qual conversor usar pela extensão de um arquivo. Por exemplo, se o nome de um arquivo for *foo.md* ou *foo.markdown*, o wiki usará o conversor Markdown, enquanto em um arquivo chamado *foo.textile*, ele usará o conversor Textile. +Wikis use [our open-source Markup library](https://github.com/github/markup) to convert the markup, and it determines which converter to use by a file's extension. For example, if you name a file *foo.md* or *foo.markdown*, wiki will use the Markdown converter, while a file named *foo.textile* will use the Textile converter. -Não use os seguintes caracteres nos títulos da sua página wiki: `\ / : * ? " < > |`. Os usuários em determinados sistemas operacionais não poderão trabalhar com nomes de arquivo contendo esses caracteres. Certifique-se de escrever seu conteúdo usando uma linguagem markup que corresponda à extensão, ou o conteúdo não será renderizado adequadamente. +Don't use the following characters in your wiki page's titles: `\ / : * ? " < > |`. Users on certain operating systems won't be able to work with filenames containing these characters. Be sure to write your content using a markup language that matches the extension, or your content won't render properly. diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md index 45d7d90a3d..06192a9266 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/creating-a-footer-or-sidebar-for-your-wiki.md @@ -1,9 +1,9 @@ --- -title: Criar rodapé ou barra lateral no wiki -intro: Você pode adicionar uma barra lateral ou um footer personalizado para seu wiki a fim de fornecer aos leitores informações mais contextuais. +title: Creating a footer or sidebar for your wiki +intro: You can add a custom sidebar or footer to your wiki to provide readers with more contextual information. redirect_from: - - /articles/creating-a-footer/ - - /articles/creating-a-sidebar/ + - /articles/creating-a-footer + - /articles/creating-a-sidebar - /articles/creating-a-footer-or-sidebar-for-your-wiki - /github/building-a-strong-community/creating-a-footer-or-sidebar-for-your-wiki product: '{% data reusables.gated-features.wikis %}' @@ -14,27 +14,33 @@ versions: ghec: '*' topics: - Community -shortTitle: Criar rodapé ou barra lateral +shortTitle: Create footer or sidebar --- -## Criar um footer +## Creating a footer {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %} -3. Na parte inferior da página, clique em **Add a custom footer** (Adicionar um footer personalizado). ![Seção wiki e footer](/assets/images/help/wiki/wiki_add_footer.png) -4. Use o editor de texto para digitar o conteúdo que deseja ter no footer. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki-footer.png) -5. Insira uma mensagem do commit descrevendo o footer que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png) -6. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página). +3. At the bottom of the page, click **Add a custom footer**. + ![Wiki add footer section](/assets/images/help/wiki/wiki_add_footer.png) +4. Use the text editor to type the content you want your footer to have. + ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-footer.png) +5. Enter a commit message describing the footer you’re adding. + ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png) +6. To commit your changes to the wiki, click **Save Page**. -## Criar uma barra lateral +## Creating a sidebar {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %} -3. Clique em **Add a custom sidebar** (Adicionar uma barra lateral personalizada). ![Seção de adição da barra lateral do wiki](/assets/images/help/wiki/wiki_add_sidebar.png) -4. Use o editor de texto para adicionar o conteúdo da página. ![WYSIWYG do wiki](/assets/images/help/wiki/wiki-sidebar.png) -5. Insira uma mensagem do commit descrevendo a barra lateral que você está adicionando. ![Mensagem do commit do wiki](/assets/images/help/wiki/wiki_commit_message.png) -6. Para fazer commit das alterações no wiki, clique em **Save Page** (Salvar página). +3. Click **Add a custom sidebar**. + ![Wiki add sidebar section](/assets/images/help/wiki/wiki_add_sidebar.png) +4. Use the text editor to add your page's content. + ![Wiki WYSIWYG](/assets/images/help/wiki/wiki-sidebar.png) +5. Enter a commit message describing the sidebar you’re adding. + ![Wiki commit message](/assets/images/help/wiki/wiki_commit_message.png) +6. To commit your changes to the wiki, click **Save Page**. -## Criar um footer ou uma barra lateral localmente +## Creating a footer or sidebar locally -Se você criar um arquivo chamado `_Footer.` ou `_Sidebar.`, nós os usaremos para preencher o footer e a barra lateral do wiki, respectivamente. Assim como qualquer outra página do wiki, a extensão que você escolhe para esses arquivos determina como nós os renderizaremos. +If you create a file named `_Footer.` or `_Sidebar.`, we'll use them to populate the footer and sidebar of your wiki, respectively. Like every other wiki page, the extension you choose for these files determines how we render them. diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index b11cff14bc..c132ba8340 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -1,14 +1,14 @@ --- -title: Editar conteúdo de wiki -intro: Você pode adicionar imagens e links no conteúdo do seu wiki e usar alguns formatos do MediaWiki compatíveis. +title: Editing wiki content +intro: 'You can add images and links to content in your wiki, and use some supported MediaWiki formats.' redirect_from: - - /articles/adding-links-to-wikis/ - - /articles/how-do-i-add-links-to-my-wiki/ - - /articles/how-do-i-add-or-upload-images-to-the-wiki/ - - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki/ - - /articles/how-do-i-add-images-to-my-wiki/ - - /articles/adding-images-to-wikis/ - - /articles/supported-mediawiki-formats/ + - /articles/adding-links-to-wikis + - /articles/how-do-i-add-links-to-my-wiki + - /articles/how-do-i-add-or-upload-images-to-the-wiki + - /articles/needs-writing-review-how-do-i-add-or-upload-images-to-the-wiki + - /articles/how-do-i-add-images-to-my-wiki + - /articles/adding-images-to-wikis + - /articles/supported-mediawiki-formats - /articles/editing-wiki-content - /github/building-a-strong-community/editing-wiki-content product: '{% data reusables.gated-features.wikis %}' @@ -21,39 +21,40 @@ topics: - Community --- -## Adicionar links +## Adding links -Você pode criar links em wikis usando markup padrão compatível para sua página ou usando sintaxe do MediaWiki. Por exemplo: +You can create links in wikis using the standard markup supported by your page, or using MediaWiki syntax. For example: -- Em páginas renderizadas com Markdown, a sintaxe do link é `[Link Text](full-URL-of-wiki-page)`. -- Com a sintaxe do MediaWiki, a sintaxe do link é `[[Link Text|nameofwikipage]]`. +- If your pages are rendered with Markdown, the link syntax is `[Link Text](full-URL-of-wiki-page)`. +- With MediaWiki syntax, the link syntax is `[[Link Text|nameofwikipage]]`. -## Adicionar imagens +## Adding images -Os wikis podem exibir imagens em PNG, JPEG e GIF. +Wikis can display PNG, JPEG, and GIF images. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-wiki %} -3. Usando a barra lateral de wikis, navegue até a página que deseja alterar e clique em **Edit** (Editar). -4. Na barra de ferramentas de wikis, clique em **Image** (Imagem). ![Imagem do botão Wiki Add (Adição de wiki)](/assets/images/help/wiki/wiki_add_image.png) -5. Na caixa de diálogo "Insert Image" (Inserir imagem), digite a URL da imagem e o texto alt (que é usado por mecanismos de pesquisa e leitores de tela). -6. Clique em **OK**. +3. Using the wiki sidebar, navigate to the page you want to change, and then click **Edit**. +4. On the wiki toolbar, click **Image**. + ![Wiki Add image button](/assets/images/help/wiki/wiki_add_image.png) +5. In the "Insert Image" dialog box, type the image URL and the alt text (which is used by search engines and screen readers). +6. Click **OK**. -### Vincular a imagens em um repositório +### Linking to images in a repository -Para vincular a uma imagem em um repositório no {% data variables.product.product_name %}, copie a URL no navegador e use-a como caminho para a imagem. Por exemplo, a incorporação de uma imagem no wiki usando Markdown pode ter esta aparência: +You can link to an image in a repository on {% data variables.product.product_name %} by copying the URL in your browser and using that as the path to the image. For example, embedding an image in your wiki using Markdown might look like this: [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] -## Formatos do MediaWiki compatíveis +## Supported MediaWiki formats -Seja qual for a linguagem de marcação em que sua página wiki foi escrita, sempre haverá uma sintaxe do MediaWiki disponível para você. -- Links ([exceto Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)) -- Regras horizontais via `---` -- Entidades de símbolo abreviadas (como `δ` ou `€`) +No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you. +- Links ([except Asciidoc](https://github.com/gollum/gollum/commit/d1cf698b456cd6a35a54c6a8e7b41d3068acec3b)) +- Horizontal rules via `---` +- Shorthand symbol entities (such as `δ` or `€`) -Por motivos de segurança e desempenho, algumas sintaxes não são compatíveis. -- [Transclusão](https://www.mediawiki.org/wiki/Transclusion) -- Listas de definições -- Indentação -- Índice +For security and performance reasons, some syntaxes are unsupported. +- [Transclusion](https://www.mediawiki.org/wiki/Transclusion) +- Definition lists +- Indentation +- Table of contents diff --git a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md index e9845e4ebc..fbec09d8fc 100644 --- a/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md +++ b/translations/pt-BR/content/communities/documenting-your-project-with-wikis/index.md @@ -1,10 +1,10 @@ --- -title: Documentar seu projeto com wikis -shortTitle: Usando wikis -intro: Você pode usar um wiki para compartilhar informações longas e detalhadas sobre seu projeto. +title: Documenting your project with wikis +shortTitle: Using wikis +intro: 'You can use a wiki to share detailed, long-form information about your project.' redirect_from: - - /categories/49/articles/ - - /categories/wiki/ + - /categories/49/articles + - /categories/wiki - /articles/documenting-your-project-with-wikis - /github/building-a-strong-community/documenting-your-project-with-wikis product: '{% data reusables.gated-features.wikis %}' diff --git a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md index fd429115bd..d2c37ba9c1 100644 --- a/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md +++ b/translations/pt-BR/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md @@ -2,7 +2,7 @@ title: Limiting interactions in your repository intro: You can temporarily enforce a period of limited activity for certain users on a public repository. redirect_from: - - /articles/limiting-interactions-with-your-repository/ + - /articles/limiting-interactions-with-your-repository - /articles/limiting-interactions-in-your-repository - /github/building-a-strong-community/limiting-interactions-in-your-repository versions: diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md index bbd3a34452..e0cecf6b62 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories.md @@ -1,8 +1,8 @@ --- -title: Sobre perfis de comunidade para repositórios públicos -intro: Os mantenedores de repositório podem revisar o respectivo perfil de comunidade do repositório público para saber como podem ajudar a expandir a comunidade e dar suporte aos contribuidores. Os contribuidores podem exibir o perfil de comunidade de um repositório público para verificar se eles desejam contribuir com o projeto. +title: About community profiles for public repositories +intro: Repository maintainers can review their public repository's community profile to learn how they can help grow their community and support contributors. Contributors can view a public repository's community profile to see if they want to contribute to the project. redirect_from: - - /articles/viewing-your-community-profile/ + - /articles/viewing-your-community-profile - /articles/about-community-profiles-for-public-repositories - /github/building-a-strong-community/about-community-profiles-for-public-repositories versions: @@ -10,36 +10,36 @@ versions: ghec: '*' topics: - Community -shortTitle: Perfis da comunidade +shortTitle: Community profiles --- -A checklist do perfil de comunidade verifica se um projeto inclui arquivos recomendados de integridade da comunidade, como README, CODE_OF_CONDUCT, LICENSE ou CONTRIBUTING em um local compatível. Para obter mais informações, consulte "[Acessar perfil de comunidade de um projeto](/articles/accessing-a-project-s-community-profile)". +The community profile checklist checks to see if a project includes recommended community health files, such as README, CODE_OF_CONDUCT, LICENSE, or CONTRIBUTING, in a supported location. For more information, see "[Accessing a project's community profile](/articles/accessing-a-project-s-community-profile)." -## Usar a checklist do perfil de comunidade como um mantenedor de repositório +## Using the community profile checklist as a repository maintainer -Como um mantenedor de repositório, use a checklist do perfil de comunidade para ver se o projeto atende aos padrões recomendados da comunidade de modo a ajudar as pessoas a usar e contribuir com seu projeto. Para obter mais informações, consulte "[Compilar comunidade](https://opensource.guide/building-community/)" nos Guias de código aberto. +As a repository maintainer, use the community profile checklist to see if your project meets the recommended community standards to help people use and contribute to your project. For more information, see "[Building community](https://opensource.guide/building-community/)" in the Open Source Guides. -Se um projeto não tiver um arquivo recomendado, você poderá clicar em **Adicionar** para rascunhar e enviar uma arquivo. +If a project doesn't have a recommended file, you can click **Add** to draft and submit a file. -{% data reusables.repositories.valid-community-issues %}Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)". +{% data reusables.repositories.valid-community-issues %} For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." -![Checklist do perfil de comunidade com padrões recomendados da comunidade para mantenedores](/assets/images/help/repository/add-button-community-profile.png) +![Community profile checklist with recommended community standards for maintainers](/assets/images/help/repository/add-button-community-profile.png) {% data reusables.repositories.security-guidelines %} -## Usar a checklist do perfil de comunidade como integrante ou colaborador da comunidade +## Using the community profile checklist as a community member or collaborator -Como um contribuidor potencial, use a checklist do perfil de comunidade para verificar se um projeto atende aos padrões recomendados da comunidade e decida se deseja contribuir. Para obter mais informações, consulte "[Como contribuir](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" nos Guias de código aberto. +As a potential contributor, use the community profile checklist to see if a project meets the recommended community standards and decide if you'd like to contribute. For more information, see "[How to contribute](https://opensource.guide/how-to-contribute/#anatomy-of-an-open-source-project)" in the Open Source Guides. -Se um projeto não tiver um arquivo recomendado, você poderá clicar em **Propor** para rascunhar e enviar um arquivo ao mantenedor de repositório para aprovação. +If a project doesn't have a recommended file, you can click **Propose** to draft and submit a file to the repository maintainer for approval. -![Checklist do perfil de comunidade com padrões recomendados da comunidade para contribuidores](/assets/images/help/repository/propose-button-community-profile.png) +![Community profile checklist with recommended community standards for contributors](/assets/images/help/repository/propose-button-community-profile.png) -## Leia mais +## Further reading -- "[Adicionar um código de conduta ao seu projeto](/articles/adding-a-code-of-conduct-to-your-project)" -- "[Configurar diretrizes para os contribuidores do repositório](/articles/setting-guidelines-for-repository-contributors)" -- "[Adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)" -- "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)" -- "[Guias de código aberto](https://opensource.guide/)" +- "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project)" +- "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors)" +- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)" +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[Open Source Guides](https://opensource.guide/)" - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md index 0220873896..f732f0c105 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/index.md @@ -1,9 +1,9 @@ --- -title: Configurar projeto para contribuições úteis -shortTitle: Contribuições saudáveis -intro: Os mantenedores de repositório podem definir diretrizes de contribuição para ajudar os colaboradores a fazer contribuições relevantes e úteis a um projeto. +title: Setting up your project for healthy contributions +shortTitle: Healthy contributions +intro: 'Repository maintainers can set contributing guidelines to help collaborators make meaningful, useful contributions to a project.' redirect_from: - - /articles/helping-people-contribute-to-your-project/ + - /articles/helping-people-contribute-to-your-project - /articles/setting-up-your-project-for-healthy-contributions - /github/building-a-strong-community/setting-up-your-project-for-healthy-contributions versions: diff --git a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md index 598c0c38cd..c5bb1df6a6 100644 --- a/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md +++ b/translations/pt-BR/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md @@ -1,68 +1,68 @@ --- -title: Configurar diretrizes para os contribuidores do repositório -intro: Você pode criar diretrizes para informar como as pessoas devem contribuir com o projeto. +title: Setting guidelines for repository contributors +intro: You can create guidelines to communicate how people should contribute to your project. versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' redirect_from: - - /articles/how-do-i-set-up-guidelines-for-contributors/ + - /articles/how-do-i-set-up-guidelines-for-contributors - /articles/setting-guidelines-for-repository-contributors - /github/building-a-strong-community/setting-guidelines-for-repository-contributors topics: - Community -shortTitle: Diretrizes de contribuidor +shortTitle: Contributor guidelines --- +## About contributing guidelines +To help your project contributors do good work, you can add a file with contribution guidelines to your project repository's root, `docs`, or `.github` folder. When someone opens a pull request or creates an issue, they will see a link to that file. The link to the contributing guidelines also appears on your repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute). -## Sobre diretrizes de contribuição -Para ajudar os contribuidores do projeto a fazer um bom trabalho, você pode adicionar um arquivo com diretrizes de contribuição às pastas raiz, `docs` ou `.github` do repositório do projeto. Quando alguém abrir uma pull request ou criar um problema, verá um link para esse arquivo. O link para as diretrizes de contribuição também aparece na página `contribuir` do seu repositório. Para obter um exemplo da página de `contribuir`, consulte [github/docs/contribua](https://github.com/github/docs/contribute). +![contributing-guidelines](/assets/images/help/pull_requests/contributing-guidelines.png) -![diretrizes de contribuição](/assets/images/help/pull_requests/contributing-guidelines.png) +For the repository owner, contribution guidelines are a way to communicate how people should contribute. -Para o proprietário do repositório, as diretrizes de contribuição são uma forma de informar como as pessoas devem contribuir. +For contributors, the guidelines help them verify that they're submitting well-formed pull requests and opening useful issues. -Para contribuidores, as diretrizes ajudam a verificar se eles estão enviando pull requests corretas e abrindo problemas úteis. - -Para proprietários e contribuidores, as diretrizes de contribuição economizam tempo e evitam aborrecimentos causados por pull requests ou problemas incorretos que precisam ser rejeitados e enviados novamente. +For both owners and contributors, contribution guidelines save time and hassle caused by improperly created pull requests or issues that have to be rejected and re-submitted. {% ifversion fpt or ghes or ghec %} -Você pode criar diretrizes de contribuição padrão para sua organização{% ifversion fpt or ghes or ghec %} ou conta de usuário{% endif %}. Para obter mais informações, consulte "[Criando um arquivo padrão de integridade da comunidade](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." +You can create default contribution guidelines for your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %}. For more information, see "[Creating a default community health file](//communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)." {% endif %} {% tip %} -**Dica:** os mantenedores de repositório podem configurar diretrizes específicas para problemas criando um modelo de problema ou pull request para o repositório. Para obter mais informações, consulte "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)". +**Tip:** Repository maintainers can set specific guidelines for issues by creating an issue or pull request template for the repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)." {% endtip %} -## Adicionar um arquivo *CONTRIBUTING* +## Adding a *CONTRIBUTING* file {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. Decida se deseja armazenar as diretrizes de contribuição no diretório root, `docs` ou `.github` do repositório. Em seguida, no campo de nome do arquivo, digite o nome e a extensão do arquivo. Os nomes de arquivos com diretrizes de contribuição não são sensíveis a maiúsculas de minúsculas. Os arquivos são renderizados no formato de texto rich se a extensão do arquivo estiver em um formato compatível. Para obter mais informações, consulte "[Trabalhando com arquivos sem código](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)". ![Nome do novo arquivo](/assets/images/help/repository/new-file-name.png) - - Para tornar as diretrizes de contribuição visíveis no diretório raiz do repositório, digite *CONTRIBUTING*. - - Para tornar as diretrizes de contribuição visíveis no diretório `docs` do repositório, digite *docs/* para criar o diretório e, em seguida, digite *CONTRIBUTING*. - - Se um repositório contiver mais de um arquivo *CONTRIBUTING*, o arquivo mostrado em links será escolhido entre locais na seguinte ordem: diretório do `.github`, em seguida, o diretório raiz do repositório e, finalmente, o diretório de `docs`. -4. Adicione as diretrizes de contribuição ao novo arquivo. Elas podem conter: - - Etapas para criar bons problemas ou pull requests. - - Links para documentações externas, listas de distribuição ou um código de conduta. - - Expectativas de comportamento e da comunidade. +3. Decide whether to store your contributing guidelines in your repository's root, `docs`, or `.github` directory. Then, in the filename field, type the name and extension for the file. Contributing guidelines filenames are not case sensitive. Files are rendered in rich text format if the file extension is in a supported format. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#rendering-differences-in-prose-documents)." + ![New file name](/assets/images/help/repository/new-file-name.png) + - To make your contributing guidelines visible in the repository's root directory, type *CONTRIBUTING*. + - To make your contributing guidelines visible in the repository's `docs` directory, type *docs/* to create the new directory, then *CONTRIBUTING*. + - If a repository contains more than one *CONTRIBUTING* file, then the file shown in links is chosen from locations in the following order: the `.github` directory, then the repository's root directory, and finally the `docs` directory. +4. In the new file, add contribution guidelines. These could include: + - Steps for creating good issues or pull requests. + - Links to external documentation, mailing lists, or a code of conduct. + - Community and behavioral expectations. {% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -## Exemplos de diretrizes de contribuição +## Examples of contribution guidelines -Caso tenha dúvidas, estes são alguns bons exemplos de diretrizes de contribuição: +If you're stumped, here are some good examples of contribution guidelines: -- [Diretrizes de contribuição](https://github.com/atom/atom/blob/master/CONTRIBUTING.md) do editor Atom. -- [Diretrizes de contribuição](https://github.com/rails/rails/blob/master/CONTRIBUTING.md) do Ruby on Rails. -- [Diretrizes de contribuição](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md) do Open Government. +- The Atom editor [contribution guidelines](https://github.com/atom/atom/blob/master/CONTRIBUTING.md). +- The Ruby on Rails [contribution guidelines](https://github.com/rails/rails/blob/master/CONTRIBUTING.md). +- The Open Government [contribution guidelines](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md). -## Leia mais -- Seção "[Iniciar um projeto de código aberto](https://opensource.guide/starting-a-project/)" de Guias de código aberto{% ifversion fpt or ghec %} +## Further reading +- The Open Source Guides' section "[Starting an Open Source Project](https://opensource.guide/starting-a-project/)"{% ifversion fpt or ghec %} - [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}){% endif %}{% ifversion fpt or ghes or ghec %} -- "[Adicionar uma licença a um repositório](/articles/adding-a-license-to-a-repository)"{% endif %} +- "[Adding a license to a repository](/articles/adding-a-license-to-a-repository)"{% endif %} diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md index 99bcf31d27..9974eff8e8 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/index.md @@ -1,10 +1,10 @@ --- -title: Usando modelos para incentivar problemas úteis e receber pull request -shortTitle: Problema & Modelos PR -intro: Os mantenedores de repositório podem adicionar modelos a um repositório para ajudar os contribuidores a criar problemas e pull requests de alta qualidade. +title: Using templates to encourage useful issues and pull requests +shortTitle: Issue & PR templates +intro: Repository maintainers can add templates in a repository to help contributors create high-quality issues and pull requests. redirect_from: - /github/building-a-strong-community/using-issue-and-pull-request-templates - - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository/ + - /articles/using-templates-to-encourage-high-quality-issues-and-pull-requests-in-your-repository - /articles/using-issue-and-pull-request-templates - /github/building-a-strong-community/using-templates-to-encourage-useful-issues-and-pull-requests versions: diff --git a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md index d29c94c910..cbf6716233 100644 --- a/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md +++ b/translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository.md @@ -1,8 +1,8 @@ --- -title: Criar manualmente um modelo único de problema no repositório -intro: 'Ao adicionar um modelo de problema criado manualmente no repositório, os colaboradores de projetos verão automaticamente o conteúdo do modelo no texto do problema.' +title: Manually creating a single issue template for your repository +intro: 'When you add a manually-created issue template to your repository, project contributors will automatically see the template''s contents in the issue body.' redirect_from: - - /articles/creating-an-issue-template-for-your-repository/ + - /articles/creating-an-issue-template-for-your-repository - /articles/manually-creating-a-single-issue-template-for-your-repository - /github/building-a-strong-community/manually-creating-a-single-issue-template-for-your-repository versions: @@ -12,29 +12,29 @@ versions: ghec: '*' topics: - Community -shortTitle: Criar um modelo de problema +shortTitle: Create an issue template --- {% data reusables.repositories.legacy-issue-template-tip %} -Você pode criar um subdiretório *ISSUE_TEMPLATE/* (MODELO_DE_PROBLEMA) em qualquer uma das pastas compatíveis. Assim, é possível incluir vários modelos de problemas e usar o parâmetro de consulta `template` (modelo) para especificar o modelo que irá preencher o texto do problema. Para obter mais informações, consulte "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)". +You can create an *ISSUE_TEMPLATE/* subdirectory in any of the supported folders to contain multiple issue templates, and use the `template` query parameter to specify the template that will fill the issue body. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)." -Você pode adicionar o YAML frontmatter a cada modelo de problema para preencher previamente o título do problema, adicionar rótulos e responsáveis ​​automaticamente e atribuir ao modelo um nome e uma descrição que serão mostrados no seletor de modelos que as pessoas veem ao criar um novo problema em seu repositório . +You can add YAML frontmatter to each issue template to pre-fill the issue title, automatically add labels and assignees, and give the template a name and description that will be shown in the template chooser that people see when creating a new issue in your repository. -Aqui está um exemplo de YAML front matter. +Here is example YAML front matter. ```yaml --- -name: Rastreando problema -about: Use este modelo para rastrear novos recursos. +name: Tracking issue +about: Use this template for tracking new features. title: "[DATE]: [FEATURE NAME]" -labels: rastreando problema, precisa de triagem +labels: tracking issue, needs triage assignees: octocat --- ``` {% note %} -**Nota:** Se um valor da matéria frontal incluir um caractere reservado em YAML como `:`, você deverá colocar todo o valor entre aspas. Por exemplo, `":bug: Bug"` ou `":new: triagem necessária, :bug: bug"`. +**Note:** If a front matter value includes a YAML-reserved character such as `:` , you must put the whole value in quotes. For example, `":bug: Bug"` or `":new: triage needed, :bug: bug"`. {% endnote %} @@ -50,27 +50,31 @@ assignees: octocat {% endif %} -## Adicionar um modelo de problema +## Adding an issue template {% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %} -3. No campo nome do arquivo: - - Para que seu modelo de problema seja visível no diretório raiz do repositório, digite o nome de seu *issue_template* (modelo_de_problema). Por exemplo, `issue_template.md`. ![Novo nome de modelo de problema no diretório raiz](/assets/images/help/repository/issue-template-file-name.png) - - Para que seu modelo de problema seja visível no diretório `docs` do repositório, digite *docs/* seguido pelo nome de seu *issue_template* (modelo_de_problema). Por exemplo, `docs/issue_template.md`. ![Novo modelo de problema no diretório docs](/assets/images/help/repository/issue-template-file-name-docs.png) - - Para armazenar seu arquivo em um diretório oculto, digite *.github/* seguido do nome de seu *issue_template* (modelo_de_problema). Por exemplo, `.github/issue_template.md`. ![Novo modelo de problema no diretório oculto](/assets/images/help/repository/issue-template-hidden-directory.png) - - Para criar vários modelos de problemas e usar o parâmetro de consulta `template` (modelo) para especificar um modelo para preencher o texto do problema, digite *.github/ISSUE_TEMPLATE/* (.github/MODELO_DE_PROBLEMA) e o nome de seu modelo de problema. Por exemplo, `.github/ISSUE_TEMPLATE/issue_template.md`. Também é possível armazenar vários modelos de problemas em um subdiretório `ISSUE_TEMPLATE` (MODELO_DE_PROBLEMA) nos diretórios raiz ou `docs/`. Para obter mais informações, consulte "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)". ![Vários novos modelos de problemas no diretório oculto](/assets/images/help/repository/issue-template-multiple-hidden-directory.png) -4. No texto do novo arquivo, adicione seu modelo de problema. Pode conter: +3. In the file name field: + - To make your issue template visible in the repository's root directory, type the name of your *issue_template*. For example, `issue_template.md`. + ![New issue template name in root directory](/assets/images/help/repository/issue-template-file-name.png) + - To make your issue template visible in the repository's `docs` directory, type *docs/* followed by the name of your *issue_template*. For example, `docs/issue_template.md`, + ![New issue template in docs directory](/assets/images/help/repository/issue-template-file-name-docs.png) + - To store your file in a hidden directory, type *.github/* followed by the name of your *issue_template*. For example, `.github/issue_template.md`. + ![New issue template in hidden directory](/assets/images/help/repository/issue-template-hidden-directory.png) + - To create multiple issue templates and use the `template` query parameter to specify a template to fill the issue body, type *.github/ISSUE_TEMPLATE/*, then the name of your issue template. For example, `.github/ISSUE_TEMPLATE/issue_template.md`. You can also store multiple issue templates in an `ISSUE_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)." + ![New multiple issue template in hidden directory](/assets/images/help/repository/issue-template-multiple-hidden-directory.png) +4. In the body of the new file, add your issue template. This could include: - YAML frontmatter - - Comportamento esperado e comportamento atual - - Etapas para reproduzir o problema - - Especificações como a versão do projeto, sistema operacional ou hardware + - Expected behavior and actual behavior + - Steps to reproduce the problem + - Specifications like the version of the project, operating system, or hardware {% data reusables.files.write_commit_message %} -{% data reusables.files.choose_commit_branch %} Os modelos são disponibilizados para os colaboradores quando sofrem merge no branch padrão do repositório. +{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch. {% data reusables.files.propose_new_file %} -## Leia mais +## Further reading -- "[Sobre modelos de problema e pull request](/articles/about-issue-and-pull-request-templates)" -- "[Configurando modelos de problemas para seu repositório](/articles/configuring-issue-templates-for-your-repository)" -- "[Sobre automação de problemas e pull requests com parâmetros de consulta](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" -- "[Criar um problema](/articles/creating-an-issue)" +- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)" +- "[Configuring issue templates for your repository](/articles/configuring-issue-templates-for-your-repository)" +- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)" +- "[Creating an issue](/articles/creating-an-issue)" diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md index 75409ef3ff..c876fc183c 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/authenticating-with-github-apps.md @@ -2,8 +2,8 @@ title: Authenticating with GitHub Apps intro: '{% data reusables.shortdesc.authenticating_with_github_apps %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps/ - - /apps/building-github-apps/authentication-options-for-github-apps/ + - /apps/building-integrations/setting-up-and-registering-github-apps/about-authentication-options-for-github-apps + - /apps/building-github-apps/authentication-options-for-github-apps - /apps/building-github-apps/authenticating-with-github-apps - /developers/apps/authenticating-with-github-apps versions: diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md index 6324ba0303..93f56c8090 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md @@ -1,9 +1,9 @@ --- -title: Criar um aplicativo GitHub +title: Creating a GitHub App intro: '{% data reusables.shortdesc.creating_github_apps %}' redirect_from: - - /early-access/integrations/creating-an-integration/ - - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps/ + - /early-access/integrations/creating-an-integration + - /apps/building-integrations/setting-up-and-registering-github-apps/registering-github-apps - /apps/building-github-apps/creating-a-github-app - /developers/apps/creating-a-github-app versions: @@ -14,13 +14,12 @@ versions: topics: - GitHub Apps --- - -{% ifversion fpt or ghec %}Para aprender como usar manifestos do aplicativo GitHub que permitem que pessoas criem aplicativos GitHub pré-configurados, consulte "[Criando aplicativos GitHub a partir de um manifesto](/apps/building-github-apps/creating-github-apps-from-a-manifest/).{% endif %} +{% ifversion fpt or ghec %}To learn how to use GitHub App Manifests, which allow people to create preconfigured GitHub Apps, see "[Creating GitHub Apps from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %} {% ifversion fpt or ghec %} {% note %} - **Observação:** {% data reusables.apps.maximum-github-apps-allowed %} + **Note:** {% data reusables.apps.maximum-github-apps-allowed %} {% endnote %} {% endif %} @@ -28,44 +27,57 @@ topics: {% data reusables.apps.settings-step %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -1. Clique em **Novo aplicativo GitHub**. ![Botão para criar um novo aplicativo GitHub](/assets/images/github-apps/github_apps_new.png) -1. Em "Nome do aplicativo GitHub App", digite o nome do seu aplicativo. ![Campo para o nome do seu aplicativo GitHub](/assets/images/github-apps/github_apps_app_name.png) +1. Click **New GitHub App**. +![Button to create a new GitHub App](/assets/images/github-apps/github_apps_new.png) +1. In "GitHub App name", type the name of your app. +![Field for the name of your GitHub App](/assets/images/github-apps/github_apps_app_name.png) - Dê um nome claro e sucinto ao seu aplicativo. Seu aplicativo não pode ter o mesmo nome de uma conta existente no GitHub, a menos que seja o seu próprio nome de usuário ou da sua organização. Uma versão movida do nome do seu aplicativo será exibida na interface do usuário quando sua integração realizar uma ação. + Give your app a clear and succinct name. Your app cannot have the same name as an existing GitHub account, unless it is your own user or organization name. A slugged version of your app's name will be shown in the user interface when your integration takes an action. -1. Opcionalmente, em "Descrição", digite uma descrição do aplicativo que os usuários irão ver. ![Campo para uma descrição do seu aplicativo GitHub](/assets/images/github-apps/github_apps_description.png) -1. Em "URL da página inicial", digite a URL completa do site do seu aplicativo. ![Campo para a URL da página inicial do seu aplicativo GitHub](/assets/images/github-apps/github_apps_homepage_url.png) +1. Optionally, in "Description", type a description of your app that users will see. +![Field for a description of your GitHub App](/assets/images/github-apps/github_apps_description.png) +1. In "Homepage URL", type the full URL to your app's website. +![Field for the homepage URL of your GitHub App](/assets/images/github-apps/github_apps_homepage_url.png) {% ifversion fpt or ghes > 3.0 or ghec %} -1. Em "URL de retorno de chamada", digite a URL completa para redirecionar após um usuário autorizar a instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. +1. In "Callback URL", type the full URL to redirect to after a user authorizes the installation. This URL is used if your app needs to identify and authorize user-to-server requests. - Você pode usar **Adicionar URL de retorno de chamada** para fornecer URLs de retorno de chamadas adicionais até o limite máximo de 10. + You can use **Add callback URL** to provide additional callback URLs, up to a maximum of 10. - ![Botão para 'Adicionar URL de retorno de chamada' e campo para URL de retorno de chamada](/assets/images/github-apps/github_apps_callback_url_multiple.png) + ![Button for 'Add callback URL' and field for callback URL](/assets/images/github-apps/github_apps_callback_url_multiple.png) {% else %} -1. Em "URL de chamada de retorno de autorização do usuário", digite a URL completa para redirecionamento após um usuário autorizar uma instalação. Esta URL é usada se o aplicativo precisar identificar e autorizar solicitações de usuário para servidor. ![Campo para a URL de chamada de retorno de autorização do usuário do seu aplicativo GitHub](/assets/images/github-apps/github_apps_user_authorization.png) +1. In "User authorization callback URL", type the full URL to redirect to after a user authorizes an installation. This URL is used if your app needs to identify and authorize user-to-server requests. +![Field for the user authorization callback URL of your GitHub App](/assets/images/github-apps/github_apps_user_authorization.png) {% endif %} -1. Por padrão, para melhorar a segurança de seus aplicativos, seus aplicativos usarão os tokens de autorização do usuário. Para optar por não usar tokens do usuário expirados, você deverá desmarcar "Expirar tokens de autorização do usuário". Para saber mais sobre como configurar o fluxo de atualização do token e os benefícios de expirar os tokens do usuário, consulte "[Atualizando tokens de acesso do usuário para o servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." ![Opção para expirar os tokens dos usuários durante a configuração dos aplicativos GitHub](/assets/images/github-apps/expire-user-tokens-selection.png) -1. Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você pode selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando uma etapa. Se você selecionar esta opção, a "URL de configuração" irá tornar-se indisponível e os usuários serão redirecionados para a "URL de retorno de chamada de autorização do usuário" após a instalação do aplicativo. Consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)" para obter mais informações. ![Solicitar autorização de usuário durante a instalação](/assets/images/github-apps/github_apps_request_auth_upon_install.png) -1. Se for necessária uma configuração adicional após a instalação, adicione um "Configurar URL" para redirecionar os usuários após a instalação do seu aplicativo. ![Campo para a URL de configuração do seu aplicativo GitHub ](/assets/images/github-apps/github_apps_setup_url.png) +1. By default, to improve your app's security, your app will use expiring user authorization tokens. To opt-out of using expiring user tokens, you must deselect "Expire user authorization tokens". To learn more about setting up a refresh token flow and the benefits of expiring user tokens, see "[Refreshing user-to-server access tokens](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." + ![Option to opt-in to expiring user tokens during GitHub Apps setup](/assets/images/github-apps/expire-user-tokens-selection.png) +1. If your app authorizes users using the OAuth flow, you can select **Request user authorization (OAuth) during installation** to allow people to authorize the app when they install it, saving a step. If you select this option, the "Setup URL" becomes unavailable and users will be redirected to your "User authorization callback URL" after installing the app. See "[Authorizing users during installation](/apps/installing-github-apps/#authorizing-users-during-installation)" for more information. +![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png) +1. If additional setup is required after installation, add a "Setup URL" to redirect users to after they install your app. +![Field for the setup URL of your GitHub App ](/assets/images/github-apps/github_apps_setup_url.png) {% note %} - **Observação:** Ao selecionar **Solicitar autorização do usuário (OAuth) durante a instalação** na etapa anterior, este campo irá tornar-se indisponível e as pessoas serão redirecionadas para a "URL de chamada de retorno de autorização do usuário" após a instalação do aplicativo. + **Note:** When you select **Request user authorization (OAuth) during installation** in the previous step, this field becomes unavailable and people will be redirected to the "User authorization callback URL" after installing the app. {% endnote %} -1. Na "URL Webhook", digite a URL para a qual os eventos serão POST. Cada aplicativo recebe o seu próprio webhook, que irá notificá-lo sempre que o aplicativo for instalado ou modificado, bem como quaisquer outros eventos que o aplicativo assinar. ![Campo para a URL do webhook do seu aplicativo GitHub](/assets/images/github-apps/github_apps_webhook_url.png) +1. In "Webhook URL", type the URL that events will POST to. Each app receives its own webhook which will notify you every time the app is installed or modified, as well as any other events the app subscribes to. +![Field for the webhook URL of your GitHub App](/assets/images/github-apps/github_apps_webhook_url.png) -1. Opcionalmente, no "Segredo do webhook", digite um token secreto opcional usado para proteger seus webhooks. ![Campo para adicionar um token secreto para seu webhook](/assets/images/github-apps/github_apps_webhook_secret.png) +1. Optionally, in "Webhook Secret", type an optional secret token used to secure your webhooks. +![Field to add a secret token for your webhook](/assets/images/github-apps/github_apps_webhook_secret.png) {% note %} - **Observação:** É altamente recomendável que você defina um token secreto. Para obter mais informações, consulte "[Protegendo seus webhooks](/webhooks/securing/)". + **Note:** We highly recommend that you set a secret token. For more information, see "[Securing your webhooks](/webhooks/securing/)." {% endnote %} -1. Em "Permissões", escolha as permissões que o seu aplicativo irá solicitar. Para cada tipo de permissão, use o menu suspenso e clique em **somente leitura**, **leitura & gravação** ou **Sem acesso**. ![Várias permissões para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) -1. Em "Assinar eventos", escolha os eventos que você deseja que seu aplicativo receba. -1. Para escolher o local onde o aplicativo pode ser instalado, selecione **somente nesta conta** ou **qualquer conta**. Para obter mais informações sobre as opções de instalação, consulte "[Tornando um aplicativo GitHub público ou privado](/apps/managing-github-apps/making-a-github-app-public-or-private/)". ![Opções de instalação para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_installation_options.png) -1. Click **Criar aplicativo GitHub**. ![Botão para criar o seu aplicativo GitHub](/assets/images/github-apps/github_apps_create_github_app.png) +1. In "Permissions", choose the permissions your app will request. For each type of permission, use the drop-down menu and click **Read-only**, **Read & write**, or **No access**. +![Various permissions for your GitHub App](/assets/images/github-apps/github_apps_new_permissions_post2dot13.png) +1. In "Subscribe to events", choose the events you want your app to receive. +1. To choose where the app can be installed, select either **Only on this account** or **Any account**. For more information on installation options, see "[Making a GitHub App public or private](/apps/managing-github-apps/making-a-github-app-public-or-private/)." +![Installation options for your GitHub App](/assets/images/github-apps/github_apps_installation_options.png) +1. Click **Create GitHub App**. +![Button to create your GitHub App](/assets/images/github-apps/github_apps_create_github_app.png) diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 1ea8edbf72..f3dc98fd52 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -2,8 +2,8 @@ title: Identifying and authorizing users for GitHub Apps intro: '{% data reusables.shortdesc.identifying_and_authorizing_github_apps %}' redirect_from: - - /early-access/integrations/user-identification-authorization/ - - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps/ + - /early-access/integrations/user-identification-authorization + - /apps/building-integrations/setting-up-and-registering-github-apps/identifying-users-for-github-apps - /apps/building-github-apps/identifying-and-authorizing-users-for-github-apps - /developers/apps/identifying-and-authorizing-users-for-github-apps versions: diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/index.md b/translations/pt-BR/content/developers/apps/building-github-apps/index.md index 6880e163d2..20e2cd4b16 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/index.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/index.md @@ -1,8 +1,8 @@ --- -title: Criar aplicativos GitHub -intro: Você pode criar aplicativos GitHub para você mesmo ou para os outros usarem. Saiba como registrar e configurar permissões e opções de autenticação para os aplicativos GitHub. +title: Building GitHub Apps +intro: You can build GitHub Apps for yourself or others to use. Learn how to register and set up permissions and authentication options for GitHub Apps. redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/ + - /apps/building-integrations/setting-up-and-registering-github-apps - /apps/building-github-apps versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md index 69254e7f3d..6027f1bb2b 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md @@ -2,9 +2,9 @@ title: Rate limits for GitHub Apps intro: '{% data reusables.shortdesc.rate_limits_github_apps %}' redirect_from: - - /early-access/integrations/rate-limits/ - - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps/ - - /apps/building-github-apps/rate-limits-for-github-apps/ + - /early-access/integrations/rate-limits + - /apps/building-integrations/setting-up-and-registering-github-apps/about-rate-limits-for-github-apps + - /apps/building-github-apps/rate-limits-for-github-apps - /apps/building-github-apps/understanding-rate-limits-for-github-apps - /developers/apps/rate-limits-for-github-apps versions: diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md index ec8795ccf9..df3ebbe72d 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/setting-permissions-for-github-apps.md @@ -1,9 +1,9 @@ --- -title: Configurando permissões para aplicativos GitHub +title: Setting permissions for GitHub Apps intro: '{% data reusables.shortdesc.permissions_github_apps %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps/ - - /apps/building-github-apps/permissions-for-github-apps/ + - /apps/building-integrations/setting-up-and-registering-github-apps/about-permissions-for-github-apps + - /apps/building-github-apps/permissions-for-github-apps - /apps/building-github-apps/setting-permissions-for-github-apps - /developers/apps/setting-permissions-for-github-apps versions: @@ -13,7 +13,6 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Definir permissões +shortTitle: Set permissions --- - -Aplicativos do GitHub não têm quaisquer permissões por padrão. Ao criar um aplicativo GitHub, você pode selecionar as permissões de que precisa para acessar os dados do usuário final. As permissões também podem ser adicionadas e removidas. Para obter mais informações, consulte "[Editando as permissões de um aplicativo GitHub](/apps/managing-github-apps/editing-a-github-app-s-permissions/)". +GitHub Apps don't have any permissions by default. When you create a GitHub App, you can select the permissions it needs to access end user data. Permissions can also be added and removed. For more information, see "[Editing a GitHub App's permissions](/apps/managing-github-apps/editing-a-github-app-s-permissions/)." diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md index fc5641bce7..d390f9c8e5 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/authorizing-oauth-apps.md @@ -2,11 +2,11 @@ title: Authorizing OAuth Apps intro: '{% data reusables.shortdesc.authorizing_oauth_apps %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps/ - - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access/ - - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps/ - - /v3/oauth/ - - /apps/building-oauth-apps/authorization-options-for-oauth-apps/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-authorization-options-for-oauth-apps + - /apps/building-integrations/setting-up-and-registering-oauth-apps/directing-users-to-review-their-access + - /apps/building-integrations/setting-up-and-registering-oauth-apps/creating-multiple-tokens-for-oauth-apps + - /v3/oauth + - /apps/building-oauth-apps/authorization-options-for-oauth-apps - /apps/building-oauth-apps/authorizing-oauth-apps - /developers/apps/authorizing-oauth-apps versions: diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md index 2ae8b9f00c..a080cbc4da 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/creating-an-oauth-app.md @@ -1,8 +1,8 @@ --- -title: Criar um aplicativo OAuth +title: Creating an OAuth App intro: '{% data reusables.shortdesc.creating_oauth_apps %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps/registering-oauth-apps - /apps/building-oauth-apps/creating-an-oauth-app - /developers/apps/creating-an-oauth-app versions: @@ -13,11 +13,10 @@ versions: topics: - OAuth Apps --- - {% ifversion fpt or ghec %} {% note %} - **Observação:** {% data reusables.apps.maximum-oauth-apps-allowed %} + **Note:** {% data reusables.apps.maximum-oauth-apps-allowed %} {% endnote %} {% endif %} @@ -25,29 +24,35 @@ topics: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} -4. Clique em **Novo aplicativo OAuth**. ![Botão para criar um novo aplicativo OAuth](/assets/images/oauth-apps/oauth_apps_new_app.png) +4. Click **New OAuth App**. +![Button to create a new OAuth app](/assets/images/oauth-apps/oauth_apps_new_app.png) {% note %} - **Observação:** Se você não criou um aplicativo antes, este botão informará: **Registre um novo aplicativo**. + **Note:** If you haven't created an app before, this button will say, **Register a new application**. {% endnote %} -6. Em "Nome do aplicativo", digite o nome do seu aplicativo. ![Campo para o nome do seu aplicativo](/assets/images/oauth-apps/oauth_apps_application_name.png) +6. In "Application name", type the name of your app. +![Field for the name of your app](/assets/images/oauth-apps/oauth_apps_application_name.png) {% warning %} - **Aviso:** Use apenas informações em seu aplicativo OAuth que você considera públicas. Ao criar um aplicativo OAuth, evite o uso de dados confidenciais, como, por exemplo, URLs internas. + **Warning:** Only use information in your OAuth app that you consider public. Avoid using sensitive data, such as internal URLs, when creating an OAuth App. {% endwarning %} -7. Em "URL da página inicial", digite a URL completa do site do seu aplicativo. ![Campo para a URL da página inicial de seu aplicativo](/assets/images/oauth-apps/oauth_apps_homepage_url.png) -8. Opcionalmente, em "Descrição do aplicativo", digite uma descrição do seu aplicativo que os usuários irão ver. ![Campo para uma descrição do seu aplicativo](/assets/images/oauth-apps/oauth_apps_application_description.png) -9. Em "URL de retorno de chamada de autorização", digite a URL de retorno de chamada do seu aplicativo. ![Campo para a URL de retorno de chamada de autorização do seu aplicativo](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) +7. In "Homepage URL", type the full URL to your app's website. +![Field for the homepage URL of your app](/assets/images/oauth-apps/oauth_apps_homepage_url.png) +8. Optionally, in "Application description", type a description of your app that users will see. +![Field for a description of your app](/assets/images/oauth-apps/oauth_apps_application_description.png) +9. In "Authorization callback URL", type the callback URL of your app. +![Field for the authorization callback URL of your app](/assets/images/oauth-apps/oauth_apps_authorization_callback_url.png) {% ifversion fpt or ghes > 3.0 or ghec %} {% note %} - **Observação:** Os aplicativos OAuth não podem ter várias URLs de retorno de chamada, diferente de {% data variables.product.prodname_github_apps %}. + **Note:** OAuth Apps cannot have multiple callback URLs, unlike {% data variables.product.prodname_github_apps %}. {% endnote %} {% endif %} -10. Clique em **Register application** (Registrar aplicativo). ![Botão para registrar um aplicativo](/assets/images/oauth-apps/oauth_apps_register_application.png) +10. Click **Register application**. +![Button to register an application](/assets/images/oauth-apps/oauth_apps_register_application.png) diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md index 94e8588342..69a5c827a2 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/index.md @@ -1,8 +1,8 @@ --- -title: Criar aplicativos OAuth -intro: Você pode criar aplicativos OAuth para você mesmo ou para outros usarem. Saiba como se registrar e configurar permissões e opções de autorização para os aplicativos OAuth. +title: Building OAuth Apps +intro: You can build OAuth Apps for yourself or others to use. Learn how to register and set up permissions and authorization options for OAuth Apps. redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps - /apps/building-oauth-apps versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md index 3dc9de0fb9..bdf4b1997d 100644 --- a/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md @@ -2,8 +2,8 @@ title: Scopes for OAuth Apps intro: '{% data reusables.shortdesc.understanding_scopes_for_oauth_apps %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps/ - - /apps/building-oauth-apps/scopes-for-oauth-apps/ + - /apps/building-integrations/setting-up-and-registering-oauth-apps/about-scopes-for-oauth-apps + - /apps/building-oauth-apps/scopes-for-oauth-apps - /apps/building-oauth-apps/understanding-scopes-for-oauth-apps - /developers/apps/scopes-for-oauth-apps versions: diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md index bcb5178dfb..d60e0d8400 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/about-apps.md @@ -2,9 +2,9 @@ title: About apps intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}' redirect_from: - - /apps/building-integrations/setting-up-a-new-integration/ - - /apps/building-integrations/ - - /apps/getting-started-with-building-apps/ + - /apps/building-integrationssetting-up-a-new-integration + - /apps/building-integrations + - /apps/getting-started-with-building-apps - /apps/about-apps - /developers/apps/about-apps versions: diff --git a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md index 3b4da45422..6e2ffa00ba 100644 --- a/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md +++ b/translations/pt-BR/content/developers/apps/getting-started-with-apps/differences-between-github-apps-and-oauth-apps.md @@ -2,8 +2,8 @@ title: Differences between GitHub Apps and OAuth Apps intro: 'Understanding the differences between {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} will help you decide which app you want to create. An {% data variables.product.prodname_oauth_app %} acts as a GitHub user, whereas a {% data variables.product.prodname_github_app %} uses its own identity when installed on an organization or on repositories within an organization.' redirect_from: - - /early-access/integrations/integrations-vs-oauth-applications/ - - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type/ + - /early-access/integrations/integrations-vs-oauth-applications + - /apps/building-integrations/setting-up-a-new-integration/about-choosing-an-integration-type - /apps/differences-between-apps - /developers/apps/differences-between-github-apps-and-oauth-apps versions: diff --git a/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md b/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md index ff4b0919c7..fa26be18c7 100644 --- a/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md +++ b/translations/pt-BR/content/developers/apps/guides/using-the-github-api-in-your-app.md @@ -1,8 +1,8 @@ --- -title: Usar a API do GitHub no seu aplicativo -intro: Aprenda como configurar seu aplicativo para ouvir eventos e usar a biblioteca do Octokit para realizar operações da API REST. +title: Using the GitHub API in your app +intro: Learn how to set up your app to listen for events and use the Octokit library to perform REST API operations. redirect_from: - - /apps/building-your-first-github-app/ + - /apps/building-your-first-github-app - /apps/quickstart-guides/using-the-github-api-in-your-app - /developers/apps/using-the-github-api-in-your-app versions: @@ -12,90 +12,89 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Crie um aplicativo com a API REST +shortTitle: Build an app with the REST API --- +## Introduction -## Introdução +This guide will help you build a GitHub App and run it on a server. The app you build will add a label to all new issues opened in the repository where the app is installed. -Este guia irá ajudá-lo a criar um aplicativo GitHub e executá-lo em um servidor. O aplicativo que você criar adicionará uma etiqueta a todos os novos problemas abertos no repositório onde o aplicativo está instalado. +This project will walk you through the following: -Este projeto orientará você no seguinte: - -* Programar seu aplicativo para ouvir eventos -* Usar a biblioteca do Octokit.rb para realizar operações da API REST +* Programming your app to listen for events +* Using the Octokit.rb library to do REST API operations {% data reusables.apps.app-ruby-guides %} -Uma concluídas as etapas, você estará pronto para desenvolver outros tipos de integrações usando o conjunto completo das APIS do GitHub. {% ifversion fpt or ghec %}Você pode conferir exemplos bem-sucedidos de aplicativos no [GitHub Marketplace](https://github.com/marketplace) e em [Trabalhos com GitHub](https://github.com/works-with).{% endif %} +Once you've worked through the steps, you'll be ready to develop other kinds of integrations using the full suite of GitHub APIs. {% ifversion fpt or ghec %}You can check out successful examples of apps on [GitHub Marketplace](https://github.com/marketplace) and [Works with GitHub](https://github.com/works-with).{% endif %} -## Pré-requisitos +## Prerequisites -Você pode achar útil ter um entendimento básico do seguinte: +You may find it helpful to have a basic understanding of the following: -* [Aplicativos do GitHub](/apps/about-apps) +* [GitHub Apps](/apps/about-apps) * [Webhooks](/webhooks) -* [Linguagem de programação Ruby](https://www.ruby-lang.org/en/) -* [APIs REST](/rest) +* [The Ruby programming language](https://www.ruby-lang.org/en/) +* [REST APIs](/rest) * [Sinatra](http://sinatrarb.com/) -Mas é possível acompanhar o processo em qualquer nível de experiência. Nós vamos nos conectar a informações de que você precisa ao longo do caminho! +But you can follow along at any experience level. We'll link out to information you need along the way! -Antes de começar, você precisará fazer o seguinte: +Before you begin, you'll need to do the following: -1. Clone o repositório [Usando a API do GitHub no seu aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app). +1. Clone the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository. ```shell $ git clone https://github.com/github-developer/using-the-github-api-in-your-app.git ``` - Dentro do diretório, você encontrará um arquivo `template_server.rb` com o código do template você usará neste início rápido e um arquivo `server.rb` arquivo com o código do projeto concluído. + Inside the directory, you'll find a `template_server.rb` file with the template code you'll use in this quickstart and a `server.rb` file with the completed project code. -1. Siga as etapas no início rápido [Configurando o seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/) para configurar e executar o servidor do aplicativo `template_server.rb`. Se você já concluiu um início rápido do aplicativo GitHub diferente de [Configurar seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/), você deverá registrar um _novo_ aplicativo GitHub e começar um novo canal da Smee para usar com este início rápido. +1. Follow the steps in the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart to configure and run the `template_server.rb` app server. If you've previously completed a GitHub App quickstart other than [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/), you should register a _new_ GitHub App and start a new Smee channel to use with this quickstart. - Este início rápido inclui o mesmo código `template_server.rb` que o início rápido [Configurando o seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/). **Observação:** Conforme você segue com o início rápido [Configurando seu ambiente de desenvolvimento](/apps/quickstart-guides/setting-up-your-development-environment/), certifique-se de usar os arquivos do projeto incluídos no repositório [Usando a API do GitHub no seu aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app). + This quickstart includes the same `template_server.rb` code as the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart. **Note:** As you follow along with the [Setting up your development environment](/apps/quickstart-guides/setting-up-your-development-environment/) quickstart, make sure to use the project files included in the [Using the GitHub API in your app](https://github.com/github-developer/using-the-github-api-in-your-app) repository. - Consulte a seção [Solução de problemas](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) se você tiver problemas na configuração do seu aplicativo GitHub do modelo. + See the [Troubleshooting](/apps/quickstart-guides/setting-up-your-development-environment/#troubleshooting) section if you are running into problems setting up your template GitHub App. -## Criar o aplicativo +## Building the app -Agora que você está familiarizado com o código `template_server.rb`, você irá criar um código que adiciona automaticamente a etiqueta `needs-response` para todos os problemas abertos no repositório onde o aplicativo está instalado. +Now that you're familiar with the `template_server.rb` code, you're going to create code that automatically adds the `needs-response` label to all issues opened in the repository where the app is installed. -O arquivo `template_server.rb` contém código do modelo do aplicativo que ainda não foi personalizado. Neste arquivo, você verá um espaço reservado para manipular eventos de webhook e outro código para inicializar um cliente Octokit.rb. +The `template_server.rb` file contains app template code that has not yet been customized. In this file, you'll see some placeholder code for handling webhook events and some other code for initializing an Octokit.rb client. {% note %} -**Observação:** `template_server.rb` contém muitos comentários de código que complementam este guia e explicam detalhes técnicos adicionais. Você pode considerar útil ler os comentários do arquivo antes de seguir com esta seção, para obter uma visão geral de como o código funciona. +**Note:** `template_server.rb` contains many code comments that complement this guide and explain additional technical details. You may find it helpful to read through the comments in that file now, before continuing with this section, to get an overview of how the code works. -O código final personalizado que você criará no final deste guia é fornecido em [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Mas espere até o final para olhar isso! +The final customized code that you'll create by the end of this guide is provided in [`server.rb`](https://github.com/github-developer/using-the-github-api-in-your-app/blob/master/server.rb). Try waiting until the end to look at it, though! {% endnote %} -Estas são as etapas que você concluirá para criar seu primeiro aplicativo GitHub: +These are the steps you'll complete to create your first GitHub App: -1. [Atualizar as permissões do aplicativo](#step-1-update-app-permissions) -2. [Adicionar gerenciamento de evento](#step-2-add-event-handling) -3. [Criar nova etiqueta](#step-3-create-a-new-label) -4. [Adicionar gerenciamento de etiqueta](#step-4-add-label-handling) +1. [Update app permissions](#step-1-update-app-permissions) +2. [Add event handling](#step-2-add-event-handling) +3. [Create a new label](#step-3-create-a-new-label) +4. [Add label handling](#step-4-add-label-handling) -## Etapa 1. Atualizar as permissões do aplicativo +## Step 1. Update app permissions -Quando você [registrou seu aplicativo pela primeira vez](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), você aceitou as permissões-padrão, o que significa que seu aplicativo não tem acesso à maioria dos recursos. Para este exemplo, seu aplicativo precisará de permissão para ler problemas e escrever etiquetas. +When you [first registered your app](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app), you accepted the default permissions, which means your app doesn't have access to most resources. For this example, your app will need permission to read issues and write labels. -Para atualizar as permissões do aplicativo: +To update your app's permissions: -1. Selecione seu aplicativo na [página de configurações do aplicativo](https://github.com/settings/apps) e clique em **Permissões & Webhooks** na barra lateral. -1. Na seção "Permissões", encontre "Problemas" e selecione **Leitura & Gravação** no menu "suspenso Acesso" ao lado. A descrição diz que esta opção concede acesso a problemas e etiquetas, o que é exatamente o que você precisa. -1. Na seção "Assinar eventos", selecione **Problemas** para assinar o evento. +1. Select your app from the [app settings page](https://github.com/settings/apps) and click **Permissions & Webhooks** in the sidebar. +1. In the "Permissions" section, find "Issues," and select **Read & Write** in the "Access" dropdown next to it. The description says this option grants access to both issues and labels, which is just what you need. +1. In the "Subscribe to events" section, select **Issues** to subscribe to the event. {% data reusables.apps.accept_new_permissions_steps %} -Ótimo! Seu aplicativo tem permissão para realizar as tarefas que você deseja que ele realize. Agora você pode adicionar o código para que ele funcione. +Great! Your app has permission to do the tasks you want it to do. Now you can add the code to make it work. -## Etapa 2. Adicionar gerenciamento de evento +## Step 2. Add event handling -A primeira coisa que seu aplicativo precisa fazer é ouvir novos problemas que estão abertos. Agora que você se assinou o evento **Problemas**, você começará a receber o webhook dos [`problemas`](/webhooks/event-payloads/#issues), que é acionado quando ocorrem certas ações relacionadas a um problema. Você pode filtrar este tipo de evento para a ação específica que você deseja no seu código. +The first thing your app needs to do is listen for new issues that are opened. Now that you've subscribed to the **Issues** event, you'll start receiving the [`issues`](/webhooks/event-payloads/#issues) webhook, which is triggered when certain issue-related actions occur. You can filter this event type for the specific action you want in your code. -O GitHub envia cargas do webhook como solicitações de `POST`. Porque você encaminhou suas cargas de webhook da Smee para `http://localhost/event_handler:3000`, seu servidor receberá as cargas de solicitação de `POST` no rota `post '/event_handler'`. +GitHub sends webhook payloads as `POST` requests. Because you forwarded your Smee webhook payloads to `http://localhost/event_handler:3000`, your server will receive the `POST` request payloads in the `post '/event_handler'` route. -Um encaminhamento vazio `post '/event_handler'` já está incluído no arquivo `template_server.rb`, que você baixou na seção [pré-requisitos](#prerequisites). O encaminhamento vazio tem a seguinte forma: +An empty `post '/event_handler'` route is already included in the `template_server.rb` file, which you downloaded in the [prerequisites](#prerequisites) section. The empty route looks like this: ``` ruby post '/event_handler' do @@ -108,7 +107,7 @@ Um encaminhamento vazio `post '/event_handler'` já está incluído no arquivo ` end ``` -Use essa encaminhamento para gerenciar o evento `problemas`, adicionando o seguinte código: +Use this route to handle the `issues` event by adding the following code: ``` ruby case request.env['HTTP_X_GITHUB_EVENT'] @@ -119,9 +118,9 @@ when 'issues' end ``` -Cada evento que o GitHub envia inclui um cabeçalho de solicitação denominado `HTTP_X_GITHUB_EVENT`, que indica o tipo de evento na solicitação de `POST`. No momento, você só está interessado nos tipos de evento de `problemas`. Cada evento tem um campo `ação` adicional que indica o tipo de ação que acionou os eventos. Para `problemas`, o campo `ação` pode ser `atribuído`, `não atribuído`, `etiquetado`, `não etiquetado`,, `abriu`, `editado`, `marcado`,, `desmarcado`, `fechado` ou `reaberto`. +Every event that GitHub sends includes a request header called `HTTP_X_GITHUB_EVENT`, which indicates the type of event in the `POST` request. Right now, you're only interested in `issues` event types. Each event has an additional `action` field that indicates the type of action that triggered the events. For `issues`, the `action` field can be `assigned`, `unassigned`, `labeled`, `unlabeled`, `opened`, `edited`, `milestoned`, `demilestoned`, `closed`, or `reopened`. -Para testar seu gerenciador de eventos, tente adicionar um método auxiliar temporário. Você irá atualizar mais tarde ao [Adicionar o gerenciamento da etiqueta](#step-4-add-label-handling). Por enquanto, adicione o seguinte código na seção `Ajudantes fazem` do código. Você pode colocar o novo método acima ou abaixo de qualquer outro método de ajuda. A ordem não importa. +To test your event handler, try adding a temporary helper method. You'll update later when you [Add label handling](#step-4-add-label-handling). For now, add the following code inside the `helpers do` section of the code. You can put the new method above or below any of the other helper methods. Order doesn't matter. ``` ruby def handle_issue_opened_event(payload) @@ -129,37 +128,37 @@ def handle_issue_opened_event(payload) end ``` -Este método recebe uma carga de eventos formatada em JSON como argumento. Isso significa que você pode analisar a carga no método e detalhar os dados específicos de que você precisa. Você pode achar útil inspecionar a carga completa em algum momento: tente alterar `logger.debug 'An issue was opened!` para `logger.debug payload`. A estrutura da carga que você vê deve corresponder ao que é [mostrado na documentação de evento de webhook dos `problemas`](/webhooks/event-payloads/#issues). +This method receives a JSON-formatted event payload as an argument. This means you can parse the payload in the method and drill down to any specific data you need. You may find it helpful to inspect the full payload at some point: try changing `logger.debug 'An issue was opened!` to `logger.debug payload`. The payload structure you see should match what's [shown in the `issues` webhook event docs](/webhooks/event-payloads/#issues). -Ótimo! É hora de testar as alterações. +Great! It's time to test the changes. {% data reusables.apps.sinatra_restart_instructions %} -No seu navegador, acesse o repositório onde você instalou seu aplicativo. Abra um novo problema neste repositório. O problema pode dizer o que você quiser. É apenas para teste. +In your browser, visit the repository where you installed your app. Open a new issue in this repository. The issue can say anything you like. It's just for testing. -Ao olhar para o seu Terminal, você deve ver uma mensagem na saída que diz: `Um problema foi aberto!` Parabéns! Você adicionou um gerenciador de eventos ao seu aplicativo. 💪 +When you look back at your Terminal, you should see a message in the output that says, `An issue was opened!` Congrats! You've added an event handler to your app. 💪 -## Etapa 3. Criar nova etiqueta +## Step 3. Create a new label -Ok, seu aplicativo pode dizer quando os problemas estão abertos. Agora você quer que ele adicione a etiqueta `needs-response` a qualquer problema recém-aberto em um repositório no qual o aplicativo está instalado. +Okay, your app can tell when issues are opened. Now you want it to add the label `needs-response` to any newly opened issue in a repository the app is installed in. -Antes que a etiqueta possa ser _adicionada_ em qualquer lugar, você precisará _criar_ a etiqueta personalizada no seu repositório. Você só terá de fazer isso uma vez. Para fins deste guia, crie a etiqueta manualmente no GitHub. No seu repositório, clique em **Problemas** e, em seguida, em **Etiquetas** e depois clique em **Nova etiqueta**. Nomeie a nova etiqueta `needs-response`. +Before the label can be _added_ anywhere, you'll need to _create_ the custom label in your repository. You'll only need to do this one time. For the purposes of this guide, create the label manually on GitHub. In your repository, click **Issues**, then **Labels**, then click **New label**. Name the new label `needs-response`. {% tip %} -**Dica**: Não seria ótimo se o aplicativo pudesse criar a etiqueta de forma programática? [Ele pode](/rest/reference/issues#create-a-label)! Adicione o código para fazer isso por conta própria depois de concluir as etapas deste guia. +**Tip**: Wouldn't it be great if your app could create the label programmatically? [It can](/rest/reference/issues#create-a-label)! Try adding the code to do that on your own after you finish the steps in this guide. {% endtip %} -Agora que o rótulo foi criado, você pode programar seu aplicativo para usar a API REST para [adicionar a etiqueta a qualquer problema recém-aberto](/rest/reference/issues#add-labels-to-an-issue). +Now that the label exists, you can program your app to use the REST API to [add the label to any newly opened issue](/rest/reference/issues#add-labels-to-an-issue). -## Etapa 4. Adicionar gerenciamento de etiqueta +## Step 4. Add label handling -Parabéns! Você chegou à etapa final: adicionando o gerenciamento de etiquetas ao seu aplicativo. Para esta tarefa, você vai irá usar a [biblioteca Octokit.rb do Ruby](http://octokit.github.io/octokit.rb/). +Congrats—you've made it to the final step: adding label handling to your app. For this task, you'll want to use the [Octokit.rb Ruby library](http://octokit.github.io/octokit.rb/). -Na documentação do Octokit.rb, encontre a lista de [métodos da etiqueta](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). O método que você vai querer usar será [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method). +In the Octokit.rb docs, find the list of [label methods](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html). The method you'll want to use is [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method). -Ao voltar para `template_server.rb`, encontre o método definido anteriormente: +Back in `template_server.rb`, find the method you defined previously: ``` ruby def handle_issue_opened_event(payload) @@ -167,13 +166,13 @@ def handle_issue_opened_event(payload) end ``` -A documentação [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) mostra que você precisará passar três argumentos para este método: +The [`add_labels_to_an_issue`](http://octokit.github.io/octokit.rb/Octokit/Client/Labels.html#add_labels_to_an_issue-instance_method) docs show you'll need to pass three arguments to this method: -* Repo (string em formato `"proprietário/nome"`) -* Número do problema (inteiro) -* Etiquetas (array) +* Repo (string in `"owner/name"` format) +* Issue number (integer) +* Labels (array) -Você pode analisar a carga para obter o repositório e o número do problema. Como o nome da etiqueta será sempre o mesmo (`needs-response`) você pode passá-lo como uma string de caracteres codificados no array de etiquetas. Ao juntar essas peças, seu método atualizado pode parecer com isto: +You can parse the payload to get both the repo and the issue number. Since the label name will always be the same (`needs-response`), you can pass it as a hardcoded string in the labels array. Putting these pieces together, your updated method might look like this: ``` ruby # When an issue is opened, add a label @@ -184,56 +183,56 @@ def handle_issue_opened_event(payload) end ``` -Tente abrir um novo problema no seu repositório de teste e veja o que acontece! Se nada acontecer imediatamente, tente atualizar. +Try opening a new issue in your test repository and see what happens! If nothing happens right away, try refreshing. -Você não verá muitos coisas no Terminal, _mas_ você deve ver que um usuário bot adicionou uma etiqueta ao problema. +You won't see much in the Terminal, _but_ you should see that a bot user has added a label to the issue. {% note %} -**Observação:** Quando os aplicativos GitHub realizam ações pela API, como, por exemplo, adicionar etiquetas, o GitHub mostra essas ações como sendo realizadas por contas _do bot_. Para obter mais informações, consulte "[Máquina vs. contas de bot](/apps/differences-between-apps/#machine-vs-bot-accounts)". +**Note:** When GitHub Apps take actions via the API, such as adding labels, GitHub shows these actions as being performed by _bot_ accounts. For more information, see "[Machine vs. bot accounts](/apps/differences-between-apps/#machine-vs-bot-accounts)." {% endnote %} -Se for assim, parabéns! Você construiu um aplicativo funcional com sucesso! 🎉 +If so, congrats! You've successfully built a working app! 🎉 -Você pode ver o código final no `server.rb` no [repositório do modelo do aplicativo](https://github.com/github-developer/using-the-github-api-in-your-app). +You can see the final code in `server.rb` in the [app template repository](https://github.com/github-developer/using-the-github-api-in-your-app). -Consulte "[Próximos passos](#next-steps)" para ter ideias sobre aonde você pode ir a partir daqui. +See "[Next steps](#next-steps)" for ideas about where you can go from here. -## Solução de Problemas +## Troubleshooting -Aqui estão alguns problemas comuns e algumas soluções sugeridas. Se você tiver qualquer outro problema, poderá pedir ajuda ou orientação em {% data variables.product.prodname_support_forum_with_url %}. +Here are a few common problems and some suggested solutions. If you run into any other trouble, you can ask for help or advice in the {% data variables.product.prodname_support_forum_with_url %}. -* **P:** Meu servidor não está ouvindo eventos! O cliente da Smee está sendo executado em uma janela de Terminal, e eu estou enviando eventos para o github.com. abrindo novos problemas, mas não vejo nenhuma saída na janela do Terminal onde estou executando o servidor. +* **Q:** My server isn't listening to events! The Smee client is running in a Terminal window, and I'm sending events on GitHub.com by opening new issues, but I don't see any output in the Terminal window where I'm running the server. - **A:** Você pode não ter o domínio correto da Smee nas configurações do seu aplicativo. Visite a sua [página de configurações do aplicativo](https://github.com/settings/apps) e verifique novamente os campos exibidos em "[Registre um novo aplicativo com GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)". Certifique-se de que o domínio nesses campos corresponde ao domínio que você usou no seu comando `smee -u ` em "[Iniciar um novo canal da Smee](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)". + **A:** You may not have the correct Smee domain in your app settings. Visit your [app settings page](https://github.com/settings/apps) and double-check the fields shown in "[Register a new app with GitHub](/apps/quickstart-guides/setting-up-your-development-environment/#step-2-register-a-new-github-app)." Make sure the domain in those fields matches the domain you used in your `smee -u ` command in "[Start a new Smee channel](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel)." -* **P:** Meu aplicativo não funciona! Eu abri um novo problema, mas mesmo depois de atualizado, nenhuma etiqueta foi adicionado a ele. +* **Q:** My app doesn't work! I opened a new issue, but even after refreshing, no label has been added to it. - **R:** Certifique-se de que todos os pontos a seguir sejam verdadeiros: + **A:** Make sure all of the following are true: - * Você [instalou o aplicativo](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) no repositório onde você está abrindo o problema. - * Seu [Cliente da Smee em execução](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) em uma janela do Terminal. - * Seu [servidor web está em execução](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) sem erros em outra janela do Terminal. - * Seu aplicativo tem permissões de [leitura & e gravação permissões em problemas e está assinado a eventos do problema](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel). - * Você [verificou seu e-mail](#step-1-update-app-permissions) depois de atualizar as permissões e aceitou as novas permissões. + * You [installed the app](/apps/quickstart-guides/setting-up-your-development-environment/#step-7-install-the-app-on-your-account) on the repository where you're opening the issue. + * Your [Smee client is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel) in a Terminal window. + * Your [web server is running](/apps/quickstart-guides/setting-up-your-development-environment/#step-6-start-the-server) with no errors in another Terminal window. + * Your app has [read & write permissions on issues and is subscribed to issue events](/apps/quickstart-guides/setting-up-your-development-environment/#step-1-start-a-new-smee-channel). + * You [checked your email](#step-1-update-app-permissions) after updating the permissions and accepted the new permissions. -## Conclusão +## Conclusion -Depois de analisar este guia, você aprendeu os componentes básicos para o desenvolvimento dos aplicativos GitHub! Para resumir, você: +After walking through this guide, you've learned the basic building blocks for developing GitHub Apps! To review, you: -* Programou seu aplicativo para ouvir eventos -* Usou a biblioteca do Octokit.rb para fazer operações da API REST +* Programmed your app to listen for events +* Used the Octokit.rb library to do REST API operations -## Próximas etapas +## Next steps -Aqui estão algumas ideias do que você pode fazer a seguir: +Here are some ideas for what you can do next: -* [Reescreva seu aplicativo usando o GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)! -* Reescreva seu aplicativo no Node.js usando o [Probot](https://github.com/probot/probot)! -* Faça o aplicativo verificar se a etiqueta `needs-response` já existe no problema, e, em caso negativo, adicione-a. -* Quando o bot adiciona a etiqueta com sucesso, é exibida uma mensagem no Terminal. (Dica: compare o ID da etiqueta `needs-response` com o ID da etiqueta na carga como uma condição para sua mensagem para que a mensagem seja exibida somente quando a etiqueta relevante for adicionada e não qualquer outra etiqueta.) -* Adicione uma página inicial ao seu aplicativo e conecte um [encaminhamento do Sinatra](https://github.com/sinatra/sinatra#routes) para isso. -* Mova o seu código para um servidor hospedado (como o Heroku). Não se esqueça de atualizar as configurações do seu aplicativo com o novo domínio. -* Compartilhe seu projeto ou receba orientações no {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %} -* Você construiu um aplicativo novo brilhante que você considera que outras pessoas podem achar útil? [Adicione-o ao GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %} +* [Rewrite your app using GraphQL](https://developer.github.com/changes/2018-04-30-graphql-supports-github-apps/)! +* Rewrite your app in Node.js using [Probot](https://github.com/probot/probot)! +* Have the app check whether the `needs-response` label already exists on the issue, and if not, add it. +* When the bot successfully adds the label, show a message in the Terminal. (Hint: compare the `needs-response` label ID with the ID of the label in the payload as a condition for your message, so that the message only displays when the relevant label is added and not some other label.) +* Add a landing page to your app and hook up a [Sinatra route](https://github.com/sinatra/sinatra#routes) for it. +* Move your code to a hosted server (like Heroku). Don't forget to update your app settings with the new domain. +* Share your project or get advice in the {% data variables.product.prodname_support_forum_with_url %}{% ifversion fpt or ghec %} +* Have you built a shiny new app you think others might find useful? [Add it to GitHub Marketplace](/apps/marketplace/creating-and-submitting-your-app-for-approval/)!{% endif %} diff --git a/translations/pt-BR/content/developers/apps/index.md b/translations/pt-BR/content/developers/apps/index.md index e13e10d7cb..30fe7ff44f 100644 --- a/translations/pt-BR/content/developers/apps/index.md +++ b/translations/pt-BR/content/developers/apps/index.md @@ -1,12 +1,12 @@ --- -title: Aplicativos -intro: Você pode automatizar e agilizar seu fluxo de trabalho criando seus próprios aplicativos. +title: Apps +intro: You can automate and streamline your workflow by building your own apps. redirect_from: - - /early-access/integrations/ - - /early-access/integrations/authentication/ - - /early-access/integrations/install-an-integration/ - - /apps/adding-integrations/ - - /apps/building-integrations/setting-up-a-new-integration/about-integrations/ + - /early-access/integrations + - /early-access/integrations/authentication + - /early-access/integrations/install-an-integration + - /apps/adding-integrations + - /apps/building-integrations/setting-up-a-new-integration/about-integrations - /apps - /v3/integrations versions: diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md index 975da7e440..5c9cdb43cf 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/deleting-a-github-app.md @@ -1,8 +1,8 @@ --- -title: Apagar um aplicativo GitHub +title: Deleting a GitHub App intro: '{% data reusables.shortdesc.deleting_github_apps %}' redirect_from: - - /apps/building-integrations/managing-github-apps/deleting-a-github-app/ + - /apps/building-integrations/managing-github-apps/deleting-a-github-app - /apps/managing-github-apps/deleting-a-github-app - /developers/apps/deleting-a-github-app versions: @@ -13,12 +13,15 @@ versions: topics: - GitHub Apps --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Selecione o aplicativo do GitHub que você deseja excluir. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png) +4. Select the GitHub App you want to delete. +![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -6. Clique em **Excluir o aplicativo GitHub**. ![Botão para excluir um aplicativo GitHub](/assets/images/github-apps/github_apps_delete.png) -7. Digite o nome do GitHub App para confirmar que você deseja excluí-lo. ![Campo para confirmar o nome do aplicativo do GitHub que você deseja excluir](/assets/images/github-apps/github_apps_delete_integration_name.png) -8. Clique em **Eu entendo as consequências. Exclua este aplicativo GitHub**. ![Botão para confirmar a exclusão do seu aplicativo GitHub](/assets/images/github-apps/github_apps_confirm_deletion.png) +6. Click **Delete GitHub App**. +![Button to delete a GitHub App](/assets/images/github-apps/github_apps_delete.png) +7. Type the name of the GitHub App to confirm you want to delete it. +![Field to confirm the name of the GitHub App you want to delete](/assets/images/github-apps/github_apps_delete_integration_name.png) +8. Click **I understand the consequences, delete this GitHub App**. +![Button to confirm the deletion of your GitHub App](/assets/images/github-apps/github_apps_confirm_deletion.png) diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md b/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md index 2e31a303f6..3d9e709d77 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/editing-a-github-apps-permissions.md @@ -1,8 +1,8 @@ --- -title: Editar permissões do aplicativo GitHub +title: Editing a GitHub App's permissions intro: '{% data reusables.shortdesc.editing_permissions_for_github_apps %}' redirect_from: - - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions/ + - /apps/building-integrations/managing-github-apps/editing-a-github-app-s-permissions - /apps/managing-github-apps/editing-a-github-app-s-permissions - /developers/apps/editing-a-github-apps-permissions versions: @@ -12,21 +12,26 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Editar permissões +shortTitle: Edit permissions --- - {% note %} -**Observação:** As permissões atualizadas não terão efeito sobre uma instalação até que o proprietário da conta ou organização aprove as alterações. Você pode usar o [webhook do InstallationEvent](/webhooks/event-payloads/#installation) para descobrir quando as pessoas aceitam novas permissões para seu aplicativo. Uma exceção são as [permissões de nível de usuário](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), que não exigem que o proprietário da conta aprove as alterações de permissão. +**Note:** Updated permissions won't take effect on an installation until the owner of the account or organization approves the changes. You can use the [InstallationEvent webhook](/webhooks/event-payloads/#installation) to find out when people accept new permissions for your app. One exception is [user-level permissions](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/#user-level-permissions), which don't require the account owner to approve permission changes. {% endnote %} {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Selecione o aplicativo GitHub cujas permissões você deseja alterar. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png) -5. Na barra lateral esquerda, clique em **Permissions & webhooks** (Permissões e webhooks). ![Permissões e webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png) -6. Modifique as permissões que você deseja alterar. Para cada tipo de permissão, selecione "Somente leitura", "Ler & gravar" ou "Sem acesso" no menu suspenso. ![Seleção de permissões para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_permissions_post2dot13.png) -7. Em "Assinar eventos", selecione quaisquer eventos que você deseja que seu aplicativo assine. ![Seleção de permissões para seu aplicativo GitHub assinar eventos](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png) -8. Opcionalmente, em "Adicionar uma observação para os usuários", adicione uma observação informando aos usuários o por que você esta mudando as permissões que o seu aplicativo GitHub solicita. ![Caixa de entrada para adicionar uma observação aos usuários explicando por que as permissões do seu aplicativo GitHub foram alteradas](/assets/images/github-apps/github_apps_permissions_note_to_users.png) -9. Clique em **Save changes** (Salvar alterações). ![Botão para salvar alterações de permissões](/assets/images/github-apps/github_apps_save_changes.png) +4. Select the GitHub App whose permissions you want to change. +![App selection](/assets/images/github-apps/github_apps_select-app.png) +5. In the left sidebar, click **Permissions & webhooks**. +![Permissions and webhooks](/assets/images/github-apps/github_apps_permissions_and_webhooks.png) +6. Modify the permissions you'd like to change. For each type of permission, select either "Read-only", "Read & write", or "No access" from the dropdown. +![Permissions selections for your GitHub App](/assets/images/github-apps/github_apps_permissions_post2dot13.png) +7. In "Subscribe to events", select any events to which you'd like to subscribe your app. +![Permissions selections for subscribing your GitHub App to events](/assets/images/github-apps/github_apps_permissions_subscribe_to_events.png) +8. Optionally, in "Add a note to users", add a note telling your users why you are changing the permissions that your GitHub App requests. +![Input box to add a note to users explaining why your GitHub App permissions have changed](/assets/images/github-apps/github_apps_permissions_note_to_users.png) +9. Click **Save changes**. +![Button to save permissions changes](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/index.md b/translations/pt-BR/content/developers/apps/managing-github-apps/index.md index b373d1be19..718fa7bb8f 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/index.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/index.md @@ -1,8 +1,8 @@ --- -title: Gerenciar aplicativos GitHub -intro: 'Após criar e registrar um aplicativo GitHub, você poderá fazer modificações no aplicativo, alterar as permissões, transferir propriedade e e excluir o aplicativo.' +title: Managing GitHub Apps +intro: 'After you create and register a GitHub App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.' redirect_from: - - /apps/building-integrations/managing-github-apps/ + - /apps/building-integrations/managing-github-apps - /apps/managing-github-apps versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md index c8409c004a..2955f8e8c0 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/making-a-github-app-public-or-private.md @@ -2,10 +2,10 @@ title: Making a GitHub App public or private intro: '{% data reusables.shortdesc.making-a-github-app-public-or-private %}' redirect_from: - - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps/ - - /apps/building-github-apps/installation-options-for-github-apps/ - - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option/ - - /apps/managing-github-apps/changing-a-github-app-s-installation-option/ + - /apps/building-integrations/setting-up-and-registering-github-apps/about-installation-options-for-github-apps + - /apps/building-github-apps/installation-options-for-github-apps + - /apps/building-integrations/managing-github-apps/changing-a-github-app-s-installation-option + - /apps/managing-github-apps/changing-a-github-app-s-installation-option - /apps/managing-github-apps/making-a-github-app-public-or-private - /developers/apps/making-a-github-app-public-or-private versions: diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md index 270ee588b7..48fc1ccfb1 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/modifying-a-github-app.md @@ -1,8 +1,8 @@ --- -title: Modificar um aplicativo GitHub +title: Modifying a GitHub App intro: '{% data reusables.shortdesc.modifying_github_apps %}' redirect_from: - - /apps/building-integrations/managing-github-apps/modifying-a-github-app/ + - /apps/building-integrations/managing-github-apps/modifying-a-github-app - /apps/managing-github-apps/modifying-a-github-app - /developers/apps/modifying-a-github-app versions: @@ -13,10 +13,11 @@ versions: topics: - GitHub Apps --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} {% data reusables.user-settings.modify_github_app %} -5. Em "Informações básicas", modifique as informações do aplicativo GitHub que você gostaria de alterar. ![Seção de informações básicas para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_basic_information.png) -6. Clique em **Save changes** (Salvar alterações). ![Botão para salvar alterações para o seu aplicativo GitHub](/assets/images/github-apps/github_apps_save_changes.png) +5. In "Basic information", modify the GitHub App information that you'd like to change. +![Basic information section for your GitHub App](/assets/images/github-apps/github_apps_basic_information.png) +6. Click **Save changes**. +![Button to save changes for your GitHub App](/assets/images/github-apps/github_apps_save_changes.png) diff --git a/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md b/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md index 34e95fe76e..4bbe104d16 100644 --- a/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/managing-github-apps/transferring-ownership-of-a-github-app.md @@ -1,8 +1,8 @@ --- -title: Transferir a propriedade de um aplicativo GitHub +title: Transferring ownership of a GitHub App intro: '{% data reusables.shortdesc.transferring_ownership_of_github_apps %}' redirect_from: - - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app/ + - /apps/building-integrations/managing-github-apps/transferring-ownership-of-a-github-app - /apps/managing-github-apps/transferring-ownership-of-a-github-app - /developers/apps/transferring-ownership-of-a-github-app versions: @@ -12,15 +12,19 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Transferir propriedade +shortTitle: Transfer ownership --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.github_apps %} -4. Selecione o aplicativo GitHub cuja propriedade você deseja transferir. ![Seleção de aplicativo](/assets/images/github-apps/github_apps_select-app.png) +4. Select the GitHub App whose ownership you want to transfer. +![App selection](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.github_apps_advanced %} -6. Clique em **Transferir propriedade**. ![Botão para transferir a propriedade](/assets/images/github-apps/github_apps_transfer_ownership.png) -7. Digite o nome do aplicativo do GitHub que você deseja transferir. ![Campo para inserir o nome do aplicativo a ser transferido](/assets/images/github-apps/github_apps_transfer_app_name.png) -8. Digite o nome do usuário ou organização para o qual você deseja transferir o aplicativo GitHub. ![Campo para inserir o usuário ou organização para o qual transferir](/assets/images/github-apps/github_apps_transfer_new_owner.png) -9. Clique **Transferir este aplicativo GitHub**. ![Botão para confirmar a transferência de um aplicativo GitHub](/assets/images/github-apps/github_apps_transfer_integration.png) +6. Click **Transfer ownership**. +![Button to transfer ownership](/assets/images/github-apps/github_apps_transfer_ownership.png) +7. Type the name of the GitHub App you want to transfer. +![Field to enter the name of the app to transfer](/assets/images/github-apps/github_apps_transfer_app_name.png) +8. Type the name of the user or organization you want to transfer the GitHub App to. +![Field to enter the user or org to transfer to](/assets/images/github-apps/github_apps_transfer_new_owner.png) +9. Click **Transfer this GitHub App**. +![Button to confirm the transfer of a GitHub App](/assets/images/github-apps/github_apps_transfer_integration.png) diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md index 3dbccbf948..26affcb17f 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/deleting-an-oauth-app.md @@ -1,8 +1,8 @@ --- -title: Excluir um aplicativo OAuth +title: Deleting an OAuth App intro: '{% data reusables.shortdesc.deleting_oauth_apps %}' redirect_from: - - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app/ + - /apps/building-integrations/managing-oauth-apps/deleting-an-oauth-app - /apps/managing-oauth-apps/deleting-an-oauth-app - /developers/apps/deleting-an-oauth-app versions: @@ -13,10 +13,12 @@ versions: topics: - OAuth Apps --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} -4. Selecione o {% data variables.product.prodname_oauth_app %} que você deseja modificar. ![Seleção de aplicativo](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) -5. Clique em **Excluir o aplicativo**. ![Botão para excluir o aplicativo](/assets/images/oauth-apps/oauth_apps_delete_application.png) -6. Clique em **Excluir este aplicativo OAuth**. ![Botão para confirmar a exclusão](/assets/images/oauth-apps/oauth_apps_delete_confirm.png) +4. Select the {% data variables.product.prodname_oauth_app %} you want to modify. +![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) +5. Click **Delete application**. +![Button to delete the application](/assets/images/oauth-apps/oauth_apps_delete_application.png) +6. Click **Delete this OAuth Application**. +![Button to confirm the deletion](/assets/images/oauth-apps/oauth_apps_delete_confirm.png) diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md index 70dcd3d028..5a40c83444 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/index.md @@ -1,8 +1,8 @@ --- -title: Gerenciar aplicativos OAuth -intro: 'Após criar e registrar um aplicativo OAuth, você poderá fazer modificações no aplicativo, alterar as permissões, transferir propriedade e e excluir o aplicativo.' +title: Managing OAuth Apps +intro: 'After you create and register an OAuth App, you can make modifications to the app, change permissions, transfer ownership, and delete the app.' redirect_from: - - /apps/building-integrations/managing-oauth-apps/ + - /apps/building-integrations/managing-oauth-apps - /apps/managing-oauth-apps versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md index 025768d17c..c6196ae921 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/modifying-an-oauth-app.md @@ -1,8 +1,8 @@ --- -title: Modificar um aplicativo OAuth +title: Modifying an OAuth App intro: '{% data reusables.shortdesc.modifying_oauth_apps %}' redirect_from: - - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app/ + - /apps/building-integrations/managing-oauth-apps/modifying-an-oauth-app - /apps/managing-oauth-apps/modifying-an-oauth-app - /developers/apps/modifying-an-oauth-app versions: @@ -13,10 +13,9 @@ versions: topics: - OAuth Apps --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} {% data reusables.user-settings.modify_oauth_app %} -1. Modifique as informações do {% data variables.product.prodname_oauth_app %} que você gostaria de alterar. +1. Modify the {% data variables.product.prodname_oauth_app %} information that you'd like to change. {% data reusables.user-settings.update_oauth_app %} diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md index c445427bc7..975ec5bafb 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app.md @@ -1,8 +1,8 @@ --- -title: Transferir a propriedade de um aplicativo OAuth +title: Transferring ownership of an OAuth App intro: '{% data reusables.shortdesc.transferring_ownership_of_oauth_apps %}' redirect_from: - - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app/ + - /apps/building-integrations/managing-oauth-apps/transferring-ownership-of-an-oauth-app - /apps/managing-oauth-apps/transferring-ownership-of-an-oauth-app - /developers/apps/transferring-ownership-of-an-oauth-app versions: @@ -12,14 +12,18 @@ versions: ghec: '*' topics: - OAuth Apps -shortTitle: Transferir propriedade +shortTitle: Transfer ownership --- - {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %} -4. Selecione o {% data variables.product.prodname_oauth_app %} que você deseja modificar. ![Seleção de aplicativo](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) -5. Clique em **Transferir propriedade**. ![Botão para transferir a propriedade](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png) -6. Digite o nome do {% data variables.product.prodname_oauth_app %} que você deseja transferir. ![Campo para inserir o nome do aplicativo a ser transferido](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png) -7. Digite o nome do usuário ou organização para o qual você deseja transferir o {% data variables.product.prodname_oauth_app %} . ![Campo para inserir o usuário ou organização para o qual transferir](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png) -8. Clique em **Transferir este aplicativo**. ![Botão para transferir o aplicativo](/assets/images/oauth-apps/oauth_apps_transfer_application.png) +4. Select the {% data variables.product.prodname_oauth_app %} you want to modify. +![App selection](/assets/images/oauth-apps/oauth_apps_choose_app_post2dot12.png) +5. Click **Transfer ownership**. +![Button to transfer ownership](/assets/images/oauth-apps/oauth_apps_transfer_ownership.png) +6. Type the name of the {% data variables.product.prodname_oauth_app %} you want to transfer. +![Field to enter the name of the app to transfer](/assets/images/oauth-apps/oauth_apps_transfer_oauth_name.png) +7. Type the name of the user or organization you want to transfer the {% data variables.product.prodname_oauth_app %} to. +![Field to enter the user or org to transfer to](/assets/images/oauth-apps/oauth_apps_transfer_new_owner.png) +8. Click **Transfer this application**. +![Button to transfer the application](/assets/images/oauth-apps/oauth_apps_transfer_application.png) diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md index 56ed0d61c9..ce44a8e347 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-authorization-request-errors.md @@ -1,8 +1,8 @@ --- -title: Solucionar problemas de erros de solicitação de autorização +title: Troubleshooting authorization request errors intro: '{% data reusables.shortdesc.troubleshooting_authorization_request_errors_oauth_apps %}' redirect_from: - - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors/ + - /apps/building-integrations/managing-oauth-apps/troubleshooting-authorization-request-errors - /apps/managing-oauth-apps/troubleshooting-authorization-request-errors - /developers/apps/troubleshooting-authorization-request-errors versions: @@ -12,38 +12,42 @@ versions: ghec: '*' topics: - GitHub Apps -shortTitle: Solucionar problemas de autorização +shortTitle: Troubleshoot authorization --- +## Application suspended -## Aplicativo suspenso - -Se o aplicativo OAuth que você configurou foi suspenso (em razão de abusos, spam, ou de má utilização da API), o GitHub irá redirecionar para a URL de chamada de retorno registrada, usando os parâmetros a seguir para resumir o erro: +If the OAuth App you set up has been suspended (due to reported abuse, spam, or a mis-use of the API), GitHub will redirect to the registered callback URL using the following parameters to summarize the error: http://your-application.com/callback?error=application_suspended &error_description=Your+application+has+been+suspended.+Contact+support@github.com. &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23application-suspended &state=xyz -Para resolver problemas com aplicativos suspensos, entre em contato com {% data variables.contact.contact_support %}. +To solve issues with suspended applications, please contact {% data variables.contact.contact_support %}. -## Erro no redirecionamento do URI +## Redirect URI mismatch -Se você fornecer um `redirect_uri` que não corresponde ao que você registrou com o seu aplicativo, o GitHub irá redirecionar para a URL de chamada de retorno registrada com os parâmetros a seguir resumindo o erro: +If you provide a `redirect_uri` that doesn't match what you've registered with your application, GitHub will redirect to the registered callback URL with the following parameters summarizing the error: http://your-application.com/callback?error=redirect_uri_mismatch &error_description=The+redirect_uri+MUST+match+the+registered+callback+URL+for+this+application. &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23redirect-uri-mismatch &state=xyz -Para corrigir este erro, ou forneça um `redirect_uri` que corresponda ao que você registrou ou deixe de fora este parâmetro para usar o padrão registrado com o seu aplicativo. +To correct this error, either provide a `redirect_uri` that matches what you registered or leave out this parameter to use the default one registered with your application. -### Acesso Negado +### Access denied -Se o usuário rejeitar o acesso ao seu aplicativo, o GitHub irá redirecionar para a URL de chamada de retorno registrada com os parâmetros a seguir resumindo o erro: +If the user rejects access to your application, GitHub will redirect to +the registered callback URL with the following parameters summarizing +the error: http://your-application.com/callback?error=access_denied &error_description=The+user+has+denied+your+application+access. &error_uri=/apps/building-integrations/setting-up-and-registering-oauth-apps/troubleshooting-authorization-request-errors/%23access-denied &state=xyz -Não há nada que você possa fazer aqui, pois os usuários são livres para escolher não usar seu aplicativo. Frequentemente, os usuários irão apenas apenas fechar a janela ou pressionar "voltar" em seu navegador. Portanto, é provável que você nunca veja esse erro. +There's nothing you can do here as users are free to choose not to use +your application. More often than not, users will just close the window +or press back in their browser, so it is likely that you'll never see +this error. diff --git a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md index 756abda42b..5dc9f10a8b 100644 --- a/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md +++ b/translations/pt-BR/content/developers/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors.md @@ -1,8 +1,8 @@ --- -title: Solucionar problemas de erros na solicitação de token de acesso do OAuth +title: Troubleshooting OAuth App access token request errors intro: '{% data reusables.shortdesc.troubleshooting_access_token_reques_errors_oauth_apps %}' redirect_from: - - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors/ + - /apps/building-integrations/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors - /apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors - /developers/apps/troubleshooting-oauth-app-access-token-request-errors versions: @@ -12,18 +12,18 @@ versions: ghec: '*' topics: - OAuth Apps -shortTitle: Solucionar problemas de solicitação do token +shortTitle: Troubleshoot token request --- - {% note %} -**Observação:** Esses exemplos mostram apenas respostas do JSON. +**Note:** These examples only show JSON responses. {% endnote %} -## Credenciais do cliente incorretas +## Incorrect client credentials -Se o cliente\_id e o cliente\_secret que você inseriu estiverem incorretos, você receberá essa resposta de erro. +If the client\_id and or client\_secret you pass are incorrect you will +receive this error response. ```json { @@ -33,11 +33,12 @@ Se o cliente\_id e o cliente\_secret que você inseriu estiverem incorretos, voc } ``` -Para resolver este erro, verifique se você tem as credenciais corretas para o seu {% data variables.product.prodname_oauth_app %}. Verifique novamente o `client_id` e `client_secret` para certificar-se de que estão corretos e que são informados corretamente para {% data variables.product.product_name %}. +To solve this error, make sure you have the correct credentials for your {% data variables.product.prodname_oauth_app %}. Double check the `client_id` and `client_secret` to make sure they are correct and being passed correctly +to {% data variables.product.product_name %}. -## Erro no redirecionamento do URI +## Redirect URI mismatch -Se você fornecer um `redirect_uri` que não coincide com o que você registrou com o seu {% data variables.product.prodname_oauth_app %}, você receberá esta mensagem de erro: +If you provide a `redirect_uri` that doesn't match what you've registered with your {% data variables.product.prodname_oauth_app %}, you'll receive this error message: ```json { @@ -47,9 +48,11 @@ Se você fornecer um `redirect_uri` que não coincide com o que você registrou } ``` -Para corrigir este erro, forneça um `redirect_uri` que corresponda ao que você registrou ou deixe este parâmetro de fora para usar o padrão registrado com o seu aplicativo. +To correct this error, either provide a `redirect_uri` that matches what +you registered or leave out this parameter to use the default one +registered with your application. -## Código de verificação incorreto +## Bad verification code ```json { @@ -60,7 +63,9 @@ Para corrigir este erro, forneça um `redirect_uri` que corresponda ao que você } ``` -Se o código de verificação que você informou estiver incorreto, expirado, ou não corresponder ao que você recebeu na primeira solicitação de autorização, você receberá este erro. +If the verification code you pass is incorrect, expired, or doesn't +match what you received in the first request for authorization you will +receive this error. ```json { @@ -70,4 +75,5 @@ Se o código de verificação que você informou estiver incorreto, expirado, ou } ``` -Para corrigir este erro, inicie o [processo de autorização do OAuth novamente](/apps/building-oauth-apps/authorizing-oauth-apps/) e obtenha um novo código. +To solve this error, start the [OAuth authorization process again](/apps/building-oauth-apps/authorizing-oauth-apps/) +and get a new code. diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md index ea47b4b45a..4a6292a7c8 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md @@ -2,11 +2,11 @@ title: Requirements for listing an app intro: 'Apps on {% data variables.product.prodname_marketplace %} must meet the requirements outlined on this page before the listing can be published.' redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/ + - /apps/adding-integrations/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace + - /apps/marketplace/listing-apps-on-github-marketplace/requirements-for-listing-an-app-on-github-marketplace + - /apps/marketplace/getting-started-with-github-marketplace-listings/requirements-for-listing-an-app-on-github-marketplace + - /apps/marketplace/creating-and-submitting-your-app-for-approval/requirements-for-listing-an-app-on-github-marketplace + - /apps/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace - /marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace - /developers/github-marketplace/requirements-for-listing-an-app versions: diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md index c098405063..edf1015910 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md @@ -1,63 +1,63 @@ --- -title: Práticas de segurança recomendadas para aplicativos -intro: 'Diretrizes para a preparação de um aplicativo seguro para compartilhar em {% data variables.product.prodname_marketplace %}.' +title: Security best practices for apps +intro: 'Guidelines for preparing a secure app to share on {% data variables.product.prodname_marketplace %}.' redirect_from: - - /apps/marketplace/getting-started/security-review-process/ + - /apps/marketplace/getting-started/security-review-process - /marketplace/getting-started/security-review-process - /developers/github-marketplace/security-review-process-for-submitted-apps - /developers/github-marketplace/security-best-practices-for-apps -shortTitle: Práticas recomendadas de segurança +shortTitle: Security best practice versions: fpt: '*' ghec: '*' topics: - Marketplace --- +If you follow these best practices it will help you to provide a secure user experience. -Se você seguir estas práticas recomendadas, elas ajudarão você a oferecer uma experiência de usuário segura. +## Authorization, authentication, and access control -## Autorização, autenticação e controle de acesso +We recommend creating a GitHub App rather than an OAuth App. {% data reusables.marketplace.github_apps_preferred %}. See "[Differences between GitHub Apps and OAuth Apps](/apps/differences-between-apps/)" for more details. +- Apps should use the principle of least privilege and should only request the OAuth scopes and GitHub App permissions that the app needs to perform its intended functionality. For more information, see [Principle of least privilege](https://en.wikipedia.org/wiki/Principle_of_least_privilege) in Wikipedia. +- Apps should provide customers with a way to delete their account, without having to email or call a support person. +- Apps should not share tokens between different implementations of the app. For example, a desktop app should have a separate token from a web-based app. Individual tokens allow each app to request the access needed for GitHub resources separately. +- Design your app with different user roles, depending on the functionality needed by each type of user. For example, a standard user should not have access to admin functionality, and billing managers might not need push access to repository code. +- Apps should not share service accounts such as email or database services to manage your SaaS service. +- All services used in your app should have unique login and password credentials. +- Admin privilege access to the production hosting infrastructure should only be given to engineers and employees with administrative duties. +- Apps should not use personal access tokens to authenticate and should authenticate as an [OAuth App](/apps/about-apps/#about-oauth-apps) or a [GitHub App](/apps/about-apps/#about-github-apps): + - OAuth Apps should authenticate using an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/). + - GitHub Apps should authenticate using either a [JSON Web Token (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app), [OAuth token](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/), or [installation access token](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). -Recomendamos criar um aplicativo GitHub em vez de um aplicativo OAuth. {% data reusables.marketplace.github_apps_preferred %}. Consulte "[Diferenças entre os aplicativos GitHub e os aplicativos OAuth](/apps/differences-between-apps/)" para obter mais informações. -- Os aplicativos devem usar o princípio do menor privilégio e devem solicitar apenas os escopos do OAuth e as permissões do aplicativo GitHub de que o aplicativo precisa para realizar suas funcionalidades pretendidas. Para obter mais informações, consulte [O princípio do menor privilégio](https://en.wikipedia.org/wiki/Principle_of_least_privilege) na Wikipédia. -- Os aplicativos devem fornecer aos clientes uma forma de excluir sua conta, sem ter de enviar um e-mail ou ligar para uma pessoa de suporte. -- Os aplicativos não devem compartilhar tokens entre diferentes implementações do aplicativo. Por exemplo, um aplicativo para computador deve ter um token separado de um aplicativo baseado na web. Os tokens individuais permitem que cada aplicativo solicite o acesso necessário aos recursos do GitHub separadamente. -- Crie seu aplicativo com diferentes funções de usuário, dependendo da funcionalidade necessária para cada tipo de usuário. Por exemplo, um usuário-padrão não deve ter acesso à funcionalidade de administração, e os gerentes de cobrança podem não precisar de acesso push ao código de repositório. -- Os aplicativos não devem compartilhar contas de serviço como, por exemplo, e-mail ou serviços de banco de dados para gerenciar seu serviço de SaaS. -- Todos os serviços usados no seu aplicativo devem ter credenciais de login e senha exclusivas. -- O acesso privilegiado de administrador à infraestrutura de hospedagem de produção deve ser concedido apenas a engenheiros e funcionários com funções administrativas. -- Os aplicativos não devem usar tokens de acesso pessoal para efetuar a autenticação e devem autenticar-se como um [aplicativo OAuth](/apps/about-apps/#about-oauth-apps) ou um [aplicativo GitHub](/apps/about-apps/#about-github-apps): - - Os aplicativos OAuth devem efetuar a autenticação usando um [token do OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/). - - Os aplicativos GitHub devem efetuar a autenticação usando um [Token web do JSON (JWT)](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-a-github-app),, [Token do OAuth](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) ou um [token de acesso à instalação](/apps/building-github-apps/authenticating-with-github-apps/#authenticating-as-an-installation). +## Data protection -## Proteção de dados +- Apps should encrypt data transferred over the public internet using HTTPS, with a valid TLS certificate, or SSH for Git. +- Apps should store client ID and client secret keys securely. We recommend storing them as [environmental variables](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). +- Apps should delete all GitHub user data within 30 days of receiving a request from the user, or within 30 days of the end of the user's legal relationship with GitHub. +- Apps should not require the user to provide their GitHub password. +- Apps should encrypt tokens, client IDs, and client secrets. -- Os aplicativos devem criptografar dados transferidos para internet pública usando HTTPS, com um certificado TLS válido ou SSH para o Git. -- Os aplicativos devem armazenar com segurança o ID do cliente e as chaves secretas do cliente. Recomendamos armazená-las como [variáveis de ambiente](http://en.wikipedia.org/wiki/Environment_variable#Getting_and_setting_environment_variables). -- Os aplicativos devem excluir todos os dados do usuário no prazo de 30 dias após receber uma solicitação do usuário ou dentro de 30 dias após o fim da relação jurídica do usuário com o GitHub. -- Aplicativos não devem exigir que o usuário forneça sua senha do GitHub. -- Os aplicativos devem criptografar tokens, IDs de clientes e segredos de clientes. +## Logging and monitoring -## Registro e monitoramento +Apps should have logging and monitoring capabilities. App logs should be retained for at least 30 days and archived for at least one year. +A security log should include: -Os aplicativos devem ter capacidade de registro e monitoramento. Os registros dos aplicativos devem ser mantidos pelo menos 30 dias e arquivados pelo menos um ano. Um log de segurança deve incluir: +- Authentication and authorization events +- Service configuration changes +- Object reads and writes +- All user and group permission changes +- Elevation of role to admin +- Consistent timestamping for each event +- Source users, IP addresses, and/or hostnames for all logged actions -- Eventos de autenticação e autorização -- Alterações na configuração do serviço -- Leitura e gravação de objetos -- Todas as alterações de permissão do usuário e de grupo -- Elevação do papel para administrador -- Marca de tempo consistente para cada evento -- Usuários de origem, endereços IP e/ou nomes de host para todas as ações registradas +## Incident response workflow -## Fluxo de trabalho de resposta a incidente +To provide a secure experience for users, you should have a clear incident response plan in place before listing your app. We recommend having a security and operations incident response team in your company rather than using a third-party vendor. You should have the capability to notify {% data variables.product.product_name %} within 24 hours of a confirmed incident. -Para oferecer uma experiência segura aos usuários, você deve ter um plano de resposta de incidente claro em vigor antes de anunciar o seu aplicativo. Recomendamos ter uma equipe de resposta a incidentes de segurança e operações na sua empresa, em vez de usar um fornecedor terceiro. Você deve ter a capacidade de notificar {% data variables.product.product_name %} no prazo de 24 horas após a confirmação de um incidente. +For an example of an incident response workflow, see the "Data Breach Response Policy" on the [SANS Institute website](https://www.sans.org/information-security-policy/). A short document with clear steps to take in the event of an incident is more valuable than a lengthy policy template. -Para obter um exemplo de um fluxo de trabalho de resposta de incidente, consulte a "Política de Resposta de Violação de Dados" no [site do Instituto SANS](https://www.sans.org/information-security-policy/). Um documento breve com medidas claras a serem tomadas em caso de incidente é mais valioso do que um modelo político moroso. +## Vulnerability management and patching workflow -## Gerenciamento de vulnerabilidades e fluxo de trabalho de patch +You should conduct regular vulnerability scans of production infrastructure. You should triage the results of vulnerability scans and define a period of time in which you agree to remediate the vulnerability. -Você deveria realizar varreduras regulares de vulnerabilidades de infraestrutura de produção. Você deve classificar os resultados de verificações de vulnerabilidades e definir um período de tempo no qual você concorda em remediar a vulnerabilidade. - -Se você não estiver pronto para criar um programa completo de gerenciamento de vulnerabilidades, é importante começar criando um processo de patching. Para obter orientações sobre a criação de uma política de gerenciamento de correções, consulte este artigo da TechRepublic "[Estabeleça uma política de gerenciamento de patch](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)". +If you are not ready to set up a full vulnerability management program, it's useful to start by creating a patching process. For guidance in creating a patch management policy, see this TechRepublic article "[Establish a patch management policy](https://www.techrepublic.com/blog/it-security/establish-a-patch-management-policy-87756/)." diff --git a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md index 489c20a421..1faccc7c50 100644 --- a/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/creating-apps-for-github-marketplace/viewing-metrics-for-your-listing.md @@ -1,10 +1,10 @@ --- -title: Visualizar métricas para a sua listagem -intro: 'A página de Insights do {% data variables.product.prodname_marketplace %} exibe métricas para o seu {% data variables.product.prodname_github_app %}. Você pode usar as métricas para acompanhar o desempenho do seu {% data variables.product.prodname_github_app %} e tomar decisões mais informadas sobre os preços, planos, testes grátis, bem como visualizar os efeitos das campanhas de marketing.' +title: Viewing metrics for your listing +intro: 'The {% data variables.product.prodname_marketplace %} Insights page displays metrics for your {% data variables.product.prodname_github_app %}. You can use the metrics to track your {% data variables.product.prodname_github_app %}''s performance and make more informed decisions about pricing, plans, free trials, and how to visualize the effects of marketing campaigns.' redirect_from: - - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing/ - - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing/ - - /apps/marketplace/github-marketplace-insights/ + - /apps/marketplace/managing-github-marketplace-listings/viewing-performance-metrics-for-a-github-marketplace-listing + - /apps/marketplace/viewing-performance-metrics-for-a-github-marketplace-listing + - /apps/marketplace/github-marketplace-insights - /marketplace/github-marketplace-insights - /developers/github-marketplace/viewing-metrics-for-your-listing versions: @@ -12,45 +12,45 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Visualizar métricas de anúncio +shortTitle: View listing metrics --- - -Você pode visualizar as métricas do último dia (24 horas), semana, mês ou referente a todo o tempo em que seu {% data variables.product.prodname_github_app %} foi listada. +You can view metrics for the past day (24 hours), week, month, or for the entire duration of time that your {% data variables.product.prodname_github_app %} has been listed. {% note %} -**Observação:** Como leva tempo para agregar dados, você notará um pequeno atraso nas datas exibidas. Ao selecionar um período de tempo, você poderá ver datas exatas para as métricas no topo da página. +**Note:** Because it takes time to aggregate data, you'll notice a slight delay in the dates shown. When you select a time period, you can see exact dates for the metrics at the top of the page. {% endnote %} -## Métricas de desempenho +## Performance metrics -A página de Insights exibe essas métricas de desempenho para o período de tempo selecionado: +The Insights page displays these performance metrics, for the selected time period: -* **Valor da assinatura:** Receita total possível (em dólar) para assinaturas. Esse valor representa a receita possível, caso nenhum plano ou teste grátis seja cancelado e todas as transações de crédito forem bem sucedidas. O valor da assinatura inclui o valor integral dos planos que começam com um teste grátis no período de tempo selecionado, mesmo quando não há transações financeiras nesse período. O valor da assinatura também inclui o valor total dos planos atualizados no período de tempo selecionado, mas não inclui a quantia rateada. Para visualizar e fazer o download das transações individuais, consulte "[Transações do GitHub Marketplace](/marketplace/github-marketplace-transactions/)". -* **Visitantes:** Número de pessoas que visualizaram uma página na sua listagem de aplicativos GitHub. Este número inclui tanto visitantes conectados quanto desconectados. -* **Visualizações de página:** Número de páginas recebidas na listagem do seu aplicativo GitHub. Um único visitante pode gerar mais de uma exibição de página. +* **Subscription value:** Total possible revenue (in US dollars) for subscriptions. This value represents the possible revenue if no plans or free trials are cancelled and all credit transactions are successful. The subscription value includes the full value for plans that begin with a free trial in the selected time period, even when there are no financial transactions in that time period. The subscription value also includes the full value of upgraded plans in the selected time period but does not include the prorated amount. To see and download individual transactions, see "[GitHub Marketplace transactions](/marketplace/github-marketplace-transactions/)." +* **Visitors:** Number of people that have viewed a page in your GitHub Apps listing. This number includes both logged in and logged out visitors. +* **Pageviews:** Number of views the pages in your GitHub App's listing received. A single visitor can generate more than one pageview. {% note %} -**Observação:** Seu valor de assinatura estimado pode ser muito maior que as transações processadas para este período. +**Note:** Your estimated subscription value could be much higher than the transactions processed for this period. {% endnote %} -### Desempenho de conversão +### Conversion performance -* **Visitantes únicos da página de destino:** Número de pessoas que visualizaram a página inicial do seu aplicativo GitHub. -* **Visitantes únicos para a página de checkout:** Número de pessoas que visualizaram uma das páginas de checkout do seu aplicativo GitHub. -* **Página de checkout para novas assinaturas:** Número total de assinaturas pagas, testes grátis e assinaturas grátis. Veja o detalhamento de assinaturas totais para obter para o número específico de cada tipo de assinatura. +* **Unique visitors to landing page:** Number of people who viewed your GitHub App's landing page. +* **Unique visitors to checkout page:** Number of people who viewed one of your GitHub App's checkout pages. +* **Checkout page to new subscriptions:** Total number of paid subscriptions, free trials, and free subscriptions. See the "Breakdown of total subscriptions" for the specific number of each type of subscription. -![Perspectivas do Marketplace](/assets/images/marketplace/marketplace_insights.png) +![Marketplace insights](/assets/images/marketplace/marketplace_insights.png) -Para acessar as perspectivas do {% data variables.product.prodname_marketplace %}: +To access {% data variables.product.prodname_marketplace %} Insights: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.marketplace_apps %} -4. Selecione o {% data variables.product.prodname_github_app %} para o qual você gostaria de ver perspectivas. +4. Select the {% data variables.product.prodname_github_app %} that you'd like to view Insights for. {% data reusables.user-settings.edit_marketplace_listing %} -6. Clique na aba **Perspectivas**. -7. Opcionalmente, selecione um período de tempo diferente, clicando no menu suspenso Período, no canto superior direito da página de Insights. ![Período de tempo do Marketplace](/assets/images/marketplace/marketplace_insights_time_period.png) +6. Click the **Insights** tab. +7. Optionally, select a different time period by clicking the Period dropdown in the upper-right corner of the Insights page. +![Marketplace time period](/assets/images/marketplace/marketplace_insights_time_period.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md index 9b9bc6f646..7370b55b41 100644 --- a/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md +++ b/translations/pt-BR/content/developers/github-marketplace/github-marketplace-overview/about-github-marketplace.md @@ -2,7 +2,7 @@ title: About GitHub Marketplace intro: 'Learn about {% data variables.product.prodname_marketplace %} where you can share your apps and actions publicly with all {% data variables.product.product_name %} users.' redirect_from: - - /apps/marketplace/getting-started/ + - /apps/marketplace/getting-started - /marketplace/getting-started - /developers/github-marketplace/about-github-marketplace versions: diff --git a/translations/pt-BR/content/developers/github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/index.md index d90afad630..7bfbc295fd 100644 --- a/translations/pt-BR/content/developers/github-marketplace/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/index.md @@ -1,9 +1,9 @@ --- title: GitHub Marketplace -intro: 'Liste suas ferramentas no Markeplace do {% data variables.product.prodname_dotcom %} para os desenvolvedores usarem ou comprarem.' +intro: 'List your tools in {% data variables.product.prodname_dotcom %} Marketplace for developers to use or purchase.' redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace/ - - /apps/marketplace/ + - /apps/adding-integrations/listing-apps-on-github-marketplace/about-github-marketplace + - /apps/marketplace - /marketplace versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md index 509710380f..d1b387eead 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes.md @@ -1,11 +1,11 @@ --- -title: Configurar um webhook para notificá-lo de alterações de plano -intro: 'Após [criar um rascunho da listagem do {% data variables.product.prodname_marketplace %} ](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), você pode configurar um webhook que notifica você quando ocorrem alterações nos planos da conta do cliente. Após configurar o webhook, você pode [gerenciar os tipos de evento `marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) no seu aplicativo.' +title: Configuring a webhook to notify you of plan changes +intro: 'After [creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/), you can configure a webhook that notifies you when changes to customer account plans occur. After you configure the webhook, you can [handle the `marketplace_purchase` event types](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) in your app.' redirect_from: - - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing/ - - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing/ - - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing/ - - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/ + - /apps/adding-integrations/managing-listings-on-github-marketplace/adding-webhooks-for-a-github-marketplace-listing + - /apps/marketplace/managing-github-marketplace-listings/adding-webhooks-for-a-github-marketplace-listing + - /apps/marketplace/setting-up-github-marketplace-webhooks/creating-a-webhook-for-a-github-marketplace-listing + - /apps/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook - /marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook - /developers/github-marketplace/configuring-a-webhook-to-notify-you-of-plan-changes versions: @@ -13,33 +13,32 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Webhooks para mudanças de plano +shortTitle: Webhooks for plan changes --- +The {% data variables.product.prodname_marketplace %} event webhook can only be set up from your application's {% data variables.product.prodname_marketplace %} listing page. You can configure all other events from your [application's developer settings page](https://github.com/settings/developers). If you haven't created a {% data variables.product.prodname_marketplace %} listing, read "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" to learn how. -O evento do webhook do {% data variables.product.prodname_marketplace %} só pode ser configurado a partir da página de listagem {% data variables.product.prodname_marketplace %} do seu aplicativo. Você pode configurar todos os outros eventos a partir da [página de configurações de desenvolvedor do seu aplicativo](https://github.com/settings/developers). Se você não criou uma listagem do {% data variables.product.prodname_marketplace %}, leia "[Criando um rascunho da listagem {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)" para aprender como fazê-lo. +## Creating a webhook -## Criar um webhook +To create a webhook for your {% data variables.product.prodname_marketplace %} listing, click **Webhook** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). You'll see the following webhook configuration options needed to configure your webhook: -Para criar um webhook para sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Webhook** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Você verá as seguintes opções de configuração de webhook necessárias para configurar seu webhook: - -### URL de carga +### Payload URL {% data reusables.webhooks.payload_url %} -### Tipo de conteúdo +### Content type -{% data reusables.webhooks.content_type %} O GitHub recomenda usar o tipo de conteúdo `application/json`. +{% data reusables.webhooks.content_type %} GitHub recommends using the `application/json` content type. -### Segredo +### Secret {% data reusables.webhooks.secret %} -### Ativo +### Active -Por padrão, as entregas de webhook estão "Ativas". Você pode optar por desativar a entrega das cargas de webhook durante o desenvolvimento, desmarcando "Ativo". Se você desativou as entregas do webhook, será necessário selecionar "Ativo" antes de enviar seu aplicativo para revisão. +By default, webhook deliveries are "Active." You can choose to disable the delivery of webhook payloads during development by deselecting "Active." If you've disabled webhook deliveries, you will need to select "Active" before you submit your app for review. -## Visualizar entregas do webhook +## Viewing webhook deliveries -Uma vez configurado seu webhook do {% data variables.product.prodname_marketplace %} , você poderá inspecionar as cargas de solicitação de `POST` da página do **Webhook** da lista do seu aplicativo do [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). O GitHub não reenvia tentativas falhas de entrega. Certifique-se de que seu aplicativo possa receber todas as cargas do webhook enviadas pelo GitHub. +Once you've configured your {% data variables.product.prodname_marketplace %} webhook, you'll be able to inspect `POST` request payloads from the **Webhook** page of your application's [{% data variables.product.prodname_marketplace %} listing](https://github.com/marketplace/manage). GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub. -![Inspecione as entregas recentes do webhook de {% data variables.product.prodname_marketplace %}](/assets/images/marketplace/marketplace_webhook_deliveries.png) +![Inspect recent {% data variables.product.prodname_marketplace %} webhook deliveries](/assets/images/marketplace/marketplace_webhook_deliveries.png) diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md index c38398e5ea..9dd64a8959 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app.md @@ -1,16 +1,16 @@ --- -title: Elaborar uma listagem para o seu aplicativo -intro: 'Ao criar uma listagem do {% data variables.product.prodname_marketplace %}, o GitHub salva-na no modo rascunho até que você envie o aplicativo para aprovação. Sua listagem mostra aos clientes como podem usar seu aplicativo.' +title: Drafting a listing for your app +intro: 'When you create a {% data variables.product.prodname_marketplace %} listing, GitHub saves it in draft mode until you submit the app for approval. Your listing shows customers how they can use your app.' redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace/ - - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing/ - - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing/ - - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/ + - /apps/adding-integrations/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace + - /apps/marketplace/listing-apps-on-github-marketplace/listing-an-app-on-github-marketplace + - /apps/marketplace/getting-started-with-github-marketplace-listings/listing-an-app-on-github-marketplace + - /apps/marketplace/creating-and-submitting-your-app-for-approval/listing-an-app-on-github-marketplace + - /apps/adding-integrations/managing-listings-on-github-marketplace/removing-a-listing-from-github-marketplace + - /apps/marketplace/managing-github-marketplace-listings/removing-a-listing-from-github-marketplace + - /apps/adding-integrations/managing-listings-on-github-marketplace/editing-a-github-marketplace-listing + - /apps/marketplace/managing-github-marketplace-listings/editing-a-github-marketplace-listing + - /apps/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing - /marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing - /developers/github-marketplace/drafting-a-listing-for-your-app versions: @@ -18,50 +18,51 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Elabore um anúncio para aplicativos +shortTitle: Draft an app listing --- +## Create a new draft {% data variables.product.prodname_marketplace %} listing -## Crie um novo rascunho da listagem do {% data variables.product.prodname_marketplace %} +You can only create draft listings for apps that are public. Before creating your draft listing, you can read the following guidelines for writing and configuring settings in your {% data variables.product.prodname_marketplace %} listing: -Você só pode criar rascunhos de listagem para aplicativos públicos. Antes de criar o seu rascunho de listagem, você pode ler as diretrizes a seguir para escrever e definir configurações na sua listagem do {% data variables.product.prodname_marketplace %}: +* [Writing {% data variables.product.prodname_marketplace %} listing descriptions](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) +* [Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) +* [Configuring the {% data variables.product.prodname_marketplace %} Webhook](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) -* [Escrever descrições de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/) -* [Definir um plano de preços do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/) -* [Configurar o Webhook do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/configuring-the-github-marketplace-webhook/) - -Para criar uma listagem do {% data variables.product.prodname_marketplace %}: +To create a {% data variables.product.prodname_marketplace %} listing: {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} -3. Na barra lateral esquerda, clique em **Aplicativos OAuth** ou **Aplicativos GitHub**, dependendo do aplicativo que você está adicionando ao {% data variables.product.prodname_marketplace %}. +3. In the left sidebar, click either **OAuth Apps** or **GitHub Apps** depending on the app you're adding to {% data variables.product.prodname_marketplace %}. {% note %} - **Observação**: Você também pode adicionar uma listagem acessando https://github.com/marketplace/new, visualizando seus aplicativos disponíveis e clicando em **Criar rascunho de listagem**. + **Note**: You can also add a listing by navigating to https://github.com/marketplace/new, viewing your available apps, and clicking **Create draft listing**. {% endnote %} - ![Seleção do tipo de aplicativo](/assets/images/settings/apps_choose_app.png) + ![App type selection](/assets/images/settings/apps_choose_app.png) -4. Selecione o aplicativo que você gostaria de adicionar ao {% data variables.product.prodname_marketplace %}. ![Seleção de aplicativo para listagem do {% data variables.product.prodname_marketplace %}](/assets/images/github-apps/github_apps_select-app.png) +4. Select the app you'd like to add to {% data variables.product.prodname_marketplace %}. +![App selection for {% data variables.product.prodname_marketplace %} listing](/assets/images/github-apps/github_apps_select-app.png) {% data reusables.user-settings.edit_marketplace_listing %} -5. Uma vez criado um novo rascunho da listagem, você verá um resumo das seções que você precisará visitar antes da sua listagem do {% data variables.product.prodname_marketplace %} ser concluída. ![Listagem do GitHub Marketplace](/assets/images/marketplace/marketplace_listing_overview.png) +5. Once you've created a new draft listing, you'll see an overview of the sections that you'll need to visit before your {% data variables.product.prodname_marketplace %} listing will be complete. +![GitHub Marketplace listing](/assets/images/marketplace/marketplace_listing_overview.png) {% note %} -**Observação:** Na seção "Informações de contato" da sua listagem, recomendamos o uso de endereços de e-mail individuais, em vez de agrupar endereços de e-mail como, por exemplo, support@domain.com. O GitHub usará estes endereços de e-mail para entrar em contato com você sobre atualizações do {% data variables.product.prodname_marketplace %} que podem afetar a sua listagem, novas versões de recurso, oportunidades de marketing, pagamentos e informações sobre conferências e patrocínios. +**Note:** In the "Contact info" section of your listing, we recommend using individual email addresses, rather than group emails addresses like support@domain.com. GitHub will use these email addresses to contact you about updates to {% data variables.product.prodname_marketplace %} that might affect your listing, new feature releases, marketing opportunities, payouts, and information on conferences and sponsorships. {% endnote %} -## Editar sua listagem +## Editing your listing -Após criar um rascunho da listagem do {% data variables.product.prodname_marketplace %}, você poderá voltar e modificar as informações na sua listagem a qualquer momento. Se o seu aplicativo já está aprovado e encontra-se no {% data variables.product.prodname_marketplace %}, você pode editar as informações e imagens na sua listagem, mas você não poderá alterar os planos de preços existentes publicados. Consulte "[Configurando um plano de preços de listagem do {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/). " +Once you've created a {% data variables.product.prodname_marketplace %} draft listing, you can come back to modify information in your listing anytime. If your app is already approved and in {% data variables.product.prodname_marketplace %}, you can edit the information and images in your listing, but you will not be able to change existing published pricing plans. See "[Setting a {% data variables.product.prodname_marketplace %} listing's pricing plan](/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/)." -## Enviar o seu aplicativo +## Submitting your app -Após concluir a sua listagem do {% data variables.product.prodname_marketplace %}, você poderá enviá-la para revisão na página **Visão geral**. Você vai precisar ler e aceitar o "[{% data variables.product.prodname_marketplace %} Contrato de desenvolvedor](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)" e, em seguida, você poderá clicar em **Enviar para revisão**. Depois de enviar seu aplicativo para análise, um especialista em integração entrará em contato com você com informações adicionais sobre o processo de integração. +Once you've completed your {% data variables.product.prodname_marketplace %} listing, you can submit your listing for review from the **Overview** page. You'll need to read and accept the "[{% data variables.product.prodname_marketplace %} Developer Agreement](/free-pro-team@latest/github/site-policy/github-marketplace-developer-agreement/)," and then you can click **Submit for review**. After you submit your app for review, an onboarding expert will contact you with additional information about the onboarding process. -## Remover uma listagem do {% data variables.product.prodname_marketplace %} +## Removing a {% data variables.product.prodname_marketplace %} listing -Se você não quiser mais listar seu aplicativo em {% data variables.product.prodname_marketplace %}, entre em contato {% data variables.contact.contact_support %} para remover o seu anúncio. +If you no longer want to list your app in {% data variables.product.prodname_marketplace %}, contact {% data variables.contact.contact_support %} to remove your listing. diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md index 89bfdcb00a..c587c34a71 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/index.md @@ -1,14 +1,14 @@ --- -title: Listar um aplicativo no GitHub Marketplace -intro: 'Saiba mais sobre requisitos e práticas recomendadas para listar seu app no {% data variables.product.prodname_marketplace %}.' +title: Listing an app on GitHub Marketplace +intro: 'Learn about requirements and best practices for listing your app on {% data variables.product.prodname_marketplace %}.' redirect_from: - - /apps/adding-integrations/listing-apps-on-github-marketplace/ - - /apps/marketplace/listing-apps-on-github-marketplace/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/ - - /apps/adding-integrations/managing-listings-on-github-marketplace/ - - /apps/marketplace/managing-github-marketplace-listings/ - - /apps/marketplace/listing-on-github-marketplace/ + - /apps/adding-integrations/listing-apps-on-github-marketplace + - /apps/marketplace/listing-apps-on-github-marketplace + - /apps/marketplace/getting-started-with-github-marketplace-listings + - /apps/marketplace/creating-and-submitting-your-app-for-approval + - /apps/adding-integrations/managing-listings-on-github-marketplace + - /apps/marketplace/managing-github-marketplace-listings + - /apps/marketplace/listing-on-github-marketplace - /marketplace/listing-on-github-marketplace versions: fpt: '*' @@ -21,6 +21,6 @@ children: - /setting-pricing-plans-for-your-listing - /configuring-a-webhook-to-notify-you-of-plan-changes - /submitting-your-listing-for-publication -shortTitle: Anuncie um aplicativo no Marketplace +shortTitle: List an app on the Marketplace --- diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md index 7a41d361d5..ffdba1e720 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing.md @@ -1,17 +1,17 @@ --- -title: Definir planos de cobrança para sua listagem -intro: 'Quando você listar seu aplicativo em {% data variables.product.prodname_marketplace %}, você poderá escolher fornecer seu aplicativo como um serviço grátis ou vender seu aplicativo. Se você pretende vender seu aplicativo, você pode criar planos de preços diferentes para diferentes níveis de recursos.' +title: Setting pricing plans for your listing +intro: 'When you list your app on {% data variables.product.prodname_marketplace %}, you can choose to provide your app as a free service or sell your app. If you plan to sell your app, you can create different pricing plans for different feature tiers.' redirect_from: - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans/ - - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan/ - - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan/ + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/setting-a-github-marketplace-listing-s-pricing-plan + - /apps/marketplace/pricing-payments-and-free-trials/setting-a-github-marketplace-listing-s-pricing-plan + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/about-github-marketplace-pricing-plans + - /apps/marketplace/pricing-payments-and-free-trials/about-github-marketplace-pricing-plans + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/changing-a-github-marketplace-listing-s-pricing-plan + - /apps/marketplace/managing-github-marketplace-listings/changing-a-github-marketplace-listing-s-pricing-plan + - /apps/marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan - /marketplace/listing-on-github-marketplace/setting-a-github-marketplace-listing-s-pricing-plan - /developers/github-marketplace/setting-pricing-plans-for-your-listing versions: @@ -19,70 +19,69 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Definir os planos de preços do anúncio +shortTitle: Set listing pricing plans --- +## About setting pricing plans -## Sobre a configuração dos planos de preços +{% data variables.product.prodname_marketplace %} offers several different types of pricing plans. For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)." -{% data variables.product.prodname_marketplace %} oferece vários tipos diferentes de planos de preços. Para obter informações detalhadas, consulte "[Planos de preços para {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)". +To offer a paid plan for your app, your app must be owned by an organization that has completed the publisher verification process and met certain criteria. For more information, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" and "[Requirements for listing an app on {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)." -Para oferecer um plano pago para seu aplicativo, este deve ser pertencente a uma organização que tenha concluído o processo de verificação de editor e atendido a certos critérios. Para obter mais informações, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)" e "[Requisitos para listar um aplicativo em {% data variables.product.prodname_marketplace %}](/marketplace/getting-started/requirements-for-listing-an-app-on-github-marketplace/)". +If your app is already published with a paid plan and you're a verified publisher, then you can publish a new paid plan from the "Edit a pricing plan" page in your Marketplace app listing settings. -Se seu aplicativo já foi publicado com um plano pago e você é um editor verificado, você poderá publicar um novo plano pago a partir da página "Editar um plano de preços" nas configurações da listagem do seu aplicativo do Marketplace. +![Publish this plan button](/assets/images/marketplace/publish-this-plan-button.png) -![Botão Publicar este plano](/assets/images/marketplace/publish-this-plan-button.png) +If your app is already published with a paid plan and but you are not a verified publisher, then you can cannot publish a new paid plan until you are a verified publisher. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." -Se seu aplicativo já foi publicado com um plano pago, mas você não é um editor verificado, você não poderá publicar um novo plano pago até que um editor seja verificado. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +## About saving pricing plans -## Sobre como salvar planos de preços +You can save pricing plans in a draft or published state. If you haven't submitted your {% data variables.product.prodname_marketplace %} listing for approval, a published plan will function in the same way as a draft plan until your listing is approved and shown on {% data variables.product.prodname_marketplace %}. Draft plans allow you to create and save new pricing plans without making them available on your {% data variables.product.prodname_marketplace %} listing page. Once you publish a pricing plan on a published listing, it's available for customers to purchase immediately. You can publish up to 10 pricing plans. -Você pode salvar planos de preços com status de rascunho ou publicado. Se você não enviou seu anúncio de {% data variables.product.prodname_marketplace %} para aprovação, um plano publicado funcionará da mesma forma que um plano provisório até que o seu anúncio seja aprovado e exibido em {% data variables.product.prodname_marketplace %}. Os planos de rascunho permitem criar e salvar novos planos de preços sem torná-los disponíveis na sua página de anúncio de {% data variables.product.prodname_marketplace %}. Depois de publicar um plano de preços em um anúncio publicado, os clientes poderão comprar imediatamente. Você pode publicar até 10 planos de preços. +For guidelines on billing customers, see "[Billing customers](/developers/github-marketplace/billing-customers)." -Para obter diretrizes sobre os clientes de cobrança, consulte "[Clientes de cobrança](/developers/github-marketplace/billing-customers)". +## Creating pricing plans -## Criar planos de preços +To create a pricing plan for your {% data variables.product.prodname_marketplace %} listing, click **Plans and pricing** in the left sidebar of your [{% data variables.product.prodname_marketplace %} listing page](https://github.com/marketplace/manage). For more information, see "[Creating a draft {% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." -Para criar um plano de preços para a sua listagem do {% data variables.product.prodname_marketplace %}, clique em **Planos e preços** na barra lateral esquerda da sua [página de listagem do {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/manage). Para obter mais informações, consulte "[Criar um rascunho de anúncio de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/creating-a-draft-github-marketplace-listing/)." +When you click **New draft plan**, you'll see a form that allows you to customize your pricing plan. You'll need to configure the following fields to create a pricing plan: -Ao clicar em **Novo rascunho do plano**, você verá um formulário que permite que você personalize o seu plano de preços. Você precisará configurar os seguintes campos para criar um plano de preços: +- **Plan name** - Your pricing plan's name will appear on your {% data variables.product.prodname_marketplace %} app's landing page. You can customize the name of your pricing plan to align with the plan's resources, the size of the company that will use the plan, or anything you'd like. -- **Nome do plano** - O nome do seu plano de preços aparecerá na página inicial do aplicativo de {% data variables.product.prodname_marketplace %}. Você pode personalizar o nome do seu plano de preços para se alinhar com os recursos do plano, o tamanho da empresa que usará o plano ou qualquer coisa que desejar. +- **Pricing models** - There are three types of pricing plan: free, flat-rate, and per-unit. All plans require you to process new purchase and cancellation events from the marketplace API. In addition, for paid plans: -- **Modelos de preços** - Existem três tipos de plano de preços: gratuito, taxa fixa e por unidade. Todos os planos exigem que você processe novos eventos de compra e cancelamento da API do marketplace. Além disso, para os planos pagos: - - - Você deve definir um preço para as assinaturas mensais e anuais em dólar. - - Seu aplicativo deve processar eventos de mudança de plano. - - Você deve solicitar verificação para publicar um anúncio com um plano pago. + - You must set a price for both monthly and yearly subscriptions in US dollars. + - Your app must process plan change events. + - You must request verification to publish a listing with a paid plan. - {% data reusables.marketplace.marketplace-pricing-free-trials %} - Para obter informações detalhadas, consulte "[Planos de preços para aplicativos de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" e "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". + For detailed information, see "[Pricing plans for {% data variables.product.prodname_marketplace %} apps](/developers/github-marketplace/pricing-plans-for-github-marketplace-apps)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -- **Disponível para** - planos de preços de {% data variables.product.prodname_marketplace %} podem ser aplicados a **Contas pessoais e da organização**, **apenas contas pessoais**ou **apenas contas de organização**. Por exemplo, se o seu plano de preços for por unidade e fornecer várias estações, você selecionaria **apenas contas de organização**, porque não há nenhuma maneira de atribuir estações a pessoas de uma organização a partir de uma conta pessoal. +- **Available for** - {% data variables.product.prodname_marketplace %} pricing plans can apply to **Personal and organization accounts**, **Personal accounts only**, or **Organization accounts only**. For example, if your pricing plan is per-unit and provides multiple seats, you would select **Organization accounts only** because there is no way to assign seats to people in an organization from a personal account. -- **Breve descrição** - Escreva um breve resumo dos detalhes do plano de preços. A descrição pode incluir o tipo de cliente para o qual o plano se destina ou os recursos que o plano inclui. +- **Short description** - Write a brief summary of the details of the pricing plan. The description might include the type of customer the plan is intended for or the resources the plan includes. -- **Marcadores** - Você pode escrever até quatro marcadores que incluem mais detalhes sobre o seu plano de precificação. Os marcadores podem incluir casos de uso do seu aplicativo ou listar informações mais detalhadas sobre as características ou os recursos incluídos no plano. +- **Bullets** - You can write up to four bullets that include more details about your pricing plan. The bullets might include the use cases of your app or list more detailed information about the resources or features included in the plan. {% data reusables.marketplace.free-plan-note %} -## Alterar um plano de preços da listagem do {% data variables.product.prodname_marketplace %} +## Changing a {% data variables.product.prodname_marketplace %} listing's pricing plan -Se um plano de preços para o seu anúncio de {% data variables.product.prodname_marketplace %} não for mais necessário, ou se você precisar ajustar os detalhes de preços, você poderá removê-lo. +If a pricing plan for your {% data variables.product.prodname_marketplace %} listing is no longer needed, or if you need to adjust pricing details, you can remove it. -![Botão para remover o seu plano de preços](/assets/images/marketplace/marketplace_remove_this_plan.png) +![Button to remove your pricing plan](/assets/images/marketplace/marketplace_remove_this_plan.png) -Depois de publicar um plano de preços para um aplicativo que já está listado em {% data variables.product.prodname_marketplace %}, você não poderá fazer alterações no plano. Em vez disso, você precisará remover o plano de preços e criar um novo plano. Os clientes que já compraram o plano de preços removido continuarão a usá-lo até que optem por sair o plano e passar para um novo plano de preços. Para obter mais informações sobre os planos de preços, consulte[ planos de preços do {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/github-marketplace-pricing-plans/)". +Once you publish a pricing plan for an app that is already listed in {% data variables.product.prodname_marketplace %}, you can't make changes to the plan. Instead, you'll need to remove the pricing plan and create a new plan. Customers who already purchased the removed pricing plan will continue to use it until they opt out and move onto a new pricing plan. For more on pricing plans, see "[{% data variables.product.prodname_marketplace %} pricing plans](/marketplace/selling-your-app/github-marketplace-pricing-plans/)." -Depois de remover um plano de preços, os usuários não poderão comprar seu aplicativo que usa esse plano. Os usuários existentes no plano de preços removido continuarão no plano até que cancelem sua assinatura do plano. +Once you remove a pricing plan, users won't be able to purchase your app using that plan. Existing users on the removed pricing plan will continue to stay on the plan until they cancel their plan subscription. {% note %} -**Observação:** {% data variables.product.product_name %} não pode remover usuários de um plano de preços removido. Você pode realizar uma campanha para incentivar os usuários a atualizar ou fazer downgrade do plano de preços removido para um novo plano de preços. +**Note:** {% data variables.product.product_name %} can't remove users from a removed pricing plan. You can run a campaign to encourage users to upgrade or downgrade from the removed pricing plan onto a new pricing plan. {% endnote %} -Você pode desativar os testes grátis do GitHub Marketplace sem remover o plano de preços, mas isso impede que você inicie futuros testes grátis para esse plano. Se você optar por desativar os testes grátis para um plano de preços, os usuários já inscritos poderão concluir o seu teste gratuito. +You can disable GitHub Marketplace free trials without retiring the pricing plan, but this prevents you from initiating future free trials for that plan. If you choose to disable free trials for a pricing plan, users already signed up can complete their free trial. -Depois de remover um plano de preços, você poderá criar um novo plano com o mesmo nome do plano de preços removido. Por exemplo, se você tem um plano de preços "Pro", mas precisa alterar o preço fixo, você poderá remover o plano de preços "Pro" e criar um novo plano de preços "Pro" com um preço atualizado. Os usuários poderão comprar o novo plano de preços imediatamente. +After retiring a pricing plan, you can create a new pricing plan with the same name as the removed pricing plan. For instance, if you have a "Pro" pricing plan but need to change the flat rate price, you can remove the "Pro" pricing plan and create a new "Pro" pricing plan with an updated price. Users will be able to purchase the new pricing plan immediately. -Se você não for um editor verificado, você não poderá alterar um plano de preços para o seu aplicativo. Para obter mais informações sobre como se tornar um editor verificado, consulte "[Candidatar-se à verificação de publicador para a sua organização](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)". +If you are not a verified publisher, then you cannot change a pricing plan for your app. For more information about becoming a verified publisher, see "[Applying for publisher verification for your organization](/developers/github-marketplace/applying-for-publisher-verification-for-your-organization)." diff --git a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 1905ce8446..0fc3e55f1b 100644 --- a/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -2,13 +2,13 @@ title: Writing a listing description for your app intro: 'To [list your app](/marketplace/listing-on-github-marketplace/) in the {% data variables.product.prodname_marketplace %}, you''ll need to write descriptions of your app and provide images that follow GitHub''s guidelines.' redirect_from: - - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions/ - - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing/ - - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing/ - - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images/ - - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images/ - - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/ + - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-writing-github-app-descriptions + - /apps/marketplace/creating-and-submitting-your-app-for-approval/writing-github-app-descriptions + - /apps/adding-integrations/listing-apps-on-github-marketplace/guidelines-for-creating-a-github-marketplace-listing + - /apps/marketplace/listing-apps-on-github/guidelines-for-creating-a-github-marketplace-listing + - /apps/marketplace/getting-started-with-github-marketplace-listings/guidelines-for-creating-github-marketplace-listing-images + - /apps/marketplace/creating-and-submitting-your-app-for-approval/creating-github-marketplace-listing-images + - /apps/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions - /marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions - /developers/github-marketplace/writing-a-listing-description-for-your-app versions: diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md index 643a091240..e7cd6e457d 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/billing-customers.md @@ -1,9 +1,9 @@ --- -title: Cobrar dos clientes -intro: 'Os aplicativos no {% data variables.product.prodname_marketplace %} devem aderir às diretrizes de cobrança do GitHub e oferecer suporte aos serviços recomendados. A observância das nossas diretrizes ajuda os clientes a percorrer o processo de cobrança sem nenhuma surpresa.' +title: Billing customers +intro: 'Apps on {% data variables.product.prodname_marketplace %} should adhere to GitHub''s billing guidelines and support recommended services. Following our guidelines helps customers navigate the billing process without any surprises.' redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace/ - - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace/ + - /apps/marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace + - /apps/marketplace/selling-your-app/billing-customers-in-github-marketplace - /marketplace/selling-your-app/billing-customers-in-github-marketplace - /developers/github-marketplace/billing-customers versions: @@ -12,39 +12,38 @@ versions: topics: - Marketplace --- +## Understanding the billing cycle -## Entender o ciclo de cobrança +Customers can choose a monthly or yearly billing cycle when they purchase your app. All changes customers make to the billing cycle and plan selection will trigger a `marketplace_purchase` event. You can refer to the `marketplace_purchase` webhook payload to see which billing cycle a customer selects and when the next billing date begins (`effective_date`). For more information about webhook payloads, see "[Webhook events for the {% data variables.product.prodname_marketplace %} API](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)." -Os clientes podem escolher um ciclo de cobrança mensal ou anual quando ao comprar seu aplicativo. Todas as alterações que os clientes fazem no ciclo de cobrança e seleção de plano acionará um evento de `marketplace_purchase`. Você pode fazer referência à carga do webhook `marketplace_purchase` para ver qual ciclo de cobrança um cliente seleciona e quando começa a próxima data de cobrança (`effective_date`). Para obter mais informações sobre cargas de webhook, consulte "[eventos de Webhook para a API de {% data variables.product.prodname_marketplace %}](/developers/github-marketplace/webhook-events-for-the-github-marketplace-api)". +## Providing billing services in your app's UI -## Fornecer serviços de cobrança na interface de usuário do seu aplicativo - -Os clientes devem ser capazes de executar as seguintes ações no site do seu aplicativo: -- Os clientes devem ser capazes de modificar ou cancelar seus planos de {% data variables.product.prodname_marketplace %} para contas pessoais e organizacionais separadamente. +Customers should be able to perform the following actions from your app's website: +- Customers should be able to modify or cancel their {% data variables.product.prodname_marketplace %} plans for personal and organizational accounts separately. {% data reusables.marketplace.marketplace-billing-ui-requirements %} -## Os serviços de cobrança para upgrade, downgrade e cancelamentos +## Billing services for upgrades, downgrades, and cancellations -Siga estas diretrizes para upgrades, downgrade e cancelamentos para manter um processo de cobrança claro e consistente. Para obter instruções mais detalhadas sobre os eventos de compra de {% data variables.product.prodname_marketplace %}, consulte "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +Follow these guidelines for upgrades, downgrades, and cancellations to maintain a clear and consistent billing process. For more detailed instructions about the {% data variables.product.prodname_marketplace %} purchase events, see "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Você pode usar a chave do `marketplace_purchase` do webhook `effective_date` para determinar quando a mudança de um plano irá ocorrer e sincronizar periodicamente as [Lista de contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). +You can use the `marketplace_purchase` webhook's `effective_date` key to determine when a plan change will occur and periodically synchronize the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). -### Atualizações +### Upgrades -Quando um cliente atualiza seu plano de preços ou altera seu ciclo de cobrança de mensal para anual, você deve implementar mudança imediatamente para este cliente. Você precisa aplicar um desconto proporcional ao novo plano e alterar o ciclo de cobrança. +When a customer upgrades their pricing plan or changes their billing cycle from monthly to yearly, you should make the change effective for them immediately. You need to apply a pro-rated discount to the new plan and change the billing cycle. {% data reusables.marketplace.marketplace-failed-purchase-event %} -Para obter informações sobre a criação fluxos de trabalho de atualização e downgrade no seu aplicativo, consulte "[Gerenciando alterações do plano](/developers/github-marketplace/handling-plan-changes)". +For information about building upgrade and downgrade workflows into your app, see "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)." -### Downgrades e cancelamentos +### Downgrades and cancellations -Os downgrades ocorrem quando um cliente muda de um plano pago para um plano gratuito, seleciona um plano com um custo menor que o seu plano atual, ou muda seu ciclo de cobrança de anual para mensal. Quando ocorre o downgrade ou cancelamento, você não precisa fornecer um reembolso. Em vez disso, o plano atual permanecerá ativo até o último dia do ciclo de cobrança atual. O evento `marketplace_purchase` será enviado quando o novo plano entrar em vigor no início do próximo ciclo de cobrança do cliente. - -Quando um cliente cancela um plano, você deve: -- Fazer o downgrade automaticamente para o plano grátis, caso exista. +Downgrades occur when a customer moves to a free plan from a paid plan, selects a plan with a lower cost than their current plan, or changes their billing cycle from yearly to monthly. When downgrades or cancellations occur, you don't need to provide a refund. Instead, the current plan will remain active until the last day of the current billing cycle. The `marketplace_purchase` event will be sent when the new plan takes effect at the beginning of the customer's next billing cycle. +When a customer cancels a plan, you must: +- Automatically downgrade them to the free plan, if it exists. + {% data reusables.marketplace.cancellation-clarification %} -- Habilitá-los para atualizar o plano por meio do GitHub, caso desejem continuar o plano mais adiante. +- Enable them to upgrade the plan through GitHub if they would like to continue the plan at a later time. -Para obter informações sobre a construção de fluxos de trabalho de cancelamento no seu aplicativo, consulte "[Manipulação de cancelamento de plano](/developers/github-marketplace/handling-plan-cancellations)". +For information about building cancellation workflows into your app, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md index 258971791e..b8325be8fc 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/index.md @@ -1,12 +1,12 @@ --- -title: Vender seu aplicativo no GitHub Marketplace -intro: 'Saiba mais sobre requisitos e práticas recomendadas para vender seu aplicativo no {% data variables.product.prodname_marketplace %}.' +title: Selling your app on GitHub Marketplace +intro: 'Learn about requirements and best practices for selling your app on {% data variables.product.prodname_marketplace %}.' redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/ - - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing/ - - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing/ - - /apps/marketplace/pricing-payments-and-free-trials/ - - /apps/marketplace/selling-your-app/ + - /apps/marketplace/administering-listing-plans-and-user-accounts + - /apps/adding-integrations/managing-pricing-and-payments-for-a-github-marketplace-listing + - /apps/marketplace/managing-pricing-and-payments-for-a-github-marketplace-listing + - /apps/marketplace/pricing-payments-and-free-trials + - /apps/marketplace/selling-your-app - /marketplace/selling-your-app versions: fpt: '*' @@ -17,6 +17,6 @@ children: - /pricing-plans-for-github-marketplace-apps - /billing-customers - /receiving-payment-for-app-purchases -shortTitle: Venda aplicativos no Marketplace +shortTitle: Sell apps on the Marketplace --- diff --git a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md index 999f345c3d..98d5bcce1c 100644 --- a/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md +++ b/translations/pt-BR/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md @@ -2,7 +2,7 @@ title: Pricing plans for GitHub Marketplace apps intro: 'Pricing plans allow you to provide your app with different levels of service or resources. You can offer up to 10 pricing plans in your {% data variables.product.prodname_marketplace %} listing.' redirect_from: - - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans/ + - /apps/marketplace/selling-your-app/github-marketplace-pricing-plans - /marketplace/selling-your-app/github-marketplace-pricing-plans - /developers/github-marketplace/pricing-plans-for-github-marketplace-apps versions: diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md index a0f8b0bb6c..54fb39ac9f 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md @@ -1,10 +1,10 @@ --- -title: Gerenciar novas compras e testes grátis -intro: 'Quando um cliente adquire um plano pago, um teste grátis ou a versão gratuita do seu aplicativo do {% data variables.product.prodname_marketplace %}, você receberá o evento [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) com a ação `comprado`, que inicia o fluxo de compra.' +title: Handling new purchases and free trials +intro: 'When a customer purchases a paid plan, free trial, or the free version of your {% data variables.product.prodname_marketplace %} app, you''ll receive the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `purchased` action, which kicks off the purchasing flow.' redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps/ - - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials/ + - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-github-apps + - /apps/marketplace/administering-listing-plans-and-user-accounts/supporting-purchase-plans-for-oauth-apps + - /apps/marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials - /marketplace/integrating-with-the-github-marketplace-api/handling-new-purchases-and-free-trials - /developers/github-marketplace/handling-new-purchases-and-free-trials versions: @@ -12,73 +12,72 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Novas compras & testes gratuitos +shortTitle: New purchases & free trials --- - {% warning %} -Se você oferece um {% data variables.product.prodname_github_app %} em {% data variables.product.prodname_marketplace %}, seu aplicativo deverá identificar usuários seguindo o fluxo de autorização do OAuth. Você não precisa configurar {% data variables.product.prodname_oauth_app %} separadamente para dar suporte a este fluxo. Consulte "[Identificar e autorizar usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" para obter mais informações. +If you offer a {% data variables.product.prodname_github_app %} in {% data variables.product.prodname_marketplace %}, your app must identify users following the OAuth authorization flow. You don't need to set up a separate {% data variables.product.prodname_oauth_app %} to support this flow. See "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)" for more information. {% endwarning %} -## Etapa 1. Compra inicial e evento de webhook +## Step 1. Initial purchase and webhook event -Antes de um cliente comprar o seu aplicativo no {% data variables.product.prodname_marketplace %}, ele irá selecionar um [plano de listagem](/marketplace/selling-your-app/github-marketplace-pricing-plans/). O cliente também escolhe se deseja comprar o aplicativo a partir da sua conta pessoal ou a partir da conta de uma organização. +Before a customer purchases your {% data variables.product.prodname_marketplace %} app, they select a [listing plan](/marketplace/selling-your-app/github-marketplace-pricing-plans/). They also choose whether to purchase the app from their personal account or an organization account. -O cliente efetua a compra clicando em **Concluir pedido e começar a instalação**. +The customer completes the purchase by clicking **Complete order and begin installation**. -{% data variables.product.product_name %} depois envia o webhook de [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) com a ação `purchased` para o seu aplicativo. +{% data variables.product.product_name %} then sends the [`marketplace_purchase`](/webhooks/event-payloads/#marketplace_purchase) webhook with the `purchased` action to your app. -Leia o objeto `effective_date` e `marketplace_purchase` do webhook `marketplace_purchase` para determinar qual plano o cliente comprou, quando começa o ciclo de cobrança, e quando começa o próximo ciclo de cobrança. +Read the `effective_date` and `marketplace_purchase` object from the `marketplace_purchase` webhook to determine which plan the customer purchased, when the billing cycle starts, and when the next billing cycle begins. -Se o seu aplicativo oferecer um teste grátis, leia o atributo `marketplace_purchase[on_free_trial]` do webhook. Se o valor for `verdadeiro`, seu aplicativo deverá acompanhar a data de início de teste gratuito (`effective_date`) e a data em que o teste gratuito termina (`free_trial_ends_on`). Use a data `free_trial_ends_on` para exibir os dias restantes em um teste gratuito na interface de usuário do seu aplicativo. Você pode fazer isso em um banner ou na sua [interface de usuário de cobrança](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). Para aprender como lidar com os cancelamentos antes de um teste grátis, consulte "[Gerenciar cancelamentos de plano](/developers/github-marketplace/handling-plan-cancellations)". Consulte "[Gerenciamento das alterações de plano](/developers/github-marketplace/handling-plan-changes)" para descobrir como fazer transição de um teste grátis para um plano pago quando um teste gratuito expira. +If your app offers a free trial, read the `marketplace_purchase[on_free_trial]` attribute from the webhook. If the value is `true`, your app will need to track the free trial start date (`effective_date`) and the date the free trial ends (`free_trial_ends_on`). Use the `free_trial_ends_on` date to display the remaining days left in a free trial in your app's UI. You can do this in either a banner or in your [billing UI](/marketplace/selling-your-app/billing-customers-in-github-marketplace/#providing-billing-services-in-your-apps-ui). To learn how to handle cancellations before a free trial ends, see "[Handling plan cancellations](/developers/github-marketplace/handling-plan-cancellations)." See "[Handling plan changes](/developers/github-marketplace/handling-plan-changes)" to find out how to transition a free trial to a paid plan when a free trial expires. -Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para obter um exemplo da carga de evento `marketplace_purchase`. +See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. -## Etapa 2. Instalação +## Step 2. Installation -Se seu aplicativo é {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} irá solicitar ao cliente que selecione quais repositórios o aplicativo pode acessar quando comprá-lo. {% data variables.product.product_name %} em seguida, instala o aplicativo na conta selecionada pelo cliente e concede acesso aos repositórios selecionados. +If your app is a {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} prompts the customer to select which repositories the app can access when they purchase it. {% data variables.product.product_name %} then installs the app on the account the customer selected and grants access to the selected repositories. -Neste ponto, se você especificou uma **Configuração de URL** nas suas configurações de {% data variables.product.prodname_github_app %}, {% data variables.product.product_name %} irá redirecionar o cliente para essa URL. Se não especificar uma URL de configuração, você não conseguirá gerenciar as compras do seu {% data variables.product.prodname_github_app %}. +At this point, if you specified a **Setup URL** in your {% data variables.product.prodname_github_app %} settings, {% data variables.product.product_name %} will redirect the customer to that URL. If you do not specify a setup URL, you will not be able to handle purchases of your {% data variables.product.prodname_github_app %}. {% note %} -**Observação:** A **URL de configuração** é descrita como opcional nas configurações de {% data variables.product.prodname_github_app %}, mas é um campo obrigatório se desejar oferecer seu aplicativo em {% data variables.product.prodname_marketplace %}. +**Note:** The **Setup URL** is described as optional in {% data variables.product.prodname_github_app %} settings, but it is a required field if you want to offer your app in {% data variables.product.prodname_marketplace %}. {% endnote %} -Se seu aplicativo for um {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} não irá instalá-lo em qualquer lugar. Em vez disso, {% data variables.product.product_name %} irá redirecionar o cliente para a **URL de Instalação** que você especificou no seu [ anúncio de {% data variables.product.prodname_marketplace %}](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). +If your app is an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} does not install it anywhere. Instead, {% data variables.product.product_name %} redirects the customer to the **Installation URL** you specified in your [{% data variables.product.prodname_marketplace %} listing](/marketplace/listing-on-github-marketplace/writing-github-marketplace-listing-descriptions/#listing-urls). -Quando um cliente compra um {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} irá redirecionar o cliente para a URL que você escolher (URL de configuração ou URL de instalação) e a URL irá incluir o plano de precificação selecionado pelo cliente como um parâmetro de consulta: `marketplace_listing_plan_id`. +When a customer purchases an {% data variables.product.prodname_oauth_app %}, {% data variables.product.product_name %} redirects the customer to the URL you choose (either Setup URL or Installation URL) and the URL includes the customer's selected pricing plan as a query parameter: `marketplace_listing_plan_id`. -## Etapa 3. Autorização +## Step 3. Authorization -Quando um cliente compra seu aplicativo, você deve enviar o cliente por meio do fluxo de autorização OAuth: +When a customer purchases your app, you must send the customer through the OAuth authorization flow: -* Se seu aplicativo for {% data variables.product.prodname_github_app %}, inicie o fluxo de autorização assim que {% data variables.product.product_name %} redirecionar o cliente para a **URL de configuração**. Siga os passos em "[Identificar e autorizar usuários para {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)". +* If your app is a {% data variables.product.prodname_github_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Setup URL**. Follow the steps in "[Identifying and authorizing users for {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)." -* Se seu aplicativo for um {% data variables.product.prodname_oauth_app %}, inicie o fluxo de autorização assim que {% data variables.product.product_name %} redirecionar o cliente para a **URL de instalação**. Siga as etapas em "[Autorizar {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)". +* If your app is an {% data variables.product.prodname_oauth_app %}, begin the authorization flow as soon as {% data variables.product.product_name %} redirects the customer to the **Installation URL**. Follow the steps in "[Authorizing {% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/authorizing-oauth-apps/)." -Para qualquer tipo de aplicativo, o primeiro passo é redirecionar o cliente para https://github.com/login/oauth/authorize. +For either type of app, the first step is to redirect the customer to https://github.com/login/oauth/authorize. -Depois que o cliente concluir a autorização, seu aplicativo receberá um token de acesso do OAuth para o cliente. Você prrecisará desse token para a próxima etapa. +After the customer completes the authorization, your app receives an OAuth access token for the customer. You'll need this token for the next step. {% note %} -**Observação:** Ao autorizar um cliente em um teste gratuito, conceda a ele o mesmo acesso que ele teria no plano pago. Você irá transferi-los para o plano pago após o término do período de teste. +**Note:** When authorizing a customer on a free trial, grant them the same access they would have on the paid plan. You'll move them to the paid plan after the trial period ends. {% endnote %} -## Etapa 4. Provisionar as contas dos clientes +## Step 4. Provisioning customer accounts -Seu aplicativo deve fornecer uma conta de cliente para todas as novas compras. Usar o token de acesso que você recebeu para o cliente na [Etapa 3. Autorização](#step-3-authorization), chame o ponto de extremidade "[Lista de assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)". A resposta incluirá a `conta` do cliente e mostrará se está em um teste grátis (`on_free_trial`). Use estas informações para concluir a configuração e o provisionamento. +Your app must provision a customer account for all new purchases. Using the access token you received for the customer in [Step 3. Authorization](#step-3-authorization), call the "[List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user)" endpoint. The response will include the customer's `account` information and show whether they are on a free trial (`on_free_trial`). Use this information to complete setup and provisioning. {% data reusables.marketplace.marketplace-double-purchases %} -Se a compra for para uma organização e por usuário, você poderá solicitar que o cliente escolha quais integrantes da organização terão acesso ao aplicativo comprado. +If the purchase is for an organization and per-user, you can prompt the customer to choose which organization members will have access to the purchased app. -É possível personalizar a forma como os integrantes da organização recebem acesso ao seu aplicativo. Aqui estão algumas sugestões: +You can customize the way that organization members receive access to your app. Here are a few suggestions: -**Preços fixos:** Se a compra for feita para uma organização que usa preços fixos, seu aplicativo poderá [obter todos os integrantes da organização](/rest/reference/orgs#list-organization-members) através da API e solicitar ao administrador da organização que escolha quais integrantes terão usuários pagos no lado do integrador. +**Flat-rate pricing:** If the purchase is made for an organization using flat-rate pricing, your app can [get all the organization’s members](/rest/reference/orgs#list-organization-members) via the API and prompt the organization admin to choose which members will have paid users on the integrator side. -**Preços por unidade:** Um método de provisionamento de estações por unidade é permitir que os usuários ocupem uma estação enquanto iniciam a sessão do aplicativo. Quando o cliente atingir o limite de contagem da estação, seu aplicativo poderá alertar o usuário de que ele precisa fazer a atualização do plano de {% data variables.product.prodname_marketplace %}. +**Per-unit pricing:** One method of provisioning per-unit seats is to allow users to occupy a seat as they log in to the app. Once the customer hits the seat count threshold, your app can alert the user that they need to upgrade through {% data variables.product.prodname_marketplace %}. diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md index 1e1cb13001..bc5ef37804 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-cancellations.md @@ -1,9 +1,9 @@ --- -title: Gerenciar cancelamento de plano -intro: 'O cancelamento de um aplicativo de {% data variables.product.prodname_marketplace %} aciona o webhook do evento [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) com a ação `cancelado`, que dá início ao fluxo de cancelamento.' +title: Handling plan cancellations +intro: 'Cancelling a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events) webhook with the `cancelled` action, which kicks off the cancellation flow.' redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans/ + - /apps/marketplace/administering-listing-plans-and-user-accounts/cancelling-plans + - /apps/marketplace/integrating-with-the-github-marketplace-api/cancelling-plans - /marketplace/integrating-with-the-github-marketplace-api/cancelling-plans - /developers/github-marketplace/handling-plan-cancellations versions: @@ -11,26 +11,25 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Cancelamentos de plano +shortTitle: Plan cancellations --- +For more information about cancelling as it relates to billing, see "[Billing customers in {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)." -Para obter mais informações sobre cancelamento e como está relacionado à cobrança, consulte "[Cobrança de clientes {% data variables.product.prodname_marketplace %}](/apps//marketplace/administering-listing-plans-and-user-accounts/billing-customers-in-github-marketplace)". +## Step 1. Cancellation event -## Etapa 1. Evento de cancelamento +If a customer chooses to cancel a {% data variables.product.prodname_marketplace %} order, GitHub sends a [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the action `cancelled` to your app when the cancellation takes effect. If the customer cancels during a free trial, your app will receive the event immediately. When a customer cancels a paid plan, the cancellation will occur at the end of the customer's billing cycle. -Se um cliente optar por cancelar um pedido do {% data variables.product.prodname_marketplace %}, o GitHub irá enviar um webhook de [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) com a ação `cancelado` para o seu aplicativo, quando o cancelamento entrar em vigor. Se o cliente efetuar o cancelamento durante um teste grátis, seu aplicativo receberá o evento imediatamente. Quando um cliente cancelar um plano pago, o cancelamento ocorrerá ao final do ciclo de cobrança do cliente. +## Step 2. Deactivating customer accounts -## Etapa 2. Desativar as contas dos clientes +When a customer cancels a free or paid plan, your app must perform these steps to complete cancellation: -Quando um cliente cancela um plano grátis ou pago, seu aplicativo deve realizar essas etapas para concluir o cancelamento: - -1. Desative a conta do cliente que cancelou o plano. -1. Revogue o token do OAuth que seu aplicativo recebeu para o cliente. -1. Se o seu aplicativo for um aplicativo OAuth, remova todos os webhooks que seu aplicativo criou para os repositórios. -1. Remova todos os dados do cliente em 30 dias após receber o evento `cancelado`. +1. Deactivate the account of the customer who cancelled their plan. +1. Revoke the OAuth token your app received for the customer. +1. If your app is an OAuth App, remove all webhooks your app created for repositories. +1. Remove all customer data within 30 days of receiving the `cancelled` event. {% note %} -**Obsevação:** Recomendamos usar a `effective_date` do webhook [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) para determinar quando ocorrerá a mudança do plano e sincronizar periodicamente [Listar as contas para um plano](/rest/reference/apps#list-accounts-for-a-plan). Para obter mais informações sobre webhooks, consulte "[eventos de webhook do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)". +**Note:** We recommend using the [`marketplace_purchase`](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook's `effective_date` to determine when a plan change will occur and periodically synchronizing the [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan). For more information on webhooks, see "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)." {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md index 236fc1edbd..34142dbb37 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-plan-changes.md @@ -1,9 +1,9 @@ --- -title: Gerenciar mudanças de plano -intro: 'Atualizar ou fazer downgrade de um aplicativo do {% data variables.product.prodname_marketplace %} aciona o webook do [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) com a ação `alterado`, que dá início ao fluxo de atualização ou downgrade.' +title: Handling plan changes +intro: 'Upgrading or downgrading a {% data variables.product.prodname_marketplace %} app triggers the [`marketplace_purchase` event](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/) webhook with the `changed` action, which kicks off the upgrade or downgrade flow.' redirect_from: - - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans/ + - /apps/marketplace/administering-listing-plans-and-user-accounts/upgrading-or-downgrading-plans + - /apps/marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans - /marketplace/integrating-with-the-github-marketplace-api/upgrading-and-downgrading-plans - /developers/github-marketplace/handling-plan-changes versions: @@ -12,55 +12,54 @@ versions: topics: - Marketplace --- +For more information about upgrading and downgrading as it relates to billing, see "[Integrating with the {% data variables.product.prodname_marketplace %} API](/marketplace/integrating-with-the-github-marketplace-api/)." -Para obter mais informações sobre atualização e downgrade com relação à cobrança, consulte "[Integração com a API do {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/)". +## Step 1. Pricing plan change event -## Etapa 1. Evento de mudança de plano de preços +GitHub send the `marketplace_purchase` webhook with the `changed` action to your app, when a customer makes any of these changes to their {% data variables.product.prodname_marketplace %} order: +* Upgrades to a more expensive pricing plan or downgrades to a lower priced plan. +* Adds or removes seats to their existing plan. +* Changes the billing cycle. -O GitHub envia o webhook `marketplace_purchase` com a ação `alterado` para o seu aplicativo, quando um cliente faz qualquer uma dessas alterações no seu pedido do {% data variables.product.prodname_marketplace %}: -* Faz a atualização para um plano de preços mais caro ou para um plano de preços mais barato. -* Adiciona ou remove estações para seu plano existente. -* Altera o ciclo de cobrança. +GitHub will send the webhook when the change takes effect. For example, when a customer downgrades a plan, GitHub sends the webhook at the end of the customer's billing cycle. GitHub sends a webhook to your app immediately when a customer upgrades their plan to allow them access to the new service right away. If a customer switches from a monthly to a yearly billing cycle, it's considered an upgrade. See "[Billing customers in {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" to learn more about what actions are considered an upgrade or downgrade. -O GitHub enviará o webhook quando a alteração entrar em vigor. Por exemplo, quando um cliente faz o downgrade de um plano, o GitHub envia o webhook no final do ciclo de cobrança do cliente. O GitHub envia um webhook para o seu aplicativo imediatamente quando um cliente atualiza seu plano para permitir que acesse o novo serviço imediatamente. Se um cliente mudar de um ciclo de cobrança mensal para anual, isso é considerado uma atualização. Consulte "[Cobrança de clientes no {% data variables.product.prodname_marketplace %}](/marketplace/selling-your-app/billing-customers-in-github-marketplace/)" para saber mais sobre quais ações são consideradas um atualização ou downgrade. +Read the `effective_date`, `marketplace_purchase`, and `previous_marketplace_purchase` from the `marketplace_purchase` webhook to update the plan's start date and make changes to the customer's billing cycle and pricing plan. See "[{% data variables.product.prodname_marketplace %} webhook events](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)" for an example of the `marketplace_purchase` event payload. -Leia o `effective_date`, `marketplace_purchase` e `precedous_marketplace_purchase` do webhook `marketplace_purchase` para atualizar a data de início do plano e fazer alterações no ciclo de cobrança do cliente e no plano de preços. Consulte "[ eventos de webhook de {% data variables.product.prodname_marketplace %}](/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/)para obter um exemplo da carga de evento `marketplace_purchase`. +If your app offers free trials, you'll receive the `marketplace_purchase` webhook with the `changed` action when the free trial expires. If the customer's free trial expires, upgrade the customer to the paid version of the free-trial plan. -Se seu aplicativo oferecer testes grátis, você receberá o webhook `marketplace_purchase` com a ação `alterado` quando o teste grátis expirar. Se o teste grátis do cliente expirar, faça a atualização do cliente para a versão paga do plano grátis de teste. +## Step 2. Updating customer accounts -## Etapa 2. Atualizar as contas dos clientes +You'll need to update the customer's account information to reflect the billing cycle and pricing plan changes the customer made to their {% data variables.product.prodname_marketplace %} order. Display upgrades to the pricing plan, `seat_count` (for per-unit pricing plans), and billing cycle on your Marketplace app's website or your app's UI when you receive the `changed` action webhook. -Você precisará atualizar as informações da conta do cliente para refletir as alterações no ciclo de cobrança e no plano de preços que o cliente fez em seu pedido do {% data variables.product.prodname_marketplace %}. Exibe as atualizações para o plano de preços, `seat_count` (para planos de preços por unidade) e ciclo de cobrança no site do aplicativo do Marketplace ou na interface do usuário do seu aplicativo quando você receber a ação de webhook `alterado`. +When a customer downgrades a plan, it's recommended to review whether a customer has exceeded their plan limits and engage with them directly in your UI or by reaching out to them by phone or email. -Quando um cliente faz o downgrade de um plano, recomenda-se revisar se o cliente excedeu os limites do seu plano e interagir diretamente com ele na sua interface de usuário ou entrando em contato por telefone ou e-mail. - -Para incentivar as pessoas a fazer a atualização, você pode exibir uma URL de upgrade na interface do usuário do seu aplicativo. Consulte "[Sobre as URLs de atualização](#about-upgrade-urls)" para obter mais detalhes. +To encourage people to upgrade you can display an upgrade URL in your app's UI. See "[About upgrade URLs](#about-upgrade-urls)" for more details. {% note %} -**Observação:** Recomendamos executar uma sincronização periódica usando `GET /marketplace_listing/plans/:id/accounts` para garantir que seu aplicativo tenha o plano, as informações do ciclo de cobrança e a contagem de unidades (preço por unidade) corretos para cada conta. +**Note:** We recommend performing a periodic synchronization using `GET /marketplace_listing/plans/:id/accounts` to ensure your app has the correct plan, billing cycle information, and unit count (for per-unit pricing) for each account. {% endnote %} -## Falha nos pagamentos de atualização +## Failed upgrade payments {% data reusables.marketplace.marketplace-failed-purchase-event %} -## Sobre as URLs de atualização +## About upgrade URLs -Você pode redirecionar os usuários da interface de usuário do seu aplicativo no GitHub, usando uma URL de atualização: +You can redirect users from your app's UI to upgrade on GitHub using an upgrade URL: ``` https://www.github.com/marketplace//upgrade// ``` -Por exemplo, se você notar que um cliente está em um plano de 5 pessoas e precisa passar para um plano de 10 pessoas, você poderia exibir um botão na interface do usuário do seu aplicativo que diz "Aqui está como atualizar" ou exibir um banner com um link para a URL de atualização. A URL atualização leva o cliente para a página de confirmação de confirmação da atualização do seu plano da listagem. +For example, if you notice that a customer is on a 5 person plan and needs to move to a 10 person plan, you could display a button in your app's UI that says "Here's how to upgrade" or show a banner with a link to the upgrade URL. The upgrade URL takes the customer to your listing plan's upgrade confirmation page. -Use o `LISTING_PLAN_NUMBER` para o plano que o cliente gostaria de comprar. Ao criar novos planos de preços, eles recebem um `LISTING_PLAN_NUMBER`, que é exclusivo para cada plano na sua listagem, e um `LISTING_PLAN_ID`, que é exclusivo para cada plano no {% data variables.product.prodname_marketplace %}. Você pode encontrar esses números ao [Listar planos](/rest/reference/apps#list-plans), que identifica os seus planos de preços da listagem. Use o `LISTING_PLAN_ID` e "[Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan)" para obter o `CUSTOMER_ACCOUNT_ID`. +Use the `LISTING_PLAN_NUMBER` for the plan the customer would like to purchase. When you create new pricing plans they receive a `LISTING_PLAN_NUMBER`, which is unique to each plan across your listing, and a `LISTING_PLAN_ID`, which is unique to each plan in the {% data variables.product.prodname_marketplace %}. You can find these numbers when you [List plans](/rest/reference/apps#list-plans), which identifies your listing's pricing plans. Use the `LISTING_PLAN_ID` and the "[List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan)" endpoint to get the `CUSTOMER_ACCOUNT_ID`. {% note %} -**Observação:** Se seu cliente atualiza unidades adicionais (como estações), você ainda poderá enviá-las para o plano apropriado para a compra, mas não podemos suportar os parâmetros de `unit_count` neste momento. +**Note:** If your customer upgrades to additional units (such as seats), you can still send them to the appropriate plan for their purchase, but we are unable to support `unit_count` parameters at this time. {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md index 4a446e6893..074d42544b 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/index.md @@ -1,9 +1,9 @@ --- -title: Usar a API do GitHub Marketplace no seu aplicativo -intro: 'Aprenda como integrar a API e os eventos do webhook do {% data variables.product.prodname_marketplace %} ao seu aplicativo para o {% data variables.product.prodname_marketplace %}.' +title: Using the GitHub Marketplace API in your app +intro: 'Learn how to integrate the {% data variables.product.prodname_marketplace %} API and webhook events into your app for the {% data variables.product.prodname_marketplace %} .' redirect_from: - - /apps/marketplace/setting-up-github-marketplace-webhooks/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/ + - /apps/marketplace/setting-up-github-marketplace-webhooks + - /apps/marketplace/integrating-with-the-github-marketplace-api - /marketplace/integrating-with-the-github-marketplace-api versions: fpt: '*' @@ -17,6 +17,6 @@ children: - /handling-new-purchases-and-free-trials - /handling-plan-changes - /handling-plan-cancellations -shortTitle: Uso da API do Marketplace +shortTitle: Marketplace API usage --- diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md index eaefc104a5..8a02a458a7 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/rest-endpoints-for-the-github-marketplace-api.md @@ -1,9 +1,9 @@ --- -title: Pontos de extremidade de REST para a API do GitHub Marketplace -intro: 'Para ajudar a gerenciar seu aplicativo em {% data variables.product.prodname_marketplace %}, use esses pontos de extremidade da API de {% data variables.product.prodname_marketplace %}.' +title: REST endpoints for the GitHub Marketplace API +intro: 'To help manage your app on {% data variables.product.prodname_marketplace %}, use these {% data variables.product.prodname_marketplace %} API endpoints.' redirect_from: - - /apps/marketplace/github-marketplace-api-endpoints/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints/ + - /apps/marketplace/github-marketplace-api-endpoints + - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-rest-api-endpoints - /developers/github-marketplace/rest-endpoints-for-the-github-marketplace-api versions: @@ -11,23 +11,22 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: API REST +shortTitle: REST API --- +Here are some useful endpoints available for Marketplace listings: -Aqui estão alguns pontos de extremidade úteis e disponíveis para listagens do Marketplace: +* [List plans](/rest/reference/apps#list-plans) +* [List accounts for a plan](/rest/reference/apps#list-accounts-for-a-plan) +* [Get a subscription plan for an account](/rest/reference/apps#get-a-subscription-plan-for-an-account) +* [List subscriptions for the authenticated user](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) -* [Listar planos](/rest/reference/apps#list-plans) -* [Listar contas de um plano](/rest/reference/apps#list-accounts-for-a-plan) -* [Obter um plano de assinatura para uma conta](/rest/reference/apps#get-a-subscription-plan-for-an-account) -* [Listar assinaturas para o usuário autenticado](/rest/reference/apps#list-subscriptions-for-the-authenticated-user) +See these pages for details on how to authenticate when using the {% data variables.product.prodname_marketplace %} API: -Veja estas páginas para obter informações sobre como efetuar a autenticação ao usar a API do {% data variables.product.prodname_marketplace %}: - -* [Opções de autorização para aplicativos OAuth](/apps/building-oauth-apps/authorizing-oauth-apps/) -* [Opções de autenticação para aplicativos GitHub](/apps/building-github-apps/authenticating-with-github-apps/) +* [Authorization options for OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/) +* [Authentication options for GitHub Apps](/apps/building-github-apps/authenticating-with-github-apps/) {% note %} -**Observação:** [Os limites de taxa para a API REST](/rest#rate-limiting) aplicam-se a todos os pontos de extremidade da API de {% data variables.product.prodname_marketplace %}. +**Note:** [Rate limits for the REST API](/rest#rate-limiting) apply to all {% data variables.product.prodname_marketplace %} API endpoints. {% endnote %} diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md index a3993b6d43..537d8fe792 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/testing-your-app.md @@ -1,9 +1,9 @@ --- -title: Testar seu aplicativo -intro: 'O GitHub recomenda testar seu aplicativo com APIs e webhooks antes de enviar sua listagem para o {% data variables.product.prodname_marketplace %}, para que você possa oferecer uma experiência ideal para os clientes. Antes que um especialista em integração aprove seu aplicativo, ele deverá tratar adequadamente os fluxos de cobrança.' +title: Testing your app +intro: 'GitHub recommends testing your app with APIs and webhooks before submitting your listing to {% data variables.product.prodname_marketplace %} so you can provide an ideal experience for customers. Before an onboarding expert approves your app, it must adequately handle the billing flows.' redirect_from: - - /apps/marketplace/testing-apps-apis-and-webhooks/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps/ + - /apps/marketplace/testing-apps-apis-and-webhooks + - /apps/marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps - /marketplace/integrating-with-the-github-marketplace-api/testing-github-marketplace-apps - /developers/github-marketplace/testing-your-app versions: @@ -12,35 +12,34 @@ versions: topics: - Marketplace --- +## Testing apps -## Testar aplicativos +You can use a draft {% data variables.product.prodname_marketplace %} listing to simulate each of the billing flows. A listing in the draft state means that it has not been submitted for approval. Any purchases you make using a draft {% data variables.product.prodname_marketplace %} listing will _not_ create real transactions, and GitHub will not charge your credit card. Note that you can only simulate purchases for plans published in the draft listing and not for draft plans. For more information, see "[Drafting a listing for your app](/developers/github-marketplace/drafting-a-listing-for-your-app)" and "[Using the {% data variables.product.prodname_marketplace %} API in your app](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)." -Você pode usar um rascunho de anúncio de {% data variables.product.prodname_marketplace %} para simular cada um dos fluxos de cobrança. Uma listagem com status de rascunho significa que não foi enviada à aprovação. Qualquer compra que você fizer usando uma listagem de rascunho do {% data variables.product.prodname_marketplace %} _não criará_ transações reais e o GitHub não efetuará nenhuma cobrança no seu cartão de crédito. Observe que você só pode simular compras para planos publicados no rascunho do anúncio e não para rascunho de planos. Para mais informações, consulte "[Elaborar um anúncio para o seu aplicativo](/developers/github-marketplace/drafting-a-listing-for-your-app)" e "[Usar a API de {% data variables.product.prodname_marketplace %} no seu aplicativo](/developers/github-marketplace/using-the-github-marketplace-api-in-your-app)". +### Using a development app with a draft listing to test changes -### Usar um aplicativo de desenvolvimento com uma listagem de rascunho para testar alterações +A {% data variables.product.prodname_marketplace %} listing can only be associated with a single app registration, and each app can only access its own {% data variables.product.prodname_marketplace %} listing. For these reasons, we recommend configuring a separate development app, with the same configuration as your production app, and creating a _draft_ {% data variables.product.prodname_marketplace %} listing that you can use for testing. The draft {% data variables.product.prodname_marketplace %} listing allows you to test changes without affecting the active users of your production app. You will never have to submit your development {% data variables.product.prodname_marketplace %} listing, since you will only use it for testing. -Uma listagem do {% data variables.product.prodname_marketplace %} só pode ser associada a um único registro do aplicativo, e cada aplicativo só pode acessar sua própria listagem do {% data variables.product.prodname_marketplace %}. Por este motivo, recomendamos configurar um aplicativo de desenvolvimento separado, com a mesma configuração que o seu aplicativo de produção, bem como criar uma listagem de _rascunho de_ {% data variables.product.prodname_marketplace %} que você pode usar para testes. A listagem de rascunho do {% data variables.product.prodname_marketplace %} permite que você teste alterações sem afetar os usuários ativos do seu aplicativo de produção. Você nunca precisará enviar a sua lista de desenvolvimento do {% data variables.product.prodname_marketplace %}, uma vez que irá usá-la apenas para testes. +Because you can only create draft {% data variables.product.prodname_marketplace %} listings for public apps, you must make your development app public. Public apps are not discoverable outside of published {% data variables.product.prodname_marketplace %} listings as long as you don't share the app's URL. A Marketplace listing in the draft state is only visible to the app's owner. -Como você pode criar apenas listagens de rascunho do {% data variables.product.prodname_marketplace %} para aplicativos públicos, você deve tornar público o seu aplicativo de desenvolvimento. Os aplicativos públicos não são detectáveis fora das listagens publicadas do {% data variables.product.prodname_marketplace %}, desde que que você não compartilhe a URL do aplicativo. Uma listagem do Marketplace com o status de rascunho é visível apenas para o proprietário do aplicativo. - -Assim que você tiver um aplicativo de desenvolvimento com uma listagem de rascunho, você poderá usá-lo para testar as alterações feitas no seu aplicativo enquanto os integra à API e aos webhooks do {% data variables.product.prodname_marketplace %}. +Once you have a development app with a draft listing, you can use it to test changes you make to your app while integrating with the {% data variables.product.prodname_marketplace %} API and webhooks. {% warning %} -Não faça compras de teste com um app que está ativo em {% data variables.product.prodname_marketplace %}. +Do not make test purchases with an app that is live in {% data variables.product.prodname_marketplace %}. {% endwarning %} -### Simular eventos de compra do Marketplace +### Simulating Marketplace purchase events -Seus cenários de teste podem exigir a definição de planos de listagem que oferecem testes grátis e alternância de assinaturas grátis e pagas. Uma vez que os downgrades e os cancelamentos não entram em vigor antes do próximo ciclo de cobrança, o GitHub fornece um recurso apenas para o desenvolvedor "Aplicar alteração Pendente" para fazer com que as ações `alterado` e `cancelado` do plano entrem em vigor imediatamente. Você pode acessar **Aplicar alteração pendente** para aplicativos de listagens do Marketplace com o status _rascunho_ em https://github.com/settings/billing#pending-cycle: +Your testing scenarios may require setting up listing plans that offer free trials and switching between free and paid subscriptions. Because downgrades and cancellations don't take effect until the next billing cycle, GitHub provides a developer-only feature to "Apply Pending Change" to force `changed` and `cancelled` plan actions to take effect immediately. You can access **Apply Pending Change** for apps with _draft_ Marketplace listings in https://github.com/settings/billing#pending-cycle: -![Aplicar alterações pendentes](/assets/images/github-apps/github-apps-apply-pending-changes.png) +![Apply pending change](/assets/images/github-apps/github-apps-apply-pending-changes.png) -## Testar APIs +## Testing APIs -Para a maioria dos pontos de extremidade da API de do {% data variables.product.prodname_marketplace %}, nós também fornecemos pontos de extremidade de teste da API, que retornam dados falsos de código que você pode usar para testes. Para receber dados de teste, você deve especificar as URLs de teste, que incluem `/teste` no encaminhamento (por exemplo, `/user/marketplace_purchases/stubbed`). Para obter uma lista de pontos de extremidade compatíveis com essa abordagem de dados de teste, consulte [pontos de extremidade do {% data variables.product.prodname_marketplace %} ](/rest/reference/apps#github-marketplace). . +For most {% data variables.product.prodname_marketplace %} API endpoints, we also provide stubbed API endpoints that return hard-coded, fake data you can use for testing. To receive stubbed data, you must specify stubbed URLs, which include `/stubbed` in the route (for example, `/user/marketplace_purchases/stubbed`). For a list of endpoints that support this stubbed-data approach, see [{% data variables.product.prodname_marketplace %} endpoints](/rest/reference/apps#github-marketplace). -## Testar webhooks +## Testing webhooks -O GitHub fornece ferramentas para testar as suas cargas implantadas. Para obter mais informações, consulte "[Testar webhooks](/webhooks/testing/)". +GitHub provides tools for testing your deployed payloads. For more information, see "[Testing webhooks](/webhooks/testing/)." diff --git a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md index ad3280eb4b..eb0ffba0ac 100644 --- a/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md +++ b/translations/pt-BR/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/webhook-events-for-the-github-marketplace-api.md @@ -1,9 +1,9 @@ --- -title: Eventos do Webhook para a API do GitHub Marketplace -intro: 'Um aplicativo do {% data variables.product.prodname_marketplace %} recebe informações sobre mudanças no plano de um usuário no webhook do evento de compra no Marketplace. Um evento de compra no Marketplace é acionado quando um usuário compra, cancela ou muda seu plano de pagamento.' +title: Webhook events for the GitHub Marketplace API +intro: 'A {% data variables.product.prodname_marketplace %} app receives information about changes to a user''s plan from the Marketplace purchase event webhook. A Marketplace purchase event is triggered when a user purchases, cancels, or changes their payment plan.' redirect_from: - - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing/ - - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events/ + - /apps/marketplace/setting-up-github-marketplace-webhooks/about-webhook-payloads-for-a-github-marketplace-listing + - /apps/marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events - /marketplace/integrating-with-the-github-marketplace-api/github-marketplace-webhook-events - /developers/github-marketplace/webhook-events-for-the-github-marketplace-api versions: @@ -11,66 +11,65 @@ versions: ghec: '*' topics: - Marketplace -shortTitle: Eventos webhook +shortTitle: Webhook events --- +## {% data variables.product.prodname_marketplace %} purchase webhook payload -## Carga do webhook de compra no {% data variables.product.prodname_marketplace %} +Webhooks `POST` requests have special headers. See "[Webhook delivery headers](/webhooks/event-payloads/#delivery-headers)" for more details. GitHub doesn't resend failed delivery attempts. Ensure your app can receive all webhook payloads sent by GitHub. -As solicitações de `POST` têm cabeçalhos especiais. Consulte "[Cabeçalhos de entrega de Webhook](/webhooks/event-payloads/#delivery-headers)" para obter mais informações. O GitHub não reenvia tentativas falhas de entrega. Certifique-se de que seu aplicativo possa receber todas as cargas do webhook enviadas pelo GitHub. - -Os cancelamentos e downgrades entram em vigor no primeiro dia do próximo ciclo de cobrança. Os eventos para downgrades e cancelamentos são enviados quando o novo plano entra em vigor no início do próximo ciclo de cobrança. Os eventos referentes às novas compras e atualizações entram em vigor imediatamente. Use `effective_date` na carga do webhook para determinar quando uma alteração terá início. +Cancellations and downgrades take effect on the first day of the next billing cycle. Events for downgrades and cancellations are sent when the new plan takes effect at the beginning of the next billing cycle. Events for new purchases and upgrades begin immediately. Use the `effective_date` in the webhook payload to determine when a change will begin. {% data reusables.marketplace.marketplace-malicious-behavior %} -Cada carga útil do webhook de `marketplace_purchase` terá as seguintes informações: +Each `marketplace_purchase` webhook payload will have the following information: -| Tecla | Tipo | Descrição | -| ---------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `Ação` | `string` | A ação realizada para gerar o webhook. Pode ser `comprado`, `cancelado`, `pending_change`, `pending_change_cancelled`, ou `alterado`. Para obter mais informações, consulte o exemplo de cargas de webhook abaixo. **Observação:** As cargas `pending_change` e `pending_change_cancelled` contêm as mesmas chaves mostradas no exemplo na carga [`alterado` da carga](#example-webhook-payload-for-a-changed-event). | -| `effective_date` | `string` | A data da `ação` entra em vigor. | -| `remetente` | `objeto` | A pessoa que realizou a `ação` que acionou o webhook. | -| `marketplace_purchase` | `objeto` | Informações de compra do {% data variables.product.prodname_marketplace %}. | +Key | Type | Description +----|------|------------- +`action` | `string` | The action performed to generate the webhook. Can be `purchased`, `cancelled`, `pending_change`, `pending_change_cancelled`, or `changed`. For more information, see the example webhook payloads below. **Note:** The `pending_change` and `pending_change_cancelled` payloads contain the same keys as shown in the [`changed` payload example](#example-webhook-payload-for-a-changed-event). +`effective_date` | `string` | The date the `action` becomes effective. +`sender` | `object` | The person who took the `action` that triggered the webhook. +`marketplace_purchase` | `object` | The {% data variables.product.prodname_marketplace %} purchase information. -O objeto `marketplace_purchase` tem as seguintes chaves: +The `marketplace_purchase` object has the following keys: -| Tecla | Tipo | Descrição | -| -------------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `conta` | `objeto` | A conta da `organização` ou do `usuário` associada à assinatura. As contas da organização incluirão `organization_billing_email`, que é o endereço de e-mail administrativo da organização. Para encontrar endereços de e-mail para contas pessoais, você pode usar o ponto de extremidade [Obter o usuário autenticado](/rest/reference/users#get-the-authenticated-user). | -| `billing_cycle` | `string` | Pode ser `anual` ou `mensal`. Quando a o proprietário da `conta` tem um plano grátis do GitHub e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `billing_cycle` será `nulo`. | -| `unit_count` | `inteiro` | Número de unidades compradas. | -| `on_free_trial` | `boolean` | `verdadeiro` quando a `conta` está em um teste grátis. | -| `free_trial_ends_on` | `string` | A data em que o teste grátis expirará. | -| `next_billing_date` | `string` | A data em que começará o próximo ciclo de faturamento. Quando o proprietário da `conta` tem um plano grátis do GitHub.com e comprou um plano grátis do {% data variables.product.prodname_marketplace %}, o `next_billing_date` será `nulo`. | -| `plano` | `objeto` | O plano comprado pelo usuário `` ou `organização`. | +Key | Type | Description +----|------|------------- +`account` | `object` | The `organization` or `user` account associated with the subscription. Organization accounts will include `organization_billing_email`, which is the organization's administrative email address. To find email addresses for personal accounts, you can use the [Get the authenticated user](/rest/reference/users#get-the-authenticated-user) endpoint. +`billing_cycle` | `string` | Can be `yearly` or `monthly`. When the `account` owner has a free GitHub plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `billing_cycle` will be `nil`. +`unit_count` | `integer` | Number of units purchased. +`on_free_trial` | `boolean` | `true` when the `account` is on a free trial. +`free_trial_ends_on` | `string` | The date the free trial will expire. +`next_billing_date` | `string` | The date that the next billing cycle will start. When the `account` owner has a free GitHub.com plan and has purchased a free {% data variables.product.prodname_marketplace %} plan, `next_billing_date` will be `nil`. +`plan` | `object` | The plan purchased by the `user` or `organization`. -O objeto `plano` tem as chaves a seguir: +The `plan` object has the following keys: -| Tecla | Tipo | Descrição | -| ------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------- | -| `id` | `inteiro` | O identificador exclusivo para este plano. | -| `name` | `string` | O nome do plano. | -| `descrição` | `string` | Descrição deste plano. | -| `monthly_price_in_cents` | `inteiro` | O preço mensal deste plano em centavos (moeda americana). Por exemplo, uma listagem que custa 10 dólares por mês será 1000 centavos. | -| `yearly_price_in_cents` | `inteiro` | O preço anual deste plano em centavos (moeda americana). Por exemplo, uma listagem que custa 100 dólares por mês será 10000 centavos. | -| `price_model` | `string` | O modelo de preço para esta listagem. Pode ser uma das `tarifas fixas`, `por unidade`, ou `grátis`. | -| `has_free_trial` | `boolean` | `verdadeiro` quando esta listagem oferece um teste grátis. | -| `unit_name` | `string` | O nome da unidade. Se o modelo de preços não é `por unidade`, será `nulo`. | -| `marcador` | `array de strigns` | Os nomes dos marcadores estabelecidos no plano de preços. | +Key | Type | Description +----|------|------------- +`id` | `integer` | The unique identifier for this plan. +`name` | `string` | The plan's name. +`description` | `string` | This plan's description. +`monthly_price_in_cents` | `integer` | The monthly price of this plan in cents (US currency). For example, a listing that costs 10 US dollars per month will be 1000 cents. +`yearly_price_in_cents` | `integer` | The yearly price of this plan in cents (US currency). For example, a listing that costs 100 US dollars per month will be 10000 cents. +`price_model` | `string` | The pricing model for this listing. Can be one of `flat-rate`, `per-unit`, or `free`. +`has_free_trial` | `boolean` | `true` when this listing offers a free trial. +`unit_name` | `string` | The name of the unit. If the pricing model is not `per-unit` this will be `nil`. +`bullet` | `array of strings` | The names of the bullets set in the pricing plan.
-### Exemplo de carga de webhook para um evento `comprado` -Este exemplo fornece a carga do evento `comprado`. +### Example webhook payload for a `purchased` event +This example provides the `purchased` event payload. {{ webhookPayloadsForCurrentVersion.marketplace_purchase.purchased }} -### Exemplo de carga de webhook para um evento `alterado` +### Example webhook payload for a `changed` event -As alterações em um plano incluem atualizações e downgrades. Este exemplo representa as cargas de eventos `alterados`,`pending_change` e `pending_change_cancelled`. A ação identifica qual destes três acontecimentos ocorreu. +Changes in a plan include upgrades and downgrades. This example represents the `changed`,`pending_change`, and `pending_change_cancelled` event payloads. The action identifies which of these three events has occurred. {{ webhookPayloadsForCurrentVersion.marketplace_purchase.changed }} -### Exemplo de carga de webhook para um evento `cancelado` +### Example webhook payload for a `cancelled` event {{ webhookPayloadsForCurrentVersion.marketplace_purchase.cancelled }} diff --git a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md index b651619a2c..6d51247d42 100644 --- a/translations/pt-BR/content/developers/overview/managing-deploy-keys.md +++ b/translations/pt-BR/content/developers/overview/managing-deploy-keys.md @@ -2,7 +2,7 @@ title: Managing deploy keys intro: Learn different ways to manage SSH keys on your servers when you automate deployment scripts and which way is best for you. redirect_from: - - /guides/managing-deploy-keys/ + - /guides/managing-deploy-keys - /v3/guides/managing-deploy-keys versions: fpt: '*' diff --git a/translations/pt-BR/content/developers/overview/replacing-github-services.md b/translations/pt-BR/content/developers/overview/replacing-github-services.md index 6e27a2cb52..7e39883b4a 100644 --- a/translations/pt-BR/content/developers/overview/replacing-github-services.md +++ b/translations/pt-BR/content/developers/overview/replacing-github-services.md @@ -1,9 +1,9 @@ --- -title: Substituir os GitHub Services -intro: 'Se você ainda depende dos serviços obsoletos do {% data variables.product.prodname_dotcom %}, aprenda como migrar seus hooks de serviço para webhooks.' +title: Replacing GitHub Services +intro: 'If you''re still relying on the deprecated {% data variables.product.prodname_dotcom %} Services, learn how to migrate your service hooks to webhooks.' redirect_from: - - /guides/replacing-github-services/ - - /v3/guides/automating-deployments-to-integrators/ + - /guides/replacing-github-services + - /v3/guides/automating-deployments-to-integrators - /v3/guides/replacing-github-services versions: fpt: '*' @@ -14,61 +14,61 @@ topics: --- -Nós tornamos o GitHub Services obsoletos em favor da integração com webhooks. Este guia ajuda você a fazer a transição para webhooks dos serviços do GitHub. Para obter mais informações sobre este anúncio, consulte o [post do blog](https://developer.github.com/changes/2018-10-01-denying-new-github-services). +We have deprecated GitHub Services in favor of integrating with webhooks. This guide helps you transition to webhooks from GitHub Services. For more information on this announcement, see the [blog post](https://developer.github.com/changes/2018-10-01-denying-new-github-services). {% note %} -Como uma alternativa ao serviço de e-mail, agora você pode começar a usar notificações por e-mail para push no repositório. Consulte "[Sobre notificações por e-mail para pushes no seu repositório](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)para aprender como configurar as notificações por e-mail do commit. +As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications. {% endnote %} -## Linha do tempo da depreciação +## Deprecation timeline -- **1 de outubro de 2018**: o GitHub foi suspenso, permitindo que os usuários instalassem serviços. Removemos o GitHub Services da interface de usuário do GitHub.com. -- **29 de janeiro de 2019**: Como alternativa ao serviço de e-mail, você pode começar a usar notificações por e-mail para push em seu repositório. Consulte "[Sobre notificações por e-mail para pushes no seu repositório](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)para aprender como configurar as notificações por e-mail do commit. -- **31 de janeiro de 2019**: o GitHub irá parar de implementar os eventos dos serviços instalados no GitHub.com. +- **October 1, 2018**: GitHub discontinued allowing users to install services. We removed GitHub Services from the GitHub.com user interface. +- **January 29, 2019**: As an alternative to the email service, you can now start using email notifications for pushes to your repository. See "[About email notifications for pushes to your repository](/github/receiving-notifications-about-activity-on-github/about-email-notifications-for-pushes-to-your-repository/)" to learn how to configure commit email notifications. +- **January 31, 2019**: GitHub will stop delivering installed services' events on GitHub.com. -## Antecedentes do GitHub Services +## GitHub Services background -P GitHub Services (às vezes referido como Hooks de Serviço) é o método legado de integração, em que o GitHub hospedou uma parte dos serviços do nosso integrador por meio do [repositório `github-services`](https://github.com/github/github-services). Ações executadas no GitHub acionam esses serviços e você pode usá-los para acionar ações fora do GitHub. +GitHub Services (sometimes referred to as Service Hooks) is the legacy method of integrating where GitHub hosted a portion of our integrator’s services via [the `github-services` repository](https://github.com/github/github-services). Actions performed on GitHub trigger these services, and you can use these services to trigger actions outside of GitHub. {% ifversion ghes or ghae %} -## Encontrar repositórios que usam o GitHub Services -Fornecemos um script de linha de comando que ajuda a identificar quais repositórios usam o GitHub Services. Para obter mais informações, consulte [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %} +## Finding repositories that use GitHub Services +We provide a command-line script that helps you identify which repositories on your appliance use GitHub Services. For more information, see [ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report).{% endif %} ## GitHub Services vs. webhooks -As principais diferenças entre o GitHub Services e webhooks: -- **Configuração**: O GitHub Services tem opções de configuração específicas do serviço, enquanto os webhooks são configurados simplesmente especificando uma URL e um conjunto de eventos. -- **Lógica personalizada**: O GitHub Services pode ter uma lógica personalizada para responder com várias ações como parte do processamento de um único evento, enquanto os webhooks não têm nenhuma lógica personalizada. -- **Tipos de solicitações**: O GitHub Services pode fazer solicitações HTTP e que não são HTTP, enquanto os webhooks podem fazer apenas solicitações HTTP. +The key differences between GitHub Services and webhooks: +- **Configuration**: GitHub Services have service-specific configuration options, while webhooks are simply configured by specifying a URL and a set of events. +- **Custom logic**: GitHub Services can have custom logic to respond with multiple actions as part of processing a single event, while webhooks have no custom logic. +- **Types of requests**: GitHub Services can make HTTP and non-HTTP requests, while webhooks can make HTTP requests only. -## Substituir os serviços por webhooks +## Replacing Services with webhooks -Para substituir GitHub Services por Webhooks: +To replace GitHub Services with Webhooks: -1. Identifique os eventos de webhook relevantes que você precisará assinar [nesta lista](/webhooks/#events). +1. Identify the relevant webhook events you’ll need to subscribe to from [this list](/webhooks/#events). -2. Altere sua configuração dependendo de como você usa atualmente os GitHub Services: +2. Change your configuration depending on how you currently use GitHub Services: - - **Aplicativos GitHub**: Atualize as permissões e eventos assinados do aplicativo para configurar seu aplicativo para receber os eventos de webhook relevantes. - - **Aplicativos OAuth**: Solicite o(s) escopo(s) `repo_hook` e/ou `org_hook` para gerenciar os eventos relevantes em nome dos usuários. - - **Provedores do GitHub Services**: Solicite que os usuários configurem manualmente um webhook com os eventos relevantes enviados a você, ou aproveite esta oportunidade para criar um aplicativo para gerenciar essa funcionalidade. Para obter mais informações, consulte "[Sobre os aplicativos](/apps/about-apps/)". + - **GitHub Apps**: Update your app's permissions and subscribed events to configure your app to receive the relevant webhook events. + - **OAuth Apps**: Request either the `repo_hook` and/or `org_hook` scope(s) to manage the relevant events on behalf of users. + - **GitHub Service providers**: Request that users manually configure a webhook with the relevant events sent to you, or take this opportunity to build an app to manage this functionality. For more information, see "[About apps](/apps/about-apps/)." -3. Mover configuração adicional de fora do GitHub. Alguns GitHub Services exigem uma configuração adicional e personalizada na página de configuração do GitHub. Se o seu serviço fizer isso, você deverá mover esta funcionalidade para seu aplicativo ou depender dos aplicativos GitHub ou OAuth, quando necessário. +3. Move additional configuration from outside of GitHub. Some GitHub Services require additional, custom configuration on the configuration page within GitHub. If your service does this, you will need to move this functionality into your application or rely on GitHub or OAuth Apps where applicable. -## Compatibilidade com {% data variables.product.prodname_ghe_server %} +## Supporting {% data variables.product.prodname_ghe_server %} -- **{% data variables.product.prodname_ghe_server %} 2.17**: O {% data variables.product.prodname_ghe_server %} com versão 2.17 ou superior irá parar de permitir que os administradores instalem serviços. Os administradores continuarão podendo modificar hooks de serviço existentes e receber hooks de serviço no {% data variables.product.prodname_ghe_server %} para as versões 2.17 a 2.19. Como alternativa ao serviço de e-mail, você poderá usar notificações de e-mail para push para seu repositório no {% data variables.product.prodname_ghe_server %} com versão 2.17 ou superior. Consulte [este poste de blog](https://developer.github.com/changes/2019-01-29-life-after-github-services) para saber mais. -- **{% data variables.product.prodname_ghe_server %} 2.20**: O {% data variables.product.prodname_ghe_server %} com versão 2.20 e superior deixará de implementar os eventos de todos os serviços instalados. +- **{% data variables.product.prodname_ghe_server %} 2.17**: {% data variables.product.prodname_ghe_server %} release 2.17 and higher will discontinue allowing admins to install services. Admins will continue to be able to modify existing service hooks and receive service hooks in {% data variables.product.prodname_ghe_server %} release 2.17 through 2.19. As an alternative to the email service, you will be able to use email notifications for pushes to your repository in {% data variables.product.prodname_ghe_server %} 2.17 and higher. See [this blog post](https://developer.github.com/changes/2019-01-29-life-after-github-services) to learn more. +- **{% data variables.product.prodname_ghe_server %} 2.20**: {% data variables.product.prodname_ghe_server %} release 2.20 and higher will stop delivering all installed services' events. -A versão 2.17 do {% data variables.product.prodname_ghe_server %} será a primeira versão que não permite que os administradores instalem o GitHub Services. Só suportaremos o GitHub Services existente até o lançamento da versão do {% data variables.product.prodname_ghe_server %}. Também aceitaremos quaisquer patches críticos o seu GitHub Services em execução em {% data variables.product.prodname_ghe_server %} até 1 de outubro de 2019. +The {% data variables.product.prodname_ghe_server %} 2.17 release will be the first release that does not allow admins to install GitHub Services. We will only support existing GitHub Services until the {% data variables.product.prodname_ghe_server %} 2.20 release. We will also accept any critical patches for your GitHub Service running on {% data variables.product.prodname_ghe_server %} until October 1, 2019. -## Migrar com a nossa ajuda +## Migrating with our help -[Entre em contato conosco](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) em caso de dúvida. +Please [contact us](https://github.com/contact?form%5Bsubject%5D=GitHub+Services+Deprecation) with any questions. -Como uma visão geral de alto nível, o processo de migração normalmente envolve: - - Identificar como e onde seu produto está usando o GitHub Services. - - Identificar os eventos de webhook correspondentes que você precisa configurar para mover para webhooks simples. - - Implementando o design usando [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) ou [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}s](/apps/building-github-apps/) são preferidos. Para saber mais sobre o porquê de {% data variables.product.prodname_github_apps %} ser preferido, consulte "[Motivos para mudar para {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)". +As a high-level overview, the process of migration typically involves: + - Identifying how and where your product is using GitHub Services. + - Identifying the corresponding webhook events you need to configure in order to move to plain webhooks. + - Implementing the design using either [{% data variables.product.prodname_oauth_apps %}](/apps/building-oauth-apps/) or [{% data variables.product.prodname_github_apps %}. {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/) are preferred. To learn more about why {% data variables.product.prodname_github_apps %} are preferred, see "[Reasons for switching to {% data variables.product.prodname_github_apps %}](/apps/migrating-oauth-apps-to-github-apps/#reasons-for-switching-to-github-apps)." diff --git a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md index 7f1768eab8..c1967ee2cc 100644 --- a/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md +++ b/translations/pt-BR/content/developers/overview/secret-scanning-partner-program.md @@ -1,9 +1,9 @@ --- -title: Programa de verificação de segredo de parceiros -intro: 'Como um provedor de serviço, você pode associar-se ao {% data variables.product.prodname_dotcom %} para proteger os seus formatos de token secretos por varredura de segredos, que pesquisa commits acidentais no seu formato secreto e que pode ser enviado para o ponto de extremidade de verificação de um provedor de serviços.' +title: Secret scanning partner program +intro: 'As a service provider, you can partner with {% data variables.product.prodname_dotcom %} to have your secret token formats secured through secret scanning, which searches for accidental commits of your secret format and can be sent to a service provider''s verify endpoint.' miniTocMaxHeadingLevel: 3 redirect_from: - - /partnerships/token-scanning/ + - /partnerships/token-scanning - /partnerships/secret-scanning - /developers/overview/secret-scanning versions: @@ -11,55 +11,55 @@ versions: ghec: '*' topics: - API -shortTitle: Varredura secreta +shortTitle: Secret scanning --- -O {% data variables.product.prodname_dotcom %} faz a varredura de repositórios de formatos secretos conhecidos para evitar uso fraudulento de credenciais confirmadas acidentalmente. {% data variables.product.prodname_secret_scanning_caps %} acontece por padrão em repositórios públicos e pode ser habilitado em repositórios privados por administradores de repositório ou proprietários da organização. Como provedor de serviço, você pode fazer parcerias com {% data variables.product.prodname_dotcom %} para que seus formatos de segredo estejam incluídos em nosso {% data variables.product.prodname_secret_scanning %}. +{% data variables.product.prodname_dotcom %} scans repositories for known secret formats to prevent fraudulent use of credentials that were committed accidentally. {% data variables.product.prodname_secret_scanning_caps %} happens by default on public repositories, and can be enabled on private repositories by repository administrators or organization owners. As a service provider, you can partner with {% data variables.product.prodname_dotcom %} so that your secret formats are included in our {% data variables.product.prodname_secret_scanning %}. -Quando uma correspondência do seu formato secreto é encontrada em um repositório público, uma carga é enviada para um ponto de extremidade HTTP de sua escolha. +When a match of your secret format is found in a public repository, a payload is sent to an HTTP endpoint of your choice. -Quando uma correspondência do formato secreto é encontrada em um repositório privado configurado para {% data variables.product.prodname_secret_scanning %}, os administradores do repositório e o committer são alertados e podem visualizar e gerenciar o resultado {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Gerenciando alertas do {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." +When a match of your secret format is found in a private repository configured for {% data variables.product.prodname_secret_scanning %}, then repository admins and the committer are alerted and can view and manage the {% data variables.product.prodname_secret_scanning %} result on {% data variables.product.prodname_dotcom %}. For more information, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning)." -Este artigo descreve como você pode fazer parceria com {% data variables.product.prodname_dotcom %} como um provedor de serviço e juntar-se ao programa de parceiro de {% data variables.product.prodname_secret_scanning %}. +This article describes how you can partner with {% data variables.product.prodname_dotcom %} as a service provider and join the {% data variables.product.prodname_secret_scanning %} partner program. -## O processo de {% data variables.product.prodname_secret_scanning %} +## The {% data variables.product.prodname_secret_scanning %} process -#### Como {% data variables.product.prodname_secret_scanning %} funciona em um repositório público +#### How {% data variables.product.prodname_secret_scanning %} works in a public repository -O diagrama a seguir resume o processo de {% data variables.product.prodname_secret_scanning %} para repositórios públicos, com qualquer correspondência enviada para o ponto de extremidade de verificação de um provedor de serviços. +The following diagram summarizes the {% data variables.product.prodname_secret_scanning %} process for public repositories, with any matches sent to a service provider's verify endpoint. -![Diagrama do fluxo que mostra o processo de varredura de um segredo e envio de correspondências para o ponto de extremidade de verificação de um provedor de serviços](/assets/images/secret-scanning-flow.png "Fluxo de {% data variables.product.prodname_secret_scanning_caps %}") +![Flow diagram showing the process of scanning for a secret and sending matches to a service provider's verify endpoint](/assets/images/secret-scanning-flow.png "{% data variables.product.prodname_secret_scanning_caps %} flow") -## Juntando-se ao programa de {% data variables.product.prodname_secret_scanning %} em {% data variables.product.prodname_dotcom %} +## Joining the {% data variables.product.prodname_secret_scanning %} program on {% data variables.product.prodname_dotcom %} -1. Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo. -1. Identifique os segredos relevantes cuja varredura você deseja realizar e crie expressões regulares para capturá-los. -1. Para correspondências de segredos encontradas em repositórios públicos, crie um serviço de alerta de segredo que aceite webhooks de {% data variables.product.prodname_dotcom %} que contenham a carga da mensagem de {% data variables.product.prodname_secret_scanning %}. -1. Implemente a verificação de assinatura em seu serviço de alerta secreto. -1. Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto. -1. Fornece feedback sobre falsos positivos (opcional). +1. Contact {% data variables.product.prodname_dotcom %} to get the process started. +1. Identify the relevant secrets you want to scan for and create regular expressions to capture them. +1. For secret matches found in public repositories, create a secret alert service which accepts webhooks from {% data variables.product.prodname_dotcom %} that contain the {% data variables.product.prodname_secret_scanning %} message payload. +1. Implement signature verification in your secret alert service. +1. Implement secret revocation and user notification in your secret alert service. +1. Provide feedback for false positives (optional). -### Entre em contato com {% data variables.product.prodname_dotcom %} para dar início ao processo +### Contact {% data variables.product.prodname_dotcom %} to get the process started -Para iniciar o processo de inscrição, envie um e-mail para secret-scanning@github.com. +To get the enrollment process started, email secret-scanning@github.com. -Você receberá detalhes do programa de {% data variables.product.prodname_secret_scanning %} e você precisará aceitar os termos de participação de {% data variables.product.prodname_dotcom %} antes de prosseguir. +You will receive details on the {% data variables.product.prodname_secret_scanning %} program, and you will need to agree to {% data variables.product.prodname_dotcom %}'s terms of participation before proceeding. -### Identifique seus segredos e crie expressões regulares +### Identify your secrets and create regular expressions -Para fazer a varredura dos seus segredos, {% data variables.product.prodname_dotcom %} precisa das informações a seguir para cada segredo que você deseja que seja incluído no programa {% data variables.product.prodname_secret_scanning %}: +To scan for your secrets, {% data variables.product.prodname_dotcom %} needs the following pieces of information for each secret that you want included in the {% data variables.product.prodname_secret_scanning %} program: -* Um nome único e legível para o tipo do segredo. Nós vamos usá-lo para gerar o valor `Tipo` na carga da mensagem posteriormente. -* Uma expressão regular que encontra o tipo do segredo. Seja o mais preciso possível, pois isso reduzirá o número de falsos positivos. -* A URL do ponto de extremidade que recebe mensagens de {% data variables.product.prodname_dotcom %}. Isso não precisa ser único para cada tipo de segredo. +* A unique, human readable name for the secret type. We'll use this to generate the `Type` value in the message payload later. +* A regular expression which finds the secret type. Be as precise as possible, because this will reduce the number of false positives. +* The URL of the endpoint that receives messages from {% data variables.product.prodname_dotcom %}. This does not have to be unique for each secret type. -Envie esta informação para secret-scanning@github.com. +Send this information to secret-scanning@github.com. -### Crie um serviço de alerta secreto +### Create a secret alert service -Crie um ponto de extremidade HTTP público e acessível à internet na URL que você nos forneceu. Quando uma correspondência da sua expressão regular é encontrada em um repositório público, {% data variables.product.prodname_dotcom %} enviará uma mensagem HTTP `POST` para o seu ponto de extremidade. +Create a public, internet accessible HTTP endpoint at the URL you provided to us. When a match of your regular expression is found in a public repository, {% data variables.product.prodname_dotcom %} will send an HTTP `POST` message to your endpoint. -#### Exemplo de POST enviado para seu ponto de extremidade +#### Example POST sent to your endpoint ```http POST / HTTP/2 @@ -73,33 +73,34 @@ Content-Length: 0123 [{"token":"NMIfyYncKcRALEXAMPLE","type":"mycompany_api_token","url":"https://github.com/octocat/Hello-World/blob/12345600b9cbe38a219f39a9941c9319b600c002/foo/bar.txt"}] ``` -O corpo da mensagem é um array do JSON que contém um ou mais objetos com o seguinte conteúdo. Quando várias correspondências forem encontradas, o {% data variables.product.prodname_dotcom %} pode enviar uma única mensagem com mais de uma correspondência secreta. Seu ponto de extremidade deve ser capaz de lidar com solicitações com um grande número de correspondências sem exceder o tempo. +The message body is a JSON array that contains one or more objects with the following contents. When multiple matches are found, {% data variables.product.prodname_dotcom %} may send a single message with more than one secret match. Your endpoint should be able to handle requests with a large number of matches without timing out. -* **Token**: O valor da correspondência secreta. -* **Tipo**: O nome único que você forneceu para identificar sua expressão regular. -* **URL**: A URL de commit pública onde a correspondência foi encontrada. +* **Token**: The value of the secret match. +* **Type**: The unique name you provided to identify your regular expression. +* **URL**: The public commit URL where the match was found. -### Implemente a verificação de assinatura em seu serviço de alerta secreto +### Implement signature verification in your secret alert service -É altamente recomendável que você implemente a validação da assinatura no seu serviço de alerta de segredo para garantir que as mensagens que você recebe sejam genuinamente de {% data variables.product.prodname_dotcom %} e não sejam maliciosas. +We strongly recommend you implement signature validation in your secret alert service to ensure that the messages you receive are genuinely from {% data variables.product.prodname_dotcom %} and not malicious. -Você pode recuperar a chave pública de da varredura secreta do segredo do {% data variables.product.prodname_dotcom %} em https://api.github.com/meta/public_keys/secret_scanning e validar a mensagem usando o algoritmo `ECDSA-NIST-P256V1-SHA256`. +You can retrieve the {% data variables.product.prodname_dotcom %} secret scanning public key from https://api.github.com/meta/public_keys/secret_scanning and validate the message using the `ECDSA-NIST-P256V1-SHA256` algorithm. {% note %} -**Observação**: Ao enviar uma solicitação para o ponto de extremidade da chave pública acima, você poderá atingir os limites de taxa. Para evitar atingir os limites de velocidade, você pode usar um token de acesso pessoal (sem escopos obrigatórios) como sugerido nas amostras abaixo, ou usar uma solicitação condicional. Para obter mais informações, consulte "[Primeiros passos com a API REST](/rest/guides/getting-started-with-the-rest-api#conditional-requests)". +**Note**: When you send a request to the public key endpoint above, you may hit rate limits. To avoid hitting rate limits, you can use a personal access token (no scopes required) as suggested in the samples below, or use a conditional request. For more information, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#conditional-requests)." {% endnote %} -Supondo que você receba a mensagem a seguir, os trechos de código abaixo demonstram como você poderia efetuar a validação da assinatura. Os snippets de código assumem que você definiu uma variável de ambiente denominada `GITHUB_PRODUCTION_TOKEN` com um PAT gerado (https://github.com/settings/tokens) para evitar atingir os limites de taxa. O PAT não precisa de escopos/permissões. +Assuming you receive the following message, the code snippets below demonstrate how you could perform signature validation. +The code snippets assume you've set an environment variable called `GITHUB_PRODUCTION_TOKEN` with a generated PAT (https://github.com/settings/tokens) to avoid hitting rate limits. The PAT does not need any scopes/permissions. {% note %} -**Observação**: A assinatura foi gerada usando o texto da mensagem não processada. Portanto, é importante que você também use o texto da mensagem não processada para validação da assinatura, em vez de analisar e criar strings do JSON a fim de evitar reorganizar a mensagem ou mudar de espaçamento. +**Note**: The signature was generated using the raw message body. So it's important you also use the raw message body for signature validation, instead of parsing and stringifying the JSON, to avoid rearranging the message or changing spacing. {% endnote %} -**Mensagem de exemplo enviada para verificar o ponto de extremidade** +**Sample message sent to verify endpoint** ```http POST / HTTP/2 Host: HOST @@ -112,7 +113,7 @@ Content-Length: 0000 [{"token":"some_token","type":"some_type","url":"some_url"}] ``` -**Exemplo de validação em Go** +**Validation sample in Go** ```golang package main @@ -199,30 +200,31 @@ func main() { ecdsaKey, ok := key.(*ecdsa.PublicKey) if !ok { fmt.Println("GitHub key was not ECDSA, what are they doing?!") - Exit(7) + os.Exit(7) } // Parse the Webhook Signature parsedSig := asn1Signature{} - asnSig, err := base64. StdEncoding. DecodeString(kSig) + asnSig, err := base64.StdEncoding.DecodeString(kSig) if err != nil { - fmt. Printf("unable to base64 decode signature: %s\n", err) - os. Exit(8) + fmt.Printf("unable to base64 decode signature: %s\n", err) + os.Exit(8) } - rest, err := asn1. Unmarshal(asnSig, &parsedSig) + rest, err := asn1.Unmarshal(asnSig, &parsedSig) if err != nil || len(rest) != 0 { - fmt. Printf("Error unmarshalling asn.1 signature: %s\n", err) - os. Exit(9) + fmt.Printf("Error unmarshalling asn.1 signature: %s\n", err) + os.Exit(9) } // Verify the SHA256 encoded payload against the signature with GitHub's Key - digest := sha256. Sum256([]byte(payload)) - keyOk := ecdsa. Verify(ecdsaKey, digest[:], parsedSig. R, parsedSig. S) + digest := sha256.Sum256([]byte(payload)) + keyOk := ecdsa.Verify(ecdsaKey, digest[:], parsedSig.R, parsedSig.S) if keyOk { - fmt. - Println("the payload is invalid :(") - os. Exit(10) + fmt.Println("THE PAYLOAD IS GOOD!!") + } else { + fmt.Println("the payload is invalid :(") + os.Exit(10) } } @@ -236,12 +238,12 @@ type GitHubSigningKeys struct { // asn1Signature is a struct for ASN.1 serializing/parsing signatures. type asn1Signature struct { - R *big. Int - S *big. Int + R *big.Int + S *big.Int } ``` -**Exemplo de validação no Ruby** +**Validation sample in Ruby** ```ruby require 'openssl' require 'net/http' @@ -281,7 +283,7 @@ openssl_key = OpenSSL::PKey::EC.new(current_key) puts openssl_key.verify(OpenSSL::Digest::SHA256.new, Base64.decode64(signature), payload.chomp) ``` -**Exemplo de validação no JavaScript** +**Validation sample in JavaScript** ```js const crypto = require("crypto"); const axios = require("axios"); @@ -323,17 +325,17 @@ const verify_signature = async (payload, signature, keyID) => { }; ``` -### Implemente revogação do segredo e notificação do usuário no seu serviço de alerta secreto +### Implement secret revocation and user notification in your secret alert service -Para {% data variables.product.prodname_secret_scanning %} em repositórios públicos, você pode melhorar o seu serviço de alerta de segredo para revogar os segredos expostos e notificar os usuários afetados. Você define como implementa isso no seu serviço de alerta de segredo, mas recomendamos considerar qualquer segredo que {% data variables.product.prodname_dotcom %} envie mensagens de que é público e que está comprometido. +For {% data variables.product.prodname_secret_scanning %} in public repositories, you can enhance your secret alert service to revoke the exposed secrets and notify the affected users. How you implement this in your secret alert service is up to you, but we recommend considering any secrets that {% data variables.product.prodname_dotcom %} sends you messages about as public and compromised. -### Fornece feedback sobre falsos positivos +### Provide feedback for false positives -Coletamos feedback sobre a validade dos segredos individuais detectados nas respostas do parceiro. Se você deseja participar, envie um e-mail para secret-scanning@github.com. +We collect feedback on the validity of the detected individual secrets in partner responses. If you wish to take part, email us at secret-scanning@github.com. -Quando relatamos segredos para você, enviamos uma matriz JSON com cada elemento que contém o token, o identificador de tipo e a URL dp commit. Quando você nos envia feedback, você nos envia informações sobre se o token detectado era uma credencial real ou falsa. Aceitamos comentários nos seguintes formatos. +When we report secrets to you, we send a JSON array with each element containing the token, type identifier, and commit URL. When you send us feedback, you send us information about whether the detected token was a real or false credential. We accept feedback in the following formats. -Você pode nos enviar o token não processado: +You can send us the raw token: ``` [ @@ -344,7 +346,7 @@ Você pode nos enviar o token não processado: } ] ``` -Você também pode fornecer o token em forma de hash após executar uma única forma de hash criptográfico do token não processado usando SHA-256: +You may also provide the token in hashed form after performing a one way cryptographic hash of the raw token using SHA-256: ``` [ @@ -355,13 +357,13 @@ Você também pode fornecer o token em forma de hash após executar uma única f } ] ``` -Alguns pontos importantes: -- Você deve enviar-nos apenas a forma não processada do token ("token_raw"), ou a forma em hash ("token_hash"), mas não ambos. -- Para a forma de hash do token não processado, você só pode usar SHA-256 para armazenar o token, e não qualquer outro algoritmo de hashing. -- A etiqueta indica se o token é verdadeiro ("true_positive") ou um falso positivo ("false_positive"). São permitidas apenas essas duas strings literais minúsculas. +A few important points: +- You should only send us either the raw form of the token ("token_raw"), or the hashed form ("token_hash"), but not both. +- For the hashed form of the raw token, you can only use SHA-256 to hash the token, not any other hashing algorithm. +- The label indicates whether the token is a true ("true_positive") or a false positive ("false_positive"). Only these two lowercased literal strings are allowed. {% note %} -**Nota:** Nosso tempo limite de solicitação está definido para ser maior (isto é, 30 segundos) para parceiros que fornecem dados sobre falsos positivos. Se você precisar de um tempo limite superior a 30 segundos, envie um e-mail para secret-scanning@github.com. +**Note:** Our request timeout is set to be higher (that is, 30 seconds) for partners who provide data about false positives. If you require a timeout higher than 30 seconds, email us at secret-scanning@github.com. {% endnote %} diff --git a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md index 39268114f0..1a5c54cd28 100644 --- a/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md +++ b/translations/pt-BR/content/developers/overview/using-ssh-agent-forwarding.md @@ -1,8 +1,8 @@ --- -title: Usar o encaminhamento de agente SSH -intro: 'Para simplificar a implantação em um servidor, você pode configurar o encaminhamento do agente para usar as chaves SSH locais de forma segura.' +title: Using SSH agent forwarding +intro: 'To simplify deploying to a server, you can set up SSH agent forwarding to securely use local SSH keys.' redirect_from: - - /guides/using-ssh-agent-forwarding/ + - /guides/using-ssh-agent-forwarding - /v3/guides/using-ssh-agent-forwarding versions: fpt: '*' @@ -11,50 +11,50 @@ versions: ghec: '*' topics: - API -shortTitle: Encaminhamento de agente SSH +shortTitle: SSH agent forwarding --- -O encaminhamento do agente SSH pode ser usado para simplificar a implantação em um servidor. Isso permite que você use suas chaves SSH locais em vez de deixar as chaves (sem frase secreta!) no seu servidor. +SSH agent forwarding can be used to make deploying to a server simple. It allows you to use your local SSH keys instead of leaving keys (without passphrases!) sitting on your server. -Se você já configurou uma chave SSH para interagir com {% data variables.product.product_name %}, você provavelmente está familiarizado com o `ssh-agent`. É um programa que é executado em segundo plano e mantém sua chave carregada na memória para que você não precise digitar a sua frase secreta toda vez que precisar usar a chave. O fato é que você pode optar por deixar os servidores acessarem seu `ssh-agent local` como se já estivessem em execução no servidor. Isso é como pedir a um amigo para digitar sua senha para que você possa usar o computador. +If you've already set up an SSH key to interact with {% data variables.product.product_name %}, you're probably familiar with `ssh-agent`. It's a program that runs in the background and keeps your key loaded into memory, so that you don't need to enter your passphrase every time you need to use the key. The nifty thing is, you can choose to let servers access your local `ssh-agent` as if they were already running on the server. This is sort of like asking a friend to enter their password so that you can use their computer. -Confira o [Guia das Dicas Técnicas de Steve Friedl][tech-tips] para obter uma explicação mais detalhada sobre encaminhamento do agente SSH. +Check out [Steve Friedl's Tech Tips guide][tech-tips] for a more detailed explanation of SSH agent forwarding. -## Configurar o encaminhamento do agente SSH +## Setting up SSH agent forwarding -Certifique-se de que sua própria chave SSH esteja configurada e funcionando. Você pode usar [nosso guia sobre a geração de chaves SSH][generating-keys], caso ainda não tenha feito isso. +Ensure that your own SSH key is set up and working. You can use [our guide on generating SSH keys][generating-keys] if you've not done this yet. -Você pode testar se a chave local funciona, inserindo `ssh -T git@{% ifversion ghes or ghae %}nome de host{% else %}github. om{% endif %}` no terminal: +You can test that your local key works by entering `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` in the terminal: ```shell $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %} # Attempt to SSH in to github -> Hi username! Você autenticou com sucesso, mas o GitHub não fornece -> acesso shell. +> Hi username! You've successfully authenticated, but GitHub does not provide +> shell access. ``` -Começamos bem. Vamos configurar SSH para permitir o encaminhamento de agentes para o seu servidor. +We're off to a great start. Let's set up SSH to allow agent forwarding to your server. -1. Usando o seu editor de texto favorito, abra o arquivo em `~/.ssh/config`. Se este arquivo não existir, você poderá criá-lo digitando `touch ~/.ssh/config` no terminal. +1. Using your favorite text editor, open up the file at `~/.ssh/config`. If this file doesn't exist, you can create it by entering `touch ~/.ssh/config` in the terminal. + +2. Enter the following text into the file, replacing `example.com` with your server's domain name or IP: -2. Digite o seguinte texto no arquivo, substituindo `example.com` pelo nome do domínio ou IP do seu servidor: - Host example.com ForwardAgent yes {% warning %} -**Aviso:** Você pode estar tentado a usar um caractere curinga como `Host *` para aplicar esta configuração em todas as conexões SSH. Na verdade, isso não é uma boa ideia, já que você iria compartilhar suas chaves SSH locais com *todos* os servidores que ingressar com SSH. Eles não terão acesso direto às chaves, mas serão poderão usá-las *como você* enquanto a conexão for estabelecida. **Você deve adicionar apenas os servidores em que confia e que pretende usar com o encaminhamento de agentes.** +**Warning:** You may be tempted to use a wildcard like `Host *` to just apply this setting to all SSH connections. That's not really a good idea, as you'd be sharing your local SSH keys with *every* server you SSH into. They won't have direct access to the keys, but they will be able to use them *as you* while the connection is established. **You should only add servers you trust and that you intend to use with agent forwarding.** {% endwarning %} -## Testar o encaminhamento de agente SSH +## Testing SSH agent forwarding -Para testar se o encaminhamento de agente está funcionando com seu servidor, você pode ingressar por SSH no servidor e executar `ssh -T git@{% ifversion ghes or ghae %}nome de host{% else %}github.com{% endif %}` mais uma vez. Se tudo correr bem, você retornará à mesma mensagem apresentada quando você fez localmente. +To test that agent forwarding is working with your server, you can SSH into your server and run `ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %}` once more. If all is well, you'll get back the same prompt as you did locally. -Se você não tiver certeza se sua chave local está sendo usada, você também poderá inspecionar a variável `SSH_AUTH_SOCK` no seu servidor: +If you're unsure if your local key is being used, you can also inspect the `SSH_AUTH_SOCK` variable on your server: ```shell $ echo "$SSH_AUTH_SOCK" @@ -62,7 +62,7 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/ssh-4hNGMk8AZX/agent.79453 ``` -Se a variável não estiver definida, significa que o encaminhamento de agentes não está funcionando: +If the variable is not set, it means that agent forwarding is not working: ```shell $ echo "$SSH_AUTH_SOCK" @@ -73,13 +73,13 @@ $ ssh -T git@{% ifversion ghes or ghae %}hostname{% else %}github.com{% endif %} > Permission denied (publickey). ``` -## Solucionar problemas de encaminhamento de agente SSH +## Troubleshooting SSH agent forwarding -Aqui estão algumas coisas a serem analisadas quando o agente SSH for encaminhado para solução de problemas. +Here are some things to look out for when troubleshooting SSH agent forwarding. -### Você deve estar usando uma URL com SSH para fazer check-out do código +### You must be using an SSH URL to check out code -O encaminhamento de SSH só funciona com URLs com SSH, e não com URLs com HTTP(s). Verifique o arquivo *.git/config* no seu servidor e certifique-se de que a URL está na forma SSH, conforme abaixo: +SSH forwarding only works with SSH URLs, not HTTP(s) URLs. Check the *.git/config* file on your server and ensure the URL is an SSH-style URL like below: ```shell [remote "origin"] @@ -87,13 +87,13 @@ O encaminhamento de SSH só funciona com URLs com SSH, e não com URLs com HTTP( fetch = +refs/heads/*:refs/remotes/origin/* ``` -### As suas chaves SSH devem funcionar localmente +### Your SSH keys must work locally -Antes de fazer suas chaves funcionarem por meio do encaminhamento de agentes, primeiro elas devem funcionar localmente. [Nosso guia sobre como gerar chaves SSH][generating-keys] pode ajudá-lo a configurar suas chaves SSH localmente. +Before you can make your keys work through agent forwarding, they must work locally first. [Our guide on generating SSH keys][generating-keys] can help you set up your SSH keys locally. -### Seu sistema deve permitir o encaminhamento do agente SSH +### Your system must allow SSH agent forwarding -Às vezes, as configurações do sistema não permitem o encaminhamento do agente SSH. Você pode verificar se um arquivo de configuração do sistema está sendo usado digitando o seguinte comando no terminal: +Sometimes, system configurations disallow SSH agent forwarding. You can check if a system configuration file is being used by entering the following command in the terminal: ```shell $ ssh -v example.com @@ -107,7 +107,7 @@ $ exit # Returns to your local command prompt ``` -No exemplo acima, o arquivo *~/.ssh/config* é carregado primeiro e */etc/ssh_config* é lido em seguida. Podemos inspecionar esse arquivo para ver se está sobrescrevendo nossas opções, ao executar os seguintes comandos: +In the example above, the file *~/.ssh/config* is loaded first, then */etc/ssh_config* is read. We can inspect that file to see if it's overriding our options by running the following commands: ```shell $ cat /etc/ssh_config @@ -117,17 +117,17 @@ $ cat /etc/ssh_config > ForwardAgent no ``` -Neste exemplo, nosso arquivo */etc/ssh_config* diz especificamente `ForwardAgent no`, que é uma maneira de bloquear o encaminhamento de agentes. A exclusão desta linha do arquivo deverá fazer com que o encaminhamento de agentes funcionando mais uma vez. +In this example, our */etc/ssh_config* file specifically says `ForwardAgent no`, which is a way to block agent forwarding. Deleting this line from the file should get agent forwarding working once more. -### Seu servidor deve permitir o encaminhamento do agente SSH em conexões de entrada +### Your server must allow SSH agent forwarding on inbound connections -O encaminhamento de agentes também pode ser bloqueado no seu servidor. Você pode verificar se o encaminhamento do agente é permitido pelo SSHing no servidor e executar `sshd_config`. A saída deste comando deve indicar que `AllowAgentForwarding` foi configurado. +Agent forwarding may also be blocked on your server. You can check that agent forwarding is permitted by SSHing into the server and running `sshd_config`. The output from this command should indicate that `AllowAgentForwarding` is set. -### Seu `ssh-agent` deve estar em execução +### Your local `ssh-agent` must be running -Na maioria dos computadores, o sistema operacional inicia automaticamente `ssh-agent` para você. No entanto, é necessário que isso seja feito manualmente no Windows. Temos [um guia sobre como iniciar `ssh-agent` sempre que você abrir o Git Bash][autolaunch-ssh-agent]. +On most computers, the operating system automatically launches `ssh-agent` for you. On Windows, however, you need to do this manually. We have [a guide on how to start `ssh-agent` whenever you open Git Bash][autolaunch-ssh-agent]. -Para verificar se `ssh-agent` está em execução no seu computador, digite o seguinte comando no terminal: +To verify that `ssh-agent` is running on your computer, type the following command in the terminal: ```shell $ echo "$SSH_AUTH_SOCK" @@ -135,15 +135,15 @@ $ echo "$SSH_AUTH_SOCK" > /tmp/launch-kNSlgU/Listeners ``` -### Sua chave deve estar disponível para `ssh-agent` +### Your key must be available to `ssh-agent` -Você pode verificar se sua chave está visível para `ssh-agent`, executando o seguinte comando: +You can check that your key is visible to `ssh-agent` by running the following command: ```shell ssh-add -L ``` -Se o comando disser que nenhuma identidade está disponível, você deverá adicionar sua chave: +If the command says that no identity is available, you'll need to add your key: ```shell $ ssh-add yourkey @@ -151,7 +151,7 @@ $ ssh-add yourkey {% tip %} -No macOS, `ssh-agent` irá "esquecer" essa chave, assim que ela for reiniciada durante reinicializações. No entanto, você poderá importar suas chaves SSH para o Keychain usando este comando: +On macOS, `ssh-agent` will "forget" this key, once it gets restarted during reboots. But you can import your SSH keys into Keychain using this command: ```shell $ ssh-add -K yourkey @@ -161,5 +161,5 @@ $ ssh-add -K yourkey [tech-tips]: http://www.unixwiz.net/techtips/ssh-agent-forwarding.html [generating-keys]: /articles/generating-ssh-keys -[generating-keys]: /articles/generating-ssh-keys +[ssh-passphrases]: /ssh-key-passphrases/ [autolaunch-ssh-agent]: /github/authenticating-to-github/working-with-ssh-key-passphrases#auto-launching-ssh-agent-on-git-for-windows diff --git a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md index 83686ec401..f98ec58b61 100644 --- a/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md +++ b/translations/pt-BR/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md @@ -3,8 +3,8 @@ title: Webhook events and payloads intro: 'For each webhook event, you can review when the event occurs, an example payload, and descriptions about the payload object parameters.' product: '{% data reusables.gated-features.enterprise_account_webhooks %}' redirect_from: - - /early-access/integrations/webhooks/ - - /v3/activity/events/types/ + - /early-access/integrations/webhooks + - /v3/activity/events/types - /webhooks/event-payloads - /developers/webhooks-and-events/webhook-events-and-payloads versions: @@ -1197,8 +1197,9 @@ Key | Type | Description {% ifversion fpt or ghes or ghec %} ## security_advisory -Activity related to a security advisory. A security advisory provides information about security-related vulnerabilities in software on GitHub. The security advisory dataset also powers the GitHub security alerts, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)." -{% endif %} +Activity related to a security advisory that has been reviewed by {% data variables.product.company_short %}. A {% data variables.product.company_short %}-reviewed security advisory provides information about security-related vulnerabilities in software on {% data variables.product.prodname_dotcom %}. + +The security advisory dataset also powers the GitHub {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)." ### Availability @@ -1215,6 +1216,8 @@ Key | Type | Description {{ webhookPayloadsForCurrentVersion.security_advisory.published }} +{% endif %} + {% ifversion fpt or ghec %} ## sponsorship diff --git a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md index d5f630fad6..1470bba1bc 100644 --- a/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md +++ b/translations/pt-BR/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md @@ -1,60 +1,60 @@ --- -title: Sobre discussões -intro: 'Use discussões para fazer e responder perguntas, compartilhar informações, fazer anúncios e conduzir ou participar de uma conversa sobre um projeto em {% data variables.product.product_name %}.' +title: About discussions +intro: 'Use discussions to ask and answer questions, share information, make announcements, and conduct or participate in a conversation about a project on {% data variables.product.product_name %}.' versions: fpt: '*' ghec: '*' --- -## Sobre o {% data variables.product.prodname_discussions %} +## About {% data variables.product.prodname_discussions %} -Com {% data variables.product.prodname_discussions %}, a comunidade para o seu projeto pode criar e participar de conversas no repositório do projeto. As discussões capacitam os mantenedores, contribuidores e visitantes para reunirem e atingirem os objetivos seguintes em um local central, sem ferramentas de terceiros. +With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools. -- Compartilhar anúncios e informações, recolher feedback, planejar e tomar decisões -- Faça perguntas, discuta e responda às perguntas, e marque as discussões como respondidas -- Promova uma atmosfera convidativa para visitantes e contribuidores para discutir objetivos, desenvolvimento, administração e fluxos de trabalho +- Share announcements and information, gather feedback, plan, and make decisions +- Ask questions, discuss and answer the questions, and mark the discussions as answered +- Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows -![Aba de discussões para um repositório](/assets/images/help/discussions/hero.png) +![Discussions tab for a repository](/assets/images/help/discussions/hero.png) -Você não precisa fechar uma discussão como você fecha um problema ou um pull request. +You don't need to close a discussion like you close an issue or a pull request. -Se um administrador de repositório ou mantenedor do projeto habilitar {% data variables.product.prodname_discussions %} para um repositório, qualquer pessoa que visitar o repositório poderá criar e participar de discussões do repositório. Os administradores de repositório e mantenedores de projetos podem gerenciar as discussões e categorias de discussão em um repositório e fixar discussões para aumentar a visibilidade da discussão. Os moderadores e colaboradores podem marcar comentários como respostas, travar discussões e converter problemas em discussões. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -Para obter mais informações sobre o gerenciamento de discussões para o repositório, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)". +For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)." -## Sobre a organização de discussão +## About discussion organization -Você pode organizar discussões com categorias e etiquetas. +You can organize discussions with categories and labels. {% data reusables.discussions.you-can-categorize-discussions %} {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.repository-category-limit %} -Para discussões com um formato de pergunta/resposta, é possível marcar um comentário individual dentro da discussão como a resposta da discussão. {% data reusables.discussions.github-recognizes-members %} +For discussions with a question/answer format, an individual comment within the discussion can be marked as the discussion's answer. {% data reusables.discussions.github-recognizes-members %} {% data reusables.discussions.about-announcement-format %} -Para obter mais informações, consulte "[Gerenciar categorias para discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)". +For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)." {% data reusables.discussions.you-can-label-discussions %} -## Práticas recomendadas para {% data variables.product.prodname_discussions %} +## Best practices for {% data variables.product.prodname_discussions %} -Como integrante ou mantenedor da comunidade, inicie uma discussão para fazer uma pergunta ou discutir informações que afetem a comunidade. Para obter mais informações, consulte "[Colaborar com mantenedores usando as discussões](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)". +As a community member or maintainer, start a discussion to ask a question or discuss information that affects the community. For more information, see "[Collaborating with maintainers using discussions](/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions)." -Participe de uma discussão para fazer e responder a perguntas, fornecer feedback e envolver-se com a comunidade do projeto. Para obter mais informações, consulte "[Participar de uma discussão](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)". +Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)." -Você pode destacar discussões que contenham conversas importantes, úteis ou exemplares entre os integrantes da comunidade. Para obter mais informações, consulte "[Gerenciar discussões no seu repositório](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)". +You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)." -{% data reusables.discussions.you-can-convert-an-issue %} Para obter mais informações, consulte "[Moderar discussões no seu repositório](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)". +{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)." -## Compartilhando feedback +## Sharing feedback -Você pode compartilhar seus comentários sobre {% data variables.product.prodname_discussions %} com {% data variables.product.company_short %}. Para se juntar à conversa, consulte [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). +You can share your feedback about {% data variables.product.prodname_discussions %} with {% data variables.product.company_short %}. To join the conversation, see [`github/feedback`](https://github.com/github/feedback/discussions?discussions_q=category%3A%22Discussions+Feedback%22). -## Leia mais +## Further reading -- "[Sobre escrita e formatação em {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" -- "[Pesquisar discussões](/search-github/searching-on-github/searching-discussions)" -- "[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" -- "[Moderar comentários e conversas](/communities/moderating-comments-and-conversations)" -- "[Mantendo sua segurança no {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" +- "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)" +- "[Searching discussions](/search-github/searching-on-github/searching-discussions)" +- "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" +- "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)" +- "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)" diff --git a/translations/pt-BR/content/get-started/index.md b/translations/pt-BR/content/get-started/index.md index 8917ef270e..8131599b42 100644 --- a/translations/pt-BR/content/get-started/index.md +++ b/translations/pt-BR/content/get-started/index.md @@ -37,6 +37,7 @@ featuredLinks: - /github/getting-started-with-github/signing-up-for-a-new-github-account - /get-started/quickstart/hello-world - /github/getting-started-with-github/set-up-git + - /get-started/learning-about-github/about-versions-of-github-docs - /github/getting-started-with-github/github-glossary - /github/getting-started-with-github/fork-a-repo - /github/getting-started-with-github/keyboard-shortcuts diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md new file mode 100644 index 0000000000..71486683c9 --- /dev/null +++ b/translations/pt-BR/content/get-started/learning-about-github/about-versions-of-github-docs.md @@ -0,0 +1,56 @@ +--- +title: About versions of GitHub Docs +intro: "You can read documentation that reflects the {% data variables.product.company_short %} product you're currently using." +versions: '*' +shortTitle: Docs versions +--- + +## About versions of {% data variables.product.prodname_docs %} + +{% data variables.product.company_short %} offers different products for storing and collaborating on code. The product you use determines which features are available to you. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)." + +This website, {% data variables.product.prodname_docs %}, provides documentation for all of {% data variables.product.company_short %}'s products. If the content you're reading applies to more than one product, you can choose the version of the documentation that's relevant to you by selecting the product you're currently using. + +At the top of a page on {% data variables.product.prodname_docs %}, select the dropdown menu and click a product. If your browser window is not wide enough to display the full navigation bar, you may need to click {% octicon "three-bars" aria-label="The three bars icon" %} first. + +![Screenshot of the dropdown menu for picking a version of {% data variables.product.prodname_docs %} to view](/assets/images/help/docs/version-picker.png) + +{% note %} + +**Note**: You can try changing the version now. You're viewing {% ifversion ghes %}a{% else %}the{% endif %} {% ifversion fpt %}Free, Pro, & Team{% else %}{% data variables.product.product_name %}{% endif %} version of this article. + +{% endnote %} + +## Determining which {% data variables.product.company_short %} product you use + +You can determine which {% data variables.product.company_short %} product you're currently using by reviewing the URL in the address bar of your browser and the heading for the {% data variables.product.prodname_dotcom %} website you're on. + +You may use more than one {% data variables.product.company_short %} product. For example, you might contribute to open source on {% data variables.product.prodname_dotcom_the_website %} and collaborate on code on your employer's {% data variables.product.prodname_ghe_server %} instance. You may need to view different versions of the same article at different times, depending on the problem you're currently trying to solve. + +### {% data variables.product.prodname_dotcom_the_website %} plans or {% data variables.product.prodname_ghe_cloud %} + +If you access {% data variables.product.prodname_dotcom %} at https://github.com, you're either using the features of a Free, Pro, or Team plan, or you're using {% data variables.product.prodname_ghe_cloud %}. + +In a wide browser window, there is no text that immediately follows the {% data variables.product.company_short %} logo on the left side of the header. + +![Screenshot of the address bar and the {% data variables.product.prodname_dotcom_the_website %} header in a browser](/assets/images/help/docs/header-dotcom.png) + +On {% data variables.product.prodname_dotcom_the_website %}, each account has its own plan. Each personal account has an associated plan that provides access to certain features, and each organization has a different associated plan. If your personal account is a member of an organization on {% data variables.product.prodname_dotcom_the_website %}, you may have access to different features when you use resources owned by that organization than when you use resources owned by your personal account. For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." + +If you don't know whether an organization uses {% data variables.product.prodname_ghe_cloud %}, ask an organization owner. For more information, see "[Viewing people's roles in an organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization)." + +### {% data variables.product.prodname_ghe_server %} + +If you access {% data variables.product.prodname_dotcom %} at a URL other than https://github.com, `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_server %}. For example, you may access {% data variables.product.prodname_ghe_server %} at `https://github.YOUR-COMPANY-NAME.com`. Your administrators may choose a URL that doesn't include the word "{% data variables.product.company_short %}." + +In a wide browser window, the word "Enterprise" immediately follows the {% data variables.product.company_short %} logo on the left side of the header. + +![Screenshot of address bar and {% data variables.product.prodname_ghe_server %} header in a browser](/assets/images/help/docs/header-ghes.png) + +### {% data variables.product.prodname_ghe_managed %} + +If you access {% data variables.product.prodname_dotcom %} at `https://*.githubenterprise.com`, `https://*.github.us`, or `https://*.ghe.com`, you're using {% data variables.product.prodname_ghe_managed %}. + +In a wide browser window, the words "{% data variables.product.prodname_ghe_managed %}" immediately follow the {% data variables.product.company_short %} logo in the header. + +![Address bar and {% data variables.product.prodname_ghe_managed %} header in a browser](/assets/images/help/docs/header-ghae.png) diff --git a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md index c5927d487d..a45107bd4c 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md +++ b/translations/pt-BR/content/get-started/learning-about-github/githubs-products.md @@ -24,6 +24,8 @@ topics: You can see pricing and a full list of features for each product at <{% data variables.product.pricing_url %}>. {% data reusables.products.product-roadmap %} +When you read {% data variables.product.prodname_docs %}, make sure to select the version that reflects your product. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." + ## {% data variables.product.prodname_free_user %} for user accounts With {% data variables.product.prodname_free_team %} for user accounts, you can work with unlimited collaborators on unlimited public repositories with a full feature set, and on unlimited private repositories with a limited feature set. diff --git a/translations/pt-BR/content/get-started/learning-about-github/index.md b/translations/pt-BR/content/get-started/learning-about-github/index.md index 32d67d6de5..5861d232ae 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/index.md +++ b/translations/pt-BR/content/get-started/learning-about-github/index.md @@ -17,10 +17,11 @@ topics: - Security children: - /githubs-products + - /about-versions-of-github-docs - /github-language-support - - /about-github-advanced-security - /types-of-github-accounts - /access-permissions-on-github + - /about-github-advanced-security - /faq-about-changes-to-githubs-plans --- diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md index 34adcc9fcb..013ac1a1af 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-ae.md @@ -73,8 +73,11 @@ For more information on enabling and configuring {% data variables.product.prodn ## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Learning with {% data variables.product.prodname_learning %} +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." + +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index d8227e1740..9598e02d65 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -199,14 +199,18 @@ Members of your organization or enterprise can use tools from the {% data variab ## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community. -### 1. Learning with {% data variables.product.prodname_learning %} + +### 1. Reading about {% data variables.product.prodname_ghe_cloud %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." + +### 2. Learning with {% data variables.product.prodname_learning %} Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." -### 2. Supporting the open source community +### 3. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 3. Contacting {% data variables.contact.github_support %} +### 4. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} {% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)." diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 6022968de4..4637e3b623 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -114,7 +114,13 @@ If you are the owner of both a {% data variables.product.product_name %} instanc ## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.product.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support. -### 1. Learning with {% data variables.product.prodname_learning %} + +### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} + +You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." + +### 2. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab-enterprise %} -### 2. Working with {% data variables.product.prodname_dotcom %} Enterprise Support + +### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md index f98c11638d..27e6ee5e6a 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-github-team.md @@ -83,13 +83,16 @@ You can help to make your organization more secure by recommending or requiring ### 2. Interacting with the {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Reading about {% data variables.product.prodname_team %} on {% data variables.product.prodname_docs %} +You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." + +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} -### 4. Supporting the open source community +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 5. Contacting {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} ## Further reading diff --git a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md index 8c5c1036a1..245a75c61f 100644 --- a/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/pt-BR/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -182,14 +182,18 @@ For more information, see "[Securing your software supply chain](/code-security/ ### 2. Interacting with {% data variables.product.prodname_gcf %} {% data reusables.support.ask-and-answer-forum %} -### 3. Learning with {% data variables.product.prodname_learning %} +### 3. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %} + +{% data reusables.docs.you-can-read-docs-for-your-product %} + +### 4. Learning with {% data variables.product.prodname_learning %} {% data reusables.getting-started.learning-lab %} {% ifversion fpt or ghec %} -### 4. Supporting the open source community +### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} -### 5. Contacting {% data variables.contact.github_support %} +### 6. Contacting {% data variables.contact.github_support %} {% data reusables.getting-started.contact-support %} {% ifversion fpt %} diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md index 0a60c0a9d2..f5c9633c79 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md @@ -56,6 +56,8 @@ Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/). +{% data reusables.docs.you-can-read-docs-for-your-product %} + {% data reusables.products.product-roadmap %} ## Finishing your trial diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 6b47866c00..1328f54580 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -41,6 +41,7 @@ To get the most out of your trial, follow these steps: - [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast - [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides - [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides + - "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)" 3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)." 4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)." 5. Invite an unlimited number of people to join your trial. diff --git a/translations/pt-BR/content/issues/index.md b/translations/pt-BR/content/issues/index.md index fe53b6ab0b..7b78e0992a 100644 --- a/translations/pt-BR/content/issues/index.md +++ b/translations/pt-BR/content/issues/index.md @@ -1,7 +1,7 @@ --- -title: Problemas do GitHub -shortTitle: Problemas do GitHub -intro: 'Saiba como usar {% data variables.product.prodname_github_issues %} para planejar e acompanhar seu trabalho.' +title: GitHub Issues +shortTitle: GitHub Issues +intro: 'Learn how you can use {% data variables.product.prodname_github_issues %} to plan and track your work.' introLinks: overview: /issues/tracking-your-work-with-issues/creating-issues/about-issues quickstart: /issues/tracking-your-work-with-issues/quickstart @@ -44,9 +44,9 @@ redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests - /github/managing-your-work-on-github/managing-your-work-with-issues - /github/managing-your-work-on-github - - /categories/100/articles/ - - /categories/managing-projects/ - - /categories/managing-projects-on-github/ + - /categories/100/articles + - /categories/managing-projects + - /categories/managing-projects-on-github - /categories/managing-your-work-on-github - /about-issues - /creating-an-issue diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md index 92a994f5d0..833004a4f8 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md @@ -1,9 +1,9 @@ --- -title: Sobre quadros de projeto -intro: 'Os quadros de projeto no {% data variables.product.product_name %} ajudam você a organizar e priorizar seu trabalho. É possível criar quadros de projeto para trabalho de recurso específico, roteiros abrangentes ou, até mesmo, checklists de versão. Com os quadros de projeto, você tem a flexibilidade de criar fluxos de trabalho personalizados adequados às suas necessidades.' +title: About project boards +intro: 'Project boards on {% data variables.product.product_name %} help you organize and prioritize your work. You can create project boards for specific feature work, comprehensive roadmaps, or even release checklists. With project boards, you have the flexibility to create customized workflows that suit your needs.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/about-project-boards - - /articles/about-projects/ + - /articles/about-projects - /articles/about-project-boards - /github/managing-your-work-on-github/about-project-boards versions: @@ -17,58 +17,58 @@ topics: {% data reusables.projects.project_boards_old %} -Os quadros de projeto são compostos por problemas, pull requests e observações que são categorizados como cartões em colunas de sua escolha. É possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões em uma coluna, mover cartões de coluna para coluna e alterar a ordem das colunas. +Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can drag and drop or use keyboard shortcuts to reorder cards within a column, move cards from column to column, and change the order of columns. -Os cartões do quadro de projeto contêm metadados relevantes para problemas e pull requests, como etiquetas, responsáveis, o status e quem os abriu. {% data reusables.project-management.edit-in-project %} +Project board cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %} -Você pode criar observações dentro de colunas para servirem de lembretes de tarefa, fazer referência a problemas e pull requests de qualquer repositório no {% data variables.product.product_location %} ou adicionar informações relacionadas ao quadro de projeto. É possível criar um cartão de referência para outro quadro de projeto adicionando um link a uma observação. Se a observação não for suficiente para suas necessidades, você poderá convertê-la em um problema. Para obter mais informações sobre como converter observações de quadro de projeto em problemas, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)". +You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the project board. You can create a reference card for another project board by adding a link to a note. If the note isn't sufficient for your needs, you can convert it to an issue. For more information on converting project board notes to issues, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." -Tipos de quadros de projeto: +Types of project boards: -- Os **quadros de projeto possuídos pelo usuário** podem conter problemas e pull requests de qualquer repositório pessoal. -- Os **quadros de projeto de toda a organização** podem conter problemas e pull requests de qualquer repositório que pertença a uma organização. {% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)." -- Os **quadros de projeto do repositório** abrangem problemas ou pull requests dentro de um único repositório. Eles também podem incluir observações que fazem referência a problemas e pull requests em outros repositórios. +- **User-owned project boards** can contain issues and pull requests from any personal repository. +- **Organization-wide project boards** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." +- **Repository project boards** are scoped to issues and pull requests within a single repository. They can also include notes that reference issues and pull requests in other repositories. -## Criar e exibir quadros de projeto +## Creating and viewing project boards -Para criar um quadro de projeto para sua organização, você deve ser um integrante da organização. Os proprietários da organização e as pessoas com permissões de administrador de quadro de projeto podem personalizar o acesso ao quadro de projeto. +To create a project board for your organization, you must be an organization member. Organization owners and people with project board admin permissions can customize access to the project board. -Se um quadro de projeto possuído pela organização incluir problemas ou pull requests de um repositório que você não tem permissão para exibir, o cartão será removido. Para obter mais informações, consulte "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)". +If an organization-owned project board includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)." -A exibição da atividade mostra o histórico recente do quadro de projeto, como cartões que alguém criou ou moveu entre colunas. Para acessar a exibição da atividade, clique em **Menu** e role para baixo. +The activity view shows the project board's recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down. -Para encontrar cartões específicos em um quadro de projeto ou exibir um subconjunto dos cartões, você pode filtrar cartões do quadro de projeto. Para obter mais informações, consulte "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)". +To find specific cards on a project board or view a subset of the cards, you can filter project board cards. For more information, see "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)." -Para simplificar seu fluxo de trabalho a manter as tarefas concluídas fora do quadro de projeto, você pode arquivar cartões. Para obter mais informações, consulte "[Arquivar cartões em um quadro de projeto](/articles/archiving-cards-on-a-project-board)." +To simplify your workflow and keep completed tasks off your project board, you can archive cards. For more information, see "[Archiving cards on a project board](/articles/archiving-cards-on-a-project-board)." -Se você concluiu todas as tarefas do quadro de projeto ou não precisar mais usar o quadro de projeto, é possível fechá-lo. Para obter mais informações, consulte "[Fechar um quadro de projeto](/articles/closing-a-project-board)". +If you've completed all of your project board tasks or no longer need to use your project board, you can close the project board. For more information, see "[Closing a project board](/articles/closing-a-project-board)." -Também é possível [desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository) ou [desabilitar quadros de projeto em sua organização](/articles/disabling-project-boards-in-your-organization), se preferir rastrear o trabalho de maneira diferente. +You can also [disable project boards in a repository](/articles/disabling-project-boards-in-a-repository) or [disable project boards in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way. {% data reusables.project-management.project-board-import-with-api %} -## Modelos para quadros de projeto +## Templates for project boards -É possível usar modelos para configurar rapidamente um novo quadro de projeto. Quando você usar um modelo para criar um quadro de projeto, o novo quadro incluirá colunas, bem como cartões com dicas para usar quadros de projeto. Você também pode escolher um modelo com automação já configurada. +You can use templates to quickly set up a new project board. When you use a template to create a project board, your new board will include columns as well as cards with tips for using project boards. You can also choose a template with automation already configured. -| Modelo | Descrição | -| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Kanban básico | Rastreie tarefas com colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas) | -| Kanban automatizado | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídas) | -| Kanban automatizado com revisão | Cartões são movidos automaticamente entre as colunas To do (Pendentes), In progress (Em andamento) e Done (Concluídos), com gatilhos adicionais para status de revisão de pull request | -| Triagem de erros | Faça a triagem e priorize erros com as colunas To do (Pendentes), High priority (Prioridade alta), Low priority (Prioridade baixa) e Closed (Fechados) | +| Template | Description | +| --- | --- | +| Basic kanban | Track your tasks with To do, In progress, and Done columns | +| Automated kanban | Cards automatically move between To do, In progress, and Done columns | +| Automated kanban with review | Cards automatically move between To do, In progress, and Done columns, with additional triggers for pull request review status | +| Bug triage | Triage and prioritize bugs with To do, High priority, Low priority, and Closed columns | -Para obter mais informações sobre automação para quadros de projeto, consulte "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)". +For more information on automation for project boards, see "[About automation for project boards](/articles/about-automation-for-project-boards)." -![Quadro de projeto com modelo de kanban básico](/assets/images/help/projects/project-board-basic-kanban-template.png) +![Project board with basic kanban template](/assets/images/help/projects/project-board-basic-kanban-template.png) {% data reusables.project-management.copy-project-boards %} -## Leia mais +## Further reading -- "[Criar um quadro de projeto](/articles/creating-a-project-board)" -- "[Editar um quadro de projeto](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} -- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %} -- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" -- "[Atalhos de teclado](/articles/keyboard-shortcuts/#project-boards)" +- "[Creating a project board](/articles/creating-a-project-board)" +- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" +- "[Keyboard shortcuts](/articles/keyboard-shortcuts/#project-boards)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md index 85ec52b1d2..868b241f59 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board.md @@ -1,9 +1,9 @@ --- -title: Fechar um quadro de projeto -intro: 'Se você concluiu todas as tarefas em um quadro de projeto ou não precisa mais usar um quadro de projeto, é possível fechá-lo.' +title: Closing a project board +intro: 'If you''ve completed all the tasks in a project board or no longer need to use a project board, you can close the project board.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board - - /articles/closing-a-project/ + - /articles/closing-a-project - /articles/closing-a-project-board - /github/managing-your-work-on-github/closing-a-project-board versions: @@ -14,21 +14,22 @@ versions: topics: - Pull requests --- - {% data reusables.projects.project_boards_old %} -Quando você fecha um quadro de projeto, qualquer automação de fluxo de trabalho configurada é pausada por padrão. +When you close a project board, any configured workflow automation will pause by default. -Se você reabrir um quadro de projeto, existirá a opção de *sincronizar* a automação, o que atualiza a posição dos cartões no quadro de acordo com as configurações de automação definidas para o quadro. Para obter mais informações, consulte "[Reabrir um quadro de projeto fechado](/articles/reopening-a-closed-project-board)" ou "[Sobre automação para quadros de projeto](/articles/about-automation-for-project-boards)". +If you reopen a project board, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed project board](/articles/reopening-a-closed-project-board)" or "[About automation for project boards](/articles/about-automation-for-project-boards)." -1. Navegue para a lista de quadros de projetos no seu repositório ou organização, ou pertencente à sua conta de usuário. -2. Na lista de projetos, ao lado do quadro de projeto que deseja fechar, clique em {% octicon "chevron-down" aria-label="The chevron icon" %}. ![Ícone de divisa à direita do nome do quadro de projeto](/assets/images/help/projects/project-list-action-chevron.png) -3. Clique em **Fechar**. ![Menu suspenso para fechar item no quadro de projeto](/assets/images/help/projects/close-project.png) +1. Navigate to list of project boards in your repository or organization, or owned by your user account. +2. In the projects list, next to the project board you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}. +![Chevron icon to the right of the project board's name](/assets/images/help/projects/project-list-action-chevron.png) +3. Click **Close**. +![Close item in the project board's drop-down menu](/assets/images/help/projects/close-project.png) -## Leia mais +## Further reading -- "[Sobre quadros de projetos](/articles/about-project-boards)" -- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)" -- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)" -- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)" -- "[Permissões de quadro de projeto para uma organização](/articles/project-board-permissions-for-an-organization)" +- "[About project boards](/articles/about-project-boards)" +- "[Deleting a project board](/articles/deleting-a-project-board)" +- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)" +- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)" +- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md index 91d0dbf116..712cb6f12d 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md @@ -1,9 +1,9 @@ --- -title: Criar um quadro de projeto -intro: 'Os quadros de projeto podem ser usados para criar fluxos de trabalho personalizados adequados às suas necessidades, como rastreamento e priorização de trabalho de recursos específicos, roteiros abrangentes ou, até mesmo, checklists de versão.' +title: Creating a project board +intro: 'Project boards can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.' redirect_from: - /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board - - /articles/creating-a-project/ + - /articles/creating-a-project - /articles/creating-a-project-board - /github/managing-your-work-on-github/creating-a-project-board versions: @@ -18,25 +18,25 @@ topics: - Project management type: how_to --- - {% data reusables.projects.project_boards_old %} {% data reusables.project-management.use-automated-template %} {% data reusables.project-management.copy-project-boards %} -{% data reusables.project-management.link-repos-to-project-board %} Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)." +{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." -Após a criação do quadro de projeto, você poderá adicionar a ele problemas, pull requests e observações. Para obter mais informações, consulte "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" e "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)". +Once you've created your project board, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." -Também é possível configurar automações de fluxo de trabalho para manter seu quadro de projeto em sincronia com o status de problemas e pull requests. Para obter mais informações, consulte "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)". +You can also configure workflow automations to keep your project board in sync with the status of issues and pull requests. For more information, see "[About automation for project boards](/articles/about-automation-for-project-boards)." {% data reusables.project-management.project-board-import-with-api %} -## Criar um quadro de projeto de propriedade do usuário +## Creating a user-owned project board {% data reusables.profile.access_profile %} -2. No topa da página do seu perfil, na navegação principal, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/user-projects-tab.png) +2. On the top of your profile page, in the main navigation, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/user-projects-tab.png) {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} @@ -52,7 +52,7 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.edit-project-columns %} -## Criar um quadro de projeto em toda a organização +## Creating an organization-wide project board {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} @@ -72,10 +72,11 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.edit-project-columns %} -## Criar um quadro de projeto de repositório +## Creating a repository project board {% data reusables.repositories.navigate-to-repo %} -2. Abaixo do nome do repositório, clique em {% octicon "project" aria-label="The project board icon" %} **Projects** (Projetos). ![Aba Project (Projeto)](/assets/images/help/projects/repo-tabs-projects.png) +2. Under your repository name, click {% octicon "project" aria-label="The project board icon" %} **Projects**. +![Project tab](/assets/images/help/projects/repo-tabs-projects.png) {% data reusables.project-management.click-new-project %} {% data reusables.project-management.create-project-name-description %} {% data reusables.project-management.choose-template %} @@ -89,10 +90,10 @@ Também é possível configurar automações de fluxo de trabalho para manter se {% data reusables.project-management.edit-project-columns %} -## Leia mais +## Further reading -- "[Sobre quadros de projetos](/articles/about-project-boards)" -- "[Editar um quadro de projeto](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} -- "[Copiar um quadro de projeto](/articles/copying-a-project-board)"{% endif %} -- "[Fechar um quadro de projeto](/articles/closing-a-project-board)" -- "[Sobre a automação para quadros de projeto](/articles/about-automation-for-project-boards)" +- "[About projects boards](/articles/about-project-boards)" +- "[Editing a project board](/articles/editing-a-project-board)"{% ifversion fpt or ghec %} +- "[Copying a project board](/articles/copying-a-project-board)"{% endif %} +- "[Closing a project board](/articles/closing-a-project-board)" +- "[About automation for project boards](/articles/about-automation-for-project-boards)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md index 0905fe82b9..1c13437734 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board.md @@ -1,9 +1,9 @@ --- -title: Excluir um quadro de projeto -intro: Você pode excluir um quadro de projeto existente se já não precisa mais ter acesso ao conteúdo dele. +title: Deleting a project board +intro: You can delete an existing project board if you no longer need access to its contents. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board - - /articles/deleting-a-project/ + - /articles/deleting-a-project - /articles/deleting-a-project-board - /github/managing-your-work-on-github/deleting-a-project-board versions: @@ -14,23 +14,23 @@ versions: topics: - Pull requests --- - {% data reusables.projects.project_boards_old %} {% tip %} -**Dica**: para manter o acesso a um quadro de projeto concluído ou desnecessário sem perder o acesso ao conteúdo dele, [feche o quadro de projeto](/articles/closing-a-project-board) em vez de excluí-lo. +**Tip**: If you'd like to retain access to a completed or unneeded project board without losing access to its contents, you can [close the project board](/articles/closing-a-project-board) instead of deleting it. {% endtip %} -1. Navegue até o quadro de projeto que deseja excluir. +1. Navigate to the project board you want to delete. {% data reusables.project-management.click-menu %} {% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Clique em **Delete project** (Excluir projeto). ![Botão Delete project (Excluir projeto)](/assets/images/help/projects/delete-project-button.png) -5. Para confirmar que você deseja excluir o quadro de projeto, clique em **OK**. +4. Click **Delete project**. +![Delete project button](/assets/images/help/projects/delete-project-button.png) +5. To confirm that you want to delete the project board, click **OK**. -## Leia mais +## Further reading -- "[Fechar um quadro de projeto](/articles/closing-a-project-board)" -- "[Desabilitar quadros de projeto em um repositório](/articles/disabling-project-boards-in-a-repository)" -- "[Desabilitar quadros de projeto na sua organização](/articles/disabling-project-boards-in-your-organization)" +- "[Closing a project board](/articles/closing-a-project-board)" +- "[Disabling project boards in a repository](/articles/disabling-project-boards-in-a-repository)" +- "[Disabling project boards in your organization](/articles/disabling-project-boards-in-your-organization)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md index c7fff0797b..e80b1eec6e 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board.md @@ -1,10 +1,10 @@ --- -title: Editar um quadro de projeto -intro: Você pode editar o título e a descrição de um quadro de projeto existente. +title: Editing a project board +intro: You can edit the title and description of an existing project board. redirect_from: - /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board - - /articles/editing-a-project/ - - /articles/editing-and-deleting-a-project/ + - /articles/editing-a-project + - /articles/editing-and-deleting-a-project - /articles/editing-a-project-board - /github/managing-your-work-on-github/editing-a-project-board versions: @@ -15,22 +15,22 @@ versions: topics: - Pull requests --- - {% data reusables.projects.project_boards_old %} {% tip %} -**Dica:** para ver detalhes sobre como adicionar, remover ou editar colunas no quadro de projeto, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)". +**Tip:** For details on adding, removing, or editing columns in your project board, see "[Creating a project board](/articles/creating-a-project-board)." {% endtip %} -1. Navegue até o quadro de projeto que deseja editar. +1. Navigate to the project board you want to edit. {% data reusables.project-management.click-menu %} -{% data reusables.project-management.click-edit-sidebar-menu-project-board %} -4. Modifique o nome e a descrição do quadro de projeto conforme necessário e clique em **Save project** (Salvar projeto). ![Campos com o nome e a descrição do quadro de projeto e o botão Save project (Salvar projeto)](/assets/images/help/projects/edit-project-board-save-button.png) +{% data reusables.project-management.click-edit-sidebar-menu-project-board %} +4. Modify the project board name and description as needed, then click **Save project**. +![Fields with the project board name and description, and Save project button](/assets/images/help/projects/edit-project-board-save-button.png) -## Leia mais +## Further reading -- "[Sobre quadros de projetos](/articles/about-project-boards)" -- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" -- "[Excluir um quadro de projeto](/articles/deleting-a-project-board)" +- "[About project boards](/articles/about-project-boards)" +- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[Deleting a project board](/articles/deleting-a-project-board)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md index 8df565cf5a..6c67376231 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board.md @@ -1,9 +1,9 @@ --- -title: Adicionar problemas e pull requests a um quadro de projeto -intro: Você pode adicionar problemas e pull requests a um quadro de projeto na forma de cartões e fazer a triagem deles em colunas. +title: Adding issues and pull requests to a project board +intro: You can add issues and pull requests to a project board in the form of cards and triage them into columns. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board - - /articles/adding-issues-and-pull-requests-to-a-project/ + - /articles/adding-issues-and-pull-requests-to-a-project - /articles/adding-issues-and-pull-requests-to-a-project-board - /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board versions: @@ -13,61 +13,67 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Adicionar issues & PRs ao quadro +shortTitle: Add issues & PRs to board --- - {% data reusables.projects.project_boards_old %} -Você pode adicionar cartões de problema ou pull request ao seu quadro de projeto ao: -- Arrastar os cartões da seção **Triage** (Triagem) na barra lateral. -- Digitar a URL do problema ou da pull request em um cartão. -- Pesquisar problemas ou pull requests na barra lateral de pesquisa do quadro de projeto. +You can add issue or pull request cards to your project board by: +- Dragging cards from the **Triage** section in the sidebar. +- Typing the issue or pull request URL in a card. +- Searching for issues or pull requests in the project board search sidebar. -É possível colocar 2.500 cartões, no máximo, em cada coluna do projeto. Se uma coluna atingir o número máximo de cartões, nenhum cartão poderá ser movido para essa coluna. +You can put a maximum of 2,500 cards into each project column. If a column has reached the maximum number of cards, no cards can be moved into that column. -![Cursor move cartão de problema da barra lateral de triagem para a coluna do quadro de projeto](/assets/images/help/projects/add-card-from-sidebar.gif) +![Cursor moves issue card from triaging sidebar to project board column](/assets/images/help/projects/add-card-from-sidebar.gif) {% note %} -**Observação:** também é possível adicionar observações ao seu quadro de projeto para que sirvam de lembretes de tarefas, referências a problemas e pull requests de qualquer repositório no {% data variables.product.product_name %} ou para adicionar informações relacionadas ao seu quadro de projeto. Para obter mais informações, consulte "[Adicionar observações a um quadro de projeto](/articles/adding-notes-to-a-project-board)". +**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your project board. For more information, see "[Adding notes to a project board](/articles/adding-notes-to-a-project-board)." {% endnote %} {% data reusables.project-management.edit-in-project %} -{% data reusables.project-management.link-repos-to-project-board %} Quando você pesquisa problemas ou pull requests para adicionar ao quadro de projeto, a pesquisa automaticamente é colocada no escopo de seus repositórios vinculados. É possível remover esses qualificadores para pesquisar em todos os repositórios da organização. Para obter mais informações, consulte "[Vincular um repositório a um quadro de projeto](/articles/linking-a-repository-to-a-project-board)". +{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your project board, the search automatically scopes to your linked repositories. You can remove these qualifiers to search within all organization repositories. For more information, see "[Linking a repository to a project board](/articles/linking-a-repository-to-a-project-board)." -## Adicionar problemas e pull requests a um quadro de projeto +## Adding issues and pull requests to a project board -1. Navegue até o quadro de projeto onde deseja adicionar problemas e pull requests. -2. No quadro de projeto, clique em {% octicon "plus" aria-label="The plus icon" %} **Add cards** (Adicionar cartões). ![Botão Add cards (Adicionar cartões)](/assets/images/help/projects/add-cards-button.png) -3. Pesquise problemas e pull requests para adicionar ao quadro de projeto usando qualificadores de pesquisa. Para obter mais informações sobre qualificadores de pesquisa que você pode usar, consulte [Pesquisar problemas](/articles/searching-issues)". ![Pesquisar problemas e pull requests](/assets/images/help/issues/issues_search_bar.png) +1. Navigate to the project board where you want to add issues and pull requests. +2. In your project board, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. +![Add cards button](/assets/images/help/projects/add-cards-button.png) +3. Search for issues and pull requests to add to your project board using search qualifiers. For more information on search qualifiers you can use, see "[Searching issues](/articles/searching-issues)." + ![Search issues and pull requests](/assets/images/help/issues/issues_search_bar.png) {% tip %} - **Dicas:** - - Também é possível adicionar um problema ou uma pull request digitando a URL em um cartão. - - Se estiver trabalhando em um recurso específico, você poderá aplicar uma etiqueta a cada pull request ou problema relacionado a esse recurso e, assim, adicionar facilmente cartões ao quadro de projeto pesquisando o nome da etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests)". + **Tips:** + - You can also add an issue or pull request by typing the URL in a card. + - If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your project board by searching for the label name. For more information, see "[Apply labels to issues and pull requests](/articles/applying-labels-to-issues-and-pull-requests)." {% endtip %} -4. Na lista filtrada de problemas e pull requests, arraste o cartão que deseja adicionar ao quadro de projeto e solte-o na coluna correta. Como alternativa, você pode mover cartões usando os atalhos de teclado. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} +4. From the filtered list of issues and pull requests, drag the card you'd like to add to your project board and drop it in the correct column. Alternatively, you can move cards using keyboard shortcuts. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} {% tip %} - **Dica:** é possível arrastar e soltar ou usar atalhos de teclado para reordenar cartões e movê-los entre colunas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} + **Tip:** You can drag and drop or use keyboard shortcuts to reorder cards and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} {% endtip %} -## Adicionar problemas e pull request a um quadro de projeto da barra lateral +## Adding issues and pull requests to a project board from the sidebar -1. No lado direito de um problema ou uma pull request, clique em **Projects (Projetos) {% octicon "gear" aria-label="The Gear icon" %}**. ![Botão Project board (Quadro de projeto) na barra lateral](/assets/images/help/projects/sidebar-project.png) -2. Clique na aba **Recent** (Recente), **Repository** (Repositório), **User** (Usuário) ou **Organization** (Organização) do quadro de projeto ao qual deseja adicionar. ![Guias Recent (Recente), Repository (Repositório) e Organization (Organização)](/assets/images/help/projects/sidebar-project-tabs.png) -3. Digite o nome do projeto no campo **Filter projects** (Filtrar projetos). ![Caixa de pesquisa Project board (Quadro de projeto)](/assets/images/help/projects/sidebar-search-project.png) -4. Selecione um ou mais quadros de projeto ao qual você deseja adicionar o problema ou pull request. ![Quadro de projeto selecionado](/assets/images/help/projects/sidebar-select-project.png) -5. Clique em {% octicon "triangle-down" aria-label="The down triangle icon" %} e depois na coluna onde você quer seu problema ou pull request. O cartão irá para a parte inferior da coluna do quadro de projeto que você selecionou. ![Menu Move card to column (Mover cartão para coluna)](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) +1. On the right side of an issue or pull request, click **Projects {% octicon "gear" aria-label="The Gear icon" %}**. + ![Project board button in sidebar](/assets/images/help/projects/sidebar-project.png) +2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the project board you would like to add to. + ![Recent, Repository and Organization tabs](/assets/images/help/projects/sidebar-project-tabs.png) +3. Type the name of the project in **Filter projects** field. + ![Project board search box](/assets/images/help/projects/sidebar-search-project.png) +4. Select one or more project boards where you want to add the issue or pull request. + ![Selected project board](/assets/images/help/projects/sidebar-select-project.png) +5. Click {% octicon "triangle-down" aria-label="The down triangle icon" %}, then click the column where you want your issue or pull request. The card will move to the bottom of the project board column you select. + ![Move card to column menu](/assets/images/help/projects/sidebar-select-project-board-column-menu.png) -## Leia mais +## Further reading -- "[Sobre quadros de projetos](/articles/about-project-boards)" -- "[Editar um quadro de projeto](/articles/editing-a-project-board)" -- "[Filtrar cartões em um quadro de projeto](/articles/filtering-cards-on-a-project-board)" +- "[About project boards](/articles/about-project-boards)" +- "[Editing a project board](/articles/editing-a-project-board)" +- "[Filtering cards on a project board](/articles/filtering-cards-on-a-project-board)" diff --git a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md index 1f25268108..2cf815d675 100644 --- a/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md +++ b/translations/pt-BR/content/issues/organizing-your-work-with-project-boards/tracking-work-with-project-boards/adding-notes-to-a-project-board.md @@ -1,9 +1,9 @@ --- -title: Adicionar observações a um quadro de projeto -intro: Você pode adicionar observações a um quadro de projeto para que sirvam como lembretes de tarefas ou para adicionar informações relacionadas ao quadro de projeto. +title: Adding notes to a project board +intro: You can add notes to a project board to serve as task reminders or to add information related to the project board. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board - - /articles/adding-notes-to-a-project/ + - /articles/adding-notes-to-a-project - /articles/adding-notes-to-a-project-board - /github/managing-your-work-on-github/adding-notes-to-a-project-board versions: @@ -13,66 +13,72 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Adicionar notas ao quadro +shortTitle: Add notes to board --- - {% data reusables.projects.project_boards_old %} {% tip %} -**Dicas:** -- É possível formatar a observação usando a sintaxe markdown. Por exemplo, você pode usar títulos, links, listas de tarefas ou emojis. Para obter mais informações, consulte "[Sintaxe básica de gravação e formatação](/articles/basic-writing-and-formatting-syntax)". -- Você pode arrastar e soltar ou usar atalhos de teclado para reordenar observações e movê-las entre colunas. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} -- Seu quadro de projeto deve ter pelo menos uma coluna para que seja possível adicionar observações. Para obter mais informações, consulte "[Criar um quadro de projeto](/articles/creating-a-project-board)". +**Tips:** +- You can format your note using Markdown syntax. For example, you can use headings, links, task lists, or emoji. For more information, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)." +- You can drag and drop or use keyboard shortcuts to reorder notes and move them between columns. {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %} +- Your project board must have at least one column before you can add notes. For more information, see "[Creating a project board](/articles/creating-a-project-board)." {% endtip %} -Ao adicionar a uma observação uma URL para um problema, uma pull request ou outro quadro de projeto, você vê uma visualização em um cartão de resumo abaixo do seu texto. +When you add a URL for an issue, pull request, or another project board to a note, you'll see a preview in a summary card below your text. -![Cartões de quadro de projeto mostrando a visualização de um problema e outro quadro de projeto](/assets/images/help/projects/note-with-summary-card.png) +![Project board cards showing a preview of an issue and another project board](/assets/images/help/projects/note-with-summary-card.png) -## Adicionar observações a um quadro de projeto +## Adding notes to a project board -1. Navegue até o quadro de projeto onde deseja adicionar observações. -2. Na coluna que deseja adicionar uma observação, clique em {% octicon "plus" aria-label="The plus icon" %}. ![Ícone de mais no header da coluna](/assets/images/help/projects/add-note-button.png) -3. Digite sua observação e clique em **Add** (Adicionar). ![Campo para digitar uma observação e botão Add card (Adicionar cartão)](/assets/images/help/projects/create-and-add-note-button.png) +1. Navigate to the project board where you want to add notes. +2. In the column you want to add a note to, click {% octicon "plus" aria-label="The plus icon" %}. +![Plus icon in the column header](/assets/images/help/projects/add-note-button.png) +3. Type your note, then click **Add**. +![Field for typing a note and Add card button](/assets/images/help/projects/create-and-add-note-button.png) {% tip %} - **Dica:** você pode fazer referência um problema ou uma pull request na observação digitando a respectiva URL no cartão. + **Tip:** You can reference an issue or pull request in your note by typing its URL in the card. {% endtip %} -## Converter uma observação em um problema +## Converting a note to an issue -Se você criou uma observação e achou que ela não é suficiente para as suas necessidades, é possível convertê-la em um problema. +If you've created a note and find that it isn't sufficient for your needs, you can convert it to an issue. -Quando você converte uma observação em um problema, o problema é criado automaticamente usando o conteúdo da observação. A primeira linha da observação será o título do problema e o conteúdo adicional da observação será adicionado à descrição do problema. +When you convert a note to an issue, the issue is automatically created using the content from the note. The first line of the note will be the issue title and any additional content from the note will be added to the issue description. {% tip %} -**Dica:** é possível adicionar conteúdo no texto da observação para fazer @menção a alguém, vinculá-la a outro problema ou pull request e adicionar emoji. Esses recursos markdown em estilo {% data variables.product.prodname_dotcom %} não são aceitos em observações do quadro de projeto, mas depois que a observação for convertida em um problema, ela será exibida corretamente. Para obter mais informações sobre o uso desses recursos, consulte "[Sobre escrita e formatação no {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)". +**Tip:** You can add content in the body of your note to @mention someone, link to another issue or pull request, and add emoji. These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within project board notes, but once your note is converted to an issue, they'll appear correctly. For more information on using these features, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." {% endtip %} -1. Navegue para a observação que deseja converter em um problema. +1. Navigate to the note that you want to convert to an issue. {% data reusables.project-management.project-note-more-options %} -3. Clique em **Convert to issue** (Converter em problema). ![Botão Convert to issue (Converter em problema)](/assets/images/help/projects/convert-to-issue.png) -4. Se o cartão estiver em um quadro de projeto em toda a organização, no menu suspenso, escolha o repositório ao qual deseja adicionar o problema. ![Menu suspenso listando repositórios onde é possível criar o problema](/assets/images/help/projects/convert-note-choose-repository.png) -5. Se desejar, edite o título do problema previamente preenchido e digite um texto para o problema. ![Campos para título e texto do problema](/assets/images/help/projects/convert-note-issue-title-body.png) -6. Clique em **Convert to issue** (Converter em problema). -7. A observação é convertida automaticamente em um problema. No quadro de projeto, o novo cartão de problema estará no mesmo local que a observação anterior. +3. Click **Convert to issue**. + ![Convert to issue button](/assets/images/help/projects/convert-to-issue.png) +4. If the card is on an organization-wide project board, in the drop-down menu, choose the repository you want to add the issue to. + ![Drop-down menu listing repositories where you can create the issue](/assets/images/help/projects/convert-note-choose-repository.png) +5. Optionally, edit the pre-filled issue title, and type an issue body. + ![Fields for issue title and body](/assets/images/help/projects/convert-note-issue-title-body.png) +6. Click **Convert to issue**. +7. The note is automatically converted to an issue. In the project board, the new issue card will be in the same location as the previous note. -## Editar e remover uma observação +## Editing and removing a note -1. Navegue para a observação que deseja editar ou remover. +1. Navigate to the note that you want to edit or remove. {% data reusables.project-management.project-note-more-options %} -3. Para editar o conteúdo da observação, clique em **Edit note** (Editar observação). ![Botão Edit note (Editar observação)](/assets/images/help/projects/edit-note.png) -4. Para excluir o conteúdo das observações, clique em **Delete note** (Excluir observação). ![Botão Delete note (Excluir observação)](/assets/images/help/projects/delete-note.png) +3. To edit the contents of the note, click **Edit note**. + ![Edit note button](/assets/images/help/projects/edit-note.png) +4. To delete the contents of the notes, click **Delete note**. + ![Delete note button](/assets/images/help/projects/delete-note.png) -## Leia mais +## Further reading -- "[Sobre quadros de projetos](/articles/about-project-boards)" -- "[Criar um quadro de projeto](/articles/creating-a-project-board)" -- "[Editar um quadro de projeto](/articles/editing-a-project-board)" -- "[Adicionar problemas e pull requests a um quadro de projeto](/articles/adding-issues-and-pull-requests-to-a-project-board)" +- "[About project boards](/articles/about-project-boards)" +- "[Creating a project board](/articles/creating-a-project-board)" +- "[Editing a project board](/articles/editing-a-project-board)" +- "[Adding issues and pull requests to a project board](/articles/adding-issues-and-pull-requests-to-a-project-board)" diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md index 8e13421983..ebd5ac6cf6 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/about-issues.md @@ -1,10 +1,10 @@ --- -title: Sobre problemas -intro: 'Use {% data variables.product.prodname_github_issues %} para rastrear ideias, comentários, tarefas ou erros para trabalho em {% data variables.product.company_short %}.' +title: About issues +intro: 'Use {% data variables.product.prodname_github_issues %} to track ideas, feedback, tasks, or bugs for work on {% data variables.product.company_short %}.' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/about-issues - - /articles/creating-issues/ - - /articles/about-issues/ + - /articles/creating-issues + - /articles/about-issues - /github/managing-your-work-on-github/about-issues - /issues/tracking-your-work-with-issues/creating-issues/about-issues versions: @@ -17,39 +17,38 @@ topics: - Issues - Project management --- +## Integrated with GitHub -## Integrado ao GitHub +Issues let you track your work on {% data variables.product.company_short %}, where development happens. When you mention an issue in another issue or pull request, the issue's timeline reflects the cross-reference so that you can keep track of related work. To indicate that work is in progress, you can link an issue to a pull request. When the pull request merges, the linked issue automatically closes. -Os problemas permitem que você acompanhe seu trabalho em {% data variables.product.company_short %}, onde o desenvolvimento acontece. Ao mencionar um problema em outro problema ou pull request, a linha do tempo do problema reflete a referência cruzada para que você possa acompanhar o trabalho relacionado. Para indicar que o trabalho está em andamento, você pode vincular um problema a um pull request. Quando o pull request faz merge, o problema vinculado é fechado automaticamente. +## Quickly create issues -## Crie problemas rapidamente +Issues can be created in a variety of ways, so you can choose the most convenient method for your workflow. For example, you can create an issue from a repository,{% ifversion fpt or ghec %} an item in a task list,{% endif %} a note in a project, a comment in an issue or pull request, a specific line of code, or a URL query. You can also create an issue from your platform of choice: through the web UI, {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL and REST APIs, or {% data variables.product.prodname_mobile %}. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)." -Os problemas podem ser criados de várias maneiras. Portanto, você pode escolher o método mais conveniente para seu fluxo de trabalho. Por exemplo, você pode criar um problema a partir de um repositório,{% ifversion fpt or ghec %} um item em uma lista de tarefas,{% endif %} uma observação em um projeto, um comentário em um problema ou pull request, uma linha de código específica ou uma consulta de URL. Você também pode criar um problema a partir da sua plataforma de escolha: por meio da interface do usuário web {% data variables.product.prodname_desktop %}, {% data variables.product.prodname_cli %}, GraphQL e APIs REST ou {% data variables.product.prodname_mobile %}. Para obter mais informações, consulte "[Criar um problema](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)". +## Track work -## Monitorar trabalho +You can organize and prioritize issues with projects. {% ifversion fpt or ghec %}To track issues as part of a larger issue, you can use task lists.{% endif %} To categorize related issues, you can use labels and milestones. -Você pode organizar e priorizar problemas com projetos. {% ifversion fpt or ghec %}Para monitorar problemas como parte de um problema maior, você pode usar as listas de tarefas.{% endif %} Para categorizar problemas relacionados, você pode usar etiquetas e marcos. +For more information about projects, see {% ifversion fpt or ghec %}"[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)" and {% endif %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)." {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}For more information about labels and milestones, see "[Using labels and milestones to track work](/issues/using-labels-and-milestones-to-track-work)." -Para obter mais informações sobre os projetos, consulte {% ifversion fpt or ghec %}"[Sobre projetos (beta)](/issues/trying-out-the-new-projects-experience/about-projects)e {% endif %}"[Organizar seu trabalho com quadros de projeto](/issues/organizing-your-work-with-project-boards)". {% ifversion fpt or ghec %}Para obter mais informações sobre listas de tarefas, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". {% endif %}Para obter mais informações sobre etiquetas e marcos, consulte "[Usando etiquetas e marcos para rastrear o trabalho](/issues/using-labels-and-milestones-to-track-work)". +## Stay up to date -## Mantenha-se atualizado +To stay updated on the most recent comments in an issue, you can subscribe to an issue to receive notifications about the latest comments. To quickly find links to recently updated issues you're subscribed to, visit your dashboard. For more information, see {% ifversion fpt or ghes or ghae or ghec %}"[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[About notifications](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" and "[About your personal dashboard](/articles/about-your-personal-dashboard)." -Para manter-se atualizado sobre os comentários mais recentes em um problema, você pode assinar um problema para receber notificações sobre os comentários mais recentes. Para encontrar links para problemas atualizados recentemente nos quais você está inscrito, visite seu painel. Para mais informações, consulte {% ifversion fpt or ghes or ghae or ghec %}"[Sobre notificações](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}"[Sobre notificações](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}" e "[Sobre o seu painel pessoal](/articles/about-your-personal-dashboard)". +## Community management -## Gerenciamento da comunidade +To help contributors open meaningful issues that provide the information that you need, you can use {% ifversion fpt or ghec %}issue forms and {% endif %}issue templates. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." -Para ajudar os colaboradores a abrir problemas significativos que fornecem as informações de que você precisa, você pode usar {% ifversion fpt or ghec %}formulários de problemas e {% endif %}modelos de problema. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". +{% ifversion fpt or ghec %}To maintain a healthy community, you can report comments that violate {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). For more information, see "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)."{% endif %} -{% ifversion fpt or ghec %}Para manter uma comunidade saudável, pode relatar comentários que violam as [diretrizes da comunidade](/free-pro-team@latest/github/site-policy/github-community-guidelines) de {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Relatar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)".{% endif %} +## Efficient communication -## Comunicação eficiente +You can @mention collaborators who have access to your repository in an issue to draw their attention to a comment. To link related issues in the same repository, you can type `#` followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies. +{% ifversion fpt or ghec %} For more information, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" and "[Assigning issues and pull requests to other GitHub users](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)." -Você pode @mencionar colaboradores com acesso ao seu repositório em um problema para chamar a atenção para um comentário. Para vincular problemas relacionados no mesmo repositório, você pode digitar `#` seguido de parte do título do problema e, em seguida, clicar no problema que você deseja vincular. Para comunicar responsabilidade, você pode atribuir problemas. Se você se encontrar, frequentemente, digitando o mesmo comentário, você poderá usar as respostas salvas. -{% ifversion fpt or ghec %} Para mais informações, consulte "[Sintaxe básica de escrita e formatação](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)" e "[Atribuindo problemas e pull requests a outros usuários do GitHub](/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users)" +## Comparing issues and discussions -## Comparando problemas e discussões +Some conversations are more suitable for {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} For guidance on when to use an issue or a discussion, see "[Communicating on GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)." -Algumas conversas são mais adequadas para {% data variables.product.prodname_discussions %}. {% data reusables.discussions.you-can-use-discussions %} Para orientação sobre quando usar um problema ou discussão, consulte "[Comunicar com o GitHub](/github/getting-started-with-github/quickstart/communicating-on-github)". - -Quando uma conversa em um problema é mais adequada para uma discussão, você pode converter a questão em uma discussão. +When a conversation in an issue is better suited for a discussion, you can convert the issue to a discussion. {% endif %} diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 739677adb9..8eca5faf19 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -3,8 +3,8 @@ title: Linking a pull request to an issue intro: You can link a pull request to an issue to show that a fix is in progress and to automatically close the issue when the pull request is merged. redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/linking-a-pull-request-to-an-issue - - /articles/closing-issues-via-commit-message/ - - /articles/closing-issues-via-commit-messages/ + - /articles/closing-issues-via-commit-message + - /articles/closing-issues-via-commit-messages - /articles/closing-issues-using-keywords - /github/managing-your-work-on-github/closing-issues-using-keywords - /github/managing-your-work-on-github/linking-a-pull-request-to-an-issue diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md index bf83d3f081..c008e01a7b 100644 --- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md +++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/creating-and-editing-milestones-for-issues-and-pull-requests.md @@ -1,9 +1,9 @@ --- -title: Criar e editar marcos para problemas e pull requests -intro: Você pode criar um marco para rastrear o progresso em grupos de problemas ou pull requests em um repositório. +title: Creating and editing milestones for issues and pull requests +intro: You can create a milestone to track progress on groups of issues or pull requests in a repository. redirect_from: - /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-milestones/creating-and-editing-milestones-for-issues-and-pull-requests - - /articles/creating-milestones-for-issues-and-pull-requests/ + - /articles/creating-milestones-for-issues-and-pull-requests - /articles/creating-and-editing-milestones-for-issues-and-pull-requests - /github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests versions: @@ -15,30 +15,32 @@ topics: - Pull requests - Issues - Project management -shortTitle: Criar & editar marcos +shortTitle: Create & edit milestones type: how_to --- +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issue-pr %} +{% data reusables.project-management.milestones %} +4. Choose one of these options: + - To create a new milestone, click **New Milestone**. + ![New milestone button](/assets/images/help/repository/new-milestone.png) + - To edit a milestone, next to the milestone you want to edit, click **Edit**. + ![Edit milestone option](/assets/images/help/repository/edit-milestone.png) +5. Type the milestone's title, description, or other changes, and click **Create milestone** or **Save changes**. Milestones will render Markdown syntax. For more information about Markdown syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/basic-writing-and-formatting-syntax)." + +## Deleting milestones + +When you delete milestones, issues and pull requests are not affected. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.milestones %} -4. Escolha uma destas opções: - - Para criar um marco, clique em **New Milestone** (Novo marco). ![Botão New milestone (Novo marco)](/assets/images/help/repository/new-milestone.png) - - Para editar um marco, ao lado do marco que deseja editar, clique em **Edit** (Editar). ![Opção para editar marco](/assets/images/help/repository/edit-milestone.png) -5. Digite o título, a descrição ou outras alterações do marco e clique em **Create milestone** (Criar marco) ou **Save changes** (Salvar alterações). Os marcos irão renderizar a sintaxe do Markdown. Para obter mais informações sobre como criar links, consulte "[Sintaxe básica de gravação e formatação](/github/writing-on-github/basic-writing-and-formatting-syntax)". +4. Next to the milestone you want to delete, click **Delete**. +![Delete milestone option](/assets/images/help/repository/delete-milestone.png) -## Excluir marcos +## Further reading -Quando você exclui marcos, os problemas e as pull requests não são afetados. - -{% data reusables.repositories.navigate-to-repo %} -{% data reusables.repositories.sidebar-issue-pr %} -{% data reusables.project-management.milestones %} -4. Ao lado do marco que deseja excluir, clique em **Delete** (Excluir). ![Opção para excluir marco](/assets/images/help/repository/delete-milestone.png) - -## Leia mais - -- "[Sobre marcos](/articles/about-milestones)" -- "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests)" -- "[Exibir o progresso do seu marco](/articles/viewing-your-milestone-s-progress)" -- "[Filtrar problemas e pull requests por marco](/articles/filtering-issues-and-pull-requests-by-milestone)" +- "[About milestones](/articles/about-milestones)" +- "[Associating milestones with issues and pull requests](/articles/associating-milestones-with-issues-and-pull-requests)" +- "[Viewing your milestone's progress](/articles/viewing-your-milestone-s-progress)" +- "[Filtering issues and pull requests by milestone](/articles/filtering-issues-and-pull-requests-by-milestone)" diff --git a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md index e7bb08156e..f5f9e3b136 100644 --- a/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md +++ b/translations/pt-BR/content/issues/using-labels-and-milestones-to-track-work/managing-labels.md @@ -1,6 +1,6 @@ --- -title: Gerenciar etiquetas -intro: 'Você pode classificar {% ifversion fpt or ghec %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %} criando, editando, aplicando e excluindo etiquetas.' +title: Managing labels +intro: 'You can classify {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %} by creating, editing, applying, and deleting labels.' permissions: '{% data reusables.enterprise-accounts.emu-permission-repo %}' redirect_from: - /github/managing-your-work-on-github/managing-your-work-with-issues-and-pull-requests/managing-labels @@ -12,7 +12,7 @@ redirect_from: - /articles/creating-and-editing-labels-for-issues-and-pull-requests - /articles/creating-a-label - /github/managing-your-work-on-github/creating-a-label - - /articles/customizing-issue-labels/ + - /articles/customizing-issue-labels - /articles/applying-labels-to-issues-and-pull-requests - /github/managing-your-work-on-github/applying-labels-to-issues-and-pull-requests - /articles/editing-a-label @@ -31,57 +31,58 @@ topics: - Project management type: how_to --- - ## Sobre etiquetas +## About labels -Você pode gerenciar seu trabalho em {% data variables.product.product_name %} criando etiquetas para classificar {% ifversion fpt or ghec %}problemas, pull requests e discussões{% else %}problemas e pull requests{% endif %}. Você pode aplicar etiquetas no repositório em que foram criadas. Uma vez criada uma etiqueta, você poderá usá-la em qualquer {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} dentro desse repositório. +You can manage your work on {% data variables.product.product_name %} by creating labels to categorize {% ifversion fpt or ghec %}issues, pull requests, and discussions{% else %}issues and pull requests{% endif %}. You can apply labels in the repository the label was created in. Once a label exists, you can use the label on any {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} within that repository. -## Sobre as etiquetas padrão +## About default labels -O {% data variables.product.product_name %} fornece etiquetas padrão para todos os repositórios novos. Você pode usar essas etiquetas padrão para ajudar com a criação de um fluxo de trabalho padronizado em um repositório. +{% data variables.product.product_name %} provides default labels in every new repository. You can use these default labels to help create a standard workflow in a repository. -| Etiqueta | Descrição | -| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `bug` | Indica um problema inesperado ou comportamento involuntário{% ifversion fpt or ghes or ghec %} -| `documentation` | Indica a necessidade de aprimoramentos ou adições à documentação{% endif %} -| `duplicate` | Indica {% ifversion fpt or ghec %}problemas, pull requests ou discussões{% else %}problemas ou pull requests{% endif %} -| `enhancement` | Indica novas solicitações de recurso | -| `good first issue` | Indica um bom problema para contribuidores principiantes | -| `help wanted` | Indica que um mantenedor deseja ajudar em um problema ou uma pull request | -| `invalid` | Indica que um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} já não é relevante | -| `question` | Indica que um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} precisa de mais informações | -| `wontfix` | Indica que o trabalho não continuará em um {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %} +Label | Description +--- | --- +`bug` | Indicates an unexpected problem or unintended behavior{% ifversion fpt or ghes or ghec %} +`documentation` | Indicates a need for improvements or additions to documentation{% endif %} +`duplicate` | Indicates similar {% ifversion fpt or ghec %}issues, pull requests, or discussions{% else %}issues or pull requests{% endif %} +`enhancement` | Indicates new feature requests +`good first issue` | Indicates a good issue for first-time contributors +`help wanted` | Indicates that a maintainer wants help on an issue or pull request +`invalid` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} is no longer relevant +`question` | Indicates that an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} needs more information +`wontfix` | Indicates that work won't continue on an {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %} -Etiquetas padrão são incluídas em todos os novos repositórios quando criados, mas você pode editar ou excluir as etiquetas posteriormente. +Default labels are included in every new repository when the repository is created, but you can edit or delete the labels later. -Problemas com a etiqueta `good first issue` são usados para preencher a página de `contribute` do repositório. Para obter um exemplo da página de `contribuir`, consulte [github/docs/contribua](https://github.com/github/docs/contribute). +Issues with the `good first issue` label are used to populate the repository's `contribute` page. For an example of a `contribute` page, see [github/docs/contribute](https://github.com/github/docs/contribute). {% ifversion fpt or ghes or ghec %} -Os proprietários da organização podem personalizar as etiquetas padrão para repositórios na organização. Para obter mais informações, consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)". +Organization owners can customize the default labels for repositories in their organization. For more information, see "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)." {% endif %} -## Criar uma etiqueta +## Creating a label -Qualquer pessoa com acesso de gravação a um repositório pode criar uma etiqueta. +Anyone with write access to a repository can create a label. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} -4. À direita do campo de pesquisa, clique em **New label** (Nova etiqueta). +4. To the right of the search field, click **New label**. {% data reusables.project-management.name-label %} {% data reusables.project-management.label-description %} {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.create-label %} -## Aplicando uma etiqueta +## Applying a label -Qualquer pessoa com acesso de triagem a um repositório pode aplicar e ignorar etiquetas. +Anyone with triage access to a repository can apply and dismiss labels. -1. Acesse {% ifversion fpt or ghec %}problema, pull request ou discussão{% else %}problema ou pull request{% endif %}. -1. Na barra lateral direita, à direita de "Etiquetas", clique em {% octicon "gear" aria-label="The gear icon" %} e, em seguida, clique em uma etiqueta. ![Menu suspenso "Etiquetas"](/assets/images/help/issues/labels-drop-down.png) +1. Navigate to the {% ifversion fpt or ghec %}issue, pull request, or discussion{% else %}issue or pull request{% endif %}. +1. In the right sidebar, to the right of "Labels", click {% octicon "gear" aria-label="The gear icon" %}, then click a label. + !["Labels" drop-down menu](/assets/images/help/issues/labels-drop-down.png) -## Editar uma etiqueta +## Editing a label -Qualquer pessoa com acesso de gravação a um repositório pode editar etiquetas existentes. +Anyone with write access to a repository can edit existing labels. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} @@ -92,18 +93,18 @@ Qualquer pessoa com acesso de gravação a um repositório pode editar etiquetas {% data reusables.project-management.label-color-randomizer %} {% data reusables.project-management.save-label %} -## Excluir uma etiqueta +## Deleting a label -Qualquer pessoa com acesso de gravação a um repositório pode excluir etiquetas existentes. +Anyone with write access to a repository can delete existing labels. -Excluir uma etiqueta removerá a etiqueta dos problemas e pull requests. +Deleting a label will remove the label from issues and pull requests. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-issue-pr %} {% data reusables.project-management.labels %} {% data reusables.project-management.delete-label %} -## Leia mais -- "[Filtrando e pesquisando problemas e pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %} -- "[Gerenciar etiquetas padrão para repositórios na organização](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %} -- "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} +## Further reading +- "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)"{% ifversion fpt or ghes or ghec %} +- "[Managing default labels for repositories in your organization](/articles/managing-default-labels-for-repositories-in-your-organization)"{% endif %}{% ifversion fpt or ghec %} +- "[Encouraging helpful contributions to your project with labels](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)"{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md index e83c53abc1..4fcc9475d4 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/allowing-people-to-delete-issues-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Permitir que as pessoas excluam problemas em sua organização -intro: Os proprietários da organização podem permitir que determinadas pessoas excluam problemas em repositórios que pertencem à sua organização. +title: Allowing people to delete issues in your organization +intro: Organization owners can allow certain people to delete issues in repositories owned by your organization. redirect_from: - /articles/allowing-people-to-delete-issues-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/allowing-people-to-delete-issues-in-your-organization @@ -12,15 +12,16 @@ versions: topics: - Organizations - Teams -shortTitle: Permitir exclusão de problema +shortTitle: Allow issue deletion --- -Por padrão, os problemas não podem ser excluídos dos repositórios de uma organização. Um proprietário da organização deve habilitar esse recurso primeiro para todos os repositórios da organização. +By default, issues cannot be deleted in an organization's repositories. An organization owner must enable this feature for all of the organization's repositories first. Once enabled, organization owners and people with admin access in an organization-owned repository can delete issues. People with admin access in a repository include organization members and outside collaborators who were given admin access. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" and "[Deleting an issue](/articles/deleting-an-issue)." {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Em "Issue deletion" (Exclusão do problema), selecione **Allow members to delete issues for this organization** (Permitir que integrantes excluam problemas dessa organização). ![Caixa de seleção para permitir que as pessoas excluam problemas](/assets/images/help/settings/issue-deletion.png) -6. Clique em **Salvar**. +5. Under "Issue deletion", select **Allow members to delete issues for this organization**. +![Checkbox to allow people to delete issues](/assets/images/help/settings/issue-deletion.png) +6. Click **Save**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md index 6e9f0c7bcb..2465aeb1de 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights.md @@ -1,6 +1,6 @@ --- -title: Alterar a visibilidade de informações de dependência da organização -intro: Você pode permitir que todos os integrantes da organização exibam informações de dependência da sua organização ou limitar a exibição aos proprietários da organização. +title: Changing the visibility of your organization's dependency insights +intro: You can allow all organization members to view dependency insights for your organization or limit viewing to organization owners. product: '{% data reusables.gated-features.org-insights %}' redirect_from: - /articles/changing-the-visibility-of-your-organizations-dependency-insights @@ -11,15 +11,16 @@ versions: topics: - Organizations - Teams -shortTitle: Mude a visibilidade da ideia +shortTitle: Change insight visibility --- -Os proprietários da organização podem definir limitações para exibir informações de dependência da organização. Todos os integrantes de uma organização podem exibir informações de dependência da organização por padrão. +Organization owners can set limitations for viewing organization dependency insights. All members of an organization can view organization dependency insights by default. -Os proprietários corporativos podem definir limitações para exibir informações de dependência da organização em todas as organizações da sua conta corporativa. For more information, see "[Enforcing policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)." +Enterprise owners can set limitations for viewing organization dependency insights on all organizations in your enterprise account. For more information, see "[Enforcing policies for dependency insights in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)." {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} -5. Em "Member organization permissions" (Permissões da organização do integrante), marque ou desmarque **Allow members to view dependency insights** (Permitir que integrantes exibam informações de dependência). ![Caixa de seleção para permitir que integrantes exibam informações](/assets/images/help/organizations/allow-members-to-view-insights.png) -6. Clique em **Salvar**. +5. Under "Member organization permissions", select or unselect **Allow members to view dependency insights**. +![Checkbox to allow members to view insights](/assets/images/help/organizations/allow-members-to-view-insights.png) +6. Click **Save**. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md index f9ca05eddb..c303abd963 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/converting-an-organization-into-a-user.md @@ -1,6 +1,6 @@ --- -title: Converter uma organização em usuário -intro: 'Não é possível converter uma organização em uma conta de usuário pessoal, mas você pode criar uma conta de usuário e transferir para ela os repositórios da organização.' +title: Converting an organization into a user +intro: 'It''s not possible to convert an organization into a personal user account, but you can create a new user account and transfer the organization''s repositories to it.' redirect_from: - /articles/converting-an-organization-into-a-user - /github/setting-up-and-managing-organizations-and-teams/converting-an-organization-into-a-user @@ -11,7 +11,7 @@ versions: topics: - Organizations - Teams -shortTitle: Converter organização em usuário +shortTitle: Convert organization to user --- {% ifversion fpt or ghec %} @@ -22,22 +22,22 @@ shortTitle: Converter organização em usuário {% endnote %} -1. [Inscreva-se](/articles/signing-up-for-a-new-github-account) para uma nova conta de usuário do GitHub. -2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} na nova conta de usuário. -4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário. +1. [Sign up](/articles/signing-up-for-a-new-github-account) for a new GitHub user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. 5. [Rename the organization](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to make the current username available. -6. [Renomeie o usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) para o nome da organização. -7. [Exclua a organização](/organizations/managing-organization-settings/deleting-an-organization-account). +6. [Rename the user](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username) to the organization's name. +7. [Delete the organization](/organizations/managing-organization-settings/deleting-an-organization-account). {% else %} -1. Inscreva-se para uma nova conta de usuário do GitHub Enterprise GitHub Enterprise. -2. [Altere a função do usuário para um proprietário](/articles/changing-a-person-s-role-to-owner). -3. {% data variables.product.signin_link %} na nova conta de usuário. -4. [Transfira cada repositório da organização](/articles/how-to-transfer-a-repository) para a nova conta de usuário. -5. [Exclua a organização](/articles/deleting-an-organization-account). -6. [Renomeie o usuário](/articles/changing-your-github-username) para o nome da organização. +1. Sign up for a new GitHub Enterprise user account. +2. [Have the user's role changed to an owner](/articles/changing-a-person-s-role-to-owner). +3. {% data variables.product.signin_link %} to the new user account. +4. [Transfer each organization repository](/articles/how-to-transfer-a-repository) to the new user account. +5. [Delete the organization](/articles/deleting-an-organization-account). +6. [Rename the user](/articles/changing-your-github-username) to the organization's name. {% endif %} diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md index dc41f75c0d..c3360a5de4 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/deleting-an-organization-account.md @@ -1,6 +1,6 @@ --- -title: Excluir uma conta de organização -intro: 'Quando você exclui uma organização, todos os repositórios, bifurcações de repositórios privados, wikis, problemas, pull requests e páginas de projeto ou de organização são excluídos também. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}' +title: Deleting an organization account +intro: 'When you delete an organization, all repositories, forks of private repositories, wikis, issues, pull requests, and Project or Organization Pages are deleted as well. {% ifversion fpt or ghec %}Your billing will end, and after 90 days the organization name becomes available for use on a new user or organization account.{% endif %}' redirect_from: - /articles/deleting-an-organization-account - /github/setting-up-and-managing-organizations-and-teams/deleting-an-organization-account @@ -12,24 +12,25 @@ versions: topics: - Organizations - Teams -shortTitle: Excluir conta da organização +shortTitle: Delete organization account --- {% ifversion fpt or ghec %} {% tip %} -**Dica**: caso queira cancelar sua assinatura paga, [faça downgrade da sua organização para {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) em vez de excluir a organização e o conteúdo dela. +**Tip**: If you want to cancel your paid subscription, you can [downgrade your organization to {% data variables.product.prodname_free_team %}](/articles/downgrading-your-github-subscription) instead of deleting the organization and its content. {% endtip %} {% endif %} -## 1. Fazer backup do conteúdo da organização +## 1. Back up your organization content -Depois que você exclui uma organização, o GitHub **não pode restaurar o conteúdo que você tem lá**. Portanto, antes de excluir sua organização, certifique-se de ter uma cópia de todos os repositórios, wikis, problemas e quadros de projetos da conta. +Once you delete an organization, GitHub **cannot restore your content**. Therefore, before you delete your organization, make sure you have a copy of all repositories, wikis, issues, and project boards from the account. -## 2. Excluir a organização +## 2. Delete the organization {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -4. Próximo à parte inferior da página de configurações da organização, clique em **Delete this Organization** (Excluir esta organização). ![Botão Delete this organization (Excluir esta organização)](/assets/images/help/settings/settings-organization-delete.png) +4. Near the bottom of the organization's settings page, click **Delete this Organization**. + ![Delete this organization button](/assets/images/help/settings/settings-organization-delete.png) diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md index 4f1e4200fe..67a4c82971 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Gerenciar o nome de branch-padrão para repositórios na sua organização -intro: 'Você pode definir o nome do branch-padrão para repositórios que os integrantes criam na sua organização em {% data variables.product.product_location %}.' +title: Managing the default branch name for repositories in your organization +intro: 'You can set the default branch name for repositories that members create in your organization on {% data variables.product.product_location %}.' redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-the-default-branch-name-for-repositories-in-your-organization permissions: Organization owners can manage the default branch name for new repositories in the organization. @@ -12,26 +12,29 @@ versions: topics: - Organizations - Teams -shortTitle: Gerenciar nome do branch padrão +shortTitle: Manage default branch name --- -## Sobre o gerenciamento do nome do brancc-padrão +## About management of the default branch name -Quando um integrante da sua organização cria um novo repositório na sua organização, o repositório contém um branch, que é o branch-padrão. Você pode alterar o nome que {% data variables.product.product_name %} usa para o branch-padrão em novos repositórios que os integrantes da sua organização criam. Para obter mais informações sobre o branch padrão, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)". +When a member of your organization creates a new repository in your organization, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories that members of your organization create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)." {% data reusables.branches.change-default-branch %} -Se um proprietário da empresa tiver aplicado uma política para o nome do branch padrão para sua empresa, você não poderá definir um nome do branch padrão para sua organização. Em vez disso, você pode alterar o branch padrão para repositórios individuais. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." +If an enterprise owner has enforced a policy for the default branch name for your enterprise, you cannot set a default branch name for your organization. Instead, you can change the default branch for individual repositories. For more information, see {% ifversion fpt %}"[Enforcing repository management policies in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% else %}"[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-the-default-branch-name)"{% endif %} and "[Changing the default branch](/github/administering-a-repository/changing-the-default-branch)." -## Definir o nome do branch-padrão +## Setting the default branch name {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.repository-defaults %} -3. Em "Branch padrão do repositório", clique em **Alterar o nome do branch-padrão agora**. ![Botão de sobrescrever](/assets/images/help/organizations/repo-default-name-button.png) -4. Digite o nome-padrão que você gostaria de usar para novos branches. ![Caixa de texto para digitar o nome-padrão](/assets/images/help/organizations/repo-default-name-text.png) -5. Clique em **Atualizar**. ![Botão de atualizar](/assets/images/help/organizations/repo-default-name-update.png) +3. Under "Repository default branch", click **Change default branch name now**. + ![Override button](/assets/images/help/organizations/repo-default-name-button.png) +4. Type the default name that you would like to use for new branches. + ![Text box for entering default name](/assets/images/help/organizations/repo-default-name-text.png) +5. Click **Update**. + ![Update button](/assets/images/help/organizations/repo-default-name-update.png) -## Leia mais +## Further reading -- "[Gerenciar o nome do branch-padrão para seus repositórios](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" +- "[Managing the default branch name for your repositories](/github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories)" diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md index 0e1b5656b5..dcf8751104 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Verificando ou aprovando um domínio para sua organização -intro: 'Você pode verificar a propriedade de domínios com {% data variables.product.company_short %} para confirmar a identidade da sua organização. Você também pode aprovar domínios para os quais {% data variables.product.company_short %} pode enviar notificações de email para os integrantes da sua organização.' +title: Verifying or approving a domain for your organization +intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm your organization''s identity. You can also approve domains that {% data variables.product.company_short %} can send email notifications to for members of your organization.' product: '{% data reusables.gated-features.verify-and-approve-domain %}' redirect_from: - /articles/verifying-your-organization-s-domain @@ -18,36 +18,36 @@ topics: - Notifications - Organizations - Policy -shortTitle: Verificar ou aprovar um domínio +shortTitle: Verify or approve a domain --- -## Sobre a verificação do domínio +## About domain verification -Após a verificação da propriedade dos domínios da sua organização, é exibido um selo "Verified" (Verificado) no perfil da organização. {% ifversion fpt or ghec %} Se a sua organização estiver no {% data variables.product.prodname_ghe_cloud %} e tiver concordado com os Termos de serviço corporativos, os proprietários da organização poderão verificar a identidade dos seus integrantes exibindo o endereço de e-mail de cada um deles no domínio verificado. Para obter mais informações, consulte "[Sobre a página de perfil da sua organização](/articles/about-your-organization-s-profile/)" e "Atualizar para os Termos de serviço corporativos".{% endif %} +After verifying ownership of your organization's domains, a "Verified" badge will display on the organization's profile. {% ifversion fpt or ghec %}If your organization is on {% data variables.product.prodname_ghe_cloud %} and has agreed to the Corporate Terms of Service, organization owners will be able to verify the identity of organization members by viewing each member's email address within the verified domain. For more information, see "[About your organization's profile page](/articles/about-your-organization-s-profile/)" and "Upgrading to the Corporate Terms of Service."{% endif %} -{% ifversion fpt or ghec %}Se sua organização pertencer a uma conta corporativa um selo "Verificado" de{% elsif ghes %}A{% endif %} será exibido no perfil da sua organização para todos os domínios verificados para a conta corporativa, além de todos os domínios verificados para a organização. Os proprietários da organização podem ver quaisquer domínios que um proprietário da empresa verificou ou aprovou e pode editar os domínios se o proprietário da organização também for um proprietário corporativo. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +{% ifversion fpt or ghec %}If your organization is owned by an enterprise account, a{% elsif ghes %}A{% endif %} "Verified" badge will display on your organization's profile for any domains verified for the enterprise account, in addition to any domains verified for the organization. Organization owners can view any domains that an enterprise owner has verified or approved, and edit the domains if the organization owner is also an enterprise owner. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} {% data reusables.organizations.verified-domains-details %} -{% ifversion fpt or ghec %}Em {% data variables.product.prodname_ghe_cloud %}, depois de verificar a propriedade do domínio da sua organização, você pode restringir notificações de e-mail para a organização para esse domínio. Para obter mais informações, consulte "[Restringir notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %} +{% ifversion fpt or ghec %}On {% data variables.product.prodname_ghe_cloud %}, after verifying ownership of your organization's domain, you can restrict email notifications for the organization to that domain. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." {% ifversion fpt %}{% data reusables.enterprise.link-to-ghec-trial %}{% endif %}{% endif %} {% ifversion fpt or ghec %}You can also verify custom domains used for {% data variables.product.prodname_pages %} to prevent domain takeovers when a custom domain remains configured but your {% data variables.product.prodname_pages %} site is either disabled or no longer uses the domain. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)."{% endif %} -## Sobre a aprovação de domínio +## About domain approval {% data reusables.enterprise-accounts.approved-domains-beta-note %} {% data reusables.enterprise-accounts.approved-domains-about %} -Após aprovar domínios para a sua organização, você pode restringir notificações de e-mail para atividades dentro da organização para usuários com endereços de e-mail verificados dentro de domínios verificados ou aprovados. Para obter mais informações, consulte "[Restringir notificações de e-mail para sua organização](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)". +After you approve domains for your organization, you can restrict email notifications for activity within the organization to users with verified email addresses within verified or approved domains. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)." -Os proprietários de empresas não podem ver quais integrantes da organização ou endereços de e-mail recebem notificações dentro dos domínios aprovados. +Enterprise owners cannot see which organization members or email addresses receive notifications within approved domains. -Os proprietários de empresas também podem aprovar domínios adicionais para organizações pertencentes à empresa. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} +Enterprise owners can also approve additional domains for organizations owned by the enterprise. {% ifversion fpt or ghec %}For more information, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}{% ifversion ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %} -## Verificando um domínio para a sua organização +## Verifying a domain for your organization -Para verificar um domínio, você deve ter acesso para modificar registros de domínio com o seu serviço de hospedagem de domínio. +To verify a domain, you must have access to modify domain records with your domain hosting service. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} @@ -55,15 +55,16 @@ Para verificar um domínio, você deve ter acesso para modificar registros de do {% data reusables.organizations.add-a-domain %} {% data reusables.organizations.add-domain %} {% data reusables.organizations.add-dns-txt-record %} -1. Aguarde a alteração da configuração de DNS, que pode demorar até 72 horas. Você pode confirmar que a configuração do DNS foi alterada executando o comando `dig` na linha de comando, substituindo `ORGANIZATION` pelo nome da sua organização e `example.com` pelo o domínio que você gostaria de verificar. Você deverá ver o novo registro TXT listado na saída do comando. +1. Wait for your DNS configuration to change, which may take up to 72 hours. You can confirm your DNS configuration has changed by running the `dig` command on the command line, replacing `ORGANIZATION` with the name of your organization and `example.com` with the domain you'd like to verify. You should see your new TXT record listed in the command output. ```shell $ dig _github-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT ``` -1. Depois de confirmar que o seu registro TXT foi adicionado ao seu DNS, siga os passos um a três acima para acessar os domínios aprovados e verificados da sua organização. +1. After confirming your TXT record is added to your DNS, follow steps one through three above to navigate to your organization's approved and verified domains. {% data reusables.organizations.continue-verifying-domain %} -11. Depois que o selo "Verified" (Verificado) estiver visível na página de perfil da sua organização, a entrada TXT poderá ser excluída do registro DNS no serviço de hospedagem de domínio. ![Selo Verified (Verificado)](/assets/images/help/organizations/verified-badge.png) +11. Optionally, once the "Verified" badge is visible on your organization's profile page, you can delete the TXT entry from the DNS record at your domain hosting service. +![Verified badge](/assets/images/help/organizations/verified-badge.png) -## Aprovando um domínio para a sua organização +## Approving a domain for your organization {% ifversion fpt or ghes > 3.1 or ghec %} @@ -79,9 +80,10 @@ Para verificar um domínio, você deve ter acesso para modificar registros de do {% data reusables.organizations.domains-approve-it-instead %} {% data reusables.organizations.domains-approve-domain %} -## Removendo um domínio aprovado ou verificado +## Removing an approved or verified domain {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.verified-domains %} -1. À direita do domínio a ser removido, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Excluir**. !["Excluir" para um domínio](/assets/images/help/organizations/domains-delete.png) +1. To the right of the domain to remove, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. + !["Delete" for a domain](/assets/images/help/organizations/domains-delete.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md index 187ceb43bf..ff7165d325 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md @@ -1,5 +1,5 @@ --- -title: Gerenciar o acesso de pessoas à organização com funções +title: Managing people's access to your organization with roles intro: 'You can control access to your organizations''s settings and repositories by giving people organization, repository, and team roles.' redirect_from: - /articles/managing-people-s-access-to-your-organization-with-roles @@ -20,6 +20,6 @@ children: - /adding-a-billing-manager-to-your-organization - /removing-a-billing-manager-from-your-organization - /managing-security-managers-in-your-organization -shortTitle: Gerenciar acesso com funções +shortTitle: Manage access with roles --- diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index 117b4661d1..5da023dcd8 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -36,16 +36,18 @@ You can assign the security manager role to a maximum of 10 teams in your organi {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} -1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. ![Add security manager](/assets/images/help/organizations/add-security-managers.png) +1. Under **Security managers**, search for and select the team to give the role. Each team you select will appear in a list below the search bar. + ![Add security manager](/assets/images/help/organizations/add-security-managers.png) ## Removing the security manager role from a team in your organization {% warning %} -**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. Para obter mais informações, consulte "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)." +**Warning:** Removing the security manager role from a team will remove the team's ability to manage security alerts and settings across the organization, but the team will retain read access to repositories that was granted when the role was assigned. You must remove any unwanted read access manually. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#removing-a-teams-access-to-a-repository)." {% endwarning %} {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security-and-analysis %} -1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}. ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png) +1. Under **Security managers**, to the right of the team you want to remove as security managers, click {% octicon "x" aria-label="The X icon" %}. + ![Remove security managers](/assets/images/help/organizations/remove-security-managers.png) diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md index dd40cb5a26..80fb7f8cb7 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -2,12 +2,12 @@ title: About GitHub Pages intro: 'You can use {% data variables.product.prodname_pages %} to host a website about yourself, your organization, or your project directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' redirect_from: - - /articles/what-are-github-pages/ - - /articles/what-is-github-pages/ - - /articles/user-organization-and-project-pages/ - - /articles/using-a-static-site-generator-other-than-jekyll/ - - /articles/mime-types-on-github-pages/ - - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio/ + - /articles/what-are-github-pages + - /articles/what-is-github-pages + - /articles/user-organization-and-project-pages + - /articles/using-a-static-site-generator-other-than-jekyll + - /articles/mime-types-on-github-pages + - /articles/should-i-rename-usernamegithubcom-repositories-to-usernamegithubio - /articles/about-github-pages - /github/working-with-github-pages/about-github-pages product: '{% data reusables.gated-features.pages %}' diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md index dae3724511..6f568026a7 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -1,9 +1,9 @@ --- -title: Adicionar um tema ao site do GitHub Pages com o seletor de temas -intro: 'É possível adicionar um tema ao site do {% data variables.product.prodname_pages %} para personalizar a aparência dele.' +title: Adding a theme to your GitHub Pages site with the theme chooser +intro: 'You can add a theme to your {% data variables.product.prodname_pages %} site to customize your site’s look and feel.' redirect_from: - - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser/ - - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser/ + - /articles/creating-a-github-pages-site-with-the-jekyll-theme-chooser + - /articles/adding-a-jekyll-theme-to-your-github-pages-site-with-the-jekyll-theme-chooser - /articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser - /github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser product: '{% data reusables.gated-features.pages %}' @@ -12,37 +12,40 @@ versions: ghec: '*' topics: - Pages -shortTitle: Adicionar tema a um site de Páginas +shortTitle: Add theme to a Pages site --- -Pessoas com permissões de administrador para um repositório podem usar o seletor de temas para adicionar um tema a um site do {% data variables.product.prodname_pages %}. +People with admin permissions for a repository can use the theme chooser to add a theme to a {% data variables.product.prodname_pages %} site. -## Sobre o seletor de temas +## About the theme chooser -O seletor de temas adiciona um tema do Jekyll ao repositório. Para obter mais informações sobre o Jekyll, consulte "[Sobre o {% data variables.product.prodname_pages %} e o Jekyll](/articles/about-github-pages-and-jekyll)". +The theme chooser adds a Jekyll theme to your repository. For more information about Jekyll, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -O funcionamento do seletor de temas depende de o repositório ser público ou privado. - - Se o {% data variables.product.prodname_pages %} já estiver habilitado para o repositório, o seletor de temas adicionará o tema à fonte de publicação atual. - - Se o repositório for público e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, o uso do seletor de temas habilitará o {% data variables.product.prodname_pages %} e definirá o branch-padrão como fonte de publicação. - - Se o repositório for privado e o {% data variables.product.prodname_pages %} estiver desabilitado para ele, será preciso habilitar o {% data variables.product.prodname_pages %} definindo uma fonte de publicação para poder usar o seletor de temas. +How the theme chooser works depends on whether your repository is public or private. + - If {% data variables.product.prodname_pages %} is already enabled for your repository, the theme chooser will add your theme to the current publishing source. + - If your repository is public and {% data variables.product.prodname_pages %} is disabled for your repository, using the theme chooser will enable {% data variables.product.prodname_pages %} and configure the default branch as your publishing source. + - If your repository is private and {% data variables.product.prodname_pages %} is disabled for your repository, you must enable {% data variables.product.prodname_pages %} by configuring a publishing source before you can use the theme chooser. -Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." -Caso você tenha adicionado manualmente um tema do Jekyll ao repositório no passado, esses arquivos poderão ser aplicados mesmo depois que você usar o seletor de temas. Para evitar conflitos, remova todas as pastas e arquivos de temas adicionados manualmente antes de usar o seletor de temas. Para obter mais informações, consulte "[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)". +If you manually added a Jekyll theme to your repository in the past, those files may be applied even after you use the theme chooser. To avoid conflicts, remove all manually added theme folders and files before using the theme chooser. For more information, see "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." -## Adicionar um tema com o seletor de temas +## Adding a theme with the theme chooser {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -3. No "{% data variables.product.prodname_pages %}", clique em **Escolher um tema** ou **Alterar tema**. ![Botão Choose a theme (Escolher um tema)](/assets/images/help/pages/choose-a-theme.png) -4. No topo da página, clique no tema desejado e depois em **Selecionar tema**. ![Opções de tema e botão Select theme (Selecionar tema)](/assets/images/help/pages/select-theme.png) -5. Talvez seja necessário editar o arquivo *README.md* do site. - - Para editá-lo mais tarde, clique em **Cancelar**. ![Link Cancel (Cancelar) ao editar um arquivo](/assets/images/help/pages/cancel-edit.png) - - Para editar o arquivo agora, consulte "[Editando os arquivos](/repositories/working-with-files/managing-files/editing-files)". +3. Under "{% data variables.product.prodname_pages %}," click **Choose a theme** or **Change theme**. + ![Choose a theme button](/assets/images/help/pages/choose-a-theme.png) +4. On the top of the page, click the theme you want, then click **Select theme**. + ![Theme options and Select theme button](/assets/images/help/pages/select-theme.png) +5. You may be prompted to edit your site's *README.md* file. + - To edit the file later, click **Cancel**. + ![Cancel link when editing a file](/assets/images/help/pages/cancel-edit.png) + - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." -O tema escolhido será aplicado automaticamente aos arquivos markdown no repositório. Para aplicar o tema a arquivos HTML no repositório, é preciso adicionar a página inicial YAML que especifica um layout para cada arquivo. Para obter mais informações, consulte "[Página inicial](https://jekyllrb.com/docs/front-matter/)" no site do Jekyll. +Your chosen theme will automatically apply to markdown files in your repository. To apply your theme to HTML files in your repository, you need to add YAML front matter that specifies a layout to each file. For more information, see "[Front Matter](https://jekyllrb.com/docs/front-matter/)" on the Jekyll site. -## Leia mais +## Further reading -- [Temas](https://jekyllrb.com/docs/themes/) no site do Jekyll +- [Themes](https://jekyllrb.com/docs/themes/) on the Jekyll site diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index 135834217a..5e931e4862 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -1,8 +1,8 @@ --- -title: Configurar uma fonte de publicação para o site do GitHub Pages -intro: 'Se você usar a fonte de publicação padrão do site do {% data variables.product.prodname_pages %}, seu site será publicado automaticamente. You can also choose to publish your site from a different branch or folder.' +title: Configuring a publishing source for your GitHub Pages site +intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.' redirect_from: - - /articles/configuring-a-publishing-source-for-github-pages/ + - /articles/configuring-a-publishing-source-for-github-pages - /articles/configuring-a-publishing-source-for-your-github-pages-site - /github/working-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site product: '{% data reusables.gated-features.pages %}' @@ -14,24 +14,41 @@ versions: ghec: '*' topics: - Pages -shortTitle: Configurar fonte de publicação +shortTitle: Configure publishing source --- -Para obter mais informações sobre fontes de publicação, consulte "[Sobre o {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)". +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." -## Escolher uma fonte de publicação +## Choosing a publishing source Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository. {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -3. Em "{% data variables.product.prodname_pages %}", use o menu suspenso **Nenhum** ou **Branch** e selecione uma fonte de publicação. ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png) -4. Opcionalmente, use o menu suspenso para selecionar uma pasta para sua fonte de publicação. ![Menu suspenso para selecionar uma pasta para a fonte de publicação](/assets/images/help/pages/publishing-source-folder-drop-down.png) -5. Clique em **Salvar**. ![Botão para salvar alterações nas configurações da fonte de publicação](/assets/images/help/pages/publishing-source-save.png) +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. + ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. + ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Click **Save**. + ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png) -## Solucionar problemas de publicação com o site do {% data variables.product.prodname_pages %} +## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site {% data reusables.pages.admin-must-push %} -If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. Para obter informações, consulte [Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)". +If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." + +{% ifversion fpt %} + +Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. + +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." + +{% note %} + +{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + +{% endnote %} + +{% endif %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md index ace196b0ef..e2a6857bc7 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site.md @@ -1,8 +1,8 @@ --- -title: Criar uma página 404 personalizada para o site do GitHub Pages -intro: Você pode exibir uma página de erro 404 personalizada quando as pessoas tentam acessar páginas não existentes no seu site. +title: Creating a custom 404 page for your GitHub Pages site +intro: You can display a custom 404 error page when people try to access nonexistent pages on your site. redirect_from: - - /articles/custom-404-pages/ + - /articles/custom-404-pages - /articles/creating-a-custom-404-page-for-your-github-pages-site - /github/working-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site product: '{% data reusables.gated-features.pages %}' @@ -13,25 +13,26 @@ versions: ghec: '*' topics: - Pages -shortTitle: Criar página 404 personalizada +shortTitle: Create custom 404 page --- {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.navigate-publishing-source %} {% data reusables.files.add-file %} -3. No campo de nome de arquivo, digite `404.html` ou `404.md`. ![Campo de nome de arquivo](/assets/images/help/pages/404-file-name.png) -4. Se você nomeou seu arquivo como `404.md`, adicione a seguinte página inicial YAML no começo do arquivo: +3. In the file name field, type `404.html` or `404.md`. + ![File name field](/assets/images/help/pages/404-file-name.png) +4. If you named your file `404.md`, add the following YAML front matter to the beginning of the file: ```yaml --- permalink: /404.html --- ``` -5. Abaixo da página inicial YAML, se houver, adicione o conteúdo que deseja exibir na página 404. +5. Below the YAML front matter, if present, add the content you want to display on your 404 page. {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -## Leia mais +## Further reading -- [Página inicial](http://jekyllrb.com/docs/frontmatter) na documentação do Jekyll +- [Front matter](http://jekyllrb.com/docs/frontmatter) in the Jekyll documentation diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index 8489cec011..fd7bb21e9a 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -1,11 +1,11 @@ --- -title: Criar um site do GitHub Pages -intro: 'É possível criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.' +title: Creating a GitHub Pages site +intro: 'You can create a {% data variables.product.prodname_pages %} site in a new or existing repository.' redirect_from: - - /articles/creating-pages-manually/ - - /articles/creating-project-pages-manually/ - - /articles/creating-project-pages-from-the-command-line/ - - /articles/creating-project-pages-using-the-command-line/ + - /articles/creating-pages-manually + - /articles/creating-project-pages-manually + - /articles/creating-project-pages-from-the-command-line + - /articles/creating-project-pages-using-the-command-line - /articles/creating-a-github-pages-site - /github/working-with-github-pages/creating-a-github-pages-site product: '{% data reusables.gated-features.pages %}' @@ -16,12 +16,12 @@ versions: ghec: '*' topics: - Pages -shortTitle: Criar um site do GitHub Pages +shortTitle: Create a GitHub Pages site --- {% data reusables.pages.org-owners-can-restrict-pages-creation %} -## Criar um repositório para seu site +## Creating a repository for your site {% data reusables.pages.new-or-existing-repo %} @@ -32,7 +32,7 @@ shortTitle: Criar um site do GitHub Pages {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %} -## Criar seu site +## Creating your site {% data reusables.pages.must-have-repo-first %} @@ -40,8 +40,8 @@ shortTitle: Criar um site do GitHub Pages {% data reusables.pages.navigate-site-repo %} {% data reusables.pages.decide-publishing-source %} -3. Se a fonte de publicação que você escolheu já existe, navegue até ela. Caso contrário, crie a fonte de publicação. -4. Na raiz da fonte de publicação, crie um novo arquivo chamado `index.md` com o conteúdo que você deseja exibir na página principal do seu site. +3. If your chosen publishing source already exists, navigate to the publishing source. If your chosen publishing source doesn't exist, create the publishing source. +4. In the root of the publishing source, create a new file called `index.md` that contains the content you want to display on the main page of your site. {% tip %} @@ -53,19 +53,20 @@ shortTitle: Criar um site do GitHub Pages {% data reusables.pages.sidebar-pages %}{% ifversion fpt or ghec %} {% data reusables.pages.choose-visibility %}{% endif %} {% data reusables.pages.visit-site %} +{% data reusables.pages.check-workflow-run %} {% data reusables.pages.admin-must-push %} -## Próximas etapas +## Next steps -Você pode adicionar mais páginas ao seu site criando novos arquivos. Cada arquivo ficará disponível no site na mesma estrutura de diretórios que a fonte de publicação. Por exemplo, se a fonte de publicação do site de projeto for o branch `gh-pages` e você criar um arquivo chamado `/about/contact-us.md` no branch `gh-pages`, o arquivo novo ficará disponível em {% ifversion fpt or ghec %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. +You can add more pages to your site by creating more new files. Each file will be available on your site in the same directory structure as your publishing source. For example, if the publishing source for your project site is the `gh-pages` branch, and you create a new file called `/about/contact-us.md` on the `gh-pages` branch, the file will be available at {% ifversion fpt or ghec %}`https://.github.io//{% else %}`http(s):///pages///{% endif %}about/contact-us.html`. -Também é possível adicionar um tema para personalizar a aparência do site. Para obter mais informações, consulte {% ifversion fpt or ghec %}"[Adicionar um tema ao site do {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adicionar um tema ao site do {% data variables.product.prodname_pages %} usando o Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}". +You can also add a theme to customize your site’s look and feel. For more information, see {% ifversion fpt or ghec %}"[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser){% else %}"[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll){% endif %}." -Para personalizar seu site ainda mais, você pode usar o Jekyll, um gerador de site estático com suporte integrado para o {% data variables.product.prodname_pages %}. Para obter mais informações, consulte "[Sobre o {% data variables.product.prodname_pages %} e o JJekyll](/articles/about-github-pages-and-jekyll)". +To customize your site even more, you can use Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." -## Leia mais +## Further reading -- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" -- "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository)" -- "[Criar arquivos](/articles/creating-new-files)" +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository)" +- "[Creating new files](/articles/creating-new-files)" diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md index 846ece7614..b391a4458c 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/index.md @@ -1,9 +1,9 @@ --- -title: Indrodução ao GitHub Pages -intro: 'Você pode configurar um site básico do {% data variables.product.prodname_pages %} para você mesmo, sua organização ou seu projeto.' +title: Getting started with GitHub Pages +intro: 'You can set up a basic {% data variables.product.prodname_pages %} site for yourself, your organization, or your project.' redirect_from: - /categories/github-pages-basics - - /articles/additional-customizations-for-github-pages/ + - /articles/additional-customizations-for-github-pages - /articles/getting-started-with-github-pages - /github/working-with-github-pages/getting-started-with-github-pages product: '{% data reusables.gated-features.pages %}' @@ -24,6 +24,6 @@ children: - /securing-your-github-pages-site-with-https - /using-submodules-with-github-pages - /unpublishing-a-github-pages-site -shortTitle: Começar +shortTitle: Get started --- diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md index cde8d59d6d..bcc60251c3 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md @@ -1,11 +1,11 @@ --- -title: Cancelar a publicação de um site do GitHub Pages -intro: 'Você pode cancelar a publicação do seu site de {% data variables.product.prodname_pages %} para que não fique mais disponível.' +title: Unpublishing a GitHub Pages site +intro: 'You can unpublish your {% data variables.product.prodname_pages %} site so that the site is no longer available.' redirect_from: - - /articles/how-do-i-unpublish-a-project-page/ - - /articles/unpublishing-a-project-page/ - - /articles/unpublishing-a-project-pages-site/ - - /articles/unpublishing-a-user-pages-site/ + - /articles/how-do-i-unpublish-a-project-page + - /articles/unpublishing-a-project-page + - /articles/unpublishing-a-project-pages-site + - /articles/unpublishing-a-user-pages-site - /articles/unpublishing-a-github-pages-site - /github/working-with-github-pages/unpublishing-a-github-pages-site product: '{% data reusables.gated-features.pages %}' @@ -17,21 +17,22 @@ versions: ghec: '*' topics: - Pages -shortTitle: Cancelar a publicação do site de páginas +shortTitle: Unpublish Pages site --- -## Cancelar a publicação de um site de projeto +## Unpublishing a project site {% data reusables.repositories.navigate-to-repo %} -2. Se existir um branch `gh-pages` no repositório, exclua o branch `gh-pages`. Para obter mais informações, consulte "[Criar e excluir branches em seu repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)". -3. Se o branch `gh-pages` fosse a sua fonte de publicação, {% ifversion fpt or ghec %}pule para a etapa 6{% else %}agora o seu site não está publicado e você pode pular as etapas restantes{% endif %}. +2. If a `gh-pages` branch exists in the repository, delete the `gh-pages` branch. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)." +3. If the `gh-pages` branch was your publishing source, {% ifversion fpt or ghec %}skip to step 6{% else %}your site is now unpublished and you can skip the remaining steps{% endif %}. {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -5. No "{% data variables.product.prodname_pages %}", use o menu suspenso **Source** (Fonte) e selecione **None** (Nenhuma). ![Menu suspenso para selecionar uma fonte de publicação](/assets/images/help/pages/publishing-source-drop-down.png) +5. Under "{% data variables.product.prodname_pages %}", use the **Source** drop-down menu and select **None.** + ![Drop down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) {% data reusables.pages.update_your_dns_settings %} -## Cancelar a publicação de um site de usuário ou organização +## Unpublishing a user or organization site {% data reusables.repositories.navigate-to-repo %} -2. Exclua o branch que você está usando como fonte de publicação ou exclua todo o repositório. Para obter mais informações, consulte "[Criar e excluir branches no repositório](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" e "[Excluir um repositório](/articles/deleting-a-repository)". +2. Delete the branch that you're using as a publishing source, or delete the entire repository. For more information, see "[Creating and deleting branches within your repository](/articles/creating-and-deleting-branches-within-your-repository#deleting-a-branch)" and "[Deleting a repository](/articles/deleting-a-repository)." {% data reusables.pages.update_your_dns_settings %} diff --git a/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md index a7ba3fab4d..a29e68ab61 100644 --- a/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md +++ b/translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md @@ -1,8 +1,8 @@ --- -title: Usar submódulos com o GitHub Pages -intro: 'Você pode usar submódulos com o {% data variables.product.prodname_pages %} para incluir outros projetos no código do seu site.' +title: Using submodules with GitHub Pages +intro: 'You can use submodules with {% data variables.product.prodname_pages %} to include other projects in your site''s code.' redirect_from: - - /articles/using-submodules-with-pages/ + - /articles/using-submodules-with-pages - /articles/using-submodules-with-github-pages - /github/working-with-github-pages/using-submodules-with-github-pages product: '{% data reusables.gated-features.pages %}' @@ -11,16 +11,16 @@ versions: ghec: '*' topics: - Pages -shortTitle: Use submódulos com páginas +shortTitle: Use submodules with Pages --- -Se o repositório do seu site do {% data variables.product.prodname_pages %} contiver submódulos, o conteúdo dele será inserido automaticamente quando o site for criado. +If the repository for your {% data variables.product.prodname_pages %} site contains submodules, their contents will automatically be pulled in when your site is built. -Só é possível usar submódulos que apontem para repositórios públicos, porque o servidor do {% data variables.product.prodname_pages %} não pode acessar repositórios privados. +You can only use submodules that point to public repositories, because the {% data variables.product.prodname_pages %} server cannot access private repositories. -Use a URL somente leitura `https://` para os submódulos, inclusive os aninhados. Essa alteração pode ser feita no arquivo _.gitmodules_. +Use the `https://` read-only URL for your submodules, including nested submodules. You can make this change in your _.gitmodules_ file. -## Leia mais +## Further reading -- "[Ferramentas Git - Submódulos](https://git-scm.com/book/en/Git-Tools-Submodules)" no livro _Pro Git_ -- "[Solucionar problemas de erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" +- "[Git Tools - Submodules](https://git-scm.com/book/en/Git-Tools-Submodules)" from the _Pro Git_ book +- "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)" diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md index e92637ff21..8df4d200f5 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md @@ -1,21 +1,21 @@ --- -title: Sobre o GitHub Pages e Jekyll -intro: 'Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %}.' +title: About GitHub Pages and Jekyll +intro: 'Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %}.' redirect_from: - /articles/about-jekyll-themes-on-github - /articles/configuring-jekyll - /articles/configuring-jekyll-plugins - /articles/using-syntax-highlighting-on-github-pages - /articles/files-that-start-with-an-underscore-are-missing - - /articles/sitemaps-for-github-pages/ - - /articles/search-engine-optimization-for-github-pages/ - - /articles/repository-metadata-on-github-pages/ - - /articles/atom-rss-feeds-for-github-pages/ - - /articles/redirects-on-github-pages/ - - /articles/emoji-on-github-pages/ - - /articles/mentions-on-github-pages/ - - /articles/using-jekyll-plugins-with-github-pages/ - - /articles/adding-jekyll-plugins-to-a-github-pages-site/ + - /articles/sitemaps-for-github-pages + - /articles/search-engine-optimization-for-github-pages + - /articles/repository-metadata-on-github-pages + - /articles/atom-rss-feeds-for-github-pages + - /articles/redirects-on-github-pages + - /articles/emoji-on-github-pages + - /articles/mentions-on-github-pages + - /articles/using-jekyll-plugins-with-github-pages + - /articles/adding-jekyll-plugins-to-a-github-pages-site - /articles/about-github-pages-and-jekyll - /github/working-with-github-pages/about-github-pages-and-jekyll product: '{% data reusables.gated-features.pages %}' @@ -29,19 +29,19 @@ topics: shortTitle: GitHub Pages & Jekyll --- -## Sobre o Jekyll +## About Jekyll -O Jekyll é um gerador de site estático com suporte integrado para {% data variables.product.prodname_pages %} e um processo de compilação simplificado. O Jekyll usa arquivos Markdown e HTML, além de criar um site estático completo com base na sua escolha de layouts. O Jekyll aceita Markdown e Liquid, uma linguagem de modelagem que carrega conteúdo dinâmico no site. Para obter mais informações, consulte [Jekyll](https://jekyllrb.com/). +Jekyll is a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. Jekyll takes Markdown and HTML files and creates a complete static website based on your choice of layouts. Jekyll supports Markdown and Liquid, a templating language that loads dynamic content on your site. For more information, see [Jekyll](https://jekyllrb.com/). -O Jekyll não é oficialmente compatível com o Windows. Para obter mais informações, consulte "[Jekyll no Windows](http://jekyllrb.com/docs/windows/#installation)" na documentação do Jekyll. +Jekyll is not officially supported for Windows. For more information, see "[Jekyll on Windows](http://jekyllrb.com/docs/windows/#installation)" in the Jekyll documentation. -É recomendável usar o Jekyll com o {% data variables.product.prodname_pages %}. Se preferir, você pode usar outros geradores de site estáticos ou personalizar seu próprio processo de compilação localmente ou em outro servidor. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)". +We recommend using Jekyll with {% data variables.product.prodname_pages %}. If you prefer, you can use other static site generators or customize your own build process locally or on another server. For more information, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#static-site-generators)." -## Configurar o Jekyll em seu site do {% data variables.product.prodname_pages %} +## Configuring Jekyll in your {% data variables.product.prodname_pages %} site -É possível configurar a maioria das definições do Jekyll, como o tema e os plugins do seu site, editando o arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll. +You can configure most Jekyll settings, such as your site's theme and plugins, by editing your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. -Algumas definições de configuração não podem ser alteradas para sites do {% data variables.product.prodname_pages %}. +Some configuration settings cannot be changed for {% data variables.product.prodname_pages %} sites. ```yaml lsi: false @@ -56,36 +56,36 @@ kramdown: syntax_highlighter: rouge ``` -Por padrão, o Jekyll não cria arquivos nem pastas que: -- estão localizadas em uma pasta chamada `/node_modules` ou `/vendor` -- comece com `_`, `.` ou `#` -- terminam com `~` -- são excluídos pela configuração `exclude` em seu arquivo de configuração +By default, Jekyll doesn't build files or folders that: +- are located in a folder called `/node_modules` or `/vendor` +- start with `_`, `.`, or `#` +- end with `~` +- are excluded by the `exclude` setting in your configuration file -Se quiser que o Jekyll processe algum desses arquivos, você poderá usar a configuração `includes` no seu arquivo de configuração. +If you want Jekyll to process any of these files, you can use the `include` setting in your configuration file. -## Material inicial +## Front matter {% data reusables.pages.about-front-matter %} -Você pode adicionar `site.github` a uma publicação ou página para incluir metadados de referências de repositório ao seu site. Para obter mais informações, consulte "[Usar `site.github`](https://jekyll.github.io/github-metadata/site.github/)" na documentação de metadados do Jekyll. +You can add `site.github` to a post or page to add any repository references metadata to your site. For more information, see "[Using `site.github`](https://jekyll.github.io/github-metadata/site.github/)" in the Jekyll Metadata documentation. -## Temas +## Themes -{% data reusables.pages.add-jekyll-theme %} Para obter mais informações, consulte "[Temas](https://jekyllrb.com/docs/themes/)" na documentação do Jekyll. +{% data reusables.pages.add-jekyll-theme %} For more information, see "[Themes](https://jekyllrb.com/docs/themes/)" in the Jekyll documentation. {% ifversion fpt or ghec %} -É possível adicionar um tema compatível ao seu site no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Temas compatíveis](https://pages.github.com/themes/)" no site do {% data variables.product.prodname_pages %} e "[Adicionar um tema ao seu site do {% data variables.product.prodname_pages %} com o seletor de temas](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)". +You can add a supported theme to your site on {% data variables.product.prodname_dotcom %}. For more information, see "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and "[Adding a theme to your {% data variables.product.prodname_pages %} site with the theme chooser](/articles/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser)." To use any other open source Jekyll theme hosted on {% data variables.product.prodname_dotcom %}, you can add the theme manually.{% else %} You can add a theme to your site manually.{% endif %} For more information, see{% ifversion fpt or ghec %} [themes hosted on {% data variables.product.prodname_dotcom %}](https://github.com/topics/jekyll-theme) and{% else %} "[Supported themes](https://pages.github.com/themes/)" on the {% data variables.product.prodname_pages %} site and{% endif %} "[Adding a theme to your {% data variables.product.prodname_pages %} site using Jekyll](/articles/adding-a-theme-to-your-github-pages-site-using-jekyll)." -Você pode substituir qualquer um dos padrões do seu tema editando os arquivos do tema. Para obter mais informações, consulte a documentação do seu tema e "[Substituir padrões do tema](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" na documentação do Jekyll. +You can override any of your theme's defaults by editing the theme's files. For more information, see your theme's documentation and "[Overriding your theme's defaults](https://jekyllrb.com/docs/themes/#overriding-theme-defaults)" in the Jekyll documentation. ## Plugins -Você pode baixar ou criar plugins do Jekyll para ampliar a funcionalidade do Jekyll em seu site. Por exemplo, o plugin [jemoji](https://github.com/jekyll/jemoji) permite usar emoji em estilo do {% data variables.product.prodname_dotcom %} em qualquer página do seu site da mesma forma que você faria no {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Plugins](https://jekyllrb.com/docs/plugins/)" na documentação do Jekyll. +You can download or create Jekyll plugins to extend the functionality of Jekyll for your site. For example, the [jemoji](https://github.com/jekyll/jemoji) plugin lets you use {% data variables.product.prodname_dotcom %}-flavored emoji in any page on your site the same way you would on {% data variables.product.prodname_dotcom %}. For more information, see "[Plugins](https://jekyllrb.com/docs/plugins/)" in the Jekyll documentation. -O {% data variables.product.prodname_pages %} usa plugins que são habilitados por padrão e não podem ser desabilitados: +{% data variables.product.prodname_pages %} uses plugins that are enabled by default and cannot be disabled: - [`jekyll-coffeescript`](https://github.com/jekyll/jekyll-coffeescript) - [`jekyll-default-layout`](https://github.com/benbalter/jekyll-default-layout) - [`jekyll-gist`](https://github.com/jekyll/jekyll-gist) @@ -96,25 +96,25 @@ O {% data variables.product.prodname_pages %} usa plugins que são habilitados p - [`jekyll-titles-from-headings`](https://github.com/benbalter/jekyll-titles-from-headings) - [`jekyll-relative-links`](https://github.com/benbalter/jekyll-relative-links) -Você pode habilitar plugins adicionais incluindo a gem do plugin à configuração `plugins` em seu arquivo *_config.yml*. Para obter mais informações, consulte "[Configuração](https://jekyllrb.com/docs/configuration/)" na documentação do Jekyll. +You can enable additional plugins by adding the plugin's gem to the `plugins` setting in your *_config.yml* file. For more information, see "[Configuration](https://jekyllrb.com/docs/configuration/)" in the Jekyll documentation. -Para obter uma lista de plugins compatíveis, consulte "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. Para obter informações de uso para um plugin específico, consulte a documentação do plugin. +For a list of supported plugins, see "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. For usage information for a specific plugin, see the plugin's documentation. {% tip %} -**Dica:** você pode ter certeza de que está usando a versão mais recente de todos os plugins mantendo o gem do {% data variables.product.prodname_pages %} atualizado. Para obter mais informações, consulte "[Testar o site do GitHub Pages localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" e "[Versões de dependência](https://pages.github.com/versions/)" no site do {% data variables.product.prodname_pages %}. +**Tip:** You can make sure you're using the latest version of all plugins by keeping the {% data variables.product.prodname_pages %} gem updated. For more information, see "[Testing your GitHub Pages site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll#updating-the-github-pages-gem)" and "[Dependency versions](https://pages.github.com/versions/)" on the {% data variables.product.prodname_pages %} site. {% endtip %} -O {% data variables.product.prodname_pages %} não pode criar sites usando plugins incompatíveis. Se quiser usar plugins incompatíveis, gere seu site localmente e faça push dos arquivos estáticos do site no {% data variables.product.product_name %}. +{% data variables.product.prodname_pages %} cannot build sites using unsupported plugins. If you want to use unsupported plugins, generate your site locally and then push your site's static files to {% data variables.product.product_name %}. -## Realce de sintaxe +## Syntax highlighting -Para facilitar a leitura do seu site, trechos de código são destacados nos sites do {% data variables.product.prodname_pages %} da mesma maneira que são destacados no {% data variables.product.product_name %}. Para mais informações sobre destaque de sintaxe em {% data variables.product.product_name %}, consulte "[Criar e realçar blocos de código](/articles/creating-and-highlighting-code-blocks)". +To make your site easier to read, code snippets are highlighted on {% data variables.product.prodname_pages %} sites the same way they're highlighted on {% data variables.product.product_name %}. For more information about syntax highlighting on {% data variables.product.product_name %}, see "[Creating and highlighting code blocks](/articles/creating-and-highlighting-code-blocks)." -Por padrão, blocos de código no seu site serão destacados pelo Jekyll. O Jekyll usa o realçador [Rouge](https://github.com/jneen/rouge), que é compatível com [Pygments](http://pygments.org/). Se você especificar Pygments no arquivo *_config.yml*, Rouge será usado no lugar. O Jekyll não pode usar qualquer outro realçador de sintaxe, e você receberá um aviso de criação de página se especificar outro realçador de sintaxe no arquivo *_config.yml*. Para obter mais informações, consulte "[Sobre erros de criação do Jekyll para sites do {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". +By default, code blocks on your site will be highlighted by Jekyll. Jekyll uses the [Rouge](https://github.com/jneen/rouge) highlighter, which is compatible with [Pygments](http://pygments.org/). If you specify Pygments in your *_config.yml* file, Rouge will be used instead. Jekyll cannot use any other syntax highlighter, and you'll get a page build warning if you specify another syntax highlighter in your *_config.yml* file. For more information, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." -Se quiser usar outro realçador, como `highlight.js`, você deverá desabilitar o realce da sintaxe do Jekyll atualizando o arquivo *_config.yml* do projeto. +If you want to use another highlighter, such as `highlight.js`, you must disable Jekyll's syntax highlighting by updating your project's *_config.yml* file. ```yaml kramdown: @@ -122,12 +122,12 @@ kramdown: disable : true ``` -Se o seu tema não incluir CSS para realce da sintaxe, você poderá gerar CSS de realce de sintaxe do {% data variables.product.prodname_dotcom %} e adicioná-lo ao arquivo `style.css` do projeto. +If your theme doesn't include CSS for syntax highlighting, you can generate {% data variables.product.prodname_dotcom %}'s syntax highlighting CSS and add it to your project's `style.css` file. ```shell $ rougify style github > style.css ``` -## Criar site localmente +## Building your site locally {% data reusables.pages.test-locally %} diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 4b37a72160..c5b53d6108 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -36,15 +36,34 @@ If Jekyll does attempt to build your site and encounters an error, you will rece For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -## Viewing Jekyll build error messages +{% ifversion fpt %} +## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} + +By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." +{% note %} + +{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + +{% endnote %} +{% endif %} + +## Viewing your repository's build failures on {% data variables.product.product_name %} + +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. + +## Viewing Jekyll build error messages locally We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +## Viewing Jekyll build error messages in your pull request + When you create a pull request to update your publishing source on {% data variables.product.product_name %}, you can see build error messages on the **Checks** tab of the pull request. For more information, see "[About status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)." +## Viewing Jekyll build errors by email + When you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} -You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +## Viewing Jekyll build error messages in your pull request with a third-party CI service You can configure a third-party service, such as [Travis CI](https://travis-ci.org/), to display error messages after each commit. diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 81a779b387..43c4262281 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -1,6 +1,6 @@ --- -title: Criar um site do GitHub Pages com o Jekyll -intro: 'É possível usar o Jekyll para criar um site do {% data variables.product.prodname_pages %} em um repositório novo ou existente.' +title: Creating a GitHub Pages site with Jekyll +intro: 'You can use Jekyll to create a {% data variables.product.prodname_pages %} site in a new or existing repository.' product: '{% data reusables.gated-features.pages %}' redirect_from: - /articles/creating-a-github-pages-site-with-jekyll @@ -13,20 +13,20 @@ versions: ghec: '*' topics: - Pages -shortTitle: Criar site com o Jekyll +shortTitle: Create site with Jekyll --- {% data reusables.pages.org-owners-can-restrict-pages-creation %} -## Pré-requisitos +## Prerequisites -Antes de poder usar o Jekyll para criar um site do {% data variables.product.prodname_pages %}, você precisa instalar o Jekyll e o Git. Para obter mais informações, consulte [Instalação](https://jekyllrb.com/docs/installation/) na documentação do Jekyll e "[Configurar o Git](/articles/set-up-git)". +Before you can use Jekyll to create a {% data variables.product.prodname_pages %} site, you must install Jekyll and Git. For more information, see [Installation](https://jekyllrb.com/docs/installation/) in the Jekyll documentation and "[Set up Git](/articles/set-up-git)." {% data reusables.pages.recommend-bundler %} {% data reusables.pages.jekyll-install-troubleshooting %} -## Criar um repositório para seu site +## Creating a repository for your site {% data reusables.pages.new-or-existing-repo %} @@ -35,67 +35,67 @@ Antes de poder usar o Jekyll para criar um site do {% data variables.product.pro {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} -## Criar seu site +## Creating your site {% data reusables.pages.must-have-repo-first %} {% data reusables.pages.private_pages_are_public_warning %} {% data reusables.command_line.open_the_multi_os_terminal %} -1. Se você ainda não tem uma cópia do seu repositório, navegue até o local onde deseja armazenar os arquivos de origem do seu site, substituindo _PARENT-FOLDER_ pela pasta que deverá conter a pasta do repositório. +1. If you don't already have a local copy of your repository, navigate to the location where you want to store your site's source files, replacing _PARENT-FOLDER_ with the folder you want to contain the folder for your repository. ```shell $ cd PARENT-FOLDER ``` -1. Caso você ainda não o tenha feito, inicialize um repositório Git local, substituindo _REPOSITORY-NAME_ pelo nome do seu repositório. +1. If you haven't already, initialize a local Git repository, replacing _REPOSITORY-NAME_ with the name of your repository. ```shell $ git init REPOSITORY-NAME > Initialized empty Git repository in /Users/octocat/my-site/.git/ - # Cria uma nova pasta no seu computador, inicializada como um repositório Git + # Creates a new folder on your computer, initialized as a Git repository ``` - 4. Altere os diretórios no repositório. + 4. Change directories to the repository. ```shell $ cd REPOSITORY-NAME - # Altera o diretório de trabalho + # Changes the working directory ``` {% data reusables.pages.decide-publishing-source %} {% data reusables.pages.navigate-publishing-source %} - Por exemplo, se você escolheu publicar o seu site a partir da pasta `documentação` no branch-padrão, crie e altere os diretórios na pasta `documentação`. + For example, if you chose to publish your site from the `docs` folder on the default branch, create and change directories to the `docs` folder. ```shell $ mkdir docs - # Cria uma nova pasta chamada docs + # Creates a new folder called docs $ cd docs ``` - Se você optou por publicar seu site a partir do branch `gh-pages`, crie e faça checkout do branch `gh-pages`. + If you chose to publish your site from the `gh-pages` branch, create and checkout the `gh-pages` branch. ```shell $ git checkout --orphan gh-pages - # Cria um novo branch, sem histórico ou conteúdo, chamado gh-pages e alterna para o branch gh-pages + # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch ``` -1. Para criar um novo site do Jekyll, use o comando `jekyll new`: +1. To create a new Jekyll site, use the `jekyll new` command: ```shell $ jekyll new --skip-bundle . - # Cria um site do Jekyll no diretório atual + # Creates a Jekyll site in the current directory ``` -1. Abra o Gemfile que o Jekyll criou. -1. Adicione "#" ao início da linha que começa com `gem "jekyll"` para comentar nesta linha. -1. Adicione o gem `github-pages` editando a linha que começa com `# gem "github-pages"`. Mudar esta linha para: +1. Open the Gemfile that Jekyll created. +1. Add "#" to the beginning of the line that starts with `gem "jekyll"` to comment out this line. +1. Add the `github-pages` gem by editing the line starting with `# gem "github-pages"`. Change this line to: ```shell gem "github-pages", "~> GITHUB-PAGES-VERSION", group: :jekyll_plugins ``` - Substitua _GITHUB-PAGES-VERSÃO_ pela última versão compatível do gem de `github-pages`. Você pode encontrar esta versão aqui: "[Versões de dependência](https://pages.github.com/versions/)". + Replace _GITHUB-PAGES-VERSION_ with the latest supported version of the `github-pages` gem. You can find this version here: "[Dependency versions](https://pages.github.com/versions/)." - A versão correta do Jekyll será instalada como uma dependência do gem de `github-pages`. -1. Salve e feche o Gemfile. -1. Da linha de comando, execute `bundle install`. -1. Opcionalmente, faça todas as edições necessárias no arquivo `_config.yml`. Isto é necessário para caminhos relativos quando o repositório é hospedado em um subdiretório. Para obter mais informações, consulte "[Dividindo uma subpasta em um novo repositório](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)." + The correct version Jekyll will be installed as a dependency of the `github-pages` gem. +1. Save and close the Gemfile. +1. From the command line, run `bundle install`. +1. Optionally, make any necessary edits to the `_config.yml` file. This is required for relative paths when the repository is hosted in a subdirectory. For more information, see "[Splitting a subfolder out into a new repository](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)." ```yml domain: my-site.github.io # if you want to force HTTPS, specify the domain without the http at the start, e.g. example.com url: https://my-site.github.io # the base hostname and protocol for your site, e.g. http://example.com baseurl: /REPOSITORY-NAME/ # place folder name if the site is served in a subfolder ``` -1. Como alternativa, teste seu site localmente. Para obter mais informações, consulte "[Testar seu site do {% data variables.product.prodname_pages %} localmente com o Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)". -1. Adicione e faça commit do seu trabalho. +1. Optionally, test your site locally. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." +1. Add and commit your work. ```shell git add . git commit -m 'Initial GitHub pages site with Jekyll' @@ -108,7 +108,7 @@ $ git remote add origin https://github.com/USER/REPOSITORY.git $ git remote add origin https://HOSTNAME/USER/REPOSITORY.git {% endif %} ``` -1. Faça push no repositório para o {% data variables.product.product_name %}, substituindo _BRANCH_ pelo nome do branch em que você está trabalhando. +1. Push the repository to {% data variables.product.product_name %}, replacing _BRANCH_ with the name of the branch you're working on. ```shell $ git push -u origin BRANCH ``` @@ -119,11 +119,12 @@ $ git remote add origin https://HOSTNAME/USER/REPOSITORY Configuration file: /Users/octocat/my-site/_config.yml @@ -48,17 +48,17 @@ Antes de usar o Jekyll para testar um site, você deve: > Server address: http://127.0.0.1:4000/ > Server running... press ctrl-c to stop. ``` -3. Para visualizar o site, navegue para `http://localhost:4000` no navegador da web. +3. To preview your site, in your web browser, navigate to `http://localhost:4000`. -## Atualizar o gem do {% data variables.product.prodname_pages %} +## Updating the {% data variables.product.prodname_pages %} gem -O Jekyll é um projeto ativo de código aberto que é atualizado com frequência. Se o gem `github-pages` no seu computador estiver desatualizado em relação ao gem `github-pages` no servidor do {% data variables.product.prodname_pages %}, seu site poderá ter uma aparência diferente da criada localmente quando for publicado no {% data variables.product.product_name %}. Para evitar isso, atualize regularmente o gem `github-pages` no seu computador. +Jekyll is an active open source project that is updated frequently. If the `github-pages` gem on your computer is out of date with the `github-pages` gem on the {% data variables.product.prodname_pages %} server, your site may look different when built locally than when published on {% data variables.product.product_name %}. To avoid this, regularly update the `github-pages` gem on your computer. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Atualize o gem `github-pages`. - - Se você instalou o bundler, execute `bundle update github-pages`. - - Se não tiver o bundler instalado, execute `gem update github-pages`. +2. Update the `github-pages` gem. + - If you installed Bundler, run `bundle update github-pages`. + - If you don't have Bundler installed, run `gem update github-pages`. -## Leia mais +## Further reading -- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) na documentação do Jekyll +- [{% data variables.product.prodname_pages %}](http://jekyllrb.com/docs/github-pages/) in the Jekyll documentation diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md index baa1318e54..c9264010b1 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/index.md @@ -1,8 +1,8 @@ --- -title: Lidar com conflitos de merge -intro: 'Se suas alterações apresentarem conflitos de merge com o branch base, você deverá resolver esses conflitos para que seja possível fazer merge das alterações da pull request.' +title: Addressing merge conflicts +intro: 'If your changes have merge conflicts with the base branch, you must address the merge conflicts before you can merge your pull request''s changes.' redirect_from: - - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/ + - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts - /articles/addressing-merge-conflicts - /github/collaborating-with-pull-requests/addressing-merge-conflicts versions: @@ -16,6 +16,5 @@ children: - /about-merge-conflicts - /resolving-a-merge-conflict-on-github - /resolving-a-merge-conflict-using-the-command-line -shortTitle: Resolver conflitos de merge +shortTitle: Address merge conflicts --- - diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md index 9dd0f8c4f8..7354246bea 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md @@ -1,9 +1,9 @@ --- -title: Resolver um conflito de merge usando a linha de comando -intro: Você pode resolver conflitos de merge usando a linha de comando e um editor de texto. +title: Resolving a merge conflict using the command line +intro: You can resolve merge conflicts using the command line and a text editor. redirect_from: - /github/collaborating-with-issues-and-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line - - /articles/resolving-a-merge-conflict-from-the-command-line/ + - /articles/resolving-a-merge-conflict-from-the-command-line - /articles/resolving-a-merge-conflict-using-the-command-line - /github/collaborating-with-issues-and-pull-requests/resolving-a-merge-conflict-using-the-command-line - /github/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line @@ -14,44 +14,43 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Resolver conflitos de merge no Git +shortTitle: Resolve merge conflicts in Git --- - -Os conflitos de merge ocorrem quando alterações concorrentes são feitas na mesma linha de um arquivo ou quando uma pessoa edita um arquivo e outra pessoa exclui o mesmo arquivo. Para obter mais informações, consulte "[Sobre conflitos de merge](/articles/about-merge-conflicts/)". +Merge conflicts occur when competing changes are made to the same line of a file, or when one person edits a file and another person deletes the same file. For more information, see "[About merge conflicts](/articles/about-merge-conflicts/)." {% tip %} -**Dica:** você pode usar o editor de conflitos no {% data variables.product.product_name %} para resolver conflitos de merge de alterações diferentes na linha entre branches que fazem parte de uma pull request. Para obter mais informações, consulte "[Revolver um conflito de merge no GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)". +**Tip:** You can use the conflict editor on {% data variables.product.product_name %} to resolve competing line change merge conflicts between branches that are part of a pull request. For more information, see "[Resolving a merge conflict on GitHub](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-on-github)." {% endtip %} -## Conflitos de merge de alterações diferentes na linha +## Competing line change merge conflicts -Para resolver um conflito de merge causado por alterações diferentes na linha, você deve escolher quais alterações dos diferentes branches incorporar em um novo commit. +To resolve a merge conflict caused by competing line changes, you must choose which changes to incorporate from the different branches in a new commit. -Por exemplo, se você e outra pessoa editarem as mesmas linhas do arquivo _styleguide.md_ em branches diferentes do mesmo repositório Git, você receberá um erro de conflito de merge quando tentar fazer merge desses branches. Você deve resolver esse conflito de merge com um novo commit antes de fazer merge desses branches. +For example, if you and another person both edited the file _styleguide.md_ on the same lines in different branches of the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navegue até o repositório Git local que tem o conflito de merge. +2. Navigate into the local Git repository that has the merge conflict. ```shell cd REPOSITORY-NAME ``` -3. Gere uma lista dos arquivos afetados pelo conflito de merge. Neste exemplo, o arquivo *styleguide.md* tem um conflito de merge. +3. Generate a list of the files affected by the merge conflict. In this example, the file *styleguide.md* has a merge conflict. ```shell $ git status - > # No branch branch-b - > # Você desfez o merge de paths. - > # (resolver conflitos e executar "git commit") + > # On branch branch-b + > # You have unmerged paths. + > # (fix conflicts and run "git commit") > # - > # Desfazer merge de paths: - > # (use "git add ..." para marcar resoluções) + > # Unmerged paths: + > # (use "git add ..." to mark resolution) > # - > # ambos modificados: styleguide.md + > # both modified: styleguide.md > # - > nenhuma alteração adicionada ao commit (use "git add" e/ou "git commit -a") + > no changes added to commit (use "git add" and/or "git commit -a") ``` -4. Abra o editor de texto de sua preferência, como o [Atom](https://atom.io/), e navegue até o arquivo que tem conflitos de merge. -5. Para ver o começo do conflito de merge no arquivo, pesquise o marcador de conflito `<<<<<<<` no arquivo. Quando abrir o arquivo no editor de texto, você verá as alterações do branch HEAD ou base após a linha `<<<<<<< HEAD`. Em seguida, você verá `=======`, que divide suas alterações das alterações no outro branch, seguido por `>>>>>>> BRANCH-NAME`. Neste exemplo, uma pessoa escreveu "open an issue" (abrir um problema) no branch base ou HEAD e outra pessoa escreveu "ask your question in IRC" (faça sua pergunta no IRC) no branch de comparação ou `branch-a`. +4. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts. +5. To see the beginning of the merge conflict in your file, search the file for the conflict marker `<<<<<<<`. When you open the file in your text editor, you'll see the changes from the HEAD or base branch after the line `<<<<<<< HEAD`. Next, you'll see `=======`, which divides your changes from the changes in the other branch, followed by `>>>>>>> BRANCH-NAME`. In this example, one person wrote "open an issue" in the base or HEAD branch and another person wrote "ask your question in IRC" in the compare branch or `branch-a`. ``` If you have questions, please @@ -61,72 +60,72 @@ Por exemplo, se você e outra pessoa editarem as mesmas linhas do arquivo _style ask your question in IRC. >>>>>>> branch-a ``` -{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} Neste exemplo, as duas alterações são incorporadas ao merge final: +{% data reusables.pull_requests.decide-how-to-resolve-competing-line-change-merge-conflict %} In this example, both changes are incorporated into the final merge: ```shell If you have questions, please open an issue or ask in our IRC channel if it's more urgent. ``` -7. Adicione ou faça stage das alterações. +7. Add or stage your changes. ```shell $ git add . ``` -8. Faça o commit das suas alterações com um comentário. +8. Commit your changes with a comment. ```shell $ git commit -m "Resolved merge conflict by incorporating both suggestions." ``` -Agora você pode fazer merge dos branches na linha de comando ou [fazer push das alterações para o repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no {% data variables.product.product_name %} e [fazer merge das alterações](/articles/merging-a-pull-request/) em uma pull request. +You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request. -## Conflitos de merge de arquivo removido +## Removed file merge conflicts -Para resolver um conflito de merge causado por alterações concorrentes em um arquivo, quando uma pessoa exclui um arquivo em um branch e outra pessoa edita o mesmo arquivo, você deve escolher se deseja excluir ou manter o arquivo removido em um novo commit. +To resolve a merge conflict caused by competing changes to a file, where a person deletes a file in one branch and another person edits the same file, you must choose whether to delete or keep the removed file in a new commit. -Por exemplo, se você editou um arquivo, como o *README.md*, e outra pessoa removeu o mesmo arquivo em outro branch no mesmo repositório Git, você receberá um erro de conflito de merge quando tentar fazer merge desses branches. Você deve resolver esse conflito de merge com um novo commit antes de fazer merge desses branches. +For example, if you edited a file, such as *README.md*, and another person removed the same file in another branch in the same Git repository, you'll get a merge conflict error when you try to merge these branches. You must resolve this merge conflict with a new commit before you can merge these branches. {% data reusables.command_line.open_the_multi_os_terminal %} -2. Navegue até o repositório Git local que tem o conflito de merge. +2. Navigate into the local Git repository that has the merge conflict. ```shell cd REPOSITORY-NAME ``` -2. Gere uma lista dos arquivos afetados pelo conflito de merge. Neste exemplo, o arquivo *README.md* tem um conflito de merge. +2. Generate a list of the files affected by the merge conflict. In this example, the file *README.md* has a merge conflict. ```shell $ git status - > # No branch master - > # Seu branch e o 'origin/master'divergiram, - > # e possuem 1 e 2 diferentes commits cada, respectivamente. - > # (use "git pull" para fazer merge do branch remoto no seu) - > # Você desfez o merge de paths. - > # (resolver conflitos e executar "git commit") + > # On branch main + > # Your branch and 'origin/main' have diverged, + > # and have 1 and 2 different commits each, respectively. + > # (use "git pull" to merge the remote branch into yours) + > # You have unmerged paths. + > # (fix conflicts and run "git commit") > # - > # Desfazer merge de paths: - > # (use "git add/rm ..." conforme apropriado para marcar a resolução) + > # Unmerged paths: + > # (use "git add/rm ..." as appropriate to mark resolution) > # - > # excluído por nós: README.md + > # deleted by us: README.md > # - > # nenhuma alteração adicionada ao commit (use "git add" e/ou "git commit -a") + > # no changes added to commit (use "git add" and/or "git commit -a") ``` -3. Abra o editor de texto de sua preferência, como o [Atom](https://atom.io/), e navegue até o arquivo que tem conflitos de merge. -6. Decida se você deseja manter o arquivo removido. Você pode ver as alterações mais recentes feitas no arquivo removido no editor de texto. +3. Open your favorite text editor, such as [Atom](https://atom.io/), and navigate to the file that has merge conflicts. +6. Decide if you want keep the removed file. You may want to view the latest changes made to the removed file in your text editor. - Para adicionar o arquivo removido de volta ao repositório: + To add the removed file back to your repository: ```shell $ git add README.md ``` - Para remover o arquivo do seu repositório: + To remove this file from your repository: ```shell $ git rm README.md > README.md: needs merge > rm 'README.md' ``` -7. Faça o commit das suas alterações com um comentário. +7. Commit your changes with a comment. ```shell $ git commit -m "Resolved merge conflict by keeping README.md file." > [branch-d 6f89e49] Merge branch 'branch-c' into branch-d ``` -Agora você pode fazer merge dos branches na linha de comando ou [fazer push das alterações para o repositório remoto](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) no {% data variables.product.product_name %} e [fazer merge das alterações](/articles/merging-a-pull-request/) em uma pull request. +You can now merge the branches on the command line or [push your changes to your remote repository](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) on {% data variables.product.product_name %} and [merge your changes](/articles/merging-a-pull-request/) in a pull request. -## Leia mais +## Further reading -- "[Sobre conflitos de merge](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)" -- "[Fazer checkout de pull requests no local](/articles/checking-out-pull-requests-locally/)" +- "[About merge conflicts](/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/about-merge-conflicts)" +- "[Checking out pull requests locally](/articles/checking-out-pull-requests-locally/)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md index 12a9dba963..a578538671 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks.md @@ -1,9 +1,9 @@ --- -title: Sobre verificações de status -intro: As verificações de status permitem que você saiba se seus commits atendem às condições definidas para o repositório com o qual está contribuindo. +title: About status checks +intro: Status checks let you know if your commits meet the conditions set for the repository you're contributing to. redirect_from: - /github/collaborating-with-issues-and-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks - - /articles/about-statuses/ + - /articles/about-statuses - /articles/about-status-checks - /github/collaborating-with-issues-and-pull-requests/about-status-checks - /github/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks @@ -15,62 +15,61 @@ versions: topics: - Pull requests --- +Status checks are based on external processes, such as continuous integration builds, which run for each push you make to a repository. You can see the *pending*, *passing*, or *failing* state of status checks next to individual commits in your pull request. -As verificações de status se baseiam em processos externos, como compilações de integração contínua, que são executados para cada push que você faz em um repositório. Você pode ver o estado de *pendência*, *aprovação* ou *falha* das verificações de status ao lado de commits individuais em sua pull request. +![List of commits and statuses](/assets/images/help/pull_requests/commit-list-statuses.png) -![Lista de commits e status](/assets/images/help/pull_requests/commit-list-statuses.png) +Anyone with write permissions to a repository can set the state for any status check in the repository. -Qualquer pessoa com permissão de gravação em um repositório pode configurar o estado de qualquer verificação de status no repositório. - -É possível ver o estado geral do último commit em um branch na página de branches do seu repositório ou na lista de pull requests do seu repositório. +You can see the overall state of the last commit to a branch on your repository's branches page or in your repository's list of pull requests. {% data reusables.pull_requests.required-checks-must-pass-to-merge %} -## Tipos de verificação de status no {% data variables.product.product_name %} +## Types of status checks on {% data variables.product.product_name %} -Há dois tipos de verificação de status no {% data variables.product.product_name %}: +There are two types of status checks on {% data variables.product.product_name %}: -- Verificações -- Status +- Checks +- Statuses -As _Verificações_ são diferentes dos _status_ na medida que fornecem anotações de linha, mensagens mais detalhadas e só estão disponíveis para uso com {% data variables.product.prodname_github_apps %}. +_Checks_ are different from _statuses_ in that they provide line annotations, more detailed messaging, and are only available for use with {% data variables.product.prodname_github_apps %}. -Os proprietários da organização e usuários com acesso push a um repositório podem criar verificações e status com a API do {% data variables.product.product_name %}. Para obter mais informações, consulte "[Verificações](/rest/reference/checks)" e "[Status](/rest/reference/repos#statuses)". +Organization owners and users with push access to a repository can create checks and statuses with {% data variables.product.product_name %}'s API. For more information, see "[Checks](/rest/reference/checks)" and "[Statuses](/rest/reference/repos#statuses)." -## Verificações +## Checks -Quando _verificações_ são configuradas em um repositório, as pull requests apresentam uma guia **Checks** (Verificações), onde é possível exibir o resultado detalhado da compilação de verificações de status e executar novamente as verificações com falha. +When _checks_ are set up in a repository, pull requests have a **Checks** tab where you can view detailed build output from status checks and rerun failed checks. -![Verificações de status em uma pull request](/assets/images/help/pull_requests/checks.png) +![Status checks within a pull request](/assets/images/help/pull_requests/checks.png) {% note %} -**Observação:** A aba **Verificações** só é preenchida para pull requests se você configurar _verificações_, não _status_, para o repositório. +**Note:** The **Checks** tab only gets populated for pull requests if you set up _checks_, not _statuses_, for the repository. {% endnote %} -Quando uma linha específica em um commit causar a falha de uma verificação, você verá detalhes sobre a falha, o aviso ou a advertência ao lado do código relevante na guia **Files** (Arquivos) da pull request. +When a specific line in a commit causes a check to fail, you will see details about the failure, warning, or notice next to the relevant code in the **Files** tab of the pull request. -![Detalhes de uma verificação de status](/assets/images/help/pull_requests/checks-detailed.png) +![Details of a status check](/assets/images/help/pull_requests/checks-detailed.png) -Você pode navegar entre os resumos das verificações de vários commits em uma pull request usando o menu suspenso do commit na guia **Conversation** (Conversa). +You can navigate between the checks summaries for various commits in a pull request, using the commit drop-down menu under the **Conversation** tab. -![Resumos de verificação para diferentes commits em um menu suspenso](/assets/images/help/pull_requests/checks-summary-for-various-commits.png) +![Check summaries for different commits in a drop-down menu](/assets/images/help/pull_requests/checks-summary-for-various-commits.png) -### Ignorar e solicitar verificações para commits individuais +### Skipping and requesting checks for individual commits -Quando um repositório é definido para solicitar verificações por pushes automaticamente, você pode optar por ignorar as verificações para um commit individual do qual fez push. Quando um repositório _não_ é definido para solicitar verificações por pushes automaticamente, você pode solicitar verificações para um commit individual do qual fez push. Para obter mais informações sobre essas configurações, consulte "[Conjuntos de verificações](/rest/reference/checks#update-repository-preferences-for-check-suites)". +When a repository is set to automatically request checks for pushes, you can choose to skip checks for an individual commit you push. When a repository is _not_ set to automatically request checks for pushes, you can request checks for an individual commit you push. For more information on these settings, see "[Check Suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." -Para ignorar ou solicitar verificações para seu commit, adicione uma das seguintes linhas de trailer ao fim da mensagem do commit: +To skip or request checks for your commit, add one of the following trailer lines to the end of your commit message: -- Para _ignorar verificações_ para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. Após a descrição do commit, antes da cotação de fechamento, adicione duas linhas vazias seguidas de `skip-checks: true`: +- To _skip checks_ for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `skip-checks: true`: ```shell $ git commit -m "Update README > > skip-checks: true" ``` -- Para _solicitar_ verificações para um commit, digite a mensagem do commit e uma descrição breve e significativa das alterações. Após a descrição do commit, antes da cotação de fechamento, adicione duas linhas vazias seguidas de `request-checks: true`: +- To _request_ checks for a commit, type your commit message and a short, meaningful description of your changes. After your commit description, before the closing quotation, add two empty lines followed by `request-checks: true`: ```shell $ git commit -m "Refactor usability tests > diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md index 90498a828d..cdec1046a8 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md @@ -1,9 +1,9 @@ --- -title: Sobre merges de pull request +title: About pull request merges intro: 'You can [merge pull requests](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request) by retaining all the commits in a feature branch, squashing all commits into a single commit, or by rebasing individual commits from the `head` branch onto the `base` branch.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges - - /articles/about-pull-request-merge-squashing/ + - /articles/about-pull-request-merge-squashing - /articles/about-pull-request-merges - /github/collaborating-with-issues-and-pull-requests/about-pull-request-merges - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges @@ -15,47 +15,46 @@ versions: topics: - Pull requests --- - {% data reusables.pull_requests.default_merge_option %} -## Combinar por squash e fazer merge de commits da pull request +## Squash and merge your pull request commits {% data reusables.pull_requests.squash_and_merge_summary %} -### Mesclar mensagem para uma mesclagem por squash +### Merge message for a squash merge -Quando você faz combinação por squash e merge, o {% data variables.product.prodname_dotcom %} gera uma mensagem de commit que você pode mudar se quiser. O padrão da mensagem depende se a pull request contém vários commits ou apenas um. Nós não incluímos commits de merge quando contamos o número total de commits. +When you squash and merge, {% data variables.product.prodname_dotcom %} generates a commit message which you can change if you want to. The message default depends on whether the pull request contains multiple commits or just one. We do not include merge commits when we count the total number of commits. -| Número de commits | Sumário | Descrição | -| ----------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | -| Um commit | O título da mensagem de commit do único commit, seguido do número de pull request | O texto da mensagem de commit para o único commit | -| Mais de um commit | Título da pull request, seguido do número da pull request | Uma lista das mensagens de commit para todos os commits combinados por squash, por ordem de data | +Number of commits | Summary | Description | +----------------- | ------- | ----------- | +One commit | The title of the commit message for the single commit, followed by the pull request number | The body text of the commit message for the single commit +More than one commit | The pull request title, followed by the pull request number | A list of the commit messages for all of the squashed commits, in date order -### Fazendo combinação por squash e merge com um branch de longa duração +### Squashing and merging a long-running branch -Se você planeja continuar trabalhando no [branch head](/github/getting-started-with-github/github-glossary#head-branch) de uma pull request depois que a pull request for mesclada, recomendamos que você não combine por squash nem faça o merge da pull request. +If you plan to continue work on the [head branch](/github/getting-started-with-github/github-glossary#head-branch) of a pull request after the pull request is merged, we recommend you don't squash and merge the pull request. -Quando você cria uma pull request, o {% data variables.product.prodname_dotcom %} identifica o commit mais recente que existe tanto no branch head quanto no [branch base](/github/getting-started-with-github/github-glossary#base-branch): o commit de ancestral comum. Quando você combinar por squash e mesclar a pull request, o {% data variables.product.prodname_dotcom %} cria um commit no branch base que contém todas as alterações feitas no branch head desde o commit de ancestral comum. +When you create a pull request, {% data variables.product.prodname_dotcom %} identifies the most recent commit that is on both the head branch and the [base branch](/github/getting-started-with-github/github-glossary#base-branch): the common ancestor commit. When you squash and merge the pull request, {% data variables.product.prodname_dotcom %} creates a commit on the base branch that contains all of the changes you made on the head branch since the common ancestor commit. -Uma vez que esse commit está apenas no branch base e não no branch head, o ancestral comum dos dois branches permanece inalterado. Se você continuar a trabalhar no branch head e, em seguida, criar uma nova pull request entre os dois branches, a pull request incluirá todos os commits desde o ancestral comum, incluindo commits que você combinou por squash e fez merge na pull request anterior. Se não houver conflitos, você pode mesclar esses commits com segurança. No entanto, este fluxo de trabalho torna os conflitos de mesclagem mais prováveis. Se você continuar a combinar por squash e mesclar pull requests para um branch head de longo prazo, você terá que resolver os mesmos conflitos repetidamente. +Because this commit is only on the base branch and not the head branch, the common ancestor of the two branches remains unchanged. If you continue to work on the head branch, then create a new pull request between the two branches, the pull request will include all of the commits since the common ancestor, including commits that you squashed and merged in the previous pull request. If there are no conflicts, you can safely merge these commits. However, this workflow makes merge conflicts more likely. If you continue to squash and merge pull requests for a long-running head branch, you will have to resolve the same conflicts repeatedly. -## Fazer rebase e merge dos commits da sua pull request +## Rebase and merge your pull request commits {% data reusables.pull_requests.rebase_and_merge_summary %} -Você não pode fazer rebase e merge automaticamente no {% data variables.product.product_location %} quando: -- A pull request tem conflitos de merge. -- O rebase dos commits do branch base no branch head se depara com conflitos. -- O rebase dos commits é considerado "não seguro"; por exemplo, quando é possível fazer rebase sem conflitos de merge, mas que geraria um resultado diferente daquele que um merge geraria. +You aren't able to automatically rebase and merge on {% data variables.product.product_location %} when: +- The pull request has merge conflicts. +- Rebasing the commits from the base branch into the head branch runs into conflicts. +- Rebasing the commits is considered "unsafe," such as when a rebase is possible without merge conflicts but would produce a different result than a merge would. -Se ainda quiser fazer rebase dos commits, mas não puder fazer rebase e merge automaticamente no {% data variables.product.product_location %}, você deverá: -- Fazer rebase do branch de tópico (ou branch head) no branch base localmente na linha de comando -- [Resolver qualquer conflito de merge na linha de comando](/articles/resolving-a-merge-conflict-using-the-command-line/). -- Forçar push dos commits com rebase no branch de tópico da pull request (ou branch head remoto). +If you still want to rebase the commits but can't rebase and merge automatically on {% data variables.product.product_location %} you must: +- Rebase the topic branch (or head branch) onto the base branch locally on the command line +- [Resolve any merge conflicts on the command line](/articles/resolving-a-merge-conflict-using-the-command-line/). +- Force-push the rebased commits to the pull request's topic branch (or remote head branch). -Qualquer pessoa com permissões de gravação no repositório pode [fazer merge das alterações](/articles/merging-a-pull-request/) usando o botão de rebase e merge no {% data variables.product.product_location %}. +Anyone with write permissions in the repository, can then [merge the changes](/articles/merging-a-pull-request/) using the rebase and merge button on {% data variables.product.product_location %}. -## Leia mais +## Further reading -- "[Sobre pull requests](/articles/about-pull-requests)" -- "[Solucionar conflitos de merge](/github/collaborating-with-pull-requests/addressing-merge-conflicts)" +- "[About pull requests](/articles/about-pull-requests/)" +- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md index 9fe7763b2f..cf9dabb2ea 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md @@ -1,8 +1,8 @@ --- -title: Incluir alterações de uma pull request -intro: 'É possível propor alterações em seu trabalho no {% data variables.product.product_name %} por meio de pull requests. Aprenda como criar, gerenciar e fazer merge de pull requests.' +title: Incorporating changes from a pull request +intro: 'You can propose changes to your work on {% data variables.product.product_name %} through pull requests. Learn how to create, manage, and merge pull requests.' redirect_from: - - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/ + - /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request - /articles/incorporating-changes-from-a-pull-request - /github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request versions: @@ -19,6 +19,5 @@ children: - /adding-a-pull-request-to-the-merge-queue - /closing-a-pull-request - /reverting-a-pull-request -shortTitle: Incorporar alterações +shortTitle: Incorporate changes --- - diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md index b14dec6166..60c225594f 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md @@ -3,7 +3,7 @@ title: About branches intro: 'Use a branch to isolate development work without affecting other branches in the repository. Each repository has one default branch, and can have multiple other branches. You can merge a branch into another branch using a pull request.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches - - /articles/working-with-protected-branches/ + - /articles/working-with-protected-branches - /articles/about-branches - /github/collaborating-with-issues-and-pull-requests/about-branches - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md index 04002cc4a8..a488f3afd5 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests.md @@ -3,7 +3,7 @@ title: About pull requests intro: 'Pull requests let you tell others about changes you''ve pushed to a branch in a repository on {% data variables.product.product_name %}. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests - - /articles/using-pull-requests/ + - /articles/using-pull-requests - /articles/about-pull-requests - /github/collaborating-with-issues-and-pull-requests/about-pull-requests - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests diff --git a/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 b/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 index f3bf58b413..aeff18cc0b 100644 --- a/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 +++ b/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 @@ -3,7 +3,7 @@ title: Creating and deleting branches within your repository intro: 'You can create or delete branches directly on {% data variables.product.product_name %}.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository - - /articles/deleting-branches-in-a-pull-request/ + - /articles/deleting-branches-in-a-pull-request - /articles/creating-and-deleting-branches-within-your-repository - /github/collaborating-with-issues-and-pull-requests/creating-and-deleting-branches-within-your-repository versions: diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md index aabf7dd4c2..6a5e87fe5c 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/index.md @@ -1,8 +1,8 @@ --- -title: Propor alterações no trabalho com pull requests -intro: 'Depois de adicionar alterações em um branch de tópico ou bifurcação, você pode abrir uma pull request para solicitar que seus colaboradores ou o administrador do repositório revisem as alterações antes de fazer merge delas no projeto.' +title: Proposing changes to your work with pull requests +intro: 'After you add changes to a topic branch or fork, you can open a pull request to ask your collaborators or the repository administrator to review your changes before merging them into the project.' redirect_from: - - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests/ + - /github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests - /articles/proposing-changes-to-your-work-with-pull-requests - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests versions: @@ -24,6 +24,5 @@ children: - /requesting-a-pull-request-review - /changing-the-base-branch-of-a-pull-request - /committing-changes-to-a-pull-request-branch-created-from-a-fork -shortTitle: Propor alterações +shortTitle: Propose changes --- - diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md index 3f36a21b44..fc4cd43b04 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request.md @@ -1,6 +1,6 @@ --- -title: Usar parâmetros de consulta para criar um pull request -intro: Usar parâmetros de consulta para criar URLs personalizadas para abrir pull requests com campos pré-preenchidos. +title: Using query parameters to create a pull request +intro: Use query parameters to create custom URLs to open pull requests with pre-populated fields. redirect_from: - /github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request versions: @@ -12,25 +12,25 @@ topics: - Pull requests --- -Você pode usar parâmetros de consulta para abrir pull requests. Os parâmetros de consulta são partes opcionais de uma URL que você pode personalizar para compartilhar uma visualização específica da página, tais como resultados de filtro de pesquisa ou um modelo de pull request em {% data variables.product.prodname_dotcom %}. Para criar seus próprios parâmetros de consulta, você deve corresponder o par de chave e valor. +You can use query parameters to open pull requests. Query parameters are optional parts of a URL you can customize to share a specific web page view, such as search filter results or a pull request template on {% data variables.product.prodname_dotcom %}. To create your own query parameters, you must match the key and value pair. {% tip %} -**Dica:** Você também pode criar modelos de pull request que abrem com as etiquetas padrão, responsáveis e um título de pull request. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". +**Tip:** You can also create pull request templates that open with default labels, assignees, and an pull request title. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." {% endtip %} -Você deve ter as permissões adequadas para qualquer ação para usar o parâmetro de consulta equivalente. Por exemplo, você precisa de permissão para adicionar uma etiqueta a um pull request para usar os parâmetros de consulta de `etiquetas`. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +You must have the proper permissions for any action to use the equivalent query parameter. For example, you must have permission to add a label to a pull request to use the `labels` query parameter. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." -Se você criar uma URL inválida usando parâmetros de consulta, ou se você não tiver as permissões adequadas, a URL retornará uma página de erro `404 Not Found`. Se você criar uma URL que excede o limite do servidor, a URL retornará uma página de erro de `414 URI Too Long`. +If you create an invalid URL using query parameters, or if you don’t have the proper permissions, the URL will return a `404 Not Found` error page. If you create a URL that exceeds the server limit, the URL will return a `414 URI Too Long` error page. -| Parâmetro de consulta | Exemplo | -| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` cria um pull request que compara o branch base `main` e o branch principal `my-branch`. A consulta `quick_pull=1` leva você diretamente para a página "Open a pull request". | -| `title` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` cria um pull request com a etiqueta "erro" e o título "correção de erro". | -| `texto` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` cria um pull request com o título "Correção de erro" e o comentário "Descreva a correção" no texto do pull request. | -| `etiquetas` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` cria um pull request com as etiquetas "help wanted" e "bug". | -| `marco` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` cria um pull request com o marco "testing milestones". | -| `assignees` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` cria um pull request e o atribui a @octocat. | -| `projetos` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` cria um pull request com o título "Bug fix" e a adiciona ao quadro do projeto da organização 1. | -| `modelo` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` cria um pull request com um template no texto do pull request. O parâmetro de consulta `template` funciona com modelos armazenados em um subdiretório `PULL_REQUEST_TEMPLATE` dentro da raiz, `docs/` ou diretório do `.github/` em um repositório. Para obter mais informações, consulte "[Usar modelos para incentivar problemas úteis e pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)". | +Query parameter | Example +--- | --- +`quick_pull` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1` creates a pull request that compares the base branch `main` and head branch `my-branch`. The `quick_pull=1` query brings you directly to the "Open a pull request" page. +`title` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=bug&title=Bug+fix+report` creates a pull request with the label "bug" and title "Bug fix." +`body` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&body=Describe+the+fix.` creates a pull request with the title "Bug fix" and the comment "Describe the fix" in the pull request body. +`labels` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&labels=help+wanted,bug` creates a pull request with the labels "help wanted" and "bug". +`milestone` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&milestone=testing+milestones` creates a pull request with the milestone "testing milestones." +`assignees` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&assignees=octocat` creates a pull request and assigns it to @octocat. +`projects` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&title=Bug+fix&projects=octo-org/1` creates a pull request with the title "Bug fix" and adds it to the organization's project board 1. +`template` | `https://github.com/octo-org/octo-repo/compare/main...my-branch?quick_pull=1&template=issue_template.md` creates a pull request with a template in the pull request body. The `template` query parameter works with templates stored in a `PULL_REQUEST_TEMPLATE` subdirectory within the root, `docs/` or `.github/` directory in a repository. For more information, see "[Using templates to encourage useful issues and pull requests](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)." diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md index fb7f246ad1..81e0efb039 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request.md @@ -1,14 +1,14 @@ --- -title: Fazer comentários em uma pull request +title: Commenting on a pull request redirect_from: - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request - - /articles/adding-commit-comments/ - - /articles/commenting-on-the-diff-of-a-pull-request/ - - /articles/commenting-on-differences-between-files/ + - /articles/adding-commit-comments + - /articles/commenting-on-the-diff-of-a-pull-request + - /articles/commenting-on-differences-between-files - /articles/commenting-on-a-pull-request - /github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request -intro: 'Depois de abrir uma pull request em um repositório, os colaboradores ou integrantes da equipe podem comentar na comparação dos arquivos entre os dois branches especificados ou deixar os comentários gerais no projeto como um todo.' +intro: 'After you open a pull request in a repository, collaborators or team members can comment on the comparison of files between the two specified branches, or leave general comments on the project as a whole.' versions: fpt: '*' ghes: '*' @@ -16,51 +16,51 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Comentar em um PR +shortTitle: Comment on a PR --- +## About pull request comments -## Sobre comentários da pull request +You can comment on a pull request's **Conversation** tab to leave general comments, questions, or props. You can also suggest changes that the author of the pull request can apply directly from your comment. -Você pode fazer comentários na guia **Conversation** (Conversa) de uma pull request para deixar comentários gerais, perguntas ou complementos. Você também pode sugerir alterações que o autor da pull request pode aplicar diretamente a partir do seu comentário. +![Pull Request conversation](/assets/images/help/pull_requests/conversation.png) -![Conversa da pull request](/assets/images/help/pull_requests/conversation.png) +You can also comment on specific sections of a file on a pull request's **Files changed** tab in the form of individual line comments or as part of a [pull request review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adding line comments is a great way to discuss questions about implementation or provide feedback to the author. -Também é possível comentar em seções específicas de um arquivo na guia **Files changed** (Arquivos alterados) de uma pull request na forma de comentários em linha individuais ou como parte de uma [revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews). Adicionar comentários em linha é uma excelente maneira de discutir questões sobre implementação ou fornecer feedback ao autor. - -Para obter mais informações sobre como adicionar comentários em linha a uma revisão de pull request, consulte ["Revisar alterações propostas em uma pull request"](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request). +For more information on adding line comments to a pull request review, see ["Reviewing proposed changes in a pull request."](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) {% note %} -**Observação:** se você responder a uma pull request por e-mail, seu comentário será adicionado na guia **Conversation** (Conversa) e não fará parte de uma revisão de pull request. +**Note:** If you reply to a pull request via email, your comment will be added on the **Conversation** tab and will not be part of a pull request review. {% endnote %} -Para responder a um comentário em linha existente, é preciso navegar até o comentário na guia **Conversation** (Conversa) ou **Files changed** (Arquivos alterados) e incluir um comentário em linha adicional abaixo dele. +To reply to an existing line comment, you'll need to navigate to the comment on either the **Conversation** tab or **Files changed** tab and add an additional line comment below it. {% tip %} -**Dicas:** -- Os comentários da pull request aceitam a mesma [formatação](/categories/writing-on-github) como comentários regulares no {% data variables.product.product_name %}, como @menções, emoji e referências. -- Você pode adicionar reações aos comentários em pull requests na aba **Arquivos alterados**. +**Tips:** +- Pull request comments support the same [formatting](/categories/writing-on-github) as regular comments on {% data variables.product.product_name %}, such as @mentions, emoji, and references. +- You can add reactions to comments in pull requests in the **Files changed** tab. {% endtip %} -## Adicionar comentários em linha a uma pull request +## Adding line comments to a pull request {% data reusables.repositories.sidebar-pr %} -2. Na lista de pull requests, clique na pull request onde deseja deixar comentários em linha. +2. In the list of pull requests, click the pull request where you'd like to leave line comments. {% data reusables.repositories.changed-files %} {% data reusables.repositories.start-line-comment %} {% data reusables.repositories.type-line-comment %} {% data reusables.repositories.suggest-changes %} -5. Quando tiver concluído, clique em **>Add single comment** (Adicionar único comentário). ![Janela de comentários inline](/assets/images/help/commits/inline-comment.png) +5. When you're done, click **Add single comment**. + ![Inline comment window](/assets/images/help/commits/inline-comment.png) -Qualquer pessoa que inspeciona a pull request ou o repositório receberá uma notificação de seu comentário. +Anyone watching the pull request or repository will receive a notification of your comment. {% data reusables.pull_requests.resolving-conversations %} -## Leia mais +## Further reading -- "[Escrevendo no GitHub](/github/writing-on-github)" -{% ifversion fpt or ghec %}- "[Denunciar abuso ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)" +- "[Writing on GitHub](/github/writing-on-github)" +{% ifversion fpt or ghec %}- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)" {% endif %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md index 98f2e6e6df..bd7a9b087f 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md @@ -1,9 +1,9 @@ --- -title: Filtrar arquivos em uma pull request -intro: 'Para facilitar a rápida revisão de alterações em uma pull request extensa, você pode filtrar arquivos alterados.' +title: Filtering files in a pull request +intro: 'To help you quickly review changes in a large pull request, you can filter changed files.' redirect_from: - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request - - /articles/filtering-files-in-a-pull-request-by-file-type/ + - /articles/filtering-files-in-a-pull-request-by-file-type - /articles/filtering-files-in-a-pull-request - /github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request @@ -14,24 +14,25 @@ versions: ghec: '*' topics: - Pull requests -shortTitle: Filtrar arquivos +shortTitle: Filter files --- - -Você pode filtrar arquivos em um pull request por tipo de extensão de arquivo, como `. tml` ou `.js`, falta de uma extensão, propriedade de código ou dotfiles. +You can filter files in a pull request by file extension type, such as `.html` or `.js`, lack of an extension, code ownership, or dotfiles. {% tip %} -**Dica:** para simplificar a visualização do diff do pull request, também é possível ocultar temporariamente os arquivos excluídos ou aqueles que você já visualizou no diff do pull request a partir menu suspenso Filtro de arquivo. +**Tip:** To simplify your pull request diff view, you can also temporarily hide deleted files or files you have already viewed in the pull request diff from the file filter drop-down menu. {% endtip %} {% data reusables.repositories.sidebar-pr %} -2. Na lista de pull requests, clique na pull request que você gostaria de filtrar. +2. In the list of pull requests, click the pull request you'd like to filter. {% data reusables.repositories.changed-files %} -4. Use o menu suspenso File filter (Filtro de arquivo) e selecione, desmarque ou clique nos filtros desejados. ![Opção File filter (Filtro de arquivo) acima do diff da pull request](/assets/images/help/pull_requests/file-filter-option.png) -5. Como opção, para limpar a seleção de filtro, abaixo da aba **Files changed** (Arquivos alterados) clique em **Clear** (Limpar). ![Limpar a seleção File filter (Filtro de arquivo)](/assets/images/help/pull_requests/clear-file-filter.png) +4. Use the File filter drop-down menu, and select, unselect, or click the desired filters. + ![File filter option above pull request diff](/assets/images/help/pull_requests/file-filter-option.png) +5. Optionally, to clear the filter selection, under the **Files changed** tab, click **Clear**. + ![Clear file filter selection](/assets/images/help/pull_requests/clear-file-filter.png) -## Leia mais +## Further reading -- "[Sobre comparar branches em uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)" -- "[Encontrar métodos e funções alterados em uma pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)" +- "[About comparing branches in a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests)" +- "[Finding changed methods and functions in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/finding-changed-methods-and-functions-in-a-pull-request)" diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md index 2d8abb45b7..94e8467a8d 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/index.md @@ -1,11 +1,11 @@ --- title: Reviewing changes in pull requests redirect_from: - - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests/ - - /articles/reviewing-and-discussing-changes-in-pull-requests/ + - /github/collaborating-with-issues-and-pull-requests/reviewing-changes-in-pull-requests + - /articles/reviewing-and-discussing-changes-in-pull-requests - /articles/reviewing-changes-in-pull-requests - /github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests -intro: 'Depois de abrir uma pull request, você pode revisar e comentar um conjunto de alterações propostas.' +intro: 'After a pull request has been opened, you can review and discuss the set of proposed changes.' versions: fpt: '*' ghes: '*' @@ -25,6 +25,5 @@ children: - /approving-a-pull-request-with-required-reviews - /dismissing-a-pull-request-review - /checking-out-pull-requests-locally -shortTitle: Revisar alterações +shortTitle: Review changes --- - diff --git a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md index 2eea27bdf8..7ad5e448ca 100644 --- a/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md +++ b/translations/pt-BR/content/rest/guides/best-practices-for-integrators.md @@ -1,8 +1,8 @@ --- -title: Práticas recomendadas para integradores +title: Best practices for integrators intro: 'Build an app that reliably interacts with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API and provides the best experience for your users.' redirect_from: - - /guides/best-practices-for-integrators/ + - /guides/best-practices-for-integrators - /v3/guides/best-practices-for-integrators versions: fpt: '*' @@ -11,63 +11,63 @@ versions: ghec: '*' topics: - API -shortTitle: Práticas recomendadas do integrador +shortTitle: Integrator best practices --- -Interessado em integrar-se à plataforma do GitHub? [Você está em boas mãos](https://github.com/integrations). Este guia ajudará você a construir um aplicativo que fornece a melhor experiência para seus usuários *e* garantir que interaja, de modo confiável, com a API. +Interested in integrating with the GitHub platform? [You're in good company](https://github.com/integrations). This guide will help you build an app that provides the best experience for your users *and* ensure that it's reliably interacting with the API. -## Garante cargas seguras entregues a partir do GitHub +## Secure payloads delivered from GitHub -É muito importante que você assegure [as cargas enviadas pelo GitHub][event-types]. Embora nenhuma informação pessoal (como senha) seja transmitida em uma carga, não é bom vazar *quaisquer informações*. Algumas informações que podem ser sensíveis incluem endereços de e-mail do committer ou os nomes de repositórios privados. +It's very important that you secure [the payloads sent from GitHub][event-types]. Although no personal information (like passwords) is ever transmitted in a payload, leaking *any* information is not good. Some information that might be sensitive include committer email address or the names of private repositories. -Há várias etapas que você pode dar para garantir o recebimento de cargas entregues pelo GitHub: +There are several steps you can take to secure receipt of payloads delivered by GitHub: -1. Certifique-se de que seu servidor de recebimento tenha uma conexão HTTPS. Por padrão, o GitHub verificará os certificados SSL ao entregar cargas.{% ifversion fpt or ghec %} -1. Você pode adicionar [o endereço IP que usamos ao entregar hooks](/github/authenticating-to-github/about-githubs-ip-addresses) à lista de permissões do seu servidor. Para garantir que você esteja sempre verificando o endereço IP correto, você pode [usar o ponto de extremidade `/meta`](/rest/reference/meta#meta) para encontrar o endereço que utilizamos.{% endif %} -1. Forneça [um token secreto](/webhooks/securing/) para garantir que as cargas estão definitivamente vindo do GitHub. Ao impor um token secreto, você garantirá que todos os dados recebidos pelo seu servidor estejam absolutamente vindo do GitHub. Idealmente, você deve fornecer um token secreto diferente *por usuário* do seu serviço. Dessa forma, se um token for comprometido, nenhum outro usuário será afetado. +1. Ensure that your receiving server is on an HTTPS connection. By default, GitHub will verify SSL certificates when delivering payloads.{% ifversion fpt or ghec %} +1. You can add [the IP address we use when delivering hooks](/github/authenticating-to-github/about-githubs-ip-addresses) to your server's allow list. To ensure that you're always checking the right IP address, you can [use the `/meta` endpoint](/rest/reference/meta#meta) to find the address we use.{% endif %} +1. Provide [a secret token](/webhooks/securing/) to ensure payloads are definitely coming from GitHub. By enforcing a secret token, you're ensuring that any data received by your server is absolutely coming from GitHub. Ideally, you should provide a different secret token *per user* of your service. That way, if one token is compromised, no other user would be affected. -## Favoreça o trabalho assíncrono em detrimento do trabalho síncrono +## Favor asynchronous work over synchronous -O GitHub espera que as integrações respondam dentro de {% ifversion fpt or ghec %}10{% else %}30{% endif %} segundos após receber a carga do webhook. Se o seu serviço demorar mais do que isso para ser concluído, o GitHub encerrará a conexão e a carga será perdida. +GitHub expects that integrations respond within {% ifversion fpt or ghec %}10{% else %}30{% endif %} seconds of receiving the webhook payload. If your service takes longer than that to complete, then GitHub terminates the connection and the payload is lost. -Como é impossível prever a rapidez com que o seu serviço será concluído, você deve fazer todo o "trabalho real" em um trabalho que atue em segundo plano. [Resque](https://github.com/resque/resque/) (para Ruby), [RQ](http://python-rq.org/) (para Python) ou [RabbitMQ](http://www.rabbitmq.com/) (para Java) são exemplos de bibliotecas que podem lidar com a fila e o processamento de trabalhos em segundo plano. +Since it's impossible to predict how fast your service will complete, you should do all of "the real work" in a background job. [Resque](https://github.com/resque/resque/) (for Ruby), [RQ](http://python-rq.org/) (for Python), or [RabbitMQ](http://www.rabbitmq.com/) (for Java) are examples of libraries that can handle queuing and processing of background jobs. -Observe que, mesmo com um trabalho em segundo plano, o GitHub ainda espera que seu servidor responda no prazo de {% ifversion fpt or ghec %}dez{% else %}trinta{% endif %} segundos. Seu servidor precisa reconhecer que recebeu a carga enviando algum tipo de resposta. É fundamental que o seu serviço realize qualquer validação em uma carga o mais rápido possível para que você possa relatar com precisão se o seu servidor irá continuar com a solicitação ou não. +Note that even with a background job running, GitHub still expects your server to respond within {% ifversion fpt or ghec %}ten{% else %}thirty{% endif %} seconds. Your server needs to acknowledge that it received the payload by sending some sort of response. It's critical that your service performs any validations on a payload as soon as possible, so that you can accurately report whether your server will continue with the request or not. -## Use códigos de status de HTTP apropriados ao responder ao GitHub +## Use appropriate HTTP status codes when responding to GitHub -Cada webhook tem sua própria seção de "Entregas Recentes", que lista se uma implantação foi bem-sucedida ou não. +Every webhook has its own "Recent Deliveries" section, which lists whether a deployment was successful or not. -![Vista das entregas recentes](/assets/images/webhooks_recent_deliveries.png) +![Recent Deliveries view](/assets/images/webhooks_recent_deliveries.png) -Você deve usar códigos de status de HTTP apropriados para informar aos usuários. Você pode usar códigos como `201` ou `202` para reconhecer que o recebimento da carga não será processado (por exemplo, uma carga entregue por um branch que não é padrão). Reserve o código de erro `500` para falhas catastróficas. +You should make use of proper HTTP status codes in order to inform users. You can use codes like `201` or `202` to acknowledge receipt of payload that won't be processed (for example, a payload delivered by a branch that's not the default). Reserve the `500` error code for catastrophic failures. -## Forneça o máximo de informações possível para o usuário +## Provide as much information as possible to the user -Os usuários podem entrar nas respostas do servidor que você enviar de volta ao GitHub. Certifique-se de que suas mensagens sejam claras e informativas. +Users can dig into the server responses you send back to GitHub. Ensure that your messages are clear and informative. -![Visualizar uma resposta de carga](/assets/images/payload_response_tab.png) +![Viewing a payload response](/assets/images/payload_response_tab.png) -## Siga qualquer redirecionamento que a API enviar para você +## Follow any redirects that the API sends you -O GitHub é explícito ao informar quando um recurso foi movido, fornecendo um código de estado de redirecionamento. Você deveria seguir estes redirecionamentos. Cada resposta de redirecionamento define o cabeçalho da `Localização` com a nova URI a ser acessada. Se você receber um redirecionamento, é melhor atualizar seu código para seguir a nova URI, caso você esteja solicitando um caminho obsoleto que possamos remover. +GitHub is explicit in telling you when a resource has moved by providing a redirect status code. You should follow these redirections. Every redirect response sets the `Location` header with the new URI to go to. If you receive a redirect, it's best to update your code to follow the new URI, in case you're requesting a deprecated path that we might remove. -Nós fornecemos [uma lista de códigos de status de HTTP](/rest#http-redirects) que você pode consultar ao projetar o seu aplicativo para seguir redirecionamentos. +We've provided [a list of HTTP status codes](/rest#http-redirects) to watch out for when designing your app to follow redirects. -## Não analise as URLs manualmente +## Don't manually parse URLs -Muitas vezes, as respostas da API contêm dados na forma de URLs. Por exemplo, ao solicitar um repositório, enviaremos uma chave denominada `clone_url` com uma URL que você pode usar para clonar o repositório. +Often, API responses contain data in the form of URLs. For example, when requesting a repository, we'll send a key called `clone_url` with a URL you can use to clone the repository. -Para a estabilidade do seu aplicativo, você não deve tentar analisar esses dados ou tentar adivinhar e construir o formato de URLs futuras. Seu app será poderá falhar se decidirmos alterar a URL. +For the stability of your app, you shouldn't try to parse this data or try to guess and construct the format of future URLs. Your app is liable to break if we decide to change the URL. -Por exemplo, ao trabalhar com resultados paginados, muitas vezes é tentador construir URLs que anexam `?page=` ao final. Evite essa tentação. [Nosso guia sobre paginação](/guides/traversing-with-pagination) oferece algumas dicas seguras sobre o acompanhamento de resultados paginados de forma dependente. +For example, when working with paginated results, it's often tempting to construct URLs that append `?page=` to the end. Avoid that temptation. [Our guide on pagination](/guides/traversing-with-pagination) offers some safe tips on dependably following paginated results. -## Verifique o tipo de evento e a ação antes de processar o evento +## Check the event type and action before processing the event -Existem vários [tipos de eventos de webhook][event-types], e cada evento pode ter várias ações. À medida que a configuração de recursos do GitHub crescer, adicionaremos, ocasionalmente, novos tipos de evento ou adicionaremos novas ações aos tipos de evento existentes. Certifique-se de que sua aplicação verifica, explicitamente, o tipo e a ação de um evento antes de realizar qualquer processamento de webhook. O cabeçalho de solicitação `X-GitHub-Event` pode ser usado para saber qual evento foi recebido para que o processamento possa ser tratado adequadamente. Da mesma forma, a carga tem uma chave de `ação` de nível superior que pode ser usada para saber qual ação foi tomada no objeto relevante. +There are multiple [webhook event types][event-types], and each event can have multiple actions. As GitHub's feature set grows, we will occasionally add new event types or add new actions to existing event types. Ensure that your application explicitly checks the type and action of an event before doing any webhook processing. The `X-GitHub-Event` request header can be used to know which event has been received so that processing can be handled appropriately. Similarly, the payload has a top-level `action` key that can be used to know which action was taken on the relevant object. -Por exemplo, se você configurou um webhook do GitHub para "Envie-me **tudo**", o seu aplicativo começará a receber novos tipos de eventos e ações conforme forem adicionados. Portanto, **não se recomenda usar qualquer tipo de cláusula "else", que recebe tudo**. Veja o código a seguir como exemplo: +For example, if you have configured a GitHub webhook to "Send me **everything**", your application will begin receiving new event types and actions as they are added. It is therefore **not recommended to use any sort of catch-all else clause**. Take the following code example: ```ruby # Not recommended: a catch-all else clause @@ -86,9 +86,9 @@ def receive end ``` -Neste exemplo de código, os métodos `process_repository` e `process_issues` serão corretamente chamados se o evento `repositório` ou `problemas` foi recebido. No entanto, qualquer outro tipo de evento resultaria na chamada de `process_pull_requests`. Uma vez que novos tipos de eventos são adicionados, isso resultaria em comportamento incorreto e novos tipos de eventos seriam processados da mesma forma que um evento `pull_request` seria processado. +In this code example, the `process_repository` and `process_issues` methods will be correctly called if a `repository` or `issues` event was received. However, any other event type would result in `process_pull_requests` being called. As new event types are added, this would result in incorrect behavior and new event types would be processed in the same way that a `pull_request` event would be processed. -Em vez disso, sugerimos que se verifiquem explicitamente os tipos de eventos e que se se tomem as ações de acordo com isso. No exemplo a seguir do código, verificamos, explicitamente, um evento `pull_request` e a cláusula `else` simplesmente registra que recebemos um novo tipo de evento: +Instead, we suggest explicitly checking event types and acting accordingly. In the following code example, we explicitly check for a `pull_request` event and the `else` clause simply logs that we've received a new event type: ```ruby # Recommended: explicitly check each event type @@ -109,9 +109,9 @@ def receive end ``` -Como cada evento também pode ter várias ações, recomenda-se que as ações sejam verificadas da mesma forma. Por exemplo, o [`IssuesEvent`](/webhooks/event-payloads/#issues) tem várias ações possíveis. Estas incluem `aberto` quando o problema é criado, `fechado` quando o problema é fechado e `atribuído` quando o problema é atribuído a alguém. +Because each event can also have multiple actions, it's recommended that actions are checked similarly. For example, the [`IssuesEvent`](/webhooks/event-payloads/#issues) has several possible actions. These include `opened` when the issue is created, `closed` when the issue is closed, and `assigned` when the issue is assigned to someone. -Assim como a adição de tipos de evento, podemos adicionar novas ações aos eventos existentes. Portanto, novamente **não se recomenda usar qualquer tipo de cláusula "else" para receber tudo** ao verificar a ação de um evento. Em vez disso, sugerimos que verifique explicitamente as ações de eventos, como fizemos com o tipo de evento. Um exemplo disso parece muito semelhante ao que sugerimos para os tipos de eventos acima: +As with adding event types, we may add new actions to existing events. It is therefore again **not recommended to use any sort of catch-all else clause** when checking an event's action. Instead, we suggest explicitly checking event actions as we did with the event type. An example of this looks very similar to what we suggested for event types above: ```ruby # Recommended: explicitly check each action @@ -129,40 +129,47 @@ def process_issue(payload) end ``` -Neste exemplo, a ação `fechada` é verificada antes de chamar o método `process_closed`. Quaisquer ações não identificadas são registradas para referência futura. +In this example the `closed` action is checked first before calling the `process_closed` method. Any unidentified actions are logged for future reference. {% ifversion fpt or ghec %} -## Lidar com limites de taxa +## Dealing with rate limits -O limite de câmbio da API [do GitHub](/rest/overview/resources-in-the-rest-api#rate-limiting) garante que a API seja rápida e disponível para todos. +The GitHub API [rate limit](/rest/overview/resources-in-the-rest-api#rate-limiting) ensures that the API is fast and available for everyone. -Se você atingir um limite de câmbio, espera-se que você recue ao fazer solicitações e tente novamente mais tarde quando for permitido fazer isso. O não cumprimento pode resultar no banimento do seu aplicativo. +If you hit a rate limit, it's expected that you back off from making requests and try again later when you're permitted to do so. Failure to do so may result in the banning of your app. -Você sempre poderá [verificar o status do seu limite de taxa](/rest/reference/rate-limit) a qualquer momento. Verificar seu limite de taxa não gera nenhum custo para o mesmo. +You can always [check your rate limit status](/rest/reference/rate-limit) at any time. Checking your rate limit incurs no cost against your rate limit. -## Lidando com limites de taxa secundária +## Dealing with secondary rate limits -[Os limites de taxa secundária](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) são outra forma de garantir a disponibilidade da API. Para evitar atingir este limite, você deverá certificar-se de que o seu aplicativo segue as diretrizes abaixo. +[Secondary rate limits](/rest/overview/resources-in-the-rest-api#secondary-rate-limits) are another way we ensure the API's availability. +To avoid hitting this limit, you should ensure your application follows the guidelines below. -* Faça solicitações autenticadas, ou use o ID de cliente e segredo do seu aplicativo. Os pedidos não autenticados estão sujeitos a limites de taxa secundária mais agressivos. -* Faça solicitações de um único usuário ou ID de cliente em série. Não faça solicitações para um único usuário ou ID de cliente simultaneamente. -* Se você estiver fazendo um grande número de solicitações `POST`, `PATCH`, `PUT` ou `DELETE` para um único usuário ou ID de cliente, espere pelo menos um segundo entre cada solicitação. -* Ao receber alguma restrição, use o cabeçalho de resposta `Retry-After` para diminuir a velocidade. O valor do cabeçalho `Retry-After` será sempre um inteiro, que representa o número de segundos que você deve esperar antes de fazer solicitações novamente. Por exemplo, `Retry-After: 30` significa que você deve esperar 30 segundos antes de enviar mais solicitações. -* Solicitações que criam conteúdo que acionam notificações, tais como problemas, comentários e pull requests, podem ser ainda mais limitadas e não incluirão um cabeçalho `Retry-After` na resposta. Crie este conteúdo em um ritmo razoável para evitar maiores limitações. +* Make authenticated requests, or use your application's client ID and secret. Unauthenticated + requests are subject to more aggressive secondary rate limiting. +* Make requests for a single user or client ID serially. Do not make requests for a single user + or client ID concurrently. +* If you're making a large number of `POST`, `PATCH`, `PUT`, or `DELETE` requests for a single user + or client ID, wait at least one second between each request. +* When you have been limited, use the `Retry-After` response header to slow down. The value of the + `Retry-After` header will always be an integer, representing the number of seconds you should wait + before making requests again. For example, `Retry-After: 30` means you should wait 30 seconds + before sending more requests. +* Requests that create content which triggers notifications, such as issues, comments and pull requests, + may be further limited and will not include a `Retry-After` header in the response. Please create this + content at a reasonable pace to avoid further limiting. -Nos nos reservamos o direito de alterar essas diretrizes, conforme necessário, para garantir a disponibilidade. +We reserve the right to change these guidelines as needed to ensure availability. {% endif %} -## Lidar com erros da API +## Dealing with API errors -Embora o seu código nunca introduzisse um erro, você pode descobrir que encontrou erros sucessivos ao tentar acessar a API. +Although your code would never introduce a bug, you may find that you've encountered successive errors when trying to access the API. -Ao invés de ignorar os códigos de status repetidos `4xx` e `5xx`, você deverá certificar-se de que você está interagindo corretamente com a API. Por exemplo, se um ponto de extremidade solicitar um string de caracteres e você estiver passando um valor numérico, você receberá um erro de validação de `5xx` e sua chamada não terá sucesso. Da mesma forma, tentar acessar um ponto de extremidade não autorizado ou inexistente, gerará um erro `4xx`. +Rather than ignore repeated `4xx` and `5xx` status codes, you should ensure that you're correctly interacting with the API. For example, if an endpoint requests a string and you're passing it a numeric value, you're going to receive a `5xx` validation error, and your call won't succeed. Similarly, attempting to access an unauthorized or nonexistent endpoint will result in a `4xx` error. -Ignorar intencionalmente erros de validação repetidos pode resultar na suspensão do seu aplicativo por abuso. - -[event-types]: /webhooks/event-payloads +Intentionally ignoring repeated validation errors may result in the suspension of your app for abuse. [event-types]: /webhooks/event-payloads diff --git a/translations/pt-BR/content/rest/guides/building-a-ci-server.md b/translations/pt-BR/content/rest/guides/building-a-ci-server.md index 67a1be8734..dbcec20196 100644 --- a/translations/pt-BR/content/rest/guides/building-a-ci-server.md +++ b/translations/pt-BR/content/rest/guides/building-a-ci-server.md @@ -1,8 +1,8 @@ --- -title: Criar um servidor de CI -intro: Crie o seu próprio sistema CI usando a API de status. +title: Building a CI server +intro: Build your own CI system using the Status API. redirect_from: - - /guides/building-a-ci-server/ + - /guides/building-a-ci-server - /v3/guides/building-a-ci-server versions: fpt: '*' @@ -15,22 +15,31 @@ topics: -A [API de Status][status API] é responsável por unir commits com um serviço de teste. para que cada push que você fizer possa ser testado e representado em um pull request do {% data variables.product.product_name %}. +The [Status API][status API] is responsible for tying together commits with +a testing service, so that every push you make can be tested and represented +in a {% data variables.product.product_name %} pull request. -Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos: +This guide will use that API to demonstrate a setup that you can use. +In our scenario, we will: -* Executar o nosso conjunto de CI quando um pull request for aberto (iremos definir o status de CI como pendente). -* Quando o CI terminar, definiremos o status do pull request. +* Run our CI suite when a Pull Request is opened (we'll set the CI status to pending). +* When the CI is finished, we'll set the Pull Request's status accordingly. -O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser Travis, Jenkins, ou qualquer outra coisa completamente diferente. O principal deste guia será criar e configurar o servidor de gerenciamento da comunicação. +Our CI system and host server will be figments of our imagination. They could be +Travis, Jenkins, or something else entirely. The crux of this guide will be setting up +and configuring the server managing the communication. -Se você ainda não tiver, certifique-se de [fazer o download do ngrok][ngrok]e aprender como [usá-lo][using ngrok]. Nós achamos que é uma ferramenta muito útil para expor conexões locais. +If you haven't already, be sure to [download ngrok][ngrok], and learn how +to [use it][using ngrok]. We find it to be a very useful tool for exposing local +connections. -Observação: você pode baixar o código-fonte completo para este projeto [no repositório de amostra de plataforma][platform samples]. +Note: you can download the complete source code for this project +[from the platform-samples repo][platform samples]. -## Escrever o seu servidor +## Writing your server -Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando. Vamos começar com isso: +We'll write a quick Sinatra app to prove that our local connections are working. +Let's start with this: ``` ruby require 'sinatra' @@ -42,20 +51,29 @@ post '/event_handler' do end ``` -(Se você não estiver familiarizado com a forma como Sinatra funciona, recomendamos [a leitura do guia do Sinatra][Sinatra].) +(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) -Inicie este servidor. Por padrão, o Sinatra começa na porta `4567`. Portanto, você deverá configurar o ngrok para começar a ouvir isso também. +Start this server up. By default, Sinatra starts on port `4567`, so you'll want +to configure ngrok to start listening for that, too. -Para que esse servidor funcione, precisamos configurar um repositório com um webhook. O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclada. Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? Em seguida, você criará um novo webhook no seu repositório, alimentando-o com a URL que o ngrok forneceu a você e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo: +In order for this server to work, we'll need to set a repository up with a webhook. +The webhook should be configured to fire whenever a Pull Request is created, or merged. +Go ahead and create a repository you're comfortable playing around in. Might we +suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? +After that, you'll create a new webhook in your repository, feeding it the URL +that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the +content type: -![Uma nova URL do ngrok](/assets/images/webhook_sample_url.png) +![A new ngrok URL](/assets/images/webhook_sample_url.png) -Clique em **Update webhook** (Atualizar webhook). Você deve ver uma resposta de texto de `Well, it worked!`. Ótimo! Clique em **Permita-me selecionar eventos individuais**e selecione o seguinte: +Click **Update webhook**. You should see a body response of `Well, it worked!`. +Great! Click on **Let me select individual events**, and select the following: * Status * Pull Request -Esses são os eventos que {% data variables.product.product_name %} serão enviados ao nosso servidor sempre que ocorrer a ação relevante. Vamos atualizar nosso servidor para *apenas* lidar com o cenário de pull request agora: +These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action +occurs. Let's update our server to *just* handle the Pull Request scenario right now: ``` ruby post '/event_handler' do @@ -76,15 +94,26 @@ helpers do end ``` -O que está acontecendo? Cada evento que {% data variables.product.product_name %} envia, anexa um cabeçalho de HTTP de `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. De lá, nós usaremos a carga das informações e retornaremos o campo de título. Em um cenário ideal, nosso servidor ficaria preocupado com cada vez que um pull request é atualizado, e não apenas quando ele é aberto. Isso asseguraria que todos os novos pushes passassem pelos testes de CI. Mas, para essa demonstração, nós nos preocuparemos quando ela for aberta. +What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` +HTTP header. We'll only care about the PR events for now. From there, we'll +take the payload of information, and return the title field. In an ideal scenario, +our server would be concerned with every time a pull request is updated, not just +when it's opened. That would make sure that every new push passes the CI tests. +But for this demo, we'll just worry about when it's opened. -Para testar esta prova de conceito, faça algumas alterações em um branch no repositório de teste e abra um pull request. Seu servidor deve responder de acordo! +To test out this proof-of-concept, make some changes in a branch in your test +repository, and open a pull request. Your server should respond accordingly! -## Trabalhar com status +## Working with statuses -Já que configuramos o nosso servidor, estamos prontos para iniciar nosso primeiro requisito, que é configurar (e atualizar) os status de CI. Observe que a sempre que você atualizar o seu servidor, você poderá clicar em **Entregar novamente** para enviar a mesma carga. Não há necessidade de fazer um novo pull request toda vez que você fizer uma alteração! +With our server in place, we're ready to start our first requirement, which is +setting (and updating) CI statuses. Note that at any time you update your server, +you can click **Redeliver** to send the same payload. There's no need to make a +new pull request every time you make a change! -Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] to manage our interactions. Vamos configurar esse cliente com +Since we're interacting with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll use [Octokit.rb][octokit.rb] +to manage our interactions. We'll configure that client with +[a personal access token][access token]: ``` ruby # !!! DO NOT EVER USE HARD-CODED VALUES IN A REAL APP !!! @@ -96,7 +125,8 @@ before do end ``` -Em seguida, vamos precisar atualizar o pull request no {% data variables.product.product_name %} para deixar claro que estamos processando na CI: +After that, we'll just need to update the pull request on {% data variables.product.product_name %} to make clear +that we're processing on the CI: ``` ruby def process_pull_request(pull_request) @@ -105,13 +135,16 @@ def process_pull_request(pull_request) end ``` -Aqui, estamos fazendo três coisas muito básicas: +We're doing three very basic things here: -* estamos procurando o nome completo do repositório -* estamos procurando o último SHA do pull request -* estamos definindo o status como "pendente" +* we're looking up the full name of the repository +* we're looking up the last SHA of the pull request +* we're setting the status to "pending" -Pronto! A partir daqui, você pode executar qualquer processo de que precise para executar o seu conjunto de testes. Talvez você vá passar seu código para o Jenkins, ou chamar em outro serviço da web através da sua API, como [Travis][travis api]. Em seguida, certifique-se de atualizar o status novamente. No nosso exemplo, vamos definir isso como`"sucesso"`: +That's it! From here, you can run whatever process you need to in order to execute +your test suite. Maybe you're going to pass off your code to Jenkins, or call +on another web service via its API, like [Travis][travis api]. After that, you'd +be sure to update the status once more. In our example, we'll just set it to `"success"`: ``` ruby def process_pull_request(pull_request) @@ -120,24 +153,33 @@ def process_pull_request(pull_request) @client.create_status(pull_request['base']['repo']['full_name'], pull_request['head']['sha'], 'success') puts "Pull request processed!" end -``` +``` -## Conclusão +## Conclusion -No GitHub, usamos uma versão do [Janky][janky] para gerenciar a nossa CI durante anos. O fluxo básico é essencialmente o mesmo que o servidor que construímos acima. No GitHub, nós: +At GitHub, we've used a version of [Janky][janky] to manage our CI for years. +The basic flow is essentially the exact same as the server we've built above. +At GitHub, we: -* Notificamos tudo ao Jenkins quando um pull request é criado ou atualizado (via Janky) -* Esperamos por uma resposta no estado da CI -* Se o código for verde, fazemos o merge do pull request +* Fire to Jenkins when a pull request is created or updated (via Janky) +* Wait for a response on the state of the CI +* If the code is green, we merge the pull request -Toda esta comunicação é canalizada de volta para nossas salas de bate-papo. Você não precisa construir sua própria configuração de CI para usar este exemplo. Você sempre pode confiar nas[Integrações do GitHub][integrations]. +All of this communication is funneled back to our chat rooms. You don't need to +build your own CI setup to use this example. +You can always rely on [GitHub integrations][integrations]. +[deploy API]: /rest/reference/repos#deployments [status API]: /rest/reference/repos#statuses [ngrok]: https://ngrok.com/ [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/building-a-ci-server [Sinatra]: http://www.sinatrarb.com/ +[webhook]: /webhooks/ [octokit.rb]: https://github.com/octokit/octokit.rb +[access token]: /articles/creating-an-access-token-for-command-line-use [travis api]: https://api.travis-ci.org/docs/ [janky]: https://github.com/github/janky +[heaven]: https://github.com/atmos/heaven +[hubot]: https://github.com/github/hubot [integrations]: https://github.com/integrations diff --git a/translations/pt-BR/content/rest/guides/delivering-deployments.md b/translations/pt-BR/content/rest/guides/delivering-deployments.md index 7fbe5d416c..13ad16c3da 100644 --- a/translations/pt-BR/content/rest/guides/delivering-deployments.md +++ b/translations/pt-BR/content/rest/guides/delivering-deployments.md @@ -1,9 +1,9 @@ --- -title: Entregar implantações -intro: 'Ao usar a API RESt de implantações, você pode criar ferramentas personalizadas que interagem com seu servidor e um aplicativo de terceiros.' +title: Delivering deployments +intro: 'Using the Deployments REST API, you can build custom tooling that interacts with your server and a third-party app.' redirect_from: - - /guides/delivering-deployments/ - - /guides/automating-deployments-to-integrators/ + - /guides/delivering-deployments + - /guides/automating-deployments-to-integrators - /v3/guides/delivering-deployments versions: fpt: '*' @@ -16,23 +16,33 @@ topics: -A [API de Implantações][deploy API] fornece seus projetos hospedados em {% data variables.product.product_name %} com a capacidade de lançá-los em um servidor do qual você é proprietário. Combinado com [a API de Status][status API], você será capaz de coordenar suas implantações no momento em que seu código chegar ao branch-padrão. +The [Deployments API][deploy API] provides your projects hosted on {% data variables.product.product_name %} with +the capability to launch them on a server that you own. Combined with +[the Status API][status API], you'll be able to coordinate your deployments +the moment your code lands on the default branch. -Este guia usará a API para demonstrar uma configuração que você pode usar. No nosso cenário, iremos: +This guide will use that API to demonstrate a setup that you can use. +In our scenario, we will: -* Fazer merge de um pull request -* Quando a CI terminar, definiremos o status do pull request. -* Quando o pull request for mesclado, executaremos a nossa implantação no nosso servidor. +* Merge a pull request +* When the CI is finished, we'll set the pull request's status accordingly. +* When the pull request is merged, we'll run our deployment to our server. -O nosso sistema de CI e servidor de hospedagem serão imaginários. Eles podem ser Heroku, Amazon, ou qualquer outra coisa completamente diferente. O principal deste guia será criar e configurar o servidor de gerenciamento da comunicação. +Our CI system and host server will be figments of our imagination. They could be +Heroku, Amazon, or something else entirely. The crux of this guide will be setting up +and configuring the server managing the communication. -Se você ainda não tiver, certifique-se de [fazer o download do ngrok][ngrok] e aprender como [usá-lo][using ngrok]. Nós achamos que é uma ferramenta muito útil para expor conexões locais. +If you haven't already, be sure to [download ngrok][ngrok], and learn how +to [use it][using ngrok]. We find it to be a very useful tool for exposing local +connections. -Observação: você pode baixar o código-fonte completo para este projeto [no repositório de amostra de plataforma][platform samples]. +Note: you can download the complete source code for this project +[from the platform-samples repo][platform samples]. -## Escrever o seu servidor +## Writing your server -Vamos escrever um aplicativo rápido do Sinatra para provar que nossas conexões locais estão funcionando. Vamos começar com isso: +We'll write a quick Sinatra app to prove that our local connections are working. +Let's start with this: ``` ruby require 'sinatra' @@ -44,21 +54,31 @@ post '/event_handler' do end ``` -(Se você não estiver familiarizado com a forma como Sinatra funciona, recomendamos [a leitura do guia do Sinatra][Sinatra].) +(If you're unfamiliar with how Sinatra works, we recommend [reading the Sinatra guide][Sinatra].) -Inicie este servidor. Por padrão, o Sinatra começa na porta `4567`. Portanto, você deverá configurar o ngrok para começar a ouvir isso também. +Start this server up. By default, Sinatra starts on port `4567`, so you'll want +to configure ngrok to start listening for that, too. -Para que esse servidor funcione, precisamos configurar um repositório com um webhook. O webhook deve ser configurado para ser acionado sempre que um pull request for criado ou mesclado. Vá em frente e crie um repositório com o qual você esteja confortável para fazer testes. Podemos sugerir [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? Em seguida, você criará um novo webhook no seu repositório, alimentando-o com a URL que o ngrok forneceu a você e escolhendo `application/x-www-form-urlencoded` como o tipo de conteúdo: +In order for this server to work, we'll need to set a repository up with a webhook. +The webhook should be configured to fire whenever a pull request is created, or merged. +Go ahead and create a repository you're comfortable playing around in. Might we +suggest [@octocat's Spoon/Knife repository](https://github.com/octocat/Spoon-Knife)? +After that, you'll create a new webhook in your repository, feeding it the URL +that ngrok gave you, and choosing `application/x-www-form-urlencoded` as the +content type: -![Uma nova URL do ngrok](/assets/images/webhook_sample_url.png) +![A new ngrok URL](/assets/images/webhook_sample_url.png) -Clique em **Update webhook** (Atualizar webhook). Você deve ver uma resposta de texto de `Well, it worked!`. Ótimo! Clique em **Permita-me selecionar eventos individuais** e selecione o seguinte: +Click **Update webhook**. You should see a body response of `Well, it worked!`. +Great! Click on **Let me select individual events.**, and select the following: -* Implantação -* Status da implantação +* Deployment +* Deployment status * Pull Request -Esses são os eventos que {% data variables.product.product_name %} serão enviados ao nosso servidor sempre que ocorrer a ação relevante. Vamos configurar nosso servidor para o manipular *apenas* quando pull requests forem mesclados neste momento: +These are the events {% data variables.product.product_name %} will send to our server whenever the relevant action +occurs. We'll configure our server to *just* handle when pull requests are merged +right now: ``` ruby post '/event_handler' do @@ -67,21 +87,26 @@ post '/event_handler' do case request.env['HTTP_X_GITHUB_EVENT'] when "pull_request" if @payload["action"] == "closed" && @payload["pull_request"]["merged"] - puts "A pull request was merged! Uma implantação deve começar agora..." + puts "A pull request was merged! A deployment should start now..." end end end ``` -O que está acontecendo? Cada evento que {% data variables.product.product_name %} envia, anexa um cabeçalho de HTTP de `X-GitHub-Event`. Por enquanto, nos importaremos apenas com os eventos do PR. Quando um pull request é mesclado (seu estado é `fechado` e `mesclado` é `verdadeiro`), vamos iniciar uma implantação. +What's going on? Every event that {% data variables.product.product_name %} sends out attached a `X-GitHub-Event` +HTTP header. We'll only care about the PR events for now. When a pull request is +merged (its state is `closed`, and `merged` is `true`), we'll kick off a deployment. -Para testar esta validação de conceito, faça algumas alterações em um branch no repositório de testes, abra um pull request e faça o merge. Seu servidor deve responder de acordo! +To test out this proof-of-concept, make some changes in a branch in your test +repository, open a pull request, and merge it. Your server should respond accordingly! -## Trabalhando com implantações +## Working with deployments -Como já temos o servidor configurado, o código que está sendo revisado e nosso pull request mesclado, queremos que nosso projeto seja implantado. +With our server in place, the code being reviewed, and our pull request +merged, we want our project to be deployed. -Vamos começar modificando nosso detector de evento para processar pull requests quando tiverem feito merge e começar a prestar atenção às implantações: +We'll start by modifying our event listener to process pull requests when they're +merged, and start paying attention to deployments: ``` ruby when "pull_request" @@ -95,7 +120,8 @@ when "deployment_status" end ``` -Com base na informação de uma solicitação, começaremos preenchendo o método `start_deployment`: +Based on the information from the pull request, we'll start by filling out the +`start_deployment` method: ``` ruby def start_deployment(pull_request) @@ -105,13 +131,19 @@ def start_deployment(pull_request) end ``` -As implantações podem ter alguns metadados anexados, na forma de `carga` e `descrição`. Embora esses valores sejam opcionais, é útil usar para registrar e representar informações. +Deployments can have some metadata attached to them, in the form of a `payload` +and a `description`. Although these values are optional, it's helpful to use +for logging and representing information. -Quando uma nova implantação é criada, um evento completamente separado é acionado. É por isso que temos um novo caso de `switch` no manipulador de eventos para `implantação`. Você pode usar esta informação para ser notificado quando uma implantação for acionada. +When a new deployment is created, a completely separate event is triggered. That's +why we have a new `switch` case in the event handler for `deployment`. You can +use this information to be notified when a deployment has been triggered. -As implantações podem demorar um pouco. Portanto, nós vamos precisar ouvir vários eventos, como quando a implantação foi criada e em que estado se encontra. +Deployments can take a rather long time, so we'll want to listen for various events, +such as when the deployment was created, and what state it's in. -Vamos simular uma implantação realize um trabalho e notar o efeito que ela tem na saída. Primeiro, vamos completar nosso método `process_deploy`: +Let's simulate a deployment that does some work, and notice the effect it has on +the output. First, let's complete our `process_deployment` method: ``` ruby def process_deployment @@ -125,7 +157,7 @@ def process_deployment end ``` -Por fim, vamos fazer a simulação do armazenamento da informação de status como a saída do console: +Finally, we'll simulate storing the status information as console output: ``` ruby def update_deployment_status @@ -133,20 +165,27 @@ def update_deployment_status end ``` -Vamos dividir o que está acontecendo. Uma nova implantação é criada por `start_deployment`, que aciona o evento `implantação`. A partir daí, chamamos `process_deployment` para simular o trabalho que está ocorrendo. Durante esse processamento, também fazemos uma chamada para `create_deployment_status`, que permite que um destinatário saiba o que está acontecendo, pois nós alteramos o status para `pendente`. +Let's break down what's going on. A new deployment is created by `start_deployment`, +which triggers the `deployment` event. From there, we call `process_deployment` +to simulate work that's going on. During that processing, we also make a call to +`create_deployment_status`, which lets a receiver know what's going on, as we +switch the status to `pending`. -Após a conclusão da implantação, definimos o status para `sucesso`. +After the deployment is finished, we set the status to `success`. -## Conclusão +## Conclusion -No GitHub, usamos uma versão do [Heavan][heaven] para gerenciar nossas implantações por anos. Um fluxo comum é essencialmente o mesmo que o servidor que construímos acima: +At GitHub, we've used a version of [Heaven][heaven] to manage +our deployments for years. A common flow is essentially the same as the +server we've built above: -* Aguarde uma resposta sobre o estado das verificações de CI (sucesso ou falha) -* Se as verificações forem bem-sucedidas, faça o merge do pull request -* Heaven toma o código mesclado e o implementa nos servidores de teste e produção -* Enquanto isso, o Heaven também notifica todos sobre a criação por meio do [Hubot][hubot] que aguarda nas nossas salas de bate-papo +* Wait for a response on the state of the CI checks (success or failure) +* If the required checks succeed, merge the pull request +* Heaven takes the merged code, and deploys it to staging and production servers +* In the meantime, Heaven also notifies everyone about the build, via [Hubot][hubot] sitting in our chat rooms -Pronto! Você não precisa criar sua própria configuração de implantação para usar este exemplo. Você sempre pode confiar nas [Integrações do GitHub][integrations]. +That's it! You don't need to build your own deployment setup to use this example. +You can always rely on [GitHub integrations][integrations]. [deploy API]: /rest/reference/repos#deployments [status API]: /guides/building-a-ci-server @@ -154,6 +193,11 @@ Pronto! Você não precisa criar sua própria configuração de implantação pa [using ngrok]: /webhooks/configuring/#using-ngrok [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/delivering-deployments [Sinatra]: http://www.sinatrarb.com/ +[webhook]: /webhooks/ +[octokit.rb]: https://github.com/octokit/octokit.rb +[access token]: /articles/creating-an-access-token-for-command-line-use +[travis api]: https://api.travis-ci.org/docs/ +[janky]: https://github.com/github/janky [heaven]: https://github.com/atmos/heaven [hubot]: https://github.com/github/hubot [integrations]: https://github.com/integrations diff --git a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md index 74f1211882..11f6410042 100644 --- a/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md +++ b/translations/pt-BR/content/rest/guides/discovering-resources-for-a-user.md @@ -2,7 +2,7 @@ title: Discovering resources for a user intro: Learn how to find the repositories and organizations that your app can access for a user in a reliable way for your authenticated requests to the REST API. redirect_from: - - /guides/discovering-resources-for-a-user/ + - /guides/discovering-resources-for-a-user - /v3/guides/discovering-resources-for-a-user versions: fpt: '*' diff --git a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md index 86d5220126..4e6053352c 100644 --- a/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md +++ b/translations/pt-BR/content/rest/guides/getting-started-with-the-rest-api.md @@ -2,7 +2,7 @@ title: Getting started with the REST API intro: 'Learn the foundations for using the REST API, starting with authentication and some endpoint examples.' redirect_from: - - /guides/getting-started/ + - /guides/getting-started - /v3/guides/getting-started versions: fpt: '*' diff --git a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md index e83530444e..a46becae06 100644 --- a/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md +++ b/translations/pt-BR/content/rest/guides/rendering-data-as-graphs.md @@ -1,8 +1,8 @@ --- -title: Representar dados como gráficos -intro: Aprenda a visualizar as linguagens de programação do seu repositório usando a biblioteca D3.js e o Ruby Octokit. +title: Rendering data as graphs +intro: Learn how to visualize the programming languages from your repository using the D3.js library and Ruby Octokit. redirect_from: - - /guides/rendering-data-as-graphs/ + - /guides/rendering-data-as-graphs - /v3/guides/rendering-data-as-graphs versions: fpt: '*' @@ -15,15 +15,21 @@ topics: -Neste guia, vamos usar a API para obter informações sobre repositórios dos quais somos proprietários e as linguagens de programação que as compõem. Em seguida, vamos visualizar essas informações de algumas formas diferentes usando a biblioteca [D3.js][D3.js]. To interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit]. +In this guide, we're going to use the API to fetch information about repositories +that we own, and the programming languages that make them up. Then, we'll +visualize that information in a couple of different ways using the [D3.js][D3.js] library. To +interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we'll be using the excellent Ruby library, [Octokit][Octokit]. -Caso você ainda não o tenha feito, você deve ler o guia ["Princípios básicos da autentifcação"][basics-of-authentication] antes de iniciar este exemplo. Você pode encontrar o código-fonte completo para este projeto no repositório de [platform-samples][platform samples]. +If you haven't already, you should read the ["Basics of Authentication"][basics-of-authentication] +guide before starting this example. You can find the complete source code for this project in the [platform-samples][platform samples] repository. -Vamos começar imediatamente! +Let's jump right in! -## Configurar um aplicativo OAuth +## Setting up an OAuth application -Primeiro, [registra um novo aplicativo ][new oauth application] no {% data variables.product.product_name %}. Define as URLs principais e a chamada de retorno para `http://localhost:4567/`. Assim como fizemos[anteriormente][basics-of-authentication], vamos gerenciar a autenticação da API implementando um Rack middleware usando [sinatra-auth-github][sinatra auth github]: +First, [register a new application][new oauth application] on {% data variables.product.product_name %}. Set the main and callback +URLs to `http://localhost:4567/`. As [before][basics-of-authentication], we're going to handle authentication for the API by +implementing a Rack middleware using [sinatra-auth-github][sinatra auth github]: ``` ruby require 'sinatra/auth/github' @@ -62,7 +68,7 @@ module Example end ``` -Configure um arquivo _config.ru_ semelhante ao exemplo anterior: +Set up a similar _config.ru_ file as in the previous example: ``` ruby ENV['RACK_ENV'] ||= 'development' @@ -74,11 +80,15 @@ require File.expand_path(File.join(File.dirname(__FILE__), 'server')) run Example::MyGraphApp ``` -## Buscar informações do repositório +## Fetching repository information -This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit Ruby library][Octokit]. Isso é muito mais fácil do que fazer diretamente um monte de chamadas de REST. Além disso, o Octokit foi desenvolvido por um GitHubber e é mantido ativamente, para que você saiba que vai funcionar. +This time, in order to talk to the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, we're going to use the [Octokit +Ruby library][Octokit]. This is much easier than directly making a bunch of +REST calls. Plus, Octokit was developed by a GitHubber, and is actively maintained, +so you know it'll work. -É fácil a autenticação com a API através do Octokit. Basta passar seu login e token para o `Octokit::Client` do cliente: +Authentication with the API via Octokit is easy. Just pass your login +and token to the `Octokit::Client` constructor: ``` ruby if !authenticated? @@ -88,13 +98,17 @@ else end ``` -Vamos fazer algo interessante com os dados sobre nossos repositórios. Vamos ver as diferentes linguagens de programação que eles usam e contar quais são usadas com maior frequência. Para fazer isso, primeiro precisaremos de uma lista dos nossos repositórios na API. Com o Octokit, será algo parecido com isso: +Let's do something interesting with the data about our repositories. We're going +to see the different programming languages they use, and count which ones are used +most often. To do that, we'll first need a list of our repositories from the API. +With Octokit, that looks like this: ``` ruby repos = client.repositories ``` -Em seguida, vamos iterar sobre cada repositório e contar a linguagem que {% data variables.product.product_name %} associa a ele: +Next, we'll iterate over each repository, and count the language that {% data variables.product.product_name %} +associates with it: ``` ruby language_obj = {} @@ -112,19 +126,25 @@ end languages.to_s ``` -Ao reiniciar seu servidor, sua página web deve exibir algo que se parece com isso: +When you restart your server, your web page should display something +that looks like this: ``` ruby {"JavaScript"=>13, "PHP"=>1, "Perl"=>1, "CoffeeScript"=>2, "Python"=>1, "Java"=>3, "Ruby"=>3, "Go"=>1, "C++"=>1} ``` -Até agora, tudo bem, mas isso não é não muito intuitivo para uma pessoa. Uma visualização seria excelente para nos ajudar a entender como as contagens de linguagens são distribuídas. Vamos alimentar nossas contagens em D3 para obter um gráfico de barras que represente a popularidade dos idiomas que usamos. +So far, so good, but not very human-friendly. A visualization +would be great in helping us understand how these language counts are distributed. Let's feed +our counts into D3 to get a neat bar graph representing the popularity of the languages we use. -## Visualizar contagens de linguagem +## Visualizing language counts -D3.js, ou apenas D3, é uma biblioteca abrangente para criar muitos tipos de gráficos, gráficos e visualizações interativas. Usar D3 em detalhes está fora do âmbito deste guia, mas para um bom artigo introdutório consulte ["D3 para mortais"][D3 mortals]. +D3.js, or just D3, is a comprehensive library for creating many kinds of charts, graphs, and interactive visualizations. +Using D3 in detail is beyond the scope of this guide, but for a good introductory article, +check out ["D3 for Mortals"][D3 mortals]. -D3 é uma biblioteca JavaScript, e gosta de trabalhar com dados como arrays. Então, vamos converter o nosso hash do Ruby em um array de JSON para uso por JavaScript no navegador. +D3 is a JavaScript library, and likes working with data as arrays. So, let's convert our Ruby hash into +a JSON array for use by JavaScript in the browser. ``` ruby languages = [] @@ -135,9 +155,13 @@ end erb :lang_freq, :locals => { :languages => languages.to_json} ``` -Estamos simplesmente iterando sobre cada par chave-valor no nosso objeto e empurrando-os para um novo array. A razão pela qual não fizemos isso anteriormente foi porque não queríamos iterar sobre o nosso objeto `language_obj` enquanto o estávamos criando. +We're simply iterating over each key-value pair in our object and pushing them into +a new array. The reason we didn't do this earlier is because we didn't want to iterate +over our `language_obj` object while we were creating it. -Agora, _lang_freq.erb_ vai precisar de um pouco de JavaScript para ajudar a interpretação de um gráfico de barras. Por enquanto, você pode simplesmente usar o código fornecido aqui e consultar os recursos vinculados acima se quiser saber mais sobre como o D3 funciona: +Now, _lang_freq.erb_ is going to need some JavaScript to support rendering a bar graph. +For now, you can just use the code provided here, and refer to the resources linked above +if you want to learn more about how D3 works: ``` html @@ -218,15 +242,26 @@ Agora, _lang_freq.erb_ vai precisar de um pouco de JavaScript para ajudar a inte ``` -Ufa! Novamente, não se preocupe com o que a maior parte deste código está fazendo. Aqui, a parte relevante é uma linha na parte superior--`var data = <%= languages %>;`--que indica que estamos passando o nosso array de `linguagens` criado previamente para o ERB para manipulação. +Phew! Again, don't worry about what most of this code is doing. The relevant part +here is a line way at the top--`var data = <%= languages %>;`--which indicates +that we're passing our previously created `languages` array into ERB for manipulation. -Como o guia "D3 para mortais" sugere, este não é necessariamente a melhor forma de utilizar o D3. No entanto, serve para ilustrar como você pode usar a biblioteca, junto com Octokit, para fazer algumas coisas realmente incríveis. +As the "D3 for Mortals" guide suggests, this isn't necessarily the best use of +D3. But it does serve to illustrate how you can use the library, along with Octokit, +to make some really amazing things. -## Combinar diferentes chamadas de API +## Combining different API calls -Agora é hora de fazer uma confissão: o atributo da `linguagem` dentro dos repositórios identifica apenas a linguagem "primária" definida. Isso significa que se você tiver um repositório que combina várias linguagens. aquela que tiver mais bytes de código será considerada a linguagem primária. +Now it's time for a confession: the `language` attribute within repositories +only identifies the "primary" language defined. That means that if you have +a repository that combines several languages, the one with the most bytes of code +is considered to be the primary language. -Vamos combinar algumas chamadas de API para obter uma _verdadeira_ representação de qual linguagem tem o maior número de bytes escritos em todo o nosso código. Um [treemap][D3 treemap] deve ser uma ótima forma de visualizar os tamanhos das nossas linguagens de codificação usadas, em vez de simplesmente contar. Precisamos construir um array de objetos que se pareçam com isto: +Let's combine a few API calls to get a _true_ representation of which language +has the greatest number of bytes written across all our code. A [treemap][D3 treemap] +should be a great way to visualize the sizes of our coding languages used, rather +than simply the count. We'll need to construct an array of objects that looks +something like this: ``` json [ { "name": "language1", "size": 100}, @@ -235,7 +270,8 @@ Vamos combinar algumas chamadas de API para obter uma _verdadeira_ representaç ] ``` -Como já temos uma lista de repositórios acima, vamos inspecionar cada um e chamar o [método da API para listar a linguagem][language API]: +Since we already have a list of repositories above, let's inspect each one, and +call [the language listing API method][language API]: ``` ruby repos.each do |repo| @@ -244,7 +280,7 @@ repos.each do |repo| end ``` -A partir daí, adicionaremos cumulativamente cada linguagem encontrado a uma "lista-mestre": +From there, we'll cumulatively add each language found to a list of languages: ``` ruby repo_langs.each do |lang, count| @@ -256,7 +292,7 @@ repo_langs.each do |lang, count| end ``` -Em seguida vamos formatar o conteúdo em uma estrutura que o D3 entende: +After that, we'll format the contents into a structure that D3 understands: ``` ruby language_obj.each do |lang, count| @@ -267,15 +303,16 @@ end language_bytes = [ :name => "language_bytes", :elements => language_byte_count] ``` -(Para obter mais informações sobre um mapa de árvore do D3, confira [este tutorial simples][language API].) +(For more information on D3 tree map magic, check out [this simple tutorial][language API].) -Para concluir, passamos esta informação JSON para o mesmo modelo de ERB: +To wrap up, we pass this JSON information over to the same ERB template: ``` ruby erb :lang_freq, :locals => { :languages => languages.to_json, :language_byte_count => language_bytes.to_json} ``` -Conforme fizemos anteriormente, aqui está um monte de JavaScript que você pode soltar diretamente no seu modelo: +Like before, here's a bunch of JavaScript that you can drop +directly into your template: ``` html
@@ -325,18 +362,19 @@ Conforme fizemos anteriormente, aqui está um monte de JavaScript que você pode ``` -Et voila! São lindos retângulos que contém suas linguagens de repositório, com proporções relativas de que são fáceis de ver rapidamente. Talvez você precise ajustar a altura e a largura do diagrama da sua árvore, passado como os dois primeiros argumentos para `drawTreemap` acima, para obter todas as informações para serem exibidas corretamente. +Et voila! Beautiful rectangles containing your repo languages, with relative +proportions that are easy to see at a glance. You might need to +tweak the height and width of your treemap, passed as the first two +arguments to `drawTreemap` above, to get all the information to show up properly. [D3.js]: http://d3js.org/ [basics-of-authentication]: /rest/guides/basics-of-authentication -[basics-of-authentication]: /rest/guides/basics-of-authentication [sinatra auth github]: https://github.com/atmos/sinatra_auth_github [Octokit]: https://github.com/octokit/octokit.rb -[Octokit]: https://github.com/octokit/octokit.rb [D3 mortals]: http://www.recursion.org/d3-for-mere-mortals/ -[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html -[language API]: /rest/reference/repos#list-repository-languages +[D3 treemap]: https://www.d3-graph-gallery.com/treemap.html [language API]: /rest/reference/repos#list-repository-languages +[simple tree map]: http://2kittymafiasoftware.blogspot.com/2011/09/simple-treemap-visualization-with-d3.html [platform samples]: https://github.com/github/platform-samples/tree/master/api/ruby/rendering-data-as-graphs [new oauth application]: https://github.com/settings/applications/new diff --git a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md index 36400d1399..4b13c46e3d 100644 --- a/translations/pt-BR/content/rest/guides/traversing-with-pagination.md +++ b/translations/pt-BR/content/rest/guides/traversing-with-pagination.md @@ -2,7 +2,7 @@ title: Traversing with pagination intro: Explore how to use pagination to manage your responses with some examples using the Search API. redirect_from: - - /guides/traversing-with-pagination/ + - /guides/traversing-with-pagination - /v3/guides/traversing-with-pagination versions: fpt: '*' diff --git a/translations/pt-BR/content/rest/guides/working-with-comments.md b/translations/pt-BR/content/rest/guides/working-with-comments.md index 371054556f..3b5736faea 100644 --- a/translations/pt-BR/content/rest/guides/working-with-comments.md +++ b/translations/pt-BR/content/rest/guides/working-with-comments.md @@ -2,7 +2,7 @@ title: Working with comments intro: 'Using the REST API, you can access and manage comments in your pull requests, issues, or commits.' redirect_from: - - /guides/working-with-comments/ + - /guides/working-with-comments - /v3/guides/working-with-comments versions: fpt: '*' diff --git a/translations/pt-BR/content/rest/overview/libraries.md b/translations/pt-BR/content/rest/overview/libraries.md index 66c7c32f9e..0128487f72 100644 --- a/translations/pt-BR/content/rest/overview/libraries.md +++ b/translations/pt-BR/content/rest/overview/libraries.md @@ -1,8 +1,8 @@ --- -title: Bibliotecas +title: Libraries intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.' redirect_from: - - /libraries/ + - /libraries - /v3/libraries versions: fpt: '*' @@ -14,9 +14,9 @@ topics: ---
- O Gundamcat -

O Octokit tem muitos sabores

-

Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.

+ The Gundamcat +

Octokit comes in many flavors

+

Use the official Octokit library, or choose between any of the available third party libraries.


Ruby → octokit.rb

.NET → octokit.net

@@ -24,130 +24,130 @@ topics:
-# Bibliotecas de terceiros +# Third-party libraries ### Clojure -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------- | -| **Tentacles** | [Raynes/tentacles](https://github.com/Raynes/tentacles) | +| Library name | Repository | +|---|---| +|**Tentacles**| [Raynes/tentacles](https://github.com/Raynes/tentacles)| ### Dart -| Nome da Biblioteca | Repositório | -| ------------------ | ----------------------------------------------------------------------- | -| **github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart) | +| Library name | Repository | +|---|---| +|**github.dart** | [DirectMyFile/github.dart](https://github.com/DirectMyFile/github.dart)| ### Emacs Lisp -| Nome da Biblioteca | Repositório | -| ------------------ | --------------------------------------------- | -| **gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el) | +| Library name | Repository | +|---|---| +|**gh.el** | [sigma/gh.el](https://github.com/sigma/gh.el)| ### Erlang -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------- | -| **octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl) | +| Library name | Repository | +|---|---| +|**octo-erl** | [sdepold/octo.erl](https://github.com/sdepold/octo.erl)| ### Go -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------- | -| **go-github** | [google/go-github](https://github.com/google/go-github) | +| Library name | Repository | +|---|---| +|**go-github**| [google/go-github](https://github.com/google/go-github)| ### Haskell -| Nome da Biblioteca | Repositório | -| ------------------ | --------------------------------------------- | -| **haskell-github** | [fpco/Github](https://github.com/fpco/GitHub) | +| Library name | Repository | +|---|---| +|**haskell-github** | [fpco/Github](https://github.com/fpco/GitHub)| ### Java -| Nome da Biblioteca | Repositório | Mais informações | -| --------------------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | -| **API do GitHub para Java** | [org.kohsuke.github (do github-api)](http://github-api.kohsuke.org/) | define uma representação de objetos orientada à API do GitHub. | -| **JCabi GitHub API** | [github.jcabi.com (Site pessoal)](http://github.jcabi.com) | é baseado na API JSON Java7 (JSR-353), simplifica testes com uma amostra de tempo de execução do GitHub e abrange toda a API. | +| Library name | Repository | More information | +|---|---|---| +|**GitHub API for Java**| [org.kohsuke.github (From github-api)](http://github-api.kohsuke.org/)|defines an object oriented representation of the GitHub API.| +|**JCabi GitHub API**|[github.jcabi.com (Personal Website)](http://github.jcabi.com)|is based on Java7 JSON API (JSR-353), simplifies tests with a runtime GitHub stub, and covers the entire API.| ### JavaScript -| Nome da Biblioteca | Repositório | -| ------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| **NodeJS GitHub library** | [pksunkara/octonode](https://github.com/pksunkara/octonode) | -| **gh3 client-side API v3 wrapper** | [k33g/gh3](https://github.com/k33g/gh3) | -| **O wrapper do Github.js sobre a API do GitHub** | [michael/github](https://github.com/michael/github) | -| **Biblioteca CoffeeScript baseada no Promise para o navegador ou NodeJS** | [philschatz/github-client](https://github.com/philschatz/github-client) | +| Library name | Repository | +|---|---| +|**NodeJS GitHub library**| [pksunkara/octonode](https://github.com/pksunkara/octonode)| +|**gh3 client-side API v3 wrapper**| [k33g/gh3](https://github.com/k33g/gh3)| +|**Github.js wrapper around the GitHub API**|[michael/github](https://github.com/michael/github)| +|**Promise-Based CoffeeScript library for the Browser or NodeJS**|[philschatz/github-client](https://github.com/philschatz/github-client)| ### Julia -| Nome da Biblioteca | Repositório | -| ------------------ | ----------------------------------------------------------- | -| **GitHub.jl** | [JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl) | +| Library name | Repository | +|---|---| +|**GitHub.jl**|[JuliaWeb/GitHub.jl](https://github.com/JuliaWeb/GitHub.jl)| ### OCaml -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------------- | -| **ocaml-github** | [mirage/ocaml-github](https://github.com/mirage/ocaml-github) | +| Library name | Repository | +|---|---| +|**ocaml-github**|[mirage/ocaml-github](https://github.com/mirage/ocaml-github)| ### Perl -| Nome da Biblioteca | Repositório | Site metacpan para a biblioteca | -| ------------------ | --------------------------------------------------------------------- | ------------------------------------------------------- | -| **Pithub** | [plu/Pithub](https://github.com/plu/Pithub) | [Pithub CPAN](http://metacpan.org/module/Pithub) | -| **Net::GitHub** | [fayland/perl-net-github](https://github.com/fayland/perl-net-github) | [Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub) | +| Library name | Repository | metacpan Website for the Library | +|---|---|---| +|**Pithub**|[plu/Pithub](https://github.com/plu/Pithub)|[Pithub CPAN](http://metacpan.org/module/Pithub)| +|**Net::GitHub**|[fayland/perl-net-github](https://github.com/fayland/perl-net-github)|[Net:GitHub CPAN](https://metacpan.org/pod/Net::GitHub)| ### PHP -| Nome da Biblioteca | Repositório | -| ------------------------------ | --------------------------------------------------------------------------------- | -| **PHP GitHub API** | [KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api) | -| **GitHub Joomla! Package** | [joomla-framework/github-api](https://github.com/joomla-framework/github-api) | -| **GitHub bridge para Laravel** | [GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub) | +| Library name | Repository | +|---|---| +|**PHP GitHub API**|[KnpLabs/php-github-api](https://github.com/KnpLabs/php-github-api)| +|**GitHub Joomla! Package**|[joomla-framework/github-api](https://github.com/joomla-framework/github-api)| +|**GitHub bridge for Laravel**|[GrahamCampbell/Laravel-GitHub](https://github.com/GrahamCampbell/Laravel-GitHub)| ### PowerShell -| Nome da Biblioteca | Repositório | -| ----------------------- | --------------------------------------------------------------------------------- | -| **PowerShellForGitHub** | [microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub) | +| Library name | Repository | +|---|---| +|**PowerShellForGitHub**|[microsoft/PowerShellForGitHub](https://github.com/microsoft/PowerShellForGitHub)| ### Python -| Nome da Biblioteca | Repositório | -| ------------------ | --------------------------------------------------------------------- | -| **gidgethub** | [brettcannon/gidgethub](https://github.com/brettcannon/gidgethub) | -| **ghapi** | [fastai/ghapi](https://github.com/fastai/ghapi) | -| **PyGithub** | [PyGithub/PyGithub](https://github.com/PyGithub/PyGithub) | -| **libsaas** | [duckboard/libsaas](https://github.com/ducksboard/libsaas) | -| **github3.py** | [sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py) | -| **sanction** | [demianbrecht/sanction](https://github.com/demianbrecht/sanction) | -| **agithub** | [jpaugh/agithub](https://github.com/jpaugh/agithub) | -| **octohub** | [turnkeylinux/octohub](https://github.com/turnkeylinux/octohub) | -| **github-flask** | [github-flask (site oficial)](http://github-flask.readthedocs.org) | -| **torngithub** | [jkeylu/torngithub](https://github.com/jkeylu/torngithub) | +| Library name | Repository | +|---|---| +|**gidgethub**|[brettcannon/gidgethub](https://github.com/brettcannon/gidgethub)| +|**ghapi**|[fastai/ghapi](https://github.com/fastai/ghapi)| +|**PyGithub**|[PyGithub/PyGithub](https://github.com/PyGithub/PyGithub)| +|**libsaas**|[duckboard/libsaas](https://github.com/ducksboard/libsaas)| +|**github3.py**|[sigmavirus24/github3.py](https://github.com/sigmavirus24/github3.py)| +|**sanction**|[demianbrecht/sanction](https://github.com/demianbrecht/sanction)| +|**agithub**|[jpaugh/agithub](https://github.com/jpaugh/agithub)| +|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)| +|**github-flask**|[github-flask (Official Website)](http://github-flask.readthedocs.org)| +|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)| ### Ruby -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------------- | -| **GitHub API Gem** | [peter-murach/github](https://github.com/peter-murach/github) | -| **Ghee** | [rauhryan/ghee](https://github.com/rauhryan/ghee) | +| Library name | Repository | +|---|---| +|**GitHub API Gem**|[peter-murach/github](https://github.com/peter-murach/github)| +|**Ghee**|[rauhryan/ghee](https://github.com/rauhryan/ghee)| ### Rust -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------------- | -| **Octocrab** | [XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab) | +| Library name | Repository | +|---|---| +|**Octocrab**|[XAMPPRocky/octocrab](https://github.com/XAMPPRocky/octocrab)| ### Scala -| Nome da Biblioteca | Repositório | -| ------------------ | ------------------------------------------------------- | -| **Hubcat** | [softprops/hubcat](https://github.com/softprops/hubcat) | -| **Github4s** | [47deg/github4s](https://github.com/47deg/github4s) | +| Library name | Repository | +|---|---| +|**Hubcat**|[softprops/hubcat](https://github.com/softprops/hubcat)| +|**Github4s**|[47deg/github4s](https://github.com/47deg/github4s)| ### Shell -| Nome da Biblioteca | Repositório | -| ------------------ | ----------------------------------------------------- | -| **ok.sh** | [whiteinge/ok.sh](https://github.com/whiteinge/ok.sh) | +| Library name | Repository | +|---|---| +|**ok.sh**|[whiteinge/ok.sh](https://github.com/whiteinge/ok.sh)| diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 2c63ab5d1e..49c8175768 100644 --- a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md @@ -1,8 +1,8 @@ --- -title: Recursos na API REST +title: Resources in the REST API intro: 'Learn how to navigate the resources provided by the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.' redirect_from: - - /rest/initialize-the-repo/ + - /rest/initialize-the-repo versions: fpt: '*' ghes: '*' @@ -13,11 +13,12 @@ topics: --- -Isso descreve os recursos que formam a API REST oficial de {% data variables.product.product_name %}. Em caso de problema ou solicitação, entre em contato com {% data variables.contact.contact_support %}. +This describes the resources that make up the official {% data variables.product.product_name %} REST API. If you have any problems or requests, please contact {% data variables.contact.contact_support %}. -## Versão atual +## Current version -Por padrão, todas as solicitações para `{% data variables.product.api_url_code %}` recebem a versão **v3** [](/developers/overview/about-githubs-apis) da API REST. Nós incentivamos que você a [solicite explicitamente esta versão por meio do cabeçalho `Aceitar`](/rest/overview/media-types#request-specific-version). +By default, all requests to `{% data variables.product.api_url_code %}` receive the **v3** [version](/developers/overview/about-githubs-apis) of the REST API. +We encourage you to [explicitly request this version via the `Accept` header](/rest/overview/media-types#request-specific-version). Accept: application/vnd.github.v3+json @@ -27,10 +28,10 @@ For information about GitHub's GraphQL API, see the [v4 documentation]({% ifvers {% endif %} -## Esquema +## Schema -{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. Todos os dados são -enviados e recebidos como JSON. +{% ifversion fpt or ghec %}All API access is over HTTPS, and{% else %}The API is{% endif %} accessed from `{% data variables.product.api_url_code %}`. All data is +sent and received as JSON. ```shell $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs @@ -51,43 +52,55 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat/orgs > X-Content-Type-Options: nosniff ``` -Os campos em branco são incluídos como `null` em vez de serem omitidos. +Blank fields are included as `null` instead of being omitted. All timestamps return in UTC time, ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ -Para obter mais informações sobre fusos horários nos registros de tempo, consulte [esta seção](#timezones). +For more information about timezones in timestamps, see [this section](#timezones). -### Apresentações resumidas +### Summary representations -Ao buscar uma lista de recursos, a resposta inclui um _subconjunto_ dos atributos para esse recurso. Esta é a representação "resumo" do recurso. (Alguns atributos são computacionalmente caros para a API fornecer. Por razões de desempenho, a representação resumida exclui esses atributos. Para obter esses atributos, busque a representação "detalhada".) +When you fetch a list of resources, the response includes a _subset_ of the +attributes for that resource. This is the "summary" representation of the +resource. (Some attributes are computationally expensive for the API to provide. +For performance reasons, the summary representation excludes those attributes. +To obtain those attributes, fetch the "detailed" representation.) -**Exemplo**: ao receber uma lista de repositórios, você recebe a representação resumida de cada repositório. Aqui, buscamos a lista de repositórios pertencentes a à organização do [octokit](https://github.com/octokit): +**Example**: When you get a list of repositories, you get the summary +representation of each repository. Here, we fetch the list of repositories owned +by the [octokit](https://github.com/octokit) organization: GET /orgs/octokit/repos -### Representações detalhadas +### Detailed representations -Ao buscar um recurso individual, a resposta normalmente inclui _todos os_ atributos para esse recurso. Esta é a representação "detalhada" do recurso. (Note que a autorização por vezes influencia o valor de detalhes incluído na representação.) +When you fetch an individual resource, the response typically includes _all_ +attributes for that resource. This is the "detailed" representation of the +resource. (Note that authorization sometimes influences the amount of detail +included in the representation.) -**Exemplo**: ao receber um repositório individual, você recebe a representação detalhada do repositório. Aqui, nós buscamos o repositório [octokit/octokit.rb](https://github.com/octokit/octokit.rb): +**Example**: When you get an individual repository, you get the detailed +representation of the repository. Here, we fetch the +[octokit/octokit.rb](https://github.com/octokit/octokit.rb) repository: GET /repos/octokit/octokit.rb -A documentação fornece um exemplo de resposta para cada método da API. O exemplo da resposta ilustra todos os atributos retornados por esse método. +The documentation provides an example response for each API method. The example +response illustrates all attributes that are returned by that method. -## Autenticação +## Authentication -{% ifversion ghae %} Recomendamos efetuar a autenticação na API REST de {% data variables.product.product_name %}, criando um token OAuth2 por meio do [fluxo do aplicativo web](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} Existem duas maneiras de efetuar a autenticação por meio da API REST de {% data variables.product.product_name %}.{% endif %} As solicitações que exigem autenticação retornarão `404 Not Found`, em vez de `403 Forbidden` em alguns lugares. Isso é para evitar a fuga acidental de repositórios privados para usuários não autorizados. +{% ifversion ghae %} We recommend authenticating to the {% data variables.product.product_name %} REST API by creating an OAuth2 token through the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow). {% else %} There are two ways to authenticate through {% data variables.product.product_name %} REST API.{% endif %} Requests that require authentication will return `404 Not Found`, instead of `403 Forbidden`, in some places. This is to prevent the accidental leakage of private repositories to unauthorized users. -### Autenticação básica +### Basic authentication ```shell $ curl -u "username" {% data variables.product.api_url_pre %} ``` -### Token do OAuth2 (enviado em um cabeçalho) +### OAuth2 token (sent in a header) ```shell $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre %} @@ -95,11 +108,11 @@ $ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product. {% note %} -Observação: O GitHub recomenda enviar tokens do OAuth usando o cabeçalho de autorização. +Note: GitHub recommends sending OAuth tokens using the Authorization header. {% endnote %} -Leia [mais sobre o OAuth2](/apps/building-oauth-apps/). Observe que os tokens do OAuth2 podem ser adquiridos usando o [fluxo de aplicação web](/developers/apps/authorizing-oauth-apps#web-application-flow) para aplicativos de produção. +Read [more about OAuth2](/apps/building-oauth-apps/). Note that OAuth2 tokens can be acquired using the [web application flow](/developers/apps/authorizing-oauth-apps#web-application-flow) for production applications. {% ifversion fpt or ghes or ghec %} ### OAuth2 key/secret @@ -110,22 +123,22 @@ Leia [mais sobre o OAuth2](/apps/building-oauth-apps/). Observe que os tokens d curl -u my_client_id:my_client_secret '{% data variables.product.api_url_pre %}/user/repos' ``` -Usar o seu `client_id` e `client_secret` _ não_ autenticam você como usuário. Isso apenas irá identificar o seu aplicativo OAuth para aumentar o seu limite de taxa. As permissões só são concedidas a usuários, não aplicativos, e você só obterá dados que um usuário não autenticado visualizaria. Por este motivo, você só deve usar a chave/segredo OAuth2 em cenários de servidor para servidor. Não compartilhe o segredo do cliente do aplicativo OAuth com os seus usuários. +Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth application to increase your rate limit. Permissions are only granted to users, not applications, and you will only get back data that an unauthenticated user would see. For this reason, you should only use the OAuth2 key/secret in server-to-server scenarios. Don't leak your OAuth application's client secret to your users. {% ifversion ghes %} -Você não conseguirá efetuar a autenticação usando sua chave e segredo do OAuth2 enquanto estiver no modo privado e essa tentativa de autenticação irá retornar `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)". +You will be unable to authenticate using your OAuth2 key and secret while in private mode, and trying to authenticate will return `401 Unauthorized`. For more information, see "[Enabling private mode](/admin/configuration/configuring-your-enterprise/enabling-private-mode)". {% endif %} {% endif %} {% ifversion fpt or ghec %} -Leia [Mais informações sobre limitação da taxa não autenticada](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). +Read [more about unauthenticated rate limiting](#increasing-the-unauthenticated-rate-limit-for-oauth-applications). {% endif %} -### Falha no limite de login +### Failed login limit -A autenticação com credenciais inválidas retornará `401 Unauthorized`: +Authenticating with invalid credentials will return `401 Unauthorized`: ```shell $ curl -I {% data variables.product.api_url_pre %} -u foo:bar @@ -137,7 +150,9 @@ $ curl -I {% data variables.product.api_url_pre %} -u foo:bar > } ``` -Após detectar várias solicitações com credenciais inválidas em um curto período de tempo, a API rejeitará temporariamente todas as tentativas de autenticação para esse usuário (incluindo aquelas com credenciais válidas) com `403 Forbidden`: +After detecting several requests with invalid credentials within a short period, +the API will temporarily reject all authentication attempts for that user +(including ones with valid credentials) with `403 Forbidden`: ```shell $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae or ghec %} @@ -149,191 +164,215 @@ $ curl -i {% data variables.product.api_url_pre %} -u {% ifversion fpt or ghae o > } ``` -## Parâmetros +## Parameters -Muitos métodos de API tomam parâmetros opcionais. Para solicitações tipo `GET`, todos os parâmetros não especificados como um segmento no caminho podem ser passados como um parâmetro de string de consulta de HTTP: +Many API methods take optional parameters. For `GET` requests, any parameters not +specified as a segment in the path can be passed as an HTTP query string +parameter: ```shell $ curl -i "{% data variables.product.api_url_pre %}/repos/vmg/redcarpet/issues?state=closed" ``` -Neste exemplo, os valores 'vmg' e 'redcarpet' são fornecidos para os parâmetros `:owner` e `:repo` no caminho enquanto `:state` é passado na string da consulta. +In this example, the 'vmg' and 'redcarpet' values are provided for the `:owner` +and `:repo` parameters in the path while `:state` is passed in the query +string. -Para solicitações de `POST`, `PATCH`, `PUT`e `EXCLUIR`, os parâmetros não incluídos na URL devem ser codificados como JSON com um Content-Type de 'application/json': +For `POST`, `PATCH`, `PUT`, and `DELETE` requests, parameters not included in the URL should be encoded as JSON +with a Content-Type of 'application/json': ```shell $ curl -i -u username -d '{"scopes":["repo_deployment"]}' {% data variables.product.api_url_pre %}/authorizations ``` -## Ponto de extremidade raiz +## Root endpoint -Você pode emitir uma solicitação `GET` para o ponto de extremidade de raiz para obter todas as categorias do ponto de extremidade com a qual a API REST é compatível: +You can issue a `GET` request to the root endpoint to get all the endpoint categories that the REST API supports: ```shell $ curl {% ifversion fpt or ghae or ghec %} -u username:token {% endif %}{% ifversion ghes %}-u username:password {% endif %}{% data variables.product.api_url_pre %} ``` -## IDs de nós globais do GraphQL +## GraphQL global node IDs See the guide on "[Using Global Node IDs]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/guides/using-global-node-ids)" for detailed information about how to find `node_id`s via the REST API and use them in GraphQL operations. -## Erros do cliente +## Client errors -Há três tipos possíveis de erros de cliente na chamadas da API que recebem textos: +There are three possible types of client errors on API calls that +receive request bodies: -1. O envio de um JSON inválido resultará em uma resposta 400 Bad Request`.

+1. Sending invalid JSON will result in a `400 Bad Request` response. -
 HTTP/2 400
- Content-Length: 35
+        HTTP/2 400
+        Content-Length: 35
 
- {"message":"Problems parsing JSON"}
-`
+ {"message":"Problems parsing JSON"} -2 +2. Sending the wrong type of JSON values will result in a `400 Bad + Request` response. -Enviar o tipo incorreto de valores do JSON resultará em uma resposta `400 Bad -Request`. - - HTTP/2 400 - Content-Length: 40 - - {"message":"Body should be a JSON object"} + HTTP/2 400 + Content-Length: 40 -3 + {"message":"Body should be a JSON object"} -O envio de campos inválidos resultará em uma resposta `422 Unprocessable Entity`. - - HTTP/2 422 - Content-Length: 149 - - { - "message": "Validation Failed", - "errors": [ - { - "resource": "Issue", - "field": "title", - "code": "missing_field" - } - ] - } - +3. Sending invalid fields will result in a `422 Unprocessable Entity` + response. -Todos objetos de erro têm propriedades de recurso e campo para que seu cliente possa dizer qual é o problema. Também há um código de erro para informar o que há de errado com o campo. Estes são os possíveis códigos de validação: + HTTP/2 422 + Content-Length: 149 -| Nome do código de erro | Descrição | -| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | -| `missing` | Um recurso não existe. | -| `missing_field` | Não foi definido um campo obrigatório em um recurso. | -| `invalid` | Formatação de um campo é inválida. Revise a documentação para obter informações mais específicas. | -| `already_exists` | Outro recurso tem o mesmo valor que este campo. Isso pode acontecer em recursos que precisam ter alguma chave única (como nomes de etiqueta). | -| `unprocessable` | As entradas fornecidas eram inválidas. | + { + "message": "Validation Failed", + "errors": [ + { + "resource": "Issue", + "field": "title", + "code": "missing_field" + } + ] + } -Os recursos também podem enviar erros de validação personalizados (em que o `código` é `personalizado`). Os erros personalizados sempre terão um campo de `mensagem` que descreve o erro e a maioria dos erros também incluirá um campo de `documentation_url` que aponta para algum conteúdo que pode ajudá-lo a resolver o erro. +All error objects have resource and field properties so that your client +can tell what the problem is. There's also an error code to let you +know what is wrong with the field. These are the possible validation error +codes: -## Redirecionamentos HTTP +Error code name | Description +-----------|-----------| +`missing` | A resource does not exist. +`missing_field` | A required field on a resource has not been set. +`invalid` | The formatting of a field is invalid. Review the documentation for more specific information. +`already_exists` | Another resource has the same value as this field. This can happen in resources that must have some unique key (such as label names). +`unprocessable` | The inputs provided were invalid. -API v3 usa redirecionamento HTTP quando apropriado. Os clientes devem assumir que qualquer solicitação pode resultar em redirecionamento. Receber um redirecionamento de HTTP *não* é um erro e os clientes devem seguir esse redirecionamento. As respostas de redirecionamento terão um campo do cabeçalho do tipo `Localização` que contém o URI do recurso ao qual o cliente deve repetir as solicitações. +Resources may also send custom validation errors (where `code` is `custom`). Custom errors will always have a `message` field describing the error, and most errors will also include a `documentation_url` field pointing to some content that might help you resolve the error. -| Código de status | Descrição | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `301` | Redirecionamento permanente. O URI que você usou para fazer a solicitação foi substituído pelo especificado no campo do cabeçalho `Localização`. Este e todas as solicitações futuras deste recurso devem ser direcionadas para o novo URI. | -| `302`, `307` | Redirecionamento temporário. A solicitação deve ser repetida literalmente para o URI especificado no campo de cabeçalho `Localização`, mas os clientes devem continuar a usar o URI original para solicitações futuras. | +## HTTP redirects -Outros códigos de status de redirecionamento podem ser usados de acordo com a especificação HTTP 1.1. +API v3 uses HTTP redirection where appropriate. Clients should assume that any +request may result in a redirection. Receiving an HTTP redirection is *not* an +error and clients should follow that redirect. Redirect responses will have a +`Location` header field which contains the URI of the resource to which the +client should repeat the requests. -## Verbos HTTP +Status Code | Description +-----------|-----------| +`301` | Permanent redirection. The URI you used to make the request has been superseded by the one specified in the `Location` header field. This and all future requests to this resource should be directed to the new URI. +`302`, `307` | Temporary redirection. The request should be repeated verbatim to the URI specified in the `Location` header field but clients should continue to use the original URI for future requests. -Quando possível, a API v3 se esforça para usar verbos HTTP apropriados para cada ação. +Other redirection status codes may be used in accordance with the HTTP 1.1 spec. -| Verbo | Descrição | -| -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `HEAD` | Pode ser emitido contra qualquer recurso para obter apenas as informações de cabeçalho HTTP. | -| `GET` | Usado para recuperar recursos. | -| `POST` | Usado para criar recursos. | -| `PATCH` | Usado para atualizar recursos com dados parciais do JSON. Por exemplo, um recurso de um problema tem atributos de `título` e `texto`. Uma solicitação de `PATCH` pode aceitar um ou mais dos atributos para atualizar o recurso. | -| `PUT` | Usado para substituir recursos ou coleções. Para as solicitações de `PUT` sem atributo de `texto`, certifique-se de definir o cabeçalho `Content-Length` como zero. | -| `DELETE` | Usado para excluir recursos. | +## HTTP verbs -## Hipermídia +Where possible, API v3 strives to use appropriate HTTP verbs for each +action. -Todos os recursos podem ter uma ou mais propriedades `*_url` vinculando outros recursos. Estes tem o objetivo de fornecer URLs explícitas para que os clientes API apropriados não precisem construir URLs por conta própria. É altamente recomendável que os clientes da API os utilizem. Fazer isso tornará as futuras atualizações da API mais fáceis para os desenvolvedores. Espera-se que todas as URLs sejam modelos de URI [RFC 6570][rfc] adequados. +Verb | Description +-----|----------- +`HEAD` | Can be issued against any resource to get just the HTTP header info. +`GET` | Used for retrieving resources. +`POST` | Used for creating resources. +`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource. +`PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero. +`DELETE` |Used for deleting resources. -Então você pode expandir estes modelos usando algo como o [uri_template][uri] gem: +## Hypermedia + +All resources may have one or more `*_url` properties linking to other +resources. These are meant to provide explicit URLs so that proper API clients +don't need to construct URLs on their own. It is highly recommended that API +clients use these. Doing so will make future upgrades of the API easier for +developers. All URLs are expected to be proper [RFC 6570][rfc] URI templates. + +You can then expand these templates using something like the [uri_template][uri] +gem: >> tmpl = URITemplate.new('/notifications{?since,all,participating}') >> tmpl.expand => "/notifications" - + >> tmpl.expand :all => 1 => "/notifications?all=1" - + >> tmpl.expand :all => 1, :participating => 1 => "/notifications?all=1&participating=1" -## Paginação +[rfc]: https://datatracker.ietf.org/doc/html/rfc6570 +[uri]: https://github.com/hannesg/uri_template -Pedidos que retornam vários itens serão paginados para 30 itens por padrão. Você pode especificar mais páginas com o parâmetro `page`. Para alguns recursos, você também pode definir um tamanho de página até 100 com o parâmetro `per_page`. Observe que, por razões técnicas, nem todos os pontos de extremidade respeitam o parâmetro `per_page`, veja [eventos](/rest/reference/activity#events) por exemplo. +## Pagination + +Requests that return multiple items will be paginated to 30 items by +default. You can specify further pages with the `page` parameter. For some +resources, you can also set a custom page size up to 100 with the `per_page` parameter. +Note that for technical reasons not all endpoints respect the `per_page` parameter, +see [events](/rest/reference/activity#events) for example. ```shell $ curl '{% data variables.product.api_url_pre %}/user/repos?page=2&per_page=100' ``` -Observe que a numeração da página é baseada em 1 e que, ao omitir o parâmetro `page`, retornará a primeira página. +Note that page numbering is 1-based and that omitting the `page` +parameter will return the first page. -Alguns pontos de extremidade usam paginação baseada no cursor. Um cursor é uma string que aponta para uma localização no conjunto de resultados. Com paginação baseada em cursor, não há um conceito fixo de "páginas" no conjunto de resultados. Portanto, você não pode navegar para uma página específica. Em vez disso, você pode percorrer os resultados usando os parâmetros `antes` ou `após`. +Some endpoints use cursor-based pagination. A cursor is a string that points to a location in the result set. +With cursor-based pagination, there is no fixed concept of "pages" in the result set, so you can't navigate to a specific page. +Instead, you can traverse the results by using the `before` or `after` parameters. -Para obter mais informações sobre paginação, confira nosso guia sobre [Passar com paginação][pagination-guide]. +For more information on pagination, check out our guide on [Traversing with Pagination][pagination-guide]. -### Cabeçalho do link +### Link header {% note %} -**Observação:** É importante formar chamadas com valores de cabeçalho de link, em vez de construir suas próprias URLs. +**Note:** It's important to form calls with Link header values instead of constructing your own URLs. {% endnote %} -O [cabeçalho do link](https://datatracker.ietf.org/doc/html/rfc5988) inclui informações de paginação. Por exemplo: +The [Link header](https://datatracker.ietf.org/doc/html/rfc5988) includes pagination information. For example: Link: <{% data variables.product.api_url_code %}/user/repos?page=3&per_page=100>; rel="next", <{% data variables.product.api_url_code %}/user/repos?page=50&per_page=100>; rel="last" -_O exemplo inclui uma quebra de linha para legibilidade._ +_The example includes a line break for readability._ -Ou, se o ponto de extremidade usar paginação baseada em cursor: +Or, if the endpoint uses cursor-based pagination: Link: <{% data variables.product.api_url_code %}/orgs/ORG/audit-log?after=MTYwMTkxOTU5NjQxM3xZbGI4VE5EZ1dvZTlla09uWjhoZFpR&before=>; rel="next", -Este `Link` de resposta contém um ou mais links de relações de [hipermídia](/rest#hypermedia), alguns dos quais podem exigir expansão como [modelos de URI](https://datatracker.ietf.org/doc/html/rfc6570). +This `Link` response header contains one or more [Hypermedia](/rest#hypermedia) link relations, some of which may require expansion as [URI templates](https://datatracker.ietf.org/doc/html/rfc6570). -Os valores de `rel` possíveis são: +The possible `rel` values are: -| Nome | Descrição | -| --------- | ---------------------------------------------------------------- | -| `avançar` | A relação de link para a próxima página de resultados. | -| `last` | A relação de link para a última página de resultados. | -| `first` | A relação de link para a primeira página de resultados. | -| `prev` | A relação de link para a página de resultados anterior imediata. | +Name | Description +-----------|-----------| +`next` |The link relation for the immediate next page of results. +`last` |The link relation for the last page of results. +`first` |The link relation for the first page of results. +`prev` |The link relation for the immediate previous page of results. -## Limite de taxa +## Rate limiting -Para solicitações de API que usam a Autenticação Básica ou OAuth, você pode criar até 5.000 solicitações por hora. As solicitações de autenticação são associadas ao usuário autenticado, independentemente de [Autenticação Básica](#basic-authentication) ou [um token do OAuth](#oauth2-token-sent-in-a-header) ter sido usado. Isto significa que todos os aplicativos OAuth autorizados por um usuário compartilham a mesma cota de 5.000 solicitações por hora quando eles são autenticados com diferentes tokens pertencentes ao mesmo usuário. +For API requests using Basic Authentication or OAuth, you can make up to 5,000 requests per hour. Authenticated requests are associated with the authenticated user, regardless of whether [Basic Authentication](#basic-authentication) or [an OAuth token](#oauth2-token-sent-in-a-header) was used. This means that all OAuth applications authorized by a user share the same quota of 5,000 requests per hour when they authenticate with different tokens owned by the same user. {% ifversion fpt or ghec %} -Para usuários que pertencem a uma conta {% data variables.product.prodname_ghe_cloud %}, solicitações feitas usando um token OAuth para recursos pertencentes à mesma conta de {% data variables.product.prodname_ghe_cloud %} têm um aumento de 15.000 solicitações por hora no limite. +For users that belong to a {% data variables.product.prodname_ghe_cloud %} account, requests made using an OAuth token to resources owned by the same {% data variables.product.prodname_ghe_cloud %} account have an increased limit of 15,000 requests per hour. {% endif %} -Ao usar o `GITHUB_TOKEN` embutido no GitHub Actions, o limite de taxa será de 1.000 solicitações por hora por repositório. Para organizações que pertencem a uma conta no GitHub Enterprise Cloud, este limite é de 15.000 solicitações por hora por repositório. +When using the built-in `GITHUB_TOKEN` in GitHub Actions, the rate limit is 1,000 requests per hour per repository. For organizations that belong to a GitHub Enterprise Cloud account, this limit is 15,000 requests per hour per repository. -Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. Solicitações não autenticadas estão associadas ao endereço IP original, e não ao usuário que faz solicitações. +For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests. {% data reusables.enterprise.rate_limit %} -Observe que [a API de pesquisa tem regras de limite de taxa personalizadas](/rest/reference/search#rate-limit). +Note that [the Search API has custom rate limit rules](/rest/reference/search#rate-limit). -Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu status atual de limite de taxa: +The returned HTTP headers of any API request show your current rate limit status: ```shell $ curl -I {% data variables.product.api_url_pre %}/users/octocat @@ -344,20 +383,20 @@ $ curl -I {% data variables.product.api_url_pre %}/users/octocat > X-RateLimit-Reset: 1372700873 ``` -| Nome do Cabeçalho | Descrição | -| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| `X-RateLimit-Limit` | O número máximo de solicitações que você pode fazer por hora. | -| `X-RateLimit-Remaining` | O número de solicitações restantes na janela de limite de taxa atual. | -| `X-RateLimit-Reset` | O tempo em que a janela de limite de taxa atual é redefinida em [segundos no tempo de computação de UTC](http://en.wikipedia.org/wiki/Unix_time). | +Header Name | Description +-----------|-----------| +`X-RateLimit-Limit` | The maximum number of requests you're permitted to make per hour. +`X-RateLimit-Remaining` | The number of requests remaining in the current rate limit window. +`X-RateLimit-Reset` | The time at which the current rate limit window resets in [UTC epoch seconds](http://en.wikipedia.org/wiki/Unix_time). -Se você precisar de outro formato de tempo, qualquer linguagem de programação moderna pode fazer o trabalho. Por exemplo, se você abrir o console em seu navegador, você pode facilmente obter o tempo de redefinição como um objeto de tempo do JavaScript. +If you need the time in a different format, any modern programming language can get the job done. For example, if you open up the console on your web browser, you can easily get the reset time as a JavaScript Date object. ``` javascript new Date(1372700873 * 1000) // => Mon Jul 01 2013 13:47:53 GMT-0400 (EDT) ``` -Se você exceder o limite de taxa, uma resposta do erro retorna: +If you exceed the rate limit, an error response returns: ```shell > HTTP/2 403 @@ -372,11 +411,11 @@ Se você exceder o limite de taxa, uma resposta do erro retorna: > } ``` -Você pode [verificar o status do seu limite de taxa](/rest/reference/rate-limit) sem a incorrer em uma consulta da API. +You can [check your rate limit status](/rest/reference/rate-limit) without incurring an API hit. -### Aumentar o limite de taxa não autenticado para aplicativos OAuth +### Increasing the unauthenticated rate limit for OAuth applications -Se o seu aplicativo OAuth precisar fazer chamadas não autenticadas com um limite de taxa mais alto, você poderá passar o ID e o segredo do cliente do seu aplicativo antes do encaminhamento de pontos de extremidade. +If your OAuth application needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route. ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos @@ -389,21 +428,21 @@ $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %} {% note %} -**Observação:** Nunca compartilhe seu segredo de cliente com alguém ou o inclua no código do navegador do lado do cliente. Use o método mostrado aqui apenas para chamadas de servidor para servidor. +**Note:** Never share your client secret with anyone or include it in client-side browser code. Use the method shown here only for server-to-server calls. {% endnote %} -### Manter-se dentro do limite de taxa +### Staying within the rate limit -Se você exceder seu limite de taxa usando a Autenticação Básica ou OAuth, você poderá corrigir o problema armazenando respostas da API e usando [solicitações condicionais](#conditional-requests). +If you exceed your rate limit using Basic Authentication or OAuth, you can likely fix the issue by caching API responses and using [conditional requests](#conditional-requests). -### Limites de taxa secundária +### Secondary rate limits -A fim de fornecer serviço de qualidade no {% data variables.product.product_name %}, podem-se aplicar limites de taxa adicionais podem a algumas ações ao usar a API. Por exemplo, usar a API para criar rapidamente conteúdo, fazer sondagem de modo agressivo em vez de usar webhooks, fazer várias solicitações simultâneas ou solicitar repetidamente dados caros do ponto de vista computacional podem resultar na limitação da taxa secundária. +In order to provide quality service on {% data variables.product.product_name %}, additional rate limits may apply to some actions when using the API. For example, using the API to rapidly create content, poll aggressively instead of using webhooks, make multiple concurrent requests, or repeatedly request data that is computationally expensive may result in secondary rate limiting. -Limites de taxa secundária não pretendem interferir com o uso legítimo da API. Seus limites de taxa normais devem ser o único limite em que você deve focar. Para garantir que você está agindo como um bom cidadão da API, confira nossas [Diretrizes sobre práticas recomendadas](/guides/best-practices-for-integrators/). +Secondary rate limits are not intended to interfere with legitimate use of the API. Your normal rate limits should be the only limit you target. To ensure you're acting as a good API citizen, check out our [Best Practices guidelines](/guides/best-practices-for-integrators/). -Se seu aplicativo acionar este limite de taxa, você receberá uma resposta informativa: +If your application triggers this rate limit, you'll receive an informative response: ```shell > HTTP/2 403 @@ -418,17 +457,19 @@ Se seu aplicativo acionar este limite de taxa, você receberá uma resposta info {% ifversion fpt or ghec %} -## Agente de usuário obrigatório +## User agent required -Todas as solicitações da API DEVEM incluir um cabeçalho válido de `User-Agent`. As requisições sem o cabeçalho do `User-Agent` serão rejeitadas. Pedimos que use seu nome de usuário de {% data variables.product.product_name %} ou o nome de seu aplicativo, para o valor do cabeçalho `User-Agent`. Isso nos permite entrar em contato com você, em caso de problemas. +All API requests MUST include a valid `User-Agent` header. Requests with no `User-Agent` +header will be rejected. We request that you use your {% data variables.product.product_name %} username, or the name of your +application, for the `User-Agent` header value. This allows us to contact you if there are problems. -Aqui está um exemplo: +Here's an example: ```shell User-Agent: Awesome-Octocat-App ``` -A cURL envia um cabeçalho válido do `User-Agent` por padrão. Se você fornecer um cabeçalho inválido de `User-Agent` via cURL (ou via um cliente alternativo), você receberá uma resposta `403 Forbidden`: +cURL sends a valid `User-Agent` header by default. If you provide an invalid `User-Agent` header via cURL (or via an alternative client), you will receive a `403 Forbidden` response: ```shell $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta @@ -443,15 +484,20 @@ $ curl -IH 'User-Agent: ' {% data variables.product.api_url_pre %}/meta {% endif %} -## Solicitações condicionais +## Conditional requests -A maioria das respostas retorna um cabeçalho de Etag`. Muitas respostas também retornam um cabeçalho Last-Modified`. Você pode usar os valores desses cabeçalhos para fazer solicitações subsequentes para esses recursos usando os cabeçalhos `If-None-Match` e `If-Modified-Desde`, respectivamente. Se o recurso não foi alterado, o servidor retornará `304 não modificado`. +Most responses return an `ETag` header. Many responses also return a `Last-Modified` header. You can use the values +of these headers to make subsequent requests to those resources using the +`If-None-Match` and `If-Modified-Since` headers, respectively. If the resource +has not changed, the server will return a `304 Not Modified`. {% ifversion fpt or ghec %} {% tip %} -**Observação**: Fazer uma solicitação condicional e receber uma resposta 304 não conta para o seu [Limite de Taxa](#rate-limiting). Portanto, recomendamos que você o utilize sempre que possível. +**Note**: Making a conditional request and receiving a 304 response does not +count against your [Rate Limit](#rate-limiting), so we encourage you to use it +whenever possible. {% endtip %} @@ -488,11 +534,16 @@ $ curl -I {% data variables.product.api_url_pre %}/user -H "If-Modified-Since: T > X-RateLimit-Reset: 1372700873 ``` -## Compartilhamento de recursos de origem cruzada +## Cross origin resource sharing -A API é compatível com Compartilhamento de Recursos de Origens Cruzadas (CORS) para solicitações de AJAX de qualquer origem. You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or [this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the HTML 5 Security Guide. +The API supports Cross Origin Resource Sharing (CORS) for AJAX requests from +any origin. +You can read the [CORS W3C Recommendation](http://www.w3.org/TR/cors/), or +[this intro](https://code.google.com/archive/p/html5security/wikis/CrossOriginRequestSecurity.wiki) from the +HTML 5 Security Guide. -Aqui está uma solicitação de exemplo enviada a partir de uma consulta em `http://exemplo.com`: +Here's a sample request sent from a browser hitting +`http://example.com`: ```shell $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" @@ -501,7 +552,7 @@ Access-Control-Allow-Origin: * Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval ``` -A solicitação pré-voo de CORS se parece com isso: +This is what the CORS preflight request looks like: ```shell $ curl -I {% data variables.product.api_url_pre %} -H "Origin: http://example.com" -X OPTIONS @@ -513,9 +564,13 @@ Access-Control-Expose-Headers: ETag, Link, X-GitHub-OTP, X-RateLimit-Limit, X-Ra Access-Control-Max-Age: 86400 ``` -## Chamadas de retorno do JSON-P +## JSON-P callbacks -Você pode enviar um parâmetro `?callback` para qualquer chamada de GET para envolver os resultados em uma função JSON. Isso é normalmente usado quando os navegadores querem que incorporem {% data variables.product.product_name %} conteúdo em páginas da web, contornando problemas de de domínio cruzado. A resposta inclui a mesma saída de dados da API regular, mais as informações relevantes do cabeçalho de HTTP. +You can send a `?callback` parameter to any GET call to have the results +wrapped in a JSON function. This is typically used when browsers want +to embed {% data variables.product.product_name %} content in web pages by getting around cross domain +issues. The response includes the same data output as the regular API, +plus the relevant HTTP Header information. ```shell $ curl {% data variables.product.api_url_pre %}?callback=foo @@ -536,7 +591,7 @@ $ curl {% data variables.product.api_url_pre %}?callback=foo > }) ``` -Você pode escrever um manipulador do JavaScript para processar o retorno de chamada. Aqui está um exemplo pequeno que você pode experimentar: +You can write a JavaScript handler to process the callback. Here's a minimal example you can try out: @@ -547,26 +602,28 @@ Você pode escrever um manipulador do JavaScript para processar o retorno de cha console.log(meta); console.log(data); } - + var script = document.createElement('script'); script.src = '{% data variables.product.api_url_code %}?callback=foo'; - + document.getElementsByTagName('head')[0].appendChild(script); - +

Open up your browser's console.

-Todos os cabeçalhos têm o mesmo valor d a string que os cabeçalhos de HTTP com uma exceção notável: Link. Cabeçalhos de link são pré-analisados para você e chegam como um array de tuplas de `[url, options]`. +All of the headers are the same String value as the HTTP Headers with one +notable exception: Link. Link headers are pre-parsed for you and come +through as an array of `[url, options]` tuples. -Um link que se parece com isto: +A link that looks like this: Link: ; rel="next", ; rel="foo"; bar="baz" -... será mostrado assim na saída da chamada de retorno: +... will look like this in the Callback output: ```json { @@ -588,42 +645,39 @@ Um link que se parece com isto: } ``` -## Fusos horários +## Timezones -Algumas solicitações que criam novos dados, como a criação de um novo commit, permitem que você forneça informações do fuso horário ao especificar ou marcas de tempo. We apply the following rules, in order of priority, to determine timezone information for such API calls. +Some requests that create new data, such as creating a new commit, allow you to provide time zone information when specifying or generating timestamps. We apply the following rules, in order of priority, to determine timezone information for such API calls. -* [Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) -* [Usar o cabeçalho `Time-Zone`](#using-the-time-zone-header) -* [Usar o último fuso horário conhecido para o usuário](#using-the-last-known-timezone-for-the-user) -* [Definir como padrão UTC sem outras informações de fuso horário](#defaulting-to-utc-without-other-timezone-information) +* [Explicitly providing an ISO 8601 timestamp with timezone information](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information) +* [Using the `Time-Zone` header](#using-the-time-zone-header) +* [Using the last known timezone for the user](#using-the-last-known-timezone-for-the-user) +* [Defaulting to UTC without other timezone information](#defaulting-to-utc-without-other-timezone-information) Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format. -### Fornecer explicitamente uma marca de tempo ISO 8601 com informações de fuso horário +### Explicitly providing an ISO 8601 timestamp with timezone information -Para chamadas de API que permitem que uma marca de tempo seja especificada, usamos essa marca de tempo exata. Um exemplo disso é a [API de Commits](/rest/reference/git#commits). +For API calls that allow for a timestamp to be specified, we use that exact timestamp. An example of this is the [Commits API](/rest/reference/git#commits). -Essas marcas de tempo se parecem com `2014-02-27T15:05:06+01:00`. Veja também [este exemplo](/rest/reference/git#example-input) para saber como essas marcas de tempo podem ser especificadas. +These timestamps look something like `2014-02-27T15:05:06+01:00`. Also see [this example](/rest/reference/git#example-input) for how these timestamps can be specified. -### Usar o cabeçalho `Time-Zone` +### Using the `Time-Zone` header -É possível fornecer um cabeçalho `Time-Zone` que define um fuso horário de acordo com a lista [ de nomes do banco de dados Olson](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). +It is possible to supply a `Time-Zone` header which defines a timezone according to the [list of names from the Olson database](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). ```shell $ curl -H "Time-Zone: Europe/Amsterdam" -X POST {% data variables.product.api_url_pre %}/repos/github/linguist/contents/new_file.md ``` -Isso significa que geramos uma marca de tempo no momento em que sua chamada de API é feita no fuso horário que este cabeçalho define. Por exemplo, o [API de Conteúdo](/rest/reference/repos#contents) gera um commit do git para cada adição ou alteração e usa a hora atual como marca de tempo. Este cabeçalho determinará o fuso horário usado para gerar essa marca de tempo atual. +This means that we generate a timestamp for the moment your API call is made in the timezone this header defines. For example, the [Contents API](/rest/reference/repos#contents) generates a git commit for each addition or change and uses the current time as the timestamp. This header will determine the timezone used for generating that current timestamp. -### Usar o último fuso horário conhecido para o usuário +### Using the last known timezone for the user -Se nenhum cabeçalho `Time-Zone` for especificado e você fizer uma chamada autenticada para a API, nós usaremos o último fuso horário conhecido para o usuário autenticado. O último fuso horário conhecido é atualizado sempre que você navegar no site de {% data variables.product.product_name %}. +If no `Time-Zone` header is specified and you make an authenticated call to the API, we use the last known timezone for the authenticated user. The last known timezone is updated whenever you browse the {% data variables.product.product_name %} website. -### Definir como padrão UTC sem outras informações de fuso horário +### Defaulting to UTC without other timezone information -Se as etapas acima não resultarem em nenhuma informação, usaremos UTC como o fuso horário para criar o commit do git. - -[rfc]: https://datatracker.ietf.org/doc/html/rfc6570 -[uri]: https://github.com/hannesg/uri_template +If the steps above don't result in any information, we use UTC as the timezone to create the git commit. [pagination-guide]: /guides/traversing-with-pagination diff --git a/translations/pt-BR/content/rest/reference/enterprise-admin.md b/translations/pt-BR/content/rest/reference/enterprise-admin.md index fbe657c8eb..d903396303 100644 --- a/translations/pt-BR/content/rest/reference/enterprise-admin.md +++ b/translations/pt-BR/content/rest/reference/enterprise-admin.md @@ -186,7 +186,7 @@ $ curl -L 'https://hostname:admin_port/setup/api?api_key=y You can also use standard HTTP authentication to send this token. For example: ```shell -$ curl -L 'https://api_key:your-amazing-password@hostname:admin_port/setup/api' +$ curl -L -u "api_key:your-amazing-password" 'https://hostname:admin_port/setup/api' ``` {% for operation in currentRestOperations %} diff --git a/translations/pt-BR/content/rest/reference/orgs.md b/translations/pt-BR/content/rest/reference/orgs.md index 83d2481551..1d2930d047 100644 --- a/translations/pt-BR/content/rest/reference/orgs.md +++ b/translations/pt-BR/content/rest/reference/orgs.md @@ -1,6 +1,6 @@ --- -title: Organizações -intro: 'A API de organizações concede acesso para controlar e gerenciar todas as suas organizações de {% data variables.product.product_name %}.' +title: Organizations +intro: 'The Organizations API gives you access to control and manage all your {% data variables.product.product_name %} organizations.' allowTitleToDifferFromFilename: true redirect_from: - /v3/orgs @@ -19,9 +19,9 @@ miniTocMaxHeadingLevel: 3 {% endfor %} {% ifversion fpt or ghec %} -## Bloquear usuários +## Blocking users -O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer quaisquer chamadas de bloqueio para uma organização. Caso contrário, a resposta retornará `HTTP 404`. +The token used to authenticate the call must have the `admin:org` scope in order to make any blocking calls for an organization. Otherwise, the response returns `HTTP 404`. {% for operation in currentRestOperations %} {% if operation.subcategory == 'blocking' %}{% include rest_operation %}{% endif %} @@ -29,13 +29,13 @@ O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer {% endif %} -## Integrantes +## Members {% for operation in currentRestOperations %} {% if operation.subcategory == 'members' %}{% include rest_operation %}{% endif %} {% endfor %} -## Colaboradores externos +## Outside collaborators {% for operation in currentRestOperations %} {% if operation.subcategory == 'outside-collaborators' %}{% include rest_operation %}{% endif %} @@ -51,28 +51,28 @@ O token usado para autenticar a chamada deve ter o escopo `admin:org` para fazer ## Webhooks -Os webhooks da organização permitem que você receba cargas de HTTP do tipo `POST` sempre que certos eventos ocorrerem dentro da organização. {% data reusables.webhooks.webhooks-rest-api-links %} +Organization webhooks allow you to receive HTTP `POST` payloads whenever certain events happen in an organization. {% data reusables.webhooks.webhooks-rest-api-links %} -Para obter mais informações sobre ações que você pode assinar, consulte "[ tipos de evento de {% data variables.product.prodname_dotcom %}](/developers/webhooks-and-events/github-event-types)". +For more information on actions you can subscribe to, see "[{% data variables.product.prodname_dotcom %} event types](/developers/webhooks-and-events/github-event-types)." -### Escopos & Restrições +### Scopes & Restrictions -Todas as ações contra webhooks da organização exigem que o usuário autenticado seja um administrador da organização que está sendo gerenciada. Além disso, os tokens do OAuth requerem o escopo `admin:org_hook`. Para obter mais informações, consulte "[Escopos para aplicativos OAuth](/developers/apps/scopes-for-oauth-apps)." +All actions against organization webhooks require the authenticated user to be an admin of the organization being managed. Additionally, OAuth tokens require the `admin:org_hook` scope. For more information, see "[Scopes for OAuth Apps](/developers/apps/scopes-for-oauth-apps)." -Para proteger dados sensíveis que podem estar presentes nas configurações do webhook, também aplicamos as seguintes regras de controle de acesso: +In order to protect sensitive data which may be present in webhook configurations, we also enforce the following access control rules: -- Os aplicativos OAuth não podem listar, visualizar ou editar webhooks que não criaram. -- Os usuários não podem listar, visualizar ou editar webhooks que foram criados por aplicativos OAuth. +- OAuth applications cannot list, view, or edit webhooks which they did not create. +- Users cannot list, view, or edit webhooks which were created by OAuth applications. -### Receber Webhooks +### Receiving Webhooks -Para que {% data variables.product.product_name %} envie cargas de webhook, seu servidor deve ser acessível pela internet. É altamente recomendável o uso de SSL para que possamos enviar cargas criptografadas por HTTPS. +In order for {% data variables.product.product_name %} to send webhook payloads, your server needs to be accessible from the Internet. We also highly suggest using SSL so that we can send encrypted payloads over HTTPS. -Para obter mais práticas recomendadas, [consulte nosso guia](/guides/best-practices-for-integrators/). +For more best practices, [see our guide](/guides/best-practices-for-integrators/). -#### Cabeçalhos de webhook +#### Webhook headers -{% data variables.product.product_name %} enviará ao longo de vários cabeçalhos de HTTP para diferenciar entre tipos de evento e identificadores de carga. Consulte [cabeçalhos de webhook](/webhooks/event-payloads/#delivery-headers) para obter informações. +{% data variables.product.product_name %} will send along several HTTP headers to differentiate between event types and payload identifiers. See [webhook headers](/webhooks/event-payloads/#delivery-headers) for details. {% for operation in currentRestOperations %} {% if operation.subcategory == 'webhooks' %}{% include rest_operation %}{% endif %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md index f6f7e88e11..74e1a19074 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md @@ -2,11 +2,11 @@ title: About searching on GitHub intro: 'Our integrated search covers the many repositories, users, and lines of code on {% data variables.product.product_name %}.' redirect_from: - - /articles/using-the-command-bar/ - - /articles/github-search-basics/ - - /articles/search-basics/ - - /articles/searching-github/ - - /articles/advanced-search/ + - /articles/using-the-command-bar + - /articles/github-search-basics + - /articles/search-basics + - /articles/searching-github + - /articles/advanced-search - /articles/about-searching-on-github - /github/searching-for-information-on-github/about-searching-on-github - /github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md index cf410536e1..2e98bbd3ee 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md @@ -3,9 +3,9 @@ title: Enabling GitHub.com repository search from your private enterprise enviro shortTitle: Search GitHub.com from enterprise intro: 'You can connect your personal accounts on {% data variables.product.prodname_dotcom_the_website %} and your private {% data variables.product.prodname_enterprise %} environment to search for content in certain {% data variables.product.prodname_dotcom_the_website %} repositories{% ifversion fpt or ghec %} from your private environment{% else %} from {% data variables.product.product_name %}{% endif %}.' redirect_from: - - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account/ - - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account/ - - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account/ + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-account + - /articles/enabling-private-github-com-repository-search-in-your-github-enterprise-server-account + - /articles/enabling-private-githubcom-repository-search-in-your-github-enterprise-server-account - /articles/enabling-githubcom-repository-search-in-github-enterprise-server - /github/searching-for-information-on-github/enabling-githubcom-repository-search-in-github-enterprise-server - /github/searching-for-information-on-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-in-github-enterprise-server diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md index 52eb5c8dcd..82108d649c 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax.md @@ -1,8 +1,8 @@ --- -title: Entender a sintaxe de pesquisa -intro: 'Durante a pesquisa no {% data variables.product.product_name %}, é possível criar consultas que correspondam a palavras e números específicos.' +title: Understanding the search syntax +intro: 'When searching {% data variables.product.product_name %}, you can construct queries that match specific numbers and words.' redirect_from: - - /articles/search-syntax/ + - /articles/search-syntax - /articles/understanding-the-search-syntax - /github/searching-for-information-on-github/understanding-the-search-syntax - /github/searching-for-information-on-github/getting-started-with-searching-on-github/understanding-the-search-syntax @@ -13,88 +13,87 @@ versions: ghec: '*' topics: - GitHub search -shortTitle: Entender a sintaxe de pesquisa +shortTitle: Understand search syntax --- +## Query for values greater or less than another value -## Consultar por valores maiores ou menores que outro valor +You can use `>`, `>=`, `<`, and `<=` to search for values that are greater than, greater than or equal to, less than, and less than or equal to another value. -Você pode usar `>`, `>=`, `<` e `<=` para pesquisar valores que sejam maiores, maiores ou iguais, menores e menores ou iguais a outro valor. +Query | Example +------------- | ------------- +>n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** matches repositories with the word "cats" that have more than 1000 stars. +>=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** matches repositories with the word "cats" that have 5 or more topics. +<n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** matches code with the word "cats" in files that are smaller than 10 KB. +<=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** matches repositories with the word "cats" that have 50 or fewer stars. -| Consulta | Exemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| >n | **[cats stars:>1000](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3E1000&type=Repositories)** corresponde a repositórios com a palavra "cats" com mais de 1000 estrelas. | -| >=n | **[cats topics:>=5](https://github.com/search?utf8=%E2%9C%93&q=cats+topics%3A%3E%3D5&type=Repositories)** corresponde a repositórios com a palavra "cats" com 5 ou mais tópicos. | -| <n | **[cats size:<10000](https://github.com/search?utf8=%E2%9C%93&q=cats+size%3A%3C10000&type=Code)** corresponde ao código com a palavra "cats" nos arquivos com tamanho inferior a 10 KB. | -| <=n | **[cats stars:<=50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%3C%3D50&type=Repositories)** corresponde a repositórios com a palavra "cats" com 50 estrelas ou menos. | +You can also use [range queries](#query-for-values-between-a-range) to search for values that are greater than or equal to, or less than or equal to, another value. -Você também pode usar [consultas de intervalo](#query-for-values-between-a-range) para pesquisar valores que são maiores ou iguais ou menores ou iguais a outro valor. +Query | Example +------------- | ------------- +n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** is equivalent to `stars:>=10` and matches repositories with the word "cats" that have 10 or more stars. +*..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** is equivalent to `stars:<=10` and matches repositories with the word "cats" that have 10 or fewer stars. -| Consulta | Exemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| n..* | **[cats stars:10..*](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..*&type=Repositories)** é equivalente a `stars:>=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas. | -| *..n | **[cats stars:*..10](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A%22*..10%22&type=Repositories)** é equivalente a `stars:<=10` e corresponde a repositórios com a palavra "cats" que têm até 10 estrelas. | +## Query for values between a range -## Consultar por valores dentro de um intervalo +You can use the range syntax n..n to search for values within a range, where the first number _n_ is the lowest value and the second is the highest value. -Você pode usar a sintaxe de intervalo n..n para pesquisar valores dentro de um intervalo, em que o primeiro número _n_ é o valor mais baixo e o segundo é o valor mais alto. +Query | Example +------------- | ------------- +n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** matches repositories with the word "cats" that have between 10 and 50 stars. -| Consulta | Exemplo | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| n..n | **[cats stars:10..50](https://github.com/search?utf8=%E2%9C%93&q=cats+stars%3A10..50&type=Repositories)** corresponde a repositórios com a palavra "cats" que têm entre 10 e 50 estrelas. | +## Query for dates -## Consultar por datas +You can search for dates that are earlier or later than another date, or that fall within a range of dates, by using `>`, `>=`, `<`, `<=`, and [range queries](#query-for-values-between-a-range). {% data reusables.time_date.date_format %} -Você pode usar `>`, `>=`, `<`, `<=` e [consultas de intervalo](#query-for-values-between-a-range) para pesquisar por datas anteriores ou posteriores a outra data ou que se enquadram em um intervalo de datas. {% data reusables.time_date.date_format %} - -| Consulta | Exemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| >YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados após 29 de abril de 2016. | -| >=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados a partir de 1 de abril de 2017. | -| <YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** corresponde ao código com a palavra "cats" em repositórios que foram carregados até 5 de julho de 2012. | -| <=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** corresponde a problemas com a palavra "cats" que foram criados em ou antes de 4 de julho de 2012. | -| YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** corresponde a repositórios com a palavra "cats" nos quais foi feito push entre o final de abril e julho de 2016. | -| YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** corresponde a problemas criados após 30 de abril de 2012 contendo a palavra "cats". | -| *..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** corresponde a problemas criados antes de 4 de julho de 2012 contendo a palavra "cats". | +Query | Example +------------- | ------------- +>YYYY-MM-DD | **[cats created:>2016-04-29](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E2016-04-29&type=Issues)** matches issues with the word "cats" that were created after April 29, 2016. +>=YYYY-MM-DD | **[cats created:>=2017-04-01](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3E%3D2017-04-01&type=Issues)** matches issues with the word "cats" that were created on or after April 1, 2017. +<YYYY-MM-DD | **[cats pushed:<2012-07-05](https://github.com/search?q=cats+pushed%3A%3C2012-07-05&type=Code&utf8=%E2%9C%93)** matches code with the word "cats" in repositories that were pushed to before July 5, 2012. +<=YYYY-MM-DD | **[cats created:<=2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A%3C%3D2012-07-04&type=Issues)** matches issues with the word "cats" that were created on or before July 4, 2012. +YYYY-MM-DD..YYYY-MM-DD | **[cats pushed:2016-04-30..2016-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+pushed%3A2016-04-30..2016-07-04&type=Repositories)** matches repositories with the word "cats" that were pushed to between the end of April and July of 2016. +YYYY-MM-DD..* | **[cats created:2012-04-30..*](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2012-04-30..*&type=Issues)** matches issues created after April 30th, 2012 containing the word "cats." +*..YYYY-MM-DD | **[cats created:*..2012-07-04](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A*..2012-07-04&type=Issues)** matches issues created before July 4th, 2012 containing the word "cats." {% data reusables.time_date.time_format %} -| Consulta | Exemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** corresponde a problemas criados entre 01 de janeiro de 2017 à 1h, com uma diferença de fuso horário de `07:00` em relação ao UTC, e 01 de março de 2017 às 15h, com uma diferença de fuso horário de `07:00` em relação ao UTC. com um ajuste de UTC de `07:00` e 1 de março de 2017 às 15h. com um ajuste de UTC de `07:00`. | -| YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** corresponde a problemas criados entre 21 de março de 2016 às 14h11 e 07 de abril de 2106 às 20h45. | +Query | Example +------------- | ------------- +YYYY-MM-DDTHH:MM:SS+00:00 | **[cats created:2017-01-01T01:00:00+07:00..2017-03-01T15:30:15+07:00](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2017-01-01T01%3A00%3A00%2B07%3A00..2017-03-01T15%3A30%3A15%2B07%3A00&type=Issues)** matches issues created between January 1, 2017 at 1 a.m. with a UTC offset of `07:00` and March 1, 2017 at 3 p.m. with a UTC offset of `07:00`. +YYYY-MM-DDTHH:MM:SSZ | **[cats created:2016-03-21T14:11:00Z..2016-04-07T20:45:00Z](https://github.com/search?utf8=%E2%9C%93&q=cats+created%3A2016-03-21T14%3A11%3A00Z..2016-04-07T20%3A45%3A00Z&type=Issues)** matches issues created between March 21, 2016 at 2:11pm and April 7, 2106 at 8:45pm. -## Excluir determinados resultados +## Exclude certain results -Usando a sintaxe `NOT`, é possível excluir resultados contendo uma determinada palavra. O operador `NOT` só pode ser usado para palavras-chave de string. Ele não funciona com numerais ou datas. +You can exclude results containing a certain word, using the `NOT` syntax. The `NOT` operator can only be used for string keywords. It does not work for numerals or dates. -| Consulta | Exemplo | -| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** corresponde a repositórios que têm a palavra "hello", mas não a palavra "world". | +Query | Example +------------- | ------------- +`NOT` | **[hello NOT world](https://github.com/search?q=hello+NOT+world&type=Repositories)** matches repositories that have the word "hello" but not the word "world." -Outra maneira de restringir os resultados da pesquisa é excluir determinados subconjuntos. Adicione um prefixo a qualquer qualificador de pesquisa com um `-` para excluir todos os resultados correspondentes a esse qualificador. +Another way you can narrow down search results is to exclude certain subsets. You can prefix any search qualifier with a `-` to exclude all results that are matched by that qualifier. -| Consulta | Exemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| -QUALIFIER | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization. | +Query | Example +------------- | ------------- +-QUALIFIER | **[mentions:defunkt -org:github](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization. -## Usar aspas para consultas com espaço em branco +## Use quotation marks for queries with whitespace -Se a consulta de pesquisa contém espaço em branco, é preciso colocá-lo entre aspas. Por exemplo: +If your search query contains whitespace, you will need to surround it with quotation marks. For example: -* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) corresponde a repositórios com a palavra "cats", mas não as palavras "hello world". -* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) corresponde a problemas com a palavra "build" que têm a etiqueta "bug fix". +* [cats NOT "hello world"](https://github.com/search?utf8=✓&q=cats+NOT+"hello+world"&type=Repositories) matches repositories with the word "cats" but not the words "hello world." +* [build label:"bug fix"](https://github.com/search?utf8=%E2%9C%93&q=build+label%3A%22bug+fix%22&type=Issues) matches issues with the word "build" that have the label "bug fix." -Alguns símbolos não alfanuméricos, como espaços, são descartados de consultas de pesquisa de código entre aspas, por isso os resultados podem ser inesperados. +Some non-alphanumeric symbols, such as spaces, are dropped from code search queries within quotation marks, so results can be unexpected. {% ifversion fpt or ghes or ghae or ghec %} -## Consultas com nomes de usuário +## Queries with usernames -Se sua consulta de pesquisa contiver um qualificador que exige um nome de usuário, como, por exemplo, `usuário`, `ator` ou `responsável`, você poderá usar qualquer nome de usuário de {% data variables.product.product_name %}, para especificar uma pessoa específica ou `@me` para especificar o usuário atual. +If your search query contains a qualifier that requires a username, such as `user`, `actor`, or `assignee`, you can use any {% data variables.product.product_name %} username, to specify a specific person, or `@me`, to specify the current user. -| Consulta | Exemplo | -| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) corresponde a commits criados por @nat | -| `QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) corresponde a problemas atribuídos à pessoa que está visualizando os resultados | +Query | Example +------------- | ------------- +`QUALIFIER:USERNAME` | [`author:nat`](https://github.com/search?q=author%3Anat&type=Commits) matches commits authored by @nat +`QUALIFIER:@me` | [`is:issue assignee:@me`](https://github.com/search?q=is%3Aissue+assignee%3A%40me&type=Issues) matches issues assigned to the person viewing the results -Você só pode usar `@me` com um qualificador e não como termo de pesquisa, como `@me main.workflow`. +You can only use `@me` with a qualifier and not as search term, such as `@me main.workflow`. {% endif %} diff --git a/translations/pt-BR/content/search-github/index.md b/translations/pt-BR/content/search-github/index.md index 9b5dc1a138..c2eeff5e6d 100644 --- a/translations/pt-BR/content/search-github/index.md +++ b/translations/pt-BR/content/search-github/index.md @@ -1,9 +1,9 @@ --- -title: Pesquisar informações no GitHub -intro: Use diferentes tipos de pesquisa para encontrar as informações desejadas. +title: Searching for information on GitHub +intro: Use different types of searches to find the information you want. redirect_from: - - /categories/78/articles/ - - /categories/search/ + - /categories/78/articles + - /categories/search - /categories/searching-for-information-on-github - /github/searching-for-information-on-github versions: @@ -16,6 +16,6 @@ topics: children: - /getting-started-with-searching-on-github - /searching-on-github -shortTitle: Pesquisar no GitHub +shortTitle: Search on GitHub --- diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md index d0f25c2d0c..f12649f07a 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md @@ -2,7 +2,7 @@ title: Searching for repositories intro: 'You can search for repositories on {% data variables.product.product_name %} and narrow the results using these repository search qualifiers in any combination.' redirect_from: - - /articles/searching-repositories/ + - /articles/searching-repositories - /articles/searching-for-repositories - /github/searching-for-information-on-github/searching-for-repositories - /github/searching-for-information-on-github/searching-on-github/searching-for-repositories diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 87b2785ed3..d41e60cedd 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -2,7 +2,7 @@ title: Searching issues and pull requests intro: 'You can search for issues and pull requests on {% data variables.product.product_name %} and narrow the results using these search qualifiers in any combination.' redirect_from: - - /articles/searching-issues/ + - /articles/searching-issues - /articles/searching-issues-and-pull-requests - /github/searching-for-information-on-github/searching-issues-and-pull-requests - /github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests diff --git a/translations/pt-BR/data/features/actions-starter-template-ui.yml b/translations/pt-BR/data/features/actions-starter-template-ui.yml new file mode 100644 index 0000000000..7e1ebe5384 --- /dev/null +++ b/translations/pt-BR/data/features/actions-starter-template-ui.yml @@ -0,0 +1,6 @@ +--- +#Reference: #5169. +#Documentation for the Actions starter template UI updates +versions: + fpt: '*' + ghec: '*' diff --git a/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md b/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md new file mode 100644 index 0000000000..cfa4a2b1c5 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/create-azure-app-plan.md @@ -0,0 +1,17 @@ +1. Create an Azure App Service plan. + + For example, you can use the Azure CLI to create a new App Service plan: + + ```bash{:copy} + az appservice plan create \ + --resource-group MY_RESOURCE_GROUP \ + --name MY_APP_SERVICE_PLAN \ + --is-linux + ``` + + In the command above, replace `MY_RESOURCE_GROUP` with your pre-existing Azure Resource Group, and `MY_APP_SERVICE_PLAN` with a new name for the App Service plan. + + See the Azure documentation for more information on using the [Azure CLI](https://docs.microsoft.com/cli/azure/): + + * For authentication, see "[Sign in with Azure CLI](https://docs.microsoft.com/cli/azure/authenticate-azure-cli)." + * If you need to create a new resource group, see "[az group](https://docs.microsoft.com/cli/azure/group?view=azure-cli-latest#az_group_create)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md b/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md new file mode 100644 index 0000000000..fc7ad43671 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/create-azure-publish-profile.md @@ -0,0 +1,5 @@ +1. Configure an Azure publish profile and create an `AZURE_WEBAPP_PUBLISH_PROFILE` secret. + + Generate your Azure deployment credentials using a publish profile. For more information, see "[Generate deployment credentials](https://docs.microsoft.com/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials)" in the Azure documentation. + + In your {% data variables.product.prodname_dotcom %} repository, create a secret named `AZURE_WEBAPP_PUBLISH_PROFILE` that contains the contents of the publish profile. For more information on creating secrets, see "[Encrypted secrets](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md b/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md new file mode 100644 index 0000000000..8de7a8d98f --- /dev/null +++ b/translations/pt-BR/data/reusables/docs/you-can-read-docs-for-your-product.md @@ -0,0 +1 @@ +You can read documentation that reflects the features available to you on {% data variables.product.product_name %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md index b78499d214..534d9c25e0 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-activity-threshold.md @@ -1 +1 @@ -A user account is considered to be dormant if it has not been active for {% ifversion ghec %}90 days{% else %}at least a month{% endif %}.{% ifversion ghes %} You may choose to suspend dormant users to release user licenses.{% endif %} +{% ifversion not ghec%}By default, a{% else %}A{% endif %} user account is considered to be dormant if it has not been active for 90 days. {% ifversion not ghec %}You can configure the length of time a user must be inactive to be considered dormant{% ifversion ghes%} and choose to suspend dormant users to release user licenses{% endif %}.{% endif %} diff --git a/translations/pt-BR/data/reusables/enterprise_migrations/locking-repositories.md b/translations/pt-BR/data/reusables/enterprise_migrations/locking-repositories.md index eaf587f3a6..3f82bb2d14 100644 --- a/translations/pt-BR/data/reusables/enterprise_migrations/locking-repositories.md +++ b/translations/pt-BR/data/reusables/enterprise_migrations/locking-repositories.md @@ -1,6 +1,6 @@ {% tip %} -**Aviso:** Bloquear um repositório impede todos os acessos de leitura ou gravação ao repositório. Não é possível associar novas equipes ou colaboradores a um repositório bloqueado. +**Note:** Locking a repository prevents all write access to the repository. Não é possível associar novas equipes ou colaboradores a um repositório bloqueado. Se você estiver realizando uma execução de teste, você não precisará bloquear o repositório. Ao fazer a migração dos dados de um repositório que está em uso, {% data variables.product.company_short %} recomenda fortemente o bloqueio do repositório. Para obter mais informações, consulte "[Sobre migrações](/enterprise/admin/migrations/about-migrations#types-of-migrations)". diff --git a/translations/pt-BR/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md b/translations/pt-BR/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md index 02145ede39..79e633d89d 100644 --- a/translations/pt-BR/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md +++ b/translations/pt-BR/data/reusables/getting-started/giving-access-to-repositories-projects-apps.md @@ -1,3 +1,3 @@ -You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with repository roles. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +You can give organization members, teams, and outside collaborators different levels of access to repositories owned by your organization with repository roles. Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". You can also customize access to your organization's project boards and allow individual organization members to manage your organization's {% data variables.product.prodname_github_apps %}. For more information, see "[Managing access to your organization's project boards](/organizations/managing-access-to-your-organizations-project-boards)" and "[Managing access to your organization's apps](/organizations/managing-access-to-your-organizations-apps)." diff --git a/translations/pt-BR/data/reusables/getting-started/managing-team-settings.md b/translations/pt-BR/data/reusables/getting-started/managing-team-settings.md index e93be75abb..509c0c3064 100644 --- a/translations/pt-BR/data/reusables/getting-started/managing-team-settings.md +++ b/translations/pt-BR/data/reusables/getting-started/managing-team-settings.md @@ -1,3 +1,3 @@ -You can designate a "team maintainer" to manage team settings and discussions, among other privileges. For more information, see "[Assigning the team maintainer role to a team member](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)." +You can designate a "team maintainer" to manage team settings and discussions, among other privileges. Para obter mais informações, consulte[Atribuindo a função de mantenedor da equipe a um integrante da equipe](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member)". You can manage code review assignments for your team, change team visibility, manage scheduled reminders for your team, and more in your team's settings. For more information, see "[Organizing members into teams](/organizations/organizing-members-into-teams)." diff --git a/translations/pt-BR/data/reusables/organizations/new-repo-permissions-more-info.md b/translations/pt-BR/data/reusables/organizations/new-repo-permissions-more-info.md index de8afc2ecc..059596eab3 100644 --- a/translations/pt-BR/data/reusables/organizations/new-repo-permissions-more-info.md +++ b/translations/pt-BR/data/reusables/organizations/new-repo-permissions-more-info.md @@ -1 +1 @@ -For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." +Para obter mais informações, consulte "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". diff --git a/translations/pt-BR/data/reusables/pages/check-workflow-run.md b/translations/pt-BR/data/reusables/pages/check-workflow-run.md new file mode 100644 index 0000000000..9a20b621d1 --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/check-workflow-run.md @@ -0,0 +1,8 @@ +{% ifversion fpt %} +1. If your {% data variables.product.prodname_pages %} site is built from a public repository, it is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." + +{% note %} + +{% data reusables.pages.pages-builds-with-github-actions-public-beta %} + +{% endnote %}{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/translations/pt-BR/data/reusables/pages/pages-builds-with-github-actions-public-beta.md new file mode 100644 index 0000000000..68073a7756 --- /dev/null +++ b/translations/pt-BR/data/reusables/pages/pages-builds-with-github-actions-public-beta.md @@ -0,0 +1,5 @@ +{% ifversion fpt %} + +**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories. + +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md index 67c95cfc8a..edc5821cce 100644 --- a/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md +++ b/translations/pt-BR/data/reusables/pages/twenty-minutes-to-publish.md @@ -1 +1 @@ -**Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}. Se você não vir suas alterações no navegador após uma hora, consulte "[Sobre erros de criação do Jekyll para sites de {% data variables.product.prodname_pages %}](/articles/about-jekyll-build-errors-for-github-pages-sites)". +**Note:** It can take up to 10 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}. If your don't see your {% data variables.product.prodname_pages %} site changes reflected in your browser after an hour, see "[About Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/about-jekyll-build-errors-for-github-pages-sites)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/saml/saml-accounts.md b/translations/pt-BR/data/reusables/saml/saml-accounts.md index 1933de50a4..7a82bfab61 100644 --- a/translations/pt-BR/data/reusables/saml/saml-accounts.md +++ b/translations/pt-BR/data/reusables/saml/saml-accounts.md @@ -1 +1,7 @@ -If you configure SAML SSO, members of your organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom_the_website %}. Quando um membro acessa recursos dentro de sua organização que usa o SAML SSO, o {% data variables.product.prodname_dotcom %} redireciona o integrante para o seu IdP para efetuar a autenticação. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. +If you configure SAML SSO, members of your organization will continue to log into their user accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. + +{% note %} + +**Note:** Organization members can perform read operations such as viewing, cloning, and forking on public resources owned by your organization even without a valid SAML session. + +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md index 562da1763a..7146a61572 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/pt-BR/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -18,6 +18,8 @@ Asana | Asana Personal Access Token | asana_personal_access_token{% endif %} Atl {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_access_token{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 %} +Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret{% endif %} +{%- ifversion fpt or ghec or ghes > 3.3 %} Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key{% endif %} Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token Azure | Azure SAS Token | azure_sas_token Azure | Azure Service Management Certificate | azure_management_certificate {%- ifversion ghes < 3.4 or ghae or ghae-issue-5342 %} Azure | Azure SQL Connection String | azure_sql_connection_string{% endif %} Azure | Azure Storage Account Key | azure_storage_account_key diff --git a/translations/pt-BR/data/ui.yml b/translations/pt-BR/data/ui.yml index 35f8d61642..06dbf1c8e1 100644 --- a/translations/pt-BR/data/ui.yml +++ b/translations/pt-BR/data/ui.yml @@ -29,6 +29,7 @@ toc: popular: Popular guides: Guias whats_new: O que há de novo + videos: Videos pages: article_version: 'Versão do artigo' miniToc: Neste artigo diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index 37f333d8eb..483a7a84b0 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -17,6 +17,7 @@ prodname_ghe_server: 'GitHub Enterprise Server' prodname_ghe_cloud: 'GitHub Enterprise Cloud' prodname_ghe_managed: 'GitHub AE' prodname_ghe_one: 'GitHub One' +prodname_docs: 'GitHub Docs' ## Use these variables when referring specifically to a location within a product product_location: >- {% ifversion ghes %}your GitHub Enterprise Server instance{% elsif ghae %}your enterprise{% else %}GitHub.com{% endif %} @@ -182,7 +183,7 @@ api_url_code: >- {% ifversion fpt or ghec %}https://api.github.com{% elsif ghes %}http(s)://[hostname]/api/v3{% elsif ghae %}https://[hostname]/api/v3{% endif %} #Use this inside command-line code blocks graphql_url_pre: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://api.[hostname]/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %} #Use this all other code blocks graphql_url_code: >- - {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://api.[hostname]/graphql{% endif %} + {% ifversion fpt or ghec %}https://api.github.com/graphql{% elsif ghes %}http(s)://[hostname]/api/graphql{% elsif ghae %}https://[hostname]/api/graphql{% endif %}