From aa1aee9dae4f9a3c4bb01ce8e2f80657ddbf1fe7 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Wed, 16 Feb 2022 10:18:04 -0800 Subject: [PATCH 1/2] New translation batch for pt (#25425) * 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/reset-files-with-broken-liquid-tags.js --language=pt * run script/i18n/reset-known-broken-translation-files.js * Check in pt CSV report Co-authored-by: Grace Park --- translations/log/pt-resets.csv | 1 - .../content/actions/advanced-guides/index.md | 17 -- .../storing-workflow-data-as-artifacts.md | 255 ----------------- ...g-openid-connect-in-amazon-web-services.md | 3 +- ...-openid-connect-with-reusable-workflows.md | 1 + translations/pt-BR/content/actions/index.md | 1 - .../actions/learn-github-actions/contexts.md | 2 + ...usage-limits-billing-and-administration.md | 2 + .../security-hardening-for-github-actions.md | 9 - ...hing-dependencies-to-speed-up-workflows.md | 7 +- .../content/actions/using-workflows/index.md | 4 + .../using-workflows/reusing-workflows.md | 1 + .../storing-workflow-data-as-artifacts.md | 256 ++++++++++++++++++ .../using-workflows/triggering-a-workflow.md | 2 + .../using-github-cli-in-workflows.md | 1 + .../workflow-syntax-for-github-actions.md | 4 + .../content/admin/code-security/index.md | 14 + ...guring-code-scanning-for-your-appliance.md | 5 +- ...ring-secret-scanning-for-your-appliance.md | 3 +- ...ub-advanced-security-in-your-enterprise.md | 2 + ...b-advanced-security-for-your-enterprise.md | 10 +- .../index.md | 3 +- ...-of-github-advanced-security-deployment.md | 2 + ...pply-chain-security-for-your-enterprise.md | 20 ++ ...he-dependency-graph-for-your-enterprise.md | 59 ++++ .../index.md | 15 + ...-vulnerability-data-for-your-enterprise.md | 25 ++ .../about-github-connect.md | 20 +- ...c-user-license-sync-for-your-enterprise.md | 2 +- ...enabling-dependabot-for-your-enterprise.md | 126 +++++++++ ...d-dependabot-alerts-for-your-enterprise.md | 127 --------- ...ified-contributions-for-your-enterprise.md | 2 +- ...ling-unified-search-for-your-enterprise.md | 2 +- .../configuring-github-connect/index.md | 2 +- .../configuring-dns-nameservers.md | 12 +- .../evacuating-a-cluster-node.md | 90 +++--- ...ting-github-actions-for-your-enterprise.md | 40 +++ .../index.md | 2 +- ...-hosted-runners-for-dependabot-updates.md} | 39 ++- ...ub-actions-for-github-enterprise-server.md | 6 +- ...ucing-github-actions-to-your-enterprise.md | 1 + .../using-saml.md | 118 ++++++-- translations/pt-BR/content/admin/index.md | 2 +- .../content/admin/overview/system-overview.md | 6 + .../index.md | 1 + ...ne-time-payments-for-customers-in-india.md | 65 +++++ .../securing-your-repository.md | 2 +- ...tifications-for-vulnerable-dependencies.md | 2 +- .../about-dependency-review.md | 2 +- .../about-the-dependency-graph.md | 9 +- ...loring-the-dependencies-of-a-repository.md | 2 +- .../signing-up-for-a-new-github-account.md | 1 + .../using-github/keyboard-shortcuts.md | 5 +- ...sferring-an-issue-to-another-repository.md | 2 +- .../pt-BR/content/organizations/index.md | 21 +- ...rs-to-repositories-in-your-organization.md | 9 +- ...ls-access-to-an-organization-repository.md | 10 +- ...am-access-to-an-organization-repository.md | 16 +- ...borator-from-an-organization-repository.md | 3 + ...g-people-with-access-to-your-repository.md | 19 +- .../managing-organization-settings/index.md | 1 + ...ll-request-reviews-in-your-organization.md | 27 ++ ...om-repository-roles-for-an-organization.md | 2 +- .../roles-in-an-organization.md | 5 +- .../about-pull-requests.md | 2 +- .../about-pull-request-reviews.md | 2 + .../about-protected-branches.md | 2 +- .../managing-a-branch-protection-rule.md | 6 +- .../about-code-owners.md | 9 +- .../managing-repository-settings/index.md | 1 + ...pull-request-reviews-in-your-repository.md | 27 ++ ...d-people-with-access-to-your-repository.md | 22 +- .../about-releases.md | 14 +- .../overview/other-authentication-methods.md | 2 +- .../overview/resources-in-the-rest-api.md | 38 +-- .../content/rest/reference/codespaces.md | 12 +- .../pt-BR/content/rest/reference/gitignore.md | 2 +- .../content/rest/reference/migrations.md | 5 +- .../pt-BR/content/rest/reference/pages.md | 2 +- .../permissions-required-for-github-apps.md | 5 +- .../content/rest/reference/rate-limit.md | 2 +- .../pt-BR/content/rest/reference/search.md | 4 +- .../content/rest/reference/secret-scanning.md | 8 +- .../pt-BR/content/rest/reference/teams.md | 10 +- .../pt-BR/content/rest/reference/webhooks.md | 6 +- .../about-searching-on-github.md | 8 +- ...rom-your-private-enterprise-environment.md | 12 +- .../sorting-search-results.md | 16 +- .../understanding-the-search-syntax.md | 8 +- .../searching-on-github/searching-code.md | 10 +- .../searching-on-github/searching-commits.md | 4 +- .../searching-discussions.md | 2 +- .../searching-for-packages.md | 8 +- .../searching-for-repositories.md | 22 +- .../searching-on-github/searching-in-forks.md | 2 +- .../searching-issues-and-pull-requests.md | 42 +-- .../about-github-sponsors.md | 4 +- .../managing-your-sponsorship-tiers.md | 6 +- ...p-github-sponsors-for-your-organization.md | 2 +- .../sponsoring-an-open-source-contributor.md | 2 +- .../contacting-github-support/index.md | 4 +- .../viewing-and-updating-support-tickets.md | 8 +- translations/pt-BR/content/support/index.md | 2 +- .../about-github-premium-support.md | 28 +- .../learning-about-github-support/index.md | 4 +- .../pt-BR/data/features/codeowners-errors.yml | 6 + .../dependabot-updates-github-connect.yml | 4 + .../features/pull-request-approval-limit.yml | 8 + .../ghes-3.4/graphql_previews.enterprise.yml | 124 +++++++++ ...hql_upcoming_changes.public-enterprise.yml | 114 ++++++++ .../enterprise-server/3-4/0-rc1.yml | 193 +++++++++++++ .../reusables/actions/minimum-hardware.md | 1 + .../actions/reusable-workflows-ghes-beta.md | 9 + .../dependabot/about-the-dependency-graph.md | 4 + .../beta-security-and-version-updates.md | 6 +- ...abot-alerts-dependency-graph-enterprise.md | 2 +- .../enterprise-enable-dependabot.md | 2 +- .../data/reusables/desktop/revert-commit.md | 2 +- .../preventing-nameservers-change.md | 5 + .../built-in-authentication-option.md | 2 +- .../built-in-authentication.md | 2 +- .../github-token-available-permissions.md | 6 + .../organizations/invite-teams-or-people.md | 2 +- .../organizations/mixed-roles-warning.md | 1 + .../pull_requests/code-review-limits.md | 1 + .../repositories/enable-security-alerts.md | 2 +- translations/pt-BR/data/variables/product.yml | 1 + .../data/variables/release_candidate.yml | 2 +- 128 files changed, 1666 insertions(+), 733 deletions(-) delete mode 100644 translations/pt-BR/content/actions/advanced-guides/index.md delete mode 100644 translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md rename translations/pt-BR/content/actions/{advanced-guides => using-workflows}/caching-dependencies-to-speed-up-workflows.md (95%) create mode 100644 translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md rename translations/pt-BR/content/actions/{advanced-guides => using-workflows}/using-github-cli-in-workflows.md (98%) create mode 100644 translations/pt-BR/content/admin/code-security/index.md rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/configuring-code-scanning-for-your-appliance.md (92%) rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/configuring-secret-scanning-for-your-appliance.md (97%) rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/deploying-github-advanced-security-in-your-enterprise.md (99%) rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/enabling-github-advanced-security-for-your-enterprise.md (93%) rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/index.md (92%) rename translations/pt-BR/content/admin/{advanced-security => code-security/managing-github-advanced-security-for-your-enterprise}/overview-of-github-advanced-security-deployment.md (99%) create mode 100644 translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md create mode 100644 translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md create mode 100644 translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md create mode 100644 translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md create mode 100644 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md delete mode 100644 translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md rename translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/{setting-up-dependabot-updates.md => managing-self-hosted-runners-for-dependabot-updates.md} (50%) create mode 100644 translations/pt-BR/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md create mode 100644 translations/pt-BR/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md create mode 100644 translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md create mode 100644 translations/pt-BR/data/features/codeowners-errors.yml create mode 100644 translations/pt-BR/data/features/dependabot-updates-github-connect.yml create mode 100644 translations/pt-BR/data/features/pull-request-approval-limit.yml create mode 100644 translations/pt-BR/data/graphql/ghes-3.4/graphql_previews.enterprise.yml create mode 100644 translations/pt-BR/data/graphql/ghes-3.4/graphql_upcoming_changes.public-enterprise.yml create mode 100644 translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml create mode 100644 translations/pt-BR/data/reusables/actions/minimum-hardware.md create mode 100644 translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md create mode 100644 translations/pt-BR/data/reusables/dependabot/about-the-dependency-graph.md create mode 100644 translations/pt-BR/data/reusables/enterprise_installation/preventing-nameservers-change.md create mode 100644 translations/pt-BR/data/reusables/organizations/mixed-roles-warning.md create mode 100644 translations/pt-BR/data/reusables/pull_requests/code-review-limits.md diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv index 49d8776218..cfd85be75d 100644 --- a/translations/log/pt-resets.csv +++ b/translations/log/pt-resets.csv @@ -1,6 +1,5 @@ file,reason translations/pt-BR/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags -translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/about-self-hosted-runners.md,broken liquid tags translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,Listed in localization-support#489 translations/pt-BR/content/actions/hosting-your-own-runners/adding-self-hosted-runners.md,broken liquid tags diff --git a/translations/pt-BR/content/actions/advanced-guides/index.md b/translations/pt-BR/content/actions/advanced-guides/index.md deleted file mode 100644 index 88ac315147..0000000000 --- a/translations/pt-BR/content/actions/advanced-guides/index.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Guias avançados -shortTitle: Guias avançados -intro: 'Como armazenar dependências, armazenar os resultados como artefatos e usar a CLI do GitHub em fluxos de trabalho.' -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -redirect_from: - - /actions/guides/caching-and-storing-workflow-data -children: - - /caching-dependencies-to-speed-up-workflows - - /storing-workflow-data-as-artifacts - - /using-github-cli-in-workflows ---- - diff --git a/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md deleted file mode 100644 index 11c7be0499..0000000000 --- a/translations/pt-BR/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md +++ /dev/null @@ -1,255 +0,0 @@ ---- -title: Storing workflow data as artifacts -shortTitle: Storing workflow artifacts -intro: Artifacts allow you to share data between jobs in a workflow and store data once that workflow has completed. -redirect_from: - - /articles/persisting-workflow-data-using-artifacts - - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts - - /actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts - - /actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts - - /actions/guides/storing-workflow-data-as-artifacts -versions: - fpt: '*' - ghes: '*' - ghae: '*' - ghec: '*' -type: tutorial -topics: - - Workflows ---- - -{% data reusables.actions.enterprise-beta %} -{% data reusables.actions.enterprise-github-hosted-runners %} - -## About workflow artifacts - -Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %} - -{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request. - -These are some of the common artifacts that you can upload: - -- Log files and core dumps -- Test results, failures, and screenshots -- Binary or compressed files -- Stress test performance output and code coverage results - -{% ifversion fpt or ghec %} - -Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)." - -{% else %} - -Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.product.product_location %}. - -{% endif %} - -Artifacts are uploaded during a workflow run, and you can view an artifact's name and size in the UI. When an artifact is downloaded using the {% data variables.product.product_name %} UI, all files that were individually uploaded as part of the artifact get zipped together into a single file. This means that billing is calculated based on the size of the uploaded artifact and not the size of the zip file. - -{% data variables.product.product_name %} provides two actions that you can use to upload and download build artifacts. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}. - -To share data between jobs: - -* **Uploading files**: Give the uploaded file a name and upload the data before the job ends. -* **Downloading files**: You can only download artifacts that were uploaded during the same workflow run. When you download a file, you can reference it by name. - -The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)." - -## Uploading build and test artifacts - -You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)." - -The output of building and testing your code often produces files you can use to debug test failures and production code that you can deploy. You can configure a workflow to build and test the code pushed to your repository and report a success or failure status. You can upload the build and test output to use for deployments, debugging failed tests or crashes, and viewing test suite coverage. - -You can use the `upload-artifact` action to upload artifacts. When uploading an artifact, you can specify a single file or directory, or multiple files or directories. You can also exclude certain files or directories, and use wildcard patterns. We recommend that you provide a name for an artifact, but if no name is provided then `artifact` will be used as the default name. For more information on syntax, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) action{% else %} `actions/upload-artifact` action on {% data variables.product.product_location %}{% endif %}. - -### Example - -For example, your repository or a web application might contain SASS and TypeScript files that you must convert to CSS and JavaScript. Assuming your build configuration outputs the compiled files in the `dist` directory, you would deploy the files in the `dist` directory to your web application server if all tests completed successfully. - -``` -|-- hello-world (repository) -| └── dist -| └── tests -| └── src -| └── sass/app.scss -| └── app.ts -| └── output -| └── test -| -``` - -This example shows you how to create a workflow for a Node.js project that builds the code in the `src` directory and runs the tests in the `tests` directory. You can assume that running `npm test` produces a code coverage report named `code-coverage.html` stored in the `output/test/` directory. - -The workflow uploads the production artifacts in the `dist` directory, but excludes any markdown files. It also uploads the `code-coverage.html` report as another artifact. - -```yaml{:copy} -name: Node CI - -on: [push] - -jobs: - build_and_test: - runs-on: ubuntu-latest - steps: - - name: Checkout repository - uses: actions/checkout@v2 - - name: npm install, build, and test - run: | - npm install - npm run build --if-present - npm test - - name: Archive production artifacts - uses: actions/upload-artifact@v2 - with: - name: dist-without-markdown - path: | - dist - !dist/**/*.md - - name: Archive code coverage results - uses: actions/upload-artifact@v2 - with: - name: code-coverage-report - path: output/test/code-coverage.html -``` - -## Configuring a custom artifact retention period - -You can define a custom retention period for individual artifacts created by a workflow. When using a workflow to create a new artifact, you can use `retention-days` with the `upload-artifact` action. This example demonstrates how to set a custom retention period of 5 days for the artifact named `my-artifact`: - -```yaml{:copy} - - name: 'Upload Artifact' - uses: actions/upload-artifact@v2 - with: - name: my-artifact - path: my_file.txt - retention-days: 5 -``` - -The `retention-days` value cannot exceed the retention limit set by the repository, organization, or enterprise. - -## Downloading or deleting artifacts - -During a workflow run, you can use the [`download-artifact`](https://github.com/actions/download-artifact) action to download artifacts that were previously uploaded in the same workflow run. - -After a workflow run has been completed, you can download or delete artifacts on {% data variables.product.prodname_dotcom %} or using the REST API. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." - -### Downloading artifacts during a workflow run - -The [`actions/download-artifact`](https://github.com/actions/download-artifact) action can be used to download previously uploaded artifacts during a workflow run. - -{% note %} - -**Note:** You can only download artifacts in a workflow that were uploaded during the same workflow run. - -{% endnote %} - -Specify an artifact's name to download an individual artifact. If you uploaded an artifact without specifying a name, the default name is `artifact`. - -```yaml -- name: Download a single artifact - uses: actions/download-artifact@v2 - with: - name: my-artifact -``` - -You can also download all artifacts in a workflow run by not specifying a name. This can be useful if you are working with lots of artifacts. - -```yaml -- name: Download all workflow run artifacts - uses: actions/download-artifact@v2 -``` - -If you download all workflow run's artifacts, a directory for each artifact is created using its name. - -For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.product.product_location %}{% endif %}. - -## Passing data between jobs in a workflow - -You can use the `upload-artifact` and `download-artifact` actions to share data between jobs in a workflow. This example workflow illustrates how to pass data between jobs in the same workflow. For more information, see the {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) and [download-artifact](https://github.com/actions/download-artifact) actions{% else %} `actions/upload-artifact` and `download-artifact` actions on {% data variables.product.product_location %}{% endif %}. - -Jobs that are dependent on a previous job's artifacts must wait for the dependent job to complete successfully. This workflow uses the `needs` keyword to ensure that `job_1`, `job_2`, and `job_3` run sequentially. For example, `job_2` requires `job_1` using the `needs: job_1` syntax. - -Job 1 performs these steps: -- Performs a math calculation and saves the result to a text file called `math-homework.txt`. -- Uses the `upload-artifact` action to upload the `math-homework.txt` file with the artifact name `homework`. - -Job 2 uses the result in the previous job: -- Downloads the `homework` artifact uploaded in the previous job. By default, the `download-artifact` action downloads artifacts to the workspace directory that the step is executing in. You can use the `path` input parameter to specify a different download directory. -- Reads the value in the `math-homework.txt` file, performs a math calculation, and saves the result to `math-homework.txt` again, overwriting its contents. -- Uploads the `math-homework.txt` file. This upload overwrites the previously uploaded artifact because they share the same name. - -Job 3 displays the result uploaded in the previous job: -- Downloads the `homework` artifact. -- Prints the result of the math equation to the log. - -The full math operation performed in this workflow example is `(3 + 7) x 9 = 90`. - -```yaml{:copy} -name: Share data between jobs - -on: [push] - -jobs: - job_1: - name: Add 3 and 7 - runs-on: ubuntu-latest - steps: - - shell: bash - run: | - expr 3 + 7 > math-homework.txt - - name: Upload math result for job 1 - uses: actions/upload-artifact@v2 - with: - name: homework - path: math-homework.txt - - job_2: - name: Multiply by 9 - needs: job_1 - runs-on: windows-latest - steps: - - name: Download math result for job 1 - uses: actions/download-artifact@v2 - with: - name: homework - - shell: bash - run: | - value=`cat math-homework.txt` - expr $value \* 9 > math-homework.txt - - name: Upload math result for job 2 - uses: actions/upload-artifact@v2 - with: - name: homework - path: math-homework.txt - - job_3: - name: Display results - needs: job_2 - runs-on: macOS-latest - steps: - - name: Download math result for job 2 - uses: actions/download-artifact@v2 - with: - name: homework - - name: Print the final result - shell: bash - run: | - value=`cat math-homework.txt` - echo The result is $value -``` - -The workflow run will archive any artifacts that it generated. For more information on downloading archived artifacts, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)." -{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) -{% else %} -![Workflow that passes data between jobs to perform math](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) -{% endif %} - -{% ifversion fpt or ghec %} - -## Further reading - -- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". - -{% endif %} diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index 690364f69f..3dc4348dcc 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -42,7 +42,8 @@ Edite o relacionamento de confiança para adicionar o campo `sub` às condiçõe ```json{:copy} "Condition": { - "StringEquals": { + "ForAllValues:StringEquals": { + "token.actions.githubusercontent.com:aud": "sts.amazonaws.com", "token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" } } diff --git a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md index da3b7d004c..bba7316c2c 100644 --- a/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md +++ b/translations/pt-BR/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md @@ -9,6 +9,7 @@ versions: fpt: '*' ghae: issue-4757-and-5856 ghec: '*' + ghes: '>=3.5' type: how_to topics: - Workflows diff --git a/translations/pt-BR/content/actions/index.md b/translations/pt-BR/content/actions/index.md index be178403ba..17bc1de834 100644 --- a/translations/pt-BR/content/actions/index.md +++ b/translations/pt-BR/content/actions/index.md @@ -63,7 +63,6 @@ children: - /using-github-hosted-runners - /hosting-your-own-runners - /security-guides - - /advanced-guides - /creating-actions - /guides --- 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 60f28a09e5..a500c615dd 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/contexts.md +++ b/translations/pt-BR/content/actions/learn-github-actions/contexts.md @@ -711,6 +711,8 @@ O contexto `entrada` contém propriedades de entrada passada para um fluxo de tr Não há propriedades padrão no contexto `entradas`, apenas aquelas definidas no arquivo de fluxo de trabalho reutilizável. +{% data reusables.actions.reusable-workflows-ghes-beta %} + Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". | Nome da propriedade | Tipo | Descrição | diff --git a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md index 5ac68ab8b2..64b12b64c2 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md +++ b/translations/pt-BR/content/actions/learn-github-actions/usage-limits-billing-and-administration.md @@ -73,6 +73,8 @@ Além dos limites de uso, você deve garantir que você usa {% data variables.pr {% ifversion fpt or ghes > 3.3 or ghec %} ## Cobrança para fluxos de trabalho reutilizáveis +{% data reusables.actions.reusable-workflows-ghes-beta %} + Se você reutilizar um fluxo de trabalho, a cobrança será sempre associada ao fluxo de trabalho de chamadas. A atribuição de executores hospedados em {% data variables.product.prodname_dotcom %}é sempre avaliada usando apenas o contexto do invocador. O invocador não pode usar os executores hospedados em {% data variables.product.prodname_dotcom %} do repositório invocado. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". diff --git a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md index 57905a4c44..ead1af7680 100644 --- a/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md @@ -141,15 +141,6 @@ Neste exemplo, a injeção de script não tem sucesso: Com esta abordagem, o valor da expressão de {% raw %}`${{ github.event.issue.title }}`{% endraw %} é armazenado na memória e usada como uma variável e não interage com o processo de geração de script. Além disso, considere usar variáveis do shell de citação dupla para evitar [divisão de palavras](https://github.com/koalaman/shellcheck/wiki/SC2086), mas esta é [uma das muitas](https://mywiki.wooledge.org/BashPitfalls) recomendações gerais para escrever scripts de shell e não é específica para {% data variables.product.prodname_actions %}. -### Usar o CodeQL para analisar seu código - -Para ajudar você a gerenciar o risco de padrões perigosos o mais cedo possível no ciclo de vida do desenvolvimento, o Laboratório de Segurança de {% data variables.product.prodname_dotcom %} desenvolveu [as consultas do CodeQL](https://github.com/github/codeql/tree/main/javascript/ql/src/experimental/Security/CWE-094) que os proprietários de repositórios podem [integrar](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#running-additional-queries) a seus pipelines CI/CD. Para obter mais informações, consulte "[Sobre a varredura de código](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)". - -Atualmente, os scripts atualmente das bibliotecas JavaScript do CodeQL, o que significa que o repositório analisado deve conter pelo menos um arquivo JavaScript e que o CodeQL deve ser [configurado para analisar esta linguagem](/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed). - -- `ExpressionInjection.ql`: Cobre as injeções de expressão descritas neste artigo e é considerada razoavelmente precisa. No entanto, ele não executa o rastreamento de dados entre as etapas do fluxo de trabalho. -- `UntrustedCheckout. l`: Os resultados deste script exigem revisão manual para determinar se o código de um pull request é realmente tratado de forma não segura. Para obter mais informações, consulte "[Manter o seu GitHub Actions e fluxos de trabalho seguro: impedindo solicitações pwn](https://securitylab.github.com/research/github-actions-preventing-pwn-requests)" no blogue {% data variables.product.prodname_dotcom %} do Laboratório de Segurança. - ### Restringir permissões para tokens Para ajudar a mitigar o risco de um token exposto, considere restringir as permissões atribuídas. Para obter mais informações, consulte "[Modificar as permissões para o GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)". diff --git a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md similarity index 95% rename from translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md rename to translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index b8d2531467..bdd2b0c959 100644 --- a/translations/pt-BR/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -7,6 +7,7 @@ redirect_from: - /actions/automating-your-workflow-with-github-actions/caching-dependencies-to-speed-up-workflows - /actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows - /actions/guides/caching-dependencies-to-speed-up-workflows + - /actions/advanced-guides/caching-dependencies-to-speed-up-workflows versions: fpt: '*' ghec: '*' @@ -88,7 +89,7 @@ Para obter mais informações, consulte [`ações/cache`](https://github.com/act ### Parâmetros de entrada para a ação da `cache` - `key`: **Obrigatório** A chave criada ao salvar uma cache e a chave usada para pesquisar uma cache. Pode ser qualquer combinação de variáveis, valores de contexto, strings estáticas e funções. As chaves têm um tamanho máximo de 512 caracteres e as chaves maiores que o tamanho máximo gerarão uma falha na ação. -- ``de caminho : **Required** O caminho do arquivo no corredor para cache ou restauração. O caminho pode ser absoluto ou relativo com relação ao diretório de trabalho. +- `path`: **Required** The file path on the runner to cache or restore. O caminho pode ser absoluto ou relativo com relação ao diretório de trabalho. - Os caminhos podem ser diretórios ou arquivos únicos. Os padrões de glob são compatíveis. - Com o `v2` da ação `cache`, é possível especificar um único caminho ou é possível adicionar vários caminhos em linhas separadas. Por exemplo: ``` @@ -99,7 +100,7 @@ Para obter mais informações, consulte [`ações/cache`](https://github.com/act ~/.gradle/caches ~/.gradle/wrapper ``` - - Com `v1` da ação da `cache`, somente um caminho único é compatível e deve ser um diretório. Você não pode armazenar um único arquivo. + - Com `v1` da ação da `cache`, somente um caminho único é compatível e deve ser um diretório. You cannot cache a single file. - `chaves de restauração`: **Opcional** Uma lista ordenada de chaves alternativas a serem usadas para encontrar a cache se não ocorrer correspondência para a `chave`. ### Parâmetros de saída para a ação da `cache` @@ -232,4 +233,4 @@ Por exemplo, se um pull request contiver um branch de`recurso` (escopo atual) e ## Limites de uso e política de eliminação -{% data variables.product.prodname_dotcom %} removerá todas as entradas da cache não acessadas há mais de 7 dias. Não há limite para o número de caches que você pode armazenar, mas o limite do tamanho total de todas as caches em um repositório é 10 GB. Se você exceder este limite, {% data variables.product.prodname_dotcom %} salvará a sua cache, mas começará a eliminar as caches até que o tamanho total seja inferior a 10 GB. +{% data variables.product.prodname_dotcom %} removerá todas as entradas da cache não acessadas há mais de 7 dias. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB. diff --git a/translations/pt-BR/content/actions/using-workflows/index.md b/translations/pt-BR/content/actions/using-workflows/index.md index a3735c7c32..ac1f11efde 100644 --- a/translations/pt-BR/content/actions/using-workflows/index.md +++ b/translations/pt-BR/content/actions/using-workflows/index.md @@ -14,6 +14,7 @@ redirect_from: - /actions/automating-your-workflow-with-github-actions/configuring-workflows - /actions/configuring-and-managing-workflows - /actions/workflows + - /actions/advanced-guides versions: fpt: '*' ghes: '*' @@ -29,5 +30,8 @@ children: - /creating-starter-workflows-for-your-organization - /using-starter-workflows - /sharing-workflows-secrets-and-runners-with-your-organization + - /caching-dependencies-to-speed-up-workflows + - /storing-workflow-data-as-artifacts + - /using-github-cli-in-workflows --- diff --git a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md index 33d61ce792..2f1356a42c 100644 --- a/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/reusing-workflows.md @@ -16,6 +16,7 @@ topics: --- {% data reusables.actions.enterprise-beta %} +{% data reusables.actions.reusable-workflows-ghes-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} ## Visão Geral diff --git a/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md new file mode 100644 index 0000000000..d90d3d51db --- /dev/null +++ b/translations/pt-BR/content/actions/using-workflows/storing-workflow-data-as-artifacts.md @@ -0,0 +1,256 @@ +--- +title: Armazenar dados do fluxo de trabalho como artefatos +shortTitle: Armazenando artefatos do fluxo de trabalho +intro: Artefatos permitem que você compartilhe dados entre trabalhos em um fluxo e armazene dados quando o fluxo de trabalho estiver concluído. +redirect_from: + - /articles/persisting-workflow-data-using-artifacts + - /github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts + - /actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts + - /actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts + - /actions/guides/storing-workflow-data-as-artifacts + - /actions/advanced-guides/storing-workflow-data-as-artifacts +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +type: tutorial +topics: + - Workflows +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Sobre artefatos de fluxos de trabalho + +Os artefatos permitem que você persista com os dados após um trabalho ter sido concluído e compartilhe os dados com outro trabalho no mesmo fluxo de trabalho. Um artefato é um arquivo ou uma coleção de arquivos produzidos durante a execução de um fluxo de trabalho. Por exemplo, você pode usar artefatos para salvar a sua criação e testar a saída após uma conclusão da execução do fluxo de trabalho. {% data reusables.actions.reusable-workflow-artifacts %} + +{% data reusables.github-actions.artifact-log-retention-statement %} O período de retenção para um pull request reinicia toda vez que alguém fizer um push de um novo commit para o pull request. + +Esses são alguns dos artefatos comuns cujo upload você pode fazer: + +- Arquivos de log e descartes de memória; +- Resultados de testes, falhas e capturas de tela; +- Arquivos binários ou comprimidos +- Resultados de teste de estresse e resultados de cobertura do código. + +{% ifversion fpt or ghec %} + +Armazenar artefatos consome espaço de armazenamento em {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} Para mais informações, consulte "[Gerenciando cobrança para {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". + +{% else %} + +Artifacts consume storage space on the external blob storage that is configured for {% data variables.product.prodname_actions %} on {% data variables.product.product_location %}. + +{% endif %} + +Faz-se o upload dos artefatos durante a execução de um fluxo de trabalho e você pode visualizar o nome e o tamanho do artefato na UI. Quando se faz o download de um artefato usando a UI {% data variables.product.product_name %}, todos os arquivos cujo upload foi feito individualmente como parte do get do artefato zipado em um arquivo único. Isso significa que a cobrança é calculada com base no tamanho do artefato subido e não com base no tamanho do arquivo zip. + +O {% data variables.product.product_name %} fornece duas ações que você pode usar para fazer upload e baixar artefatos de compilação. Para mais informações veja o {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) e [download-artefact](https://github.com/actions/download-artifact) ações{% else %} `actions/upload-artefact` e `download-artefact` ações em {% data variables.product.product_location %}{% endif %}. + +Para compartilhar dados entre trabalhos: + +* **Fazendo o upload dos arquivos**: Fornece ao arquivo subido um nome e faz o upload dos dados antes da conclusão do trabalho. +* **Fazendo o download dos arquivos**: Você pode apenas fazer o download dos artefatos que foram subidos durante a mesma execução do fluxo de trabalho. Ao fazer o download de um arquivo, você pode fazer referenciá-lo pelo nome. + +As etapas de um trabalho compartilham o mesmo ambiente na máquina executora, mas são executados em seus próprios processos individuais. Para transmitir dados entre etapas de um trabalho, você pode usar entradas e saídas. Para obter mais informações sobre entradas e saídas, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)". + +## Fazer upload da compilação e testar artefatos + +Você pode criar um fluxo de trabalho de integração contínua (CI) para criar e testar o seu código. Para obter mais informações sobre o uso do {% data variables.product.prodname_actions %} para executar CI, consulte "[Sobre integração contínua](/articles/about-continuous-integration)." + +A saída da compilação e teste de seu código muitas vezes produz arquivos que podem ser usados para depurar falhas em testes e códigos de produção que você pode implantar. É possível configurar um fluxo de trabalho para compilar e testar o código com push no repositório e relatar um status de sucesso ou falha. Você pode fazer upload da saída de compilação e teste para usar em implantações, para depurar falhas e testes com falhas e visualizar a cobertura do conjunto de teste. + +Você pode usar a ação `upload-artifact` para fazer o upload dos artefatos. Ao fazer o upload de um artefato, você pode especificar um arquivo ou diretório único, ou vários arquivos ou diretórios. Você também pode excluir certos arquivos ou diretórios e usar padrões coringa. Recomendamos que você forneça um nome para um artefato, mas se nenhum nome for fornecido, `artefato` será usado como nome-padrão. Para mais informações sobre sintaxe, consulte a ação {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) {% else %} `actions/upload-artifact` em {% data variables.product.product_location %}{% endif %}. + +### Exemplo + +Por exemplo, o seu repositório ou um aplicativo web pode conter arquivos SASS e TypeScript que você deve converter para CSS e JavaScript. Pressupondo que sua configuração de compilação envia os arquivos compilados para o diretório `dist`, você implementaria os arquivos no diretório `dist` no seu servidor de aplicativo web, se todos os testes foram concluídos com sucesso. + +``` +|-- hello-world (repository) +| └── dist +| └── tests +| └── src +| └── sass/app.scss +| └── app.ts +| └── output +| └── test +| +``` + +Esse exemplo mostra como criar um fluxo de trabalho para um projeto Node.js que builds (compila) o código no diretório `src` e executa os testes no diretório `tests`. Você pode partir do princípio que executar `npm test` produz um relatório de cobertura de código denominado `code-coverage.html`, armazenado no diretório `output/test/`. + +O fluxo de trabalho faz o upload dos artefatos de produção no diretório `dist`, mas exclui todos os arquivos de markdown. Ele também faz o upload do relatório de `code-coverage.html` como outro artefato. + +```yaml{:copy} +name: Node CI + +on: [push] + +jobs: + build_and_test: + runs-on: ubuntu-latest + steps: + - name: Checkout repository + uses: actions/checkout@v2 + - name: npm install, build, and test + run: | + npm install + npm run build --if-present + npm test + - name: Archive production artifacts + uses: actions/upload-artifact@v2 + with: + name: dist-without-markdown + path: | + dist + !dist/**/*.md + - name: Archive code coverage results + uses: actions/upload-artifact@v2 + with: + name: code-coverage-report + path: output/test/code-coverage.html +``` + +## Configurar um período de retenção do artefato personalizado + +Você pode definir um período de retenção personalizado para artefatos individuais criados por um fluxo de trabalho. Ao usar um fluxo de trabalho para criar um novo artefato, você pode usar `retention-days` com a ação `upload-artifact`. Este exemplo demonstra como definir um período de retenção personalizado de 5 dias para o artefato denominado `my-artifact`: + +```yaml{:copy} + - name: 'Upload Artifact' + uses: actions/upload-artifact@v2 + with: + name: my-artifact + path: my_file.txt + retention-days: 5 +``` + +O valor `retention-days` não pode exceder o limite de retenção definido pelo repositório, organização ou empresa. + +## Fazer o download ou excluir artefatos + +Durante a execução de um fluxo de trabalho, você pode usar a ação [`download-artifact`](https://github.com/actions/download-artifact)para fazer o download de artefatos previamente carregados na mesma execução de fluxo de trabalho. + +Após a conclusão da execução de um fluxo de trabalho, você pode fazer o download ou excluir artefatos em {% data variables.product.prodname_dotcom %} ou usar a API REST. For more information, see "[Downloading workflow artifacts](/actions/managing-workflow-runs/downloading-workflow-artifacts)," "[Removing workflow artifacts](/actions/managing-workflow-runs/removing-workflow-artifacts)," and the "[Artifacts REST API](/rest/reference/actions#artifacts)." + +### Fazer o download dos artefatos durante a execução de um fluxo de trabalho + +A ação [`actions/download-artefact`](https://github.com/actions/download-artifact) pode ser usada para fazer o download de artefatos previamente carregados durante a execução de um fluxo de trabalho. + +{% note %} + +**Observação:** Você só pode baixar artefatos em um fluxo de trabalho que foram carregados durante a mesma execução do fluxo de trabalho. + +{% endnote %} + +Especifique o nome de um artefato para fazer o download de um artefato individual. Se você fez o upload de um artefato sem especificar um nome, o nome-padrão será `artefato`. + +```yaml +- name: Download a single artifact + uses: actions/download-artifact@v2 + with: + name: my-artifact +``` + +Você também pode baixar todos os artefatos em uma execução de fluxo de trabalho sem especificar um nome. Isso pode ser útil se você estiver trabalhando com muitos artefatos. + +```yaml +- name: Download all workflow run artifacts + uses: actions/download-artifact@v2 +``` + +Se você fizer o download de todos os artefatos da execução de um fluxo de trabalho, será criado um diretório para cada artefato usando seu nome. + +For more information on syntax, see the {% ifversion fpt or ghec %}[actions/download-artifact](https://github.com/actions/download-artifact) action{% else %} `actions/download-artifact` action on {% data variables.product.product_location %}{% endif %}. + +## Transmitir dados entre trabalhos em um fluxo + +Você pode usar as ações `upload-artifact` e `download-artifact` para compartilhar os dados entre os trabalhos em um fluxo de trabalho. Este exemplo de fluxo de trabalho ilustra como transmitir dados entre trabalhos em um mesmo fluxo. Para mais informações veja o {% ifversion fpt or ghec %}[actions/upload-artifact](https://github.com/actions/upload-artifact) e [download-artefact](https://github.com/actions/download-artifact) ações{% else %} `actions/upload-artefact` e `download-artefact` ações em {% data variables.product.product_location %}{% endif %}. + +Os trabalhos que são dependentes de artefatos de um trabalho anterior devem aguardar a finalização do trabalho dependente. Esse fluxo de trabalho usa a palavra-chave `needs` para garantir que `job_1`, `job_2` e `job_3` sejam executados sequencialmente. Por exemplo, `job_2` requer `job_1` usando a sintaxe `needs: job_1`. + +O Job 1 (Trabalho 1) executa estas etapas: +- Realiza um cálculo de correspondência e salva o resultado em um arquivo de texto denominado `math-homework.txt`. +- Usa a ação `upload-artifact` para fazer upload do arquivo `math-homework.txt` com o nome do artefato `homework`. + +O Job 2 (Trabalho 2) usa o resultado do trabalho anterior: +- Baixa o artefato `homework` carregado no trabalho anterior. Por padrão, a ação `download-artifact` baixa artefatos no diretório da área de trabalho no qual a etapa está sendo executada. Você pode usar o parâmetro da entrada do `caminho` para especificar um diretório diferente para o download. +- Lê o valor no arquivo `math-homework.txt`, efetua um cálculo matemático e salva o resultado em `math-homework.txt` novamente, sobrescrevendo o seu conteúdo. +- Faz upload do arquivo `math-homework.txt`. Este upload sobrescreve o artefato carregado anteriormente porque compartilham o mesmo nome. + +O Job 3 (Trabalho 3) mostra o resultado carregado no trabalho anterior: +- Baixa o artefato `homework`. +- Imprime o resultado da operação matemática no log. + +A operação matemática completa executada nesse fluxo de trabalho é `(3 + 7) x 9 = 90`. + +```yaml{:copy} +name: Share data between jobs + +on: [push] + +jobs: + job_1: + name: Add 3 and 7 + runs-on: ubuntu-latest + steps: + - shell: bash + run: | + expr 3 + 7 > math-homework.txt + - name: Upload math result for job 1 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt + + job_2: + name: Multiply by 9 + needs: job_1 + runs-on: windows-latest + steps: + - name: Download math result for job 1 + uses: actions/download-artifact@v2 + with: + name: homework + - shell: bash + run: | + value=`cat math-homework.txt` + expr $value \* 9 > math-homework.txt + - name: Upload math result for job 2 + uses: actions/upload-artifact@v2 + with: + name: homework + path: math-homework.txt + + job_3: + name: Display results + needs: job_2 + runs-on: macOS-latest + steps: + - name: Download math result for job 2 + uses: actions/download-artifact@v2 + with: + name: homework + - name: Print the final result + shell: bash + run: | + value=`cat math-homework.txt` + echo The result is $value +``` + +A execução do fluxo de trabalho arquivará quaisquer artefatos gerados por ele. Para obter mais informações sobre o download de artefatos arquivados, consulte "[Fazer download dos artefatos de fluxo de trabalho](/actions/managing-workflow-runs/downloading-workflow-artifacts)". +{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% else %} +![Fluxo de trabalho que transmite dados entre trabalhos para executar cálculos matemáticos](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow.png) +{% endif %} + +{% ifversion fpt or ghec %} + +## Leia mais + +- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)". + +{% endif %} diff --git a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md index d25ca23a33..e367075ff4 100644 --- a/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md +++ b/translations/pt-BR/content/actions/using-workflows/triggering-a-workflow.md @@ -130,6 +130,8 @@ Use a chave `on` para especificar quais eventos acionam o seu fluxo de trabalho. {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## Definindo entradas, saídas e segredos para fluxos de trabalho reutilizáveis +{% data reusables.actions.reusable-workflows-ghes-beta %} + É possível definir entradas e segredos que um fluxo de trabalho reutilizável deve receber de um fluxo de trabalho chamado. Também é possível especificar saídas que um fluxo de trabalho reutilizável disponibilizará para um fluxo de trabalho chamado. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/using-workflows/reusing-workflows)". {% endif %} diff --git a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md b/translations/pt-BR/content/actions/using-workflows/using-github-cli-in-workflows.md similarity index 98% rename from translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md rename to translations/pt-BR/content/actions/using-workflows/using-github-cli-in-workflows.md index 8aea18af30..87156349b3 100644 --- a/translations/pt-BR/content/actions/advanced-guides/using-github-cli-in-workflows.md +++ b/translations/pt-BR/content/actions/using-workflows/using-github-cli-in-workflows.md @@ -4,6 +4,7 @@ shortTitle: CLI do GitHub em fluxos de trabalho intro: 'Você pode fazero script com {% data variables.product.prodname_cli %} em fluxos de trabalho {% data variables.product.prodname_actions %}.' redirect_from: - /actions/guides/using-github-cli-in-workflows + - /actions/advanced-guides/using-github-cli-in-workflows versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md index a8337f8e28..1613202f79 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -56,6 +56,8 @@ Nome do fluxo de trabalho. O {% data variables.product.prodname_dotcom %} exibe {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `on.workflow_call` +{% data reusables.actions.reusable-workflows-ghes-beta %} + Use `on.workflow_call` para definir as entradas e saídas para um fluxo de trabalho reutilizável. Você também pode mapear os segredos disponíveis para o fluxo de trabalho chamado. Para obter mais informações sobre fluxos de trabalho reutilizáveis, consulte "[Reutilizando fluxos de trabalho](/actions/using-workflows/reusing-workflows)". ### `on.workflow_call.inputs` @@ -881,6 +883,8 @@ Opções adicionais de recursos do contêiner Docker. Para obter uma lista de op {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} ## `jobs..uses` +{% data reusables.actions.reusable-workflows-ghes-beta %} + O local e a versão de um arquivo de fluxo de trabalho reutilizável para ser executado como job. {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %}Use uma das seguintes sintaxes:{% endif %} {% data reusables.actions.reusable-workflow-calling-syntax %} diff --git a/translations/pt-BR/content/admin/code-security/index.md b/translations/pt-BR/content/admin/code-security/index.md new file mode 100644 index 0000000000..d1fdeb0bf5 --- /dev/null +++ b/translations/pt-BR/content/admin/code-security/index.md @@ -0,0 +1,14 @@ +--- +title: Managing code security for your enterprise +shortTitle: Manage code security +intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.' +versions: + ghes: '*' + ghec: '*' +topics: + - Enterprise +children: + - /managing-github-advanced-security-for-your-enterprise + - /managing-supply-chain-security-for-your-enterprise +--- + diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md similarity index 92% rename from translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md index aa5ce5b397..2cb323be44 100644 --- a/translations/pt-BR/content/admin/advanced-security/configuring-code-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md @@ -7,6 +7,7 @@ miniTocMaxHeadingLevel: 3 redirect_from: - /enterprise/admin/configuration/configuring-code-scanning-for-your-appliance - /admin/configuration/configuring-code-scanning-for-your-appliance + - /admin/advanced-security/configuring-code-scanning-for-your-appliance versions: ghes: '*' type: how_to @@ -65,8 +66,8 @@ Se você configurar a ferramenta de sincronização de ação de {% data variabl ### Configurar {% data variables.product.prodname_github_connect %} para sincronizar {% data variables.product.prodname_actions %} -1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)". -2. Você também precisa habilitar o {% data variables.product.prodname_actions %} para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". +1. Se você deseja fazer o download dos fluxos de trabalho de ação sob demanda a partir de {% data variables.product.prodname_dotcom_the_website %}, você deverá habilitar o {% data variables.product.prodname_github_connect %}. For more information, see "[Enabling {% data variables.product.prodname_github_connect %}](/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud#enabling-github-connect)." +2. You'll also need to enable {% data variables.product.prodname_actions %} for {% data variables.product.product_location %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server)". 3. A próxima etapa é configurar o acesso a ações no {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% data variables.product.prodname_github_connect %}](/enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect)". 4. Adicione um executor auto-hospedado ao seu repositório, organização ou conta corporativa. Para obter mais informações, consulte "[Adicionando executores auto-hospedados](/actions/hosting-your-own-runners/adding-self-hosted-runners)". diff --git a/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md similarity index 97% rename from translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md index ce92212efc..d45ae746f6 100644 --- a/translations/pt-BR/content/admin/advanced-security/configuring-secret-scanning-for-your-appliance.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md @@ -6,6 +6,7 @@ product: '{% data reusables.gated-features.secret-scanning %}' miniTocMaxHeadingLevel: 3 redirect_from: - /admin/configuration/configuring-secret-scanning-for-your-appliance + - /admin/advanced-security/configuring-secret-scanning-for-your-appliance versions: ghes: '*' type: how_to @@ -50,7 +51,7 @@ O conjunto de instruções das SSSE3 é necessário porque o {% data variables.p Se isso não retornar `0`, SSSE3 não está habilitado no seu VM/KVM. Você precisa consultar a documentação do hardware/hipervisor sobre como habilitar o sinalizador ou disponibilizá-lo para VMs convidados. -## Habilitar {% data variables.product.prodname_secret_scanning %} +## Habilitar o {% data variables.product.prodname_secret_scanning %} {% data reusables.enterprise_management_console.enable-disable-security-features %} diff --git a/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md similarity index 99% rename from translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md index 1d1240e548..a5e5a5c0f2 100644 --- a/translations/pt-BR/content/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md @@ -2,6 +2,8 @@ title: Implantando o GitHub Advanced Security na sua empresa intro: 'Aprenda a planejar, preparar e implementar uma abordagem em fases para implantar {% data variables.product.prodname_GH_advanced_security %} (GHAS) na sua empresa.' product: '{% data reusables.gated-features.advanced-security %}' +redirect_from: + - /admin/advanced-security/deploying-github-advanced-security-in-your-enterprise miniTocMaxHeadingLevel: 3 versions: ghes: '*' diff --git a/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md similarity index 93% rename from translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md index 6982fa3b9a..50239a4d91 100644 --- a/translations/pt-BR/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md @@ -3,6 +3,8 @@ title: Habilitar o GitHub Advanced Security para a sua empresa shortTitle: Habilitar o GitHub Advanced Security intro: 'Você pode configurar {% data variables.product.product_name %} para incluir {% data variables.product.prodname_GH_advanced_security %}. Isso fornece funcionalidades extras que ajudam os usuários a encontrar e corrigir problemas de segurança no seu código.' product: '{% data reusables.gated-features.ghas %}' +redirect_from: + - /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise versions: ghes: '*' type: how_to @@ -21,7 +23,7 @@ topics: {% ifversion ghes > 3.0 %} Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, os administradores de repositórios em todas as organizações poderão habilitar as funcionalidades, a menos que você configure uma política para restringir o acesso. Para obter mais informações, consulte "[Aplicar políticas para {% data variables.product.prodname_advanced_security %} na sua empresa](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)". {% else %} -Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, os administradores de repositórios em todas as organizações podem habilitar as funcionalidades. {% ifversion ghes = 3.0 %}Para obter mais informações, consulte "[Gerenciar as configurações de segurança e análise de sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} +Ao habilitar {% data variables.product.prodname_GH_advanced_security %} para a sua empresa, os administradores de repositórios em todas as organizações podem habilitar as funcionalidades. {% ifversion ghes = 3.0 %}Para obter mais informações, consulte "[Gerenciar as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" e "[Gerenciar as configurações de segurança e análise do seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).{% endif %} {% endif %} {% ifversion ghes %} @@ -54,7 +56,7 @@ Para obter orientação sobre uma implantação em fases da segurança avançada - {% data variables.product.prodname_code_scanning_capc %}, consulte "[Configurando {% data variables.product.prodname_code_scanning %} para seu dispositivo](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)." - {% data variables.product.prodname_secret_scanning_caps %}, consulte "[Configurando {% data variables.product.prodname_secret_scanning %} para seu dispositivo](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %} - - {% data variables.product.prodname_dependabot %}, consulte "[Habilitando o gráfico de dependência e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." + - {% data variables.product.prodname_dependabot %}, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." ## Habilitar e desabilitar funcionalidades de {% data variables.product.prodname_GH_advanced_security %} @@ -88,7 +90,7 @@ Por exemplo, você pode habilitar qualquer recurso de {% data variables.product. ```shell ghe-config app.secret-scanning.enabled true ``` - - Para habilitar {% data variables.product.prodname_dependabot %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}. + - To enable the dependency graph, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. {% ifversion ghes > 3.1 %}```shell ghe-config app.dependency-graph.enabled true ``` @@ -107,7 +109,7 @@ Por exemplo, você pode habilitar qualquer recurso de {% data variables.product. ```shell ghe-config app.secret-scanning.enabled false ``` - - Para desabilitar {% data variables.product.prodname_dependabot_alerts %}, digite os comandos a seguir {% ifversion ghes > 3.1 %}{% else %}comandos{% endif %}. + - To disable the dependency graph, enter the following {% ifversion ghes > 3.1 %}command{% else %}commands{% endif %}. {% ifversion ghes > 3.1 %}```shell ghe-config app.dependency-graph.enabled false ``` diff --git a/translations/pt-BR/content/admin/advanced-security/index.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md similarity index 92% rename from translations/pt-BR/content/admin/advanced-security/index.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md index 72ca6b7e6a..971651e978 100644 --- a/translations/pt-BR/content/admin/advanced-security/index.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/index.md @@ -1,11 +1,12 @@ --- title: Gerenciando o GitHub Advanced Security para a sua empresa -shortTitle: Gerenciar o GitHub Advanced Security +shortTitle: Segurança Avançada GitHub intro: 'Você pode configurar {% data variables.product.prodname_advanced_security %} e gerenciar o uso pela sua empresa para atender às necessidades da sua organização.' product: '{% data reusables.gated-features.ghas %}' redirect_from: - /enterprise/admin/configuration/configuring-advanced-security-features - /admin/configuration/configuring-advanced-security-features + - /admin/advanced-security versions: ghes: '*' ghec: '*' diff --git a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md similarity index 99% rename from translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md rename to translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md index dfc4fc3100..9f8db7ed2b 100644 --- a/translations/pt-BR/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md +++ b/translations/pt-BR/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md @@ -2,6 +2,8 @@ title: Visão geral da implantação de Segurança Avançada do GitHub intro: 'Ajude sua empresa a se preparar para adotar {% data variables.product.prodname_GH_advanced_security %} (GHAS) de forma bem-sucedida revisando e entendendo as práticas recomendadas, exemplos de implementação e a nossa abordagem em fases testada pela empresa.' product: '{% data variables.product.prodname_GH_advanced_security %} é um conjunto de funcionalidades de segurança projetado para tornar o código corporativo mais seguro. Está disponível para {% data variables.product.prodname_ghe_server %} 3.0 ou superior, {% data variables.product.prodname_ghe_cloud %} e para repositórios de código aberto. Para saber mais sobre as funcionalidades, incluído em {% data variables.product.prodname_GH_advanced_security %}, consulte "[Sobre o GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."' +redirect_from: + - /admin/advanced-security/overview-of-github-advanced-security-deployment miniTocMaxHeadingLevel: 3 versions: ghes: '*' diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md new file mode 100644 index 0000000000..1329a5086d --- /dev/null +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md @@ -0,0 +1,20 @@ +--- +title: About supply chain security for your enterprise +intro: You can enable features that help your developers understand and update the dependencies their code relies on. +shortTitle: About supply chain security +permissions: '' +versions: + ghes: '*' + ghae: issue-4864 +type: how_to +topics: + - Enterprise + - Security + - Dependency graph +--- + +You can allow users to identify their projects' dependencies by enabling the dependency graph for {% data variables.product.product_location %}. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)." + +You can also allow users on {% data variables.product.product_location %} to find and fix vulnerabilities in their code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.product.product_location %} and manually sync the data. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)." diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md new file mode 100644 index 0000000000..c066a910db --- /dev/null +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md @@ -0,0 +1,59 @@ +--- +title: Enabling the dependency graph for your enterprise +intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. +shortTitle: Enable dependency graph +permissions: Site administrators can enable the dependency graph. +versions: + ghes: '*' +type: how_to +topics: + - Enterprise + - Security + - Dependency graph +--- + +## Sobre o gráfico de dependências + +{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" + +After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect vulnerable dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +{% ifversion ghes > 3.1 %} +Você pode habilitar o gráfico de dependências por meio do {% data variables.enterprise.management_console %} ou do shell administrativo. We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.product.product_location %} uses clustering. + +## Habilitando o gráfico de dependências por meio do {% data variables.enterprise.management_console %} + +If your {% data variables.product.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)." + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Em "Segurança", clique em **Gráfico de dependência**. ![Caixa de seleção para habilitar ou desabilitar o gráfico de dependências](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) +{% data reusables.enterprise_management_console.save-settings %} +1. Clique **Visit your instance** (Visite sua instância). + +## Habilitando o gráfico de dependências por meio do shell administrativo + +{% endif %}{% ifversion ghes < 3.2 %} +## Habilitar o gráfico de dependências +{% endif %} +{% data reusables.enterprise_site_admin_settings.sign-in %} +1. No shell administrativo, habilite o gráfico de dependências em {% data variables.product.product_location %}: + {% ifversion ghes > 3.1 %}```shell + ghe-config app.dependency-graph.enabled true + ``` + {% else %}```shell + ghe-config app.github.dependency-graph-enabled true + ghe-config app.github.vulnerability-alerting-and-settings-enabled true + ```{% endif %} + {% note %} + + **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." + + {% endnote %} +2. Aplique a configuração. + ```shell + $ ghe-config-apply + ``` +3. Volte para o {% data variables.product.prodname_ghe_server %}. diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md new file mode 100644 index 0000000000..b66d5c6548 --- /dev/null +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/index.md @@ -0,0 +1,15 @@ +--- +title: Managing supply chain security for your enterprise +shortTitle: Segurança da cadeia de suprimento +intro: 'You can visualize, maintain, and secure the dependencies in your developers'' software supply chain.' +versions: + ghes: '*' + ghae: issue-4864 +topics: + - Enterprise +children: + - /about-supply-chain-security-for-your-enterprise + - /enabling-the-dependency-graph-for-your-enterprise + - /viewing-the-vulnerability-data-for-your-enterprise +--- + diff --git a/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md new file mode 100644 index 0000000000..f5e67a039f --- /dev/null +++ b/translations/pt-BR/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md @@ -0,0 +1,25 @@ +--- +title: Viewing the vulnerability data for your enterprise +intro: 'You can view vulnerability data from the {% data variables.product.prodname_advisory_database %} on {% data variables.product.product_location %}.' +shortTitle: View vulnerability data +permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.' +versions: + ghes: '*' + ghae: issue-4864 +type: how_to +topics: + - Enterprise + - Security + - Dependency graph +--- + +If {% data variables.product.prodname_dependabot_alerts %} are enabled for your enterprise, you can view all vulnerabilities that were downloaded to {% data variables.product.product_location %} from the {% data variables.product.prodname_advisory_database %}. + +You can manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list. + +Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." + +{% data reusables.enterprise_site_admin_settings.access-settings %} +2. Na barra lateral esquerda, clique em **Vulnerabilities** (Vulnerabilidades). ![Guia Vulnerabilities (Vulnerabilidades) na barra lateral de administração do site](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) +3. Para sincronizar os dados de vulnerabilidade, clique em **Sync Vulnerabilities now** (Sincronizar vulnerabilidades agora). ![Botão Sync Vulnerabilities now (Sincronizar vulnerabilidades agora)](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) + diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md index 586c11c770..373eefd092 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -29,7 +29,7 @@ Após configurar a conexão entre {% data variables.product.product_location %} | Funcionalidade | Descrição | Mais informações | | ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |{% ifversion ghes %} | Sincronização automática da licença do usuário | Gerencie o uso da licença entre as suas implantações de {% data variables.product.prodname_enterprise %} sincronizando automaticamente as licenças de usuários de {% data variables.product.product_location %} para {% data variables.product.prodname_ghe_cloud %}. | "[Habilitando a sincronização automática de licença de usuário para sua empresa](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Permite aos usuários encontrar e corrigir vulnerabilidades nas dependências do código. | "[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)"{% endif %} +| {% data variables.product.prodname_dependabot %} | Permite aos usuários encontrar e corrigir vulnerabilidades nas dependências do código. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} | Ações de {% data variables.product.prodname_dotcom_the_website %} | Permitir que os usuários usem ações de {% data variables.product.prodname_dotcom_the_website %} em arquivos de fluxo de trabalho. | "[Habilitando o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %} usando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)" | | Pesquisa unificada | Permitir que os usuários incluam repositórios em {% data variables.product.prodname_dotcom_the_website %} nos seus resultados de pesquisa ao pesquisar em {% data variables.product.product_location %}. | "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | | Contribuições unificadas | Permitir que os usuários incluam o número de contribuições anonimizadas pelo trabalho deles em {% data variables.product.product_location %} nos seus gráficos de contribuição em {% data variables.product.prodname_dotcom_the_website %}. | "[Habilitando {% data variables.product.prodname_unified_contributions %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | @@ -52,20 +52,20 @@ Ao habilitar {% data variables.product.prodname_github_connect %} ou funcionalid {% note %} -**Observação:** Nenhum repositório, problema ou pull request foi transmitido por {% data variables.product.prodname_github_connect %}. +**Note:** No repositories, issues, or pull requests are ever transmitted from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} by {% data variables.product.prodname_github_connect %}. {% endnote %} Os dados adicionais são transmitidos se você habilitar as funcionalidades individuais de {% data variables.product.prodname_github_connect %}. -| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | -| ------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name%} -{% endif %} -| Ações de {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Pesquisa unificada | Termos de pesquisa, resultados de pesquisa | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Contribuições unificadas | Contagens de contribuição | De {% data variables.product.product_name %} paraa {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} +| Funcionalidade | Dados | Para onde os dados são transmitidos? | Onde os dados são usados? | +| ------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| Sincronização automática da licença do usuário | O ID de usuário de cada {% data variables.product.product_name %} e endereço de e-mail | De {% data variables.product.product_name %} para {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| {% data variables.product.prodname_dependabot_alerts %} | Alertas de vulnerabilidade | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} +| {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} +| Ações de {% data variables.product.prodname_dotcom_the_website %} | Nome da ação, ação (arquivo YAML de {% data variables.product.prodname_marketplace %}) | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} +| Pesquisa unificada | Termos de pesquisa, resultados de pesquisa | De {% data variables.product.prodname_dotcom_the_website %} para {% data variables.product.product_name %}

De {% data variables.product.product_name %} para {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} +| Contribuições unificadas | Contagens de contribuição | De {% data variables.product.product_name %} paraa {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} ## Leia mais diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md index 8415737de6..6a34b80d9d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md @@ -7,7 +7,7 @@ redirect_from: - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud -permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.' +permissions: Enterprise owners can enable automatic user license synchronization. versions: ghes: '*' type: how_to diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md new file mode 100644 index 0000000000..4a08c6b632 --- /dev/null +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -0,0 +1,126 @@ +--- +title: Enabling Dependabot for your enterprise +intro: 'You can allow users of {% data variables.product.product_location %} to find and fix vulnerabilities in code dependencies by enabling {% data variables.product.prodname_dependabot_alerts %}{% ifversion ghes > 3.2 %} and {% data variables.product.prodname_dependabot_updates %}{% endif %}.' +miniTocMaxHeadingLevel: 3 +shortTitle: Dependabot +redirect_from: + - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server + - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account + - /admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise +permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.' +versions: + ghes: '*' + ghae: issue-4864 +type: how_to +topics: + - Enterprise + - Security + - Dependency graph + - Dependabot +--- + +## About {% data variables.product.prodname_dependabot %} for {% data variables.product.product_name %} + +{% data variables.product.prodname_dependabot %} helps users of {% data variables.product.product_location %} find and fix vulnerabilities in their dependencies.{% ifversion ghes > 3.2 %} You can enable {% data variables.product.prodname_dependabot_alerts %} to notify users about vulnerable dependencies and {% data variables.product.prodname_dependabot_updates %} to fix the vulnerabilities and keep dependencies updated to the latest version. + +### Sobre o {% data variables.product.prodname_dependabot_alerts %} +{% endif %} + +{% data reusables.dependabot.dependabot-alerts-beta %} + +With {% data variables.product.prodname_dependabot_alerts %}, {% data variables.product.prodname_dotcom %} identifies vulnerable dependencies in repositories and creates alerts on {% data variables.product.product_location %}, using data from the {% data variables.product.prodname_advisory_database %} and the dependency graph service. + +{% data reusables.repositories.tracks-vulnerabilities %} + +After you enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. Apenas as consultorias revisadas por {% data variables.product.company_short %} estão sincronizados. {% data reusables.security-advisory.link-browsing-advisory-db %} + +Também é possível sincronizar os dados de vulnerabilidade manualmente a qualquer momento. For more information, see "[Viewing the vulnerability data for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise)." + +{% note %} + +**Note:** When you enable enable {% data variables.product.prodname_dependabot_alerts %}, no code or information about code from {% data variables.product.product_location %} is uploaded to {% data variables.product.prodname_dotcom_the_website %}. + +{% endnote %} + +When {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in {% data variables.product.product_location %} that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. Você pode escolher se quer ou não notificar os usuários automaticamente sobre o novo {% data variables.product.prodname_dependabot_alerts %}. + +Para repositórios com {% data variables.product.prodname_dependabot_alerts %} habilitado, a digitalização é acionada em qualquer push para o branch padrão que contém um arquivo de manifesto ou arquivo de bloqueio. Additionally, when a new vulnerability record is added to {% data variables.product.product_location %}, {% data variables.product.product_name %} scans all existing repositories on {% data variables.product.product_location %} and generates alerts for any repository that is vulnerable. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" + +{% ifversion ghes > 3.2 %} +### Sobre o {% data variables.product.prodname_dependabot_updates %} + +{% data reusables.dependabot.beta-security-and-version-updates %} + +After you enable {% data variables.product.prodname_dependabot_alerts %}, you can choose to enable {% data variables.product.prodname_dependabot_updates %}. When {% data variables.product.prodname_dependabot_updates %} are enabled for {% data variables.product.product_location %}, users can configure repositories so that their dependencies are updated and kept secure automatically. + +{% note %} + +**Note:** {% data variables.product.prodname_dependabot_updates %} on {% data variables.product.product_name %} requires {% data variables.product.prodname_actions %} with self-hosted runners. + +{% endnote %} + +With {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} automatically creates pull requests to update dependencies in two ways. + +- **{% data variables.product.prodname_dependabot_version_updates %}**: Os usuários adicionam um arquivo de configuração de {% data variables.product.prodname_dependabot %} ao repositório para habilitar {% data variables.product.prodname_dependabot %} e criar pull requests quando uma nova versão de uma dependência monitorada for lançada. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". +- **{% data variables.product.prodname_dependabot_security_updates %}**: Os usuários alternam uma configuração de repositório para habilitar {% data variables.product.prodname_dependabot %} para criar pull requests quando {% data variables.product.prodname_dotcom %} detecta uma vulnerabilidade em uma das dependências do gráfico de dependências para o repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" e[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)". +{% endif %} + +## Habilitar o {% data variables.product.prodname_dependabot_alerts %} + +Before you can enable {% data variables.product.prodname_dependabot_alerts %}: +- Você deve habilitar {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."{% ifversion ghes %} +- Você deve habilitar o gráfico de dependências. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."{% endif %} + +{% data reusables.enterprise-accounts.access-enterprise %} +{%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %} +{% data reusables.enterprise-accounts.github-connect-tab %} +{%- if dependabot-updates-github-connect %} +1. Under "{% data variables.product.prodname_dependabot %}", to the right of "Users can receive vulnerability alerts for open source code dependencies", select the dropdown menu and click **Enabled without notifications**. Opcionalmente, para habilitar alertas com notificações, clique em **Habilitado com as notificações**. + + ![Screenshot of the dropdown menu to enable scanning repositories for vulnerabilities](/assets/images/enterprise/site-admin-settings/dependabot-alerts-dropdown.png) + +{%- else %} +1. Em "Repositórios podem ser digitalizados com relação a vulnerabilidades", selecione o menu suspenso e clique em **Habilitado sem notificações**. Opcionalmente, para habilitar alertas com notificações, clique em **Habilitado com as notificações**. ![Menu suspenso para habilitar a verificação vulnerabilidades nos repositórios](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) +{%- endif %} + {% tip %} + + **Dica**: Recomendamos configurar {% data variables.product.prodname_dependabot_alerts %} sem notificações para os primeiros dias para evitar uma sobrecarga de e-mails. Após alguns dias, você poderá habilitar as notificações para receber {% data variables.product.prodname_dependabot_alerts %}, como de costume. + + {% endtip %} + +{% if dependabot-updates-github-connect %} +## Habilitar o {% data variables.product.prodname_dependabot_updates %} + +After you enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise, you can enable {% data variables.product.prodname_dependabot_updates %}. + +{% ifversion ghes %} +Before you enable {% data variables.product.prodname_dependabot_updates %}, you must configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." + +{% data variables.product.prodname_dependabot_updates %} are not supported on {% data variables.product.product_name %} if your enterprise uses clustering or a high-availability configuration. +{% endif %} + +{% data reusables.enterprise_site_admin_settings.sign-in %} +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.advanced-security-tab %} +1. Under "Security", select **{% data variables.product.prodname_dependabot_security_updates %}**. + + ![Screenshot of the checkbox to enable or disable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/management-console/enable-dependabot-updates.png) + +{% data reusables.enterprise_management_console.save-settings %} +1. Clique **Visit your instance** (Visite sua instância). +1. Configure self-hosted runners to create the pull requests that will update dependencies. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +1. Under "{% data variables.product.prodname_dependabot %}", to the right of "Users can easily upgrade to non-vulnerable open source code dependencies", click **Enable**. + + ![Screenshot of the dropdown menu to enable updating vulnerable dependencies](/assets/images/enterprise/site-admin-settings/dependabot-updates-button.png) + +{% elsif ghes > 3.2 %} +Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. For more information, see "[Managing self-hosted runners for {% data variables.product.prodname_dependabot_updates %} on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates)." +{% endif %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md deleted file mode 100644 index d0ab1f0936..0000000000 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md +++ /dev/null @@ -1,127 +0,0 @@ ---- -title: Habilitando o gráfico de dependências e alertas de dependências para a sua empresa -intro: 'Você pode permitir que os usuários de {% data variables.product.product_location %} encontrem e corrijam vulnerabilidades em dependências de código, habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}.' -miniTocMaxHeadingLevel: 3 -shortTitle: Dependabot -redirect_from: - - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server - - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account -permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.product_location %}.' -versions: - ghes: '*' - ghae: issue-4864 -type: how_to -topics: - - Enterprise - - Security - - Dependency graph - - Dependabot ---- - -## Sobre alertas para dependências vulneráveis no {% data variables.product.product_location %} - -{% data reusables.dependabot.dependabot-alerts-beta %} - -{% data variables.product.prodname_dotcom %} identifica dependências vulneráveis nos repositórios e cria {% data variables.product.prodname_dependabot_alerts %} em {% data variables.product.product_location %}, usando: - -- Dados do {% data variables.product.prodname_advisory_database %} -- O serviço gráfico de dependências - -Para obter mais informações sobre essas funcionalidades, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" e "[Sobre alertas para dependências vulneráveis](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)". - -### Sobre a sincronização de dados de {% data variables.product.prodname_advisory_database %} - -{% data reusables.repositories.tracks-vulnerabilities %} - -Você pode conectar-se {% data variables.product.product_location %} a {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_github_connect %}. Uma vez conectados, os dados de vulnerabilidade são sincronizados de {% data variables.product.prodname_advisory_database %} para sua instância uma vez a cada hora. Também é possível sincronizar os dados de vulnerabilidade manualmente a qualquer momento. Nenhum código ou informações sobre o código da {% data variables.product.product_location %} são carregados para o {% data variables.product.prodname_dotcom_the_website %}. - -Apenas as consultorias revisadas por {% data variables.product.company_short %} estão sincronizados. {% data reusables.security-advisory.link-browsing-advisory-db %} - -### Sobre a digitalização de repositórios com dados sincronizados do {% data variables.product.prodname_advisory_database %} - -Para repositórios com {% data variables.product.prodname_dependabot_alerts %} habilitado, a digitalização é acionada em qualquer push para o branch padrão que contém um arquivo de manifesto ou arquivo de bloqueio. Além disso, quando um novo registro de vulnerabilidade é adicionado à instância, {% data variables.product.prodname_ghe_server %} irá digitalizar todos os repositórios existentes nessa instância e gerará alertas para qualquer repositório que seja vulnerável. Para obter mais informações, consulte "[Detecção de dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". - -### Sobre a geração de {% data variables.product.prodname_dependabot_alerts %} - -Se você habilitar a detecção de vulnerabilidade, quando {% data variables.product.product_location %} recebe informações sobre uma vulnerabilidade, ela irá identificar os repositórios na sua instância que usam a versão afetada da dependência e irá gerar {% data variables.product.prodname_dependabot_alerts %}. Você pode escolher se quer ou não notificar os usuários automaticamente sobre o novo {% data variables.product.prodname_dependabot_alerts %}. - -## Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em {% data variables.product.product_location %} - -### Pré-requisitos - -Para {% data variables.product.product_location %} detectar dependências vulneráveis e gerar {% data variables.product.prodname_dependabot_alerts %}: -- Você deve habilitar {% data variables.product.prodname_github_connect %}. {% ifversion ghae %}Isso também habilita o serviço gráfico de dependência.{% endif %}{% ifversion ghes or ghae %}Para obter mais informações, consulte"[Gerenciando {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)".{% endif %} -{% ifversion ghes %}- Você deve habilitar o serviço do gráfico de dependências.{% endif %} -- Você deve habilitar a digitalização de vulnerabilidade. - -{% ifversion ghes %} -{% ifversion ghes > 3.1 %} -Você pode habilitar o gráfico de dependências por meio do {% data variables.enterprise.management_console %} ou do shell administrativo. Recomendamos que você siga o encaminhamento de {% data variables.enterprise.management_console %} a menos que {% data variables.product.product_location %} use clustering. - -### Habilitando o gráfico de dependências por meio do {% data variables.enterprise.management_console %} -{% data reusables.enterprise_site_admin_settings.sign-in %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -{% data reusables.enterprise_management_console.advanced-security-tab %} -1. Em "Segurança", clique em **Gráfico de dependência**. ![Caixa de seleção para habilitar ou desabilitar o gráfico de dependências](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png) -{% data reusables.enterprise_management_console.save-settings %} -1. Clique **Visit your instance** (Visite sua instância). - -### Habilitando o gráfico de dependências por meio do shell administrativo -{% endif %}{% ifversion ghes < 3.2 %} -### Habilitar o gráfico de dependências -{% endif %} -{% data reusables.enterprise_site_admin_settings.sign-in %} -1. No shell administrativo, habilite o gráfico de dependências em {% data variables.product.product_location %}: - {% ifversion ghes > 3.1 %}```shell - ghe-config app.dependency-graph.enabled true - ``` - {% else %}```shell - ghe-config app.github.dependency-graph-enabled true - ghe-config app.github.vulnerability-alerting-and-settings-enabled true - ```{% endif %} - {% note %} - - **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)." - - {% endnote %} -2. Aplique a configuração. - ```shell - $ ghe-config-apply - ``` -3. Volte para o {% data variables.product.prodname_ghe_server %}. -{% endif %} - -### Habilitar o {% data variables.product.prodname_dependabot_alerts %} - -{% ifversion ghes %} -Antes de habilitar {% data variables.product.prodname_dependabot_alerts %} para sua instância, você deverá habilitar o gráfico de dependências. Para obter mais informações, consulte acima. -{% endif %} - -{% data reusables.enterprise-accounts.access-enterprise %} -{%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %} -{% data reusables.enterprise-accounts.github-connect-tab %} -1. Em "Repositórios podem ser digitalizados com relação a vulnerabilidades", selecione o menu suspenso e clique em **Habilitado sem notificações**. Opcionalmente, para habilitar alertas com notificações, clique em **Habilitado com as notificações**. ![Menu suspenso para habilitar a verificação vulnerabilidades nos repositórios](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png) - - {% tip %} - - **Dica**: Recomendamos configurar {% data variables.product.prodname_dependabot_alerts %} sem notificações para os primeiros dias para evitar uma sobrecarga de e-mails. Após alguns dias, você poderá habilitar as notificações para receber {% data variables.product.prodname_dependabot_alerts %}, como de costume. - - {% endtip %} - -{% ifversion fpt or ghec or ghes > 3.2 %} -Ao habilitar {% data variables.product.prodname_dependabot_alerts %}, você também deve considerar configurar {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot_security_updates %}. Este recurso permite aos desenvolvedores corrigir a vulnerabilidades nas suas dependências. Para obter mais informações, consulte "[Configurando a segurança de {% data variables.product.prodname_dependabot %} e as atualizações de versão na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)". -{% endif %} - -## Exibir dependências vulneráveis no {% data variables.product.product_location %} - -Você pode exibir todas as vulnerabilidades na {% data variables.product.product_location %} e sincronizar manualmente os dados de vulnerabilidade do {% data variables.product.prodname_dotcom_the_website %} para atualizar a lista. - -{% data reusables.enterprise_site_admin_settings.access-settings %} -2. Na barra lateral esquerda, clique em **Vulnerabilities** (Vulnerabilidades). ![Guia Vulnerabilities (Vulnerabilidades) na barra lateral de administração do site](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png) -3. Para sincronizar os dados de vulnerabilidade, clique em **Sync Vulnerabilities now** (Sincronizar vulnerabilidades agora). ![Botão Sync Vulnerabilities now (Sincronizar vulnerabilidades agora)](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png) diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md index a64e96519e..c15efca0e4 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md @@ -11,7 +11,7 @@ redirect_from: - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom -permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' +permissions: 'Enterprise owners can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md index 23ad9f5dee..8bbee4160d 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md @@ -11,7 +11,7 @@ redirect_from: - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom -permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' +permissions: 'Enterprise owners can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.' versions: ghes: '*' ghae: '*' diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md index 1a7db4eacc..d684188940 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/index.md @@ -20,7 +20,7 @@ children: - /about-github-connect - /managing-github-connect - /enabling-automatic-user-license-sync-for-your-enterprise - - /enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise + - /enabling-dependabot-for-your-enterprise - /enabling-unified-search-for-your-enterprise - /enabling-unified-contributions-for-your-enterprise shortTitle: GitHub Connect diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md index 5624b4c487..037459917e 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md @@ -30,14 +30,20 @@ Os servidores de nomes que você especificar devem resolver o nome de host da {% ## Configurar servidores de nomes usando o shell administrativo {% data reusables.enterprise_installation.ssh-into-instance %} + 2. Para editar seus servidores de nomes, insira: + ```shell - $ sudo vim /etc/resolvconf/resolv.conf.d/head + sudo vim /etc/resolvconf/resolv.conf.d/head ``` + +{% data reusables.enterprise_installation.preventing-nameservers-change %} + 3. Adicione quaisquer entradas `nameserver` e salve o arquivo. 4. Depois de verificar suas alterações, salve o arquivo. 5. Para adicionar as suas novas entradas de nameserver para {% data variables.product.product_location %}, execute o seguinte: + ```shell - $ sudo service resolvconf restart - $ sudo service dnsmasq restart + sudo service resolvconf restart + sudo service dnsmasq restart ``` diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md index 0165a717bb..fa6dc0e788 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-clustering/evacuating-a-cluster-node.md @@ -13,55 +13,73 @@ topics: - Enterprise --- -Se houver somente três nós no seu cluster de serviços de dados, não será possível removê-los porque o `ghe-spokes` não tem outro local para fazer cópia. Se houver quatro ou mais nós, o `ghe-spokes` vai retirar todos os repositórios do nó removido. +## About evacuation of cluster nodes -Se você estiver usando um nó offline que tenha qualquer tipo de serviços de dados (como git, páginas ou armazenamento), remova cada nó antes de deixar o nó offline. +In a cluster configuration for {% data variables.product.product_name %}, you can evacuate a node before taking the node offline. Evacuation ensures that the remaining nodes in a service tier contain all of the service's data. For example, when you replace the virtual machine for a node in your cluster, you should first evacuate the node. -1. Encontre o `uuid` do nó com o comando `ghe-config`. +For more information about nodes and service tiers for {% data variables.product.prodname_ghe_server %}, see "[About cluster nodes](/admin/enterprise-management/configuring-clustering/about-cluster-nodes)." - ```shell - $ ghe-config cluster.HOSTNAME.uuid - ``` +{% warning %} -2. Você terá que monitorar o status do seu nó durante a operação de cópia dos dados. O ideal é que o nó não fique offline até a conclusão da operação de cópia. Para monitorar o status do seu nó, execute qualquer um dos comandos a seguir: +**Avisos**: - Para o Git - ``` - ghe-spokes evac-status - ``` - Para o {% data variables.product.prodname_pages %} +- To avoid data loss, {% data variables.product.company_short %} strongly recommends that you evacuate a node before taking the node offline. - ```shell - echo "select count(*) from pages_replicas where host = 'pages-server-UUID'" | ghe-dbconsole -y - ``` +- If you only have three nodes in your data services cluster, you can't evacuate the nodes because `ghe-spokes` doesn't have another place to make a copy. Se houver quatro ou mais nós, o `ghe-spokes` vai retirar todos os repositórios do nó removido. - Para o armazenamento - ``` - ghe-storage evacuation-status - ``` +{% endwarning %} -3. Após a conclusão do processo de cópia, você poderá remover o serviço de armazenamento. Execute qualquer um dos comandos a seguir: +## Remover um nó de cluster - Para o Git +If you plan to take a node offline and the node runs a data service role like `git-server`, `pages-server`, or `storage-server`, evacuate each node before taking the node offline. - ```shell - ghe-spokes server evacuate git-server-UUID \'REASON FOR EVACUATION\' - ``` +{% data reusables.enterprise_clustering.ssh-to-a-node %} +1. To find the UUID of the node to evacuate, run the following command. Replace `HOSTNAME` with the node's hostname. - Para o {% data variables.product.prodname_pages %} + ```shell + $ ghe-config cluster.HOSTNAME.uuid + ``` +1. Monitor the node's status while {% data variables.product.product_name %} copies the data. Don't take the node offline until the copy is complete. To monitor the status of your node, run any of the following commands, replacing `UUID` with the UUID from step 2. - ```shell - ghe-dpages evacuate pages-server-UUID - ``` + - **Git**: - Para o armazenamento, use o nó offline + ```shell + $ ghe-spokes evac-status git-server-UUID + ``` - ```shell - ghe-storage offline storage-server-UUID - ``` + - **{% data variables.product.prodname_pages %}**: - e remova + ```shell + $ echo "select count(*) from pages_replicas where host = 'pages-server-UUID'" | ghe-dbconsole -y + ``` - ```shell - ghe-storage evacuate storage-server-UUID - ``` + - **Storage**: + + ```shell + $ ghe-storage evacuation-status storage-server-UUID + ``` +1. After the copy is complete, you can evacuate the node by running any of the following commands, replacing `UUID` with the UUID from step 2. + + - **Git**: + + ```shell + $ ghe-spokes server evacuate git-server-UUID \'REASON FOR EVACUATION\' + ``` + + - **{% data variables.product.prodname_pages %}**: + + ```shell + $ ghe-dpages evacuate pages-server-UUID + ``` + + - For **storage**, first take the node offline by running the following command. + + ```shell + $ ghe-storage offline storage-server-UUID + ``` + + After the storage node is offline, you can evacuate the node by running the following command. + + ```shell + $ ghe-storage evacuate storage-server-UUID + ``` diff --git a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md index e90307d494..bb1d12c527 100644 --- a/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md @@ -185,3 +185,43 @@ Há três maneiras de resolver este problema: 1. Volte para o {% data variables.product.prodname_ghe_server %}. {% endif %} + +{% ifversion ghes > 3.3 %} + + + +## Troubleshooting bundled actions in {% data variables.product.prodname_actions %} + +If you receive the following error when installing {% data variables.product.prodname_actions %} in {% data variables.product.prodname_ghe_server %}, you can resolve the problem by installing the official bundled actions and starter workflows. + +```shell +A part of the Actions setup had problems and needs an administrator to resolve. +``` + +To install the official bundled actions and starter workflows within a designated organization in {% data variables.product.prodname_ghe_server %}, follow this procedure. + +1. Identify an organization that will store the official bundled actions and starter worflows. You can create a new organization or reuse an existing one. + - To create a new organization, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." + - For assistance with choosing a name for this organization, see "[Reserved Names](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#reserved-names)." + +1. Efetue o login no shell administrativo usando SSH. Para obter mais informações, consulte "[Acessar o shell administrativo (SSH)](/admin/configuration/accessing-the-administrative-shell-ssh)". +1. To designate your organization as the location to store the bundled actions, use the `ghe-config` command, replacing `ORGANIZATION` with the name of your organization. + ```shell + $ ghe-config app.actions.actions-org ORGANIZATION + ``` + e: + ```shell + $ ghe-config app.actions.github-org ORGANIZATION + ``` +1. To add the bundled actions to your organization, unset the SHA. + ```shell + $ ghe-config --unset 'app.actions.actions-repos-sha1sum' + ``` +1. Aplique a configuração. + ```shell + $ ghe-config-apply + ``` + +After you've completed these steps, you can resume configuring {% data variables.product.prodname_actions %} at "[Managing access permissions for GitHub Actions in your enterprise](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#managing-access-permissions-for-github-actions-in-your-enterprise)." + +{% endif %} diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md index 3800e52d05..3e5aa2c3a4 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md @@ -9,7 +9,7 @@ children: - /enabling-github-actions-with-azure-blob-storage - /enabling-github-actions-with-amazon-s3-storage - /enabling-github-actions-with-minio-gateway-for-nas-storage - - /setting-up-dependabot-updates + - /managing-self-hosted-runners-for-dependabot-updates shortTitle: Habilitar GitHub Actions --- diff --git a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md similarity index 50% rename from translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md rename to translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md index 0b2123af75..e4a310ce0c 100644 --- a/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md +++ b/translations/pt-BR/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md @@ -1,6 +1,8 @@ --- -title: Configurando as atualizações de segurança e versão do Dependabot na sua empresa +title: Managing self-hosted runners for Dependabot updates on your enterprise intro: 'Você pode criar executores dedicados para {% data variables.product.product_location %} que {% data variables.product.prodname_dependabot %} usa para criar pull requests a fim de ajudar a proteger e manter as dependências usadas em repositórios da sua empresa.' +redirect_from: + - /admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -10,38 +12,31 @@ topics: - Security - Dependabot - Dependencies -shortTitle: Configurar atualizações do Dependabot +shortTitle: Dependabot updates --- {% data reusables.dependabot.beta-security-and-version-updates %} -{% tip %} +## About self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -**Dica**: Se {% data variables.product.product_location %} usar clustering, você não poderá configurar a segurança de {% data variables.product.prodname_dependabot %} e as atualizações de versão, uma vez que {% data variables.product.prodname_actions %} não é compatível no modo cluster. +You can help users of {% data variables.product.product_location %} to create and maintain secure code by setting up {% data variables.product.prodname_dependabot %} security and version updates. With {% data variables.product.prodname_dependabot_updates %}, developers can configure repositories so that their dependencies are updated and kept secure automatically. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -{% endtip %} +To use {% data variables.product.prodname_dependabot_updates %} on {% data variables.product.product_location %}, you must configure self-hosted runners to create the pull requests that will update dependencies. -## Sobre as atualizações do {% data variables.product.prodname_dependabot %} +## Pré-requisitos -Ao configurar {% data variables.product.prodname_dependabot %} de segurança e atualizações de versão para {% data variables.product.product_location %}, os usuários podem configurar os repositórios para que suas dependências sejam atualizadas e mantidas seguras automaticamente. Este é um passo importante para ajudar os desenvolvedores a criar e manter o código seguro. +{% if dependabot-updates-github-connect %} +Configuring self-hosted runners is only one step in the middle of the process for enabling {% data variables.product.prodname_dependabot_updates %}. There are several steps you must follow before these steps, including configuring {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% else %} +Before you configure self-hosted runners for {% data variables.product.prodname_dependabot_updates %}, you must: -Os usuários podem configurar {% data variables.product.prodname_dependabot %} para criar pull requests e atualizar as suas dependências usando duas funcionalidades. +- Configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %} with self-hosted runners. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +- Enable {% data variables.product.prodname_dependabot_alerts %} for your enterprise. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +{% endif %} -- **{% data variables.product.prodname_dependabot_version_updates %}**: Os usuários adicionam um arquivo de configuração de {% data variables.product.prodname_dependabot %} ao repositório para habilitar {% data variables.product.prodname_dependabot %} e criar pull requests quando uma nova versão de uma dependência monitorada for lançada. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". -- **{% data variables.product.prodname_dependabot_security_updates %}**: Os usuários alternam uma configuração de repositório para habilitar {% data variables.product.prodname_dependabot %} para criar pull requests quando {% data variables.product.prodname_dotcom %} detecta uma vulnerabilidade em uma das dependências do gráfico de dependências para o repositório. Para obter mais informações, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" e[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)". +## Configuring self-hosted runners for {% data variables.product.prodname_dependabot_updates %} -## Pré-requisitos para atualizações de {% data variables.product.prodname_dependabot %} - -Ambos os tipos de atualização de {% data variables.product.prodname_dependabot %} têm os seguintes requisitos. - -- Configure {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." -- Configure um ou mais executores auto-hospedados de {% data variables.product.prodname_actions %} para {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Configurando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}](#setting-up-self-hosted-runners-for-dependabot-updates)" abaixo. - -Além disso, {% data variables.product.prodname_dependabot_security_updates %} depende do gráfico de dependências, dados de vulnerabilidades de {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_dependabot_alerts %}. Essas funcionalidades devem ser habilitadas em {% data variables.product.product_location %}. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." - -## Configurando executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %} - -Quando você tiver configurado {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}, você deverá adicionar executores auto-hospedados para atualizações de {% data variables.product.prodname_dependabot %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +After you configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}, you need to add self-hosted runners for {% data variables.product.prodname_dependabot_updates %}. ### Requisitos do sistema para executores de {% data variables.product.prodname_dependabot %} diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 523e2631e5..7020adcdf8 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -32,7 +32,7 @@ Por padrão, {% data variables.product.prodname_actions %} não está habilitado {% data reusables.actions.migrating-enterprise %} -## Revise as considerações de hardware +## Review hardware requirements {% ifversion ghes = 3.0 %} @@ -46,7 +46,7 @@ Por padrão, {% data variables.product.prodname_actions %} não está habilitado {%- ifversion ghes < 3.2 %} -Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}. +Os recursos da CPU e memória disponíveis para {% data variables.product.product_location %} determinam o rendimento máximo do trabalho para {% data variables.product.prodname_actions %}. {% data reusables.actions.minimum-hardware %} O teste interno em {% data variables.product.company_short %} demonstrou o rendimento máximo a seguir para instâncias de {% data variables.product.prodname_ghe_server %} com um intervalo de configurações da CPU e memória. Você pode ver diferentes tipos de transferência, dependendo dos níveis gerais de atividade na sua instância. @@ -54,7 +54,7 @@ O teste interno em {% data variables.product.company_short %} demonstrou o rendi {%- ifversion ghes > 3.1 %} -Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho. +Os recursos de CPU e memória disponíveis para {% data variables.product.product_location %} determinam o número de trabalhos que podem ser executados simultaneamente sem perda de desempenho. {% data reusables.actions.minimum-hardware %} O pico de trabalhos simultâneos rodando sem perda de desempenho depende de fatores como duração do trabalho, uso de artefatos, número de repositórios em execução de ações, e quanto outro trabalho sua instância está fazendo não relacionado a ações. Os testes internos no GitHub demonstraram os objetivos de desempenho a seguir para o GitHub Enterprise Server em uma série de configurações de CPU e memória: diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 0d82557bc7..8df47315f7 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -71,6 +71,7 @@ Pense em como sua empresa pode usar funcionalidades de {% data variables.product {% data reusables.actions.internal-actions-summary %} {% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %} +{% data reusables.actions.reusable-workflows-ghes-beta %} Com fluxos de trabalho reutilizáveis, a sua equipe pode chamar um fluxo de trabalho a partir de outro fluxo de trabalho, evitando duplicação exata. Os fluxos de trabalho reutilizáveis promovem práticas recomendadas, ajudando a sua equipe a usar os fluxos de trabalho bem desenhados e que já foram testados. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". {% endif %} diff --git a/translations/pt-BR/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md b/translations/pt-BR/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md index 6a7c107d12..f2ec5f8fc2 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml.md @@ -7,7 +7,7 @@ redirect_from: - /enterprise/admin/authentication/using-saml - /admin/authentication/using-saml - /enterprise/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance/using-saml -intro: 'O SAML é um padrão de autenticação e autorização baseado em XML. O {% data variables.product.prodname_ghe_server %} pode agir como provedor de serviços (SP, Service Provider) com seu provedor de identidade (IdP, Identity Provider) SAML interno.' +intro: 'You can configure SAML single sign-on (SSO) for {% data variables.product.product_name %}, which allows users to authenticate through a SAML identity provider (IdP) to access your instance.' versions: ghes: '*' type: how_to @@ -19,12 +19,24 @@ topics: - SSO --- +## About SAML for {% data variables.product.product_name %} + +SAML SSO allows people to authenticate and access {% data variables.product.product_location %} through an external system for identity management. + +O SAML é um padrão de autenticação e autorização baseado em XML. When you configure SAML for {% data variables.product.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. + {% data reusables.enterprise_user_management.built-in-authentication %} ## Serviços SAML compatíveis {% data reusables.saml.saml-supported-idps %} +{% ifversion ghes > 3.3 %} + +If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. + +{% endif %} + {% data reusables.saml.saml-single-logout-not-supported %} ## Considerações de nome de usuário no SAML @@ -42,7 +54,7 @@ O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam prese {% note %} -**Observação**: Se o `NameID` para um usuário for alterado no IdP, o usuário verá uma mensagem de erro ao tentar entrar na sua instância do {% data variables.product.prodname_ghe_server %}. {% ifversion ghes %}Para restaurar o acesso do usuário, você precisa atualizar o mapeamento do `NameID` da conta do usuário. Para obter mais informações, consulte "[Atualizar o `NameIDo`](#updating-a-users-saml-nameid) do SAML.{% else %} Para obter mais informações, consulte "[Erro: 'Outro usuário já possui a conta'](#error-another-user-already-owns-the-account)."{% endif %} +**Observação**: Se o `NameID` para um usuário for alterado no IdP, o usuário verá uma mensagem de erro ao tentar entrar na sua instância do {% data variables.product.prodname_ghe_server %}. {% ifversion ghes %}To restore the user's access, you'll need to update the user account's `NameID` mapping. Para obter mais informações, consulte "[Atualizar o `NameIDo`](#updating-a-users-saml-nameid) do SAML.{% else %} Para obter mais informações, consulte "[Erro: 'Outro usuário já possui a conta'](#error-another-user-already-owns-the-account)."{% endif %} {% endnote %} @@ -55,13 +67,13 @@ O elemento `NameID` é obrigatório, mesmo que os outros atributos estejam prese ## Metadados SAML -Os metadados do seu provedor de serviço da instância de {% data variables.product.prodname_ghe_server %} estão disponíveis em `http(s)://[hostname]/saml/metadata`. +The service provider metadata for {% data variables.product.product_location %} is available at `http(s)://[hostname]/saml/metadata`. Para configurar seu provedor de identidade manualmente, a URL do serviço de consumidor de declaração (ACS, Assertion Consumer Service) é `http(s)://[hostname]/saml/consume` e usa a associação `urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST`. ## Atributos SAML -Os atributos a seguir estão disponíveis. Você pode alterar seus nomes no [console de gerenciamento](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), exceto o atributo `administrator`. +Os atributos a seguir estão disponíveis. You can change the attribute names in the [management console](/enterprise/{{ currentVersion }}/admin/guides/installation/accessing-the-management-console/), with the exception of the `administrator` attribute. | Nome padrão do atributo | Tipo | Descrição | | ----------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -87,24 +99,92 @@ Para especificar mais de um valor para um atributo, use múltiplos elementos de {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.authentication %} -3. Selecione **SAML**. ![Autenticação SAML](/assets/images/enterprise/management-console/auth-select-saml.png) -4. {% data reusables.enterprise_user_management.built-in-authentication-option %} ![Selecionar caixa de autenticação integrada SAML](/assets/images/enterprise/management-console/saml-built-in-authentication.png) -5. Para habilitar SSO de resposta não solicitada, selecione **IdP initiated SSO** (SSO iniciado pelo IdP). Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo Provedor de identidade (IdP) não solicitado com `AuthnRequest`. ![SAML idP SSO](/assets/images/enterprise/management-console/saml-idp-sso.png) +1. Selecione **SAML**. - {% tip %} + ![Screenshot of option to enable SAML authentication in management console](/assets/images/enterprise/management-console/auth-select-saml.png) +1. {% data reusables.enterprise_user_management.built-in-authentication-option %} - **Observação**: é recomendável manter esse valor **desmarcado**. Você deve habilitar esse recurso **somente ** na rara instância em que sua implementação SAML não oferecer suporte ao SSO iniciado pelo provedor de serviços e quando recomendado pelo {% data variables.contact.enterprise_support %}. + ![Screenshot of option to enable built-in authentication outside of SAML IdP](/assets/images/enterprise/management-console/saml-built-in-authentication.png) +1. Para habilitar SSO de resposta não solicitada, selecione **IdP initiated SSO** (SSO iniciado pelo IdP). Por padrão, o {% data variables.product.prodname_ghe_server %} responderá a uma solicitação iniciada pelo Provedor de identidade (IdP) não solicitado com `AuthnRequest`. - {% endtip %} + ![Screenshot of option to enable IdP-initiated unsolicited response](/assets/images/enterprise/management-console/saml-idp-sso.png) -5. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. ![Configuração de desabilitar administrador de SAML](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) -6. No campo **Sign on URL** (URL de logon), digite o ponto de extremidade HTTP ou HTTPS do seu IdP para solicitações de logon único. Esse valor é fornecido pela configuração do IdP. Se o nome do host só estiver disponível na rede interna, talvez seja necessário [configurar a {% data variables.product.product_location %} para usar servidores de nomes internos](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). ![Autenticação SAML](/assets/images/enterprise/management-console/saml-single-sign-url.png) -7. Como alternativa, no campo **Issuer** (Emissor), digite o nome do emissor de SAML. Fazer isso verifica a autenticidade das mensagens enviadas para a {% data variables.product.product_location %}. ![Emissor SAML](/assets/images/enterprise/management-console/saml-issuer.png) -8. Nos menus suspensos **Signature Method** (Método de assinatura) e **Digest Method** (Método de compilação), escolha o algoritmo de hash usado pelo emissor SAML para verificar a integridade das solicitações do {% data variables.product.product_location %}. Especifique o formato no menu suspenso **Name Identifier Format** (Formato de identificador de nome). ![Método SAML ](/assets/images/enterprise/management-console/saml-method.png) -9. Em **Verification certificate** (Certificado de verificação), clique em **Choose File** (Escolher arquivo) e escolha um certificado para validar as respostas SAML do IdP. ![Autenticação SAML](/assets/images/enterprise/management-console/saml-verification-cert.png) -10. Modifique os nomes do atributo SAML para corresponder ao IdP, se necessário, ou aceite os nomes padrão. ![Nomes de atributos SAML](/assets/images/enterprise/management-console/saml-attributes.png) + {% tip %} -{% ifversion ghes %} + **Note**: We recommend keeping this value **unselected**. You should enable this feature **only** in the rare instance that your SAML implementation does not support service provider initiated SSO, and when advised by {% data variables.contact.enterprise_support %}. + + {% endtip %} + +1. Selecione **Disable administrator demotion/promotion** (Desabilitar rebaixamento/promoção do administrador) se você **não** quiser que o provedor SAML determine direitos de administrador para usuários no {% data variables.product.product_location %}. + + ![Screenshot of option to enable option to respect the "administrator" attribute from the IdP to enable or disable administrative rights](/assets/images/enterprise/management-console/disable-admin-demotion-promotion.png) +1. Optionally, to allow {% data variables.product.product_location %} to send and receive encrypted assertions to and from your SAML IdP, select **Require encrypted assertions**. For more information, see "[Enabling encrypted assertions](#enabling-encrypted-assertions)." + + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) + + {% warning %} + + **Warning**: Incorrectly configuring encrypted assertions can cause all authentication to {% data variables.product.product_location %} to fail. + + - You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.product.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](#enabling-encrypted-assertions)." + + - Before enabling encrypted assertions, {% data variables.product.company_short %} recommends testing encrypted assertions in a staging environment, and confirming that SAML authentication functions as you expect. Para obter mais informações, consulte "[Configurar instância de preparo](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)". + + {% endwarning %} +1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. Esse valor é fornecido pela configuração do IdP. If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/). + + ![Screenshot of text field for single sign-on URL](/assets/images/enterprise/management-console/saml-single-sign-url.png) +1. Optionally, in the **Issuer** field, type your SAML issuer's name. This verifies the authenticity of messages sent to {% data variables.product.product_location %}. + + ![Screenshot of text field for SAML issuer URL](/assets/images/enterprise/management-console/saml-issuer.png) +1. In the **Signature Method** and **Digest Method** drop-down menus, choose the hashing algorithm used by your SAML issuer to verify the integrity of the requests from {% data variables.product.product_location %}. Specify the format with the **Name Identifier Format** drop-down menu. + + ![Screenshot of drop-down menus to select signature and digest method](/assets/images/enterprise/management-console/saml-method.png) +1. Em **Verification certificate** (Certificado de verificação), clique em **Choose File** (Escolher arquivo) e escolha um certificado para validar as respostas SAML do IdP. + + ![Screenshot of button for uploading validation certificate from IdP](/assets/images/enterprise/management-console/saml-verification-cert.png) +1. Modify the SAML attribute names to match your IdP if needed, or accept the default names. + + ![Screenshot of fields for entering additional SAML attributes](/assets/images/enterprise/management-console/saml-attributes.png) + +{% ifversion ghes > 3.3 %} + +## Enabling encrypted assertions + +To enable encrypted assertions, your SAML IdP must also support encrypted assertions. You must provide {% data variables.product.product_location %}'s public certificate to your IdP, and configure encryption settings that match your IdP. + +{% warning %} + +**Warning**: Incorrectly configuring encrypted assertions can cause all authentication to {% data variables.product.product_location %} to fail. {% data variables.product.company_short %} strongly recommends testing your SAML configuration in a staging environment. For more information about staging instances, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)." + +{% endwarning %} + +1. Configure SAML for {% data variables.product.product_location %}. For more information, see "[Configuring SAML settings](#configuring-saml-settings)." +{% data reusables.enterprise_installation.ssh-into-instance %} +1. Run the following command to output {% data variables.product.product_location %}'s public certificate. + + openssl pkcs12 -in /data/user/common/saml-sp.p12 -nokeys -passin pass: +1. In the output, copy the text beginning with `-----BEGIN CERTIFICATE-----` and ending with `-----END CERTIFICATE-----`, and paste the output into a plaintext file. +1. Sign into your SAML IdP as an administrator. +1. In the application for {% data variables.product.product_location %}, enable encrypted assertions. + - Note the encryption method and key transport method. + - Provide the public certificate from step 3. +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +{% data reusables.enterprise_management_console.authentication %} +1. Select **Require encrypted assertions**. + + ![Screenshot of "Enable encrypted assertions" checkbox within management console's "Authentication" section](/assets/images/help/saml/management-console-enable-encrypted-assertions.png) +1. To the right of "Encryption Method", select the encryption method for your IdP from step 5. + + ![Screenshot of "Encryption Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-encryption-method.png) +1. To the right of "Key Transport Method", select the key transport method for your IdP from step 5. + + ![Screenshot of "Key Transport Method" for encrypted assertions](/assets/images/help/saml/management-console-encrypted-assertions-key-transport-method.png) +1. Clique em **Save settings** (Salvar configurações). +{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} + +{% endif %} ## Atualizando `NameID` do SAML de um usuário @@ -116,8 +196,6 @@ Para especificar mais de um valor para um atributo, use múltiplos elementos de 6. No campo "NameID", digite o novo `NameID` para o usuário. ![Campo "NameID" na caixa de diálogo modal com NameID digitado](/assets/images/enterprise/site-admin-settings/update-saml-nameid-field-in-modal.png) 7. Clique **Atualizar o NameID**. ![Botão "Atualizar o NameID" com o valor do NameID atualizado dentro do modal](/assets/images/enterprise/site-admin-settings/update-saml-nameid-update.png) -{% endif %} - ## Revogar o acesso à {% data variables.product.product_location %} Se remover um usuário do seu provedor de identidade, você também deverá suspendê-lo manualmente. Caso contrário, ele continuará podendo fazer autenticação usando tokens de acesso ou chaves SSH. Para obter mais informações, consulte "[Suspender e cancelar a suspensão de usuários](/enterprise/admin/guides/user-management/suspending-and-unsuspending-users)". @@ -128,7 +206,7 @@ A mensagem de resposta deve atender aos seguintes requisitos: - O `` elemento deve sempre ser fornecido no documento de resposta raiz e deve corresponder ao URL do ACS somente quando o documento de resposta raiz estiver assinado. Se for assinada, a declaração será ignorada. - O elemento `` deve sempre ser fornecido como parte do elemento ``. Ele deve corresponder ao `EntityId` para {% data variables.product.prodname_ghe_server %}. Esta é a URL para a instância do {% data variables.product.prodname_ghe_server %}, como `https://ghe.corp.example.com`. -- Todas as declarações na resposta **devem** ser precedidas de assinatura digital. É possível fazer isso assinando cada elemento `` ou assinando o elemento ``. +- Each assertion in the response **must** be protected by a digital signature. É possível fazer isso assinando cada elemento `` ou assinando o elemento ``. - Um elemento `` deve ser fornecido como parte do elemento ``. Qualquer formato de identificador de nome persistente pode ser usado. - O atributo `Recipient` deve estar presente e definido na URL do ACS. Por exemplo: diff --git a/translations/pt-BR/content/admin/index.md b/translations/pt-BR/content/admin/index.md index 7cd897feaf..55d6eaa248 100644 --- a/translations/pt-BR/content/admin/index.md +++ b/translations/pt-BR/content/admin/index.md @@ -127,7 +127,7 @@ children: - /enterprise-management - /github-actions - /packages - - /advanced-security + - /code-security - /guides - /release-notes - /all-releases diff --git a/translations/pt-BR/content/admin/overview/system-overview.md b/translations/pt-BR/content/admin/overview/system-overview.md index 16dd005679..690af4a60a 100644 --- a/translations/pt-BR/content/admin/overview/system-overview.md +++ b/translations/pt-BR/content/admin/overview/system-overview.md @@ -102,6 +102,12 @@ O {% data variables.product.prodname_dotcom %} desenvolveu o {% data variables.p Por padrão, o appliance também fornece acesso Secure Shell (SSH) para acesso a repositórios com o Git e para finalidades administrativas. Para obter mais informações, consulte "[Sobre SSH](/enterprise/user/articles/about-ssh)" e "[Acessar o shell administrativo (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)". +{% ifversion ghes > 3.3 %} + +If you configure SAML authentication for {% data variables.product.product_location %}, you can enable encrypted assertions between the instance and your SAML IdP. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." + +{% endif %} + ### Usuários e permissões de acesso O {% data variables.product.prodname_ghe_server %} oferece três tipos de contas. diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md index a4c66cf00f..6d68a99239 100644 --- a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/index.md @@ -29,6 +29,7 @@ children: - /managing-invoices-for-your-enterprise - /connecting-an-azure-subscription-to-your-enterprise - /how-does-upgrading-or-downgrading-affect-the-billing-process + - /one-time-payments-for-customers-in-india - /discounted-subscriptions-for-github-accounts --- diff --git a/translations/pt-BR/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md new file mode 100644 index 0000000000..37213caf34 --- /dev/null +++ b/translations/pt-BR/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md @@ -0,0 +1,65 @@ +--- +title: One-time payments for customers in India +intro: Customers in India who have been impacted by the Reserve Bank of India's recurring payment regulation can now make one-time payments for their GitHub subscriptions and services. +redirect_from: + - /early-access/billing/india-rbi-regulation +versions: + fpt: '*' + ghec: '*' +topics: + - Billing + - Sponsors + - Policy +shortTitle: India one-time payments +--- + + +## About the Reserve Bank of India's recurring payments regulation + +A new payments regulation from the Reserve Bank of India (RBI) recently came into effect. This regulation places additional requirements on recurring online transactions and has prevented some {% data variables.product.company_short %} customers in India from making recurring payments. Customers using payment methods issued in India for any recurring transactions on {% data variables.product.product_name %} may find that their payments are declined by their banks or card issuers. For more information, see [the RBI's press release](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353). + +The regulation applies to all recurring transactions, including: +- {% data variables.product.prodname_dotcom %} plan subscriptions (Pro, Team, Enterprise) +- {% data variables.product.prodname_marketplace %} purchases +- {% data variables.product.prodname_sponsors %} transactions +- Git Large File Storage purchases +- {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} consumption + +In order to minimize disruption, recurring payments for our affected customers were paused on October 29th, 2021. Paid features and services have remained available to customers impacted by the RBI regulation. + +## About one-time payments on {% data variables.product.company_short %} + +As we work with our payment gateway provider to meet the new requirements, we are providing a temporary one-time payment option for impacted customers in India. From February 15th 2022, {% data variables.product.company_short %} customers in India who have been affected by the new RBI regulation will be able to make one-time payments on their regular billing cycle cadence. + +### For customers on monthly billing + +Customers on monthly billing plans will be able to make a one-time payment on the same day their billing cycle usually renews. For example, if you're usually billed on the 7th of each month, you will now be able to make a one-time payment from your account from the 7th of each month. Your first one-time payment will also include any accrued usage from October 2021 onwards. + +If you are currently billed monthly, and would like to switch to yearly billing, you can reduce the frequency of your one-time payments. For more information, see "[Changing the duration of your billing cycle](/en/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)." + +### For customers on yearly billing + +If you are billed yearly, and your renewal date was between October 1st, 2021 and February 14th, 2022, you will be able to make a one-time payment for your annual subscriptions from February 15th. This initial payment will include the prorated outstanding cost of your subscription for the period since your previous billing cycle ended. + +If your billing cycle is due to renew after February 15th, we will attempt to take the recurring payment. If the payment attempt is declined, you will then be able to make a one-time payment through your account's billing page. + +In the meantime, we are actively working with our payment partners to restore recurring payments for impacted customers. For more information or questions, you can contact [GitHub Support](https://support.github.com/contact). + +### Impact to {% data variables.product.prodname_sponsors %} + +Existing sponsorships will remain in place during this period and maintainers will continue to be paid out as expected. Payments for the accrued sponsorship amounts from the funding account will be collected at the same time as other accrued charges. + +## Making a one-time payment for a GitHub subscription + +{% note %} + +**Note**: Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made. + +{% endnote %} + +{% data reusables.user_settings.access_settings %} +{% data reusables.user_settings.billing_plans %} +3. At the top of the page, click **Pay now**. ![One-time payment pay now button](/assets/images/help/billing/pay-now-button.png) +4. Review your billing and payment information. If you need to make an edit, click **Edit** next to the relevant section. Otherwise, click **Submit payment**. ![One-time payment summary](/assets/images/help/billing/payment-summary.png) +5. Optionally, if you clicked **Edit**, make any necessary changes, and then click **Submit payment**. ![One-time payment edit summary](/assets/images/help/billing/payment-summary-edit.png) +6. Once payment for the current billing cycle has been successfully made, the **Pay now** button on your "Billing & plans" page will be disabled until your next payment is due. ![One-time payment pay now button disabled](/assets/images/help/billing/pay-now-button-disabled.png) diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 0b9c98f2b2..9bcc197ff1 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md @@ -32,7 +32,7 @@ O primeiro passo para proteger um repositório é configurar quem pode ver e mod Na página principal do seu repositório, clique em **{% octicon "gear" aria-label="The Settings gear" %}configurações**e, em seguida, desça a barra de rolagem até a "Zona de perigo". -- Para alterar quem pode visualizar seu repositório, clique em **Alterar a visibilidade**. Para obter mais informações, consulte "[Configurar a visibilidade do repositório](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec %} +- Para alterar quem pode visualizar seu repositório, clique em **Alterar a visibilidade**. For more information, see "[Setting repository visibility](/github/administering-a-repository/setting-repository-visibility)."{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} - Para alterar quem pode acessar o seu repositório e ajustar as permissões, clique em **Gerenciar acesso**. Para obter mais informações, consulte[Gerenciar equipes e pessoas com acesso ao seu repositório](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository)".{% endif %} {% ifversion fpt or ghes > 3.0 or ghae or ghec %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md index c1e5f5e4db..b6c03a41f0 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md @@ -33,7 +33,7 @@ Quando {% data variables.product.prodname_dependabot %} detecta dependências vu {% ifversion ghes or ghae-issue-4864 %} Por padrão, se o proprietário da sua empresa configurou e-mail para notificações na sua empresa, você receberá {% data variables.product.prodname_dependabot_alerts %} por e-mail. -Os proprietários das empresas também podem habilitar {% data variables.product.prodname_dependabot_alerts %} sem notificações. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." +Os proprietários das empresas também podem habilitar {% data variables.product.prodname_dependabot_alerts %} sem notificações. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} ## Configurar notificações para {% data variables.product.prodname_dependabot_alerts %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md index e114976e99..2221bc45cb 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md @@ -46,4 +46,4 @@ A revisão de dependências é compatível com as mesmas linguagens e os mesmos ## Habilitar revisão de dependências -O recurso de revisão de dependências é disponibilizado quando você habilitar o gráfico de dependências. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Habilitando o gráfico de dependência](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}Para obter mais informações, consulte "[Habilitando o gráfico de dependência e{% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."{% endif %} +O recurso de revisão de dependências é disponibilizado quando você habilitar o gráfico de dependências. {% ifversion fpt or ghec %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."{% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index fa6b543bf6..dc24745e23 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -28,10 +28,7 @@ shortTitle: Gráfico de dependências ## Sobre o gráfico de dependências -O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, ele mostra{% ifversion fpt or ghec %}: - -- As dependências, os ecossistemas e os pacotes do qual depende -- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.product_name %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% endif %} +{% data reusables.dependabot.about-the-dependency-graph %} Ao fazer push de um commit para o {% data variables.product.product_name %}, que muda ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch-padrão, o gráfico de dependências será atualizado automaticamente.{% ifversion fpt or ghec %} Além disso, o gráfico é atualizado quando alguém faz push de uma alteração no repositório de uma de suas dependências.{% endif %} Para obter informações sobre os ecossistemas compatíveis e arquivos de manifesto, consulte "[ecossistemas de pacotes compatíveis](#supported-package-ecosystems)" abaixo. @@ -66,7 +63,7 @@ Você pode usar o gráfico de dependências para: {% ifversion fpt or ghec %}Para gerar um gráfico de dependência, o {% data variables.product.product_name %} precisa de acesso somente leitura ao manifesto dependência e aos arquivos de bloqueio em um repositório. O gráfico de dependências é gerado automaticamente para todos os repositórios públicos e você pode optar por habilitá-lo para repositórios privados. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} -{% ifversion ghes or ghae %}Se o gráfico de dependências não estiver disponível no seu sistema, o proprietário da empresa poderá habilitar o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."{% endif %} +{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)."{% endif %} Quando o gráfico de dependências é ativado pela primeira vez, todos manifesto e arquivos de bloqueio para ecossistemas suportados são analisados imediatamente. O gráfico geralmente é preenchido em minutos, mas isso pode levar mais tempo para repositórios com muitas dependências. Uma vez habilitado, o gráfico é atualizado automaticamente a cada push no repositório{% ifversion fpt or ghec %} e a cada push para outros repositórios no gráfico{% endif %}. @@ -112,7 +109,7 @@ Os formatos recomendados definem explicitamente quais versões são usadas para ## Leia mais - "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia -- "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} +- "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} - "[Visualizar informações da sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} - "[Visualizar e atualizar dependências vulneráveis no seu repositório](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index 057007c89e..b48bba6947 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -34,7 +34,7 @@ O gráfico de dependências mostra as dependências{% ifversion fpt or ghec %} e 4. Opcionalmente, em "Gráfico de dependência", clique em **Dependentes**. ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} {% ifversion ghes or ghae-issue-4864 %} -Os proprietários das empresas podem configurar o gráfico de dependências a nível da empresa. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." +Os proprietários das empresas podem configurar o gráfico de dependências a nível da empresa. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)." {% endif %} ### Vista de dependências diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md b/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md index a011fa94cf..e35aa42265 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md @@ -21,6 +21,7 @@ Ao criar uma conta pessoal ou organização, você deve selecionar um plano de c ## Inscrevendo-se em uma nova conta +1. If you want to create a new personal account, make sure you are currently signed out of GitHub. {% data reusables.accounts.create-account %} 1. Siga as instruções para criar a conta pessoa ou organização. diff --git a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md index 0d4e7c561d..c39167bec4 100644 --- a/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md +++ b/translations/pt-BR/content/get-started/using-github/keyboard-shortcuts.md @@ -24,7 +24,7 @@ Digitar ? no {% data variables.product.prodname_dotcom %} exibe uma c Veja abaixo uma lista dos atalhos de teclado disponíveis. {% if command-palette %} -O {% data variables.product.prodname_command_palette %} também fornece acesso rápido a uma ampla gama de ações, sem a necessidade de lembrar os atalhos de teclado. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +O {% data variables.product.prodname_command_palette %} também fornece acesso rápido a uma ampla gama de ações, sem a necessidade de lembrar os atalhos de teclado. Para obter mais informações, consulte "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".{% endif %} ## Atalhos para o site @@ -36,7 +36,7 @@ O {% data variables.product.prodname_command_palette %} também fornece acesso r {% if command-palette %} -Command+K (Mac) ou
Ctrl+K (Windows/Linux) | Abre o {% data variables.product.prodname_command_palette %}. Se você estiver editanto o texto de markdown, abra a paleta de comando com Command+Opção+K ou Ctrl+Alt+K. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +Command+K (Mac) ou
Ctrl+K (Windows/Linux) | Abre o {% data variables.product.prodname_command_palette %}. Se você estiver editanto o texto de markdown, abra a paleta de comando com Command+Opção+K ou Ctrl+Alt+K. Para obter mais informações, consulte "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".{% endif %} ## Repositórios @@ -127,6 +127,7 @@ Para mais atalhos de teclado, consulte a [Documentação CodeMirror](https://cod | M | Define um marco. Para obter mais informações, consulte "[Associar marcos a problemas e pull requests](/articles/associating-milestones-with-issues-and-pull-requests/)". | | L | Aplica uma etiqueta. Para obter mais informações, consulte "[Aplicar etiquetas a problemas e pull requests](/articles/applying-labels-to-issues-and-pull-requests/)". | | A | Define um responsável. Para obter mais informações, consulte "[Atribuir problemas e pull requests a outros usuários {% data variables.product.company_short %}](/articles/assigning-issues-and-pull-requests-to-other-github-users/)". | +| X | Link an issue or pull request from the same repository. Para obter mais informações, consulte "[Vincular um pull request a um problema](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue/)." | | Command+Shift+P (Mac) ou
Ctrl+Shift+P (Windows/Linux) | Alterna entre as abas **Escrever** e **Visualizar**{% ifversion fpt or ghec %} | Alt e clique | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas na aba atual, mantendo Alt pressionado e clicando no {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | | Shift e clique | Ao criar um problema a partir de uma lista de tarefas, abra o novo formulário de problemas em uma nova aba mantendo Shift pressionado e clicando em {% octicon "issue-opened" aria-label="The issue opened icon" %} no canto superior direito da tarefa. Para obter mais informações, consulte "[Sobre listas de tarefas](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)". | diff --git a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md index 37418550e5..2757827507 100644 --- a/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md +++ b/translations/pt-BR/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md @@ -20,7 +20,7 @@ Para transferir um problema aberto para outro repositório, é preciso ter acess Você somente pode transferir problemas entre repositórios pertencentes à mesma conta de usuário ou organização. {% ifversion fpt or ghes or ghec %}Você não pode transferir um problema de um repositório privado para um repositório público.{% endif %} -Quando você transfere um problema, os comentários e responsáveis são mantidos. As etiquetas e os marcos do problema não são retidos. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". +When you transfer an issue, comments, labels and assignees are retained. The issue's milestones are not retained. Esse problema permanecerá em qualquer quadro de projeto pertencente ao usuário ou à organização e será removido dos quadros de projeto de todos os repositórios. Para obter mais informações, consulte "[Sobre quadros de projeto](/articles/about-project-boards)". As pessoas ou equipes mencionadas no problema receberão uma notificação informando que o problema foi transferido para um novo repositório. O URL original redirecionará para o novo URL do problema. As pessoas que não tenham permissões de leitura no novo repositório verão um banner informando que o problema foi transferido para um novo repositório ao qual elas não têm acesso. diff --git a/translations/pt-BR/content/organizations/index.md b/translations/pt-BR/content/organizations/index.md index 0ef9164460..74ea29f74b 100644 --- a/translations/pt-BR/content/organizations/index.md +++ b/translations/pt-BR/content/organizations/index.md @@ -1,11 +1,30 @@ --- title: Organizações e equipes shortTitle: Organizações -intro: Colabore em muitos projetos gerenciando o acesso a projetos e dados e personalizando as configurações de sua organização. +intro: 'You can use organizations to collaborate with an unlimited number of people across many projects at once, while managing access to your data and customizing settings.' redirect_from: - /articles/about-improved-organization-permissions - /categories/setting-up-and-managing-organizations-and-teams - /github/setting-up-and-managing-organizations-and-teams +introLinks: + overview: /organizations/collaborating-with-groups-in-organizations/about-organizations +featuredLinks: + guides: + - /get-started/learning-about-github/types-of-github-accounts + - /organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization + - /organizations/organizing-members-into-teams/about-teams + popular: + - /organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch + - /organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization + - /organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization + - /organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions + - '{% ifversion ghae %}/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization{% endif %}' + guideCards: + - /organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization + - /organizations/managing-membership-in-your-organization/adding-people-to-your-organization + - /organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository + - /organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization +layout: product-landing versions: fpt: '*' ghes: '*' diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md index 5747fb67d6..6b58af1c59 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md @@ -38,14 +38,11 @@ Para apoiar ainda mais as habilidades de colaboração da sua equipe, você pode ## Adicionando colaboradores externos a um repositório +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +You can give outside collaborators access to a repository in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person). " +{% else %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} -{% data reusables.repositories.click-collaborators-teams %} -{% data reusables.organizations.invite-teams-or-people %} -5. No campo de pesquisa, comece a digitar o nome da pessoa que deseja convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma pessoa para convidar para o repositório](/assets/images/help/repository/manage-access-invite-search-field.png) -6. Em "Escolher uma função", selecione as permissões a serem concedidas à pessoa e, em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionar permissões para a pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png) -{% else %} 5. Na barra lateral esquerda, clique em **Collaborators & teams** (Colaboradores e equipes). ![Barra lateral de configurações do repositório com destaque para Collaborators & teams (Colaboradores e equipes)](/assets/images/help/repository/org-repo-settings-collaborators-and-teams.png) 6. Em "Collaborators" (Colaboradores), digite o nome da pessoa à qual deseja conceder acesso ao repositório e clique em **Add collaborator** (Adicionar colaborador). ![A seção Collaborators (Colaboradores) com o nome de usuário Octocat inserido no campo de pesquisa](/assets/images/help/repository/org-repo-collaborators-find-name.png) 7. Ao lado do nome do novo colaborador, escolha o nível de permissão apropriado: *Gravação*, *Leitura* ou *Administrador*. ![O selecionador de permissões do repositório](/assets/images/help/repository/org-repo-collaborators-choose-permissions.png) diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md index 5c530ecbb0..18752062fe 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md @@ -24,15 +24,15 @@ Ao remover um colaborador de um repositório de sua organização, o colaborador {% data reusables.repositories.deleted_forks_from_private_repositories_warning %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +## Gerenciar o acesso de um indivíduo a um repositório da organização +You can give a person access to a repository or change a person's level of access to a repository in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository). " +{% else %} ## Concedendo acesso a uma pessoa a um repositório {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} -{% data reusables.repositories.click-collaborators-teams %} -{% else %} {% data reusables.repositories.navigate-to-manage-access %} -{% endif %} {% data reusables.organizations.invite-teams-or-people %} 1. No campo de busca, comece a digitar o nome da pessoa para convidar e, em seguida, clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma equipe ou pessoa para convidar ao repositório](/assets/images/help/repository/manage-access-invite-search-field.png) 6. Em "Escolher uma função ", selecione a função do repositório para atribuir a pessoa e, em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionando permissões para a equipe ou pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png) @@ -46,7 +46,7 @@ Ao remover um colaborador de um repositório de sua organização, o colaborador 5. À direita do nome do colaborador que deseja remover, use o menu suspenso {% octicon "gear" aria-label="The Settings gear" %} e clique em **Manage** (Gerenciar). ![Link para manage access (gerenciar acesso)](/assets/images/help/organizations/member-manage-access.png) 6. Na página "Manage access" (Gerenciar acesso), ao lado do repositório clique em **Manage access** (Gerenciar acesso). ![Botão Manage access (Gerenciar acesso) em um repositório](/assets/images/help/organizations/repository-manage-access.png) 7. Revise o acesso da pessoa em determinado repositório, por exemplo, se a pessoa é um colaborador ou tem acesso ao repositório como integrante de equipe. ![Matriz de acesso a repositório para o usuário](/assets/images/help/organizations/repository-access-matrix-for-user.png) - +{% endif %} ## Leia mais {% ifversion fpt or ghec %}- "[Restringir interações no repositório](/articles/limiting-interactions-with-your-repository)"{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md index f26aeceb84..81a439dfaa 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md @@ -28,6 +28,9 @@ Pessoas com acesso de administrador a um repositório podem gerenciar o acesso d ## Conceder a uma equipe acesso a um repositório +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +You can give a team access to a repository or change a team's level of access to a repository in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#inviting-a-team-or-person). " +{% else %} {% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} {% data reusables.organizations.specific_team %} @@ -35,9 +38,18 @@ Pessoas com acesso de administrador a um repositório podem gerenciar o acesso d 5. Acima da lista de repositórios, clique em **Add repository** (Adicionar repositório). ![Botão Add repository (Adicionar repositório)](/assets/images/help/organizations/add-repositories-button.png) 6. Digite o nome de um repositório e clique em **Add repository to team** (Adicionar repositório a uma equipe). ![Campo de pesquisa Repository (Repositório)](/assets/images/help/organizations/team-repositories-add.png) 7. Como opção, use o menu suspenso à direita do nome do repositório e escolha um nível de permissão diferente para a equipe. ![Menu suspenso Repository access level (Nível de acesso ao repositório)](/assets/images/help/organizations/team-repositories-change-permission-level.png) - +{% endif %} ## Remover acesso de uma equipe a um repositório +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +You can remove a team's access to an organization repository in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person). " + +If a team has direct access to a repository, you can remove that team's access to the repository. Se o acesso da equipe ao repositório é herdado de uma equipe principal, você deve remover o repositório da equipe principal para remover o repositório das equipes secundárias. + +{% data reusables.repositories.deleted_forks_from_private_repositories_warning %} + +{% else %} + Você pode remover o acesso de uma equipe a um repositório se a equipe tiver acesso direto a ele. Se o acesso da equipe ao repositório é herdado de uma equipe principal, você deve remover o repositório da equipe principal para remover o repositório das equipes secundárias. {% data reusables.repositories.deleted_forks_from_private_repositories_warning %} @@ -49,7 +61,7 @@ Você pode remover o acesso de uma equipe a um repositório se a equipe tiver ac 5. Selecione o repositório ou repositórios que deseja remover da equipe. ![Lista de repositórios de equipes com as caixas de seleção para alguns repositórios selecionadas](/assets/images/help/teams/select-team-repositories-bulk.png) 6. Acesse o menu suspenso acima da lista de repositórios e clique em **Remove from team** (Remover da equipe). ![Menu suspenso com a opção para Remove a repository from a team (Remover um repositório de uma equipe)](/assets/images/help/teams/remove-team-repo-dropdown.png) 7. Verifique o repositório ou repositórios que serão removidos da equipe e clique em **Remove repositories** (Remover repositórios). ![Caixa modal com uma lista de repositórios que a equipe não terá mais acesso](/assets/images/help/teams/confirm-remove-team-repos.png) - +{% endif %} ## Leia mais - "[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/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md index bb641e6090..fe79dc79fb 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md @@ -53,6 +53,9 @@ Se você desejar remover um colaborador externo de repositórios específicos na 7. Para remover completamente o acesso do colaborador externo ao repositório, clique em **Remove access to this repository** (Remover acesso a este repositório) no canto superior direito. ![Botão Remove access to this repository (Remover acesso a este repositório)](/assets/images/help/organizations/remove-access-to-this-repository.png) 8. Para confirmar, clique em **Remove access** (Remover acesso). ![Confirme o colaborador externo que será removido do repositório](/assets/images/help/teams/confirm-remove-outside-collaborator-from-a-repository.png) +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +You can also remove an outside collaborator from a repository in the access overview in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#removing-access-for-a-team-or-person). " +{% endif %} ## Leia mais - "[Adicionar colaboradores externos a repositórios na sua organização](/articles/adding-outside-collaborators-to-repositories-in-your-organization)" diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md index 94e4bad9ae..1476e14234 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md @@ -16,23 +16,20 @@ shortTitle: Visualizar pessoas com acesso --- Os administradores podem usar essas informações para ajudar pessoas fora do quadro, coletar dados para conformidade e outras verificações gerais de segurança. - +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +![Acessar visão geral do gerenciamento ](/assets/images/help/repository/manage-access-overview.png) +{% else %} ![Lista de permissões para pessoas no repositório](/assets/images/help/repository/repository-permissions-list.png) - +{% endif %} ## Exibir pessoas com acesso ao seu repositório -{% ifversion fpt or ghec %} -{% note %} - -**Observação**: Você também pode ver uma visão geral combinada das equipes e pessoas com acesso ao seu repositório. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/github/administering-a-repository/managing-teams-and-people-with-access-to-your-repository). " - -{% endnote %} -{% endif %} - +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %} +You can see a combined overview of teams and people with access to your repository in your repository settings. Para obter mais informações, consulte "[Gerenciar equipes e pessoas com acesso ao seu repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository#about-access-management-for-repositories). " +{% else %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} {% data reusables.repositories.accessing-repository-people %} - +{% endif %} ## Exportar uma lista de pessoas com acesso a um repositório Os proprietários de organizações no {% data variables.product.prodname_ghe_cloud %} ou no {% data variables.product.prodname_ghe_server %} podem exportar uma lista CSV de pessoas que têm acesso a um repositório. diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/index.md b/translations/pt-BR/content/organizations/managing-organization-settings/index.md index 020d030fc1..0d440b3262 100644 --- a/translations/pt-BR/content/organizations/managing-organization-settings/index.md +++ b/translations/pt-BR/content/organizations/managing-organization-settings/index.md @@ -20,6 +20,7 @@ children: - /setting-permissions-for-deleting-or-transferring-repositories - /restricting-repository-visibility-changes-in-your-organization - /managing-the-forking-policy-for-your-organization + - /managing-pull-request-reviews-in-your-organization - /disabling-or-limiting-github-actions-for-your-organization - /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization - /setting-permissions-for-adding-outside-collaborators diff --git a/translations/pt-BR/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/translations/pt-BR/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md new file mode 100644 index 0000000000..2e709d88c2 --- /dev/null +++ b/translations/pt-BR/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md @@ -0,0 +1,27 @@ +--- +title: Managing pull request reviews in your organization +intro: You can limit which users can approve or request changes to a pull requests in your organization. +versions: + feature: pull-request-approval-limit +permissions: Organization owners can limit which users can submit reviews that approve or request changes to a pull request. +topics: + - Organizations + - Pull requests +shortTitle: Manage pull request reviews +--- + +## About code review limits + +By default, in public repositories, any user can submit reviews that approve or request changes to a pull request. + +You can limit who is able to approve or request changes to pull requests in public repositories owned by your organization. After you enable code review limits, anyone can comment on pull requests in your public repositories, but only people with explicit access to a repository can approve a pull request or request changes. + +You can also enable code review limits for individual repositories. If you enable or limits for your organization, you will override any limits for individual repositories owned by the organization. For more information, see "[Managing pull request reviews in your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository)." + +## Enabling code review limits + +{% data reusables.profile.access_org %} +{% data reusables.profile.org_settings %} +{% data reusables.organizations.moderation-settings %} +1. Under "{% octicon "report" aria-label="The report icon" %} Moderation", click **Code review limits**. ![Screenshot of sidebar item for code review limits for organizations](/assets/images/help/organizations/code-review-limits-organizations.png) +1. Review the information on screen. Click **Limit review on all repositories** to limit reviews to those with explicit access, or click **Remove review limits from all repositories** to remove the limits from every public repository in your organization. ![Screenshot of code review limits settings for organizations](/assets/images/help/organizations/code-review-limits-organizations-settings.png) diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 04d878c12e..a2a3905773 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -99,7 +99,7 @@ Você só pode escolher uma permissão adicional se já não estiver incluída n If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. -If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**. +{% data reusables.organizations.mixed-roles-warning %} To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. Para obter mais informações, consulte: - "[Configurando permissões de base para uma organização](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md index 283d42f957..31a30de291 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md @@ -130,6 +130,7 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu | Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | |{% ifversion ghec %} | Habilitar sincronização de equipes (consulte "[Gerenciar sincronização de equipe para a sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" para obter informações) | **X** | | | {% endif %} +| Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | | {% elsif ghes > 3.2 or ghae-issue-4999 %} @@ -176,7 +177,9 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu | Converter integrantes da organização em [colaboradores externos](#outside-collaborators) | **X** | | | | [Exibir as pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository) | **X** | | | | [Exportar uma lista das pessoas com acesso a um repositório da organização](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository) | **X** | | | -| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | | +| Gerenciar etiquetas padrão (consulte "[Gerenciar etiquetas padrão nos repositórios da organização](/articles/managing-default-labels-for-repositories-in-your-organization)") | **X** | | |{% if pull-request-approval-limit %} +| Manage pull request reviews in the organization (see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)") | **X** | | | +{% endif %} {% ifversion ghae %}| Gerenciar listas de permissão de IP (consulte "[Restringir tráfego de rede para a sua empresa](/admin/configuration/restricting-network-traffic-to-your-enterprise)") | **X** | | |{% endif %} 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 567981bf13..9caf075b8e 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 @@ -32,7 +32,7 @@ Após inicialização de uma pull request, você verá uma página de revisão q Depois que tiver criado uma pull request, você poderá fazer push dos commits do branch de tópico para adicioná-los à sua pull request existente. Esses commits aparecerão em ordem cronológica na pull request e as alterações estarão visíveis na guia "Files chenged" (Arquivos alterados). -Outros contribuidores podem revisar as alterações propostas, adicionar comentários de revisão, contribuir com a discussão da pull request e, até mesmo, adicionar commits à pull request. +Outros contribuidores podem revisar as alterações propostas, adicionar comentários de revisão, contribuir com a discussão da pull request e, até mesmo, adicionar commits à pull request. {% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} {% ifversion fpt or ghec %} Você pode ver as informações sobre o status da implantação atual do branch e atividades passadas de implantação na guia "Conversa". Para obter mais informações, consulte "[Exibir atividade de implantação para um repositório](/repositories/viewing-activity-and-data-for-your-repository/viewing-deployment-activity-for-your-repository)". diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md index c4fa2e1c42..541484ca62 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews.md @@ -20,6 +20,8 @@ shortTitle: Sobre revisões de PR Após a abertura de uma pull request, qualquer pessoa com acesso *de leitura* pode revisar e comentar nas alterações que ela propõe. Você também pode sugerir alterações específicas às linhas de código, que o autor pode aplicar diretamente a partir da pull request. Para obter mais informações, 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)". +{% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %} + Os proprietários de repositório e colaboradores podem solicitar uma revisão de pull request de uma pessoa específica. Os integrantes da organização também podem solicitar uma revisão de pull request de uma equipe com acesso de leitura ao repositório. Para obter mais informações, consulte "[Solicitar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)". {% ifversion fpt or ghae or ghes or ghec %}Você pode especificar um subconjunto de integrantes da equipe que será automaticamente responsável no lugar de toda a equipe. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %} As revisões permitem discussão das alterações propostas e ajudam a garantir que as alterações atendam às diretrizes de contribuição do repositório e outros padrões de qualidade. Você pode definir quais indivíduos ou equipes possuem determinados tipos de área de código em um arquivo CODEOWNERS. Quando uma pull request modifica código que tem um proprietário definido, esse indivíduo ou equipe será automaticamente solicitado como um revisor. Para obter mais informações, consulte "[Sobre proprietários de código](/articles/about-code-owners/)". diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index 4f9c33b6a4..fe56259467 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -160,7 +160,7 @@ Você só pode dar acesso de push a um branch protegido a usuários, equipes ou ### Permitir push forçado -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Por padrão, os blocks do {% data variables.product.product_name %} fazem push forçado em todos os branches protegidos. Ao habilitar push forçado em um branch protegido, você pode escolher um dos dois grupos que podem fazer push forçado: 1. Permitir que todos com, no mínimo, permissões de gravação para que o repositório faça push forçado no branch, incluindo aqueles com permissões de administrador. diff --git a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md index 8db8311954..a83f0d33a3 100644 --- a/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md +++ b/translations/pt-BR/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md @@ -51,7 +51,7 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.repository-branches %} {% data reusables.repositories.add-branch-protection-rules %} -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5506 %} 1. Opcionalmente, habilite os pull requests necessários. - Em "Proteger os branches correspondentes", selecione **Exigir um pull request antes de realizar o merge**. ![Caixa de seleção Pull request review restriction (Restrição de revisão de pull request)](/assets/images/help/repository/PR-reviews-required-updated.png) - Opcionalmente, para exigir aprovações antes que um pull request possa ser mesclado, selecione **Exigir aprovações**, clique no menu suspenso **Número necessário de aprovações antes do merge** e, em seguida, selecione o número de aprovações de revisões que deseja exigir no branch. ![Menu suspenso para selecionar o número de revisões de aprovação obrigatórias](/assets/images/help/repository/number-of-required-review-approvals-updated.png) @@ -62,7 +62,7 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n {% endif %} - Opcionalmente, para ignorar uma revisão de aprovação de pull request quando um commit de modificação de código for enviado por push para o branch, selecione **Ignorar aprovações obsoletas de pull request quando novos commits forem enviados por push**. ![Caixa de seleção Dismiss stale pull request approvals when new commits are pushed (Ignorar aprovações de pull requests obsoletas ao fazer push de novos commits)](/assets/images/help/repository/PR-reviews-required-dismiss-stale.png) - Opcionalmente, para exigir a revisão de um proprietário do código quando o pull request afeta o código que tem um proprietário designado, selecione **Exigir revisão de Proprietários do Código**. Para obter mais informações, consulte "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)". ![Require review from code owners (Exigir revisão de proprietários de código)](/assets/images/help/repository/PR-review-required-code-owner.png) -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5611 %} - Opcionalmente, para permitir que pessoas ou equipes específicas façam push de código para o branch sem estar sujeito às regras de pull request acima, selecione **Permitir que atores específicos ignorem os requisitos de pull request**. Em seguida, pesquise e selecione as pessoas ou equipes que têm permissão para ignorar os requisitos do pull request. ![Permitir que os atores específicos ignorem a caixa de seleção de requisitos de pull request](/assets/images/help/repository/PR-bypass-requirements.png) {% endif %} - Opcionalmente, se o repositório fizer parte de uma organização, selecione **Restringir quem pode ignorar as revisões de pull request**. Em seguida, procure e selecione as pessoas ou equipes que têm permissão para ignorar as revisões de pull request. Para obter mais informações, consulte "[Ignorar uma revisão de pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)". ![Caixa de seleção Restrict who can dismiss pull request reviews (Restringir quem pode ignorar revisões de pull request)](/assets/images/help/repository/PR-review-required-dismissals.png) @@ -88,7 +88,7 @@ Ao criar uma regra de branch, o branch que você especificar ainda não existe n - Selecione **Restringir quem pode fazer push para os branches correspondentes**. ![Caixa de seleção Branch restriction (Restrição de branch)](/assets/images/help/repository/restrict-branch.png) - Procurar e selecionar pessoas, equipes ou aplicativos que tenham permissão para fazer push para o branch protegido. ![Pesquisa de restrição de branch](/assets/images/help/repository/restrict-branch-search.png) 1. Opcionalmente, em "Regras aplicadas a todos incluindo administradores", selecione **Permitir pushes forçados**. ![Permitir opção push forçado](/assets/images/help/repository/allow-force-pushes.png) -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Em seguida, escolha quem pode fazer push forçado no branch. - Selecione **Todos** para permitir que todos com pelo menos permissões de escrita no repositório para forçar push para o branch, incluindo aqueles com permissões de administrador. - Selecione **Especificar quem pode fazer push forçado** para permitir que apenas pessoas ou equipes específicas possam fazer push forçado no branch. Em seguida, procure e selecione essas pessoas ou equipes. ![Captura de tela das opções para especificar quem pode fazer push forçado](/assets/images/help/repository/allow-force-pushes-specify-who.png) diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index af827603ca..899a23d249 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -50,9 +50,14 @@ Para reduzir o tamanho do seu arquivo CODEOWNERS, considere o uso de padrões cu Um arquivo CODEOWNERS usa um padrão que segue a maioria das mesmas regras usadas nos arquivos [gitignore](https://git-scm.com/docs/gitignore#_pattern_format), com [algumas exceções](#syntax-exceptions). O padrão é seguido por um ou mais nomes de usuário ou nomes de equipe do {% data variables.product.prodname_dotcom %} usando o formato padrão `@username` ou `@org/team-name`. Os usuários devem ter acessso de `leitura` ao repositório e as equipes devem ter acesso explícito de `gravação`, mesmo que os integrantes da equipe já tenham acesso. Você também pode se referir a um usuário por um endereço de e-mail que foi adicionado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, por exemplo `user@example.com`. -Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões. - Os caminhos dos CODEOWNERS diferenciam maiúsculas de minúsculas, porque {% data variables.product.prodname_dotcom %} usa um sistema de arquivos que diferencia maiúsculas e minúsculas. Uma vez que os CODEOWNERS são avaliados por {% data variables.product.prodname_dotcom %}, até mesmo sistemas que diferenciam maiúsculas de minúsculas (por exemplo, macOS) devem usar caminhos e arquivos que são tratados corretamente no arquivo dos CODEOWNERS. + +{% if codeowners-errors %} +If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#list-codeowners-errors)" na documentação da API REST. +{% else %} +Se qualquer linha do seu arquivo CODEOWNERS contiver uma sintaxe inválida, o arquivo não será detectado e não será usado para solicitar revisões. +{% endif %} + ### Exemplo de um arquivo CODEOWNERS ``` # Este é um comentário. diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md index 9265423b55..27c1e80c0f 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/index.md @@ -12,6 +12,7 @@ children: - /setting-repository-visibility - /managing-teams-and-people-with-access-to-your-repository - /managing-the-forking-policy-for-your-repository + - /managing-pull-request-reviews-in-your-repository - /managing-git-lfs-objects-in-archives-of-your-repository - /enabling-anonymous-git-read-access-for-a-repository - /about-email-notifications-for-pushes-to-your-repository diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md new file mode 100644 index 0000000000..f45430b860 --- /dev/null +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository.md @@ -0,0 +1,27 @@ +--- +title: Managing pull request reviews in your repository +intro: You can limit which users can approve or request changes to a pull requests in a public repository. +versions: + feature: pull-request-approval-limit +permissions: Repository administrators can limit which users can approve or request changes to a pull request in a public repository. +topics: + - Repositories + - Pull requests +shortTitle: Manage pull request reviews +--- + +## About code review limits + +By default, in public repositories, any user can submit reviews that approve or request changes to a pull request. + +You can limit which users are able to submit reviews that approve or request changes to pull requests in your public repository. When you enable code review limits, anyone can comment on pull requests in your public repository, but only people with read access or higher can approve pull requests or request changes. + +You can also enable code review limits for an organization. If you enable limits for an organization, you will override any limits for individual repositories owned by the organization. For more information, see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)" + +## Enabling code review limits + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. Under **Access**, click **Moderation options**. ![Moderation options repository settings](/assets/images/help/repository/access-settings-repositories.png) +1. Under **Moderation options**, click **Code review limits**. ![Code review limits repositories](/assets/images/help/repository/code-review-limits-repositories.png) +1. Select or deselect **Limit to users explicitly granted read or higher access**. ![Limit review in repository](/assets/images/help/repository/limit-reviews-in-repository.png) diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md index ebc810d46c..cdc2ae4785 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md @@ -9,6 +9,8 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.3' + ghae: issue-5974 topics: - Repositories shortTitle: Equipes & pessoas @@ -20,6 +22,8 @@ Para cada repositório que você administra no {% data variables.product.prodnam Esta visão geral pode ajudá-lo a auditar o acesso ao seu repositório, incluir ou excluir funcionários ou colaboradores, e responder efetivamente aos incidentes de segurança. +{% data reusables.organizations.mixed-roles-warning %} + Para obter mais informações sobre funções do repositório, consulte "[Níveis de permissão para um repositório de conta de usuário](/github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository)" e "[Funções do repositório para uma organização](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)". ![Acessar visão geral do gerenciamento ](/assets/images/help/repository/manage-access-overview.png) @@ -28,21 +32,33 @@ Para obter mais informações sobre funções do repositório, consulte "[Nívei {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} -4. Em "Gerenciar acesso", no campo de busca, comece a digitar o nome da equipe ou pessoa que você gostaria de encontrar. ![Campo de busca para lista de filtros de equipes ou pessoas com acesso](/assets/images/help/repository/manage-access-filter.png) +{% else %} +{% data reusables.repositories.navigate-to-manage-access %} +{% endif %} +1. Em "Gerenciar acesso", no campo de busca, comece a digitar o nome da equipe ou pessoa que você gostaria de encontrar. Optionally, use the dropdown menus to filter your search. ![Campo de busca para lista de filtros de equipes ou pessoas com acesso](/assets/images/help/repository/manage-access-filter.png) ## Alterando as permissões para uma equipe ou pessoa {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} +{% data reusables.repositories.click-collaborators-teams %} +{% else %} {% data reusables.repositories.navigate-to-manage-access %} +{% endif %} 4. Em "Gerenciar acesso", encontre a equipe ou pessoa cuja função você gostaria de alterar. Em seguida, selecione a função suspensa e clique em uma nova função. ![Usando a "Função" menu suspenso para selecionar novas permissões para uma equipe ou pessoa](/assets/images/help/repository/manage-access-role-drop-down.png) ## Convidando uma equipe ou pessoa {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} +{% else %} +{% data reusables.repositories.navigate-to-manage-access %} +{% endif %} {% data reusables.organizations.invite-teams-or-people %} 5. No campo de busca, comece a digitar o nome da equipe ou pessoa para convidar, depois clique em um nome na lista de correspondências. ![Campo de pesquisa para digitar o nome de uma equipe ou pessoa para convidar ao repositório](/assets/images/help/repository/manage-access-invite-search-field.png) 6. Em "Escolher uma função", selecione o a função do repositório para conceder à equipe ou pessoa. Em seguida, clique em **Adicionar NOME ao REPOSITÓRIO**. ![Selecionando permissões para a equipe ou pessoa](/assets/images/help/repository/manage-access-invite-choose-role-add.png) @@ -51,7 +67,11 @@ Para obter mais informações sobre funções do repositório, consulte "[Nívei {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} +{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %} +{% else %} +{% data reusables.repositories.navigate-to-manage-access %} +{% endif %} 4. Em "Gerenciar acesso", localize a equipe ou pessoa cujo acesso você deseja remover e clique em {% octicon "trash" aria-label="The trash icon" %}. ![ícone da lixeira para remover acesso](/assets/images/help/repository/manage-access-remove.png) ## Leia mais diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md index 3c89cdd04b..232f426303 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/about-releases.md @@ -37,30 +37,22 @@ Você pode receber notificações quando novas versões são publicadas em um re Qualquer pessoa com acesso de leitura a um repositório pode ver e comparar versões, mas somente pessoas com permissões de gravação a um repositório podem gerenciar versões. Para obter mais informações, consulte "[Gerenciando versões em um repositório](/github/administering-a-repository/managing-releases-in-a-repository)." {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4974 %} - Você pode criar notas de versão manualmente enquanto gerencia uma versão. Como alternativa, você pode gerar automaticamente notas de versão a partir de um modelo padrão, ou personalizar seu próprio modelo de notas de versão. Para obter mais informações, consulte "[Notas de versão geradas automaticamente](/repositories/releasing-projects-on-github/automatically-generated-release-notes)". - -Pessoas com permissões de administrador para um repositório podem escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. Para obter mais informações, consulte " - -[Gerenciando {% data variables.large_files.product_name_short %} objetos nos arquivos de seu repositório](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)".

- {% endif %} {% ifversion fpt or ghec %} +Pessoas com permissões de administrador para um repositório podem escolher se objetos {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) estão incluídos nos arquivos ZIP e tarballs que {% data variables.product.product_name %} cria para cada versão. For more information, see "[Managing {% data variables.large_files.product_name_short %} objects in archives of your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository)." Se uma versão consertar uma vulnerabilidade de segurança, você deverá publicar uma consultoria de segurança no seu repositório. {% data variables.product.prodname_dotcom %} revisa a cada consultoria de segurança publicado e pode usá-lo para enviar {% data variables.product.prodname_dependabot_alerts %} para repositórios afetados. Para obter mais informações, consulte "[Sobre as consultorias de segurança do GitHub](/github/managing-security-vulnerabilities/about-github-security-advisories)." -Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". - +Você pode visualizar a aba **Dependentes** do gráfico de dependências para ver quais repositórios e pacotes dependem do código no repositório e pode, portanto, ser afetado por uma nova versão. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". {% endif %} Você também pode usar a API de Releases para reunir informações, tais como o número de vezes que as pessoas baixam um ativo de versão. Para obter mais informações, consulte "[Versões](/rest/reference/repos#releases)". {% ifversion fpt or ghec %} - - ## Cotas de armazenamento e banda -Cada arquivo incluído em uma versão deve ser inferior a {% data variables.large_files.max_file_size %}. Não há limite para o tamanho total de uma versão, nem uso de largura de banda. + Cada arquivo incluído em uma versão deve ser inferior a {% data variables.large_files.max_file_size %}. Não há limite para o tamanho total de uma versão, nem uso de largura de banda. {% endif %} diff --git a/translations/pt-BR/content/rest/overview/other-authentication-methods.md b/translations/pt-BR/content/rest/overview/other-authentication-methods.md index 486802515e..228bc546f0 100644 --- a/translations/pt-BR/content/rest/overview/other-authentication-methods.md +++ b/translations/pt-BR/content/rest/overview/other-authentication-methods.md @@ -104,7 +104,7 @@ O valor das `organizações` é uma lista de ID de organizações separada por v Quando você tem a autenticação de dois fatores habilitada, a [Autenticação básica](#basic-authentication) para _a maioria dos_ pontos de extremidade na API REST exige que você use um token de acesso pessoal{% ifversion ghes %} ou token do OAuth em vez do seu nome de usuário e senha{% endif %}. -Você pode gerar um novo token de acesso pessoal {% ifversion fpt or ghec %}usando [ as configurações de desenvolvedor de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} ou com o ponto de extremidade "\[Criar uma nova autorização\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" na API de Autorizações OAuth para gerar um novo token OAuth{% endif %}. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Then you would use these tokens to [authenticate using OAuth token][oauth-auth] with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.{% ifversion ghes %} The only time you need to authenticate with your username and password is when you create your OAuth token or use the OAuth Authorizations API.{% endif %} +Você pode gerar um novo token de acesso pessoal {% ifversion fpt or ghec %}usando [ as configurações de desenvolvedor de {% data variables.product.product_name %}](https://github.com/settings/tokens/new){% endif %}{% ifversion ghes %} ou com o ponto de extremidade "\[Criar uma nova autorização\]\[/rest/reference/oauth-authorizations#create-a-new-authorization\]" na API de Autorizações OAuth para gerar um novo token OAuth{% endif %}. Para obter mais informações, consulte "[Criar um token de acesso pessoal para a linha de comando](/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line)". Em seguida, você usaria esses tokens para [efetuar a autenticação usando o token OAuth token][oauth-auth] com a API de {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %}.{% ifversion ghes %} TA única vez que você deve efetuar a autenticação com o seu nome de usuário e senha é no momento de criar o seu token OAuth ou usar a API de autorizações do OAuth.{% endif %} {% endif %} diff --git a/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md b/translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md index 7fbf8bf758..89f2fb69c0 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 @@ -111,7 +111,7 @@ 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' ``` -Using your `client_id` and `client_secret` does _not_ authenticate as a user, it will only identify your OAuth App to increase your rate limit. 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. Don't leak your OAuth App's client secret to your users. +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 deixe vazar o segredo do cliente do OAuth do seu aplicativo para os seus usuários. {% 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`. Para obter mais informações, consulte "[Habilitar o modo privado](/admin/configuration/configuring-your-enterprise/enabling-private-mode)". @@ -318,19 +318,19 @@ Os valores de `rel` possíveis são: ## Limite de taxa -Different types of API requests to {% data variables.product.product_location %} are subject to different rate limits. +Os diferentes tipos de solicitações de API para {% data variables.product.product_location %} estão sujeitos a diferentes limites de taxa. -Additionally, the Search API has dedicated limits. For more information, see "[Search](/rest/reference/search#rate-limit)" in the REST API documentation. +Além disso, a API de pesquisa tem limites dedicados. Para obter mais informações, consulte "[Pesquisa](/rest/reference/search#rate-limit)" na documentação da API REST. {% data reusables.enterprise.rate_limit %} {% data reusables.rest-api.always-check-your-limit %} -### Requests from user accounts +### Solicitações de contas de usuários -Direct API requests that you authenticate with a personal access token are user-to-server requests. An OAuth App or GitHub App can also make a user-to-server request on your behalf after you authorize the app. For more information, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)," "[Authorizing OAuth Apps](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)," and "[Authorizing GitHub Apps](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)." +Os pedidos diretos da API que você autentica com um token de acesso pessoal são solicitações do usuário para servidor. Um aplicativo OAuth ou GitHub também pode fazer uma solicitação de usuário para servidor em seu nome depois de autorizar o aplicativo. Para obter mais informações, consulte[Criando um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token), "[Autorizando aplicativos OAuth](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)" e "[Autorizando aplicativos GitHub](/authentication/keeping-your-account-and-data-secure/authorizing-github-apps)". -{% data variables.product.product_name %} associates all user-to-server requests with the authenticated user. For OAuth Apps and GitHub Apps, this is the user who authorized the app. All user-to-server requests count toward the authenticated user's rate limit. +{% data variables.product.product_name %} associa todas as solicitações de usuário para servidor ao usuário autenticado. Para aplicativos OAuth e aplicativos GitHub, este é o usuário que autorizou o aplicativo. Todos os pedidos de usuário-servidor contam para o limite de taxa do usuário autenticado. {% data reusables.apps.user-to-server-rate-limits %} @@ -340,31 +340,31 @@ Direct API requests that you authenticate with a personal access token are user- {% ifversion fpt or ghec or ghes %} -Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. Unauthenticated requests are associated with the originating IP address, and not the person making requests. +Para solicitações não autenticadas, o limite de taxa permite até 60 solicitações por hora. As solicitações não autenticadas estão associadas ao endereço IP original, e não à pessoa que faz as solicitações. {% endif %} {% endif %} -### Requests from GitHub Apps +### Solicitações de aplicativos GitHub -Requests from a GitHub App may be either user-to-server or server-to-server requests. For more information about rate limits for GitHub Apps, see "[Rate limits for GitHub Apps](/developers/apps/building-github-apps/rate-limits-for-github-apps)." +As solicitações de um aplicativo GitHub podem ser de usuário para servidor ou de servidor para servidor. Para obter mais informações sobre os limites de taxa para os aplicativos GitHub, consulte "[Limites de taxa para os aplicativos GitHub](/developers/apps/building-github-apps/rate-limits-for-github-apps)". -### Requests from GitHub Actions +### Solicitações do GitHub Actions -You can use the built-in `GITHUB_TOKEN` to authenticate requests in GitHub Actions workflows. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)". +Você pode utilizar o `GITHUB_TOKEN` integrado para autenticar as solicitações nos fluxos de trabalho do GitHub Actions. Para obter mais informações, consulte "[Autenticação automática de tokens](/actions/security-guides/automatic-token-authentication)". -When using `GITHUB_TOKEN`, the rate limit is 1,000 requests per hour per repository.{% ifversion fpt or ghec %} For requests to resources that belong to an enterprise account on {% data variables.product.product_location %}, {% data variables.product.prodname_ghe_cloud %}'s rate limit applies, and the limit is 15,000 requests per hour per repository.{% endif %} +Ao usar `GITHUB_TOKEN`, o limite de taxa é de 1.000 solicitações por hora por repositório.{% ifversion fpt or ghec %} Para solicitações de recursos que pertencem a uma conta corporativa em {% data variables.product.product_location %}, aplicam-se os limites de taxa de {% data variables.product.prodname_ghe_cloud %} e o limite é de 15.000 solicitações por hora por repositório.{% endif %} -### Checking your rate limit status +### Verificando o status do seu limite da taxa -The Rate Limit API and a response's HTTP headers are authoritative sources for the current number of API calls available to you or your app at any given time. +A API de limite de taxa e os cabeçalhos HTTP de uma resposta são fontes autorizadas para o número atual de chamadas de API disponíveis para você ou seu aplicativo a qualquer momento. -#### Rate Limit API +#### API de limite de taxa -You can use the Rate Limit API to check your rate limit status without incurring a hit to the current limit. For more information, see "[Rate limit](/rest/reference/rate-limit)." +Você pode usar a API do limite de taxa para verificar o status do seu limite de taxa sem impactar no limite atual. Para obter mais informações, consulte "[Limite de taxa](/rest/reference/rate-limit)". -#### Rate limit HTTP headers +#### Cabeçalhos de HTTP de limite de taxa Os cabeçalhos HTTP retornados de qualquer solicitação de API mostram o seu status atual de limite de taxa: @@ -405,9 +405,9 @@ Se você exceder o limite de taxa, uma resposta do erro retorna: > } ``` -### Increasing the unauthenticated rate limit for OAuth Apps +### Aumentando o limite de taxa não autenticado para aplicativos OAuth -If your OAuth App needs to make unauthenticated calls with a higher rate limit, you can pass your app's client ID and secret before the endpoint route. +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. ```shell $ curl -u my_client_id:my_client_secret {% data variables.product.api_url_pre %}/user/repos diff --git a/translations/pt-BR/content/rest/reference/codespaces.md b/translations/pt-BR/content/rest/reference/codespaces.md index 6db2829805..79373723ca 100644 --- a/translations/pt-BR/content/rest/reference/codespaces.md +++ b/translations/pt-BR/content/rest/reference/codespaces.md @@ -1,6 +1,6 @@ --- title: Codespaces -intro: 'The {% data variables.product.prodname_codespaces %} API enables you to manage your codespaces using the REST API.' +intro: 'A API de {% data variables.product.prodname_codespaces %} permite que você gerencie seus codespaces usando a API REST.' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,22 +12,22 @@ miniTocMaxHeadingLevel: 3 {% data reusables.codespaces.codespaces-api-beta-note %} -A API de {% data variables.product.prodname_codespaces %} permite que você gerencie {% data variables.product.prodname_codespaces %} usando a API REST. This API is available for authenticated users and OAuth Apps, but not GitHub Apps. Para obter mais informações, consulte "[{% data variables.product.prodname_codespaces %}](/codespaces)". +A API de {% data variables.product.prodname_codespaces %} permite que você gerencie {% data variables.product.prodname_codespaces %} usando a API REST. Esta API está disponível para usuários autenticados e aplicativos OAuth, mas não para aplicativos GitHub. Para obter mais informações, consulte "[{% data variables.product.prodname_codespaces %}](/codespaces)". {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} -## Machines -The Machines API allows a user to determine which machine types are available to create a codespace, either on a given repository or as an authenticated user. For more information, see "[About machine types](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)." +## Máquinas +A API de Máquinas permite que um usuário determine quais tipos de máquina estão disponíveis para criar um codespace, seja em um determinado repositório ou como um usuário autenticado. Para obter mais informações, consulte "[Sobre tipos de máquinas](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace#about-machine-types)". -You can also use this information when changing the machine of an existing codespace by updating its `machine` property. The machine update will take place the next time the codespace is restarted. For more information, see "[Changing the machine type for your codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)." +Você também pode usar essas informações alterando a máquina de um codespace existente, atualizando a propriedade `máquina`. A atualização da máquina ocorrerá na próxima vez que o codespace for reiniciado. Para obter mais informações, consulte "["Mudar o tipo de máquina para seu codespace](/codespaces/developing-in-codespaces/changing-the-machine-type-for-your-codespace)." {% for operation in currentRestOperations %} {% if operation.subcategory == 'machines' %}{% include rest_operation %}{% endif %} {% endfor %} ## Segredos -The Secrets API allows a user to create, list, and delete secrets (such as access tokens for cloud services) as well as assign secrets to repositories that the user has access to. These secrets are made available to the codespace at runtime. For more information, see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)." +A API de Segredos permite que um usuário crie, liste e exclua segredos (como tokens de acesso para serviços de nuvem), além de atribuir segredos para repositórios aos quais o usuário tem acesso. Estes segredos são disponibilizados para o codespace em tempo de execução. Para obter mais informações, consulte "[Gerenciar segredos criptografados para seus codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)". {% for operation in currentRestOperations %} {% if operation.subcategory == 'secrets' %}{% include rest_operation %}{% endif %} {% endfor %} diff --git a/translations/pt-BR/content/rest/reference/gitignore.md b/translations/pt-BR/content/rest/reference/gitignore.md index acb84167cf..739dd8cbb8 100644 --- a/translations/pt-BR/content/rest/reference/gitignore.md +++ b/translations/pt-BR/content/rest/reference/gitignore.md @@ -13,7 +13,7 @@ topics: miniTocMaxHeadingLevel: 3 --- -When you create a new repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} via the API, you can specify a [.gitignore template](/github/getting-started-with-github/ignoring-files) to apply to the repository upon creation. A API de modlos do .gitignore lista e recupera modelos do repositório de [.gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}. +Ao criar um novo repositório em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} por meio da API, você pode especificar um [.gitignore template](/github/getting-started-with-github/ignoring-files) para que seja aplicado ao repositório após a criação. A API de modlos do .gitignore lista e recupera modelos do repositório de [.gitignore](https://github.com/github/gitignore) de {% data variables.product.product_name %}. ### Tipos de mídia personalizados para gitignore diff --git a/translations/pt-BR/content/rest/reference/migrations.md b/translations/pt-BR/content/rest/reference/migrations.md index 3ed320a489..5b192e8a74 100644 --- a/translations/pt-BR/content/rest/reference/migrations.md +++ b/translations/pt-BR/content/rest/reference/migrations.md @@ -8,6 +8,8 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '>3.3' + ghae: issue-6184 topics: - API miniTocMaxHeadingLevel: 3 @@ -27,6 +29,7 @@ A API de migrações só está disponível para os proprietários de organizaç {% if operation.subcategory == 'orgs' %}{% include rest_operation %}{% endif %} {% endfor %} +{% ifversion fpt or ghec %} ## Importações de código-fonte {% data variables.migrations.source_imports_intro %} @@ -111,7 +114,7 @@ Um exemplo mais detalhado pode ser visto neste diagrama: {% for operation in currentRestOperations %} {% if operation.subcategory == 'source-imports' %}{% include rest_operation %}{% endif %} {% endfor %} - +{% endif %} ## Usuário A API de migrações do usuário só está disponível para proprietários de contas autenticadas. Para obter mais informações, consulte "[Outros métodos de autenticação](/rest/overview/other-authentication-methods)". diff --git a/translations/pt-BR/content/rest/reference/pages.md b/translations/pt-BR/content/rest/reference/pages.md index 2ace83a091..7d95cfc619 100644 --- a/translations/pt-BR/content/rest/reference/pages.md +++ b/translations/pt-BR/content/rest/reference/pages.md @@ -27,7 +27,7 @@ Nos pontos de extremidade da API de {% data variables.product.prodname_pages %} - `branch`: O branch do repositório utilizado para publicar os [arquivos de origem do site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site). Por exemplo, _principal_ ou _gh-pages_. - `path`: O diretório do repositório a partir do qual o site é publicado. Será `/` ou `/docs`. -{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %} +{% comment %}É necessária uma linha em branco adicional aqui para garantir que as operações abaixo não deem continuidade à lista acima.{% endcomment %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} diff --git a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md index dbd118c949..aafc594d8c 100644 --- a/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md +++ b/translations/pt-BR/content/rest/reference/permissions-required-for-github-apps.md @@ -348,6 +348,9 @@ _Tráfego_ - [`GET /repos/:owner/:repo/check-suites/:check_suite_id`](/rest/reference/checks#get-a-check-suite) (:read) - [`GET /repos/:owner/:repo/check-suites/:check_suite_id/check-runs`](/rest/reference/checks#list-check-runs-in-a-check-suite) (:read) - [`POST /repos/:owner/:repo/check-suites/:check_suite_id/rerequest`](/rest/reference/checks#rerequest-a-check-suite) (:write) +{% if codeowners-errors %} +- [`GET /repos/:owner/:repo/codeowners/errors`](/rest/reference/repos#list-codeowners-errors) (:read) +{% endif %} - [`GET /repos/:owner/:repo/commits`](/rest/reference/commits#list-commits) (:read) - [`GET /repos/:owner/:repo/commits/:sha`](/rest/reference/commits#get-a-commit) (:read) - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read) @@ -876,7 +879,7 @@ _Equipes_ {% endif %} {% ifversion fpt or ghec or ghes > 3.3%} -### Permission on "dependabot_secrets" +### Permissão em "dependabot_secrets" - [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read) - [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read) - [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read) diff --git a/translations/pt-BR/content/rest/reference/rate-limit.md b/translations/pt-BR/content/rest/reference/rate-limit.md index bb73829459..d95ccfe6f5 100644 --- a/translations/pt-BR/content/rest/reference/rate-limit.md +++ b/translations/pt-BR/content/rest/reference/rate-limit.md @@ -30,6 +30,6 @@ Por esses motivos, a resposta da API do limite de taxa categoriza o seu limite d * O objeto `integration_manifest` fornece o status do limite de taxa para o ponto de extremidade [Conversão do código de manifesto do aplicativo GitHub](/apps/building-github-apps/creating-github-apps-from-a-manifest/#3-you-exchange-the-temporary-code-to-retrieve-the-app-configuration). -For more information on the headers and values in the rate limit response, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)." +Para obter mais informações sobre os cabeçalhos e valores na resposta de limite de taxa, consulte "[Recursos na API REST](/rest/overview/resources-in-the-rest-api#rate-limit-http-headers)". {% include rest_operations_at_current_path %} diff --git a/translations/pt-BR/content/rest/reference/search.md b/translations/pt-BR/content/rest/reference/search.md index 42a79f1e23..cd1854c509 100644 --- a/translations/pt-BR/content/rest/reference/search.md +++ b/translations/pt-BR/content/rest/reference/search.md @@ -51,7 +51,7 @@ GitHub Octocat in:readme user:defunkt const queryString = 'q=' + encodeURIComponent('GitHub Octocat in:readme user:defunkt'); ``` -See "[Searching on GitHub](/search-github/searching-on-github)" for a complete list of available qualifiers, their format, and an example of how to use them. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)". +Consulte "[Pesquisar no GitHub](/search-github/searching-on-github)" para obter uma lista completa de qualificadores disponíveis, seu formato e um exemplo de como usá-los. Para obter informações sobre como usar operadores para corresponder a quantidades e datas específicas ou para excluir resultados, consulte "[Entender a sintaxe de pesquisa](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax/)". ### Limitações no tamanho da consulta @@ -69,7 +69,7 @@ Atingir um tempo limite não significa necessariamente que os resultados da pesq ### Erros de acesso ou resultados de pesquisa ausentes -You need to successfully authenticate and have access to the repositories in your search queries, otherwise, you'll see a `422 Unprocessable Entry` error with a "Validation Failed" message. Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores `repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}. +Você precisa efetuar a autenticação com sucesso e ter acesso aos repositórios nas consultas de pesquisa. Caso contrário, você verá um erro `422 Unprocessable Entry` com uma mensagem "Falha na validação". Por exemplo, sua pesquisa irá falhar se sua consulta incluir qualificadores `repo:`, `user:` ou `org:` que solicitam recursos aos quais você não tem acesso ao efetuar login em {% data variables.product.prodname_dotcom %}. Quando sua consulta de pesquisa solicitar vários recursos, a resposta só conterá os recursos aos quais você tem acesso e **não** fornecerá uma mensagem de erro listando os recursos que não foram retornados. diff --git a/translations/pt-BR/content/rest/reference/secret-scanning.md b/translations/pt-BR/content/rest/reference/secret-scanning.md index 37b88c6e0d..a5f3e0390b 100644 --- a/translations/pt-BR/content/rest/reference/secret-scanning.md +++ b/translations/pt-BR/content/rest/reference/secret-scanning.md @@ -11,11 +11,11 @@ miniTocMaxHeadingLevel: 3 {% data reusables.secret-scanning.api-beta %} -The {% data variables.product.prodname_secret_scanning %} API lets you{% ifversion fpt or ghec or ghes > 3.1 or ghae %}: +A API de {% data variables.product.prodname_secret_scanning %} permite que você{% ifversion fpt or ghec or ghes > 3.1 or ghae %}: -- Enable or disable {% data variables.product.prodname_secret_scanning %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" in the REST API documentation. -- Retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository. For futher details, see the sections below. -{%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a {% ifversion fpt or ghec %}private {% endif %}repository.{% endif %} +- Habilitar ou desabilitar {% data variables.product.prodname_secret_scanning %} para um repositório. Para obter mais informações, consulte "[Repositórios](/rest/reference/repos#update-a-repository)" na documentação da API REST. +- Recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado {% endif %}. Para obter detalhes adicionais, consulte as seções abaixo. +{%- else %} recuperar e atualizar alertas de {% data variables.product.prodname_secret_scanning %} a partir de um repositório {% ifversion fpt or ghec %}privado{% endif %}.{% endif %} Para obter mais informações sobre {% data variables.product.prodname_secret_scanning %}, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)." diff --git a/translations/pt-BR/content/rest/reference/teams.md b/translations/pt-BR/content/rest/reference/teams.md index 025911e294..d5790631d3 100644 --- a/translations/pt-BR/content/rest/reference/teams.md +++ b/translations/pt-BR/content/rest/reference/teams.md @@ -53,9 +53,9 @@ Esta API só está disponível para os integrantes autenticados da organização {% endfor %} {% ifversion ghec or ghae %} -## External groups +## Grupos externos -The external groups API allows you to view the external identity provider groups that are available to your organization and manage the connection between external groups and teams in your organization. +A API de grupos externos permite que você visualize os grupos de provedores de identidade externos que estão disponíveis para sua organização e gerencie a conexão entre grupos externos e equipes na sua organização. Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou um proprietário da organização associada à equipe. @@ -64,8 +64,8 @@ Para usar esta API, o usuário autenticado deve ser um mantenedor de equipe ou u **Notas:** -- The external groups API is only available for organizations that are part of a enterprise using {% data variables.product.prodname_emus %}. For more information, see "[About Enterprise Managed Users](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." -- If your organization uses team synchronization, you can use the Team Synchronization API. For more information, see "[Team synchronization API](#team-synchronization)." +- A API de grupos externos está disponível apenas para organizações que fazem parte de uma empresa que usa {% data variables.product.prodname_emus %}. Para obter mais informações, consulte[Sobre usuários gerenciados pela empresa](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)". +- Se sua organização usar a sincronização de equipe, você poderá usar a API de sincronização de equipe. Para obter mais informações, consulte "[API de sincronização de equipe](#team-synchronization)". {% endnote %} {% endif %} @@ -85,7 +85,7 @@ Você pode gerenciar os integrantes da equipe do GitHub através do seu IdP com {% note %} -**Observação:** A API de sincronização de equipe não pode ser usada com {% data variables.product.prodname_emus %}. To learn more about managing an {% data variables.product.prodname_emu_org %}, see "[External groups API](/enterprise-cloud@latest/rest/reference/teams#external-groups)". +**Observação:** A API de sincronização de equipe não pode ser usada com {% data variables.product.prodname_emus %}. Para saber mais sobre como gerenciar um {% data variables.product.prodname_emu_org %}, consulte "[API de grupos externos](/enterprise-cloud@latest/rest/reference/teams#external-groups)". {% endnote %} diff --git a/translations/pt-BR/content/rest/reference/webhooks.md b/translations/pt-BR/content/rest/reference/webhooks.md index 7a86457037..be3c51cfe1 100644 --- a/translations/pt-BR/content/rest/reference/webhooks.md +++ b/translations/pt-BR/content/rest/reference/webhooks.md @@ -1,6 +1,6 @@ --- title: Webhooks -intro: The webhooks API allows you to create and manage webhooks for your repositories. +intro: A API de webhooks permite que você crie e gerencie webhooks para seus repositórios. allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -28,13 +28,13 @@ Além da API REST, {% data variables.product.prodname_dotcom %} também pode ser {% if operation.subcategory == 'repos' %}{% include rest_operation %}{% endif %} {% endfor %} -## Repository webhook configuration +## Configuração de webhook do repositório {% for operation in currentRestOperations %} {% if operation.subcategory == 'repo-config' %}{% include rest_operation %}{% endif %} {% endfor %} -## Repository webhook deliveries +## Entregas do webhook do repositório {% for operation in currentRestOperations %} {% if operation.subcategory == 'repo-deliveries' %}{% 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 d3726ecb17..59ce5d5937 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 @@ -56,7 +56,7 @@ Você pode pesquisar as seguintes informações em todos os repositórios que vo ## Pesquisar usando uma interface visual -You can search {% data variables.product.product_name %} using the {% data variables.search.search_page_url %} or {% data variables.search.advanced_url %}. {% if command-palette %}Alternatively, you can use the interactive search in the {% data variables.product.prodname_command_palette %} to search your current location in the UI, a specific user, repository or organization, and globally across all of {% data variables.product.product_name %}, without leaving the keyboard. For more information, see "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)."{% endif %} +Você pode pesquisar {% data variables.product.product_name %} usando o {% data variables.search.search_page_url %} ou {% data variables.search.advanced_url %}. {% if command-palette %}Como alternativa, você pode usar a pesquisa interativa no {% data variables.product.prodname_command_palette %} para pesquisar sua localização atual na interface do usuário, um usuário, repositório ou organização específico e globalmente em todo o {% data variables.product.product_name %}, sem deixar o teclado. Para obter mais informações, consulte "[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)".{% endif %} A {% data variables.search.advanced_url %} fornece uma interface visual para construção de consultas de pesquisa. Você pode filtrar as pesquisas por diversos fatores, como o número de estrelas ou o número de bifurcações que um repositório tem. À medida que você preenche os campos de pesquisa avançada, sua consulta é automaticamente construída na barra de pesquisa superior. @@ -66,12 +66,12 @@ A {% data variables.search.advanced_url %} fornece uma interface visual para con ## Pesquisando repositórios em {% data variables.product.prodname_dotcom_the_website %} a partir do seu ambiente corporativo privado -If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} or {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} and you're a member of a {% data variables.product.prodname_dotcom_the_website %} organization using {% data variables.product.prodname_ghe_cloud %}, an enterprise owner for your {% data variables.product.prodname_enterprise %} environment can enable {% data variables.product.prodname_github_connect %} so that you can search across both environments at the same time{% ifversion ghes or ghae %} from {% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte o seguinte. +Se você usar {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %} ou {% data variables.product.prodname_ghe_managed %}{% else %}{% data variables.product.product_name %}{% endif %} e você for um membro de uma organização de {% data variables.product.prodname_dotcom_the_website %} que estiver usando {% data variables.product.prodname_ghe_cloud %}, o proprietário de uma empresa para o seu ambiente de {% data variables.product.prodname_enterprise %} poderá habilitar {% data variables.product.prodname_github_connect %} para que você possa pesquisar em ambos os ambientes ao mesmo tempo{% ifversion ghes or ghae %} a partir de {% data variables.product.product_name %}{% endif %}. Para obter mais informações, consulte o seguinte. {% ifversion fpt or ghes or ghec %} -- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %} -- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_managed %} documentation +- "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" na documentação de {% data variables.product.prodname_ghe_server %}{% endif %} +- "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" na documentação de {% data variables.product.prodname_ghe_managed %} {% ifversion ghes or ghae %} 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 2abd4e300c..db23b0da41 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 @@ -25,8 +25,8 @@ Você pode pesquisar repositórios privados designados em {% data variables.prod ## Pré-requisitos - Um proprietário de empresa para {% ifversion fpt or ghec %}seu ambiente {% data variables.product.prodname_enterprise %} privado{% else %}{% data variables.product.product_name %}{% endif %} deve habilitar {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_unified_search %} para repositórios privados. Para obter mais informações, consulte o seguinte.{% ifversion fpt or ghes or ghec %} - - "\[Enabling {% data variables.product.prodname_unified_search %} for your enterprise\](/{% ifversion not ghes %}enterprise-server@latest/{% endif %}admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %} - - "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise}](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %} + - "\[Habilitando {% data variables.product.prodname_unified_search %} for your enterprise\](/{% ifversion not ghes %}enterprise-server@latest/{% endif %}admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise"{% ifversion fpt or ghec %} na documentação de {% data variables.product.prodname_ghe_server %}{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %} + - "[Habilitando {% data variables.product.prodname_unified_search %} para a sua empresa}](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"{% ifversion fpt or ghec %} na documentação de {% data variables.product.prodname_ghe_managed %}{% endif %} {% endif %} - Você já deve ter acesso aos repositórios privados e conectar sua conta {% ifversion fpt or ghec %}no seu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}em {% data variables.product.product_name %}{% endif %} com sua conta em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações sobre os repositórios que você pode pesquisar, consulte "[Sobre pesquisa no GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)". @@ -37,10 +37,10 @@ Você pode pesquisar repositórios privados designados em {% data variables.prod Para obter mais informações, consulte o seguinte. -| Seu ambiente corporativo | Mais informações | -|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% data variables.product.prodname_ghe_server %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" | -| {% data variables.product.prodname_ghe_managed %} | "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search from your private enterprise environment](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" | +| Seu ambiente corporativo | Mais informações | +|:--------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% data variables.product.prodname_ghe_server %} | "[Habilitando a pesquisa de repositório de {% data variables.product.prodname_dotcom_the_website %} a partir do seu ambiente corporativo privado](/enterprise-server@latest/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-enterprise-server)" | +| {% data variables.product.prodname_ghe_managed %} | "[Habilitando a pesquisa de repositório de {% data variables.product.prodname_dotcom_the_website %} a partir do seu ambiente corporativo privado](/github-ae@latest//search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment#enabling-githubcom-repository-search-from-github-ae)" | {% elsif ghes or ghae %} diff --git a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md index 5f775de933..a72bdc707e 100644 --- a/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md +++ b/translations/pt-BR/content/search-github/getting-started-with-searching-on-github/sorting-search-results.md @@ -47,19 +47,19 @@ O qualificador `sort:reactions` ordena pelo número ou tipo de reações. O qualificador `sort:author-date` ordena de forma crescente ou decrescente por data de criação. -| Qualifier | Exemplo | -| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sort:author-date` ou `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data de criação. | -| `sort:author-date-asc` | [**`feature org:github sort:author-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending author date. | +| Qualifier | Exemplo | +| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:author-date` ou `sort:author-date-desc` | [**feature org:github sort:author-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data de criação. | +| `sort:author-date-asc` | [**`feature org:github sort:author-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Aauthor-date-asc&type=Commits) corresponde a commits que contêm a palavra "recurso" nos repositórios pertencentes a {% data variables.product.product_name %}, ordenado pela data crescente de criação. | ## Ordenar por data do committer O qualificador `sort:committer-date` ordena de forma crescente ou decrescente por data do committer. -| Qualifier | Exemplo | -| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `sort:committer-date` ou `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data do committer. | -| `sort:committer-date-asc` | [**`feature org:github sort:committer-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) matches commits containing the word "feature" in repositories owned by {% data variables.product.product_name %}, sorted by ascending committer date. | +| Qualifier | Exemplo | +| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `sort:committer-date` ou `sort:committer-date-desc` | [**feature org:github sort:committer-date**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date&type=Commits) identifica os commits que contêm a palavra "feature" nos repositórios do {% data variables.product.product_name %} ordenados de forma decrescente por data do committer. | +| `sort:committer-date-asc` | [**`feature org:github sort:committer-date-asc`**](https://github.com/search?utf8=%E2%9C%93&q=feature+org%3Agithub+sort%3Acommitter-date-asc&type=Commits) corresponde a commits que contêm a palavra "recurso" nos repositórios pertencentes a {% data variables.product.product_name %}, classificado por data crescente do committer. | ## Ordenar por data da atualização 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 69d1573bb1..eef236ee15 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 @@ -73,10 +73,10 @@ Usando a sintaxe `NOT`, é possível excluir resultados contendo uma determinada Outra maneira de restringir os resultados da pesquisa é excluir determinados subconjuntos. Adicione um prefixo a qualquer qualificador de pesquisa com um `-` para excluir todos os resultados correspondentes a esse qualificador. -| Consulta | Exemplo | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| -QUALIFIER | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** matches repositories with the word "cats" that have more than 10 stars but are not written in JavaScript. | -| | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** matches issues mentioning @defunkt that are not in repositories in the GitHub organization | +| Consulta | Exemplo | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| -QUALIFIER | **[`cats stars:>10 -language:javascript`](https://github.com/search?q=cats+stars%3A>10+-language%3Ajavascript&type=Repositories)** corresponde repositórios com a palavra "cats" com mais de 10 estrelas, mas que não estão gravados no JavaScript. | +| | **[`mentions:defunkt -org:github`](https://github.com/search?utf8=%E2%9C%93&q=mentions%3Adefunkt+-org%3Agithub&type=Issues)** corresponde problemas que mencionam @defunkt que não estão em repositórios na organização do GitHub | ## Usar aspas para consultas com espaço em branco diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-code.md b/translations/pt-BR/content/search-github/searching-on-github/searching-code.md index 2fff3a4405..274d5b62cb 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-code.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-code.md @@ -62,11 +62,11 @@ Para pesquisar códigos em todos os repositórios de um determinado usuário ou Você pode usar o qualificador `path` para pesquisar o código-fonte que aparece em um local específico de um repositório. Use o `path:/` para pesquisar os arquivos que estão no diretório raiz de um repositório. Ou especifique o nome ou o caminho do diretório para pesquisar os arquivos presentes nesse diretório e em seus subdiretórios. -| Qualifier | Exemplo | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) identifica os arquivos _readme_ com a palavra "octocat" localizados no diretório raiz de um repositório. | -| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) corresponde a arquivos Perl com a palavra "form" no diretório cgi-bin ou em qualquer um dos seus subdiretórios. | -| path:PATH/TO/DIRECTORY | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) matches JavaScript files with the word "console" in the app/public directory, or in any of its subdirectories (even if they reside in app/public/js/form-validators). | +| Qualifier | Exemplo | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| path:/ | [**octocat filename:readme path:/**](https://github.com/search?utf8=%E2%9C%93&q=octocat+filename%3Areadme+path%3A%2F&type=Code) identifica os arquivos _readme_ com a palavra "octocat" localizados no diretório raiz de um repositório. | +| path:DIRECTORY | [**form path:cgi-bin language:perl**](https://github.com/search?q=form+path%3Acgi-bin+language%3Aperl&type=Code) corresponde a arquivos Perl com a palavra "form" no diretório cgi-bin ou em qualquer um dos seus subdiretórios. | +| path:PATH/TO/DIRECTORY | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) corresponde arquivos do JavaScript com a palavra "console" no diretório app/public ou em qualquer um dos seus subdiretórios (ainda que residam em app/public/js/form-validators). | ## Pesquisar por linguagem diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md index 6bbc8f674b..bf4f04a75c 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-commits.md @@ -109,10 +109,10 @@ O qualificador `is` corresponde a commits dos repositórios com a visibilidade e | --------- | ------- | | | | {%- ifversion fpt or ghes or ghec %} -| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories. +| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) corresponde os commits aos repositórios públicos. {%- endif %} {%- ifversion ghes or ghec or ghae %} -| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories. +| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) corresponde commits a repositórios internos. {%- endif %} | `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) corresponde aos commits dos repositórios privados. diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md index 575e2d6054..59b9011e3a 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-discussions.md @@ -41,7 +41,7 @@ Para pesquisar discussões em todos os repositórios pertencentes a um determina Você pode filtrar pela visibilidade do repositório que contém as discussões que usam o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -| Qualifier | Example | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) matches discussions in public repositories.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) matches discussions in internal repositories.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) matches discussions that contain the word "tiramisu" in private repositories you can access. +| Qualificador | Exemplo | :- | :- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Discussions) corresponde discussões em repositórios públicos.{% endif %}{% ifversion ghec %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Discussions) corresponde discussões em repositórios internos.{% endif %} | `is:private` | [**is:private tiramisu**](https://github.com/search?q=is%3Aprivate+tiramisu&type=Discussions) corresponde discussões que contêm a palavra "tiramisu" nos repositórios privados que você pode acessar. ## Pesquisar por autor diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md index 9ceef1cdfe..886e6b2676 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-packages.md @@ -31,10 +31,10 @@ Você só pode procurar por pacotes em {% data variables.product.product_name %} Para encontrar pacotes que pertencem a um determinado usuário ou organização, use o `usuário` ou `org` qualificador. -| Qualifier | Exemplo | -| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| user:USERNAME | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) matches packages owned by @codertocat | -| org:ORGNAME | [**`org:github`**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) matches packages owned by the {% data variables.product.prodname_dotcom %} organization | +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| user:USERNAME | [**`user:codertocat`**](https://github.com/search?q=user%3Acodertocat&type=RegistryPackages) corresponde pacotes pertencentes ao @codertocat | +| org:ORGNAME | [**`org:github`**](https://github.com/search?q=org%3Agithub&type=RegistryPackages) corresponde pacotes pertencentes à organização de {% data variables.product.prodname_dotcom %} ## Filtrar por visibilidade do pacote 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 436dab7b2a..e8fa32f3b5 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 @@ -111,17 +111,17 @@ Os dois usam uma data como parâmetro. {% data reusables.time_date.date_format % Você pode pesquisar repositórios com base na linguagem do código nos repositórios. -| Qualifier | Exemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) matches repositories with the word "rails" that are written in JavaScript. | +| Qualifier | Exemplo | +| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| language:LANGUAGE | [**`rails language:javascript`**](https://github.com/search?q=rails+language%3Ajavascript&type=Repositories) corresponde reposit´rios com a palavra "rails" gravaddos no JavaScript. | ## Pesquisar por tópico Você pode encontrar todos os repositórios classificados com um determinado tópico. Para obter mais informações, consulte "[Classificar seu repositório com tópicos](/github/administering-a-repository/classifying-your-repository-with-topics)". -| Qualifier | Exemplo | -| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| topic:TOPIC | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) matches repositories that have been classified with the topic "Jekyll." | +| Qualifier | Exemplo | +| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| topic:TOPIC | [**`topic:jekyll`**](https://github.com/search?utf8=%E2%9C%93&q=topic%3Ajekyll&type=Repositories&ref=searchresults) corresponde repositórios classificados com o tópico "Jekyll". | ## Pesquisar por número de tópicos @@ -148,7 +148,7 @@ Você pode pesquisar repositórios pelo tipo de licença nos repositórios. É p Você pode filtrar sua pesquisa com base na visibilidade dos repositórios. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) matches public repositories owned by {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) matches internal repositories that you can access and contain the word "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) matches private repositories that you can access and contain the word "pages." +| Qualificador | Exemplo | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public org:github**](https://github.com/search?q=is%3Apublic+org%3Agithub&type=Repositories) corresponde repositórios públicos pertencentes a {% data variables.product.company_short %}.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal test**](https://github.com/search?q=is%3Ainternal+test&type=Repositories) corresponde repositórios internos que você pode acessar e que contêm a palavra "test".{% endif %} | `is:private` | [**is:private pages**](https://github.com/search?q=is%3Aprivate+pages&type=Repositories) corresponde repositórios privados que você pode acessar e que contêm a palavra "pages." {% ifversion fpt or ghec %} @@ -178,10 +178,10 @@ Você pode pesquisar repositórios com base no fato de os repositórios estarem Você pode pesquisar repositórios que têm um número mínimo de problemas com as etiquetas `help-wanted` (procura-se ajuda) ou `good-first-issue` (um bom primeiro problema) com os qualificadores `help-wanted-issues:>n` e `good-first-issues:>n`. Para obter mais informações, consulte "[Incentivar contribuições úteis para o seu projeto com etiquetas](/communities/setting-up-your-project-for-healthy-contributions/encouraging-helpful-contributions-to-your-project-with-labels)". -| Qualifier | Exemplo | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `good-first-issues:>n` | [**`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) matches repositories with more than two issues labeled `good-first-issue` and that contain the word "javascript." | -| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) identifica os repositórios com mais de quatro problemas com a etiqueta `help-wanted` e que contêm a palavra "React". | +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `good-first-issues:>n` | [**`good-first-issues:>2 javascript`**](https://github.com/search?utf8=%E2%9C%93&q=javascript+good-first-issues%3A%3E2&type=) corresponde repositórios com mais de dois problemas etiquetados como `good-first-issue` e que contêm a palavra "javascript." | +| `help-wanted-issues:>n` | [**help-wanted-issues:>4 react**](https://github.com/search?utf8=%E2%9C%93&q=react+help-wanted-issues%3A%3E4&type=) identifica os repositórios com mais de quatro problemas com a etiqueta `help-wanted` e que contêm a palavra "React". | ## Pesquisar com base na capacidade de patrocinador diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md b/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md index 87f510b0d1..54d44e0c56 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-in-forks.md @@ -1,6 +1,6 @@ --- title: Pesquisar em bifurcações -intro: 'By default, [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) are not shown in search results. Você poderá optar por incluí-las nas pesquisas de repositórios e nas pesquisas de códigos se elas atenderem a determinados critérios.' +intro: 'Por padrão, [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) não são exibidas nos resultados de pesquisas. Você poderá optar por incluí-las nas pesquisas de repositórios e nas pesquisas de códigos se elas atenderem a determinados critérios.' redirect_from: - /articles/searching-in-forks - /github/searching-for-information-on-github/searching-in-forks 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 be4afcb494..e98acad006 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 @@ -79,7 +79,7 @@ Você pode filtrar somente problemas e pull requests abertos ou fechados usando É possível filtrar pela visibilidade do repositório que contém os problemas e pull requests usando o qualificador `is`. Para obter mais informações, consulte "[Sobre repositórios](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)". -| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) matches issues and pull requests in public repositories.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) matches issues and pull requests in internal repositories.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) matches issues and pull requests that contain the word "cupcake" in private repositories you can access. +| Qualifier | Example | ------------- | ------------- |{% ifversion fpt or ghes or ghec %} | `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Issues) corresponde problemas e pull requests em repositórios públicos.{% endif %}{% ifversion ghes or ghec or ghae %} | `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Issues) corresponde problemas e pull requests em repositórios internos.{% endif %} | `is:private` | [**is:private cupcake**](https://github.com/search?q=is%3Aprivate+cupcake&type=Issues) corresponde problemas e pull requests que contêm a palavra "cupcake" nos repositórios privados que você pode acessar. ## Pesquisar por autor @@ -103,9 +103,9 @@ O qualificador `assignee` encontra problemas e pull requests que foram atribuíd O qualificador `mentions` encontra problemas que mencionam um usuário específico. Para obter mais informações, consulte "[Mencionar pessoas e equipes](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)". -| Qualifier | Exemplo | -| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| mentions:USERNAME | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) matches issues with the word "resque" that mention @defunkt. | +| Qualifier | Exemplo | +| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| mentions:USERNAME | [**`resque mentions:defunkt`**](https://github.com/search?q=resque+mentions%3Adefunkt&type=Issues) corresponde problemas com a palavra "resque" que menciona @defunkt. | ## Pesquisar por menção da equipe @@ -113,7 +113,7 @@ Para organizações e equipes das quais você faz parte, você pode usar o quali | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------- | -| team:ORGNAME/TEAMNAME | **`team:jekyll/owners`** matches issues where the `@jekyll/owners` team is mentioned. | +| team:ORGNAME/TEAMNAME | **`team:jekyll/owners`** corresponde problemas em que a equipe `@jekyll/owners` é mencionada. | | | **team:myorg/ops is:open is:pr** corresponde pull requests abertos em que a equipe `@myorg/ops` é mencionada. | ## Pesquisar por autor do comentário @@ -153,7 +153,7 @@ Você pode limitar os resultados por etiquetas usando o qualificador `label`. Al | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) identifica os problemas com a etiqueta "help wanted" nos repositórios de Ruby. | | | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) identifica problemas com a palavra "broken" no texto e que não têm a etiqueta "bug", mas *têm* a etiqueta "priority". | -| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %} +| | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) corresponde problemas com as etiquetas "bug" e "resolved"."{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | | [**rótulo:bug,resolvido**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) corresponde a problemas com a etiqueta "erro" ou a etiqueta "resolvido".{% endif %} ## Pesquisar por marco @@ -176,7 +176,7 @@ Você pode usar o qualificador `project` para encontrar problemas associados a u ## Pesquisar por status do commit -Você pode filtrar pull requests com base no status dos commits. This is especially useful if you are using [the Status API](/rest/reference/commits#commit-statuses) or a CI service. +Você pode filtrar pull requests com base no status dos commits. Isso é especialmente útil se você estiver usando [a API de Status](/rest/reference/commits#commit-statuses) ou um serviço de CI. | Qualifier | Exemplo | | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | @@ -246,16 +246,16 @@ Você pode filtrar por pull requests de rascunho. Para obter mais informações, Você pode filtrar as pull requests com base no [status de revisão](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_ (nenhuma), _required_ (obrigatória), _approved_ (aprovada) ou _changes requested_ (alterações solicitadas)), por revisor e por revisor solicitado. -| Qualifier | Exemplo | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) identifica as pull requests que não foram revisadas. | -| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) identifica as pull requests que exigem uma revisão antes do merge. | -| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) identifica as pull requests aprovadas por um revisor. | -| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) identifica as pull requests nas quais um revisor solicitou alterações. | -| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) identifica as pull requests revisadas por uma pessoa específica. | -| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) identifica as pull requests nas quais uma pessoa específica foi solicitada para revisão. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} +| Qualifier | Exemplo | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `review:none` | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) identifica as pull requests que não foram revisadas. | +| `review:required` | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) identifica as pull requests que exigem uma revisão antes do merge. | +| `review:approved` | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) identifica as pull requests aprovadas por um revisor. | +| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) identifica as pull requests nas quais um revisor solicitou alterações. | +| reviewed-by:USERNAME | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) identifica as pull requests revisadas por uma pessoa específica. | +| review-requested:USERNAME | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) identifica as pull requests nas quais uma pessoa específica foi solicitada para revisão. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. Se a pessoa solicitada está em uma equipe solicitada para revisão, as solicitações de revisão para essa equipe também aparecerão nos resultados de pesqusa.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %} | user-review-requested:@me | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) corresponde a pull requests que foi solicitado diretamente que você revise.{% endif %} -| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) identifica as pull requests que tem solicitações de revisão da equipe `atom/design`. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. | +| team-review-requested:TEAMNAME | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) identifica as pull requests que tem solicitações de revisão da equipe `atom/design`. Os revisores solicitados deixam de ser relacionados nos resultados da pesquisa depois de revisarem uma pull request. | ## Pesquisar por data da criação ou da última atualização de um problema ou uma pull request @@ -293,17 +293,17 @@ Esse qualificador usa a data como parâmetro. {% data reusables.time_date.date_f | Qualifier | Exemplo | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| merged:YYYY-MM-DD | [**`language:javascript merged:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) matches pull requests in JavaScript repositories that were merged before 2011. | +| merged:YYYY-MM-DD | [**`língua:javascript mesclado:<2011-01-01`**](https://github.com/search?q=language%3Ajavascript+merged%3A%3C2011-01-01+&type=Issues) corresponde pull requests em repositórios JavaScript que foram mesclados antes de 2011. | | | [**ast in:title language:ruby merged:>=2014-05-01**](https://github.com/search?q=fast+in%3Atitle+language%3Aruby+merged%3A%3E%3D2014-05-01+&type=Issues) corresponde a pull requests no Ruby com a palavra "fast" no título que foram mesclados após maio de 2014. | ## Pesquisar somente pull request com merge ou sem merge Você pode filtrar as pull requests com ou sem merge usando o qualificador `is`. -| Qualifier | Exemplo | -| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) matches merged pull requests with the word "bug." | -| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) identifica problemas e pull requests fechados com a palavra "error". | +| Qualifier | Exemplo | +| ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `is:merged` | [**bug is:pr is:merged**](https://github.com/search?utf8=%E2%9C%93&q=bugfix+is%3Apr+is%3Amerged&type=) identifica as pull requests com merge que têm a palavra "bug". | +| `is:unmerged` | [**error is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=error+is%3Aunmerged&type=) identifica problemas e pull requests fechados com a palavra "error". | ## Pesquisar com base no fato de o repositório estar arquivado diff --git a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md index 81daf948a2..f3e9d458a2 100644 --- a/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md +++ b/translations/pt-BR/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md @@ -23,7 +23,7 @@ topics: {% data reusables.sponsors.you-can-be-a-sponsored-organization %} Para mais informações, consulte "[Configurando o {% data variables.product.prodname_sponsors %} para a sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." -Quando você se tornar um desenvolvedor patrocinado ou uma organização patrocinada, termos adicionais para o {% data variables.product.prodname_sponsors %} se aplicam. For more information, see "[GitHub Sponsors Additional Terms](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms)." +Quando você se tornar um desenvolvedor patrocinado ou uma organização patrocinada, termos adicionais para o {% data variables.product.prodname_sponsors %} se aplicam. Para obter mais informações, consulte "[Equipes adicionais do GitHub Sponsors](/free-pro-team@latest/github/site-policy/github-sponsors-additional-terms)." ## Sobre o {% data variables.product.prodname_matching_fund %} @@ -33,7 +33,7 @@ Quando você se tornar um desenvolvedor patrocinado ou uma organização patroci {% endnote %} -The {% data variables.product.prodname_matching_fund %} aims to benefit members of the {% data variables.product.prodname_dotcom %} community who develop open source software that promotes the [{% data variables.product.prodname_dotcom %} Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). Pagamentos a organizações patrocinadas e pagamentos de organizações não são elegíveis para {% data variables.product.prodname_matching_fund %}. +O {% data variables.product.prodname_matching_fund %} visa a beneficiar os integrantes da comunidade {% data variables.product.prodname_dotcom %} que desenvolvem softwares de código aberto que promovem as [Diretrizes da comunidade de {% data variables.product.prodname_dotcom %}](/free-pro-team@latest/github/site-policy/github-community-guidelines). Pagamentos a organizações patrocinadas e pagamentos de organizações não são elegíveis para {% data variables.product.prodname_matching_fund %}. Para ser elegível para o {% data variables.product.prodname_matching_fund %}, você deve criar um perfil que atrairá uma comunidade que irá sustentar você a longo prazo. Para obter mais informações sobre criar um perfil forte, consulte "[Editando os detalhes de seu perfil para {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)". diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md index 8c615f1523..c74f712cdb 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md @@ -49,13 +49,13 @@ shortTitle: Gerenciar camadas de pagamento {% data reusables.sponsors.tier-update %} {% data reusables.sponsors.retire-tier %} -## Adding a repository to a sponsorship tier +## Adicionando um repositório a uma camada de patrocínio {% data reusables.sponsors.sponsors-only-repos %} -### About adding repositories to a sponsorship tier +### Sobre adicionar repositórios a uma camada de patrocínio -To add a repository to a tier, the repository must be private and owned by an organization, and you must have admin access to the repository. +Para adicionar um repositório a uma camada, o repositório deve ser privado e pertencente a uma organização, e você deverá ter acesso de administrador ao repositório. When you add a repository to a tier, {% data variables.product.company_short %} will automatically send repository invitations to new sponsors and remove access when a sponsorship is cancelled. diff --git a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index 33b093dd0c..6605883a32 100644 --- a/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -80,7 +80,7 @@ Para obter mais informações sobre como configurar o Stripe Connect usando o Op ## Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %} -Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". +Antes que sua organização possa se tornar uma organização patrocinada, você deverá habilitar a 2FA para sua conta em {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)". ## Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação diff --git a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md index b4fc96eade..e2cda4fbd0 100644 --- a/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md +++ b/translations/pt-BR/content/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor.md @@ -37,7 +37,7 @@ Ao patrocinar uma conta usando um cartão de crédito, a alteração entrará em {% data reusables.sponsors.manage-updates-for-orgs %} -You can choose whether to display your sponsorship publicly. One-time sponsorships remain visible for one month. +Você pode escolher se deseja mostrar seu patrocínio publicamente. Patrocínios únicos permanecem visíveis por um mês. Se a conta patrocinada for retirada, a sua camada permanecerá em vigor para você até que você escolha uma camada diferente ou cancele a sua assinatura. Para obter mais informações, consulte "[Atualizar um patrocínio](/articles/upgrading-a-sponsorship)" e "[Fazer downgrade de um patrocínio](/articles/downgrading-a-sponsorship)". diff --git a/translations/pt-BR/content/support/contacting-github-support/index.md b/translations/pt-BR/content/support/contacting-github-support/index.md index c9476fbd03..d272a01ec8 100644 --- a/translations/pt-BR/content/support/contacting-github-support/index.md +++ b/translations/pt-BR/content/support/contacting-github-support/index.md @@ -1,7 +1,7 @@ --- -title: Contacting GitHub Support +title: Entrando em contato com o suporte do GitHub shortTitle: Entrar em contato com o suporte -intro: 'You can use the {% ifversion ghae %}{% data variables.contact.ae_azure_portal %}{% else %}{% data variables.contact.support_portal %}{% endif %} to contact GitHub Support for help troubleshooting issues you encounter while using GitHub.' +intro: 'Você pode usar o {% ifversion ghae %}{% data variables.contact.ae_azure_portal %}{% else %}{% data variables.contact.support_portal %}{% endif %} para entrar em contato com o suporte do GitHub para ajudar a solucionar problemas que você encontrar ao usar o GitHub.' versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md b/translations/pt-BR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md index 3729e71b60..f1406e315d 100644 --- a/translations/pt-BR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md +++ b/translations/pt-BR/content/support/contacting-github-support/viewing-and-updating-support-tickets.md @@ -1,7 +1,7 @@ --- -title: Viewing and updating support tickets -intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.' -shortTitle: Managing your tickets +title: Visualizando e atualizando tíquetes de suporte +intro: 'Você pode visualizar os seus tíquetes de suporte{% ifversion ghes or ghec %}, colaborar com colegas em tíquetes,{% endif %} e responder a {% data variables.contact.github_support %} usando o {% data variables.contact.support_portal %}.' +shortTitle: Gerenciando seus tíquetes versions: fpt: '*' ghec: '*' @@ -10,7 +10,7 @@ topics: - Support --- -## About ticket management +## Sobre gestão de tíquetes {% data reusables.support.zendesk-old-tickets %} diff --git a/translations/pt-BR/content/support/index.md b/translations/pt-BR/content/support/index.md index a8517971c7..756e3864b5 100644 --- a/translations/pt-BR/content/support/index.md +++ b/translations/pt-BR/content/support/index.md @@ -2,7 +2,7 @@ title: Suporte do GitHub shortTitle: Suporte do GitHub layout: product-landing -intro: 'GitHub offers different levels of support with each product, including community forum support and limited email support for everyone, full email support for all paid products, and 24/7 email and callback support with a service level agreement (SLA) if your account includes {% data variables.contact.premium_support %}.' +intro: 'O GitHub oferece diferentes níveis de suporte a cada produto, incluindo suporte ao fórum comunitário e suporte por e-mail limitado para todos, suporte por e-mail completo para todos os produtos pagos e suporte de e-mail e retorno de chamada 24/7 com um acordo de nível de serviço (SLA) se a sua conta incluir {% data variables.contact.premium_support %}.' versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md b/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md index d701f2d86c..151c93e90c 100644 --- a/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md +++ b/translations/pt-BR/content/support/learning-about-github-support/about-github-premium-support.md @@ -1,5 +1,5 @@ --- -title: About GitHub Premium Support +title: Sobre suporte premium do GitHub intro: 'O {% data variables.contact.premium_support %} é uma opção de suporte complementar pago oferecida aos clientes do {% data variables.product.prodname_enterprise %}.' shortTitle: Suporte do GitHub Premium versions: @@ -26,7 +26,7 @@ topics: **Notas:** -- The terms of {% data variables.contact.premium_support %} are subject to change without notice and are effective as of November 2021. +- Os termos do {% data variables.contact.premium_support %} estão sujeitos a alteração sem aviso prévio e entram em vigor a partir de novembro de 2021. - {% data reusables.support.data-protection-and-privacy %} @@ -40,16 +40,16 @@ topics: Há dois {% data variables.contact.premium_support %} planos: Premium e Premium Plus / {% data variables.product.microsoft_premium_plus_support_plan %}. -| | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} -| --------------------------------- | --------------------------------------------------- | -------------------------------------------------------- | -| Horas de operação | 24 x 7 | 24 x 7 | -| Tempo inicial de resposta |
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
| -| Canais de suporte |
  • Envio do tíquete on-line
  • Phone support in English via callback request
|
  • Envio do tíquete on-line
  • Phone support in English via callback request
  • Compartilhamento de tela para problemas críticos
| -| Treinamentos | Acesso a conteúdo premium |
  • Acesso a conteúdo premium
  • 1 aula de treinamento virtual por ano
| -| Members with support entitlements | 10 | 25 | -| Recursos | Processamento de tíquete com prioridade |
  • Processamento de tíquete com prioridade
  • Engenheiro de Responsabilidade do Cliente Nomeado
| -| Verificações agendadas | Verificação de integridade e relatórios semestrais |
  • Verificação de integridade e relatórios trimestrais
  • Revisões trimestrais de conta
| -| Administration assistance | | 4 hours per month | +| | {% data variables.product.premium_support_plan %} | {% data variables.product.premium_plus_support_plan %} +| ----------------------------- | --------------------------------------------------- | -------------------------------------------------------- | +| Horas de operação | 24 x 7 | 24 x 7 | +| Tempo inicial de resposta |
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
|
  • 30 minutos para {% data variables.product.support_ticket_priority_urgent %}
  • 4 hours para {% data variables.product.support_ticket_priority_high %}
| +| Canais de suporte |
  • Envio do tíquete on-line
  • Suporte por telefone em inglês via solicitação de retorno de chamada
|
  • Envio do tíquete on-line
  • Suporte por telefone em inglês via solicitação de retorno de chamada
  • Compartilhamento de tela para problemas críticos
| +| Treinamentos | Acesso a conteúdo premium |
  • Acesso a conteúdo premium
  • 1 aula de treinamento virtual por ano
| +| Membros com direito a suporte | 10 | 25 | +| Recursos | Processamento de tíquete com prioridade |
  • Processamento de tíquete com prioridade
  • Engenheiro de Responsabilidade do Cliente Nomeado
| +| Verificações agendadas | Verificação de integridade e relatórios semestrais |
  • Verificação de integridade e relatórios trimestrais
  • Revisões trimestrais de conta
| +| Assistência administrativa | | 4 horas por mês | {% note %} @@ -113,7 +113,7 @@ Ao entrar em contato com {% data variables.contact.premium_support %}, você pod ## Resolução e fechamento de tíquete de suporte -{% data variables.contact.premium_support %} may consider a ticket solved after providing an explanation, recommendation, usage instructions, workaround instructions, or by advising you of an available {% data variables.product.prodname_ghe_server %} release that addresses the issue. +{% data variables.contact.premium_support %} pode considerar um tíquete resolvido após fornecer uma explicação, recomendação, instruções uso, instruções alternativas ou aconselhando você sobre uma versão de {% data variables.product.prodname_ghe_server %} disponível que resolve o problema. Se você usar um plugin, módulo ou código personalizado incompatível, o {% data variables.contact.premium_support %} solicitará a remoção desse item incompatível durante a tentativa de resolução do problema. Se o problema for corrigido quando o plugin, módulo ou código personalizado incompatível for removido, o {% data variables.contact.premium_support %} poderá considerar o tíquete resolvido. @@ -126,7 +126,7 @@ Se você não receber uma resposta inicial dentro do tempo de resposta garantido A solicitação de crédito deve ser feita dentro de 30 dias do final do trimestre durante o qual {% data variables.contact.premium_support %} não respondeu aos seus tíquetes dentro do tempo de resposta indicado. As solicitações de crédito não serão cumpridas se o respectivo prazo tiver passado. Uma vez esgotado o respectivo prazo, você renunciou à capacidade de reivindicar um reembolso pelo crédito qualificado. Para receber um reembolso, você deve enviar uma solicitação de crédito completa para . Para ser elegível, a solicitação de crédito deve: -- Be sent from an email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} +- Receba de um endereço de e-mail associado à sua conta em {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} - Ser recebida por {% data variables.product.company_short %} até o final do 30 dia após o trimestre em que ocorreram os quatro créditos qualificados - Incluir "Solicitação de Crédito" na linha de assunto diff --git a/translations/pt-BR/content/support/learning-about-github-support/index.md b/translations/pt-BR/content/support/learning-about-github-support/index.md index cab96cbae0..dbacd88a68 100644 --- a/translations/pt-BR/content/support/learning-about-github-support/index.md +++ b/translations/pt-BR/content/support/learning-about-github-support/index.md @@ -1,7 +1,7 @@ --- -title: Learning about GitHub Support +title: Aprendendo sobre o suporte do GitHub shortTitle: Sobre o GitHub Support -intro: 'You can learn more about getting in touch with {% data variables.contact.github_support %}.' +intro: 'Você pode aprender mais sobre como entrar em contato com {% data variables.contact.github_support %}.' versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/data/features/codeowners-errors.yml b/translations/pt-BR/data/features/codeowners-errors.yml new file mode 100644 index 0000000000..e186a4e6ec --- /dev/null +++ b/translations/pt-BR/data/features/codeowners-errors.yml @@ -0,0 +1,6 @@ +--- +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-6078' diff --git a/translations/pt-BR/data/features/dependabot-updates-github-connect.yml b/translations/pt-BR/data/features/dependabot-updates-github-connect.yml new file mode 100644 index 0000000000..6ec916de7e --- /dev/null +++ b/translations/pt-BR/data/features/dependabot-updates-github-connect.yml @@ -0,0 +1,4 @@ +--- +versions: + ghes: '>=3.4' + ghae: 'issue-5867' diff --git a/translations/pt-BR/data/features/pull-request-approval-limit.yml b/translations/pt-BR/data/features/pull-request-approval-limit.yml new file mode 100644 index 0000000000..e544ac681b --- /dev/null +++ b/translations/pt-BR/data/features/pull-request-approval-limit.yml @@ -0,0 +1,8 @@ +--- +#Reference: #5244 +#Documentation for moderation setting to limit who can approve or request changes on a PR. +versions: + fpt: '*' + ghec: '*' + ghes: '>3.4' + ghae: 'issue-5244' diff --git a/translations/pt-BR/data/graphql/ghes-3.4/graphql_previews.enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.4/graphql_previews.enterprise.yml new file mode 100644 index 0000000000..0c72449228 --- /dev/null +++ b/translations/pt-BR/data/graphql/ghes-3.4/graphql_previews.enterprise.yml @@ -0,0 +1,124 @@ +--- +- + title: Acesso à exclusão de versão pacote + description: >- + Esta pré-visualização adiciona suporte para a mudança do DeletePackageVersion que permite a exclusão de versões privadas de pacotes. + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: Implantações + description: >- + Esta visualização adiciona suporte para mudanças e novos recursos nos deployments. + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/c2c-actions-service' +- + title: >- + >- MergeInfoPreview - Mais informações detalhadas sobre o estado de merge de uma pull request. + description: >- + Esta visualização adiciona suporte para acessar campos que fornecem informações mais detalhadas sobre o estado de merge de uma pull request. + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - Atualiza vários refs em uma única operação. + description: Essa pré-visualização adiciona suporte para atualizar múltiplas refs em uma única operação. + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: Detalhes Tarefa Projeto + description: >- + Esta visualização adiciona detalhes de projeto, cartão de projeto e coluna de projetos para eventos de questões relacionadas ao projeto. + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: Visualização de Etiquetas + description: >- + Esta visualização adiciona suporte para adicionar, atualizar, criar e excluir etiquetas. + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: Importar Projeto + description: Esta visualização adiciona suporte para a importação de projetos. + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Pré-visualização da Revisão da Equipe + description: >- + Esta pré-visualização adiciona suporte para atualizar as configurações da atribuição de revisão de equipe. + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/pt-BR/data/graphql/ghes-3.4/graphql_upcoming_changes.public-enterprise.yml b/translations/pt-BR/data/graphql/ghes-3.4/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000..7ec32796da --- /dev/null +++ b/translations/pt-BR/data/graphql/ghes-3.4/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: LegacyMigration.uploadUrlTemplate + description: '`uploadUrlTemplate` será removido. Use `uploadUrl` em vez disso.' + reason: '''uploadUrlTemplate'' está sendo removido porque não é uma URL padrão e adiciona um passo extra do usuário.' + date: '2019-04-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: AssignedEvent.user + description: '`user` será removido. Use o campo `assignee`.' + reason: Os responsáveis podem agora ser mannequines. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: '`availableSeats` será removido. Use EnterpriseBillingInfo.totalAvailableLicenses em vez disso.' + reason: '`availableSeats` serão substituídos por ''totalAvailableLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: '`seats` serão removidos. Use EnterpriseBillingInfo.totalLicenses em vez disso.' + reason: '`seats` serão substituídos por ''totalLicenses'' para fornecer mais clareza sobre o valor que está sendo devolvido' + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: '`user` será removido. Use o campo `assignee`.' + reason: Os responsáveis podem agora ser mannequines. + date: '2020-01-01T00:00:00+00:00' + criticality: breaking + owner: tambling + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: '`isUnlicensed` será removido.' + reason: Todos os integrantes pendentes consomem uma licença + date: '2020-07-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOwnerInfo.pendingCollaborators + description: '`pendingCollaborators` será removido. Use o campo `pendingCollaboratorInvitations` em vez disso.' + reason: Os convites de repositório agora podem ser associados a um email, não apenas a um convidado. + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: Issue.timeline + description: '`timeline` será removido. Use Issue.timelineItems em vez disso.' + reason: '`timeline` será removido' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: PullRequest.timeline + description: '`timeline` será removido. Use PullRequest.timelineItems em vez disso.' + reason: '`timeline` será removido' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: mikesea + - + location: RepositoryInvitationOrderField.INVITEE_LOGIN + description: '`INVITEE_LOGIN` será removido.' + reason: '`INVITEE_LOGIN` não é mais um valor de campo válido. Convites de repositório agora podem ser associados a um email, não apenas a um convidado.' + date: '2020-10-01T00:00:00+00:00' + criticality: breaking + owner: jdennes + - + location: EnterpriseMemberEdge.isUnlicensed + description: '`isUnlicensed` será removido.' + reason: Todos os integrantes consomem uma licença + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: '`isUnlicensed` será removido.' + reason: Todos os colaboradores externos consomem uma licença + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: EnterprisePendingCollaboratorEdge.isUnlicensed + description: '`isUnlicensed` será removido.' + reason: Todos os colaboradores pendentes consomem uma licença + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: 'O `DRAFT` será removido. Use PullRequest.isDraft.' + reason: O status DRAFT será removido deste enum e o `isDraft` deverá ser usado + date: '2021-01-01T00:00:00+00:00' + criticality: breaking + owner: nplasterer + - + location: PackageType.DOCKER + description: '`DOCKER` será removido.' + reason: O DOCKER será removido deste enum, pois este tipo será transferido para ser usado apenas pela API REST dos pacotes. + date: '2021-06-21' + criticality: breaking + owner: reybard + - + location: ReactionGroup.users + description: '`users` será removido. Use o campo `reactors`.' + reason: Os reatores agora podem ser mannequins, bots e organizações. + date: '2021-10-01T00:00:00+00:00' + criticality: breaking + owner: synthead diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml new file mode 100644 index 0000000000..38b9f9a0b5 --- /dev/null +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -0,0 +1,193 @@ +--- +date: '2022-03-15' +release_candidate: true +deprecated: false +intro: | + {% note %} + + **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + + {% endnote %} + + For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." + + > This release is dedicated to our colleague and friend John, a Hubber who was always there to help. You will be greatly missed. + > + > **John "Ralph" Wiebalk 1986–2021** +sections: + features: + - + heading: Secret scanning REST API now returns locations + notes: + - | + {% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve commit details of secrets detected in private repository scans. The new endpoint returns details of a secret's first detection within a file, including the secret's location and commit SHA. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation. + - + heading: Export license data of committer-based billing for GitHub Advanced Security + notes: + - | + Enterprise and organization owners can now export their {% data variables.product.prodname_GH_advanced_security %} license usage data to a CSV file. The {% data variables.product.prodname_advanced_security %} billing data can also be retrieved via billing endpoints in the REST API. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-11-export-github-advanced-security-license-usage-data/)." + - + heading: GitHub Actions reusable workflows in public beta + notes: + - | + You can now reuse entire workflows as if they were an action. This feature is available in public beta. Instead of copying and pasting workflow definitions across repositories, you can now reference an existing workflow with a single line of configuration. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-05-github-actions-dry-your-github-actions-configuration-by-reusing-workflows/)." + - + heading: Dependabot security and version updates in public beta + notes: + - | + {% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/github/feedback/discussions/categories/dependabot-feedback). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + changes: + - + heading: Alterações na administração + notes: + - Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size. + - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. + - + heading: Performance Changes + notes: + - WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation. + - + heading: Notification Changes + notes: + - Organization owners can now unsubscribe from email notifications when new deploy keys are added to repositories belonging to their organizations. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)." + - 'Notification emails from newly created issues and pull requests now include `(Issue #xx)` or `(PR #xx)` in the email subject, so you can recognize and filter emails that reference these types of issues.' + - + heading: Organization Changes + notes: + - Organizations can now display a `README.md` file on their profile Overview. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-14-readmes-for-organization-profiles/)." + - 'Members of organizations can now view a list of their enterprise owners under the organization''s "People" tab. The enterprise owners list is also now accessible using the GraphQL API. For more information, see the "[`enterpriseOwners`](/graphql/reference/objects#organization)" field under the Organization object in the GraphQL API documentation.' + - + heading: Repositories changes + notes: + - | + A "Manage Access" section is now shown on the "Collaborators and teams" page in your repository settings. The new section makes it easier for repository administrators to see and manage who has access to their repository, and the level of access granted to each user. Administrators can now: + + * Search all members, teams and collaborators who have access to the repository. + * View when members have mixed role assignments, granted to them directly as individuals or indirectly via a team. This is visualized through a new "mixed roles" warning, which displays the highest level role the user is granted if their permission level is higher than their assigned role. + * Manage access to popular repositories reliably, with page pagination and fewer timeouts when large groups of users have access. + - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the repository invitation experience, such as notifications for private repository invites, a UI prompt when visiting a private repository you have a pending invitation for, and a banner on a public repository overview page when there is an pending invitation.' + - 'You can now use single-character prefixes for custom autolinks. Autolink prefixes also now allow `.`, `-`, `_`, `+`, `=`, `:`, `/`, and `#` characters, as well as alphanumerics. For more information about custom autolinks, see "[Configuring autolinks to reference external resources](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)."' + - A `CODE_OF_CONDUCT.md` file in the root of a repository is now highlighted in the "About" sidebar on the repository overview page. + - + heading: 'Releases changes' + notes: + - '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the Releases UI, such as automatically generated release notes which display a summary of all the pull requests for a given release. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-20-improvements-to-github-releases-generally-available/)."' + - When a release is published, an avatar list is now displayed at the bottom of the release. Avatars for all user accounts mentioned in the release notes are shown. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)." + - + heading: 'Markdown changes' + notes: + - You can now use the new "Accessibility" settings page to manage your keyboard shortcuts. You can choose to disable keyboard shortcuts that only use single characters like S, G C, and . (the period key). For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-16-managing-keyboard-shortcuts-using-accessibility-settings/)." + - You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-12-fixed-width-font-support-in-markdown-enabled-fields/)." + - You can now paste a URL on selected text to quickly create a Markdown link. This works in all Markdown-enabled fields, such as issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-linkify-selected-text-on-url-paste/)." + - 'An image URL can now be appended with a theme context, such as `#gh-dark-mode-only`, to define how the Markdown image is displayed to a viewer. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/)."' + - When creating or editing a gist file with the Markdown (`.md`) file extension, you can now use the "Preview" or "Preview Changes" tab to display a Markdown rendering of the file contents. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-17-preview-the-markdown-rendering-of-gists/)." + - When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed. + - Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments. + - + heading: 'Issues and pull requests changes' + notes: + - The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request. + - When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)." + - + heading: 'Branches changes' + notes: + - 'Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.' + - When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)." + - Only users with administrator permissions are now able to rename protected branches and modify branch protection rules. Previously, with the exception of the default branch, a collaborator could rename a branch and consequently any non-wildcard branch protection rules that applied to that branch were also renamed. For more information, see "[Renaming a branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)." + - Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)." + - Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)." + - When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)." + - + heading: 'GitHub Actions changes' + notes: + - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' + - Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)." + - '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."' + - You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)." + - 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.' + - 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."' + - Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional. + - The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order. + - 'Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.' + - + heading: 'Dependabot and Dependency graph changes' + notes: + - Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files. + - When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." + - '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.' + - + heading: 'Code scanning and secret scanning changes' + notes: + - The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)." + - The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)." + - | + The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)." + - Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)." + - | + Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API: + + * The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis. + * Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)." + * A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation. + * The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)." + * Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)." + * Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission. + + For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation. + - '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.' + #No security/bug fixes for the RC release + #security_fixes: + #- PLACEHOLDER + #bugs: + #- PLACEHOLDER + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - As regras de firewall personalizadas são removidas durante o processo de atualização. + - Arquivos LFS do Git [enviados através da interface web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de forma incorreta. + - Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório, onde o caminho do arquivo blob's é maior que 255 caracteres. + - Quando "Usuários podem pesquisar pelo GitHub.com" está habilitado com o GitHub Connect, os problemas em repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. + - O registro npm de {% data variables.product.prodname_registry %} não retorna mais o valor de tempo em respostas de metadados. Isso foi feito para permitir melhorias substanciais de desempenho. Continuamos a ter todos os dados necessários para devolver um valor de tempo como parte da resposta aos metadados e retomaremos o retorno desse valor no futuro, assim que tivermos resolvido os problemas de desempenho existentes. + - Os limites de recursos que são específicos para processamento de hooks pre-receive podem causar falha em alguns hooks pre-receive. + deprecations: + - + heading: Deprecation of GitHub Enterprise Server 3.0 + notes: + - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Deprecation of GitHub Enterprise Server 3.1 + notes: + - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.' + - + heading: Obsolescência do suporte para Hypervisor XenServer + notes: + - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns. + - + heading: Deprecation of the Content Attachments API preview + notes: + - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments. + - + heading: Deprecation of the Codes of Conduct API preview + notes: + - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-01-deprecating-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.' + - + heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters + notes: + - | + Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make). + - + heading: Deprecation of the CodeQL runner + notes: + - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/). + - + heading: Deprecation of custom bit-cache extensions + notes: + - | + Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards. + + Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated. + + Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed. + + To start a repository maintenance task manually, browse to `https:///stafftools/repositories///network` for each affected repository and click the Schedule button. + backups: + - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).' diff --git a/translations/pt-BR/data/reusables/actions/minimum-hardware.md b/translations/pt-BR/data/reusables/actions/minimum-hardware.md new file mode 100644 index 0000000000..4f4460df6b --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/minimum-hardware.md @@ -0,0 +1 @@ +{% data variables.product.company_short %} recommends a minimum of 8 vCPU and 64 GB memory to run {% data variables.product.prodname_actions %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md new file mode 100644 index 0000000000..7264d89ee0 --- /dev/null +++ b/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md @@ -0,0 +1,9 @@ +{% ifversion ghes = 3.4 %} + +{% note %} + +**Note**: Reusable workflows are currently in beta and subject to change. + +{% endnote %} + +{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/dependabot/about-the-dependency-graph.md b/translations/pt-BR/data/reusables/dependabot/about-the-dependency-graph.md new file mode 100644 index 0000000000..45de529630 --- /dev/null +++ b/translations/pt-BR/data/reusables/dependabot/about-the-dependency-graph.md @@ -0,0 +1,4 @@ +O gráfico de dependências é um resumo do manifesto e bloqueia arquivos armazenados em um repositório. Para cada repositório, ele mostra{% ifversion fpt or ghec %}: + +- As dependências, os ecossistemas e os pacotes do qual depende +- Dependentes, os repositórios e pacotes que dependem dele{% else %} dependências, isto é, os ecossistemas e pacotes de que ele depende. O {% data variables.product.product_name %} não calcula informações sobre dependentes, repositórios e pacotes que dependem de um repositório.{% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates.md b/translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates.md index 80d479ff90..e356372aa4 100644 --- a/translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates.md +++ b/translations/pt-BR/data/reusables/dependabot/beta-security-and-version-updates.md @@ -1,9 +1,11 @@ {% ifversion ghes > 3.2 %} {% note %} - +{% if dependabot-updates-github-connect %} +**Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in public beta and subject to change. +{% else %} **Note:** {% data variables.product.prodname_dependabot %} security and version updates are currently in private beta and subject to change. To request access to the beta release, [contact your account management team](https://enterprise.github.com/contact). - +{% endif %} {% endnote %} {% endif %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md index 9123cc090d..14d560b7e4 100644 --- a/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md +++ b/translations/pt-BR/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md @@ -1,3 +1,3 @@ {% ifversion ghes or ghae-issue-4864 %} -The dependency graph and {% data variables.product.prodname_dependabot_alerts %} are configured at an enterprise level by the enterprise owner. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." +The dependency graph and {% data variables.product.prodname_dependabot_alerts %} are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md b/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md index f36e39a69b..41968d8dd5 100644 --- a/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md +++ b/translations/pt-BR/data/reusables/dependabot/enterprise-enable-dependabot.md @@ -2,7 +2,7 @@ {% note %} -**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot %} updates for {% data variables.product.product_location %} before you can use this feature. Para obter mais informações, consulte "[Configurando a segurança de {% data variables.product.prodname_dependabot %} e as atualizações de versão na sua empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)". +**Note:** Your site administrator must set up {% data variables.product.prodname_dependabot_updates %} for {% data variables.product.product_location %} before you can use this feature. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endnote %} diff --git a/translations/pt-BR/data/reusables/desktop/revert-commit.md b/translations/pt-BR/data/reusables/desktop/revert-commit.md index c58e2bfc55..5694921a0f 100644 --- a/translations/pt-BR/data/reusables/desktop/revert-commit.md +++ b/translations/pt-BR/data/reusables/desktop/revert-commit.md @@ -1 +1 @@ -1. Clique com o botão direito no commit que você deseja reverter e clique em **Revert This Commit** (Reverter este commit). +1. Right-click the commit you want to revert and click **Revert Changes in Commit**. diff --git a/translations/pt-BR/data/reusables/enterprise_installation/preventing-nameservers-change.md b/translations/pt-BR/data/reusables/enterprise_installation/preventing-nameservers-change.md new file mode 100644 index 0000000000..c90d54c03a --- /dev/null +++ b/translations/pt-BR/data/reusables/enterprise_installation/preventing-nameservers-change.md @@ -0,0 +1,5 @@ + {% note %} + + **Note**: The 127.0.0.1 entry is required to be the first entry in the list. Do not remove the 127.0.0.1 entry, add another entry above the 127.0.0.1 entry, or use options that affect the ordering of entries, such as "options rotate". + + {% endnote %} diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-option.md b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-option.md index 5162c731c7..3562f911e6 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-option.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication-option.md @@ -1 +1 @@ -Opcionalmente, selecione **Allow built-in authentication** para convidar usuários a utilizar a autenticação integrada se eles não pertencerem ao provedor de identidade do {% data variables.product.product_location %}. +Optionally, to allow people to use built-in authentication if they don't have an account on your IdP, select **Allow built-in authentication**. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do provedor de identidade](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md index b63241a055..f5cff2bb46 100644 --- a/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md +++ b/translations/pt-BR/data/reusables/enterprise_user_management/built-in-authentication.md @@ -1 +1 @@ -Se você quiser autenticar usuários sem adicioná-los ao seu provedor de identidade, você pode configurar a autenticação integrada. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do provedor de identidade](/enterprise/{{ currentVersion }}/admin/guides/user-management/allowing-built-in-authentication-for-users-outside-your-identity-provider)". +If you want to authenticate some users without adding them to your identity provider, you can configure built-in authentication in addition to SAML SSO. Para obter mais informações, consulte "[Permitir a autenticação integrada para usuários de fora do provedor de identidade](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/allowing-built-in-authentication-for-users-outside-your-identity-provider)". diff --git a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md index da96012798..c816597321 100644 --- a/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md +++ b/translations/pt-BR/data/reusables/github-actions/github-token-available-permissions.md @@ -24,3 +24,9 @@ Você pode usar a sintaxe a seguir para definir o acesso de leitura ou gravaçã ```yaml permissions: read-all|write-all ``` + +You can use the following syntax to disable permissions for all of the available scopes: + +```yaml +permissions: {} +``` diff --git a/translations/pt-BR/data/reusables/organizations/invite-teams-or-people.md b/translations/pt-BR/data/reusables/organizations/invite-teams-or-people.md index 6bb398292f..b7b059b67b 100644 --- a/translations/pt-BR/data/reusables/organizations/invite-teams-or-people.md +++ b/translations/pt-BR/data/reusables/organizations/invite-teams-or-people.md @@ -1 +1 @@ -1. À direita de "Gerenciar acesso", clique em **Invite teams or people** (Convidar equipes ou pessoas). !["Botão para convidar equipes ou pessoas"](/assets/images/help/repository/manage-access-invite-button.png) +1. To the right of "Manage access", click **Add people** or **Add teams**. !["Botão para convidar equipes ou pessoas"](/assets/images/help/repository/manage-access-invite-button.png) diff --git a/translations/pt-BR/data/reusables/organizations/mixed-roles-warning.md b/translations/pt-BR/data/reusables/organizations/mixed-roles-warning.md new file mode 100644 index 0000000000..a88e2a17dd --- /dev/null +++ b/translations/pt-BR/data/reusables/organizations/mixed-roles-warning.md @@ -0,0 +1 @@ +If a person has been given conflicting access, you'll see a warning on the repository access page. The warning appears with "{% octicon "alert" aria-label="The alert icon" %} Mixed roles" next to the person with the conflicting access. To see the source of the conflicting access, hover over the warning icon or click **Mixed roles**. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/pull_requests/code-review-limits.md b/translations/pt-BR/data/reusables/pull_requests/code-review-limits.md new file mode 100644 index 0000000000..55d0836c64 --- /dev/null +++ b/translations/pt-BR/data/reusables/pull_requests/code-review-limits.md @@ -0,0 +1 @@ +By default, in public repositories, any user can submit reviews that approve or request changes to a pull request. Organization owners and repository admins can limit who is able to give approving pull request reviews or request changes. For more information, see "[Managing pull request reviews in your organization](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)" and "[Managing pull request reviews in your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-pull-request-reviews-in-your-repository)." diff --git a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md index 84ff4f24ea..8c258ad344 100644 --- a/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md +++ b/translations/pt-BR/data/reusables/repositories/enable-security-alerts.md @@ -1,4 +1,4 @@ {% ifversion ghes or ghae-issue-4864 %} Enterprise owners must enable -{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. Para obter mais informações, consulte[Habilitando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)." +{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. Para obter mais informações, consulte "[Habilitar {% data variables.product.prodname_dependabot %} para a sua empresa](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." {% endif %} diff --git a/translations/pt-BR/data/variables/product.yml b/translations/pt-BR/data/variables/product.yml index d4ea5b8b59..955db91aa3 100644 --- a/translations/pt-BR/data/variables/product.yml +++ b/translations/pt-BR/data/variables/product.yml @@ -143,6 +143,7 @@ prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Alertas do Dependabot' prodname_dependabot_security_updates: 'Atualizações de segurança do Dependabot' prodname_dependabot_version_updates: 'Atualizações de versão do Dependabot' +prodname_dependabot_updates: 'Dependabot updates' #GitHub Archive Program prodname_archive: 'Programa Arquivo do GitHub' prodname_arctic_vault: 'Cofre de Código do Ártico' diff --git a/translations/pt-BR/data/variables/release_candidate.yml b/translations/pt-BR/data/variables/release_candidate.yml index ec65ef6f94..08448113ee 100644 --- a/translations/pt-BR/data/variables/release_candidate.yml +++ b/translations/pt-BR/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.4 From 3d7a29ec4df231672694c0203d619276f9ed1214 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Wed, 16 Feb 2022 10:31:25 -0800 Subject: [PATCH 2/2] New translation batch for ja (#25400) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report Co-authored-by: Grace Park --- translations/ja-JP/content/admin/index.md | 4 +- ...or-security-settings-in-your-enterprise.md | 2 +- .../overview/github-developer-program.md | 2 +- .../get-started/using-git/about-git-rebase.md | 2 +- .../creating-and-highlighting-code-blocks.md | 7 + .../creating-diagrams.md | 33 + .../working-with-advanced-formatting/index.md | 1 + ...ing-the-audit-log-for-your-organization.md | 980 +++++++++--------- ...aging-scheduled-reminders-for-your-team.md | 2 +- .../ja-JP/content/rest/reference/pages.md | 1 + translations/ja-JP/data/features/mermaid.yml | 8 + .../gpg/desktop-support-for-commit-signing.md | 2 +- translations/log/ja-resets.csv | 1 + 13 files changed, 546 insertions(+), 499 deletions(-) create mode 100644 translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md create mode 100644 translations/ja-JP/data/features/mermaid.yml diff --git a/translations/ja-JP/content/admin/index.md b/translations/ja-JP/content/admin/index.md index e660dafc6e..045b62fd54 100644 --- a/translations/ja-JP/content/admin/index.md +++ b/translations/ja-JP/content/admin/index.md @@ -10,9 +10,7 @@ redirect_from: - /github/installing-and-configuring-github-insights/key-metrics-for-collaboration-in-pull-requests - /github/installing-and-configuring-github-insights/viewing-and-filtering-key-metrics-and-reports - /github/installing-and-configuring-github-insights/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.22/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.21/github/site-policy/github-insights-and-data-protection-for-your-organization - - /enterprise-server@2.20/github/site-policy/github-insights-and-data-protection-for-your-organization + - /github/site-policy/github-insights-and-data-protection-for-your-organization - /insights/installing-and-configuring-github-insights/configuring-the-connection-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/navigating-between-github-insights-and-github-enterprise - /github/installing-and-configuring-github-insights/enabling-a-link-between-github-insights-and-github-enterprise diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md index 11b1ab119f..bb2260fdb3 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md @@ -10,7 +10,7 @@ redirect_from: - /github/articles/managing-allowed-ip-addresses-for-organizations-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account - /github/setting-up-and-managing-your-enterprise/enforcing-security-settings-in-your-enterprise-account - - github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account + - /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-security-settings-in-your-enterprise-account versions: ghec: '*' ghes: '*' diff --git a/translations/ja-JP/content/developers/overview/github-developer-program.md b/translations/ja-JP/content/developers/overview/github-developer-program.md index e15c16d96c..baa484c969 100644 --- a/translations/ja-JP/content/developers/overview/github-developer-program.md +++ b/translations/ja-JP/content/developers/overview/github-developer-program.md @@ -28,7 +28,7 @@ Email partnerships@github.com to re ## GitHubと連携するインテグレーションがありますか？ 素晴らしいです！ プログラムに参加していただければ嬉しく思います。 以下のようにすれば、情報を展開できます。

-* [あなたのインテグレーションについてお知らせください。](https://github.com/contact?form[subject]=New+GitHub+Integration) +* [あなたのインテグレーションについてお知らせください。](https://support.github.com/contact?tags=rr-general-technical&form[subject]=New+GitHub+Integration) * [OctocatもしくはGitHubロゴ](https://github.com/logos)を使って、あなたの製品がGitHubと動作することを示してください。 * Webサイトにインテグレーションに関するビデオあるいはブログをポストしてください。 diff --git a/translations/ja-JP/content/get-started/using-git/about-git-rebase.md b/translations/ja-JP/content/get-started/using-git/about-git-rebase.md index fcbfed428c..a5239b4bb6 100644 --- a/translations/ja-JP/content/get-started/using-git/about-git-rebase.md +++ b/translations/ja-JP/content/get-started/using-git/about-git-rebase.md @@ -2,7 +2,7 @@ title: Gitリベースについて redirect_from: - /rebase - - articles/interactive-rebase/ + - /articles/interactive-rebase - /articles/about-git-rebase - /github/using-git/about-git-rebase - /github/getting-started-with-github/about-git-rebase diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md index 446bd2b800..7d1b636b4c 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md @@ -66,6 +66,13 @@ Look! You can see my backticks. 構文強調表示のための言語検出の実行や[サードパーティの文法](https://github.com/github/linguist/blob/master/vendor/README.md)の選択には [Linguist](https://github.com/github/linguist) を使用します。 どのキーワードが有効かについては[言語 YAML ファイル](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)でご覧いただけます。 +{% if mermaid %} +## Creating diagrams + +You can use Mermaid syntax to add diagrams. For more information, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)." + +{% endif %} + ## 参考リンク - [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/) diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md new file mode 100644 index 0000000000..4f4f1a2e26 --- /dev/null +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -0,0 +1,33 @@ +--- +title: Creating diagrams +intro: Create diagrams to convey information through charts and graphs +versions: + feature: mermaid +shortTitle: Create diagrams +--- + +You can use Mermaid syntax to create diagrams. Mermaid is a Markdown-inspired tool that renders text into diagrams. For example, Mermaid can render flow charts, sequence diagrams, pie charts and more. For more information, see the [Mermaid documentation](https://mermaid-js.github.io/mermaid/#/). + +To create a Mermaid diagram, add Mermaid syntax inside a fenced code block with the `mermaid` language identifier. For more information about creating code blocks, see "[Creating and highlighting code blocks](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)." + +For example, you can create a flow chart: + +
+Here is a simple flow chart:
+
+```mermaid
+graph TD;
+    A-->B;
+    A-->C;
+    B-->D;
+    C-->D;
+```
+
+ +![Rendered Mermaid flow chart](/assets/images/help/writing/mermaid-flow-chart.png) + +{% note %} + +**Note:** You may observe errors if you run a third-party Mermaid plugin when using Mermaid syntax on {% data variables.product.company_short %}. + +{% endnote %} diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md index a66d1b2d61..7e78f4a5f5 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/index.md @@ -13,6 +13,7 @@ children: - /organizing-information-with-tables - /organizing-information-with-collapsed-sections - /creating-and-highlighting-code-blocks + - /creating-diagrams - /autolinked-references-and-urls - /attaching-files - /creating-a-permanent-link-to-a-code-snippet diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index c453aca5f9..22ab4ee850 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -1,6 +1,6 @@ --- -title: Organization の Audit log をレビューする -intro: Audit log により、Organization の管理者は Organization のメンバーによって行われたアクションをすばやくレビューできます。 これには、誰がいつ何のアクションを実行したかなどの詳細が残されます。 +title: Reviewing the audit log for your organization +intro: 'The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.' miniTocMaxHeadingLevel: 3 redirect_from: - /articles/reviewing-the-audit-log-for-your-organization @@ -14,96 +14,95 @@ versions: topics: - Organizations - Teams -shortTitle: 監査ログのレビュー +shortTitle: Review audit log --- -## Audit log にアクセスする +## Accessing the audit log -Audit logは、当月及び過去6ヶ月の間にOrganizationに影響するアクティビティによって生じたイベントをリストします。 Organization の Audit log にアクセスできるのはオーナーのみです。 +The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log. {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.audit_log.audit_log_sidebar_for_org_admins %} -## Audit log を検索する +## Searching the audit log {% data reusables.audit_log.audit-log-search %} -### 実行されたアクションに基づく検索 +### Search based on the action performed -特定のイベントを検索するには、クエリで `action` 修飾子を使用します。 Audit log に一覧表示されるアクションは以下のカテゴリに分類されます。 +To search for specific events, use the `action` qualifier in your query. Actions listed in the audit log are grouped within the following categories: -| カテゴリ名 | 説明 | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| [`アカウント`](#account-category-actions) | Organization アカウントに関連するすべてのアクティビティが対象です。 | -| [`advisory_credit`](#advisory_credit-category-actions) | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリのコントリビューターのクレジットに関連するすべてのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | -| [`支払い`](#billing-category-actions) | Organization の支払いに関連するすべてのアクティビティが対象です。 | -| [`business`](#business-category-actions) | Enterpriseのビジネス設定に関連するアクティビティを含みます。 | -| [`codespaces`](#codespaces-category-actions) | OrganizationのCodespacesに関連するすべてのアクティビティを含みます。 |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} -| [`dependabot_alerts`](#dependabot_alerts-category-actions) | 既存のリポジトリの{% data variables.product.prodname_dependabot_alerts %}に対するOrganizationレベルの設定アクティビティを含みます。 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | -| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Organizationで新たに作成されたリポジトリ内の{% data variables.product.prodname_dependabot_alerts %}に対するOrganizationレベルの設定アクティビティを含みます。 | -| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | 既存のリポジトリ内の {% data variables.product.prodname_dependabot_security_updates %} の Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)」を参照してください。 | -| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Organizationで新たに作成されたリポジトリに対する{% data variables.product.prodname_dependabot_security_updates %}のOrganizationレベルの設定アクティビティを含みます。{% endif %}{% ifversion fpt or ghec %} -| [`dependency_graph`](#dependency_graph-category-actions) | リポジトリの依存関係グラフの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | -| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Organization 内に作成された新しいリポジトリの Organization レベルの設定アクティビティが対象です。{% endif %} -| [`discussion_post`](#discussion_post-category-actions) | Team ページに投稿されたディスカッションに関連するすべてのアクティビティが対象です。 | -| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Teamページにポストされたディスカッションへの返信に関連するすべてのアクティビティを含みます。{% ifversion fpt or ghes or ghec %} -| [`Enterprise`](#enterprise-category-actions) | Enterprise設定に関連するアクティビティを含みます。 |{% endif %} -| [`フック`](#hook-category-actions) | webhookに関連するすべてのアクティビティを含みます。 | -| [`integration_installation_request`](#integration_installation_request-category-actions) | Organization 内で使用するインテグレーションをオーナーが承認するよう求める、 Organization メンバーからのリクエストに関連するすべてのアクティビティが対象です。 | -| [`ip_allow_list`](#ip_allow_list) | Organizationに対するIP許可リストの有効化あるいは無効化に関連するアクティビティが含まれます。 | -| [`ip_allow_list_entry`](#ip_allow_list_entry) | Organizationに対するIP許可リストのエントリの作成、削除、編集に関連するアクティビティが含まれます。 | -| [`Issue`](#issue-category-actions) | Issue の削除に関連するアクティビティが対象です。 |{% ifversion fpt or ghec %} -| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | {% data variables.product.prodname_marketplace %} Developer Agreement の署名に関連するすべての活動が対象です。 | -| [`marketplace_listing`](#marketplace_listing-category-actions) | {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} でのアプリのリストに関連するすべてのアクティビティが対象です。 | -| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Organization 内のリポジトリの {% data variables.product.prodname_pages %} サイトの公開の管理に関連するすべてのアクティビティが対象です。 詳しい情報については「[Organizationの{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 |{% endif %} -| [`org`](#org-category-actions) | Organizationのメンバーシップに関連するアクティビティを含みます。{% ifversion ghec %} -| [`org_credential_authorization`](#org_credential_authorization-category-actions) | SAML シングルサインオンで使用する認可クレデンシャルに関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghes or ghae or ghec %} -| [`organization_label`](#organization_label-category-actions) | Organization のリポジトリのデフォルトラベルに関連するすべてのアクティビティが対象です。{% endif %} -| [`oauth_application`](#oauth_application-category-actions) | OAuth アプリに関連するすべてのアクティビティが対象です。{% ifversion fpt or ghes > 3.0 or ghec %} -| [`パッケージ`](#packages-category-actions) | {% data variables.product.prodname_registry %} に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghec %} -| [`payment_method`](#payment_method-category-actions) | Organization の GitHub への支払い方法に関連するすべてのアクティビティが対象です。{% endif %} -| [`profile_picture`](#profile_picture-category-actions) | Organization のプロフィール画像に関連するすべてのアクティビティが対象です。 | -| [`project`](#project-category-actions) | プロジェクト ボードに関連するすべての活動が対象です。 | -| [`protected_branch`](#protected_branch-category-actions) | 保護されたブランチ関連するすべてのアクティビティが対象です。 | -| [`repo`](#repo-category-actions) | Organization が所有するリポジトリに関連するアクティビティを含みます。{% ifversion fpt or ghec %} -| [`repository_advisory`](#repository_advisory-category-actions) | {% data variables.product.prodname_advisory_database %} のセキュリティアドバイザリに関連するリポジトリレベルのアクティビティが対象です。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | -| [`repository_content_analysis`](#repository_content_analysis-category-actions) | [プライベート リポジトリに対するデータの使用を有効または無効にする](/articles/about-github-s-use-of-your-data)に関連するすべての活動が対象です。{% endif %}{% ifversion fpt or ghec %} -| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | プライベートリポジトリの依存関係グラフの有効化または無効化に関連する | -| {% ifversion fpt or ghec %}リポジトリ{% endif %}レベルのアクティビティが含まれます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。{% endif %}{% ifversion ghes or ghae or ghec %} | | -| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | シークレットスキャンに関連するリポジトリレベルのアクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 |{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | [脆弱性のある依存関係](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)の {% data variables.product.prodname_dependabot_alerts %} に関連するすべてのアクティビティが対象です。{% endif %}{% ifversion fpt or ghec %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | {% data variables.product.prodname_dependabot_alerts %}に対するリポジトリレベルの設定アクティビティが含まれます。{% endif %}{% ifversion ghec %} -| [`ロール`](#role-category-actions) | [カスタムのリポジトリロール](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)に関連するすべてのアクティビティが含まれます。{% endif %}{% ifversion ghes or ghae or ghec %} -| [`secret_scanning`](#secret_scanning-category-actions) | 既存のリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | -| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Organization で作成された新しいリポジトリ内のシークレットスキャンの Organization レベルの設定アクティビティが対象です。 |{% endif %}{% ifversion fpt or ghec %} -| [`sponsors`](#sponsors-category-actions) | スポンサーボタンに関連するすべてのアクティビティが対象です (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照){% endif %} -| [`Team`](#team-category-actions) | Organization内のチームに関連するすべてのアクティビティを含みます。 | -| [`team_discussions`](#team_discussions-category-actions) | OrganizationのTeamディスカッションの管理に関連するアクティビティが含まれます。{% ifversion fpt or ghec or ghes > 3.1 or ghae %} -| [`workflows`](#workflows-category-actions) | {% data variables.product.prodname_actions %}ワークフローに関連するアクティビティが含まれます。{% endif %} +| Category name | Description +|------------------|-------------------{% ifversion fpt or ghec %} +| [`account`](#account-category-actions) | Contains all activities related to your organization account. +| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing. +| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. | +| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %} +| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. +| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +| [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %} +| [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| [`dependency_graph_new_repos`](#dependency_graph_new_repos-category-actions) | Contains organization-level configuration activities for new repositories created in the organization.{% endif %} +| [`discussion_post`](#discussion_post-category-actions) | Contains all activities related to discussions posted to a team page. +| [`discussion_post_reply`](#discussion_post_reply-category-actions) | Contains all activities related to replies to discussions posted to a team page.{% ifversion fpt or ghes or ghec %} +| [`enterprise`](#enterprise-category-actions) | Contains activities related to enterprise settings. | {% endif %} +| [`hook`](#hook-category-actions) | Contains all activities related to webhooks. +| [`integration_installation_request`](#integration_installation_request-category-actions) | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. | +| [`ip_allow_list`](#ip_allow_list) | Contains activities related to enabling or disabling the IP allow list for an organization. +| [`ip_allow_list_entry`](#ip_allow_list_entry) | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization. +| [`issue`](#issue-category-actions) | Contains activities related to deleting an issue. {% ifversion fpt or ghec %} +| [`marketplace_agreement_signature`](#marketplace_agreement_signature-category-actions) | Contains all activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. +| [`marketplace_listing`](#marketplace_listing-category-actions) | Contains all activities related to listing apps in {% data variables.product.prodname_marketplace %}.{% endif %}{% ifversion fpt or ghes > 3.0 or ghec %} +| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %} +| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %} +| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% ifversion fpt or ghes or ghae or ghec %} +| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %} +| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes > 3.0 or ghec %} +| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %} +| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %} +| [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture. +| [`project`](#project-category-actions) | Contains all activities related to project boards. +| [`protected_branch`](#protected_branch-category-actions) | Contains all activities related to protected branches. +| [`repo`](#repo-category-actions) | Contains activities related to the repositories owned by your organization.{% ifversion fpt or ghec %} +| [`repository_advisory`](#repository_advisory-category-actions) | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| [`repository_content_analysis`](#repository_content_analysis-category-actions) | Contains all activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data).{% endif %}{% ifversion fpt or ghec %} +| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %} +| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} +| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %} +| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} +| [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %} +| [`sponsors`](#sponsors-category-actions) | Contains all events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)"){% endif %} +| [`team`](#team-category-actions) | Contains all activities related to teams in your organization. +| [`team_discussions`](#team_discussions-category-actions) | Contains activities related to managing team discussions for an organization.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} +| [`workflows`](#workflows-category-actions) | Contains activities related to {% data variables.product.prodname_actions %} workflows.{% endif %} -次の用語を使用すれば、特定の一連の行動を検索できます。 例: +You can search for specific sets of actions using these terms. For example: - * `action:team`はteamカテゴリ内でグループ化されたすべてのイベントを検索します。 - * `-action:hook` は webhook カテゴリ内のすべてのイベントを除外します。 + * `action:team` finds all events grouped within the team category. + * `-action:hook` excludes all events in the webhook category. -各カテゴリには、フィルタできる一連の関連アクションがあります。 例: +Each category has a set of associated actions that you can filter on. For example: - * `action:team.create`はTeamが作成されたすべてのイベントを検索します。 - * `-action:hook.events_changed` は webhook の変更されたすべてのイベントを除外します。 + * `action:team.create` finds all events where a team was created. + * `-action:hook.events_changed` excludes all events where the events on a webhook have been altered. -### アクション時間に基づく検索 +### Search based on time of action -`created` 修飾子を使用して、行われた日時に基づいて Audit log 内のイベントをフィルタします。 {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} +Use the `created` qualifier to filter events in the audit log based on when they occurred. {% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %} {% data reusables.search.date_gt_lt %} -例: +For example: - * `created:2014-07-08` は、2014 年 7 月 8 日に発生したイベントをすべて検索します。 - * `created:>=2014-07-08` は、2014 年 7 月 8 日かそれ以降に生じたすべてのイベントを検索します。 - * `created:<=2014-07-08`は、2014 年 7 月 8 日かそれ以前に生じたすべてのイベントを検索します。 - * `created:2014-07-01..2014-07-31`は、2014 年 7 月に起きたすべてのイベントを検索します。 + * `created:2014-07-08` finds all events that occurred on July 8th, 2014. + * `created:>=2014-07-08` finds all events that occurred on or after July 8th, 2014. + * `created:<=2014-07-08` finds all events that occurred on or before July 8th, 2014. + * `created:2014-07-01..2014-07-31` finds all events that occurred in the month of July 2014. {% note %} @@ -112,35 +111,35 @@ Audit logは、当月及び過去6ヶ月の間にOrganizationに影響するア {% endnote %} -### 場所に基づく検索 +### Search based on location -修飾子 `country` を使用すれば、発信元の国に基づいて Audit log 内のイベントをフィルタリングできます。 国の 2 文字のショートコードまたはフル ネームを使用できます。 名前に空白がある国は引用符で囲む必要があることに注意してください。 例: +Using the qualifier `country`, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example: - * `country:de` は、ドイツで発生したイベントをすべて検索します。 - * `country:Mexico` はメキシコで発生したすべてのイベントを検索します。 - * `country:"United States"` はアメリカ合衆国で発生したすべてのイベントを検索します。 + * `country:de` finds all events that occurred in Germany. + * `country:Mexico` finds all events that occurred in Mexico. + * `country:"United States"` all finds events that occurred in the United States. {% ifversion fpt or ghec %} -## Audit log をエクスポートする +## Exporting the audit log {% data reusables.audit_log.export-log %} {% data reusables.audit_log.exported-log-keys-and-values %} {% endif %} -## Audit log API を使用する +## Using the audit log API -GraphQL API{% ifversion fpt or ghec %} または REST API を使用して Audit log を操作できます{% endif %}。 +You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}. {% ifversion fpt or ghec %} The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %} -### GraphQL API を使用する +### Using the GraphQL API {% endif %} {% note %} -**注釈**: {% data variables.product.prodname_enterprise %} を使用している Organization が Audit log GraphQL API を利用できます。 {% data reusables.gated-features.more-info-org-products %} +**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %} {% endnote %} @@ -148,20 +147,20 @@ To ensure your intellectual property is secure, and you maintain compliance for {% data reusables.audit_log.audit-log-api-info %} {% ifversion fpt or ghec %} -GraphQL API を使用して Git イベントを取得することはできませんので、ご注意ください。 Git イベントを取得するには、代わりに REST API を使用してください。 詳しい情報については、「[`git` category actions](#git-category-actions)」を参照してください。 +Note that you can't retrieve Git events using the GraphQL API. To retrieve Git events, use the REST API instead. For more information, see "[`git` category actions](#git-category-actions)." {% endif %} -GraphQL のレスポンスには、90 日から 120 日までのデータを含めることができます。 +The GraphQL response can include data for up to 90 to 120 days. -たとえば、GraphQL にリクエストして、Organization に新しく追加された Organization メンバー全員を表示できます。 詳細は「[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)」を参照してください。 +For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "[GraphQL API Audit Log]({% ifversion ghec%}/free-pro-team@latest{% endif %}/graphql/reference/interfaces#auditentry/)." {% ifversion fpt or ghec %} -### REST API を使用する +### Using the REST API {% note %} -**注釈:** Audit log REST API は、{% data variables.product.prodname_ghe_cloud %} のユーザのみが利用できます。 +**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. {% endnote %} @@ -170,143 +169,143 @@ To ensure your intellectual property is secure, and you maintain compliance for {% data reusables.audit_log.audit-log-git-events-retention %} -Audit log REST API の詳細については、「[Organization](/rest/reference/orgs#get-the-audit-log-for-an-organization)」を参照してください。 +For more information about the audit log REST API, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." {% endif %} -## Audit log のアクション +## Audit log actions -Audit log にイベントとして記録される最も一般的なアクションの概要です。 +An overview of some of the most common actions that are recorded as events in the audit log. {% ifversion fpt or ghec %} -### `account` カテゴリアクション +### `account` category actions -| アクション | 説明 | -| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `billing_plan_change` | Organization の[支払いサイクル](/articles/changing-the-duration-of-your-billing-cycle)が変わるときにトリガーされます。 | -| `plan_change` | Organization の[プラン](/articles/about-billing-for-github-accounts)が変わるときにトリガーされます。 | -| `pending_plan_change` | Organization のオーナーまたは支払いマネージャーが[支払い済みサブスクリプションをキャンセルまたはダウングレードする](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/)ときにトリガーされます。 | -| `pending_subscription_change` | [{% data variables.product.prodname_marketplace %} の無料トライアルが始まるか期限切れになる](/articles/about-billing-for-github-marketplace/)ときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `billing_plan_change` | Triggered when an organization's [billing cycle](/articles/changing-the-duration-of-your-billing-cycle) changes. +| `plan_change` | Triggered when an organization's [subscription](/articles/about-billing-for-github-accounts) changes. +| `pending_plan_change` | Triggered when an organization owner or billing manager [cancels or downgrades a paid subscription](/articles/how-does-upgrading-or-downgrading-affect-the-billing-process/). +| `pending_subscription_change` | Triggered when a [{% data variables.product.prodname_marketplace %} free trial starts or expires](/articles/about-billing-for-github-marketplace/). {% endif %} {% ifversion fpt or ghec %} -### `advisory_credit` カテゴリアクション +### `advisory_credit` category actions -| アクション | 説明 | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `accept` | ユーザがセキュリティアドバイザリのクレジットを受け入れるとトリガーされます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 | -| `create` | セキュリティアドバイザリの管理者がクレジットセクションにユーザを追加するとトリガーされます。 | -| `decline` | ユーザがセキュリティアドバイザリのクレジットを拒否するとトリガーされます。 | -| `destroy` | セキュリティアドバイザリの管理者がクレジットセクションからユーザを削除するとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `accept` | Triggered when someone accepts credit for a security advisory. For more information, see "[Editing a security advisory](/github/managing-security-vulnerabilities/editing-a-security-advisory)." +| `create` | Triggered when the administrator of a security advisory adds someone to the credit section. +| `decline` | Triggered when someone declines credit for a security advisory. +| `destroy` | Triggered when the administrator of a security advisory removes someone from the credit section. {% endif %} {% ifversion fpt or ghec %} -### `billing` カテゴリアクション +### `billing` category actions -| アクション | 説明 | -| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| `change_billing_type` | Organization が[{% data variables.product.prodname_dotcom %} の支払い方法を変更する](/articles/adding-or-editing-a-payment-method)ときにトリガーされます。 | -| `change_email` | Organization の[支払い請求先メール アドレス](/articles/setting-your-billing-email)が変わるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `change_billing_type` | Triggered when your organization [changes how it pays for {% data variables.product.prodname_dotcom %}](/articles/adding-or-editing-a-payment-method). +| `change_email` | Triggered when your organization's [billing email address](/articles/setting-your-billing-email) changes. {% endif %} -### `business`カテゴリアクション +### `business` category actions -| アクション | 説明 | -| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Enterpriseで、パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %} -| `set_actions_retention_limit` | {% data variables.product.prodname_actions %}の成果物とログの保持期間がEnterpriseで変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %} +| Action | Description +|------------------|-------------------{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "{% ifversion fpt or ghec%}[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."{% endif %} {% ifversion fpt or ghec %} -### `codespaces` カテゴリアクション +### `codespaces` category actions -| アクション | 説明 | -| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `create` | ユーザが[Codespaceを作成](/github/developing-online-with-codespaces/creating-a-codespace)するとトリガーされます。 | -| `resume` | ユーザがサスペンドされたCodespaceを再開するとトリガーされます。 | -| `delete` | ユーザが[Codespaceを削除](/github/developing-online-with-codespaces/deleting-a-codespace)するとトリガーされます。 | -| `create_an_org_secret` | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を作成するとトリガーされます。 | -| `update_an_org_secret` | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を更新するとトリガーされます。 | -| `remove_an_org_secret` | ユーザがOrganizationレベルの[{% data variables.product.prodname_codespaces %}用シークレット](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)を削除するとトリガーされます。 | -| `manage_access_and_security` | ユーザが[Codespaceがアクセスできるリポジトリ](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces)を更新するとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a user [creates a codespace](/github/developing-online-with-codespaces/creating-a-codespace). +| `resume` | Triggered when a user resumes a suspended codespace. +| `delete` | Triggered when a user [deletes a codespace](/github/developing-online-with-codespaces/deleting-a-codespace). +| `create_an_org_secret` | Triggered when a user creates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces) +| `update_an_org_secret` | Triggered when a user updates an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). +| `remove_an_org_secret` | Triggered when a user removes an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). +| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces). {% endif %} {% ifversion fpt or ghec or ghes > 3.2 %} -### `dependabot_alerts` カテゴリアクション +### `dependabot_alerts` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. -### `dependabot_alerts_new_repos` カテゴリアクション +### `dependabot_alerts_new_repos` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. -### `dependabot_security_updates` カテゴリアクション +### `dependabot_security_updates` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Organization のオーナーが既存のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. -### `dependabot_security_updates_new_repos` カテゴリアクション +### `dependabot_security_updates_new_repos` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Organization のオーナーが新規のすべてのリポジトリに対して {% data variables.product.prodname_dependabot_security_updates %} を有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. {% endif %} {% ifversion fpt or ghec %} -### `dependency_graph` カテゴリアクション +### `dependency_graph` category actions -| アクション | 説明 | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Organization のオーナーが既存のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all existing repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all existing repositories. -### `dependency_graph_new_repos` カテゴリアクション +### `dependency_graph_new_repos` category actions -| アクション | 説明 | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを無効にするとトリガーされます。 詳しい情報については「[Organizatonのためのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」を参照してください。 | -| `enable` | Organization のオーナーが新規のすべてのリポジトリに対して依存関係グラフを有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables the dependency graph for all new repositories. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +| `enable` | Triggered when an organization owner enables the dependency graph for all new repositories. {% endif %} -### `discussion_post` カテゴリアクション +### `discussion_post` category actions -| アクション | 説明 | -| --------- | ------------------------------------------------------------------------------------------------ | -| `update` | [Team ディスカッションの投稿が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。 | -| `destroy` | [Team ディスカッションの投稿が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `update` | Triggered when [a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). +| `destroy` | Triggered when [a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). -### `discussion_post_reply` カテゴリアクション +### `discussion_post_reply` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------- | -| `update` | [Team ディスカッションの投稿への返答が編集される](/articles/managing-disruptive-comments/#editing-a-comment)ときにトリガーされます。 | -| `destroy` | [Team ディスカッションの投稿への返答が削除される](/articles/managing-disruptive-comments/#deleting-a-comment)ときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `update` | Triggered when [a reply to a team discussion post is edited](/articles/managing-disruptive-comments/#editing-a-comment). +| `destroy` | Triggered when [a reply to a team discussion post is deleted](/articles/managing-disruptive-comments/#deleting-a-comment). {% ifversion fpt or ghes or ghec %} -### `enterprise` カテゴリアクション +### `enterprise` category actions {% data reusables.actions.actions-audit-events-for-enterprise %} {% endif %} {% ifversion fpt or ghec %} -### `environment` カテゴリアクション +### `environment` category actions -| アクション | 説明 | -| ----------------------- | -------------------------------------------------------------------------------------------------------------------- | -| `create_actions_secret` | シークレットが環境で作成されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。 | -| `delete` | 環境が削除されるとトリガーされます。 詳しい情報については、「[環境を削除する](/actions/reference/environments#deleting-an-environment)」を参照してください。 | -| `remove_actions_secret` | シークレットが環境で削除されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。 | -| `update_actions_secret` | 環境内のシークレットが更新されたときにトリガーされます。 詳しい情報については、「[環境のシークレット](/actions/reference/environments#environment-secrets)」を参照してください。 | +| Action | Description +|------------------|------------------- +| `create_actions_secret` | Triggered when a secret is created in an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." +| `delete` | Triggered when an environment is deleted. For more information, see ["Deleting an environment](/actions/reference/environments#deleting-an-environment)." +| `remove_actions_secret` | Triggered when a secret is removed from an environment. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." +| `update_actions_secret` | Triggered when a secret in an environment is updated. For more information, see ["Environment secrets](/actions/reference/environments#environment-secrets)." {% endif %} {% ifversion ghae %} @@ -324,449 +323,448 @@ Audit log にイベントとして記録される最も一般的なアクショ {% endif %} {% ifversion fpt or ghec %} -### `git` カテゴリアクション +### `git` category actions {% note %} -**注釈:** Audit log の Git イベントにアクセスするには、Audit log REST API を使用する必要があります。 Audit log REST API は、{% data variables.product.prodname_ghe_cloud %} のユーザのみが利用できます。 詳しい情報については「[Organization](/rest/reference/orgs#get-the-audit-log-for-an-organization)」を参照してください。 +**Note:** To access Git events in the audit log, you must use the audit log REST API. The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only. For more information, see "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)." {% endnote %} {% data reusables.audit_log.audit-log-git-events-retention %} -| アクション | 説明 | -| ------ | --------------------------- | -| `クローン` | リポジトリがクローンされるとトリガーされます。 | -| `フェッチ` | リポジトリから変更がフェッチされるとトリガーされます。 | -| `プッシュ` | リポジトリに変更がプッシュされるとトリガーされます。 | +| Action | Description +|---------|---------------------------- +| `clone` | Triggered when a repository is cloned. +| `fetch` | Triggered when changes are fetched from a repository. +| `push` | Triggered when changes are pushed to a repository. {% endif %} -### `hook` カテゴリアクション +### `hook` category actions -| アクション | 説明 | -| ---------------- | ------------------------------------------------------------------------------- | -| `create` | Organization が所有するリポジトリに[新たなフックが追加された](/articles/creating-webhooks)ときにトリガーされます。 | -| `config_changed` | 既存のフックに変更された設定がある場合にトリガーされます。 | -| `destroy` | 既存のフックがリポジトリから削除されたときにトリガーされます。 | -| `events_changed` | フックでのイベントが変更された場合にトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when [a new hook was added](/articles/creating-webhooks) to a repository owned by your organization. +| `config_changed` | Triggered when an existing hook has its configuration altered. +| `destroy` | Triggered when an existing hook was removed from a repository. +| `events_changed` | Triggered when the events on a hook have been altered. -### `integration_installation_request` カテゴリアクション +### `integration_installation_request` category actions -| アクション | 説明 | -| -------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Organization のメンバーが、Organization 内で使用するために、Organization のオーナーにインテグレーションをインストールすることを要求するときにトリガーされます。 | -| `close` | Organization 内で使用するためにインテグレーションをインストールする要求が、Organization のオーナーにより承認または拒否されるか、あるいは要求を公開した Organization のメンバーによりキャンセルされるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when an organization member requests that an organization owner install an integration for use in the organization. +| `close` | Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request. ### `ip_allow_list` category actions -| アクション | 説明 | -| ---------------------------- | --------------------------------------------------------------------------------------------------------------- | -| `enable` | Triggered when an IP allow list was enabled for an organization. | -| `disable` | Triggered when an IP allow list was disabled for an organization. | -| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. | -| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. | +| Action | Description +|------------------|------------------- +| `enable` | Triggered when an IP allow list was enabled for an organization. +| `disable` | Triggered when an IP allow list was disabled for an organization. +| `enable_for_installed_apps` | Triggered when an IP allow list was enabled for installed {% data variables.product.prodname_github_apps %}. +| `disable_for_installed_apps` | Triggered when an IP allow list was disabled for installed {% data variables.product.prodname_github_apps %}. ### `ip_allow_list_entry` category actions -| アクション | 説明 | -| --------- | --------------------------------------------------------------- | -| `create` | Triggered when an IP address was added to an IP allow list. | -| `update` | Triggered when an IP address or its description was changed. | -| `destroy` | Triggered when an IP address was deleted from an IP allow list. | +| Action | Description +|------------------|------------------- +| `create` | Triggered when an IP address was added to an IP allow list. +| `update` | Triggered when an IP address or its description was changed. +| `destroy` | Triggered when an IP address was deleted from an IP allow list. -### `issue` カテゴリアクション +### `issue` category actions -| アクション | 説明 | -| --------- | -------------------------------------------------------------------------------------- | -| `destroy` | リポジトリで管理者権限を所有する Organization のオーナーまたは誰かが、Organization が所有するリポジトリから問題を削除するときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `destroy` | Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository. {% ifversion fpt or ghec %} -### `marketplace_agreement_signature` カテゴリアクション +### `marketplace_agreement_signature` category actions -| アクション | 説明 | -| -------- | --------------------------------------------------------------------------------------- | -| `create` | {% data variables.product.prodname_marketplace %} Developer Agreement に署名するときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when you sign the {% data variables.product.prodname_marketplace %} Developer Agreement. -### `marketplace_listing` カテゴリアクション +### `marketplace_listing` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------- | -| `承認` | 一覧表を {% data variables.product.prodname_marketplace %}に掲載することが承認されるときにトリガーされます。 | -| `create` | {% data variables.product.prodname_marketplace %} で自分のアプリケーションの一覧表を作成するときにトリガーされます。 | -| `delist` | 一覧表が {% data variables.product.prodname_marketplace %} から削除されるときにトリガーされます。 | -| `redraft` | 一覧表がドラフト状態に戻されるときにトリガーされます。 | -| `reject` | 一覧表が {% data variables.product.prodname_marketplace %} に掲載することを認められないときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `approve` | Triggered when your listing is approved for inclusion in {% data variables.product.prodname_marketplace %}. +| `create` | Triggered when you create a listing for your app in {% data variables.product.prodname_marketplace %}. +| `delist` | Triggered when your listing is removed from {% data variables.product.prodname_marketplace %}. +| `redraft` | Triggered when your listing is sent back to draft state. +| `reject` | Triggered when your listing is not accepted for inclusion in {% data variables.product.prodname_marketplace %}. {% endif %} {% ifversion fpt or ghes > 3.0 or ghec %} -### `members_can_create_pages` カテゴリアクション +### `members_can_create_pages` category actions -詳しい情報については「[Organizationの{% data variables.product.prodname_pages %}サイトの公開の管理](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)」を参照してください。 +For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." -| アクション | 説明 | -|:--------- |:-------------------------------------------------------------------------------------------------------------- | -| `enable` | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を有効化するときトリガーされます。 | -| `disable` | Organizationのオーナーが Organization のリポジトリについて {% data variables.product.prodname_pages %} サイトの公開を無効化するときトリガーされます。 | +| Action | Description | +| :- | :- | +| `enable` | Triggered when an organization owner enables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | +| `disable` | Triggered when an organization owner disables publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. | {% endif %} -### `org` カテゴリアクション +### `org` category actions -| アクション | 説明 | -| --------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -| `advanced_security_policy_selected_member_disabled` | Enterprise のオーナーが、Organization が所有するリポジトリで {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できないようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %} -| `advanced_security_policy_selected_member_enabled` | Enterprise のオーナーが、Organization が所有するリポジトリに対して {% data variables.product.prodname_GH_advanced_security %} 機能を有効化できるようにするとトリガーされます。 {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} -| `audit_log_export` | Organization の管理者が [Organization の Audit log のエクスポートを作成する](#exporting-the-audit-log)ときにトリガーされます。 エクスポートにクエリが含まれていた場合、ログには使用されたクエリとそのクエリに一致する Audit log エントリの数が一覧表示されます。 | -| `block_user` | Organization のオーナーが[Organization のリポジトリにユーザーがアクセスするのをブロックする](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)ときにトリガーされます。 | -| `cancel_invitation` | Organization の招待が取り消されている場合にトリガーされます。 |{% endif %}{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` | Organization に対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[Organization の暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)」を参照してください。{% endif %} |{% ifversion fpt or ghec %} -| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} -| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %} -| `disable_member_team_creation_permission` | Organization のオーナーがオーナーに Team 作成を制限するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 {% ifversion not ghae %} -| `disable_two_factor_requirement` | Organization のすべてのメンバー{% ifversion fpt or ghec %}、支払いマネージャー、{% endif %}および外部のコラボレータに対してオーナーが 2 要素認証を無効化するときにトリガーされます。{% endif %}{% ifversion fpt or ghec %} -| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} -| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %} -| `enable_member_team_creation_permission` | メンバーが Team を作成するのを Organizationのオーナーが許可するときにトリガーされます。 詳細は「[Organization のチーム作成権限を設定する](/articles/setting-team-creation-permissions-in-your-organization)」を参照してください。 {% ifversion not ghae %} -| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} -| `invite_member` | [新しいユーザーがOrganization に参加するよう招待](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)されたときにトリガーされます。 | -| `oauth_app_access_approved` | オーナーが [{% data variables.product.prodname_oauth_app %} へのアクセスを許可する](/articles/approving-oauth-apps-for-your-organization/)ときにトリガーされます。 | -| `oauth_app_access_denied` | オーナーが Organization への[以前に承認した {% data variables.product.prodname_oauth_app %} のアクセス権を無効にする](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization)ときにトリガーされます。 | -| `oauth_app_access_requested` | オーナーが Organization への {% data variables.product.prodname_oauth_app %} アクセスを許可することを Organization のメンバーが要求するときにトリガーされます。{% endif %} -| `register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[Organization へのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)」を参照してください。 | -| `remove_actions_secret` | {% data variables.product.prodname_actions %} シークレットが削除されるとトリガーされます。{% ifversion fpt or ghec %} -| `remove_billing_manager` | [オーナーが Organization から支払いマネージャーを削除する](/articles/removing-a-billing-manager-from-your-organization/)とき、または [Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、支払いマネージャーが 2 要素認証を使用しないか 2 要素認証を無効にしているときにトリガーされます。 -{% endif %} -| `remove_member` | [オーナーが Organization からメンバーを削除する](/articles/removing-a-member-from-your-organization/)とき {% ifversion not ghae %}、または[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、Organization のメンバーが 2 要素認証を使用しないか 2 要素認証を無効化するとき{% endif %}にトリガーされます。 Organization から [Organization のメンバーが自身を削除](/articles/removing-yourself-from-an-organization/)するときにもトリガーされます。 | -| `remove_outside_collaborator` | オーナーが Organization から外部のコラボレータを削除するとき{% ifversion not ghae %}、または[Organization で 2 要素認証が義務付けられている](/articles/requiring-two-factor-authentication-in-your-organization)が、外部のコラボレータが 2 要素認証を使用しないか 2 要素認証を無効化するとき{% endif %}にトリガーされます。 | -| `remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[Organization からランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)」を参照してください。 |{% ifversion ghec %} -| `revoke_external_identity` | Organization のオーナーがメンバーのリンクされたアイデンティティを取り消すときにトリガーされます。 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 | -| `revoke_sso_session` | Organization のオーナーがメンバーの SAML セッションを取り消すときにトリガーされます。 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 |{% endif %} -| `runner_group_created` | セルフホストランナーグループが作成されたときにトリガーされます。 詳しい情報については、「[Organization のセルフホストランナーグループを作成する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)」を参照してください。 | -| `runner_group_created` | セルフホストランナーグループが削除されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループの削除](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)」を参照してください。 | -| `runner_group_updated` | セルフホストランナーグループの設定が変更されたときにトリガーされます。 詳しい情報については「[セルフホストランナーグループのアクセスポリシーの変更](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)」を参照してください。 | -| `runner_group_runners_added` | セルフホストランナーがグループに追加されたときにトリガーされます。 詳しい情報については、「[セルフホストランナーをグループに移動する](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)」を参照してください。 | -| `runner_group_runner_removed` | セルフホストランナーをグループから削除するのにREST APIが使われたときにトリガーされます。 詳しい情報については、「[Organization のグループからセルフホストランナーを削除する](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)」を参照してください。 | -| `runner_group_runners_updated` | ランナーグループのメンバーリストが更新されたときにトリガーされます。 詳しい情報については、「[Organizationのグループにセルフホストランナーを設定する](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | Organizationで、パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 詳しい情報については「[パブリックフォークからのワークフローで承認を必須とする](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)」を参照してください。{% endif %} -| `set_actions_retention_limit` | {% data variables.product.prodname_actions %}の成果物とログの保持期間が変更されたときにトリガーされます。 For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 詳しい情報については「[プライベートリポジトリフォークからのワークフローの有効化](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)」を参照してください。{% endif %}{% ifversion fpt or ghec %} -| `unblock_user` | Organizationのオーナーが[ Organization からのユーザのブロックを解除](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)するときにトリガーされます。{% endif %}{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。{% endif %} -| `update_new_repository_default_branch_setting` | オーナーが Organization の新しいリポジトリのデフォルトブランチの名前を変更するときにトリガーされます。 詳しい情報については、「[Organization のリポジトリのデフォルブランチ名を管理する](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)」を参照してください。 | -| `update_default_repository_permission` | オーナーが Organization のメンバーのデフォルトリポジトリの権限レベルを変更するときにトリガーされます。 | -| `update_member` | オーナーがユーザーのロールをオーナーからメンバーに、またはメンバーからオーナーに変更するときにトリガーされます。 | -| `update_member_repository_creation_permission` | オーナーが Organization のメンバーのリポジトリ作成権限を変更するときにトリガーされます。{% ifversion fpt or ghec %} -| `update_saml_provider_settings` | Organization の SAML プロバイダ設定が更新されるときにトリガーされます。 | -| `update_terms_of_service` | Organization が標準利用規約と企業向け利用規約を切り替えるときにトリガーされます。 詳細は「[企業利用規約にアップグレードする](/articles/upgrading-to-the-corporate-terms-of-service)」を参照してください。{% endif %} +| Action | Description +|------------------|------------------- +| `add_member` | Triggered when a user joins an organization.{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +| `advanced_security_policy_selected_member_disabled` | Triggered when an enterprise owner prevents {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} +| `advanced_security_policy_selected_member_enabled` | Triggered when an enterprise owner allows {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %}{% endif %}{% ifversion fpt or ghec %} +| `audit_log_export` | Triggered when an organization admin [creates an export of the organization audit log](#exporting-the-audit-log). If the export included a query, the log will list the query used and the number of audit log entries matching that query. +| `block_user` | Triggered when an organization owner [blocks a user from accessing the organization's repositories](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization). +| `cancel_invitation` | Triggered when an organization invitation has been revoked. {% endif %}{% ifversion fpt or ghes or ghec %} +| `create_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is created for an organization. For more information, see "[Creating encrypted secrets for an organization](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)."{% endif %} {% ifversion fpt or ghec %} +| `disable_oauth_app_restrictions` | Triggered when an owner [disables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/disabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} +| `disable_saml` | Triggered when an organization admin disables SAML single sign-on for an organization.{% endif %}{% endif %} +| `disable_member_team_creation_permission` | Triggered when an organization owner limits team creation to owners. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} +| `disable_two_factor_requirement` | Triggered when an owner disables a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} +| `enable_oauth_app_restrictions` | Triggered when an owner [enables {% data variables.product.prodname_oauth_app %} access restrictions](/articles/enabling-oauth-app-access-restrictions-for-your-organization) for your organization.{% ifversion ghec %} +| `enable_saml` | Triggered when an organization admin [enables SAML single sign-on](/articles/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.{% endif %}{% endif %} +| `enable_member_team_creation_permission` | Triggered when an organization owner allows members to create teams. For more information, see "[Setting team creation permissions in your organization](/articles/setting-team-creation-permissions-in-your-organization)." |{% ifversion not ghae %} +| `enable_two_factor_requirement` | Triggered when an owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.{% endif %}{% ifversion fpt or ghec %} +| `invite_member` | Triggered when [a new user was invited to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization). +| `oauth_app_access_approved` | Triggered when an owner [grants organization access to an {% data variables.product.prodname_oauth_app %}](/articles/approving-oauth-apps-for-your-organization/). +| `oauth_app_access_denied` | Triggered when an owner [disables a previously approved {% data variables.product.prodname_oauth_app %}'s access](/articles/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to your organization. +| `oauth_app_access_requested` | Triggered when an organization member requests that an owner grant an {% data variables.product.prodname_oauth_app %} access to your organization.{% endif %} +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to an organization](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)." +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% ifversion fpt or ghec %} +| `remove_billing_manager` | Triggered when an [owner removes a billing manager from an organization](/articles/removing-a-billing-manager-from-your-organization/) or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and a billing manager doesn't use 2FA or disables 2FA. |{% endif %} +| `remove_member` | Triggered when an [owner removes a member from an organization](/articles/removing-a-member-from-your-organization/){% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disables 2FA{% endif %}. Also triggered when an [organization member removes themselves](/articles/removing-yourself-from-an-organization/) from an organization.| +| `remove_outside_collaborator` | Triggered when an owner removes an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication is required in an organization](/articles/requiring-two-factor-authentication-in-your-organization) and an outside collaborator does not use 2FA or disables 2FA{% endif %}. | +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from an organization](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)." {% ifversion ghec %} +| `revoke_external_identity` | Triggered when an organization owner revokes a member's linked identity. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." +| `revoke_sso_session` | Triggered when an organization owner revokes a member's SAML session. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." {% endif %} +| `runner_group_created` | Triggered when a self-hosted runner group is created. For more information, see "[Creating a self-hosted runner group for an organization](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)." +| `runner_group_removed` | Triggered when a self-hosted runner group is removed. For more information, see "[Removing a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)." +| `runner_group_updated` | Triggered when the configuration of a self-hosted runner group is changed. For more information, see "[Changing the access policy of a self-hosted runner group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)." +| `runner_group_runners_added` | Triggered when a self-hosted runner is added to a group. For more information, see [Moving a self-hosted runner to a group](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group). +| `runner_group_runner_removed` | Triggered when the REST API is used to remove a self-hosted runner from a group. For more information, see "[Remove a self-hosted runner from a group for an organization](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)." +| `runner_group_runners_updated`| Triggered when a runner group's list of members is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." +| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."{% endif %}{% ifversion fpt or ghec %} +| `unblock_user` | Triggered when an organization owner [unblocks a user from an organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization).{% endif %}{% ifversion fpt or ghes or ghec %} +| `update_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} +| `update_new_repository_default_branch_setting` | Triggered when an owner changes the name of the default branch for new repositories in the organization. For more information, see "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)." +| `update_default_repository_permission` | Triggered when an owner changes the default repository permission level for organization members. +| `update_member` | Triggered when an owner changes a person's role from owner to member or member to owner. +| `update_member_repository_creation_permission` | Triggered when an owner changes the create repository permission for organization members.{% ifversion fpt or ghec %} +| `update_saml_provider_settings` | Triggered when an organization's SAML provider settings are updated. +| `update_terms_of_service` | Triggered when an organization changes between the Standard Terms of Service and the Corporate Terms of Service. For more information, see "[Upgrading to the Corporate Terms of Service](/articles/upgrading-to-the-corporate-terms-of-service)."{% endif %} {% ifversion ghec %} -### `org_credential_authorization` カテゴリアクション +### `org_credential_authorization` category actions -| アクション | 説明 | -| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `grant` | [SAML シングルサインオンに使用するクレデンシャルをメンバーが認可する](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。 | -| `deauthorized` | [SAML シングルサインオンに使用するクレデンシャルの認可をメンバーが取り消す](/github/authenticating-to-github/authenticating-with-saml-single-sign-on)ときにトリガーされます。 | -| `revoke` | オーナーが[認可された認証情報を取り消す](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)ときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `grant` | Triggered when a member [authorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). +| `deauthorized` | Triggered when a member [deauthorizes credentials for use with SAML single sign-on](/github/authenticating-to-github/authenticating-with-saml-single-sign-on). +| `revoke` | Triggered when an owner [revokes authorized credentials](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization). {% endif %} {% ifversion fpt or ghes or ghae or ghec %} -### `organization_label` カテゴリアクション +### `organization_label` category actions -| アクション | 説明 | -| --------- | -------------------------- | -| `create` | デフォルトラベルが作成されるときにトリガーされます。 | -| `update` | デフォルトラベルが編集されるときにトリガーされます。 | -| `destroy` | デフォルトラベルが削除されるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a default label is created. +| `update` | Triggered when a default label is edited. +| `destroy` | Triggered when a default label is deleted. {% endif %} -### `oauth_application` カテゴリアクション +### `oauth_application` category actions -| アクション | 説明 | -| --------------- | ------------------------------------------------------------------------------------------ | -| `create` | 新たな {% data variables.product.prodname_oauth_app %} が作成されるときにトリガーされます。 | -| `destroy` | 既存の {% data variables.product.prodname_oauth_app %} が削除されるときにトリガーされます。 | -| `reset_secret` | {% data variables.product.prodname_oauth_app %} のクライアント シークレットがリセットされるときにトリガーされます。 | -| `revoke_tokens` | {% data variables.product.prodname_oauth_app %} のユーザートークンが取り消されるときにトリガーされます。 | -| `移譲` | 既存の {% data variables.product.prodname_oauth_app %} が新しい Organization に移譲されるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a new {% data variables.product.prodname_oauth_app %} is created. +| `destroy` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is deleted. +| `reset_secret` | Triggered when an {% data variables.product.prodname_oauth_app %}'s client secret is reset. +| `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked. +| `transfer` | Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization. {% ifversion fpt or ghes > 3.0 or ghec %} -### `packages` カテゴリアクション +### `packages` category actions -| アクション | 説明 | -| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | -| `package_version_published` | パッケージのバージョンが公開されるとトリガーされます。 | -| `package_version_deleted` | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 | -| `package_deleted` | パッケージ全体が削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 | -| `package_version_restored` | 特定のパッケージのバージョンが削除されるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 | -| `package_restored` | パッケージ全体がリストアされるとトリガーされます。 詳しい情報については、「[パッケージの削除とリストア](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。 | +| Action | Description | +|--------|-------------| +| `package_version_published` | Triggered when a package version is published. | +| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." +| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)." {% endif %} {% ifversion fpt or ghec %} -### `payment_method` カテゴリアクション +### `payment_method` category actions -| アクション | 説明 | -| -------- | ------------------------------------------------------- | -| `create` | 新しいクレジット カードや PayPal アカウントなど、新たな支払い方法が追加されるときにトリガーされます。 | -| `update` | 既存の支払い方法が更新されるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a new payment method is added, such as a new credit card or PayPal account. +| `update` | Triggered when an existing payment method is updated. {% endif %} -### `profile_picture` カテゴリアクション -| アクション | 説明 | -| ------ | -------------------------------------------- | -| update | Organization のプロファイル写真を設定または更新するときにトリガーされます。 | +### `profile_picture` category actions +| Action | Description +|------------------|------------------- +| update | Triggered when you set or update your organization's profile picture. -### `project` カテゴリアクション +### `project` category actions -| アクション | 説明 | -| ------------------------ | -------------------------------------------------------------------------------------- | -| `create` | プロジェクト ボードが作成されるときにトリガーされます。 | -| `link` | リポジトリがプロジェクト ボードにリンクされるときにトリガーされます。 | -| `rename` | プロジェクトボードの名前が変更されるときにトリガーされます。 | -| `update` | プロジェクト ボードが更新されるときにトリガーされます。 | -| `delete` | プロジェクトボードが削除されるときにトリガーされます。 | -| `unlink` | リポジトリがプロジェクトボードからリンク解除されるときにトリガーされます。 | -| `update_org_permission` | Organization のすべてのメンバーに対して、基本レベルの権限が変更または削除されるときにトリガーされます。 | -| `update_team_permission` | Team のプロジェクト ボードの権限レベルが変更されるとき、または Team がプロジェクト ボードに追加または削除されるときにトリガーされます。 | -| `update_user_permission` | Organization のメンバーまたは外部コラボレーターがプロジェクト ボードに追加または削除されるとき、または彼らの権限レベルが変更されている場合にトリガーされます。 | +| Action | Description +|--------------------|--------------------- +| `create` | Triggered when a project board is created. +| `link` | Triggered when a repository is linked to a project board. +| `rename` | Triggered when a project board is renamed. +| `update` | Triggered when a project board is updated. +| `delete` | Triggered when a project board is deleted. +| `unlink` | Triggered when a repository is unlinked from a project board. +| `update_org_permission` | Triggered when the base-level permission for all organization members is changed or removed. | +| `update_team_permission` | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. | +| `update_user_permission` | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed.| -### `protected_branch` カテゴリアクション +### `protected_branch` category actions -| アクション | 説明 | -| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | -| `create` | ブランチでブランチの保護が有効になるときにトリガーされます。 | -| `destroy` | ブランチでブランチの保護が無効になるときにトリガーされます。 | -| `update_admin_enforced` | リポジトリの管理者に対してブランチの保護が実施されるときにトリガーされます。 | -| `update_require_code_owner_review` | 必須コードオーナーレビューの実施がブランチで更新されるときにトリガーされます。 | -| `dismiss_stale_reviews` | 古い Pull Request の却下の実施がブランチで更新されるときにトリガーされます。 | -| `update_signature_requirement_enforcement_level` | 必須コミット署名の実施がブランチで更新されるときにトリガーされます。 | -| `update_pull_request_reviews_enforcement_level` | 必須 Pull Request レビューの実施がブランチで更新されるときにトリガーされます。 Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). | -| `update_required_status_checks_enforcement_level` | 必須ステータスチェックの実施がブランチで更新されるときにトリガーされます。 | -| `update_strict_required_status_checks_policy` | マージする前に最新にする必要があるブランチの要件が変更されるときにトリガーされます。 | -| `rejected_ref_update` | ブランチ更新の試行が拒否されるときにトリガーされます。 | -| `policy_override` | ブランチ保護の要件がリポジトリ管理者によってオーバーライドされるときにトリガーされます。{% ifversion fpt or ghes or ghae or ghec %} -| `update_allow_force_pushes_enforcement_level` | 保護されたブランチについて、フォースプッシュが有効化または無効化されるときにトリガーされます。 | -| `update_allow_deletions_enforcement_level` | 保護されたブランチについて、ブランチ削除が有効化または無効化されるときにトリガーされます。 | -| `update_linear_history_requirement_enforcement_level` | 保護されたブランチについて、必須の直線状のコミット履歴が有効化または無効化されるときにトリガーされます。 | +| Action | Description +|--------------------|--------------------- +| `create ` | Triggered when branch protection is enabled on a branch. +| `destroy` | Triggered when branch protection is disabled on a branch. +| `update_admin_enforced ` | Triggered when branch protection is enforced for repository administrators. +| `update_require_code_owner_review ` | Triggered when enforcement of required Code Owner review is updated on a branch. +| `dismiss_stale_reviews ` | Triggered when enforcement of dismissing stale pull requests is updated on a branch. +| `update_signature_requirement_enforcement_level ` | Triggered when enforcement of required commit signing is updated on a branch. +| `update_pull_request_reviews_enforcement_level ` | Triggered when enforcement of required pull request reviews is updated on a branch. Can be one of `0`(deactivated), `1`(non-admins), `2`(everyone). +| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch. +| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed. +| `rejected_ref_update ` | Triggered when a branch update attempt is rejected. +| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %} +| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch. +| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch. +| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch. {% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} -### `pull_request`カテゴリのアクション +### `pull_request` category actions -| アクション | 説明 | -| ----------------------- | ----------------------------------------------------------------------------- | -| `create` | Pull Requestが作成されたときにトリガーされます。 | -| `close` | Pull Requestがマージされずにクローズされたときにトリガーされます。 | -| `reopen` | 以前クローズされたPull Requestが再オープンされたときにトリガーされます。 | -| `マージ` | Pull Requestがマージされたときにトリガーされます。 | -| `indirect_merge` | Pull Requestのコミットがターゲットブランチにマージされたことで、そのPull Requestがマージされたと考えられるときにトリガーされます。 | -| `ready_for_review` | Pull Requestがレビューの準備ができたとしてマークされたときにトリガーされます。 | -| `converted_to_draft` | Pull Requestがドラフトに変換されたときにトリガーされます。 | -| `create_review_request` | レビューが要求されたときにトリガーされます。 | -| `remove_review_request` | レビューの要求が削除されたときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a pull request is created. +| `close` | Triggered when a pull request is closed without being merged. +| `reopen` | Triggered when a pull request is reopened after previously being closed. +| `merge` | Triggered when a pull request is merged. +| `indirect_merge` | Triggered when a pull request is considered merged because its commits were merged into the target branch. +| `ready_for_review` | Triggered when a pull request is marked as ready for review. +| `converted_to_draft` | Triggered when a pull request is converted to a draft. +| `create_review_request` | Triggered when a review is requested. +| `remove_review_request` | Triggered when a review request is removed. -### `pull_request_review`カテゴリのアクション +### `pull_request_review` category actions -| アクション | 説明 | -| -------- | ------------------------- | -| `サブミット` | レビューがサブミットされたときにトリガーされます。 | -| `却下` | レビューが却下されたときにトリガーされます。 | -| `delete` | レビューが削除されたときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `submit` | Triggered when a review is submitted. +| `dismiss` | Triggered when a review is dismissed. +| `delete` | Triggered when a review is deleted. -### `pull_request_review_comment`カテゴリのアクション +### `pull_request_review_comment` category actions -| アクション | 説明 | -| -------- | -------------------------- | -| `create` | レビューコメントが追加されたときにトリガーされます。 | -| `update` | レビューコメントが変更されたときにトリガーされます。 | -| `delete` | レビューコメントが削除されたときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when a review comment is added. +| `update` | Triggered when a review comment is changed. +| `delete` | Triggered when a review comment is deleted. {% endif %} -### `repo` カテゴリアクション +### `repo` category actions -| アクション | 説明 | -| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `access` | ユーザが Organization 内のリポジトリの[可視性を変更](/github/administering-a-repository/setting-repository-visibility)するとトリガーされます。 | -| `actions_enabled` | リポジトリに対して {% data variables.product.prodname_actions %} が有効化されたときにトリガーされます。 UI を使用して表示できます。 REST API を使用して Audit log にアクセスする場合、このイベントは対象外です。 詳しい情報については、「[REST API を使用する](#using-the-rest-api)」を参照してください。 | -| `add_member` | ユーザーが[リポジトリへのコラボレーションアクセスへの招待](/articles/inviting-collaborators-to-a-personal-repository)を受諾するときにトリガーされます。 | -| `add_topic` | リポジトリ管理者がリポジトリに[トピックを追加](/articles/classifying-your-repository-with-topics)するとトリガーされます。{% ifversion fpt or ghes > 3.0 or ghae or ghec %} -| `advanced_security_disabled` | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を無効にするとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。 | -| `advanced_security_enabled` | リポジトリ管理者がリポジトリの {% data variables.product.prodname_GH_advanced_security %} 機能を有効にするとトリガーされます。 詳しい情報については、「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)」を参照してください。{% endif %} -| `archived` | リポジトリの管理者が[リポジトリをアーカイブする](/articles/about-archiving-repositories)ときにトリガーされます。{% ifversion ghes %} -| `config.disable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが無効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | -| `config.enable_anonymous_git_access` | 公開リポジトリで[匿名の Git 読み取りアクセスが有効になる](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)ときにトリガーされます。 | -| `config.lock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロックされる](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。 | -| `config.unlock_anonymous_git_access` | リポジトリの[匿名の Git 読み取りアクセス設定がロック解除される](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)ときにトリガーされます。{% endif %} -| `create` | [新しいリポジトリが作成された](/articles/creating-a-new-repository)ときにトリガーされます。{% ifversion fpt or ghes or ghec %} -| `create_actions_secret` | リポジトリに対して {% data variables.product.prodname_actions %} シークレットが作成されたときにトリガーされます。 詳しい情報については、「[リポジトリの暗号化されたシークレットを作成する](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)」を参照してください。{% endif %} -| `destroy` | [リポジトリが削除される](/articles/deleting-a-repository)ときにトリガーされます。{% ifversion fpt or ghec %} -| `disable` | リポジトリが無効になるときにトリガーされます ([残高不足](/articles/unlocking-a-locked-account)などの場合)。{% endif %} -| `enable` | リポジトリが再び有効になるときにトリガーされます。{% ifversion fpt or ghes or ghec %} -| `remove_actions_secret` | {% data variables.product.prodname_actions %} シークレットが削除されたときにトリガーされます。{% endif %} -| `remove_member` | ユーザーが[リポジトリのコラボレーターではなくなる](/articles/removing-a-collaborator-from-a-personal-repository)ときにトリガーされます。 | -| `register_self_hosted_runner` | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については、「[リポジトリにセルフホストランナーを追加する](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)」を参照してください。 | -| `remove_self_hosted_runner` | セルフホストランナーが削除されたときにトリガーされます。 詳しい情報については、「[リポジトリからランナーを削除する](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)」を参照してください。 | -| `remove_topic` | リポジトリの管理者がリポジトリからトピックを削除するときにトリガーされます。 | -| `rename` | [リポジトリの名前が変更された](/articles/renaming-a-repository)ときにトリガーされます。{% ifversion fpt or ghes > 3.1 or ghae or ghec %} -| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." | -| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} -| `self_hosted_runner_updated` | ランナーアプリケーションが更新されたときにトリガーされます。 REST API及びUIを使って見ることができます。JSON/CSVエクスポートで見ることはできません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」を参照してください。{% endif %}{% ifversion fpt or ghec %} -| `set_actions_fork_pr_approvals_policy` | パブリックフォークからのワークフローが承認を必要とする設定が変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %} -| `set_actions_retention_limit` | {% data variables.product.prodname_actions %}の成果物とログの保持期間が変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %} -| `set_fork_pr_workflows_policy` | プライベートのリポジトリフォークのワークフローのポリシーが変更されたときにトリガーされます。 For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} -| `移譲` | [リポジトリが移譲される](/articles/how-to-transfer-a-repository)ときにトリガーされます。 | -| `transfer_start` | リポジトリの移譲が行われようとしているときにトリガーされます。 | -| `unarchived` | リポジトリ管理者がリポジトリをアーカイブ解除するとトリガーされます。{% ifversion fpt or ghes or ghec %} -| `update_actions_secret` | {% data variables.product.prodname_actions %} シークレットが更新されたときにトリガーされます。{% endif %} +| Action | Description +|------------------|------------------- +| `access` | Triggered when a user [changes the visibility](/github/administering-a-repository/setting-repository-visibility) of a repository in the organization. +| `actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)." +| `add_member` | Triggered when a user accepts an [invitation to have collaboration access to a repository](/articles/inviting-collaborators-to-a-personal-repository). +| `add_topic` | Triggered when a repository admin [adds a topic](/articles/classifying-your-repository-with-topics) to a repository.{% ifversion fpt or ghes > 3.0 or ghae or ghec %} +| `advanced_security_disabled` | Triggered when a repository administrator disables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." +| `advanced_security_enabled` | Triggered when a repository administrator enables {% data variables.product.prodname_GH_advanced_security %} features for the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository).".{% endif %} +| `archived` | Triggered when a repository admin [archives a repository](/articles/about-archiving-repositories).{% ifversion ghes %} +| `config.disable_anonymous_git_access` | Triggered when [anonymous Git read access is disabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.enable_anonymous_git_access` | Triggered when [anonymous Git read access is enabled](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository) in a public repository. +| `config.lock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is locked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access). +| `config.unlock_anonymous_git_access` | Triggered when a repository's [anonymous Git read access setting is unlocked](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access).{% endif %} +| `create` | Triggered when [a new repository is created](/articles/creating-a-new-repository).{% ifversion fpt or ghes or ghec %} +| `create_actions_secret` |Triggered when a {% data variables.product.prodname_actions %} secret is created for a repository. For more information, see "[Creating encrypted secrets for a repository](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-a-repository)."{% endif %} +| `destroy` | Triggered when [a repository is deleted](/articles/deleting-a-repository).{% ifversion fpt or ghec %} +| `disable` | Triggered when a repository is disabled (e.g., for [insufficient funds](/articles/unlocking-a-locked-account)).{% endif %} +| `enable` | Triggered when a repository is re-enabled.{% ifversion fpt or ghes or ghec %} +| `remove_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is removed.{% endif %} +| `remove_member` | Triggered when a user is [removed from a repository as a collaborator](/articles/removing-a-collaborator-from-a-personal-repository). +| `register_self_hosted_runner` | Triggered when a new self-hosted runner is registered. For more information, see "[Adding a self-hosted runner to a repository](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)." +| `remove_self_hosted_runner` | Triggered when a self-hosted runner is removed. For more information, see "[Removing a runner from a repository](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)." +| `remove_topic` | Triggered when a repository admin removes a topic from a repository. +| `rename` | Triggered when [a repository is renamed](/articles/renaming-a-repository).{% ifversion fpt or ghes > 3.1 or ghae or ghec %} +| `self_hosted_runner_online` | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)." +| `self_hosted_runner_offline` | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}{% ifversion fpt or ghes or ghec %} +| `self_hosted_runner_updated` | Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)."{% endif %}{% ifversion fpt or ghec %} +| `set_actions_fork_pr_approvals_policy` | Triggered when the setting for requiring approvals for workflows from public forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."{% endif %} +| `set_actions_retention_limit` | Triggered when the retention period for {% data variables.product.prodname_actions %} artifacts and logs is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)."{% ifversion fpt or ghes or ghec %} +| `set_fork_pr_workflows_policy` | Triggered when the policy for workflows on private repository forks is changed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#enabling-workflows-for-private-repository-forks)."{% endif %} +| `transfer` | Triggered when [a repository is transferred](/articles/how-to-transfer-a-repository). +| `transfer_start` | Triggered when a repository transfer is about to occur. +| `unarchived` | Triggered when a repository admin unarchives a repository.{% ifversion fpt or ghes or ghec %} +| `update_actions_secret` | Triggered when a {% data variables.product.prodname_actions %} secret is updated.{% endif %} {% ifversion fpt or ghec %} -### `repository_advisory` カテゴリアクション +### `repository_advisory` category actions -| アクション | 説明 | -| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `close` | ユーザがセキュリティアドバイザリをクローズするとトリガーされます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} のセキュリティアドバイザリについて](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 | -| `cve_request` | ユーザがセキュリティアドバイザリのドラフトのために {% data variables.product.prodname_dotcom %} に CVE (Common Vulnerabilities and Exposures) 番号をリクエストするとトリガーされます。 | -| `github_broadcast` | {% data variables.product.prodname_dotcom %} が {% data variables.product.prodname_advisory_database %} でセキュリティアドバイザリを公開するとトリガーされます。 | -| `github_withdraw` | {% data variables.product.prodname_dotcom %} が誤って公開されたセキュリティアドバイザリを撤回するとトリガーされます。 | -| `オープン` | ユーザがドラフトのセキュリティアドバイザリをオープンするとトリガーされます。 | -| `publish` | ユーザがセキュリティアドバイザリを公開するとトリガーされます。 | -| `reopen` | ユーザがドラフトのセキュリティアドバイザリとして再オープンするとトリガーされます。 | -| `update` | ユーザがドラフトまたは公開済みのセキュリティアドバイザリを編集するとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `close` | Triggered when someone closes a security advisory. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)." +| `cve_request` | Triggered when someone requests a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory. +| `github_broadcast` | Triggered when {% data variables.product.prodname_dotcom %} makes a security advisory public in the {% data variables.product.prodname_advisory_database %}. +| `github_withdraw` | Triggered when {% data variables.product.prodname_dotcom %} withdraws a security advisory that was published in error. +| `open` | Triggered when someone opens a draft security advisory. +| `publish` | Triggered when someone publishes a security advisory. +| `reopen` | Triggered when someone reopens as draft security advisory. +| `update` | Triggered when someone edits a draft or published security advisory. -### `repository_content_analysis`カテゴリアクション +### `repository_content_analysis` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `enable` | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を有効にする](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 | -| `disable` | Organization のオーナーまたはリポジトリへの管理者アクセス権を所有する人が[プライベート リポジトリに対してデータ使用設定を無効にする](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)ときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `enable` | Triggered when an organization owner or person with admin access to the repository [enables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). +| `disable` | Triggered when an organization owner or person with admin access to the repository [disables data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). {% endif %}{% ifversion fpt or ghec %} -### `repository_dependency_graph` カテゴリアクション +### `repository_dependency_graph` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% ifversion fpt or ghec %}プライベート{% endif %}リポジトリの依存関係グラフを無効にするとトリガーされます。 詳しい情報については、「[依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)」を参照してください。 | -| `enable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが{% ifversion fpt or ghec %}プライベート{% endif %}リポジトリの依存関係グラフを有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. {% endif %}{% ifversion ghec or ghes or ghae %} -### `repository_secret_scanning` カテゴリアクション +### `repository_secret_scanning` category actions -| アクション | 説明 | -| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | -| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -### `repository_vulnerability_alert` カテゴリアクション +### `repository_vulnerability_alert` category actions -| アクション | 説明 | -| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. 詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)」を参照してください。 | -| `却下` | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency. | -| `解決` | リポジトリへの書き込みアクセスを持つユーザが変更をプッシュして、プロジェクトの依存関係の脆弱性を更新および解決するとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `create` | Triggered when {% data variables.product.product_name %} creates a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. For more information, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." +| `dismiss` | Triggered when an organization owner or person with admin access to the repository dismisses a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency. +| `resolve` | Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency. {% endif %}{% ifversion fpt or ghec %} -### `repository_vulnerability_alerts` カテゴリアクション +### `repository_vulnerability_alerts` category actions -| アクション | 説明 | -| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `authorized_users_teams` | Organization のオーナーまたはリポジトリへの管理者権限を持つユーザが、リポジトリ内の脆弱性のある依存関係の {% data variables.product.prodname_dependabot_alerts %} を受け取ることを許可されたユーザまたは Team のリストを更新するとトリガーされます。 詳しい情報については「[リポジトリのセキュリティ及び分析の設定の管理](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)」を参照してください。 | -| `disable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を無効にするとトリガーされます。 | -| `enable` | リポジトリのオーナーまたはリポジトリへの管理者アクセスを持つユーザが {% data variables.product.prodname_dependabot_alerts %} を有効にするとトリガーされます。 | +| Action | Description +|------------------|------------------- +| `authorized_users_teams` | Triggered when an organization owner or a person with admin permissions to the repository updates the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." +| `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. +| `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. {% endif %}{% ifversion ghec %} ### `role` category actions -| アクション | 説明 | -| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | -| `destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | -| `update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." | +| Action | Description +|------------------|------------------- +|`create` | Triggered when an organization owner creates a new custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." +|`destroy` | Triggered when a organization owner deletes a custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." +|`update` | Triggered when an organization owner edits an existing custom repository role. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." {% endif %} {% ifversion ghec or ghes or ghae %} -### `secret_scanning` カテゴリアクション +### `secret_scanning` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | -| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all existing{% ifversion ghec %}, private or internal{% endif %} repositories. -### `secret_scanning_new_repos` カテゴリアクション +### `secret_scanning_new_repos` category actions -| アクション | 説明 | -| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. 詳しい情報については、「[シークレットスキャニングについて](/github/administering-a-repository/about-secret-scanning)」を参照してください。 | -| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. | +| Action | Description +|------------------|------------------- +| `disable` | Triggered when an organization owner disables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." +| `enable` | Triggered when an organization owner enables secret scanning for all new {% ifversion ghec %}private or internal {% endif %}repositories. {% endif %} {% ifversion fpt or ghec %} -### `sponsors` カテゴリアクション +### `sponsors` category actions -| アクション | 説明 | -| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `custom_amount_settings_change` | カスタム金額を有効または無効にするとき、または提案されたカスタム金額を変更するときにトリガーされます (「[スポンサーシップ層を管理する](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)」を参照)。 | -| `repo_funding_links_file_action` | リポジトリで FUNDING ファイルを変更したときにトリガーされます (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | -| `sponsor_sponsorship_cancel` | スポンサーシップをキャンセルしたときにトリガーされます (「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) | -| `sponsor_sponsorship_create` | アカウントをスポンサーするとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照) | -| `sponsor_sponsorship_payment_complete` | アカウントをスポンサーし、支払が処理されるとトリガーされます (「[オープンソースコントリビューターに対するスポンサー](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)」を参照) | -| `sponsor_sponsorship_preference_change` | スポンサードアカウントからメールで最新情報を受け取るかどうかを変更するとトリガーされます (「[スポンサーシップを管理する](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)」を参照) | -| `sponsor_sponsorship_tier_change` | スポンサーシップをアップグレードまたはダウングレードしたときにトリガーされます (「[スポンサーシップをアップグレードする](/articles/upgrading-a-sponsorship)」および「[スポンサーシップをダウングレードする](/articles/downgrading-a-sponsorship)」を参照) | -| `sponsored_developer_approve` | {% data variables.product.prodname_sponsors %} アカウントが承認されるとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） | -| `sponsored_developer_create` | {% data variables.product.prodname_sponsors %} アカウントが作成されるとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） | -| `sponsored_developer_disable` | {% data variables.product.prodname_sponsors %} アカウントが無効になるとトリガーされます | -| `sponsored_developer_redraft` | {% data variables.product.prodname_sponsors %} アカウントが承認済みの状態からドラフト状態に戻るとトリガーされます | -| `sponsored_developer_profile_update` | スポンサード Organization のプロフィールを編集するとトリガーされます（「[{% data variables.product.prodname_sponsors %} のプロフィール詳細を編集する](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)」を参照） | -| `sponsored_developer_request_approval` | 承認のために {% data variables.product.prodname_sponsors %} のアプリケーションをサブミットするとトリガーされます（「[Organization に{% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） | -| `sponsored_developer_tier_description_update` | スポンサーシップ層の説明を変更したときにトリガーされます (「[スポンサーシップ層を管理する](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)」を参照) | -| `sponsored_developer_update_newsletter_send` | スポンサーにメールで最新情報を送信するとトリガーされます (「[スポンサーに連絡する](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)」を参照) | -| `waitlist_invite_sponsored_developer` | 待ちリストから {% data variables.product.prodname_sponsors %} に参加するよう招待されたときにトリガーされます（「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） | -| `waitlist_join` | スポンサード Organization になるために待ちリストに参加するとトリガーされます（「[Organization に {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照） | +| Action | Description +|------------------|------------------- +| `custom_amount_settings_change` | Triggered when you enable or disable custom amounts, or when you change the suggested custom amount (see "[Managing your sponsorship tiers](/github/supporting-the-open-source-community-with-github-sponsors/managing-your-sponsorship-tiers)") +| `repo_funding_links_file_action` | Triggered when you change the FUNDING file in your repository (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") +| `sponsor_sponsorship_cancel` | Triggered when you cancel a sponsorship (see "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") +| `sponsor_sponsorship_create` | Triggered when you sponsor an account (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") +| `sponsor_sponsorship_payment_complete` | Triggered after you sponsor an account and your payment has been processed (see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)") +| `sponsor_sponsorship_preference_change` | Triggered when you change whether you receive email updates from a sponsored account (see "[Managing your sponsorship](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)") +| `sponsor_sponsorship_tier_change` | Triggered when you upgrade or downgrade your sponsorship (see "[Upgrading a sponsorship](/articles/upgrading-a-sponsorship)" and "[Downgrading a sponsorship](/articles/downgrading-a-sponsorship)") +| `sponsored_developer_approve` | Triggered when your {% data variables.product.prodname_sponsors %} account is approved (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_create` | Triggered when your {% data variables.product.prodname_sponsors %} account is created (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_disable` | Triggered when your {% data variables.product.prodname_sponsors %} account is disabled +| `sponsored_developer_redraft` | Triggered when your {% data variables.product.prodname_sponsors %} account is returned to draft state from approved state +| `sponsored_developer_profile_update` | Triggered when you edit your sponsored organization profile (see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)") +| `sponsored_developer_request_approval` | Triggered when you submit your application for {% data variables.product.prodname_sponsors %} for approval (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `sponsored_developer_tier_description_update` | Triggered when you change the description for a sponsorship tier (see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)") +| `sponsored_developer_update_newsletter_send` | Triggered when you send an email update to your sponsors (see "[Contacting your sponsors](/sponsors/receiving-sponsorships-through-github-sponsors/contacting-your-sponsors)") +| `waitlist_invite_sponsored_developer` | Triggered when you are invited to join {% data variables.product.prodname_sponsors %} from the waitlist (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") +| `waitlist_join` | Triggered when you join the waitlist to become a sponsored organization (see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)") {% endif %} -### `team` カテゴリアクション +### `team` category actions -| アクション | 説明 | -| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `add_member` | Organization のメンバーが[Team に追加される](/articles/adding-organization-members-to-a-team)ときにトリガーされます。 | -| `add_repository` | リポジトリの管理が Team に任せられるときにトリガーされます。 | -| `change_parent_team` | 子チームが作成されるとき、または[子チームの親が変更される](/articles/moving-a-team-in-your-organization-s-hierarchy)ときにトリガーされます。 | -| `change_privacy` | Team のプライバシー レベルが変更されるときにトリガーされます。 | -| `create` | 新たな Team が作成されるときにトリガーされます。 | -| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. 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)." | -| `destroy` | Team が Organization から削除されるときにトリガーされます。 | -| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. 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)." | -| `remove_member` | Organization のメンバーが[Team から削除される](/articles/removing-organization-members-from-a-team)ときにトリガーされます。 | -| `remove_repository` | リポジトリが Team の管理下でなくなるときにトリガーされます。 | +| Action | Description +|------------------|------------------- +| `add_member` | Triggered when a member of an organization is [added to a team](/articles/adding-organization-members-to-a-team). +| `add_repository` | Triggered when a team is given control of a repository. +| `change_parent_team` | Triggered when a child team is created or [a child team's parent is changed](/articles/moving-a-team-in-your-organization-s-hierarchy). +| `change_privacy` | Triggered when a team's privacy level is changed. +| `create` | Triggered when a new team is created. +| `demote_maintainer` | Triggered when a user was demoted from a team maintainer to a team member. 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)." +| `destroy` | Triggered when a team is deleted from the organization. +| `team.promote_maintainer` | Triggered when a user was promoted from a team member to a team maintainer. 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)." +| `remove_member` | Triggered when a member of an organization is [removed from a team](/articles/removing-organization-members-from-a-team). +| `remove_repository` | Triggered when a repository is no longer under a team's control. -### `team_discussions` カテゴリアクション +### `team_discussions` category actions -| アクション | 説明 | -| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `disable` | Organization のオーナーが Organization の Team ディスカッションを無効にするときにトリガーされます。 詳しい情報については [Organization の Team ディスカッションの無効化](/articles/disabling-team-discussions-for-your-organization)を参照してください。 | -| `enable` | Organization のオーナーが Organization の Team ディスカッションを有効にするときにトリガーされます。 | +| Action | Description +|---|---| +| `disable` | Triggered when an organization owner disables team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/articles/disabling-team-discussions-for-your-organization)." +| `enable` | Triggered when an organization owner enables team discussions for an organization. {% ifversion fpt or ghec or ghes > 3.1 or ghae %} -### `workflows` カテゴリアクション +### `workflows` category actions {% data reusables.actions.actions-audit-events-workflow %} {% endif %} -## 参考リンク +## Further reading - "[Keeping your organization secure](/articles/keeping-your-organization-secure)"{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5146 %} - "[Exporting member information for your organization](/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization)"{% endif %} diff --git a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md index 7e2203682f..b7d950e429 100644 --- a/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md +++ b/translations/ja-JP/content/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team.md @@ -3,7 +3,7 @@ title: Team のスケジュールされたリマインダーを管理する intro: Team に対してレビュー待ちのプルリクエストがあるとき、Slack でリマインダーを受け取ることができます。 redirect_from: - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests - - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your team + - /github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-your-team versions: fpt: '*' ghec: '*' diff --git a/translations/ja-JP/content/rest/reference/pages.md b/translations/ja-JP/content/rest/reference/pages.md index 880fca8db8..58482b1bd0 100644 --- a/translations/ja-JP/content/rest/reference/pages.md +++ b/translations/ja-JP/content/rest/reference/pages.md @@ -27,6 +27,7 @@ GitHub Pages サイトの情報を返す {% data variables.product.prodname_page - `branch`: [サイトのソースファイル](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)を公開するために使用するリポジトリのブランチ。 たとえば、_main_ or _gh-pages_ などです。 - `path`: サイトの公開元のリポジトリディレクトリ。 `/` または `/docs` のどちらかとなります。 +{% comment %}An extra blank line is needed here to make sure the operations below don't continue the list above.{% endcomment %} {% for operation in currentRestOperations %} {% unless operation.subcategory %}{% include rest_operation %}{% endunless %} {% endfor %} diff --git a/translations/ja-JP/data/features/mermaid.yml b/translations/ja-JP/data/features/mermaid.yml new file mode 100644 index 0000000000..09870e35f9 --- /dev/null +++ b/translations/ja-JP/data/features/mermaid.yml @@ -0,0 +1,8 @@ +--- +#Issue 5812 and 6172 +#Mermaid syntax support +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-6172' diff --git a/translations/ja-JP/data/reusables/gpg/desktop-support-for-commit-signing.md b/translations/ja-JP/data/reusables/gpg/desktop-support-for-commit-signing.md index 3704166bf6..5093127a3e 100644 --- a/translations/ja-JP/data/reusables/gpg/desktop-support-for-commit-signing.md +++ b/translations/ja-JP/data/reusables/gpg/desktop-support-for-commit-signing.md @@ -1,5 +1,5 @@ {% note %} -**ノート：** [GitHub Desktop](https://desktop.github.com/)はコミット署名をサポートしていません。 +**Note:** [GitHub Desktop](https://desktop.github.com/) only supports commit signing if your Git client is configured to sign commits by default. {% endnote %} diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index f5ea5e0ba4..eaa8273a04 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -152,6 +152,7 @@ translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489 translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags +translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,broken liquid tags translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags translations/ja-JP/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags translations/ja-JP/content/packages/learn-github-packages/deleting-a-package.md,broken liquid tags