diff --git a/translations/ja-JP/content/actions/learn-github-actions/contexts.md b/translations/ja-JP/content/actions/learn-github-actions/contexts.md index c8cd701eb4a2..72f5276d645c 100644 --- a/translations/ja-JP/content/actions/learn-github-actions/contexts.md +++ b/translations/ja-JP/content/actions/learn-github-actions/contexts.md @@ -192,7 +192,7 @@ jobs: | `github.event_path` | `string` | The path to the file on the runner that contains the full event webhook payload. | | `github.graphql_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} GraphQL API. | | `github.head_ref` | `string` | ワークフローの実行における `head_ref` またはPull Requestのソースブランチ。 このプロパティは、ワークフローの実行をトリガーするイベントが `pull_request` または `pull_request_target` のいずれかである場合にのみ使用できます。 | -| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 | +| `github.job` | `string` | 現在のジョブの[`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。
Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. | | `github.ref` | `string` | ワークフローの実行をトリガーしたブランチまたはタグ ref。 For branches this is the format `refs/heads/`, and for tags it is `refs/tags/`. | {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} | `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} @@ -201,7 +201,7 @@ jobs: {%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %} | `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. | {%- endif %} -| `github.server_url` | `string` | The URL of the GitHub server. たとえば、`https://github.com` などです。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。 | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | +| `github.server_url` | `string` | The URL of the GitHub server. たとえば、`https://github.com` などです。 | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。
Note: This context property is set by the Actions runner, and is only available within the execution `steps` of a job. Otherwise, the value of this property will be `null`. | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. | ### Example contents of the `github` context diff --git a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md index 7e5a2848eca8..a4abbe3e2be6 100644 --- a/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md +++ b/translations/ja-JP/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md @@ -36,6 +36,11 @@ Commits and tags have the following verification statuses, depending on whether | **Unverified** | The commit is signed but the signature could not be verified. | No verification status | The commit is not signed. +### Signature verification for rebase and merge +{% data reusables.pull_requests.rebase_and_merge_verification %} + +For more information, see "[Rebasing and merging your commits](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github#rebasing-and-merging-your-commits)." + ### Statuses with vigilant mode enabled {% data reusables.identity-and-permissions.vigilant-mode-verification-statuses %} diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md index 05d98013e98e..9ba058a987b3 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md @@ -53,7 +53,7 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y {% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security %} {% data reusables.two_fa.enable-two-factor-authentication %} -{%- ifversion fpt or ghes > 3.1 %} +{%- ifversion fpt or ghec or ghes > 3.1 %} 5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**. 6. Under "Authentication verification", do one of the following: - QR コードを、モバイルデバイスのアプリでスキャンする。 スキャン後、アプリは {% data variables.product.product_name %} で入力する 6 桁の数字を表示します。 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index f0b9ba935870..eb87c1da2fd3 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -72,7 +72,7 @@ The recommended formats explicitly define which versions are used for all direct {%- if github-actions-in-dependency-graph %} | {% data variables.product.prodname_actions %} workflows[1] | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` | {%- endif %} -{%- ifversion fpt or ghes > 3.2 or ghae %} +{%- ifversion fpt or ghec or ghes > 3.2 or ghae %} | Go modules | Go | `go.sum` | `go.mod`, `go.sum` | {%- elsif ghes = 3.2 %} | Go modules | Go | `go.mod` | `go.mod` | diff --git a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md index 8fadf02ae82e..81b210ccbe2d 100644 --- a/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md +++ b/translations/ja-JP/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/common-validation-errors-when-creating-issue-forms.md @@ -311,7 +311,6 @@ Errors with `body` will be prefixed with `body[i]` where `i` represents the zero body: - attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false ``` The error can be fixed by adding the key `type` with a valid input type as the value. For the available `body` input types and their syntaxes, see "[Syntax for {% data variables.product.prodname_dotcom %}'s form schema](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#keys)." @@ -321,7 +320,6 @@ body: - type: markdown attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false ``` ## Body[i]: `x` is not a valid input type @@ -337,7 +335,6 @@ body: - type: x attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false ``` The error can be fixed by changing `x` to one of the valid types. @@ -347,7 +344,6 @@ body: - type: markdown attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false ``` ## Body[i]: required attribute key `value` is missing @@ -363,7 +359,6 @@ body: - type: markdown attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false - type: markdown ``` @@ -374,7 +369,6 @@ body: - type: markdown attributes: value: "Thanks for taking the time to fill out this bug! If you need real-time help, join us on Discord." - preview_only: false - type: markdown attributes: value: "This is working now!" diff --git a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md index e99cae3fc8f8..1fe27aeab7c0 100644 --- a/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md +++ b/translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md @@ -19,7 +19,7 @@ shortTitle: GitHub Campus Program - Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners - Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %} -To read about how GitHub is used by educators, see [GitHub Education stories.](https://education.github.com/stories) +To read about how GitHub is used by educators, see [GitHub Education stories](https://education.github.com/stories). ## {% data variables.product.prodname_campus_program %} terms and conditions @@ -32,7 +32,7 @@ To read about how GitHub is used by educators, see [GitHub Education stories.](h - New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support. -To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices) +To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices). ## {% data variables.product.prodname_campus_program %} Application Eligibility diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md index 50e74ed37d9c..5612c62f5d11 100644 --- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md @@ -154,7 +154,7 @@ When you fork a project in order to propose changes to the original repository, 6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. 次のようになります: ```shell - $ git remote add upstream https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/Spoon-Knife.git + $ git remote add upstream https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/Spoon-Knife.git ``` 7. To verify the new upstream repository you have specified for your fork, type `git remote -v` again. フォークの URL が `origin` として、オリジナルのリポジトリの URL が `upstream` として表示されるはずです。 diff --git a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index b781425b93a6..58b21e3a35d8 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -49,15 +49,27 @@ For example, you can create a simple map: 
 ```geojson
 {
-  "type": "Polygon",
-  "coordinates": [
-      [
-          [-90,30],
-          [-90,35],
-          [-90,35],
-          [-85,35],
-          [-85,30]
-      ]
+  "type": "FeatureCollection",
+  "features": [
+    {
+      "type": "Feature",
+      "id": 1,
+      "properties": {
+        "ID": 0
+      },
+      "geometry": {
+        "type": "Polygon",
+        "coordinates": [
+          [
+              [-90,35],
+              [-90,30],
+              [-85,30],
+              [-85,35],
+              [-90,35]
+          ]
+        ]
+      }
+    }
   ]
 }
 ```
