New translation batch for ja (#31011)

translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md

@@ -1,6 +1,6 @@
 ---
-title: Docker イメージの発行
-intro: '継続的インテグレーション（CI）の一部として、Docker Hubや{% data variables.product.prodname_registry %}といったレジストリに対しDockerイメージを公開できます。'
+title: Publishing Docker images
+intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
 redirect_from:
   - /actions/language-and-framework-guides/publishing-docker-images
   - /actions/guides/publishing-docker-images
@@ -14,61 +14,63 @@ topics:
   - Packaging
   - Publishing
   - Docker
-ms.openlocfilehash: 01f20527dedeea3685855797993187e7af462de4
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147410292'
 ---
-{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
 
-## はじめに
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
 
-このガイドでは、Dockerのビルドを実行し、DockerのイメージをDocker Hubあるいは{% data variables.product.prodname_registry %}に公開するワークフローの作成方法を紹介します。 1つのワークフローで、1つのレジストリあるいは複数のレジストリにイメージを公開できます。
+## Introduction
+
+This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
 
 {% note %}
 
-**注:** 別のサードパーティの Docker レジストリにプッシュする場合は、「[{% data variables.product.prodname_registry %} へのイメージの公開](#publishing-images-to-github-packages)」セクションの例が適切なテンプレートとして役立つことがあります。
+**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
 
 {% endnote %}
 
-## 前提条件
+## Prerequisites
 
-ワークフローの設定オプションと、ワークフローファイルの作成方法についての基本的な知識を持っておくことをおすすめします。 詳細については、「[{% data variables.product.prodname_actions %} について学ぶ](/actions/learn-github-actions)」を参照してください。
+We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
 
-以下についての基本的な理解があると役に立つでしょう。
+You might also find it helpful to have a basic understanding of the following:
 
-- 「[暗号化されたシークレット](/actions/reference/encrypted-secrets)」
-- "[ワークフローでの認証](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
-- "[{% data variables.product.prodname_container_registry %} の操作](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
-- "[Docker レジストリの操作](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
+- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
+- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
+- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
+- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
 
-## イメージの設定について
+## About image configuration
 
-このガイドは、{% data variables.product.prodname_dotcom %}リポジトリ内に保存されたDockerのイメージについての完全な定義を持っていることを前提としています。 たとえば、リポジトリにはイメージを作成するための Docker ビルドを行うのに必要な _Dockerfile_ やその他のファイルが含まれていなければなりません。
+This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
 
-このガイドでは、Docker `build-push-action` アクションを使用して Docker イメージをビルドし、1 つまたは複数の Docker レジストリにプッシュします。 詳細については、「[`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images)」を参照してください。
+{% ifversion fpt or ghec or ghes > 3.4 %}
+
+{% data reusables.package_registry.about-docker-labels %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry#labelling-container-images)."
+
+{% endif %}
+
+In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
 
 {% data reusables.actions.enterprise-marketplace-actions %}
 
-## Docker Hubへのイメージの公開
+## Publishing images to Docker Hub
 
 {% data reusables.actions.release-trigger-workflow %}
 
-以下のワークフロー例では、Docker `login-action` および `build-push-action` アクションを使用して Docker イメージをビルドし、ビルドが成功した場合は、ビルドされたイメージを Docker Hub にプッシュします。
+In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
 
-Docker Hubにプッシュするためには、Docker Hubのアカウントを持っており、Docker Hubのレジストリを作成していなければなりません。 詳細については、Docker ドキュメントの「[Docker コンテナー イメージを Docker Hub にプッシュする](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)」を参照してください。
+To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
 
-Docker Hub に必要な `login-action` オプションは次のとおりです。
-* `username` と `password`: これは Docker Hub のユーザー名とパスワードです。 ワークフローファイルに公開されないように、Docker Hub のユーザ名とパスワードをシークレットとして保存することをお勧めします。 詳細については、「[暗号化されたシークレットの作成と使用](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)」を参照してください。
+The `login-action` options required for Docker Hub are:
+* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 
-Docker Hub に必要な `metadata-action` オプションは次のとおりです。
-* `images`: ビルドして Docker Hub にプッシュする Docker イメージの名前空間と名前。
+The `metadata-action` option required for Docker Hub is:
+* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
 
-Docker Hub に必要な `build-push-action` オプションは次のとおりです。
-* `tags`: `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION` 形式の新しいイメージのタグ。 以下のとおり、単一のタグを設定することも、リストに複数のタグを指定することもできます。
-* `push`: `true` に設定した場合は、イメージが正常にビルドされると、レジストリにプッシュされます。
+The `build-push-action` options required for Docker Hub are:
+* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
+* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -110,38 +112,42 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-上記のワークフローでは、{% data variables.product.prodname_dotcom %} リポジトリをチェックアウトし、`login-action` を使用してレジストリにログインしてから、`build-push-action` アクションを使用して、リポジトリの `Dockerfile` に基づいて Docker イメージをビルドし、イメージを Docker Hub にプッシュし、タグをイメージに適用します。
+The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
 
-## {% data variables.product.prodname_registry %}へのイメージの公開
+## Publishing images to {% data variables.product.prodname_registry %}
 
-{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
+{% ifversion ghes > 3.4 %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
+{% endif %}
 
 {% data reusables.actions.release-trigger-workflow %}
 
-以下のワークフロー例では、Docker `login-action`{% ifversion fpt or ghec %}、`metadata-action`、{% endif %} および `build-push-action` アクションを使用して Docker イメージをビルドし、ビルドが成功した場合は、ビルド イメージを {% data variables.product.prodname_registry %} にプッシュします。
+In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
 
-{% data variables.product.prodname_registry %} に必要な `login-action` オプションは次のとおりです。
-* `registry`: {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %} に設定する必要があります。
-* `username`: {% raw %}`${{ github.actor }}`{% endraw %} コンテキストを使用すると、ワークフロー実行をトリガーしたユーザーのユーザー名を自動的に使用できます。 詳細については、「[コンテキスト](/actions/learn-github-actions/contexts#github-context)」を参照してください。
-* `password`: 自動的に生成された `GITHUB_TOKEN` シークレットをパスワードに使用できます。 詳細については、「[GITHUB_TOKEN を使用した認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。
+The `login-action` options required for {% data variables.product.prodname_registry %} are:
+* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
+* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
+* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
 
-{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} に必要な `metadata-action` オプションは次のとおりです。
-* `images`: ビルドする Docker イメージの名前空間と名前。
+{% ifversion fpt or ghec %}
+The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
+* `images`: The namespace and name for the Docker image you are building.
 {% endif %}
 
-{% data variables.product.prodname_registry %} に必要な `build-push-action` オプションは次のとおりです。{% ifversion fpt or ghec %}
-* `context`: ビルドのコンテキストを、指定されたパス内にあるファイルのセットとして定義します。{% endif %}
-* `push`: `true` に設定した場合は、イメージが正常にビルドされると、レジストリにプッシュされます。{% ifversion fpt or ghec %}
-* `tags` と `labels`: これらは `metadata-action` からの出力によって設定されます。{% else %}
-* `tags`: {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION` 形式で設定する必要があります。 
+The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
+* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
+* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
+* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
+* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. 
   
-   たとえば、{% data variables.product.prodname_ghe_server %} (`https://HOSTNAME/octo-org/octo-repo`) に格納されている `octo-image` という名前のイメージの場合、`tags` オプションは `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION` に設定する必要があります。
+   For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
   
-   たとえば、{% data variables.product.prodname_dotcom %} (`http://github.com/octo-org/octo-repo`) に格納されている `octo-image` という名前のイメージの場合、`tags` オプションは `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %} に設定する必要があります。 以下のとおり、単一のタグを設定することも、リストに複数のタグを指定することもできます。{% endif %}
+   For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.4 %} {% data reusables.package_registry.publish-docker-image %}
+{% ifversion fpt or ghec or ghes > 3.4 %}
+{% data reusables.package_registry.publish-docker-image %}
 
-上記のワークフローは、"リリース" ブランチへのプッシュによってトリガーされます。 GitHub リポジトリをチェックアウトし、`login-action` を使用して {% data variables.product.prodname_container_registry %} にログインします。 その後、Docker イメージのラベルとタグを抽出します。 最後に、`build-push-action` アクションを使用してイメージをビルドし、{% data variables.product.prodname_container_registry %} に公開します。
+The above workflow is triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
 
 {% else %}
 
@@ -183,16 +189,18 @@ jobs:
             {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
 ```
 
-上記のワークフローでは、{% data variables.product.product_name %} リポジトリをチェックアウトし、`login-action` を使用してレジストリにログインしてから、`build-push-action` アクションを使用して、リポジトリの `Dockerfile` に基づいて Docker イメージをビルドし、Docker レジストリにイメージをプッシュし、コミット SHA とリリース バージョンをイメージ タグとして適用します。
+The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
 {% endif %}
 
-## Docker Hubと{% data variables.product.prodname_registry %}へのイメージの公開
+## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
 
-{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
+{% ifversion ghes > 3.4 %}
+{% data reusables.package_registry.container-registry-ghes-beta %}
+{% endif %}
 
-単一のワークフローで、各レジストリに対して `login-action` および `build-push-action` アクションを使用して、Docker イメージを複数のレジストリに公開できます。
+In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
 
-次のワークフロー例では、前のセクション (「[Docker Hub へのイメージの公開](#publishing-images-to-docker-hub)」と「[{% data variables.product.prodname_registry %} へのイメージの公開](#publishing-images-to-github-packages)」) の手順を使用して、両方のレジストリにプッシュする単一のワークフローを作成します。
+The following example workflow uses the steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
 
 ```yaml{:copy}
 {% data reusables.actions.actions-not-certified-by-github-comment %}
@@ -246,5 +254,5 @@ jobs:
           labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
 ```
 
-上記のワークフローでは、{% data variables.product.product_name %} リポジトリをチェックアウトし、`login-action` を 2 回使用して両方のレジストリにログインし、`metadata-action` アクションでタグとラベルを生成します。
-その後、`build-push-action` アクションによって Docker イメージがビルドされ、Docker Hub および {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker レジストリ{% endif %}にプッシュされます。
+The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
+Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.

translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md

@@ -1,6 +1,6 @@
 ---
-title: コンテナレジストリの利用
-intro: 'Docker イメージと OCI イメージは、パッケージの名前空間 `https://{% data reusables.package_registry.container-registry-hostname %}` が使われている {% data variables.product.prodname_container_registry %} に保存して管理できます。'
+title: Working with the Container registry
+intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.'
 product: '{% data reusables.gated-features.packages %}'
 redirect_from:
   - /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
@@ -17,85 +17,82 @@ versions:
   ghec: '*'
   ghes: '>= 3.5'
 shortTitle: Container registry
-ms.openlocfilehash: fc99e2e21a647c7a1a2517de8aa68822faac496e
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '147705052'
 ---
+
 {% data reusables.package_registry.container-registry-ghes-beta %}
 
-## {% data variables.product.prodname_container_registry %} について
+## About the {% data variables.product.prodname_container_registry %}
 
 {% data reusables.package_registry.container-registry-benefits %}
 
 {% ifversion ghes > 3.4 %}
 
-{% data variables.product.product_name %} で {% data variables.product.prodname_container_registry %} を使用するには、サイト管理者が最初にインスタンスの {% data variables.product.prodname_registry %} を構成 **してから** サブドメインの分離を有効にする必要があります。 詳細については、「[エンタープライズ向けの GitHub パッケージの概要](/admin/packages/getting-started-with-github-packages-for-your-enterprise)」と「[Subdomain Isolation の有効化](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)」を参照してください。
+To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
 
 {% endif %}
 
-## {% data variables.product.prodname_container_registry %}サポートについて
+## About {% data variables.product.prodname_container_registry %} support
 
-現在のところ、{% data variables.product.prodname_container_registry %} では以下のコンテナフォーマットをサポートしています。
+The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
 
-* [Docker Image Manifest V2、Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
-* [Open Container Initiative (OCI) 仕様](https://github.com/opencontainers/image-spec)
+* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
+* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
 
-Dockerイメージをインストールあるいは公開する際には、{% data variables.product.prodname_container_registry %}はWindowsイメージのような外部レイヤーもサポートします。
+When installing or publishing a Docker image, the {% data variables.product.prodname_container_registry %} supports foreign layers, such as Windows images.
 
-## {% data variables.product.prodname_container_registry %}での認証
+## Authenticating to the {% data variables.product.prodname_container_registry %}
 
-{% ifversion fpt or ghec or ghes > 3.4 %} {% data variables.product.prodname_actions %} ワークフロー内で {% data variables.product.prodname_container_registry %} (`ghcr.io`) の認証を受けるには、最高のセキュリティとエクスペリエンスのために `GITHUB_TOKEN` を使用します。 {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} {% endif %}
+{% ifversion fpt or ghec or ghes > 3.4 %}
+To authenticate to the {% data variables.product.prodname_container_registry %} (`ghcr.io`) within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
+{% endif %}
 
-{% ifversion ghes %}次の例の `HOSTNAME` を、{% data variables.product.product_location_enterprise %} のホスト名または IP アドレスに置き換えてください。{% endif %}
+{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %}
 
 {% data reusables.package_registry.authenticate-to-container-registry-steps %}
 
-## コンテナイメージをプッシュする
+## Pushing container images
 
-この例では、最新バージョンの `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
   ```
 
-以下の例では、イメージのバージョン `2.5` をプッシュします。
+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
   ```
 
-パッケージを最初に公開する際のデフォルトの可視性はプライベートです。 可視性を変更したりアクセス権限を設定するには、「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
+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)."
 
-## コンテナイメージをプルする
+## Pulling container images
 
-### ダイジェストによるプル
+### Pull by digest
 
-常に同一のイメージを使用するため、`digest` SHA 値でプルするコンテナー イメージのバージョンを指定できます。
+To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
 
-1. `docker inspect` または `docker pull` を使用してダイジェスト SHA 値を調べ、その SHA 値を `Digest:` の後にコピーします
+1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
   ```shell
   $ docker inspect {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
   ```
-2. 必要に応じてローカルでイメージを削除します。
+2. Remove image locally as needed.
   ```shell
   $ docker rmi  {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
   ```
 
-3. イメージ名の後に `@YOUR_SHA_VALUE` を付けてコンテナー イメージをプルします。
+3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
   ```
 
-### 名前によるプル
+### Pull by name
 
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
   ```
 
-### 名前とバージョンによるプル
+### Pull by name and version
 
-名前と `1.14.1` バージョン タグにより Docker CLI でイメージをプルする例を以下に示します。
+Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:1.14.1
   > 5e35bd43cf78: Pull complete
@@ -107,7 +104,7 @@ Dockerイメージをインストールあるいは公開する際には、{% da
   > {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1
   ```
 
-### 名前と最新バージョンによるプル
+### Pull by name and latest version
 
   ```shell
   $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
@@ -117,16 +114,16 @@ Dockerイメージをインストールあるいは公開する際には、{% da
   > {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest
   ```
 
-## コンテナイメージを構築する
+## Building container images
 
-以下の例では `hello_docker` イメージを構築します。
+This example builds the `hello_docker` image:
   ```shell
   $ docker build -t hello_docker .
   ```
 
-## コンテナイメージにタグ付けする
+## Tagging container images
 
-1. タグ付けする Docker イメージの ID を調べます。
+1. Find the ID for the Docker image you want to tag.
   ```shell
   $ docker images
   > REPOSITORY                                            TAG                 IMAGE ID            CREATED             SIZE
@@ -135,7 +132,35 @@ Dockerイメージをインストールあるいは公開する際には、{% da
   > hello-world                                           latest              fce289e99eb9        16 months ago       1.84kB
   ```
 
-2. イメージ ID を使用して、Docker イメージを任意のイメージ名とホスティング先でタグ付けします。
+2. Tag your Docker image using the image ID and your desired image name and hosting destination.
   ```shell
   $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest
   ```
+
+## Labelling container images
+
+{% data reusables.package_registry.about-docker-labels %} For more information on Docker labels, see [LABEL](https://docs.docker.com/engine/reference/builder/#label) in the official Docker documentation and [Pre-Defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys) in the `opencontainers/image-spec` repository.
+
+The following labels are supported in the {% data variables.product.prodname_container_registry %}. Supported labels will appear on the package page for the image.
+
+Label | Description
+------|------------
+| `org.opencontainers.image.source` | The URL of the repository associated with the package. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package#connecting-a-repository-to-a-container-image-using-the-command-line)."
+| `org.opencontainers.image.description` | A text-only description limited to 512 characters. This description will appear on the package page, below the name of the package.
+| `org.opencontainers.image.licenses` | An SPDX license identifier such as "MIT," limited to 256 characters. The license will appear on the package page, in the "Details" sidebar. For more information, see [SPDX License List](https://spdx.org/licenses/).
+
+To add labels to an image, we recommend using the `LABEL` instruction in your `Dockerfile`. For example, if you're the user `monalisa` and you own `my-repo`, and your image is distributed under the terms of the MIT license, you would add the following lines to your `Dockerfile`:
+
+```dockerfile
+LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo
+LABEL org.opencontainers.image.description="My container image"
+LABEL org.opencontainers.image.licenses=MIT
+```
+
+Alternatively, you can add labels to an image at buildtime with the `docker build` command.
+
+```shell
+$ docker build \
+ --label "org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo" \
+ --label "org.opencontainers.image.description=My container image" \
+ --label "org.opencontainers.image.licenses=MIT"

translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md

@@ -13,6 +13,7 @@ children:
   - /about-github-sponsors-for-open-source-contributors
   - /setting-up-github-sponsors-for-your-personal-account
   - /setting-up-github-sponsors-for-your-organization
+  - /using-a-fiscal-host-to-receive-github-sponsors-payouts
   - /editing-your-profile-details-for-github-sponsors
   - /managing-your-sponsorship-goal
   - /managing-your-sponsorship-tiers

translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md

@@ -1,6 +1,6 @@
 ---
-title: Organization の GitHub スポンサーシップを設定する
-intro: 'Organizationが{% data variables.product.prodname_sponsors %}に参加すると、作業に対する報酬を得られます。'
+title: Setting up GitHub Sponsors for your organization
+intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
 redirect_from:
   - /articles/setting-up-github-sponsorship-for-your-organization
   - /articles/receiving-sponsorships-as-a-sponsored-organization
@@ -15,65 +15,84 @@ topics:
   - Sponsors profile
   - Open Source
 shortTitle: Set up for organization
-ms.openlocfilehash: d7de813453d379ae898cc26d9579e06710aab26d
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145164471'
 ---
-## {% data variables.product.prodname_sponsors %} に参加する
+
+## Joining {% data variables.product.prodname_sponsors %}
 
 {% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
 
-Organizationとして{% data variables.product.prodname_sponsors %}
-参加する招待を受け取ったら、以下のステップを実行すればスポンサードOrganizationになることができます。
+After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
 
-Organization 外の個人の共同作成者として {% data variables.product.prodname_sponsors %} に参加する方法については、「[個人アカウントの {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)」を参照してください。
+To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)."
 
-{% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %}
-3. Organization の右側にある **[待機リストに参加]** をクリックします。
-{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
+{% data reusables.sponsors.navigate-to-github-sponsors %}
+{% data reusables.sponsors.view-eligible-accounts %}
+3. To the right of your organization, click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.payout-choice %}
+  ![Screenshot of option to choose between a bank account and a fiscal host](/assets/images/help/sponsors/org-waitlist-payout-options.png)
 
-## スポンサードOrganizationプロフィールを記入する
+{% data reusables.sponsors.accept-legal-terms %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.meet-the-team %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
+## Completing your sponsored organization profile
 
-## スポンサーシップ層を作成する
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.meet-the-team %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+## Creating sponsorship tiers
 
 {% data reusables.sponsors.tier-details %}
 
 {% data reusables.sponsors.maximum-tier %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.add-welcome-message %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
 
-## 銀行口座情報をサブミットする
+## Submitting your bank information
 
-スポンサー付き Organization は、サポートされているリージョンの銀行口座で支払いを受けます。 この場合、Organization の専用銀行口座か個人の銀行口座を指定できます。 [Stripe Atlas](https://stripe.com/atlas) のようなサービスを通じて事業用の銀行口座を取得したり、[Open Collective](https://opencollective.com/) のような会計ホストに参加したりすることができます。 Organization のために {% data variables.product.prodname_sponsors %} を設定するユーザーも、サポートされている同じ地域に住んでいる必要があります。 {% data reusables.sponsors.stripe-supported-regions %}
+As a sponsored organization, you will receive payouts to a bank account in a supported region or via a fiscal host.
+
+{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
+
+If you choose to receive payouts to a bank account, your bank account can be a dedicated bank account for your organization or a personal bank account. You can get a business bank account through services like [Stripe Atlas](https://stripe.com/atlas). The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
 
 {% data reusables.sponsors.double-check-stripe-info %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
 
-Open Collective を使用した Stripe Connect の設定に関する詳しい情報については、Open Collective Docs で「[{% data variables.product.prodname_sponsors %} を設定する](https://docs.opencollective.com/help/collectives/github-sponsors)」を参照してください。
-
-## 納税情報をサブミットする
+## Submitting your tax information
 
 {% data reusables.sponsors.tax-form-information-org %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
 
-## {% data variables.product.prodname_dotcom %} アカウントで 2 要素認証 (2FA) を有効にする
+## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
 
-自分の Organization をスポンサー付き Organization にするには、{% data variables.product.product_location %} の自分のアカウントで 2FA を有効にする必要があります。 詳細については、「[2 要素認証の構成](/articles/configuring-two-factor-authentication)」を参照してください。
+Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
 
-## {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める
+## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.request-approval %}
 
 {% data reusables.sponsors.github-review-app %}
 
-## 参考資料
+## Further reading
 
-- 「[{% data variables.product.prodname_sponsors %} について](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)」
-- 「[{% data variables.product.prodname_sponsors %} スポンサーを通じてスポンサーシップを獲得する](/sponsors/receiving-sponsorships-through-github-sponsors)」
+- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
+- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"

translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md

@@ -1,6 +1,6 @@
 ---
-title: 個人アカウントの GitHub スポンサーの設定
-intro: 'スポンサード開発者になるには、{% data variables.product.prodname_sponsors %} に参加して、スポンサード開発者プロフィールに必要事項をすべて記入し、スポンサーシップ層を作成し、銀行口座と税に関する情報を送信し、{% data variables.product.product_location %} のアカウントで 2 要素認証を有効にします。'
+title: Setting up GitHub Sponsors for your personal account
+intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.'
 redirect_from:
   - /articles/becoming-a-sponsored-developer
   - /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
@@ -14,62 +14,82 @@ topics:
   - User account
   - Sponsors profile
 shortTitle: Set up for personal account
-ms.openlocfilehash: 288dd5ab53d1a27b7f97ccf9429973a668d8f72b
-ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
-ms.translationtype: HT
-ms.contentlocale: ja-JP
-ms.lasthandoff: 09/05/2022
-ms.locfileid: '145164815'
 ---
-## {% data variables.product.prodname_sponsors %} に参加する
+
+## Joining {% data variables.product.prodname_sponsors %}
 
 {% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
 
-{% data variables.product.prodname_sponsors %} に組織として参加する方法については、「[組織の {% data variables.product.prodname_sponsors %} を設定する](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)」を参照してください。
+To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
 
 {% data reusables.sponsors.navigate-to-github-sponsors %}
-2. Organization のオーナーの場合は、適格なアカウントが複数あります。 **[適格なアカウントの表示]** をクリックし、アカウントの一覧で個人アカウントを探します。
-3. **[順番待ちリストに登録する]** をクリックします。
-{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
+2. If you are an organization owner, you have more than one eligible account. Click **Get sponsored**, then in the list of accounts, find your personal account.
+  ![Screenshot of the Get sponsored button](/assets/images/help/sponsors/get-sponsored.png)
+3. Click **Join the waitlist**.
+{% data reusables.sponsors.contact-info %}
+{% data reusables.sponsors.payout-choice %}
+  ![Screenshot of option to choose between a bank account and a fiscal host](/assets/images/help/sponsors/user-waitlist-payout-options.png)
 
-サポートされている地域で銀行口座をお持ちであれば、{% data variables.product.prodname_dotcom %} は 2 週間以内に申請をレビューします。
+{% data reusables.sponsors.accept-legal-terms %}
 
-## スポンサード開発者プロフィールを記入する
+If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
 
-{% data variables.product.prodname_dotcom %} で申請がレビューされたら、ユーザがあなたのスポンサーになれるようにスポンサード開発者プロフィールを設定できます。
+## Completing your sponsored developer profile
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
+After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
 
-## スポンサーシップ層を作成する
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-profile-tab %}
+{% data reusables.sponsors.short-bio %}
+{% data reusables.sponsors.add-introduction %}
+{% data reusables.sponsors.edit-featured-work %}
+{% data reusables.sponsors.opt-in-to-being-featured %}
+{% data reusables.sponsors.save-profile %}
+
+## Creating sponsorship tiers
 
 {% data reusables.sponsors.tier-details %}
 
 {% data reusables.sponsors.maximum-tier %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
+{% data reusables.sponsors.click-add-tier %}
+{% data reusables.sponsors.tier-price-description %}
+{% data reusables.sponsors.add-welcome-message %}
+{% data reusables.sponsors.save-tier-draft %}
+{% data reusables.sponsors.review-and-publish-tier %}
+{% data reusables.sponsors.add-more-tiers %}
 
-## 銀行口座情報をサブミットする
+## Submitting your bank information
 
-サポートされている地域にお住まいの場合は、次の手順に従って Stripe Connect アカウントを作成し、銀行口座情報をサブミットできます。 在住している地位と、銀行口座の地域は一致している必要があります。 {% data reusables.sponsors.stripe-supported-regions %}
+As a sponsored user, you will receive payouts to a bank account in a supported region or via a fiscal host.
+
+{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
+
+If you choose to receive payouts to a bank account, your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
 
 {% data reusables.sponsors.double-check-stripe-info %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.create-stripe-account %}
 
-## 納税情報をサブミットする
+## Submitting your tax information
 
 {% data reusables.sponsors.tax-form-information-dev %}
 
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
+{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
+{% data reusables.sponsors.overview-tab %}
+{% data reusables.sponsors.tax-form-link %}
 
-## {% data variables.product.prodname_dotcom %} アカウントで 2 要素認証 (2FA) を有効にする
+## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
 
-スポンサード開発者になるには、{% data variables.product.product_location %} でアカウントの 2FA を有効にする必要があります。 詳細については、「[2 要素認証の構成](/articles/configuring-two-factor-authentication)」を参照してください。
+Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
 
-## {% data variables.product.prodname_dotcom %} に申請をサブミットして承認を求める
+## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
 
 {% data reusables.sponsors.navigate-to-sponsors-dashboard %}
-4. **[承認の要求]** をクリックします。
-  ![[承認の要求]](/assets/images/help/sponsors/request-approval-button.png) ボタン
+4. Click **Request approval**.
+  ![Request approval button](/assets/images/help/sponsors/request-approval-button.png)
 
 {% data reusables.sponsors.github-review-app %}

translations/ja-JP/data/features/GH-advisory-db-erlang-support.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #6207.
+# We have added support for Elixir advisories to the Advisory Database.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6207'

translations/ja-JP/data/features/GH-advisory-db-supports-malware.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #7088 GitHub Advisory Database now supports advisories for malware
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-7088'

translations/ja-JP/data/features/actions-cache-list-delete-apis.yml

@@ -0,0 +1,8 @@
+# Reference: #7340
+# Extends actions-cache-management.yml (Issue #6154)
+# Documentation for Actions cache list and delete APIs
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '> 3.6'
+  ghae: 'issue-7340'

translations/ja-JP/data/features/actions-cache-management.yml

@@ -0,0 +1,7 @@
+# Reference: #6154
+# Documentation for Actions cache management APIs (initial ship)
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '3.4 より新しいバージョン'
+  ghae: 'issue-6154'

translations/ja-JP/data/features/actions-cache-policy-apis.yml

@@ -0,0 +1,5 @@
+# Reference: #6456
+# APIs to set default and max cache sizes. Only for GHES.
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-6456'

translations/ja-JP/data/features/actions-caching.yml

@@ -0,0 +1,7 @@
+# Reference: #6456
+# General versioning for caching feature for Actions, newly added to GHES in 3.5
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6456'

translations/ja-JP/data/features/actions-hosted-runners.yml

@@ -0,0 +1,5 @@
+# Reference: #6458
+# Larger GitHub-hosted runners
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/actions-inherit-secrets-reusable-workflows.yml

@@ -0,0 +1,7 @@
+# Reference: #6920
+# Documentation for inheriting secrets from the calling workflow
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.6'
+  ghae: 'issue-6920'

translations/ja-JP/data/features/actions-job-summaries.yml

@@ -0,0 +1,7 @@
+# Reference: #6405
+# Documentation for job summaries for jobs on the workflow run summary page.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6405'

translations/ja-JP/data/features/actions-node16-action.yml

@@ -0,0 +1,7 @@
+# Reference: #6447
+# Versions of actions used in workflows have been updated to their Node 16 version.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6447'

translations/ja-JP/data/features/actions-oidc-hardening-config.yml

@@ -0,0 +1,6 @@
+# Reference: #7336
+# General versioning for oidc hardening options
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'

translations/ja-JP/data/features/actions-reusable-workflow-matrix.yml

@@ -0,0 +1,7 @@
+# Reference: #7094
+# Documentation for allowing matrix jobs to call reusable workflows.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7094'

translations/ja-JP/data/features/actions-runner-arch-envvars.yml

@@ -0,0 +1,7 @@
+# Reference: #5727
+# Documentation for new runner 'arch' environment variables set by the `runner` app.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5727'

translations/ja-JP/data/features/actions-stable-actor-ids.yml

@@ -0,0 +1,7 @@
+# Issue 7387
+# Differentiating triggering actor from executing actor
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7387'

translations/ja-JP/data/features/actions-starter-template-ui.yml

@@ -0,0 +1,7 @@
+# Reference: #5169.
+# Documentation for the Actions starter template UI updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
+  ghae: 'issue-5169'

translations/ja-JP/data/features/actions-unified-inputs.yml

@@ -0,0 +1,6 @@
+# Issue 6921
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6921'

translations/ja-JP/data/features/actions-workflow-policy.yml

@@ -0,0 +1,5 @@
+# Reference: #6478.
+# Versioning for enterprise/org/repo policy settings for reusable workflow use.
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/allow-actions-to-approve-pr-with-ent-repo.yml

@@ -0,0 +1,7 @@
+# Reference: #6926.
+# Versioning for enterprise/repository policy settings for workflow PR creation or approval permission. This is only the enterprise and repo settings! For the previous separate ship for the org setting (that only overed approvals), see the allow-actions-to-approve-pr flag.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6926'

translations/ja-JP/data/features/allow-actions-to-approve-pr.yml

@@ -0,0 +1,7 @@
+# Reference: #6926.
+# Versioning for org policy settings for workflow PR approval permission. This is only org setting! For the later separate ship for the enterprise and repo setting, see the allow-actions-to-approve-pr-with-ent-repo flag.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6926'

translations/ja-JP/data/features/audit-data-retention-tab.yml

@@ -0,0 +1,5 @@
+# Reference #5104
+# Documentation for the "Audit data retention" tab in the enterprise audit log
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5104'

translations/ja-JP/data/features/audit-log-sso-response-events.yml

@@ -0,0 +1,6 @@
+# Documentation for adding business.sso_response and org.sso_repsonse
+
+versions:
+  ghec: '*'
+  ghes: '>=3.8'
+  ghae: 'issue-7939'

translations/ja-JP/data/features/audit-log-streaming.yml

@@ -0,0 +1,5 @@
+# Reference: #7055
+# Documentation for audit log streaming
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'

translations/ja-JP/data/features/autolink-reference-alphanumeric.yml

@@ -0,0 +1,7 @@
+# Reference: #7370.
+# Versioning for autolinks being able to accept alphanumeric chars.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7370'

translations/ja-JP/data/features/blame-ignore-revs.yml

@@ -0,0 +1,6 @@
+# Reference: #6378.
+# Documentation for the `.git-blame-ignore-revs` file and the blame view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'

translations/ja-JP/data/features/build-pages-with-actions.yml

@@ -0,0 +1,5 @@
+# Issue 7584
+# Building Pages sites with Actions [GA]
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/bypass-branch-protections.yml

@@ -0,0 +1,7 @@
+# Issue: 6667
+# Description: Allow merging pull requests without complying with branch protection rules.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6667'

translations/ja-JP/data/features/classic-project-visibility-permissions-or-projects-v2.yml

@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects /OR/ Projects V2
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7720'

translations/ja-JP/data/features/classic-project-visibility-permissions.yml

@@ -0,0 +1,7 @@
+# Issue 7720
+# Organization owners can restrict public classic projects.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7720'

translations/ja-JP/data/features/code-scanning-exclude-queries-from-analysis.yml

@@ -0,0 +1,7 @@
+# Issue 7617
+# Users can easily exclude CodeQL queries from code scanning analyses - [GA]
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7617'

translations/ja-JP/data/features/code-scanning-pr-conversations-tab.yml

@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-5895'

translations/ja-JP/data/features/code-scanning-task-lists.yml

@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-5036'

translations/ja-JP/data/features/codeowners-errors.yml

@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6078'

translations/ja-JP/data/features/codeql-action-debug-logging.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #2499 in the codeql-core repository, and issue #7626 in the docs-content repository
+# We have added one-click re-running in debug mode for code scanning CodeQL.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7626'

translations/ja-JP/data/features/codeql-ml-queries.yml

@@ -0,0 +1,6 @@
+# Reference: #5604.
+# Documentation for the beta release of CodeQL queries boosted by machine learning
+# to generate experiemental alerts in code scanning.
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/codeql-packs.yml

@@ -0,0 +1,5 @@
+# Reference: #4702.
+# Documentation for the CodeQL package manager and CodeQL packs.
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/codeql-runner-supported.yml

@@ -0,0 +1,5 @@
+# Tracking deprecation of CodeQL runner
+# https://github.blog/changelog/2022-04-05-codeql-runner-is-now-deprecated/
+
+versions:
+  ghes: '<=3.3'

translations/ja-JP/data/features/command-palette.yml

@@ -0,0 +1,5 @@
+# Reference: #5199.
+# Documentation for the Command palette.
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/comment-dismissed-code-scanning-alert.yml

@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-2191'

translations/ja-JP/data/features/commit-signoffs.yml

@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6049'

translations/ja-JP/data/features/commit-tree-view.yml

@@ -0,0 +1,7 @@
+# Issue 6662
+# Commit file tree view
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6662'

translations/ja-JP/data/features/container-hooks.yml

@@ -0,0 +1,6 @@
+# Reference: #7070
+# Actions Runner Container Hooks
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-7070'

translations/ja-JP/data/features/copilot.yml

@@ -0,0 +1,3 @@
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/create-branch-from-overview.yml

@@ -0,0 +1,5 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6670'

translations/ja-JP/data/features/custom-pattern-dry-run-ga.yml

@@ -0,0 +1,5 @@
+# Secret scanning: custom pattern dry run GA #7527
+versions:
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7527'

translations/ja-JP/data/features/custom-repository-roles.yml

@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6271'

translations/ja-JP/data/features/debug-reruns.yml

@@ -0,0 +1,7 @@
+# Issue 6629
+# Enabling debug logging when re-running jobs or workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6629'

translations/ja-JP/data/features/default-merge-squash-commit-message.yml

@@ -0,0 +1,7 @@
+# Reference: issue #7597
+# Admin can control default PR merge/ squash commit messages
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7597'

translations/ja-JP/data/features/delete-code-scanning-alerts.yml

@@ -0,0 +1,5 @@
+# Tracking removing ability to delete code scanning alerts: ghae-issue-6776
+
+versions:
+  ghae: '*'
+  ghes: '<3.6'

translations/ja-JP/data/features/dependabot-alerts-development-label.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #6631 - Dependabot alerts: surface information about development dependencies - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6631'

translations/ja-JP/data/features/dependabot-alerts-dismissal-comment.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #7673 - Dependabot alerts: optional comment with dismissal - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7673'

translations/ja-JP/data/features/dependabot-alerts-vulnerable-calls.yml

@@ -0,0 +1,5 @@
+# Reference: Issue #6076 introduction of label for "vulnerable calls" in Dependabot alerts
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghae: 'issue-6076'

translations/ja-JP/data/features/dependabot-bulk-alerts.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #6076 ability to dismiss or re-open multiple Dependabot alerts
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6628'

translations/ja-JP/data/features/dependabot-grouped-dependencies.yml

@@ -0,0 +1,7 @@
+# Reference: #6913
+# Dependabot support for TypeScript @types/*
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6913'

translations/ja-JP/data/features/dependabot-most-important-sort-option.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #7510 - Dependabot alerts: "Most important" sort (prioritization score) - [GA]
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7510'

translations/ja-JP/data/features/dependabot-settings-update-37.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #7044 Update repository settings for Dependabot to include shortcut for Version updates
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-7044'

translations/ja-JP/data/features/dependabot-updates-github-connect.yml

@@ -0,0 +1,3 @@
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5867'

translations/ja-JP/data/features/dependency-graph-rust-support.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #6964 Support for Rust manifest parsing in Dependency graph
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-6964'

translations/ja-JP/data/features/dependency-review-action-configuration.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #7061 Configuring the dependency review action - [Public Beta]
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.5'
+  ghae: 'issue-7061'

translations/ja-JP/data/features/dependency-review-action-ghes.yml

@@ -0,0 +1,4 @@
+# Reference: Issue #7753 Dependency review action has shipped with GHES 3.6 and needs admin docs
+versions:
+  ghes: '>3.5'
+  ghae: 'issue-7753'

translations/ja-JP/data/features/dependency-review-action-licenses.yml

@@ -0,0 +1,4 @@
+# Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/dependency-submission-api.yml

@@ -0,0 +1,7 @@
+# Reference: #6397
+# Documentation for dependency submission API (beta)
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6397'

translations/ja-JP/data/features/device-flow-is-opt-in.yml

@@ -0,0 +1,6 @@
+# docs-content 6307. OAuth device auth flow is opt in.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>3.4'
+  ghae: 'issue-6307'

translations/ja-JP/data/features/discussions.yml

@@ -0,0 +1,4 @@
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'

translations/ja-JP/data/features/docker-ghcr-enterprise-migration.yml

@@ -0,0 +1,4 @@
+# Reference: #7360
+# Documentation for migration from Docker registry to Container registry for enterprise products
+versions:
+  ghes: '>= 3.6'

translations/ja-JP/data/features/enable-git-events.yml

@@ -0,0 +1,5 @@
+# Reference: #7283
+# Documentation for enabling Git events in the audit log
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-7283'

translations/ja-JP/data/features/enterprise-membership-view-improvements.yml

@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6344'

translations/ja-JP/data/features/enterprise-namespace-repo-setting.yml

@@ -0,0 +1,6 @@
+# Reference: #7757
+# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+ and GHAE 3.7+ users
+versions:
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7757'

translations/ja-JP/data/features/enterprise-owner-join-org.yml

@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-5740'

translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml

@@ -0,0 +1,6 @@
+# Reference: Issue #5741 in docs-content
+# Documentation for enterprise owners UI updates
+versions:
+  ghes: '>=3.4'
+  ghae: 'issue-5741'
+  ghec: '*'

translations/ja-JP/data/features/file-finder-exclusion-controls.yml

@@ -0,0 +1,7 @@
+# Reference: Issue #7579 - Improved file finder exclusion controls
+
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7579'

translations/ja-JP/data/features/fixed-width-font-gfm-fields.yml

@@ -0,0 +1,7 @@
+# Reference: #5278.
+# Documentation for the fixed-width font support for markdown fields.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5278'

translations/ja-JP/data/features/for-you-feed.yml

@@ -0,0 +1,6 @@
+# Issues 4834 and 5722
+# New feed for personal dashboards and option to follow organizations
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'

translations/ja-JP/data/features/geoJSON-with-MapBox.yml

@@ -0,0 +1,5 @@
+# Reference: #7429
+# Dotcom now uses Azure maps for geoJSON, but GHES/AE will still use the existing MapBox system
+versions:
+  ghes: '*'
+  ghae: '*'

translations/ja-JP/data/features/ghas-enablement-webhook.yml

@@ -0,0 +1,5 @@
+# docs-content 7314. GHAS enablement webhook
+versions:
+  ghec: '*'
+  ghes: '>= 3.6'
+  ghae: 'issue-7314'

translations/ja-JP/data/features/ghe-announce-dismiss.yml

@@ -0,0 +1,5 @@
+# Reference: #2221.
+# Documentation for dismissing GHES announcement banner
+versions:
+  ghes: '>=3.6'
+  ghae: 'issue-6764'

translations/ja-JP/data/features/git-events-audit-log.yml

@@ -0,0 +1,6 @@
+# Reference: #6724
+# Documentation for Git events in the audit log
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6724'

translations/ja-JP/data/features/github-actions-in-dependency-graph.yml

@@ -0,0 +1,7 @@
+# Reference: #5813.
+# Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
+versions:
+  fpt: '*'
+  ghae: 'issue-5813'
+  ghes: '>3.4'
+  ghec: '*'

translations/ja-JP/data/features/github-runner-dashboard.yml

@@ -0,0 +1,3 @@
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/githubdev-editor.yml

@@ -0,0 +1,5 @@
+# Reference: #4918, #7438.
+# Documentation for the github.dev web-based editor
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/innersource-fork-policies.yml

@@ -0,0 +1,7 @@
+# Reference: #6035 #6036 #6037
+# Documentation for enterprise policies that define where forks can be created.
+
+versions:
+  ghec: '*'
+  ghes: '>3.6'
+  ghae: 'issue-6035'

translations/ja-JP/data/features/integration-branch-protection-exceptions.yml

@@ -0,0 +1,7 @@
+# Reference: #6665
+# GitHub Apps are supported as actors in all types of exceptions to branch protections
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.6'
+  ghae: 'issue-6665'

translations/ja-JP/data/features/internal-actions.yml

@@ -0,0 +1,4 @@
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-5610'

translations/ja-JP/data/features/ip-allow-list-address-check.yml

@@ -0,0 +1,3 @@
+versions:
+  ghec: '*'
+  ghae: 'issue-7818'

translations/ja-JP/data/features/ip-exception-list.yml

@@ -0,0 +1,2 @@
+versions:
+  ghes: '>=3.5'

translations/ja-JP/data/features/issue-close-reasons.yml

@@ -0,0 +1,7 @@
+# Issues 6363
+# Closed issue states
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6363'

translations/ja-JP/data/features/job-hooks-for-runners.yml

@@ -0,0 +1,7 @@
+# Reference: #6530
+# Running scripts before or after a job
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6530'

translations/ja-JP/data/features/keyboard-shortcut-accessibility-setting.yml

@@ -0,0 +1,7 @@
+# Reference: #4999.
+# Documentation for the security manager org-level role
+versions:
+  fpt: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5430'
+  ghec: '*'

translations/ja-JP/data/features/math-fenced-blocks.yml

@@ -0,0 +1,7 @@
+# Reference: #7471.
+# Documentation for fenced math blocks in markdown.
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7471'

translations/ja-JP/data/features/math.yml

@@ -0,0 +1,7 @@
+# Issues 6054
+# Math support using LaTeX syntax
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6054'

translations/ja-JP/data/features/mermaid.yml

@@ -0,0 +1,7 @@
+# Issues 5812 and 6172, also 6411
+# Mermaid syntax support, also ASCII STL and geoJSON/topoJSON syntax support
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-6172'

translations/ja-JP/data/features/motion-management.yml

@@ -0,0 +1,7 @@
+# Issue 6523
+# Support for customizing the automatic playback of animated images in the web interface
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6523'

translations/ja-JP/data/features/multiple-accounts-one-workstation.yml

@@ -0,0 +1,6 @@
+# Issue #7330
+# Documentation for managing multiple GitHub accounts on one workstation
+
+versions:
+  fpt: '*'
+  ghec: '*'

translations/ja-JP/data/features/nested-reusable-workflow.yml

@@ -0,0 +1,7 @@
+# Issues 7093
+# Reusable workflows can call other reusable workflows
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.7'
+  ghae: 'issue-7093'

translations/ja-JP/data/features/oidc-for-emu.yml

@@ -0,0 +1,5 @@
+# Issues 6495 and 6494
+# OIDC/CAP for Enterprise Managed Users
+versions:
+  ghec: '*'
+  ghae: 'issue-6495'

translations/ja-JP/data/features/only-notify-requested-members.yml

@@ -0,0 +1,7 @@
+# Issue #5108
+# Documentation for the "Only notify requested team members" option in the code review settings
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.4'
+  ghae: 'issue-5108'