diff --git a/.github/workflows/optimize-images.yml b/.github/workflows/optimize-images.yml index bf7c46442827..756cd12425a2 100644 --- a/.github/workflows/optimize-images.yml +++ b/.github/workflows/optimize-images.yml @@ -41,7 +41,7 @@ jobs: git checkout $GITHUB_HEAD_REF echo "List the files that changed" - git diff --name-only $GITHUB_HEAD_REF $GITHUB_BASE_REF + git diff --name-only --diff-filter=d $GITHUB_BASE_REF $GITHUB_HEAD_REF echo "Run optipng on pngs in from the diff" git diff --name-only -z $GITHUB_HEAD_REF $GITHUB_BASE_REF -- '*.png' | xargs -0 optipng -nx diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 12ace91be1a2..3194cb9c3f62 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -479,16 +479,46 @@ branding: ### `branding.icon` -利用する[Feather](https://feathericons.com/)アイコンの名前。 - + @@ -503,7 +533,7 @@ branding: - + @@ -582,10 +612,10 @@ branding: - + - + @@ -635,12 +665,12 @@ branding: - + - + @@ -658,7 +688,7 @@ branding: - + @@ -760,13 +790,13 @@ branding: - + - + @@ -785,7 +815,7 @@ branding: - + @@ -807,7 +837,7 @@ branding: - + @@ -837,14 +867,14 @@ branding: - + - + diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index a54a9544b957..c02e8d813911 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -15,6 +15,13 @@ miniTocMaxHeadingLevel: 3 ## Monitoring your workflows +{% if github-runner-dashboard %} +### Monitoring your current jobs in your organization or enterprise + +{% data reusables.github-actions.github-hosted-runners-check-concurrency %} + +{% endif %} + {% ifversion fpt or ghae or ghes > 3.0 or ghec %} ### 視覚化グラフの利用 diff --git a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md index 8394d835deb5..16a0f24f9588 100644 --- a/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md @@ -86,7 +86,7 @@ The following table shows the permissions granted to the `GITHUB_TOKEN` by defau | checks | read/write | none | read | | contents | read/write | read | read | | deployments | read/write | none | read |{% ifversion fpt or ghec %} -| id-token | read/write | none | read |{% endif %} +| id-token | none | none | read |{% endif %} | issues | read/write | none | read | | metadata | read | read | read | | packages | read/write | none | read | diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index ce4cb11c31f1..547884a1f56c 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -141,6 +141,16 @@ In this example, the attempted script injection is unsuccessful: With this approach, the value of the {% raw %}`${{ github.event.issue.title }}`{% endraw %} expression is stored in memory and used as a variable, and doesn't interact with the script generation process. In addition, consider using double quote shell variables to avoid [word splitting](https://github.com/koalaman/shellcheck/wiki/SC2086), but this is [one of many](https://mywiki.wooledge.org/BashPitfalls) general recommendations for writing shell scripts, and is not specific to {% data variables.product.prodname_actions %}. +{% ifversion fpt or ghec %} +### Using starter workflows for code scanning + +{% data reusables.advanced-security.starter-workflows-beta %} +{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available. + +For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)." + +{% endif %} + ### Restricting permissions for tokens To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)." diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md index c35d53ff24ac..74adb103aa46 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/index.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/index.md @@ -7,6 +7,7 @@ versions: ghes: '*' children: - /about-github-hosted-runners + - /monitoring-your-current-jobs - /customizing-github-hosted-runners shortTitle: Use GitHub-hosted runners --- diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md new file mode 100644 index 000000000000..ac5027e2afb7 --- /dev/null +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md @@ -0,0 +1,30 @@ +--- +title: Monitoring your current jobs +intro: 'Monitor how {% data variables.product.prodname_dotcom %}-hosted runners are processing jobs in your organization or enterprise, and identify any related constraints.' +versions: + feature: github-runner-dashboard +shortTitle: Monitoring your current jobs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Viewing active jobs in your organization or enterprise + +You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise. + +{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.github-hosted-runners-table-entry %} +1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners. + + ![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png) + +## Viewing queued jobs in your organization or enterprise + +{% data variables.product.prodname_dotcom %}-hosted runners allow you to run jobs concurrently, and the maximum number of concurrent jobs will vary depending on your plan. If you reach the maximum number of concurrent jobs, any new jobs will start to enter a queue. To find out more about the number of concurrent jobs available to your plan, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration)." + +The following procedure demonstrates how to check the maximum number of concurrent jobs you can run. + +{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.github-hosted-runners-table-entry %} +1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. ![Screenshot of the maximum jobs for an account](/assets/images/help/settings/github-hosted-runners-max-jobs.png) diff --git a/translations/ja-JP/content/actions/using-jobs/using-concurrency.md b/translations/ja-JP/content/actions/using-jobs/using-concurrency.md index 62aa4d6cc5bd..20b1284a9f33 100644 --- a/translations/ja-JP/content/actions/using-jobs/using-concurrency.md +++ b/translations/ja-JP/content/actions/using-jobs/using-concurrency.md @@ -17,3 +17,8 @@ miniTocMaxHeadingLevel: 4 {% data reusables.actions.jobs.section-using-concurrency-jobs %} +{% if github-runner-dashboard %} +## Monitoring your current jobs in your organization or enterprise + +{% data reusables.github-actions.github-hosted-runners-check-concurrency %} +{% endif %} diff --git a/translations/ja-JP/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md b/translations/ja-JP/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md index 3463eb4fd48e..8051f7776a45 100644 --- a/translations/ja-JP/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md +++ b/translations/ja-JP/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md @@ -24,6 +24,8 @@ topics: {% data reusables.actions.workflow-organization-templates %} +{% data reusables.actions.starter-workflow-categories %} + ## Creating a starter workflow Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows. diff --git a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md index 2b9b9f0cfe04..d09b0f1a615d 100644 --- a/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/events-that-trigger-workflows.md @@ -685,6 +685,25 @@ on: {% endnote %} +#### Running your workflow when a pull request merges + +When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged. + +```yaml +on: + pull_request: + types: + - closed + +jobs: + if_merged: + if: github.event.pull_request.merged == true + runs-on: ubuntu-latest + steps: + - run: | + echo The PR was merged +``` + {% data reusables.developer-site.pull_request_forked_repos_link %} ### `pull_request_comment` (use `issue_comment`) @@ -869,6 +888,25 @@ on: {% endnote %} +#### Running your workflow when a pull request merges + +When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request_target` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged. + +```yaml +on: + pull_request_target: + types: + - closed + +jobs: + if_merged: + if: github.event.pull_request_target.merged == true + runs-on: ubuntu-latest + steps: + - run: | + echo The PR was merged +``` + ### `プッシュ` | webhook イベントのペイロード | アクティビティタイプ | `GITHUB_SHA` | `GITHUB_REF` | diff --git a/translations/ja-JP/content/actions/using-workflows/using-starter-workflows.md b/translations/ja-JP/content/actions/using-workflows/using-starter-workflows.md index ce1a152c8315..ca35b12ddacf 100644 --- a/translations/ja-JP/content/actions/using-workflows/using-starter-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/using-starter-workflows.md @@ -28,6 +28,8 @@ topics: {% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %} +{% data reusables.actions.starter-workflow-categories %} + You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)." ## Using starter workflows diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index fbe73981b0bc..0d133bdb7f1c 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -52,12 +52,6 @@ topics: {% data reusables.enterprise-accounts.dormant-user-release-phase %} -{% warning %} - -**Note:** During the private beta, ongoing improvements to the report download feature may limit its availability. - -{% endwarning %} - ## Downloading the dormant users report from your enterprise account {% data reusables.enterprise-accounts.access-enterprise %} diff --git a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 756d143b3a59..fca5817da7f3 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/ja-JP/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -40,6 +40,12 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr {% data reusables.dotcom_billing.pricing_cal %} +### Billing for {% data variables.product.prodname_codespaces %} prebuilds + +{% data reusables.codespaces.prebuilds-beta-note %} + +{% data reusables.codespaces.billing-for-prebuilds %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index ba3abc88d4b6..e5d16e2cfdfc 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -33,15 +33,26 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.code-scanning.enabling-options %} +{% ifversion ghes or ghae %} +{% note %} + +**Note:** If you want to use the CodeQL analysis, note that this article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + {% ifversion ghae %} ## Prerequisites -Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository. +Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository. Enterprise owners, organization and repository administrators can add self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." {% endif %} -## Setting up {% data variables.product.prodname_code_scanning %} using actions +{% ifversion fpt or ghec %} +## Setting up {% data variables.product.prodname_code_scanning %} using starter workflows + +{% data reusables.advanced-security.starter-workflows-beta %} {% ifversion ghes or ghae %} {% note %} @@ -51,13 +62,30 @@ Enterprise owners, organization and repository administrators can add self-hoste {% endnote %} {% endif %} -{% ifversion fpt or ghec %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %} +{% data reusables.advanced-security.starter-workflow-overview %} {% data variables.product.prodname_code_scanning_capc %} starter workflows are only available for your repository if {% data variables.product.prodname_code_scanning %} is enabled. + +{% data reusables.code-scanning.billing %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. If the repository has already at least one workflow set up and running, click **New workflow** and go to step 5. If there are currently no workflows configured for the repository, go to the next step. + ![Screenshot of the New workflow button](/assets/images/help/security/actions-new-workflow-button.png) +1. Scroll down to the "Security" category and click **Configure** under the workflow you want to configure, or click **View all** to see all available security workflows. + ![Screenshot of the Actions workflows security section](/assets/images/help/security/actions-workflows-security-section.png) +1. On the right pane of the workflow page, click **Documentation** and follow the on-screen instructions to tailor the workflow to your needs. + ![Screenshot of the Documentation tab for starter workflows](/assets/images/help/security/actions-workflows-documentation.png) + For more information, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows#using-starter-workflows)" and "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)." + +{% endif %} + +## Setting up {% data variables.product.prodname_code_scanning %} manually +{% data reusables.code-scanning.billing %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository. 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -73,9 +101,9 @@ Enterprise owners, organization and repository administrators can add self-hoste In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." -## Bulk set up of {% data variables.product.prodname_code_scanning %} +## Bulk set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. +You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. ## Viewing the logging output from {% data variables.product.prodname_code_scanning %} @@ -122,7 +150,7 @@ When the {% data variables.product.prodname_code_scanning %} jobs complete, {% d {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. +The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. {% else %} diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 16d884751c27..26a343456460 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -223,7 +223,7 @@ When you have decided on the most secure and reliable method for your CI server, | Option | Required | Usage | |--------|:--------:|-----| | `--repository` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% ifversion fpt or ghec %}, unless the repository is public{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." -| `--ref` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pulls/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pulls/NUMBER/merge`. +| `--ref` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pull/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pull/NUMBER/merge`. | `--commit` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed. | `--sarif` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %} | `--github-url` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %} diff --git a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index 2e77b5da3ab8..374c362bb888 100644 --- a/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -52,7 +52,7 @@ These examples also assume that the {% data variables.product.prodname_codeql_cl In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via `stdin`, or is stored in the `$GITHUB_TOKEN` environment variable. -The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. +The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pull/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pull/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. ### Single non-compiled language (JavaScript) diff --git a/translations/ja-JP/content/code-security/guides.md b/translations/ja-JP/content/code-security/guides.md index ecaf5f42abcf..4d9fe682de77 100644 --- a/translations/ja-JP/content/code-security/guides.md +++ b/translations/ja-JP/content/code-security/guides.md @@ -47,16 +47,16 @@ includeGuides: - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - - /code-security/security-advisories/about-github-security-advisories - - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory - - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /code-security/security-advisories/creating-a-security-advisory - - /code-security/security-advisories/editing-a-security-advisory - - /code-security/security-advisories/permission-levels-for-security-advisories - - /code-security/security-advisories/publishing-a-security-advisory - - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory - - /code-security/security-advisories/withdrawing-a-security-advisory + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/about-github-security-advisories-for-repositories + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /code-security/repository-security-advisories/creating-a-repository-security-advisory + - /code-security/repository-security-advisories/editing-a-repository-security-advisory + - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories + - /code-security/repository-security-advisories/publishing-a-repository-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory - /code-security/security-overview/about-the-security-overview - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions @@ -72,6 +72,7 @@ includeGuides: - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database + - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors diff --git a/translations/ja-JP/content/code-security/index.md b/translations/ja-JP/content/code-security/index.md index 49eee619c6c5..4cc88fec9208 100644 --- a/translations/ja-JP/content/code-security/index.md +++ b/translations/ja-JP/content/code-security/index.md @@ -8,7 +8,7 @@ featuredLinks: guides: - /code-security/getting-started/securing-your-repository - /code-security/getting-started/securing-your-organization - - '{% ifversion fpt %}/code-security/security-advisories/creating-a-security-advisory{% endif %}' + - '{% ifversion fpt %}/code-security/repository-security-advisories/creating-a-repository-security-advisory{% endif %}' - '{% ifversion ghes or ghae %}/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif%}' guideCards: - '{% ifversion fpt %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates{% endif %}' @@ -22,7 +22,7 @@ featuredLinks: popular: - '{% ifversion ghes %}/admin/release-notes{% endif %}' - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot @@ -51,7 +51,7 @@ children: - /getting-started - /secret-scanning - /code-scanning - - /security-advisories + - /repository-security-advisories - /supply-chain-security - /security-overview - /guides diff --git a/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md similarity index 94% rename from translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md rename to translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md index 64a558687149..844d9e5eeec7 100644 --- a/translations/ja-JP/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md @@ -1,6 +1,8 @@ --- title: セキュリティ脆弱性の調整された開示について intro: 脆弱性の開示は、セキュリティの報告者とリポジトリメンテナの調整された取り組みです。 +redirect_from: + - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -63,7 +65,7 @@ shortTitle: 協調開示 あなたがメンテナなら、リポジトリのセキュリティポリシーを設定するか、たとえばプロジェクトのREADMEファイルでセキュリティの報告方法を明確にしておくことによって、このパイプラインの開始時点からプロセスの所有権を取ることができます。 セキュリティポリシーの追加に関する情報については「[セキュリティポリシーについて](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)」を参照してください。 セキュリティポリシーがない場合、セキュリティの報告者はおそらくあなたにメールするか、非公開であなたに連絡しようとするでしょう。 あるいは、誰かがセキュリティの問題の詳細を含む（パブリックな）Issueをオープンするかもしれません。 - メンテナとしてコード中の脆弱性を開示するために、まずは{% data variables.product.prodname_dotcom %}でパッケージのリポジトリにドラフトのセキュリティアドバイザリを作成します。 {% data reusables.security-advisory.security-advisory-overview %} 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories)」を参照してください。 + メンテナとしてコード中の脆弱性を開示するために、まずは{% data variables.product.prodname_dotcom %}でパッケージのリポジトリにドラフトのセキュリティアドバイザリを作成します。 {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - 作成方法については、「[セキュリティアドバイザリを作成する](/github/managing-security-vulnerabilities/creating-a-security-advisory)」を参照してください。 + To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." diff --git a/translations/ja-JP/content/code-security/security-advisories/about-github-security-advisories.md b/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md similarity index 59% rename from translations/ja-JP/content/code-security/security-advisories/about-github-security-advisories.md rename to translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md index 44d257019c57..5511d2ed9671 100644 --- a/translations/ja-JP/content/code-security/security-advisories/about-github-security-advisories.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md @@ -1,10 +1,11 @@ --- -title: GitHub セキュリティアドバイザリについて +title: About GitHub Security Advisories for repositories intro: '{% data variables.product.prodname_security_advisories %} を使用して、リポジトリにおけるセキュリティの脆弱性に関する情報を非公開で議論、修正、公開できます。' redirect_from: - /articles/about-maintainer-security-advisories - /github/managing-security-vulnerabilities/about-maintainer-security-advisories - /github/managing-security-vulnerabilities/about-github-security-advisories + - /code-security/security-advisories/about-github-security-advisories versions: fpt: '*' ghec: '*' @@ -13,44 +14,46 @@ topics: - Security advisories - Vulnerabilities - CVEs -shortTitle: セキュリティアドバイザリ +shortTitle: Repository security advisories --- {% data reusables.repositories.security-advisory-admin-permissions %} {% data reusables.security-advisory.security-researcher-cannot-create-advisory %} -## {% data variables.product.prodname_security_advisories %} について +## {% data variables.product.prodname_security_advisories %}について -{% data reusables.security-advisory.disclosing-vulnerabilities %} 詳しい情報については「[セキュリティ脆弱性の調整された開示について](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)」を参照してください。 +{% data reusables.security-advisory.disclosing-vulnerabilities %} 詳しい情報については「[セキュリティ脆弱性の調整された開示について](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)」を参照してください。 {% data reusables.security-advisory.security-advisory-overview %} {% data variables.product.prodname_security_advisories %} では、次のことができます。 -1. セキュリティアドバイザリのドラフトを作成し、そのドラフトを用いて、プロジェクトに対する脆弱性の影響について非公開で議論します。 詳しい情報については、「[セキュリティアドバイザリを作成する](/github/managing-security-vulnerabilities/creating-a-security-advisory)」を参照してください。 +1. セキュリティアドバイザリのドラフトを作成し、そのドラフトを用いて、プロジェクトに対する脆弱性の影響について非公開で議論します。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." 2. 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 -3. パッチがリリースされたら、脆弱性のコミュニティに警告するため、セキュリティアドバイザリを公開してください。 詳しい情報については、「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」を参照してください。 +3. パッチがリリースされたら、脆弱性のコミュニティに警告するため、セキュリティアドバイザリを公開してください。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." {% data reusables.repositories.security-advisories-republishing %} -セキュリティアドバイザリに貢献した個人にクレジットを付与することができます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)」を参照してください。 +セキュリティアドバイザリに貢献した個人にクレジットを付与することができます。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)." {% data reusables.repositories.security-guidelines %} -セキュリティアドバイザリをリポジトリ中で作成した場合、そのセキュリティアドバイザリはリポジトリに残ります。 依存関係グラフでサポートされているあらゆるエコシステムに対するセキュリティアドバイザリは、[github.com/advisories](https://github.com/advisories)上の{% data variables.product.prodname_advisory_database %}に公開します。 特にnpmに対するものであるセキュリティアドバイザリについては、npmセキュリティアドバイザリにも公開します。 詳しい情報については[npmjs.com/advisories](https://www.npmjs.com/advisories)を参照してください。 +セキュリティアドバイザリをリポジトリ中で作成した場合、そのセキュリティアドバイザリはリポジトリに残ります。 依存関係グラフでサポートされているあらゆるエコシステムに対するセキュリティアドバイザリは、[github.com/advisories](https://github.com/advisories)上の{% data variables.product.prodname_advisory_database %}に公開します。 Anyone can submit a change to an advisory published in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." + +特にnpmに対するものであるセキュリティアドバイザリについては、npmセキュリティアドバイザリにも公開します。 詳しい情報については[npmjs.com/advisories](https://www.npmjs.com/advisories)を参照してください。 {% data reusables.repositories.github-security-lab %} ## CVE 識別番号 -{% data variables.product.prodname_security_advisories %} は、共通脆弱性識別子(CVE) リストに基づいています。 {% data variables.product.prodname_dotcom %}上のセキュリティアドバイザリフォームは、CVEの記述フォーマットにマッチする標準化されたフォームです。 +{% data variables.product.prodname_security_advisories %} は、Common Vulnerabilities and Exposures (CVE) リストに基づいています。 {% data variables.product.prodname_dotcom %}上のセキュリティアドバイザリフォームは、CVEの記述フォーマットにマッチする標準化されたフォームです。 {% data variables.product.prodname_dotcom %} は CVE Numbering Authority (CNA) であり、CVE 識別番号を割り当てる権限があります。 詳細については、CVE Web サイトの「[CVE について](https://www.cve.org/About/Overview)」および「[CVE Numbering Authorities](https://www.cve.org/ProgramOrganization/CNAs)」を参照してください。 {% data variables.product.prodname_dotcom %} でパブリックリポジトリのセキュリティアドバイザリを作成する場合、セキュリティの脆弱性に対する既存の CVE 識別番号を提供するオプションがあります。 {% data reusables.repositories.request-security-advisory-cve-id %} -セキュリティアドバイザリを公開し、{% data variables.product.prodname_dotcom %} が CVE 識別番号を脆弱性に割り当てたら、{% data variables.product.prodname_dotcom %} は CVE を MITER データベースに公開します。 詳しい情報については、「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)」を参照してください。 +セキュリティアドバイザリを公開し、{% data variables.product.prodname_dotcom %} が CVE 識別番号を脆弱性に割り当てたら、{% data variables.product.prodname_dotcom %} は CVE を MITER データベースに公開します。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." ## 公開されたセキュリティアドバイザリの {% data variables.product.prodname_dependabot_alerts %} diff --git a/translations/ja-JP/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md similarity index 56% rename from translations/ja-JP/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md rename to translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md index 93661e7f1981..9505c8ad548b 100644 --- a/translations/ja-JP/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: セキュリティアドバイザリにコラボレータを追加する +title: Adding a collaborator to a repository security advisory intro: あなたと協力するセキュリティアドバイザリとして、ユーザや Team を追加できます。 redirect_from: - /articles/adding-a-collaborator-to-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory + - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory versions: fpt: '*' ghec: '*' @@ -13,18 +14,20 @@ topics: - Security advisories - Vulnerabilities - Collaboration -shortTitle: アドバイザリにコラボレータを追加する +shortTitle: Add collaborators --- セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加できます。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## セキュリティアドバイザリにコラボレータを追加する -コラボレータは、セキュリティアドバイザリへの書き込み権限を持ちます。 詳しい情報については、「[セキュリティアドバイザリの権限レベル](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)」を参照してください。 +コラボレータは、セキュリティアドバイザリへの書き込み権限を持ちます。 For more information, see "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)." {% note %} -{% data reusables.repositories.security-advisory-collaborators-public-repositories %} セキュリティアドバイザリでのコラボレータの削除の詳細については、「[セキュリティアドバイザリからコラボレータを削除する](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)」を参照してください。 +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} For more information about removing a collaborator on a security advisory, see "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)." {% endnote %} @@ -37,6 +40,6 @@ shortTitle: アドバイザリにコラボレータを追加する ## 参考リンク -- 「[セキュリティアドバイザリの権限レベル](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)」 -- 「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」 -- 「[セキュリティアドバイザリからコラボレータを削除する](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)」 +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)." diff --git a/translations/ja-JP/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md similarity index 85% rename from translations/ja-JP/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md rename to translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md index 64c2228f4ba3..a86f316e529d 100644 --- a/translations/ja-JP/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md @@ -1,9 +1,10 @@ --- -title: 一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする +title: Collaborating in a temporary private fork to resolve a repository security vulnerability intro: リポジトリにおけるセキュリティ脆弱性の修正について非公開でコラボレートするため、一時的なプライベートフォークを作成できます。 redirect_from: - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability versions: fpt: '*' ghec: '*' @@ -16,9 +17,11 @@ topics: shortTitle: 一時的なプライベートフォーク --- +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 必要な環境 -一時的なプライベートフォークでコラボレートする前に、ドラフトのセキュリティアドバイザリを作成する必要があります。 詳しい情報については、「[セキュリティアドバイザリを作成する](/github/managing-security-vulnerabilities/creating-a-security-advisory)」を参照してください。 +一時的なプライベートフォークでコラボレートする前に、ドラフトのセキュリティアドバイザリを作成する必要があります。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." ## 一時的なプライベートフォークを作成する @@ -34,7 +37,7 @@ shortTitle: 一時的なプライベートフォーク ## 一時的なプライベートフォークにコラボレータを追加する -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加でき、セキュリティアドバイザリのコラボレータは一時的なプライベートフォークにアクセスできます。 詳しい情報については、「[セキュリティアドバイザリにコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)」を参照してください。 +セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加でき、セキュリティアドバイザリのコラボレータは一時的なプライベートフォークにアクセスできます。 For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." ## 一時的なプライベートフォークに変更を追加する @@ -76,9 +79,9 @@ shortTitle: 一時的なプライベートフォーク 4. [Security Advisories] のリストから、変更をマージするセキュリティアドバイザリをクリックします。 ![リスト内のセキュリティアドバイザリ](/assets/images/help/security/security-advisory-in-list.png) 5. 一時的なプライベートフォークにあるすべてのオープンされたプルリクエストをマージするには、[**Merge pull requests**] をクリックします。 ![[Merge pull requests] ボタン](/assets/images/help/security/merge-pull-requests-button.png) -セキュリティアドバイザリの変更をマージした後は、プロジェクトの以前のバージョンにある脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 詳しい情報については、「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」を参照してください。 +セキュリティアドバイザリの変更をマージした後は、プロジェクトの以前のバージョンにある脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." ## 参考リンク -- 「[セキュリティアドバイザリの権限レベル](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)」 -- 「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」 +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/security-advisories/creating-a-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md similarity index 66% rename from translations/ja-JP/content/code-security/security-advisories/creating-a-security-advisory.md rename to translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md index 789b5e2f1df7..c93af324a484 100644 --- a/translations/ja-JP/content/code-security/security-advisories/creating-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: セキュリティアドバイザリを作成する +title: Creating a repository security advisory intro: セキュリティアドバイザリのドラフトを作成して、オープンソースプロジェクトのセキュリティ脆弱性について非公開で議論して修正することができます。 redirect_from: - /articles/creating-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/creating-a-security-advisory + - /code-security/security-advisories/creating-a-security-advisory versions: fpt: '*' ghec: '*' @@ -12,7 +13,7 @@ type: how_to topics: - Security advisories - Vulnerabilities -shortTitle: アドバイザリの作成 +shortTitle: Create repository advisories --- リポジトリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリを作成できます。 @@ -35,7 +36,7 @@ shortTitle: アドバイザリの作成 ## 次のステップ - セキュリティアドバイザリのドラフトにコメントして、チームと脆弱性について話し合います。 -- セキュリティアドバイザリにコラボレータを追加します。 詳しい情報については、「[セキュリティアドバイザリにコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory)」を参照してください。 -- 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 詳細は「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照してください。 -- セキュリティアドバイザリへの貢献に対してクレジットを受け取る必要がある個人を追加します。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)」を参照してください。 -- コミュニティにセキュリティの脆弱性を知らせるため、セキュリティアドバイザリを公開します。 詳しい情報については、「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」を参照してください。 +- セキュリティアドバイザリにコラボレータを追加します。 For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." +- 一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートします。 For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)." +- セキュリティアドバイザリへの貢献に対してクレジットを受け取る必要がある個人を追加します。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)." +- コミュニティにセキュリティの脆弱性を知らせるため、セキュリティアドバイザリを公開します。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." diff --git a/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md similarity index 83% rename from translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md rename to translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md index 2d8c62dac943..69f60bf0bea9 100644 --- a/translations/ja-JP/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md @@ -1,8 +1,9 @@ --- -title: セキュリティアドバイザリを編集する -intro: 詳細を更新したりエラーを修正したりする必要がある場合は、セキュリティアドバイザリのメタデータと説明を編集できます。 +title: Editing a repository security advisory +intro: You can edit the metadata and description for a repository security advisory if you need to update details or correct errors. redirect_from: - /github/managing-security-vulnerabilities/editing-a-security-advisory + - /code-security/security-advisories/editing-a-security-advisory versions: fpt: '*' ghec: '*' @@ -10,10 +11,12 @@ type: how_to topics: - Security advisories - Vulnerabilities -shortTitle: アドバイザリの編集 +shortTitle: Edit repository advisories --- -セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリを編集できます。 +People with admin permissions to a repository security advisory can edit the security advisory. + +{% data reusables.security-advisory.repository-level-advisory-note %} ## セキュリティアドバイザリのクレジットについて @@ -40,4 +43,4 @@ shortTitle: アドバイザリの編集 ## 参考リンク -- 「[セキュリティアドバイザリを撤回する](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)」 +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/index.md b/translations/ja-JP/content/code-security/repository-security-advisories/index.md new file mode 100644 index 000000000000..58bf1aeb1468 --- /dev/null +++ b/translations/ja-JP/content/code-security/repository-security-advisories/index.md @@ -0,0 +1,29 @@ +--- +title: Managing repository security advisories for vulnerabilities in your project +shortTitle: Repository security advisories +intro: 'Discuss, fix, and disclose security vulnerabilities in your repositories using repository security advisories.' +redirect_from: + - /articles/managing-security-vulnerabilities-in-your-project + - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project + - /code-security/security-advisories +versions: + fpt: '*' + ghec: '*' +topics: + - Security advisories + - Vulnerabilities + - Repositories + - CVEs +children: + - /about-coordinated-disclosure-of-security-vulnerabilities + - /about-github-security-advisories-for-repositories + - /permission-levels-for-repository-security-advisories + - /creating-a-repository-security-advisory + - /adding-a-collaborator-to-a-repository-security-advisory + - /removing-a-collaborator-from-a-repository-security-advisory + - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /publishing-a-repository-security-advisory + - /editing-a-repository-security-advisory + - /withdrawing-a-repository-security-advisory +--- + diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md new file mode 100644 index 000000000000..3a9103f20713 --- /dev/null +++ b/translations/ja-JP/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md @@ -0,0 +1,45 @@ +--- +title: Permission levels for repository security advisories +intro: The actions you can take in a repository security advisory depend on whether you have admin or write permissions to the security advisory. +redirect_from: + - /articles/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories + - /code-security/security-advisories/permission-levels-for-security-advisories +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Security advisories + - Vulnerabilities + - Permissions +shortTitle: 権限レベル +--- + +This article applies only to repository-level security advisories. Anyone can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." + +## 権限の概要 + +{% data reusables.repositories.security-advisory-admin-permissions %} For more information about adding a collaborator to a security advisory, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." + +| アクション | Write 権限 | Admin 権限 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | +| セキュリティアドバイザリのドラフトを表示する | X | X | +| Add collaborators to the security advisory (see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | X | +| セキュリティアドバイザリでコメントを編集および削除する | X | X | +| Create a temporary private fork in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +| Add changes to a temporary private fork in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +| Create pull requests in a temporary private fork (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +| Merge changes in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +| Add and edit metadata in the security advisory (see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | X | X | +| Add and remove credits for a security advisory (see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | X | X | +| セキュリティアドバイザリのドラフトをクローズする | | X | +| Publish the security advisory (see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | X | + +## 参考リンク + +- "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" +- "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)" +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md similarity index 81% rename from translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md rename to translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md index a93ff1ac19dc..8804803e8c84 100644 --- a/translations/ja-JP/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: セキュリティアドバイザリを公開する +title: Publishing a repository security advisory intro: プロジェクト内のセキュリティ脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 redirect_from: - /articles/publishing-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/publishing-a-security-advisory + - /code-security/security-advisories/publishing-a-security-advisory versions: fpt: '*' ghec: '*' @@ -14,18 +15,20 @@ topics: - Vulnerabilities - CVEs - Repositories -shortTitle: アドバイザリの公開 +shortTitle: Publish repository advisories --- セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリを公開できます。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 必要な環境 -セキュリティアドバイザリを公開したり、CVE の ID 番号をリクエストしたりする前に、セキュリティアドバイザリのドラフトを作成し、セキュリティの脆弱性の影響を受けるプロジェクトのバージョンに関する情報を提供する必要があります。 詳しい情報については、「[セキュリティアドバイザリを作成する](/github/managing-security-vulnerabilities/creating-a-security-advisory)」を参照してください。 +セキュリティアドバイザリを公開したり、CVE の ID 番号をリクエストしたりする前に、セキュリティアドバイザリのドラフトを作成し、セキュリティの脆弱性の影響を受けるプロジェクトのバージョンに関する情報を提供する必要があります。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." -セキュリティアドバイザリを作成したが、セキュリティの脆弱性が影響を与えるプロジェクトのバージョンに関する詳細をまだ入力していない場合は、セキュリティアドバイザリを編集できます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 +セキュリティアドバイザリを作成したが、セキュリティの脆弱性が影響を与えるプロジェクトのバージョンに関する詳細をまだ入力していない場合は、セキュリティアドバイザリを編集できます。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." ## セキュリティアドバイザリの公開について @@ -33,7 +36,7 @@ shortTitle: アドバイザリの公開 {% data reusables.repositories.security-advisories-republishing %} -セキュリティアドバイザリを公開する前に、一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートできます。 詳細は「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照してください。 +セキュリティアドバイザリを公開する前に、一時的なプライベートフォークで、脆弱性を修正するため非公式でコラボレートできます。 For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)." {% warning %} @@ -60,7 +63,7 @@ shortTitle: アドバイザリの公開 セキュリティアドバイザリの URL は、セキュリティアドバイザリの公開後も公開前と同じままです。 リポジトリへの読み取りアクセス権を持つユーザは、セキュリティアドバイザリを閲覧することができます。 セキュリティアドバイザリのコラボレータは、管理者権限を持つユーザがコラボレータをセキュリティアドバイザリから削除しない限り、セキュリティアドバイザリでコメントストリーム全体を含む過去の会話を引き続き表示できます。 -公開したセキュリティアドバイザリの情報をアップデートまたは修正する必要がある場合は、セキュリティアドバイザリを編集できます。 詳しい情報については、「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory)」を参照してください。 +公開したセキュリティアドバイザリの情報をアップデートまたは修正する必要がある場合は、セキュリティアドバイザリを編集できます。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." ## セキュリティアドバイザリを公開する @@ -78,7 +81,7 @@ shortTitle: アドバイザリの公開 ## Requesting a CVE identification number (Optional) -{% data reusables.repositories.request-security-advisory-cve-id %} 詳しい情報については、「[{% data variables.product.prodname_security_advisories %} について](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)」を参照してください。 +{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -89,4 +92,4 @@ shortTitle: アドバイザリの公開 ## 参考リンク -- 「[セキュリティアドバイザリを撤回する](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)」 +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md similarity index 69% rename from translations/ja-JP/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md rename to translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md index cbd033ec5d6e..1a1b65ce5769 100644 --- a/translations/ja-JP/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md +++ b/translations/ja-JP/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md @@ -1,8 +1,9 @@ --- -title: セキュリティアドバイザリからコラボレータを削除する -intro: セキュリティアドバイザリからコラボレータを削除すると、そのコラボレータはセキュリティアドバイザリのディスカッションとメタデータへの読み取りおよび書き込みアクセス権を失います。 +title: Removing a collaborator from a repository security advisory +intro: 'When you remove a collaborator from a repository security advisory, they lose read and write access to the security advisory''s discussion and metadata.' redirect_from: - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory + - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory versions: fpt: '*' ghec: '*' @@ -16,6 +17,8 @@ shortTitle: コラボレータの削除 セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリからコラボレータを削除できます。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## セキュリティアドバイザリからコラボレータを削除する {% data reusables.repositories.security-advisory-collaborators-public-repositories %} @@ -29,5 +32,5 @@ shortTitle: コラボレータの削除 ## 参考リンク -- 「[セキュリティアドバイザリの権限レベル](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)」 -- 「[セキュリティアドバイザリにコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)」 +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md new file mode 100644 index 000000000000..652e4c35d6ca --- /dev/null +++ b/translations/ja-JP/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md @@ -0,0 +1,23 @@ +--- +title: Withdrawing a repository security advisory +intro: You can withdraw a repository security advisory that you've published. +redirect_from: + - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory + - /code-security/security-advisories/withdrawing-a-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities +shortTitle: Withdraw repository advisories +--- + +{% data reusables.security-advisory.repository-level-advisory-note %} + +誤ってセキュリティアドバイザリを公開した場合は、{% data variables.contact.contact_support %} に連絡するとセキュリティアドバイザリを撤回できます。 + +## 参考リンク + +- "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)" diff --git a/translations/ja-JP/content/code-security/security-advisories/index.md b/translations/ja-JP/content/code-security/security-advisories/index.md deleted file mode 100644 index 22875a177427..000000000000 --- a/translations/ja-JP/content/code-security/security-advisories/index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: プロジェクト中の脆弱性に関するセキュリティアドバイザリの管理 -shortTitle: セキュリティアドバイザリ -intro: セキュリティアドバイザリを利用したリポジトリ内のセキュリティ脆弱性に関する議論、修正、開示 -redirect_from: - - /articles/managing-security-vulnerabilities-in-your-project - - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project -versions: - fpt: '*' - ghec: '*' -topics: - - Security advisories - - Vulnerabilities - - Repositories - - CVEs -children: - - /about-coordinated-disclosure-of-security-vulnerabilities - - /about-github-security-advisories - - /permission-levels-for-security-advisories - - /creating-a-security-advisory - - /adding-a-collaborator-to-a-security-advisory - - /removing-a-collaborator-from-a-security-advisory - - /collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /publishing-a-security-advisory - - /editing-a-security-advisory - - /withdrawing-a-security-advisory ---- - diff --git a/translations/ja-JP/content/code-security/security-advisories/permission-levels-for-security-advisories.md b/translations/ja-JP/content/code-security/security-advisories/permission-levels-for-security-advisories.md deleted file mode 100644 index 7eccc1ecc759..000000000000 --- a/translations/ja-JP/content/code-security/security-advisories/permission-levels-for-security-advisories.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: セキュリティアドバイザリの権限レベル -intro: セキュリティアドバイザリで実行できるアクションは、セキュリティアドバイザリに対する管理者権限や書き込み権限を持っているかどうかによって変わります。 -redirect_from: - - /articles/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Security advisories - - Vulnerabilities - - Permissions -shortTitle: 権限レベル ---- - -## 権限の概要 - -{% data reusables.repositories.security-advisory-admin-permissions %}セキュリティアドバイザリへのコラボレータの追加についての詳細については、「[セキュリティアドバイザリからコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)」を参照してください。 - -| アクション | Write 権限 | Admin 権限 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | -| セキュリティアドバイザリのドラフトを表示する | X | X | -| セキュリティアドバイザリにコラボレータを追加する (「[セキュリティアドバイザリにコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)」を参照) | | X | -| セキュリティアドバイザリでコメントを編集および削除する | X | X | -| セキュリティアドバイザリに一時的なプライベートフォークを作成する (「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照) | | X | -| セキュリティアドバイザリの一時的なプライベートフォークに変更を追加する (「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照) | X | X | -| 一時的なプライベートフォークにプルリクエストを作成する (「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照) | X | X | -| セキュリティアドバイザリの変更をマージする (「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」を参照) | | X | -| セキュリティアドバイザリのメタデータを追加および編集する (「[セキュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」を参照) | X | X | -| セキュリティアドバイザリのクレジットを追加および削除する（「[セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)」を参照） | X | X | -| セキュリティアドバイザリのドラフトをクローズする | | X | -| セキュリティアドバイザリを公開する (「[キュリティアドバイザリを公開する](/github/managing-security-vulnerabilities/publishing-a-security-advisory)」を参照) | | X | - -## 参考リンク - -- 「[セキュリティアドバイザリにコラボレータを追加する](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)」 -- 「[一時的なプライベートフォークで、セキュリティ脆弱性を解決するためにコラボレートする](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)」 -- 「[セキュリティアドバイザリからコラボレータを削除する](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)」 -- 「[セキュリティアドバイザリを撤回する](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/security-advisories/withdrawing-a-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/withdrawing-a-security-advisory.md deleted file mode 100644 index 863805305bc8..000000000000 --- a/translations/ja-JP/content/code-security/security-advisories/withdrawing-a-security-advisory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: セキュリティアドバイザリを撤回する -intro: 公開したセキュリティアドバイザリを撤回できます。 -redirect_from: - - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities -shortTitle: アドバイザリの撤回 ---- - -誤ってセキュリティアドバイザリを公開した場合は、{% data variables.contact.contact_support %} に連絡するとセキュリティアドバイザリを撤回できます。 - -## 参考リンク - -- [セキュリティアドバイザリを編集する](/github/managing-security-vulnerabilities/editing-a-security-advisory) diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 8e996fa90cdd..7be2222f6583 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -75,6 +75,9 @@ Each security advisory contains information about the vulnerability, which may i {% endnote %} +## Editing an advisory in the {% data variables.product.prodname_advisory_database %} +You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." + ## {% data variables.product.prodname_advisory_database %} を検索する データベースを検索し、修飾子を使用して検索を絞り込むことができます。 たとえば、特定の日付、特定のエコシステム、または特定のライブラリで作成されたアドバイザリを検索できます。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md new file mode 100644 index 000000000000..5f75c903731c --- /dev/null +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md @@ -0,0 +1,32 @@ +--- +title: Editing security advisories in the GitHub Advisory Database +intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.' +redirect_from: + - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Alerts + - Dependabot + - Vulnerabilities + - CVEs +shortTitle: Edit Advisory Database +--- + +## About editing advisories in the {% data variables.product.prodname_advisory_database %} +Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted. + +Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)." +## Editing advisories in the GitHub Advisory Database + +1. Https://github.com/advisories にアクセスします。 +2. Select the security advisory you would like to contribute to. +3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link. ![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png) +4. In the contribution form, make the desired improvements. You can edit or add any detail. +5. When you finish editing the advisory, click **Submit improvements**. +6. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed. + +You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md index d5acb5f5d3cd..150d83c73486 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md @@ -23,6 +23,7 @@ topics: children: - /about-managing-vulnerable-dependencies - /browsing-security-vulnerabilities-in-the-github-advisory-database + - /editing-security-advisories-in-the-github-advisory-database - /about-alerts-for-vulnerable-dependencies - /configuring-notifications-for-vulnerable-dependencies - /about-dependabot-security-updates diff --git a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md index 5c1967fc3590..6b7910ad9a0d 100644 --- a/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md @@ -30,6 +30,8 @@ To see the pricing for {% data variables.product.prodname_codespaces %} usage, s Your codespace is billed for its compute minutes and for the amount of storage it uses on disk. +If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + ### Understanding what compute minutes are Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again. diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md index fd2ae496ee95..45ebdd95223e 100644 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md +++ b/translations/ja-JP/content/codespaces/customizing-your-codespace/index.md @@ -15,6 +15,5 @@ children: - /setting-your-default-editor-for-codespaces - /setting-your-default-region-for-codespaces - /setting-your-timeout-period-for-codespaces - - /prebuilding-codespaces-for-your-project --- diff --git a/translations/ja-JP/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/ja-JP/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md deleted file mode 100644 index 0351991d3e1e..000000000000 --- a/translations/ja-JP/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Prebuilding Codespaces for your project -intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals -product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Prebuild Codespaces ---- - -{% note %} - -**Note:** This feature is currently in private preview. - -{% endnote %} - -## About prebuilding a Codespace - -Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds. - -The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com. diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md index b526c31462f9..4e93dbceb165 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md @@ -23,6 +23,8 @@ If you choose to create a new codespace each time you work on a project, you sho If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. +{% data reusables.codespaces.prebuilds-crossreference %} + ## Saving changes in a codespace When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation. diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 9fd9da6552e8..e3dd89f7f60d 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -41,6 +41,8 @@ If you want to use Git hooks for your codespace, then you should set up hooks us {% data reusables.codespaces.you-can-see-all-your-codespaces %} +{% data reusables.codespaces.prebuilds-crossreference %} + ## Access to {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} diff --git a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md index 219849eb6178..b67cf81a4291 100644 --- a/translations/ja-JP/content/codespaces/getting-started/deep-dive.md +++ b/translations/ja-JP/content/codespaces/getting-started/deep-dive.md @@ -24,7 +24,7 @@ There are a number of entry points to create a codespace. Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace)」を参照してください。 -Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. +Once you've selected the option to create a new codespace, and chosen a machine type for your codespace, some steps happen in the background before the codespace is available to you. ![[Open with Codespaces] ボタン](/assets/images/help/codespaces/new-codespace-button.png) diff --git a/translations/ja-JP/content/codespaces/index.md b/translations/ja-JP/content/codespaces/index.md index bb6a9d789ddc..f26f2fdfd691 100644 --- a/translations/ja-JP/content/codespaces/index.md +++ b/translations/ja-JP/content/codespaces/index.md @@ -46,9 +46,10 @@ versions: children: - /overview - /getting-started + - /developing-in-codespaces - /setting-up-your-project-for-codespaces - /customizing-your-codespace - - /developing-in-codespaces + - /prebuilding-your-codespaces - /managing-your-codespaces - /managing-codespaces-for-your-organization - /codespaces-reference diff --git a/translations/ja-JP/content/codespaces/overview.md b/translations/ja-JP/content/codespaces/overview.md index 05d79b7972b0..dc4f8a2af166 100644 --- a/translations/ja-JP/content/codespaces/overview.md +++ b/translations/ja-JP/content/codespaces/overview.md @@ -13,7 +13,7 @@ redirect_from: versions: fpt: '*' ghec: '*' -type: quick_start +type: overview topics: - Codespaces --- diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md new file mode 100644 index 000000000000..d9652cb62073 --- /dev/null +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md @@ -0,0 +1,44 @@ +--- +title: About Codespaces prebuilds +shortTitle: About prebuilds +intro: Codespaces prebuilds help to speed up the creation of new codespaces. +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## 概要 + +Prebuilding your codespaces allows you to be more productive and access your codespace faster, regardless of the size and complexity of your project. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace. + +Whenever you push changes to your repository, {% data variables.product.prodname_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. + +When prebuilds are available for a particular branch of a repository, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the machine type dialog box that's displayed when you create a codespace and multiple machine types are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +## About billing for {% data variables.product.prodname_codespaces %} prebuilds + +{% data reusables.codespaces.billing-for-prebuilds %} For details of {% data variables.product.prodname_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." + +Use of codespaces created using prebuilds is charged at the same rate as regular codespaces. + +## About pushing changes to prebuild-enabled branches + +Each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild template. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. + +This means that if there are very frequent pushes to your repository, prebuild creation will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container on the branch. + +For example, let's imagine 5 pushes are made, in quick succession, against a branch that has a prebuild configuration. In this situation: + +* A workflow run is started for the first push, to update the prebuild template. +* If the 4 remaining pushes do not affect the dev container configuration, the workflow runs for these are queued in a "pending" state. + + If any of the remaining 4 pushes change the dev container configuration, then the service will not skip that one and will immediately run the prebuild creation workflow, updating the prebuild accordingly if it succeeds. + +* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild template. diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md new file mode 100644 index 000000000000..823e0fcbe862 --- /dev/null +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -0,0 +1,93 @@ +--- +title: Configuring prebuilds +shortTitle: Configure prebuilds +intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: "People with admin access to a repository can configure prebuilds for the repository." +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +You can set up a prebuild configuration for a specific branch of your repository. + +Any branch created from a prebuild-enabled base branch will typically also get assigned a prebuild during codespace creation. This is true if the dev container on the branch is the same as on the base branch. This is because the majority of the prebuild configuration for branches with the same dev container configuration are identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)." + +Typically, when you configure prebuilds for a branch, prebuilds will be available for {% data variables.product.prodname_codespaces %} machine types for that branch. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. + +## Prerequisites + +Before you can configure prebuilds for your project the following must be true: +* {% data variables.product.prodname_github_codespaces %} must be enabled for your organization. For more information, see "[Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +* {% data variables.product.prodname_actions %} must be enabled for your repository. Each prebuild configuration needs to be able to trigger an associated Actions workflow. 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 a prebuild + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**. +1. Under "Prebuild configuration", click **Set up prebuild**. + + ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png) + +1. Choose the branch for which you want to set up a prebuild. + + ![The Branch drop-down menu](/assets/images/help/codespaces/prebuilds-choose-branch.png) + + {% note %} + + **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds. For example, if you enable prebuilds for the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds. For more information, see "[Why do I get prebuilds for branches that do not have prebuilds enabled?](/codespaces/troubleshooting/troubleshooting-prebuilds#2-why-do-i-get-prebuilds-for-branches-that-do-not-have-prebuilds-enabled)" + + {% endnote %} + +1. Choose the regions in which you want to set up a prebuild. Developers must be located in a region you select to be able to create codespaces from a prebuild. Alternatively, select **All regions**. + + ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png) + + {% note %} + + **Notes**: + * The prebuild template for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + * Developers can set their default region for {% data variables.product.prodname_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces)." + + {% endnote %} + +1. Click **Create**. + + The prebuild configuration is listed on the {% data variables.product.prodname_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuild templates, based on the branch you selected, in the regions you specified. + + {% note %} + + **Note**: By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access resources in its own repository. If your project uses resources from outside of the repository, you'll need to set the `CODESPACES_PREBUILD_TOKEN` secret to grant the required access. For more information, see "[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + + {% endnote %} + +## Configuring access to resources that are not in the repository + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. If your project needs to access external resources to build the development environment, you will need to set up a personal access token (PAT) with the appropriate access scopes. + +For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## Configuring environment variables + +To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-an-organization)." + +Prebuilds do not use any user-level secrets while building your environment, because these are not added until after the codespace has been created. + +{% data variables.product.prodname_codespaces %} secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces. For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## Configuring time-consuming tasks to be included in the prebuild + +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." + +`onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. + +## Further reading + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md new file mode 100644 index 000000000000..5f3bdca59ad0 --- /dev/null +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/index.md @@ -0,0 +1,19 @@ +--- +title: Prebuilding your codespaces +intro: 'To speed up codespace creation, you can configure your project to prebuild codespaces for specific branches in specific regions.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +redirect_from: + - /codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project +children: + - /about-codespaces-prebuilds + - /configuring-prebuilds + - /managing-prebuilds + - /testing-dev-container-changes +--- + +{% data reusables.codespaces.prebuilds-beta-note %} \ No newline at end of file diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md new file mode 100644 index 000000000000..51bf964381c7 --- /dev/null +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -0,0 +1,109 @@ +--- +title: Managing prebuilds +shortTitle: Manage prebuilds +intro: 'You can review, modify, and delete the prebuild configurations for your repository.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## Checking, changing, and deleting your prebuild configurations + +The prebuilds that you configure are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_codespaces %} service. + +The workflow is triggered by these events: + +* Creating or updating the prebuild configuration +* Pushing a commit or a pull request to a branch that's configured to have prebuilds +* Manually triggering the workflow + +People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. + +### Viewing the progress of prebuilds +You can view the current status of the latest workflow run for each prebuild configuration you've set up on the {% data variables.product.prodname_codespaces %} page of your repository settings. For example, "Currently running" or "Last run 1 hour ago." + +To see the log output for the latest prebuild workflow run, click **See output**. + +![The 'See output' button](/assets/images/help/codespaces/prebuilds-see-output.png) + +This displays the output of the most recent run of the workflow in the **Actions** tab. + +![The prebuild workflow output](/assets/images/help/codespaces/prebuilds-log-output.png) + +Alternatively, to view all prebuild workflow runs associated with the specified branch, click the ellipsis button and choose **View runs** from the dropdown menu. + +![The 'View runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-view-runs.png) + +This displays the workflow run history for prebuilds for the associated branch. + +![The workflow run history](/assets/images/help/codespaces/prebuilds-workflow-runs.png) + +### Editing a prebuild configuration + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to edit. +1. In the dropdown menu, click **Edit**. + + ![The 'Edit' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-edit.png) + +1. Make the required changes to the prebuild configuration, then click **Update**. + +### Delete a prebuild configuration + +Deleting a prebuild configuration also deletes all previously created prebuild templates for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace. + +After you delete a prebuild configuration, workflow runs for that configuration that have been queued or started will still run. They will be listed in the workflow run history, along with previously completed workflow runs. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to delete. +1. In the dropdown menu, click **Delete**. + + ![The 'Delete' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-delete.png) + +1. Click **OK** to confirm the deletion. + +### Manually trigger prebuilds + +It may be useful to manually trigger a workflow run for a prebuild configuration. Generally this is only necessary if you are debugging a problem with the workflow for a prebuild configuration. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger. +1. In the dropdown menu, click **Manually trigger**. + + ![The 'Manually trigger' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) + +## Allowing a prebuild to access external resources + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. Your project may use additional resources to build the development environment, such as files in other repositories, packages, GHCR images, and APIs. To allow your prebuild setup to access these resources, you will need to create a new personal account and then use this account to create a personal access token (PAT) with the appropriate scopes. + +1. Create a new personal account on {% data variables.product.prodname_dotcom %}. + + {% warning %} + + **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + + {% endwarning %} +1. Give the new account read access to the required repositories. 詳細は、「[Organization のリポジトリへの個人のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)」を参照してください。 +1. While signed into the new account, create a PAT with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. 詳しい情報については、「[個人アクセストークンを作成する](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)」を参照してください。 + + !['repo' and 'packages' scopes selected for a PAT](/assets/images/help/codespaces/prebuilds-select-scopes.png) + + If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. 詳しい情報については「[パッケージのアクセス制御と可視性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。 +{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. 詳しい情報については「[SAMLシングルサインオンと使う個人アクセストークンの認可](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)」を参照してください。 + + ![The button to configure SSO for a PAT](/assets/images/help/codespaces/configure-SSO-for-PAT.png) + +{% endif %} +1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. +1. Sign back into the account that has admin access to the repository. +1. In the repository for which you want to create {% data variables.product.prodname_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)." + +The PAT will be used for all subsequent prebuild templates created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. + +## 参考リンク + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md new file mode 100644 index 000000000000..417e8623f596 --- /dev/null +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md @@ -0,0 +1,35 @@ +--- +title: Testing dev container configuration changes on a prebuild-enabled branch +shortTitle: Test dev container changes +allowTitleToDifferFromFilename: true +intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch. +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild template. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team. + +For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)." + +## Testing changes to the dev container configuration + +1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "[Creating a codespace ](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +1. In the codespace, check out a test branch. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)." +1. Make the required changes to the dev container configuration. +1. Apply the changes by rebuilding the container. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." +1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild template for that branch. + + {% note %} + + **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild. + + {% endnote %} diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md index 4e1820d03450..40cf3cd836f4 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md @@ -164,4 +164,8 @@ For more information about the available settings for `devcontainer.json`, see [ 1. {% data reusables.codespaces.recovery-mode %} Fix the errors in the configuration. ![Error message about recovery mode](/assets/images/help/codespaces/recovery-mode-error-message.png) - To diagnose the error by reviewing the creation logs, click **View creation log**. - To fix the errors identified in the logs, update your `devcontainer.json` file. - - To apply the changes, rebuild your container. + - To apply the changes, rebuild your container. + +## 参考リンク + +- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md index a991d786582f..37cc870c2255 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md @@ -1,6 +1,6 @@ --- title: Setting a minimum specification for codespace machines -shortTitle: Setting a minimum machine spec +shortTitle: Set a minimum machine spec intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.' permissions: People with write permissions to a repository can create or edit the codespace configuration. versions: diff --git a/translations/ja-JP/content/codespaces/troubleshooting/index.md b/translations/ja-JP/content/codespaces/troubleshooting/index.md index 4910ceea9a8f..988b43f7bd81 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/index.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/index.md @@ -16,6 +16,7 @@ children: - /exporting-changes-to-a-branch - /troubleshooting-creation-and-deletion-of-codespaces - /troubleshooting-your-connection-to-codespaces + - /troubleshooting-prebuilds - /troubleshooting-dotfiles-for-codespaces - /troubleshooting-port-forwarding-for-codespaces - /troubleshooting-codespaces-clients diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md new file mode 100644 index 000000000000..024569b88d66 --- /dev/null +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -0,0 +1,59 @@ +--- +title: Troubleshooting prebuilds +shortTitle: Codespaces prebuilds +intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds. +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +For more information about {% data variables.product.prodname_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)." + +## Checking whether a codespace was created from a prebuild? + +If multiple machine types are available when you create a codespace then a dialog box is displayed giving you a choice of machine types. This will display the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label beside machine types for which prebuilds are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." + +After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: + +```shell{:copy} +gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild +``` + +This returns `true` if the codespace was created using a prebuild. + +Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild: + +```shell{:copy} +cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME' +``` + +## The "Prebuild Ready" label is sometimes missing + +You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. + +Each time you push to a prebuild-enabled branch, the prebuild template is updated. If the push involves a change to the dev container then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the machine types dialog box. During this time you can still create codespaces without a prebuild template. + +If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container is changed on your branch, so that it's not the same as the dev container on the base branch, prebuilds will no longer be available on your branch. + +Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch: + +* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this. +* Confirm that the prebuild configuration includes your region. +* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will have to wait until the prebuild workflow run for this push completes before prebuilds are available again. +* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container, then there will be no available prebuilds for the associated branch. + +## 参考リンク + +- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)" +- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)" diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md index dcc0c4636ae2..7dfd19d6d1e8 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md @@ -45,7 +45,11 @@ shortTitle: Apply for a student pack ## 期限切れと更新 -{% data variables.product.prodname_student_pack %}アクセスが期限切れになった場合、まだあなたが適格であれば再応募できる場合があります。ただし、弊社のパートナーからの提供されているものの中には更新できないものがあります。 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 詳しい情報については[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)ページを参照してください。 +{% data variables.product.prodname_student_pack %}アクセスが期限切れになった場合、まだあなたが適格であれば再応募できる場合があります。ただし、弊社のパートナーからの提供されているものの中には更新できないものがあります。 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 To reapply, simply return to https://education.github.com, click your profile picture, then click **Reverify your academic affiliation**. + +![Menu option to reverify your academic affiliation](/assets/images/help/education/reverify-academic-affiliation.png) + +詳しい情報については[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)ページを参照してください。 無料の {% data variables.product.prodname_student_pack %} プランへのアクセス期限が切れる時期を知るには、アカウントの[支払い設定](https://github.com/settings/billing)にアクセスしてください。 diff --git a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 00820b68b53f..c053ec150b7c 100644 --- a/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/ja-JP/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -46,10 +46,12 @@ You can integrate your personal or organization account on {% data variables.pro ### Slack と {% data variables.product.product_name %} の統合 -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, and provide rich references to issues and pull requests without leaving Slack. +The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. -The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). 詳細については、Marketplace の[Slack 統合アプリケーション](https://github.com/marketplace/slack-github)にアクセスしてください。 +The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace. ### Microsoft Teams と {% data variables.product.product_name %} の統合 -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like close or open issues, comment on your issues and pull requests, and provide rich references to issues and pull requests without leaving Microsoft Teams. 詳細については、Microsoft AppSource の [Microsoft Teams 統合アプリケーション](https://appsource.microsoft.com/en-us/product/office/WA200002077)にアクセスしてください。 +The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. + +For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource. diff --git a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md index 0231b06a5a72..3b9c4546dbe6 100644 --- a/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md @@ -24,9 +24,9 @@ shortTitle: GitHub Advanced Security A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." -- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)." +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)." {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." @@ -95,6 +95,16 @@ If you have an enterprise account, license use for the entire enterprise is show {% endif %} +{% ifversion fpt or ghec %} +## About starter workflows for {% data variables.product.prodname_advanced_security %} + +{% data reusables.advanced-security.starter-workflows-beta %} +{% data reusables.advanced-security.starter-workflow-overview %} + +For more information on starter workflows, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)" and "[Using starter workflows](/actions/using-workflows/using-starter-workflows)." + +{% endif %} + {% ifversion ghec or ghes > 3.0 or ghae %} ## Further reading diff --git a/translations/ja-JP/content/get-started/using-github/github-command-palette.md b/translations/ja-JP/content/get-started/using-github/github-command-palette.md index c7a7db288f97..1c3a0ddeba2c 100644 --- a/translations/ja-JP/content/get-started/using-github/github-command-palette.md +++ b/translations/ja-JP/content/get-started/using-github/github-command-palette.md @@ -210,7 +210,7 @@ These commands are available only when you open the command palette from an issu | `Edit issue title` | Open the title of the issue ready for editing. | | `Lock issue` | Limit new comments to users with write access to the repository. 詳細は「[会話をロックする](/communities/moderating-comments-and-conversations/locking-conversations)」を参照してください。 | | `Pin`/`unpin issue` | Change whether or not the issue is shown in the pinned issues section for the repository. 詳細は「[Issue をリポジトリにピン止めする](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)」を参照してください。 | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this issue. 詳しい情報については、「[通知について](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)」を参照してください。 | +| `Subscribe`/`unsubscribe` | Opt in or out of notifications for changes to this issue. 詳しい情報については、「[通知について](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)」を参照してください。 | | `Transfer issue...` | Transfer the issue to another repository. 詳細は「[他のリポジトリへ Issue を移譲する](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)」を参照してください。 | ### Pull request commands @@ -225,5 +225,5 @@ These commands are available only when you open the command palette from a pull | `Edit pull request body` | Open the main body of the pull request ready for editing. | | `Edit pull request title` | Open the title of the pull request ready for editing. | | `Open in new codespace` | Create and open a codespace for the head branch of the pull request. 詳しい情報については、「[codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace)」を参照してください。 | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this pull request. 詳しい情報については、「[通知について](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)」を参照してください。 | +| `Subscribe`/`unsubscribe` | Opt in or out of notifications for changes to this pull request. 詳しい情報については、「[通知について](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)」を参照してください。 | | `Update current branch` | Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. 詳細は「[ブランチについて](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)」を参照してください。 | diff --git a/translations/ja-JP/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/ja-JP/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md index f7e5b94bbfd5..774fcbbbb7a5 100644 --- a/translations/ja-JP/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md +++ b/translations/ja-JP/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md @@ -18,7 +18,7 @@ topics: GitHubは、現代の奴隷制と児童労働が存在し続けていることを強く非難し、現代の奴隷制も児童労働も当社のサプライチェーンや当社の事業に占める位置がないようにするという責任を真剣に受け止めています。 (本声明における「現代の奴隷制」とは、奴隷制、強制または意思に反した労働、人身売買、隷属、および拘禁、年季奉公、拘束された労働者のことを指します。 「児童労働」とは、16歳未満、また軽労働では14歳未満による労働を指します。ただし、児童の就学を妨げる期間に限定されているものや、また児童の健康や幸福を妨げる条件ではないものを除きます。 -[英国現代奴隷法](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted)に従い、また[ILOによる強制労働条約の2014年の議定書](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029)、[労働における基本的原則及び権利に関するILO宣言](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm)、[国連の持続可能な開発目標　ターゲット8.7](https://sustainabledevelopment.un.org/sdg8)と協調し、現代版奴隷と児童労働に関する2018年の声明 (「本声明」) は、当社の事業やサプライチェーンで現代版奴隷や児童労働が生じることを防ぐためにGitHabが取ってきた行動について記載しています。 +In accordance with the [UK Modern Slavery Act](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), and in alignment with the [ILO 2014 Protocol to its Forced Labour Convention](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029), [ILO Declaration on Fundamental Principles and Rights at Work](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), and [United Nations Sustainable Development Goals target 8.7](https://www.unodc.org/roseap/en/sustainable-development-goals.html#:~:text=Target%208.7%20%2D%20Take%20immediate%20and,labour%20in%20all%20its%20forms), this 2018 Statement Against Modern Slavery and Child Labor ("the Statement") describes the steps GitHub has taken to prevent modern slavery and child labor from occurring in its business or supply chain. ## GitHubの組織、事業、およびサプライチェーン diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 7b44f44e452b..96179bb4a3bd 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -77,69 +77,69 @@ Organizationが{% data variables.product.prodname_ghe_cloud %}を使っている - **Manage wiki settings（Wiki設定の管理）**: リポジトリでWikiを有効化。 - **Manage project settings（プロジェクト設定の管理）**: リポジトリでプロジェクトを有効化。 - **Manage pull request merging settings（Pull Requestのマージ設定の管理）**: マージ、squash、リベースなど、リポジトリで許可されるマージコミットの種類を選択。 -- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください。 -- **Manage webhooks**: Add webhooks to the repository. -- **Manage deploy keys**: Add deploy keys to the repository. -- **Edit repository metadata**: Update the repository description as well as the repository topics. -- **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." -- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. 詳細は「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)」を参照してください。 -- **Push commits to protected branches**: Push to a branch that is marked as a protected branch. +- **Manage {% data variables.product.prodname_pages %} settings（設定の管理）**: リポジトリで{% data variables.product.prodname_pages %}を有効化し、公開したいブランチを選択。 詳しい情報については「[{% data variables.product.prodname_pages %} サイトの公開元を設定する](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)」を参照してください。 +- **Manage webhooks（webhookの管理）**: リポジトリにwebhookを追加。 +- **Manage deploy keys（デプロイキーを管理）**: リポジトリにデプロイキーを追加。 +- **Edit repository metadata（リポジトリのメタデータを編集）**: リポジトリの説明とともにリポジトリのトピックを更新。 +- **Set interaction limits（インタラクションの制限を設定）**: 自分のパブリックリポジトリで特定のユーザによるコメント、Issueのオープン、Pull Requestの作成を一時的に制限し、アクティビティの制限期間を施行。 詳しい情報については「[リポジトリでのインタラクションの制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 +- **Set the social preview（ソーシャルプレビューの設定）**: リポジトリがリンクされたときにソーシャルメディア上に表示される識別画像をリポジトリに追加。 詳細は「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)」を参照してください。 +- **Push commits to protected branches（保護されたブランチにコミットをプッシュ）**: 保護されたブランチとしてマークされているブランチにプッシュ。 ### セキュリティ -- **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts. -- **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts. -- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}. -- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}. -- **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts. +- **View {% data variables.product.prodname_code_scanning %} results（Code scanningの結果を表示）**: {% data variables.product.prodname_code_scanning %}アラートを表示できる。 +- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results（Code scanningの結果を却下もしくは再オープン）**: {% data variables.product.prodname_code_scanning %}アラートを却下もしくは再オープンできる。 +- **Delete {% data variables.product.prodname_code_scanning %} results（Code scanningの結果の削除）**: {% data variables.product.prodname_code_scanning %}アラートを削除できる。 +- **View {% data variables.product.prodname_dependabot_alerts %}（Dependabotアラートの表示）**: {% data variables.product.prodname_dependabot_alerts %}を見ることができる。 +- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}（Dependabotアラートを却下もしくは再オープン）**: {% data variables.product.prodname_dependabot_alerts %}を却下もしくは再オープンできる。 +- **View {% data variables.product.prodname_secret_scanning %} results（Secret scanningの結果の表示）**: {% data variables.product.prodname_secret_scanning %}アラートを表示できる。 +- **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results（Secret scanningの結果の却下もしくは再オープン）**: {% data variables.product.prodname_secret_scanning %}アラートを却下もしくは再オープンできる。 -## Precedence for different levels of access +## 様々なアクセスレベルの優先順位 -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. +TeamのメンバーシップやOrganizationの基本権限など、様々な方法を通じて様々なレベルのアクセスを与えられている場合、最上位のアクセスが他よりも優先されます。 たとえば、OrganizationのオーナーがOrganizationのメンバーに継承ロールの"Read"を使うカスタムロールを与え、そしてOrganizationのオーナーがOrganizationの基本権限を"Write"にした場合、このカスタムロールはカスタムロールに含まれている追加の権限とともに、書き込みアクセスを持つことになります。 {% 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. 詳しい情報については、以下を参照してください。 +競合するアクセスを解決するには、Organizationの基本アクセスあるいはTeamのアクセスを調整するか、カスタムロールを編集してください。 詳しい情報については、以下を参照してください。 - 「[Organization の基本レベルの権限の設定](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)」 - [OrganizationのリポジトリへのTeamのアクセスの管理](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) - - "[Editing a repository role](#editing-a-repository-role)" + - 「[リポジトリロールの編集](#editing-a-repository-role)」 -## Creating a repository role +## リポジトリロールの作成 -To create a new repository role, you add permissions to an inherited role and give the custom role a name. +新しいリポジトリロールを作成するには、継承されたロールに権限を追加し、カスタムロールに名前を付けます {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) -4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) -5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) -6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) -7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) -7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) +5. **Create a Role（ロールの作成）**をクリックしてください。 !["ロールの作成"ボタンのスクリーンショット](/assets/images/help/organizations/repository-role-create-role.png) +4. "Name（名前）"の下で、リポジトリロールの名前を入力してください。 ![リポジトリロールの名前の入力フィールド](/assets/images/help/organizations/repository-role-name.png) +5. "Description（説明）"の下で、リポジトリロールの説明を入力してください。 ![リポジトリロールの説明の入力フィールド](/assets/images/help/organizations/repository-role-description.png) +6. "Choose a role to inherit（継承するロールの選択）"の下で、継承したいロールを選択してください。 ![リポジトリロールの基本ロールの選択](/assets/images/help/organizations/repository-role-base-role-option.png) +7. "Add Permissions（権限の追加）"の下で、ドロップダウンメニューを使ってカスタムロールに含めたい権限を選択してください。 ![リポジトリロールのドロップダウンで権限レベルを選択](/assets/images/help/organizations/repository-role-drop-down.png) +7. **Create role（ロールの作成）**をクリックしてください。 ![リポジトリロールの作成の確認](/assets/images/help/organizations/repository-role-creation-confirm.png) -## Editing a repository role +## リポジトリロールの編集 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) -4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) +3. 編集したいロールの右で{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて**Edit（編集）**をクリックしてください。 ![リポジトリロールのドロップダウンメニュー内の選択肢を編集](/assets/images/help/organizations/repository-role-edit-setting.png) +4. 編集し、続いて**Update role（ロールの更新）**をクリックしてください。 ![リポジトリロールのフィールドを編集して更新](/assets/images/help/organizations/repository-role-update.png) -## Deleting a repository role +## リポジトリロールの削除 -If you delete an existing repository role, all pending invitations, teams, and users with the custom role will be reassigned to the organization's base permissions. +既存のリポジトリロールを削除すると、そのカスタムロールを持つ保留中の招待、Team、ユーザはすべてOrganizationの基本権限に割り当てなおされます。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) -4. Review changes for the role you want to remove, then click **Delete role**. ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) +3. 削除したいロールの右で{% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}をクリックし、続いて**Delete（削除）**をクリックしてください。 ![リポジトリロールのドロップダウンメニュー内の選択肢を編集](/assets/images/help/organizations/repository-role-delete-setting.png) +4. 削除したいロールに対する変更をレビューし、続いて**Delete role（ロールの削除）**をクリックしてください。 ![リポジトリロールの削除を確認](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md index c4c1475f3a70..1542632ead27 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: Managing security managers in your organization -intro: You can give your security team the least access they need to your organization by assigning a team to the security manager role. +title: Organizationでのセキュリティ管理者の管理 +intro: セキュリティ管理者のロールを割り当てることで、セキュリティチームにOrganizationに対する必要最小限のアクセスを付与できます。 versions: fpt: '*' ghes: '>=3.3' @@ -8,7 +8,7 @@ versions: topics: - Organizations - Teams -shortTitle: Security manager role +shortTitle: セキュリティ管理者のロール permissions: Organization owners can assign the security manager role. --- @@ -16,12 +16,12 @@ permissions: Organization owners can assign the security manager role. {% data reusables.organizations.about-security-managers %} -## Permissions for the security manager role +## セキュリティ管理者のロールの権限 -Members of a team with the security manager role have only the permissions required to effectively manage security for the organization. +セキュリティ管理者のロールを持つチームのメンバーは、Organizationのセキュリティを効率的に管理するのに必要な権限だけを持ちます。 -- Read access on all repositories in the organization, in addition to any existing repository access -- Write access on all security alerts in the organization {% ifversion not fpt %} +- 既存のすべてのリポジトリへのアクセスに加えて、Organization内のすべてのリポジトリへの読み取りアクセス +- Organization内のすべてのセキュリティアラートに対する書き込みアクセス{% ifversion not fpt %} - Access to the organization's security overview {% endif %} - The ability to configure security settings at the organization level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %} - The ability to configure security settings at the repository level{% ifversion not fpt %}, including the ability to enable or disable {% data variables.product.prodname_GH_advanced_security %}{% endif %} diff --git a/translations/ja-JP/data/features/github-runner-dashboard.yml b/translations/ja-JP/data/features/github-runner-dashboard.yml new file mode 100644 index 000000000000..f5fe71ecb494 --- /dev/null +++ b/translations/ja-JP/data/features/github-runner-dashboard.yml @@ -0,0 +1,4 @@ +--- +versions: + fpt: '*' + ghec: '*' diff --git a/translations/ja-JP/data/learning-tracks/code-security.yml b/translations/ja-JP/data/learning-tracks/code-security.yml index abee50a00362..91dbbde2ac23 100644 --- a/translations/ja-JP/data/learning-tracks/code-security.yml +++ b/translations/ja-JP/data/learning-tracks/code-security.yml @@ -2,17 +2,17 @@ #Feature available only on dotcom security_advisories: title: 'セキュリティ脆弱性の修正及び開示' - description: 'セキュリティアドバイザリを使用して報告された脆弱性を非公開で修正し、CVEを取得してください。' + description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' featured_track: '{% ifversion fpt %}true{% else %}false{% endif %}' guides: - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - - /code-security/security-advisories/creating-a-security-advisory - - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory - - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /code-security/security-advisories/publishing-a-security-advisory - - /code-security/security-advisories/editing-a-security-advisory - - /code-security/security-advisories/withdrawing-a-security-advisory - - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/creating-a-repository-security-advisory + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /code-security/repository-security-advisories/publishing-a-repository-security-advisory + - /code-security/repository-security-advisories/editing-a-repository-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory #Feature available on dotcom and GHES dependabot_alerts: title: '脆弱な依存関係に関する通知を取得' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml index bfcae7aaa382..a6eef4d23391 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -148,6 +148,7 @@ sections: - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 + - Actions services needs to be restarted after restoring appliance from backup taken on a different host. deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 diff --git a/translations/ja-JP/data/reusables/actions/starter-workflow-categories.md b/translations/ja-JP/data/reusables/actions/starter-workflow-categories.md new file mode 100644 index 000000000000..c8cc30285c2a --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/starter-workflow-categories.md @@ -0,0 +1,5 @@ +{% data variables.product.prodname_dotcom %} provides ready-to-use starter workflows for the following high level categories: +- **Deployment (CD)**. For more information, see "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)." +{% ifversion fpt or ghec %}- **Security**. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."{% endif %} +- **Continuous Integration (CI)**. 詳細については、「[継続的インテグレーションについて](/actions/automating-builds-and-tests/about-continuous-integration)」を参照してください。 +- **Automation**. Automation starter workflows offer solutions for automating workflows, such as triaging pull requests and applying a label based on the paths that are modified in the pull request, or greeting users who are first time contributors to the repository. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md b/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md new file mode 100644 index 000000000000..7425d26a2982 --- /dev/null +++ b/translations/ja-JP/data/reusables/advanced-security/starter-workflow-overview.md @@ -0,0 +1 @@ +{% data variables.product.product_name %} provides starter workflows for security features such as {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md b/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md new file mode 100644 index 000000000000..54baa92fc33d --- /dev/null +++ b/translations/ja-JP/data/reusables/advanced-security/starter-workflows-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Starter workflows for {% data variables.product.prodname_advanced_security %} have been consolidated in a "Security" category in the **Actions** tab of a repository. This new configuration is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/code-scanning/billing.md b/translations/ja-JP/data/reusables/code-scanning/billing.md new file mode 100644 index 000000000000..161bee54c084 --- /dev/null +++ b/translations/ja-JP/data/reusables/code-scanning/billing.md @@ -0,0 +1 @@ +{% ifversion fpt or ghec %}アクションを使用して {% data variables.product.prodname_code_scanning %} を実行すると、分数を消費します。 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md new file mode 100644 index 000000000000..da4d38341baa --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md @@ -0,0 +1,5 @@ +A {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." + +If you are an organization owner, you can track usage of prebuild workflows by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." 詳細については、「[{% data variables.product.prodname_actions %} の使用状況を表示する](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)」を参照してください。 + +While {% data variables.product.prodname_codespaces %} prebuilds is in beta there is no charge for storage of templates. When prebuilds become generally available, you will be billed for storing prebuild templates for each prebuild configuration in each region selected for that configuration. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md new file mode 100644 index 000000000000..7e48d1342cd4 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The ability to prebuild codespaces is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md new file mode 100644 index 000000000000..e7697bec4262 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/prebuilds-crossreference.md @@ -0,0 +1 @@ +To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-release-phase.md b/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-release-phase.md index 8b8f769a90a4..3ac13f76079f 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-release-phase.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/dormant-user-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Dormant Users report is currently in private beta so admins only have access to this feature with a special invite. To join the private beta, receive support, or address your questions, contact the {% data variables.product.company_short %} representative who helps manage your account. +**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability. {% endnote %} diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-check-concurrency.md new file mode 100644 index 000000000000..f216e917feaf --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-check-concurrency.md @@ -0,0 +1,5 @@ +To identify any constraints with concurrency or queuing, you can check how many jobs are currently being processed on the {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise. + +![Screenshot of a list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png) + +For more information, see "[Monitoring your current jobs](/actions/using-github-hosted-runners/monitoring-your-current-jobs)." \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md new file mode 100644 index 000000000000..62e6e350de17 --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md @@ -0,0 +1,12 @@ +{% ifversion fpt %} +1. Navigate to the main page of the organization or repository. +1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. +1. In the left sidebar, click **Actions**, then click **Runners**. +{% elsif ghec %} +1. Navigate to your runner settings: + * **In an organization or repository**: Navigate to the main page, then click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. + * **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise. +1. {% data variables.product.prodname_actions %}設定にアクセスしてください: + * **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**. + * **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-label="The law icon" %} Policies"**, then click **Actions**, then click the **Runners** tab. +{% endif %} diff --git a/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-table-entry.md new file mode 100644 index 000000000000..cb4e59b206fc --- /dev/null +++ b/translations/ja-JP/data/reusables/github-actions/github-hosted-runners-table-entry.md @@ -0,0 +1 @@ +1. In the "Runners" table, click the entry for **GitHub-hosted runners**. This entry will only be present if you're using {% data variables.product.prodname_dotcom %}-hosted runners. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/security-advisory/repository-level-advisory-note.md b/translations/ja-JP/data/reusables/security-advisory/repository-level-advisory-note.md new file mode 100644 index 000000000000..dd7f32d588fe --- /dev/null +++ b/translations/ja-JP/data/reusables/security-advisory/repository-level-advisory-note.md @@ -0,0 +1,7 @@ +{% note %} + +**Note**: This article applies to editing repository-level advisories as a repository owner. + +Users who are not repository owners can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." + +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/ui.yml b/translations/ja-JP/data/ui.yml index f1ed26a4eaac..51bd284c8c84 100644 --- a/translations/ja-JP/data/ui.yml +++ b/translations/ja-JP/data/ui.yml @@ -44,6 +44,7 @@ pages: miniToc: 'ここには以下の内容があります:' contributor_callout: この記事は、次の人によってコントリビュートされ、管理されています。 all_enterprise_releases: All Enterprise Server releases + about_versions: About versions errors: oops: 問題が発生しています。 something_went_wrong: 何か問題が生じています。 diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index cf778dcac9f3..762556c5d2b7 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -110,6 +110,7 @@ translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerab translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489 translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,broken liquid tags translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags +translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags translations/ja-JP/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,broken liquid tags translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,Listed in localization-support#489 translations/ja-JP/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-a-repository-from-your-local-computer-to-github-desktop.md,broken liquid tags diff --git a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md index e39d2b175dff..acb421c414fd 100644 --- a/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -479,7 +479,7 @@ Cor de fundo do selo. Pode ser: `branco`, `amarelo`, `azul`, `verde`, `laranja`, ### `branding.icon` -The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand icons are omitted as well as the following: +O nome do ícone de [Pena](https://feathericons.com/) da v4.28.0 a ser utilizado. Os ícones da marca são omitidos, assim como os itens seguintes:
activityアクティビティ airplay alert-circle alert-octagonalign-right anchor aperturearchiveアーカイブ
arrow-down-circlecloud-rain cloud-snow cloudcodeコード
commandコマンド compass copy corner-down-left
file-plus file-textfileファイル film
filterflagフラグ folder-minus folder-plus
hard-drivehashハッシュ headphones heart
repeatrewind巻き戻し rotate-ccw rotate-cw
rsssave保存 scissors search
shopping-cart shufflesidebarサイドバー skip-back
tablet
tagタグ target terminal thermometerupload-cloud
uploadアップロード user-check user-minus user-plus
user-xuserユーザ users video-off
@@ -508,7 +508,7 @@ The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand
-Here is an exhaustive list of all currently supported icons: +Aqui está uma lista taxativa de todos os ícones atualmente compatíveis: @@ -26,9 +26,9 @@ Qualquer pessoa com permissão de administrador para um consultor de segurança ## Pré-requisitos -Antes de publicar uma consultoria de segurança ou solicitar um número de identificação CVE, você deve criar um rascunho da consultoria de segurança e fornecer informações sobre as versões do seu projeto afetadas pela vulnerabilidade de segurança. For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." +Antes de publicar uma consultoria de segurança ou solicitar um número de identificação CVE, você deve criar um rascunho da consultoria de segurança e fornecer informações sobre as versões do seu projeto afetadas pela vulnerabilidade de segurança. Para obter mais informações, consulte "[Criando uma consultoria de segurança do repositório](/code-security/repository-security-advisories/creating-a-repository-security-advisory)". -Se você criou uma consultoria de segurança, mas ainda não forneceu as informações sobre as versões do seu projeto que a vulnerabilidade de segurança afeta, você pode editar a consultoria de segurança. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." +Se você criou uma consultoria de segurança, mas ainda não forneceu as informações sobre as versões do seu projeto que a vulnerabilidade de segurança afeta, você pode editar a consultoria de segurança. Para obter mais informações, consulte "[Editando uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)". ## Sobre a publicação de uma consultoria de segurança @@ -36,7 +36,7 @@ Ao publicar uma consultoria de segurança, você notifica a sua comunidade sobre {% data reusables.repositories.security-advisories-republishing %} -Antes de publicar uma consultoria de segurança, você pode colaborar de forma privada para consertar a vulnerabilidade em uma bifurcação privada temporária. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)." +Antes de publicar uma consultoria de segurança, você pode colaborar de forma privada para consertar a vulnerabilidade em uma bifurcação privada temporária. Para obter mais informações, consulte "[Colaborando em uma bifurcação privada temporária para resolver uma vulnerabilidade de segurança do repositório](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)". {% warning %} @@ -63,7 +63,7 @@ Ao publicar um rascunho de consultoria a partir de um repositório público, tod Depois de publicar uma consultoria de segurança, sua URL permanecerá a mesma de antes da publicação da consultoria de segurança. Qualquer pessoa com acesso de leitura ao repositório pode ver a consultoria de segurança. Os colaboradores na consultoria de segurança podem continuar a visualizar conversas anteriores, incluindo o fluxo de comentários completo na consultoria de segurança, a menos que alguém com permissões de administração remova o colaborador da consultoria de segurança. -Se você precisar atualizar ou corrigir informações em uma consultoria de segurança que publicou, poderá editar a consultoria de segurança. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." +Se você precisar atualizar ou corrigir informações em uma consultoria de segurança que publicou, poderá editar a consultoria de segurança. Para obter mais informações, consulte "[Editando uma consultoria de segurança do repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)". ## Publicar uma consultoria de segurança @@ -81,7 +81,7 @@ A publicação de uma consultor de segurança elimina a bifurcação privada tem ## Solicitando um número de identificação CVE (Opcional) -{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)." +{% data reusables.repositories.request-security-advisory-cve-id %} Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %} para repositórios](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -92,4 +92,4 @@ A publicação de uma consultor de segurança elimina a bifurcação privada tem ## Leia mais -- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" +- "[Retirando uma consultoria de segurança de repositório](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md index 599fe2c9cff0..c13e14c944ea 100644 --- a/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md +++ b/translations/pt-BR/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md @@ -1,6 +1,6 @@ --- -title: Removing a collaborator from a repository security advisory -intro: 'When you remove a collaborator from a repository security advisory, they lose read and write access to the security advisory''s discussion and metadata.' +title: Removendo um colaborador de uma consultoria de segurança de repositório +intro: 'Ao remover um colaborador de uma consultoria de segurança do repositório, ele perderá acesso de leitura e gravação às discussões e metadados da consultoria de segurança.' redirect_from: - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory @@ -32,5 +32,5 @@ As pessoas com permissões de administrador para uma consultoria de segurança p ## Leia mais -- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" -- "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" +- "[Níveis de permissão para consultoria de segurança do repositório](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Adicionar um colaborador a uma consultoria de segurança do repositório](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md index be1c09a07655..98a9c28da1bf 100644 --- a/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md +++ b/translations/pt-BR/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md @@ -1,6 +1,6 @@ --- -title: Withdrawing a repository security advisory -intro: You can withdraw a repository security advisory that you've published. +title: Retirando uma consultoria de segurança do repositório +intro: Você pode retirar uma consultoria de segurança do repositório que você publicou. redirect_from: - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory - /code-security/security-advisories/withdrawing-a-security-advisory @@ -11,7 +11,7 @@ type: how_to topics: - Security advisories - Vulnerabilities -shortTitle: Withdraw repository advisories +shortTitle: Retirar consultorias do repositório --- {% data reusables.security-advisory.repository-level-advisory-note %} @@ -20,4 +20,4 @@ Se você publicar uma consultoria de segurança por engano, poderá retirar a co ## Leia mais -- "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)" +- "[Editando uma consultoria de segurança de repositório](/code-security/repository-security-advisories/editing-a-repository-security-advisory)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md index d87a173ad3a4..b2d452d22ff5 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -75,8 +75,8 @@ O banco de dados também pode ser acessado usando a API do GraphQL. Para obter m {% endnote %} -## Editing an advisory in the {% data variables.product.prodname_advisory_database %} -You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." +## Editando uma consultoria em {% data variables.product.prodname_advisory_database %} +Você pode sugerir melhorias para qualquer consultoria em {% data variables.product.prodname_advisory_database %}. Para obter mais informações, consulte "[Editando consultorias de segurança em {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." ## Pesquisar em {% data variables.product.prodname_advisory_database %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md index 6a14544f806e..91ee6a0a3e8e 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md @@ -1,6 +1,6 @@ --- -title: Editing security advisories in the GitHub Advisory Database -intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.' +title: Editando consultorias de segurança no banco de dados consultivo do GitHub +intro: 'Você pode enviar melhorias para qualquer consultoria publicada no {% data variables.product.prodname_advisory_database %}.' redirect_from: - /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database versions: @@ -13,20 +13,20 @@ topics: - Dependabot - Vulnerabilities - CVEs -shortTitle: Edit Advisory Database +shortTitle: Editar banco de dados consultivo --- -## About editing advisories in the {% data variables.product.prodname_advisory_database %} -Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted. +## Sobre a edição de consultorias no {% data variables.product.prodname_advisory_database %} +Consultorias de segurança em {% data variables.product.prodname_advisory_database %} em [github.com/advisories](https://github.com/advisories) são consideradas consultorias globais. Qualquer pessoa pode sugerir melhorias em qualquer consultoria de segurança global na {% data variables.product.prodname_advisory_database %}. Você pode editar ou adicionar qualquer detalhe, incluindo ecossistemas adicionalmente afetados, nível de gravidade ou descrição de quem é impactado. A equipe de curadoria da {% data variables.product.prodname_security %} irá revisar as melhorias apresentadas e publicá-las em {% data variables.product.prodname_advisory_database %}, se aceitas. -Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)." -## Editing advisories in the GitHub Advisory Database +Somente proprietários e administradores de repositórios podem editar consultorias de segurança no nível do repositório. Para obter mais informações, consulte "[Editando uma consultoria de segurança do repositório](/code-security/security-advisories/editing-a-security-advisory)". +## Editando consultorias no banco de dados consultivo do GitHub 1. Navegue até https://github.com/advisories. -2. Select the security advisory you would like to contribute to. -3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link. ![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png) -4. In the contribution form, make the desired improvements. You can edit or add any detail. -5. When you finish editing the advisory, click **Submit improvements**. -6. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed. +2. Selecione a consultoria de segurança com a qual você gostaria de contribuir. +3. No lado direito da página, clique no link **Sugerir melhorias para esta vulnerabilidade**. ![Link para sugerir melhorias](/assets/images/help/security/suggest-improvements-to-advisory.png) +4. Na forma de contribuição, faça as melhorias desejadas. Você pode editar ou adicionar qualquer detalhe. +5. Quando terminar de editar a consultoria, clique em **Enviar melhorias**. +6. Depois de enviar suas melhorias, um pull request que contém suas alterações será criado para revisão em [github/advisory-database](https://github.com/github/advisory-database) pela equipe de curadoria de {% data variables.product.prodname_security %}. Se a consultoria se originar de um repositório {% data variables.product.prodname_dotcom %}, também marcaremos o editor original para comentários opcionais. Você pode ver o pull request e receber notificações quando ele for atualizado ou fechado. -You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). +Você também pode abrir um pull request diretamente em um arquivo consultivo no repositório [github/advisory-database](https://github.com/github/advisory-database). Para obter mais informações, consulte as [diretrizes de contribuição](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md). diff --git a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md index 941325adad23..46ff620b7f10 100644 --- a/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/pt-BR/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md @@ -30,6 +30,8 @@ Para ver os preços para uso de {% data variables.product.prodname_codespaces %} A cobrança do seu codespace é feita por minutos de computação e para a quantidade de armazenamento que usa no disco. +If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + ### Ententendo quais minutos de computação são A cobrança do seu codespace é feita pelo número de minutos ativos. Se sua janela de codespace estiver inativa por 30 minutos, ela será desligada automaticamente, e o cálculo da cobrança para o codespace terminará até que você inicie o codespace novamente. diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md index 434b913156d0..ca39b36c60b9 100644 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md +++ b/translations/pt-BR/content/codespaces/customizing-your-codespace/index.md @@ -15,6 +15,5 @@ children: - /setting-your-default-editor-for-codespaces - /setting-your-default-region-for-codespaces - /setting-your-timeout-period-for-codespaces - - /prebuilding-codespaces-for-your-project --- diff --git a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md deleted file mode 100644 index 6bc1a8535382..000000000000 --- a/translations/pt-BR/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Codespaces de pré-criação para o seu projeto -intro: Você pode configurar o seu projeto para pré-criar um codespace automaticamente cada vez que você fizer push de uma alteração no repositório. -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals -product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Codespaces pré-construídos ---- - -{% note %} - -**Observação:** Este recurso está atualmente em pré-visualização privada. - -{% endnote %} - -## Sobre a pré-criação de um codespace - -A pré-construção de seus codespace permite que você seja mais produtivo e acesse o seu codespace mais rapidamente. Isso ocorre porque qualquer código-fonte, extensões de editor, dependências de projetos, comandos, ou configurações já foram baixadas, instaladas e aplicadas antes de começar sua sessão de codificação. Depois de fazer push das alterações no repositório, o {% data variables.product.prodname_codespaces %} gerencia automaticamente a configuração das criações. - -A capacidade de pré-criar codespace está atualmente em visualização privada. Para obter acesso a este recurso, entre em contato com codespaces@github.com. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md index a118d0b903da..7f4a0cee34ba 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md @@ -23,6 +23,8 @@ Se você escolher criar um novo codespace, sempre que você trabalhar em um proj Se você optar por usar um codespace de longo prazo para o seu projeto, você deverá retirá-lo do branch padrão do repositório cada vez que começar a trabalhar no seu codespace para que seu ambiente tenha os commits mais recentes. Esse fluxo de trabalho é muito parecido como se você estivesse trabalhando com um projeto na sua máquina local. +{% data reusables.codespaces.prebuilds-crossreference %} + ## Salvar alterações em um codespace Ao conectar-se a um código através da web, a gravação automática é habilitada automaticamente para o editor da web e configurada para salvar as alterações após um atraso. Ao conectar-se a um codespace por meio de {% data variables.product.prodname_vscode %} em execução no seu computador, você deverá habilitar o salvamento automático. Para obter mais informações, consulte [Salvar/Salvar Automaticamente](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) na documentação de {% data variables.product.prodname_vscode %}. diff --git a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 14981a0d16f1..44df555fed24 100644 --- a/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/pt-BR/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -41,6 +41,8 @@ Se você quiser usar hooks do Git para o seu código, você deverá configurar h {% data reusables.codespaces.you-can-see-all-your-codespaces %} +{% data reusables.codespaces.prebuilds-crossreference %} + ## Acesso a {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} diff --git a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md index 5ff8ce484fb4..878760576621 100644 --- a/translations/pt-BR/content/codespaces/getting-started/deep-dive.md +++ b/translations/pt-BR/content/codespaces/getting-started/deep-dive.md @@ -24,7 +24,7 @@ Há uma série de pontos de entrada para criar um codespace. Seu codespace pode ser efêmero se você tiver de fazer algum teste ou você pode retornar ao mesmo codespace para fazer um trabalho de recurso de longo prazo. Para obter mais informações, consulte "[Criar um codespace](/codespaces/developing-in-codespaces/creating-a-codespace)". -Depois de selecionar a opção de criar um novo codespace, algumas etapas são executadas em segundo plano antes que o codespace esteja disponível para você. +Once you've selected the option to create a new codespace, and chosen a machine type for your codespace, some steps happen in the background before the codespace is available to you. ![Botão de abrir com codespaces](/assets/images/help/codespaces/new-codespace-button.png) diff --git a/translations/pt-BR/content/codespaces/index.md b/translations/pt-BR/content/codespaces/index.md index 25ca08481ab1..6175ad2ba465 100644 --- a/translations/pt-BR/content/codespaces/index.md +++ b/translations/pt-BR/content/codespaces/index.md @@ -46,9 +46,10 @@ versions: children: - /overview - /getting-started + - /developing-in-codespaces - /setting-up-your-project-for-codespaces - /customizing-your-codespace - - /developing-in-codespaces + - /prebuilding-your-codespaces - /managing-your-codespaces - /managing-codespaces-for-your-organization - /codespaces-reference diff --git a/translations/pt-BR/content/codespaces/overview.md b/translations/pt-BR/content/codespaces/overview.md index 461d369fc14f..fd8b734dc7af 100644 --- a/translations/pt-BR/content/codespaces/overview.md +++ b/translations/pt-BR/content/codespaces/overview.md @@ -13,7 +13,7 @@ redirect_from: versions: fpt: '*' ghec: '*' -type: quick_start +type: overview topics: - Codespaces --- diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md new file mode 100644 index 000000000000..94f3dd9d22de --- /dev/null +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md @@ -0,0 +1,44 @@ +--- +title: About Codespaces prebuilds +shortTitle: About prebuilds +intro: Codespaces prebuilds help to speed up the creation of new codespaces. +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## Visão Geral + +Prebuilding your codespaces allows you to be more productive and access your codespace faster, regardless of the size and complexity of your project. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace. + +Whenever you push changes to your repository, {% data variables.product.prodname_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. + +When prebuilds are available for a particular branch of a repository, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the machine type dialog box that's displayed when you create a codespace and multiple machine types are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +## About billing for {% data variables.product.prodname_codespaces %} prebuilds + +{% data reusables.codespaces.billing-for-prebuilds %} For details of {% data variables.product.prodname_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." + +Use of codespaces created using prebuilds is charged at the same rate as regular codespaces. + +## About pushing changes to prebuild-enabled branches + +Each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild template. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)". If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. + +This means that if there are very frequent pushes to your repository, prebuild creation will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container on the branch. + +For example, let's imagine 5 pushes are made, in quick succession, against a branch that has a prebuild configuration. In this situation: + +* A workflow run is started for the first push, to update the prebuild template. +* If the 4 remaining pushes do not affect the dev container configuration, the workflow runs for these are queued in a "pending" state. + + If any of the remaining 4 pushes change the dev container configuration, then the service will not skip that one and will immediately run the prebuild creation workflow, updating the prebuild accordingly if it succeeds. + +* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild template. diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md new file mode 100644 index 000000000000..b5052aadc0ea --- /dev/null +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -0,0 +1,93 @@ +--- +title: Configuring prebuilds +shortTitle: Configure prebuilds +intro: Você pode configurar o seu projeto para pré-criar um codespace automaticamente cada vez que você fizer push de uma alteração no repositório. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: People with admin access to a repository can configure prebuilds for the repository. +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +You can set up a prebuild configuration for a specific branch of your repository. + +Any branch created from a prebuild-enabled base branch will typically also get assigned a prebuild during codespace creation. This is true if the dev container on the branch is the same as on the base branch. This is because the majority of the prebuild configuration for branches with the same dev container configuration are identical, so developers can benefit from faster codespace creation times on those branches also. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)". + +Typically, when you configure prebuilds for a branch, prebuilds will be available for {% data variables.product.prodname_codespaces %} machine types for that branch. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. + +## Pré-requisitos + +Before you can configure prebuilds for your project the following must be true: +* {% data variables.product.prodname_github_codespaces %} must be enabled for your organization. For more information, see "[Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +* {% data variables.product.prodname_actions %} must be enabled for your repository. Each prebuild configuration needs to be able to trigger an associated Actions workflow. Para obter mais informações, consulte "[Gerenciar configurações de {% data variables.product.prodname_actions %} para um repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)". + +## Configuring a prebuild + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**. +1. Under "Prebuild configuration", click **Set up prebuild**. + + ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png) + +1. Choose the branch for which you want to set up a prebuild. + + ![The Branch drop-down menu](/assets/images/help/codespaces/prebuilds-choose-branch.png) + + {% note %} + + **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds. For example, if you enable prebuilds for the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds. For more information, see "[Why do I get prebuilds for branches that do not have prebuilds enabled?](/codespaces/troubleshooting/troubleshooting-prebuilds#2-why-do-i-get-prebuilds-for-branches-that-do-not-have-prebuilds-enabled)" + + {% endnote %} + +1. Choose the regions in which you want to set up a prebuild. Developers must be located in a region you select to be able to create codespaces from a prebuild. Alternatively, select **All regions**. + + ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png) + + {% note %} + + **Atenção**: + * The prebuild template for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + * Developers can set their default region for {% data variables.product.prodname_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces)." + + {% endnote %} + +1. Clique em **Criar**. + + The prebuild configuration is listed on the {% data variables.product.prodname_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuild templates, based on the branch you selected, in the regions you specified. + + {% note %} + + **Note**: By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access resources in its own repository. If your project uses resources from outside of the repository, you'll need to set the `CODESPACES_PREBUILD_TOKEN` secret to grant the required access. For more information, see "[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + + {% endnote %} + +## Configuring access to resources that are not in the repository + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. If your project needs to access external resources to build the development environment, you will need to set up a personal access token (PAT) with the appropriate access scopes. + +For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## Configurar variáveis de ambiente + +To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-an-organization)." + +Prebuilds do not use any user-level secrets while building your environment, because these are not added until after the codespace has been created. + +{% data variables.product.prodname_codespaces %} secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces. For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## Configuring time-consuming tasks to be included in the prebuild + +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." + +`onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. + +## Leia mais + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/index.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/index.md new file mode 100644 index 000000000000..5f3bdca59ad0 --- /dev/null +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/index.md @@ -0,0 +1,19 @@ +--- +title: Prebuilding your codespaces +intro: 'To speed up codespace creation, you can configure your project to prebuild codespaces for specific branches in specific regions.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +redirect_from: + - /codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project +children: + - /about-codespaces-prebuilds + - /configuring-prebuilds + - /managing-prebuilds + - /testing-dev-container-changes +--- + +{% data reusables.codespaces.prebuilds-beta-note %} \ No newline at end of file diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md new file mode 100644 index 000000000000..7ccf8abe5630 --- /dev/null +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -0,0 +1,109 @@ +--- +title: Managing prebuilds +shortTitle: Manage prebuilds +intro: 'You can review, modify, and delete the prebuild configurations for your repository.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## Checking, changing, and deleting your prebuild configurations + +The prebuilds that you configure are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_codespaces %} service. + +The workflow is triggered by these events: + +* Creating or updating the prebuild configuration +* Pushing a commit or a pull request to a branch that's configured to have prebuilds +* Manually triggering the workflow + +People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. + +### Viewing the progress of prebuilds +You can view the current status of the latest workflow run for each prebuild configuration you've set up on the {% data variables.product.prodname_codespaces %} page of your repository settings. For example, "Currently running" or "Last run 1 hour ago." + +To see the log output for the latest prebuild workflow run, click **See output**. + +![The 'See output' button](/assets/images/help/codespaces/prebuilds-see-output.png) + +This displays the output of the most recent run of the workflow in the **Actions** tab. + +![The prebuild workflow output](/assets/images/help/codespaces/prebuilds-log-output.png) + +Alternatively, to view all prebuild workflow runs associated with the specified branch, click the ellipsis button and choose **View runs** from the dropdown menu. + +![The 'View runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-view-runs.png) + +This displays the workflow run history for prebuilds for the associated branch. + +![The workflow run history](/assets/images/help/codespaces/prebuilds-workflow-runs.png) + +### Editing a prebuild configuration + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to edit. +1. In the dropdown menu, click **Edit**. + + ![The 'Edit' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-edit.png) + +1. Make the required changes to the prebuild configuration, then click **Update**. + +### Delete a prebuild configuration + +Deleting a prebuild configuration also deletes all previously created prebuild templates for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace. + +After you delete a prebuild configuration, workflow runs for that configuration that have been queued or started will still run. They will be listed in the workflow run history, along with previously completed workflow runs. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to delete. +1. In the dropdown menu, click **Delete**. + + ![The 'Delete' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-delete.png) + +1. Click **OK** to confirm the deletion. + +### Manually trigger prebuilds + +It may be useful to manually trigger a workflow run for a prebuild configuration. Generally this is only necessary if you are debugging a problem with the workflow for a prebuild configuration. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger. +1. In the dropdown menu, click **Manually trigger**. + + ![The 'Manually trigger' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) + +## Allowing a prebuild to access external resources + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. Your project may use additional resources to build the development environment, such as files in other repositories, packages, GHCR images, and APIs. To allow your prebuild setup to access these resources, you will need to create a new personal account and then use this account to create a personal access token (PAT) with the appropriate scopes. + +1. Create a new personal account on {% data variables.product.prodname_dotcom %}. + + {% warning %} + + **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + + {% endwarning %} +1. Give the new account read access to the required repositories. Para obter mais informações, consulte "[Gerenciar o acesso de um indivíduo ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)". +1. While signed into the new account, create a PAT with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. Para obter mais informações, consulte "[Criando um token de acesso pessoal](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." + + !['repo' and 'packages' scopes selected for a PAT](/assets/images/help/codespaces/prebuilds-select-scopes.png) + + If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)". +{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. Para obter mais informações, consulte "[Autorizar um token de acesso pessoal para uso com o logon único SAML](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)". + + ![The button to configure SSO for a PAT](/assets/images/help/codespaces/configure-SSO-for-PAT.png) + +{% endif %} +1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. +1. Sign back into the account that has admin access to the repository. +1. In the repository for which you want to create {% data variables.product.prodname_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)." + +The PAT will be used for all subsequent prebuild templates created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. + +## Leia mais + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md new file mode 100644 index 000000000000..b487a78a46db --- /dev/null +++ b/translations/pt-BR/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md @@ -0,0 +1,35 @@ +--- +title: Testing dev container configuration changes on a prebuild-enabled branch +shortTitle: Test dev container changes +allowTitleToDifferFromFilename: true +intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch. +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild template. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team. + +Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)". + +## Testing changes to the dev container configuration + +1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "[Creating a codespace ](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +1. In the codespace, check out a test branch. Para obter mais informações, consulte "[Usando controle de origem no seu codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)." +1. Make the required changes to the dev container configuration. +1. Apply the changes by rebuilding the container. Para obter mais informações, consulte "[Introdução a contêineres de desenvolvimento](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)". +1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild template for that branch. + + {% note %} + + **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild. + + {% endnote %} diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md index ed66d1e318cb..e0b340c98721 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md @@ -165,4 +165,10 @@ For more information about the available settings for `devcontainer.json`, see [ - Para diagnosticar o erro revisando os registros de criação, clique em **Visualizar registro de criação**. - Para corrigir os erros identificados nos registros, atualize seu arquivo devcontainer.json..
  • Para aplicar as alterações, reconstrua seu contêiner.
    • - + + +

    Leia mais

    + + diff --git a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md index 3194087ac93e..a0a9afaa8535 100644 --- a/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md +++ b/translations/pt-BR/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md @@ -1,6 +1,6 @@ --- title: Definindo uma especificação mínima para máquinas de codespaces -shortTitle: Definindo uma especificação mínima da máquina +shortTitle: Set a minimum machine spec intro: 'Você pode evitar que tipos de máquina com recursos insuficientes sejam usados no {% data variables.product.prodname_codespaces %} para o seu repositório.' permissions: People with write permissions to a repository can create or edit the codespace configuration. versions: diff --git a/translations/pt-BR/content/codespaces/troubleshooting/index.md b/translations/pt-BR/content/codespaces/troubleshooting/index.md index 69d0c5c22287..184a347d82b3 100644 --- a/translations/pt-BR/content/codespaces/troubleshooting/index.md +++ b/translations/pt-BR/content/codespaces/troubleshooting/index.md @@ -16,6 +16,7 @@ children: - /exporting-changes-to-a-branch - /troubleshooting-creation-and-deletion-of-codespaces - /troubleshooting-your-connection-to-codespaces + - /troubleshooting-prebuilds - /troubleshooting-dotfiles-for-codespaces - /troubleshooting-port-forwarding-for-codespaces - /troubleshooting-codespaces-clients diff --git a/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md new file mode 100644 index 000000000000..5a010260864d --- /dev/null +++ b/translations/pt-BR/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -0,0 +1,59 @@ +--- +title: Troubleshooting prebuilds +shortTitle: Codespaces prebuilds +intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds. +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +For more information about {% data variables.product.prodname_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)." + +## Checking whether a codespace was created from a prebuild? + +If multiple machine types are available when you create a codespace then a dialog box is displayed giving you a choice of machine types. This will display the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label beside machine types for which prebuilds are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." + +After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: + +```shell{:copy} +gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild +``` + +This returns `true` if the codespace was created using a prebuild. + +Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild: + +```shell{:copy} +cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME' +``` + +## The "Prebuild Ready" label is sometimes missing + +You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. + +Each time you push to a prebuild-enabled branch, the prebuild template is updated. If the push involves a change to the dev container then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the machine types dialog box. During this time you can still create codespaces without a prebuild template. + +If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container is changed on your branch, so that it's not the same as the dev container on the base branch, prebuilds will no longer be available on your branch. + +Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch: + +* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this. +* Confirm that the prebuild configuration includes your region. +* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will have to wait until the prebuild workflow run for this push completes before prebuilds are available again. +* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container, then there will be no available prebuilds for the associated branch. + +## Leia mais + +- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)" +- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)" diff --git a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md index 6cb1ead9816f..187813b1f735 100644 --- a/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md +++ b/translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md @@ -45,7 +45,11 @@ Para obter informações sobre como renovar seu {% data variables.product.prodna ## Vencimento e renovações -Assim que seu acesso ao {% data variables.product.prodname_student_pack %} expirar, você poderá se recandidatar se ainda estiver qualificado, embora algumas das nossas ofertas de parceiro não possam ser renovadas. A maioria das ofertas com tempo limitado de nossos parceiros entra em vigor assim que você as configura. Para obter mais informações, consulte a página do [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). +Assim que seu acesso ao {% data variables.product.prodname_student_pack %} expirar, você poderá se recandidatar se ainda estiver qualificado, embora algumas das nossas ofertas de parceiro não possam ser renovadas. A maioria das ofertas com tempo limitado de nossos parceiros entra em vigor assim que você as configura. To reapply, simply return to https://education.github.com, click your profile picture, then click **Reverify your academic affiliation**. + +![Menu option to reverify your academic affiliation](/assets/images/help/education/reverify-academic-affiliation.png) + +Para obter mais informações, consulte a página do [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). Para ver quando seu acesso grátis ao {% data variables.product.prodname_student_pack %} expira, visite as [configurações de cobrança](https://github.com/settings/billing) da sua conta. diff --git a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md index c29f8f813aa4..c9cbf6a32540 100644 --- a/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/pt-BR/content/get-started/learning-about-github/about-github-advanced-security.md @@ -25,7 +25,7 @@ shortTitle: Segurança Avançada GitHub Uma licença de {% data variables.product.prodname_GH_advanced_security %} fornece as funcionalidades adicionais a seguir: -- **{% data variables.product.prodname_code_scanning_capc %}** - Pesquisa de possíveis vulnerabilidades de segurança e erros de codificação no seu código. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." +- **{% data variables.product.prodname_code_scanning_capc %}** - Pesquisa de possíveis vulnerabilidades de segurança e erros de codificação no seu código. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning) - **{% data variables.product.prodname_secret_scanning_caps %}** - Detectar segredos, por exemplo, chaves e tokens, que foram verificados no repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning) @@ -95,12 +95,12 @@ Se você tem uma conta corporativa, a utilização da licença para toda a empre {% endif %} {% ifversion fpt or ghec %} -## About starter workflows for {% data variables.product.prodname_advanced_security %} +## Sobre os fluxos de trabalho iniciais para {% data variables.product.prodname_advanced_security %} {% data reusables.advanced-security.starter-workflows-beta %} {% data reusables.advanced-security.starter-workflow-overview %} -For more information on starter workflows, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)" and "[Using starter workflows](/actions/using-workflows/using-starter-workflows)." +Para mais informações sobre fluxos de trabalho iniciais, consulte "[Configurando {% data variables.product.prodname_code_scanning %} usando fluxos de trabalho iniciais](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)" e "[Usando fluxos de trabalho iniciais](/actions/using-workflows/using-starter-workflows)". {% endif %} diff --git a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md index ea071465bb33..953a39cf9e3d 100644 --- a/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md +++ b/translations/pt-BR/content/github/site-policy/github-data-protection-agreement.md @@ -720,7 +720,7 @@ Em países onde a aprovação regulatória é necessária para o uso das Cláusu A partir de 25 de maio de 2018 e após esse período, qualquer referência aos diversos artigos da Diretiva 95/46/CE nas Cláusulas Contratuais Padrão abaixo será tratada como referência aos artigos relevantes e apropriados no RGPD. -For the purposes of Article 26(2) of Directive 95/46/EC for the transfer of personal data to processors established in third countries which do not ensure an adequate level of data protection, Customer (as data exporter) and GitHub, Inc. (as data importer, whose signature appears below), each a “party,” together “the parties,” have agreed on the following Contractual Clauses (the “Clauses” or “Standard Contractual Clauses”) in order to adduce adequate safeguards with respect to the protection of privacy and fundamental rights and freedoms of individuals for the transfer by the data exporter to the data importer of the personal data specified in Appendix 1. +Para as finalidades do artigo 26(2) da Diretiva 95/46/CE referente à transferência de dados pessoais para transformadores estabelecidos em países terceiros que não garantam um nível adequado de proteção de dados, o Cliente (como exportador de dados) e o GitHub, Inc. (como importador de dados, cuja assinatura aparece abaixo), cada um "parte", coletivamente "as partes, acordaram as Cláusulas Contratuais a seguir (as “Cláusulas” ou “Cláusulas Contratuais Padrão”) a fim de adjudicar salvaguardas adequadas referentes à proteção da privacidade e dos direitos e liberdades fundamentais dos indivíduos para a transferência pelo exportador de dados para o importador de dados dos dados pessoais especificados no Apêndice 1. ### Cláusula 1: Definições @@ -895,7 +895,7 @@ Attn: Privacy
    88 Colin P. Kelly Jr. Street
    San Francisco, California 94107 USA
    -
  • Technical and Organization Measures. The data importer has implemented and will maintain appropriate technical and organizational measures, internal controls, and information security routines intended to protect personal data, as defined in the Security Practices and Policies section of the DPA, against accidental loss, destruction, or alteration; unauthorized disclosure or access; or unlawful destruction as follows: The technical and organizational measures, internal controls, and information security routines set forth in the Security Practices and Policies section of the DPA are hereby incorporated into this Appendix 2 by this reference and are binding on the data importer as if they were set forth in this Appendix 2 in their entirety.
    • +
  • Medidas técnicas e organizacionais. O importador de dados implementou e manterá medidas técnicas e organizacionais adequadas, controles internos, rotinas de segurança de informações destinadas a proteger os dados pessoais, conforme definido na seção de Práticas de Segurança e Políticas do DPA, contra perda acidental, destruição ou alteração; divulgação ou acesso não autorizado; ou destruição ilegal da seguinte forma: medidas técnicas e organizacionais, controles internos, e as rotinas de segurança da informação estabelecidas na seção Práticas de Segurança e Políticas do DPA estão incorporadas a este Apêndice 2 por referência e estão vinculadas ao importador de dados como se estivessem definidas neste Apêndice 2 em seu inteiro teor.
    • ### Apêndice 3 das Cláusulas Contratuais Padrão (Reino Unido) @@ -914,7 +914,7 @@ Este adendo é um complemento e parte constituinte, mas não diverge ou modifica
  • fará o possível juridicamente para contestar a ordem de divulgação com base em eventuais deficiências jurídicas nos termos das leis da parte requerente ou em quaisquer conflitos relevantes com a legislação da União Europeia ou com a legislação aplicável do Estado-membro.

    • Para a finalidade desta seção, os esforços jurídicos não incluem acções que possam resultar em sanções civis ou penais, como o desprezo pelos tribunais ao abrigo das leis da jurisdição relevante. -
  • Indenização dos Titulares de Dados. Subject to Sections 3 and 4, GitHub shall indemnify a data subject for any material or non-material damage to the data subject caused by GitHub’s disclosure of personal data of the data subject that has been transferred under the Standard Contractual Clauses (UK) in response to an order from a non-EU/EEA government body or law enforcement agency (a “Relevant Disclosure”). Não obstante o exposto, o GitHub não terá nenhuma obrigação de indenizar o titular de dados nos termos desta Seção 2, na medida em que o titular de dados já tenha sido compensado pelos mesmos danos, seja pelo GitHub ou de outro modo.
    • +
  • Indenização dos Titulares de Dados. Sujeito às seções 3 e 4, o GitHub indenizará o titular de dados por qualquer dano material ou não material perante o titular de dados causados pela divulgação de dados pessoais do GitHub sobre o titular de dados que foram transferidos nos termos as Cláusulas Contratuais Padrão (Reino Unido) em resposta a uma ordem de um órgão governamental ou autoridade policial que não ou órgão governamental que não seja da UE/EEE (uma “Divulgação relevante”). Não obstante o exposto, o GitHub não terá nenhuma obrigação de indenizar o titular de dados nos termos desta Seção 2, na medida em que o titular de dados já tenha sido compensado pelos mesmos danos, seja pelo GitHub ou de outro modo.
  • Condições de Indenização. A indenização nos termos da Seção 2 fica condicionada ao estabelecimento do titular dos dados, para satisfação razoável do GitHub, que:
    1. o GitHub participou em uma Divulgação Relevante;
      2. diff --git a/translations/pt-BR/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/pt-BR/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md index 04d5e8da0cf7..2e888d1d5a33 100644 --- a/translations/pt-BR/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md +++ b/translations/pt-BR/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md @@ -18,7 +18,7 @@ De acordo com a Organização Internacional do Trabalho (OIT), [40 milhões de p O GitHub lamenta a presença e persistência da escravatura moderna e do trabalho infantil, e leva a sério a sua responsabilidade de garantir que nem a escravatura moderna, nem o trabalho infantil se realizem na sua cadeia de fornecedores ou em qualquer parte do seu negócio. ("Escravidão moderna", nesta declaração, refere-se à escravatura, ao trabalho forçado ou obrigatório, ao tráfico, à servidão e aos trabalhadores que são presos, coagidos ou obrigados. "Trabalho infantil" refere-se ao trabalho realizado por alguém menor de 16 anos de idade, ou menor de 14 anos, para trabalho leve, desde que não se limite a períodos que interfiram na escolaridade da criança nem em condições que interfiram na saúde ou o bem-estar da criança.) -De acordo com a [Lei da Escravidão Moderna do Reino Unido](http://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), e em consonância com o [Protocolo da OIT de 2014 à Convenção do Trabalho Forçado](http://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029), a [Declaração da OIT sobre os Princípios Fundamentais e os Direitos do Trabalho](http://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), e os [Objetivos das Nações Unidas para o Desenvolvimento Sustentável 8.7](https://sustainabledevelopment.un.org/sdg8), esta declaração contra a Escravidão Moderna e o Trabalho Infantil de 2018 ("a Declaração") descreve as etapas tomadas pelo GitHub para evitar que a escravatura moderna e o trabalho infantil ocorram em seus negócios ou cadeia de fornecedores. +In accordance with the [UK Modern Slavery Act](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), and in alignment with the [ILO 2014 Protocol to its Forced Labour Convention](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029), [ILO Declaration on Fundamental Principles and Rights at Work](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), and [United Nations Sustainable Development Goals target 8.7](https://www.unodc.org/roseap/en/sustainable-development-goals.html#:~:text=Target%208.7%20%2D%20Take%20immediate%20and,labour%20in%20all%20its%20forms), this 2018 Statement Against Modern Slavery and Child Labor ("the Statement") describes the steps GitHub has taken to prevent modern slavery and child labor from occurring in its business or supply chain. ## Estrutura, negócios e cadeias de fornecedores do GitHub diff --git a/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md index de055cc1d3b3..8329e3b77d88 100644 --- a/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md +++ b/translations/pt-BR/content/support/contacting-github-support/providing-data-to-github-support.md @@ -177,4 +177,4 @@ Você pode fazer upload diretamente de um pacote de suporte para o nosso servido ## Leia mais - "[Sobre o suporte do GitHub](/support/learning-about-github-support/about-github-support)" -- "[Generating a Health Check for your enterprise](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)" +- "[Gerando uma verificação de integridade da sua empresa](/enterprise-server@latest/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise)" diff --git a/translations/pt-BR/data/learning-tracks/actions.yml b/translations/pt-BR/data/learning-tracks/actions.yml index badfea227267..eac92d8f5f33 100644 --- a/translations/pt-BR/data/learning-tracks/actions.yml +++ b/translations/pt-BR/data/learning-tracks/actions.yml @@ -38,8 +38,8 @@ deploy_to_the_cloud: - /actions/deployment/deploying-to-azure-app-service - /actions/deployment/deploying-to-google-kubernetes-engine adopting_github_actions_for_your_enterprise: - title: 'Adopt GitHub Actions for your enterprise' - description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + title: 'Adote o GitHub Actions para a sua empresa' + description: 'Aprenda a planejar e implementar uma versão de {% data variables.product.prodname_actions %} na sua empresa.' guides: - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises - /actions/learn-github-actions/understanding-github-actions diff --git a/translations/pt-BR/data/learning-tracks/admin.yml b/translations/pt-BR/data/learning-tracks/admin.yml index 2f5bcc4d81a4..7158366a3939 100644 --- a/translations/pt-BR/data/learning-tracks/admin.yml +++ b/translations/pt-BR/data/learning-tracks/admin.yml @@ -37,8 +37,8 @@ upgrade_your_instance: - /admin/configuration/enabling-and-scheduling-maintenance-mode - /admin/enterprise-management/upgrading-github-enterprise-server adopting_github_actions_for_your_enterprise: - title: 'Adopt GitHub Actions for your enterprise' - description: 'Learn how to plan and implement a roll out of {% data variables.product.prodname_actions %} in your enterprise.' + title: 'Adote o GitHub Actions para a sua empresa' + description: 'Aprenda a planejar e implementar uma versão de {% data variables.product.prodname_actions %} na sua empresa.' guides: - /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises - /actions/learn-github-actions/understanding-github-actions diff --git a/translations/pt-BR/data/learning-tracks/code-security.yml b/translations/pt-BR/data/learning-tracks/code-security.yml index 4802759e758f..c1fa2ba98d15 100644 --- a/translations/pt-BR/data/learning-tracks/code-security.yml +++ b/translations/pt-BR/data/learning-tracks/code-security.yml @@ -2,7 +2,7 @@ #Feature available only on dotcom security_advisories: title: 'Corrigir e revelar uma vulnerabilidade de segurança' - description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' + description: 'Usando consultorias de segurança do repositório para corrigir de forma privada uma vulnerabilidade relatada e obter um CVE.' featured_track: '{% ifversion fpt %}true{% else %}false{% endif %}' guides: - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities diff --git a/translations/pt-BR/data/product-examples/codespaces/code-examples.yml b/translations/pt-BR/data/product-examples/codespaces/code-examples.yml index 00958245abdd..83e9faf890fe 100644 --- a/translations/pt-BR/data/product-examples/codespaces/code-examples.yml +++ b/translations/pt-BR/data/product-examples/codespaces/code-examples.yml @@ -1,43 +1,43 @@ --- - - title: Node.js sample project - description: Try a Node.js project with a custom dev container + title: Projeto de amostra no Node.js + description: Tente um projeto do Node.js com um contêiner de desenvolvimento personalizado languages: Javascript href: microsoft/vscode-remote-try-node tags: - - development containers + - contêineres de desenvolvimento - - title: Python sample project - description: Try a Python project with a custom dev container + title: Projeto de amostra do Python + description: Experimente um projeto do Python com um contêiner de desenvolvimento personalizado languages: Python href: microsoft/vscode-remote-try-python tags: - - development containers + - contêineres de desenvolvimento - - title: Java sample project - description: Try a Java project with a custom dev container + title: Projeto de amostra do Java + description: Experimente um projeto do Java com um contêiner de desenvolvimento personalizado languages: Java href: microsoft/vscode-remote-try-java tags: - - development containers + - contêineres de desenvolvimento - - title: Go sample project - description: Try a Go project with a custom dev container + title: Projeto de amostra no Go + description: Experimente um projeto do Go com um contêiner de desenvolvimento personalizado languages: Go href: microsoft/vscode-remote-try-go tags: - - development containers + - contêineres de desenvolvimento - - title: Rust sample project - description: Try a Rust project with a custom dev container + title: Projeto de amostra do Rust + description: Experimente um projeto do Rust com um contêiner de desenvolvimento personalizado languages: Rust href: microsoft/vscode-remote-try-rust tags: - - development containers + - contêineres de desenvolvimento - - title: PHP sample project - description: Try a PHP project with a custom dev container + title: Projeto de amostra no PHP + description: Experimente um projeto do PHP com um contêiner de desenvolvimento personalizado languages: PHP href: microsoft/vscode-remote-try-php tags: - - development containers + - contêineres de desenvolvimento diff --git a/translations/pt-BR/data/product-examples/sponsors/user-examples.yml b/translations/pt-BR/data/product-examples/sponsors/user-examples.yml index 92800edaf330..4ac77eb36ba3 100644 --- a/translations/pt-BR/data/product-examples/sponsors/user-examples.yml +++ b/translations/pt-BR/data/product-examples/sponsors/user-examples.yml @@ -2,19 +2,19 @@ - #Images and descriptions are pulled directly from the repo user: chaynHQ - description: Chayn helps women experiencing abuse find the right information and support they need to take control of their lives. + description: O Chayn ajuda as mulheres que são vítimas de abusos a encontrarem as informações corretas e o apoio de que precisam para assumirem o controle das suas vidas. - user: foosel - description: '👋 I''m Gina, and I''m mostly known for being the creator and main developer of OctoPrint 🐙.' + description: '👋 Sou Gina e, de modo geral, sou conhecida por ser a criadora e desenvolvedora principal do OctoPrint 🐙.' - user: dayhaysoos - description: What's up? I'm Nick. I'm an engineer who has a new-found passion for removing friction from the e-commerce developer experience. + description: Tudo bem? Eu sou o Nick. Eu sou um engenheiro que acaba de encontrar a sua paixão por remover fricção da experiência de desenvolvimento de comércio eletrônico. - user: yyx990803 - description: I'm working fulltime on Vue.js, a frontend JavaScript framework for building web applications, and Vite, a modern web build tool. + description: Estou trabalhando no Vue.js em tempo integral, uma estrutura frontend do JavaScript para criar aplicativos da web e Vite, uma moderna ferramenta de criação da web. - user: calebporzio - description: '🚶‍♂️I left my day job in Jan 2019 to pursue open-source. Since then, I''ve built Laravel Livewire, AlpineJS, and a bunch of other stuff.' + description: '🚶‍♂️ Eu saí do meu trabalho diurno em janeiro de 2019 para dedicar-me ao código aberto. Desde então, eu criei Laravel Livewire, AlpineJS e uma série de outras coisas.' - user: kjaymiller - description: Hi Y'all I'm Jay! 👋 I'm a Marine Corps Veteran turned developer that's been actively coding since 2014. I'm also involved in the productivity space where I can be found helping people with automations for some of their favorite apps and tools. + description: '¡Olá a todos, eu sou! 👋 Sou um veterano do corpo de fuzileiros navais e venho trabalhando ativamente com codificação desde 2014. Além disso, eu me envolvo com a área de produtividade, em que eu posso ajudar as pessoas com automações para alguns dos seus aplicativos e ferramentas favoritos.' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml index 44c7395394b9..6f3cea7c0271 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml @@ -1,8 +1,8 @@ date: '2020-08-11' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**High:** An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GitHub Enterprise Server instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' + - '{% octicon "alert" aria-label="The alert icon" %}**CRÍTICO:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**Alto:** Um invasor pode injetar um argumento malicioso em um subcomando do Git quando executado no GitHub Enterprise Server. Isso pode permitir que o invasor sobrescreva arquivos arbitrários com conteúdo controlado parcialmente pelo usuário e potencialmente execute comandos arbitrários na instância do GitHub Enterprise Server. Para explorar essa vulnerabilidade, um invasor precisaria de permissão para acessar repositórios dentro da instância do GitHub Enterprise Server. No entanto, devido a outras proteções em vigor, não conseguimos identificar uma forma de explorar ativamente esta vulnerabilidade. Esta vulnerabilidade foi relatada por meio do programa GitHub Security Bug Bounty {% comment %} https://github.com/github/github/pull/151097 {% endcomment %}' - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-21/4.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-21/4.yml index 61512a816192..ed15193b5c58 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/2-21/4.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-21/4.yml @@ -1,8 +1,8 @@ date: '2020-08-11' sections: security_fixes: - - '{% octicon "alert" aria-label="The alert icon" %} **Critical:** A remote code execution vulnerability was identified in GitHub Pages that could allow an attacker to execute commands as part building a GitHub Pages site. This issue was due to an outdated and vulnerable dependency used in the Pages build process. To exploit this vulnerability, an attacker would need permission to create and build a GitHub Pages site on the GitHub Enterprise Server instance. This vulnerability affected all versions of GitHub Enterprise Server. To mitigate this vulnerability, Kramdown has been updated to address CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' - - '**High:** High: An attacker could inject a malicious argument into a Git sub-command when executed on GitHub Enterprise Server. This could allow an attacker to overwrite arbitrary files with partially user-controlled content and potentially execute arbitrary commands on the GitHub Enterprise Server instance. To exploit this vulnerability, an attacker would need permission to access repositories within the GHES instance. However, due to other protections in place, we could not identify a way to actively exploit this vulnerability. This vulnerability was reported through the GitHub Security Bug Bounty program. {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' + - '{% octicon "alert" aria-label="The alert icon" %}**Crítico:** Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Pages e permite que um invasor execute comandos como parte de criação de um site do GitHub Pages. Esse problema deve-se a uma dependência desatualizada e vulnerável usada no processo de criação de páginas. Para explorar essa vulnerabilidade, um invasor precisará de permissão para criar e construir um site do GitHub Pages na instância do GitHub Enterprise Server. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server. Para mitigar essa vulnerabilidade, a Kramdown foi atualizada para abordar o CVE-2020-14001. {% comment %} https://github.com/github/pages/pull/2835, https://github.com/github/pages/pull/2827 {% endcomment %}' + - '**Alto:** Alto: Um invasor pode injetar um argumento malicioso em um subcomando do Git quando executado no GitHub Enterprise Server. Isso pode permitir que o invasor sobrescreva arquivos arbitrários com conteúdo controlado parcialmente pelo usuário e potencialmente execute comandos arbitrários na instância do GHES. Para explorar essa vulnerabilidade, um invasor precisaria de permissão para acessar repositórios dentro da instância do GitHub Enterprise Server. No entanto, devido a outras proteções em vigor, não conseguimos identificar uma forma de explorar ativamente esta vulnerabilidade. Esta vulnerabilidade foi relatada por meio do programa GitHub Security Bug Bounty {% comment %} https://github.com/github/github/pull/150936, https://github.com/github/github/pull/150634 {% endcomment %}' - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/21679, https://github.com/github/enterprise2/pull/21542, https://github.com/github/enterprise2/pull/21812, https://github.com/github/enterprise2/pull/21700 {% endcomment %}' bugs: - 'Um erro de configuração do Cônsul impediu que algumas tarefas de segundo plano fossem processadas em instâncias autônomas. {% comment %} https://github.com/github/enterprise2/pull/21463 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/2-22/17.yml b/translations/pt-BR/data/release-notes/enterprise-server/2-22/17.yml index a0b60a3dbe0d..a68724ee12c3 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/2-22/17.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/2-22/17.yml @@ -7,11 +7,11 @@ sections: bugs: - '`ghe-cluster-config-node-init` falharia durante a configuração do cluster se o proxy HTTP estiver habilitado.' - O Collectd não resolveria o nome de host de destino após a inicialização. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. + - O trabalho que os repositórios obsoletos excluídos pode não conseguir progredir se alguns desses repositórios estiverem protegidos da exclusão por retenção legal. + - Os pushes do Git podem gerar um erro de 500 servidor interno durante o processo de reconciliação do usuário em instâncias usando o modo de autenticação do LDAP. - Um número significativo de erros 503 foram registrados toda vez que um usuário visitou a página `/settings` de um repositório se o gráfico de dependência não estava habilitado. changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - Aprimorou-se a eficiência da aplicação da configuração ao ignorar as regras de firewall para permitir IP, que não haviam sido alteradas, o que economizou tempo significativo em grandes clusters. known_issues: - Em uma nova configuração do GitHub Enterprise Server sem nenhum usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/11.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/11.yml index f19c39fae0e9..62043328d1f4 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/11.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/11.yml @@ -8,15 +8,15 @@ sections: - A variável de data de vencimento do SAML não era configurável. - Os serviços do aplicativo falhariam as suas verificações de saúde durante a configuração fossem aplicadas antes de poderem entrar em um estado saudável. - '`ghe-cluster-config-node-init` falharia durante a configuração do cluster se o proxy HTTP estiver habilitado.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. + - Os hooks de pre-receive podem encontrar um erro `Failed to resolve full path of the current executable` due to `/proc` não sendo montado no container. - O Collectd não resolveria o nome de host de destino após a inicialização. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. + - O trabalho que os repositórios obsoletos excluídos pode não conseguir progredir se alguns desses repositórios estiverem protegidos da exclusão por retenção legal. - Executar `git nw-gc --pristine` geraria um erro. - Os Trabalhos de fundo estavam sendo enfileirados na fila `spam` que não estavam sendo processados. - O método de merge preferido seria redefinido ao tentar novamente após um merge de PR falhada. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. + - Os pushes do Git podem gerar um erro de 500 servidor interno durante o processo de reconciliação do usuário em instâncias usando o modo de autenticação do LDAP. changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - Aprimorou-se a eficiência da aplicação da configuração ao ignorar as regras de firewall para permitir IP, que não haviam sido alteradas, o que economizou tempo significativo em grandes clusters. known_issues: - Em uma nova configuração do GitHub Enterprise Server sem nenhum usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml index f9463e073f0f..22702ea2095b 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/16.yml @@ -8,7 +8,7 @@ sections: - 'As contagens dos trabalhadores de Resque foram exibidas incorretamente no modo de manutenção. {% comment %} https://github.com/github/enterprise2/pull/26898, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - 'A memória memorizada memcached poderia ser zero no modo de clustering. {% comment %} https://github.com/github/enterprise2/pull/26927, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - 'Corrige versões {% data variables.product.prodname_pages %} para que elas levem em conta a configuração NO_PROXY do aparelho. Isto é relevante para os aparelhos configurados apenas com um proxy HTTP. (atualização 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' + - 'A configuração do GitHub Connect da instância de origem foi sempre restaurada para novas instâncias mesmo quando `--config` option for `ghe-restore` não foi usada. Isto geraria um conflito com a conexão e a sincronização de licença do GitHub Connect se as instâncias de origem e destino estivessem on-line ao mesmo tempo. A correção também exige atualização do backup-utils para a versão 3.2.0 ou superior. [atualizado: 2021-11-18]' known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/18.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/18.yml index 6a0b5c63b1c0..88467757cd69 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/18.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/18.yml @@ -2,10 +2,10 @@ date: '2021-10-28' sections: security_fixes: - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' + - 'Várias chaves públicas SSH fracas conhecidas foram adicionadas à lista de recusas e já não podem ser registradas. Além disso, as versões do GitKraken conhecidas por gerar chaves SSH fracas (7.6.x, 7.7.x e 8.0.0) foram impedidas de registrar novas chaves públicas.' - 'Os pacotes foram atualizados para as últimas versões de segurança.' bugs: - - 'Several parts of the application were unusable for users who are owners of many organizations.' + - 'Várias partes do aplicativo eram inutilizáveis para usuários que são proprietários de várias organizações.' known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. - As regras de firewall personalizadas são removidas durante o processo de atualização. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/19.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/19.yml index ccfa29074ea6..d1006995e537 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/19.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/19.yml @@ -5,9 +5,9 @@ sections: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. + - Algumas operações Git falharam depois de atualizar um cluster 3.x de {% data variables.product.prodname_ghe_server %} devido à configuração do HAProxy. + - É possível que as contagens de trabalhadores do Unicorn possam ter sido definidas de forma incorreta no modo de agrupamento. + - É possível que as contagens dos trabalhadores do Resqued possam ter sido definidas incorretamente no modo cluster. - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. - The enterprise audit log page would not display audit events for {% data variables.product.prodname_secret_scanning %}. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml index fd360134489b..ce616fd0477e 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-0/20.yml @@ -4,13 +4,13 @@ sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - Os hooks de pre-receive falhariam em razão de `PATH` indefinido. + - 'A execução de `ghe-repl-setup` retornaria um erro: `cannot create directory /data/user/elasticsearch: File exists` se a instância tiver sido configurada anteriormente como uma réplica.' + - Em ambientes de grandes clusters, o back-end de autenticação pode estar indisponível em um subconjunto de nós do frontend. + - Alguns serviços críticos podem não estar disponíveis em nós de backend do Cluster do GHES. changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - A camada externa adicional de compressão `gzip` ao criar um pacote de suporte de cluster com `ghe-cluster-suport-bundle` agora está desativada por padrão. Essa compressão externa pode ser aplicada opcionalmente com a opção de linha de comando `ghe-cluster-suport-bundle -c`. + - Nós adicionamos texto adicional ao console de administração para lembrar os usuários da coleta de dados dos aplicativos móveis para fins de melhoria de experiência. - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml index 6b929ef70fc8..e239d7dff7c2 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml @@ -67,9 +67,9 @@ sections: heading: Filtro do GitHub Mobile notes: - | - [{% data variables.product.prodname_mobile %}](https://github.com/mobile) filtering allows you to search for and find issues, pull requests, and discussions from your device. New metadata for issues and pull request list items allow you to filter by assignees, checks status, review states, and comment counts. + [{% data variables.product.prodname_mobile %}](https://github.com/mobile) o filtro permite que você procure e encontre problemas, pull requests e discussões do seu dispositivo. Novos metadados para problemas e itens da lista de pull request permitem que você filtre por responsáveis, verifique status, status de revisão e contagens de comentários. - {% data variables.product.prodname_mobile %} beta is available for {% data variables.product.prodname_ghe_server %}. Sign in with our [Android](https://play.google.com/store/apps/details?id=com.github.android) and [iOS](https://apps.apple.com/app/github/id1477376905) apps to triage notifications and manage issues and pull requests on the go. Administrators can disable mobile support for their Enterprise using the management console or by running `ghe-config app.mobile.enabled false`. For more information, see "[GitHub Mobile](/get-started/using-github/github-mobile)." + A beta de {% data variables.product.prodname_mobile %} está disponível para {% data variables.product.prodname_ghe_server %}. Efetue o login com os nossos aplicativos de [Android](https://play.google.com/store/apps/details?id=com.github.android) e [iOS](https://apps.apple.com/app/github/id1477376905) para triar as notificações e gerenciar problemas e pull requests em qualquer lugar. Os administradores podem desabilitar o suporte móvel para sua empresa usando o console de gerenciamento ou executando o `ghe-config app.mobile.enabled false`. Para mais informações, consulte "[GitHub Mobile](/get-started/using-github/github-mobile)." changes: - heading: Alterações na administração diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/10.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/10.yml index f17695ae771d..58456573cf5f 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/10.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/10.yml @@ -3,11 +3,11 @@ date: '2021-10-28' sections: security_fixes: - 'It was possible for cleartext passwords to end up in certain log files.' - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' + - 'Várias chaves públicas SSH fracas conhecidas foram adicionadas à lista de recusas e já não podem ser registradas. Além disso, as versões do GitKraken conhecidas por gerar chaves SSH fracas (7.6.x, 7.7.x e 8.0.0) foram impedidas de registrar novas chaves públicas.' - 'Os pacotes foram atualizados para as últimas versões de segurança.' bugs: - - 'Restore might fail for enterprise server in clustering mode if orchestrator isnt healthily.' - - 'Several parts of the application were unusable for users who are owners of many organizations.' + - 'Restaurar pode gerar uma falha para o servidor corporativo no modo de agrupamento se orquestrador não tiveru ma boa integridade.' + - 'Várias partes do aplicativo eram inutilizáveis para usuários que são proprietários de várias organizações.' - 'Fixed a link to https://docs.github.com.' changes: - 'Browsing and job performance optimizations for repositories with many refs.' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/11.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/11.yml index 54e469bd92c9..047cffa2da82 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/11.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/11.yml @@ -5,9 +5,9 @@ sections: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. + - Algumas operações Git falharam depois de atualizar um cluster 3.x de {% data variables.product.prodname_ghe_server %} devido à configuração do HAProxy. + - É possível que as contagens de trabalhadores do Unicorn possam ter sido definidas de forma incorreta no modo de agrupamento. + - É possível que as contagens dos trabalhadores do Resqued possam ter sido definidas incorretamente no modo cluster. - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml index 9f04d332b246..eaf81c16442c 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/12.yml @@ -4,15 +4,15 @@ sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - Executar `ghe-repl-start` ou `ghe-repl-status` às vezes poderia retornar erros conectados ao banco de dados quando o GitHub Actions foi habilitado. + - Os hooks de pre-receive falhariam em razão de `PATH` indefinido. + - 'A execução de `ghe-repl-setup` retornaria um erro: `cannot create directory /data/user/elasticsearch: File exists` se a instância tiver sido configurada anteriormente como uma réplica.' + - 'Após configurar uma réplica de alta disponibilidade, o ''ghe-repl-status'' incluiu um erro na saída: `unexpected unclosed action in command`.' + - Em ambientes de grandes clusters, o back-end de autenticação pode estar indisponível em um subconjunto de nós do frontend. + - Alguns serviços críticos podem não estar disponíveis em nós de backend do Cluster do GHES. changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - A camada externa adicional de compressão `gzip` ao criar um pacote de suporte de cluster com `ghe-cluster-suport-bundle` agora está desativada por padrão. Essa compressão externa pode ser aplicada opcionalmente com a opção de linha de comando `ghe-cluster-suport-bundle -c`. + - Nós adicionamos texto adicional ao console de administração para lembrar os usuários da coleta de dados dos aplicativos móveis para fins de melhoria de experiência. - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - 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. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/13.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/13.yml index 7cd0b1a0c163..0f89ee9a40b3 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/13.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/13.yml @@ -4,7 +4,7 @@ sections: security_fixes: - Support bundles could include sensitive files if they met a specific set of conditions. - A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed more permissions to be granted during a GitHub App's user-authorization web flow than was displayed to the user during approval. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.2.5, 3.1.13, 3.0.21. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41598](https://www.cve.org/CVERecord?id=CVE-2021-41598). - - A remote code execution vulnerability was identified in GitHub Enterprise Server that could be exploited when building a GitHub Pages site. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.3 and was fixed in versions 3.0.21, 3.1.13, 3.2.5. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned [CVE-2021-41599](https://www.cve.org/CVERecord?id=CVE-2021-41599). Updated February 17, 2022 + - Uma vulnerabilidade de execução de código remoto foi identificada no GitHub Enterprise Server que pode ser explorada ao criar um site do GitHub Pages. Esta vulnerabilidade afetou todas as versões do GitHub Enterprise Server antes de 3.3 e foi corrigida nas versões 3.0.21, 3.1.13 e 3.2.5. Esta vulnerabilidade foi informada no programa de Compensação de Erro do GitHub e recebeu um [CVE-2021-41599](https://www. ve.org/CVERecord?id=CVE-2021-41599). Atualizado em 17 de fevereiro 2022 bugs: - Running `ghe-config-apply` could sometimes fail because of permission issues in `/data/user/tmp/pages`. - A misconfiguration in the Management Console caused scheduling errors. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/17.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/17.yml index d76b7c9ca26f..773dfa85ccb4 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/17.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/17.yml @@ -4,7 +4,7 @@ sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. + - Corrige SystemStackError (stack muito profundo) ao obter mais de 2^16 chaves de memcached. known_issues: - 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. - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/3.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/3.yml index 1cedf841406d..639820975516 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/3.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/3.yml @@ -8,15 +8,15 @@ sections: - A variável de data de vencimento do SAML não era configurável. - Os serviços do aplicativo falhariam as suas verificações de saúde durante a configuração fossem aplicadas antes de poderem entrar em um estado saudável. - '`ghe-cluster-config-node-init` falharia durante a configuração do cluster se o proxy HTTP estiver habilitado.' - - Pre-receive hooks could encounter an error `Failed to resolve full path of the current executable` due to `/proc` not being mounted on the container. + - Os hooks de pre-receive podem encontrar um erro `Failed to resolve full path of the current executable` due to `/proc` não sendo montado no container. - O Collectd não resolveria o nome de host de destino após a inicialização. - - The job that purged stale deleted repositories could fail to make progress if some of those repositories were protected from deletion by legal holds. + - O trabalho que os repositórios obsoletos excluídos pode não conseguir progredir se alguns desses repositórios estiverem protegidos da exclusão por retenção legal. - Os Trabalhos de fundo estavam sendo enfileirados na fila `spam` que não estavam sendo processados. - O método de merge preferido seria redefinido ao tentar novamente após um merge de PR falhada. - - Git pushes could result in a 500 Internal Server Error during the user reconciliation process on instances using LDAP authentication mode. + - Os pushes do Git podem gerar um erro de 500 servidor interno durante o processo de reconciliação do usuário em instâncias usando o modo de autenticação do LDAP. - 'Após a atualização de 3.0.x para 3.1.x, em alguns casos o GitHub Actions falharia com um erro: `An unexpected error occurred when executing this workflow.`' changes: - - Improved the efficiency of config apply by skipping IP allow firewall rules that had not changed, which saved significant time on large clusters. + - Aprimorou-se a eficiência da aplicação da configuração ao ignorar as regras de firewall para permitir IP, que não haviam sido alteradas, o que economizou tempo significativo em grandes clusters. known_issues: - 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. - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml index 2cbedda70444..ba138e341878 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/8.yml @@ -2,14 +2,14 @@ date: '2021-09-24' sections: security_fixes: - - '**HIGH:** A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} that could be exploited when building a {% data variables.product.prodname_pages %} site. User-controlled configuration options used by {% data variables.product.prodname_pages %} were not sufficiently restricted and made it possible to read files on the {% data variables.product.prodname_ghe_server %} instance. To exploit this vulnerability, an attacker would need permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.1.8 and was fixed in 3.1.8, 3.0.16, and 2.22.22. This is the result of an incomplete fix for CVE-2021-22867. This vulnerability was reported via the GitHub Bug Bounty program and has been assigned CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' - - '**MEDIUM:** An improper access control vulnerability in {% data variables.product.prodname_ghe_server %} allowed a workflow job to execute in a self-hosted runner group it should not have had access to. This affects customers using self-hosted runner groups for access control. A repository with access to one enterprise runner group could access all of the enterprise runner groups within the organization because of improper authentication checks during the request. This could cause code to be run unintentionally by the incorrect runner group. This vulnerability affected {% data variables.product.prodname_ghe_server %} versions from 3.0.0 to 3.0.15 and 3.1.0 to 3.1.7 and was fixed in 3.0.16 and 3.1.8 releases. It has been assigned CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' + - '**ALTO:** Uma vulnerabilidade transversal de caminho foi identificada em {% data variables.product.prodname_ghe_server %}, que poderia ser explorada ao criar um site de {% data variables.product.prodname_pages %}. As opções de configuração controladas pelo usuário usadas por {% data variables.product.prodname_pages %} não eram suficientemente restritas e possibilitaram a leitura de arquivos na instância de {% data variables.product.prodname_ghe_server %}. Para explorar essa vulnerabilidade, um invasor precisaria de permissão para criar e um site de {% data variables.product.prodname_pages %} na instância de {% data variables.product.prodname_ghe_server %}. Esta vulnerabilidade afetou todas as versões de {% data variables.product.prodname_ghe_server %} anteriores à versão 3.1.8 e foi corrigida nas versões 3.1.8, 3.0.16 e 2.22.22. Este é o resultado de uma correção incompleta para o CVE-2021-22867. Esta vulnerabilidade foi relatada por meio do programa de Compensação de Erros do GitHub e recebeu o CVE-2021-22868. {% comment %} https://github.com/github/pages/pull/3361, https://github.com/github/pages/pull/3357 {% endcomment %}' + - '**MÉDIO:** Uma vulnerabilidade de controle de acesso imprópria em {% data variables.product.prodname_ghe_server %} permitiu que uma tarefa de fluxo de trabalho fosse executada em um grupo de executores auto-hospedados ao qual não deveria ter acesso. Isto afeta os clientes usando grupos de executores auto-hospedados para controle de acesso. Um repositório com acesso a um grupo de corredores corporativos poderia acessar todos os grupos de executores corporativos dentro da organização por causa das verificações de autenticação inadequadas durante a solicitação. Isso pode fazer com que o código seja executado involuntariamente pelo grupo de executores incorreto. Essa vulnerabilidade afetou {% data variables.product.prodname_ghe_server %} versões de 3.0.0 até 3.0.15 e 3.1.0 a 3.1.7 e foi corrigido nas versões 3.0.16 e 3.1.8. Atribuiu-se um CVE-2021-22869. {% comment %} https://github.com/github/enterprise2/pull/27013 {% endcomment %}' bugs: - - 'Resque worker counts were displayed incorrectly during maintenance mode. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' - - 'Allocated memcached memory could be zero in clustering mode. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' - - 'Non-empty binary files displayed an incorrect file type and size on the pull request "Files" tab. {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' + - 'As contagens dos trabalhadores de Resque foram exibidas incorretamente no modo de manutenção. {% comment %} https://github.com/github/enterprise2/pull/26899, https://github.com/github/enterprise2/pull/26883 {% endcomment %}' + - 'A memória memorizada memcached poderia ser zero no modo de clustering. {% comment %} https://github.com/github/enterprise2/pull/26928, https://github.com/github/enterprise2/pull/26832 {% endcomment %}' + - 'Os arquivos binários não vazios exibiram um tipo de arquivo e tamanho incorreto na aba "Arquivos". {% comment %} https://github.com/github/github/pull/192810, https://github.com/github/github/pull/172284, https://github.com/github/coding/issues/694 {% endcomment %}' - 'Corrige versões {% data variables.product.prodname_pages %} para que elas levem em conta a configuração NO_PROXY do aparelho. Isto é relevante para os aparelhos configurados apenas com um proxy HTTP. (atualização 2021-09-30) {% comment %} https://github.com/github/pages/pull/3360 {% endcomment %}' - - 'The GitHub Connect configuration of the source instance was always restored to new instances even when the `--config` option for `ghe-restore` was not used. This would lead to a conflict with the GitHub Connect connection and license synchronization if both the source and destination instances were online at the same time. The fix also requires updating backup-utils to 3.2.0 or higher. [updated: 2021-11-18]' + - 'A configuração do GitHub Connect da instância de origem foi sempre restaurada para novas instâncias mesmo quando `--config` option for `ghe-restore` não foi usada. Isto geraria um conflito com a conexão e a sincronização de licença do GitHub Connect se as instâncias de origem e destino estivessem on-line ao mesmo tempo. A correção também exige atualização do backup-utils para a versão 3.2.0 ou superior. [atualizado: 2021-11-18]' known_issues: - 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. - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/9.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/9.yml index 8c585b2e810a..387bc90cb650 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/9.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/9.yml @@ -4,8 +4,8 @@ sections: security_fixes: - 'Os pacotes foram atualizados para as últimas versões de segurança. {% comment %} https://github.com/github/enterprise2/pull/27035, https://github.com/github/enterprise2/pull/27010 {% endcomment %}' bugs: - - 'Custom pre-receive hooks could have failed due to too restrictive virtual memory or CPU time limits. {% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' - - 'Attempting to wipe all existing configuration settings with `ghe-cleanup-settings` failed to restart the Management Console service. {% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' + - 'É possível que os hooks pre-receive personalizados tenham falhado devido a limites de tempo de memória virtual ou CPU muito restritivos. {% comment %} https://github.com/github/enterprise2/pull/26972, https://github.com/github/enterprise2/pull/26955 {% endcomment %}' + - 'A tentativa de limpar todas as configurações existentes com `ghe-cleanup-settings` falhou ao reiniciar o serviço do Console de Gerenciamento. {% comment %} https://github.com/github/enterprise2/pull/26987, https://github.com/github/enterprise2/pull/26901 {% endcomment %}' - 'During replication teardown via `ghe-repl-teardown` Memcached failed to be restarted. {% comment %} https://github.com/github/enterprise2/pull/26993, https://github.com/github/enterprise2/pull/26983 {% endcomment %}' - 'During periods of high load, users would receive HTTP 503 status codes when upstream services failed internal healthchecks. {% comment %} https://github.com/github/enterprise2/pull/27082, https://github.com/github/enterprise2/pull/26999 {% endcomment %}' - 'With Actions configured, MSSQL replication would fail after restoring from a GitHub Enterprise Backup Utilities snapshot. {% comment %} https://github.com/github/enterprise2/pull/27097, https://github.com/github/enterprise2/pull/26254 {% endcomment %}' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/2.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/2.yml index e073717c950f..d7280824bd72 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/2.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/2.yml @@ -3,12 +3,12 @@ date: '2021-10-28' sections: security_fixes: - 'It was possible for cleartext passwords to end up in certain log files.' - - 'Several known weak SSH public keys have been added to the deny list and can no longer be registered. In addition, versions of GitKraken known to generate weak SSH keys (7.6.x, 7.7.x and 8.0.0) have been blocked from registering new public keys.' + - 'Várias chaves públicas SSH fracas conhecidas foram adicionadas à lista de recusas e já não podem ser registradas. Além disso, as versões do GitKraken conhecidas por gerar chaves SSH fracas (7.6.x, 7.7.x e 8.0.0) foram impedidas de registrar novas chaves públicas.' - 'Os pacotes foram atualizados para as últimas versões de segurança.' bugs: - 'Restore might fail for enterprise server in clustering mode if orchestrator is not healthily.' - 'Codespaces links were displayed in organization settings.' - - 'Several parts of the application were unusable for users who are owners of many organizations.' + - 'Várias partes do aplicativo eram inutilizáveis para usuários que são proprietários de várias organizações.' - 'Fixed a link to https://docs.github.com.' changes: - 'Browsing and job performance optimizations for repositories with many refs.' diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/3.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/3.yml index 93185e9b222f..4f709566ab00 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/3.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/3.yml @@ -5,9 +5,9 @@ sections: - A path traversal vulnerability was identified in {% data variables.product.prodname_pages %} builds on {% data variables.product.prodname_ghe_server %} that could allow an attacker to read system files. To exploit this vulnerability, an attacker needed permission to create and build a {% data variables.product.prodname_pages %} site on the {% data variables.product.prodname_ghe_server %} instance. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.3, and was fixed in versions 3.0.19, 3.1.11, and 3.2.3. This vulnerability was reported through the {% data variables.product.company_short %} Bug Bounty program and has been assigned CVE-2021-22870. - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Some Git operations failed after upgrading a {% data variables.product.prodname_ghe_server %} 3.x cluster because of the HAProxy configuration. - - Unicorn worker counts might have been set incorrectly in clustering mode. - - Resqued worker counts might have been set incorrectly in clustering mode. + - Algumas operações Git falharam depois de atualizar um cluster 3.x de {% data variables.product.prodname_ghe_server %} devido à configuração do HAProxy. + - É possível que as contagens de trabalhadores do Unicorn possam ter sido definidas de forma incorreta no modo de agrupamento. + - É possível que as contagens dos trabalhadores do Resqued possam ter sido definidas incorretamente no modo cluster. - If Ubuntu's Uncomplicated Firewall (UFW) status was inactive, a client could not clearly see it in the logs. - Upgrading from {% data variables.product.prodname_ghe_server %} 2.x to 3.x failed when there were UTF8 characters in an LDAP configuration. - Some pages and Git-related background jobs might not run in cluster mode with certain cluster configurations. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml index afd9fdced15e..c2553f790b9f 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/4.yml @@ -5,20 +5,20 @@ sections: security_fixes: - Os pacotes foram atualizados para as últimas versões de segurança. bugs: - - Running `ghe-repl-start` or `ghe-repl-status` would sometimes return errors connecting to the database when GitHub Actions was enabled. - - Pre-receive hooks would fail due to undefined `PATH`. - - 'Running `ghe-repl-setup` would return an error: `cannot create directory /data/user/elasticsearch: File exists` if the instance had previously been configured as a replica.' + - Executar `ghe-repl-start` ou `ghe-repl-status` às vezes poderia retornar erros conectados ao banco de dados quando o GitHub Actions foi habilitado. + - Os hooks de pre-receive falhariam em razão de `PATH` indefinido. + - 'A execução de `ghe-repl-setup` retornaria um erro: `cannot create directory /data/user/elasticsearch: File exists` se a instância tiver sido configurada anteriormente como uma réplica.' - 'Running `ghe-support-bundle` returned an error: `integer expression expected`.' - - 'After setting up a high availability replica, `ghe-repl-status` included an error in the output: `unexpected unclosed action in command`.' - - In large cluster environments, the authentication backend could be unavailable on a subset of frontend nodes. - - Some critical services may not have been available on backend nodes in GHES Cluster. + - 'Após configurar uma réplica de alta disponibilidade, o ''ghe-repl-status'' incluiu um erro na saída: `unexpected unclosed action in command`.' + - Em ambientes de grandes clusters, o back-end de autenticação pode estar indisponível em um subconjunto de nós do frontend. + - Alguns serviços críticos podem não estar disponíveis em nós de backend do Cluster do GHES. - The repository permissions to the user returned by the `/repos` API would not return the full list. - The `childTeams` connection on the `Team` object in the GraphQL schema produced incorrect results under some circumstances. - In a high availability configuration, repository maintenance always showed up as failed in stafftools, even when it succeeded. - User defined patterns would not detect secrets in files like `package.json` or `yarn.lock`. changes: - - An additional outer layer of `gzip` compression when creating a cluster support bundle with `ghe-cluster-suport-bundle` is now turned off by default. This outer compression can optionally be applied with the `ghe-cluster-suport-bundle -c` command line option. - - We have added extra text to the admin console to remind users about the mobile apps' data collection for experience improvement purposes. + - A camada externa adicional de compressão `gzip` ao criar um pacote de suporte de cluster com `ghe-cluster-suport-bundle` agora está desativada por padrão. Essa compressão externa pode ser aplicada opcionalmente com a opção de linha de comando `ghe-cluster-suport-bundle -c`. + - Nós adicionamos texto adicional ao console de administração para lembrar os usuários da coleta de dados dos aplicativos móveis para fins de melhoria de experiência. - The {% data variables.product.prodname_github_connect %} data connection record now includes a list of enabled {% data variables.product.prodname_github_connect %} features. [Updated 2021-12-09] known_issues: - Em uma nova configuração de {% data variables.product.prodname_ghe_server %} sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/9.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/9.yml index aad01f2d0546..5af300bf23da 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/9.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/9.yml @@ -7,7 +7,7 @@ sections: bugs: - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. + - Corrige SystemStackError (stack muito profundo) ao obter mais de 2^16 chaves de memcached. changes: - Secret scanning will skip scanning ZIP and other archive files for secrets. known_issues: diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-3/4.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-3/4.yml index 5a9a0ba0b239..2cf784b8a859 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-3/4.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-3/4.yml @@ -7,7 +7,7 @@ sections: bugs: - GitHub Packages storage settings could not be validated and saved in the Management Console when Azure Blob Storage was used. - The mssql.backup.cadence configuration option failed ghe-config-check with an invalid characterset warning. - - Fixes SystemStackError (stack too deep) when getting more than 2^16 keys from memcached. + - Corrige SystemStackError (stack muito profundo) ao obter mais de 2^16 chaves de memcached. - A number of select menus across the site rendered incorrectly and were not functional. changes: - Dependency Graph can now be enabled without vulnerability data, allowing customers to see what dependencies are in use and at what versions. Enabling Dependency Graph without enabling GitHub Connect will *not* provide vulnerability information. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml index 18c532c50d8d..3979fa75017b 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -148,6 +148,7 @@ sections: - 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. + - Actions services needs to be restarted after restoring appliance from backup taken on a different host. deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 diff --git a/translations/pt-BR/data/reusables/accounts/accounts-billed-separately.md b/translations/pt-BR/data/reusables/accounts/accounts-billed-separately.md index 79e9ab7d1d4d..ba9660a5d776 100644 --- a/translations/pt-BR/data/reusables/accounts/accounts-billed-separately.md +++ b/translations/pt-BR/data/reusables/accounts/accounts-billed-separately.md @@ -1 +1 @@ -Each account on {% data variables.product.product_name %} is billed separately. Upgrading an organization account enables paid features for the organization's repositories only and does not affect the features available in repositories owned by any associated personal accounts. Similarly, upgrading a personal account enables paid features for the personal account's repositories only and does not affect the repositories of any organization accounts. Para obter mais informações sobre os tipos de conta, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". +Cada conta em {% data variables.product.product_name %} é cobrada separadamente. Fazer a atualização de uma conta de organização permite apenas funcionalidades pagas para repositórios da organização e não afeta os recursos disponíveis nos repositórios pertencentes a contas pessoais associadas. Da mesma forma, a atualização de uma conta pessoal permite funcionalidades pagas apenas para repositórios da conta pessoal e não afeta os repositórios de contas de qualquer organização. Para obter mais informações sobre os tipos de conta, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". diff --git a/translations/pt-BR/data/reusables/accounts/you-must-know-your-password.md b/translations/pt-BR/data/reusables/accounts/you-must-know-your-password.md index f4795c3909e7..e09d3453f2f4 100644 --- a/translations/pt-BR/data/reusables/accounts/you-must-know-your-password.md +++ b/translations/pt-BR/data/reusables/accounts/you-must-know-your-password.md @@ -1 +1 @@ -If you protect your personal account with two-factor authentication but do not know your password, you will not be able to generate a one-time password to recover your account. {% data variables.product.company_short %} can send a password reset email to a verified address associated with your account. For more information, see "[Updating your {% data variables.product.prodname_dotcom %} access credentials](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)." +Se você proteger sua conta pessoal com autenticação de dois fatores, mas não souber a sua senha, você não poderá gerar uma senha única para recuperar sua conta. {% data variables.product.company_short %} pode enviar um e-mail de redefinição de senha para um endereço verificado associado à sua conta. Para obter mais informações, consulte "[Atualizando suas credenciais de acesso a {% data variables.product.prodname_dotcom %}](/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials#requesting-a-new-password)". diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md index 7a3774de81ad..3b742b9d2cc4 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs-specific.md @@ -1,11 +1,11 @@ -For a specific job, you can use `jobs..permissions` to modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +Para um trabalho específico, você pode usar `jobs..permissions` para modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionar ou remover o acesso conforme necessário, para que você apenas permita o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". Ao especificar a permissão de uma definição de trabalho, você pode configurar um conjunto diferente de permissões para o `GITHUB_TOKEN` para cada trabalho, se necessário. Como alternativa, você pode especificar as permissões para todas as tarefas do fluxo de trabalho. Para informações sobre como definir permissões no nível do fluxo de trabalho, consulte [`permissões`](/actions/using-workflows/workflow-syntax-for-github-actions#permissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -#### Example: Setting permissions for a specific job +#### Exemplo: Configurar permissões para um trabalho específico Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que só se aplicará ao trabalho denominado `stale`. O acesso de gravação é concedido para os escopos dos `problemas` e `pull-requests`. Todos os outros escopos não terão acesso. diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md index bb0339f406e1..2cdde46e52f2 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-assigning-permissions-to-jobs.md @@ -1,11 +1,11 @@ -You can use `permissions` to modify the default permissions granted to the `GITHUB_TOKEN`, adding or removing access as required, so that you only allow the minimum required access. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". +Você pode usar as `permissões` para modificar as permissões padrão concedidas ao `GITHUB_TOKEN`, adicionar ou remover o acesso conforme necessário, para que você permita apenas o acesso mínimo necessário. Para obter mais informações, consulte "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)". Você pode usar as permissões de `` como uma chave de nível superior, para aplicar a todos os trabalhos do fluxo de trabalho ou em trabalhos específicos. Ao adicionar a chave das `permissões` em um trabalho específico, todas as ações e comandos de execução dentro desse trabalho que usam o `GITHUB_TOKEN` ganham os direitos de acesso que você especificar. Para obter mais informações, consulte [`jobs..permissions`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idpermissions). {% data reusables.github-actions.github-token-available-permissions %} {% data reusables.github-actions.forked-write-permission %} -### Example: Assigning permissions to GITHUB_TOKEN +### Exemplo: Atribuindo permissões ao GITHUB_TOKEN Este exemplo mostra as permissões que estão sendo definidas para o `GITHUB_TOKEN` que será aplicado a todos os trabalhos do fluxo de trabalho. É concedido acesso de leitura a todas as permissões. diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index 399eebff7a9d..349be91971ca 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -1,10 +1,10 @@ -Use `jobs..runs-on` to define the type of machine to run the job on. {% ifversion fpt or ghec %}A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado.{% endif %} Você pode fornecer `runs-on` como uma única string ou como uma matriz de strings. Se você especificar uma matriz de strings, o seu fluxo de trabalho será executado em um executor auto-hospedado cujas etiquetas correspondam a todos os valores de `runs-on`, se disponível. Se você quiser executar seu fluxo de trabalho em várias máquinas, use [`jobs..strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy). +Use `jobs..runs-on` para definir o tipo de máquina para executar o trabalho. {% ifversion fpt or ghec %}A máquina pode ser ou um executor hospedado em {% data variables.product.prodname_dotcom %} ou um executor auto-hospedado.{% endif %} Você pode fornecer `runs-on` como uma única string ou como uma matriz de strings. Se você especificar uma matriz de strings, o seu fluxo de trabalho será executado em um executor auto-hospedado cujas etiquetas correspondam a todos os valores de `runs-on`, se disponível. Se você quiser executar seu fluxo de trabalho em várias máquinas, use [`jobs..strategy`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategy). {% ifversion fpt or ghec or ghes %} {% data reusables.actions.enterprise-github-hosted-runners %} -### Choosing {% data variables.product.prodname_dotcom %}-hosted runners +### Escolhendo executores hospedados em {% data variables.product.prodname_dotcom %} Se você usar um executor hospedado no {% data variables.product.prodname_dotcom %}, cada trabalho será executado em uma nova instância de um ambiente virtual especificado por `runs-on`. @@ -12,7 +12,7 @@ Os tipos de executor disponíveis para {% data variables.product.prodname_dotcom {% data reusables.github-actions.supported-github-runners %} -#### Example: Specifying an operating system +#### Exemplo: Especificar um sistema operacional ```yaml runs-on: ubuntu-latest @@ -22,14 +22,14 @@ Para obter mais informações, consulte "[Ambientes virtuais para executores hos {% endif %} {% ifversion fpt or ghec or ghes %} -### Choosing self-hosted runners +### Escolhendo executores auto-hospedados {% endif %} {% data reusables.actions.ae-self-hosted-runners-notice %} {% data reusables.github-actions.self-hosted-runner-labels-runs-on %} -#### Example: Using labels for runner selection +#### Exemplo: Usando etiquetas para seleção do executor ```yaml runs-on: [self-hosted, linux] diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md index 9329eed1cf02..081b4cb70cb6 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md @@ -1,10 +1,10 @@ -You can use `jobs..outputs` to create a `map` of outputs for a job. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs..needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds). +Você pode usar `jobs..outputs` para criar um `mapa` de saídas para um trabalho. As saídas de trabalho estão disponíveis para todos os trabalhos downstream que dependem deste trabalho. Para obter mais informações sobre a definição de dependências de trabalhos, consulte [`jobs..needs`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idneeds). As saídas de trabalho são strings e saídas de trabalho que contêm expressões são avaliadas no executor ao final de cada trabalho. As saídas que contêm segredos são eliminadas no executor e não são enviadas para {% data variables.product.prodname_actions %}. Para usar as saídas de trabalho em um trabalho dependente, você poderá usar o contexto `needs`. Para obter mais informações, consulte "[Contextos](/actions/learn-github-actions/contexts#needs-context)". -### Example: Defining outputs for a job +### Exemplo: Definindo saídas para um trabalho {% raw %} ```yaml diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md b/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md index d645231024f0..54b1b5321b91 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-credentials.md @@ -1,6 +1,6 @@ {% data reusables.actions.registry-credentials %} -#### Example: Defining credentials for a container registry +#### Exemplo: Definindo credenciais para o registro de um contêiner {% raw %} ```yaml diff --git a/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md b/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md index a59a63c8543d..84e9ed53e5c7 100644 --- a/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md +++ b/translations/pt-BR/data/reusables/actions/jobs/section-running-jobs-in-a-container-env.md @@ -1 +1 @@ -Use `jobs..container.env` to set a `map` of environment variables in the container. \ No newline at end of file +Usar `jobs..container.env` para definir um `mapa` de variáveis de ambiente no contêiner. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/advanced-security/starter-workflow-overview.md b/translations/pt-BR/data/reusables/advanced-security/starter-workflow-overview.md index 7425d26a2982..5c082f638fc0 100644 --- a/translations/pt-BR/data/reusables/advanced-security/starter-workflow-overview.md +++ b/translations/pt-BR/data/reusables/advanced-security/starter-workflow-overview.md @@ -1 +1 @@ -{% data variables.product.product_name %} provides starter workflows for security features such as {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. \ No newline at end of file +{% data variables.product.product_name %} provides starter workflows for security features such as {% data variables.product.prodname_code_scanning %}. Você pode usar esses fluxos de trabalho sugeridos para construir seus fluxos de trabalho de {% data variables.product.prodname_code_scanning %}, ao invés de começar do zero. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/billing-for-prebuilds.md b/translations/pt-BR/data/reusables/codespaces/billing-for-prebuilds.md new file mode 100644 index 000000000000..0fcf41de691a --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/billing-for-prebuilds.md @@ -0,0 +1,5 @@ +A {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." + +If you are an organization owner, you can track usage of prebuild workflows by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." Para obter mais informações, consulte "[Visualizar o uso do seu {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)". + +While {% data variables.product.prodname_codespaces %} prebuilds is in beta there is no charge for storage of templates. When prebuilds become generally available, you will be billed for storing prebuild templates for each prebuild configuration in each region selected for that configuration. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/prebuilds-beta-note.md b/translations/pt-BR/data/reusables/codespaces/prebuilds-beta-note.md new file mode 100644 index 000000000000..7e48d1342cd4 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/prebuilds-beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The ability to prebuild codespaces is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/codespaces/prebuilds-crossreference.md b/translations/pt-BR/data/reusables/codespaces/prebuilds-crossreference.md new file mode 100644 index 000000000000..e7697bec4262 --- /dev/null +++ b/translations/pt-BR/data/reusables/codespaces/prebuilds-crossreference.md @@ -0,0 +1 @@ +To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-release-phase.md b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-release-phase.md index 8b8f769a90a4..3ac13f76079f 100644 --- a/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-release-phase.md +++ b/translations/pt-BR/data/reusables/enterprise-accounts/dormant-user-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Dormant Users report is currently in private beta so admins only have access to this feature with a special invite. To join the private beta, receive support, or address your questions, contact the {% data variables.product.company_short %} representative who helps manage your account. +**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability. {% endnote %} diff --git a/translations/pt-BR/data/reusables/security-advisory/repository-level-advisory-note.md b/translations/pt-BR/data/reusables/security-advisory/repository-level-advisory-note.md index dd7f32d588fe..98a16a52eae1 100644 --- a/translations/pt-BR/data/reusables/security-advisory/repository-level-advisory-note.md +++ b/translations/pt-BR/data/reusables/security-advisory/repository-level-advisory-note.md @@ -2,6 +2,6 @@ **Note**: This article applies to editing repository-level advisories as a repository owner. -Users who are not repository owners can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." +Users who are not repository owners can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). As edições nas consultorias globais não mudarão ou afetarão a forma como a consultoria aparece no repositório. Para obter mais informações, consulte "[Editando consultorias de segurança em {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)." {% endnote %} \ No newline at end of file