diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index 5a18705739..fed4af9a0b 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -215,6 +215,12 @@ For more information on how to configure this setting, see {% ifversion allow-ac These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. +{% note %} + +**Note:** {% data variables.product.prodname_dotcom %}-hosted runners do not scan for malicious code downloaded by a user during their job, such as a compromised third party library. + +{% endnote %} + ### Accessing secrets Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 5b79fefc07..fd0656617f 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -77,9 +77,15 @@ Maximum concurrency was measured using multiple repositories, job duration of ap {%- endif %} -{%- ifversion ghes = 3.6 %} +{%- ifversion ghes > 3.5 %} -{% data reusables.actions.hardware-requirements-3.6 %} + +| vCPUs | Memory | Maximum Connected Runners | +| :---| :--- | :--- | +| 8 | 64 GB | 740 runners | +| 32 | 160 GB | 2700 runners | +| 96 | 384 GB | 7000 runners | +| 128 | 512 GB | 7000 runners | {% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance. diff --git a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md index 4f4b684e45..f2a0daf3c9 100644 --- a/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/ja-JP/content/code-security/dependabot/dependabot-alerts/index.md @@ -19,11 +19,11 @@ children: - /configuring-dependabot-alerts - /viewing-and-updating-dependabot-alerts - /configuring-notifications-for-dependabot-alerts -ms.openlocfilehash: 04365ffa391c8da15c34f1e0651d9efa4ebb1a42 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: b9abda5288d4f0dfed2175b0e944c0d1bc48f3f7 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '146455494' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114099' --- diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md new file mode 100644 index 0000000000..0ebab7e66c --- /dev/null +++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md @@ -0,0 +1,51 @@ +--- +title: リポジトリ セキュリティ アドバイザリへのコラボレータの追加 +intro: あなたと協力するセキュリティアドバイザリとして、ユーザや Team を追加できます。 +redirect_from: + - /articles/adding-a-collaborator-to-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory + - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory + - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration +shortTitle: Add collaborators +ms.openlocfilehash: d080fa5d7b66d9ce89b7985f689133e52ec69cc3 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114139' +--- +セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加できます。 + +{% data reusables.security-advisory.repository-level-advisory-note %} + +## セキュリティアドバイザリにコラボレータを追加する + +コラボレータは、セキュリティアドバイザリへの書き込み権限を持ちます。 詳細については、「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」を参照してください。 + +{% note %} + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} セキュリティ アドバイザリのコラボレーターの削除に関する詳細については、「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」を参照してください。 + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、コラボレータとして追加するセキュリティアドバイザリをクリックします。 +5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリとして追加するユーザまたは Team の名前を入力します。 + ![ユーザ名または Team 名を入力するフィールド](/assets/images/help/security/add-collaborator-field.png) +6. **[追加]** をクリックします。 + ![[追加] ボタン](/assets/images/help/security/security-advisory-add-collaborator-button.png) + +## 参考資料 + +- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 +- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」 +- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」。 diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md new file mode 100644 index 0000000000..5a182af936 --- /dev/null +++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md @@ -0,0 +1,91 @@ +--- +title: 一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする +intro: リポジトリにおけるセキュリティ脆弱性の修正について非公開でコラボレートするため、一時的なプライベートフォークを作成できます。 +redirect_from: + - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration + - Forks +shortTitle: Temporary private forks +ms.openlocfilehash: c5d4f5f8b58498f995a473b4c0c0f3c38ea96083 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114131' +--- +{% data reusables.security-advisory.repository-level-advisory-note %} + +## 前提条件 + +一時的なプライベートフォークでコラボレートする前に、ドラフトのセキュリティアドバイザリを作成する必要があります。 詳細については、「[リポジトリ セキュリティ アドバイザリの作成](/code-security/repository-security-advisories/creating-a-repository-security-advisory)」を参照してください。 + +## 一時的なプライベートフォークを作成する + +セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークを作成できます。 + +脆弱性についての情報を保護するため、CI を含むインテグレーションは、一時的なプライベートフォークにアクセスできません。 + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、一時的なプライベートフォークを作成するセキュリティアドバイザリをクリックします。 + ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. **[新しい一時的なプライベートフォーク]** をクリックします。 + ![[新しい一時的なプライベートフォーク] ボタン](/assets/images/help/security/new-temporary-private-fork-button.png) + +## 一時的なプライベートフォークにコラボレータを追加する + +セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリにコラボレータを追加でき、セキュリティアドバイザリのコラボレータは一時的なプライベートフォークにアクセスできます。 詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。 + +## 一時的なプライベートフォークに変更を追加する + +セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、一時的なプライベートフォークに変更を追加できます。 + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、変更を追加するセキュリティアドバイザリをクリックします。 + ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. {% data variables.product.product_name %} またはローカルに変更を追加します: + - {% data variables.product.product_name %} に変更を追加するには、[このアドバイザリに変更を追加する] で、 **[一時的なプライベート フォーク]** をクリックします。 そして、新しいブランチを作成し、ファイルを編集します。 詳細については、「[リポジトリ内でブランチを作成および削除する](/articles/creating-and-deleting-branches-within-your-repository)」および「[ファイルの編集](/repositories/working-with-files/managing-files/editing-files)」を参照してください。 + - ローカルで変更を追加するには、「クローンを作成して新しいブランチを作成する」および「変更を加えてからプッシュする」の手順に従ってください。 + ![[このアドバイザリに変更を追加する] ボックス](/assets/images/help/security/add-changes-to-this-advisory-box.png) + +## 一時的なプライベートフォークからプルリクエストを作成する + +セキュリティアドバイザリに対する書き込み権限があるユーザなら誰でも、一時的なプライベートフォークからプルリクエストを作成できます。 + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、セキュリティアドバイザリを作成するプルリクエストをクリックします。 + ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. ブランチ名の右側にある **[比較と pull request]** をクリックします。 + ![[比較と pull request] ボタン](/assets/images/help/security/security-advisory-compare-and-pr.png) {% data reusables.repositories.pr-title-description %} {% data reusables.repositories.create-pull-request %} + +{% data reusables.repositories.merge-all-pulls-together %} 詳細については、「[変更をセキュリティ アドバイザリにマージする](#merging-changes-in-a-security-advisory)」を参照してください。 + +## 変更をセキュリティアドバイザリにマージする + +セキュリティアドバイザリに対する管理者権限があるユーザなら誰でも、セキュリティアドバイザリに変更をマージできます。 + +{% data reusables.repositories.merge-all-pulls-together %} + +セキュリティアドバイザリの変更をマージするには、一時的なプライベートフォークにあるすべてのオープンされたプルリクエストがマージできる必要があります。 マージコンフリクトは許容されません。また、ブランチ保護の要件を満たす必要があります。 脆弱性についての情報を保護するため、一時的なプライベートフォークにあるプルリクエストに対しては、ステータスチェックは実行されません。 詳細については、「[保護されたブランチについて](/articles/about-protected-branches)」を参照してください。 + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、変更をマージするセキュリティアドバイザリをクリックします。 + ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. 一時的なプライベート フォーク内にあるすべてのオープンされた pull request をマージするには、 **[pull requests をマージする]** をクリックします。 + ![[pull request のマージ] ボタン](/assets/images/help/security/merge-pull-requests-button.png) + +セキュリティアドバイザリの変更をマージした後は、プロジェクトの以前のバージョンにある脆弱性についてコミュニティにアラートするため、セキュリティアドバイザリを公開できます。 詳細については、「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください。 + +## 参考資料 + +- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 +- 「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md new file mode 100644 index 0000000000..28b1d70215 --- /dev/null +++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/permission-levels-for-repository-security-advisories.md @@ -0,0 +1,51 @@ +--- +title: リポジトリ セキュリティ アドバイザリの権限レベル +intro: リポジトリ セキュリティ アドバイザリで実行できるアクションは、セキュリティ アドバイザリに対する管理者や書き込みの権限を持っているかどうかによって変わります。 +redirect_from: + - /articles/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories + - /code-security/security-advisories/permission-levels-for-security-advisories + - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Security advisories + - Vulnerabilities + - Permissions +shortTitle: Permission levels +ms.openlocfilehash: f4195822de121780f1629fda3d646170d4c4e566 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114136' +--- +この記事は、リポジトリ レベルのセキュリティ アドバイザリのみを対象としています。 あらゆるユーザーは、[github.com/advisories](https://github.com/advisories) で、{% data variables.product.prodname_advisory_database %} のグローバル セキュリティ アドバイザリに貢献できます。 グローバル アドバイザリを編集しても、リポジトリでのアドバイザリの表示方法が変更されたり、影響を受けたりすることはありません。 詳細については、「[{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリの編集](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)」を参照してください。 + +## アクセス許可の概要 + +{% data reusables.repositories.security-advisory-admin-permissions %} セキュリティ アドバイザリへのコラボレーターの追加に関する詳細については、「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください。 + +アクション | Write 権限 | 管理者のアクセス許可 | +------ | ----------------- | ----------------- | +セキュリティアドバイザリのドラフトを表示する | X | X | +コラボレーターをセキュリティ アドバイザリに追加する (「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」を参照してください) | | X | +セキュリティアドバイザリでコメントを編集および削除する | X | X | +セキュリティ アドバイザリに一時的なプライベート フォークを作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X | +セキュリティ アドバイザリの一時的なプライベート フォークに変更を追加する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X | +一時的なプライベート フォークに pull request を作成する (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | X | X | +セキュリティ アドバイザリに変更をマージする (「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」を参照してください) | | X | +メタデータをセキュリティ アドバイザリに追加して編集する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | X | X | +セキュリティ アドバイザリのクレジットを追加および削除する (「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」を参照してください) | X | X | +セキュリティアドバイザリのドラフトをクローズする | | X | +セキュリティ アドバイザリを公開する (「[リポジトリ セキュリティ アドバイザリの公開](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)」を参照してください) | | X | + +## 参考資料 + +- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」 +- 「[一時的なプライベート フォークで、リポジトリのセキュリティ脆弱性を解決するためにコラボレートする](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)」 +- 「[リポジトリ セキュリティ アドバイザリからのコラボレータの削除](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)」 +- 「[リポジトリ セキュリティ アドバイザリの撤回](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md new file mode 100644 index 0000000000..1736cb5f6d --- /dev/null +++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md @@ -0,0 +1,43 @@ +--- +title: リポジトリ セキュリティ アドバイザリからのコラボレータの削除 +intro: リポジトリ セキュリティ アドバイザリからコラボレーターを削除すると、そのコラボレーターはセキュリティ アドバイザリのディスカッションとメタデータへの読み取りおよび書き込みアクセス権を失います。 +redirect_from: + - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory + - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities + - Collaboration +shortTitle: Remove collaborators +ms.openlocfilehash: 77c21bea9c593935ee1b92028fc52859320f5a38 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114123' +--- +セキュリティアドバイザリの管理者権限を持つユーザは、セキュリティアドバイザリからコラボレータを削除できます。 + +{% data reusables.security-advisory.repository-level-advisory-note %} + +## セキュリティアドバイザリからコラボレータを削除する + +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} + +{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %} +4. [Security Advisories] のリストから、コラボレータを削除するセキュリティアドバイザリをクリックします。 + ![リスト内のセキュリティ アドバイザリ](/assets/images/help/security/security-advisory-in-list.png) +5. ページの右側にある、[Collaborators] の下で、セキュリティアドバイザリから削除するユーザまたは Team の名前を探します。 + ![セキュリティ アドバイザリのコラボレータ](/assets/images/help/security/security-advisory-collaborator.png) +6. 削除するコラボレーターの横にある **[X]** アイコンをクリックします。 + ![セキュリティ アドバイザリからコラボレータを削除する [X] アイコン](/assets/images/help/security/security-advisory-remove-collaborator-x.png) + +## 参考資料 + +- 「[リポジトリ セキュリティ アドバイザリの権限レベル](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)」 +- 「[リポジトリ セキュリティ アドバイザリへのコラボレータの追加](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md new file mode 100644 index 0000000000..05d8e1da48 --- /dev/null +++ b/translations/ja-JP/content/code-security/security-advisories/repository-security-advisories/withdrawing-a-repository-security-advisory.md @@ -0,0 +1,29 @@ +--- +title: リポジトリ セキュリティ アドバイザリの撤回 +intro: 公開したリポジトリ セキュリティ アドバイザリを撤回できます。 +redirect_from: + - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory + - /code-security/security-advisories/withdrawing-a-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities +shortTitle: Withdraw repository advisories +ms.openlocfilehash: 71a6560c463384b032546b824e5f4294ced568e5 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114015' +--- +{% data reusables.security-advisory.repository-level-advisory-note %} + +誤ってセキュリティアドバイザリを公開した場合は、{% data variables.contact.contact_support %} に連絡するとセキュリティアドバイザリを撤回できます。 + +## 参考資料 + +- 「[リポジトリ セキュリティ アドバイザリの編集](/code-security/repository-security-advisories/editing-a-repository-security-advisory)」 diff --git a/translations/ja-JP/content/codespaces/guides.md b/translations/ja-JP/content/codespaces/guides.md index 70587a4b81..560f403a61 100644 --- a/translations/ja-JP/content/codespaces/guides.md +++ b/translations/ja-JP/content/codespaces/guides.md @@ -55,11 +55,11 @@ includeGuides: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces - /codespaces/codespaces-reference/disaster-recovery-for-codespaces - /codespaces/codespaces-reference/security-in-codespaces -ms.openlocfilehash: 54ba7cc4fbacd536f0438626281d1b59252eb3f1 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 24bf08da053efd9f822b1eb43bacbbe822c1ba8b +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147783112' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148113898' --- diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md index 2219a57e3b..614a43786a 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/index.md @@ -19,11 +19,11 @@ children: - /setting-a-minimum-specification-for-codespace-machines - /automatically-opening-files-in-the-codespaces-for-a-repository - /adding-a-codespaces-badge -ms.openlocfilehash: 1e172243dc351f0a173c8624b66914e1c3795495 -ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794 +ms.openlocfilehash: 4649ef4e36dff0b37d4a579ecd56bbb0edd2a184 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/09/2022 -ms.locfileid: '147783040' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148114104' --- diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md index 66d943e422..31665db03e 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/renaming-a-repository.md @@ -12,12 +12,12 @@ versions: ghec: '*' topics: - Repositories -ms.openlocfilehash: e56e8ca634ca1bfec3c587fe8fb606ab73ac72d4 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: d0067d96dce2f2cf9fe8bb2dd519668780d861ff +ms.sourcegitcommit: bd8b3e152f17d90acf222a0d50ba9595184c1f5f ms.translationtype: HT ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145132294' +ms.lasthandoff: 10/27/2022 +ms.locfileid: '148111674' --- リポジトリの名前を変更すると、プロジェクトサイトの URL を除くすべての既存の情報は、下記を含む新しい名前に自動的にリダイレクトされます。 @@ -28,10 +28,10 @@ ms.locfileid: '145132294' プロジェクト サイトの詳細については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)」を参照してください。 -Web トラフィックのリダイレクトに加えて、以前の場所を対象とするすべての `git clone`、`git fetch`、`git push` 操作は、新しい場所で行われたかのように機能し続けます。 ただし、混乱を低減するため、既存のローカルクローンが新しいリポジトリ URL を指すよう更新することを強く推奨します。 これはコマンドラインで `git remote` を使うことで行えます。 +Web トラフィックのリダイレクトに加えて、以前の場所を対象とするすべての `git clone`、`git fetch`、`git push` 操作は、新しい場所で行われたかのように機能し続けます。 ただし、混乱を低減するため、既存のローカルクローンが新しいリポジトリ URL を指すよう更新することを強く推奨します。 これはコマンド ラインで `git remote` を使うことで行えます。 ```shell -$ git remote set-url origin new_url +$ git remote set-url origin NEW_URL ``` 詳細については、「[リモート リポジトリを管理する](/github/getting-started-with-github/managing-remote-repositories)」を参照してください。 @@ -50,7 +50,7 @@ $ git remote set-url origin new_url {% warning %} -**警告**: 将来的にアカウントで新しいリポジトリを作成する場合、名前変更したリポジトリの元の名前を再利用しないでください。 再利用した場合、名前変更したリポジトリへのリダイレクトが切断されます。 +**警告**: 将来的にアカウントで新しいリポジトリを作成する場合、名前変更したリポジトリの元の名前を再利用しないでください。 再利用した場合、名前変更したリポジトリへのリダイレクトは機能しなくなります。 {% endwarning %} diff --git a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index 1ee323f4f4..7a6fcdc772 100644 --- a/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- -title: Git Large File Storageについて -intro: '{% data variables.product.product_name %} には、リポジトリで許可されるファイルのサイズに制限があります。 この制限を超えるファイルを追跡するには、{% data variables.large_files.product_name_long %} を使います。' +title: About Git Large File Storage +intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage @@ -12,35 +12,33 @@ versions: ghae: '*' ghec: '*' shortTitle: Git Large File Storage -ms.openlocfilehash: af198fe13f69fc4768178aea74a03f27a82ec20b -ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/11/2022 -ms.locfileid: '145131946' --- -## {% data variables.large_files.product_name_long %}について -{% data variables.large_files.product_name_short %}は、リポジトリに実際のファイルではなく、ファイルへの参照を保存することで大きなファイルを扱います。 Git のアーキテクチャを回避するため、{% data variables.large_files.product_name_short %} では実際のファイル (どこか別の場所に格納されています) への参照として働くポインター ファイルが作成されます。 {% data variables.product.product_name %}はこのポインタファイルをリポジトリ中で管理します。 リポジトリをクローンすると、{% data variables.product.product_name %}はこのポインタファイルを大きなファイルを見つけるための地図として使います。 +## About {% data variables.large_files.product_name_long %} -{% ifversion fpt or ghec %}{% data variables.large_files.product_name_short %} を使うと、最大で次のファイルまで格納できます。 +{% data variables.large_files.product_name_short %} handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git's architecture, {% data variables.large_files.product_name_short %} creates a pointer file which acts as a reference to the actual file (which is stored somewhere else). {% data variables.product.product_name %} manages this pointer file in your repository. When you clone the repository down, {% data variables.product.product_name %} uses the pointer file as a map to go and find the large file for you. -| 製品 | ファイルの最大サイズ | +{% ifversion fpt or ghec %} +Using {% data variables.large_files.product_name_short %}, you can store files up to: + +| Product | Maximum file size | |------- | ------- | | {% data variables.product.prodname_free_user %} | 2 GB | | {% data variables.product.prodname_pro %} | 2 GB | | {% data variables.product.prodname_team %} | 4 GB | | {% data variables.product.prodname_ghe_cloud %} | 5 GB |{% else %} -{% data variables.large_files.product_name_short %} を使うと、最大 5 GB までのファイルをリポジトリに格納できます。 -{% endif %} +Using {% data variables.large_files.product_name_short %}, you can store files up to 5 GB in your repository. +{% endif %} -{% data variables.large_files.product_name_short %}を{% data variables.product.prodname_desktop %}と共に使うこともできます。 {% data variables.product.prodname_desktop %} での Git FLS リポジトリのクローンについて詳しくは、「[GitHub からの GitHub Desktop へのリポジトリのクローン方法](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)」をご覧ください。 +{% data reusables.repositories.git-lfs %} + +You can also use {% data variables.large_files.product_name_short %} with {% data variables.product.prodname_desktop %}. For more information about cloning Git LFS repositories in {% data variables.product.prodname_desktop %}, see "[Cloning a repository from GitHub to GitHub Desktop](/desktop/guides/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)." {% data reusables.large_files.can-include-lfs-objects-archives %} -## ポインタファイルのフォーマット +## Pointer file format -{% data variables.large_files.product_name_short %}のポインタファイルは以下のようになっています。 +{% data variables.large_files.product_name_short %}'s pointer file looks like this: ``` version {% data variables.large_files.version_name %} @@ -48,16 +46,16 @@ oid sha256:4cac19622fc3ada9c0fdeadb33f88f367b541f38b89102a3f1261ac81fd5bcb5 size 84977953 ``` -使われている {% data variables.large_files.product_name_short %} の `version` の後にファイルの一意識別子 (`oid`) が付いたものが追跡されます。 また、最終的なファイルの `size` も格納されます。 +It tracks the `version` of {% data variables.large_files.product_name_short %} you're using, followed by a unique identifier for the file (`oid`). It also stores the `size` of the final file. {% note %} -**注**: -- {% data variables.large_files.product_name_short %} は {% data variables.product.prodname_pages %} サイトでは使用できません。 -- {% data variables.large_files.product_name_short %} はテンプレートリポジトリでは使用できません。 +**Notes**: +- {% data variables.large_files.product_name_short %} cannot be used with {% data variables.product.prodname_pages %} sites. +- {% data variables.large_files.product_name_short %} cannot be used with template repositories. {% endnote %} -## 参考資料 +## Further reading -- [{% data variables.large_files.product_name_long %} でのコラボレーション](/articles/collaboration-with-git-large-file-storage) +- "[Collaboration with {% data variables.large_files.product_name_long %}](/articles/collaboration-with-git-large-file-storage)" diff --git a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md index ed7f9b1189..f47cd8dbbf 100644 --- a/translations/ja-JP/content/rest/guides/traversing-with-pagination.md +++ b/translations/ja-JP/content/rest/guides/traversing-with-pagination.md @@ -12,6 +12,7 @@ versions: topics: - API shortTitle: Traverse with pagination +miniTocMaxHeadingLevel: 3 --- The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume. @@ -24,10 +25,13 @@ in the [platform-samples][platform samples] repository. {% data reusables.rest-api.dotcom-only-guide-note %} + + ## Basics of Pagination To start with, it's important to know a few facts about receiving paginated items: + 1. Different API calls respond with different defaults. For example, a call to [List public repositories](/rest/reference/repos#list-public-repositories) provides paginated items in sets of 30, whereas a call to the GitHub Search API @@ -37,55 +41,127 @@ provides items in sets of 100 [events](/rest/reference/activity#events) won't let you set a maximum for items to receive. Be sure to read the documentation on how to handle paginated results for specific endpoints. -Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988) -of an API call. For example, let's make a curl request to the search API, to find -out how many times Mozilla projects use the phrase `addClass`: +{% note %} + +**Note**: You should always rely on URLs included in the link header. Don't try to guess or construct your own URLs. + +{% endnote %} + + +### Link header + +The response header includes information about pagination. For more information about headers, see "[Getting started with the REST API](/rest/guides/getting-started-with-the-rest-api#about-the-response-code-and-headers)." To get the response header, include the `-I` flag in your request. For example: + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/advacado-corp/audit-log -```shell -$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla" ``` -The `-I` parameter indicates that we only care about the headers, not the actual -content. In examining the result, you'll notice some information in the Link header -that looks like this: +The `-I` flag returns only the response header. If the response is paginated, the response header will include a `link` header. The header will look something like this: - Link: ; rel="next", - ; rel="last" +``` +link: ; rel="next" +``` -Let's break that down. `rel="next"` says that the next page is `page=2`. This makes -sense, since by default, all paginated queries start at page `1.` `rel="last"` -provides some more information, stating that the last page of results is on page `34`. -Thus, we have 33 more pages of information about `addClass` that we can consume. -Nice! +or -**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL. +``` +link: ; rel="next", ; rel="last" +``` +### Types of pagination -### Navigating through the pages +{% data variables.product.company_short %}'s API uses two pagination methods: page-based pagination and cursor-based pagination. If the `link` header includes `page`, then the operation uses page-based pagination. If the `link` header includes `before` and `after`, then the operation uses cursor-based pagination. -Now that you know how many pages there are to receive, you can start navigating -through the pages to consume the results. You do this by passing in a `page` -parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14 -and see what happens: + +#### Page based pagination + +The link header for page-based pagination will tell you information about the previous, next, first, and last pages. If you did not request a specific page, then the response will default to the first page and information about the first and previous pages will be omitted. + +For example, for a request that did not specify a page, this header states that the next page is `2` and the last page is `511`. + +``` +link: ; rel="next", ; rel="last" +``` + +For example, for a request that specified page 5, this header states that the previous page is `4`, the next page is `6`, the last page is `511`, and the first page is `1`. + +``` +link: ; rel="prev", ; rel="next", ; rel="last", ; rel="first" +``` + +#### Cursor based pagination + +Cursor pagination uses terms `before` and `after` in order to navigate through pages. `rel="next"` and `rel="prev"` this mark the cursor point in the data set and provides a reference for traveling to the page `before` and `after` the current page. + +``` +link: ; rel="next", +; rel="first", +; rel="prev" +``` + +In this example, `rel=next` says that the next page is located at: + +``` +after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=> +``` + + + + +### Using pagination + +#### Cursor based pagination + +Using cursor based pagination requires you to use the terms `before` and `after`. To navigate using `before` and `after`, copy the link header generated above into your curl request: + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=> +``` + +The above example will generate a page of results and new header information that you can use to make the next request. `rel="next"` provides the next page of results. `rel="prev"` provides the previous page of results. The important part of the output here is the link header needs to be generated rather than manually imputed. Copy the entire link from the following output. + +``` +link: ; rel="next", +; rel="first", +; rel="prev" +``` + +Unlike page-based pagination, the results will not return the last page number in the response. + + link: ; rel="next", + ; rel="first", + ; rel="prev" + +Because cursor based pagination creates a reference point in the data set, it cannot calculate the total number of results. + + +#### Page based pagination + +To navigate using page based pagination pass in a `page` +parameter. By default, `page` always starts at `1`. In the following example, we have made a curl request to the search API Mozilla projects use the phrase `addClass`. Instead of starting at 1, lets jump to page 14. ```shell $ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14" ``` -Here's the link header once more: +Here's an except of the link header in the HTTP request: Link: ; rel="next", ; rel="last", ; rel="first", ; rel="prev" -As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've +In this example, `rel="next"` is at 15, and `rel="last"` is 34. But now we've got some more information: `rel="first"` indicates the URL for the _first_ page, and more importantly, `rel="prev"` lets you know the page number of the previous page. Using this information, you could construct some UI that lets users jump between the first, previous, next, or last list of results in an API call. + ### Changing the number of items received +#### Page based pagination + By passing the `per_page` parameter, you can specify how many items you want each page to return, up to 100 items. Let's try asking for 50 items about `addClass`: @@ -102,6 +178,14 @@ As you might have guessed, the `rel="last"` information says that the last page is now 20. This is because we are asking for more information per page about our results. +#### Cursor based pagination + +You can also pass the `per_page` parameter for cursor-based pagination. + +```shell +$ curl -I -H "Accept: application/vnd.github+json" -H "Authorization: Bearer YOUR_TOKEN" https://api.github.com/enterprises/13827/audit-log?after=MS42NjQzODM5MTkzNDdlKzEyfDM0MkI6NDdBNDo4RTFGMEM6NUIyQkZCMzo2MzM0N0JBRg%3D%3D&before=>&per_page=50 +``` + ## Consuming the information You don't want to be making low-level curl calls just to be able to work with diff --git a/translations/ja-JP/data/reusables/actions/hardware-requirements-3.6.md b/translations/ja-JP/data/reusables/actions/hardware-requirements-3.6.md deleted file mode 100644 index 2019de8458..0000000000 --- a/translations/ja-JP/data/reusables/actions/hardware-requirements-3.6.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -ms.openlocfilehash: 5c7cf10fca8efdcb186487e5de0e9a9d7e88d66b -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: ja-JP -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147580746" ---- -| vCPU 数 | メモリ | 最大接続ランナー数 | -| :---| :--- | :--- | -| 8 | 64 GB | 740 ランナー | -| 32 | 160 GB | 2700 ランナー | -| 96 | 384 GB | 7000 ランナー | -| 128 | 512 GB | 7000 ランナー | diff --git a/translations/ja-JP/data/reusables/codespaces/edit-devcontainer-json.md b/translations/ja-JP/data/reusables/codespaces/edit-devcontainer-json.md new file mode 100644 index 0000000000..6ad1646807 --- /dev/null +++ b/translations/ja-JP/data/reusables/codespaces/edit-devcontainer-json.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 38208812f73fda89c12d251955a1eee327ceb8db +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: "148114120" +--- +1. ご利用のリポジトリの {% data variables.product.prodname_github_codespaces %} は、`devcontainer.json` ファイル内で構成されます。 リポジトリに `devcontainer.json` ファイルがまだ含まれていない場合は、今すぐ追加します。 「[開発コンテナー構成をリポジトリに追加する](/free-pro-team@latest/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md index db1256da20..9bda52c077 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md @@ -1,6 +1,6 @@ If your workflow is using a {% data variables.product.pat_generic %} to authenticate to a registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. -{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-pat)."{% endif %} +{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to a registry with a {% data variables.product.pat_generic %}, see "[Upgrading a workflow that accesses a registry using a {% data variables.product.pat_generic %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-a-registry-using-a-personal-access-token)."{% endif %} For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." diff --git a/translations/ja-JP/data/reusables/security-advisory/global-advisories.md b/translations/ja-JP/data/reusables/security-advisory/global-advisories.md new file mode 100644 index 0000000000..05c965bbc9 --- /dev/null +++ b/translations/ja-JP/data/reusables/security-advisory/global-advisories.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: cb874d7a6fcaa0deeb828d91f9769df69050d337 +ms.sourcegitcommit: 27882d9b3f19979c817c25952a2fb4dc4c6f0a65 +ms.translationtype: HT +ms.contentlocale: ja-JP +ms.lasthandoff: 10/27/2022 +ms.locfileid: "148114005" +--- +[github.com/advisories](https://github.com/advisories) で、{% data variables.product.prodname_advisory_database %} のセキュリティ アドバイザリは、グローバル アドバイザリと見なされます。 {% data variables.product.prodname_advisory_database %} のグローバル セキュリティ アドバイザリに対する改善は、誰でも提案することができます。 影響を受けるエコシステム、重大度レベル、または影響を受けるユーザーの説明など、任意の詳細を編集または追加できます。 {% data variables.product.prodname_security %} キュレーション チームは、送信された改善を確認し、受け入れられた場合は {% data variables.product.prodname_advisory_database %} にそれらを発行します。 \ No newline at end of file diff --git a/translations/log/msft-ja-resets.csv b/translations/log/msft-ja-resets.csv index 0c39b2403a..6a85d4e3bc 100644 --- a/translations/log/msft-ja-resets.csv +++ b/translations/log/msft-ja-resets.csv @@ -227,6 +227,7 @@ translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponso translations/ja-JP/data/glossaries/internal.yml,file deleted because it no longer exists in main translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main translations/ja-JP/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main +translations/ja-JP/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main @@ -244,9 +245,7 @@ translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md,file translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main -translations/ja-JP/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main -translations/ja-JP/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main @@ -254,7 +253,6 @@ translations/ja-JP/data/reusables/education/upgrade-organization.md,file deleted translations/ja-JP/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main -translations/ja-JP/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise_management_console/username_normalization.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main translations/ja-JP/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main @@ -321,7 +319,7 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-accessibility-settings.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error -translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,broken liquid tags +translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/permission-levels-for-a-personal-account-repository.md,broken liquid tags translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error @@ -431,7 +429,7 @@ translations/ja-JP/content/admin/enterprise-management/caching-repositories/conf translations/ja-JP/content/admin/enterprise-management/caching-repositories/index.md,rendering error translations/ja-JP/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags -translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,broken liquid tags +translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/about-geo-replication.md,rendering error translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/creating-a-high-availability-replica.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags translations/ja-JP/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags @@ -622,13 +620,13 @@ translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/c translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md,rendering error translations/ja-JP/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md,rendering error -translations/ja-JP/content/code-security/dependabot/index.md,broken liquid tags +translations/ja-JP/content/code-security/dependabot/index.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md,rendering error translations/ja-JP/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md,rendering error -translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,broken liquid tags +translations/ja-JP/content/code-security/getting-started/adding-a-security-policy-to-your-repository.md,rendering error translations/ja-JP/content/code-security/getting-started/github-security-features.md,rendering error translations/ja-JP/content/code-security/getting-started/securing-your-organization.md,rendering error translations/ja-JP/content/code-security/getting-started/securing-your-repository.md,rendering error @@ -649,7 +647,7 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags -translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags +translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,rendering error translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags @@ -828,7 +826,7 @@ translations/ja-JP/content/organizations/managing-organization-settings/integrat translations/ja-JP/content/organizations/managing-organization-settings/managing-the-commit-signoff-policy-for-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags -translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,broken liquid tags +translations/ja-JP/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/ja-JP/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md,broken liquid tags @@ -913,6 +911,7 @@ translations/ja-JP/content/repositories/releasing-projects-on-github/comparing-r translations/ja-JP/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error translations/ja-JP/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error translations/ja-JP/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags +translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md,broken liquid tags translations/ja-JP/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags translations/ja-JP/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags translations/ja-JP/content/repositories/working-with-files/using-files/working-with-non-code-files.md,rendering error @@ -1024,7 +1023,7 @@ translations/ja-JP/data/reusables/actions/github-connect-resolution.md,broken li translations/ja-JP/data/reusables/actions/hosted-runner-security.md,broken liquid tags translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags -translations/ja-JP/data/reusables/actions/message-parameters.md,broken liquid tags +translations/ja-JP/data/reusables/actions/message-parameters.md,rendering error translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md,rendering error translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error translations/ja-JP/data/reusables/actions/ref_name-description.md,broken liquid tags @@ -1051,7 +1050,7 @@ translations/ja-JP/data/reusables/advanced-security/about-committer-numbers-ghec translations/ja-JP/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags translations/ja-JP/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error translations/ja-JP/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error -translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,broken liquid tags +translations/ja-JP/data/reusables/advanced-security/secret-scanning-new-custom-pattern.md,rendering error translations/ja-JP/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags translations/ja-JP/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md,rendering error @@ -1154,16 +1153,16 @@ translations/ja-JP/data/reusables/organizations/billing_plans.md,rendering error translations/ja-JP/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error translations/ja-JP/data/reusables/organizations/member-privileges.md,rendering error translations/ja-JP/data/reusables/organizations/navigate-to-org.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/new_team.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/org_settings.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/organization-wide-project.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/owners-team.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/people.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/new_team.md,rendering error +translations/ja-JP/data/reusables/organizations/org_settings.md,rendering error +translations/ja-JP/data/reusables/organizations/organization-wide-project.md,rendering error +translations/ja-JP/data/reusables/organizations/owners-team.md,rendering error +translations/ja-JP/data/reusables/organizations/people.md,rendering error translations/ja-JP/data/reusables/organizations/repository-defaults.md,rendering error translations/ja-JP/data/reusables/organizations/security-and-analysis.md,rendering error translations/ja-JP/data/reusables/organizations/security.md,rendering error -translations/ja-JP/data/reusables/organizations/specific_team.md,broken liquid tags -translations/ja-JP/data/reusables/organizations/teams.md,broken liquid tags +translations/ja-JP/data/reusables/organizations/specific_team.md,rendering error +translations/ja-JP/data/reusables/organizations/teams.md,rendering error translations/ja-JP/data/reusables/organizations/teams_sidebar.md,rendering error translations/ja-JP/data/reusables/organizations/verified-domains.md,rendering error translations/ja-JP/data/reusables/package_registry/authenticate-packages.md,broken liquid tags @@ -1171,7 +1170,7 @@ translations/ja-JP/data/reusables/package_registry/authenticate-to-container-reg translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags -translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md,broken liquid tags +translations/ja-JP/data/reusables/package_registry/package-settings-from-org-level.md,rendering error translations/ja-JP/data/reusables/package_registry/packages-billing.md,broken liquid tags translations/ja-JP/data/reusables/package_registry/required-scopes.md,broken liquid tags translations/ja-JP/data/reusables/pages/build-failure-email-server.md,broken liquid tags @@ -1218,7 +1217,7 @@ translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-public-rep translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error translations/ja-JP/data/reusables/security-advisory/security-advisory-overview.md,broken liquid tags translations/ja-JP/data/reusables/security-overview/permissions.md,rendering error -translations/ja-JP/data/reusables/security/displayed-information.md,broken liquid tags +translations/ja-JP/data/reusables/security/displayed-information.md,rendering error translations/ja-JP/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags translations/ja-JP/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags translations/ja-JP/data/reusables/ssh/about-ssh.md,broken liquid tags @@ -1251,7 +1250,7 @@ translations/ja-JP/data/reusables/user-settings/ssh.md,rendering error translations/ja-JP/data/reusables/webhooks/pull_request_properties.md,broken liquid tags translations/ja-JP/data/reusables/webhooks/pull_request_webhook_properties.md,broken liquid tags translations/ja-JP/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags -translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md,broken liquid tags +translations/ja-JP/data/reusables/webhooks/webhooks-rest-api-links.md,rendering error translations/ja-JP/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags translations/ja-JP/data/variables/product.yml,broken liquid tags translations/ja-JP/data/variables/projects.yml,broken liquid tags