From 94409f9d379a533df8160bed37bf3f44e4dda683 Mon Sep 17 00:00:00 2001 From: Nick McCurdy Date: Tue, 19 Jul 2022 07:19:46 -0400 Subject: [PATCH 01/41] Remove implied GraphQL API Explorer scope --- content/graphql/guides/forming-calls-with-graphql.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/graphql/guides/forming-calls-with-graphql.md b/content/graphql/guides/forming-calls-with-graphql.md index 7f7f6f01a0..5526810b97 100644 --- a/content/graphql/guides/forming-calls-with-graphql.md +++ b/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ The following scopes are recommended: ``` repo -repo_deployment read:packages read:org read:public_key From 1aa82241d25ef72942f76b594105ea237eb58327 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Wed, 20 Jul 2022 15:43:25 -0700 Subject: [PATCH 02/41] First pass a documenting Pages on Actions GA --- ...lishing-source-for-your-github-pages-site.md | 10 ++-------- ...ekyll-build-errors-for-github-pages-sites.md | 17 +++-------------- data/features/build-pages-with-actions.yml | 5 +++++ data/reusables/pages/check-workflow-run.md | 10 +++------- ...es-builds-with-github-actions-public-beta.md | 5 ----- 5 files changed, 13 insertions(+), 34 deletions(-) create mode 100644 data/features/build-pages-with-actions.yml delete mode 100644 data/reusables/pages/pages-builds-with-github-actions-public-beta.md diff --git a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index bf76deca2f..66158678f6 100644 --- a/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -49,17 +49,11 @@ shortTitle: Configure publishing source If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} workflow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." - -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% endif %} diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index b76538436f..c277060f5e 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,27 +30,16 @@ shortTitle: Jekyll build errors for Pages {% endnote %} -If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. -- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. -- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion fpt %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %} {% endif %} -## Viewing your repository's build failures on {% data variables.product.product_name %} - -You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. - ## Viewing Jekyll build error messages locally We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." @@ -63,7 +52,7 @@ We recommend testing your site locally, which allows you to see build error mess ## Viewing Jekyll build errors by email -{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. You'll also receive emails for build warnings. {% data reusables.pages.build-failure-email-server %} +{% ifversion pages-custom-workflow %}If you are publishing from a branch, when{% else %}When{% endif %} you push changes to your publishing source on {% data variables.product.product_name %}, {% data variables.product.prodname_pages %} will attempt to build your site. If the build fails, you'll receive an email at your primary email address. {% data reusables.pages.build-failure-email-server %} {% ifversion pages-custom-workflow %}If you are publishing with a custom {% data variables.product.prodname_actions %} workflow, in order to receive emails about build errors in your pull request, you must configure your workflow to run on the `pull_request` trigger. When you do this, we recommend that you skip any deploy steps if the workflow was triggered by the `pull_request` event. This will allow you to see any build errors without deploying the changes from your pull request to your site. For more information, see "[Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows#pull_request)" and "[Expressions](/actions/learn-github-actions/expressions)."{% endif %} diff --git a/data/features/build-pages-with-actions.yml b/data/features/build-pages-with-actions.yml new file mode 100644 index 0000000000..458017e24d --- /dev/null +++ b/data/features/build-pages-with-actions.yml @@ -0,0 +1,5 @@ +# Issue 7584 +# Building Pages sites with Actions [GA] +versions: + fpt: '*' + ghec: '*' diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index f4f66b6f9f..664639dd7f 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,8 +1,4 @@ -{% ifversion fpt %} -1. Unless your {% data variables.product.prodname_pages %} site is built from a private or internal repository and published from a branch, your site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information about how to view the workflow status, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." +{% ifversion build-pages-with-actions %} +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the amount of free minutes they are given each. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)" and "{% data variables.product.prodname_actions %} [Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)". -{% note %} - -{% data reusables.pages.pages-builds-with-github-actions-public-beta %} - -{% endnote %}{% endif %} +{% endif %} \ No newline at end of file diff --git a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md b/data/reusables/pages/pages-builds-with-github-actions-public-beta.md deleted file mode 100644 index 0daefdc979..0000000000 --- a/data/reusables/pages/pages-builds-with-github-actions-public-beta.md +++ /dev/null @@ -1,5 +0,0 @@ -{% ifversion fpt %} - -**Note:** {% data variables.product.prodname_actions %} workflow runs for your {% data variables.product.prodname_pages %} sites are in public beta for public repositories and subject to change. {% data variables.product.prodname_actions %} workflow runs are free for public repositories. - -{% endif %} From 633622f6a34e5e81373704fd1adaac655ae73747 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Wed, 20 Jul 2022 15:55:25 -0700 Subject: [PATCH 03/41] Add billing change --- data/reusables/gated-features/environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md index a74a249da7..97b6b0c679 100644 --- a/data/reusables/gated-features/environments.md +++ b/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** repositories, you must use {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** and **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} From bd52f8d34ec27b4daad75f640fb48e86a12f9999 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:35:12 -0700 Subject: [PATCH 04/41] Update data/reusables/gated-features/environments.md Co-authored-by: Sarah Edwards --- data/reusables/gated-features/environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/gated-features/environments.md b/data/reusables/gated-features/environments.md index 97b6b0c679..87a40b9ed1 100644 --- a/data/reusables/gated-features/environments.md +++ b/data/reusables/gated-features/environments.md @@ -1 +1 @@ -Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** and **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} +Environments, environment protection rules, and environment secrets are available in **public** repositories for all products. For access to environments in **private** or **internal** repositories, you must use {% data variables.product.prodname_pro %}, {% data variables.product.prodname_team %}, or {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info %} From 6e841736cebe80c39a11063bbc5df991092947ac Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:37:07 -0700 Subject: [PATCH 05/41] Update content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md Co-authored-by: Sarah Edwards --- .../about-jekyll-build-errors-for-github-pages-sites.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index c277060f5e..962299c2ed 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -30,7 +30,13 @@ shortTitle: Jekyll build errors for Pages {% endnote %} +{% ifversion build-pages-with-actions %} If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. +{% else %} +If Jekyll does attempt to build your site and encounters an error, you will receive a build error message. There are two main types of Jekyll build error messages. +- A "Page build warning" message means your build completed successfully, but you may need to make changes to prevent future problems. +- A "Page build failed" message means your build failed to complete. If Jekyll is able to detect a reason for the failure, you'll see a descriptive error message. +{% endif %} For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." From 7039d016db7544ec15fd8b380407825af6f83f40 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:39:05 -0700 Subject: [PATCH 06/41] Update data/reusables/pages/check-workflow-run.md Co-authored-by: Sarah Edwards --- data/reusables/pages/check-workflow-run.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index 664639dd7f..4b44fa889c 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,4 +1,10 @@ {% ifversion build-pages-with-actions %} -1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the amount of free minutes they are given each. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)" and "{% data variables.product.prodname_actions %} [Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)". +1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". + +{% note %} + +{% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". + +{% endnote %} {% endif %} \ No newline at end of file From ca7820cab6eb86119b3f2ba2ca995d1aaad22471 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:39:44 -0700 Subject: [PATCH 07/41] Update content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md Co-authored-by: Sarah Edwards --- .../about-jekyll-build-errors-for-github-pages-sites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 962299c2ed..741830eda9 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -40,7 +40,7 @@ If Jekyll does attempt to build your site and encounters an error, you will rece For more information about troubleshooting build errors, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites)." -{% ifversion fpt %} +{% ifversion build-pages-with-actions %} ## Viewing Jekyll build error messages with {% data variables.product.prodname_actions %} By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." From 570fcb71a5fc284a6cb651d3d7ffbdad89140695 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 16:47:51 -0700 Subject: [PATCH 08/41] Gate some content instead of removing it completly --- .../about-jekyll-build-errors-for-github-pages-sites.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md index 741830eda9..9e84172aa2 100644 --- a/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md +++ b/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md @@ -46,6 +46,12 @@ For more information about troubleshooting build errors, see "[Troubleshooting J By default, your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow run unless you've configured your {% data variables.product.prodname_pages %} site to use a different CI tool. To find potential build errors, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% endif %} +{% ifversion build-pages-with-actions %}{% else %} +## Viewing your repository's build failures on {% data variables.product.product_name %} + +You can see build failures (but not build warnings) for your site on {% data variables.product.product_name %} in the **Settings** tab of your site's repository. +{% endif %} + ## Viewing Jekyll build error messages locally We recommend testing your site locally, which allows you to see build error messages on the command line, and addressing any build failures before pushing changes to {% data variables.product.product_name %}. For more information, see "[Testing your {% data variables.product.prodname_pages %} site locally with Jekyll](/articles/testing-your-github-pages-site-locally-with-jekyll)." From 2edca69c0ebaae10b680d4d378d7cff687186e99 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Thu, 21 Jul 2022 17:22:41 -0700 Subject: [PATCH 09/41] More billing changes --- .../using-environments-for-deployment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index a51cc186df..2e7850abd1 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ You can configure environments with protection rules and secrets. When a workflo **Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. -Organizations that use {% data variables.product.prodname_ghe_cloud %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% data reusables.enterprise.link-to-ghec-trial %} +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). {% endnote %} {% endif %} @@ -74,7 +74,7 @@ Secrets stored in an environment are only available to workflow jobs that refere {% ifversion fpt or ghec %} {% note %} -**Note:** To create an environment in a private repository, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %} +**Note:** Creation of an environment in a private repository is available to organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %}. {% endnote %} {% endif %} From 2089b25821d48ad9d23967370cbd6c10bd090379 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Fri, 22 Jul 2022 09:30:44 -0700 Subject: [PATCH 10/41] Update content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md Co-authored-by: Sarah Edwards --- .../using-environments-for-deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index 2e7850abd1..68c4e5b4e5 100644 --- a/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -27,7 +27,7 @@ You can configure environments with protection rules and secrets. When a workflo **Note:** You can only configure environments for public repositories. If you convert a repository from public to private, any configured protection rules or environment secrets will be ignored, and you will not be able to configure any environments. If you convert your repository back to public, you will have access to any previously configured protection rules and environment secrets. -Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/deployment/targeting-different-environments/using-environments-for-deployment). +Organizations with {% data variables.product.prodname_team %} and users with {% data variables.product.prodname_pro %} can configure environments for private repositories. For more information, see "[{% data variables.product.prodname_dotcom %}'s products](/get-started/learning-about-github/githubs-products)." {% endnote %} {% endif %} From 76a6d67dfe7d6994976c32af197c2cb4b952ca67 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Fri, 22 Jul 2022 09:36:32 -0700 Subject: [PATCH 11/41] Fix indentation --- data/reusables/pages/check-workflow-run.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/data/reusables/pages/check-workflow-run.md b/data/reusables/pages/check-workflow-run.md index 4b44fa889c..1af0012c40 100644 --- a/data/reusables/pages/check-workflow-run.md +++ b/data/reusables/pages/check-workflow-run.md @@ -1,10 +1,10 @@ {% ifversion build-pages-with-actions %} 1. Your {% data variables.product.prodname_pages %} site is built and deployed with a {% data variables.product.prodname_actions %} workflow. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)". -{% note %} + {% note %} -{% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". + **Note:** {% data variables.product.prodname_actions %} is free for public repositories. Usage charges apply for private and internal repositories that go beyond the monthly allotment of free minutes. For more information, see "[Usage limits, billing, and administration](/actions/reference/usage-limits-billing-and-administration)". -{% endnote %} + {% endnote %} {% endif %} \ No newline at end of file From 84dbbb3f65e25a54d30cc5c99283ec750d4996c3 Mon Sep 17 00:00:00 2001 From: Harsh Kumar <95894045+thisisharsh7@users.noreply.github.com> Date: Thu, 28 Jul 2022 08:32:03 +0530 Subject: [PATCH 12/41] Create README.md --- assets/images/README.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 assets/images/README.md diff --git a/assets/images/README.md b/assets/images/README.md new file mode 100644 index 0000000000..d547029560 --- /dev/null +++ b/assets/images/README.md @@ -0,0 +1,5 @@ +# Images🖼️ +The `/assets/images` directory holds all the site's images. + + +See the [contributing docs](/CONTRIBUTING.md) for general information about working with the docs. From 63de3fdf6ca256c9515ea2c795de15b91c5047e9 Mon Sep 17 00:00:00 2001 From: Aditya Patel Date: Wed, 3 Aug 2022 18:06:15 +0530 Subject: [PATCH 13/41] =?UTF-8?q?Replaced=20cross-marks=20=E2=9C=96?= =?UTF-8?q?=EF=B8=8F=20with=20tick-marks=20=E2=9C=94=EF=B8=8F=20to=20bette?= =?UTF-8?q?r=20represent=20permssions=20(#19503)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../repository-roles-for-an-organization.md | 190 +++++++++--------- 1 file changed, 95 insertions(+), 95 deletions(-) diff --git a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 9017551439..47112b17da 100644 --- a/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -63,89 +63,89 @@ Some of the features listed below are limited to organizations using {% data var | Repository action | Read | Triage | Write | Maintain | Admin | |:---|:---:|:---:|:---:|:---:|:---:| -| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **X** | -| Pull from the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Fork the person or team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Edit and delete their own comments | **X** | **X** | **X** | **X** | **X** | -| Open issues | **X** | **X** | **X** | **X** | **X** | -| Close issues they opened themselves | **X** | **X** | **X** | **X** | **X** | -| Reopen issues they closed themselves | **X** | **X** | **X** | **X** | **X** | -| Have an issue assigned to them | **X** | **X** | **X** | **X** | **X** | -| Send pull requests from forks of the team's assigned repositories | **X** | **X** | **X** | **X** | **X** | -| Submit reviews on pull requests | **X** | **X** | **X** | **X** | **X** | -| View published releases | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Edit wikis in public repositories | **X** | **X** | **X** | **X** | **X** | -| Edit wikis in private repositories | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| Apply/dismiss labels | | **X** | **X** | **X** | **X** | -| Create, edit, delete labels | | | **X** | **X** | **X** | -| Close, reopen, and assign all issues and pull requests | | **X** | **X** | **X** | **X** | -| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| Apply milestones | | **X** | **X** | **X** | **X** | -| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **X** | **X** | **X** | **X** | -| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Push to (write) the person or team's assigned repositories | | | **X** | **X** | **X** | -| Edit and delete anyone's comments on commits, pull requests, and issues | | | **X** | **X** | **X** | -| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **X** | **X** | **X** | -| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Submit reviews that affect a pull request's mergeability | | | **X** | **X** | **X** | -| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **X** | **X** | **X** | -| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** |{% endif %} -| Create and edit releases | | | **X** | **X** | **X** | -| View draft releases | | | **X** | **X** | **X** | -| Edit a repository's description | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [View and install packages](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** | {% endif %} -| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Enable wikis and restrict wiki editors | | | | **X** | **X** | -| Enable project boards | | | | **X** | **X** | -| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [Push to protected branches](/articles/about-protected-branches) | | | | **X** | **X** | -| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **X** | **X** | -| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **X** |{% endif %} -| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **X** | **X** |{% endif %} -| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **X** | -| [Define code owners for a repository](/articles/about-code-owners) | | | | | **X** | -| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **X** | -| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **X** | -| Change a repository's settings | | | | | **X** | -| Manage team and collaborator access to the repository | | | | | **X** | -| Edit the repository's default branch | | | | | **X** | -| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** | -| Manage webhooks and deploy keys | | | | | **X** |{% ifversion fpt or ghec %} -| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** |{% endif %} -| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Archive repositories](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** |{% endif %} -| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion discussions %} -| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **X** | **X** | -| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **X** | **X** | **X** | -| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| Create [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** |{% endif %} +| Manage [individual](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository), and [outside collaborator](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) access to the repository | | | | | **✔️** | +| Pull from the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Fork the person or team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Edit and delete their own comments | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Open issues | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Close issues they opened themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Reopen issues they closed themselves | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Have an issue assigned to them | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Send pull requests from forks of the team's assigned repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Submit reviews on pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| View published releases | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| View [GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Edit wikis in public repositories | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Edit wikis in private repositories | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [Report abusive or spammy content](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| Apply/dismiss labels | | **✔️** | **✔️** | **✔️** | **✔️** | +| Create, edit, delete labels | | | **✔️** | **✔️** | **✔️** | +| Close, reopen, and assign all issues and pull requests | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Enable and disable auto-merge on a pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| Apply milestones | | **✔️** | **✔️** | **✔️** | **✔️** | +| Mark [duplicate issues and pull requests](/articles/about-duplicate-issues-and-pull-requests)| | **✔️** | **✔️** | **✔️** | **✔️** | +| Request [pull request reviews](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | +| Merge a [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | +| Push to (write) the person or team's assigned repositories | | | **✔️** | **✔️** | **✔️** | +| Edit and delete anyone's comments on commits, pull requests, and issues | | | **✔️** | **✔️** | **✔️** | +| [Hide anyone's comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [Lock conversations](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Transfer issues (see "[Transferring an issue to another repository](/articles/transferring-an-issue-to-another-repository)" for details) | | | **✔️** | **✔️** | **✔️** | +| [Act as a designated code owner for a repository](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [Mark a draft pull request as ready for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [Convert a pull request to a draft](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| Submit reviews that affect a pull request's mergeability | | | **✔️** | **✔️** | **✔️** | +| [Apply suggested changes](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) to pull requests | | | **✔️** | **✔️** | **✔️** | +| Create [status checks](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Create, edit, run, re-run, and cancel [GitHub Actions workflows](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** |{% endif %} +| Create and edit releases | | | **✔️** | **✔️** | **✔️** | +| View draft releases | | | **✔️** | **✔️** | **✔️** | +| Edit a repository's description | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [View and install packages](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Publish packages](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [Delete and restore packages](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** | {% endif %} +| Manage [topics](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | +| Enable wikis and restrict wiki editors | | | | **✔️** | **✔️** | +| Enable project boards | | | | **✔️** | **✔️** | +| Configure [pull request merges](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | +| Configure [a publishing source for {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | +| [Manage branch protection rules](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [Push to protected branches](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| Merge pull requests on protected branches, even if there are no approving reviews | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| Create tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | +| Delete tags that match a [tag protection rule](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** |{% endif %} +| [Create and edit repository social cards](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Limit [interactions in a repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)| | | | **✔️** | **✔️** |{% endif %} +| Delete an issue (see "[Deleting an issue](/articles/deleting-an-issue)") | | | | | **✔️** | +| [Define code owners for a repository](/articles/about-code-owners) | | | | | **✔️** | +| Add a repository to a team (see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" for details) | | | | | **✔️** | +| [Manage outside collaborator access to a repository](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [Change a repository's visibility](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| Make a repository a template (see "[Creating a template repository](/articles/creating-a-template-repository)") | | | | | **✔️** | +| Change a repository's settings | | | | | **✔️** | +| Manage team and collaborator access to the repository | | | | | **✔️** | +| Edit the repository's default branch | | | | | **✔️** | +| Rename the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | +| Rename a branch other than the repository's default branch (see "[Renaming a branch](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | +| Manage webhooks and deploy keys | | | | | **✔️** |{% ifversion fpt or ghec %} +| [Manage data use settings for your private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** |{% endif %} +| [Manage the forking policy for a repository](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [Transfer repositories into the organization](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [Delete or transfer repositories out of the organization](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [Archive repositories](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| Display a sponsor button (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** |{% endif %} +| Create autolink references to external resources, like Jira or Zendesk (see "[Configuring autolinks to reference external resources](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} +| [Enable {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) in a repository | | | | **✔️** | **✔️** | +| [Create and edit categories](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) for {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | +| [Move a discussion to a different category](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Transfer a discussion](/discussions/managing-discussions-for-your-community/managing-discussions) to a new repository| | | **✔️** | **✔️** | **✔️** | +| [Manage pinned discussions](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Convert issues to discussions in bulk](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Lock and unlock discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Individually convert issues to discussions](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Create new discussions and comment on existing discussions](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Delete a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Create [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** |{% endif %} ### Access requirements for security features @@ -153,18 +153,18 @@ In this section, you can find the access required for security features, such as | Repository action | Read | Triage | Write | Maintain | Admin | |:---|:---:|:---:|:---:|:---:|:---:| -| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **X** | -| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** |{% endif %} -| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} -| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **X** |{% endif %} +| Receive [{% data variables.product.prodname_dependabot_alerts %} for insecure dependencies](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) in a repository | | | | | **✔️** | +| [Dismiss {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Designate additional people or teams to receive security alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Create [security advisories](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| Manage access to {% data variables.product.prodname_GH_advanced_security %} features (see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [Enable the dependency graph](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) for a private repository | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [View dependency reviews](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% endif %} +| [View {% data variables.product.prodname_code_scanning %} alerts on pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [List, dismiss, and delete {% data variables.product.prodname_code_scanning %} alerts](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [View {% data variables.product.prodname_secret_scanning %} alerts in a repository](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} +| [Resolve, revoke, or re-open {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designate additional people or teams to receive {% data variables.product.prodname_secret_scanning %} alerts](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) in repositories | | | | | **✔️** |{% endif %} [1] Repository writers and maintainers can only see alert information for their own commits. From 6cdc31d2a7f808caff3298800fd91d0d6642bbee Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Thu, 4 Aug 2022 11:11:09 +0200 Subject: [PATCH 14/41] clarifies availability of math, mermaid, etc --- .../documenting-your-project-with-wikis/about-wikis.md | 4 +++- .../editing-wiki-content.md | 5 +++++ .../working-with-advanced-formatting/creating-diagrams.md | 2 +- .../writing-mathematical-expressions.md | 4 ++++ data/reusables/getting-started/available-throughout.md | 1 + data/reusables/getting-started/math-and-diagrams.md | 1 + 6 files changed, 15 insertions(+), 2 deletions(-) create mode 100644 data/reusables/getting-started/available-throughout.md create mode 100644 data/reusables/getting-started/math-and-diagrams.md diff --git a/content/communities/documenting-your-project-with-wikis/about-wikis.md b/content/communities/documenting-your-project-with-wikis/about-wikis.md index c9ab964dbd..d270e7ba51 100644 --- a/content/communities/documenting-your-project-with-wikis/about-wikis.md +++ b/content/communities/documenting-your-project-with-wikis/about-wikis.md @@ -17,7 +17,9 @@ topics: Every repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} comes equipped with a section for hosting documentation, called a wiki. You can use your repository's wiki to share long-form content about your project, such as how to use it, how you designed it, or its core principles. A README file quickly tells what your project can do, while you can use a wiki to provide additional documentation. For more information, see "[About READMEs](/articles/about-readmes)." -With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. +With wikis, you can write content just like everywhere else on {% data variables.product.product_name %}. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/getting-started-with-writing-and-formatting-on-github)." We use [our open-source Markup library](https://github.com/github/markup) to convert different formats into HTML, so you can choose to write in Markdown or any other supported format. + +{% data reusables.getting-started.math-and-diagrams %} {% ifversion fpt or ghes or ghec %}If you create a wiki in a public repository, the wiki is available to {% ifversion ghes %}anyone with access to {% data variables.product.product_location %}{% else %}the public{% endif %}. {% endif %}If you create a wiki in a private{% ifversion ghec or ghes %} or internal{% endif %} repository, only {% ifversion fpt or ghes or ghec %}people{% elsif ghae %}enterprise members{% endif %} with access to the repository can access the wiki. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)." diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index 95fb65a300..a1b8206e12 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,6 +46,11 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] +{% ifversion math %} +## Adding mathematical expressions{% ifversion mermaid %} and diagrams{% endif %}{% endif %} + +{% data reusables.getting-started.math-and-diagrams %} + ## Supported MediaWiki formats No matter which markup language your wiki page is written in, certain MediaWiki syntax will always be available to you. diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index 8d0b98c315..bcd9ed27f2 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -8,7 +8,7 @@ shortTitle: Create diagrams ## About creating diagrams -You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. +You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. Diagram rendering is {% data reusables.getting-started.available-throughout %} ## Creating Mermaid diagrams diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 443ac80528..20360675b3 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -6,10 +6,14 @@ versions: shortTitle: Mathematical expressions --- +## About writing mathematical expressions + To enable clear communication of mathematical expressions, {% data variables.product.product_name %} supports LaTeX formatted math within Markdown. For more information, see [LaTeX/Mathematics](http://en.wikibooks.org/wiki/LaTeX/Mathematics) in Wikibooks. {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). +Mathematical expressions rendering is {% data reusables.getting-started.available-throughout %} + ## Writing inline expressions To include a math expression inline with your text, delimit the expression with a dollar symbol `$`. diff --git a/data/reusables/getting-started/available-throughout.md b/data/reusables/getting-started/available-throughout.md new file mode 100644 index 0000000000..3133e543e6 --- /dev/null +++ b/data/reusables/getting-started/available-throughout.md @@ -0,0 +1 @@ +available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, Markdown files, and wikis. diff --git a/data/reusables/getting-started/math-and-diagrams.md b/data/reusables/getting-started/math-and-diagrams.md new file mode 100644 index 0000000000..12f17c6856 --- /dev/null +++ b/data/reusables/getting-started/math-and-diagrams.md @@ -0,0 +1 @@ +{% ifversion math %}You can use Markdown to add rendered math expressions{% ifversion mermaid %}, diagrams, maps, and 3D models{% endif %} to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)."{% ifversion mermaid %} For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %}{% endif %} \ No newline at end of file From 475e4fa28ece8c1f23fa01d16199e9b7af95d46a Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Thu, 4 Aug 2022 11:44:54 +0200 Subject: [PATCH 15/41] fix versioning --- .../editing-wiki-content.md | 4 ++-- .../working-with-advanced-formatting/creating-diagrams.md | 2 +- .../writing-mathematical-expressions.md | 2 +- data/reusables/getting-started/available-throughout.md | 1 - data/reusables/getting-started/math-and-diagrams.md | 2 +- 5 files changed, 5 insertions(+), 6 deletions(-) delete mode 100644 data/reusables/getting-started/available-throughout.md diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index a1b8206e12..f496dcf094 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,8 +46,8 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] -{% ifversion math %} -## Adding mathematical expressions{% ifversion mermaid %} and diagrams{% endif %}{% endif %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %} +## Adding mathematical expressions and diagrams{% endif %} {% data reusables.getting-started.math-and-diagrams %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index bcd9ed27f2..4b690277a2 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -8,7 +8,7 @@ shortTitle: Create diagrams ## About creating diagrams -You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. Diagram rendering is {% data reusables.getting-started.available-throughout %} +You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. Diagram rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, wikis, and Markdown files. ## Creating Mermaid diagrams diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 20360675b3..2a01789396 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -12,7 +12,7 @@ To enable clear communication of mathematical expressions, {% data variables.pro {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). -Mathematical expressions rendering is {% data reusables.getting-started.available-throughout %} +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}wikis, {% endif %}and Markdown files. ## Writing inline expressions diff --git a/data/reusables/getting-started/available-throughout.md b/data/reusables/getting-started/available-throughout.md deleted file mode 100644 index 3133e543e6..0000000000 --- a/data/reusables/getting-started/available-throughout.md +++ /dev/null @@ -1 +0,0 @@ -available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, Markdown files, and wikis. diff --git a/data/reusables/getting-started/math-and-diagrams.md b/data/reusables/getting-started/math-and-diagrams.md index 12f17c6856..0b8fd102b4 100644 --- a/data/reusables/getting-started/math-and-diagrams.md +++ b/data/reusables/getting-started/math-and-diagrams.md @@ -1 +1 @@ -{% ifversion math %}You can use Markdown to add rendered math expressions{% ifversion mermaid %}, diagrams, maps, and 3D models{% endif %} to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)."{% ifversion mermaid %} For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %}{% endif %} \ No newline at end of file +{% ifversion mermaid %}You can use Markdown to add rendered math expressions, diagrams, maps, and 3D models to your wiki. For more information on creating rendered math expressions, see "[Writing mathematical expressions](/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions)." For more information on creating diagrams, maps and 3D models, see "[Creating diagrams](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)."{% endif %} \ No newline at end of file From 53c24149555d97f182131e27ee13b699db50f063 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Thu, 4 Aug 2022 12:09:35 +0200 Subject: [PATCH 16/41] fix versioning --- .../documenting-your-project-with-wikis/editing-wiki-content.md | 2 +- .../writing-mathematical-expressions.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index f496dcf094..b37efa2281 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,7 +46,7 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] -{% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae %} ## Adding mathematical expressions and diagrams{% endif %} {% data reusables.getting-started.math-and-diagrams %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 2a01789396..8a118c0e7a 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -12,7 +12,7 @@ To enable clear communication of mathematical expressions, {% data variables.pro {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). -Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}wikis, {% endif %}and Markdown files. +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae %}wikis, {% endif %}and Markdown files. ## Writing inline expressions From 85cab1bdc883b38d2d59075b95602cec20c3471e Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Fri, 5 Aug 2022 17:06:51 -0700 Subject: [PATCH 17/41] Document that using a wildcard DNS record is incompatible with domain verification --- .../verifying-your-custom-domain-for-github-pages.md | 6 ++++-- data/reusables/pages/wildcard-dns-warning.md | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index 6c0cb23014..5b5dac7385 100644 --- a/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -18,6 +18,8 @@ Verifying your domain stops other GitHub users from taking over your custom doma When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers. +{% data reusables.pages.wildcard-dns-warning %} + It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}." ## Verifying a domain for your user site @@ -28,7 +30,7 @@ It's also possible to verify a domain for your organization{% ifversion ghec %} 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} ## Verifying a domain for your organization site @@ -42,5 +44,5 @@ Organization owners can verify custom domains for their organization. 1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. ``` dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT - ``` + ``` {% data reusables.pages.settings-verify-domain-confirm %} diff --git a/data/reusables/pages/wildcard-dns-warning.md b/data/reusables/pages/wildcard-dns-warning.md index 468c509c00..8978c322e4 100644 --- a/data/reusables/pages/wildcard-dns-warning.md +++ b/data/reusables/pages/wildcard-dns-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains. +**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are [verified](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages). {% endwarning %} From 8e0164fe2a75ccedf569573432d0373656a7e44f Mon Sep 17 00:00:00 2001 From: Ritesh Ganjewala <42371840+InvincibleZeal@users.noreply.github.com> Date: Sun, 7 Aug 2022 18:30:32 +0530 Subject: [PATCH 18/41] doc(search-repository): add search by size to link text as per example --- .../searching-on-github/searching-for-repositories.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/search-github/searching-on-github/searching-for-repositories.md b/content/search-github/searching-on-github/searching-for-repositories.md index ae86c3967b..243e2b9651 100644 --- a/content/search-github/searching-on-github/searching-for-repositories.md +++ b/content/search-github/searching-on-github/searching-for-repositories.md @@ -90,7 +90,7 @@ You can search repositories based on the number of stars the repositories have, | Qualifier | Example | ------------- | ------------- | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) matches repositories with exactly 500 stars. -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) matches repositories with the at least 500 stars, including forked ones, that are written in PHP. ## Search by when a repository was created or last updated From a5d9cb44d9922eb5be7e5131fb35549f9fd78550 Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Mon, 8 Aug 2022 08:40:12 +0200 Subject: [PATCH 19/41] fix versioning --- .../documenting-your-project-with-wikis/editing-wiki-content.md | 2 +- .../writing-mathematical-expressions.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index b37efa2281..a1e4a89466 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,7 +46,7 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] -{% ifversion fpt or ghec or ghes > 3.6 or ghae %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-6054 %} ## Adding mathematical expressions and diagrams{% endif %} {% data reusables.getting-started.math-and-diagrams %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index 8a118c0e7a..d63aa3736d 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -12,7 +12,7 @@ To enable clear communication of mathematical expressions, {% data variables.pro {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). -Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae %}wikis, {% endif %}and Markdown files. +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-6054 %}wikis, {% endif %}and Markdown files. ## Writing inline expressions From 74edd43f0f20af98c8a1a322628f8ce0a4e2ddbb Mon Sep 17 00:00:00 2001 From: Jules Parker <19994093+jules-p@users.noreply.github.com> Date: Mon, 8 Aug 2022 10:17:59 +0200 Subject: [PATCH 20/41] fix versioning --- .../documenting-your-project-with-wikis/editing-wiki-content.md | 2 +- .../writing-mathematical-expressions.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md index a1e4a89466..32dcbdc4b5 100644 --- a/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md +++ b/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md @@ -46,7 +46,7 @@ You can link to an image in a repository on {% data variables.product.product_na [[https://github.com/USERNAME/REPOSITORY/blob/main/img/octocat.png|alt=octocat]] -{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-6054 %} +{% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %} ## Adding mathematical expressions and diagrams{% endif %} {% data reusables.getting-started.math-and-diagrams %} diff --git a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md index d63aa3736d..94b2e2bec0 100644 --- a/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md +++ b/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md @@ -12,7 +12,7 @@ To enable clear communication of mathematical expressions, {% data variables.pro {% data variables.product.company_short %}'s math rendering capability uses MathJax; an open source, JavaScript-based display engine. MathJax supports a wide range of LaTeX macros, and several useful accessibility extensions. For more information, see [the MathJax documentation](http://docs.mathjax.org/en/latest/input/tex/index.html#tex-and-latex-support) and [the MathJax Accessibility Extensions Documentation](https://mathjax.github.io/MathJax-a11y/docs/#reader-guide). -Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-6054 %}wikis, {% endif %}and Markdown files. +Mathematical expressions rendering is available in {% data variables.product.prodname_github_issues %}, {% data variables.product.prodname_discussions %}, pull requests, {% ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7647 %}wikis, {% endif %}and Markdown files. ## Writing inline expressions From cd4731972867e5ecd21cf97f105c7948384b4000 Mon Sep 17 00:00:00 2001 From: github-openapi-bot Date: Mon, 8 Aug 2022 12:50:51 -0700 Subject: [PATCH 21/41] Update OpenAPI Descriptions --- .../dereferenced/api.github.com.deref.json | 54 +++++++++++++++-- .../static/dereferenced/ghes-3.2.deref.json | 60 +++++++++++++++++-- .../static/dereferenced/ghes-3.3.deref.json | 60 +++++++++++++++++-- .../static/dereferenced/ghes-3.4.deref.json | 60 +++++++++++++++++-- .../static/dereferenced/ghes-3.5.deref.json | 60 +++++++++++++++++-- .../static/dereferenced/ghes-3.6.deref.json | 60 +++++++++++++++++-- .../static/dereferenced/github.ae.deref.json | 60 +++++++++++++++++-- 7 files changed, 372 insertions(+), 42 deletions(-) diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json index 433fedb97e..92403a170e 100644 --- a/lib/rest/static/dereferenced/api.github.com.deref.json +++ b/lib/rest/static/dereferenced/api.github.com.deref.json @@ -377322,6 +377322,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -377345,7 +377357,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -377466,6 +377480,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -377487,7 +377513,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -377657,6 +377685,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -377678,7 +377718,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -431268,7 +431310,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -431323,7 +431365,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -434309,7 +434351,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json index 3689b58aaa..9e5135fa54 100644 --- a/lib/rest/static/dereferenced/ghes-3.2.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json @@ -1268,6 +1268,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -323028,6 +323034,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -323051,7 +323069,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -323172,6 +323192,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -323193,7 +323225,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -323363,6 +323397,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -323384,7 +323430,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -370277,7 +370325,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -370332,7 +370380,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.2/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -373318,7 +373366,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.2/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json index 99a04bfbdf..4cb2fa7891 100644 --- a/lib/rest/static/dereferenced/ghes-3.3.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json @@ -1200,6 +1200,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -325217,6 +325223,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -325240,7 +325258,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -325361,6 +325381,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -325382,7 +325414,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -325552,6 +325586,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -325573,7 +325619,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -372649,7 +372697,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.3/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -372704,7 +372752,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.3/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -375690,7 +375738,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.3/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.4.deref.json b/lib/rest/static/dereferenced/ghes-3.4.deref.json index d663f29c0a..2db5a8655d 100644 --- a/lib/rest/static/dereferenced/ghes-3.4.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.4.deref.json @@ -1200,6 +1200,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -341765,6 +341771,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -341788,7 +341806,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -341909,6 +341929,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -341930,7 +341962,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -342100,6 +342134,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -342121,7 +342167,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -389197,7 +389245,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.4/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.4/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.4/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -389252,7 +389300,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.4/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -392238,7 +392286,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.4/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.5.deref.json b/lib/rest/static/dereferenced/ghes-3.5.deref.json index 0b45eee24f..4bddbbaa0b 100644 --- a/lib/rest/static/dereferenced/ghes-3.5.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.5.deref.json @@ -1200,6 +1200,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -351898,6 +351904,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -351921,7 +351939,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -352042,6 +352062,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -352063,7 +352095,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -352233,6 +352267,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -352254,7 +352300,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -399336,7 +399384,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.5/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.5/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.5/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -399391,7 +399439,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.5/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -402377,7 +402425,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.5/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/ghes-3.6.deref.json b/lib/rest/static/dereferenced/ghes-3.6.deref.json index 2e3f5bbf4c..d9789cd36e 100644 --- a/lib/rest/static/dereferenced/ghes-3.6.deref.json +++ b/lib/rest/static/dereferenced/ghes-3.6.deref.json @@ -1200,6 +1200,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -353784,6 +353790,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -353807,7 +353825,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -353928,6 +353948,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -353949,7 +353981,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -354119,6 +354153,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -354140,7 +354186,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -401278,7 +401326,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.6/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.6/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/enterprise-server@3.6/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -401333,7 +401381,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.6/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -404319,7 +404367,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/enterprise-server@3.6/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json index 6edcdd9bff..717dd25b5b 100644 --- a/lib/rest/static/dereferenced/github.ae.deref.json +++ b/lib/rest/static/dereferenced/github.ae.deref.json @@ -1196,6 +1196,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -309889,6 +309895,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -309912,7 +309930,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ] } @@ -310033,6 +310053,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -310054,7 +310086,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -310224,6 +310258,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -310245,7 +310291,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } } } @@ -356937,7 +356985,7 @@ }, "post": { "summary": "Create a review for a pull request", - "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state do not include the `submitted_at` property in the response.\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/github-ae@latest/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", + "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.\n\nPull request reviews created in the `PENDING` state are not submitted and therefore do not include the `submitted_at` property in the response. To create a pending review for a pull request, leave the `event` parameter blank. For more information about submitting a `PENDING` review, see \"[Submit a review for a pull request](https://docs.github.com/github-ae@latest/rest/pulls#submit-a-review-for-a-pull-request).\"\n\n**Note:** To comment on a specific line in a file, you need to first determine the _position_ of that line in the diff. The GitHub REST API v3 offers the `application/vnd.github.v3.diff` [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types#commits-commit-comparison-and-pull-requests). To see a pull request diff, add this media type to the `Accept` header of a call to the [single pull request](https://docs.github.com/github-ae@latest/rest/reference/pulls#get-a-pull-request) endpoint.\n\nThe `position` value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.", "tags": [ "pulls" ], @@ -356992,7 +357040,7 @@ }, "event": { "type": "string", - "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/github-ae@latest/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "description": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/github-ae@latest/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -359978,7 +360026,7 @@ "/repos/{owner}/{repo}/pulls/{pull_number}/reviews/{review_id}/events": { "post": { "summary": "Submit a review for a pull request", - "description": "", + "description": "Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"[Create a review for a pull request](https://docs.github.com/github-ae@latest/rest/pulls#create-a-review-for-a-pull-request).\"", "tags": [ "pulls" ], From 840abe1004c0a7e6ac7ebc58e1d41399268b3a13 Mon Sep 17 00:00:00 2001 From: github-openapi-bot Date: Mon, 8 Aug 2022 20:01:28 +0000 Subject: [PATCH 22/41] Add decorated OpenAPI schema files --- lib/rest/static/decorated/api.github.com.json | 56 ++++++++++++++--- lib/rest/static/decorated/ghes-3.2.json | 62 ++++++++++++++++--- lib/rest/static/decorated/ghes-3.3.json | 62 ++++++++++++++++--- lib/rest/static/decorated/ghes-3.4.json | 62 ++++++++++++++++--- lib/rest/static/decorated/ghes-3.5.json | 62 ++++++++++++++++--- lib/rest/static/decorated/ghes-3.6.json | 62 ++++++++++++++++--- lib/rest/static/decorated/github.ae.json | 62 ++++++++++++++++--- 7 files changed, 379 insertions(+), 49 deletions(-) diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json index 26a6245615..e2908a32de 100644 --- a/lib/rest/static/decorated/api.github.com.json +++ b/lib/rest/static/decorated/api.github.com.json @@ -261791,7 +261791,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -261821,6 +261823,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -261934,7 +261948,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -261961,6 +261977,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -262050,7 +262078,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -262077,6 +262107,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -458422,7 +458464,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -458431,7 +458473,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -458985,7 +459027,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -461766,8 +461808,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json index 69a80e0a42..3360e2f711 100644 --- a/lib/rest/static/decorated/ghes-3.2.json +++ b/lib/rest/static/decorated/ghes-3.2.json @@ -186897,7 +186897,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -186927,6 +186929,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -187040,7 +187054,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -187067,6 +187083,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -187156,7 +187184,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -187183,6 +187213,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -203129,6 +203171,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -355702,7 +355750,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -355711,7 +355759,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.2/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.2/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -356265,7 +356313,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -359046,8 +359094,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json index fce632fa85..b8cff72547 100644 --- a/lib/rest/static/decorated/ghes-3.3.json +++ b/lib/rest/static/decorated/ghes-3.3.json @@ -187710,7 +187710,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -187740,6 +187742,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -187853,7 +187867,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -187880,6 +187896,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -187969,7 +187997,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -187996,6 +188026,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -204241,6 +204283,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -357303,7 +357351,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -357312,7 +357360,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.3/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.3/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -357866,7 +357914,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -360647,8 +360695,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.4.json b/lib/rest/static/decorated/ghes-3.4.json index 9f1ea0f741..a690133aa6 100644 --- a/lib/rest/static/decorated/ghes-3.4.json +++ b/lib/rest/static/decorated/ghes-3.4.json @@ -195509,7 +195509,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -195539,6 +195541,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -195652,7 +195666,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -195679,6 +195695,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -195768,7 +195796,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -195795,6 +195825,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -212220,6 +212262,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -377284,7 +377332,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -377293,7 +377341,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.4/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.4/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -377847,7 +377895,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -380628,8 +380676,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.5.json b/lib/rest/static/decorated/ghes-3.5.json index 7d7f896a9b..4c6d9d9ab5 100644 --- a/lib/rest/static/decorated/ghes-3.5.json +++ b/lib/rest/static/decorated/ghes-3.5.json @@ -205500,7 +205500,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -205530,6 +205532,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -205643,7 +205657,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -205670,6 +205686,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -205759,7 +205787,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -205786,6 +205816,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -222211,6 +222253,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -387281,7 +387329,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -387290,7 +387338,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.5/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.5/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -387844,7 +387892,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -390625,8 +390673,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/ghes-3.6.json b/lib/rest/static/decorated/ghes-3.6.json index 03c2d6ea85..ab4cfa260a 100644 --- a/lib/rest/static/decorated/ghes-3.6.json +++ b/lib/rest/static/decorated/ghes-3.6.json @@ -206778,7 +206778,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -206808,6 +206810,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -206921,7 +206935,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -206948,6 +206964,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -207037,7 +207065,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -207064,6 +207094,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -223489,6 +223531,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -388751,7 +388799,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -388760,7 +388808,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.6/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/enterprise-server@3.6/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -389314,7 +389362,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -392095,8 +392143,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json index 52937956f0..0838a2aad2 100644 --- a/lib/rest/static/decorated/github.ae.json +++ b/lib/rest/static/decorated/github.ae.json @@ -164145,7 +164145,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" } ], "schema": { @@ -164175,6 +164177,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -164288,7 +164302,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -164315,6 +164331,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -164404,7 +164432,9 @@ "title": "octocat@octomac", "verified": true, "created_at": "2014-12-10T15:53:42Z", - "read_only": true + "read_only": true, + "added_by": "octocat", + "last_used": "2022-01-10T15:53:42Z" }, "schema": { "title": "Deploy Key", @@ -164431,6 +164461,18 @@ }, "read_only": { "type": "boolean" + }, + "added_by": { + "type": [ + "string", + "null" + ] + }, + "last_used": { + "type": [ + "string", + "null" + ] } }, "required": [ @@ -178105,6 +178147,12 @@ "type": "string", "format": "date-time" }, + "added_by": { + "type": [ + "string", + "null" + ] + }, "last_used": { "type": [ "string", @@ -334675,7 +334723,7 @@ }, { "type": "string", - "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", + "description": "

The review action you want to perform. The review actions include: APPROVE, REQUEST_CHANGES, or COMMENT. By leaving this blank, you set the review action state to PENDING, which means you will need to submit the pull request review when you are ready.

", "enum": [ "APPROVE", "REQUEST_CHANGES", @@ -334684,7 +334732,7 @@ "name": "event", "in": "body", "rawType": "string", - "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/github-ae@latest/rest/reference/pulls#submit-a-review-for-a-pull-request) when you are ready.", + "rawDescription": "The review action you want to perform. The review actions include: `APPROVE`, `REQUEST_CHANGES`, or `COMMENT`. By leaving this blank, you set the review action state to `PENDING`, which means you will need to [submit the pull request review](https://docs.github.com/github-ae@latest/rest/pulls#submit-a-review-for-a-pull-request) when you are ready.", "isRequired": false, "childParamsGroups": [] }, @@ -335238,7 +335286,7 @@ } ], "previews": [], - "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state do not include the submitted_at property in the response.

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", + "descriptionHTML": "

This endpoint triggers notifications. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"Secondary rate limits\" and \"Dealing with secondary rate limits\" for details.

\n

Pull request reviews created in the PENDING state are not submitted and therefore do not include the submitted_at property in the response. To create a pending review for a pull request, leave the event parameter blank. For more information about submitting a PENDING review, see \"Submit a review for a pull request.\"

\n

Note: To comment on a specific line in a file, you need to first determine the position of that line in the diff. The GitHub REST API v3 offers the application/vnd.github.v3.diff media type. To see a pull request diff, add this media type to the Accept header of a call to the single pull request endpoint.

\n

The position value equals the number of lines down from the first \"@@\" hunk header in the file you want to add a comment. The line just below the \"@@\" line is position 1, the next line is position 2, and so on. The position in the diff continues to increase through lines of whitespace and additional hunks until the beginning of a new file.

", "statusCodes": [ { "httpStatusCode": "200", @@ -338019,8 +338067,8 @@ } } ], - "descriptionHTML": "", "previews": [], + "descriptionHTML": "

Submits a pending review for a pull request. For more information about creating a pending review for a pull request, see \"Create a review for a pull request.\"

", "statusCodes": [ { "httpStatusCode": "200", From 2e7b951d1737e8462233fd28024e40da694acde3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rapha=C3=ABl=20Larivi=C3=A8re?= <54908935+Sylfwood@users.noreply.github.com> Date: Mon, 8 Aug 2022 16:38:12 -0400 Subject: [PATCH 23/41] fixed typo on about-authentication-with-saml-single-sign-on.md file --- .../about-authentication-with-saml-single-sign-on.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 3caa475045..f93239d387 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -44,7 +44,7 @@ When you authenticate with your IdP account and return to {% data variables.prod If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. For more information, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)." -If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll recieve a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. ## Authorizing PATs and SSH keys with SAML SSO From 4d24a40d08696608d77186bacc3e63a2659072e9 Mon Sep 17 00:00:00 2001 From: Orhan Toy Date: Tue, 9 Aug 2022 11:40:43 +0200 Subject: [PATCH 24/41] Fix typo: updatng -> updating (#29726) Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> --- .../dependabot/dependabot-alerts/about-dependabot-alerts.md | 4 ++-- ...roubleshooting-the-detection-of-vulnerable-dependencies.md | 2 +- .../getting-started/securing-your-organization.md | 2 +- .../code-security/getting-started/securing-your-repository.md | 2 +- .../exploring-the-dependencies-of-a-repository.md | 2 +- .../managing-data-use-settings-for-your-private-repository.md | 2 +- 6 files changed, 7 insertions(+), 7 deletions(-) diff --git a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index c900d9dfe1..5bbb673719 100644 --- a/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -88,7 +88,7 @@ For repositories where {% data variables.product.prodname_dependabot_security_up ## Access to {% data variables.product.prodname_dependabot_alerts %} -You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} @@ -102,5 +102,5 @@ You can also see all the {% data variables.product.prodname_dependabot_alerts %} ## Further reading - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index b94ae151ca..0344ac5067 100644 --- a/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe ## Further reading - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/content/code-security/getting-started/securing-your-organization.md b/content/code-security/getting-started/securing-your-organization.md index 155ef044ab..e560122037 100644 --- a/content/code-security/getting-started/securing-your-organization.md +++ b/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/content/code-security/getting-started/securing-your-repository.md b/content/code-security/getting-started/securing-your-repository.md index 9d2fbc8235..ec95d618b2 100644 --- a/content/code-security/getting-started/securing-your-repository.md +++ b/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index fd276a2d28..5984c9c70e 100644 --- a/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -111,7 +111,7 @@ If a manifest or lock file is not processed, its dependencies are omitted from t ## Further reading - "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}{% ifversion fpt or ghec %} - "[Understanding how {% data variables.product.prodname_dotcom %} uses and protects your data](/get-started/privacy-on-github)" {% endif %} diff --git a/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index b8025330c8..3b257f4052 100644 --- a/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -45,5 +45,5 @@ When you enable data use for your private repository, you'll be able to access t ## Further reading - "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" From bd8fe2f2d073ff1baee7c9322cd8511ff52ef168 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Tue, 9 Aug 2022 11:19:05 +0100 Subject: [PATCH 25/41] Enterprise bug fixes for the week of August 1, 2022 (#29661) --- .../about-saml-for-enterprise-iam.md | 2 ++ .../configuring-saml-single-sign-on-for-your-enterprise.md | 6 +++++- content/admin/overview/about-enterprise-accounts.md | 2 +- .../adding-organizations-to-your-enterprise.md | 3 ++- .../about-authentication-with-saml-single-sign-on.md | 4 ++-- ...entity-and-access-management-with-saml-single-sign-on.md | 4 +--- ...creating-and-deleting-branches-within-your-repository.md | 4 ++++ data/features/create-branch-from-overview.yml | 5 +++++ data/reusables/saml/dotcom-saml-explanation.md | 2 +- data/reusables/saml/outside-collaborators-exemption.md | 5 ++++- data/reusables/saml/saml-accounts.md | 6 +++--- 11 files changed, 30 insertions(+), 13 deletions(-) create mode 100644 data/features/create-branch-from-overview.yml diff --git a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 0ad2ac1361..0992bd4192 100644 --- a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." diff --git a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index be095b071c..f62297bd90 100644 --- a/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/content/admin/overview/about-enterprise-accounts.md b/content/admin/overview/about-enterprise-accounts.md index 684e032555..60793424f8 100644 --- a/content/admin/overview/about-enterprise-accounts.md +++ b/content/admin/overview/about-enterprise-accounts.md @@ -35,7 +35,7 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. For more information, see "[Adding organizations to your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)." {% endif %} Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." diff --git a/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 437374e8e5..0e4046bd7f 100644 --- a/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,13 +14,14 @@ topics: - Enterprise - Organizations shortTitle: Add organizations +permissions: Enterprise owners can add organizations to an enterprise. --- ## About organizations Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. +You can add a new or existing organization to your enterprise in your enterprise account's settings. You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." diff --git a/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 3caa475045..dc86c1d0b6 100644 --- a/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: About authentication with SAML single sign-on -intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -30,7 +30,7 @@ If you can't access {% data variables.product.product_name %}, contact your loca If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} -When you access resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to {% data variables.product.prodname_dotcom %}, where you can access the organization's resources. {% data reusables.saml.outside-collaborators-exemption %} diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 5e863a03d9..076f7265e3 100644 --- a/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,14 +12,12 @@ topics: shortTitle: IAM with SAML SSO --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## About SAML SSO {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} Organization owners can enforce SAML SSO for an individual organization, or enterprise owners can enforce SAML SSO for all organizations in an enterprise account. For more information, see "[Configuring SAML single sign-on for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." diff --git a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index f2bc4e9bfd..521d8fef16 100644 --- a/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ You can create a branch in different ways on {% data variables.product.product_n {% endnote %} +{% ifversion create-branch-from-overview %} ### Creating a branch via the branches overview {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -35,6 +36,7 @@ You can create a branch in different ways on {% data variables.product.product_n ![Screenshot of branch creation modal for a fork with branch source emphasized](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. Click **Create branch**. ![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### Creating a branch using the branch dropdown {% data reusables.repositories.navigate-to-repo %} @@ -44,10 +46,12 @@ You can create a branch in different ways on {% data variables.product.product_n ![branch selector menu](/assets/images/help/branch/branch-selection-dropdown.png) 1. Type a unique name for your new branch, then select **Create branch**. ![branch creation text box](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### Creating a branch for an issue You can create a branch to work on an issue directly from the issue page and get started right away. For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)". {% endif %} + ## Deleting a branch {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/data/features/create-branch-from-overview.yml b/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/data/reusables/saml/dotcom-saml-explanation.md b/data/reusables/saml/dotcom-saml-explanation.md index 1193514f50..d8413a8725 100644 --- a/data/reusables/saml/dotcom-saml-explanation.md +++ b/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. \ No newline at end of file diff --git a/data/reusables/saml/outside-collaborators-exemption.md b/data/reusables/saml/outside-collaborators-exemption.md index 29525c7593..c6c2ae1009 100644 --- a/data/reusables/saml/outside-collaborators-exemption.md +++ b/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**Note:** Outside collaborators aren't required to authenticate with an IdP to access the resources in an organization with SAML SSO. For more information on outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +**Notes:** + +- SAML authentication is not required for organization members to perform read operations such as viewing, cloning, and forking of public resources. +- SAML authentication is not required for outside collaborators. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." {% endnote %} diff --git a/data/reusables/saml/saml-accounts.md b/data/reusables/saml/saml-accounts.md index cfb5746ae3..1c176cf358 100644 --- a/data/reusables/saml/saml-accounts.md +++ b/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -If you configure SAML SSO, members of your organization will continue to log into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}, where the member can access your organization's resources. +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. For more information, see "[About authentication with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)." {% note %} -**Note:** Organization members can perform read operations such as viewing, cloning, and forking on public resources owned by your organization even without a valid SAML session. +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file From 16fcaa78690bb99c6d5dc69a86642b49a3d58f2f Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 9 Aug 2022 12:58:08 +0200 Subject: [PATCH 26/41] next@12.2.4 (#29731) * next@12.2.4 * suppress 'Large Page Data' * Update next.config.js Co-authored-by: Rachael Sewell Co-authored-by: Rachael Sewell --- next.config.js | 9 + package-lock.json | 426 ++++++++++++++++++++++++++++++++++++++-------- package.json | 2 +- 3 files changed, 362 insertions(+), 75 deletions(-) diff --git a/next.config.js b/next.config.js index 049527a1f8..e427ea4c61 100644 --- a/next.config.js +++ b/next.config.js @@ -45,4 +45,13 @@ export default { // This causes problems with serving stale content, since upon revalidating // the CDN marks the cached content as "fresh". generateEtags: false, + + experimental: { + // The output of our getServerSideProps() return large chunks of + // data because it contains our rendered Markdown. + // The default, for a "Large Page Data" warning is 128KB + // but many of our pages are much larger. + // The warning is: https://nextjs.org/docs/messages/large-page-data + largePageDataBytes: 1024 * 1024, // 1 MB + }, } diff --git a/package-lock.json b/package-lock.json index a2c7081473..46002fd01f 100644 --- a/package-lock.json +++ b/package-lock.json @@ -54,7 +54,7 @@ "mdast-util-to-string": "^3.1.0", "morgan": "^1.10.0", "msgpack5rpc": "^1.1.0", - "next": "12.1.6", + "next": "12.2.4", "parse5": "7.0.0", "port-used": "^2.0.8", "react": "^17.0.2", @@ -3474,9 +3474,204 @@ } }, "node_modules/@next/env": { - "version": "12.1.6", - "resolved": "https://registry.npmjs.org/@next/env/-/env-12.1.6.tgz", - "integrity": "sha512-Te/OBDXFSodPU6jlXYPAXpmZr/AkG6DCATAxttQxqOWaq6eDFX25Db3dK0120GZrSZmv4QCe9KsZmJKDbWs4OA==" + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/env/-/env-12.2.4.tgz", + "integrity": "sha512-/gApFXWk5CCLFQJL5IYJXxPQuG5tz5nPX4l27A9Zm/+wJxiwFrRSP54AopDxIv4JRp/rGwcgk/lZS/0Clw8jYA==" + }, + "node_modules/@next/swc-android-arm-eabi": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-android-arm-eabi/-/swc-android-arm-eabi-12.2.4.tgz", + "integrity": "sha512-P4YSFNpmXXSnn3P1qsOAqz+MX3On9fHrlc8ovb/CFJJoU+YLCR53iCEwfw39e0IZEgDA7ttgr108plF8mxaX0g==", + "cpu": [ + "arm" + ], + "optional": true, + "os": [ + "android" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-android-arm64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-android-arm64/-/swc-android-arm64-12.2.4.tgz", + "integrity": "sha512-4o2n14E18O+8xHlf6dgJsWPXN9gmSmfIe2Z0EqKDIPBBkFt/2CyrH0+vwHnL2l7xkDHhOGfZYcYIWVUR5aNu0A==", + "cpu": [ + "arm64" + ], + "optional": true, + "os": [ + "android" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-darwin-arm64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-12.2.4.tgz", + "integrity": "sha512-DcUO6MGBL9E3jj5o86MUnTOy4WawIJJhyCcFYO4f51sbl7+uPIYIx40eo98A6NwJEXazCqq1hLeqOaNTAIvDiQ==", + "cpu": [ + "arm64" + ], + "optional": true, + "os": [ + "darwin" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-darwin-x64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-12.2.4.tgz", + "integrity": "sha512-IUlFMqeLjdIzDorrGC2Dt+2Ae3DbKQbRzCzmDq4/CP1+jJGeDXo/2AHnlE+WYnwQAC4KtAz6pbVnd3KstZWsVA==", + "cpu": [ + "x64" + ], + "optional": true, + "os": [ + "darwin" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-freebsd-x64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-freebsd-x64/-/swc-freebsd-x64-12.2.4.tgz", + "integrity": "sha512-475vwyWcjnyDVDWLgAATP0HI8W1rwByc+uXk1B6KkAVFhkoDgH387LW0uNqxavK+VxCzj3avQXX/58XDvxtSlg==", + "cpu": [ + "x64" + ], + "optional": true, + "os": [ + "freebsd" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-linux-arm-gnueabihf": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm-gnueabihf/-/swc-linux-arm-gnueabihf-12.2.4.tgz", + "integrity": "sha512-qZW+L3iG3XSGtlOPmD5RRWXyk6ZNdscLV0BQjuDvP+exTg+uixqHXOHz0/GVATIJEBQOF0Kew7jAXVXEP+iRTQ==", + "cpu": [ + "arm" + ], + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-linux-arm64-gnu": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-12.2.4.tgz", + "integrity": "sha512-fEPRjItWYaKyyG9N+2HIA59OBHIhk7WC+Rh+LwXsh0pQe870Ykpek3KQs0umjsrEGe57NyMomq3f80/N8taDvA==", + "cpu": [ + "arm64" + ], + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-linux-arm64-musl": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-12.2.4.tgz", + "integrity": "sha512-rnCTzXII0EBCcFn9P5s/Dho2kPUMSX/bP0iOAj8wEI/IxUEfEElbin89zJoNW30cycHu19xY8YP4K2+hzciPzQ==", + "cpu": [ + "arm64" + ], + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-linux-x64-gnu": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-12.2.4.tgz", + "integrity": "sha512-PhXX6NSuIuhHInxPY2VkG2Bl7VllsD3Cjx+pQcS1wTym7Zt7UoLvn05PkRrkiyIkvR+UXnqPUM3TYiSbnemXEw==", + "cpu": [ + "x64" + ], + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-linux-x64-musl": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-12.2.4.tgz", + "integrity": "sha512-GmC/QROiUZpFirHRfPQqMyCXZ+5+ndbBZrMvL74HtQB/CKXB8K1VM+rvy9Gp/5OaU8Rxp48IcX79NOfI2LiXlA==", + "cpu": [ + "x64" + ], + "optional": true, + "os": [ + "linux" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-win32-arm64-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-12.2.4.tgz", + "integrity": "sha512-9XKoCXbNZuaMRPtcKQz3+hgVpkMosaLlcxHFXT8/j4w61k7/qvEbrkMDS9WHNrD/xVcLycwhPRgXcns2K1BdBQ==", + "cpu": [ + "arm64" + ], + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-win32-ia32-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-ia32-msvc/-/swc-win32-ia32-msvc-12.2.4.tgz", + "integrity": "sha512-hEyRieZKH9iw4AzvXaQ+Fyb98k0G/o9QcRGxA1/O/O/elf1+Qvuwb15phT8GbVtIeNziy66XTPOhKKfdr8KyUg==", + "cpu": [ + "ia32" + ], + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">= 10" + } + }, + "node_modules/@next/swc-win32-x64-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-12.2.4.tgz", + "integrity": "sha512-5Pl1tdMJWLy4rvzU1ecx0nHWgDPqoYuvYoXE/5X0Clu9si/yOuBIj573F2kOTY7mu0LX2wgCJVSnyK0abHBxIw==", + "cpu": [ + "x64" + ], + "optional": true, + "os": [ + "win32" + ], + "engines": { + "node": ">= 10" + } }, "node_modules/@nodelib/fs.scandir": { "version": "2.1.5", @@ -3879,6 +4074,14 @@ "@styled-system/css": "^5.1.5" } }, + "node_modules/@swc/helpers": { + "version": "0.4.3", + "resolved": "https://registry.npmjs.org/@swc/helpers/-/helpers-0.4.3.tgz", + "integrity": "sha512-6JrF+fdUK2zbGpJIlN7G3v966PQjyx/dPt1T9km2wj+EUBqgrxCk3uX4Kct16MIm9gGxfKRcfax2hVf5jvlTzA==", + "dependencies": { + "tslib": "^2.4.0" + } + }, "node_modules/@szmarczak/http-timer": { "version": "4.0.6", "dev": true, @@ -15041,14 +15244,16 @@ "peer": true }, "node_modules/next": { - "version": "12.1.6", - "resolved": "https://registry.npmjs.org/next/-/next-12.1.6.tgz", - "integrity": "sha512-cebwKxL3/DhNKfg9tPZDQmbRKjueqykHHbgaoG4VBRH3AHQJ2HO0dbKFiS1hPhe1/qgc2d/hFeadsbPicmLD+A==", + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/next/-/next-12.2.4.tgz", + "integrity": "sha512-b1xlxEozmAWokAXzXsi5vlmU/IfJcFNIJA8dpU5UdkFbyDPio8wwb8mAQ/Y7rGtfTgG/t/u49BiyEA+xAgFvow==", "dependencies": { - "@next/env": "12.1.6", + "@next/env": "12.2.4", + "@swc/helpers": "0.4.3", "caniuse-lite": "^1.0.30001332", - "postcss": "8.4.5", - "styled-jsx": "5.0.2" + "postcss": "8.4.14", + "styled-jsx": "5.0.2", + "use-sync-external-store": "1.2.0" }, "bin": { "next": "dist/bin/next" @@ -15057,18 +15262,19 @@ "node": ">=12.22.0" }, "optionalDependencies": { - "@next/swc-android-arm-eabi": "12.1.6", - "@next/swc-android-arm64": "12.1.6", - "@next/swc-darwin-arm64": "12.1.6", - "@next/swc-darwin-x64": "12.1.6", - "@next/swc-linux-arm-gnueabihf": "12.1.6", - "@next/swc-linux-arm64-gnu": "12.1.6", - "@next/swc-linux-arm64-musl": "12.1.6", - "@next/swc-linux-x64-gnu": "12.1.6", - "@next/swc-linux-x64-musl": "12.1.6", - "@next/swc-win32-arm64-msvc": "12.1.6", - "@next/swc-win32-ia32-msvc": "12.1.6", - "@next/swc-win32-x64-msvc": "12.1.6" + "@next/swc-android-arm-eabi": "12.2.4", + "@next/swc-android-arm64": "12.2.4", + "@next/swc-darwin-arm64": "12.2.4", + "@next/swc-darwin-x64": "12.2.4", + "@next/swc-freebsd-x64": "12.2.4", + "@next/swc-linux-arm-gnueabihf": "12.2.4", + "@next/swc-linux-arm64-gnu": "12.2.4", + "@next/swc-linux-arm64-musl": "12.2.4", + "@next/swc-linux-x64-gnu": "12.2.4", + "@next/swc-linux-x64-musl": "12.2.4", + "@next/swc-win32-arm64-msvc": "12.2.4", + "@next/swc-win32-ia32-msvc": "12.2.4", + "@next/swc-win32-x64-msvc": "12.2.4" }, "peerDependencies": { "fibers": ">= 3.1.0", @@ -15089,23 +15295,6 @@ } } }, - "node_modules/next/node_modules/postcss": { - "version": "8.4.5", - "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.5.tgz", - "integrity": "sha512-jBDboWM8qpaqwkMwItqTQTiFikhs/67OYVvblFFTM7MrZjt6yMKd6r2kgXizEbTTljacm4NldIlZnhbjr84QYg==", - "dependencies": { - "nanoid": "^3.1.30", - "picocolors": "^1.0.0", - "source-map-js": "^1.0.1" - }, - "engines": { - "node": "^10 || ^12 || >=14" - }, - "funding": { - "type": "opencollective", - "url": "https://opencollective.com/postcss/" - } - }, "node_modules/no-case": { "version": "3.0.4", "dev": true, @@ -16091,7 +16280,6 @@ "version": "8.4.14", "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.14.tgz", "integrity": "sha512-E398TUmfAYFPBSdzgeieK2Y1+1cpdxJx8yXbK/m57nRhKSmk1GB2tO4lbLBtlkfPQTDKfe4Xqv1ASWPpayPEig==", - "dev": true, "funding": [ { "type": "opencollective", @@ -19777,6 +19965,14 @@ "node": "^12.20.0 || ^14.13.1 || >=16.0.0" } }, + "node_modules/use-sync-external-store": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/use-sync-external-store/-/use-sync-external-store-1.2.0.tgz", + "integrity": "sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA==", + "peerDependencies": { + "react": "^16.8.0 || ^17.0.0 || ^18.0.0" + } + }, "node_modules/utf8-byte-length": { "version": "1.0.4", "resolved": "https://registry.npmjs.org/utf8-byte-length/-/utf8-byte-length-1.0.4.tgz", @@ -22996,9 +23192,87 @@ } }, "@next/env": { - "version": "12.1.6", - "resolved": "https://registry.npmjs.org/@next/env/-/env-12.1.6.tgz", - "integrity": "sha512-Te/OBDXFSodPU6jlXYPAXpmZr/AkG6DCATAxttQxqOWaq6eDFX25Db3dK0120GZrSZmv4QCe9KsZmJKDbWs4OA==" + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/env/-/env-12.2.4.tgz", + "integrity": "sha512-/gApFXWk5CCLFQJL5IYJXxPQuG5tz5nPX4l27A9Zm/+wJxiwFrRSP54AopDxIv4JRp/rGwcgk/lZS/0Clw8jYA==" + }, + "@next/swc-android-arm-eabi": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-android-arm-eabi/-/swc-android-arm-eabi-12.2.4.tgz", + "integrity": "sha512-P4YSFNpmXXSnn3P1qsOAqz+MX3On9fHrlc8ovb/CFJJoU+YLCR53iCEwfw39e0IZEgDA7ttgr108plF8mxaX0g==", + "optional": true + }, + "@next/swc-android-arm64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-android-arm64/-/swc-android-arm64-12.2.4.tgz", + "integrity": "sha512-4o2n14E18O+8xHlf6dgJsWPXN9gmSmfIe2Z0EqKDIPBBkFt/2CyrH0+vwHnL2l7xkDHhOGfZYcYIWVUR5aNu0A==", + "optional": true + }, + "@next/swc-darwin-arm64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-arm64/-/swc-darwin-arm64-12.2.4.tgz", + "integrity": "sha512-DcUO6MGBL9E3jj5o86MUnTOy4WawIJJhyCcFYO4f51sbl7+uPIYIx40eo98A6NwJEXazCqq1hLeqOaNTAIvDiQ==", + "optional": true + }, + "@next/swc-darwin-x64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-darwin-x64/-/swc-darwin-x64-12.2.4.tgz", + "integrity": "sha512-IUlFMqeLjdIzDorrGC2Dt+2Ae3DbKQbRzCzmDq4/CP1+jJGeDXo/2AHnlE+WYnwQAC4KtAz6pbVnd3KstZWsVA==", + "optional": true + }, + "@next/swc-freebsd-x64": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-freebsd-x64/-/swc-freebsd-x64-12.2.4.tgz", + "integrity": "sha512-475vwyWcjnyDVDWLgAATP0HI8W1rwByc+uXk1B6KkAVFhkoDgH387LW0uNqxavK+VxCzj3avQXX/58XDvxtSlg==", + "optional": true + }, + "@next/swc-linux-arm-gnueabihf": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm-gnueabihf/-/swc-linux-arm-gnueabihf-12.2.4.tgz", + "integrity": "sha512-qZW+L3iG3XSGtlOPmD5RRWXyk6ZNdscLV0BQjuDvP+exTg+uixqHXOHz0/GVATIJEBQOF0Kew7jAXVXEP+iRTQ==", + "optional": true + }, + "@next/swc-linux-arm64-gnu": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-gnu/-/swc-linux-arm64-gnu-12.2.4.tgz", + "integrity": "sha512-fEPRjItWYaKyyG9N+2HIA59OBHIhk7WC+Rh+LwXsh0pQe870Ykpek3KQs0umjsrEGe57NyMomq3f80/N8taDvA==", + "optional": true + }, + "@next/swc-linux-arm64-musl": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-arm64-musl/-/swc-linux-arm64-musl-12.2.4.tgz", + "integrity": "sha512-rnCTzXII0EBCcFn9P5s/Dho2kPUMSX/bP0iOAj8wEI/IxUEfEElbin89zJoNW30cycHu19xY8YP4K2+hzciPzQ==", + "optional": true + }, + "@next/swc-linux-x64-gnu": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-12.2.4.tgz", + "integrity": "sha512-PhXX6NSuIuhHInxPY2VkG2Bl7VllsD3Cjx+pQcS1wTym7Zt7UoLvn05PkRrkiyIkvR+UXnqPUM3TYiSbnemXEw==", + "optional": true + }, + "@next/swc-linux-x64-musl": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-12.2.4.tgz", + "integrity": "sha512-GmC/QROiUZpFirHRfPQqMyCXZ+5+ndbBZrMvL74HtQB/CKXB8K1VM+rvy9Gp/5OaU8Rxp48IcX79NOfI2LiXlA==", + "optional": true + }, + "@next/swc-win32-arm64-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-arm64-msvc/-/swc-win32-arm64-msvc-12.2.4.tgz", + "integrity": "sha512-9XKoCXbNZuaMRPtcKQz3+hgVpkMosaLlcxHFXT8/j4w61k7/qvEbrkMDS9WHNrD/xVcLycwhPRgXcns2K1BdBQ==", + "optional": true + }, + "@next/swc-win32-ia32-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-ia32-msvc/-/swc-win32-ia32-msvc-12.2.4.tgz", + "integrity": "sha512-hEyRieZKH9iw4AzvXaQ+Fyb98k0G/o9QcRGxA1/O/O/elf1+Qvuwb15phT8GbVtIeNziy66XTPOhKKfdr8KyUg==", + "optional": true + }, + "@next/swc-win32-x64-msvc": { + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/@next/swc-win32-x64-msvc/-/swc-win32-x64-msvc-12.2.4.tgz", + "integrity": "sha512-5Pl1tdMJWLy4rvzU1ecx0nHWgDPqoYuvYoXE/5X0Clu9si/yOuBIj573F2kOTY7mu0LX2wgCJVSnyK0abHBxIw==", + "optional": true }, "@nodelib/fs.scandir": { "version": "2.1.5", @@ -23323,6 +23597,14 @@ "@styled-system/css": "^5.1.5" } }, + "@swc/helpers": { + "version": "0.4.3", + "resolved": "https://registry.npmjs.org/@swc/helpers/-/helpers-0.4.3.tgz", + "integrity": "sha512-6JrF+fdUK2zbGpJIlN7G3v966PQjyx/dPt1T9km2wj+EUBqgrxCk3uX4Kct16MIm9gGxfKRcfax2hVf5jvlTzA==", + "requires": { + "tslib": "^2.4.0" + } + }, "@szmarczak/http-timer": { "version": "4.0.6", "dev": true, @@ -31148,38 +31430,29 @@ "peer": true }, "next": { - "version": "12.1.6", - "resolved": "https://registry.npmjs.org/next/-/next-12.1.6.tgz", - "integrity": "sha512-cebwKxL3/DhNKfg9tPZDQmbRKjueqykHHbgaoG4VBRH3AHQJ2HO0dbKFiS1hPhe1/qgc2d/hFeadsbPicmLD+A==", + "version": "12.2.4", + "resolved": "https://registry.npmjs.org/next/-/next-12.2.4.tgz", + "integrity": "sha512-b1xlxEozmAWokAXzXsi5vlmU/IfJcFNIJA8dpU5UdkFbyDPio8wwb8mAQ/Y7rGtfTgG/t/u49BiyEA+xAgFvow==", "requires": { - "@next/env": "12.1.6", - "@next/swc-android-arm-eabi": "12.1.6", - "@next/swc-android-arm64": "12.1.6", - "@next/swc-darwin-arm64": "12.1.6", - "@next/swc-darwin-x64": "12.1.6", - "@next/swc-linux-arm-gnueabihf": "12.1.6", - "@next/swc-linux-arm64-gnu": "12.1.6", - "@next/swc-linux-arm64-musl": "12.1.6", - "@next/swc-linux-x64-gnu": "12.1.6", - "@next/swc-linux-x64-musl": "12.1.6", - "@next/swc-win32-arm64-msvc": "12.1.6", - "@next/swc-win32-ia32-msvc": "12.1.6", - "@next/swc-win32-x64-msvc": "12.1.6", + "@next/env": "12.2.4", + "@next/swc-android-arm-eabi": "12.2.4", + "@next/swc-android-arm64": "12.2.4", + "@next/swc-darwin-arm64": "12.2.4", + "@next/swc-darwin-x64": "12.2.4", + "@next/swc-freebsd-x64": "12.2.4", + "@next/swc-linux-arm-gnueabihf": "12.2.4", + "@next/swc-linux-arm64-gnu": "12.2.4", + "@next/swc-linux-arm64-musl": "12.2.4", + "@next/swc-linux-x64-gnu": "12.2.4", + "@next/swc-linux-x64-musl": "12.2.4", + "@next/swc-win32-arm64-msvc": "12.2.4", + "@next/swc-win32-ia32-msvc": "12.2.4", + "@next/swc-win32-x64-msvc": "12.2.4", + "@swc/helpers": "0.4.3", "caniuse-lite": "^1.0.30001332", - "postcss": "8.4.5", - "styled-jsx": "5.0.2" - }, - "dependencies": { - "postcss": { - "version": "8.4.5", - "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.5.tgz", - "integrity": "sha512-jBDboWM8qpaqwkMwItqTQTiFikhs/67OYVvblFFTM7MrZjt6yMKd6r2kgXizEbTTljacm4NldIlZnhbjr84QYg==", - "requires": { - "nanoid": "^3.1.30", - "picocolors": "^1.0.0", - "source-map-js": "^1.0.1" - } - } + "postcss": "8.4.14", + "styled-jsx": "5.0.2", + "use-sync-external-store": "1.2.0" } }, "no-case": { @@ -31828,7 +32101,6 @@ "version": "8.4.14", "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.4.14.tgz", "integrity": "sha512-E398TUmfAYFPBSdzgeieK2Y1+1cpdxJx8yXbK/m57nRhKSmk1GB2tO4lbLBtlkfPQTDKfe4Xqv1ASWPpayPEig==", - "dev": true, "requires": { "nanoid": "^3.3.4", "picocolors": "^1.0.0", @@ -34276,6 +34548,12 @@ "url-template": { "version": "3.0.0" }, + "use-sync-external-store": { + "version": "1.2.0", + "resolved": "https://registry.npmjs.org/use-sync-external-store/-/use-sync-external-store-1.2.0.tgz", + "integrity": "sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA==", + "requires": {} + }, "utf8-byte-length": { "version": "1.0.4", "resolved": "https://registry.npmjs.org/utf8-byte-length/-/utf8-byte-length-1.0.4.tgz", diff --git a/package.json b/package.json index b899c79c61..f620c3bd15 100644 --- a/package.json +++ b/package.json @@ -56,7 +56,7 @@ "mdast-util-to-string": "^3.1.0", "morgan": "^1.10.0", "msgpack5rpc": "^1.1.0", - "next": "12.1.6", + "next": "12.2.4", "parse5": "7.0.0", "port-used": "^2.0.8", "react": "^17.0.2", From c3924d56c20cc2769ac353ead4e0b3b9e488059e Mon Sep 17 00:00:00 2001 From: mc <42146119+mchammer01@users.noreply.github.com> Date: Tue, 9 Aug 2022 17:32:37 +0100 Subject: [PATCH 27/41] Update outdated screenshot in `Renaming a repository` (#29755) * update screenshot * Optimize images Co-authored-by: github-actions --- .../repository/repository-name-change.png | Bin 14983 -> 11550 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/assets/images/help/repository/repository-name-change.png b/assets/images/help/repository/repository-name-change.png index 8deb3709927aa52e8677198dfeef9a5a2026f150..f828f77b279497d22c32f97b5620e6d694356b18 100644 GIT binary patch literal 11550 zcmZv?1z1#D*akX^f=G;#gWzyfK)Rb5P^443B!*I9014?35k?x3PU(=2K|nwlLb|)V zyQJ?PJmyC4vVNLEHd6$HXz1CA5#+yp-P zUxF%uuN(HN(&C_kE}B)~g0$rHyV0**eLGc zOi0a-9O2)lpr#VAdXYw&X$8Ul5LJ9(tU|IxXApV=WW@3qS2*iAw|fd6D6h>qCf_@@ z(NbyVJ_v*)Z=5mj;~s&4jGACbI}1OwI$aQT%p3huW}ch-48oOV64%BKt}r*lLt)#?5|V9ghnBv>L3scC&$}xPSM+~hk=!plHZ+S zqAA=3+_)f6JS|0!_PaF3mX07HDpGDyowur7?%BX%))8|?F@l6rDJUw)Fh_u9T3XtZ zCr>aK%nN2Nyi`Dl-FJ6&Sih;5ru~sp2{C?1$!%_eLq2uP{yr+qee}Dt}W&Vut6>EfwLfUVs-QZN3CSe9svI|CBRk}|B zH$a-bm_{mDm4*=rr0L0Nt<0?d99dJI5$DM8@bLKfcz-|X%T@FY9_T|bich=vAF19T z;|G%b0XAfdj6*7oX+NZULxY3;nf*p(LB9aqZW_ffA`ae%)l#a$QaJ(-h{6GhSOd&N zlM72rOZ7AI^E)k5$N^`B4jD<_5Ax*>cuO|QSgR6|rY(IxbPg&h7T`^WFG-FG18hPM z4+8s*%4yS)q}ZUyB3A;R+-3^UB&*cb)s2gfkB^IkF{0%Zsza!$bDy^{E=S za%LyMZ%XSMD4Vzf%*py0OSqo?F9{Wz7@1X(>33vpRTC0Fp>BYp<`9{(vS?Ux?HWCa z|L*SYmoH!H>z|*p%OJ9EfIxlZ*i|t>Rn^l+WbTL0(diY1<^T$_g9inF-;YEfIgt(y zycB`HnAxc*gHtJ)FLxf|fn;7Vo~jV0%gF48r9N(w;-_oY@<&*ZfQnv$NuSb>wsG=9 zhNh>dCnqPTrij5fp!9syzn2sF7i$>D#N7hr{X`W5a&aS#j6T%fJaw-f8q#!zfc~+9 z2O0k(DIS0#BOhhv66M1OZfEVqyO?e*>`HFi#`%rs_pO3E|$OdoM5o9<_ zB&x9VY?h2FoGPnWKE9@V`Dqso<;#$>>I*h-7?)-M&*m~6G@p` z2}1e98=&?>&P#~L5@LRS-rZLF_3PL6_Vykga2O#d3=Ngy3VZyh=|!zX&|LZoLi;fg zr3I*6T6u0T0SW_$!;!Wz?Ta7(o4kbHn2el>KLF~NaSHkndBAyOB73yJiI$n3-<_y- z0z+{@GJ4=Nh|HHTw!zoR_f5oNvF6q6!~A){!q`?sD~~QOS2@VZ&-eXrO02xUJ-J)q zgrNl>P+ltPy_1t$jX}jY5!NJ?D3$B=+y`dXwggwZ9kc%@_dVdJ55O!S><_rm=F8Wz z0V2V{!SP)f9LoU~+B_~}j^!Gm{UN-Gdc2g?MB58sfJ`^olPr!Q(q)ol}uo16dn^#b=U_SJCdFg>E@y)u zBP{J~X3Wt5E+%Kh2s~+`k@-(!)l$V2- z8VYMt^-U)b4U*AJopm^75G!xCUgU`$HLfK1G~M7}VRw_B%J{YMHKnS%Obkp>CZG7y zJ;+R)?V^M4lROnxfgos92j-mew{FRifoh~_?&_a{Jge?yO3mS64MWe@TAIxT%J9+& z4DrTA7EVjx_CRD(w_6g@#LeKgo;LrwP$lZJ!)4uF*2+WHTX?u~J>s=oZ&h0b`nBnI z>A@)`VcVH9y`!Shuq^cXpTGzggXdNr`c_6CC2|F$2bj+y)g%WG`I@qb!!Tyc6u!3- z+d5pgOfPP!WsIJ>GjBDud*(k+X^1Z2HmI5qvsp&ejep%IDObwzf9wL&Nf$hhH1W+) z_ZIQp-ry3JI4qjp8grWYx>wa_FQ>@u1ce>6BpkC37hSeaBpHfWI*1?DIr9ZFmX=U43s0Q);Jz-K5;aBr{TZo2#`ro*)yL9LY z$i^?7v2S;Fj2&G*WPeDS;j+frcW<=&tz>wYTk_8HC!?58_54-_;Vy&n(HG}oQTBBi z=jHcBmJlr#w=lb&Xr3qbhKPz&>Ep$Oj=Txgbq??VPHE_%g1;}cAc(rWFW%#6vOq8q zMQs{i@cYjQn=Lgu`#SizXra?b74~+C71HbI0fBig47gcZ{tV8&Y<;xKhRzW-({CVW zK7HC3rwm_v!AO>4hi_IiDm9pJ9zF0SE9+<>iS=m3=Upo-Z&gjs>l>q~X0}$K$3Zd?3J%as+_QC!`X9MN_UcDEkn@@PlK+&vjHI;cm_X5PB&++*8}@+;ygM}V+7RT zH$Z^eKrn^<(5Jh???rcwY-M&*O!(4v@onQ1EB1?yx;?WxaT$&|&5(=(>JF;b6&X@GeEJZ z)viz3@(%L%X&pnD2-|Njds8;u>AxOtbOm)JI)-Wu4x!%Kd+oO!By&@?24(5T3Y>4^ zV?0M}ILl>)MHdB370ej+i~e-NG<;4^yleM`BCcL4Ij+TRqrE5kwqrAJQi?l16ls-&*Q~^6Tx_hM!C+w^?>YeGPUYIEo!! z6^k?!5>9T!jO3PBjgIqpI(40y7DF>bHqEw04Dv38XM1Xwqh=6od0UQC`0odsvZh5f zN$Q&jv56A|mY+k6U2&&}E*?w@U7jXwC>+K3i!JFJcboP2O}nF;>Et z)p=GM2*5?1A=i@X5%{gi2Ly)J?Uix2LK>QIfCXI7kWaPtINz#!fuhWaj{-0+HqR5d z0*UAsP@NV#6`(0r$0AYj@Y~VarKAd_(+j zr|@d@tgY_&T(oX|*yb0e2%*;~RY5o@=y2AfC{dxh=VoQ<5JX1DEy&9cO-^)6=+ZNG z^%M54`Y8OV>NX&Yj2bviIV92R=%O&RYSkw_50OyYf7}E`VEovcf~~2lY*&s_;y+tw z&@oG)dl$DKoy52tI4|{193ZP~2Ji>S{d1_+qR7>`u*&IohIoAHiFQ6c7u2VDE{#(} zv%-+7=Woq8j^8#a9s2X3sAPjV!l)#;v+GNM%5vVoEqcHLMQ>pn61^ag&@7@F!e4s` zC(=pHp^C@7+NSUBkSwJeU(DWEdyHLi4Gig2yM273Z$>n~Vg`x=Ps%yG=(RHQXkP{s z1_wQ_OhEVU3ckOOE!+msqxRvNI!{de-1bips8xmGbb6-`xb}N~sim>qgWAP1mF1U| zSPZqgh}gh0^eC2IS)>p966>o3dhEbb?ACS~Re`}9m8(^`z6!7z80SBu10@}b3-$p} z!u8SrYx%#IU>f0e(C;BD6o68C#=DmR=)zE~^KCDtDVIIeRX>-r7aX<$wmDy%4}IgdJyZC* zxdg1g>4Uhm)FDyrAo~ z_5lc}sq*yv^OAC#r%9j0Bo&irOsw8Qrk8JGfSoKJ`v!tF`E#wayg^;l8b)rIO-?2@ z_Wgv_d(n$YAdO4ik9yIVDCMs(9Or!hhj0bVq@OFi2oUax?1;$pw$T3kENWIatI=`^ zQJ?xE9CbM8nGl~w9KPv1Tf>r{#;P-qSGGJ8IW)wwz2yv`Ja%a$o2HN(r){sus!Re5CQf-&6&6sqP>^yC&+e4;mE+}td$jlE30ZD zQoyS~P_!=8oEy5u$dG6ZO{)yqlA23a!W(mjJd|f{zO)u*|9t;@=s$XW)f?KPZ5eA% zx=|0?+ap^ryeIJ$ykGew+z6m(Gv~ej`Pj0e~L&`bTk3Bobp+W;u`|?cm(pU?J>1!*uP1i8Dk&uK* zx9PKzJ;zy;*NBwYR?SF8>_q(8bagh3s>|+XVq5xhw7wq-UTVL6S@){2($W0NW+ne> zch3^f>1w=*nJvR$3z@nlp(J%QRlzY)kW+cFI4(pLD?~e~e4V|D1`jwzgG^N!slhzy z(jLPHSr~6eCzBya~#=*pi7k?>os-52VDioE6 zI&N)MKlBL}yEr%1hX>h+O#K-8UN`th1$}7OdHTz&Lmv0geNCxH4|R8R?edY~pl|4O z=VY~8cZk*6qcPSjehwx@wXI9lLig#&Xr^6%DKm-9LR8*jK+|=&6?HBml;#oZGl(T$ zvwePy`A$*(a}S$EyhXgd0#Ubx>V*9QaJ6w~TU-&E0IN{h5wFQJ9@&w!79Ilga*F+M z(%Ob$0In{%&&WXne_hU|zJ5o?j5JY`g(FjU(-L*4M5bZ(`RL|J>U>z-1m=_Pn~$g* z%Ymu`3`(MLYo#Ce!->TRd{I`sS1$kl;gIn)`0J*e?qPBXN>L!$ zg@I>17HrwF<0cEhF60HggHC~E6`^CtB>Sn=JWz=!Cp~SHc7;Fo;Kp}&#>dy;9@?+?KYVhx1(K$fRnt@ZTgliuXCjN5PG=4LGf)N zkEi{PPwF@yU%3_sjmL=?HRTScMhbdUNJm>u@BM5|^zi~~6UH2`fcc62xYP1Qbk)>V zo3zbC{jMjS*PF2sZdix2tMAT4K;#23Pm193RTj9j}zDhk(PW0KjO}SJUiJHBN#_oKv6~}obiWZ1P z4YdA`8R4aaM)!a53^u#}vfzS8L*fJ2H?{xwucv<#`3yp@9RpyNdZ6h1izNTXl4b|S z^Q20EWtjSNM{4v9ZBYl7ULwhg$isYe7kiB6UU1bNEN0*UpCx-8)i~!>=OJjYH9G|; z^4XIo{PV)1UPh+Knt-rmu;VYEne9^XQuH1eUhk*0c@ydUIy>1o)QbhM*jzhCC~+N2?(^PBaJw5sh?b= zDt#;1ar~1F%%I6^+yE5P_zuj{AbuOL%IbZOH4etz*#IKFT@@IbfQ<#hH4A8|a~b$3_ueve+`nlqIq-;O9CN*U0pJlx zEDQd9p!nZY&=B5r)%q7k!jO{q&1c)b>u=I11-bq;CRz&GOqXZYF@Bt#eCZ2x6aPAx zt~1aCMEd;Cd9GWGM#DGb|881?F3}-g0(1OD#W%q69rU`=H5C{>vwG?bk45*h=Ht!L zDEkUr>v1{A_=>(91Ju_F$J)Vs^}J6f(>^%v7Ng(J)jlZL{R!!)~ zkI37_UZvZ|%1-?!8Knx#ab1F2EPtJGXd1Kfq>|gAKYm4qd(PL2#fr|!_A0s$C@BP3y=bT@3`m84P_q5W`YJy*w9uv@q_xnZT zvvHaJ=Hu@roomVs-AFebj%=N7I73_kZCXP$DSpl-Z#B=nbX8L98*Q1qJ%d;QT9H*Q z+HVbog6OOSgwK9d14@8n`#=aR$OGg^k45Qkv$WWw`y8*{J43Ls0|G(77{6W4zuJZH z17^Y6XaoX1`nD1oM5@8Ele68{EvUU?6s+NMx3i<|cSl|EZ=6WYLRYKrA*SXJZ8LgW zL-eJEe%dkI0iFSb)<`2XYC}h@>T!D2^lmu=spUytp4@Xa{sW$xTi{apG>1t_FfxSC zWhAv7=yY9&b`etxh61jHKAK0=f4m5!#n+1_nn(P*Gm)13Vf$D6Q5z1^C*fR6=O!HcAP9!FR#M#m1(dsJN>O#cQC)At#jm`VvF*? zJzrk_H51;U%uA`HvFc3oJu%(Ff;L+0+GyL`R`GXdcrveX?+a+Ba6|!G>A>tsL&!;g zUU!(nq%zZJ9hxUS1j=AKH}PJ|y1{uQ+!N;p7)NjX|I;)4fTGu<&7__Ck&av(La{Yq zpk#~d_<8kEw;M(A}6onqMrP>B9|U@?sK za2Z9lj`?$tS|kW(bk=@Xe~8FjHc6b_w{^Grx>%_*caZ9$81ugFhiFh+Ni3Cv=VjF7 zHqBrHTlYnu*SK>dq^+-wq%Tm+yh9)#{56Tzob0&m3u)geXZ&UH=Wj0uzs(?=J^u~6 z?;D7em!Dl?#y6)-uL^ssU>3C0&6r? zd)>*#{@ZdB;r;9zz4LJo z*ygS_7l0e$N#RH%qi+=z6#!{dSy@?ID=LZ2(#$Uexagv+sS|hmYVEMu>sQpl|8)7& zM;Kipl1hLkjC7z8ZP@p}c(i#o4ji0q5g;+xOL3M@t)bTrGbd z0g0L_Yd=Jf0IBh}?>_fPQZgWz>=Bbv0JQlg6QJ8732+*RJ(;5U>(^PCnT)kTK|zGX z#JE1s>!!C4UExsWHE6R&9-=YWyO{0g7tdZG@xL0=BF4Y=!T-%C1bii9V=`A=F!i}^ zbgIIFloh$b@kvP`E%RwAhrz=rkd7v+A_)J?2ue zD!Gd_(NMTOCghgh6lP=&%OCs|R<(=_9we=P0QdntI9~a5Qo zGout~P*}lBfJFL@3pnhatSl=r(9dtjEIkBf41?&=QvmikJ7Xg36=*m*IvN@p%FJX4 zZLz<)yf{5|jc$LxJyoL{Sq-p|qeioVbN@HTMuvY)M)}DCl-6Chm{qN>$jFhE6-G6# zQ}z*nM4X)5+&^LDcd40*ii%oVGG8+Nq?ZNIulzVLi~pNal!Y|CKy!B-$jf5gsS;}L zT2!migo}rVndS6gO3x;{bL-qw>~>C9SC?ZX8qHtms|gfDXKf#HNluD3#?1dAOC@0e zZe$lo`VL+Qw#ox=J@17v(ot2t7#ILar_Cz0`vyynJ;e2?2i!bB4N%&RNNa-23{^w- zEiq96tLecrt*EN?WG}VJjcEnmY35f_iF&!UC!vKl<>|^!-WuKopX`UX^M_~Uf1e-@ zhnFsfjQ(XK9}Z3@Rc>W6N*9MbhBmw$=a= zEX4$qe0)DZ4G|gk>?)ww_P9@rJow_fPu5%@i<3w=ndkC2M_b&f0Ap<&%WHYKrS{Cy zRsr9)oP+N+mco5`y#)H?>%I=;XoPQ;J^o4OGwg^Ll7IFSDwq2?kY zt-}GG9UYw1X*Qo;{r+qlSv>f7;bdzsbo0DBgqDCKS*s%4FD&fYwAXi^O_lx#*V7Y~ zgE(5tF`KTFbEhrN%{O%(N!uzVM$+8GlY@Y!eAYw271pJ5A2{ zyIhSd{WBbp+o+r6lsNIs(l!eBNQB0+UtjoQi$pCj;jBONrbQyW;vkB-GWLOWZu(Tk zrg0^4aLr)7o2p>eP~)1}&^HRJO4tC7?+a&+(O00G7S&bGZoW!9P9F!ndjhtHMWhjzXfr|->%!ArWbgXro78XI0=oxY3)4)e{1A$xwqV7rK- zB;u4uhF;rL5ZX}QC=ZWu%Ir#2=he2Rb}bv&XVrr=h@gnbgv#z@g;rfw{%`Vab}Z&(ch)&-7i~PR7tt)ZQ|3(+Vso?`WTkVlnTC4Z+q*gKy!oaMoG&K+ghe@>(jiWt+f3Wo`e% z*;YUI+WTf%A}JSCRNs5TgSCTITN@KU{|LSX(=+HfKMyKo$c^S(kcWs&it^d#H}FS( zLdBvQV*>nfuy0A=Q#o-<8J9!coiF69DBU&-Yv^igcR5q(8Gjy_JX3y|y{XK|Ro0x$ zc~r{lFEJb{?#jlsS;j=)_o_LxghO9~O_D{0Rno(wMyTqUVnKup?&wzbvR{-z-m~aw z_1E-N99>L!mic8Da&@b#he~Lsu7PK1-JLCQ)$-4#y1y$v{rs9_Wc7x0B-}Uevcy6ru(~e0qUIvGKy66$kY;LkO)bJOf1N-?uk)4%^ zcq@T(wxK09DG4?zEbm@z&Tch|0GlUiq-C04&1nfJIrKBj>9>qC8& zedm}sd?$jmmrVAp2}r+wiRI4{n4y#>Y%LGUpa*uvlIm$0~JlwrN0IE4@N0Pt-i8s%8`~;RO{1r^&G1u zb*>~Pj}i`xwoV>V7dYd2oaBHa_*IN{bv;v>8K$mz$5*aigyYgpAQLQ?Gy9WaiGQs% z&x1XajGc4;wh>+FwgswLmz_|}ru4DvD>JryCuh+-VsSrJvxScv9O@a5rXI1y1@mg@ zSBQ|>wR2ZDHMO7I}k-hOJ zzJCIP)KDnn64hySDGLZHoBlD>^Zn-o%ahr?NXtIW@uv(%Z*z5}%EVmP*{9!7s~H^f zy)k^vCtkjB&$ccc+^y4Ynx4NVr@x{S-X}?8ZxWv&k;Wjmq-rgm79qTY$)IUWORx`< zU+@s;Q0PRQbvBLiagG-2I<+pp9OKZ8jI*IBSg={+tr2ANo~T&5tZ=x=F`Uw1=UUUU zK`I{|>ueC@n%mjSA(ln(?3s16Cvs2e8!|`ops+-(E+|ptQHI}lE0v>o4y6>oOi@a= z7lLi>nL)(G+ZI{PaU6uzAA0n%78K}J(YhD;0>pJ|3;nOXQXUYc#PCnK?vJ}YN8j1l zoi7e)+n&5oPC5`EBabfHY%5=HJMyvVD`QniMwKMWRa+dVC?)@Z6<(hyN4-Qr9efa)=;6Dn0HX;ZJr8!3k^0zEaD=jbd@bH4)YR1 z$gA63>eQ`jrCWQ(EXFgb;2U9~@BU%IT0-%_9+9kFCB8sG1xLOT3ZeX9Qhi|ZP}nB%)+R)O3>B36ljw zadgNLz4M5l#!&8$ky1+Wtc#TVd zmTl=FCy?Xj5J1c0Et3IYj;{eaz8$${-+wtjmHg#-B)o9R;$;;-BRiqz(JxYP@!Zhh zyYSqpH!N560mAG3@{d2_@_A<5Q}vmT667iG^Qg!Rgpl_O4yJz^o*0>){ucc^{%u4m z9giq8ja|`@+<2ksn}f*9f(*fN+_8t2TkQ7V%O@gu^YEHQ^z#^`@;_O~mygNs(NsU^{vLW;|VbCQNC#DR|i#%OI48tQYQza zhS`0I;cwFJq7MHNcn)2{S33`Mx_DPp1>a&s%t~G0Xq-imM~Xl6mmS2U^Sw}_?PkgY zf6XG^Oin6VI7CD}s*1BXn+8ciwf*YDonuBE`P~oyLH3)jpK_|`4AiF&oYi|Ow68|k zg6%~Kc0}qu$ zj);x~nn}O$cd(XUw=t_a=}{C@v3jZjeKFbQy_yq8p%@FZ1OJ3t?W-yq_O2Z7D3kn2 zdJ>Bna_RxG*|J7Eu{$D%?&-oTS>t_D)gQBSA6bMr7j%-NJ%`2)(xbF%iJL5bJP5Mx z74C6W86DKLi0*s0uc5{2l-b9dBjmXJdmx*RXnR5N-v0gdyo%wm<)!$pgQ&wYVW)CM z6DtlvHHDe?n)1u78+Mv|Wq$YL6Po;r?yjdO^>TzB4S!f3dylFVUv06iqPbJ&YWYUN z1J(iaF&B7jO!s4yT>qU%%xZ<(-c3F=rm>)y&TV>nF&;j{aFTJ^R?DTsy}oVw`Te2f zcbZNTH0I=o2j};5Y;(Th%{CqR&{+VrSW`>iEslZ$dU}bVf};l0f^A^crx zXfEp;Xx=g8%w5<+==F;yz$?kuugLv<6#_WB?imALK&Jvbu>EFWVB4YC0qpRAG4lD` Yi@|m>ElxX=4|^^vsU%S#ZuIg00h7TVQ2+n{ literal 14983 zcmbumbzD?Y_cuB;0)ikhARW>SjVL7@(jX;_l$4@$4~lem3P?8t2qHNs9a7TWorClY z+=I{ad*A!H@BQ3=?)d}G*=O&ySM0UU`tH3ZOiM%QJ^>8@2n4#XqAafi0%381Kp3+4 zm_SQhLTfY#^i)Gd{<)qf#@^JY5N2&q_wn`Z?dMNm3~a2Dk9tf5pExjbJcNpKOP(Ec zku}vHM2hWpRSw}n1si5f{?{xeY4N$IEeI5a@&u)P}km`9GSxCFsYi zQ%ix%z5`|NoPBrK)eOS`J@}2n1o0z4pc!-EDHVEt-SU)DTOYWh(xB=Gy1>nN=p@_| z1ibqPyddg{9QkhH!zU~&AU4mGlbOWsdvTAiKj&HgHndglLk~HK=})l zDe&0yOLKztGz!Zgls+Dg_CU+?mv_(HWp*@4R zH<@N_o+5%D#1{#xYZmEVmSBK3ChhA~?YG>U)C-4R^DAd1_gkak3fj$CP&0%vF7Ub{ z?SU-vWznCs-)~MXCDi|{RcyO@M~I}oh%Y+zHobMo+VmfQKRR*(T`ZnBe4A#4zpbBL z+{?VDMymo2zP;77Jz(+ZkyM$ok`&jY)jF1aF5$GUgJFYvH05_>8Ie-Covt#({Nl{- zBlE=gxZKAOcxx%l(^Hv5Qd06a*6YtNzdG7wWoBj`n_PnbM73pOSq}WQh!mKBxL?Je z4-5^3_-H@AH@mnv*_J9L5MVPfyzScRdnw!SB7)wA%NJw{gw~~_5=H}+ut5>gLJI=aUUi|9wX<7J+QOMlWoxV-me{g<1 z@ZrOUw%SDbd8D=kp|0=w0o|dR)ZDDZv6R@jE9FuTqMKX z;^MdI^UIS>X@;Ek@o{}&b5U+?Zhb893s=jFlg*(rbKi?23~lb(Umj-MkP>rJeW0^m@DhX1Hi$dcj3%W=?5NXvaiK=dx~?&QLP8QX(Frm?{D z;!oRxj_=>MxBS4$<&yo%@mDQV(H!@0*)WZ4`?HO!0&(+8A_DKCZHpkwtQUOWR0xch zc>|-OqCVa6e8YYfR9MT`u$x1JYvP=dk+C;C!aE6{pPx6rt$)9`A?o7ir@k4(AZ_1L zN}rHoLYT(!qf{O186hdvhq8wb-K1YS_+@P z5#lQ0`Qz*B^TRUcw^C%REc=qd4{E$mHq`C?&i1IE#h1rMsWHnW$(Tu(7{|R(v`E7Z zFUHO?vyFmU6~pZO>@70lwF7rw8W=b@m4GqRS4kvN?isP#5Idt)^FBOpp~~B~#r)KM zQ)>=rCADY*VilD7JAw*Q%DgOQ^+QNLq57kGTdlIZYC`WD8=GF%h{vb&1CP1n29Xn# zR|=tOa;}XA%3w(F*x7@7&D#@PLc-fAd?Y54;^H~+DL7;(5BeN`dBlIL%SDPA81$7~ zzCn=&Oua?JL7;Aq_mFV;h;f8*{zbMNQ*Xe_BQ8$C^faW`ENNsk;<_HA%sa-le2OJIg8kpL@_k4;M)sUbTNzud~5 zC={sGZ^Mhou?ZhfLg;>(5M@@mck}p<>SBFT?_UBx*T*JVwXuTKy}uKE(G2ki>rw>i)RiI}(EmGqfjYuzyno)pKA%GDsPn~UBZF~x@Jh#ww_ zpJSi3e{J29Tdmzl*ROcAQsz@#8BZGFtYVo*dy<>k0TG1F%RY zAfubq6OHmk_-n3DGfS0yv7Sj`P-inSN9wsl{)P^28+kLqWNM_(pY#o-A#YO96=MZ;>Z=S-!j{=cw?ao6 ziuNHSlk0}qX7{qSHlHf3aF&9XP|%$(ZK#~8aV|2%eJ7=$U}UpUs2k)lOyZa}YpBbF z2~?>dE{NEAkxrr~v-R(V3q)MTzLGt8p_MS^8&v8fc4wk$SRLpcbDInMYw@Xp3pu@J zXG2js%p1wlQ--qxnrG9Dpmy6c1Ql2Eu^QJ?$8*Z}ugdT)9yc^+%0>5D z38KpSIzJ~}Z{iZeZo6+_o={K^@!233H_~$0b&G_ zleNit5Wo=#bUAJ-Ov&)(u7iW-lrD1j3*6>E4-MyKH*Fvg4awdnYR8eIa!ga_85T$e z{Wc~G`e$4Cr2&e2p9x_rArEBXjFwqm@D0Rjz7 zHxZilJMj|z^13y!e*;{UB66Gv?_QffA8I5^4;Rdx0}HI5P_PqPPqE zlk)z%wcH-kTb@6)x=8<9KAyECfYopGjnS;R2vJ5$TX53;>3V+(Ngfa1PtV&Mw9om$ z@w@FRyu53~d;+UV`l|xvzCigB#xnALJs#3z_1^XU9%`gRPK%WP%>Y!*r@DjoY=!V} zt|4Kx(dV2G5i^@-5|wc)pc0>N5;b-=RwW_MV!JB5>aD7y+^758v%7zaG)4YeB#Cb% z)vmN7pNTon{g7&O-=7)JtbEl_bKw9C^|z|#BjAjG%%q|7=3R(2{Y#t92?{V`aL+CP z%8sC%ji5ppKH##iKTkbBSkFxox`?8D+x0XC(V2 zmZL=ADGy6^IKRakxlf%FXeQ#|STm1kn&kM~+-UCFf#Uqss z&sVvlN1oTt^(!@&mkMl>AkL7CnZb(~HH&QZJdSu4Gj6uVRA$vsq?x^;mbxJ@VM&&J zUnwAxWEGN0lldi(RYhm!Gd`07e*9bcc#c3-Q3e-lemq1f_xe19Ib@8shTOTv{PA48aBp^(w%3s)`p&HNX#*NdJQupHlh)Vp}dl+!5;;X1e{c-$W)r|iab_BSU4e^7tO)FY-U@PJg_A3s4 z1V9sU+4&?axC8@SB6q}!Q2r`@5eSAWjs=umx`-N1-vAMvimPdm3F`oC{5U8z~v~yfIW5O zI3a$@Yt2aLL@l26Gz0pVNRCZWty$*z+S-LdX6ySC!iVbyJ_lK|spVmrBeW=s&A4nE zI~bs0*hz%gaY_2qo1{(lnLp>JXB}@ZJL7~M-_$7dDRN%AEwy3%FPi%8wwyznu}^2? zpu)%; z<*IXm`o~PIyg3RXsiHzg8W#~5s!SI5kdX;QMqu`JtCWMJv%<_tjaB~|-Plxb?05ae z%jc_y=Ha!zSXb+}$#Ux7lj$N3x8pBpcz&iPrlqC5Uu+ej15$A#{(UT-{5LnRf#l5) zhSThDywZuKFx}|J{YE%}D4Q#0`HQ$qp$en*hbIFzIbpYWVSd+Vz0Pa!+3)Wn@C=84 zqki6fs8Ix-^EKA}xM1( zA_%vN{o!-&D3rD|z^<9a|3@=hYQ2AlMY76vBo_j0eG!fd0J3DwSd<`;K=2@BI+etJ zDD3!g@QZ(Mr=wNMdg^8m1Tz2!F%XAvh=$Sop)RWH5&}I?7wBt`EODom4#3_3(ah)} zaz5-Yl0M0xp{vu~qQb%pukBGbo&F5%Vcyc?woh1wqcn2mYRFxI$Vs#~Ui5wSvyI;w z;H3Z@LNF=(O{)WM4x3{5qwP;|-`m%sYU}xP;Nb5Qb5Gxh z8O)<5+15oKjQPd-`n)oiZv5<7m9>_71kWMo6&!0a*k0_uB*#1n+!p`7Wo>GkA z`vx}LS#0!VFo16`lcCAbXC4QU`zL)#-0$+`gVa1y#sfW)h=1;kmmR-vKIn;K`OHkk z_X_{yXy_|`%gAQWm=C6eh2{ibU9$WwW<6_HaQ~qBEueD^}t(v&dpkVjl#8D*Qt1cU_w#dN&3!_^w!G49N%H0JdTo5 zC9?Q%h96j0m)4j1GR$nswR5486;OT=4+S3&U3TiwKYUq37)&z9OBQh~Yq@?GM>(G~ z$TydMewG-3TX7x%>j?L$Id7m|&Jp&v3_{J?lJmM`5 z%o<(bZ}mn@f5UkCk%YHPQ?};!6u7|fgjn`7o1ig1Uf1}*8m;B}12B(;;|RTZxhh0(1X!dmhA$ zF6(G-!$p^-EF+U3vNGm=5cWH5-b-^uZBG$xZgJ?UY0zfF(G+_f>IQu+&4{q)jk{r? z;))gKA^IA0(xjE$T>la_qC6hSlmD{v6({m84djBCtsCT+?w1%piUM4LFBw{S-T6^P zFTSENRUIxq@3&?k!9$S8=&h^~KI^{5?&NH6^HQe{Ra!59efUvlz%PCtKK(igsire8 zAQeHsM&+(}VDNFhJDToV9a(1ozj#-43~x65zGG7Fs6e1TWX)Wh0{&`c{q{a(1S+EovP^qq3oO?EdQhb(1Sq9oyECtSG`??AFP zH;S7OAqN8-suKtx>nXdi-bx0N{El~$3cob4A5hDp)_k7Ss3bJUaJ%?HdeN9q6Iq&3 z&COJsYp%>$VXEjaV0%hqZCLN`?tk+vy^#^qQ6MSKWk`m8*q^D3Lq=iTN+Y)NFrRo|wf;+aBGznCs(?8^MKleI&4 zQ~KfIbxi*aiCnZ&qdlS$TI9W$<=3O) zWnaampCup(Io6Gz_!2p=sqo=mm#rCe-Z{~U|6RZdjgdV_p>2zJ!RFAK&8L5qSo((H)Zk1(R=eWL_Av~@3G z$I?X(nu~RJyJE=x5xDFn7A^zEqXrkHsNasGVn2&G9zZh0iSM1p>0DLx@ai{_~=tX%)aIV`Acx!N}l6#*z~l~ zjSK~DS0`L-HD?ns-Sj!LIEN#;{qR<=e2SDEbI)8>R+WXw#Zp0RRk|fkA*xGjTpa1g zO*s?&{mV^rlKZ#m=8W|SCt4EeWN=@158PLJ*0J7i6~T9}CVM>swUF%}FVd1h0bl24 zxvjdszDBLDy;Uha)3`d{#03TQ!dH_?nt$Y-cd;!|zHgKu2XMF=Oh4gau{5FOW%dGa zx^T&cAh^2O?;XspqX%F*CP3?7Qw83CPU^G25814D2?Rq_9O2(L9HB_+iM2O}0kDtdKU%&uZRw~9Bw96UWGQb#QPX#|g4>wfSfhd5-z4e0X;E z>`XLce&78%Pl;HU_$9Fsq>2U*zUJ7s=}mt-zZH~(ge2zM{0P>PQ}ReAh7^%pu$SUh z*`e%)@xm;(LAD>~TI?z2Gjc{mE3e=D+}z(I@AUl$(30H*3r~A9JYi7WMDbMWAs5QFK#og0=p(;f?8c5k24qx8aUT~g4C zKVvNA(2tXwldU}A>nW(dXk&*<+(B4&cD6JXhD@-#q6e<018;lt3m6k(%>a6pURY8; znZgX(!Vy*1g@U*fpgoYw)0)5f)h!_MseVjDG)nf)8f#PlJOBCbAbE-N@&8w=8VrLG zabdESg1YK!rM4}8s9=uDxq&~xevTbL&ob=u7c=LhT{xqx3OScv$qIB@6(|1ZOm=09 zV#WT9!t4d?D|M03qGbKSH3?^3Soti7`pZd`h}yJ`-*ST-cv*|Pn(BQC~v79h9Joecp!U5 z=%8QmvPDUlChF81{UkFM9gkjNShw|4&eA9f<4IDD?)A@E?(A82-ipablgakLGBt{f zD>fRQ7r7{NS|Pr~p;aFz$Ws#FOvCx->VI1aZpC!3qApSo7-jL9tPsPijtIk1H={Z@=)L{3;`;DR@3&W1P^v#O0ZR&1c_uO)>pG|8AcE#-Llz)Ym6SWQ&i<6vO zqPou_9Gpyp?asd7e#X$rSv-XDQ9XL2ukG&AvlT0x_Tp{Z@`u+1DDD>>EnMBo1cL+V zeN}jG*5_qJlz$!hw9x;0vYLMu!xR{cF4g0z9reKfv{8j+NlNISxzIh@-LJCmp7DI- zvEjil3|eEM?)ZLLRXFQtn@##)3l}q01Wr_Ypj(rvG1$TGNwA`#h9#x+)HAH;zV95- z{>2#l3>F|z*V44Pw`l6K@8%?HNSsk+v%IujK^*%_jor@Q*B97F-_G~rnHPjnBcfwsfF1D# z@=>Y0+-C(+z89e59;|D}<{|_P&GosB)RE+fqa~T}_{g)y?DBYF><(Xm-lT5puP zV;XE5|F+ytIqts@VFfeP%X`?PR%DUGWx%l$)zV~NUmuV#E6uH#TfG9^7y8!HQjwhg z1@!f3*!G@N^b*x_B@;HP{Sfioj=HsKrzHSu1Ny#ZXA(RZLDiZnuOCz^6qL>+(X1nZ8fImAuy=;4& zu=Npx0dmyFP9(zIeC)g;*)b)U_g4ua3+!iwI$K*Y71tjwwB#vB75x6KE~RbWD_NrW z%lTL=*E9|>lr4?-Qq)+GAh_$p$`0vz^n#!ovMpaA!Flt?F4%V-9zaiUsE*uh>G$QsPcghU_=vhL0v~xDF2w``ynlroCQ_2qw?7OFA%~ zQs_o}*Lv19%DtL$Oz6Bqsq@UQkS#W#K0xPCcR6hBlTVFe0e}*5$T$N;p24asIJ0*$ ze!1PV{h{)UXyWqX*isnjuA-p3{t2PbWbJhdpzS11TSkLaIy$-}da&mMa9s22y1Cij zz8aovU+iE*2e080wwhBT4{hhp08=?KuNL!xkh2;|+)kw4frd`qv&b~bVzmo};ul#8 z%1=7t-O`F2kuRPl_edm( zMO{YT4lz=a0uDv3+t(uS(+YA*UVq$APEQLBxra#PH;B)5b#fx54-MR0(0F;b?xwC@ zhed6^OBzCSj)&>5vrqkrUHMJQb?u$&TKY?$9* z@wR!48a<%-RfjfqEvGcH(h0?^jU5tK@^XcW6_0j!a4luucaREJ7h^rqAPQ?ZFo3{% z+XpU^NQ}7%L;|2M1mQZW6A1>J!P=`&^sM{&Q1R-YkN7M4Z0>}=_K|zg9FL}*VXQE4ocrOI7npmH5RP1Kl^QW&Wio|y}qw)XVotr0c*Vr(mKB- z$yHldSFlB;j+QE*B%aStvIyBk(rbDyGgv zDgxTy-@ob~-MgG(Z3N&Eo$%VPHOr|Sf#v0is<%RVIgb_^k0M_A)O{_+Ag`SIk&1Um z((E6};{v&eP6(a2yqi_T45ggZ^o1q`gO;CGoJr-pGd_YmYE_2gT<87=HH5r1LS^+o z6TE*28|jHRIOt2tCu7^_{jmc5E(msh1}mtLftlozq-0^iPXA{D3S=#LZm^-PzA8+@ZlCA%XGj@J3xl9{7O=;f_z?&# z_d{tF7M!%@$E}1~KO-@WghoPXH6jncvMeYP-$;lu_;io*tr{dmLYtYGzhJq4;9YQ! z_yyirC%*pT2t;}gGRtcxIJ`B=R0g5&K6?4J0R zbemtE!tSDljx`T;M{xVLOE^JgO9Pa1m4Ke6)JXc-oluH*v8+U@)IPZoLU(m?L9wUL z-PlJIbB+D6)&Ev%?bE!>M%ARw>(cN`vR-pJdYP{8zrIBPYU_e%pvE&|bhxZkjd9d) z9o})>&+c%f6J5PvBe~M2wUqYL0O>No?q~b%(L?~jdYpAIMqZ+1uyCd9y^e_Qf^RLO zf_Jb)F1DI{Kw zb}?$hQ$mzLP~P<~PK^HU30RC85hyS6gFm+MDVAzA^V{@ewc3U_{@wJA6mJaw? zHTa)b0?xKNxzhQxSU=1hO)0(gTE01w<>ZhTu%;aIVEsVxQ6f4|`No1woq z`jCn!@2(NP3jhctA&^G{Py^`lKmY%e@|3_y0|JAApz>3u;Yg96S zQGMe6Sy1%E3F}v#a1=oT^p9{sVzTu%gMq`l3QqoyhWq2jWp!Db4LoY9cIk!ZY%$$= ziwKuNP0T*=emMW-I3!DF$AGUO5@(8oA0%sA5jAeWx$fRnka*_j4;9paZ+LwN5f;Ui zlW4#I>{bnWg!8>}*NL`n0t&*`c94v=G@TqV^M46Vp?aOy<~&%CXoEdS>oSusnd-`2i6P^{Fr#Dz?KQ8g z78EmZU9b%)i@2G3n6j^hKE;fgVnO)^LHlbWSBt~EvK%T8ug{PXcO(sHyLHt62>UG( zisueqqZ$uqk9MC#zniVKOMk4+6V9wc=0{nT0tNWTM%+w2Bh**QWh7|5y{%CAT+!5I zLcTcTqwHeoxgn@kch&rew{ghzh?>t{5-5NI_M4T7OFtidl^lV{b6f@asFy-Be!ppW zrHGL7yZU>!Z=#w%T&}iR1_jv7g~c_&^Ps?hhiF-t)>kvc2YAWpE^uzXi0~g;*H?XU zm4#mQJyio38G{5s17}XAEFCMEC2Td}(6{tOe;}_8|NfXt#4&Sl zWAT%{-bn$*3>Y9jI+4k-sOKMxZuyvUKUBT^%5tAFnh6I>n)Hpf4SfV zM2=IDk+5Ja#+MC9W@P6e$PK9c%Exm&oce<*%qKaroXX*^K07<^7L_y)ZZg`EC=wg2 ze}=1wC4s48sV&gBlA}ChnV_2O8yal>kDq%^B&^sJ&y|PC)>v19Dp^-Mx!@k~<^lJ) z-L154fh+xcRppE&HAIo4b{~_sqHZ7bc6Z^!Ne7DL20xGN%y-fKV=2^!k?H@=(%Q5l z(rk~`=e%!5;6UW{U;Qf_KTINqe4YS1>({m{D!$%%y;EQ%OS{MtFr7t8EkWvIi935X z2v$df@wozGzq0k*3lAukZyrviO?u)CFQ-$AYF!G>9wTY%Yr`+>Z2O>CT7;M0!L8O~ zOT?Zhw@0=m+Wg=j1vdKQ2Z7kU&o!Jiaytmqp4;{K&^1hMZ#jH~WzvA-l^dp*3;uw} zlAjxV;W^BypPIUk_PDd5!G@obFQKy>g?0&xSt!+z_+tnEH8V>^XaUsbexz{;_+Fm3 zcMsD`t8cZD9vkSRg4J)pI_XKe96hc(uFx*h6*`t}2I@1d_aP0FVDwXwD(NV&p)a?O z;>;2{?whYLDwXz5S=l}?5v@c+gD`_&v)&mJ5BP`n>~FY=oz}*26>BY9pEQ!A5I#3| z>y~KcFw2^yPk*A$A<^@`JA4%W4R_+%M0Qt5*Y|3>auTC3pwo+G9dW?1?# zTy&C>>>fvrt^}%RKT^BpNpXct#?NvO!3Q)GZH(Ql@>+-eXh9$uXw^eL&R_$wc$`gx z6{Ypn&cmLly*^;j51aNtf6DmIO@rhOgJgHZhxdo(fQ>p35#&Nv`K1UV9u@94ArG@K zybm8gE~Aw3YJu9E#U z4#bKTwj32BeOI;{oZ_N!Kw5En>McnhbB%`8&-%S1TFdP(NV)6vJU*5mYz|cJwxPbb z#B|GX0>!+Sz7xjhehgJA&f9FDUKxv6R#u{3mH|Sbba-h??SQyoZ27~FdB^RTj~$FE z%Ha6!FLCK=Uxu(8MqRG{W)r2si-!L0 z?V~NS6WBwhuhT@fPN<%@&Xs(IKgJILFeh4=2!{$c1&^v%vzwh(5_oK=NPhHhlZo3uovO|4QRDWBeFF)c(W-NvIvr7~WY4Y;6}} zy*}VUSU}908O8TT@{~Bp^26Y=?j9aqhj^nMcH|Z}tSwKs+kb|TF!acjD#R)U)tE!& zH7+&2D}JEeZBBfs;UZPnJS=HsW>&cQH&EiQs}PpwFtXnd;u^+vVWR<_=}&>ARURuv ziJ^o{Q4x}`2mS;6XQ=+_gN8?(s&R0+FDGB9w*9($A%m(U$0`)w%vs;~5cCqBM=UEo z$y3)yH~Sg>ExxyQ?`a)AFXrCHEWIA!l4kxPF$kPl6Sc3U*oLkhQ5+sWp#J$MV%<57 zOucD7IlOwwh-WnekLi>XW5_moP0y+EQ=00g0g}6#Jv3jyCiwXAK%~%-Pei%X5ba!p zO9*k%qtlrg<7&f5>Oaf@f`v)IiEhPwI36EZQaTWeI^Zmla-b1)CAGrH?Ylp?$tVWh z&a!nl+H_yrLX{w;-1pt431tvV01h~ zeSS`0r=XGdu&nAV``N9$v{ebX!i(Mg)#aiY{765;jm0wrj~6hKl@7 z-CJ^ECAPS)E)VM^;ZyIv^4*=_rQC?O>0%(Ik9{uoeqqcaRIG1%!p}CsG5=9rmX)M^ zCH6abw(0l?8`+Mo-yS zZjyhSEZ#a{fFpsG&WKB2 z7-s;Ml#ZuG=V$x`Xt24J94xMQZB~n|P=fXK=LMwOy>(_k6vfl939V3Cr{uRCJMp)I$Bl6iWGHAjg zD@;Dz=CRhjrnmiYH0h#-m4^%GW510$`drruI=(Sc)BQNlbW>x~SwpCsVp&w{w{5YP zoTO!Lk(IpWqEJcKnsLL3y1{9O(+auUx}Y!o{_pY{TR-Gi1}pg$cPc$7>79SCi#I9i zy^CD$FBiX|{)xfBxi;ohccx^e2%`=*M@INGzh7NMj6Brvk^u)-uZzMCwb-kNiP!ht zn?`J#!$buPWMfsoS3o)8bcHv&;)T`y7EXSVSkW6t`!Q`*Gk+pvKgsvB!x~4 zJ0x+z7&=Zc>wJSNa_NiR1SkKkEN--=oX?x*h`npH2 z_r`I&HSgcvqB%E&ngC8iTOMBStxc+Ke&gOZrL%)8E+)ZXH6Mz*U&Xnfe~{8qB6(J+ zyhddWw`Hs*f$@U3OD};^kDp}})o8JxENULfoU6od{zUimTcdg+|HTq2F+1sim4n5n zPA2ck3Ke1=MN=}^sKeOaOFVZchgrP4tVn>;l?fheyKrqYsdrw+LFa7K_UA)~*ah*a zSoU=s@1sWTrSL9Q!H~d)9mWHz;d>@gpq+l9Gwro$J&VInSLSZB_(sxqKHCqL<)=Dyt{G&R z0o8ec8>FH}JsevwC|sY?sakL@vyFoNVgee~+G>)tVIq_z;k02aq1 z@*SlrZI8+~^IdytK585BRwy1_;)rw@MV9G4A#h0AiK6spE)dt(eqnMdo7I+-H%$G7 z6@fg^?q*b!e62l}0v#>m4B0>6Gj06qPe34^q;hEu4(^5A4yw;ZR1mnzMCct)5#%B0 zm2%0Z*HIB#&ous4)iq`_u9vP#TvE%_Z}z>@4n1f&Ptx z{8~KFFS9XvB6=y}bU9wa%g~qiH9>F0a@dYy*v7Fz$mv*swr;Xb%jIT`N;u;;Ay8rS zcZns45-mu?l7LhbjVP6meR3%L3ComCayc9^VMzL-W1a0Q>onzHpUyEif}JG&qI{V_=*fJr)hoSjRGQ&v~DO zM8s&Q9dDv+u<>*(M&R2&`Cq`cCrKOq)*kK|+5XAxw${=%t;rPjmNR($`*?Dl3Ksgh zz;k=}A|YY;%1)^Qy%i{QOTHfX=;2)BwR+8_3pWC3w@#(Xl_D>-^?J)@cxa$_4w9oS z@w9!!S;Uo;-`?lcX3pH<1N}PH(K^`*8kpF(cI=wR9FRTUQVqM(zK-S?oT;mMkA_g8 zVDTXG!w89n>dPN$o|EtQx+vP2R9@M{J(Tsi`fE3kN-q5L>#AX;)_Zi@Atb`pvJdi7 zZ#7Ss#oBr6+k&U)cPj2L?qh-k`yt;^VpQ5A=b95K2keg)g(z(j_Kf=LTqw|`T$eZz z0v@aXWm55w=}^)vGy39~-l5UAhl$jUP~E#L5+7TeMzTp4xXgdWiL z!q-pE)>xz;YqC74VrLNg2zXOEV=*`OD@g9_zH@nyF=h`YmmmSTiL=7Jd~?l*sMK($ zrx$26&Cj2Qp4GK9r}EEBb2&%Med$nY;U-s)1-TLUtG)Gm(>iQd9 zx&?=@@Rv~Ao2h9h4ZUzi-5;$TtQKH_7;x`5Uf|SUqv(&7;Pl}+Vv`EV9ZY%>8Yh7< z(+6R^aR73CUnxj`4JSY8G?s$ozr@kw6$& zaeze;i5&|aKA8PcHf}FWV{P=Zb#AK~$=3BCA=JD>V#ar!Iu}j(%Rw2TAYmn$ zso~Kyf9cD&UGU@zEHl9PKRs`02pJJ=IEHuILT^Pgrr(Ov661aT3H&Hd%=Gsc;xgpMk}^oJ+FHj?$Ucgu~&P)APpNH@p=S0H#ptsm-qiqix6 z3Ts$A)YmUal(-o;ar!IpG4*+54)IJG79&C?P;%iwvVB$E69c*X@L#>dU0s9>fY9!K zj<7Zf{Q0-z_TS$rQ2qB2-Ti;|H2{8&a5oOFi3M6>K<;`<+-v~|4`mPFJpTds?7sUx z5%5@Ax-&x!)KiR~;(+fSca1-};Q`yDQKhBwhCX*MnC>Qq{)Ypg?BYL#8Xyn~du@fE V$V#WQ3V@X$6$K6XO4-)|{}&_sdiekV From ed5101398599abd3edba6c29084ef04e76ab2c91 Mon Sep 17 00:00:00 2001 From: rachmari Date: Tue, 9 Aug 2022 16:36:02 +0000 Subject: [PATCH 28/41] Action ran graphql script"update-files" --- data/graphql/ghes-3.5/schema.docs-enterprise.graphql | 6 ++++++ lib/graphql/static/schema-ghes-3.5.json | 8 ++++++++ 2 files changed, 14 insertions(+) diff --git a/data/graphql/ghes-3.5/schema.docs-enterprise.graphql b/data/graphql/ghes-3.5/schema.docs-enterprise.graphql index a6c1edca7a..d981e1fe43 100644 --- a/data/graphql/ghes-3.5/schema.docs-enterprise.graphql +++ b/data/graphql/ghes-3.5/schema.docs-enterprise.graphql @@ -32385,6 +32385,12 @@ enum ReportedContentClassifiers { A repository contains the content for a project. """ type Repository implements Node & PackageOwner & ProjectOwner & RepositoryInfo & Starrable & Subscribable & UniformResourceLocatable { + """ + Whether or not a pull request head branch that is behind its base branch can + always be updated even if it is not required to be up to date before merging. + """ + allowUpdateBranch: Boolean! + """ A list of users that can be assigned to issues in this repository. """ diff --git a/lib/graphql/static/schema-ghes-3.5.json b/lib/graphql/static/schema-ghes-3.5.json index 52b18cf79b..c397bd6c48 100644 --- a/lib/graphql/static/schema-ghes-3.5.json +++ b/lib/graphql/static/schema-ghes-3.5.json @@ -45523,6 +45523,14 @@ } ], "fields": [ + { + "name": "allowUpdateBranch", + "description": "

Whether or not a pull request head branch that is behind its base branch can\nalways be updated even if it is not required to be up to date before merging.

", + "type": "Boolean!", + "id": "boolean", + "kind": "scalars", + "href": "/graphql/reference/scalars#boolean" + }, { "name": "assignableUsers", "description": "

A list of users that can be assigned to issues in this repository.

", From 04f38e4779effde49eac793f98ff692cf9a971a5 Mon Sep 17 00:00:00 2001 From: Kevin Heis Date: Tue, 9 Aug 2022 09:48:18 -0700 Subject: [PATCH 29/41] Parse color_mode cookie in browser (#29738) * Parse color_mode cookie in browser * Update useTheme.ts * Update use-theme.js * Update use-theme.js * Add support for dark_high_contrast Per https://primer.style/css/support/theming I also checked all the color mode options, this is the only additional working with Primer 20 so far * Remove gray bg * Remove type * Use defaults instead of types for fn args * Thicker types --- components/hooks/useSession.ts | 11 ---- components/hooks/useTheme.ts | 114 +++++++++++++++++++++++++++++++++ lib/get-theme.js | 66 ------------------- middleware/api/session.js | 3 - pages/_app.tsx | 22 +++---- stylesheets/index.scss | 6 -- tests/unit/get-theme.js | 80 ----------------------- tests/unit/use-theme.js | 39 +++++++++++ 8 files changed, 163 insertions(+), 178 deletions(-) create mode 100644 components/hooks/useTheme.ts delete mode 100644 lib/get-theme.js delete mode 100644 tests/unit/get-theme.js create mode 100644 tests/unit/use-theme.js diff --git a/components/hooks/useSession.ts b/components/hooks/useSession.ts index f9119798a1..7bbbfaaca9 100644 --- a/components/hooks/useSession.ts +++ b/components/hooks/useSession.ts @@ -1,4 +1,3 @@ -import type { ThemeProviderProps } from '@primer/react' import { useEffect } from 'react' import useSWR from 'swr' @@ -14,16 +13,6 @@ export type Session = { isSignedIn: boolean csrfToken?: string userLanguage: string // en, es, ja, cn - theme: { - colorMode: Pick - nightTheme: string - dayTheme: string - } - themeCss: { - colorMode: Pick - nightTheme: string - dayTheme: string - } } // React hook version diff --git a/components/hooks/useTheme.ts b/components/hooks/useTheme.ts new file mode 100644 index 0000000000..b8134a0e57 --- /dev/null +++ b/components/hooks/useTheme.ts @@ -0,0 +1,114 @@ +import { useState, useEffect } from 'react' +import Cookies from 'js-cookie' + +enum CssColorMode { + auto = 'auto', + light = 'light', + dark = 'dark', +} + +enum ComponentColorMode { + auto = 'auto', + day = 'day', + night = 'night', +} + +enum SupportedTheme { + light = 'light', + dark = 'dark', + dark_dimmed = 'dark_dimmed', + dark_high_contrast = 'dark_high_contrast', +} + +type CssColorTheme = { + colorMode: CssColorMode + lightTheme: SupportedTheme + darkTheme: SupportedTheme +} + +type ComponentColorTheme = { + colorMode: ComponentColorMode + dayScheme: SupportedTheme + nightScheme: SupportedTheme +} + +type ColorModeThemes = { + css: CssColorTheme + component: ComponentColorTheme +} + +export const defaultCSSTheme: CssColorTheme = { + colorMode: CssColorMode.auto, + lightTheme: SupportedTheme.light, + darkTheme: SupportedTheme.dark, +} + +export const defaultComponentTheme: ComponentColorTheme = { + colorMode: ComponentColorMode.auto, + dayScheme: SupportedTheme.light, + nightScheme: SupportedTheme.dark, +} + +const cssColorModeToComponentColorMode: Record = { + [CssColorMode.auto]: ComponentColorMode.auto, + [CssColorMode.light]: ComponentColorMode.day, + [CssColorMode.dark]: ComponentColorMode.night, +} + +function filterMode(mode = ''): CssColorMode | undefined { + if (Object.values(CssColorMode).includes(mode)) { + return mode as CssColorMode + } +} + +function filterTheme({ name = '', color_mode = '' } = {}): SupportedTheme | undefined { + if (Object.values(SupportedTheme).includes(name)) { + return name as SupportedTheme + } + if (Object.values(SupportedTheme).includes(color_mode)) { + return color_mode as SupportedTheme + } +} + +export function getCssTheme(cookieValue = ''): CssColorTheme { + if (!cookieValue) return defaultCSSTheme + try { + const parsed = JSON.parse(cookieValue) + const { color_mode, light_theme, dark_theme } = parsed + return { + colorMode: filterMode(color_mode) || defaultCSSTheme.colorMode, + lightTheme: filterTheme(light_theme) || defaultCSSTheme.lightTheme, + darkTheme: filterTheme(dark_theme) || defaultCSSTheme.darkTheme, + } + } catch (err) { + console.warn("Unable to parse 'color_mode' cookie", err) + return defaultCSSTheme + } +} + +export function getComponentTheme(cookieValue = ''): ComponentColorTheme { + const { colorMode, lightTheme, darkTheme } = getCssTheme(cookieValue) + return { + // The cookie value is a primer/css color_mode. + // We need to convert that to a primer/react compatible version. + colorMode: cssColorModeToComponentColorMode[colorMode], + dayScheme: lightTheme, + nightScheme: darkTheme, + } +} + +export function useTheme() { + const [theme, setTheme] = useState({ + css: defaultCSSTheme, + component: defaultComponentTheme, + }) + + useEffect(() => { + const cookieValue = Cookies.get('color_mode') + const css = getCssTheme(cookieValue) + const component = getComponentTheme(cookieValue) + setTheme({ css, component }) + }, []) + + return { theme } +} diff --git a/lib/get-theme.js b/lib/get-theme.js deleted file mode 100644 index a4b9b964dc..0000000000 --- a/lib/get-theme.js +++ /dev/null @@ -1,66 +0,0 @@ -export const defaultCSSTheme = { - colorMode: 'auto', // light, dark, auto - nightTheme: 'dark', - dayTheme: 'light', -} - -export const defaultComponentTheme = { - colorMode: 'auto', // day, night, auto - nightTheme: 'dark', - dayTheme: 'light', -} - -const cssColorModeToComponentColorMode = { - auto: 'auto', - light: 'day', - dark: 'night', -} - -const supportedThemes = ['light', 'dark', 'dark_dimmed'] - -/* - * Our version of primer/css is out of date, so we can only support known themes. - * For the least jarring experience possible, we fallback to the color_mode (light / dark) if provided by the theme, otherwise our own defaults - */ -function getSupportedTheme(theme, fallbackTheme) { - if (!theme) { - return fallbackTheme - } - - return supportedThemes.includes(theme.name) ? theme.name : theme.color_mode -} - -/* - * Returns theme for consumption by either primer/css or primer/components - * based on the cookie and/or fallback values - */ -export function getTheme(req, cssMode = false) { - const cookieValue = {} - - const defaultTheme = cssMode ? defaultCSSTheme : defaultComponentTheme - - if (req.cookies?.color_mode) { - try { - const parsed = JSON.parse(decodeURIComponent(req.cookies.color_mode)) - cookieValue.color_mode = parsed.color_mode - cookieValue.dark_theme = parsed.dark_theme - cookieValue.light_theme = parsed.light_theme - } catch (err) { - if (process.env.NODE_ENV !== 'test') { - console.warn("Unable to parse 'color_mode' cookie", err) - } - } - } - - // The cookie value is a primer/css color_mode. sometimes we need to convert that to a primer/components compatible version - const colorMode = - (cssMode - ? cookieValue.color_mode - : cssColorModeToComponentColorMode[cookieValue.color_mode || '']) || defaultTheme.colorMode - - return { - colorMode, - nightTheme: getSupportedTheme(cookieValue.dark_theme, defaultTheme.nightTheme), - dayTheme: getSupportedTheme(cookieValue.light_theme, defaultTheme.dayTheme), - } -} diff --git a/middleware/api/session.js b/middleware/api/session.js index c6d5e65ea8..4fe5d86f5c 100644 --- a/middleware/api/session.js +++ b/middleware/api/session.js @@ -1,5 +1,4 @@ import express from 'express' -import { getTheme } from '../../lib/get-theme.js' import { cacheControlFactory } from '../cache-control.js' const router = express.Router() @@ -11,8 +10,6 @@ router.get('/', (req, res) => { isSignedIn: Boolean(req.cookies?.dotcom_user), csrfToken: req.csrfToken?.() || '', userLanguage: req.userLanguage, - theme: getTheme(req), - themeCss: getTheme(req, true), }) }) diff --git a/pages/_app.tsx b/pages/_app.tsx index 24d691f143..bb9a4597b7 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -2,7 +2,7 @@ import React, { useEffect } from 'react' import App from 'next/app' import type { AppProps, AppContext } from 'next/app' import Head from 'next/head' -import { ThemeProvider, SSRProvider, ThemeProviderProps } from '@primer/react' +import { ThemeProvider, SSRProvider } from '@primer/react' import '../stylesheets/index.scss' @@ -10,16 +10,17 @@ import { initializeEvents } from 'components/lib/events' import experiment from 'components/lib/experiment' import { LanguagesContext, LanguagesContextT } from 'components/context/LanguagesContext' import { useSession } from 'components/hooks/useSession' +import { useTheme } from 'components/hooks/useTheme' type MyAppProps = AppProps & { isDotComAuthenticated: boolean languagesContext: LanguagesContextT } -type colorModeAuto = Pick - const MyApp = ({ Component, pageProps, languagesContext }: MyAppProps) => { const { session } = useSession() + const { theme } = useTheme() + useEffect(() => { if (session?.csrfToken) { initializeEvents(session.csrfToken) @@ -54,18 +55,15 @@ const MyApp = ({ Component, pageProps, languagesContext }: MyAppProps) => { {/* Appears Next.js can't modify after server rendering: https://stackoverflow.com/a/54774431 */}
diff --git a/stylesheets/index.scss b/stylesheets/index.scss index a4f3e1b7b7..d4f295dc41 100644 --- a/stylesheets/index.scss +++ b/stylesheets/index.scss @@ -13,9 +13,3 @@ @import "shadows.scss"; @import "syntax-highlighting.scss"; @import "utilities.scss"; - -// render a mostly gray background until we know the color mode via XHR -html, -body { - background: #6e7781; -} diff --git a/tests/unit/get-theme.js b/tests/unit/get-theme.js deleted file mode 100644 index aba0a20bcb..0000000000 --- a/tests/unit/get-theme.js +++ /dev/null @@ -1,80 +0,0 @@ -import { describe, expect, test } from '@jest/globals' - -import { getTheme, defaultCSSTheme, defaultComponentTheme } from '../../lib/get-theme.js' - -function serializeCookieValue(obj) { - return encodeURIComponent(JSON.stringify(obj)) -} - -describe('getTheme basics', () => { - test('always return an object with certain keys', () => { - const req = {} // doesn't even have a `.cookies`. - const theme = getTheme(req) - expect(theme.colorMode).toBe(defaultComponentTheme.colorMode) - expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) - expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) - const cssTheme = getTheme(req, true) - expect(cssTheme.colorMode).toBe(defaultCSSTheme.colorMode) - expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) - expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) - }) - - test('respect the color_mode cookie value', () => { - const req = { - cookies: { - color_mode: serializeCookieValue({ - color_mode: 'dark', - light_theme: { name: 'light_colorblind', color_mode: 'light' }, - dark_theme: { name: 'dark_tritanopia', color_mode: 'dark' }, - }), - }, - } - const theme = getTheme(req) - expect(theme.colorMode).toBe('night') - expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) - expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) - - const cssTheme = getTheme(req, true) - expect(cssTheme.colorMode).toBe('dark') - expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) - expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) - }) - - test('respect the color_mode cookie value', () => { - const req = { - cookies: { - color_mode: serializeCookieValue({ - color_mode: 'dark', - light_theme: { name: 'light_colorblind', color_mode: 'light' }, - dark_theme: { name: 'dark_tritanopia', color_mode: 'dark' }, - }), - }, - } - const theme = getTheme(req) - expect(theme.colorMode).toBe('night') - expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) - expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) - - const cssTheme = getTheme(req, true) - expect(cssTheme.colorMode).toBe('dark') - expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) - expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) - }) - - test('ignore "junk" cookie values', () => { - const req = { - cookies: { - color_mode: '[This is not valid JSON}', - }, - } - const theme = getTheme(req) - expect(theme.colorMode).toBe('auto') - expect(theme.nightTheme).toBe(defaultComponentTheme.nightTheme) - expect(theme.dayTheme).toBe(defaultComponentTheme.dayTheme) - - const cssTheme = getTheme(req, true) - expect(cssTheme.colorMode).toBe('auto') - expect(cssTheme.nightTheme).toBe(defaultCSSTheme.nightTheme) - expect(cssTheme.dayTheme).toBe(defaultCSSTheme.dayTheme) - }) -}) diff --git a/tests/unit/use-theme.js b/tests/unit/use-theme.js new file mode 100644 index 0000000000..76b050c36d --- /dev/null +++ b/tests/unit/use-theme.js @@ -0,0 +1,39 @@ +import { describe, expect, test } from '@jest/globals' +import { + getComponentTheme, + getCssTheme, + defaultCSSTheme, + defaultComponentTheme, +} from '../../components/hooks/useTheme.ts' + +describe('getTheme basics', () => { + test('always return an object with certain keys', () => { + const cookieValue = JSON.stringify({}) + expect(getCssTheme(cookieValue)).toEqual(defaultCSSTheme) + expect(getComponentTheme(cookieValue)).toEqual(defaultComponentTheme) + }) + + test('ignore "junk" cookie values', () => { + const cookieValue = '[This is not valid JSON}' + expect(getCssTheme(cookieValue)).toEqual(defaultCSSTheme) + expect(getComponentTheme(cookieValue)).toEqual(defaultComponentTheme) + }) + + test('respect the color_mode cookie value', () => { + const cookieValue = JSON.stringify({ + color_mode: 'dark', + light_theme: { name: 'light_colorblind', color_mode: 'light' }, + dark_theme: { name: 'dark_tritanopia', color_mode: 'dark' }, + }) + + const cssTheme = getCssTheme(cookieValue) + expect(cssTheme.colorMode).toBe('dark') + expect(cssTheme.darkTheme).toBe(defaultCSSTheme.darkTheme) + expect(cssTheme.lightTheme).toBe(defaultCSSTheme.lightTheme) + + const componentTheme = getComponentTheme(cookieValue) + expect(componentTheme.colorMode).toBe('night') + expect(componentTheme.nightScheme).toBe(defaultComponentTheme.nightScheme) + expect(componentTheme.dayScheme).toBe(defaultComponentTheme.dayScheme) + }) +}) From 897c519a88823fcf94905967d32f7da27faa2660 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 9 Aug 2022 14:01:22 -0400 Subject: [PATCH 30/41] New translation batch for pt (#29760) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt * run script/i18n/reset-known-broken-translation-files.js --- .../about-saml-for-enterprise-iam.md | 2 + ...saml-single-sign-on-for-your-enterprise.md | 6 +- .../overview/about-enterprise-accounts.md | 2 +- ...adding-organizations-to-your-enterprise.md | 3 +- ...authentication-with-saml-single-sign-on.md | 17 +- .../about-dependabot-alerts.md | 4 +- .../github-security-features.md | 23 +- .../securing-your-organization.md | 2 +- .../securing-your-repository.md | 2 +- .../secret-scanning/about-secret-scanning.md | 2 +- .../about-the-security-overview.md | 2 +- ...ltering-alerts-in-the-security-overview.md | 4 + .../viewing-the-security-overview.md | 2 + ...loring-the-dependencies-of-a-repository.md | 2 +- .../about-github-advanced-security.md | 22 +- .../guides/forming-calls-with-graphql.md | 1 - .../repository-roles-for-an-organization.md | 198 +++++++++--------- ...ess-management-with-saml-single-sign-on.md | 6 +- ...eleting-branches-within-your-repository.md | 4 + .../searching-for-repositories.md | 2 +- .../features/create-branch-from-overview.yml | 5 + .../security-overview-displayed-alerts.yml | 6 + .../gated-features/advanced-security.md | 1 - .../data/reusables/gated-features/ghas.md | 2 +- .../gated-features/security-overview.md | 13 +- .../reusables/saml/dotcom-saml-explanation.md | 2 +- .../saml/outside-collaborators-exemption.md | 5 +- .../data/reusables/saml/saml-accounts.md | 6 +- .../information-varies-GHAS.md | 3 + 29 files changed, 195 insertions(+), 154 deletions(-) create mode 100644 translations/pt-BR/data/features/create-branch-from-overview.yml create mode 100644 translations/pt-BR/data/features/security-overview-displayed-alerts.yml delete mode 100644 translations/pt-BR/data/reusables/gated-features/advanced-security.md create mode 100644 translations/pt-BR/data/reusables/security-overview/information-varies-GHAS.md diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index caa0c8422c..9b28a36084 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: Se os integrantes da sua empresa gerenciarem suas próprias contas de usuários em {% data variables.product.product_location %}, você pode configurar a autenticação SAML como uma restrição de acesso adicional para sua empresa ou organização. {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %} Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". Como alternativa, você pode fornecer e gerenciar as contas dos integrantes da empresa com {% data variables.product.prodname_emus %}. Para ajudar você a determinar se o SAML SSO ou {% data variables.product.prodname_emus %} é melhor para sua empresa, consulte "[Sobre autenticação para sua empresa](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)". diff --git a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index e1e22d96b1..475993a461 100644 --- a/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +Para obter mais informações, consulte "[Sobre identidade e gerenciamento de acesso com o logon único SAML](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)". {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md index 0684008d97..7747911da6 100644 --- a/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md +++ b/translations/pt-BR/content/admin/overview/about-enterprise-accounts.md @@ -35,7 +35,7 @@ A conta corporativa em {% ifversion ghes %}{% data variables.product.product_loc As organizações são contas compartilhadas em que os integrantes da empresa podem colaborar em muitos projetos de uma só vez. Os proprietários da organização podem gerenciar o acesso aos dados e projetos da organização, com recursos sofisticados de segurança e administrativos. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". {% ifversion ghec %} -Os proprietários da empresa podem convidar organizações existentes para participar da conta corporativa ou criar novas organizações nas configurações da empresa. +Os proprietários da empresa podem convidar organizações existentes para participar da conta corporativa ou criar novas organizações nas configurações da empresa. Para obter mais informações, consulte "[Adicionando organizações à sua empresa](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)". {% endif %} Sua conta corporativa permite que você gerencie e aplique as políticas para todas as organizações pertencentes à empresa. {% data reusables.enterprise.about-policies %} Para obter mais informações, consulte "[Sobre as políticas corporativas](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)". diff --git a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 97b773256e..f7ccf9516e 100644 --- a/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/pt-BR/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,13 +14,14 @@ topics: - Enterprise - Organizations shortTitle: Adicionar organizações +permissions: Enterprise owners can add organizations to an enterprise. --- ## Sobre organizações Sua conta corporativa pode ser proprietária de organizações. Os integrantes da sua empresa podem colaborar em projetos relacionados dentro de uma organização. Para obter mais informações, consulte "[Sobre organizações](/organizations/collaborating-with-groups-in-organizations/about-organizations)". -Os proprietários corporativos podem criar novas organizações dentro das configurações de uma conta corporativa ou convidar organizações existentes para participar de uma empresa. Para adicionar uma organização à sua empresa, você deve criar a organização dentro das configurações de conta corporativa. +You can add a new or existing organization to your enterprise in your enterprise account's settings. Você só pode adicionar organizações dessa forma a uma conta corporativa existente. {% data reusables.enterprise.create-an-enterprise-account %} Para obter mais informações, consulte "[Criando uma conta corporativa](/admin/overview/creating-an-enterprise-account)". diff --git a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index 1a7053f70d..cd8382cf43 100644 --- a/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: Sobre a autenticação com SAML SSO -intro: 'Você pode acessar {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}uma organização que usa o logon único SAML (SSO){% endif %} efetuando a autenticação {% ifversion ghae %}com o logon único SAML (SSO) {% endif %}por meio de um provedor de identidade (IdP).{% ifversion ghec %} Depois de efetuar a autenticação com o IdP em {% data variables.product.product_name %}, você deverá autorizar qualquer token de acesso pessoal, Chave SSH, ou {% data variables.product.prodname_oauth_app %} que você gostaria de acessar os recursos da organização.{% endif %}' +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -29,10 +29,9 @@ Se você não puder acessar {% data variables.product.product_name %}, entre em {% data reusables.saml.dotcom-saml-explanation %} Os proprietários da organização podem convidar sua conta pessoal em {% data variables.product.prodname_dotcom %} para participar da organização que usa o SSO SAML, o que permite que você contribua com a organização e mantenha sua identidade e contribuições existentes em {% data variables.product.prodname_dotcom %}. -Se você for integrante de um {% data variables.product.prodname_emu_enterprise %}, você usará uma nova conta que lhe será fornecida. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} - -Ao acessar os recursos dentro de uma organização que usa o SSO SAML, o {% data variables.product.prodname_dotcom %} irá redirecionar você para o SAML IdP da organização para que você efetue a autenticação. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização. +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. Depois de efetuar a autenticação com sucesso com sua conta no IdP, este irá redirecionar você de volta para {% data variables.product.prodname_dotcom %}, onde você poderá acessar os recursos da organização. {% data reusables.saml.outside-collaborators-exemption %} @@ -40,6 +39,16 @@ Se você efetuou a autenticação recentemente com o IdP SAML da sua organizaç {% data reusables.saml.you-must-periodically-authenticate %} +## Linked SAML identities + +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. + +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. Para obter mais informações, consulte "[Visualizar e gerenciar o acesso SAML de um integrante à sua organização](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)". + +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. + +## Authorizing PATs and SSH keys with SAML SSO + Para usar a API ou o Git na linha de comando de modo a acessar conteúdo protegido em uma organização que usa SAML SSO, você precisará usar um token de acesso pessoal autorizado por HTTPS ou uma chave SSH autorizada. Na falta de um token de acesso pessoal ou uma chave SSH, você poderá criar um token de acesso pessoal para a linha de comando ou gerar uma nova chave SSH. Para obter mais informações consulte "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token)ou "[Gerar uma nova chave SSH e adicioná-la ao ssh-agent-](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 6b4352fc15..f4cfa3a0fc 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -89,7 +89,7 @@ Para repositórios em que {% data variables.product.prodname_dependabot_security ## Acesso a {% data variables.product.prodname_dependabot_alerts %} -É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. Para obter mais informações, consulte "[Visualizando e atualizando {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." +É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente dependências inseguras para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} @@ -103,5 +103,5 @@ Você também pode ver todos os {% data variables.product.prodname_dependabot_al ## Leia mais - "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Visualizando e atualizando {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacidade em {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md index 3231640ddd..d2c67cbd77 100644 --- a/translations/pt-BR/content/code-security/getting-started/github-security-features.md +++ b/translations/pt-BR/content/code-security/getting-started/github-security-features.md @@ -57,8 +57,15 @@ O gráfico de dependências permite explorar os ecossistemas e pacotes dos quais Você pode encontrar o gráfico de dependências na aba **Ideias** para o seu repositório. Para obter mais informações, consulte "[Sobre o gráfico de dependência](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)". +{% ifversion security-overview-displayed-alerts %} +### Visão geral da segurança + +The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)". + +{% else %} ### Visão geral de segurança para repositórios -Para todos os repositórios públicos, a visão geral de segurança mostra quais funcionalidades de segurança estão habilitadas no repositório e oferece a opção de configurar quaisquer recursos de segurança disponíveis que não estão habilitadas no momento. +The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled. +{% endif %} ## Disponível com {% data variables.product.prodname_GH_advanced_security %} @@ -66,7 +73,7 @@ Para todos os repositórios públicos, a visão geral de segurança mostra quais As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} a seguir estão disponíveis e são grátos para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com uma licença para {% data variables.product.prodname_GH_advanced_security %} podem usar o conjunto completo de funcionalidades em qualquer um dos seus repositórios. Para obter uma lista dos recursos disponíveis com {% data variables.product.prodname_ghe_cloud %}, consulte a [a documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security). {% elsif ghec %} -Muitas funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão disponíveis e gratuitos para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações de uma empresa que tem uma licença {% data variables.product.prodname_GH_advanced_security %} podem usar todos as funcionalidades a seguir em seus repositórios. {% data reusables.advanced-security.more-info-ghas %} +Muitas funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão disponíveis e gratuitos para repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %} {% elsif ghes %} As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão disponíveis para empresas com uma licença para {% data variables.product.prodname_GH_advanced_security %}. As funcionalidades são restritas aos repositórios pertencentes a uma organização. {% data reusables.advanced-security.more-info-ghas %} @@ -85,7 +92,7 @@ Detectar automaticamente vulnerabilidades de segurança e erros de codificação Detectar automaticamente segredos vazados em todos os repositórios públicos. {% data variables.product.company_short %} informa ao provedor de serviços relevante que o segredo pode estar comprometido. Para obter detalhes dos segredos e provedores de serviço compatíveis, consulte "[ Padrões de {% data variables.product.prodname_secret_scanning_caps %}](/code-security/secret-scanning/secret-scanning-patterns)". {% endif %} -{% ifversion not fpt %} +{% ifversion ghec or ghes or ghae %} ### {% data variables.product.prodname_secret_scanning_GHAS_caps %} {% ifversion ghec %} @@ -99,12 +106,12 @@ Detectar automaticamente tokens ou credenciais que foram verificados em um repos Mostre o impacto completo das alterações nas dependências e veja detalhes de qualquer versão vulnerável antes de fazer merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". -{% ifversion ghec or ghes or ghae %} -### Visão geral de segurança das organizações{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, empresas,{% endif %} e equipes +{% ifversion security-overview-displayed-alerts %} -{% ifversion ghec %} -Disponível apenas com uma licença para {% data variables.product.prodname_GH_advanced_security %}. -{% endif %} +{% elsif fpt %} + +{% else %} +### Visão geral de segurança das organizações{% ifversion ghes > 3.4 or ghae-issue-6199 %}, empresas,{% endif %} e equipes Revise a configuração de segurança e os alertas para sua organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)". {% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md index 1734a2e421..06cfedff8b 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ Para obter mais informações, consulte "[Gerenciar configurações de seguranç {% data variables.product.prodname_code_scanning_capc %} está configurado no nível do repositório. Para obter mais informações, consulte "[Configurar {% data variables.product.prodname_code_scanning %} para um repositório](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)". ## Próximas etapas -Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes or ghec %} "[Visualizando e atualizando {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciando pull requests para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Gerenciando {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," e "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 27ae90a239..8f51da36a2 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ Você pode configurar {% data variables.product.prodname_code_scanning %} para i {% endif %} ## Próximas etapas -Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes or ghec %} "[Visualizando e atualizando {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciando pull requests para atualizações de dependência](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Gerenciando {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," e "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md index d6d8def31e..481ec138e4 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md @@ -91,7 +91,7 @@ For more information about viewing and resolving {% data variables.product.prodn Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -{% ifversion ghec or ghes %} +{% ifversion ghec or ghes or ghae-issue-5503 %} You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)." {% endif %} diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md index f22323a795..69b1ffa8c6 100644 --- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ No resumo da segurança, é possível visualizar, ordenar e filtrar alertas para {% ifversion security-overview-views %} -Na visão geral de segurança, tanto ao nível da organização como ao nível do repositório. existem visualizações dedicadas a recursos de segurança específicos, como alertas de digitalização de segredos e alertas de digitalização de código. Você pode usar essas visualizações para limitar sua análise para um conjunto específico de alertas e estreitar os resultados com uma variedade de filtros específicos para cada visualização. Por exemplo, na vista de alerta de digitalização de segredo, você pode usar o filtro do tipo `secredo` para visualizar somente alertas de digitalização de segredo para um segredo específico, como um Token de Acesso Pessoal do GitHub. No nível do repositório, é possível usar a visão geral de segurança para avaliar o status de segurança atual do repositório específico e configurar todos as funcionalidades adicionais de segurança que ainda não estão sendo usadas no repositório. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. Você pode usar essas visualizações para limitar sua análise para um conjunto específico de alertas e estreitar os resultados com uma variedade de filtros específicos para cada visualização. Por exemplo, na vista de alerta de digitalização de segredo, você pode usar o filtro do tipo `secredo` para visualizar somente alertas de digitalização de segredo para um segredo específico, como um Token de Acesso Pessoal do GitHub. No nível do repositório, é possível usar a visão geral de segurança para avaliar o status de segurança atual do repositório específico e configurar todos as funcionalidades adicionais de segurança que ainda não estão sendo usadas no repositório. {% endif %} diff --git a/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index f7a823e08f..a9b5fb756b 100644 --- a/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -25,6 +25,10 @@ shortTitle: Filtrando alertas Você pode usar filtros na visão geral de segurança para restringir seu foco baseado em uma série de fatores como, por exemplo, o nível de risco de alerta, tipo de alerta e habilitação do recurso. Diferentes filtros estão disponíveis dependendo da exibição específica e se sua análise está no nível de organização, equipe ou repositório. +{% note %} +{% data reusables.security-overview.information-varies-GHAS %} +{% endnote %} + ## Filtrar por repositório Disponível em todos os níveis da organização e no nível da equipe. diff --git a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md index ca2a53f71b..26cc24e7d0 100644 --- a/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/viewing-the-security-overview.md @@ -21,6 +21,8 @@ shortTitle: Ver visão geral de segurança {% data reusables.security-overview.beta %} {% endif %} +{% data reusables.security-overview.information-varies-GHAS %} + ## Visualizar a visão geral de segurança de uma organização {% data reusables.organizations.navigate-to-org %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index cdcc872f2d..db6d2bf666 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -110,7 +110,7 @@ Se um arquivo de manifesto ou de bloqueio não for processado, suas dependência ## Leia mais - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Visualizando e atualizando {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - "[Visualizando insights para a sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}{% ifversion fpt or ghec %} - "[Entender como o {% data variables.product.prodname_dotcom %} usa e protege seus dados](/get-started/privacy-on-github)" {% endif %} 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 f8f71dfca2..fc8bc403c3 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 @@ -33,36 +33,28 @@ Uma licença de {% data variables.product.prodname_GH_advanced_security %} forne - **Revisão de dependências** - Mostra o impacto total das alterações nas dependências e vê detalhes de qualquer versão vulnerável antes de realizar o merge de um pull request. Para obter mais informações, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/about-dependency-review)". -{% ifversion ghec or ghes %} +{% ifversion ghes < 3.7 or ghae %} + - **Visão geral de segurança** - Revise a configuração de segurança e os alertas para uma organização e identifique os repositórios com maior risco. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)". {% endif %} {% ifversion fpt or ghec %} -A tabela abaixo resume a disponibilidade de funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para repositórios públicos e privados. |{% ifversion fpt %} +A tabela abaixo resume a disponibilidade de funcionalidades de {% data variables.product.prodname_GH_advanced_security %} para repositórios públicos e privados. + | | Repositório público | Repositório privado sem {% data variables.product.prodname_advanced_security %} | Repositório privado com {% data variables.product.prodname_advanced_security %} |:----------------------:|:----------------------------------------:|:---------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| | Varredura de código | Sim | Não | Sim | | Varredura secreta | Sim **(apenas funcionalidade limitada)** | Não | Sim | -| Revisão de dependência | Sim | Não | Sim |{% endif %} -| -{% ifversion ghec %} -| | Repositório público | Repositório privado sem {% data variables.product.prodname_advanced_security %} | Repositório privado com {% data variables.product.prodname_advanced_security %} -|:------------------------:|:----------------------------------------:|:---------------------------------------------------------------------------------:|:---------------------------------------------------------------------------------:| -| Varredura de código | Sim | Não | Sim | -| Varredura secreta | Sim **(apenas funcionalidade limitada)** | Não | Sim | -| Revisão de dependência | Sim | Não | Sim | -| Visão geral da segurança | Não | Não | Sim | -{% endif %} - +| Revisão de dependência | Sim | Não | Sim | {% endif %} Para obter informações sobre funcionalidades de {% data variables.product.prodname_advanced_security %} em desenvolvimento, consulte "[Plano de trabalho de {% data variables.product.prodname_dotcom %}](https://github.com/github/roadmap)". Para uma visão geral de todas as funcionalidades de segurança, consulte "[ funcionalidades de segurança de{% data variables.product.prodname_dotcom %}](/code-security/getting-started/github-security-features)". {% ifversion fpt or ghec %} -As funcionalidades de{% data variables.product.prodname_GH_advanced_security %} estão habilitadas para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, exceto para a visão geral de segurança{% endif %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. Elas também têm acesso a uma visão geral de segurança no nível da organização. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +As funcionalidades de {% data variables.product.prodname_GH_advanced_security %} estão habilitadas para todos os repositórios públicos em {% data variables.product.prodname_dotcom_the_website %}. As organizações que usam {% data variables.product.prodname_ghe_cloud %} com {% data variables.product.prodname_advanced_security %} também podem habilitar essas funcionalidades para repositórios internos e privados. {% ifversion fpt %}Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} -{% ifversion ghes > 3.1 or ghec %} +{% ifversion ghes > 3.1 or ghec or ghae %} ## Implantando o GitHub Advanced Security na sua empresa Para saber mais sobre o que você precisa saber para planejar a sua implantação de {% data variables.product.prodname_GH_advanced_security %} em um nível alto e para revisar as fases de implementação recomendadas, consulte "[Adotando {% data variables.product.prodname_GH_advanced_security %} em escala](/code-security/adopting-github-advanced-security-at-scale)". diff --git a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md index 3d96ecb5b8..a4b827b838 100644 --- a/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/pt-BR/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ Recomendam-se os escopos a seguir: ``` repo -repo_deployment read:packages read:org read:public_key diff --git a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 422da88145..52e7cc63ba 100644 --- a/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -60,123 +60,123 @@ Algumas das funcionalidades listadas abaixo estão limitadas a organizações qu {% endnote %} {% endif %} -| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:-------------------------------------------------------------------:| -| Gerencie o acesso ao repositório de [equipes](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [individuais](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) e [colaboradores externos](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **X** | **X** | **X** | **X** | **X** | -| Editar e excluir seus próprios comentários | **X** | **X** | **X** | **X** | **X** | -| Criar problemas | **X** | **X** | **X** | **X** | **X** | -| Fechar os problemas que eles criaram | **X** | **X** | **X** | **X** | **X** | -| Reabrir problemas que eles fecharam | **X** | **X** | **X** | **X** | **X** | -| Ter um problema atribuído a eles | **X** | **X** | **X** | **X** | **X** | -| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **X** | **X** | **X** | **X** | **X** | -| Enviar revisões em pull requests | **X** | **X** | **X** | **X** | **X** | -| Exibir as versões publicadas | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **X** | **X** | **X** | **X** | **X** +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:--------:|:----------:|:--------------------------------------------------------------------:| +| Gerencie o acesso ao repositório de [equipes](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository), [individuais](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository) e [colaboradores externos](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| Fazer pull nos repositórios atribuídos ao usuário ou à equipe | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Bifurcar os repositórios atribuídos ao usuário ou à equipe | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Editar e excluir seus próprios comentários | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Criar problemas | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Fechar os problemas que eles criaram | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Reabrir problemas que eles fecharam | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Ter um problema atribuído a eles | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Enviar pull requests de bifurcações dos repositórios atribuídos à equipe | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Enviar revisões em pull requests | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Exibir as versões publicadas | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Visualizar [execuções de fluxo de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| Editar wikis em repositórios públicos | **X** | **X** | **X** | **X** | **X** | -| Editar wikis em repositórios privados | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| Editar wikis em repositórios públicos | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Editar wikis em repositórios privados | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [Denunciar conteúdo abusivo ou spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| Aplicar/ignorar etiquetas | | **X** | **X** | **X** | **X** | -| Criar, editar, excluir etiquetas | | | **X** | **X** | **X** | -| Fechar, reabrir e atribuir todos os problemas e pull requests | | **X** | **X** | **X** | **X** | -| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| Aplicar marcos | | **X** | **X** | **X** | **X** | -| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **X** | **X** | **X** | **X** | -| Solicitar [revisões de pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **X** | **X** | **X** | **X** | -| Fazer merge de um [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **X** | **X** | **X** | -| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **X** | **X** | **X** | -| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **X** | **X** | **X** | -| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **X** | **X** | **X** | -| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [Marcar uma pull request de rascunho como pronta para revisão](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [Converter um pull request em rascunho](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **X** | **X** | **X** | -| [Aplicar alterações sugeridas](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) a pull requests | | | **X** | **X** | **X** | -| Criar [verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **X** | **X** | **X** +| Aplicar/ignorar etiquetas | | **✔️** | **✔️** | **✔️** | **✔️** | +| Criar, editar, excluir etiquetas | | | **✔️** | **✔️** | **✔️** | +| Fechar, reabrir e atribuir todos os problemas e pull requests | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Habilitar e desabilitar o merge automático em um pull request](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| Aplicar marcos | | **✔️** | **✔️** | **✔️** | **✔️** | +| Marcar [problemas e pull requests duplicados](/articles/about-duplicate-issues-and-pull-requests) | | **✔️** | **✔️** | **✔️** | **✔️** | +| Solicitar [revisões de pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) | | **✔️** | **✔️** | **✔️** | **✔️** | +| Fazer merge de um [pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges) | | | **✔️** | **✔️** | **✔️** | +| Fazer push (gravar) nos repositórios atribuídos ao usuário ou à equipe | | | **✔️** | **✔️** | **✔️** | +| Editar e excluir comentários de qualquer usuário em commits, pull request e problemas | | | **✔️** | **✔️** | **✔️** | +| [Ocultar comentários de qualquer usuário](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [Bloquear conversas](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Transferir problemas (consulte "[Transferir um problema para outro repositório](/articles/transferring-an-issue-to-another-repository)" para obter mais informações) | | | **✔️** | **✔️** | **✔️** | +| [Atuar como um proprietário do código designado de um repositório](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [Marcar uma pull request de rascunho como pronta para revisão](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [Converter um pull request em rascunho](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| Enviar revisões que afetam a capacidade de merge de uma pull request | | | **✔️** | **✔️** | **✔️** | +| [Aplicar alterações sugeridas](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) a pull requests | | | **✔️** | **✔️** | **✔️** | +| Criar [verificações de status](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks) | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Criar, editar, executar, reexecutar e cancelar [fluxos de trabalho no GitHub Actions](/actions/automating-your-workflow-with-github-actions/) | | | **✔️** | **✔️** | **✔️** {% endif %} -| Criar e editar versões | | | **X** | **X** | **X** | -| Exibir versões de rascunho | | | **X** | **X** | **X** | -| Editar a descrição de um repositório | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [Excluir e restaurar pacotes](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** |{% endif %} -| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **X** | **X** | -| Habilitar wikis e restringir editores de wiki | | | | **X** | **X** | -| Habilitar quadros de projeto | | | | **X** | **X** | -| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **X** | **X** | -| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **X** | **X** | -| [Gerenciar regras de proteção do branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **X** | **X** | -| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| Criar tags que correspondam a uma [regra de proteção de tags](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **X** | **X** | -| Excluir tags que correspondam a uma [ regra de proteção de tags](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **X** +| Criar e editar versões | | | **✔️** | **✔️** | **✔️** | +| Exibir versões de rascunho | | | **✔️** | **✔️** | **✔️** | +| Editar a descrição de um repositório | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [Visualizar e instalar pacotes](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Publicar pacotes](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [Excluir e restaurar pacotes](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** |{% endif %} +| Gerenciar [tópicos](/articles/classifying-your-repository-with-topics) | | | | **✔️** | **✔️** | +| Habilitar wikis e restringir editores de wiki | | | | **✔️** | **✔️** | +| Habilitar quadros de projeto | | | | **✔️** | **✔️** | +| Configurar [merges de pull request](/articles/configuring-pull-request-merges) | | | | **✔️** | **✔️** | +| Configurar [uma fonte de publicação para {% data variables.product.prodname_pages %}](/articles/configuring-a-publishing-source-for-github-pages) | | | | **✔️** | **✔️** | +| [Gerenciar regras de proteção do branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [Fazer push em branches protegidos](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| Fazer merge de pull requests em branches protegidos, mesmo sem revisões de aprovação | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| Criar tags que correspondam a uma [regra de proteção de tags](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | **✔️** | **✔️** | +| Excluir tags que correspondam a uma [ regra de proteção de tags](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules) | | | | | **✔️** {% endif %} -| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **X** | **X** +| [Criar e editar cartões sociais do repositório](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| Limitar [interações em um repositório](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) | | | | **✔️** | **✔️** {% endif %} -| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **X** | -| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **X** | -| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **X** | -| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **X** | -| Alterar as configurações do repositório | | | | | **X** | -| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **X** | -| Editar o branch padrão do repositório | | | | | **X** | -| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **X** | -| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | **X** | **X** | **X** | -| Gerenciar webhooks e chaves de implantação | | | | | **X** |{% ifversion fpt or ghec %} -| [Gerenciar as configurações do uso de dados para seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Excluir um problema (consulte "[Excluir um problema](/articles/deleting-an-issue)") | | | | | **✔️** | +| [Definir os proprietários do código de um repositório](/articles/about-code-owners) | | | | | **✔️** | +| Adicionar um repositório a uma equipe (consulte "[Gerenciar o acesso da equipe ao repositório de uma organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)" para obter informações) | | | | | **✔️** | +| [Gerenciar o acesso dos colaboradores externos a um repositório](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [Alterar a visibilidade de um repositório](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| Criar um modelo de repositório (consulte "[Criar um modelo de repositório](/articles/creating-a-template-repository)") | | | | | **✔️** | +| Alterar as configurações do repositório | | | | | **✔️** | +| Gerenciar o acesso de equipe e de colaborador ao repositório | | | | | **✔️** | +| Editar o branch padrão do repositório | | | | | **✔️** | +| Renomeie o branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | | | **✔️** | +| Renomeie um branch diferente do branch padrão do repositório (veja "[Renomear um branch](/github/administering-a-repository/renaming-a-branch)") | | | **✔️** | **✔️** | **✔️** | +| Gerenciar webhooks e chaves de implantação | | | | | **✔️** |{% ifversion fpt or ghec %} +| [Gerenciar as configurações do uso de dados para seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** {% endif %} -| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **X** +| [Gerenciar a política de bifurcação de um repositório](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [Transferir repositório na organização](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [Excluir ou transferir repositórios na organização](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [Arquivar repositórios](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| Exibir um botão de patrocinador (consulte "[Exibir um botão de patrocinador no seu repositório](/articles/displaying-a-sponsor-button-in-your-repository)") | | | | | **✔️** {% endif %} -| Crie referências autolink para recursos externos, como Jira ou Zendesk (consulte "[Configurando links automáticos para fazer referência a recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **X** |{% ifversion discussions %} -| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **X** | **X** | -| [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) para {% data variables.product.prodname_discussions %} | | | | **X** | **X** | -| [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions) para um novo repositório | | | **X** | **X** | **X** | -| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| Crie [codespaces](/codespaces/about-codespaces) | | | **X** | **X** | **X** +| Crie referências autolink para recursos externos, como Jira ou Zendesk (consulte "[Configurando links automáticos para fazer referência a recursos externos](/articles/configuring-autolinks-to-reference-external-resources)") | | | | | **✔️** |{% ifversion discussions %} +| [Habilitar {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) em um repositório | | | | **✔️** | **✔️** | +| [Criar e editar categorias](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) para {% data variables.product.prodname_discussions %} | | | | **✔️** | **✔️** | +| [Mover uma discussão para uma categoria diferente](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Transferir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions) para um novo repositório | | | **✔️** | **✔️** | **✔️** | +| [Gerenciar discussões fixadas](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Converter problemas para discussões em massa](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Bloquear e desbloquear discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Converter individualmente problemas em discussões](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Criar novas discussões e comentar em discussões existentes](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Excluir uma discussão](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Crie [codespaces](/codespaces/about-codespaces) | | | **✔️** | **✔️** | **✔️** {% endif %} ### Requisitos de acesso para funcionalidades de segurança Nesta seção, você pode encontrar o acesso necessário para as funcionalidades de segurança, como as funcionalidades de {% data variables.product.prodname_advanced_security %}. -| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | -|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:| -| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências inseguras](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **X** | -| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} +| Ação no repositório | Leitura | Triagem | Gravação | Manutenção | Administrador | +|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-------:|:-------:|:-------------------------------------------------------:|:-------------------------------------------------------:|:--------------------------------------------------------------------------------------------------:| +| Receber [{% data variables.product.prodname_dependabot_alerts %} para dependências inseguras](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) em um repositório | | | | | **✔️** | +| [Ignorar {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [Designe outras pessoas ou equipes para receber alertas de segurança](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designe outras pessoas ou equipes para receber alertas de segurança](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| Criar [consultorias de segurança](/code-security/security-advisories/about-github-security-advisories) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| Gerenciar acesso às funcionalidades de {% data variables.product.prodname_GH_advanced_security %} (ver "[Gerenciar configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)") | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} | -| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| [Habilitar o gráfico de dependências](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) em um repositório privado | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Visualizar as revisões de dependências](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [Visualizar alertas de {% data variables.product.prodname_code_scanning %} em pull requests](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [Lista, descarta e exclui alertas de {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [Visualizar alertas de {% data variables.product.prodname_secret_scanning %} em um repositório](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **X** +| [Resolver, revogar ou reabrir alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [Designar outras pessoas ou equipes para receber alertas de {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) em repositórios | | | | | **✔️** {% endif %} [1] Os autores e mantenedores do repositório só podem ver informações de alertas sobre seus próprios commits. diff --git a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index b456b79d4c..d2585dceec 100644 --- a/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/pt-BR/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,21 +12,19 @@ topics: shortTitle: IAM com SSO do SAML --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## Sobre o SAML SSO {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} Os proprietários da organização podem aplicar o SSO do SAML para uma organização individual ou os proprietários corporativos podem aplicar o SSO do SAML para todas as organizações em uma conta corporativa. Para obter mais informações, consulte "[Configurar logon único SAML para a sua empresa](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)". {% data reusables.saml.outside-collaborators-exemption %} -Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, consulte "[Conectar o provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)". +Antes de ativar o SAML SSO para sua organização, é necessário conectar seu IdP à sua organização. Para obter mais informações, consulte "[Conectando o seu provedor de identidade à sua organização](/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization)." Para uma organização, o SAML SSO pode ser desabilitado, habilitado, mas não aplicado, ou habilitado e aplicado. Depois de ativar o SSO SAML para a sua organização e os integrantes da sua organização efetuarem a autenticação com sucesso com o seu IdP, você poderá aplicar a configuração SAML SSO. Para obter mais informações sobre a aplicação de SAML SSO para a sua organização do {% data variables.product.prodname_dotcom %}, consulte "[Aplicando logon único SAML para a sua organização](/articles/enforcing-saml-single-sign-on-for-your-organization)". diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index 9f19074fdf..c398d62602 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ Você pode criar um branch de diferentes maneiras em {% data variables.product.p {% endnote %} +{% ifversion create-branch-from-overview %} ### Criando um branch por meio da visão geral dos branches {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -32,16 +33,19 @@ Você pode criar um branch de diferentes maneiras em {% data variables.product.p 2. Na caixa de diálogo, digite o nome do branch e, opcionalmente, altere a fonte do branch. Se o repositório for uma bifurcação, você também terá a opção de selecionar o repositório upstream como fonte do branch. ![Captura de tela do modo de criação de branch para uma bifurcação com fonte de branch destacada](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. Clique **Criar branch**. ![Captura de tela do modo de criação do branch com botão de criar branch enfatizado](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### Criando um branch usando o branch menu suspenso {% data reusables.repositories.navigate-to-repo %} 1. Opcionalmente, se quiser criar um novo branch a partir de um branch diferente do branch padrão do repositório, clique em {% octicon "git-branch" aria-label="The branch icon" %} **Branches** e, em seguida, escolha outro branch. ![Link de branches numa página de visão geral](/assets/images/help/branches/branches-overview-link.png) 1. Clique no menu seletor de branch. ![menu seletor de branch](/assets/images/help/branch/branch-selection-dropdown.png) 1. Digite um nome exclusivo para o novo branch e selecione **Create branch** (Criar branch). ![caixa de texto de criação de branch](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### Criando um branch para um problema Você pode criar um branch para trabalhar em um problema diretamente da página de problemas e começar imediatamente. Para obter mais informações, consulte[Criando um branch para trabalhar em um problema](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)". {% endif %} + ## Excluir um branch {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md index ff6145755a..fdd6d4abb6 100644 --- a/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/pt-BR/content/search-github/searching-on-github/searching-for-repositories.md @@ -91,7 +91,7 @@ Você pode pesquisar repositórios com base no número de estrelas que os reposi | Qualifier | Exemplo | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) identifica repositórios com exatamente 500 estrelas. | -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) identifica repositórios com 10 a 20 estrelas com menos de 1.000 KB. | +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) identifica os repositórios que tem no mínimo 500 estrelas, incluindo os bifurcados e que foram escritos em PHP. | ## Pesquisar por data da criação ou da última atualização do repositório diff --git a/translations/pt-BR/data/features/create-branch-from-overview.yml b/translations/pt-BR/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/translations/pt-BR/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/translations/pt-BR/data/features/security-overview-displayed-alerts.yml b/translations/pt-BR/data/features/security-overview-displayed-alerts.yml new file mode 100644 index 0000000000..da84d07e41 --- /dev/null +++ b/translations/pt-BR/data/features/security-overview-displayed-alerts.yml @@ -0,0 +1,6 @@ +#Reference: #7114. +#Documentation for security overview availability to all enterprise accounts. +versions: + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7114' diff --git a/translations/pt-BR/data/reusables/gated-features/advanced-security.md b/translations/pt-BR/data/reusables/gated-features/advanced-security.md deleted file mode 100644 index df106b05fb..0000000000 --- a/translations/pt-BR/data/reusables/gated-features/advanced-security.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_GH_advanced_security %} é um conjunto de funcionalidades de segurança projetado para tornar o código corporativo mais seguro. Está disponível para {% data variables.product.prodname_ghe_server %} 3.0 ou superior, {% data variables.product.prodname_ghe_cloud %} e para repositórios de código aberto. To learn more about the features included in {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." diff --git a/translations/pt-BR/data/reusables/gated-features/ghas.md b/translations/pt-BR/data/reusables/gated-features/ghas.md index 0f74920694..b6362ec2f9 100644 --- a/translations/pt-BR/data/reusables/gated-features/ghas.md +++ b/translations/pt-BR/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} diff --git a/translations/pt-BR/data/reusables/gated-features/security-overview.md b/translations/pt-BR/data/reusables/gated-features/security-overview.md index e218337a5c..c3d7aa4fb7 100644 --- a/translations/pt-BR/data/reusables/gated-features/security-overview.md +++ b/translations/pt-BR/data/reusables/gated-features/security-overview.md @@ -1,6 +1,9 @@ -{% ifversion ghae %} -A visão geral de segurança para sua organização está disponível se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}, que é grátis durante a versão beta. {% data reusables.advanced-security.more-info-ghas %} -{% elsif ghec or ghes %} +{% ifversion fpt %} +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. Para obter mais informações, consulte os "[Produtos do GitHub](/articles/githubs-products)". +{% elsif security-overview-displayed-alerts %} +All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %} +{% elsif ghes < 3.7 %} A visão geral de segurança para sua organização está disponível se você tiver uma licença para {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} -{% elsif fpt %} -The security overview is available for organizations that use {% data variables.product.prodname_enterprise %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} +{% elsif ghae %} +A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %} +{% endif %} diff --git a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md index 1193514f50..d8413a8725 100644 --- a/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/pt-BR/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md b/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md index 3d14dd8fc2..4ca7da5685 100644 --- a/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/pt-BR/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**Observação:** Os colaboradores externos não são obrigados a efetuar a autenticação com um IdP para acessar os recursos de uma organização com SSO do SAML. For more information on outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +**Notas:** + +- SAML authentication is not required for organization members to perform read operations such as viewing, cloning, and forking of public resources. +- SAML authentication is not required for outside collaborators. Para obter mais informações sobre colaboradores externos, consulte "[Funções em uma organização](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)". {% endnote %} diff --git a/translations/pt-BR/data/reusables/saml/saml-accounts.md b/translations/pt-BR/data/reusables/saml/saml-accounts.md index 0963e8f3d3..e9c0949caa 100644 --- a/translations/pt-BR/data/reusables/saml/saml-accounts.md +++ b/translations/pt-BR/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -If you configure SAML SSO, members of your organization will continue to log into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. Após a autenticação bem-sucedida, seu IdP redireciona o integrante para {% data variables.product.prodname_dotcom %}, onde poderá acessar os recursos da sua organização. +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre a autenticação com logon único SAML](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)". {% note %} -**Note:** Organization members can perform read operations such as viewing, cloning, and forking on public resources owned by your organization even without a valid SAML session. +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/security-overview/information-varies-GHAS.md b/translations/pt-BR/data/reusables/security-overview/information-varies-GHAS.md new file mode 100644 index 0000000000..7d642c7fda --- /dev/null +++ b/translations/pt-BR/data/reusables/security-overview/information-varies-GHAS.md @@ -0,0 +1,3 @@ +{% ifversion security-overview-displayed-alerts %} +The information shown in the security overview will vary according to your access to repositories, and on whether {% data variables.product.prodname_GH_advanced_security %} is used by those repositories. +{% endif %} \ No newline at end of file From 93fdabb039af7046b68bb70bd9a2dcfeb4642cd7 Mon Sep 17 00:00:00 2001 From: Mikhail Timofeev <48208649+miketimofeev@users.noreply.github.com> Date: Tue, 9 Aug 2022 22:10:32 +0400 Subject: [PATCH 31/41] GA ubuntu 22.04 image (#29385) --- data/reusables/actions/supported-github-runners.md | 1 - 1 file changed, 1 deletion(-) diff --git a/data/reusables/actions/supported-github-runners.md b/data/reusables/actions/supported-github-runners.md index 7475357d15..e0b2ae9b99 100644 --- a/data/reusables/actions/supported-github-runners.md +++ b/data/reusables/actions/supported-github-runners.md @@ -36,7 +36,6 @@ Ubuntu 22.04 ubuntu-22.04 -Ubuntu 22.04 is currently in public beta. From 1ceffe9adddcfa1729c33b4c1e3d494548338407 Mon Sep 17 00:00:00 2001 From: Rachael Sewell Date: Tue, 9 Aug 2022 12:13:08 -0700 Subject: [PATCH 32/41] add close issue reason to stalebot workflow (#29646) --- .github/workflows/stale.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml index 925c9e07f1..29ebe4a6d2 100644 --- a/.github/workflows/stale.yml +++ b/.github/workflows/stale.yml @@ -29,3 +29,4 @@ jobs: exempt-pr-labels: 'never-stale,waiting for review' exempt-issue-labels: 'never-stale,help wanted,waiting for review' operations-per-run: 1000 + close-issue-reason: not_planned From 848dbf46977cf3b1018b004246f4ac19cb45692b Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Tue, 9 Aug 2022 19:44:23 +0000 Subject: [PATCH 33/41] update search indexes --- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 80 files changed, 160 insertions(+), 160 deletions(-) diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 6d58ff0ff7..813952a00c 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:951534c481d4aeea5a570306a3432dab4833ff5a7ebaa4fb553229fd59c2625f -size 794260 +oid sha256:bd3054b030ec008d7df09049fda548417ebfc79686fcaf4befc17d540ab2e791 +size 794385 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 6fd800f462..90b3918e8e 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0846a6a54c0f809ad2eb1b2a778a58835e8b696657409b95bea6211c7499ebce -size 1636838 +oid sha256:15ec3a3958adeb3eac5ef14ed30c4a532c0a8815b9603c74f129dd7b3f0f7a90 +size 1636346 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index b8162e4272..1c30cebb16 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c7a4d90f7f636e1daaf572e11a8d662c184de95e739303946ebd78a646eefc73 -size 1089178 +oid sha256:ad2bcd6de9db27fb054dd5f3f1b26a65dd0fdb7b47b96bfd83515c6d3a5415e8 +size 1089379 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index f5bc4d6c9c..5803c54f5e 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:de0125d56dc10319cd5ab529dd8f6a2fa816b909cb278e4fc1175d2724dad157 -size 4417895 +oid sha256:84aeab8edea2e3fe815a777bdafc2dd2158371cfd5b0e317976011e7869b13eb +size 4415857 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 6c63efb70f..fa6e31e7ef 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb111430bbbbac3f738f328ea987e4ec73f8892d5c9d815dca3485ac0c5f99c8 -size 733797 +oid sha256:0b1f8ba4623312a7d09c576668f8c475f9c3c5a56dbf8ecc3ff6d472a3cd9223 +size 733865 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index f18c2d2450..a49027f657 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b1a177e31e30a795960529cb066c471a0b51c9c5b3bbd4a1ea07cd1c20e0ff26 -size 3131095 +oid sha256:502f72c288478f2dbb70ce57605a22b9966ad4834f37ce35d65e339768c852cc +size 3130975 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index 74bc0cad28..ef80f9a96b 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:935060adbe656a23cbb87c8fbf89cdd5bd22890ca444e8acfe99048bd1dc5bf2 -size 808832 +oid sha256:52af056bbad9cf34d8aadccbf4553721a8937ad5a35d8047de59761d398fd57e +size 808750 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 51ee11c427..997d975611 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:baa71d0164c73a44457467cc1dc99aec8ef9f1514a276f85a5482d02e678056d -size 4447455 +oid sha256:74f81ca5149c1001af580a8d70759bf7f6c2b02709d66eacfdbbc9d0cafd7001 +size 4448046 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 51a7ed61a8..df5213e560 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1f01ed60636d74962b5b9029316aed65bd070b2e8785ced9091bb80a8863eb8b -size 722304 +oid sha256:fb33f9191102e91f865baaad113c5760fca052da08de0b9124da24bef94a7922 +size 722361 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index 0032f99496..fe97569367 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0b3a995100e2a1c55815996b6fd53d38bf807de604f028501b5311a49d178010 -size 3028345 +oid sha256:503724e7a4f7b07880bf773107efa5d0dca89f905ab132924fc51a2662950ef7 +size 3028450 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index bd10feb978..95f06c6adc 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a9218f0358530d87224490eadb78f1aaed95327b549a3f83b95d83ecedd65cbc -size 819614 +oid sha256:8deea3941494e7ff55bf48500a179d717037ff6128975b43ee4e7f675551656e +size 819578 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index bf6c1c0408..673458847b 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e84101d458d87b1408ca7b82bdf0b966f5b93cddc4872d852b0ef49c31ec17e0 -size 1684910 +oid sha256:75ac97bf12fe195bcf59b2251b9b50ae1b3f86bdabe93d60a5e65b0ce380f0ae +size 1684325 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 65b65e8255..68e493c216 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8dc75a6bd06f64091d19c4d07b85d5a6129221691f25edff9dafe0d65521120e -size 1124224 +oid sha256:7e801da386fb91c7578d33566732a7da4abbfbaf034b1987aeb0dfeba22567a4 +size 1124613 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 1b310ef8ac..6f855def6f 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:51b561bdd5d395132e6a1341bb62a40e45e57b4eef22c7cc56118f3c15686507 -size 4521369 +oid sha256:531bb089ce86db9302b415f3ed219a61a5f6e3b54f46771f491eabad42f14436 +size 4521947 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index ac8aef76ba..ad33505b41 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9f8c53d57fd08d52c7bc68358238c30f4813ba22aa25a7fe95ca3bbe4b8416d4 -size 754837 +oid sha256:f3ac4348968f7bd55349a3e4032226d83f6732aa0b9359d7a5faf0db09502d7e +size 754937 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index fa71e7f9b0..96a7e34022 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0e0baa2813129386c192606596553fa64d2dfcce96983fbd6675043e167382a1 -size 3217777 +oid sha256:540eff3744a4ddbe77cfc07777921f4ceae6e609fbccae109d5465198a46b7b7 +size 3217380 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 1503afdfb8..2a92cc048b 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5755109b7092d68dfbc4732d9ae0b0ed880c2e5823ef6a1695cf91b08da1ff9e -size 834229 +oid sha256:19de45fb9362fd481f0a3c6bcf98c6f2152df95bfbc431075f02746b1c3b22e2 +size 834182 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index a4b55984e6..6a4b5526b3 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c6b583181cfce320cdb09d00ddaed94318f08cfca95433b1786a3209c180defe -size 4583272 +oid sha256:2f428cc5ed39a4ffc5f827060360aa0d63cc4bcac45c75ab07f6578399c4dff2 +size 4583688 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index bcb5a145ae..e5dc1178f0 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:308ce247a3ac39bc8815f9ec6e960f71eff69ad58cc4528ce13e2d31e3690d18 -size 743857 +oid sha256:aef2924d191ff717ff27b80ffeba8c5dc34deb1e33bf0eddf1ee3ad6041c81ad +size 743853 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 191e3d708d..e88fd4ad53 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7b59426eea644c6818fde62c55dac35b29b0af6e9b3e82fd14b0bc734824d3be -size 3112841 +oid sha256:77cc1df2bc33d36c054f82cb365ebca6569857d735e7e16fc630302eee485861 +size 3113254 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 4b46e44ff9..3fa19ba4a7 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e678e10726ecaadd0a241310a4837e0226c68fcd4bb9f88f40233e7067265522 -size 822241 +oid sha256:f2a240e2d1a8229923aadd9e4f6603386b8e235c9b585e4dea3159215c2dc3ea +size 822193 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index 60bd73d0ce..bcbf04e63c 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fa4b8f33f6669b7480247bf24a29ec1049d8b6f08dbcce5ab4fb98453f2036be -size 1699374 +oid sha256:7aa0b3e6687ed56ede3abf08636360f468e496856312be6eb98225821fd35f57 +size 1699288 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index e768f34528..3a64b79a2a 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2b0b3a988af8a7f559fd6eff96274b58ce46381d20a2338f198ea8f823c7eae7 -size 1135617 +oid sha256:81c80033e901b97ddb1e847327aeb0857b05e90742cb20050a0dd9d6d90f1d9f +size 1135570 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index e0abff2198..cdaa99a3a6 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5a80ee83fe1713833c9a03a325668c12652d5ce4b66c5c14893598b16a1a5d72 -size 4578928 +oid sha256:086de113f35f54ca6a996e7e0623235e7a03d370f10bbe4bbdd12348675fc3e2 +size 4577573 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index 51e002f452..ea1236f741 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:47d6759b77c3438f0d38b4d6c02dd063631f57ad8e6cfceab2cde941a53c40a5 -size 759303 +oid sha256:96bbbc0ac2bcac52a4233b35e2152e702573229657b4f45dc17a299f5e4c8759 +size 759341 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index b1c4ebcba2..ec358b0c85 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:afb422b13d24918c97ced3d48e92ac2f753a847556999025b751fe170c66fbfc -size 3239852 +oid sha256:101c5765e9f0693aaf648528118292a03fdb482c822ad384c77073fc868c3f76 +size 3239901 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index 8c851c3fc4..7968167619 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6caf563e6040c3cc88e032bf01cded6a13fe0227938569e77cd111a2c090f2ac -size 837703 +oid sha256:72b8e188075b52f2a774441b43d3c34aa50e073dffe84faeec22688453442f8c +size 837643 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index d55755b1c0..3f6562e41f 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7ac194251797c1447b07427b547a610215ae477a11fd68a4f2490a00375f80b4 -size 4617779 +oid sha256:4645621391ac4966edf0cf6375b3fdffe1d4ab5fec7fd0309137e46aaf637404 +size 4618546 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index 937c0a0155..f07ad42c25 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:335eabb55f0d1faf39cd6c600f85deb4b81c4afce9a0d32e8cea1f6f5643e92d -size 748047 +oid sha256:c27b0748cb0a6539b7bb9ae1497768e003058d3d6fbae94ad5c8f18b6d8c13b5 +size 748029 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index 1d996b43b2..b61f42a0e1 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fef8a9e1d2a3412b1eeb2cfd35a1ace7f744d13d994c0e520055534796741bc2 -size 3137537 +oid sha256:1e8fdf084009d76c178a8b2613a608e95b45fdf165493c114a04d89c12aa0bf9 +size 3137852 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index a3b0511eb1..f2399b9939 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3974ec2b083dcd0935f1e119d039ea2415e611117a260375e1175427938da883 -size 851714 +oid sha256:cbcf5c0bf83babfe878d2e5e253e00f0407b11ab4a2991ab7bee52741e4b520d +size 851696 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index 6f91cea12e..d44c2e977d 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:758aa2932e00917cd84699c1936b3accad64ca69dd92dcc58efad134e423ace4 -size 1759619 +oid sha256:8561675c11f177e3a718e55155c462f320d4286bd80ee21894ea7dffe93fc947 +size 1759584 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index a39eb0e233..7e939e43f3 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e40bdcb78967f8efe325aa13adcc9634c54f1d23b595b0799652765ef5c2da51 -size 1173883 +oid sha256:6a25efaad9295507a45ff1832b3219d6ad04a9aaa0c1a9de4fa0cda887ebfc4d +size 1174270 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index 081caf818b..ef15be2e04 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0be702bce55fd5b2e34581c2fb4d6171b35a38acc8806653878e72391472e022 -size 4737028 +oid sha256:c86659be747dd6995c72facb6c570986799e592b1f8c9f4d1cb6a1db07b35273 +size 4737884 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index 459ba946de..e016acdc58 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b9cf96315f2eeefa77f9d2c25611b831cef03f75b7b980f2758521f35b224a9a -size 782633 +oid sha256:90ab6db0e0e41988378be0d3c7ca212443590e69b81d1a4e1b9c8759341776cf +size 782685 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index 57d4b7c4f7..9170c223bf 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2039169681b2fbab37e24fcc6d1d55444ebfba6e726b3ccdcb160f00a814b995 -size 3353864 +oid sha256:75a8b2c0e938e4f6947a7cba21400a7f6e455339aac347cb01de1385d574b936 +size 3354240 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index e5a2a20787..dfa18f5769 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a9f45ee32243cfb4995fdd9822ec119d38eb787e43e3c4a0c5ed7bc63fea351a -size 864763 +oid sha256:384e100902ba3da3961888fe250020bc76f95227e2f36b3fcdd0eda2f1e9dac5 +size 864769 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index c9db131082..f54bf18713 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4edfb7bef0f7eb1cad22fc3974be013245d989c6c240e221515f2897811558d8 -size 4780530 +oid sha256:06ec78d38d666274d2c23ac8f077aeafddf8ffe867bf63696d4a9eab0c4d1552 +size 4781105 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 6ea8405116..1e3e786f5b 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5308ee199c1754fb6fb6d0474903a2da2494558750d7543112d1619483e06116 -size 770846 +oid sha256:fb3e4e4b96893b13f1377f12950a74d21278f0325f1e695ec35d4477dfe13ff8 +size 770794 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 6cc5e0927b..2e152aa64d 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d23911995804e87241544bd301c7fa0075f493cc56b8a48d847aaaa6f79ae114 -size 3247297 +oid sha256:8edbd543a76775a490f57280a16ab6bb163ccf53c7f8e0750e97c6618f0da0d1 +size 3246575 diff --git a/lib/search/indexes/github-docs-3.6-cn-records.json.br b/lib/search/indexes/github-docs-3.6-cn-records.json.br index fb6b39833f..cf74ca6998 100644 --- a/lib/search/indexes/github-docs-3.6-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.6-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:baf0709df725780b0ef047f76c975a57ada39ef5baff6d048796ebb3bee3cc9d -size 874309 +oid sha256:7069890407e191ef61162ac7aa72b69eaab2d834165017c70fceeced8c2c0156 +size 874339 diff --git a/lib/search/indexes/github-docs-3.6-cn.json.br b/lib/search/indexes/github-docs-3.6-cn.json.br index 67e6b253fb..5d76b4cefa 100644 --- a/lib/search/indexes/github-docs-3.6-cn.json.br +++ b/lib/search/indexes/github-docs-3.6-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ade978fd3927467e0290e0a5b4f5a8ae3a2a07e6bc1319056b8a5ab2ff385391 -size 1807450 +oid sha256:7af904f4b6fbe431a6c703eb79be47a6112ec1efdf3faa0c0ebd2701c51a90e2 +size 1807589 diff --git a/lib/search/indexes/github-docs-3.6-en-records.json.br b/lib/search/indexes/github-docs-3.6-en-records.json.br index ae795bce74..a27c2aa4bb 100644 --- a/lib/search/indexes/github-docs-3.6-en-records.json.br +++ b/lib/search/indexes/github-docs-3.6-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7bf006960fb721929c92cb3736dd387d55e8a3126b5e2fbd15cf92ada012eb94 -size 1202765 +oid sha256:bc83caa795c42e78d38085cd5f6667cc6da56eb752eb2473765f6dbc1b87a8e4 +size 1202567 diff --git a/lib/search/indexes/github-docs-3.6-en.json.br b/lib/search/indexes/github-docs-3.6-en.json.br index 8d56345f8a..c0c716d098 100644 --- a/lib/search/indexes/github-docs-3.6-en.json.br +++ b/lib/search/indexes/github-docs-3.6-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f0d9c81afab2bf1a343c4e4c2a7c399d41bd55414e930ef313d031c23022a9b5 -size 4852968 +oid sha256:eb243d78cfebfe8d8e52595fa32b4c61c2e39c444f5e63e096f88ba7f0301f91 +size 4852373 diff --git a/lib/search/indexes/github-docs-3.6-es-records.json.br b/lib/search/indexes/github-docs-3.6-es-records.json.br index e5ad9f14fd..7fd5bc0645 100644 --- a/lib/search/indexes/github-docs-3.6-es-records.json.br +++ b/lib/search/indexes/github-docs-3.6-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6e8d795752d8c7aa73e5b6728707cc848afbf3c2de4635b397be21330731b698 -size 802916 +oid sha256:63ab8f3be141c78ab30c615813f522be6a95b5b8df1d364a3f12d26fd9c5ed26 +size 803062 diff --git a/lib/search/indexes/github-docs-3.6-es.json.br b/lib/search/indexes/github-docs-3.6-es.json.br index 62dde8daa7..2f4573a9f3 100644 --- a/lib/search/indexes/github-docs-3.6-es.json.br +++ b/lib/search/indexes/github-docs-3.6-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dad30b914b2f25912d84d7ac63bfabdee680f6852848a134e17c91e05a74c809 -size 3451853 +oid sha256:a02eb794157c3b345c0eddad44dc189b4f3d32bcea52a241111a0cad6aa60b09 +size 3451472 diff --git a/lib/search/indexes/github-docs-3.6-ja-records.json.br b/lib/search/indexes/github-docs-3.6-ja-records.json.br index 6b01cee2d3..b829483beb 100644 --- a/lib/search/indexes/github-docs-3.6-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.6-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:10129c2753a0069b7d698a5b770698297663c24c459902239bf4f28487159aa7 -size 887369 +oid sha256:3401701f18cf295316463905afdcb706f93d6ec0bf9d5c7f06e24f4c89b4afdb +size 887333 diff --git a/lib/search/indexes/github-docs-3.6-ja.json.br b/lib/search/indexes/github-docs-3.6-ja.json.br index d77699bbb2..a179bb33e1 100644 --- a/lib/search/indexes/github-docs-3.6-ja.json.br +++ b/lib/search/indexes/github-docs-3.6-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:21c9348ccde6ee2b1c9547b12d59c1dbc57d2c007352563cab2cebac9b4665ff -size 4913666 +oid sha256:9a86436348af4af5861bbd7780f11b445d57bd66eb61196b1ea8933fb338964f +size 4914478 diff --git a/lib/search/indexes/github-docs-3.6-pt-records.json.br b/lib/search/indexes/github-docs-3.6-pt-records.json.br index 100d16c28e..b9af80cdd0 100644 --- a/lib/search/indexes/github-docs-3.6-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.6-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3eae108ab7cd033283dfb123c7e8c77dc023cd6f058a5c4625826c431a0f8c86 -size 791369 +oid sha256:1a200c213206a1969929c7799ee929cb4635cc3e31295f2734d0163f9dd7c694 +size 791409 diff --git a/lib/search/indexes/github-docs-3.6-pt.json.br b/lib/search/indexes/github-docs-3.6-pt.json.br index de0be538af..516ee9e47a 100644 --- a/lib/search/indexes/github-docs-3.6-pt.json.br +++ b/lib/search/indexes/github-docs-3.6-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:658640fc0a69718f6e07d7da36df844e896cc11fef17ff2ab0c8a76993263e90 -size 3343408 +oid sha256:86580388bab174c5ed558c7ee0bd7f389fc73eb16a0c440b833117fc64519693 +size 3343809 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index b8c54baa88..37f4b8efc5 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:63ababe63dc779ad4b3915667b8f9afd6e9c09e0bbdaea2eabd0e3bace7047d6 -size 1036299 +oid sha256:2cbaf2e644856e74da346bc4eb179bdc2cca720e29feed74bf907bfcfb66b5ab +size 1036207 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 92063a05f1..f7f6a0aa53 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6e107c3ddbbd4bbf73ff798a2f8c6cf5213f30df5141813d197d7cb2ec803549 -size 1842603 +oid sha256:3418fbdb1d39e6f3fcae891308640d298a2c44312ee9fabcade4f6a3f01a8467 +size 1841510 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index bafb44ada1..9d9a49d465 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8f61746409d911376e17fab1ba6eeca4eb8bce1baf118c39ce9d8b260256177b -size 1445187 +oid sha256:6a977b70f80882546ebba5eeec9bf22a074a51dcfda137e271608edf44d0853e +size 1445163 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 0d28194c83..6b44c5e2d1 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3f37fc7cc31f04bae6f6914049e0a46553f82e7cf873f088840c9d8ff246ef4c -size 5566007 +oid sha256:58f39cbc6e90f04602b41a1710c56d7ea381b9705755aa0cdb6243f1238c54fd +size 5566225 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 411b37e2b4..f568175d59 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:43ed12c83826d67a14b4ffba4150cf80a196814a0c2b52254bc926e67b28452f -size 934244 +oid sha256:b7bb9db5ba3d4e6999aef5e232216a64b0398043a481de02bfa49d24624e8811 +size 934250 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 3187273e0e..c99e8bae14 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9db38b1bbf50a0cc18589e7781e58e305723616d09d4743cf9c7beaf56320f7b -size 3885466 +oid sha256:66934092b477f5a62a98c59ea2f505ea02ee15ad7d97d07e6c5ddfdc1faefdab +size 3885445 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index c85c4ed1d6..233cf3847c 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fbccf3707a78e080c17ce5ad5256b4020d740d6dd88cf6238d693956eead2e4a -size 1043317 +oid sha256:4ce56531d08b584248c608f499b05b21f5f7d21b4e464cd09094da013455a614 +size 1043240 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 0201f9a4cb..a32d78bd4a 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a7b733e77054e27a85e7646922be57b5075d994001a7fdb70ed743aea03970b -size 5608025 +oid sha256:fbfb7498a01ff65bc46ad3d47991bb2784227bf0e32eaebffab6eb218289830c +size 5607983 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index 8483ef85dc..d26400bf10 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2a0b7adeae708add25c497548ee15adc69f23c345dd3a3d7f89b1402906ce80a -size 923110 +oid sha256:a064a299445ced84011f8422b86e65cb250e7996936298b2bd0991509b3f3b2a +size 923257 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 45ab18d260..64067ed6c8 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:831d5f36d98eb49e971fc0981c8fb9f7f85d3ce7c3a9e13032a60663bdac7f88 -size 3801064 +oid sha256:f679752b629f3dfcc70d5d4bbe5a4efe5f2f75878e23363e7dd36666263494b0 +size 3800651 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 276849cb37..158ee256cd 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:872ab1034c33112b04756e7c276c7cbfe75a0fb40ae501bde5b01cc1ec3742e4 -size 659390 +oid sha256:8eb2cce701ede42f418a425d237162dfd44e7c3488a9fe7762c9e5088d75c176 +size 659180 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 701d49466b..3a2e83a969 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6b0b0602d11e2c96c26f9df5bfea3a687c1f521f4e611cd751d4e6dd857db392 -size 1311055 +oid sha256:fe8f0cfeef91a813c13a27c8196a6c1007caf9390a79e24a901047cc2c889a1f +size 1311026 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index d1c63c108a..da50bf3ef9 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bb5ed8abf3048bc91f2f580c6a753cbbad792b7286a9e3a7dd5a74b4621b0369 -size 932494 +oid sha256:d58cb6e774244892146d7e2bb0b3221775f9d4ae77fcbaab96a9c4b380d2a235 +size 932648 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 4ad3b2e43e..76157149f1 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6252be1685c15accc4b90e2502be8d633a0399365a92586162c211c6d2b67503 -size 3696477 +oid sha256:6fc36b7e4d3fbc64c5398d8ca938673feacd3a48f71b22c9702ecab63abc9838 +size 3697983 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 2c568b8a68..985fe79558 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:acf93a85cae1851c67af58dc331bbfaa3373f24f0c8caf0b02997d63c63b40a3 -size 613082 +oid sha256:fb9a3b214dd83130b4df85d295b521440f74ec423e63934c06530d9fa532ef82 +size 613165 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 571a07ca24..2d5f6e0281 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b32c6127da80532136daf94ce6b4653459372853e8e9c2b4be94064c833d2bd1 -size 2536674 +oid sha256:95912386cad690660058938dc06b95f744a54b8158dafa7bc0b9907a67da1c00 +size 2536518 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index 74e34bd323..9e46671367 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e5358a1350b628541317fc5bf5b99b977de143589ab00d642fcdca2a2a8ee76c -size 673268 +oid sha256:585592d859f874abcafcb97cd76a12a4979d9672653589bca0637b0e19f6ce8c +size 673320 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index dca7435d29..47122de73a 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:835c83e165d97518e5a6d2dcebd68bd7a38457d86749d00aae0dbb8b6917ef30 -size 3600857 +oid sha256:537ddd303d8397af31b6287ac4654ec167ee29cd2d5288772fd67e6188afc8be +size 3601242 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index f02b7b184f..42c0be3016 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3677abf02c0dbb339b3bb90fa78570a28fa14e534f2073e9bf37558eeb6ccf6f -size 604188 +oid sha256:e47241b870dc126c7e8c502c12221af4e0b8a81f2b8f1853505a9ae0e3396d48 +size 604324 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 4b31ae5d1f..37ba408c1d 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4118658b6e418cefa06667bea13b7651ade925d29840a085f64a8a0463560e36 -size 2434071 +oid sha256:0efd922709faefb52adcdf3431cd7f75105ab88a48a33a5a9f363a54db2b4cd0 +size 2433883 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 2fcf2f6b1b..98b36f9223 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ca65700d0a901e33a3b964a94cdff54adc5a651069e24ad52a1e74c32bf615ee -size 1005220 +oid sha256:82fc6b0349b75548f087979b3f97ff0b289f73303f028c39918c0dc6f133d5e1 +size 1005303 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 177be428a2..e40c3297be 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:021443b2bc121fe47f073d388c0748ef24347de7549f0f48970c14d8c8cdaecb -size 1964563 +oid sha256:6f139f9dd2049babcacf96bd861f6e39ebb25df68e94cd87fb97ed1754e4f0bc +size 1965025 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index b478834bf0..ce099bd4fa 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:730af930bb9a7c21550c483357bf937a31af8350674f8032d737f839aaed835e -size 1376066 +oid sha256:28f9028dee9a6f07591e668408d97046c71e1a681ab0a8d163d806a7cc346f9d +size 1371784 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index 89e2f20167..c26abc156b 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b34b324fe194332a9d507c4a3bae99830b6a05164a787bbfa76699ebde5f29aa -size 5567444 +oid sha256:c8dd38875cc2b1ba0796901891e114360778e35f2c30894b12ee70af7b71a6ae +size 5568340 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 414dff0fdc..34541022fc 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d3acdf3d60d11ac4a2ec346c6e870785a356076056be14fb129aea75eb31cf92 -size 930765 +oid sha256:b51f95e2d8293d7add9eaae58a2df16bb8e436bf9dbf748006d8fa93b04725da +size 930767 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index 7d52149181..cb8671cf02 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:715eaf0c8e6bda66848c275f9f328917862710bc4931267708afbbd0ef474e7e -size 4018139 +oid sha256:2a9e98e71276f4a5cef6abde1a89aedf1082e5477b1495896f21180c2307aa16 +size 4018689 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 9ab7ec2419..1eab1e6036 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ed9caabec0913f617a4f2c326e33c4817f92d2afcd11f69fce0ebab9803f2331 -size 1018330 +oid sha256:339c0d63a401f0d6ce3470585e0ace8e4c52157a688849ba4e2d9a91b7bb7c46 +size 1018356 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index edf29d95ec..3ce41d1745 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d9c6b14e5e7983244a8fadeb455126eb1cc1985fb12e8a4b873e53c078383f0 -size 5689722 +oid sha256:d09d8e0d6931fb61585e1977d03e87321ef5374f4e3e1a561258600dc36ef7cd +size 5689440 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 560ac1aa2c..e7fb70052f 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0a932cb940f77a303a8a2c7b66c64c74840870471b0a7c10165c3d23b3478eba -size 918607 +oid sha256:23d8e2d6dee457a8be4e12d840daecee51f39e155daa79ff958eddcef94369a8 +size 918619 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 843fe6247b..d6373b17d1 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f86f98c4d99f32321b89041afdf89f3b8dd78f58db434a1f09fe05539e32ccaf -size 3915835 +oid sha256:49f02b6d8f76edc65c796577a66b43abd03182a4d6a24dda5413504a32bc0f37 +size 3915819 From 37203886ff3d781c33dc0483a006e698923b7304 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 9 Aug 2022 21:55:36 +0200 Subject: [PATCH 34/41] remove now obsolete code comment from render caching (#29767) --- pages/_app.tsx | 4 ---- 1 file changed, 4 deletions(-) diff --git a/pages/_app.tsx b/pages/_app.tsx index bb9a4597b7..1b3ffe7f32 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -75,10 +75,6 @@ const MyApp = ({ Component, pageProps, languagesContext }: MyAppProps) => { ) } -// Remember, function is only called once if the rendered page can -// be in-memory cached. But still, the `` component will be -// executed every time **in the client** if it was the first time -// ever (since restart) or from a cached HTML. MyApp.getInitialProps = async (appContext: AppContext) => { const { ctx } = appContext // calls page's `getInitialProps` and fills `appProps.pageProps` From 6e1bf47b5c723d15e416bfb369f2a8c736a8c078 Mon Sep 17 00:00:00 2001 From: Mikhail Timofeev <48208649+miketimofeev@users.noreply.github.com> Date: Wed, 10 Aug 2022 00:37:39 +0400 Subject: [PATCH 35/41] Add a note about Ubuntu 18 deprecation (#29527) Co-authored-by: Dusko Dobranic <101048884+ddobranic@users.noreply.github.com> Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com> Co-authored-by: skedwards88 --- .../about-github-hosted-runners.md | 2 +- .../using-workflows/workflow-syntax-for-github-actions.md | 4 ++-- ...-cache-on-self-hosted-runners-without-internet-access.md | 6 +++--- data/reusables/actions/jobs/multi-dimension-matrix.md | 2 +- data/reusables/actions/supported-github-runners.md | 5 +++-- 5 files changed, 10 insertions(+), 9 deletions(-) diff --git a/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 3032851f64..dcfa57bf9b 100644 --- a/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -113,7 +113,7 @@ For the overall list of included tools for each runner operating system, see the * [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md) * [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md) -* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) (deprecated) * [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md) * [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md) * [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) diff --git a/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 65e0259043..671f0dac0e 100644 --- a/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -793,11 +793,11 @@ strategy: fail-fast: false matrix: node: [13, 14] - os: [macos-latest, ubuntu-18.04] + os: [macos-latest, ubuntu-latest] experimental: [false] include: - node: 15 - os: ubuntu-18.04 + os: ubuntu-latest experimental: true ``` {% endraw %} diff --git a/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index 367ced039b..0dfc96abe2 100644 --- a/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -30,7 +30,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr {% note %} -**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." +**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-22.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 22.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." {% endnote %} @@ -45,14 +45,14 @@ You can populate the runner tool cache by running a {% data variables.product.pr 1. On {% data variables.product.prodname_dotcom_the_website %}, navigate to a repository that you can use to run a {% data variables.product.prodname_actions %} workflow. 1. Create a new workflow file in the repository's `.github/workflows` folder that uploads an artifact containing the {% data variables.product.prodname_dotcom %}-hosted runner's tool cache. - The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 18.04 environment, using the `setup-node` action with Node.js versions 10 and 12. + The following example demonstrates a workflow that uploads the tool cache for an Ubuntu 22.04 environment, using the `setup-node` action with Node.js versions 10 and 12. ```yaml name: Upload Node.js 10 and 12 tool cache on: push jobs: upload_tool_cache: - runs-on: ubuntu-18.04 + runs-on: ubuntu-22.04 steps: - name: Clear any existing tool cache run: | diff --git a/data/reusables/actions/jobs/multi-dimension-matrix.md b/data/reusables/actions/jobs/multi-dimension-matrix.md index 5041ca5554..c3eb6dc685 100644 --- a/data/reusables/actions/jobs/multi-dimension-matrix.md +++ b/data/reusables/actions/jobs/multi-dimension-matrix.md @@ -12,7 +12,7 @@ jobs: example_matrix: strategy: matrix: - os: [ubuntu-18.04, ubuntu-20.04] + os: [ubuntu-22.04, ubuntu-20.04] version: [10, 12, 14] runs-on: {% raw %}${{ matrix.os }}{% endraw %} steps: diff --git a/data/reusables/actions/supported-github-runners.md b/data/reusables/actions/supported-github-runners.md index e0b2ae9b99..6918629c2d 100644 --- a/data/reusables/actions/supported-github-runners.md +++ b/data/reusables/actions/supported-github-runners.md @@ -48,12 +48,13 @@ Ubuntu 20.04 -Ubuntu 18.04 +Ubuntu 18.04 [deprecated] ubuntu-18.04 +Migrate to ubuntu-20.04 or ubuntu-22.04. For more information, see this GitHub blog post. @@ -97,6 +98,6 @@ Migrate to macOS-11 or macOS-12. For more information, {% warning %} -Note: Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support. +Note: Beta and Deprecated Images are provided "as-is", "with all faults" and "as available" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support. {% endwarning %} From e6aced406c8aef1c20633129b1567ad254906eb6 Mon Sep 17 00:00:00 2001 From: Yoann Chaudet Date: Tue, 9 Aug 2022 15:17:43 -0700 Subject: [PATCH 36/41] Update data/reusables/pages/wildcard-dns-warning.md Co-authored-by: Jules <19994093+jules-p@users.noreply.github.com> --- data/reusables/pages/wildcard-dns-warning.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/pages/wildcard-dns-warning.md b/data/reusables/pages/wildcard-dns-warning.md index 8978c322e4..700c2473be 100644 --- a/data/reusables/pages/wildcard-dns-warning.md +++ b/data/reusables/pages/wildcard-dns-warning.md @@ -1,5 +1,5 @@ {% warning %} -**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are [verified](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages). +**Warning:** We strongly recommend not using wildcard DNS records, such as `*.example.com`. A wildcard DNS record will allow anyone to host a {% data variables.product.prodname_pages %} site at one of your subdomains even when they are verified. For more information, see "[Verifying your custom domain for {% data variables.product.prodname_pages %}](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)." {% endwarning %} From 738081634bc8c9b576353bd6e549afa41d351dd4 Mon Sep 17 00:00:00 2001 From: Courtney Wilson <77312589+cmwilson21@users.noreply.github.com> Date: Tue, 9 Aug 2022 17:34:27 -0500 Subject: [PATCH 37/41] Update assets/images/README.md --- assets/images/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/images/README.md b/assets/images/README.md index d547029560..43d7c51808 100644 --- a/assets/images/README.md +++ b/assets/images/README.md @@ -2,4 +2,4 @@ The `/assets/images` directory holds all the site's images. -See the [contributing docs](/CONTRIBUTING.md) for general information about working with the docs. +See [imaging and versioning](https://github.com/github/docs/blob/main/contributing/images-and-versioning.md) from the contributing docs for more information. From c37df3e30b0a79dfef2a74afe91ad5fe2b9c5cf3 Mon Sep 17 00:00:00 2001 From: Courtney Wilson <77312589+cmwilson21@users.noreply.github.com> Date: Tue, 9 Aug 2022 17:34:33 -0500 Subject: [PATCH 38/41] Update assets/images/README.md --- assets/images/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/assets/images/README.md b/assets/images/README.md index 43d7c51808..9756be1695 100644 --- a/assets/images/README.md +++ b/assets/images/README.md @@ -1,4 +1,4 @@ -# Images🖼️ +# Images The `/assets/images` directory holds all the site's images. From c563e8abeee1146c279007e7eb719d3dde41942f Mon Sep 17 00:00:00 2001 From: Mariam <15mariams@github.com> Date: Tue, 9 Aug 2022 17:32:23 -0700 Subject: [PATCH 39/41] Update secret-list-private-push-protection.md (#29773) --- .../secret-scanning/secret-list-private-push-protection.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/data/reusables/secret-scanning/secret-list-private-push-protection.md b/data/reusables/secret-scanning/secret-list-private-push-protection.md index fd323a2dd4..adc0cef6d8 100644 --- a/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -10,6 +10,8 @@ Atlassian | Bitbucket Server Personal Access Token | bitbucket_server_personal_a Azure | Azure Active Directory Application Secret | azure_active_directory_application_secret Azure | Azure Cache for Redis Access Key | azure_cache_for_redis_access_key Azure | Azure DevOps Personal Access Token | azure_devops_personal_access_token +{%- ifversion fpt or ghec or ghes > 3.6 or ghae-issue-7456 %} +Azure | Azure Storage Account Key | azure_storage_account_key{% endif %} Checkout.com | Checkout.com Production Secret Key | checkout_production_secret_key Clojars | Clojars Deploy Token | clojars_deploy_token Databricks | Databricks Access Token | databricks_access_token From ebe388f003e57fb597fdf19b02293d7d84e2bd9b Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 9 Aug 2022 20:41:41 -0400 Subject: [PATCH 40/41] New translation batch for ja (#29769) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report Co-authored-by: Rachael Sewell --- ...-of-your-personal-accounts-repositories.md | 2 +- .../about-continuous-integration.md | 2 +- ...ilding-and-testing-xamarin-applications.md | 4 +- .../creating-a-docker-container-action.md | 2 +- .../metadata-syntax-for-github-actions.md | 2 +- ...grating-from-circleci-to-github-actions.md | 9 +- .../using-workflow-run-logs.md | 2 +- .../about-github-hosted-runners.md | 20 +- ...hing-dependencies-to-speed-up-workflows.md | 2 +- ...self-hosted-runners-for-your-enterprise.md | 2 +- ...-hosted-runners-without-internet-access.md | 2 +- .../about-saml-for-enterprise-iam.md | 2 + ...saml-single-sign-on-for-your-enterprise.md | 6 +- .../audit-log-events-for-your-enterprise.md | 14 +- ...es-in-the-audit-log-for-your-enterprise.md | 6 - .../overview/about-enterprise-accounts.md | 4 +- ...adding-organizations-to-your-enterprise.md | 5 +- .../auditing-ssh-keys.md | 6 +- ...authentication-with-saml-single-sign-on.md | 21 +- .../about-ssh.md | 2 - ...ng-a-new-ssh-key-to-your-github-account.md | 4 +- .../sudo-mode.md | 81 ++++++- ...updating-your-github-access-credentials.md | 4 + ...ing-codeql-code-scanning-in-a-container.md | 8 +- .../about-dependabot-alerts.md | 4 +- ...he-detection-of-vulnerable-dependencies.md | 2 +- .../github-security-features.md | 23 +- .../securing-your-organization.md | 2 +- .../securing-your-repository.md | 2 +- .../secret-scanning/about-secret-scanning.md | 2 +- .../about-the-security-overview.md | 2 +- ...ltering-alerts-in-the-security-overview.md | 4 + .../viewing-the-security-overview.md | 2 + .../securing-builds.md | 2 +- ...loring-the-dependencies-of-a-repository.md | 2 +- .../creating-a-codespace.md | 12 +- .../about-github-advanced-security.md | 18 +- ...se-settings-for-your-private-repository.md | 2 +- .../guides/forming-calls-with-graphql.md | 1 - .../index.md | 4 +- .../learning-about-projects/about-projects.md | 22 +- .../best-practices-for-projects.md | 20 +- .../learning-about-projects/index.md | 4 +- .../quickstart-for-projects.md | 48 ++--- .../adding-items-to-your-project.md | 36 ++-- .../archiving-items-from-your-project.md | 26 +-- .../converting-draft-issues-to-issues.md | 22 +- .../managing-items-in-your-project/index.md | 6 +- .../adding-your-project-to-a-repository.md | 16 +- .../closing-and-deleting-your-projects.md | 6 +- .../managing-your-project/index.md | 4 +- .../managing-access-to-your-projects.md | 42 ++-- .../managing-visibility-of-your-projects.md | 18 +- .../about-date-fields.md | 16 +- .../about-iteration-fields.md | 40 ++-- .../about-single-select-fields.md | 32 +-- .../about-text-and-number-fields.md | 28 +-- .../deleting-fields.md | 10 +- .../understanding-field-types/index.md | 6 +- .../renaming-fields.md | 10 +- .../about-insights-for-projects.md | 22 +- .../configuring-charts.md | 20 +- .../creating-charts.md | 10 +- .../index.md | 4 +- .../about-issues.md | 2 +- .../linking-a-pull-request-to-an-issue.md | 2 +- ...-tracking-work-for-your-team-or-project.md | 139 ++++++------ .../quickstart.md | 4 +- .../customizing-your-organizations-profile.md | 28 +-- ...to-a-project-board-in-your-organization.md | 6 +- .../index.md | 6 +- ...-project-board-for-organization-members.md | 12 +- ...access-to-an-organization-project-board.md | 14 +- ...access-to-an-organization-project-board.md | 20 +- .../repository-roles-for-an-organization.md | 198 +++++++++--------- ...visibility-changes-in-your-organization.md | 2 +- ...ights-for-projects-in-your-organization.md | 2 +- ...ess-management-with-saml-single-sign-on.md | 4 +- .../about-github-pages.md | 1 + ...eleting-branches-within-your-repository.md | 4 + .../overview/resources-in-the-rest-api.md | 2 +- .../searching-for-repositories.md | 2 +- .../features/create-branch-from-overview.yml | 5 + .../security-overview-displayed-alerts.yml | 6 + .../totp-and-mobile-sudo-challenge.yml | 5 + .../graphql_upcoming_changes.public-ghae.yml | 14 +- .../ghec/graphql_upcoming_changes.public.yml | 14 +- .../graphql_upcoming_changes.public.yml | 14 +- .../section-choosing-the-runner-for-a-job.md | 4 +- .../reusables/actions/macos-runner-preview.md | 2 +- .../data/reusables/actions/pure-javascript.md | 2 +- .../actions/supported-github-runners.md | 4 +- .../creating-a-codespace-in-vscode.md | 6 +- .../gated-features/advanced-security.md | 1 - .../data/reusables/gated-features/ghas.md | 2 +- .../gated-features/security-overview.md | 13 +- .../reusables/projects/add-draft-issue.md | 2 +- .../reusables/projects/add-item-via-paste.md | 2 +- .../projects/enable-basic-workflow.md | 12 +- .../reusables/projects/project-settings.md | 2 +- .../reusables/projects/reopen-a-project.md | 2 +- .../reusables/saml/dotcom-saml-explanation.md | 2 +- .../saml/outside-collaborators-exemption.md | 5 +- .../data/reusables/saml/saml-accounts.md | 6 +- .../information-varies-GHAS.md | 3 + .../user-settings/sudo-mode-popup.md | 4 +- translations/log/ja-resets.csv | 1 + 107 files changed, 731 insertions(+), 614 deletions(-) create mode 100644 translations/ja-JP/data/features/create-branch-from-overview.yml create mode 100644 translations/ja-JP/data/features/security-overview-displayed-alerts.yml create mode 100644 translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml delete mode 100644 translations/ja-JP/data/reusables/gated-features/advanced-security.md create mode 100644 translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md index 73254d889d..54dce91ea3 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md @@ -36,4 +36,4 @@ shortTitle: Ownership continuity 3. [Successor settings] で後継者を招待し、ユーザ名、フルネーム、メールアドレスを入力して、名前が必要されたらそれをクリックします。 ![後継者招待の検索フィールド](/assets/images/help/settings/settings-invite-successor-search-field.png) 4. [**Add successor**] をクリックします。 {% data reusables.user-settings.sudo-mode-popup %} -5. 招待したユーザーは、後継者になることに合意するまで "Pending" としてリストされます。 ![後継者招待が Pending](/assets/images/help/settings/settings-pending-successor.png) +6. 招待したユーザーは、後継者になることに合意するまで "Pending" としてリストされます。 ![後継者招待が Pending](/assets/images/help/settings/settings-pending-successor.png) diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md index 941d889e9d..01aee641b7 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md @@ -32,7 +32,7 @@ shortTitle: 継続的インテグレーション ## {% data variables.product.prodname_actions %} を使用する継続的インテグレーションについて {% ifversion ghae %}{% data variables.product.prodname_actions %} を使用する CI は、リポジトリにコードをビルドしてテストを実行できるワークフローが利用できます。 Workflows can run on runner systems that you host. 詳しい情報については「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners)」を参照してください。 -{% else %}{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ中のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 詳しい情報については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」および「[セルフホストランナーについて](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)」を参照してください。 +{% else %}{% data variables.product.prodname_actions %} を利用した CI では、リポジトリ中のコードをビルドしてテストを実行できるワークフローが利用できます。 ワークフローは、{% data variables.product.prodname_dotcom %} でホストされている仮想マシン、または自分がホストしているマシンで実行できます。 For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)." {% endif %} CIワークフローは、{% data variables.product.prodname_dotcom %}イベントが発生する (たとえば、新しいコードがリポジトリにプッシュされ) とき、または設定したスケジュールに応じて、あるいはリポジトリディスパッチwebhookを使用して外部イベントが発生するときに実行されるように設定することができます。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md index 5780a6fe0d..8b2cf5626e 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-xamarin-applications.md @@ -28,8 +28,8 @@ shortTitle: Build & test Xamarin apps For a full list of available Xamarin SDK versions on the {% data variables.product.prodname_actions %}-hosted macOS runners, see the documentation: -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles) {% data reusables.actions.macos-runner-preview %} diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md index 19e28b3dae..240ebbf8c3 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-docker-container-action.md @@ -39,7 +39,7 @@ shortTitle: Docker container action {% ifversion ghae %} - 「[Docker コンテナファイルシステム](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)」 {% else %} -- [{% data variables.product.prodname_dotcom %}の仮想環境](/actions/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners#docker-container-filesystem) +- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)" {% endif %} 始める前に、{% data variables.product.prodname_dotcom %} リポジトリを作成する必要があります。 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 e252ca1561..c6fa4237a6 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 @@ -74,7 +74,7 @@ To access the environment variable in a Docker container action, you must pass t ### `inputs..required` -**必須** この入力パラメーターがアクションに必須かどうかを示す`論理値`。 パラメーターが必須の場合は`true`に設定してください。 +**Optional** A `boolean` to indicate whether the action requires the input parameter. パラメーターが必須の場合は`true`に設定してください。 ### `inputs..default` diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 316ebc58ae..d24fc59b63 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -37,7 +37,7 @@ CircleCIから移行する際には、以下の差異を考慮してください - CircleCIの自動テストの並列性は、ユーザが指定したルールもしくは過去のタイミングの情報に基づいて、自動的にテストをグループ化します。 この機能は{% data variables.product.prodname_actions %}には組み込まれていません。 - コンテナはユーザのマッピングが異なるので、Dockerコンテナ内で実行されるアクションは、権限の問題に敏感です。 これらの問題の多くは、*Dockerfile*中で`USER`命令を使わなければ回避できます。 {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} -{% else %}{% data variables.product.product_name %}ホストランナー上の Docker のファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %} ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 +{% else %}For more information about the Docker filesystem on {% data variables.product.product_name %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." {% endif %} ## ワークフローとジョブの移行 @@ -66,10 +66,10 @@ Docker ファイルシステムの詳細については、「[Docker コンテ {% data reusables.actions.self-hosted-runners-software %} {% else %} -Dockerのファイルシステムに関する詳しい情報については「[{% data variables.product.product_name %}ホストランナーの仮想環境](/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem)」を参照してください。 +For more information about the Docker filesystem, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)." ー -{% data variables.product.prodname_dotcom %} ホストの仮想環境で使用できるツールとパッケージの詳細については、「[{% data variables.product.prodname_dotcom %} ホストランナーの仕様](/actions/reference/specifications-for-github-hosted-runners/#supported-software)」を参照してください。 +{% data variables.product.prodname_dotcom %}-hosted runner images, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". {% endif %} ## 変数とシークレットの利用 @@ -287,7 +287,8 @@ jobs: steps: # This Docker file changes sets USER to circleci instead of using the default user, so we need to update file permissions for this image to work on GH Actions. - # See https://docs.github.com/actions/reference/virtual-environments-for-github-hosted-runners#docker-container-filesystem + # See https://docs.github.com/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem + - name: Setup file system permissions run: sudo chmod -R 777 $GITHUB_WORKSPACE /github /__w/_temp - uses: {% data reusables.actions.action-checkout %} diff --git a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md index e83742f53b..e98483ae8a 100644 --- a/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md +++ b/translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md @@ -27,7 +27,7 @@ versions: ワークフローファイルで設定されたステップに加えて、{% data variables.product.prodname_dotcom %} はジョブの実行をセットアップして完了するために、各ジョブに 2 つの追加ステップを追加します。 これらのステップは、「Set up job」および「Complete job」として実行されるワークフローに記録されます。 -{% data variables.product.prodname_dotcom %}ホストランナー上のジョブの実行では、"Set up job"はランナーの仮想環境の詳細を記録し、ランナーマシン上にあったプリインストールされたツールのリストへのリンクを含みます。 +For jobs run on {% data variables.product.prodname_dotcom %}-hosted runners, "Set up job" records details of the runner image, and includes a link to the list of preinstalled tools that were present on the runner machine. {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index eb6456168e..38cebfc663 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -105,18 +105,18 @@ macOS 仮想マシンのハードウェア仕様: {% data variables.product.prodname_dotcom %} ホストランナーに含まれているソフトウェアツールは毎週更新されます。 The update process takes several days, and the list of preinstalled software on the `main` branch is updated after the whole deployment ends. ### Preinstalled software -ワークフローログには、正確なランナーにプレインストールされているツールへのリンクが含まれています。 ワークフローログでこの情報を見つけるには、[`Set up job`] セクションを展開します。 そのセクションの下で、[`Virtual Environment`] セクションを展開します。 The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 詳しい情報については、「[ワークフローの実行履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 +ワークフローログには、正確なランナーにプレインストールされているツールへのリンクが含まれています。 ワークフローログでこの情報を見つけるには、[`Set up job`] セクションを展開します。 Under that section, expand the `Runner Image` section. The link following `Included Software` will describe the preinstalled tools on the runner that ran the workflow. ![Installed software link](/assets/images/actions-runner-installed-software-link.png) 詳しい情報については、「[ワークフローの実行履歴を表示する](/actions/managing-workflow-runs/viewing-workflow-run-history)」を参照してください。 For the overall list of included tools for each runner operating system, see the links below: -* [Ubuntu 22.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2204-Readme.md) -* [Ubuntu 20.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md) -* [Ubuntu 18.04 LTS](https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu1804-Readme.md) -* [Windows Server 2022](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2022-Readme.md) -* [Windows Server 2019](https://github.com/actions/virtual-environments/blob/main/images/win/Windows2019-Readme.md) -* [macOS 12](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-12-Readme.md) -* [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md) -* [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md) +* [Ubuntu 22.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2204-Readme.md) +* [Ubuntu 20.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu2004-Readme.md) +* [Ubuntu 18.04 LTS](https://github.com/actions/runner-images/blob/main/images/linux/Ubuntu1804-Readme.md) +* [Windows Server 2022](https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md) +* [Windows Server 2019](https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md) +* [macOS 12](https://github.com/actions/runner-images/blob/main/images/macos/macos-12-Readme.md) +* [macOS 11](https://github.com/actions/runner-images/blob/main/images/macos/macos-11-Readme.md) +* [macOS 10.15](https://github.com/actions/runner-images/blob/main/images/macos/macos-10.15-Readme.md) {% data variables.product.prodname_dotcom %}ホストランナーには、オペレーティングシステムのデフォルトの組み込みツールに加え、上のリファレンスのリスト内のパッケージにが含まれています。 たとえば、Ubuntu及びmacOSのランナーには、`grep`、`find`、`which`やその他のデフォルトのツールが含まれています。 @@ -126,7 +126,7 @@ For the overall list of included tools for each runner operating system, see the - アクションでは通常、バージョンの選択、引数を渡す機能、パラメータなどの機能が提供されています - これにより、ソフトウェアの更新に関係なく、ワークフローで使用されるツールのバージョンが同じままになります -リクエストしたいツールがある場合、[actions/virtual-environments](https://github.com/actions/virtual-environments) で Issue を開いてください。 このリポジトリには、ランナーに関するすべての主要なソフトウェア更新に関するお知らせも含まれています。 +If there is a tool that you'd like to request, please open an issue at [actions/runner-images](https://github.com/actions/runner-images). このリポジトリには、ランナーに関するすべての主要なソフトウェア更新に関するお知らせも含まれています。 ### Installing additional software diff --git a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index 4280d9e7de..cae3ee1894 100644 --- a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -20,7 +20,7 @@ miniTocMaxHeadingLevel: 3 ワークフローの実行は、しばしば他の実行と同じ出力あるいはダウンロードされた依存関係を再利用します。 たとえばMaven、Gradle、npm、Yarnといったパッケージ及び依存関係管理ツールは、ダウンロードされた依存関係のローカルキャッシュを保持します。 -{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows. +{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean runner image and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows. To cache dependencies for a job, you can use {% data variables.product.prodname_dotcom %}'s [`cache` action](https://github.com/actions/cache). The action creates and restores a cache identified by a unique key. Alternatively, if you are caching the package managers listed below, using their respective setup-* actions requires minimal configuration and will create and restore dependency caches for you. diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md index a47693dade..2dab1e7ae7 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md @@ -146,7 +146,7 @@ Optionally, you can build custom tooling to automatically scale the self-hosted - "Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}" in the [{% data variables.product.prodname_ghe_server %}](/enterprise-server@latest/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) or [{% data variables.product.prodname_ghe_managed %}](/github-ae@latest//admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect) documentation {%- endif %} -- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/virtual-environments`](https://github.com/actions/virtual-environments) repositories. +- You can customize the software available on your self-hosted runner machines, or configure your runners to run software similar to {% data variables.product.company_short %}-hosted runners{% ifversion ghes or ghae %} available for customers using {% data variables.product.prodname_dotcom_the_website %}{% endif %}. The software that powers runner machines for {% data variables.product.prodname_actions %} is open source. For more information, see the [`actions/runner`](https://github.com/actions/runner) and [`actions/runner-images`](https://github.com/actions/runner-images) repositories. ## 参考リンク diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md index f19b8e5278..367ced039b 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md @@ -30,7 +30,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr {% note %} -**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[Virtual environments for GitHub-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." +**Note:** You can only use a {% data variables.product.prodname_dotcom %}-hosted runner's tool cache for a self-hosted runner that has an identical operating system and architecture. For example, if you are using a `ubuntu-18.04` {% data variables.product.prodname_dotcom %}-hosted runner to generate a tool cache, your self-hosted runner must be a 64-bit Ubuntu 18.04 machine. For more information on {% data variables.product.prodname_dotcom %}-hosted runners, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/free-pro-team@latest/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources)." {% endnote %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index 042ecc2b2b..1308198d54 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -30,6 +30,8 @@ redirect_from: If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} +{% data reusables.saml.saml-accounts %} + {% data reusables.saml.about-saml-enterprise-accounts %}詳しい情報については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md index 228e1477c0..1d5f052d14 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md @@ -29,7 +29,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} 詳細は「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」を参照してください。 +{% data reusables.saml.dotcom-saml-explanation %} + +{% data reusables.saml.saml-accounts %} + +For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." {% data reusables.saml.about-saml-enterprise-accounts %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index bb1cdd3ba2..7e0c84eedc 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -418,13 +418,13 @@ Before you'll see `git` category actions, you must enable Git events in the audi ## `integration_installation`category actions -| アクション | 説明 | -| ------------------------------------------------ | ----------------------------------------------- | -| `integration_installation.contact_email_changed` | A contact email for an integration was changed. | -| `integration_installation.create` | An integration was installed. | -| `integration_installation.destroy` | An integration was uninstalled. | -| `integration_installation.repositories_added` | Repositories were added to an integration. | -| `integration_installation.repositories_removed` | Repositories were removed from an integration. | +| アクション | 説明 | +| ------------------------------------------------ | ------------------------- | +| `integration_installation.contact_email_changed` | インテグレーションの連絡先メールが変更されました。 | +| `integration_installation.create` | インテグレーションがインストールされました。 | +| `integration_installation.destroy` | インテグレーションがアンインストールされました。 | +| `integration_installation.repositories_added` | インテグレーションにリポジトリが追加されました。 | +| `integration_installation.repositories_removed` | インテグレーションからリポジトリが削除されました。 | {%- ifversion fpt or ghec %} | `integration_installation.suspend` | An integration was suspended. | `integration_installation.unsuspend` | An integration was unsuspended. {%- endif %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index d5240df0e0..37ce5c99c0 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -14,12 +14,6 @@ topics: - Security --- -{% note %} - -**Note:** Display of IP addresses in the enterprise audit log is currently in public beta and is subject to change. - -{% endnote %} - ## About display of IP addresses in the audit log By default, {% data variables.product.product_name %} does not display the source IP address for events in your enterprise's audit log. Optionally, to ensure compliance and respond to threats, you can display the full IP address associated with the actor responsible for each event. Actors are typically users, but can also be apps or integrations. diff --git a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md index ce0b3dfeef..38233a46b1 100644 --- a/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md +++ b/translations/ja-JP/content/admin/overview/about-enterprise-accounts.md @@ -35,14 +35,14 @@ The enterprise account on {% ifversion ghes %}{% data variables.product.product_ Organizations are shared accounts where enterprise members can collaborate across many projects at once. Organization owners can manage access to the organization's data and projects with sophisticated security and administrative features. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。 {% ifversion ghec %} -Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. +Enterprise owners can invite existing organizations to join your enterprise account, or create new organizations in the enterprise settings. 詳しい情報については「[EnterpriseへのOrganizationの追加](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)」を参照してください。 {% endif %} Your enterprise account allows you to manage and enforce policies for all the organizations owned by the enterprise. {% data reusables.enterprise.about-policies %} For more information, see "[About enterprise policies](/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies)." {% ifversion ghec %} -{% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." +{% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md index 06a647f299..ed361ffe3c 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md @@ -14,15 +14,16 @@ topics: - Enterprise - Organizations shortTitle: Add organizations +permissions: Enterprise owners can add organizations to an enterprise. --- ## Organizationについて Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 詳細は「[Organization について](/organizations/collaborating-with-groups-in-organizations/about-organizations)」を参照してください。 -Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings. +You can add a new or existing organization to your enterprise in your enterprise account's settings. -You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)." +You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} 詳しい情報については「[Enterpriseアカウントの作成](/admin/overview/creating-an-enterprise-account)」を参照してください。 ## Enterprise アカウント内で Organization を作成する diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md index 0c85dd65ca..cc5bc9e133 100644 --- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md +++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/auditing-ssh-keys.md @@ -50,9 +50,11 @@ fatal: The remote end hung up unexpectedly ## SSH キーを追加する -新規ユーザは、SSHキーを追加する際にパスワードを要求されます。 +{% ifversion ghes %} -![パスワードの確認](/assets/images/help/settings/sudo_mode_popup.png) +When a new user adds an SSH key to an account, to confirm the user's access, {% data variables.product.product_name %} will prompt for authentication. For more information, see "[Sudo mode](/authentication/keeping-your-account-and-data-secure/sudo-mode)." + +{% endif %} ユーザがキーを追加したら、次のような通知メールが届きます。 diff --git a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md index fddbc48cd8..4ddcce7730 100644 --- a/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md @@ -1,6 +1,6 @@ --- title: SAMLのシングルサインオンでの認証について -intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).{% ifversion ghec %} After you authenticate with the IdP successfully from {% data variables.product.product_name %}, you must authorize any personal access token, SSH key, or {% data variables.product.prodname_oauth_app %} you would like to access the organization''s resources.{% endif %}' +intro: 'You can access {% ifversion ghae %}{% data variables.product.product_location %}{% elsif ghec %}an organization that uses SAML single sign-on (SSO){% endif %} by authenticating {% ifversion ghae %}with SAML single sign-on (SSO) {% endif %}through an identity provider (IdP).' redirect_from: - /articles/about-authentication-with-saml-single-sign-on - /github/authenticating-to-github/about-authentication-with-saml-single-sign-on @@ -29,10 +29,9 @@ SAML SSO を使用すると、Enterprise のオーナーは、SAML IdP から {% {% data reusables.saml.dotcom-saml-explanation %} Organization owners can invite your personal account on {% data variables.product.prodname_dotcom %} to join their organization that uses SAML SSO, which allows you to contribute to the organization and retain your existing identity and contributions on {% data variables.product.prodname_dotcom %}. -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will use a new account that is provisioned for you. {% data reusables.enterprise-accounts.emu-more-info-account %} +If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will instead use a new account that is provisioned for you and controlled by your enterprise. {% data reusables.enterprise-accounts.emu-more-info-account %} - -SAML SSO を使用する Organization のリソースにアクセスすると、{% data variables.product.prodname_dotcom %}は認証のために Organization の SAML IdP にリダイレクトします。 IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 +When you access private resources within an organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} will redirect you to the organization's SAML IdP to authenticate. IdP でアカウントが正常に認証されると、IdP は{% data variables.product.prodname_dotcom %}に戻り、Organization のリソースにアクセスできます。 {% data reusables.saml.outside-collaborators-exemption %} @@ -40,6 +39,16 @@ SAML SSO を使用する Organization のリソースにアクセスすると、 {% data reusables.saml.you-must-periodically-authenticate %} +## Linked SAML identities + +When you authenticate with your IdP account and return to {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_dotcom %} will record a link in the organization or enterprise between your {% data variables.product.prodname_dotcom %} personal account and the SAML identity you signed into. This linked identity is used to validate your membership in that organization, and depending on your organization or enterprise setup, is also used to determine which organizations and teams you're a member of as well. Each {% data variables.product.prodname_dotcom %} account can be linked to exactly one SAML identity per organization. Likewise, each SAML identity can be linked to exactly one {% data variables.product.prodname_dotcom %} account in an organization. + +If you sign in with a SAML identity that is already linked to another {% data variables.product.prodname_dotcom %} account, you will receive an error message indicating that you cannot sign in with that SAML identity. This situation can occur if you are attempting to use a new {% data variables.product.prodname_dotcom %} account to work inside of your organization. If you didn't intend to use that SAML identity with that {% data variables.product.prodname_dotcom %} account, then you'll need to sign out of that SAML identity and then repeat the SAML login. If you do want to use that SAML identity with your {% data variables.product.prodname_dotcom %} account, you'll need to ask your admin to unlink your SAML identity from your old account, so that you can link it to your new account. Depending on the setup of your organization or enterprise, your admin may also need to reassign your identity within your SAML provider. 詳細は、「[Organizationへのメンバーの SAML アクセスの表示と管理](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)」を参照してください。 + +If the SAML identity you sign in with does not match the SAML identity that is currently linked to your {% data variables.product.prodname_dotcom %} account, you'll receive a warning that you are about to relink your account. Because your SAML identity is used to govern access and team membership, continuing with the new SAML identity can cause you to lose access to teams and organizations inside of {% data variables.product.prodname_dotcom %}. Only continue if you know that you're supposed to use that new SAML identity for authentication in the future. + +## Authorizing PATs and SSH keys with SAML SSO + SAML SSL を要求する Organization 内の保護されたコンテンツにアクセスするために API またはコマンドライン上の Git を利用するには、認可された個人のアクセストークンを HTTPS 経由で使うか、認可された SSH キーを使う必要があります。 個人のアクセストークンあるいは SSH キーを持っていない場合、コマンドライン用の個人のアクセストークンを作成するか、新しい SSH キーを生成できます。 詳しい情報については、「[個人アクセストークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token)」または「[新しい SSH キーを生成して ssh-agent へ追加する](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)」を参照してください。 @@ -58,5 +67,5 @@ To see the {% data variables.product.prodname_oauth_apps %} you've authorized, v ## 参考リンク -{% ifversion ghec %}- "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)"{% endif %} -{% ifversion ghae %}- "[About identity and access management for your enterprise](/admin/authentication/about-identity-and-access-management-for-your-enterprise)"{% endif %} +{% ifversion ghec %}- 「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)」{% endif %} +{% ifversion ghae %}- 「[SAML シングルサインオンを使うアイデンティティおよびアクセス管理について](/admin/authentication/about-identity-and-access-management-for-your-enterprise)」{% endif %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md index e64b6f397c..5293b50d56 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/about-ssh.md @@ -14,8 +14,6 @@ topics: - SSH --- -## SSH について - {% data reusables.ssh.about-ssh %} For more information about SSH, see [Secure Shell](https://en.wikipedia.org/wiki/Secure_Shell) on Wikipedia. When you set up SSH, you will need to generate a new private SSH key and add it to the SSH agent. You must also add the public SSH key to your account on {% data variables.product.product_name %} before you use the key to authenticate. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)" and "[Adding a new SSH key to your {% data variables.product.prodname_dotcom %} account](/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account)." diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md index e00b4bd018..06825e0163 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md @@ -90,7 +90,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab 5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) -8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{% data reusables.user-settings.sudo-mode-popup %} {% endwebui %} @@ -122,7 +122,7 @@ After adding a new SSH key to your account on {% ifversion ghae %}{% data variab 5. [Title] フィールドで、新しいキーを説明するラベルを追加します。 たとえば、個人のMacを使っているなら、このキーを「Personal MacBook Air」とすることができるでしょう。 6. キーを [Key] フィールドに貼り付けます。 ![キーフィールド](/assets/images/help/settings/ssh-key-paste.png) 7. **[Add SSH key]** をクリックしてください。 ![キーの追加ボタン](/assets/images/help/settings/ssh-add-key.png) -8. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{% data reusables.user-settings.sudo-mode-popup %} {% endwebui %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md index 59f3c82976..7232bec404 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md @@ -1,6 +1,6 @@ --- title: Sudo モード -intro: '{% data variables.product.product_name %} は、メールアドレスの修正、第三者のアプリケーションの許可や新しい公開鍵の追加前、または、sudo でプロテクトされたアクションを開始する前に、パスワードを尋ねます。' +intro: 'To confirm access to your account before you perform a potentially sensitive action, {% data variables.product.product_location %} prompts for authentication.' redirect_from: - /articles/sudo-mode - /github/authenticating-to-github/sudo-mode @@ -9,15 +9,86 @@ versions: fpt: '*' ghes: '*' ghec: '*' +miniTocMaxHeadingLevel: 3 topics: - Identity - Access management --- -sudoでプロテクトされたアクションを実行したあとは、数時間アクションがない場合に限り、再認証を要求されます。 Sudo でプロテクトされたアクションを行った場合、このタイマーはリセットされます。 +## About sudo mode -![Sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +To maintain the security of your account when you perform a potentially sensitive action on {% data variables.product.product_location %}, you must authenticate even though you're already signed in. For example, {% data variables.product.company_short %} considers the following actions sensitive because each action could allow a new person or system to access your account. -## 参考リンク +- Modification of an associated email address +- Authorization of a third-party application +- Addition of a new SSH key -- [Unix `sudo` コマンド](http://en.wikipedia.org/wiki/Sudo) +After you authenticate to perform a sensitive action, your session is temporarily in "sudo mode." In sudo mode, you can perform sensitive actions without authentication. {% data variables.product.product_name %} will wait a few hours before prompting you for authentication again. During this time, any sensitive action that you perform will reset the timer. + +{% ifversion ghes %} + +{% note %} + +**Note**: If {% data variables.product.product_location %} uses an external authentication method like CAS or SAML SSO, you will not receive prompts to enter sudo mode. 詳しい情報については、サイト管理者にお問い合わせください。 + +{% endnote %} + +{% endif %} + +"sudo" is a reference to a program on Unix systems, where the name is short for "**su**peruser **do**." For more information, see [sudo](https://wikipedia.org/wiki/Sudo) on Wikipedia. + +## Confirming access for sudo mode + +To confirm access for sudo mode, you {% ifversion totp-and-mobile-sudo-challenge %}can{% else %}must{% endif %} authenticate with your password.{% ifversion totp-and-mobile-sudo-challenge %} Optionally, you can use a different authentication method, like {% ifversion fpt or ghec %}a security key, {% data variables.product.prodname_mobile %}, or a 2FA code{% elsif ghes %}a security key or a 2FA code{% endif %}.{% endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} +- [Confirming access using a security key](#confirming-access-using-a-security-key) +{%- ifversion fpt or ghec %} +- [Confirming access using GitHub Mobile](#confirming-access-using-github-mobile) +{%- endif %} +- [Confirming access using a 2FA code](#confirming-access-using-a-2fa-code) +- [Confirming access using your password](#confirming-access-using-your-password) + +### Confirming access using a security key + +You must configure two-factor authentication (2FA) for your account using a security key to confirm access to your account for sudo mode using the security key. 詳しい情報については、「[2 要素認証を設定する](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)」を参照してください。 + +When prompted to authenticate for sudo mode, click **Use security key**, then follow the prompts. + +![Screenshot of security key option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_security_key.png) + +{% endif %} + +{% ifversion fpt or ghec %} + +### Confirming access using {% data variables.product.prodname_mobile %} + +You must install and sign into {% data variables.product.prodname_mobile %} to confirm access to your account for sudo mode using the app. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)." + +1. When prompted to authenticate for sudo mode, click **Use GitHub Mobile**. + + ![Screenshot of {% data variables.product.prodname_mobile %} option for sudo mode](/assets/images/help/settings/sudo_mode_prompt_github_mobile_prompt.png) +1. Open {% data variables.product.prodname_mobile %}. {% data variables.product.prodname_mobile %} will display numbers that you must enter on {% data variables.product.product_location %} to approve the request. + + ![Screenshot of numbers from {% data variables.product.prodname_mobile %} to enter on {% data variables.product.product_name %} to approve sudo mode access](/assets/images/help/settings/sudo_mode_prompt_github_mobile.png) +1. On {% data variables.product.product_name %}, type the numbers displayed in {% data variables.product.prodname_mobile %}. + +{% endif %} + +{% ifversion totp-and-mobile-sudo-challenge %} + +### Confirming access using a 2FA code + +You must configure 2FA using a TOTP mobile app{% ifversion fpt or ghec %} or text messages{% endif %} to confirm access to your account for sudo mode using a 2FA code. 詳しい情報については、「[2 要素認証を設定する](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)」を参照してください。 + +When prompted to authenticate for sudo mode, type the authentication code from your TOTP mobile app{% ifversion fpt or ghec %} or the text message{% endif %}, then click **Verify**. + +![Screenshot of 2FA code prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_2fa_code.png) + +### Confirming access using your password + +{% endif %} + +When prompted to authenticate for sudo mode, type your password, then click **Confirm**. + +![Screenshot of password prompt for sudo mode](/assets/images/help/settings/sudo_mode_prompt_password.png) diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md index c6c10d3caf..4e61ee5158 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md @@ -25,14 +25,18 @@ shortTitle: Update access credentials ![Password reset email request dialog](/assets/images/help/settings/password-recovery-email-request.png) 3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder. 4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials: +{% ifversion fpt or ghec %} * If you have {% data variables.product.prodname_mobile %}, you will be sent a push notification to verify your identity. Open the push notification or the {% data variables.product.prodname_mobile %} app and enter the two-digit code shown to you on the password reset page in your browser. ![Two-factor {% data variables.product.prodname_mobile %} authentication prompt](/assets/images/help/2fa/2fa-mobile-challenge-password-reset.png) * To skip using GitHub Mobile to verify, click **Enter two-factor authentication or recovery code**. ![Two-factor GitHub Mobile authentication prompt on {% data variables.product.product_name %} with "Enter two-factor authentication or recovery code" highlighted](/assets/images/help/2fa/2fa-github-mobile-password-reset.png) +{% endif %} * Type your authentication code or one of your recovery codes and click **Verify**. ![Two-factor authentication prompt](/assets/images/help/2fa/2fa-password-reset.png) * If you have added a security key to your account, click **Use security key** instead of typing an authentication code. + {% ifversion fpt or ghec %} * If you have set up [{% data variables.product.prodname_mobile %}](https://github.com/mobile), click **Authenticate with GitHub Mobile** instead. + {% endif %} 5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)." {% ifversion fpt or ghec %}![Password recovery box](/assets/images/help/settings/password-recovery-page.png){% else %} ![Password recovery box](/assets/images/enterprise/settings/password-recovery-page.png){% endif %} diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 729a1e93f7..686a099b7b 100644 --- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -34,11 +34,11 @@ topics: ## 依存関係 -使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、{% data variables.product.prodname_dotcom %} の仮想環境に通常含まれているソフトウェアのリストを確認してください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。 +使用しているコンテナで特定の依存関係がない場合 (たとえば、Git は PATH 変数にインストールされ、追加されている必要がある)、{% data variables.product.prodname_code_scanning %} を実行する上で困難が生じる場合があります。 依存関係の問題が生じた場合は、通常{% data variables.product.prodname_dotcom %}のランナーのイメージに含まれているソフトウェアのリストをレビューしてください。 詳しい情報については、次の場所にある特定のバージョンの `readme` ファイルを参照してください。 -* Linux: https://github.com/actions/virtual-environments/tree/main/images/linux -* macOS: https://github.com/actions/virtual-environments/tree/main/images/macos -* Windows: https://github.com/actions/virtual-environments/tree/main/images/win +* Linux: https://github.com/actions/runner-images/tree/main/images/linux +* macOS: https://github.com/actions/runner-images/tree/main/images/macos +* Windows: https://github.com/actions/runner-images/tree/main/images/win ## ワークフローの例 diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index c900d9dfe1..5bbb673719 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -88,7 +88,7 @@ For repositories where {% data variables.product.prodname_dependabot_security_up ## Access to {% data variables.product.prodname_dependabot_alerts %} -You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." +You can see all of the alerts that affect a particular project{% ifversion fpt or ghec %} on the repository's Security tab or{% endif %} in the repository's dependency graph. For more information, see "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)." By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} never publicly discloses insecure dependencies for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working with repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." {% endif %} @@ -102,5 +102,5 @@ You can also see all the {% data variables.product.prodname_dependabot_alerts %} ## Further reading - "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% endif %} {% ifversion fpt or ghec %}- "[Privacy on {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index b94ae151ca..0344ac5067 100644 --- a/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -93,7 +93,7 @@ You can configure {% data variables.product.prodname_dependabot %} to ignore spe ## Further reading - "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/github-security-features.md b/translations/ja-JP/content/code-security/getting-started/github-security-features.md index 19978f53ae..bc033f52bd 100644 --- a/translations/ja-JP/content/code-security/getting-started/github-security-features.md +++ b/translations/ja-JP/content/code-security/getting-started/github-security-features.md @@ -58,8 +58,15 @@ The dependency graph allows you to explore the ecosystems and packages that your You can find the dependency graph on the **Insights** tab for your repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)." +{% ifversion security-overview-displayed-alerts %} +### Security overview + +The security overview allows you to review security configurations and alerts, making it easy to identify the repositories and organizations at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + +{% else %} ### Security overview for repositories -For all public repositories, the security overview shows which security features are enabled for the repository, and offers the option to configure any available security features that are not currently enabled. +The security overview shows which security features are enabled for the repository, and offers you the option of configuring any available security features that are not already enabled. +{% endif %} ## Available with {% data variables.product.prodname_GH_advanced_security %} @@ -67,7 +74,7 @@ For all public repositories, the security overview shows which security features The following {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with a license for {% data variables.product.prodname_GH_advanced_security %} can use the full set of features in any of their repositories. For a list of the features available with {% data variables.product.prodname_ghe_cloud %}, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/getting-started/github-security-features#available-with-github-advanced-security). {% elsif ghec %} -Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that has a {% data variables.product.prodname_GH_advanced_security %} license can use all the following features on their repositories. {% data reusables.advanced-security.more-info-ghas %} +Many {% data variables.product.prodname_GH_advanced_security %} features are available and free of charge for public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations within an enterprise that have a {% data variables.product.prodname_GH_advanced_security %} license can use the following features on all their repositories. {% data reusables.advanced-security.more-info-ghas %} {% elsif ghes %} {% data variables.product.prodname_GH_advanced_security %} features are available for enterprises with a license for {% data variables.product.prodname_GH_advanced_security %}. The features are restricted to repositories owned by an organization. {% data reusables.advanced-security.more-info-ghas %} @@ -86,7 +93,7 @@ Automatically detect security vulnerabilities and coding errors in new or modifi Automatically detect leaked secrets across all public repositories. {% data variables.product.company_short %} informs the relevant service provider that the secret may be compromised. For details of the supported secrets and service providers, see "[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns)." {% endif %} -{% ifversion not fpt %} +{% ifversion ghec or ghes or ghae %} ### {% data variables.product.prodname_secret_scanning_GHAS_caps %} {% ifversion ghec %} @@ -100,12 +107,12 @@ Automatically detect tokens or credentials that have been checked into a reposit 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)." -{% ifversion ghec or ghes or ghae %} -### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams +{% ifversion security-overview-displayed-alerts %} -{% ifversion ghec %} -Available only with a license for {% data variables.product.prodname_GH_advanced_security %}. -{% endif %} +{% elsif fpt %} + +{% else %} +### Security overview for organizations{% ifversion ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams Review the security configuration and alerts for your organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md index 155ef044ab..e560122037 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-organization.md @@ -123,7 +123,7 @@ For more information, see "[Managing security and analysis settings for your org {% data variables.product.prodname_code_scanning_capc %} is configured at the repository level. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md index 9d2fbc8235..ec95d618b2 100644 --- a/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md +++ b/translations/ja-JP/content/code-security/getting-started/securing-your-repository.md @@ -132,7 +132,7 @@ You can set up {% data variables.product.prodname_code_scanning %} to automatica {% endif %} ## Next steps -You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +You can view and manage alerts from security features to address dependencies and vulnerabilities in your code. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)." {% endif %} diff --git a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md index d6d8def31e..481ec138e4 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md @@ -91,7 +91,7 @@ For more information about viewing and resolving {% data variables.product.prodn Repository administrators and organization owners can grant users and teams access to {% data variables.product.prodname_secret_scanning %} alerts. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)." -{% ifversion ghec or ghes %} +{% ifversion ghec or ghes or ghae-issue-5503 %} You can use the security overview to see an organization-level view of which repositories have enabled {% data variables.product.prodname_secret_scanning %} and the alerts found. For more information, see "[Viewing the security overview](/code-security/security-overview/viewing-the-security-overview)." {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md index d3f602193d..ba90d98e13 100644 --- a/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/about-the-security-overview.md @@ -43,7 +43,7 @@ In the security overview, you can view, sort, and filter alerts to understand th {% ifversion security-overview-views %} -In the security overview, at both the organization and repository level, there are dedicated views for specific security features, such as secret scanning alerts and code scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. +In the security overview, there are dedicated views for each type of security alert, such as Dependabot, code scanning, and secret scanning alerts. You can use these views to limit your analysis to a specific set of alerts, and narrow the results further with a range of filters specific to each view. For example, in the secret scanning alert view, you can use the `Secret type` filter to view only secret scanning alerts for a specific secret, like a GitHub Personal Access Token. At the repository level, you can use the security overview to assess the specific repository's current security status, and configure any additional security features not yet in use on the repository. {% endif %} diff --git a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md index 6c427b0e8a..1d6e0dba3a 100644 --- a/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md @@ -25,6 +25,10 @@ shortTitle: アラートのフィルタリング アラートのリスクレベル、アラートの種類、機能の有効化の状況といった様々な要素に基づいて焦点を絞り込むために、セキュリティの概要でフィルタを利用できます。 特定のビューや、分析がOrganization、Team、リポジトリのレベルなのかといったことに応じて、様々なフィルタが利用できます。 +{% note %} +{% data reusables.security-overview.information-varies-GHAS %} +{% endnote %} + ## リポジトリでフィルタリング すべてのOrganizationレベル及びTeamレベルのビューで利用可能。 diff --git a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md index e371b12dfc..728958e1ac 100644 --- a/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md +++ b/translations/ja-JP/content/code-security/security-overview/viewing-the-security-overview.md @@ -21,6 +21,8 @@ shortTitle: セキュリティの概要の表示 {% data reusables.security-overview.beta %} {% endif %} +{% data reusables.security-overview.information-varies-GHAS %} + ## Organizationのセキュリティの概要の表示 {% data reusables.organizations.navigate-to-org %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md index c381e02761..00e0bc5440 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md @@ -34,7 +34,7 @@ topics: 3. 侵害されたビルドが将来のビルドに影響し続けることがないよう、各ビルドは新しい環境で開始されなければなりません。 -{% data variables.product.prodname_actions %}は、これらの機能を満たすのに役立ちます。 ビルドの手順は、コードとともにリポジトリに保存されます。 ビルドが実行される環境は、Windows、Mac、Linux、自分でホストするランナーを含め、選択できます。 各ビルドは新しい仮想環境で開始され、攻撃がビルド環境に留まり続けるのを難しくします。 +{% data variables.product.prodname_actions %}は、これらの機能を満たすのに役立ちます。 ビルドの手順は、コードとともにリポジトリに保存されます。 ビルドが実行される環境は、Windows、Mac、Linux、自分でホストするランナーを含め、選択できます。 各ビルドは新しいランナーのイメージで開始され、攻撃がビルド環境に留まり続けるのを難しくします。 セキュリティ上の利点に加えて、{% data variables.product.prodname_actions %}はビルドを手動、定期的、リポジトリでのgitイベントでトリガーし、頻繁に高速なビルドを行えます。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index d5b1211fe0..172d711d88 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -110,7 +110,7 @@ Dependency submission API（ベータ）を使ってプロジェクトにサブ ## 参考リンク - [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) -- 「[{% data variables.product.prodname_dependabot_alerts %}の表示と更新](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)」{% ifversion ghec %} +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)"{% ifversion ghec %} - 「[Organizationのインサイトの表示](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)」{% endif %}{% ifversion fpt or ghec %} - [{% data variables.product.prodname_dotcom %}によるデータの利用と保護の方法の理解](/get-started/privacy-on-github) {% endif %} 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 668ab35ee1..d4164f266b 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 @@ -138,22 +138,18 @@ To create a new codespace, use the `gh codespace create` subcommand. gh codespace create ``` -You are prompted to choose a repository, a branch, and a machine type (if more than one is available). - -{% note %} - -**ノート**: 現在、{% data variables.product.prodname_cli %}ではcodespaceの作成時に開発コンテナの設定を選択することはできません。 特定の開発コンテナの設定を選択したい場合、{% data variables.product.prodname_dotcom %} Webインターフェースを使ってcodespaceを作成してください。 For more information, click the "Web browser" tab at the top of this page. - -{% endnote %} +You are prompted to choose a repository, a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available). Alternatively, you can use flags to specify some or all of the options: ```shell -gh codespace create -r owner/repo -b branch -m machine-type +gh codespace create -r owner/repo -b branch --devcontainer-path path -m machine-type ``` In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch. +Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." + Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list. For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create). 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 ec6b3b6496..f2774b816b 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 @@ -32,38 +32,28 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th - **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)." -{% ifversion ghec or ghes %} +{% ifversion ghes < 3.7 or ghae %} + - **Security overview** - Review the security configuration and alerts for an organization and identify the repositories at greatest risk. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." {% endif %} {% ifversion fpt or ghec %} The table below summarizes the availability of {% data variables.product.prodname_GH_advanced_security %} features for public and private repositories. -{% ifversion fpt %} | | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | | :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | | Code scanning | Yes | No | Yes | | Secret scanning | Yes **(limited functionality only)** | No | Yes | | Dependency review | Yes | No | Yes | -{% endif %} -{% ifversion ghec %} -| | Public repository | Private repository without {% data variables.product.prodname_advanced_security %} | Private repository with {% data variables.product.prodname_advanced_security %} | -| :-----------------: | :---------------------------: | :--------------------------------------------: | :-----------------------------------------: | -| Code scanning | Yes | No | Yes | -| Secret scanning | Yes **(limited functionality only)** | No | Yes | -| Dependency review | Yes | No | Yes | -| Security overview | No | No | Yes | -{% endif %} - {% endif %} For information about {% data variables.product.prodname_advanced_security %} features that are in development, see "[{% data variables.product.prodname_dotcom %} public roadmap](https://github.com/github/roadmap)." For an overview of all security features, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)." {% ifversion fpt or ghec %} -{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}{% ifversion ghec %}, except for the security overview{% endif %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. They also have access to an organization-level security overview. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} +{% data variables.product.prodname_GH_advanced_security %} features are enabled for all public repositories on {% data variables.product.prodname_dotcom_the_website %}. Organizations that use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_advanced_security %} can additionally enable these features for private and internal repositories. {% ifversion fpt %}For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/get-started/learning-about-github/about-github-advanced-security#enabling-advanced-security-features).{% endif %} {% endif %} -{% ifversion ghes > 3.1 or ghec %} +{% ifversion ghes > 3.1 or ghec or ghae %} ## Deploying GitHub Advanced Security in your enterprise To learn about what you need to know to plan your {% data variables.product.prodname_GH_advanced_security %} deployment at a high level and to review the rollout phases we recommended, see "[Adopting {% data variables.product.prodname_GH_advanced_security %} at scale](/code-security/adopting-github-advanced-security-at-scale)." diff --git a/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index b8025330c8..3b257f4052 100644 --- a/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -45,5 +45,5 @@ When you enable data use for your private repository, you'll be able to access t ## Further reading - "[About {% data variables.product.prodname_dotcom %}'s use of your data](/articles/about-github-s-use-of-your-data)" -- "[Viewing and updatng {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" +- "[Viewing and updating {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts)" - "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md index 3b5693c44b..3c1e663c39 100644 --- a/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md +++ b/translations/ja-JP/content/graphql/guides/forming-calls-with-graphql.md @@ -33,7 +33,6 @@ GraphQLサーバーと通信するには、適切なスコープを持つOAuth ``` repo -repo_deployment read:packages read:org read:public_key diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md index 85aefe6a1f..808fa924cd 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/index.md @@ -1,7 +1,7 @@ --- -title: 'Planning and tracking with {% data variables.product.prodname_projects_v2 %}' +title: '{% data variables.product.prodname_projects_v2 %}での計画と追跡' shortTitle: '{% data variables.product.prodname_projects_v2 %}' -intro: 'Build adaptable projects to track your work on {% data variables.product.company_short %}.' +intro: '{% data variables.product.company_short %}での作業を追跡するために、適応性のあるプロジェクトを構築してください。' versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md index 984016d45d..23db9c4d98 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects.md @@ -1,6 +1,6 @@ --- title: '{% data variables.product.prodname_projects_v2 %}について' -intro: '{% data variables.product.prodname_projects_v2 %} is an adaptable, flexible tool for planning and tracking work on {% data variables.product.company_short %}.' +intro: '{% data variables.product.prodname_projects_v2 %}は、{% data variables.product.company_short %}上の作業の計画と追跡のための、適応性のある柔軟なツールです。' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,25 +14,25 @@ topics: ## {% data variables.product.prodname_projects_v2 %}について -A project is an adaptable spreadsheet that integrates with your issues and pull requests on {% data variables.product.company_short %} to help you plan and track your work effectively. You can create and customize multiple views by filtering, sorting, grouping your issues and pull requests, adding custom fields to track metadata specific to your team, and visualize work with configurable charts. Rather than enforcing a specific methodology, a project provides flexible features you can customize to your team’s needs and processes. +プロジェクトは、{% data variables.product.company_short %}上のIssueやPull Requestと統合された適応性のあるスプレッドシートで、作業を効果的に計画し、追跡するのに役立ちます。 IssueやPull Requestをフィルタリングし、ソートし、グループ化して、チーム固有のメタデータを追跡するためのカスタムフィールドを追加し、設定可能なグラフで作業を可視化することによって、複数のビューを作成してカスタマイズできます。 プロジェクトは、特定の方法論を強制するのではなく、チームの要求やプロセスに合わせてカスタマイズ可能な重要な機能を提供します。 ### 最新の状態に保つ -Your projects are built from the issues and pull requests you add, creating direct references between your project and your work. Information is synced automatically to your project as you make changes, updating your views and charts. This integration works both ways, so that when you change information about a pull request or issue in your project, the pull request or issue reflects that information. For example, change an assignee in your project and that change is shown in your issue. You can take this integration even further, group your project by assignee, and make changes to issue assignment by dragging issues into the different groups. +プロジェクトは追加するIssueやPull Requestから構築され、プロジェクトと作業の間に直接の参照を作成します。 情報は変更があるたびにプロジェクトと自動的に同期され、ビューやグラフが更新されます。 この統合は双方向なので、Pull ReqeustやIssueに関する情報をプロジェクトから変更すると、そのPull RequestやIssueにはその情報が反映されます。 たとえばプロジェクトでアサインされた人を変更すると、その変更はIssueでも表示されます。 この統合をさらに推し進め、プロジェクトをアサインされた人でグループ化し、Issueを他のグループにドラッグすることによってIssueにアサインされた人を変更できます。 ### タスクへのメタデータの追加 -You can use custom fields to add metadata to your tasks and build a richer view of item attributes. You’re not limited to the built-in metadata (assignee, milestone, labels, etc.) that currently exists for issues and pull requests. For example, you can add the following metadata as custom fields: +カスタムフィールドを使って、タスクにメタデータを追加し、アイテムの属性のより豊かなビューを構築できます。 IssueやPull Requestに現在存在するビルトインのメタデータ（アサインされた人、マイルストーン、ラベルなど）に限定はされません。 たとえば、以下のメタデータをカスタムフィールドとして追加できます: -- A date field to track target ship dates. -- A number field to track the complexity of a task. -- A single select field to track whether a task is Low, Medium, or High priority. -- A text field to add a quick note. -- An iteration field to plan work week-by-week, including support for breaks. +- ターゲットの出荷日を追跡する日付フィールド。 +- タスクの複雑さを追跡する数値フィールド。 +- タスクの優先度が低、中、高なのかを追跡するための単一選択フィールド。 +- クイックノートを追加するためのテキストフィールド。 +- 休憩のサポートを含め、作業を週単位で計画するための繰り返しフィールド。 ### 様々な観点からプロジェクトを見る -Quickly answer your most pressing questions by tailoring your project view to give you the information you need. You can save these views, allowing you to quickly return to them as needed and make them available to your team. Views not only let you scope down the items listed but also offer two different layout options. +必要な情報が得られるようにプロジェクトのビューを調整して、最も差し迫った疑問に素早く答えてください。 それらのビューを保存して、必要なときにすぐに戻れるように、そしてチームでそれらを利用できるようにすることができます。 ビューはリストされたアイテムだけを対象とするだけでなく、2つの異なるレイアウトの選択肢も提供します。 プロジェクトは、高密度のテーブルレイアウトで表示できます。 @@ -46,4 +46,4 @@ Quickly answer your most pressing questions by tailoring your project view to gi ![プロジェクトのビュー](/assets/images/help/issues/project_view.png) -For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." +詳しい情報については「[ビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」を参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md index 73b2bb8ae6..69d65d93a6 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects.md @@ -1,6 +1,6 @@ --- -title: 'Best practices for {% data variables.product.prodname_projects_v2 %}' -intro: Learn tips for managing your projects. +title: '{% data variables.product.prodname_projects_v2 %}のベストプラクティス' +intro: プロジェクトを管理するためのヒントを学んでください。 allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,7 +14,7 @@ topics: - Project management --- -You can use {% data variables.product.prodname_projects_v2 %} to manage your work on {% data variables.product.company_short %}, where your issues and pull requests live. プロジェクトを効率的かつ効果的に管理するためのヒントを読んでください。 {% data variables.product.prodname_projects_v2 %} の詳細については、「[{% data variables.product.prodname_projects_v2 %} について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。 +{% data variables.product.prodname_projects_v2 %}を使って、IssueやPull Requestがある{% data variables.product.company_short %}上の作業を管理できます。 プロジェクトを効率的かつ効果的に管理するためのヒントを読んでください。 {% data variables.product.prodname_projects_v2 %} の詳細については、「[{% data variables.product.prodname_projects_v2 %} について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」を参照してください。 ## 大きなIssueを小さなIssueに分割する @@ -50,32 +50,32 @@ IssueとPull Requestには、コラボレータと容易にコミュニケーシ - カスタムの優先度フィールドでグループ化して、高優先度のアイテムの量をモニター - 最短の出荷ターゲット日でアイテムを見るために、カスタムの日付フィールドでソート -For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)." +詳しい情報については「[ビューのカスタマイズ](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)」を参照してください。 ## 信頼できる唯一の情報源を持つ 情報がずれてしまわないようにするために、信頼できる唯一の情報源を管理してください。 たとえば、ターゲットの出荷日は複数のフィールドに分散させず、一カ所で追跡してください。 そうすれば、ターゲットの出荷日が変更された場合、一カ所で日付を更新するだけでよくなります。 -{% data variables.product.prodname_projects_v2 %} automatically stay up to date with {% data variables.product.company_short %} data, such as assignees, milestones, and labels. これらのフィールドのいずれかがIssueあるいはPull Requestで変更されると、その変更は自動的にプロジェクトにも反映されます。 +{% data variables.product.prodname_projects_v2 %}は、アサインされた人、マイルストーン、ラベルといった{% data variables.product.company_short %}のデータと自動的に同期を保ちます。 これらのフィールドのいずれかがIssueあるいはPull Requestで変更されると、その変更は自動的にプロジェクトにも反映されます。 ## 自動化の利用 意味の無い作業に費やす時間を減らし、プロジェクト自体にかける時間を増やすために、タスクを自動化できます。 手動でやることを覚えておく必要が減れば、それだけプロジェクトは最新の状態に保たれるようになります。 -{% data variables.product.prodname_projects_v2 %} offers built-in workflows. たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 +{% data variables.product.prodname_projects_v2 %}はビルトインワークフローを提供します。 たとえば、Issueがクローズされると自動的にステータスを「Done」に設定できます。 加えて、{% data variables.product.prodname_actions %}とGraphQL APIでルーチンのプロジェクト管理タスクを自動化できます。 たとえば、レビュー待ちのPull Requestを追跡するために、Pull Requestをプロジェクトに追加し、そのステータスを"needs review"に設定するようなワークフローを作成できます。このプロセスは、Pull Requestが"ready for review"としてマークされたときに自動的にトリガーできます。 -- For an example workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." -- For more information about the API, see "[Using the API to manage {% data variables.product.prodname_projects_v2 %}](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)." +- ワークフローの例については「[Actionsを使った{% data variables.product.prodname_projects_v2 %}の自動化](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)」を参照してください。 +- APIに関する詳しい情報については「[{% data variables.product.prodname_projects_v2 %}を管理するためのAPIの利用](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)」を参照してください。 - {% data variables.product.prodname_actions %}に関する詳しい情報については「[{% data variables.product.prodname_actions %}](/actions)」を参照してください。 ## 様々なフィールドタイプの利用 様々なフィールドタイプを活用して、要求を満たしてください。 -繰り返しフィールドを使って、作業をスケジュールしたり、タイムラインを作成したりしてください。 繰り返しをグループ化して、アイテムが繰り返し間でバランスしているかを見たり、あるいは繰り返しの1つに焦点を当てるためにフィルタリングできます。 繰り返しフィールドを使えば、過去の繰り返しで完了した作業を見ることもでき、それを速度の計画とチームの成果への反映に役立てられます。 繰り返しフィールドは、あなたとあなたのチームが繰り返しから離れる時間を取っている時を示す休憩もサポートします。 For more information, see "[About iteration fields](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)." +繰り返しフィールドを使って、作業をスケジュールしたり、タイムラインを作成したりしてください。 繰り返しをグループ化して、アイテムが繰り返し間でバランスしているかを見たり、あるいは繰り返しの1つに焦点を当てるためにフィルタリングできます。 繰り返しフィールドを使えば、過去の繰り返しで完了した作業を見ることもでき、それを速度の計画とチームの成果への反映に役立てられます。 繰り返しフィールドは、あなたとあなたのチームが繰り返しから離れる時間を取っている時を示す休憩もサポートします。 詳しい情報については「[繰り返しフィールドについて](/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields)」を参照してください。 単一の選択フィールドを利用して、事前設定された値のリストに基づき、タスクに関する情報を追跡してください。 たとえば、優先度やプロジェクトのフェーズを追跡してください。 値は事前設定されたリストから選択されるので、グループ化や特定の値のアイテムに集中するためのフィルタリングが容易です。 -For more information about the different field types, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)." +様々なフィールドタイプに関する詳しい情報については「[フィールドタイプを理解する](/issues/planning-and-tracking-with-projects/understanding-field-types)」を参照してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md index aed5d5a211..4070a3e055 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/index.md @@ -1,6 +1,6 @@ --- -title: 'Learning about {% data variables.product.prodname_projects_v2 %}' -intro: 'Learn about {% data variables.product.prodname_projects_v2 %} and how to make the very best of this powerful tool.' +title: '{% data variables.product.prodname_projects_v2 %}について学ぶ' +intro: '{% data variables.product.prodname_projects_v2 %}について、そしてこの強力なツールを最大限に活用する方法を学んでください。' versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md index 8ed93830a2..d4ca475134 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects.md @@ -1,6 +1,6 @@ --- -title: 'Quickstart for {% data variables.product.prodname_projects_v2 %}' -intro: 'Experience the speed, flexibility, and customization of {% data variables.product.prodname_projects_v2 %} by creating a project in this interactive guide.' +title: '{% data variables.product.prodname_projects_v2 %}のクイックスタート' +intro: 'このインタラクティブガイドでプロジェクトを作成して、{% data variables.product.prodname_projects_v2 %}のスピード、柔軟性、カスタマイズを体験してください。' allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -14,7 +14,7 @@ topics: ## はじめに -This guide demonstrates how to use {% data variables.product.prodname_projects_v2 %} to plan and track work. このガイドでは、新しいプロジェクトを作成し、タスクの優先度を追跡するためにカスタムフィールドを追加します。 また、コラボレータと優先度や進捗について伝えるための役に立つ、保存されるビューも作成します。 +このガイドは、作業を計画して追跡するための{% data variables.product.prodname_projects_v2 %}の使い方を紹介します。 このガイドでは、新しいプロジェクトを作成し、タスクの優先度を追跡するためにカスタムフィールドを追加します。 また、コラボレータと優先度や進捗について伝えるための役に立つ、保存されるビューも作成します。 ## 必要な環境 @@ -46,7 +46,7 @@ Organizationプロジェクトもしくはユーザプロジェクトを作成 上記のステップを何回か繰り返し、複数のIssueをプロジェクトに追加してください。 -For more information and other ways to add issues to your project, or about other items you can add to your project, see "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)." +プロジェクトにIssueを追加する他の方法、あるいはプロジェクトに追加できる他のアイテムに関する情報については、「[プロジェクトへのアイテムの追加](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)」を参照してください。 ## プロジェクトへのドラフトIssueの追加 @@ -54,24 +54,24 @@ For more information and other ways to add issues to your project, or about othe {% data reusables.projects.add-draft-issue %} -## Adding an iteration field +## 繰り返しフィールドの追加 -Next, create an iteration field so you can plan and track your work over repeating blocks of time. Iterations can be configured to suit how you and your team works, with customizable lengths and the ability to insert breaks. +次に、繰り返しフィールドを作成して、繰り返される時間のブロックに対して作業を計画して追跡できるようにしましょう。 繰り返しは、長さがカスタマイズ可能で休憩を挟むことがき、あなたとあなたのチームの作業に合わせて設定できます。 {% data reusables.projects.new-field %} -1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) -3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) -4. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) +1. **Iteration（繰り返し）**を選択してください。 ![繰り返しのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-iteration.png) +3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![繰り返しの期間を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-duration.png) +4. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save-and-create.png) ## 優先度を追跡するためのフィールドの作成 -Now, create a custom field named `Priority` and containing the values: `High`, `Medium`, or `Low`. +さあ、`High`、`Medium`、`Low`のいずれかの値を含む`Priority`という名前のカスタムフィールドを作成してください。 {% data reusables.projects.new-field %} -1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) -1. Below "Options", type the first option, "High". ![Screenshot showing the single select option](/assets/images/help/projects-v2/priority-example.png) -1. To add additional fields, for "Medium" and "Low", click **Add option**. -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Single select（単一選択）**を選択してください。 ![単一選択オプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-single-select.png) +1. "Options（オプション）"の下で、最初の選択肢の"High"を入力してください。 ![単一選択オプションを表示しているスクリーンショット](/assets/images/help/projects-v2/priority-example.png) +1. "Medium"と"Low"のためのフィールドを追加するため、**Add option（選択肢の追加）**をクリックしてください。 +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) プロジェクト中のすべてのIssueに優先度を指定してください。 @@ -82,8 +82,8 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 次に、高優先度のアイテムに集中しやすくするために、プロジェクト中のすべてのアイテムを優先度でグループ化します。 {% data reusables.projects.open-view-menu %} -1. Click {% octicon "rows" aria-label="the rows icon" %} **Group**. ![Screenshot showing the group menu item](/assets/images/help/projects-v2/group-menu-item.png) -1. Click **Priority**. ![Screenshot showing the group menu](/assets/images/help/projects-v2/group-menu.png) +1. {% octicon "rows" aria-label="the rows icon" %} **Group（グループ）**をクリックしてください。 ![グループメニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/group-menu-item.png) +1. **Priority（優先度）**をクリックしてください。 ![グループメニューを表示しているスクリーンショット](/assets/images/help/projects-v2/group-menu.png) さあ、優先度を変更するために、Issueをグループ間で移動させてください。 @@ -117,7 +117,7 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 次に、ボードレイアウトに切り替えてください。 {% data reusables.projects.open-view-menu %} -1. Under "Layout", click **Board**. ![Screenshot showing layout option](/assets/images/help/projects-v2/table-or-board.png) +1. "Layout（レイアウト）"の下で、**Board（ボード）**をクリックしてください。 ![レイアウトオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/table-or-board.png) ![優先度の例](/assets/images/help/projects/example_board.png) @@ -130,7 +130,7 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` {% data reusables.projects.open-view-menu %} 1. {% octicon "pencil" aria-label="the pencil icon" %} **Rename view（ビューの名前の変更）**をクリックしてください。 ![名前の変更のメニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/rename-view.png) 1. ビューの新しい名前を入力してください。 -1. To save changes, press Return. +1. 変更を保存するためにReturnを押してください。 ![優先度の例](/assets/images/help/projects/project-view-switch.gif) @@ -138,12 +138,12 @@ Now, create a custom field named `Priority` and containing the values: `High`, ` 最後に、組み込みのワークフローを追加して、アイテムがプロジェクトに追加されたときにステータスが**Todo**に設定されるようにしてください。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) -1. **Default workflows（デフォルトのワークフロー）**の下で、**Item added to project（アイテムがプロジェクトに追加）**をクリックしてください。 ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) -1. **When（時期）**の隣で、`issues`と`pull requests`がどちらも選択されていることを確認してください。 ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) -1. **Set（設定）**の隣で、**Status:Todo**を選択してください。 ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) -1. **Disabled（無効）**トグルをクリックして、ワークフローを有効化してください。 ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "workflow" aria-label="The workflow icon" %} **Workflows（ワークフロー）**をクリックしてください。 !['Workflows'メニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png) +1. **Default workflows（デフォルトのワークフロー）**の下で、**Item added to project（アイテムがプロジェクトに追加）**をクリックしてください。 ![デフォルトのワークフローを表示しているスクリーンショット](/assets/images/help/projects-v2/default-workflows.png) +1. **When（時期）**の隣で、`issues`と`pull requests`がどちらも選択されていることを確認してください。 ![ワークフローの"when"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-when.png) +1. **Set（設定）**の隣で、**Status:Todo**を選択してください。 ![ワークフローの"set"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-set.png) +1. **Disabled（無効）**トグルをクリックして、ワークフローを有効化してください。 ![ワークフローの"enable"コントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-enable.png) ## 参考リンク diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md index 7744c91356..efde8b15f8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project.md @@ -1,7 +1,7 @@ --- -title: 'Adding items to your {% data variables.projects.project_v2 %}' -shortTitle: Adding items -intro: 'Learn how to add pull requests, issues, and draft issues to your projects individually or in bulk.' +title: '{% data variables.projects.project_v2 %}へのアイテムの追加' +shortTitle: アイテムの追加 +intro: Pull Request、Issue、ドラフトIssueをプロジェクトに個別あるいはまとめて追加する方法を学んでください。 miniTocMaxHeadingLevel: 4 versions: feature: projects-v2 @@ -15,13 +15,13 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** A project can contain a maximum of 1,200 items and 10,000 archived items. +**ノート:** プロジェクトには最大で1,200個のアイテム及び10,000個のアーカイブされたアイテムを含めることができます。 {% endnote %} -### Adding issues and pull requests to a project +### プロジェクトへのIssueやPull Requestの追加 -#### Pasting the URL of an issue or pull request +#### IssueあるいはPull RequestのURLの貼り付け {% data reusables.projects.add-item-via-paste %} @@ -29,13 +29,13 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.add-item-bottom-row %} 2. #を入力してください。 -3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-repo.png) -4. IssueあるいはPull Requestを選択してください。 タイトルの一部を入力して、選択肢を狭めることができます。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-item-select-issue.png) +3. Pull RequestあるいはIssueがあるリポジトリを選択してください。 リポジトリ名の一部を入力して、選択肢を狭めることができます。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-item-select-repo.png) +4. IssueあるいはPull Requestを選択してください。 タイトルの一部を入力して、選択肢を狭めることができます。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-item-select-issue.png) -#### Bulk adding issues and pull requests +#### IssueやPull Requestの一括での追加 -1. In the bottom row of the project, click {% octicon "plus" aria-label="plus icon" %}. ![Screenshot showing + button at the bottom of the project](/assets/images/help/projects-v2/omnibar-add.png) -1. Click **Add item from repository**. ![Screenshot showing "add item from repository" menu item](/assets/images/help/projects-v2/add-bulk-menu-item.png) +1. プロジェクトの最下行で{% octicon "plus" aria-label="plus icon" %}をクリックしてください。 ![プロジェクトの下部に+ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/omnibar-add.png) +1. **Add item from repository（リポジトリからアイテムを追加）**をクリックしてください。 !["add item from repository" メニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/add-bulk-menu-item.png) {% data reusables.projects.bulk-add %} #### リポジトリから複数のIssueあるいはPull Requestを追加する @@ -44,25 +44,25 @@ allowTitleToDifferFromFilename: true {% data reusables.repositories.sidebar-issue-pr %} 1. それぞれのIssueのタイトルの左で、プロジェクトに追加したいIssueを選択してください。 ![IssueあるいはPull Requestを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-issue-checkbox.png) 1. あるいは、ページ上のすべてのIssueあるいはPull Requestを選択するには、IssueあるいはPull Requestのリストの上部で、すべてを選択してください。 ![画面上のすべてを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-all-checkbox.png) -1. Above the list of issues or pull requests, click **Projects**. ![Screenshot showing projects option](/assets/images/help/projects-v2/issue-index-project-menu.png) +1. IssueあるいはPull Requestのリストの上で**Projects（プロジェクト）**をクリックしてください。 ![プロジェクトのオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-index-project-menu.png) 1. 選択されたIssueあるいはPull Requestを追加したいプロジェクトをクリックしてください。 ![画面上のすべてを選択するためのチェックボックスが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-index-select-project.png) #### IssueあるいはPull Requestの中からプロジェクトをアサインする 1. プロジェクトに追加したいIssueあるいはPull Requestにアクセスしてください。 -2. サイドバーで**Projects（プロジェクト）**をクリックしてください。 ![Screenshot showing "Projects" in the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-projects.png) -3. Select the project that you want to add the issue or pull request to. ![Screenshot showing selecting a project from the issue sidebar](/assets/images/help/projects-v2/issue-sidebar-select-project.png) -4. Optionally, populate the custom fields. ![プロジェクトサイドバー](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) +2. サイドバーで**Projects（プロジェクト）**をクリックしてください。 ![Issueサイドバーに"Projects"が表示されているスクリーンショット](/assets/images/help/projects-v2/issue-sidebar-projects.png) +3. IssueあるいはPull Requestを追加したいプロジェクトを選択してください。 ![Issueサイドバーからプロジェクトを選択しているところが表示されているスクリーンショット](/assets/images/help/projects-v2/issue-sidebar-select-project.png) +4. あるいは、カスタムフィールドに入力してください。 ![プロジェクトサイドバー](/assets/images/help/projects-v2/issue-edit-project-sidebar.png) -#### Using the command palette to add an issue or pull request +#### コマノン度パレットを使用してIssueあるいはPull Requestを追加する 1. {% data reusables.projects.open-command-palette %} -1. Start typing "Add items" and press Return. +1. "Add items"と入力し、Returnを押してください。 {% data reusables.projects.bulk-add %} ### ドラフトIssueの作成 -ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。 Unlike issues and pull requests that are referenced from your repositories, draft issues exist only in your project. +ドラフトIssueは、素早くアイデアを捕捉するのに役立ちます。 リポジトリから参照されるIssueやPull Requestとは異なり、ドラフトIssueはプロジェクトの中にだけ存在します。 {% data reusables.projects.add-draft-issue %} diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md index b7d40b5d3c..262b299aad 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/archiving-items-from-your-project.md @@ -1,7 +1,7 @@ --- -title: 'Archiving items from your {% data variables.projects.project_v2 %}' -shortTitle: Archiving items -intro: 'You can archive items, keeping them available to restore, or permanently delete them.' +title: '{% data variables.projects.project_v2 %}からのアイテムのアーカイブ' +shortTitle: アイテムのアーカイブ +intro: アイテムをアーカイブし、復元できるようにしておくか、恒久的に削除できます。 miniTocMaxHeadingLevel: 2 versions: feature: projects-v2 @@ -11,29 +11,29 @@ topics: allowTitleToDifferFromFilename: true --- -## Archiving items +## アイテムのアーカイブ アイテムをアーカイブして、そのアイテムに関するコンテキストをプロジェクト中に保持しながら、アイテムをプロジェクトのビューから削除できます。 {% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. [**Archive**] をクリックします。 ![Screenshot showing archive option](/assets/images/help/projects-v2/archive-menu-item.png) -1. When prompted, confirm your choice by clicking **Archive**. ![Screenshot showing archive prompt](/assets/images/help/projects-v2/archive-item-prompt.png) +1. [**Archive**] をクリックします。 ![アーカイブのオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/archive-menu-item.png) +1. プロンプトが表示されたら、**Archive（アーカイブ）**をクリックして選択を確認してください。 ![アーカイブのプロンプトが表示されているスクリーンショット](/assets/images/help/projects-v2/archive-item-prompt.png) ## アーカイブされたアイテムの復元 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "archive" aria-label="The archive icon" %} **Archived items**. ![Screenshot showing the 'Archived items' menu item](/assets/images/help/projects-v2/archived-items-menu-item.png) -1. あるいは、表示されているアーカイブされたアイテムをフィルタリングするには、アイテムのリストの上にあるテキストボックスにフィルタを入力してください。 For more information about the available filters, see "[Filtering projects](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)." ![アーカイブされているアイテムをフィルタリングするためのフィールドが表示されているスクリーンショット](/assets/images/help/issues/filter-archived-items.png) -1. To the left of each item title, select the items you would like to restore. ![アーカイブされたアイテムの隣のチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-archived-item.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "archive" aria-label="The archive icon" %} **Archived items（アーカイブされたアイテム）**をクリックしてください。 ![Archived items'メニューアイテムが表示されているスクリーンショット](/assets/images/help/projects-v2/archived-items-menu-item.png) +1. あるいは、表示されているアーカイブされたアイテムをフィルタリングするには、アイテムのリストの上にあるテキストボックスにフィルタを入力してください。 利用可能なフィルタに関する詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 ![アーカイブされているアイテムをフィルタリングするためのフィールドが表示されているスクリーンショット](/assets/images/help/issues/filter-archived-items.png) +1. 各アイテムのタイトルの左で、復元したいアイテムを選択してください。 ![アーカイブされたアイテムの隣のチェックボックスが表示されているスクリーンショット](/assets/images/help/issues/select-archived-item.png) 1. 選択されたアイテムを復元するには、アイテムのリストの上部で**Restore（復元）**をクリックしてください。 !["復元"ボタンが表示されているスクリーンショット](/assets/images/help/issues/restore-archived-item-button.png) -## Deleting items +## アイテムの削除 アイテムを削除すれば、それをプロジェクトから完全に取り除くことができます。 {% data reusables.projects.select-an-item %} {% data reusables.projects.open-item-menu %} -1. Click **Delete from project**. ![Screenshot showing delete option](/assets/images/help/projects-v2/delete-menu-item.png) -1. When prompted, confirm your choice by clicking **Delete**. ![Screenshot showing delete prompt](/assets/images/help/projects-v2/delete-item-prompt.png) +1. **Delete from project（プロジェクトから削除）**をクリックしてください。 ![削除のオプションが表示されているスクリーンショット](/assets/images/help/projects-v2/delete-menu-item.png) +1. プロンプトが表示されたら、**Delete（削除）**をクリックして選択を確認してください。 ![削除のプロンプトが表示されているスクリーンショット](/assets/images/help/projects-v2/delete-item-prompt.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md index f7fe4c8931..8b313b1728 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/converting-draft-issues-to-issues.md @@ -1,7 +1,7 @@ --- title: ドラフトIssueのIssueへの変換 -shortTitle: Converting draft issues -intro: Learn how to convert draft issues into issues. +shortTitle: ドラフトIssueの変換 +intro: ドラフトIssueをIssueに変換する方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,18 +10,18 @@ topics: - Projects --- -## Converting draft issues in table layout +## テーブルレイアウトでのドラフトIssueの変換 -1. Click the {% octicon "triangle-down" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-table.png) -2. **Convert to issue（Issueに変換）**を選択してください。 ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) -3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) +1. 変換したいドラフトIssueの{% octicon "triangle-down" aria-label="the item menu" %}をクリックしてください。 ![アイテムメニューボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/item-context-menu-button-table.png) +2. **Convert to issue（Issueに変換）**を選択してください。 !["Convert to issue"オプションが表示されているスクリーンショット](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. このIssueを追加したいリポジトリを選択してください。 ![リポジトリの選択が表示されているスクリーンショット](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) -## Converting draft issues in board layout +## ボードレイアウトでのドラフトIssueの変換 -1. Click the {% octicon "kebab-horizontal" aria-label="the item menu" %} on the draft issue that you want to convert. ![Screenshot showing item menu button](/assets/images/help/projects-v2/item-context-menu-button-board.png) -2. **Convert to issue（Issueに変換）**を選択してください。 ![Screenshot showing "Convert to issue" option](/assets/images/help/projects-v2/item-convert-to-issue.png) -3. Select the repository that you want to add the issue to. ![Screenshot showing repository selection](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) +1. 変換したいドラフトIssueの{% octicon "kebab-horizontal" aria-label="the item menu" %}をクリックしてください。 ![アイテムメニューボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/item-context-menu-button-board.png) +2. **Convert to issue（Issueに変換）**を選択してください。 !["Convert to issue"オプションが表示されているスクリーンショット](/assets/images/help/projects-v2/item-convert-to-issue.png) +3. このIssueを追加したいリポジトリを選択してください。 ![リポジトリの選択が表示されているスクリーンショット](/assets/images/help/projects-v2/convert-to-issue-select-repo.png) ## 参考リンク -- "[Creating draft issues](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)" +- 「[ドラフトIssueの作成](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project#creating-draft-issues)」 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md index 0d43deeba0..ac61277e8a 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-items-in-your-project/index.md @@ -1,7 +1,7 @@ --- -title: 'Managing items in your {% data variables.projects.project_v2 %}' -shortTitle: 'Managing items in your {% data variables.projects.project_v2 %}' -intro: 'Learn how to add and manage issues, pull requests, and draft issues.' +title: '{% data variables.projects.project_v2 %}内のアイテムの管理' +shortTitle: '{% data variables.projects.project_v2 %}内のアイテムの管理' +intro: Issue、Pull Request、ドラフトIssueの追加と管理の方法を学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md index 03f355e94c..8b5e1ccb52 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository.md @@ -1,7 +1,7 @@ --- -title: 'Adding your {% data variables.projects.project_v2 %} to a repository' -shortTitle: 'Adding a {% data variables.projects.project_v2 %} to a repo' -intro: 'You can add your {% data variables.projects.project_v2 %} to a repository to make it accessible from that repository.' +title: '{% data variables.projects.project_v2 %}のリポジトリへの追加' +shortTitle: '{% data variables.projects.project_v2 %}のリポジトリへの追加' +intro: '{% data variables.projects.project_v2 %}をリポジトリへ追加して、リポジトリからアクセスできるようにすることができます。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -13,10 +13,10 @@ allowTitleToDifferFromFilename: true リポジトリ中で、関連するプロジェクトをリストできます。 リストできるのは、リポジトリを所有している同じユーザもしくはOrganizationが所有しているプロジェクトだけです。 -リポジトリのメンバーがリストされているプロジェクトを見るためには、そのプロジェクトを見ることができなければなりません。 For more information, see "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)" and "[Managing access to your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." +リポジトリのメンバーがリストされているプロジェクトを見るためには、そのプロジェクトを見ることができなければなりません。 詳しい情報については「[{% data variables.projects.projects_v2 %}の可視性の管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)」及び「[{% data variables.projects.projects_v2 %}へのアクセスの管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)」を参照してください。 1. {% data variables.product.prodname_dotcom %}で、リポジトリのメインページにアクセスしてください。 -1. {% octicon "table" aria-label="the project icon" %} **Projects（プロジェクト）**をクリックしてください。 ![Screenshot showing projects tab in a repository](/assets/images/help/projects-v2/repo-tab.png) -1. **Add project（プロジェクトの追加）**をクリックしてください。 ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo-button.png) -1. In the search bar that appears, search for projects that are owned by the same user or organization that owns the repository. ![Screenshot showing searching for a project](/assets/images/help/projects-v2/add-to-repo-search.png) -1. Click on a project to list it in your repository. ![Screenshot showing "Add project" button](/assets/images/help/projects-v2/add-to-repo.png) +1. {% octicon "table" aria-label="the project icon" %} **Projects（プロジェクト）**をクリックしてください。 ![リポジトリのプロジェクトタブが表示されているスクリーンショット](/assets/images/help/projects-v2/repo-tab.png) +1. **Add project（プロジェクトの追加）**をクリックしてください。 !["Add project"ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/add-to-repo-button.png) +1. 表示される検索バーで、リポジトリを所有しているのと同じユーザあるいはOrganizationが所有しているプロジェクトを検索してください。 ![プロジェクトを検索しているところを表示しているスクリーンショット](/assets/images/help/projects-v2/add-to-repo-search.png) +1. リポジトリでリストされているプロジェクトをクリックしてください。 !["Add project"ボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/add-to-repo.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md index 457ba55c97..59ee204fb5 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/closing-and-deleting-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Closing and deleting your {% data variables.projects.projects_v2 %}' -shortTitle: 'Closing and deleting {% data variables.projects.projects_v2 %}' -intro: 'Learn about closing, re-opening, and permanently deleting a {% data variables.projects.project_v2 %}.' +title: '{% data variables.projects.projects_v2 %}のクローズと削除' +shortTitle: '{% data variables.projects.projects_v2 %}のクローズと削除' +intro: '{% data variables.projects.project_v2 %}のクローズ、再オープン、完全な削除について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md index ad6852040f..3c65ece66b 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/index.md @@ -1,6 +1,6 @@ --- -title: 'Managing your {% data variables.projects.project_v2 %}' -intro: Learn how to manage your projects and control visibility and access. +title: '{% data variables.projects.project_v2 %}の管理' +intro: プロジェクトの管理と、可視性及びアクセスの制御の方法を学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md index 0a3b38f596..cd1bd40c98 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Managing access to your {% data variables.projects.projects_v2 %}' -shortTitle: 'Managing {% data variables.projects.project_v2 %} access' -intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.' +title: '{% data variables.projects.projects_v2 %}へのアクセスの管理' +shortTitle: '{% data variables.projects.project_v2 %}のアクセスの管理' +intro: '{% data variables.projects.project_v2 %}のTeam及び個人のアクセス管理の方法を学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -29,8 +29,8 @@ Organizationレベルのプロジェクトの管理者は、Organization全体 デフォルトの基本ロールは`write`であり、これはOrganization内の誰もがプロジェクトを見て編集できるということです。 この基本ロールを変更すれば、Organizationの全員に対するプロジェクトのアクセスを変更できます。 基本ロールへの変更は、Organizationのオーナーではなく、個別にアクセス権を付与されていないOrganizaitonのメンバーにだけ影響します。 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Base role（基本ロール）**の下で、デフォルトロールを選択してください。 ![Screenshot showing the base role menu](/assets/images/help/projects-v2/base-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Base role（基本ロール）**の下で、デフォルトロールを選択してください。 ![ベースロールメニューを表示しているスクリーンショット](/assets/images/help/projects-v2/base-role.png) - **No access（アクセス無し）**: Organizationのオーナーと、個別にアクセス権を付与されたユーザだけがプロジェクトを見ることができます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 - **Read（読み取り）**: Organizationの全員がプロジェクトを見ることができます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 - **Write（書き込み）**: Organizationの全員がプロジェクトを見て編集できます。 Organizationのオーナーは、プロジェクトの管理者でもあります。 @@ -43,24 +43,24 @@ Organizationレベルのプロジェクトには、Team、外部のコラボレ 個人ユーザが既にOrganizationのメンバーになっているか、Organizationの少なくとも1つのリポジトリで外部のコラボレータになっている場合にのみ、Organizationレベルのプロジェクトに共同作業をするように招待できます。 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Invite collaborators（コラボレータの招待）**の下で、招待したいTeamもしくは個人ユーザを検索してください。 ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) -3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Invite collaborators（コラボレータの招待）**の下で、招待したいTeamもしくは個人ユーザを検索してください。 ![コラボレータの検索を表示しているスクリーンショット](/assets/images/help/projects-v2/access-search.png) +3. コラボレータのロールを選択してください。 ![ロールの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/access-role.png) - **Read（読み取り）**: Teamあるいは個人はプロジェクトを見ることができます。 - **Write（書き込み）**: Teamあるいは個人はプロジェクトを編集できます。 - **Admin（管理）**: Teamあるいは個人はプロジェクトを見て編集でき、新しいコラボレータを追加できます。 -4. **Invite（招待）**をクリックしてください。 ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) +4. **Invite（招待）**をクリックしてください。 ![招待ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/access-invite.png) ### プロジェクトの既存のコラボレータのアクセス管理 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) 1. **Manage access（アクセス管理）**の下で、権限を変更したいコラボレータを見つけてください。 - **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) + **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![コラボレータを表示しているスクリーンショット](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) -1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) +1. コラボレータのロールを編集してください。 ![コラボレータのロールの変更を表示しているスクリーンショット](/assets/images/help/projects-v2/access-change-role.png) +1. あるいは、**Remove（削除）** をクリックしてコラボレータを削除してください。 ![コラボレータの削除を表示しているスクリーンショット](/assets/images/help/projects-v2/access-remove-member.png) ## ユーザレベルプロジェクトのアクセス管理 @@ -73,21 +73,21 @@ Organizationレベルのプロジェクトには、Team、外部のコラボレ {% endnote %} {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) -2. **Invite collaborators（コラボレータの招待）**の下で、招待したいユーザを検索してください。 ![Screenshot showing searching for a collaborator](/assets/images/help/projects-v2/access-search.png) -3. Select the role for the collaborator. ![Screenshot showing selecting a role](/assets/images/help/projects-v2/access-role.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) +2. **Invite collaborators（コラボレータの招待）**の下で、招待したいユーザを検索してください。 ![コラボレータの検索を表示しているスクリーンショット](/assets/images/help/projects-v2/access-search.png) +3. コラボレータのロールを選択してください。 ![ロールの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/access-role.png) - **Read（読み取り）**: ユーザはプロジェクトを見ることができます。 - **Write（書き込み）**: ユーザはプロジェクトを見て編集できます。 - **Admin（管理）**: ユーザはプロジェクトを見て編集でき、新しいコラボレータを追加できます。 -4. **Invite（招待）**をクリックしてください。 ![Screenshot showing the invite button](/assets/images/help/projects-v2/access-invite.png) +4. **Invite（招待）**をクリックしてください。 ![招待ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/access-invite.png) ### プロジェクトの既存のコラボレータのアクセス管理 {% data reusables.projects.project-settings %} -1. **Manage access（アクセス管理）**をクリックしてください。 ![Screenshot showing the "Manage access" item](/assets/images/help/projects-v2/manage-access.png) +1. **Manage access（アクセス管理）**をクリックしてください。 !["Manage access"アイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/manage-access.png) 1. **Manage access（アクセス管理）**の下で、権限を変更したいコラボレータを見つけてください。 - **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![Screenshot showing a collaborator](/assets/images/help/projects-v2/access-find-member.png) + **Type（タイプ）**及び**Role（ロール）**ドロップダウンメニューを使って、アクセスリストをフィルタリングできます。 ![コラボレータを表示しているスクリーンショット](/assets/images/help/projects-v2/access-find-member.png) -1. Edit the role for the collaborator(s). ![Screenshot showing changing a collaborator's role](/assets/images/help/projects-v2/access-change-role.png) -1. Optionally, click **Remove** to remove the collaborator(s). ![Screenshot showing removing a collaborator](/assets/images/help/projects-v2/access-remove-member.png) +1. コラボレータのロールを編集してください。 ![コラボレータのロールの変更を表示しているスクリーンショット](/assets/images/help/projects-v2/access-change-role.png) +1. あるいは、**Remove（削除）** をクリックしてコラボレータを削除してください。 ![コラボレータの削除を表示しているスクリーンショット](/assets/images/help/projects-v2/access-remove-member.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md index d2150a6fc7..ae755d0bbc 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md @@ -1,7 +1,7 @@ --- -title: 'Managing visibility of your {% data variables.projects.projects_v2 %}' -shortTitle: 'Managing {% data variables.projects.project_v2 %} visibility' -intro: 'Learn about setting your {% data variables.projects.project_v2 %} to private or public visibility.' +title: '{% data variables.projects.projects_v2 %}の可視性の管理' +shortTitle: '{% data variables.projects.project_v2 %}の可視性の管理' +intro: '{% data variables.projects.project_v2 %}の可視性のプライベートもしくはパブリックへの設定について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -16,25 +16,25 @@ permissions: Organization owners can manage the visibility of project boards in ## プロジェクトの可視性について -Projects can be public or private. パブリックプロジェクトでは、インターネット上の誰もがプロジェクトを見ることができます。 プライベートプロジェクトでは、最低でも読み取りアクセスを付与されたユーザだけがプロジェクトを見ることができます。 +プロジェクトはパブリックあるいはプライベートにできます。 パブリックプロジェクトでは、インターネット上の誰もがプロジェクトを見ることができます。 プライベートプロジェクトでは、最低でも読み取りアクセスを付与されたユーザだけがプロジェクトを見ることができます。 影響を受けるのはプロジェクトの可視性のみです。プロジェクト上のアイテムを見るには、アイテムが属する得リポジトリに対する必要な権限を持っていなければなりません。 プロジェクトにプライベートリポジトリのアイテムが含まれているなら、そのリポジトリのコラボレータではないユーザは、そのリポジトリのアイテムを見ることはできません。 ![非表示のアイテムを持つプロジェクト](/assets/images/help/projects/hidden-items.png) -Project admins and organization owners can control project visibility. Organization owners can restrict the ability to change project visibility to just organization owners. +プロジェクトの管理者とOrganizationのオーナーは、プロジェクトの可視性を制御できます。 Organizationのオーナーは、プロジェクトの可視性を変更できるのをOrganizationのオーナーだけに制限できます。 -In public and private projects, insights are only visible to users with write permissions for the project. +パブリック及びプライベートのプロジェクトでは、インサイトはプロジェクトの書き込み権限を持っているユーザだけが見ることができます。 Organizationが所有するプライベートのプロジェクトでは、プロジェクトを現在更新しているユーザのアバターがプロジェクトのUIに表示されます。 -プロジェクトの管理者は、プロジェクトに対する書き込み及び管理アクセスの管理と、個々のユーザの読み取りアクセスの制御もできます。 For more information, see "[Managing access to your projects](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)." +プロジェクトの管理者は、プロジェクトに対する書き込み及び管理アクセスの管理と、個々のユーザの読み取りアクセスの制御もできます。 詳しい情報については「[プロジェクトへのアクセスの管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects)」を参照してください。 ## プロジェクトの可視性の変更 {% data reusables.projects.project-settings %} -1. Next to **Visibility** in the "Danger zone", select **Private** or **Public**. ![Screenshot showing the visibility controls](/assets/images/help/projects-v2/visibility.png) +1. "Danger zone（危険区域）"の**Visibility（可視性）**の隣で、**Private（プライベート）**もしくは**Public（パブリック）**を選択してください。 ![可視性のコントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/visibility.png) ## 参考リンク -- [Allowing project visibility changes in your organization](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization) +- [Organizationでのプロジェクトの可視性の変更の許可](/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md index 21a0bc288a..47f43f9d19 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md @@ -1,7 +1,7 @@ --- -title: About date fields -shortTitle: About date fields -intro: You can create custom date fields that can be set by typing a date or using a calendar. +title: 日付フィールドについて +shortTitle: 日付フィールドについて +intro: 日付を入力するか、カレンダーを使って設定できるカスタムの日付フィールドを作成できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,12 +10,12 @@ topics: - Projects --- -You can filter for date values using the `YYYY-MM-DD` format, for example: `date:2022-07-01`. You can also use operators, such as `>`, `>=`, `<`, `<=`, and `..`. For example, `date:>2022-07-01` and `date:2022-07-01..2022-07-31`. You can also provide `@today` to represent the current day in your filter. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +日付の値を、たとえば`date:2022-07-01`のような`YYYY-MM-DD`という形式を使ってフィルタリングできます。 `>`、`>=`、`<`、`<=`、`..`といった演算子を使うこともできます。 たとえば`date:>2022-07-01`や`date:2022-07-01..2022-07-31`のようにです。 `@today`としてフィルタ中で今日の日付を示すこともできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -## Adding a date field +## 日付フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Date** ![Screenshot showing the date option](/assets/images/help/projects-v2/new-field-date.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Date（日付）**を選択してください。 ![日付のオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-date.png) +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md index 3fa989b258..f30706c2bf 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md @@ -1,6 +1,6 @@ --- -title: About iteration fields -shortTitle: About iteration fields +title: 繰り返しフィールドについて +shortTitle: 繰り返しフィールドについて intro: 今後の作業を計画し、アイテムをグループ化するために、繰り返しを作成できます。 miniTocMaxHeadingLevel: 3 versions: @@ -14,47 +14,47 @@ topics: 繰り返しフィールドを作成して、アイテムを特定の繰り返し時間ブロックに関連づけることができます。 繰り返しは任意の長さに設定でき、休憩を含められ、名前と日付の範囲を変更するために個別に編集できます。 プロジェクトでは、繰り返しでグループ化を行い、今後の作業のバランスを視覚化し、フィルタを使って繰り返しの1つに焦点を当て、繰り返しで並べ替えできます。 -You can filter for iterations by specifying the iteration name or `@current` for the current iteration, `@previous` for the previous iteration, or `@next` for the next iteration. You can also use operators such as `>`, `>=`, `<`, `<=`, and `..`. For example, `iteration:>"Iteration 4"` and `iteration:<@current`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +繰り返しの名前もしくは現在の繰り返しとして`@current`、前の繰り返しとして`@previous`、次の繰り返しとして`@next`を指定して、繰り返しをフィルタリングできます。 `>`、`>=`、`<`、`<=`、`..`といった演算子を使うこともできます。 たとえば`iteration:>"Iteration 4"`や`iteration:<@current`とできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 最初に繰り返しフィールドを作成すると、3回の繰り返しが自動的に作成されます。 プロジェクトの設定ページから、繰り返しを追加したり、他の変更をしたりできます。 ![繰り返しフィールドの設定を表示しているスクリーンショット](/assets/images/help/issues/iterations-example.png) -## Adding an iteration field +## 繰り返しフィールドの追加 {% data reusables.projects.new-field %} -1. Select **Iteration** ![Screenshot showing the iteration option](/assets/images/help/projects-v2/new-field-iteration.png) -2. Optionally, if you don't want the iteration to start today, select the calendar dropdown next to "Starts on" and choose a new start date. ![Screenshot showing the iteration start date](/assets/images/help/projects-v2/iteration-field-starts.png) -3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![Screenshot showing the iteration duration](/assets/images/help/projects-v2/iteration-field-duration.png) -4. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save-and-create.png) +1. **Iteration（繰り返し）**を選択してください。 ![繰り返しのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-iteration.png) +2. あるいは、繰り返しを今日始めたくない場合は、"Starts on（開始）"の隣のカレンダードロップダウンを選択し、新しい開始日を選択してください。 ![繰り返しの開始日を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-starts.png) +3. それぞれの繰り返しの期間を変更するには、新しい数値を入力し、ドロップダウンを選択して**days（日）**もしくは**weeks（週）**をクリックしてください。 ![繰り返しの期間を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-field-duration.png) +4. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save-and-create.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 ## 新しい繰り返しの追加 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) -1. 同じ期間の新しい繰り返しを追加したいなら、**Add iteration（繰り返しの追加）**をクリックしてください。 ![Screenshot the "add iteration" button](/assets/images/help/projects-v2/add-iteration.png) -1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} **More options**, select a starting date and duration, and click **Add**. ![Screenshot the add iteration options form](/assets/images/help/projects-v2/add-iteration-options.png) -1. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) +1. 同じ期間の新しい繰り返しを追加したいなら、**Add iteration（繰り返しの追加）**をクリックしてください。 !["add iteration"ボタンのスクリーンショット](/assets/images/help/projects-v2/add-iteration.png) +1. あるいは、新しい繰り返しの期間と開始時点をカスタマイズしたいなら、{% octicon "triangle-down" aria-label="The triangle icon" %} **More options（追加のオプション）**をクリックし、開始日と期間を選択し、**Add（追加）**をクリックしてください。 ![繰り返しの追加オプションフォームのスクリーンショット](/assets/images/help/projects-v2/add-iteration-options.png) +1. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) ## 繰り返しの編集 繰り返しは、プロジェクトの設定で編集できます。 繰り返しフィールドの設定には、フィールドの表ヘッダ内の{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、**Edit values（値の編集）**をクリックしてもアクセスできます。 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) -1. To change the name of an iteration, click on the name and start typing. ![Screenshot an title field to rename an iteration](/assets/images/help/projects-v2/iteration-rename.png) -1. 繰り返しの日付や期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 ![Screenshot showing iteration dates](/assets/images/help/projects-v2/iteration-date.png) -1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}. ![Screenshot the delete button](/assets/images/help/projects-v2/iteration-delete.png) -2. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) +1. 繰り返しの名前を変更するには、名前をクリックして入力していってください。 ![繰り返しの名前を変更するタイトルフィールドのスクリーンショット](/assets/images/help/projects-v2/iteration-rename.png) +1. 繰り返しの日付や期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 ![繰り返しの日付を表示しているスクリーンショット](/assets/images/help/projects-v2/iteration-date.png) +1. あるいは、繰り返しを削除したい場合は{% octicon "trash" aria-label="The trash icon" %}をクリックしてください。 ![削除ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-delete.png) +2. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) ## 休憩の挿入 繰り返しには、スケジュールされた作業から離れることを知らせるために休憩を挿入できます。 新しい休憩期間のデフォルトは、直近に作成された繰り返しの長さです。 {% data reusables.projects.project-settings %} -1. Click the name of the iteration field you want to adjust. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-iteration-field.png) +1. 調整したい繰り返しフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-iteration-field.png) 2. 繰り返しの上の分割線上の右で**Insert break（休憩の挿入）**をクリックしてください。 !["休憩の挿入"ボタンの場所を表示しているスクリーンショット](/assets/images/help/issues/iteration-insert-break.png) 3. あるいは、休憩の期間を変更するには、日付をクリックしてカレンダーを開いてください。 開始日をクリックし、続いて終了日をクリックし、そして**Apply（適用）**をクリックしてください。 -4. [**Save changes**] をクリックします。 ![Screenshot the save button](/assets/images/help/projects-v2/iteration-save.png) +4. [**Save changes**] をクリックします。 ![保存ボタンのスクリーンショット](/assets/images/help/projects-v2/iteration-save.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md index fdb76a38e7..393209f0e0 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md @@ -1,7 +1,7 @@ --- -title: About single select fields -shortTitle: About single select fields -intro: You can create single select fields with defined options that can be selected from a dropdown menu. +title: 単一選択フィールドについて +shortTitle: 単一選択フィールドについて +intro: ドロップダウンメニューから選択できる定義済みの選択肢で単一選択フィールドを作成できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,24 +10,24 @@ topics: - Projects --- -You can filter by your single select fields by specifying the option, for example: `fieldname:option`. You can filter for multiple values by providing a comma-separated list of options, for example: `fieldname:option,option`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +単一選択フィールドは、たとえば`fieldname:option`のようにオプションを指定してフィルタリングできます。 たとえば`fieldname:option,option`というように、カンマ区切りのリストのオプションを渡すことで、複数の値に対してフィルタリングできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -Single select fields can contain up to 50 options. +単一選択フィールドは、最大で50個の選択肢を含むことができます。 -## Adding a single select field +## 単一選択フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Single select** ![Screenshot showing the single select option](/assets/images/help/projects-v2/new-field-single-select.png) -1. Below "Options", type the first option. ![Screenshot showing the single select option](/assets/images/help/projects-v2/single-select-create-with-options.png) - - To add additional options, click **Add option**. -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Single select（単一選択）**を選択してください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-single-select.png) +1. "Options（選択肢）"の下で、最初の選択肢を入力してください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-create-with-options.png) + - 選択肢を追加するには**Add option（選択肢の追加）**をクリックしてください。 +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 -## Editing a single select field +## 単一選択フィールドの編集 {% data reusables.projects.project-settings %} -1. Click the name of the single select field you want to adjust. ![Screenshot showing an single select field](/assets/images/help/projects-v2/select-single-select.png) -1. Edit existing options or click **Add option**. ![Screenshot showing single select options](/assets/images/help/projects-v2/single-select-edit-options.png) -1. Optionally, to delete an option, click {% octicon "x" aria-label="The x icon" %}. ![Screenshot showing delete button](/assets/images/help/projects-v2/single-select-delete.png) -1. Click **Save options**. ![Screenshot showing save button](/assets/images/help/projects-v2/save-options.png) +1. 調整したい単一選択フィールドの名前をクリックしてください。 ![単一選択フィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. 既存の選択肢を編集するか、**Add option（選択肢の追加）**をクリックしてください。 ![単一選択の選択肢を表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-edit-options.png) +1. あるいは、選択肢を削除したい場合は{% octicon "x" aria-label="The x icon" %}をクリックしてください。 ![削除ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/single-select-delete.png) +1. **Save options（選択肢の保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/save-options.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md index e07cb71d3f..4abb2def2b 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md @@ -1,7 +1,7 @@ --- -title: About text and number fields -shortTitle: About text and number fields -intro: You can add custom text and number fields to your project. +title: テキスト及び数値フィールドについて +shortTitle: テキスト及び数値フィールドについて +intro: プロジェクトに、カスタムのテキスト及び数値フィールドを追加できます。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,24 +10,24 @@ topics: - Projects --- -You can use text fields to include notes or any other freeform text in your project. +テキストフィールドを使ってノートやその他の自由形式のテキストをプロジェクトに含めることができます。 -Text fields can be used in filters, for example: `field:"exact text"`. Text fields and item titles will also be used if you filter for text without specifying a field. +テキストフィールドは、たとえば`field:"exact text"`というようにフィルタで使うことができます。 テキストフィールドとアイテムのタイトルは、フィールドを指定せずにテキストに対してフィルタを掛けた場合にも使われます。 -Number fields can also be used in filters. You can use `>`, `>=`, `<`, `<=`, and `..` range queries to filter by a number field. For example: `field:5..15` or `field:>=20`. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +数値フィールドもフィルタで利用できます。 `>`、`>=`、`<`、`<=`、`..`といった範囲修飾子を数値フィールドでのフィルタリングのために利用できます。 たとえば`field:5..15`あるいは`field:>=20`といったようにできます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -## Adding a text field +## テキストフィールドの追加 {% data reusables.projects.new-field %} -1. Select **Text** ![Screenshot showing the text option](/assets/images/help/projects-v2/new-field-text.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Text（テキスト）**を選択してください。 ![テキストのオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-text.png) +1. **Save（保存）**をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 -## Adding a number field +## 数値フィールドの追加 {% data reusables.projects.new-field %} -1. Select **Number** ![Screenshot showing the number option](/assets/images/help/projects-v2/new-field-number.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/new-field-save.png) +1. **Number（数値）**を選択してください。 ![数値のオプションを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-number.png) +1. **Save（保存）**をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/new-field-save.png) -Alternatively, open the project command palette by pressing {% data variables.projects.command-palette-shortcut %} and start typing "Create new field." +または、{% data variables.projects.command-palette-shortcut %}を押してプロジェクトのコマンドパレットをオープンし、"Create new field"と入力していってください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md index 94b0ea1cec..bb3bfe0db5 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md @@ -1,6 +1,6 @@ --- -title: Deleting fields -intro: 'Learn how to delete a field from your {% data variables.projects.project_v2 %}.' +title: フィールドの削除 +intro: '{% data variables.projects.project_v2 %}からフィールドを削除する方法を学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,6 +10,6 @@ topics: --- {% data reusables.projects.project-settings %} -1. Click the name of the field you want to delete. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) -1. Next to the field's name, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing field name](/assets/images/help/projects-v2/field-options.png) -1. Click **Delete field**. ![Screenshot showing field name](/assets/images/help/projects-v2/delete-field.png) +1. 削除したいフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. フィード名の隣の{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/field-options.png) +1. **Delete field（フィールドを削除）**をクリックしてください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/delete-field.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md index 09b569a5d0..5368b5b0f8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md @@ -1,7 +1,7 @@ --- -title: Understanding field types -shortTitle: Understanding field types -intro: 'Learn about the different custom field types, how to add custom fields to your project, and how to manage custom fields.' +title: フィールドタイプを理解する +shortTitle: フィールドタイプを理解する +intro: 様々なカスタムフィールドについて、そしてプロジェクトへのカスタムフィールドの追加の方法、カスタムフィールドの管理の方法について学んでください。 versions: feature: projects-v2 topics: diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md index 0455d3640d..253221914c 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md @@ -1,6 +1,6 @@ --- -title: Renaming fields -intro: 'Learn about renaming existing fields in your {% data variables.projects.project_v2 %}.' +title: フィールドの名前の変更 +intro: '{% data variables.projects.project_v2 %}中の既存のフィールドの名前の変更について学んでください。' miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -10,6 +10,6 @@ topics: --- {% data reusables.projects.project-settings %} -1. Click the name of the field you want to rename. ![Screenshot showing an iteration field](/assets/images/help/projects-v2/select-single-select.png) -1. Under "Field name", type the new name for the field. ![Screenshot showing field name](/assets/images/help/projects-v2/field-rename.png) -1. To save changes, press Return. +1. 名前を変更したいフィールドの名前をクリックしてください。 ![繰り返しフィールドを表示しているスクリーンショット](/assets/images/help/projects-v2/select-single-select.png) +1. "Field name（フィールド名）"の下で、フィールドの新しい名前を入力してください。 ![フィールド名を表示しているスクリーンショット](/assets/images/help/projects-v2/field-rename.png) +1. 変更を保存するためにReturnを押してください。 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md index 8207aa5d0e..415a4a3eb8 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/about-insights-for-projects.md @@ -1,5 +1,5 @@ --- -title: 'About insights for {% data variables.product.prodname_projects_v2 %}' +title: '{% data variables.product.prodname_projects_v2 %}のインサイトについて' intro: プロジェクトのデータから構築されたグラフを表示させ、カスタマイズできます。 miniTocMaxHeadingLevel: 3 versions: @@ -17,35 +17,35 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** Historical charts are currently available as a feature preview for organizations using {% data variables.product.prodname_team %} and are generally available for organizations using {% data variables.product.prodname_ghe_cloud %}. +**ノート:** 履歴グラフは現在{% data variables.product.prodname_team %}を使用しているOrganizationでは機能プレビューとして利用でき、{% data variables.product.prodname_ghe_cloud %}を利用しているOrganizationでは一般利用可能です。 {% endnote %} {% endif %} - You can use insights for {% data variables.product.prodname_projects_v2 %} to view, create, and customize charts that use the items added to your project as their source data. デフォルトのグラフにフィルタを適用することも、独自のグラフを作成することもできます。 When you create a chart, you set the filters, chart type, the information displayed, and the chart is available to anyone that can view the project. You can generate two types of chart: current charts and historical charts. + {% data variables.product.prodname_projects_v2 %}のインサイトを使い、プロジェクトに追加したアイテムをソースデータとして利用してグラフの表示、作成、カスタマイズができます。 デフォルトのグラフにフィルタを適用することも、独自のグラフを作成することもできます。 グラフを作成する際には、フィルタ、グラフの種類、表示される情報を設定します。そのグラフは、プロジェクトを見ることができる人なら誰でも利用できます。 現在のグラフと履歴グラフという2種類のグラフを生成できます。 - ### About current charts + ### 現在のグラフについて -You can create current charts to visualize your project items. For example, you can create charts to show how many items are assigned to each individual, or how many issues are assigned to each upcoming iteration. +現在のグラフを作成して、プロジェクトのアイテムを可視化できます。 たとえば、各個人にいくつのアイテムが割り当てられているかを表示するグラフや、この先の繰り返しにいくつのIssueがアサインされているかを表示するグラフを作成できます。 -You can also use filters to manipulate the data used to build your chart. For example, you can create a chart showing how much upcoming work you have, but limit those results to particular labels or assignees. 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 +グラフを構築する溜めに使われるデータを操作するために、フィルタを使うこともできます。 たとえば、この先の作業がいくつあるのかを示すグラフを作成し、ただしその結果を特定のラベルやアサインされた人に限定することができます。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 ![各イテレーションのアイテムの種類を表示する積み上げ列グラフのスクリーンショット](/assets/images/help/issues/column-chart-example.png) -For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)." +詳しい情報については「[グラフの作成](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)」を参照してください。 - ### About historical charts + ### 履歴グラフについて - Historical charts are time-based charts that allow you to view your project's trends and progress. You can view the number of items, grouped by status and other fields, over time. + 履歴グラフは時間ベースのグラフで、プロジェクトのトレンドと進捗を表示できます。 ステータスやその他のフィールドでグループ化されたアイテム数を、時間の経過とともに表示できます。 デフォルトの「バーンアップ」グラフは、時間の経過に伴うアイテムのステータスを表示し、進捗を可視化して時間の経過にともなるパターンを特定できます。 ![現在の繰り返しに対するデフォルトのバーンアップグラフの例を表示しているスクリーンショット](/assets/images/help/issues/burnup-example.png) - To create a historical chart, set your chart's X-axis to "Time." For more information, see "[Creating charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)" and "[Configuring charts](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)." + 履歴グラフを作成するには、グラフのX軸を"Time（時間）"に設定してください。 詳しい情報については「[グラフの作成](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts)」及び「[グラフの設定](/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts)」を参照してください。 ## 参考リンク - [{% data variables.product.prodname_projects_v2 %}について](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) -- "[Disabling insights for {% data variables.product.prodname_projects_v2 %} in your organization](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)" +- 「[Organizationでの{% data variables.product.prodname_projects_v2 %}のインサイトの無効化](/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization)」 diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md index 342f88625d..bec7dbd328 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/configuring-charts.md @@ -1,6 +1,6 @@ --- -title: Configuring charts -intro: Learn how to configure your charts and filter data from your project. +title: グラフの設定 +intro: グラフを設定し、プロジェクトからのデータをフィルタリングする方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -14,17 +14,17 @@ topics: {% note %} -**Note:** Historical charts are currently available as a feature preview. +**ノート:** 履歴グラフは現在機能プレビューとして利用できます。 {% endnote %} {% endif %} {% data reusables.projects.access-insights %} -1. In the menu on the left, click on the chart you would like to configure. ![Screenshot showing selecting a custom chart](/assets/images/help/projects-v2/insights-select-a-chart.png) -1. ページの右側で、**Configure（設定）**をクリックしてください。 パネルが右側に開きます。 ![Screenshot showing the configure button](/assets/images/help/projects-v2/insights-configure.png) -1. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 ![Screenshot showing selecting a chart layout](/assets/images/help/projects-v2/insights-layout.png) -1. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 ![Screenshot showing selecting what to display on the x axis](/assets/images/help/projects-v2/insights-x-axis.png) -1. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 ![Screenshot showing selecting a grouping method](/assets/images/help/projects-v2/insights-group.png) -1. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 ![Screenshot showing selecting what to display on the y axis](/assets/images/help/projects-v2/insights-y-axis.png) -1. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 ![Screenshot showing the save button](/assets/images/help/projects-v2/insights-save.png) +1. 左のメニューで、設定したいグラフをクリックしてください。 ![カスタムグラフの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-select-a-chart.png) +1. ページの右側で、**Configure（設定）**をクリックしてください。 パネルが右側に開きます。 ![設定ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-configure.png) +1. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 ![グラフのレイアウトの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-layout.png) +1. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 ![X軸に表示するものの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-x-axis.png) +1. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 ![グループ化の方法の選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-group.png) +1. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 ![Y軸に表示するものの選択を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-y-axis.png) +1. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-save.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md index 14541998c7..5a2a1dfcab 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/creating-charts.md @@ -1,6 +1,6 @@ --- -title: Creating charts -intro: Learn how to create new charts to save your configurations. +title: グラフの作成 +intro: 新しいグラフを作成して設定を保存する方法を学んでください。 miniTocMaxHeadingLevel: 3 versions: feature: projects-v2 @@ -11,7 +11,7 @@ topics: --- {% data reusables.projects.access-insights %} -3. 左のメニューで**New chart（新規グラフ）**をクリックしてください。 ![Screenshot showing the new chart button](/assets/images/help/projects-v2/insights-new-chart.png) -4. あるいは、新しいグラフの名前を変更するには{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、新しい名前を入力し、Returnを押してください。 ![Screenshot showing how to rename a chart](/assets/images/help/projects-v2/insights-rename.png) +3. 左のメニューで**New chart（新規グラフ）**をクリックしてください。 ![新規グラフボタンが表示されているスクリーンショット](/assets/images/help/projects-v2/insights-new-chart.png) +4. あるいは、新しいグラフの名前を変更するには{% octicon "triangle-down" aria-label="The triangle icon" %}をクリックし、新しい名前を入力し、Returnを押してください。 ![グラフの名前の変更方法を表示しているスクリーンショット](/assets/images/help/projects-v2/insights-rename.png) 5. グラフの上で、グラフを構築するのに使われたデータを変更するフィルタを入力してください。 詳しい情報については「[プロジェクトのフィルタリング](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/filtering-projects)」を参照してください。 -6. フィルタのテキストボックスの右で、**Save changes（変更を保存）**をクリックしてください。 ![Screenshot showing save button](/assets/images/help/projects-v2/insights-save-filter.png) +6. フィルタのテキストボックスの右で、**Save changes（変更を保存）**をクリックしてください。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/insights-save-filter.png) diff --git a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md index 84047d3771..267a5afea9 100644 --- a/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md +++ b/translations/ja-JP/content/issues/planning-and-tracking-with-projects/viewing-insights-from-your-project/index.md @@ -1,6 +1,6 @@ --- -title: 'Viewing insights from your {% data variables.projects.project_v2 %}' -shortTitle: Viewing insights +title: '{% data variables.projects.project_v2 %}のインサイトの表示' +shortTitle: インサイトの表示 intro: ... versions: feature: projects-v2 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md index c7595f2857..c2bf8fb3f7 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/about-issues.md @@ -32,7 +32,7 @@ Issueは様々な方法で作成できるので、ワークフローで最も便 プロジェクトで、Issueを整理して優先順位付けできます。 {% ifversion fpt or ghec %}大きなIssueの一部であるIssueを追跡するには、タスクリストが使えます。{% endif %}関連するIssueを分類するには、ラベルとマイルストーンが使えます。 -For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)." {% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} {% ifversion fpt or ghec %}For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." {% endif %}ラベルとマイルストーンに関する詳しい情報については「[作業を追跡するためのラベルとマイルストーンの利用](/issues/using-labels-and-milestones-to-track-work)」を参照してください。 +プロジェクトに関する詳しい情報については{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」 {% else %}「[プロジェクトボードで作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。{% ifversion fpt or ghec %}タスクリストに関する詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。 {% endif %}ラベルとマイルストーンに関する詳しい情報については「[作業を追跡するためのラベルとマイルストーンの利用](/issues/using-labels-and-milestones-to-track-work)」を参照してください。 ## 最新情報の確認 diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index f4c2ab30cb..e751ab3fbb 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -43,7 +43,7 @@ Pull Requestの説明もしくはコミットメッセージ中でサポート * fix * fixes * fixed -* 解決 +* resolve * resolves * resolved diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md index f71e3526c1..c436e96ae1 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md @@ -1,6 +1,6 @@ --- -title: Teamもしくはプロジェクトの作業の計画と追跡 -intro: '{% data variables.product.prodname_dotcom %}の計画及び追跡ツールを使って、Teamあるいはプロジェクトの作業を管理するために必要なこと。' +title: Planning and tracking work for your team or project +intro: 'The essentials for using {% data variables.product.prodname_dotcom %}''s planning and tracking tools to manage work on a team or project.' versions: fpt: '*' ghes: '*' @@ -11,120 +11,119 @@ topics: - Project management - Projects --- +## Introduction +You can use {% data variables.product.prodname_dotcom %} repositories, issues, project boards, and other tools to plan and track your work, whether working on an individual project or cross-functional team. -## はじめに -個別のプロジェクトで作業しているにしても、機能横断的なチームで作業しているにしても、{% data variables.product.prodname_dotcom %}のリポジトリ、Issue、プロジェクトボードやその他のツールを使って作業の計画と追跡ができます。 +In this guide, you will learn how to create and set up a repository for collaborating with a group of people, create issue templates{% ifversion fpt or ghec %} and forms{% endif %}, open issues and use task lists to break down work, and establish a project board for organizing and tracking issues. -このガイドでは、人々のグループとコラボレーションするためのリポジトリの作成とセットアップ、Issueテンプレート{% ifversion fpt or ghec %}及びフォーム{% endif %}の作成、Issueのオープンと作業をブレークダウンするためのタスクリストの利用、Issueを整理して追跡するためのプロジェクトボードの設置の方法を学びます。 +## Creating a repository +When starting a new project, initiative, or feature, the first step is to create a repository. Repositories contain all of your project's files and give you a place to collaborate with others and manage your work. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)." -## リポジトリを作成する -新しいプロジェクト、イニシアティブ、機能を開始するとき、最初のステップはリポジトリの作成です。 リポジトリにはプロジェクトのすべてのファイルが含まれ、他者とコラボレーションしたり、作業を管理したりする場所を提供します。 詳しい情報については「[新しいリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-a-new-repository)」を参照してください。 +You can set up repositories for different purposes based on your needs. The following are some common use cases: -必要に応じて、様々な目的のためにリポジトリをセットアップできます。 以下は、いくつかの一般的なユースケースです。 +- **Product repositories**: Larger organizations that track their work and goals around specific products may have one or more repositories containing the code and other files. These repositories can also be used for documentation, reporting on product health or future plans for the product. +- **Project repositories**: You can create a repository for an individual project you are working on, or for a project you are collaborating on with others. For an organization that tracks work for short-lived initiatives or projects, such as a consulting firm, there is a need to report on the health of a project and move people between different projects based on skills and needs. Code for the project is often contained in a single repository. +- **Team repositories**: For an organization that groups people into teams, and brings projects to them, such as a dev tools team, code may be scattered across many repositories for the different work they need to track. In this case it may be helpful to have a team-specific repository as one place to track all the work the team is involved in. +- **Personal repositories**: You can create a personal repository to track all your work in one place, plan future tasks, or even add notes or information you want to save. You can also add collaborators if you want to share this information with others. -- **製品リポジトリ**: 特定の製品に関する作業とゴールを追跡する大規模な組織は、そのコードや他のファイルを含む1つ以上のリポジトリを持つことがあります。 それらのリポジトリは、ドキュメンテーション、製品の改善性、あるいは製品の将来の計画のためにも使われることがあります。 -- **プロジェクトリポジトリ**: 作業をしている個々のプロジェクト、あるいは他者とコラボレーションしているプロジェクトのためにリポジトリを作成することができます。 短期間のイニシアティブやプロジェクトなどのための作業を追跡する、たとえばコンサルティングファームなどの組織では、プロジェクトの健全性に関するレポートや、人々をスキルや要求に応じて様々なプロジェクト間で移動させる必要があります。 こうしたプロジェクトのためのコードは、多くの場合1つのリポジトリに含まれます。 -- **チームリポジトリ**: 人々をチームにグループ化し、開発ツールチームのようなそれらのグループにプロジェクトを割り当てるような組織では、コードは追跡しなければならない様々な作業に対する多くのリポジトリに分散されるかもしれません。 この場合、そのチームが関わるすべての作業を追跡するための1つの場所として、チーム固有のリポジトリを持つとよいかもしれません。 -- **個人リポジトリ**: 個人リポジトリを作成して、自分のすべての作業を1カ所で追跡し、将来のタスクを計画し、さらには保存しておきたいノートや情報を追加しておくことさえできます。 この情報を他者と共有したい場合は、コラボレータを追加することもできます。 +You can create multiple, separate repositories if you want different access permissions for the source code and for tracking issues and discussions. For more information, see "[Creating an issues-only repository](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)." -ソースコードに様々なアクセス権限を設定し、Issueやディスカッションを追跡したい場合には、複数の個別のリポジトリを作成することもできます。 詳しい情報については「[Issueのみのリポジトリの作成](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/creating-an-issues-only-repository)」を参照してください。 +For the following examples in this guide, we will be using an example repository called Project Octocat. +## Communicating repository information +You can create a README.md file for your repository to introduce your team or project and communicate important information about it. A README is often the first item a visitor to your repository will see, so you can also provide information on how users or contributors can get started with the project and how to contact the team. For more information, see "[About READMEs](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)." -このガイドの以下の例では、Projet Octocatというサンプルリポジトリを使います。 -## リポジトリ情報のコミュニケーション -リポジトリにREADME.mdファイルを追加して、Teamやプロジェクトを紹介し、それらに関する重要な情報を伝えることができます。 リポジトリにアクセスした人が最初に見るのはREADMEのことが多いので、ユーザやコントリビュータがプロジェクトとどのように関わり始めたらいいのか、そしてチームとどのように連絡を取ればいいのかに関する情報を提供することもできます。 詳細は「[README について](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-readmes)」を参照してください。 +You can also create a CONTRIBUTING.md file specifically to contain guidelines on how users or contributors can contribute and interact with the team or project, such as how to open a bug fix issue or request an improvement. For more information, see "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)." +### README example +We can create a README.md to introduce our new project, Project Octocat. -特に、バグ修正のIssueのオープンや改善のリクエストの方法といった、ユーザやコントリビュータがチームやプロジェクトに貢献して関わるやりかたのガイドラインを含む、CONTRIBUTING.mdファイルを作成することもできます。 詳しい情報については、「[リポジトリコントリビューターのためのガイドラインを定める](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)」を参照してください。 -### README の例 -新しいプロジェクトであるProject Octocatを紹介するREADME.mdを作成できます。 +![Creating README example](/assets/images/help/issues/quickstart-creating-readme.png) +## Creating issue templates -![READMEの例の作成](/assets/images/help/issues/quickstart-creating-readme.png) -## Issue テンプレートを作成する +You can use issues to track the different types of work that your cross-functional team or project covers, as well as gather information from those outside of your project. The following are a few common use cases for issues. -Issueを使って、機能横断的なチームやプロジェクトがカバーする様々な種類の作業を追跡したり、プロジェクト外のチームやプロジェクトから情報を集めることができます。 以下は、いくつかの一般的なIssueのユースケースです。 +- Release tracking: You can use an issue to track the progress for a release or the steps to complete the day of a launch. +- Large initiatives: You can use an issue to track progress on a large initiative or project, which is then linked to the smaller issues. +- Feature requests: Your team or users can create issues to request an improvement to your product or project. +- Bugs: Your team or users can create issues to report a bug. -- リリース追跡: Issueを使って、リリースやローンチ日を完了させるステップの進捗を追跡できます。 -- 大規模なイニシアティブ: Issueを使って、大規模なイニシアティブやプロジェクトの進捗を追跡できます。それらは、より小さなIssueにリンクされます。 -- 機能リクエスト: チームやユーザは、Issueを作成して製品やプロジェクトに改善をリクエストできます。 -- バグ: チームやユーザは、Issueを作成してバグを報告できます。 +Depending on the type of repository and project you are working on, you may prioritize certain types of issues over others. Once you have identified the most common issue types for your team, you can create issue templates {% ifversion fpt or ghec %}and forms{% endif %} for your repository. Issue templates {% ifversion fpt or ghec %}and forms{% endif %} allow you to create a standardized list of templates that a contributor can choose from when they open an issue in your repository. For more information, see "[Configuring issue templates for your repository](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)." -作業をしているリポジトリやプロジェクトの種類によっては、特定の種類のIssueを他よりも優先することになるかもしれません。 チームで最も一般的なIssueの種類を特定できたら、リポジトリにIssueテンプレート{% ifversion fpt or ghec %}やフォーム{% endif %}を作成できます。 Issueテンプレート{% ifversion fpt or ghec %}とフォーム{% endif %}を使うと、リポジトリでIssueをオープンするときにコントリビューターが選択できる標準化されたテンプレートのリストを作成できます。 詳しい情報については、「[リポジトリ用に Issue テンプレートを設定する](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)」を参照してください。 +### Issue template example +Below we are creating an issue template for reporting a bug in Project Octocat. -### Issueテンプレートの例 -以下、Project OctocatでバグレポートのためのIssueテンプレートを作成しています。 +![Creating issue template example](/assets/images/help/issues/quickstart-creating-issue-template.png) -![Issueテンプレートの例の作成](/assets/images/help/issues/quickstart-creating-issue-template.png) +Now that we created the bug report issue template, you are able to select it when creating a new issue in Project Octocat. -バグレポートのIssueテンプレートを作成したので、新しいIssueをProject Octocatで作成する際に選択できるようになりました。 +![Choosing issue template example](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png) -![Issueテンプレートの例の選択](/assets/images/help/issues/quickstart-issue-creation-menu-with-template.png) +## Opening issues and using task lists to track work +You can organize and track your work by creating issues. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)." +### Issue example +Here is an example of an issue created for a large initiative, front-end work, in Project Octocat. -## Issueのオープンとタスクリストを使用した作業の追跡 -Issueを作成することで、作業を整理し、追跡できます。 詳しい情報については、「[Issue を作成する](/issues/tracking-your-work-with-issues/creating-issues/creating-an-issue)」を参照してください。 -### Issueの例 -以下は、Project Octocatの大規模なイニシアティブであるフロントエンドの作業のために作成されたIssueの例です。 +![Creating large initiative issue example](/assets/images/help/issues/quickstart-create-large-initiative-issue.png) +### Task list example -![大規模なイニシアティブのissueの例の作成](/assets/images/help/issues/quickstart-create-large-initiative-issue.png) -### タスクリストの例 +You can use task lists to break larger issues down into smaller tasks and to track issues as part of a larger goal. {% ifversion fpt or ghec %} Task lists have additional functionality when added to the body of an issue. You can see the number of tasks completed out of the total at the top of the issue, and if someone closes an issue linked in the task list, the checkbox will automatically be marked as complete.{% endif %} For more information, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)." -タスクリストを使って、大きなIssueを小さなタスクに分割し、大きなゴールの一部としてIssueを追跡できます。 {% ifversion fpt or ghec %}Issueの本体に追加されたタスクリストには、追加の機能があります。 Issueの上部では全体の中で完了したタスク数を見ることができ、誰かがタスクリストにリンクされたIssueをクローズすると、そのチェックボックスは自動的に完了としてマークされます。{% endif %}詳しい情報については「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。 +Below we have added a task list to our Project Octocat issue, breaking it down into smaller issues. -以下では、Project OctocatのIssueにタスクリストを追加し、小さなIssueに分割しました。 +![Adding task list to issue example](/assets/images/help/issues/quickstart-add-task-list-to-issue.png) -![Issueの例へのタスクリストの追加](/assets/images/help/issues/quickstart-add-task-list-to-issue.png) +## Making decisions as a team +You can use issues and discussions to communicate and make decisions as a team on planned improvements or priorities for your project. Issues are useful when you create them for discussion of specific details, such as bug or performance reports, planning for the next quarter, or design for a new initiative. Discussions are useful for open-ended brainstorming or feedback, outside the codebase and across repositories. For more information, see "[Which discussion tool should I use?](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)." -## チームとしての意思決定 -Issueやディスカッションを使い、プロジェクトの計画された改善や優先順位についてコミュニケーションを取り、チームとして意思決定することができます。 Issueは、バグやパフォーマンスレポート、次の四半期の計画、新しいイニシアティブのデザインといった、特定の詳細に関するディスカッションのために作成すると役立ちます。 ディスカッションは、コードベース外でリポジトリをまたぐオープンエンドのブレインストーミングやフィードバックのために役立ちます。 詳しい情報については「[どのディスカッションツールを使うべきでしょうか？](/github/getting-started-with-github/quickstart/communicating-on-github#which-discussion-tool-should-i-use)」を参照してください。 +As a team, you can also communicate updates on day-to-day tasks within issues so that everyone knows the status of work. For example, you can create an issue for a large feature that multiple people are working on, and each team member can add updates with their status or open questions in that issue. +### Issue example with project collaborators +Here is an example of project collaborators giving a status update on their work on the Project Octocat issue. -チームとして、Issue内の日々のタスクの更新についてコミュニケーションを取り、全員に作業の状況を知らせることができます。 たとえば、複数の人が作業をしている大きな機能についてのIssueを作成し、各チームメンバーがそのIssue内で状況を更新したり質問を投げたりできるようにすることができます。 -### プロジェクトのコラボレータとのIssueの例 -以下は、Project OctocatのIssueで作業状況を更新するプロジェクトのコラボレータの例です。 +![Collaborating on issue example](/assets/images/help/issues/quickstart-collaborating-on-issue.png) +## Using labels to highlight project goals and status +You can create labels for a repository to categorize issues, pull requests, and discussions. {% data variables.product.prodname_dotcom %} also provides default labels for every new repository that you can edit or delete. Labels are useful for keeping track of project goals, bugs, types of work, and the status of an issue. -![Issueの例でのコラボレーション](/assets/images/help/issues/quickstart-collaborating-on-issue.png) -## プロジェクトのゴールとステータスをハイライトするためのラベルの利用 -Issue、Pull Request、ディスカッションを分類するために、リポジトリにラベルを作成できます。 {% data variables.product.prodname_dotcom %}は、すべての新しいリポジトリにデフォルトのラベルを提供します。それらは編集したり削除したりできます。 ラベルは、プロジェクトのゴール、バグ、作業の種類、Issueのステータスを追跡するための役に立ちます。 +For more information, see "[Creating a label](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)." -詳細は「[ラベルの作成](/issues/using-labels-and-milestones-to-track-work/managing-labels#creating-a-label)」を参照してください。 +Once you have created a label in a repository, you can apply it on any issue, pull request or discussion in the repository. You can then filter issues and pull requests by label to find all associated work. For example, find all the front end bugs in your project by filtering for issues with the `front-end` and `bug` labels. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)." +### Label example +Below is an example of a `front-end` label that we created and added to the issue. -リポジトリにラベルを作成すると、それはリポジトリ内の任意のIssue、Pull Request、ディスカッションに適用できます。 そして、すべての関連する作業を見つけるためにラベルでIssueやPull Requestをフィルタリングできます。 たとえば、Issueを`front-end`及び`bug`というラベルでフィルタリングし、すべてのフロントエンドのバグを見つけることができます。 詳しい情報については「[IssueやPull Requestのフィルタリングと検索](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests)」を参照してください。 -### ラベルの例 -以下は、作成した`front-end`の例で、Issueに追加されています。 +![Adding a label to an issue example](/assets/images/help/issues/quickstart-add-label-to-issue.png) -![Issueの例へのラベルの追加](/assets/images/help/issues/quickstart-add-label-to-issue.png) - -## プロジェクトボードへのIssueの追加 +## Adding issues to a project board {% ifversion projects-v2 %} -You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. プロジェクトはカスタマイズ可能なスプレッドシートで、{% data variables.product.prodname_dotcom %}上のIssueやPull Requestと統合されており、自動的に{% data variables.product.prodname_dotcom %}上の情報を最新の状態に保ちます。 IssueやPull Requestのフィルタリング、ソート、グループ化によってレイアウトをカスタマイズできます。 To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." +You can use {% data variables.projects.projects_v2 %} on {% data variables.product.prodname_dotcom %} to plan and track the work for your team. A project is a customizable spreadsheet that integrates with your issues and pull requests on {% data variables.product.prodname_dotcom %}, automatically staying up-to-date with the information on {% data variables.product.prodname_dotcom %}. You can customize the layout by filtering, sorting, and grouping your issues and PRs. To get started with projects, see "[Quickstart for projects](/issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects)." ### Project example -以下は、作成したProject OctocatのIssueが展開されたサンプルプロジェクトの表レイアウトのビューです。 +Here is the table layout of an example project, populated with the Project Octocat issues we have created. ![Projects table layout example](/assets/images/help/issues/quickstart-projects-table-view.png) -同じプロジェクトをボードとして見ることもできます。 +We can also view the same project as a board. ![Projects board layout example](/assets/images/help/issues/quickstart-projects-board-view.png) {% endif %} {% ifversion projects-v1 %} -You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. プロジェクトボードは、Issue、プルリクエスト、選択した列内でカードとして分類されるノートから構成されます。 機能の作業、高レベルのロードマップ、さらにはリリースチェックリストのためにプロジェクトボードを作成できます。 詳細は「[プロジェクトボードについて](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)」を参照してください。 -### プロジェクトボードの例 -以下は、サンプルのProject Octocatのプロジェクトボードで、作成したIssueと、そのIssueをブレークダウンした小さなIssueが追加されています。 +You can {% ifversion projects-v2 %} also use the existing{% else %} use{% endif %} {% data variables.product.prodname_projects_v1 %} on {% data variables.product.prodname_dotcom %} to plan and track your or your team's work. Project boards are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. You can create project boards for feature work, high-level roadmaps, or even release checklists. For more information, see "[About project boards](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)." +### Project board example +Below is a project board for our example Project Octocat with the issue we created, and the smaller issues we broke it down into, added to it. -![プロジェクトボードの例](/assets/images/help/issues/quickstart-project-board.png) +![Project board example](/assets/images/help/issues/quickstart-project-board.png) {% endif %} -## 次のステップ +## Next steps -これで、作業の計画と追跡のために{% data variables.product.prodname_dotcom %}が提供するツールについて学び、機能横断的なチームやプロジェクトのリポジトリのセットアップを始めることができました！ 以下は、さらにリポジトリをカスタマイズし、作業を整理するのに役立つリソースです。 +You have now learned about the tools {% data variables.product.prodname_dotcom %} offers for planning and tracking your work, and made a start in setting up your cross-functional team or project repository! Here are some helpful resources for further customizing your repository and organizing your work. -- リポジトリの作成についてさらに学ぶための「[リポジトリについて](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)」 -- Issueの作成と管理のための様々な方法を学ぶための「[Issueでの作業の追跡](/issues/tracking-your-work-with-issues)」 -- Issueテンプレートについてさらに学ぶための「[IssueとPull Requestテンプレートについて](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)」 -- ラベルの作成、編集、削除の方法を学ぶための「[ラベルの管理](/issues/using-labels-and-milestones-to-track-work/managing-labels)」 -- タスクリストについてさらに学ぶための「[タスクリストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」 +- "[About repositories](/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-repositories)" for learning more about creating repositories +- "[Tracking your work with issues](/issues/tracking-your-work-with-issues)" for learning more about different ways to create and manage issues +- "[About issues and pull request templates](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates)" for learning more about issue templates +- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)" for learning how to create, edit and delete labels +- "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)" for learning more about task lists {% ifversion projects-v2 %} - "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)" for learning more about projects - "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)" for learning how to customize views for projects{% endif %} {% ifversion projects-v1 %}- "[About {% data variables.product.prodname_projects_v1 %}](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)" for learning how to manage project boards{% endif %} diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md index b93003199f..5e22f4ebb3 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/quickstart.md @@ -71,7 +71,7 @@ Issueを分類するために、ラベルを追加してください。 たと ## プロジェクトへのIssueの追加 -You can add the issue to an existing project{% ifversion projects-v2 %} and populate metadata for the project. {% endif %} For more information about projects, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} +Issueを既存のプロジェクトに追加{% ifversion projects-v2 %}してプロジェクトのメタデータを展開 {% endif %}できます。プロジェクトに関する詳しい情報については{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」{% else %}「[プロジェクトボードでの作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。 ![プロジェクトを持つIssue](/assets/images/help/issues/issue-project.png) @@ -97,5 +97,5 @@ Issueは、幅広い目的で使用できます。 例: {% data variables.product.prodname_github_issues %} で次のステップに進む際に役立つ、以下のようなリソースを参照してください。 - Issueについてさらに学ぶには「[Issueについて](/issues/tracking-your-work-with-issues/about-issues)」を参照してください。 -- To learn more about how projects can help you with planning and tracking, see {% ifversion projects-v2 %}"[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."{% else %}"[Organizing your work with project boards](/issues/organizing-your-work-with-project-boards)."{% endif %} +- プロジェクトがどのように計画と追跡に役立つかについてさらに学ぶには、{% ifversion projects-v2 %}「[プロジェクトについて](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)」{% else %}「[プロジェクトボードでの作業の整理](/issues/organizing-your-work-with-project-boards)」{% endif %}を参照してください。 - Issueテンプレート{% ifversion fpt or ghec %}及びIssueフォーム{% endif %}を利用して、コントリビューターが特定の情報を提供してくれるよう促進することについてさらに学ぶには「[IssueやPull Requestが役立つものになるよう促進するためのテンプレートの利用](/communities/using-templates-to-encourage-useful-issues-and-pull-requests)」を参照してください。 diff --git a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index bae593ce4b..fe79929e80 100644 --- a/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -15,21 +15,21 @@ shortTitle: Organizationのプロフィールのカスタマイズ ## Organization のプロフィールページについて {% ifversion org-profile-pin-private %} -You can customize your organization's Overview page to show a README and pinned repositories dedicated to public users or members of the organization. +Organizationの概要ページをカスタマイズして、一般ユーザもしくはOrganizationのメンバー専用のREADMEと固定リポジトリを表示させることができます。 -![Image of a public organization profile page](/assets/images/help/organizations/public_profile.png) +![パブリックのOrganizationプロフィールページの画像](/assets/images/help/organizations/public_profile.png) -Members of your organization who are signed into {% data variables.product.prodname_dotcom %}, can select a `member` or `public` view of the README and pinned repositories when they visit your organization's profile page. +{% data variables.product.prodname_dotcom %}にサインインしたOrganizationのメンバーは、Organizationのプロフィールページにアクセスした際に、READMEと固定リポジトリの`member`もしくは`public`ビューを選択できます。 -![Image of a public organization profile page view context switcher](/assets/images/help/organizations/profile_view_switcher_public.png) +![パブリックのOrganizationプロフィールページのコンテキストスイッチャーの画像](/assets/images/help/organizations/profile_view_switcher_public.png) -The view defaults to `member` if either a members-only README or members-only pinned repositories are present, and `public` otherwise. +メンバー専用のREADMEあるいはメンバー専用の固定リポジトリがある場合は`member`がデフォルトであり、そうでない場合は`public`がデフォルトになります。 -![Image of a members only organization profile page](/assets/images/help/organizations/member_only_profile.png) +![メンバー専用のOrganizationプロフィールページの画像](/assets/images/help/organizations/member_only_profile.png) -Users who are not members of your organization will be shown a `public` view. +Organizationのメンバーではないユーザには、`public`ビューが表示されます。 -### Pinned repositories +### 固定リポジトリ 最大で一般ユーザに対し6つのリポジトリ、そしてOrganizationのメンバーに対して6つのリポジトリを選択することによって、ユーザに対して重要なリポジトリや頻繁に利用されるリポジトリへアクセスを容易にできます。 Organizationのプロフィールにリポジトリを固定すると、"Pinned（ピン止め）"セクションがプロフィールページの"Repositories（リポジトリ）"セクションの上部に表示されます。 @@ -64,24 +64,24 @@ OrganizationのプロフィールのREADMEにどういった情報を含める 2. Organizationの`.github-private`リポジトリで、`profile`フォルダ内に`README.md`というファイルを作成してください。 3. `README.md`ファイルへの変更をコミットしてください。 `README.md`の内容は、Organizationプロフィールのメンバービューに表示されます。 - ![Image of an organization's member-only README](/assets/images/help/organizations/org_member_readme.png) + ![Organizationのメンバー専用READMEの画像](/assets/images/help/organizations/org_member_readme.png) -## Organizationのプロフィールへのリポジトリのピン止め +## Organizationのプロフィールへのリポジトリの固定 -頻繁に使われるようなリポジトリなど、強調したいリポジトリをOrganizationのプロフィールページにピン止めできます。 Organizaitonのプロフィールにピン止めするリポジトリを選択するには、Organizationのオーナーでなければなりません。 +頻繁に使われるようなリポジトリなど、強調したいリポジトリをOrganizationのプロフィールページに固定できます。 Organizaitonのプロフィールに固定するリポジトリを選択するには、Organizationのオーナーでなければなりません。 1. Organizationのプロフィールページにアクセスしてください。 2. ページの右のサイドバー内の{% octicon "eye" aria-label="The eye octicon" %} "View as"リンク内で、ドロップダウンメニューから**Public（公開）**もしくは**Member（メンバー）**プロフィールビューを選択してください。 ![Organizationプロフィールビューのドロップダウンの画像](/assets/images/help/organizations/org_profile_view.png) -3. ピン止めされたリポジトリのセクションで、**Customize pins（ピン止めのカスタマイズ）**を選択してください。 +3. 固定リポジトリのセクションで、**Customize pins（固定のカスタマイズ）**を選択してください。 ![ピン止めのカスタマイズリンクの画像](/assets/images/help/organizations/customize_pins_link.png) - - まだOrganizationのプロフィールにピン止めしたリポジトリがないなら、代わりにプロフィールページの右のサイドバーにある**pin repositories（リポジトリのピン止め）**をクリックしなければなりません。 ![右のサイドバーにあるリポジトリのピン止めリンクの画像](/assets/images/help/organizations/pin_repositories_link.png) + - まだOrganizationのプロフィールに固定リポジトリがないなら、代わりにプロフィールページの右のサイドバーにある**pin repositories（リポジトリの固定）**をクリックしなければなりません。 ![右のサイドバーにあるリポジトリのピン止めリンクの画像](/assets/images/help/organizations/pin_repositories_link.png) -4. "Edit pinned repositories（ピン止めされたリポジトリの編集）"ダイアログボックスで、最大で6つの表示するパブリック、{% ifversion not fpt %}プライベート、もしくはインターナル{% else %}もしくはプライベート{% endif %}リポジトリの組み合わせを選択してください。 +4. "Edit pinned repositories（固定リポジトリの編集）"ダイアログボックスで、最大で6つの表示するパブリック、{% ifversion not fpt %}プライベート、もしくはインターナル{% else %}もしくはプライベート{% endif %}リポジトリの組み合わせを選択してください。 ![ピン止めされたリポジトリダイアログの画像](/assets/images/help/organizations/pinned_repo_dialog.png) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md index 90a1037c57..cac3872bad 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/adding-an-outside-collaborator-to-a-project-board-in-your-organization.md @@ -1,6 +1,6 @@ --- -title: 'Adding an outside collaborator to a {% data variables.product.prodname_project_v1 %} in your organization' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can add an outside collaborator and customize their permissions to a {% data variables.projects.projects_v1_board %}.' +title: 'Organizationの{% data variables.product.prodname_project_v1 %}への外部のコラボレータの追加' +intro: 'Organizationのオーナーもしくは{% data variables.projects.projects_v1_board %}の管理者は、{% data variables.projects.projects_v1_board %}に外部のコラボレータを追加してその権限をカスタマイズできます。' redirect_from: - /articles/adding-an-outside-collaborator-to-a-project-board-in-your-organization - /github/setting-up-and-managing-organizations-and-teams/adding-an-outside-collaborator-to-a-project-board-in-your-organization @@ -18,7 +18,7 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.project_boards_old %} -An outside collaborator is a person who isn't explicitly a member of your organization, but who has permissions to a {% data variables.projects.projects_v1_board %} in your organization. +外部のコラボレータは Organization の明示的なメンバーではありませんが、Organizationの{% data variables.projects.projects_v1_board %}への権限を持っています。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md index 151b332f3b..fe90d2cf81 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/index.md @@ -1,6 +1,6 @@ --- -title: 'Managing access to your organization’s {% data variables.product.prodname_projects_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give organization members, teams, and outside collaborators different levels of access to {% data variables.projects.projects_v1_boards %} owned by your organization.' +title: 'Organizationの{% data variables.product.prodname_projects_v1 %}へのアクセス管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organization が所有する{% data variables.projects.projects_v1_boards %}について、Organization のメンバー、チーム、外部のコラボレータごとに異なるレベルのアクセス権を付与できます。' redirect_from: - /articles/managing-access-to-your-organization-s-project-boards - /articles/managing-access-to-your-organizations-project-boards @@ -20,7 +20,7 @@ children: - /managing-an-individuals-access-to-an-organization-project-board - /adding-an-outside-collaborator-to-a-project-board-in-your-organization - /removing-an-outside-collaborator-from-an-organization-project-board -shortTitle: 'Manage {% data variables.product.prodname_project_v1 %} access' +shortTitle: '{% data variables.product.prodname_project_v1 %}アクセスの管理' allowTitleToDifferFromFilename: true --- diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md index 4d15a9b801..d864160caa 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members.md @@ -1,6 +1,6 @@ --- -title: 'Managing access to a {% data variables.product.prodname_project_v1 %} for organization members' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can set a default permission level for a {% data variables.projects.projects_v1_board %} for all organization members.' +title: 'Organizationのメンバーに対する{% data variables.product.prodname_project_v1 %}へのアクセスの管理' +intro: 'Organizationのオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、すべてのOrganizationメンバーに対して{% data variables.projects.projects_v1_board %}へのデフォルトの権限レベルを設定できます。' redirect_from: - /articles/managing-access-to-a-project-board-for-organization-members - /github/setting-up-and-managing-organizations-and-teams/managing-access-to-a-project-board-for-organization-members @@ -18,13 +18,13 @@ allowTitleToDifferFromFilename: true {% data reusables.projects.project_boards_old %} -By default, organization members have write access to their organization's {% data variables.projects.projects_v1_boards %} unless organization owners or {% data variables.projects.projects_v1_board %} admins set different permissions for specific {% data variables.projects.projects_v1_boards %}. +デフォルトでは、Organization のメンバーはその Organization の{% data variables.projects.projects_v1_boards %}に対する書き込みアクセスを持ちます。ただし、Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者が、特定の{% data variables.projects.projects_v1_boards %}に異なる権限を設定している場合は例外です。 ## Organization のすべてのメンバーに対して標準の権限レベルを設定する {% tip %} -**Tip:** You can give an organization member higher permissions to {% data variables.projects.projects_v1_board %}. 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +**参考:** Organizationのメンバーに{% data variables.projects.projects_v1_board %}へのより高い権限を付与することができます。 詳しい情報については、「[Organization のプロジェクトボードの権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endtip %} @@ -40,6 +40,6 @@ By default, organization members have write access to their organization's {% da ## 参考リンク -- "[Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-an-individual-s-access-to-an-organization-project-board)" -- "[Managing team access to an organization {% data variables.product.prodname_project_v1 %}](/articles/managing-team-access-to-an-organization-project-board)" +- 「[Organizationの{% data variables.product.prodname_project_v1 %}への個人のアクセスの管理](/articles/managing-an-individual-s-access-to-an-organization-project-board)」 +- 「[Organizationの{% data variables.product.prodname_project_v1 %}への Team のアクセスの管理](/articles/managing-team-access-to-an-organization-project-board)」 - 「[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」 diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md index 93946c2fba..95c070f450 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing an individual’s access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can manage an individual member''s access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: '{% data variables.product.prodname_project_v1 %}への個人のアクセス管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organization が所有する{% data variables.projects.projects_v1_board %}への個々のメンバーのアクセスを管理できます。' redirect_from: - /articles/managing-an-individual-s-access-to-an-organization-project-board - /articles/managing-an-individuals-access-to-an-organization-project-board @@ -21,11 +21,11 @@ allowTitleToDifferFromFilename: true {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**ノート:** {% data reusables.project-management.cascading-permissions %} 詳しい情報については「[Organizatonの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endnote %} -## Giving an organization member access to a {% data variables.projects.projects_v1_board %} +## Organizationのメンバーへの{% data variables.projects.projects_v1_board %}に対するアクセスの付与 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -39,7 +39,7 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.add-collaborator %} {% data reusables.project-management.collaborator-permissions %} -## Changing an organization member's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのOrganizationメンバーのアクセスの変更 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} @@ -51,9 +51,9 @@ allowTitleToDifferFromFilename: true {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.collaborator-permissions %} -## Removing an organization member's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのOrganizationのメンバーのアクセスの削除 -When you remove a collaborator from a {% data variables.projects.projects_v1_board %}, they may still retain access to the board based on the permissions they have for other roles. To completely remove access to a {% data variables.projects.projects_v1_board %}, you must remove access for each role the person has. For instance, a person may have access to the {% data variables.projects.projects_v1_board %} as an organization member or team member. 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 +{% data variables.projects.projects_v1_board %}からコラボレータを削除しても、コラボレータは引き続き他のロールの権限に基づきボードにアクセスできることがあります。 {% data variables.projects.projects_v1_board %}へのアクセスを完全に削除するには、その人が持っている各ロールのアクセスを削除しなければなりません。 たとえば、ある人は{% data variables.projects.projects_v1_board %}へのアクセスをOrganizationのメンバーあるいはTeamのメンバーとして持っているかもしれません。 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md index 68240bbaa3..e48de84cea 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md @@ -1,6 +1,6 @@ --- -title: 'Managing team access to an organization {% data variables.product.prodname_project_v1 %}' -intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.' +title: 'Organizationの{% data variables.product.prodname_project_v1 %}へのTeamアクセスの管理' +intro: 'Organization のオーナーまたは{% data variables.projects.projects_v1_board %}の管理者は、Organizationが所有する{% data variables.projects.projects_v1_board %}へのアクセスをTeamに付与できます。' redirect_from: - /articles/managing-team-access-to-an-organization-project-board - /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board @@ -21,18 +21,18 @@ allowTitleToDifferFromFilename: true {% warning %} **警告:** -- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}. -- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. 詳しい情報については[Team について](/articles/about-teams)を参照してください。 +- Teamが{% data variables.projects.projects_v1_board %}への直接のアクセスを持っているなら、Teamの権限レベルを変更できます。 {% data variables.projects.projects_v1_board %}へのTeamのアクセスが親チームから継承されたものなら、{% data variables.projects.projects_v1_board %}への親チームのアクセスを変更しなければなりません。 +- 親チームへの{% data variables.projects.projects_v1_board %}へのアクセスを追加もしくは削除した場合、親チームのそれぞれの子チームも{% data variables.projects.projects_v1_board %}へのアクセスを受け取ったり失ったりします。 詳しい情報については[Team について](/articles/about-teams)を参照してください。 {% endwarning %} -## Giving a team access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのTeamのアクセスの付与 -You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}. +Team全体に{% data variables.projects.projects_v1_board %}に対する同じ権限レベルを付与できます。 {% note %} -**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)." +**ノート:** {% data reusables.project-management.cascading-permissions %} たとえば、Organization のオーナーが、ある{% data variables.projects.projects_v1_board %}に対する読み取り権限をチームに付与しており、{% data variables.projects.projects_v1_board %}の管理者がチームのメンバーいずれかに、個別のコラボレーターとしてそのボードに対する管理者権限を付与している場合、そのユーザは{% data variables.projects.projects_v1_board %}に対する管理者権限を持つことになります。 詳しい情報については「[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。 {% endnote %} @@ -47,12 +47,12 @@ You can give an entire team the same permission level to a {% data variables.pro 9. チームを追加する場合は、[**Add a team: Select team**] をクリックします。 次に、ドロップダウン メニューからチームを選択するか、追加したいチームを検索します。 ![Organization のチームのリストが表示される [Add a team] ドロップダウン メニュー](/assets/images/help/projects/add-a-team.png) 10. チーム名の隣にあるドロップダウン メニューを使って、目的の権限レベルを [**Read**]、[**Write**]、[**Admin**] から選択します。 ![[Read]、[Write]、[Admin] のオプションがあるチームの権限](/assets/images/help/projects/org-project-team-choose-permissions.png) -## Configuring a team's access to a {% data variables.projects.projects_v1_board %} +## {% data variables.projects.projects_v1_board %}へのTeamのアクセスの設定 -If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams. +{% data variables.projects.projects_v1_board %}へのTeamのアクセスが親チームから継承されたものなら、子チームのアクセスを更新するには{% data variables.projects.projects_v1_board %}への親チームのアクセスを変更しなければなりません。 {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %} 4. チームの会話の上にある {% octicon "project" aria-label="The Projects icon" %}[**Projects**] をクリックします。 ![チームの [Repositories] タブ](/assets/images/help/organizations/team-project-board-button.png) -5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**. ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png) +5. 権限レベルを変更するには、更新したい{% data variables.projects.projects_v1_board %}の右でドロップダウンを使ってください。 {% data variables.projects.projects_v1_board %}を削除するには**{% octicon "trash" aria-label="The trash icon" %}**をクリックしてください。 ![チームからプロジェクトボードを削除する [Trash] ボタン](/assets/images/help/organizations/trash-button.png) diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index ba946be185..64d37366f8 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -60,123 +60,123 @@ Organizationレベルの設定の管理に加えて、Organizationのオーナ {% endnote %} {% endif %} -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:-----:|:--------:|:-------------------------------------------------------------------:| -| リポジトリへの[個人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[Team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)、[外部のコラボレータ](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)のアクセス管理 | | | | | **X** | -| 個人または Team の割り当てリポジトリからのプル | **X** | **X** | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリのフォーク | **X** | **X** | **X** | **X** | **X** | -| 自分のコメントの編集および削除 | **X** | **X** | **X** | **X** | **X** | -| Issue のオープン | **X** | **X** | **X** | **X** | **X** | -| 自分でオープンした Issue のクローズ | **X** | **X** | **X** | **X** | **X** | -| 自分でクローズした Issue を再オープン | **X** | **X** | **X** | **X** | **X** | -| 自分に割り当てられた Issue の取得 | **X** | **X** | **X** | **X** | **X** | -| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **X** | **X** | **X** | **X** | **X** | -| プルリクエストについてのレビューのサブミット | **X** | **X** | **X** | **X** | **X** | -| 公開済みリリースの表示 | **X** | **X** | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **X** | **X** | **X** | **X** | **X** +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:------:|:--------:|:--------------------------------------------------------------------:| +| リポジトリへの[個人](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)、[Team](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)、[外部のコラボレータ](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)のアクセス管理 | | | | | **✔️** | +| 個人または Team の割り当てリポジトリからのプル | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 個人または Team の割り当てリポジトリのフォーク | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分のコメントの編集および削除 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Issue のオープン | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分でオープンした Issue のクローズ | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分でクローズした Issue を再オープン | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 自分に割り当てられた Issue の取得 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| Team の割り当てリポジトリのフォークからのプルリクエストの送信 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| プルリクエストについてのレビューのサブミット | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| 公開済みリリースの表示 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [[GitHub Actions workflow runs](/actions/automating-your-workflow-with-github-actions/managing-a-workflow-run)] の表示 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| パブリックリポジトリでのWikiの編集 | **X** | **X** | **X** | **X** | **X** | -| プライベートリポジトリのWikiの編集 | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **X** | **X** | **X** | **X** | **X** +| パブリックリポジトリでのWikiの編集 | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| プライベートリポジトリのWikiの編集 | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [悪用あるいはスパムの可能性があるコンテンツのレポート](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| ラベルの適用/却下 | | **X** | **X** | **X** | **X** | -| ラベルの作成、編集、削除 | | | **X** | **X** | **X** | -| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **X** | **X** | **X** | **X** | -| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **X** | **X** | **X** | -| マイルストーンの適用 | | **X** | **X** | **X** | **X** | -| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **X** | **X** | **X** | **X** | -| [プルリクエストのレビュー](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)の要求 | | **X** | **X** | **X** | **X** | -| [Pull Request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)のマージ | | | **X** | **X** | **X** | -| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **X** | **X** | **X** | -| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **X** | **X** | **X** | -| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **X** | **X** | **X** | -| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **X** | **X** | **X** | -| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **X** | **X** | **X** | -| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **X** | **X** | **X** | -| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| [プルリクエストをドラフトに変換する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **X** | **X** | **X** | -| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **X** | **X** | **X** | -| プルリクエストに[提案された変更を適用する](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **X** | **X** | **X** | -| [ステータスチェック](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)の作成 | | | **X** | **X** | **X** |{% ifversion fpt or ghec %} -| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **X** | **X** | **X** +| ラベルの適用/却下 | | **✔️** | **✔️** | **✔️** | **✔️** | +| ラベルの作成、編集、削除 | | | **✔️** | **✔️** | **✔️** | +| すべての Issue およびプルリクエストのクローズ、再オープン、割り当て | | **✔️** | **✔️** | **✔️** | **✔️** | +| [プルリクエストの自動マージの有効化または無効化](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) | | | **✔️** | **✔️** | **✔️** | +| マイルストーンの適用 | | **✔️** | **✔️** | **✔️** | **✔️** | +| [重複した Issue とプルリクエスト](/articles/about-duplicate-issues-and-pull-requests)のマーク付け | | **✔️** | **✔️** | **✔️** | **✔️** | +| [プルリクエストのレビュー](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)の要求 | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Pull Request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)のマージ | | | **✔️** | **✔️** | **✔️** | +| 個人または Team の割り当てリポジトリへのプッシュ (書き込み) | | | **✔️** | **✔️** | **✔️** | +| コミット、プルリクエスト、Issue についての他者によるコメントの編集と削除 | | | **✔️** | **✔️** | **✔️** | +| [他者によるコメントの非表示](/communities/moderating-comments-and-conversations/managing-disruptive-comments) | | | **✔️** | **✔️** | **✔️** | +| [会話のロック](/communities/moderating-comments-and-conversations/locking-conversations) | | | **✔️** | **✔️** | **✔️** | +| Issue の移譲 (詳細は「[他のリポジトリへ Issue を移譲する](/articles/transferring-an-issue-to-another-repository)」を参照) | | | **✔️** | **✔️** | **✔️** | +| [リポジトリに指定されたコードオーナーとしてのアクション](/articles/about-code-owners) | | | **✔️** | **✔️** | **✔️** | +| [プルリクエストのドラフトに、レビューの準備ができたことを示すマークを付ける](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [プルリクエストをドラフトに変換する](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request) | | | **✔️** | **✔️** | **✔️** | +| プルリクエストのマージ可能性に影響するレビューのサブミット | | | **✔️** | **✔️** | **✔️** | +| プルリクエストに[提案された変更を適用する](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) | | | **✔️** | **✔️** | **✔️** | +| [ステータスチェック](/pull-requests/collaborating-with-pull-requests/collaborating-on-repositories-with-code-quality-features/about-status-checks)の作成 | | | **✔️** | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [GitHub Actions ワークフロー](/actions/automating-your-workflow-with-github-actions/) の作成、編集、実行、再実行、キャンセル | | | **✔️** | **✔️** | **✔️** {% endif %} -| リリースの作成と編集 | | | **X** | **X** | **X** | -| ドラフトリリースの表示 | | | **X** | **X** | **X** | -| リポジトリの説明の編集 | | | | **X** | **X** |{% ifversion fpt or ghae or ghec %} -| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **X** | **X** | **X** | **X** | **X** | -| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **X** | **X** | **X** | -| [パッケージの削除および復元](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **X** |{% endif %} -| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **X** | **X** | -| Wiki の有効化および Wiki 編集者の制限 | | | | **X** | **X** | -| プロジェクトボードの有効化 | | | | **X** | **X** | -| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **X** | **X** | -| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **X** | **X** | -| [ブランチ保護ルールの管理](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **X** | -| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **X** | **X** | -| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **X** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} -| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの作成 | | | | **X** | **X** | -| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの削除 | | | | | **X** +| リリースの作成と編集 | | | **✔️** | **✔️** | **✔️** | +| ドラフトリリースの表示 | | | **✔️** | **✔️** | **✔️** | +| リポジトリの説明の編集 | | | | **✔️** | **✔️** |{% ifversion fpt or ghae or ghec %} +| [パッケージの表示とインストール](/packages/publishing-and-managing-packages) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [パッケージの公開](/packages/publishing-and-managing-packages/publishing-a-package) | | | **✔️** | **✔️** | **✔️** | +| [パッケージの削除および復元](/packages/learn-github-packages/deleting-and-restoring-a-package) | | | | | **✔️** |{% endif %} +| [Topics](/articles/classifying-your-repository-with-topics) の管理 | | | | **✔️** | **✔️** | +| Wiki の有効化および Wiki 編集者の制限 | | | | **✔️** | **✔️** | +| プロジェクトボードの有効化 | | | | **✔️** | **✔️** | +| [プルリクエストのマージ](/articles/configuring-pull-request-merges)の設定 | | | | **✔️** | **✔️** | +| [{% data variables.product.prodname_pages %} の公開ソース](/articles/configuring-a-publishing-source-for-github-pages)の設定 | | | | **✔️** | **✔️** | +| [ブランチ保護ルールの管理](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) | | | | | **✔️** | +| [保護されたブランチへのプッシュ](/articles/about-protected-branches) | | | | **✔️** | **✔️** | +| 保護されたブランチでのプルリクエストのマージ（レビューの承認がなくても） | | | | | **✔️** |{% ifversion fpt or ghes > 3.4 or ghae-issue-6337 or ghec %} +| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの作成 | | | | **✔️** | **✔️** | +| [タグ保護ルール](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)にマッチするタグの削除 | | | | | **✔️** {% endif %} -| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **X** | **X** |{% ifversion fpt or ghec %} -| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **X** | **X** +| [リポジトリソーシャルカードの作成と編集](/articles/customizing-your-repositorys-social-media-preview) | | | | **✔️** | **✔️** |{% ifversion fpt or ghec %} +| [リポジトリでのインタラクション](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)を制限する | | | | **✔️** | **✔️** {% endif %} -| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **X** | -| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **X** | -| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **X** | -| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **X** | -| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **X** | -| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **X** | -| リポジトリ設定の変更 | | | | | **X** | -| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **X** | -| リポジトリのデフォルトブランチ編集 | | | | | **X** | -| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **X** | -| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **X** | **X** | **X** | -| Webhookおよびデプロイキーの管理 | | | | | **X** |{% ifversion fpt or ghec %} -| [プライベートリポジトリ用のデータ利用設定を管理する](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **X** +| Issue の削除 (「[Issue を削除する](/articles/deleting-an-issue)」を参照) | | | | | **✔️** | +| [リポジトリのコードオーナーの定義](/articles/about-code-owners) | | | | | **✔️** | +| リポジトリを Team に追加する (詳細は「[Organization リポジトリへの Team のアクセスを管理する](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository#giving-a-team-access-to-a-repository)」を参照) | | | | | **✔️** | +| [外部のコラボレータのリポジトリへのアクセスの管理](/articles/adding-outside-collaborators-to-repositories-in-your-organization) | | | | | **✔️** | +| [リポジトリの可視性の変更](/articles/restricting-repository-visibility-changes-in-your-organization) | | | | | **✔️** | +| リポジトリのテンプレート化 (「[テンプレートリポジトリを作成する](/articles/creating-a-template-repository)」を参照) | | | | | **✔️** | +| リポジトリ設定の変更 | | | | | **✔️** | +| Team およびコラボレータのリポジトリへのアクセス管理 | | | | | **✔️** | +| リポジトリのデフォルトブランチ編集 | | | | | **✔️** | +| リポジトリのデフォルトブランチの名前を変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | | | **✔️** | +| リポジトリのデフォルトブランチを変更する（「[ブランチの名前を変更する](/github/administering-a-repository/renaming-a-branch)」を参照） | | | **✔️** | **✔️** | **✔️** | +| Webhookおよびデプロイキーの管理 | | | | | **✔️** |{% ifversion fpt or ghec %} +| [プライベートリポジトリ用のデータ利用設定を管理する](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository) | | | | | **✔️** {% endif %} -| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **X** | -| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **X** | -| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **X** | -| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **X** |{% ifversion fpt or ghec %} -| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **X** +| [リポジトリのフォークポリシーを管理する](/github/administering-a-repository/managing-the-forking-policy-for-your-repository) | | | | | **✔️** | +| [リポジトリの Organization への移譲](/articles/restricting-repository-creation-in-your-organization) | | | | | **✔️** | +| [リポジトリの削除または Organization 外への移譲](/articles/setting-permissions-for-deleting-or-transferring-repositories) | | | | | **✔️** | +| [リポジトリのアーカイブ](/articles/about-archiving-repositories) | | | | | **✔️** |{% ifversion fpt or ghec %} +| スポンサーボタンの表示 (「[リポジトリにスポンサーボタンを表示する](/articles/displaying-a-sponsor-button-in-your-repository)」を参照) | | | | | **✔️** {% endif %} -| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **X** |{% ifversion discussions %} -| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **X** | **X** | -| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **X** | **X** | -| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **X** | **X** | **X** | -| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **X** | **X** | **X** | **X** | -| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **X** | **X** | **X** | **X** | **X** | -| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **X** | | **X** | **X** |{% endif %}{% ifversion fpt or ghec %} -| [codespaces](/codespaces/about-codespaces)の作成 | | | **X** | **X** | **X** +| JiraやZendeskなどの外部リソースに対する自動リンク参照の作成 (「[外部リソースを参照する自動リンクの設定](/articles/configuring-autolinks-to-reference-external-resources)」を参照)。 | | | | | **✔️** |{% ifversion discussions %} +| リポジトリの [{% data variables.product.prodname_discussions %} の有効化](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository) | | | | **✔️** | **✔️** | +| {% data variables.product.prodname_discussions %} の[カテゴリの作成および編集](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions) | | | | **✔️** | **✔️** | +| [ディスカッションを別のカテゴリに移動する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| 新しいリポジトリに[ディスカッションを転送する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [ピン止めされたディスカッションを管理する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [Issue をまとめてディスカッションに変換する](/discussions/managing-discussions-for-your-community/managing-discussions) | | | **✔️** | **✔️** | **✔️** | +| [ディスカッションのロックとロック解除](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [Issue を個別にディスカッションに変換する](/discussions/managing-discussions-for-your-community/moderating-discussions) | | **✔️** | **✔️** | **✔️** | **✔️** | +| [新しいディスカッションを作成し、既存のディスカッションにコメントする](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [ディスカッションの削除](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion) | | **✔️** | | **✔️** | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [codespaces](/codespaces/about-codespaces)の作成 | | | **✔️** | **✔️** | **✔️** {% endif %} ### セキュリティ機能のためのアクセス要件 このセクションでは、{% data variables.product.prodname_advanced_security %}の機能のようなセキュリティ機能に必要なアクセス権を知ることができます。 -| リポジトリアクション | Read | Triage | Write | Maintain | Admin | -|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:| -| リポジトリでの[安全ではない依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **X** | -| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% ifversion ghes or ghae or ghec %} +| リポジトリアクション | Read | Triage | Write | Maintain | Admin | +|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:------:|:------:|:-------------------------------------------------------:|:-------------------------------------------------------:|:--------------------------------------------------------------------------------------------------:| +| リポジトリでの[安全ではない依存関係に対する{% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)を受信 | | | | | **✔️** | +| [{% data variables.product.prodname_dependabot_alerts %} を閉じる](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} -| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [セキュリティアラートを受信する追加のユーザまたはTeamの指定](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} +| [セキュリティアドバイザリ](/code-security/security-advisories/about-github-security-advisories)の作成 | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} | -| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %} +| {% data variables.product.prodname_GH_advanced_security %}の機能へのアクセス管理（「[Organizationのセキュリティと分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」参照） | | | | | **✔️** |{% endif %}{% ifversion fpt or ghec %} | -| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X** +| プライベートリポジトリの[依存関係グラフの有効化](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| [依存関係のレビューを表示する](/code-security/supply-chain-security/about-dependency-review) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** {% endif %} -| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** | -| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** | -| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% ifversion ghes or ghae or ghec %} +| [プルリクエストの {% data variables.product.prodname_code_scanning %} アラートを表示する](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **✔️** | **✔️** | **✔️** | **✔️** | **✔️** | +| [{% data variables.product.prodname_code_scanning %} アラートを一覧表示、却下、削除します](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **✔️** | **✔️** | **✔️** | +| [リポジトリの {% data variables.product.prodname_secret_scanning %} アラートを表示する](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% ifversion ghes or ghae or ghec %} | -| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}[1]{% endif %} | **X**{% ifversion not ghae %}[1]{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} -| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** +| [{% data variables.product.prodname_secret_scanning %} アラートを解決、取り消し、再オープンする](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️**{% ifversion not ghae %}[1]{% endif %} | **✔️** |{% endif %}{% ifversion ghes or ghae or ghec %} +| リポジトリで [{% data variables.product.prodname_secret_scanning %} アラートを受信する追加の人または Team を指定する](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **✔️** {% endif %} [1] リポジトリの作者とメンテナは、自分のコミットのアラート情報のみを表示できます。 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md index 64a9a3cff9..5274dffcd6 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/allowing-project-visibility-changes-in-your-organization.md @@ -1,5 +1,5 @@ --- -title: Allowing project visibility changes in your organization +title: Organizationでのプロジェクトの可視性の変更の許可 intro: Organization owners can allow members with admin permissions to adjust the visibility of projects in their organization. versions: feature: projects-v2 diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md index bc4e39f1ac..276b444e49 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/disabling-insights-for-projects-in-your-organization.md @@ -17,7 +17,7 @@ After you disable insights for projects in your organization, it won't be possib {% data reusables.profile.org_settings %} 1. In the sidebar, click **{% octicon "sliders" aria-label="The sliders icon" %} Features**. ![Screenshot showing features menu item](/assets/images/help/projects-v2/features-org-menu.png) 1. Under "Insights", deselect **Enable Insights for the organization**. ![Screenshot showing Enable Insights for the organization checkbox](/assets/images/help/projects-v2/disable-insights-checkbox.png) -1. [**Save**] をクリックします。 ![Screenshot showing save button](/assets/images/help/projects-v2/disable-insights-save.png) +1. [**Save**] をクリックします。 ![保存ボタンを表示しているスクリーンショット](/assets/images/help/projects-v2/disable-insights-save.png) ## 参考リンク diff --git a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md index 8483bb41ab..9dde67b4b6 100644 --- a/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md +++ b/translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md @@ -12,14 +12,12 @@ topics: shortTitle: SAML SSOを使うIAM --- -{% data reusables.enterprise-accounts.emu-saml-note %} +{% data reusables.saml.ghec-only %} ## SAML SSO について {% data reusables.saml.dotcom-saml-explanation %} -{% data reusables.saml.ghec-only %} - {% data reusables.saml.saml-accounts %} Organization のオーナーは、個々の Organization に SAML SSO を適用できます。または、Enterprise のオーナーは、Enterprise アカウント内のすべての Organization に SAML SSO を適用できます。 詳しい情報については、「[Enterprise 向けのSAML シングルサインオンを設定する](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md index 765d90a90f..d270178440 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -126,6 +126,7 @@ In addition, your use of {% data variables.product.prodname_pages %} is subject {% ifversion fpt or ghec %} - {% data variables.product.prodname_pages %} sites have a *soft* bandwidth limit of 100 GB per month. - {% data variables.product.prodname_pages %} sites have a *soft* limit of 10 builds per hour.{% ifversion pages-custom-workflow %} This limit does not apply if you build and publish your site with a custom {% data variables.product.prodname_actions %} workflow {% endif %} + - In order to provide consistent quality of service for all {% data variables.product.prodname_pages %} sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of {% data variables.product.prodname_pages %}. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of `429`, along with an informative HTML body. If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from {% data variables.contact.contact_support %} suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other {% data variables.product.prodname_dotcom %} features such as releases, or moving to a different hosting service that might better fit your needs. diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md index 2c5cf2886c..1a2fea66fe 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md @@ -25,6 +25,7 @@ You can create a branch in different ways on {% data variables.product.product_n {% endnote %} +{% ifversion create-branch-from-overview %} ### Creating a branch via the branches overview {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.navigate-to-branches %} @@ -32,16 +33,19 @@ You can create a branch in different ways on {% data variables.product.product_n 2. In the dialog box, enter the branch name and optionally change the branch source. If the repository is a fork, you also have the option to select the upstream repository as the branch source. ![Screenshot of branch creation modal for a fork with branch source emphasized](/assets/images/help/branches/branch-creation-popup-branch-source.png) 3. Click **Create branch**. ![Screenshot of branch creation modal with create branch button emphasized](/assets/images/help/branches/branch-creation-popup-button.png) +{% endif %} ### Creating a branch using the branch dropdown {% data reusables.repositories.navigate-to-repo %} 1. Optionally, if you want to create the new branch from a branch other than the default branch of the repository, click {% octicon "git-branch" aria-label="The branch icon" %} **Branches** then choose another branch. ![概要ページのブランチリンク](/assets/images/help/branches/branches-overview-link.png) 1. ブランチセレクタメニューをクリックします。 ![ブランチセレクタメニュー](/assets/images/help/branch/branch-selection-dropdown.png) 1. 新しいブランチに、一意の名前を入力して、[**Create branch**] を選択します。 ![ブランチ作成のテキストボックス](/assets/images/help/branch/branch-creation-text-box.png) + {% ifversion fpt or ghec or ghes > 3.4 %} ### Issueのためのブランチの作成 直接Issueのページから作業のためのブランチを作成し、すぐに作業を開始できます。 For more information, see "[Creating a branch to work on an issue](/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue)". {% endif %} + ## ブランチの削除 {% data reusables.pull_requests.automatically-delete-branches %} diff --git a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md index 94eb059bfb..a719f4b0cb 100644 --- a/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md +++ b/translations/ja-JP/content/rest/overview/resources-in-the-rest-api.md @@ -226,7 +226,7 @@ REST API を介して `node_id` を検索し、それらを GraphQL 操作で使 ## HTTP メソッド -可能な場合、{% data variables.product.product_name %} REST APIはそれぞれのアクションに対して適切なHTTPメソッドを使うように努めます。 +可能な場合、{% data variables.product.product_name %} REST APIはそれぞれのアクションに対して適切なHTTPメソッドを使うように努めます。 Note that HTTP verbs are case-sensitive. | メソッド | 説明 | | -------- | ----------------------------------------------------------------------------------------------------------------------------- | diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md index 750c7d68df..f269b7fbf7 100644 --- a/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-for-repositories.md @@ -91,7 +91,7 @@ With the `in` qualifier you can restrict your search to the repository name, rep | 修飾子 | サンプル | | ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stars:n | [**stars:500**](https://github.com/search?utf8=%E2%9C%93&q=stars%3A500&type=Repositories) は、Star がちょうど 500 のリポジトリにマッチします。 | -| | [**stars:10..20**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) は、1000 KB 未満で、Star が 10 から 20 のリポジトリにマッチします。 | +| | [**stars:10..20 size:<1000**](https://github.com/search?q=stars%3A10..20+size%3A%3C1000&type=Repositories) matches repositories 10 to 20 stars, that are smaller than 1000 KB. | | | [**stars:>=500 fork:true language:php**](https://github.com/search?q=stars%3A%3E%3D500+fork%3Atrue+language%3Aphp&type=Repositories) は、PHP 形式のフォークされたリポジトリを含め Star が 500 以上のリポジトリにマッチします。 | ## リポジトリの作成時期や最終更新時期で検索 diff --git a/translations/ja-JP/data/features/create-branch-from-overview.yml b/translations/ja-JP/data/features/create-branch-from-overview.yml new file mode 100644 index 0000000000..a51e624c41 --- /dev/null +++ b/translations/ja-JP/data/features/create-branch-from-overview.yml @@ -0,0 +1,5 @@ +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-6670' diff --git a/translations/ja-JP/data/features/security-overview-displayed-alerts.yml b/translations/ja-JP/data/features/security-overview-displayed-alerts.yml new file mode 100644 index 0000000000..da84d07e41 --- /dev/null +++ b/translations/ja-JP/data/features/security-overview-displayed-alerts.yml @@ -0,0 +1,6 @@ +#Reference: #7114. +#Documentation for security overview availability to all enterprise accounts. +versions: + ghec: '*' + ghes: '>=3.7' + ghae: 'issue-7114' diff --git a/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml b/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml new file mode 100644 index 0000000000..0eae9cda9c --- /dev/null +++ b/translations/ja-JP/data/features/totp-and-mobile-sudo-challenge.yml @@ -0,0 +1,5 @@ +#TOTP and mobile challenge for sudo mode prompt. +versions: + fpt: '*' + ghec: '*' + ghes: '>= 3.7' diff --git a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 10abd35353..fc8477114a 100644 --- a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -154,6 +154,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -168,13 +175,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: RemovePullRequestFromMergeQueueInput.branch description: '`branch`は削除されます。' diff --git a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml index f7cdd42018..7b4b915eef 100644 --- a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -574,6 +574,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -588,13 +595,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: ProjectNextItem.content description: '`content`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' diff --git a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml index f7cdd42018..7b4b915eef 100644 --- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml @@ -574,6 +574,13 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar + - + location: ProjectNextFieldType.TASKS + description: '`TASKS` will be removed. Follow the ProjectV2 guide at https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/, to find a suitable replacement.' + reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' + date: '2022-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: lukewar - location: ProjectNextFieldType.TEXT description: '`TEXT`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' @@ -588,13 +595,6 @@ upcoming_changes: date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: lukewar - - - location: ProjectNextFieldType.TRACKS - description: '`TRACKS`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' - reason: '`ProjectNext`は、より多機能な`ProjectV2`に置き換えられて非推奨になりました。' - date: '2022-10-01T00:00:00+00:00' - criticality: 破壊的 - owner: lukewar - location: ProjectNextItem.content description: '`content`は削除されます。適切な置き換えを見つけるには、https://github.blog/changelog/2022-06-23-the-new-github-issues-june-23rd-update/ にあるProjectV2ガイドに従ってください。' diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md index b4d7a50a1d..aa6186a5bb 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md +++ b/translations/ja-JP/data/reusables/actions/jobs/section-choosing-the-runner-for-a-job.md @@ -6,7 +6,7 @@ ### {% data variables.product.prodname_dotcom %}ホストランナーの選択 -{% data variables.product.prodname_dotcom %}ホストランナーを使う場合、それぞれのジョブは`runs-on`で指定された仮想環境の新しいインスタンスで実行されます。 +If you use a {% data variables.product.prodname_dotcom %}-hosted runner, each job runs in a fresh instance of a runner image specified by `runs-on`. 利用可能な{% data variables.product.prodname_dotcom %}ホストランナーの種類は以下のとおりです。 @@ -18,7 +18,7 @@ runs-on: ubuntu-latest ``` -詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーの仮想環境](/github/automating-your-workflow-with-github-actions/virtual-environments-for-github-hosted-runners)」を参照してください。 +詳しい情報については「[{% data variables.product.prodname_dotcom %}ホストランナーについて](/actions/using-github-hosted-runners/about-github-hosted-runners)」を参照してください。 {% endif %} {% ifversion fpt or ghec or ghes %} diff --git a/translations/ja-JP/data/reusables/actions/macos-runner-preview.md b/translations/ja-JP/data/reusables/actions/macos-runner-preview.md index b96f447329..c9b93aecbe 100644 --- a/translations/ja-JP/data/reusables/actions/macos-runner-preview.md +++ b/translations/ja-JP/data/reusables/actions/macos-runner-preview.md @@ -1 +1 @@ -macos-latestのYAMLワークフローのラベルは、現在macOS 10.15の仮想環境を使用します。 +The macos-latest YAML workflow label currently uses the macOS 10.15 runner image. diff --git a/translations/ja-JP/data/reusables/actions/pure-javascript.md b/translations/ja-JP/data/reusables/actions/pure-javascript.md index db4eec7753..933fe00c03 100644 --- a/translations/ja-JP/data/reusables/actions/pure-javascript.md +++ b/translations/ja-JP/data/reusables/actions/pure-javascript.md @@ -1 +1 @@ -JavaScriptのアクションがGitHubがホストするすべてのランナー（Ubuntu、Windows、macOS）と互換性があることを保証するためには、作成するパッケージ化されたJacScriptのコードは純粋なJavaScriptであり、他のバイナリに依存していてはなりません。 JavaScriptのアクションはランナー上で直接実行され、仮想環境内にすでに存在するバイナリを利用します。 +JavaScriptのアクションがGitHubがホストするすべてのランナー（Ubuntu、Windows、macOS）と互換性があることを保証するためには、作成するパッケージ化されたJacScriptのコードは純粋なJavaScriptであり、他のバイナリに依存していてはなりません。 JavaScript actions run directly on the runner and use binaries that already exist in the runner image. diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md index 68b601bbc8..8f3ec2e695 100644 --- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md +++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md @@ -1,7 +1,7 @@ - + @@ -92,7 +92,7 @@ macOS Catalina 10.15 [deprecated] {% note %} -**ノート:** `-latest`の仮想環境は、{% data variables.product.prodname_dotcom %}が提供している最新の安定版イメージであり、オペレーティングシステムのベンダーから提供されているオペレーティングシステムの最新バージョンではないことがあります。 +**Note:** The `-latest` runner images are the latest stable images that {% data variables.product.prodname_dotcom %} provides, and might not be the most recent version of the operating system available from the operating system vendor. {% endnote %} diff --git a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md index 6ad33181dd..fa6ffee006 100644 --- a/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md +++ b/translations/ja-JP/data/reusables/codespaces/creating-a-codespace-in-vscode.md @@ -19,7 +19,11 @@ ![新しい {% data variables.product.prodname_codespaces %} を作成するためのブランチを検索する](/assets/images/help/codespaces/choose-branch-vscode.png) -5. 使用したいマシンタイプをクリックしてください。 +5. If prompted to choose a dev container configuration file, choose a file from the list. + + ![Choosing a dev container configuration file for {% data variables.product.prodname_codespaces %}](/assets/images/help/codespaces/choose-dev-container-vscode.png) + +6. 使用したいマシンタイプをクリックしてください。 ![新しい {% data variables.product.prodname_codespaces %} のインスタンスタイプ](/assets/images/help/codespaces/choose-sku-vscode.png) diff --git a/translations/ja-JP/data/reusables/gated-features/advanced-security.md b/translations/ja-JP/data/reusables/gated-features/advanced-security.md deleted file mode 100644 index a8a075f2fe..0000000000 --- a/translations/ja-JP/data/reusables/gated-features/advanced-security.md +++ /dev/null @@ -1 +0,0 @@ -{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features included in {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." diff --git a/translations/ja-JP/data/reusables/gated-features/ghas.md b/translations/ja-JP/data/reusables/gated-features/ghas.md index 0f74920694..b6362ec2f9 100644 --- a/translations/ja-JP/data/reusables/gated-features/ghas.md +++ b/translations/ja-JP/data/reusables/gated-features/ghas.md @@ -1 +1 @@ -{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %} 3.0 or higher.{% ifversion fpt or ghec %} {% data variables.product.prodname_GH_advanced_security %} is also included in all public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} +{% data variables.product.prodname_GH_advanced_security %} is available for enterprise accounts on {% data variables.product.prodname_ghe_cloud %}{% ifversion ghae %}, {% data variables.product.prodname_ghe_managed %},{% endif %} and {% data variables.product.prodname_ghe_server %}.{% ifversion fpt or ghec %} Some features of {% data variables.product.prodname_GH_advanced_security %} are also available for public repositories on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About GitHub's products](/github/getting-started-with-github/githubs-products)."{% else %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/security-overview.md b/translations/ja-JP/data/reusables/gated-features/security-overview.md index d3f9f4b3ce..7a4f00d780 100644 --- a/translations/ja-JP/data/reusables/gated-features/security-overview.md +++ b/translations/ja-JP/data/reusables/gated-features/security-overview.md @@ -1,6 +1,9 @@ -{% ifversion ghae %} -{% data variables.product.prodname_GH_advanced_security %}のライセンスを持っているなら、Organizationのセキュリティの概要が利用できます。これは、ベータリリースの間は無料です。 {% data reusables.advanced-security.more-info-ghas %} -{% elsif ghec or ghes %} +{% ifversion fpt %} +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %}. 詳しい情報については「[GitHubの製品](/articles/githubs-products)」を参照してください。 +{% elsif security-overview-displayed-alerts %} +All organizations and enterprises have a security overview. If you use {% data variables.product.prodname_GH_advanced_security %}{% ifversion ghae %}, which is free during the beta release,{% endif %} you will see additional information. {% data reusables.advanced-security.more-info-ghas %} +{% elsif ghes < 3.7 %} The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} -{% elsif fpt %} -The security overview is available for organizations that use {% data variables.product.prodname_enterprise %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}について](/get-started/learning-about-github/about-github-advanced-security)」を参照してください。 {% endif %} +{% elsif ghae %} +A security overview for your enterprise and for organizations is available if you use {% data variables.product.prodname_GH_advanced_security %}, which is free during the beta release. {% data reusables.advanced-security.more-info-ghas %} +{% endif %} diff --git a/translations/ja-JP/data/reusables/projects/add-draft-issue.md b/translations/ja-JP/data/reusables/projects/add-draft-issue.md index ce0fd22442..1ab213586c 100644 --- a/translations/ja-JP/data/reusables/projects/add-draft-issue.md +++ b/translations/ja-JP/data/reusables/projects/add-draft-issue.md @@ -1,3 +1,3 @@ {% data reusables.projects.add-item-bottom-row %} -1. アイデアを入力し、**Enter**を押してください。 ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/add-draft-issue.png) +1. アイデアを入力し、**Enter**を押してください。 ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/add-draft-issue.png) 1. 本文のテキストを追加するには、ドラフトIssueのタイトルをクリックしてください。 表示されるMarkdownの入力ボックスに、ドラフトIssueの本文のテキストを入力し、**Save（保存）**をクリックしてください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md index f0ad9645a0..ddae60160c 100644 --- a/translations/ja-JP/data/reusables/projects/add-item-via-paste.md +++ b/translations/ja-JP/data/reusables/projects/add-item-via-paste.md @@ -1,3 +1,3 @@ {% data reusables.projects.add-item-bottom-row %} -1. Paste the URL of the issue or pull request. ![Screenshot showing pasting an issue URL to add it to the project](/assets/images/help/projects-v2/paste-url-to-add.png) +1. Paste the URL of the issue or pull request. ![IssueのURLを貼り付けてプロジェクトに追加しているスクリーンショット](/assets/images/help/projects-v2/paste-url-to-add.png) 3. To add the issue or pull request, press Return. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md index 24ad34d005..3a854d7655 100644 --- a/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md +++ b/translations/ja-JP/data/reusables/projects/enable-basic-workflow.md @@ -1,7 +1,7 @@ 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) -1. In the menu, click {% octicon "workflow" aria-label="The workflow icon" %} **Workflows**. ![Screenshot showing the 'Workflows' menu item](/assets/images/help/projects-v2/workflows-menu-item.png) -1. Under **Default workflows**, click on the workflow that you want to edit. ![Screenshot showing default workflows](/assets/images/help/projects-v2/default-workflows.png) -1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. ![Screenshot showing the "when" configuration for a workflow](/assets/images/help/projects-v2/workflow-when.png) -1. Next to **Set**, choose the value that you want to set the status to. ![Screenshot showing the "set" configuration for a workflow](/assets/images/help/projects-v2/workflow-set.png) -1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. ![Screenshot showing the "enable" control for a workflow](/assets/images/help/projects-v2/workflow-enable.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) +1. メニューで{% octicon "workflow" aria-label="The workflow icon" %} **Workflows（ワークフロー）**をクリックしてください。 !['Workflows'メニューアイテムを表示しているスクリーンショット](/assets/images/help/projects-v2/workflows-menu-item.png) +1. Under **Default workflows**, click on the workflow that you want to edit. ![デフォルトのワークフローを表示しているスクリーンショット](/assets/images/help/projects-v2/default-workflows.png) +1. If the workflow can apply to both issues and pull requests, next to **When**, check the item type(s) that you want to act on. ![ワークフローの"when"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-when.png) +1. Next to **Set**, choose the value that you want to set the status to. ![ワークフローの"set"設定を表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-set.png) +1. If the workflow is disabled, click the toggle next to **Disabled** to enable the workflow. ![ワークフローの"enable"コントロールを表示しているスクリーンショット](/assets/images/help/projects-v2/workflow-enable.png) diff --git a/translations/ja-JP/data/reusables/projects/project-settings.md b/translations/ja-JP/data/reusables/projects/project-settings.md index 77fff8c531..68ebdfd368 100644 --- a/translations/ja-JP/data/reusables/projects/project-settings.md +++ b/translations/ja-JP/data/reusables/projects/project-settings.md @@ -1,3 +1,3 @@ 1. プロジェクトにアクセスします。 -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) 2. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) diff --git a/translations/ja-JP/data/reusables/projects/reopen-a-project.md b/translations/ja-JP/data/reusables/projects/reopen-a-project.md index 9be346cda1..bef6c7ee87 100644 --- a/translations/ja-JP/data/reusables/projects/reopen-a-project.md +++ b/translations/ja-JP/data/reusables/projects/reopen-a-project.md @@ -1,6 +1,6 @@ 1. Click the **Projects** tab. ![プロジェクトのクローズボタンが表示されているスクリーンショット](/assets/images/help/issues/projects-profile-tab.png) 1. To show closed projects, click **Closed**. ![プロジェクトのクローズボタンが表示されているスクリーンショット](/assets/images/help/issues/closed-projects-tab.png) 1. Click the project you want to reopen. -1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. ![Screenshot showing the menu icon](/assets/images/help/projects-v2/open-menu.png) +1. 右上で{% octicon "kebab-horizontal" aria-label="The menu icon" %}をクリックしてメニューを開いてください。 ![メニューアイコンを表示しているスクリーンショット](/assets/images/help/projects-v2/open-menu.png) 1. In the menu, click {% octicon "gear" aria-label="The gear icon" %} **Settings** to access the project settings. ![Screenshot showing the 'Settings' menu item](/assets/images/help/projects-v2/settings-menu-item.png) 1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png) diff --git a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md index 1193514f50..d8413a8725 100644 --- a/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md +++ b/translations/ja-JP/data/reusables/saml/dotcom-saml-explanation.md @@ -1 +1 @@ -SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. +SAML single sign-on (SSO) gives organization owners and enterprise owners using {% data variables.product.product_name %} a way to control and secure access to organization resources like repositories, issues, and pull requests. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md index ffab0f818a..cc15ec0c4e 100644 --- a/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md +++ b/translations/ja-JP/data/reusables/saml/outside-collaborators-exemption.md @@ -1,5 +1,8 @@ {% note %} -**Note:** 外部のコラボレータは、SAML SSOを使っているOrganization内のリソースにアクセスするために、IdPでの認証を受ける必要はありません。 For more information on outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)." +**ノート:** + +- SAML authentication is not required for organization members to perform read operations such as viewing, cloning, and forking of public resources. +- SAML authentication is not required for outside collaborators. 外部コラボレータに関する詳しい情報については「[Organization内のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)」を参照してください。 {% endnote %} diff --git a/translations/ja-JP/data/reusables/saml/saml-accounts.md b/translations/ja-JP/data/reusables/saml/saml-accounts.md index cc2788744f..7a9dbdd87a 100644 --- a/translations/ja-JP/data/reusables/saml/saml-accounts.md +++ b/translations/ja-JP/data/reusables/saml/saml-accounts.md @@ -1,7 +1,7 @@ -If you configure SAML SSO, members of your organization will continue to log into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization that uses SAML SSO, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. 認証に成功すると、IdP はメンバーを {% data variables.product.prodname_dotcom %} にリダイレクトして戻し、そこでメンバーは Organization のリソースにアクセスできます。 +If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}. When a member accesses non-public resources within your organization, {% data variables.product.prodname_dotcom %} redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to {% data variables.product.prodname_dotcom %}. 詳しい情報については「[SAML シングルサインオンでの認証について](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)」を参照してください。 {% note %} -**Note:** Organization members can perform read operations such as viewing, cloning, and forking on public resources owned by your organization even without a valid SAML session. +**Note:** SAML SSO does not replace the normal sign-in process for {% data variables.product.prodname_dotcom %}. Unless you use {% data variables.product.prodname_emus %}, members will continue to sign into their personal accounts on {% data variables.product.prodname_dotcom_the_website %}, and each personal account will be linked to an external identity in your IdP. -{% endnote %} +{% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md new file mode 100644 index 0000000000..7d642c7fda --- /dev/null +++ b/translations/ja-JP/data/reusables/security-overview/information-varies-GHAS.md @@ -0,0 +1,3 @@ +{% ifversion security-overview-displayed-alerts %} +The information shown in the security overview will vary according to your access to repositories, and on whether {% data variables.product.prodname_GH_advanced_security %} is used by those repositories. +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md b/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md index f76378972a..ec184765fe 100644 --- a/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md +++ b/translations/ja-JP/data/reusables/user-settings/sudo-mode-popup.md @@ -1 +1,3 @@ -1. {% data variables.product.product_name %} パスワードの確認を促された場合は、確認します。 ![sudo モードダイアログ](/assets/images/help/settings/sudo_mode_popup.png) +{%- ifversion fpt or ghec or ghes %} +1. If prompted, confirm access to your account on {% data variables.product.product_name %}. For more information, see "[Sudo mode](/authentication/keeping-your-account-and-data-secure/sudo-mode)." +{%- endif %} diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index af5bcfc559..985c0c3891 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -175,6 +175,7 @@ translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-setti translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags translations/ja-JP/content/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards.md,broken liquid tags +translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags translations/ja-JP/content/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository.md,broken liquid tags translations/ja-JP/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags translations/ja-JP/content/organizations/collaborating-with-your-team/about-team-discussions.md,Listed in localization-support#489 From f2b9e04687d58d5c064844d4deb00b499e5ebc9c Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Wed, 10 Aug 2022 03:18:24 +0000 Subject: [PATCH 41/41] update search indexes --- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.6-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 80 files changed, 160 insertions(+), 160 deletions(-) diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index 813952a00c..900f7c5fb5 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bd3054b030ec008d7df09049fda548417ebfc79686fcaf4befc17d540ab2e791 -size 794385 +oid sha256:4e05624ee8f6ebb844cab490ec7224f318787657646f028d1e039cf48622ada9 +size 794279 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 90b3918e8e..c7374cd8f8 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:15ec3a3958adeb3eac5ef14ed30c4a532c0a8815b9603c74f129dd7b3f0f7a90 -size 1636346 +oid sha256:c108d9ec444b901e34178d2597c71b1810edf2fbb1930d7e8c655d009037c95e +size 1636274 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 1c30cebb16..3d5e1e8977 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad2bcd6de9db27fb054dd5f3f1b26a65dd0fdb7b47b96bfd83515c6d3a5415e8 -size 1089379 +oid sha256:c446f17019a5a5e3737fe0b930902560c4bf9051aacd8d1250f00204e046bb03 +size 1089436 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 5803c54f5e..64ffbd88e1 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:84aeab8edea2e3fe815a777bdafc2dd2158371cfd5b0e317976011e7869b13eb -size 4415857 +oid sha256:44f8e1e4ffda02c497ebda37fa9e7a7159324d239971ca6aa55ce2ee7ea03cf1 +size 4417085 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index fa6e31e7ef..655f65db77 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0b1f8ba4623312a7d09c576668f8c475f9c3c5a56dbf8ecc3ff6d472a3cd9223 -size 733865 +oid sha256:816f32b442b95fa5f73375cedae5a03b30837835c9ac7b46ec6ae58fd0d9bff1 +size 733806 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index a49027f657..b8b1edd020 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:502f72c288478f2dbb70ce57605a22b9966ad4834f37ce35d65e339768c852cc -size 3130975 +oid sha256:2092a02af4eb6e09cc28d958d6308e04c8078fa9e87b73817d9d4f2e3186d85d +size 3130764 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index ef80f9a96b..6a7a8425db 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:52af056bbad9cf34d8aadccbf4553721a8937ad5a35d8047de59761d398fd57e -size 808750 +oid sha256:18d3e7b6402f3e943b3a042d9a2d96efc21aed1067da7da41b0a4e3c9e19a3b4 +size 807913 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index 997d975611..6a94ef0a74 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:74f81ca5149c1001af580a8d70759bf7f6c2b02709d66eacfdbbc9d0cafd7001 -size 4448046 +oid sha256:bd1330a276b33d01042a577c763981d7bfefb290675e5744fa1786b236a44d4d +size 4445432 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index df5213e560..9562b852e5 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb33f9191102e91f865baaad113c5760fca052da08de0b9124da24bef94a7922 -size 722361 +oid sha256:c9ce040190706cd1721a6386113d8b81db477b1f723f5ff7c02458e04f7b2c16 +size 722246 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index fe97569367..2c7e7ad22c 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:503724e7a4f7b07880bf773107efa5d0dca89f905ab132924fc51a2662950ef7 -size 3028450 +oid sha256:23f6a7f6f41697cccb8a0b113a4acb009a5f5436713f8a2148d0c847ad41e5ec +size 3027533 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 95f06c6adc..b02251de31 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8deea3941494e7ff55bf48500a179d717037ff6128975b43ee4e7f675551656e -size 819578 +oid sha256:5bd8c26704036bae59c19d126d26b5a4f348980fcc6573e08557277a2235ee3e +size 819696 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 673458847b..496b45f971 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:75ac97bf12fe195bcf59b2251b9b50ae1b3f86bdabe93d60a5e65b0ce380f0ae -size 1684325 +oid sha256:18db234bc0828dffca4bf08cc90fb612b344ad9d1dee86cb6c0da35e523c9e65 +size 1684323 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 68e493c216..5f9abc41d4 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7e801da386fb91c7578d33566732a7da4abbfbaf034b1987aeb0dfeba22567a4 -size 1124613 +oid sha256:c3a174d10c12a55472e4903bd0e29c88ce24af5f15c61bf35a79a118309b24c2 +size 1124343 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 6f855def6f..66061e3bc7 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:531bb089ce86db9302b415f3ed219a61a5f6e3b54f46771f491eabad42f14436 -size 4521947 +oid sha256:ac95cec5e119fa56de3dcd8125da659d8467d25641667686fe78a07f35764460 +size 4521313 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index ad33505b41..21dd59a9fe 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f3ac4348968f7bd55349a3e4032226d83f6732aa0b9359d7a5faf0db09502d7e -size 754937 +oid sha256:d6e9fe363564ae34936abd64a71032abd12ffd92b2f39e3f7079fec7c406a627 +size 755013 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 96a7e34022..c5e0038aeb 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:540eff3744a4ddbe77cfc07777921f4ceae6e609fbccae109d5465198a46b7b7 -size 3217380 +oid sha256:b6ec83391ecb80d65bcb0f3f38fd02e4d554dd656fea851afc31595b25bb10ef +size 3217548 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 2a92cc048b..cdc8d0e982 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:19de45fb9362fd481f0a3c6bcf98c6f2152df95bfbc431075f02746b1c3b22e2 -size 834182 +oid sha256:88951bf1586fc18f70efc85b5b443f3a056e4672308a047cbdd20ca8069b5870 +size 833709 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index 6a4b5526b3..5302111d45 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2f428cc5ed39a4ffc5f827060360aa0d63cc4bcac45c75ab07f6578399c4dff2 -size 4583688 +oid sha256:b85a619b5fde2151567a9a7374c7ee6d7e67b17edec21d14add2dcc563ee1521 +size 4581817 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index e5dc1178f0..ae80c06630 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:aef2924d191ff717ff27b80ffeba8c5dc34deb1e33bf0eddf1ee3ad6041c81ad -size 743853 +oid sha256:335e583dc343fdbd43b0cf373e954df54370ff685d42bdcb5dcb4ee7ca47938a +size 743782 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index e88fd4ad53..ffe7f9328b 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:77cc1df2bc33d36c054f82cb365ebca6569857d735e7e16fc630302eee485861 -size 3113254 +oid sha256:d9ec27f299196c50f4059172bc54cb248fc0056380c031d4b813cfb52cc5cfc7 +size 3113575 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 3fa19ba4a7..c90d8e5c58 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f2a240e2d1a8229923aadd9e4f6603386b8e235c9b585e4dea3159215c2dc3ea -size 822193 +oid sha256:23b05992b823957207665db965adcc7eef5eed99e564d37f48b4aa3454bf6a05 +size 822177 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index bcbf04e63c..51f3c0315f 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7aa0b3e6687ed56ede3abf08636360f468e496856312be6eb98225821fd35f57 -size 1699288 +oid sha256:d27f6b397a434082a0a14971b22f1b5867fdc2459722ed63c34f21222faae1b5 +size 1699319 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index 3a64b79a2a..581d461e54 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:81c80033e901b97ddb1e847327aeb0857b05e90742cb20050a0dd9d6d90f1d9f -size 1135570 +oid sha256:2de84b5e7ebd3a5007b825630e2f34e1d40748ac13862556d94f846306583197 +size 1135180 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index cdaa99a3a6..f6f12cfa93 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:086de113f35f54ca6a996e7e0623235e7a03d370f10bbe4bbdd12348675fc3e2 -size 4577573 +oid sha256:5365f5e01a654d1475c24d05f84e69d3c706711bf576d24fc94853e97c8a586d +size 4578320 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index ea1236f741..615bd6e4eb 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:96bbbc0ac2bcac52a4233b35e2152e702573229657b4f45dc17a299f5e4c8759 -size 759341 +oid sha256:5e604fe693e307708146108a865c5654bf3d328f9351b63d9b75b1ab36a78686 +size 759350 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index ec358b0c85..2c1f055cba 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:101c5765e9f0693aaf648528118292a03fdb482c822ad384c77073fc868c3f76 -size 3239901 +oid sha256:e0d3f4a89a5184f9a496aa8fe82df7d74103a6aeb7788e71642ee4b0ff90b574 +size 3239562 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index 7968167619..1ef52c03db 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:72b8e188075b52f2a774441b43d3c34aa50e073dffe84faeec22688453442f8c -size 837643 +oid sha256:64e4f6a3e6bb96e59f8ade00bc05ec6d06bf836941686b740d6e4eb57792b8cb +size 836633 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 3f6562e41f..78da0f5c54 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4645621391ac4966edf0cf6375b3fdffe1d4ab5fec7fd0309137e46aaf637404 -size 4618546 +oid sha256:4a3893d0f0f3ad76839c5c03dc1e6eaeedfd2108f223fea5ddfeca4199d0a9e5 +size 4616463 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index f07ad42c25..d1046c54b8 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c27b0748cb0a6539b7bb9ae1497768e003058d3d6fbae94ad5c8f18b6d8c13b5 -size 748029 +oid sha256:ce38e402e5b71812deeff53863f7f073511ec348ea55fd8b589da6a043764edb +size 747862 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index b61f42a0e1..3a3e7ba493 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1e8fdf084009d76c178a8b2613a608e95b45fdf165493c114a04d89c12aa0bf9 -size 3137852 +oid sha256:1668b48569c80d0c9935481a96a4d536c0eeb981e38dcdb69d48168d368ad20c +size 3136751 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index f2399b9939..60f4503d19 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cbcf5c0bf83babfe878d2e5e253e00f0407b11ab4a2991ab7bee52741e4b520d -size 851696 +oid sha256:62ae6e5867dd441d6393c7edcf28b5661bfd19bc761e8845999ace814bdda2dd +size 851611 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index d44c2e977d..7603b9a6fe 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8561675c11f177e3a718e55155c462f320d4286bd80ee21894ea7dffe93fc947 -size 1759584 +oid sha256:b032f49be7ee9621fb8c5b00b7acb904fe82f2a7068a6897a70f8cfeff1ecc36 +size 1759626 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index 7e939e43f3..c2b932f1a7 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a25efaad9295507a45ff1832b3219d6ad04a9aaa0c1a9de4fa0cda887ebfc4d -size 1174270 +oid sha256:8fb1718415ffe38c35b5656d7b8705568139171a0f8c65da1c3b56febaad693c +size 1174136 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index ef15be2e04..f75504a9ff 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c86659be747dd6995c72facb6c570986799e592b1f8c9f4d1cb6a1db07b35273 -size 4737884 +oid sha256:743c083d827e9155acfe32e04a3dac488ce202cd97730006b1e0945ffed4a458 +size 4736764 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index e016acdc58..22b6d91b2d 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:90ab6db0e0e41988378be0d3c7ca212443590e69b81d1a4e1b9c8759341776cf -size 782685 +oid sha256:f8dbc2361b75dc43a18b7e4e6279c1b485f12615d17c6181b195e43bb851472c +size 782570 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index 9170c223bf..37c9f73a58 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:75a8b2c0e938e4f6947a7cba21400a7f6e455339aac347cb01de1385d574b936 -size 3354240 +oid sha256:ec7040398feec5d3cb3d6f0a0c13093c6e89d9be2d025d1c1940a70dcfe59e9d +size 3354146 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index dfa18f5769..62b86434b7 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:384e100902ba3da3961888fe250020bc76f95227e2f36b3fcdd0eda2f1e9dac5 -size 864769 +oid sha256:c507bf88e06a496f157e20d22a49c7a10652c14d9bab74b81db523eccedef5be +size 863971 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index f54bf18713..6ef7deb252 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:06ec78d38d666274d2c23ac8f077aeafddf8ffe867bf63696d4a9eab0c4d1552 -size 4781105 +oid sha256:b14c906bcfd4728a0ea9886e64a47e98062b0b4d5d107e01c50de7c0f6529bf4 +size 4780237 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 1e3e786f5b..153b5fa81c 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb3e4e4b96893b13f1377f12950a74d21278f0325f1e695ec35d4477dfe13ff8 -size 770794 +oid sha256:08e87f73971ebde3a1d09c1acb4be6cb13be6b1701ee1f97e7214fa5847dead0 +size 770697 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 2e152aa64d..4e98c762f9 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8edbd543a76775a490f57280a16ab6bb163ccf53c7f8e0750e97c6618f0da0d1 -size 3246575 +oid sha256:1da56463d8650a188acd4f3eae1866762f242f49231931ac0d60c4a261e8b5c6 +size 3246942 diff --git a/lib/search/indexes/github-docs-3.6-cn-records.json.br b/lib/search/indexes/github-docs-3.6-cn-records.json.br index cf74ca6998..fcefa08d4b 100644 --- a/lib/search/indexes/github-docs-3.6-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.6-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7069890407e191ef61162ac7aa72b69eaab2d834165017c70fceeced8c2c0156 -size 874339 +oid sha256:a08c68cc86cc6a5c27080e69884453e5475b882714a29b50fbb4d67d074adf28 +size 874505 diff --git a/lib/search/indexes/github-docs-3.6-cn.json.br b/lib/search/indexes/github-docs-3.6-cn.json.br index 5d76b4cefa..7860a373f3 100644 --- a/lib/search/indexes/github-docs-3.6-cn.json.br +++ b/lib/search/indexes/github-docs-3.6-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7af904f4b6fbe431a6c703eb79be47a6112ec1efdf3faa0c0ebd2701c51a90e2 -size 1807589 +oid sha256:c9b1b4906f1d497610f266cc8ed1b5c0363c20098c13486c53cda518c0b40a3d +size 1807571 diff --git a/lib/search/indexes/github-docs-3.6-en-records.json.br b/lib/search/indexes/github-docs-3.6-en-records.json.br index a27c2aa4bb..4c409d1ad0 100644 --- a/lib/search/indexes/github-docs-3.6-en-records.json.br +++ b/lib/search/indexes/github-docs-3.6-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bc83caa795c42e78d38085cd5f6667cc6da56eb752eb2473765f6dbc1b87a8e4 -size 1202567 +oid sha256:508d13d8ba53eb0fabffeca03a9e4b3dc460aa688996a740e93061c4eab743c2 +size 1202807 diff --git a/lib/search/indexes/github-docs-3.6-en.json.br b/lib/search/indexes/github-docs-3.6-en.json.br index c0c716d098..afd4a31c30 100644 --- a/lib/search/indexes/github-docs-3.6-en.json.br +++ b/lib/search/indexes/github-docs-3.6-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eb243d78cfebfe8d8e52595fa32b4c61c2e39c444f5e63e096f88ba7f0301f91 -size 4852373 +oid sha256:f50c7359248b8dfccb716b7eedccc5e29c48c138a78b993a4902530dec26d5d4 +size 4852404 diff --git a/lib/search/indexes/github-docs-3.6-es-records.json.br b/lib/search/indexes/github-docs-3.6-es-records.json.br index 7fd5bc0645..bf6ddca192 100644 --- a/lib/search/indexes/github-docs-3.6-es-records.json.br +++ b/lib/search/indexes/github-docs-3.6-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:63ab8f3be141c78ab30c615813f522be6a95b5b8df1d364a3f12d26fd9c5ed26 -size 803062 +oid sha256:61857c48d92589ded99a3fe5e6529b116cd20b53107283f5d0d84523be435b2e +size 803088 diff --git a/lib/search/indexes/github-docs-3.6-es.json.br b/lib/search/indexes/github-docs-3.6-es.json.br index 2f4573a9f3..5ec1a8a9fd 100644 --- a/lib/search/indexes/github-docs-3.6-es.json.br +++ b/lib/search/indexes/github-docs-3.6-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a02eb794157c3b345c0eddad44dc189b4f3d32bcea52a241111a0cad6aa60b09 -size 3451472 +oid sha256:f736851b743c7e1c41d710ca60ad5b6d14a7b19c5fe5c78d856bb4eecb32bc6c +size 3451885 diff --git a/lib/search/indexes/github-docs-3.6-ja-records.json.br b/lib/search/indexes/github-docs-3.6-ja-records.json.br index b829483beb..bcd3e37fb1 100644 --- a/lib/search/indexes/github-docs-3.6-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.6-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3401701f18cf295316463905afdcb706f93d6ec0bf9d5c7f06e24f4c89b4afdb -size 887333 +oid sha256:babe221a8fc95bda88185d162cd6639099d4765d505d8f89bb0b61719998f8f7 +size 886560 diff --git a/lib/search/indexes/github-docs-3.6-ja.json.br b/lib/search/indexes/github-docs-3.6-ja.json.br index a179bb33e1..75f52796c0 100644 --- a/lib/search/indexes/github-docs-3.6-ja.json.br +++ b/lib/search/indexes/github-docs-3.6-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9a86436348af4af5861bbd7780f11b445d57bd66eb61196b1ea8933fb338964f -size 4914478 +oid sha256:aab8388e0c5807390ffc46eae3c61c62d5ddd87cd5d5713ed0f82f1696a0af65 +size 4911859 diff --git a/lib/search/indexes/github-docs-3.6-pt-records.json.br b/lib/search/indexes/github-docs-3.6-pt-records.json.br index b9af80cdd0..6869794c3a 100644 --- a/lib/search/indexes/github-docs-3.6-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.6-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1a200c213206a1969929c7799ee929cb4635cc3e31295f2734d0163f9dd7c694 -size 791409 +oid sha256:8ec2b71d094f418e311101866d168c97fbf13e82ae8171a93d7da7fd661dad19 +size 791430 diff --git a/lib/search/indexes/github-docs-3.6-pt.json.br b/lib/search/indexes/github-docs-3.6-pt.json.br index 516ee9e47a..fd28928243 100644 --- a/lib/search/indexes/github-docs-3.6-pt.json.br +++ b/lib/search/indexes/github-docs-3.6-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:86580388bab174c5ed558c7ee0bd7f389fc73eb16a0c440b833117fc64519693 -size 3343809 +oid sha256:dd4cba30e797a56d9aa382792dbf83d74a0891501ec18e5b59864aa143d21a02 +size 3342763 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 37f4b8efc5..f413a9babe 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2cbaf2e644856e74da346bc4eb179bdc2cca720e29feed74bf907bfcfb66b5ab -size 1036207 +oid sha256:7c4002bb3a3367941fc2e97cc784e443c8b3a6e90fb2a4991dfce7f784dbc183 +size 1036113 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index f7f6a0aa53..141e7bc4d8 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3418fbdb1d39e6f3fcae891308640d298a2c44312ee9fabcade4f6a3f01a8467 -size 1841510 +oid sha256:475e2e816bd8d6a63ecce6712cdfc6bc563c55e5dd3561c150524d009e12f594 +size 1841960 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index 9d9a49d465..d26db70fe0 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a977b70f80882546ebba5eeec9bf22a074a51dcfda137e271608edf44d0853e -size 1445163 +oid sha256:7ea944c6877de227db1bbd0a900669602d0b65a700b3decd149e971bb14aa0c2 +size 1445316 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 6b44c5e2d1..208502779a 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:58f39cbc6e90f04602b41a1710c56d7ea381b9705755aa0cdb6243f1238c54fd -size 5566225 +oid sha256:c11daa836e0ef6cc99b3b08e68ab48a0b95ce92171e33fa077b3cbc81fdc402c +size 5568416 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index f568175d59..74422c3d57 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b7bb9db5ba3d4e6999aef5e232216a64b0398043a481de02bfa49d24624e8811 -size 934250 +oid sha256:b0f5b18ed45e510c9c64c9628f520ea80840af12a405e1a6a495d58d5fe4ee60 +size 934135 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index c99e8bae14..d21d632d8b 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:66934092b477f5a62a98c59ea2f505ea02ee15ad7d97d07e6c5ddfdc1faefdab -size 3885445 +oid sha256:294e58d515c2883c79daa5ece957000c946329f79390ef5c74e981f525d23094 +size 3885546 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 233cf3847c..afe95cb3fe 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4ce56531d08b584248c608f499b05b21f5f7d21b4e464cd09094da013455a614 -size 1043240 +oid sha256:21e8bcdf90c31530e5c961308383603bcfc3768041a5869f35a26eaca66851c9 +size 1042504 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index a32d78bd4a..eabaa84376 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fbfb7498a01ff65bc46ad3d47991bb2784227bf0e32eaebffab6eb218289830c -size 5607983 +oid sha256:c8568c7ce9ac06a4e2dcda0813a1bca89b7438409f2eada4540610dc6375d376 +size 5603150 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index d26400bf10..fccbe59d8d 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a064a299445ced84011f8422b86e65cb250e7996936298b2bd0991509b3f3b2a -size 923257 +oid sha256:ad89e256214fe9d652207cc8218e3d1dd33a679245a49935a566de647c1aba56 +size 923302 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index 64067ed6c8..c432a4277e 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f679752b629f3dfcc70d5d4bbe5a4efe5f2f75878e23363e7dd36666263494b0 -size 3800651 +oid sha256:a3531bd196e679aa8eac4156c9ced5f702ec526b07214ba25b7b8a3a552cb9e6 +size 3800584 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 158ee256cd..c34289f9ce 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8eb2cce701ede42f418a425d237162dfd44e7c3488a9fe7762c9e5088d75c176 -size 659180 +oid sha256:a7540f3cb2398168ded1a94f83199c5e97bfac9c1a98c35049bc3f13b258fb1f +size 659211 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 3a2e83a969..94c341252e 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fe8f0cfeef91a813c13a27c8196a6c1007caf9390a79e24a901047cc2c889a1f -size 1311026 +oid sha256:79705db652382169111040119b71a00b17744c33cda560137868753518fea374 +size 1311052 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index da50bf3ef9..1a8bf9523c 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d58cb6e774244892146d7e2bb0b3221775f9d4ae77fcbaab96a9c4b380d2a235 -size 932648 +oid sha256:e9054163a223275a7cb828d7fa7e192be67ccafdc2630af0b438ca98ea716d99 +size 932345 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index 76157149f1..0cb029e759 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6fc36b7e4d3fbc64c5398d8ca938673feacd3a48f71b22c9702ecab63abc9838 -size 3697983 +oid sha256:481008b9e2dfaee5de9a2c462af9cbcc1e173ee2e62f9a6588b75c6de278f8ab +size 3696604 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 985fe79558..760735a670 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb9a3b214dd83130b4df85d295b521440f74ec423e63934c06530d9fa532ef82 -size 613165 +oid sha256:c98a5626db824b00b210ad23c14d42ee4222b7a59f82468830b6d539e03c405a +size 613264 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 2d5f6e0281..34a38893e3 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:95912386cad690660058938dc06b95f744a54b8158dafa7bc0b9907a67da1c00 -size 2536518 +oid sha256:59b8f3862467169301c17f1314a42a4eb40ef164204f86681d6713e33d089ada +size 2536962 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index 9e46671367..78a2bd19c5 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:585592d859f874abcafcb97cd76a12a4979d9672653589bca0637b0e19f6ce8c -size 673320 +oid sha256:2e44debc7479b54e6a1ebfc37ea577908bdbd52149d0277bc0704d2fd6130a41 +size 672338 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 47122de73a..704696f59c 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:537ddd303d8397af31b6287ac4654ec167ee29cd2d5288772fd67e6188afc8be -size 3601242 +oid sha256:10d96e7c258fd606a180638d5b5d6289b5787333929f6b1b1ae2b62622d3cac4 +size 3597717 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 42c0be3016..203dfc5334 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e47241b870dc126c7e8c502c12221af4e0b8a81f2b8f1853505a9ae0e3396d48 -size 604324 +oid sha256:a53b273b1b7c4ecd17cb99760624fd40c9802563d0650d40efd64af2f3ed9ddc +size 604239 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 37ba408c1d..f4c8f315f3 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0efd922709faefb52adcdf3431cd7f75105ab88a48a33a5a9f363a54db2b4cd0 -size 2433883 +oid sha256:4c86353936b741d550e3bd7481b5135306e5d9c8d58c0b915a679d283f84414c +size 2434305 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 98b36f9223..5f5429b38c 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:82fc6b0349b75548f087979b3f97ff0b289f73303f028c39918c0dc6f133d5e1 -size 1005303 +oid sha256:8755c23ab048a89d407c75647c228ccb788cce36b0ed25888990e3708c20c2f8 +size 1005383 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index e40c3297be..431d6e265f 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6f139f9dd2049babcacf96bd861f6e39ebb25df68e94cd87fb97ed1754e4f0bc -size 1965025 +oid sha256:433c3374b2a17945dfa844ab065514b3a3f557c02281acb96b6b9b595aa6d41c +size 1964883 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index ce099bd4fa..b07d5ec446 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:28f9028dee9a6f07591e668408d97046c71e1a681ab0a8d163d806a7cc346f9d -size 1371784 +oid sha256:9e32ad50465c9d4fb1213924f3c70db366246a8aac73caf825b2f49e0dacb9e3 +size 1371786 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index c26abc156b..ebb6753aa7 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c8dd38875cc2b1ba0796901891e114360778e35f2c30894b12ee70af7b71a6ae -size 5568340 +oid sha256:ad041bc6c2d856d2884153b9fcd57d041ad5d2f0c3ef4dd40b58db14a4f4e849 +size 5570755 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 34541022fc..c6a8a1ed9e 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b51f95e2d8293d7add9eaae58a2df16bb8e436bf9dbf748006d8fa93b04725da -size 930767 +oid sha256:e92fda231e3dc8fa0be129d0e6ac8e1f43fd508bf86b742815761bf597dc7849 +size 930820 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index cb8671cf02..797e533fb5 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2a9e98e71276f4a5cef6abde1a89aedf1082e5477b1495896f21180c2307aa16 -size 4018689 +oid sha256:a499c3cd9df467d8d16f54df090cdb8ee8544bc177962edb93f76a32b8b40c83 +size 4018509 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 1eab1e6036..b184909c2d 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:339c0d63a401f0d6ce3470585e0ace8e4c52157a688849ba4e2d9a91b7bb7c46 -size 1018356 +oid sha256:86ade65c287b63e4f369d20308d2aa3f1673740444a9085d430bf3c1950e45a1 +size 1018007 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 3ce41d1745..14ddbffae0 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d09d8e0d6931fb61585e1977d03e87321ef5374f4e3e1a561258600dc36ef7cd -size 5689440 +oid sha256:2efb26ad9b3bd50a8407806966100ef2559abe325ea0d58bdde0096ea05466ab +size 5687125 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index e7fb70052f..61ccf0057a 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:23d8e2d6dee457a8be4e12d840daecee51f39e155daa79ff958eddcef94369a8 -size 918619 +oid sha256:8ae9368ce26fe54ef810f233c8888dc0943b34def54150d7e69b96fc71cc353f +size 918751 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index d6373b17d1..11ac632071 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:49f02b6d8f76edc65c796577a66b43abd03182a4d6a24dda5413504a32bc0f37 -size 3915819 +oid sha256:5c68a894b09026de4450c87814b89c4d59e3b1d10059e5f6f38afb89e617846a +size 3920019
仮想環境Runner image YAMLのワークフローラベル 注釈