diff --git a/translations/ja-JP/content/graphql/guides/using-global-node-ids.md b/translations/ja-JP/content/graphql/guides/using-global-node-ids.md
index 48c9b7edeafe..14c968c5d8e7 100644
--- a/translations/ja-JP/content/graphql/guides/using-global-node-ids.md
+++ b/translations/ja-JP/content/graphql/guides/using-global-node-ids.md
@@ -12,7 +12,7 @@ topics:
   - API
 ---
 
-GitHubのほとんどのオブジェクト（ユーザ、Issue、プルリクエストなど）には、REST APIを使っても、GraphQL APIを使ってもアクセスできます。 [最近のアップデート](https://developer.github.com/changes/2017-12-19-graphql-node-id/)で、多くのオブジェクトの**グローバルノードID**をREST APIから見つけ、それらのIDをGraphQLの操作で使えるようになりました。
+GitHubのほとんどのオブジェクト（ユーザ、Issue、プルリクエストなど）には、REST APIを使っても、GraphQL APIを使ってもアクセスできます。 You can find the **global node ID** of many objects from within the REST API and use these IDs in your GraphQL operations. For more information, see "[Preview GraphQL API v4 Node IDs in REST API v3 resources](https://developer.github.com/changes/2017-12-19-graphql-node-id/)."
 
 {% note %}
 
diff --git a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
index 3d00a3439430..72fcea30ab34 100644
--- a/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
+++ b/translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md
@@ -50,14 +50,14 @@ When installing or publishing a Docker image, the {% data variables.product.prod
 
 ## Pushing container images
 
-This example pushes the latest version of `IMAGE-NAME`.
+This example pushes the latest version of `IMAGE_NAME`.
   ```shell
   $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
   ```
 
 This example pushes the `2.5` version of the image.
   ```shell
-  $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:2.5
+  $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:2.5
   ```
 
 When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
index 3d66e04fecfe..f9508a64877a 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md
@@ -46,5 +46,6 @@ shortTitle: About merge methods
 
 コミットのリベースを有効化する前に、以下の欠点について考慮してください:
 - リポジトリのコントリビューターは、コマンドライン上でリベースし、コンフリクトがあれば解決し、変更をプルリクエストのトピックブランチ (あるいはリモートの head ブランチ) へフォースプッシュしなければ、{% data variables.product.product_location %} 上で**リベースとマージ**という選択肢を使えるようにならないかもしれません。 フォースプッシュは、コントリビューターが他者が作業のベースとしている作業を上書きすることがないよう、慎重に行わなければなりません。 {% data variables.product.product_location %}で**リベースとマージ**の選択肢が無効化されている場合と、それを再度有効にするワークフローについてもっと知るには、[プルリクエストのマージについて](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits)を参照してください。
+- {% indented_data_reference reusables.pull_requests.rebase_and_merge_verification spaces=3 %}
 
 詳しい情報については[プルリクエストのためのコミットのリベースの設定](/articles/configuring-commit-rebasing-for-pull-requests)を参照してください。
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index 7917efae0559..077cc07f2a8f 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -70,7 +70,7 @@ For more information about each of the available branch protection settings, see
    - [**Require status checks to pass before merging**] を選択します。 ![必須ステータスチェックのオプション](/assets/images/help/repository/required-status-checks.png)
    - プルリクエストを保護されたブランチの最新コードで確実にテストしたい場合は、[**Require branches to be up to date before merging**] を選択します。 ![必須ステータスのチェックボックス、ゆるい、または厳格な](/assets/images/help/repository/protecting-branch-loose-status.png)
    - Search for status checks, selecting the checks you want to require. ![Search interface for available status checks, with list of required checks](/assets/images/help/repository/required-statuses-list.png)
-{%- ifversion fpt or ghes > 3.1 or ghae %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
 1. Optionally, select **Require conversation resolution before merging**. ![Require conversation resolution before merging option](/assets/images/help/repository/require-conversation-resolution.png)
 {%- endif %}
 1. 必要に応じて、[**Require signed commits**] を選択します。 ![[Require signed commits] オプション](/assets/images/help/repository/require-signed-commits.png)
diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
index 69922d5a5678..3383d0c373cf 100644
--- a/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
+++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md
@@ -39,7 +39,7 @@ Automatically generated release notes provide an automated alternative to manual
 8. Check the generated notes to ensure they include all (and only) the information you want to include.
 9. オプションで、コンパイルされたプログラムなどのバイナリファイルをリリースに含めるには、ドラッグアンドドロップするかバイナリボックスで手動で選択します。 ![リリースに DMG ファイルを含める](/assets/images/help/releases/releases_adding_binary.gif)
 10. リリースが不安定であり、運用準備ができていないことをユーザに通知するには、[**This is a pre-release**] を選択します。 ![リリースをプレリリースとしてマークするチェックボックス](/assets/images/help/releases/prerelease_checkbox.png)
-{%- ifversion fpt %}
+{%- ifversion fpt or ghec %}
 11. 必要に応じて、[**Create a discussion for this release**] を選択し、[**Category**] ドロップダウンメニューを選択してリリースディスカッションのカテゴリをクリックします。 ![リリースディスカッションを作成するためのチェックボックスと、カテゴリを選択するドロップダウンメニュー](/assets/images/help/releases/create-release-discussion.png)
 {%- endif %}
 12. リリースを公開する準備ができている場合は、[**Publish release**] をクリックします。 リリースの作業を後でする場合は、[**Save draft**] をクリックします。 ![[Publish release] と [Save draft] ボタン](/assets/images/help/releases/release_buttons.png)
diff --git a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
index 1e784ea6238a..1b85ea0e852b 100644
--- a/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
+++ b/translations/ja-JP/content/rest/overview/permissions-required-for-github-apps.md
@@ -41,7 +41,7 @@ GitHub Appは、デフォルトで`Read-only`メタデータ権限を持ちま
 - [`GET /orgs/:org/repos`](/rest/reference/repos#list-organization-repositories)
 - [`GET /rate_limit`](/rest/reference/rate-limit#get-rate-limit-status-for-the-authenticated-user)
 - [`GET /repos/:owner/:repo`](/rest/reference/repos#get-a-repository)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/community/profile`](/rest/reference/repository-metrics#get-community-profile-metrics)
 {% endif -%}
 - [`GET /repos/:owner/:repo/contributors`](/rest/reference/repos#list-repository-contributors)
@@ -128,7 +128,7 @@ _検索_
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/approve`](/rest/reference/actions#approve-a-workflow-run-for-a-fork-pull-request) (:write)
 {% endif -%}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
@@ -156,27 +156,27 @@ _検索_
 - [`PUT /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#set-custom-labels-for-a-self-hosted-runner-for-a-repository) (:write)
 - [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels`](/rest/reference/actions#remove-all-custom-labels-from-a-self-hosted-runner-for-a-repository) (:write)
 - [`DELETE /repos/:owner/:repo/actions/runners/:runner_id/labels/:name`](/rest/reference/actions#remove-a-custom-label-from-a-self-hosted-runner-for-a-repository) (:write)
-{% ifversion fpt or ghes -%}
+{% ifversion fpt or ghec or ghes -%}
 - [`POST /repos/:owner/:repo/actions/runners/registration-token`](/rest/reference/actions#create-a-registration-token-for-a-repository) (:write)
 - [`POST /repos/:owner/:repo/actions/runners/remove-token`](/rest/reference/actions#create-a-remove-token-for-a-repository) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#enable-automated-security-fixes) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/automated-security-fixes`](/rest/reference/repos#disable-automated-security-fixes) (:write)
 {% endif -%}
 - [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:write)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-a-repository) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-a-repository) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-a-repository) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif -%}
 {% ifversion ghes > 3.3 -%}
@@ -184,13 +184,13 @@ _検索_
 {% endif -%}
 - [`PUT /repos/:owner/:repo/topics`](/rest/reference/repos#replace-all-repository-topics) (:write)
 - [`POST /repos/:owner/:repo/transfer`](/rest/reference/repos#transfer-a-repository) (:write)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#enable-vulnerability-alerts) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/vulnerability-alerts`](/rest/reference/repos#disable-vulnerability-alerts) (:write)
 {% endif -%}
 - [`PATCH /user/repository_invitations/:invitation_id`](/rest/reference/collaborators#accept-a-repository-invitation) (:write)
@@ -226,9 +226,7 @@ _ブランチ_
 - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#add-user-access-restrictions) (:write)
 - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#set-user-access-restrictions) (:write)
 - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/users`](/rest/reference/branches#remove-user-access-restrictions) (:write)
-{% ifversion fpt or ghes or ghae -%}
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
-{% endif %}
 
 _コラボレータ_
 - [`PUT /repos/:owner/:repo/collaborators/:username`](/rest/reference/collaborators#add-a-repository-collaborator) (:write)
@@ -281,7 +279,7 @@ _トラフィック_
 - [`GET /repos/:owner/:repo/commits/:sha/check-runs`](/rest/reference/checks#list-check-runs-for-a-git-reference) (:read)
 - [`GET /repos/:owner/:repo/commits/:sha/check-suites`](/rest/reference/checks#list-check-suites-for-a-git-reference) (:read)
 
-{% ifversion fpt %}
+{% ifversion fpt or ghec %}
 ### "codespaces"に対する権限
 
 - [`GET /repos/:owner/:repo/codespaces/machines`](/rest/reference/codespaces#list-available-machine-types-for-a-repository)
@@ -289,67 +287,67 @@ _トラフィック_
 ### "contents"に対する権限
 
 - [`GET /repos/:owner/:repo/:archive_format/:ref`](/rest/reference/repos#download-a-repository-archive) (:read)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id`](/rest/reference/actions#get-a-workflow-run) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/artifacts`](/rest/reference/actions#list-workflow-run-artifacts) (:read)
 {% endif -%}
 {% ifversion fpt -%}
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/cancel`](/rest/reference/actions#cancel-a-workflow-run) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/jobs`](/rest/reference/actions#list-jobs-for-a-workflow-run) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#download-workflow-run-logs) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/actions/runs/:run_id/logs`](/rest/reference/actions#delete-workflow-run-logs) (:write)
 {% endif -%}
 {% ifversion fpt -%}
 - [`POST /repos/:owner/:repo/actions/runs/:run_id/rerun`](/rest/reference/actions#re-run-a-workflow) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/secrets`](/rest/reference/actions#list-repository-secrets) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#get-a-repository-secret) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#create-or-update-a-repository-secret) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /repos/:owner/:repo/actions/secrets/:name`](/rest/reference/actions#delete-a-repository-secret) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/secrets/public-key`](/rest/reference/actions#get-a-repository-public-key) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/workflows`](/rest/reference/actions#list-repository-workflows) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id`](/rest/reference/actions#get-a-workflow) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/actions/workflows/:workflow_id/runs`](/rest/reference/actions#list-workflow-runs) (:read)
 {% endif -%}
 - [`GET /repos/:owner/:repo/check-runs/:check_run_id`](/rest/reference/checks#get-a-check-run) (:read)
@@ -367,9 +365,7 @@ _トラフィック_
 - [`GET /repos/:owner/:repo/community/code_of_conduct`](/rest/reference/codes-of-conduct#get-the-code-of-conduct-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/compare/:base...:head`](/rest/reference/commits#compare-two-commits) (:read)
 - [`GET /repos/:owner/:repo/contents/:path`](/rest/reference/repos#get-repository-content) (:read)
-{% ifversion fpt or ghes or ghae -%}
 - [`POST /repos/:owner/:repo/dispatches`](/rest/reference/repos#create-a-repository-dispatch-event) (:write)
-{% endif -%}
 - [`POST /repos/:owner/:repo/forks`](/rest/reference/repos#create-a-fork) (:read)
 - [`POST /repos/:owner/:repo/merges`](/rest/reference/branches#merge-a-branch) (:write)
 - [`PUT /repos/:owner/:repo/pulls/:pull_number/merge`](/rest/reference/pulls#merge-a-pull-request) (:write)
@@ -382,9 +378,7 @@ _ブランチ_
 - [`POST /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#add-app-access-restrictions) (:write)
 - [`PUT /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#set-app-access-restrictions) (:write)
 - [`DELETE /repos/:owner/:repo/branches/:branch/protection/restrictions/apps`](/rest/reference/branches#remove-user-access-restrictions) (:write)
-{% ifversion fpt or ghes or ghae -%}
 - [`POST /repos/:owner/:repo/branches/:branch/rename`](/rest/reference/branches#rename-a-branch) (:write)
-{% endif %}
 
 _コミットのコメント_
 - [`PATCH /repos/:owner/:repo/comments/:comment_id`](/rest/reference/commits#update-a-commit-comment) (:write)
@@ -421,19 +415,13 @@ _インポート_
 
 _リアクション_
 
-{% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
-{% else -%}
-- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
-{% endif -%}
-{% ifversion fpt or ghes or ghae -%}
 - [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write)
 - [`DELETE /repos/:owner/:repo/issues/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-comment-reaction) (:write)
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
-{% endif %}
 
 _リリース_
 - [`GET /repos/:owner/:repo/releases`](/rest/reference/repos/#list-releases) (:read)
@@ -453,9 +441,7 @@ _リリース_
 - [`GET /repos/:owner/:repo/deployments`](/rest/reference/deployments#list-deployments) (:read)
 - [`POST /repos/:owner/:repo/deployments`](/rest/reference/deployments#create-a-deployment) (:write)
 - [`GET /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#get-a-deployment) (:read)
-{% ifversion fpt or ghes or ghae -%}
 - [`DELETE /repos/:owner/:repo/deployments/:deployment_id`](/rest/reference/deployments#delete-a-deployment) (:write)
-{% endif -%}
 - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#list-deployment-statuses) (:read)
 - [`POST /repos/:owner/:repo/deployments/:deployment_id/statuses`](/rest/reference/deployments#create-a-deployment-status) (:write)
 - [`GET /repos/:owner/:repo/deployments/:deployment_id/statuses/:status_id`](/rest/reference/deployments#get-a-deployment-status) (:read)
@@ -463,7 +449,7 @@ _リリース_
 {% ifversion fpt or ghes or ghec %}
 ### "emails"に対する権限
 
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PATCH /user/email/visibility`](/rest/reference/users#set-primary-email-visibility-for-the-authenticated-user) (:write)
 {% endif -%}
 - [`GET /user/emails`](/rest/reference/users#list-email-addresses-for-the-authenticated-user) (:read)
@@ -552,7 +538,6 @@ _リアクション_
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#list-reactions-for-an-issue) (:read)
 - [`POST /repos/:owner/:repo/issues/:issue_number/reactions`](/rest/reference/reactions#create-reaction-for-an-issue) (:write)
-{% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
 - [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write)
@@ -560,9 +545,6 @@ _リアクション_
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
-{% else -%}
-- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
-{% endif %}
 
 ### "keys"に対する権限
 
@@ -574,35 +556,35 @@ _キー_
 
 ### "members"に対する権限
 
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#list-idp-groups-for-a-team) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec  -%}
 - [`PATCH /organizations/:org_id/team/:team_id/team-sync/group-mappings`](/rest/reference/teams#create-or-update-idp-group-connections) (:write)
 {% endif -%}
 - [`GET /orgs/:org/outside_collaborators`](/rest/reference/orgs#list-outside-collaborators-for-an-organization) (:read)
 - [`PUT /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#convert-an-organization-member-to-outside-collaborator) (:write)
 - [`DELETE /orgs/:org/outside_collaborators/:username`](/rest/reference/orgs#remove-outside-collaborator-from-an-organization) (:write)
-{% ifversion fpt -%}
-- [`GET /orgs/:org/team-sync/groups`](/rest/reference/teams#list-idp-groups-for-an-organization) (:write)
+{% ifversion fpt or ghec -%}
+- [`GET /orgs/:org/team-sync/groups`](/rest/teams/team-sync#list-idp-groups-for-an-organization) (:write)
 {% endif -%}
-- [`GET /orgs/:org/team/:team_id`](/rest/reference/teams#get-a-team-by-name) (:read)
-{% ifversion fpt -%}
+- [`GET /orgs/:org/team/:team_id`](/rest/teams/teams#get-a-team-by-name) (:read)
+{% ifversion fpt or ghec -%}
 - [`GET /scim/v2/orgs/:org/Users`](/rest/reference/scim#list-scim-provisioned-identities) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`POST /scim/v2/orgs/:org/Users`](/rest/reference/scim#provision-and-invite-a-scim-user) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#get-scim-provisioning-information-for-a-user) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#set-scim-information-for-a-provisioned-user) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PATCH /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#update-an-attribute-for-a-scim-user) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /scim/v2/orgs/:org/Users/:external_identity_guid`](/rest/reference/scim#delete-a-scim-user-from-an-organization) (:write)
 {% endif %}
 
@@ -637,12 +619,10 @@ _Team_
 - [`GET /orgs/:org/teams/:team_slug`](/rest/reference/teams#get-a-team-by-name) (:read)
 - [`PATCH /teams/:team_id`](/rest/reference/teams#update-a-team) (:write)
 - [`DELETE /teams/:team_id`](/rest/reference/teams#delete-a-team) (:write)
-{% ifversion fpt or ghes or ghae -%}
 - [`GET /teams/:team_id/projects`](/rest/reference/teams#list-team-projects) (:read)
 - [`GET /teams/:team_id/projects/:project_id`](/rest/reference/teams#check-team-permissions-for-a-project) (:read)
 - [`PUT /teams/:team_id/projects/:project_id`](/rest/reference/teams#add-or-update-team-project-permissions) (:read)
 - [`DELETE /teams/:team_id/projects/:project_id`](/rest/reference/teams#remove-a-project-from-a-team) (:read)
-{% endif -%}
 - [`GET /teams/:team_id/repos`](/rest/reference/teams#list-team-repositories) (:read)
 - [`GET /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#check-team-permissions-for-a-repository) (:read)
 - [`PUT /teams/:team_id/repos/:owner/:repo`](/rest/reference/teams#add-or-update-team-repository-permissions) (:read)
@@ -656,13 +636,13 @@ _Team_
 - [`GET /orgs/:org/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization) (:read)
 - [`GET /orgs/:org/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`PUT /orgs/:org/interaction-limits`](/rest/reference/interactions#set-interaction-restrictions-for-an-organization) (:write)
 {% endif -%}
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`DELETE /orgs/:org/interaction-limits`](/rest/reference/interactions#remove-interaction-restrictions-for-an-organization) (:write)
 {% endif %}
 
@@ -730,7 +710,7 @@ _Team_
 - [`POST /repos/:owner/:repo/pages/builds`](/rest/reference/pages#request-a-github-pages-build) (:write)
 - [`GET /repos/:owner/:repo/pages/builds/:build_id`](/rest/reference/pages#get-github-pages-build) (:read)
 - [`GET /repos/:owner/:repo/pages/builds/latest`](/rest/reference/pages#get-latest-pages-build) (:read)
-{% ifversion fpt -%}
+{% ifversion fpt or ghec -%}
 - [`GET /repos/:owner/:repo/pages/health`](/rest/reference/pages#get-a-dns-health-check-for-github-pages) (:write)
 {% endif %}
 
@@ -799,7 +779,6 @@ _リアクション_
 - [`POST /repos/:owner/:repo/issues/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-an-issue-comment) (:write)
 - [`GET /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#list-reactions-for-a-pull-request-review-comment) (:read)
 - [`POST /repos/:owner/:repo/pulls/comments/:comment_id/reactions`](/rest/reference/reactions#create-reaction-for-a-pull-request-review-comment) (:write)
-{% ifversion fpt or ghes or ghae -%}
 - [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction-legacy) (:write)
 - [`DELETE /repos/:owner/:repo/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-commit-comment-reaction) (:write)
 - [`DELETE /repos/:owner/:repo/issues/:issue_number/reactions/:reaction_id`](/rest/reference/reactions#delete-an-issue-reaction) (:write)
@@ -807,9 +786,6 @@ _リアクション_
 - [`DELETE /repos/:owner/:repo/pulls/comments/:comment_id/reactions/:reaction_id`](/rest/reference/reactions#delete-a-pull-request-comment-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-reaction) (:write)
 - [`DELETE /orgs/:org/teams/:team_slug/discussions/:discussion_number/comments/:comment_number/reactions/:reaction_id`](/rest/reference/reactions#delete-team-discussion-comment-reaction) (:write)
-{% else -%}
-- [`DELETE /reactions/:reaction_id`](/rest/reference/reactions#delete-a-reaction) (:write)
-{% endif %}
 
 _リクエストされたレビュー担当者_
 - [`GET /repos/:owner/:repo/pulls/:pull_number/requested_reviewers`](/rest/reference/pulls#list-requested-reviewers-for-a-pull-request) (:read)
@@ -923,18 +899,18 @@ _Team_
 - [`GET /repos/:owner/:repo/code-scanning/alerts`](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository) (:read)
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#get-a-code-scanning-alert) (:read)
 - [`PATCH /repos/:owner/:repo/code-scanning/alerts/:alert_number`](/rest/reference/code-scanning#update-a-code-scanning-alert) (:write)
-{% ifversion fpt or ghes > 3.0 or ghae -%}
+{% ifversion fpt or ghec or ghes > 3.0 or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/alerts/:alert_number/instances`](/rest/reference/code-scanning#list-instances-of-a-code-scanning-alert) (:read)
 {% endif -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses`](/rest/reference/code-scanning#list-code-scanning-analyses-for-a-repository) (:read)
-{% ifversion fpt or ghes > 3.0 or ghae -%}
+{% ifversion fpt or ghec or ghes > 3.0 or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository) (:read)
 {% endif -%}
-{% ifversion fpt or ghes > 3.0 -%}
+{% ifversion fpt or ghec or ghes > 3.0 -%}
 - [`DELETE /repos/:owner/:repo/code-scanning/analyses/:analysis_id`](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository) (:write)
 {% endif -%}
 - [`POST /repos/:owner/:repo/code-scanning/sarifs`](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) (:write)
-{% ifversion fpt or ghes > 3.0 or ghae -%}
+{% ifversion fpt or ghec or ghes > 3.0 or ghae -%}
 - [`GET /repos/:owner/:repo/code-scanning/sarifs/:sarif_id`](/rest/reference/code-scanning#get-information-about-a-sarif-upload) (:read)
 {% endif -%}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5435 -%}
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
index 12e6a71501b8..342ad04268dd 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0-rc1.yml
@@ -87,32 +87,32 @@ sections:
           * 順序無しリストを追加するには、Macではcmd shift 8 Windows及びLinuxではctrl shift 8としてください。
 
           利用可能なショートカットの完全なリストについては「[キーボードショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。
-        - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."'
-        - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.
-        - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
-        - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
-        - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.
+        - 'Markdownフィールドで脚注構文を使えるようになりました。脚注は、上付きリンクとして表示され、クリックすると参照された情報にジャンプできます。この情報は、ドキュメントの下部の新しいセクションに表示されます。この構文に関する詳しい情報については「[基本的な執筆とフォーマットの構文](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)を参照してください。'
+        - Markdownファイルが表示される場合、ツールバーの{% octicon "code" aria-label="The code icon" %}をクリックしてMarkdownファイルのソースを表示させられるようになりました。以前は、blameビューを使ってMarkdownファイルのソースの特定の行番号にリンクしなければなりませんでした。
+        - 画像やビデオを、Markdownの本文に貼り付けるか、Markdownファイルの末尾のダイアログから選択して、Gist中のMarkdownファイルに追加できるようになりました。サポートされるファイルタイプに関する情報については「[ファイルの添付](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)」を参照してください。
+        - '{% data variables.product.prodname_ghe_server %}はWikiについて、見出しに基づいて目次を自動的に生成するようになりました。'
+        - Markdownエディタに画像やビデオなどのファイルをドラッグアンドドロップする際に、{% data variables.product.prodname_ghe_server %}はファイルの置き場所としてカーソルの場所ではなく、マウスポインタの場所を使うようになりました。
     - 
       heading: 'Issue及びPull Requestの変更'
       notes:
-        - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."'
+        - '論理OR演算子を使用して、Issueをラベルで検索できるようになりました。論理ORを使ってIssueを検索するには、カンマ構文を使ってください。たとえば`label:"good first issue","bug"`とすれば、`good first issue`もしくは`bug`というラベルの付いたすべてのIssueがリストされます。詳しい情報については「[IssueとPull Requestのフィルタリングと検索](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)」を参照してください。'
         - |
-          Improvements have been made to help teams manage code review assignments. You can now:
+          Teamによるコードレビューの割り当てを支援する改善が行われました。以下のことができるようになりました:
 
-          - Limit assignment to only direct members of the team.
-          - Continue with automatic assignment even if one or more members of the team are already requested.
-          - Keep a team assigned to review even if one or more members is newly assigned.
+          - 割り当てをTeamの直接のメンバーに限定する
+          - Teamの1人以上のメンバーが既にリクエストされていても、自動割り当てを継続する
+          - 1人以上のメンバーが新たに割り当てられていても、レビューにTeamが割り当てられたままにする
 
-          The timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.
+          Pull Requestページのタイムラインとレビュー担当者のサイドバーは、レビューリクエストが自動的に1人以上のTeamメンバーに割り当てられていれば、それを表示するようになりました。
 
-          For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).
-        - You can now filter pull request searches to only include pull requests you are directly requested to review.
-        - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+          詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/)を参照してください。
+        - Pull Requestの検索に、直接自分がレビューをリクエストされているPull Requestだけを含むようにフィルタリングできるようになりました。
+        - Pull Requestでフィルタされたファイルはビューで完全に表示されなくなり、"Files Changed（変更されたファイル）"タブに折りたたんで表示されることもなくなりました。"File Filter（ファイルフィルタ）"メニューも単純化されました。詳しい情報については「[Pull Request中のファイルのフィルタリング](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)」を参照してください。
     - 
       heading: 'GitHub Actionsの変更'
       notes:
-        - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
-        - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.'
+        - 複数のワークフローステップを1つのアクションに結合し、他のアクションを参照できる機能を含む「複合アクション」を作成できるようになりました。これによって、ワークフロー中の重複を削減しやすくなります。以前は、アクションはYAML定義中でスクリプトを使うことしかできませんでした。詳しい情報については「[複合アクションの作成](/actions/creating-actions/creating-a-composite-action)」を参照してください。
+        - 'Enterpriseレベルでのセルフホストランナーの管理に、`admin:enterprise`スコープ付きの個人アクセストークンを使う必要がなくなりました。トークンの権限を制限するには、その代わりに`manage_runners:enterprise`スコープが利用できます。このスコープを持つトークンは、[多くのREST APIエンドポイント](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise)で認証を受けて、Enterpriseのセルフホストランナーを管理できます。'
         - |
           The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:
 
diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
index 2e8df3ab315d..22d19b1679cf 100644
--- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
+++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/0.yml
@@ -79,32 +79,32 @@ sections:
           * 順序無しリストを追加するには、Macではcmd shift 8 Windows及びLinuxではctrl shift 8としてください。
 
           利用可能なショートカットの完全なリストについては「[キーボードショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。
-        - 'You can now use footnote syntax in any Markdown field. Footnotes are displayed as superscript links that you can click to jump to the referenced information, which is displayed in a new section at the bottom of the document. For more information about the syntax, see "[Basic writing and formatting syntax](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)."'
-        - When viewing Markdown files, you can now click {% octicon "code" aria-label="The code icon" %} in the toolbar to view the source of a Markdown file. Previously, you needed to use the blame view to link to specific line numbers in the source of a Markdown file.
-        - You can now add images and videos to Markdown files in gists by pasting them into the Markdown body or selecting them from the dialog at the bottom of the Markdown file. For information about supported file types, see "[Attaching files](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)."
-        - '{% data variables.product.prodname_ghe_server %} now automatically generates a table of contents for Wikis, based on headings.'
-        - When dragging and dropping files into a Markdown editor, such as images and videos, {% data variables.product.prodname_ghe_server %} now uses the mouse pointer location instead of the cursor location when placing the file.
+        - 'Markdownフィールドで脚注構文を使えるようになりました。脚注は、上付きリンクとして表示され、クリックすると参照された情報にジャンプできます。この情報は、ドキュメントの下部の新しいセクションに表示されます。この構文に関する詳しい情報については「[基本的な執筆とフォーマットの構文](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#footnotes)を参照してください。'
+        - Markdownファイルが表示される場合、ツールバーの{% octicon "code" aria-label="The code icon" %}をクリックしてMarkdownファイルのソースを表示させられるようになりました。以前は、blameビューを使ってMarkdownファイルのソースの特定の行番号にリンクしなければなりませんでした。
+        - 画像やビデオを、Markdownの本文に貼り付けるか、Markdownファイルの末尾のダイアログから選択して、Gist中のMarkdownファイルに追加できるようになりました。サポートされるファイルタイプに関する情報については「[ファイルの添付](https://docs.github.com/en/github/writing-on-github/working-with-advanced-formatting/attaching-files)」を参照してください。
+        - '{% data variables.product.prodname_ghe_server %}はWikiについて、見出しに基づいて目次を自動的に生成するようになりました。'
+        - Markdownエディタに画像やビデオなどのファイルをドラッグアンドドロップする際に、{% data variables.product.prodname_ghe_server %}はファイルの置き場所としてカーソルの場所ではなく、マウスポインタの場所を使うようになりました。
     - 
       heading: 'Issue及びPull Requestの変更'
       notes:
-        - 'You can now search issues by label using a logical OR operator. To filter issues using logical OR, use the comma syntax. For example, `label:"good first issue","bug"` will list all issues with a label of `good first issue` or `bug`. For more information, see "[Filtering and searching issues and pull requests](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)."'
+        - '論理OR演算子を使用して、Issueをラベルで検索できるようになりました。論理ORを使ってIssueを検索するには、カンマ構文を使ってください。たとえば`label:"good first issue","bug"`とすれば、`good first issue`もしくは`bug`というラベルの付いたすべてのIssueがリストされます。詳しい情報については「[IssueとPull Requestのフィルタリングと検索](/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests#about-search-terms)」を参照してください。'
         - |
-          Improvements have been made to help teams manage code review assignments. You can now:
+          Teamによるコードレビューの割り当てを支援する改善が行われました。以下のことができるようになりました:
 
-          - Limit assignment to only direct members of the team.
-          - Continue with automatic assignment even if one or more members of the team are already requested.
-          - Keep a team assigned to review even if one or more members is newly assigned.
+          - 割り当てをTeamの直接のメンバーに限定する
+          - Teamの1人以上のメンバーが既にリクエストされていても、自動割り当てを継続する
+          - 1人以上のメンバーが新たに割り当てられていても、レビューにTeamが割り当てられたままにする
 
-          The timeline and reviewers sidebar on the pull request page now indicate if a review request was automatically assigned to one or more team members.
+          Pull Requestページのタイムラインとレビュー担当者のサイドバーは、レビューリクエストが自動的に1人以上のTeamメンバーに割り当てられていれば、それを表示するようになりました。
 
-          For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/).
-        - You can now filter pull request searches to only include pull requests you are directly requested to review.
-        - Filtered files in pull requests are now completely hidden from view, and are no longer shown as collapsed in the "Files Changed" tab. The "File Filter" menu has also been simplified. For more information, see "[Filtering files in a pull request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)."
+          詳しい情報については[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-29-new-code-review-assignment-settings-and-team-filtering-improvements/)を参照してください。
+        - Pull Requestの検索に、直接自分がレビューをリクエストされているPull Requestだけを含むようにフィルタリングできるようになりました。
+        - Pull Requestでフィルタされたファイルはビューで完全に表示されなくなり、"Files Changed（変更されたファイル）"タブに折りたたんで表示されることもなくなりました。"File Filter（ファイルフィルタ）"メニューも単純化されました。詳しい情報については「[Pull Request中のファイルのフィルタリング](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request)」を参照してください。
     - 
       heading: 'GitHub Actionsの変更'
       notes:
-        - You can now create "composite actions" which combine multiple workflow steps into one action, and includes the ability to reference other actions. This makes it easier to reduce duplication in workflows. Previously, an action could only use scripts in its YAML definition. For more information, see "[Creating a composite action](/actions/creating-actions/creating-a-composite-action)."
-        - 'Managing self-hosted runners at the enterprise level no longer requires using personal access tokens with the `admin:enterprise` scope. You can instead use the new `manage_runners:enterprise` scope to restrict the permissions on your tokens. Tokens with this scope can authenticate to [many REST API endpoints](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise) to manage your enterprise''s self-hosted runners.'
+        - 複数のワークフローステップを1つのアクションに結合し、他のアクションを参照できる機能を含む「複合アクション」を作成できるようになりました。これによって、ワークフロー中の重複を削減しやすくなります。以前は、アクションはYAML定義中でスクリプトを使うことしかできませんでした。詳しい情報については「[複合アクションの作成](/actions/creating-actions/creating-a-composite-action)」を参照してください。
+        - 'Enterpriseレベルでのセルフホストランナーの管理に、`admin:enterprise`スコープ付きの個人アクセストークンを使う必要がなくなりました。トークンの権限を制限するには、その代わりに`manage_runners:enterprise`スコープが利用できます。このスコープを持つトークンは、[多くのREST APIエンドポイント](/rest/reference/enterprise-admin#list-self-hosted-runner-groups-for-an-enterprise)で認証を受けて、Enterpriseのセルフホストランナーを管理できます。'
         - |
           The audit log now includes additional events for {% data variables.product.prodname_actions %}. Audit log entries are now recorded for the following events:
 
diff --git a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
index 4d9e7ffb32b6..a4c2afad83f4 100644
--- a/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
+++ b/translations/ja-JP/data/reusables/notifications-v2/custom-notification-types.md
@@ -1,3 +1,3 @@
-{%- ifversion fpt or ghes > 3.1 or ghae-issue-4910 %}issues, pull requests, releases, security alerts, or discussions
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae-issue-4910 %}issues, pull requests, releases, security alerts, or discussions
 {%- else %}issues, pull requests, releases, or discussions
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_verification.md b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_verification.md
new file mode 100644
index 000000000000..e76a9b9e08ef
--- /dev/null
+++ b/translations/ja-JP/data/reusables/pull_requests/rebase_and_merge_verification.md
@@ -0,0 +1,4 @@
+When using the **Rebase and Merge** option on a pull request, it's important to note that the commits in the head branch are added to the base branch without commit signature verification. When you use this option, {% data variables.product.prodname_dotcom %} creates a modified commit, using the data and content of the original commit. This means that{% data variables.product.prodname_dotcom %} didn't truly create this commit, and can't therefore sign it as a generic system user.
+{% data variables.product.prodname_dotcom %} doesn't have access to the committer's private signing keys, so it can't sign the commit on the user's behalf.
+
+A workaround for this is to rebase and merge locally, and then push the changes to the pull request's base branch.
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index a3a04f21f3cf..93fdea6b65bf 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -270,9 +270,9 @@ translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liqui
 translations/ja-JP/data/reusables/education/apply-for-team.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise-accounts/actions-tab.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,Listed in localization-support#489
-translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,rendering error
 translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,Listed in localization-support#489
-translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,broken liquid tags
+translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,rendering error
 translations/ja-JP/data/reusables/enterprise-accounts/pages-tab.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags
 translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags