diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md index 2f31955447..3ab2e1c147 100644 --- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md +++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md @@ -49,7 +49,7 @@ You can also view whether an enterprise owner has a specific role in the organiz | Enterprise owner | Organization owner | Able to configure organization settings and manage access to the organization's resources through teams, etc. | | Enterprise owner | Organization member | Able to access organization resources and content, such as repositories, without access to the organization's settings. | -To review all roles in an organization, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% ifversion ghec %} An organization member can also have a custom role for a specific repository. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %} +To review all roles in an organization, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." {% if custom-repository-roles %} An organization member can also have a custom role for a specific repository. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %} For more information about the enterprise owner role, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)." diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md index b3ce456811..a57f818201 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md @@ -22,7 +22,7 @@ shortTitle: Build & test Java & Gradle ## はじめに -このガイドは、Gradleビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 +このガイドは、Gradleビルドシステムを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} @@ -110,12 +110,16 @@ steps: arguments: -b ci.gradle package ``` +{% if actions-caching %} + ## 依存関係のキャッシング -When using {% data variables.product.prodname_dotcom %}-hosted runners, your build dependencies can be cached to speed up your workflow runs. After a successful run, the `gradle/gradle-build-action` caches important parts of the Gradle user home directory. In future jobs, the cache will be restored so that build scripts won't need to be recompiled and dependencies won't need to be downloaded from remote package repositories. +Your build dependencies can be cached to speed up your workflow runs. After a successful run, the `gradle/gradle-build-action` caches important parts of the Gradle user home directory. In future jobs, the cache will be restored so that build scripts won't need to be recompiled and dependencies won't need to be downloaded from remote package repositories. Caching is enabled by default when using the `gradle/gradle-build-action` action. For more information, see [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action#caching). +{% endif %} + ## 成果物としてのワークフローのデータのパッケージ化 ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md index 2240d69685..20f57af5d3 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md @@ -22,7 +22,7 @@ shortTitle: Build & test Java with Maven ## はじめに -このガイドは、ソフトウェアプロジェクト管理ツールのMavenを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 CIワークフローを拡張して、ファイルをキャッシュし、ワークフローの実行による成果物をアップロードするようにもできます。 +このガイドは、ソフトウェアプロジェクト管理ツールのMavenを使ってJavaのプロジェクトのための継続的インテグレーション（CI）を実行するワークフローを作成する方法を紹介します。 作成するワークフローによって、Pull Requestに対するコミットがデフォルトブランチに対してビルドあるいはテストの失敗を引き起こしたことを見ることができるようになります。このアプローチは、コードが常に健全であることを保証するための役に立ちます。 You can extend your CI workflow to {% if actions-caching %}cache files and{% endif %} upload artifacts from a workflow run. {% ifversion ghae %} {% data reusables.actions.self-hosted-runners-software %} @@ -99,9 +99,11 @@ steps: run: mvn --batch-mode --update-snapshots verify ``` +{% if actions-caching %} + ## 依存関係のキャッシング -{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化できます。 実行に成功した後、ローカルのMavenリポジトリがGitHub Actionsのインフラストラクチャ上に保存されます。 その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. +ワークフローの実行速度を上げるために、依存関係をキャッシュすることもできます。 After a successful run, your local Maven repository will be stored in a cache. その後のワークフローの実行では、キャッシュがリストアされ、依存関係をリモートのMavenリポジトリからダウンロードする必要がなくなります。 You can cache dependencies simply using the [`setup-java` action](https://github.com/marketplace/actions/setup-java-jdk) or can use [`cache` action](https://github.com/actions/cache) for custom and more advanced configuration. ```yaml{:copy} steps: @@ -118,6 +120,8 @@ steps: このワークフローは、ランナーのホームディレクトリ内の`.m2`ディレクトリにあるローカルのMavenリポジトリの内容を保存します。 キャッシュのキーは_pom.xml_の内容をハッシュしたものになるので、_pom.xml_が変更されればキャッシュは無効になります。 +{% endif %} + ## 成果物としてのワークフローのデータのパッケージ化 ビルドが成功し、テストがパスした後には、結果のJavaのパッケージをビルドの成果物としてアップロードすることになるかもしれません。 そうすれば、ビルドされたパッケージをワークフローの実行の一部として保存することになり、それらをダウンロードできるようになります。 成果物によって、Pull Requestをマージする前にローカルの環境でテスト及びデバッグしやすくなります。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md index b80a4993ce..1b9355a5dc 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-net.md @@ -120,7 +120,7 @@ steps: run: dotnet add package Newtonsoft.Json --version 12.0.1 ``` -{% ifversion fpt or ghec %} +{% if actions-caching %} ### 依存関係のキャッシング diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md index bf6c97f509..4ac3ef0254 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-nodejs.md @@ -136,7 +136,7 @@ Node.jsのバージョンを指定しなかった場合、{% data variables.prod {% data variables.product.prodname_dotcom %}ホストランナーには、依存関係マネージャーのnpmとYarnがインストールされています。 コードのビルドとテストに先立って、npmやYarnを使ってワークフロー中で依存関係をインストールできます。 Windows及びLinuxの{% data variables.product.prodname_dotcom %}ホストランナーには、Grunt、Gulp、Bowerもインストールされています。 -{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} ### npmの利用例 @@ -228,9 +228,11 @@ steps: always-auth=true ``` +{% if actions-caching %} + ### 依存関係のキャッシングの例 -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node). +You can cache and restore the dependencies using the [`setup-node` action](https://github.com/actions/setup-node). The following example caches dependencies for npm. @@ -278,7 +280,9 @@ steps: - run: pnpm test ``` -If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "Caching dependencies to speed up workflows". +If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). 詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)」を参照してください。 + +{% endif %} ## コードのビルドとテスト diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md index 0f0f21b5d4..2c0d8a5a2d 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-powershell.md @@ -104,7 +104,7 @@ jobs: {% endnote %} -{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} たとえば以下のジョブは、`SqlServer`及び`PSScriptAnalyzer`モジュールをインストールします。 @@ -128,9 +128,11 @@ jobs: {% endnote %} +{% if actions-caching %} + ### 依存関係のキャッシング -{% data variables.product.prodname_dotcom %} ホストランナーを使用する場合、一意のキーを使用してPowerShellの依存関係をキャッシュし、[`cache`](https://github.com/marketplace/actions/cache)アクションで将来のワークフローを実行するときに依存関係を復元できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +You can cache PowerShell dependencies using a unique key, which allows you to restore the dependencies for future workflows with the [`cache`](https://github.com/marketplace/actions/cache) action. 詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)」を参照してください。 PowerShellは、ランナーのオペレーティングシステムによって依存関係を様々な場所にキャッシュします。 たとえば以下のUbuntuの例で使われる`path`の場所は、Windowsオペレーティングシステムの場合とは異なります。 @@ -151,6 +153,8 @@ steps: Install-Module SqlServer, PSScriptAnalyzer -ErrorAction Stop ``` +{% endif %} + ## コードのテスト ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md index 9b72dad4e9..d106d62269 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-python.md @@ -197,7 +197,7 @@ jobs: {% data variables.product.prodname_dotcom %}ホストランナーには、パッケージマネージャーのpipがインストールされています。 コードのビルドとテストに先立って、pipを使ってパッケージレジストリのPyPIから依存関係をインストールできます。 たとえば以下のYAMLは`pip`パッケージインストーラーと`setuptools`及び`wheel`パッケージのインストールやアップグレードを行います。 -{% data variables.product.prodname_dotcom %}ホストランナーを使用する場合、依存関係をキャッシュしてワークフローの実行を高速化することもできます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% if actions-caching %}You can also cache dependencies to speed up your workflow. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} ```yaml{:copy} steps: @@ -227,9 +227,11 @@ steps: pip install -r requirements.txt ``` +{% if actions-caching %} + ### 依存関係のキャッシング -When using {% data variables.product.prodname_dotcom %}-hosted runners, you can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). +You can cache and restore the dependencies using the [`setup-python` action](https://github.com/actions/setup-python). The following example caches dependencies for pip. @@ -244,10 +246,12 @@ steps: - run: pip test ``` -By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "Caching packages dependencies" in the `setup-python` actions README. +By default, the `setup-python` action searches for the dependency file (`requirements.txt` for pip or `Pipfile.lock` for pipenv) in the whole repository. For more information, see "[Caching packages dependencies](https://github.com/actions/setup-python#caching-packages-dependencies)" in the `setup-python` README. If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). ランナーのオペレーティングシステムによって、pipは依存関係を様々な場所にキャッシュします。 The path you'll need to cache may differ from the Ubuntu example above, depending on the operating system you use. For more information, see [Python caching examples](https://github.com/actions/cache/blob/main/examples.md#python---pip) in the `cache` action repository. +{% endif %} + ## コードのテスト ローカルで使うのと同じコマンドを、コードのビルドとテストに使えます。 diff --git a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md index aa5b6be35c..a1e67daf87 100644 --- a/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md +++ b/translations/ja-JP/content/actions/automating-builds-and-tests/building-and-testing-ruby.md @@ -144,9 +144,11 @@ steps: - run: bundle install ``` +{% if actions-caching %} + ### 依存関係のキャッシング -{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`setup-ruby`は実行間でのgemのキャッシュを自動的に処理する方法を提供します。 +The `setup-ruby` actions provides a method to automatically handle the caching of your gems between runs. キャッシングを有効にするには、以下の設定をしてください。 @@ -159,11 +161,11 @@ steps: ``` {% endraw %} -これで、gemを`vendor/cache`にインストールするようbundlerが設定されます。 ワークフローの実行が成功するたびに、このフォルダーはアクションによってキャッシュされ、それ以降のワークフローの実行の際に再ダウンロードされます。 キャッシュのキーとしては、gemfile.lockのハッシュとRubyのバージョンが使われます。 新しいgemをインストールしたり、バージョンを変更したりすると、キャッシュは無効になり、bundlerは新しくインストールを行います。 +これで、gemを`vendor/cache`にインストールするようbundlerが設定されます。 For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. キャッシュのキーとしては、gemfile.lockのハッシュとRubyのバージョンが使われます。 新しいgemをインストールしたり、バージョンを変更したりすると、キャッシュは無効になり、bundlerは新しくインストールを行います。 **setup-rubyを使わないキャッシング** -キャッシュをさらに制御するには、{% data variables.product.prodname_dotcom %}ホストランナーを使っているなら、`actions/cache`アクションを直接使うことができます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +For greater control over caching, you can use the `actions/cache` action directly. 詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)」を参照してください。 ```yaml steps: @@ -195,6 +197,8 @@ steps: bundle install --jobs 4 --retry 3 ``` +{% endif %} + ## コードのマトリクステスト 以下の例のマトリクスは、すべての安定リリースとヘッドバージョンのMRI、JRuby、TruffleRubyをUbuntu及びmacOSでテストします。 diff --git a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md index 4224bfdebe..dfbe78d0e3 100644 --- a/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md +++ b/translations/ja-JP/content/actions/creating-actions/creating-a-composite-action.md @@ -75,7 +75,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari outputs: random-number: description: "Random number" - value: ${{ steps.random-number-generator.outputs.random-id }} + value: ${{ steps.random-number-generator.outputs.random-number }} runs: using: "composite" steps: diff --git a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md index 312e38946c..ffd131d0b3 100644 --- a/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -286,7 +286,7 @@ steps: **Example: Using status check functions** -The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +The `my backup step` only runs when the previous step of a composite action fails. For more information, see "[Expressions](/actions/learn-github-actions/expressions#status-check-functions)." ```yaml steps: diff --git a/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md b/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md index e3b14c424e..0225fecbdf 100644 --- a/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md +++ b/translations/ja-JP/content/actions/deployment/about-deployments/about-continuous-deployment.md @@ -31,7 +31,7 @@ You can configure your CD workflow to run when a {% data variables.product.produ {% data variables.product.prodname_actions %} provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. {% ifversion fpt or ghae or ghes > 3.1 or ghec %}You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. {% endif %}For more information about these features, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)." -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} ## Using OpenID Connect to access cloud resources diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md index f8e68b675b..d492ddbb8a 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md @@ -26,7 +26,7 @@ This guide explains how to use {% data variables.product.prodname_actions %} to On every new push to `main` in your {% data variables.product.company_short %} repository, the {% data variables.product.prodname_actions %} workflow builds and pushes a new container image to Amazon ECR, and then deploys a new task definition to Amazon ECS. -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md index 0022ea914e..31c7c70a06 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md @@ -21,7 +21,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Docker container to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md index a47a3472a5..e17be673ac 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md @@ -20,7 +20,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Java project to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md index bfecfe31ed..37f12a178a 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md @@ -19,7 +19,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a .NET project to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md index cc01446f5d..09883bc82e 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md @@ -25,7 +25,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build, test, and deploy a Node.js project to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md index be79e98caa..47b24f81d4 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md @@ -19,7 +19,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a PHP project to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md index 36c2d1df26..2357ca8436 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md @@ -20,7 +20,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a Python project to [Azure App Service](https://azure.microsoft.com/services/app-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md index 938e7329e1..280e18d493 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md @@ -20,7 +20,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a project to [Azure Kubernetes Service](https://azure.microsoft.com/services/kubernetes-service/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md index 23fe47acbb..015d26e16e 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md @@ -20,7 +20,7 @@ topics: This guide explains how to use {% data variables.product.prodname_actions %} to build and deploy a web app to [Azure Static Web Apps](https://azure.microsoft.com/services/app-service/static/). -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md index facebc7cea..f4ffc66513 100644 --- a/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md +++ b/translations/ja-JP/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md @@ -26,7 +26,7 @@ This guide explains how to use {% data variables.product.prodname_actions %} to GKEはGoogle CloudによるマネージドなKubernetesクラスタサービスで、コンテナ化されたワークロードをクラウドもしくはユーザ自身のデータセンターでホストできます。 詳しい情報については[Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine)を参照してください。 -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md index f10fbcc34c..7e41005e42 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security @@ -66,11 +67,14 @@ The following example OIDC token uses a subject (`sub`) that references a job en "jti": "example-id", "sub": "repo:octo-org/octo-repo:environment:prod", "environment": "prod", - "aud": "https://github.com/octo-org", + "aud": "{% ifversion ghes %}https://HOSTNAME{% else %}https://github.com{% endif %}/octo-org", "ref": "refs/heads/main", "sha": "example-sha", "repository": "octo-org/octo-repo", "repository_owner": "octo-org", + "actor_id": "12", + "repository_id": "74", + "repository_owner_id": "65", "run_id": "example-run-id", "run_number": "10", "run_attempt": "2", @@ -81,22 +85,25 @@ The following example OIDC token uses a subject (`sub`) that references a job en "event_name": "workflow_dispatch", "ref_type": "branch", "job_workflow_ref": "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main", - "iss": "https://token.actions.githubusercontent.com", + "iss": "{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}", "nbf": 1632492967, "exp": 1632493867, "iat": 1632493567 } ``` -To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at https://token.actions.githubusercontent.com/.well-known/openid-configuration. +To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at +{% ifversion ghes %}`https://HOSTNAME/_services/token/.well-known/openid-configuration`{% else %}https://token.actions.githubusercontent.com/.well-known/openid-configuration{% endif %}. The token includes the standard audience, issuer, and subject claims: -| Claim | 説明 | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `aud` | _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | -| `iss` | _(Issuer)_ The issuer of the OIDC token: `https://token.actions.githubusercontent.com` | -| `sub` | _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way. | +| Claim | 説明 | +| ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `aud` | _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | +| `iss` | _(Issuer)_ The issuer of the OIDC token: | +| {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} | | +| | | +| `sub` | _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way. | The OIDC token also includes additional standard claims: @@ -112,22 +119,25 @@ The OIDC token also includes additional standard claims: The token also includes custom claims provided by {% data variables.product.prodname_dotcom %}: -| Claim | 説明 | -| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor` | The personal account that initiated the workflow run. | -| `base_ref` | The target branch of the pull request in a workflow run. | -| `environment` | The name of the environment used by the job. | -| `event_name` | ワークフローの実行をトリガーしたイベントの名前。 | -| `head_ref` | The source branch of the pull request in a workflow run. | -| `job_workflow_ref` | This is the ref path to the reusable workflow used by this job. For more information, see "["Using OpenID Connect with reusable workflows"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." | -| `ref` | _(Reference)_ The git ref that triggered the workflow run. | -| `ref_type` | The type of `ref`, for example: "branch". | -| `リポジトリ` | The repository from where the workflow is running. | -| `repository_owner` | The name of the organization in which the `repository` is stored. | -| `run_id` | The ID of the workflow run that triggered the workflow. | -| `run_number` | The number of times this workflow has been run. | -| `run_attempt` | The number of times this workflow run has been retried. | -| `ワークフロー` | ワークフローの名前。 | +| Claim | 説明 | +| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `actor` | The personal account that initiated the workflow run. | +| `actor_id` | The ID of personal account that initiated the workflow run. | +| `base_ref` | The target branch of the pull request in a workflow run. | +| `environment` | The name of the environment used by the job. | +| `event_name` | ワークフローの実行をトリガーしたイベントの名前。 | +| `head_ref` | The source branch of the pull request in a workflow run. | +| `job_workflow_ref` | This is the ref path to the reusable workflow used by this job. For more information, see "["Using OpenID Connect with reusable workflows"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." | +| `ref` | _(Reference)_ The git ref that triggered the workflow run. | +| `ref_type` | The type of `ref`, for example: "branch". | +| `リポジトリ` | The repository from where the workflow is running. | +| `repository_id` | The ID of the repository from where the workflow is running. | +| `repository_owner` | The name of the organization in which the `repository` is stored. | +| `repository_owner_id` | The ID of the organization in which the `repository` is stored. | +| `run_id` | The ID of the workflow run that triggered the workflow. | +| `run_number` | The number of times this workflow has been run. | +| `run_attempt` | The number of times this workflow run has been retried. | +| `ワークフロー` | ワークフローの名前。 | ### Defining trust conditions on cloud roles using OIDC claims @@ -199,12 +209,12 @@ You can create a subject that filters for specific tag. In this example, the wor To configure the subject in your cloud provider's trust relationship, you must add the subject string to its trust configuration. The following examples demonstrate how various cloud providers can accept the same `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` subject in different ways: -| | | -| --------------------- | ------------------------------------------------------------------------------------------------- | -| Amazon Web Services | `"token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | -| Azure | `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | -| Google Cloud Plafform | `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` | -| HashiCorp Vault | `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | +| | | +| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Amazon Web Services | `"{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:sub": "repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | +| Azure | `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | +| Google Cloud Plafform | `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` | +| HashiCorp Vault | `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | For more information, see the guides listed in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)." diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index 666900bbd8..ac5186d48c 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security @@ -31,7 +32,7 @@ This guide explains how to configure AWS to trust {% data variables.product.prod To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, see the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). -- For the provider URL: Use `https://token.actions.githubusercontent.com` +- For the provider URL: Use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} - For the "Audience": Use `sts.amazonaws.com` if you are using the [official action](https://github.com/aws-actions/configure-aws-credentials). ### Configuring the role and trust policy @@ -42,9 +43,9 @@ Edit the trust relationship to add the `sub` field to the validation conditions. ```json{:copy} "Condition": { - "StringEquals": { - "token.actions.githubusercontent.com:aud": "sts.amazonaws.com", - "token.actions.githubusercontent.com:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" + "ForAllValues:StringEquals": { + "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com", + "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:sub": "repo:octo-org/octo-repo:ref:refs/heads/octo-branch" } } ``` diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md index 2d415572a4..14a1fb25b3 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md index 9e4e90c47e..98704b4922 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md index 84a65bc170..221db7d69c 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security @@ -39,7 +40,7 @@ Additional guidance for configuring the identity provider: - For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). - For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions). -- The Issuer URL to use: `https://token.actions.githubusercontent.com` +- The Issuer URL to use: {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} ## {% data variables.product.prodname_actions %} ワークフローを更新する diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md index 75aae09acc..32a53184c1 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md @@ -7,6 +7,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' type: tutorial topics: - Security @@ -32,8 +33,8 @@ This guide gives an overview of how to configure HashiCorp Vault to trust {% dat To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt). Configure the vault to accept JSON Web Tokens (JWT) for authentication: -- For the `oidc_discovery_url`, use `https://token.actions.githubusercontent.com` -- For `bound_issuer`, use `https://token.actions.githubusercontent.com` +- For the `oidc_discovery_url`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} +- For `bound_issuer`, use {% ifversion ghes %}`https://HOSTNAME/_services/token`{% else %}`https://token.actions.githubusercontent.com`{% endif %} - Ensure that `bound_subject` is correctly defined for your security requirements. For more information, see ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) and [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action). ## {% data variables.product.prodname_actions %} ワークフローを更新する diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/index.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/index.md index 8a6f5e6066..51b8975f59 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/index.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/index.md @@ -6,6 +6,7 @@ versions: fpt: '*' ghae: issue-4856 ghec: '*' + ghes: '>=3.5' children: - /about-security-hardening-with-openid-connect - /configuring-openid-connect-in-amazon-web-services diff --git a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md index 0047ecfc81..c832e1235a 100644 --- a/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md +++ b/translations/ja-JP/content/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows.md @@ -45,11 +45,14 @@ For example, the following OIDC token is for a job that was part of a called wor { "jti": "example-id", "sub": "repo:octo-org/octo-repo:environment:prod", - "aud": "https://github.com/octo-org", + "aud": "{% ifversion ghes %}https://HOSTNAME{% else %}https://github.com{% endif %}/octo-org", "ref": "refs/heads/main", "sha": "example-sha", "repository": "octo-org/octo-repo", "repository_owner": "octo-org", + "actor_id": "12", + "repository_id": "74", + "repository_owner_id": "65", "run_id": "example-run-id", "run_number": "10", "run_attempt": "2", @@ -60,7 +63,7 @@ For example, the following OIDC token is for a job that was part of a called wor "event_name": "workflow_dispatch", "ref_type": "branch", "job_workflow_ref": "octo-org/octo-automation/.github/workflows/oidc.yml@refs/heads/main", - "iss": "https://token.actions.githubusercontent.com", + "iss": "{% ifversion ghes %}https://HOSTNAME/_services/token{% else %}https://token.actions.githubusercontent.com{% endif %}", "nbf": 1632492967, "exp": 1632493867, "iat": 1632493567 diff --git a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md index 4ce5b67def..0bc5ed4654 100644 --- a/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md +++ b/translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md @@ -27,12 +27,12 @@ Re-running a workflow{% if re-run-jobs %} or jobs in a workflow{% endif %} uses {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %} +{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %} 1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。 If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**. ![Rerun checks drop-down menu](/assets/images/help/repository/rerun-checks-drop-down.png) {% endif %} -{% ifversion ghes < 3.3 or ghae %} +{% ifversion ghes < 3.5 or ghae %} 1. ワークフローの右上隅にある [**Re-run jobs**] ドロップダウンメニューを使用して、[**Re-run all jobs**] を選択します。 ![[Re-run checks] ドロップダウンメニュー](/assets/images/help/repository/rerun-checks-drop-down-updated.png) {% endif %} @@ -109,7 +109,7 @@ gh run rerun --job job-id {% endif %} -{% ifversion fpt or ghes > 3.2 or ghae-issue-4721 or ghec %} +{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %} ## Reviewing previous workflow runs You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run). diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md index 382361acd9..8ab4474956 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions.md @@ -82,6 +82,8 @@ CircleCIと{% data variables.product.prodname_actions %}は、設定ファイル CircleCIと{% data variables.product.prodname_actions %}は、設定ファイル中で手動でファイルをキャッシュする方法を提供しています。 +{% if actions-caching %} + 以下は、それぞれのシステムにおける構文の例です。 @@ -119,7 +121,11 @@ GitHub Actions
-{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% else %} + +{% data reusables.actions.caching-availability %} + +{% endif %} {% data variables.product.prodname_actions %}は、CircleCIのDocker Layer Caching（DLC）に相当する機能を持っていません。 @@ -175,7 +181,7 @@ GitHub Actions -詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)」を参照してください。 +For more information, see "[Persisting workflow data using artifacts](/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts)." ## データベースとサービスコンテナの利用 diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md index ea26b603ac..f5f414d48c 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-gitlab-cicd-to-github-actions.md @@ -309,6 +309,8 @@ GitLab CI/CD および {% data variables.product.prodname_actions %} は、パ GitLab CI/CD と {% data variables.product.prodname_actions %} では、設定ファイルにワークフローファイルを手動でキャッシュするためのメソッドがあります。 +{% if actions-caching %} + 以下が、それぞれのシステムの構文の例です。 @@ -359,7 +361,11 @@ jobs:
-{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% else %} + +{% data reusables.actions.caching-availability %} + +{% endif %} ## 成果物 diff --git a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md index 4bbdae4d39..a4681f72fc 100644 --- a/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md +++ b/translations/ja-JP/content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md @@ -302,7 +302,11 @@ jobs: ## 依存関係のキャッシング -Travis CIと{% data variables.product.prodname_actions %}では、後で利用できるよう依存関係を手動でキャッシュできます。 以下の例は、それぞれのシステムでのキャッシュの構文を示します。 +Travis CIと{% data variables.product.prodname_actions %}では、後で利用できるよう依存関係を手動でキャッシュできます。 + +{% if actions-caching %} + +以下の例は、それぞれのシステムでのキャッシュの構文を示します。 @@ -337,7 +341,11 @@ cache: npm
-{% data variables.product.prodname_actions %} キャッシュは、{% data variables.product.prodname_dotcom_the_website %} でホストされているリポジトリにのみ適用できます。 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 +{% else %} + +{% data reusables.actions.caching-availability %} + +{% endif %} ## 一般的なタスクの例 diff --git a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md index 1c332342f4..c127b8adf3 100644 --- a/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md +++ b/translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md @@ -78,7 +78,7 @@ on: jobs: push_to_registry: name: Push Docker image to Docker Hub - runs-on: ubuntu-latest + runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %} steps: - name: Check out the repo uses: {% data reusables.actions.action-checkout %} @@ -108,12 +108,16 @@ The above workflow checks out the {% data variables.product.prodname_dotcom %} r ## {% data variables.product.prodname_registry %}へのイメージの公開 +{% ifversion ghes > 3.4 %} +{% data reusables.package_registry.container-registry-ghes-beta %} +{% endif %} + {% data reusables.actions.release-trigger-workflow %} 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`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% else %}`docker.pkg.github.com`{% endif %}. +* `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`: {% 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)」を参照してください。 @@ -126,9 +130,13 @@ The `build-push-action` options required for {% data variables.product.prodname_ * `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`: `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` に設定する必要があります。 You can set a single tag as shown below, or specify multiple tags in a list.{% endif %} +* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`. -{% ifversion fpt or ghec %} + 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`. + + 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 %} 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 %}. @@ -170,11 +178,15 @@ jobs: {% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %} ``` -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 the Docker registry, and apply the commit SHA and release version as image tags. +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 %}へのイメージの公開 +{% ifversion ghes > 3.4 %} +{% data reusables.package_registry.container-registry-ghes-beta %} +{% endif %} + 単一のワークフローで、各レジストリの `login-action` アクションと `build-push-action` アクションを使用して、Docker イメージを複数のレジストリに公開できます。 次のワークフロー例では、前のセクションのステップ（「[Docker Hub へのイメージの公開](#publishing-images-to-docker-hub)」と「[{% data variables.product.prodname_registry %} へのイメージの公開](#publishing-images-to-github-packages)」）を使用して、両方のレジストリにプッシュする単一のワークフローを作成します。 @@ -191,7 +203,7 @@ on: jobs: push_to_registries: name: Push Docker image to multiple registries - runs-on: ubuntu-latest{% ifversion fpt or ghes > 3.1 or ghae or ghec %} + runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %}{% ifversion fpt or ghes > 3.1 or ghae or ghec %} permissions: packages: write contents: read{% endif %} @@ -205,10 +217,10 @@ jobs: username: {% raw %}${{ secrets.DOCKER_USERNAME }}{% endraw %} password: {% raw %}${{ secrets.DOCKER_PASSWORD }}{% endraw %} - - name: Log in to the {% ifversion fpt or ghec %}Container{% else %}Docker{% endif %} registry + - name: Log in to the {% ifversion fpt or ghec or ghes > 3.4 %}Container{% else %}Docker{% endif %} registry uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9 with: - registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %} + registry: {% ifversion fpt or ghec %}ghcr.io{% elsif ghae %}docker.YOUR-HOSTNAME.com{% elsif ghes > 3.4 %}{% data reusables.package_registry.container-registry-hostname %}{% else %}docker.pkg.github.com{% endif %} username: {% raw %}${{ github.actor }}{% endraw %} password: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %} @@ -218,7 +230,7 @@ jobs: with: images: | my-docker-hub-namespace/my-docker-hub-repository - {% ifversion fpt or ghec %}ghcr.io/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %} + {% ifversion fpt or ghec or ghes > 3.4 %}{% data reusables.package_registry.container-registry-hostname %}/{% raw %}${{ github.repository }}{% endraw %}{% elsif ghae %}{% raw %}docker.YOUR-HOSTNAME.com/${{ github.repository }}/my-image{% endraw %}{% else %}{% raw %}docker.pkg.github.com/${{ github.repository }}/my-image{% endraw %}{% endif %} - name: Build and push Docker images uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc @@ -229,4 +241,4 @@ jobs: labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %} ``` -The above workflow checks out the {% data variables.product.prodname_dotcom %} 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 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% 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 %}. diff --git a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md index f66aed66cc..0b589159a2 100644 --- a/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md +++ b/translations/ja-JP/content/actions/security-guides/encrypted-secrets.md @@ -25,7 +25,7 @@ Secrets are encrypted environment variables that you create in an organization, 環境レベルで保存されたシークレットについては、それらへのアクセスを制御するために必須のレビュー担当者を有効化することができます。 必須の承認者によって許可されるまで、ワークフローのジョブは環境のシークレットにアクセスできません。 -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} {% note %} diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md index cc874327cb..77378badf1 100644 --- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md @@ -159,7 +159,7 @@ For more information, see "[About {% data variables.product.prodname_code_scanni To help mitigate the risk of an exposed token, consider restricting the assigned permissions. For more information, see "[Modifying the permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)." -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} ## Using OpenID Connect to access cloud resources @@ -209,7 +209,7 @@ The same principles described above for using third-party actions also apply to These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner. -### Accessing secrets +### シークレットへのアクセス Workflows triggered using the `pull_request` event have read-only permissions and have no access to secrets. However, these permissions differ for various event triggers such as `issue_comment`, `issues` and `push`, where the attacker could attempt to steal repository secrets or use the write permission of the job's [`GITHUB_TOKEN`](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token). @@ -291,7 +291,7 @@ A self-hosted runner can be added to various levels in your {% data variables.pr - If each team will manage their own self-hosted runners, then the recommendation is to add the runners at the highest level of team ownership. For example, if each team owns their own organization, then it will be simplest if the runners are added at the organization level too. - You could also add runners at the repository level, but this will add management overhead and also increases the numbers of runners you need, since you cannot share runners between repositories. -{% ifversion fpt or ghec or ghae-issue-4856 %} +{% ifversion fpt or ghec or ghae-issue-4856 or ghes > 3.4 %} ### Authenticating to your cloud provider If you are using {% data variables.product.prodname_actions %} to deploy to a cloud provider, or intend to use HashiCorp Vault for secret management, then its recommended that you consider using OpenID Connect to create short-lived, well-scoped access tokens for your workflow runs. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)." diff --git a/translations/ja-JP/content/actions/using-workflows/about-workflows.md b/translations/ja-JP/content/actions/using-workflows/about-workflows.md index c4277d4883..64a87a06c1 100644 --- a/translations/ja-JP/content/actions/using-workflows/about-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/about-workflows.md @@ -124,10 +124,10 @@ jobs: For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." -{% ifversion fpt or ghec %} +{% if actions-caching %} ### 依存関係のキャッシング -{% data variables.product.prodname_dotcom %} ホストランナーは各ジョブの新しい環境として開始されるため、ジョブが依存関係を定期的に再利用する場合は、これらのファイルをキャッシュしてパフォーマンスを向上させることを検討できます。 キャッシュが作成されると、同じリポジトリ内のすべてのワークフローで使用できるようになります。 +If your jobs regularly reuse dependencies, you can consider caching these files to help improve performance. キャッシュが作成されると、同じリポジトリ内のすべてのワークフローで使用できるようになります。 この例は、`~/.npm` ディレクトリをキャッシュする方法を示しています。 diff --git a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index ca791f402a..c3f57d8a46 100644 --- a/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/ja-JP/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -9,22 +9,20 @@ redirect_from: - /actions/guides/caching-dependencies-to-speed-up-workflows - /actions/advanced-guides/caching-dependencies-to-speed-up-workflows versions: - fpt: '*' - ghec: '*' + feature: actions-caching type: tutorial topics: - Workflows +miniTocMaxHeadingLevel: 3 --- ## ワークフローの依存関係のキャッシングについて ワークフローの実行は、しばしば他の実行と同じ出力あるいはダウンロードされた依存関係を再利用します。 たとえばMaven、Gradle、npm、Yarnといったパッケージ及び依存関係管理ツールは、ダウンロードされた依存関係のローカルキャッシュを保持します。 -{% data variables.product.prodname_dotcom %}ホストランナー上のジョブは、クリーンな仮想環境で開始され、依存関係を毎回ダウンロードしなければならず、ネットワークの利用率を増大させ、実行時間が長くなり、コストが高まってしまいます。 これらのファイルの再生成にかかる時間を短縮しやすくするために、{% data variables.product.prodname_dotcom %}はワークフロー内で頻繁に使われる依存関係をキャッシュできます。 +{% ifversion fpt or ghec %} Jobs on {% data variables.product.prodname_dotcom %}-hosted runners start in a clean virtual environment and must download dependencies each time, causing increased network utilization, longer runtime, and increased cost. {% endif %}To help speed up the time it takes to recreate files like dependencies, {% data variables.product.prodname_dotcom %} can cache files you frequently use in workflows. -ジョブのために依存関係をキャッシュするには、{% data variables.product.prodname_dotcom %}の`cache`アクションを使わなければなりません。 このアクションは、ユニークなキーで指定されるキャッシュを取得します。 詳しい情報については「[`actions/cache`](https://github.com/actions/cache)」を参照してください。 - -If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use. +To cache dependencies for a job, you can use {% data variables.product.prodname_dotcom %}'s [`cache` action](https://github.com/actions/cache). The action creates and restores a cache identified by a unique key. Alternatively, if you are caching the package managers listed below, using their respective setup-* actions requires minimal configuration and will create and restore dependency caches for you. @@ -36,62 +34,59 @@ If you are caching the package managers listed below, consider using the respect - + - + - + - +
npm, yarn, pnpmsetup-nodesetup-node
pip, pipenvsetup-pythonsetup-python
gradle, mavensetup-javasetup-java
ruby gemssetup-rubysetup-ruby
{% warning %} -**警告**: パブリックリポジトリのキャッシュには、センシティブな情報を保存しないことをおすすめします。 たとえばキャッシュパス内のファイルに保存されたアクセストークンあるいはログインクレデンシャルなどがセンシティブな情報です。 また、`docker login`のようなコマンドラインインターフェース（CLI）プログラムは、アクセスクレデンシャルを設定ファイルに保存することがあります。 読み取りアクセスを持つ人は誰でも、リポジトリにPull Requestを作成し、キャッシュの内容にアクセスできます。 リポジトリのフォークも、ベースブランチ上にPull Requestを作成し、ベースブランチ上のキャッシュにアクセスできます。 +**Warning**: {% ifversion fpt or ghec %}Be mindful of the following when using caching with {% data variables.product.prodname_actions %}: + +* {% endif %}We recommend that you don't store any sensitive information in the cache. たとえばキャッシュパス内のファイルに保存されたアクセストークンあるいはログインクレデンシャルなどがセンシティブな情報です。 また、`docker login`のようなコマンドラインインターフェース（CLI）プログラムは、アクセスクレデンシャルを設定ファイルに保存することがあります。 Anyone with read access can create a pull request on a repository and access the contents of a cache. リポジトリのフォークも、ベースブランチ上にPull Requestを作成し、ベースブランチ上のキャッシュにアクセスできます。 +{%- ifversion fpt or ghec %} +* When using self-hosted runners, caches from workflow runs are stored on {% data variables.product.company_short %}-owned cloud storage. A customer-owned storage solution is only available with {% data variables.product.prodname_ghe_server %}. +{%- endif %} {% endwarning %} -## 成果物の比較と依存関係のキャッシング +{% data reusables.actions.comparing-artifacts-caching %} -成果物とキャッシングは、{% data variables.product.prodname_dotcom %}にファイルを保存できるようにするので似ていますが、それぞれの機能のユースケースは異なっており、入れ替えて使うことはできません。 - -- キャッシングは、ジョブやワークフローの実行間で頻繁に変化しないファイルを再利用したいときに使ってください。 -- ジョブによって生成されたファイルをワークフローの終了後に見るために保存したい場合に成果物を使ってください。 詳しい情報については「[成果物を利用してワークフローのデータを永続化する](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)」を参照してください。 +For more information on workflow run artifacts, see "[Persisting workflow data using artifacts](/github/automating-your-workflow-with-github-actions/persisting-workflow-data-using-artifacts)." ## キャッシュへのアクセスについての制限 -`cache` アクションの `v2` を使用すると、`GITHUB_REF` を含むイベントによってトリガーされるワークフローのキャッシュにアクセスできます。 `cache` アクションの `v1` を使用している場合、`pull_request` の `closed` イベントを除いて、`push` イベントと `pull_request` イベントによってトリガーされるワークフローでのみキャッシュにアクセスできます。 詳しい情報については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows)」を参照してください。 - ワークフローは、現在のブランチ、ベースブランチ（フォークされたリポジトリのベースブランチを含む）、またはデフォルトブランチ（通常は `main`）で作成されたキャッシュにアクセスして復元できます。 たとえば、デフォルトブランチで作成されたキャッシュは、どのPull Requestからもアクセスできます。 また、`feature-b` ブランチに `feature-a` ベースブランチがある場合、`feature-b` でトリガーされたワークフローは、デフォルトのブランチ（`main`）、`feature-a`、および `feature-b` で作成されたキャッシュにアクセスできます。 -Access restrictions provide cache isolation and security by creating a logical boundary between different branches. たとえば、`feature-a` ブランチ（ベース `main` を使用）向けに作成されたキャッシュは、`feature-b` ブランチ（ベース `main` を使用）のPull Requestにアクセスできません。 +Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch. ## `cache`アクションの利用 -`cache`アクションは、提供された`key`に基づいてキャッシュをリストアしようとします。 このアクションは、キャッシュを見つけるとそのキャッシュされたファイルを設定された`path`にリストアします。 +The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. このアクションは、キャッシュを見つけるとそのキャッシュされたファイルを設定された`path`にリストアします。 -正確なマッチがなければ、ジョブが成功したならこのアクションは新しいキャッシュエントリを作成します。 新しいキャッシュは提供された`key`を使い、`path`ディレクトリ内にファイルを保存します。 +If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. 既存のキャッシュに`key`がマッチしなかった場合に使われる、`restore-keys`のリストを提供することもできます。 `restore-keys`のリストは、 `restore-keys`がキャッシュキーと部分的にマッチできるので、他のブランチからのキャッシュをリストアする場合に役立ちます。 `restore-keys`のマッチに関する詳しい情報については「[キャッシュキーのマッチ](#matching-a-cache-key)」を参照してください。 -詳しい情報については「[`actions/cache`](https://github.com/actions/cache)」を参照してください。 - ### `cache` アクションの入力パラメータ -- `key`: **必須** このキーはキャッシュの保存時に作成され、キャッシュの検索に使われます。 変数、コンテキスト値、静的な文字列、関数の任意の組み合わせが使えます。 キーの長さは最大で512文字であり、キーが最大長よりも長いとアクションは失敗します。 -- `path`: **必須** ランナーがキャッシュあるいはリストアをするファイルパス。 The path can be an absolute path or relative to the workspace directory. - - パスはディレクトリまたは単一ファイルのいずれかで、glob パターンがサポートされています。 - - `cache` アクションの `v2` では、単一のパスを指定することも、別々の行に複数のパスを追加することもできます。 例: +- `key`: **必須** このキーはキャッシュの保存時に作成され、キャッシュの検索に使われます。 It can be any combination of variables, context values, static strings, and functions. キーの長さは最大で512文字であり、キーが最大長よりも長いとアクションは失敗します。 +- `path`: **Required** The path(s) on the runner to cache or restore. + - You can specify a single path, or you can add multiple paths on separate lines. 例: ``` - name: Cache Gradle packages @@ -101,14 +96,15 @@ Multiple workflows within a repository share cache entries. A cache created for ~/.gradle/caches ~/.gradle/wrapper ``` - - `cache` アクションの `v1` では、単一のパスのみがサポートされ、かつそれがディレクトリである必要があります。 単一のファイルをキャッシュすることはできません。 -- `restore-keys`: **Optional** A string containing alternative restore keys, with each restore key placed on a new line. If no cache hit occurred for `key`, these restore keys are used sequentially in the order provided to find and restore a cache. 例: + - You can specify either directories or single files, and glob patterns are supported. + - You can specify absolute paths, or paths relative to the workspace directory. +- `restore-keys`: **Optional** A string containing alternative restore keys, with each restore key placed on a new line. If no cache hit occurs for `key`, these restore keys are used sequentially in the order provided to find and restore a cache. 例: {% raw %} ```yaml restore-keys: | - npm-foobar-${{ hashFiles('package-lock.json') }} - npm-foobar- + npm-feature-${{ hashFiles('package-lock.json') }} + npm-feature- npm- ``` {% endraw %} @@ -123,17 +119,15 @@ Multiple workflows within a repository share cache entries. A cache created for ```yaml{:copy} name: Caching with npm - on: push - jobs: build: runs-on: ubuntu-latest - steps: - uses: {% data reusables.actions.action-checkout %} - name: Cache node modules + id: cache-npm uses: {% data reusables.actions.action-cache %} env: cache-name: cache-node-modules @@ -146,7 +140,12 @@ jobs: {% raw %}${{ runner.os }}-build-{% endraw %} {% raw %}${{ runner.os }}-{% endraw %} - - name: Install Dependencies + - if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == false }}{% endraw %} + name: List the state of node modules + continue-on-error: true + run: npm list + + - name: Install dependencies run: npm install - name: Build @@ -156,23 +155,27 @@ jobs: run: npm test ``` -`key`が既存のキャッシュにマッチした場合はキャッシュヒットと呼ばれ、このアクションはキャッシュされたファイルを`path`ディレクトリにリストアします。 +When `key` matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory. -`key`が既存のキャッシュにマッチしなかった場合はキャッシュミスと呼ばれ、ジョブが成功して完了したなら新しいキャッシュが作成されます。 キャッシュミスが生じた場合、このアクションは`restore-keys`と呼ばれる代理キーを検索します。 +When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully. + +When a cache miss occurs, the action also searches your specified `restore-keys` for any matches: 1. `restore-keys`が渡された場合、`cache`アクションは`restore-keys`のリストにマッチするキャッシュを順番に検索します。 - 完全なマッチがあった場合、アクションはそのファイルを`path`ディレクトリ中のキャッシュにリストアします。 - 完全なマッチがなかった場合、アクションはリストアキーに対する部分一致を検索します。 アクションが部分一致を見つけた場合、最も最近のキャッシュが`path`ディレクトリにリストアされます。 -1. `cache` アクションが完了し、ジョブ内の次のワークフローステップが実行されます。 -1. ジョブが成功して完了したなら、アクションは`path`ディレクトリの内容で新しいキャッシュを作成します。 +1. The `cache` action completes and the next step in the job runs. +1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory. -複数のディレクトリにファイルをキャッシュするには、各ディレクトリごとに[`cache`](https://github.com/actions/cache) アクションを使うステップが必要です。 キャッシュをいったん作成すると、既存のキャッシュの内容を変更することはできませんが、新しいキーで新しいキャッシュを作成することはできます。 +For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." キャッシュをいったん作成すると、既存のキャッシュの内容を変更することはできませんが、新しいキーで新しいキャッシュを作成することはできます。 ### コンテキストを使ったキャッシュキーの作成 -キャッシュキーには、コンテキスト、関数、リテラル、{% data variables.product.prodname_actions %}がサポートする演算子を含めることができます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions)." +キャッシュキーには、コンテキスト、関数、リテラル、{% data variables.product.prodname_actions %}がサポートする演算子を含めることができます。 For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)." -式を使って`key`を作成すれば、依存関係が変化したときに自動的に新しいキャッシュを作成できます。 たとえばnpmの`package-lock.json`ファイルのハッシュを計算する式を使って`key`を作成できます。 +Using expressions to create a `key` allows you to automatically create a new cache when dependencies change. + +たとえばnpmの`package-lock.json`ファイルのハッシュを計算する式を使って`key`を作成できます。 So, when the dependencies that make up the `package-lock.json` file change, the cache key changes and a new cache is automatically created. {% raw %} ```yaml @@ -186,19 +189,32 @@ npm-${{ hashFiles('package-lock.json') }} npm-d5ea0750 ``` +### Using the output of the `cache` action + +You can use the output of the `cache` action to do something based on whether a cache hit or miss occurred. If there is a cache miss (an exact match for a cache was not found for the specified `key`), the `cache-hit` output is set to `false`. + +In the example workflow above, there is a step that lists the state of the Node modules if a cache miss occurred: + +```yaml +- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == false }}{% endraw %} + name: List the state of node modules + continue-on-error: true + run: npm list +``` + ## キャッシュキーのマッチング `cache` アクションは最初に、ワークフロー実行を含むブランチで `key` および `restore-keys` のキャッシュヒットを検索します。 現在のブランチにヒットがない場合、`cache` アクションは、親ブランチと上流のブランチで `key` および `restore-keys` を検索します。 -`key`でキャッシュミスがあった場合に使うリストアキーのリストを提供できます。 特定の度合いが強いものから弱いものへ並べて複数のリストアキーを作成できます。 `cache`アクションは順番に`restore-keys`を検索していきます。 キーが直接マッチしなかった場合、アクションはリストアキーでプレフィックスされたキーを検索します。 リストアキーに対して複数の部分一致があった場合、アクションは最も最近に作成されたキャッシュを返します。 +`restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. 特定の度合いが強いものから弱いものへ並べて複数のリストアキーを作成できます。 The `cache` action searches the `restore-keys` in sequential order. キーが直接マッチしなかった場合、アクションはリストアキーでプレフィックスされたキーを検索します。 リストアキーに対して複数の部分一致があった場合、アクションは最も最近に作成されたキャッシュを返します。 ### 複数のリストアキーの利用例 {% raw %} ```yaml restore-keys: | - npm-foobar-${{ hashFiles('package-lock.json') }} - npm-foobar- + npm-feature-${{ hashFiles('package-lock.json') }} + npm-feature- npm- ``` {% endraw %} @@ -208,16 +224,16 @@ restore-keys: | {% raw %} ```yaml restore-keys: | - npm-foobar-d5ea0750 - npm-foobar- + npm-feature-d5ea0750 + npm-feature- npm- ``` {% endraw %} -リストアキーの`npm-foobar-`は、`npm-foobar-`という文字列で始まる任意のキーにマッチします。 たとえば`npm-foobar-fd3052de`や`npm-foobar-a9b253ff`というキーはいずれもこのリストアキーにマッチします。 最も最近の期日に作成されたキャッシュが使われます。 この例でのキーは、以下の順序で検索されます。 +The restore key `npm-feature-` matches any key that starts with the string `npm-feature-`. For example, both of the keys `npm-feature-fd3052de` and `npm-feature-a9b253ff` match the restore key. 最も最近の期日に作成されたキャッシュが使われます。 この例でのキーは、以下の順序で検索されます。 -1. **`npm-foobar-d5ea0750`**は特定のハッシュにマッチします。 -1. **`npm-foobar-`**は`npm-foobar-`をプレフィックスとするキャッシュキーにマッチします。 +1. **`npm-feature-d5ea0750`** matches a specific hash. +1. **`npm-feature-`** matches cache keys prefixed with `npm-feature-`. 1. **`npm-`**は`npm-`をプレフィックスとする任意のキーにマッチします。 #### 検索の優先度の例 @@ -230,18 +246,24 @@ restore-keys: | npm- ``` -たとえば、プルリクエストに `feature` ブランチ（現在のスコープ）が含まれ、デフォルトブランチ（`main`）をターゲットにしている場合、アクションは次の順序で `key` と `restore-keys` を検索します。 +For example, if a pull request contains a `feature` branch and targets the default branch (`main`), the action searches for `key` and `restore-keys` in the following order: -1. `feature`ブランチのスコープ内で`npm-feature-d5ea0750`というキー -1. `feature`ブランチのスコープ内で`npm-feature-`というキー -2. `feature`ブランチのスコープ内で`npm-`というキー -1. `main` ブランチのスコープ内で `npm-feature-d5ea0750` というキー -3. `main` ブランチのスコープ内で `npm-feature-` というキー -4. `main` ブランチのスコープ内で `npm-` というキー +1. Key `npm-feature-d5ea0750` in the `feature` branch +1. Key `npm-feature-` in the `feature` branch +1. Key `npm-` in the `feature` branch +1. Key `npm-feature-d5ea0750` in the `main` branch +1. Key `npm-feature-` in the `main` branch +1. Key `npm-` in the `main` branch ## 利用制限と退去のポリシー -{% data variables.product.prodname_dotcom %}は、7日間以上アクセスされていないキャッシュエントリを削除します。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB. +{% data variables.product.prodname_dotcom %}は、7日間以上アクセスされていないキャッシュエントリを削除します。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited{% if actions-cache-policy-apis %}. By default, the limit is 10 GB per repository, but this limit might be different depending on policies set by your enterprise owners or repository administrators.{% else %} to 10 GB.{% endif %} + +{% data reusables.actions.cache-eviction-process %} + +{% if actions-cache-policy-apis %} +For information on changing the policies for the repository cache size limit, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-cache-storage-in-your-enterprise)" and "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-cache-storage-for-a-repository)." +{% endif %} {% if actions-cache-management %} diff --git a/translations/ja-JP/content/actions/using-workflows/index.md b/translations/ja-JP/content/actions/using-workflows/index.md index b94c06be00..17fbe570c7 100644 --- a/translations/ja-JP/content/actions/using-workflows/index.md +++ b/translations/ja-JP/content/actions/using-workflows/index.md @@ -27,11 +27,11 @@ children: - /workflow-syntax-for-github-actions - /workflow-commands-for-github-actions - /reusing-workflows + - /caching-dependencies-to-speed-up-workflows + - /storing-workflow-data-as-artifacts - /creating-starter-workflows-for-your-organization - /using-starter-workflows - /sharing-workflows-secrets-and-runners-with-your-organization - - /caching-dependencies-to-speed-up-workflows - - /storing-workflow-data-as-artifacts - /using-github-cli-in-workflows --- diff --git a/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md b/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md index e78d57d69c..7e9f72347d 100644 --- a/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md +++ b/translations/ja-JP/content/actions/using-workflows/storing-workflow-data-as-artifacts.md @@ -56,6 +56,14 @@ To share data between jobs: The steps of a job share the same environment on the runner machine, but run in their own individual processes. To pass data between steps in a job, you can use inputs and outputs. For more information about inputs and outputs, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions)." +{% if actions-caching %} + +{% data reusables.actions.comparing-artifacts-caching %} + +For more information on dependency caching, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows#comparing-artifacts-and-dependency-caching)." + +{% endif %} + ## Uploading build and test artifacts You can create a continuous integration (CI) workflow to build and test your code. For more information about using {% data variables.product.prodname_actions %} to perform CI, see "[About continuous integration](/articles/about-continuous-integration)." diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 6e39faceca..e4d28251bc 100644 --- a/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -367,7 +367,7 @@ steps: #### Example: Using status check functions -`my backup step`は、ジョブの前のステップが失敗した場合にのみ実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +`my backup step`は、ジョブの前のステップが失敗した場合にのみ実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#status-check-functions)." ```yaml steps: diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md index ef82dd7256..082bd40e29 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -26,13 +26,14 @@ After enabling {% data variables.product.prodname_github_connect %}, you will be After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. -| 機能 | 説明 | 詳細情報 | -| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| 機能 | 説明 | 詳細情報 | +| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %} | Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %} | {% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)" | -| Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | -| Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | +| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %} +| {% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} +| Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}. | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" | +| Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" | ## Data transmission for {% data variables.product.prodname_github_connect %} @@ -61,14 +62,15 @@ When you enable {% data variables.product.prodname_github_connect %} or specific Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}. -| 機能 | Data | Which way does the data flow? | Where is the data used? | -| ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} -| Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} -| {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} -| {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} -| {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} -| Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} +| 機能 | Data | Which way does the data flow? | Where is the data used? | +| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %} +| Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %} +| {% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %} +| {% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository

If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} +| {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %} +| {% data variables.product.prodname_server_statistics %} | Aggregate {% data variables.product.prodname_ghe_server %} usage metrics
For the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} +| Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}

From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} +| Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} ## 参考リンク diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md index d36a08f22b..8e1b61c8b8 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md @@ -20,9 +20,9 @@ shortTitle: Automatic user license sync ## ライセンスの同期について -{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)." +{% data reusables.enterprise-licensing.about-license-sync %} 詳しい情報については「[{% data variables.product.prodname_github_connect %}にちて](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)」を参照してください。 -If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. +If you enable automatic user license sync for your enterprise, {% data variables.product.prodname_github_connect %} will automatically synchronize license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly.{% ifversion ghes > 3.4 %} You can also synchronize your license data at any time outside of the automatic weekly sync, by manually triggering a license sync job. For more information, see "[Triggering a license sync job](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#triggering-a-license-sync-job)."{% endif %} If you use multiple {% data variables.product.prodname_ghe_server %} instances, you can enable automatic license sync between each of your instances and the same organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md new file mode 100644 index 0000000000..a4bb148ac0 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md @@ -0,0 +1,31 @@ +--- +title: Enabling Server Statistics for your enterprise +intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.' +versions: + feature: server-statistics +redirect_from: + - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics/enabling-server-statistics +topics: + - Enterprise +shortTitle: Server Statistics +--- + +{% data reusables.server-statistics.release-phase %} + +## {% data variables.product.prodname_server_statistics %}について + +{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.product.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. + +{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features.{% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. 詳しい情報については、「[{% data variables.product.prodname_server_statistics %} について](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)」を参照してください。 + +By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you. + +## {% data variables.product.prodname_server_statistics %} の有効化 + +Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. 詳細は、「[{% data variables.product.prodname_ghe_server %}を{% data variables.product.prodname_ghe_cloud %}に接続する](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)」を参照してください。 + +You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time. + +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.github-connect-tab %} +4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**. ![Screenshot of {% data variables.product.prodname_server_statistics %} drop-down menu with disabled or enabled options](/assets/images/help/server-statistics/server-statistics-enable-disable-options.png) diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md index baf1fbba8d..95089bed13 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md +++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md @@ -21,6 +21,7 @@ children: - /managing-github-connect - /enabling-automatic-user-license-sync-for-your-enterprise - /enabling-dependabot-for-your-enterprise + - /enabling-server-statistics-for-your-enterprise - /enabling-unified-search-for-your-enterprise - /enabling-unified-contributions-for-your-enterprise shortTitle: GitHub Connect diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md index 0c286afa66..8ca809c4ad 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md @@ -24,23 +24,25 @@ Subdomain Isolationは、クロスサイトスクリプティングや関連す Subdomain Isolation が有効な場合、{% data variables.product.prodname_ghe_server %} はいくつかのパスをサブドメインで置き換えます。 After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors. -| Subdomain Isolationなしのパス | Subdomain Isolationされたパス | -| -------------------------------------- | ----------------------------------------------------------- | -| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | -| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | -| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | -| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | -| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | -| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | -| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | -| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | -| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | -| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% ifversion ghes %} +| Subdomain Isolationなしのパス | Subdomain Isolationされたパス | +| -------------------------------------- | -------------------------------------------------------------- | +| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` | +| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` | +| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` | +| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` | +| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` | +| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` | +| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` | +| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` | +| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` | +| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |{% ifversion ghes %} | `https://HOSTNAME/_registry/docker/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %} -| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | -| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | -| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | -| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %} +| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` | +| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` | +| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` | +| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %} +| Not supported | `https://containers.HOSTNAME/` +{% endif %} ## 必要な環境 diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md index dda614d0f4..bbd29e52aa 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md @@ -209,7 +209,7 @@ ghe-logs-tail ### ghe-maintenance -This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly. +This utility allows you to control the state of the installation's maintenance mode. It's designed to be used primarily by the {% data variables.enterprise.management_console %} behind-the-scenes, but it can be used directly. For more information, see "[Enabling and scheduling maintenance mode](/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." ```shell ghe-maintenance -h diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md index afe9132dfc..c8f852bc51 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md @@ -129,6 +129,10 @@ $ ghe-restore -c 169.154.1.1 > Visit https://169.154.1.1/setup/settings to review appliance configuration. ``` +{% if ip-exception-list %} +Optionally, to validate the restore, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." +{% endif %} + {% note %} **Note:** The network settings are excluded from the backup snapshot. You must manually configure the network on the target {% data variables.product.prodname_ghe_server %} appliance as required for your environment. diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md index 8f9f359c87..c1805d878d 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md @@ -1,6 +1,6 @@ --- -title: Configuring email for notifications -intro: 'To make it easy for users to respond quickly to activity on {% data variables.product.product_name %}, you can configure {% data variables.product.product_location %} to send email notifications for issue, pull request, and commit comments.' +title: 通知のためのメール設定 +intro: 'ユーザが {% data variables.product.product_name %} のアクティビティにすばやく応答できるようにするために、{% data variables.product.product_location %} を設定して、Issue、プルリクエスト、およびコミットコメントのメール通知を送信できます。' redirect_from: - /enterprise/admin/guides/installation/email-configuration - /enterprise/admin/articles/configuring-email @@ -19,93 +19,76 @@ topics: - Notifications shortTitle: Configure email notifications --- + {% ifversion ghae %} -Enterprise owners can configure email for notifications. +Enterprise オーナーは、通知用のメールを設定できます。 {% endif %} -## Configuring SMTP for your enterprise +## Enterprise 向けの SMTP を設定する {% ifversion ghes %} -{% data reusables.enterprise_site_admin_settings.access-settings %} -{% data reusables.enterprise_site_admin_settings.management-console %} -2. At the top of the page, click **Settings**. -![Settings tab](/assets/images/enterprise/management-console/settings-tab.png) -3. In the left sidebar, click **Email**. -![Email tab](/assets/images/enterprise/management-console/email-sidebar.png) -4. Select **Enable email**. This will enable both outbound and inbound email, however for inbound email to work you will also need to configure your DNS settings as described below in "[Configuring DNS and firewall -settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." -![Enable outbound email](/assets/images/enterprise/management-console/enable-outbound-email.png) -5. Type the settings for your SMTP server. - - In the **Server address** field, type the address of your SMTP server. - - In the **Port** field, type the port that your SMTP server uses to send email. - - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any. - - Select the **Authentication** dropdown, and choose the type of encryption used by your SMTP server. - - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. -6. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. -![Checkbox to discard emails addressed to the no-reply email address](/assets/images/enterprise/management-console/discard-noreply-emails.png) -7. Under **Support**, choose a type of link to offer additional support to your users. +{% data reusables.enterprise_site_admin_settings.email-settings %} +4. **Enable email（メールの有効化）**を選択してください。 これでアウトバウンドとインバウンドのメールがどちらも有効化されますが、インバウンドのメールが動作するには[着信メールを許可する DNS とファイアウォールの設定](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)に記述されているように DNS を設定する必要もあります。 ![アウトバウンドメールの有効化](/assets/images/enterprise/management-console/enable-outbound-email.png) +5. SMTP サーバーの設定を入力します。 + - [**Server address**] フィールドに SMTP サーバのアドレスを入力します。 + - [**Port**] フィールドには、SMTP サーバがメールを送信するのに使用するポートを入力します。 + - [**Domain**] フィールドには、SMTP サーバが HELO レスポンスを送信するドメイン名があれば入力してください。 + - [**Authentication**] ドロップダウンを選択し、SMTP サーバーで使用される暗号化の種類を選択します。 + - [**No-reply email address（No-replyメールアドレス）**] フィールドには、すべての通知メールの From および To フィールドに使うメールアドレスを入力してください。 +6. no-replyメールアドレスへの着信メールをすべて破棄したい場合には、**Discard email addressed to the no-reply email address（no-replyメールアドレスへのメールの破棄）**を選択してください。 ![no-reply メールアドレス宛のメールを廃棄するチェックボックス](/assets/images/enterprise/management-console/discard-noreply-emails.png) +7. [**Support**] で、リンクの種類を選択してユーザに追加のサポートを提供します。 - **Email:** An internal email address. - - **URL:** A link to an internal support site. You must include either `http://` or `https://`. - ![Support email or URL](/assets/images/enterprise/management-console/support-email-url.png) -8. [Test email delivery](#testing-email-delivery). + - **URL:** A link to an internal support site. `http://` または `https://` を含める必要があります。 ![サポートのメールあるいは URL](/assets/images/enterprise/management-console/support-email-url.png) +8. [メール配信のテスト](#testing-email-delivery)。 {% elsif ghae %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.email-tab %} -2. Select **Enable email**. - !["Enable" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-enable-email-configure.png) -3. Type the settings for your email server. - - In the **Server address** field, type the address of your SMTP server. - - In the **Port** field, type the port that your SMTP server uses to send email. - - In the **Domain** field, type the domain name that your SMTP server will send with a HELO response, if any. - - Select the **Authentication** dropdown, and choose the type of encryption used by your SMTP server. - - In the **No-reply email address** field, type the email address to use in the From and To fields for all notification emails. -4. If you want to discard all incoming emails that are addressed to the no-reply email address, select **Discard email addressed to the no-reply email address**. - !["Discard" checkbox for email settings configuration](/assets/images/enterprise/configuration/ae-discard-email.png) -5. Click **Test email settings**. - !["Test email settings" button for email settings configuration](/assets/images/enterprise/configuration/ae-test-email.png) -6. Under "Send test email to," type the email address where you want to send a test email, then click **Send test email**. - !["Send test email" button for email settings configuration](/assets/images/enterprise/configuration/ae-send-test-email.png) -7. Click **Save**. - !["Save" button for enterprise support contact configuration](/assets/images/enterprise/configuration/ae-save.png) +2. **Enable email（メールの有効化）**を選択してください。 ![メール設定の [Enable] チェックボックス](/assets/images/enterprise/configuration/ae-enable-email-configure.png) +3. メールサーバーの設定を入力します。 + - [**Server address**] フィールドに SMTP サーバのアドレスを入力します。 + - [**Port**] フィールドには、SMTP サーバがメールを送信するのに使用するポートを入力します。 + - [**Domain**] フィールドには、SMTP サーバが HELO レスポンスを送信するドメイン名があれば入力してください。 + - [**Authentication**] ドロップダウンを選択し、SMTP サーバーで使用される暗号化の種類を選択します。 + - [**No-reply email address（No-replyメールアドレス）**] フィールドには、すべての通知メールの From および To フィールドに使うメールアドレスを入力してください。 +4. no-replyメールアドレスへの着信メールをすべて破棄したい場合には、**Discard email addressed to the no-reply email address（no-replyメールアドレスへのメールの破棄）**を選択してください。 ![メール設定の [Discard] チェックボックス](/assets/images/enterprise/configuration/ae-discard-email.png) +5. [**Test email settings**] をクリックします。 ![メール設定の [Test email settings] ボタン](/assets/images/enterprise/configuration/ae-test-email.png) +6. [Send test email to] で、テストメールを送信するメールアドレスを入力し、[**Send test email**] をクリックします。 ![メール設定の [Send test email] ボタン](/assets/images/enterprise/configuration/ae-send-test-email.png) +7. [**Save**] をクリックします。 ![Enterprise サポート連絡先設定の [Save] ボタン](/assets/images/enterprise/configuration/ae-save.png) {% endif %} {% ifversion ghes %} -## Testing email delivery +## メール配信のテスト -1. At the top of the **Email** section, click **Test email settings**. -![Test email settings](/assets/images/enterprise/management-console/test-email.png) -2. In the **Send test email to** field, type an address to send the test email to. -![Test email address](/assets/images/enterprise/management-console/test-email-address.png) -3. Click **Send test email**. -![Send test email](/assets/images/enterprise/management-console/test-email-address-send.png) +1. **Email（メール）**セクションの上部で、**Test email settings（メール設定のテスト）**をクリックしてください。 ![メール設定のテスト](/assets/images/enterprise/management-console/test-email.png) +2. **Send test email to（テストメールの送信先）**フィールドに、テストメールを送信するアドレスを入力してください。 ![メールアドレスのテスト](/assets/images/enterprise/management-console/test-email-address.png) +3. **Send test email（テストメールの送信）**をクリックしてください。 ![テストメールの送信](/assets/images/enterprise/management-console/test-email-address-send.png) {% tip %} - **Tip:** If SMTP errors occur while sending a test email—such as an immediate delivery failure or an outgoing mail configuration error—you will see them in the Test email settings dialog box. + **Tip：**即時の配信失敗や送出メール設定のエラーなど、テストメールの送信時にSMTPエラーが生じたなら、それらはTest email settingsダイアログボックスに表示されます。 {% endtip %} -4. If the test email fails, [troubleshoot your email settings](#troubleshooting-email-delivery). -5. When the test email succeeds, at the bottom of the page, click **Save settings**. -![Save settings button](/assets/images/enterprise/management-console/save-settings.png) +4. テストメールが失敗したなら[メール設定のトラブルシューティング](#troubleshooting-email-delivery)をしてください。 +5. テストメールが成功したなら、ページの下部で**Save settings（設定の保存）**をクリックしてください。 ![設定保存のボタン](/assets/images/enterprise/management-console/save-settings.png) {% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %} -## Configuring DNS and firewall settings to allow incoming emails +## メール着信を許可する DNS とファイアウォールの設定 -If you want to allow email replies to notifications, you must configure your DNS settings. +通知へのメールでの返信を許可したいなら、DNSを設定しなければなりません。 -1. Ensure that port 25 on the instance is accessible to your SMTP server. -2. Create an A record that points to `reply.[hostname]`. Depending on your DNS provider and instance host configuration, you may be able to instead create a single A record that points to `*.[hostname]`. -3. Create an MX record that points to `reply.[hostname]` so that emails to that domain are routed to the instance. -4. Create an MX record that points `noreply.[hostname]` to `[hostname]` so that replies to the `cc` address in notification emails are routed to the instance. For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}." +1. インスタンスのポート25がSMTPサーバにアクセスできることを確認してください。 +2. `reply.[hostname]`を指すAレコードを作成してください。 DNSプロバイダとインスタンスのホスト設定によっては、 `*.[hostname]`を指す単一のAレコードを作成できる場合があります。 +3. `reply.[hostname]`を指すMXレコードを作成して、このドメインへのメールがインスタンスにルーティングされるようにしてください。 +4. `noreply.[hostname]` が `[hostname]` を指すようにする MX レコードを作成し、 通知メールの `cc` アドレスへの返信がインスタンスにルーティングされるようにしてください。 詳しい情報については、{% ifversion ghes %}「[通知を設定する](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}「[メール通知について](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}」を参照してください。 -## Troubleshooting email delivery +## メール配信のトラブルシューティング -### Create a Support Bundle +### Support Bundleの作成 If you cannot determine what is wrong from the displayed error message, you can download a [support bundle](/enterprise/{{ currentVersion }}/admin/guides/enterprise-support/providing-data-to-github-support) containing the entire SMTP conversation between your mail server and {% data variables.product.prodname_ghe_server %}. Once you've downloaded and extracted the bundle, check the entries in *enterprise-manage-logs/unicorn.log* for the entire SMTP conversation log and any related errors. -The unicorn log should show a transaction similar to the following: +unicornログは以下のようなトランザクションになっているはずです。 ```shell This is a test email generated from https://10.0.0.68/setup/settings @@ -137,18 +120,18 @@ TLS connection started -> "535 5.7.1 http://support.yourdomain.com/smtp/auth-not-accepted nt3sm2942435pbc.14\r\n" ``` -This log shows that the appliance: +このログからは、アプライアンスについて以下のことが分かります。 -* Opened a connection with the SMTP server (`Connection opened: smtp.yourdomain.com:587`). -* Successfully made a connection and chose to use TLS (`TLS connection started`). -* The `login` authentication type was performed (`<- "AUTH LOGIN\r\n"`). -* The SMTP Server rejected the authentication as invalid (`-> "535-5.7.1 Username and Password not accepted.`). +* SMTPサーバとのコネクションを開いている（`Connection opened: smtp.yourdomain.com:587`）。 +* コネクションの作成には成功し、TLSの使用を選択している（`TLS connection started`）。 +* `login`認証が実行されている（`<- "AUTH LOGIN\r\n"`）。 +* SMTPサーバは、認証を不正として拒否している（`-> "535-5.7.1 Username and Password not accepted.`）。 -### Check {% data variables.product.product_location %} logs +### {% data variables.product.product_location %}ログのチェック -If you need to verify that your inbound email is functioning, there are two log files that you can examine on your instance: To verify that */var/log/mail.log* and */var/log/mail-replies/metroplex.log*. +インバウンドのメールが機能していることを検証する必要がある場合、インスタンスの */var/log/mail.log* と */var/log/mail-replies/metroplex.log* との 2 つのログファイルを検証してください。 -*/var/log/mail.log* verifies that messages are reaching your server. Here's an example of a successful email reply: +*/var/log/mail.log* verifies that messages are reaching your server. 以下は、成功したメールの返信の例です: ``` Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250] @@ -160,9 +143,9 @@ Oct 30 00:47:19 54-171-144-1 postfix/qmgr[17250]: 51DC9163323: removed Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: disconnect from st11p06mm-asmtp002.mac.com[17.172.124.250] ``` -Note that the client first connects; then, the queue becomes active. Then, the message is delivered, the client is removed from the queue, and the session disconnects. +クライアントがまず接続し、続いてキューがアクティブになっていることに注意してください。 そしてメッセージが配信され、クライアントがキューから削除され、セッションが切断されています。 -*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. Here's an example of a successful message: +*/var/log/mail-replies/metroplex.log* shows whether inbound emails are being processed to add to issues and pull requests as replies. 以下は成功したメッセージの例です: ``` [2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing @@ -170,19 +153,19 @@ Note that the client first connects; then, the queue becomes active. Then, the m [2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success ``` -You'll notice that `metroplex` catches the inbound message, processes it, then moves the file over to `/data/user/incoming-mail/success`.{% endif %} +`metroplex` がインバウンドのメッセージをキャッチして処理し、ファイルを `/data/user/incoming-mail/success` に移動します。{% endif %} -### Verify your DNS settings +### DNS設定の検証 -In order to properly process inbound emails, you must configure a valid A Record (or CNAME), as well as an MX Record. For more information, see "[Configuring DNS and firewall settings to allow incoming emails](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)." +インバウンドのメールを適切に処理するには、適切にAレコード（あるいはCNAME）と共にMXレコードを設定しなければなりません。 詳しい情報については、「[着信メールを許可するよう DNS およびファイアウォールを設定する](#configuring-dns-and-firewall-settings-to-allow-incoming-emails)」を参照してください。 -### Check firewall or AWS Security Group settings +### ファイアウォールあるいはAWSセキュリティグループの設定のチェック If {% data variables.product.product_location %} is behind a firewall or is being served through an AWS Security Group, make sure port 25 is open to all mail servers that send emails to `reply@reply.[hostname]`. -### Contact support +### サポートへの連絡 {% ifversion ghes %} -If you're still unable to resolve the problem, contact {% data variables.contact.contact_ent_support %}. Please attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email to help us troubleshoot your problem. +依然として問題が解決できない場合は、{% data variables.contact.contact_ent_support %} に連絡してください。 問題のトラブルシューティングを支援するため、メールには`http(s)://[hostname]/setup/diagnostics`からの出力ファイルを添付してください。 {% elsif ghae %} -You can contact {% data variables.contact.github_support %} for help configuring email for notifications to be sent through your SMTP server. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)." +You can contact {% data variables.contact.github_support %} for help configuring email for notifications to be sent through your SMTP server. 詳しい情報については、「[{% data variables.contact.github_support %} からの支援を受ける](/admin/enterprise-support/receiving-help-from-github-support)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md new file mode 100644 index 0000000000..67bb383325 --- /dev/null +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md @@ -0,0 +1,76 @@ +--- +title: Configuring web commit signing +shortTitle: Configure web commit signing +intro: 'You can enable auto-signing of commits made in the web interface of {% data variables.product.product_name %}.' +versions: + ghes: '>=3.5' +type: how_to +topics: + - Access management + - Enterprise + - Fundamentals + - Identity + - Security +permissions: 'Site administrators can configure web commit signing for {% data variables.product.product_location %}.' +--- + +## About web commit signing + +If you enable web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits users make on the web interface of {% data variables.product.product_location %}. Commits signed by {% data variables.product.product_name %} will have a verified status. 詳細については、「[コミット署名の検証について](/authentication/managing-commit-signature-verification/about-commit-signature-verification)」を参照してください。 + +You can enable web commit signing, rotate the private key used for web commit signing, and disable web commit signing. + +## Enabling web commit signing + +{% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} + - If you have a no-reply email address defined in the {% data variables.enterprise.management_console %}, use that email address. If not, use any email address, such as `web-flow@my-company.com`. The email address does not need to be valid. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +1. Enable web commit signing. + + ```bash{:copy} + ghe-config app.github.web-commit-signing-enabled true + ``` +1. Apply the configuration, then wait for the configuration run to complete. + + ```bash{:copy} + ghe-config-apply + ``` +1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." + - The user's username must be `web-flow`. + - The user's email address must be the same address you used for the PGP key. +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} +{% data reusables.enterprise_site_admin_settings.email-settings %} +1. Under "No-reply email address", type the same email address you used for the PGP key. + + {% note %} + + **Note:** The "No-reply email address" field will only be displayed if you've enabled email for {% data variables.product.product_location %}. 詳しい情報については、「[通知のためのメールを設定する](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications#configuring-smtp-for-your-enterprise)」を参照してください。 + + {% endnote %} +{% data reusables.enterprise_management_console.save-settings %} + +## Rotating the private key used for web commit signing + +{% data reusables.enterprise_site_admin_settings.create-pgp-key-web-commit-signing %} + - Use the no-reply email address defined in the {% data variables.enterprise.management_console %}, which should be the same as the email address of the `web-flow` user. +{% data reusables.enterprise_site_admin_settings.pgp-key-no-passphrase %} +{% data reusables.enterprise_site_admin_settings.pgp-key-env-variable %} +{% data reusables.enterprise_site_admin_settings.update-commit-signing-service %} +{% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} + +## Disabling web commit signing + +You can disable web commit signing for {% data variables.product.product_location %}. + +1. In the administrative shell, run the following command. + + ```bash{:copy} + ghe-config app.github.web-commit-signing-enabled false + ``` +1. 設定を適用します。 + + ```bash{:copy} + ghe-config-apply + ``` diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md index f8ac88c84a..782c9dc076 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md @@ -33,12 +33,20 @@ shortTitle: Configure maintenance mode メンテナンスウィンドウのスケジュールは、ユーザに準備時間を与えるために少なくとも30分は先にすることをおすすめします。 メンテナンスウィンドウがスケジューリングされると、すべてのユーザにはサイトにアクセスしたときにバナーが表示されます。 + + ![スケジューリングされたメンテナンスに関するエンドユーザ向けバナー](/assets/images/enterprise/maintenance/maintenance-scheduled.png) インスタンスがメンテナンスモードに入ると、通常のHTTP及びGitアクセスはすべて拒否されます。 Git fetch、clone、pushの操作も、サイトが一時的に利用できなくなっていることを示すエラーメッセージと共に拒否されます。 In high availability configurations, Git replication will be paused. GitHub Actions jobs will not be executed. サイトにブラウザーでアクセスすると、メンテナンスページが表示されます。 ![メンテナンスモードのスプラッシュスクリーン](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png) +{% if ip-exception-list %} + +You can perform initial validation of your maintenance operation by configuring an IP exception list to allow access to {% data variables.product.product_location %} from only the IP addresses and ranges provided. Attempts to access {% data variables.product.product_location %} from IP addresses not specified on the IP exception list will receive a response consistent with those sent when the instance is in maintenance mode. + +{% endif %} + ## メンテナンスモードの即時有効化あるいは後のためのメンテナンスウィンドウのスケジューリング {% data reusables.enterprise_site_admin_settings.access-settings %} @@ -50,6 +58,23 @@ shortTitle: Configure maintenance mode 4. **Enable maintenance mode（メンテナンスモードの有効化）**を選択してください。 ![メンテナンスモードの有効化とスケジューリングのためのチェックボックス](/assets/images/enterprise/maintenance/enable-maintenance-mode-checkbox.png) {% data reusables.enterprise_management_console.save-settings %} +{% if ip-exception-list %} + +## Validating changes in maintenance mode using the IP exception list + +The IP exception list provides controlled and restricted access to {% data variables.product.product_location %}, which is ideal for initial validation of server health following a maintenance operation. Once enabled, {% data variables.product.product_location %} will be taken out of maintenance mode and available only to the configured IP addresses. The maintenance mode checkbox will be updated to reflect the change in state. + +If you re-enable maintenance mode, the IP exception list will be disabled and {% data variables.product.product_location %} will return to maintenance mode. If you just disable the IP exception list, {% data variables.product.product_location %} will return to normal operation. + +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +1. At the top of the {% data variables.enterprise.management_console %}, click **Maintenance**, and confirm maintenance mode is already enabled. ![[Maintenance] タブ](/assets/images/enterprise/management-console/maintenance-tab.png) +1. Select **Enable IP exception list**. ![Checkbox for enabling ip exception list](/assets/images/enterprise/maintenance/enable-ip-exception-list.png) +1. In the text box, type a valid list of space-separated IP addresses or CIDR blocks that should be allowed to access {% data variables.product.product_location %}. ![completed field for IP addresses](/assets/images/enterprise/maintenance/ip-exception-list-ip-addresses.png) +1. [**Save**] をクリックします。 ![after IP excetpion list has saved](/assets/images/enterprise/maintenance/ip-exception-save.png) + +{% endif %} + ## {% data variables.product.prodname_enterprise_api %}でのメンテナンスモードのスケジューリング {% data variables.product.prodname_enterprise_api %}では、様々な時間や日付にメンテナンスをスケジューリングできます。 詳しい情報については、「[Management Console](/enterprise/{{ currentVersion }}/user/rest/reference/enterprise-admin#enable-or-disable-maintenance-mode)」を参照してください。 diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md index b8699d8deb..0614d6eacd 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/index.md @@ -36,6 +36,7 @@ children: - /configuring-github-pages-for-your-enterprise - /configuring-the-referrer-policy-for-your-enterprise - /configuring-custom-footers + - /configuring-web-commit-signing shortTitle: Configure your enterprise --- diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md index 61b681ed8b..0de266deb6 100644 --- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md +++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md @@ -16,6 +16,12 @@ shortTitle: Increase CPU or memory --- {% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %} +{% note %} + +**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% if ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." + +{% endnote %} + ## Adding CPU or memory resources for AWS {% note %} diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md index 383cc400e8..200e7aee65 100644 --- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md +++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md @@ -24,7 +24,7 @@ shortTitle: Increase storage capacity {% note %} -**Note:** Before resizing any storage volume, put your instance in maintenance mode. 詳しい情報については"[メンテナンスモードの有効化とスケジューリング](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)"を参照してください。 +**Note:** Before resizing any storage volume, put your instance in maintenance mode.{% if ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[Enabling and scheduling maintenance mode](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-and-scheduling-maintenance-mode)." {% endnote %} diff --git a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md index 1c16eab175..e78b3ad651 100644 --- a/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md @@ -174,6 +174,9 @@ High Availability と Geo-replication が設定されたアプライアンスは Target root partition: /dev/xvda2 Proceed with installation? [y/N] ``` +{% if ip-exception-list %} +1. Optionally, to validate the upgrade, configure an IP exception list to allow access to a specified list of IP addresses. For more information, see "[Validating changes in maintenance mode using the IP exception list](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." +{% endif %} 7. 単一アプライアンスのアップグレードであれば、メンテナンスモードを無効化してユーザが {% data variables.product.product_location %} を利用できるようにしてください。 {% note %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md index 309655b87e..1bc068bda4 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with Amazon S3 storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store artifacts generated by workflow runs.' +title: Amazon S3 ストレージで GitHub Actions を有効化する +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Amazon S3 storage to store data generated by workflow runs.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -14,17 +14,18 @@ redirect_from: - /admin/github-actions/enabling-github-actions-with-amazon-s3-storage shortTitle: Amazon S3 storage --- -## Prerequisites + +## 必要な環境 {% data reusables.actions.enterprise-s3-support-warning %} -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 + +* Create your Amazon S3 bucket for storing data generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} -* Create your Amazon S3 bucket for storing artifacts generated by workflow runs. {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} - {% data reusables.actions.enterprise-common-prereqs %} -## Enabling {% data variables.product.prodname_actions %} with Amazon S3 storage +## Amazon S3 ストレージで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.actions.perform-blob-storage-precheck %} @@ -32,15 +33,15 @@ Before enabling {% data variables.product.prodname_actions %}, make sure you hav {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: +1. [Artifact & Log Storage] で、[**Amazon S3**] を選択し、ストレージバケットの詳細を入力します。 - * **AWS Service URL**: The service URL for your bucket. For example, if your S3 bucket was created in the `us-west-2` region, this value should be `https://s3.us-west-2.amazonaws.com`. + * **AWS Service URL**: バケットのサービス URL。 たとえば、S3 バケットが `us-west-2` リージョンで作成された場合、この値は `https://s3.us-west-2.amazonaws.com` である必要があります。 - For more information, see "[AWS service endpoints](https://docs.aws.amazon.com/general/latest/gr/rande.html)" in the AWS documentation. - * **AWS S3 Bucket**: The name of your S3 bucket. - * **AWS S3 Access Key** and **AWS S3 Secret Key**: The AWS access key ID and secret key for your bucket. For more information on managing AWS access keys, see the "[AWS Identity and Access Management Documentation](https://docs.aws.amazon.com/iam/index.html)." + 詳しい情報については、AWS ドキュメントの「[AWS サービスエンドポイント](https://docs.aws.amazon.com/general/latest/gr/rande.html)」を参照してください。 + * **AWS S3 Bucket**: S3 バケットの名前。 + * **AWS S3 Access Key** および **AWS S3 Secret Key**: バケットの AWS アクセスキー IDと シークレットキー。 AWS アクセスキーの管理の詳細については、「[AWS ID およびアクセス管理のドキュメント](https://docs.aws.amazon.com/iam/index.html)」を参照してください。 - ![Radio button for selecting Amazon S3 Storage and fields for S3 configuration](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) + ![Amazon S3 ストレージを選択するためのラジオボタンと S3 設定のフィールド](/assets/images/enterprise/management-console/actions-aws-s3-storage.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md index cb73b7f4fa..10d298ac33 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with Azure Blob storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store artifacts generated by workflow runs.' +title: Azure Blob ストレージで GitHub Actions を有効化する +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use Azure Blob storage to store data generated by workflow runs.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -12,26 +12,27 @@ topics: - Storage redirect_from: - /admin/github-actions/enabling-github-actions-with-azure-blob-storage -shortTitle: Azure Blob storage +shortTitle: Azure Blob ストレージ --- -## Prerequisites -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: +## 必要な環境 -* Create your Azure storage account for storing workflow artifacts. {% data variables.product.prodname_actions %} stores its data as block blobs, and two storage account types are supported: - * A **general-purpose** storage account (also known as `general-purpose v1` or `general-purpose v2`) using the **standard** performance tier. +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 + +* Create your Azure storage account for storing workflow data. {% data variables.product.prodname_actions %} はデータをブロック Blob として保存し、次の 2 つのストレージアカウントタイプがサポートされています。 + * **標準**のパフォーマンス層を使用する **general-purpose** ストレージアカウント (`general-purpose v1` または `general-purpose v2` としても知られる)。 {% warning %} - **Warning:** Using the **premium** performance tier with a general-purpose storage account is not supported. The **standard** performance tier must be selected when creating the storage account, and it cannot be changed later. + **Warning:** general-purpose ストレージアカウントでの**プレミアム**パフォーマンス層の使用はサポートされていません。 ストレージアカウントを作成するときに**標準**のパフォーマンス層を選択する必要があり、後で変更することはできません。 {% endwarning %} - * A **BlockBlobStorage** storage account, which uses the **premium** performance tier. + * **プレミアム**パフォーマンス層を使用する **BlockBlobStorage** ストレージアカウント。 - For more information on Azure storage account types and performance tiers, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts). + Azure ストレージアカウントの種類とパフォーマンス層の詳細については、[Azure のドキュメント](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview?toc=/azure/storage/blobs/toc.json#types-of-storage-accounts)を参照してください。 {% data reusables.actions.enterprise-common-prereqs %} -## Enabling {% data variables.product.prodname_actions %} with Azure Blob storage +## Azure Blob ストレージで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.actions.perform-blob-storage-precheck %} @@ -39,8 +40,7 @@ Before enabling {% data variables.product.prodname_actions %}, make sure you hav {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Azure Blob Storage**, and enter your Azure storage account's connection string. For more information on getting the connection string for your storage account, see the [Azure documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys). - ![Radio button for selecting Azure Blob Storage and the Connection string field](/assets/images/enterprise/management-console/actions-azure-storage.png) +1. [Artifact & Log Storage] で、[**Azure Blob Storage**] を選択し、Azure ストレージアカウントの接続文字列型を入力します。 ストレージアカウントの接続文字列型を取得する方法について詳しくは、[Azure のドキュメント](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage?tabs=azure-portal#view-account-access-keys)を参照してください。 ![[Azure Blob Storage] と [Connection string] フィールドを選択するためのラジオボタン](/assets/images/enterprise/management-console/actions-azure-storage.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md index 514ab779d4..9ad28dcff6 100644 --- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md +++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md @@ -1,6 +1,6 @@ --- -title: Enabling GitHub Actions with MinIO Gateway for NAS storage -intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store artifacts generated by workflow runs.' +title: NAS ストレージ用の MinIO ゲートウェイで GitHub Actions を有効化する +intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO Gateway for NAS storage to store data generated by workflow runs.' permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.' versions: ghes: '*' @@ -15,22 +15,18 @@ redirect_from: shortTitle: MinIO Gateway for NAS storage --- -{% warning %} +{% data reusables.actions.minio-gateways-removal %} -**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. +## 必要な環境 -{% endwarning %} +{% data variables.product.prodname_actions %} を有効化する前に、次のステップを完了していることを確認してください。 -## Prerequisites +* アプライアンスでのリソースの競合を回避するために、MinIO を {% data variables.product.product_location %} とは別にホストすることをお勧めします。 +* Create your bucket for storing workflow data. バケットとアクセスキーを設定するには、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} -Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps: - -* To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.product.product_location %}. -* Create your bucket for storing workflow artifacts. To set up your bucket and access key, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). {% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} - {% data reusables.actions.enterprise-common-prereqs %} -## Enabling {% data variables.product.prodname_actions %} with MinIO Gateway for NAS storage +## NAS ストレージ用の MinIO ゲートウェイで {% data variables.product.prodname_actions %} を有効化する {% data reusables.enterprise_installation.ssh-into-instance %} {% data reusables.actions.perform-blob-storage-precheck %} @@ -38,15 +34,14 @@ Before enabling {% data variables.product.prodname_actions %}, make sure you hav {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %} -1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details: +1. [Artifact & Log Storage] で、[**Amazon S3**] を選択し、ストレージバケットの詳細を入力します。 - * **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`. - * **AWS S3 Bucket**: The name of your S3 bucket. - * **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance. For more information, see the [MinIO documentation](https://docs.min.io/docs/minio-gateway-for-nas.html). + * **AWS Service URL**: MinIO サービスへの URL。 たとえば、`https://my-minio.example:9000` などです。 + * **AWS S3 Bucket**: S3 バケットの名前。 + * **AWS S3 Access Key** および **AWS S3 Secret Key**: MinIO インスタンスに使用される `MINIO_ACCESS_KEY` および `MINIO_SECRET_KEY`。 詳しい情報については、[MinIO のドキュメント](https://docs.min.io/docs/minio-gateway-for-nas.html)を参照してください。 - ![Radio button for selecting Amazon S3 Storage and fields for MinIO configuration](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) -1. Under "Artifact & Log Storage", select **Force path style**. - ![Checkbox to Force path style](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) + ![Amazon S3 ストレージを選択するためのラジオボタンと MinIO 設定のフィールド](/assets/images/enterprise/management-console/actions-minio-s3-storage.png) +1. [Artifact & Log Storage] で [**Force path style**] を選択します。 ![[Force path style] チェックボックス](/assets/images/enterprise/management-console/actions-minio-force-path-style.png) {% data reusables.enterprise_management_console.save-settings %} {% data reusables.actions.enterprise-postinstall-nextsteps %} diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index b0313604d2..19a28786f4 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -39,7 +39,7 @@ You can create your own unique automations, or you can use and adapt workflows f {% ifversion ghec %}You can enjoy the convenience of {% data variables.product.company_short %}-hosted runners, which are maintained and upgraded by {% data variables.product.company_short %}, or you{% else %}You{% endif %} can control your own private CI/CD infrastructure by using self-hosted runners. Self-hosted runners allow you to determine the exact environment and resources that complete your builds, testing, and deployments, without exposing your software development cycle to the internet. For more information, see {% ifversion ghec %}"[About {% data variables.product.company_short %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and{% endif %} "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." -{% data variables.product.prodname_actions %} provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %} +{% data variables.product.prodname_actions %} provides greater control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets.{% ifversion ghec or ghae-issue-4856 or ghes > 3.4 %} If your workflows need to access resources from a cloud provider that supports OpenID Connect (OIDC), you can configure your workflows to authenticate directly to the cloud provider. OIDC provides security benefits such as eliminating the need to store credentials as long-lived secrets. For more information, see "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)."{% endif %} {% data variables.product.prodname_actions %} also includes tools to govern your enterprise's software development cycle and meet compliance obligations. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)." diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md index 9321667ae6..73c5b2b8bc 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md @@ -25,7 +25,7 @@ This article explains how site administrators can configure {% data variables.pr {% data reusables.enterprise.upgrade-ghes-for-actions %} -{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. +{% data reusables.actions.ghes-actions-not-enabled-by-default %} You'll need to determine whether your instance has adequate CPU and memory resources to handle the load from {% data variables.product.prodname_actions %} without causing performance loss, and possibly increase those resources. You'll also need to decide which storage provider you'll use for the blob storage required to store artifacts{% if actions-caching %} and caches{% endif %} generated by workflow runs. Then, you'll enable {% data variables.product.prodname_actions %} for your enterprise, manage access permissions, and add self-hosted runners to run workflows. {% data reusables.actions.introducing-enterprise %} @@ -104,7 +104,7 @@ Optionally, you can limit resource consumption on {% data variables.product.prod To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage. -{% data variables.product.prodname_actions %} uses blob storage to store artifacts generated by workflow runs, such as workflow logs and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. +{% data variables.product.prodname_actions %} uses blob storage to store data generated by workflow runs, such as workflow logs{% if actions-caching %}, caches,{% endif %} and user-uploaded build artifacts. The amount of storage required depends on your usage of {% data variables.product.prodname_actions %}. Only a single external storage configuration is supported, and you can't use multiple storage providers at the same time. {% data variables.product.prodname_actions %} supports these storage providers: @@ -118,6 +118,8 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro {% endnote %} +{% data reusables.actions.minio-gateways-removal %} + Before you enable {% data variables.product.prodname_actions %}, you can test your storage configuration from the administrative shell with the `ghe-actions-precheck` utility. For more information, see "[Command-line utilities](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-actions-check)" and "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)." ## Networking considerations diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md index 1cdcda101a..109ae9815c 100644 --- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md @@ -111,20 +111,18 @@ Finally, you should consider security hardening for self-hosted runners. For mor {% data reusables.actions.about-artifacts %} For more information, see "[Storing workflow data as artifacts](/actions/advanced-guides/storing-workflow-data-as-artifacts)." -![Screenshot of artifact](/assets/images/help/repository/passing-data-between-jobs-in-a-workflow-updated.png) +{% if actions-caching %}{% data variables.product.prodname_actions %} also has a caching system that you can use to cache dependencies to speed up workflow runs. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."{% endif %} {% ifversion ghes %} -You must configure external blob storage for these artifacts. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." +You must configure external blob storage for workflow artifacts{% if actions-caching %}, caches,{% endif %} and other workflow logs. Decide which supported storage provider your enterprise will use. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server#external-storage-requirements)." {% endif %} {% ifversion ghec or ghes %} -{% data reusables.actions.artifact-log-retention-statement %} +You can use policy settings for {% data variables.product.prodname_actions %} to customize the storage of workflow artifacts{% if actions-caching %}, caches,{% endif %} and log retention. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_actions %}のポリシーの施行](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)」を参照してください。 {% endif %} -If you want to retain logs and artifacts longer than the upper limit you can configure in {% data variables.product.product_name %}, you'll have to plan how to export and store the data. - {% ifversion ghec %} Some storage is included in your subscription, but additional storage will affect your bill. You should plan for this cost. 詳しい情報については、「[{% data variables.product.prodname_actions %}の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md index 35f11511a9..4f7efdb517 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md @@ -16,19 +16,27 @@ topics: - SSO --- +{% ifversion ghec %} +{% note %} + +**Note:** This article only applies to {% data variables.product.prodname_emus %}. If you use {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, usernames are created by users, not {% data variables.product.prodname_dotcom %}. + +{% endnote %} +{% endif %} + ## About usernames with external authentication {% ifversion ghes %} -You can configure external authentication for {% data variables.product.product_name %} using CAS, LDAP, or SAML. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." +You can configure external authentication for {% data variables.product.product_name %} using CAS, LDAP, or SAML. 詳しい情報については「[Enterpriseでの認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)」を参照してください。 When you use external authentication, {% data variables.product.product_location %} automatically creates a username for each person when the person signs into {% data variables.product.product_location %} through your external authentication system for the first time. {% elsif ghec %} -If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." +If you use an enterprise with {% data variables.product.prodname_emus %}, members of your enterprise authenticate to access {% data variables.product.prodname_dotcom %} through your SAML identity provider (IdP). For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)" and "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-server)." -{% data variables.product.product_name %} automatically creates a username for each person when the person signs in through your IdP for the first time. +{% data variables.product.product_name %} automatically creates a username for each person when their user account is provisioned via SCIM, by normalizing an identifier provided by your IdP. If multiple identifiers are normalized into the same username, a username conflict occurs, and only the first user account is created. You can resolve username conflicts by making a change in your IdP so that the normalized usernames will be unique. {% elsif ghae %} @@ -36,32 +44,63 @@ If you use an enterprise with {% data variables.product.prodname_emus %}, member {% endif %} +{% ifversion ghec %} +## About usernames for {% data variables.product.prodname_managed_users %} + +When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. + +When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. The IDP-USERNAME component is formed by normalizing the SCIM `userName` attribute value sent from the IdP. + +| Identity provider | {% data variables.product.prodname_dotcom %} username | +| --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Azure Active Directory (Azure AD) | _IDP-USERNAME_ is formed by normalizing the characters preceding the `@` character in the UPN (User Principal Name), which does not include the `#EXT#` for guest accounts. | +| Okta | _IDP-USERNAME_ is the normalized username attribute provided by the IdP. | + +These rules may result in your IdP providing the same _IDP-USERNAME_ for multiple users. For example, for Azure AD, the following UPNs will result in the same username: + +- `bob@contoso.com` +- `bob@fabrikam.com` +- `bob#EXT#fabrikamcom@contoso.com` + +This will cause a username conflict, and only the first user will be provisioned. For more information, see "[Resolving username conflicts](#resolving-username-conflicts)." +{% endif %} + +Usernames{% ifversion ghec %}, including underscore and short code,{% endif %} must not exceed 39 characters. + ## About username normalization Usernames for user accounts on {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %} can only contain alphanumeric characters and dashes (`-`). -{% ifversion ghec or ghes %}When you configure {% ifversion ghes %}CAS, LDAP, or {% endif %}SAML authentication, {% endif %}{% data variables.product.product_name %} uses an identifier from the user account on your {% ifversion ghes %}external authentication provider{% elsif ghec or ghae %}IdP{% endif %} to determine the username for the corresponding user account on {% ifversion ghes or ghae %}{% data variables.product.product_name %}{% elsif ghec %}{% data variables.product.prodname_dotcom_the_website %}{% endif %}. If the identifier for the account on your provider includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules. +{% ifversion ghec %} +When you configure SAML authentication, {% data variables.product.product_name %} uses the SCIM `userName` attribute value sent from the IdP to determine the username for the corresponding user account on {% data variables.product.prodname_dotcom_the_website %}. If this value includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules. +{% elsif ghes %} +When you configure CAS, LDAP, or SAML authentication, {% data variables.product.product_name %} uses an identifier from the user account on your external authentication provider to determine the username for the corresponding user account on {% data variables.product.product_name %}. If the identifier includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules. +{% elsif ghae %} +When you configure SAML authentication, {% data variables.product.product_name %} uses an identifier from the user account on your IdP to determine the username for the corresponding user account on {% data variables.product.product_name %}. If the identifier includes unsupported characters, {% data variables.product.product_name %} will normalize the username per the following rules. +{% endif %} -1. {% data variables.product.product_name %} will normalize any non-alphanumeric character in your account's username into a dash. For example, a username of `mona.the.octocat` will be normalized to `mona-the-octocat`. 変換されたユーザ名の先頭及び末尾はダッシュであってはならないことに注意してください。 2つの連続するダッシュを含めることもできません。 +1. {% data variables.product.product_name %}は、アカウントのユーザ名に含まれている非英数字をダッシュに変換します。 For example, a username of `mona.the.octocat` will be normalized to `mona-the-octocat`. 変換されたユーザ名の先頭及び末尾はダッシュであってはならないことに注意してください。 2つの連続するダッシュを含めることもできません。 1. メールアドレスから作成されたユーザ名は、`@`以前の文字を変換して作成されます。 -1. If multiple accounts are normalized into the same {% data variables.product.product_name %} username, only the first user account is created. 同じユーザ名のそれ以降のユーザは、サインインできません。 +1. 複数のアカウントが変換後に同じ{% data variables.product.product_name %}のユーザ名になる場合、最初のユーザアカウントだけが作成されます。 同じユーザ名のそれ以降のユーザは、サインインできません。 {% ifversion ghec %}For more information, see "[Resolving username conflicts](#resolving-username-conflicts)."{% endif %} ### Examples of username normalization -| Identifier on provider | Normalized username for {% data variables.product.product_location %} | 結果 | -|:----------------------- |:--------------------------------------------------------------------- |:------------------------------------------- | -| The.Octocat | `the-octocat` | このユーザ名の作成は成功します。 | -| !The.Octocat | `-the-octocat` | このユーザ名はダッシュで始まるので作成されません。 | -| The.Octocat! | `the-octocat-` | このユーザ名はダッシュで終わるので作成されません。 | -| The!!Octocat | `the--octocat` | このユーザ名には連続する2つのダッシュが含まれるので作成されません。 | -| The!Octocat | `the-octocat` | このユーザ名は作成されません。 変換されたユーザ名は正当ですが、すでに存在しています。 | -| The.Octocat@example.com | `the-octocat` | このユーザ名は作成されません。 変換されたユーザ名は正当ですが、すでに存在しています。 | +| Identifier on provider | Normalized username on {% data variables.product.prodname_dotcom %} | 結果 | +|:------------------------------------------------------------- |:------------------------------------------------------------------------------------------- |:------------------------------------------------------------------------ | +| The.Octocat | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名の作成は成功します。 | +| !The.Octocat | `-the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名はダッシュで始まるので作成されません。 | +| The.Octocat! | `the-octocat-{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名はダッシュで終わるので作成されません。 | +| The!!Octocat | `the--octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名には連続する2つのダッシュが含まれるので作成されません。 | +| The!Octocat | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名は作成されません。 変換されたユーザ名は正当ですが、すでに存在しています。 | +| `The.Octocat@example.com` | `the-octocat{% ifversion ghec %}_SHORT-CODE{% endif %}` | このユーザ名は作成されません。 変換されたユーザ名は正当ですが、すでに存在しています。 | +| `mona.lisa.the.octocat.from.github.united.states@example.com` | `mona-lisa-the-octocat-from-github-united-states{% ifversion ghec %}_SHORT-CODE{% endif %}` | This username is not created, because it exceeds the 39-character limit. | +{% ifversion not ghec %} ### About username normalization with SAML -{% ifversion ghec or ghes %}If you {% ifversion ghec %}use an enterprise with {% data variables.product.prodname_emus %}, you must use SAML authentication. {% else %}configure SAML authentication for {% data variables.product.product_location %}, {% endif %}{% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by priority. +{% ifversion ghes %}If you configure SAML authentication for {% data variables.product.product_location %}, {% endif %}{% data variables.product.product_name %} determines each person's username by one of the following assertions in the SAML response, ordered by descending priority. 1. The custom `username` attribute, if defined and present 1. `http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name`アサーション (存在する場合) @@ -70,12 +109,49 @@ Usernames for user accounts on {% ifversion ghes or ghae %}{% data variables.pro {% data variables.product.product_name %} requires the `NameID` element even if other attributes are present. For more information, see "[SAML configuration reference](/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference#saml-attributes)." -{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghec or ghae %}in{% elsif ghes %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. +{% data variables.product.product_name %} creates a mapping between the `NameID` from the IdP and the username {% ifversion ghae %}in{% else %}on{% endif %} {% data variables.product.product_location %}, so the `NameID` should be persistent, unique, and not subject to change for the lifecycle of the user. {% ifversion ghes %} {% note %} -**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when {% ifversion ghec %}authenticating through your IdP to access your resources on{% else %}signing into{% endif} {% data variables.product.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." +**Note**: If the `NameID` for a user does change on the IdP, the person will see an error message when signing into {% data variables.product.product_location %}. To restore the person's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid)." {% endnote %} {% endif %} +{% endif %} + +{% ifversion ghec %} +## Resolving username conflicts + +When a new user is being provisioned, if the user's normalized username conflicts with an existing user in the enterprise, the provisioning attempt will fail with a `409` error. + +To resolve this problem, you must make a change in your IdP so that the normalized usernames will be unique. If you cannot change the identifier that's being normalized, you can change the attribute mapping for the `userName` attribute. If you change the attribute mapping, usernames of existing {% data variables.product.prodname_managed_users %} will be updated, but nothing else about the accounts will change, including activity history. + +{% note %} + +**Note:** {% data variables.contact.github_support %} cannot provide assistance with customizing attribute mappings or configuring custom expressions. You can contact your IdP with any questions. + +{% endnote %} + +### Resolving username conflicts with Azure AD + +To resolve username conflicts in Azure AD, either modify the User Principal Name value for the conflicting user or modify the attribute mapping for the `userName` attribute. If you modify the attribute mapping, you can choose an existing attribute or use an expression to ensure that all provisioned users have a unique normalized alias. + +1. In Azure AD, open the {% data variables.product.prodname_emu_idp_application %} application. +1. In the left sidebar, click **Provisioning**. +1. Click **Edit Provisioning**. +1. Expand **Mappings**, then click **Provision Azure Active Directory Users**. +1. Click the {% data variables.product.prodname_dotcom %} `userName` attribute mapping. +1. Change the attribute mapping. + - To map an existing attribute in Azure AD to the `userName` attribute in {% data variables.product.prodname_dotcom %}, click your desired attribute field. Then, save and wait for a provisioning cycle to occur within about 40 minutes. + - To use an expression instead of an existing attribute, change the Mapping type to "Expression", then add a custom expression that will make this value unique for all users. For example, you could use `[FIRST NAME]-[LAST NAME]-[EMPLOYEE ID]`. For more information, see [Reference for writing expressions for attribute mappings in Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/app-provisioning/functions-for-customizing-application-data) in Microsoft Docs. + +### Resolving username conflicts with Okta + +To resolve username conflicts in Okta, update the attribute mapping settings for the {% data variables.product.prodname_emu_idp_application %} application. + +1. In Okta, open the {% data variables.product.prodname_emu_idp_application %} application. +1. Click **Sign On**. +1. In the "Settings" section, click **Edit**. +1. Update the "Application username format." +{% endif %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md index 3df26d5da0..12577f3412 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md @@ -56,6 +56,7 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e * Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. * {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. * Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. +* {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)」を参照してください。 ## About enterprises with managed users @@ -87,17 +88,8 @@ The setup user's username is your enterprise's shortcode suffixed with `_admin`. ## Usernames and profile information -When your {% data variables.product.prodname_emu_enterprise %} is created, you will choose a short code that will be used as the suffix for your enterprise member's usernames. {% data reusables.enterprise-accounts.emu-shortcode %} The setup user who configures SAML SSO has a username in the format of **@SHORT-CODE_admin**. +{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." -When you provision a new user from your identity provider, the new {% data variables.product.prodname_managed_user %} will have a {% data variables.product.prodname_dotcom %} username in the format of **@IDP-USERNAME_SHORT-CODE**. - -| Identity provider | {% data variables.product.prodname_dotcom %} username | -| --------------------------------- | ----------------------------------------------------- | -| Azure Active Directory (Azure AD) | | -| Okta | | - -It's possible for a conflict to occur when provisioning users if the unique parts of the username provided by your IdP are removed when it is normalized. If you are unable to provision a user due to a username conflict, you should modify the username provided by your IdP. - -The username of the new account provisioned on {% data variables.product.prodname_dotcom %}, including underscore and short code, must not exceed 39 characters. +A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username conflicts](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-conflicts)." The profile name and email address of a {% data variables.product.prodname_managed_user %} is also provided by the IdP. {% data variables.product.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}. diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md new file mode 100644 index 0000000000..35436eba62 --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics.md @@ -0,0 +1,102 @@ +--- +title: About Server Statistics +intro: 'You can use {% data variables.product.prodname_server_statistics %} to analyze your own aggregate data from {% data variables.product.prodname_ghe_server %}, and help us improve {% data variables.product.company_short %} products.' +versions: + feature: server-statistics +permissions: 'Enterprise owners can enable {% data variables.product.prodname_server_statistics %}.' +redirect_from: + - /early-access/github/analyze-how-your-team-works-with-server-statistics/about-server-statistics +topics: + - Enterprise +--- + +{% data reusables.server-statistics.release-phase %} + +## About the benefits of {% data variables.product.prodname_server_statistics %} + +{% data variables.product.prodname_server_statistics %} can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. + +Once enabled, {% data variables.product.prodname_server_statistics %} collects aggregate data on how much certain features are used on your instance over time. Unlike other [Admin Stats API](/rest/reference/enterprise-admin#admin-stats) endpoints, which only return data for the last day, {% data variables.product.prodname_server_statistics %} provides historical data of all {% data variables.product.prodname_server_statistics %} metrics collected since the day you enabled the feature. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 + +When you enable {% data variables.product.prodname_server_statistics %}, you're helping to build a better {% data variables.product.prodname_dotcom %}. The aggregated data you'll provide gives us insights into how {% data variables.product.prodname_dotcom %} adds value to our customers. This information allows {% data variables.product.company_short %} to make better and more informed product decisions, ultimately benefiting you. + +## About data security + +We respect your data. We will never transmit data from {% data variables.product.product_location %} unless you have first given us permission to do so. + +We collect no personal data. We also don't collect any {% data variables.product.company_short %} content, such as code, issues, comments, or pull request content. + +Only owners of the connected enterprise account or organization on {% data variables.product.prodname_ghe_cloud %} can access the data. + +Only certain aggregate metrics are collected on repositories, issues, pull requests, and other features. To see the list of aggregate metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." + +Any updates to the collected metrics will happen in future feature releases of {% data variables.product.prodname_ghe_server %} and will be described in the [{% data variables.product.prodname_ghe_server %} release notes](/admin/release-notes). In addition, we will update this article with all metric updates. + +For a better understanding of how we store and secure {% data variables.product.prodname_server_statistics %} data, see "[GitHub Security](https://github.com/security)." + +### About data retention and deletion + +{% data variables.product.company_short %} collects {% data variables.product.prodname_server_statistics %} data for as long as your {% data variables.product.prodname_ghe_server %} license is active and the {% data variables.product.prodname_server_statistics %} feature is enabled. + +If you would like to delete your data, you may do so by contacting GitHub Support, your {% data variables.product.prodname_dotcom %} account representative, or your Customer Success Manager. Generally, we delete data in the timeframe specified in our privacy statement. For more information, see [{% data variables.product.company_short %}'s privacy statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#data-retention-and-deletion-of-data) in the {% data variables.product.prodname_dotcom_the_website %} documentation. + +### About data portability + +As an organization owner or enterprise owner on {% data variables.product.prodname_ghe_cloud %}, you can access {% data variables.product.prodname_server_statistics %} data by exporting the data in a CSV or JSON file or through the {% data variables.product.prodname_server_statistics %} REST API. For more information, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)" or "[Exporting {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics)." + +## About disabling data collection + +You can disable the {% data variables.product.prodname_server_statistics %} feature at any time. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 + +## {% data variables.product.prodname_server_statistics %} data collected + +After you enable {% data variables.product.prodname_server_statistics %}, metrics are collected through a daily job that runs on {% data variables.product.product_location %}. The aggregate metrics are stored on your organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} and are not stored on {% data variables.product.product_location %}. + +The following aggregate metrics will be collected and transmitted on a daily basis and represent the total counts for the day: + - `active_hooks` + - `admin_users` + - `closed_issues` + - `closed_milestones` + - `collection_date` + - `disabled_orgs` + - `dormancy_threshold` + - `fork_repos` + - `ghes_version` + - `github_connect_features_enabled` + - `inactive_hooks` + - `mergeable_pulls` + - `merged_pulls` + - `open_issues` + - `open_milestones` + - `org_repos` + - `private_gists` + - `public_gists` + - `root_repos` + - `schema_version` + - `server_id` + - `suspended_users` + - `total_commit_comments` + - `total_dormant_users` + - `total_gist_comments` + - `total_gists` + - `total_hooks` + - `total_issues` + - `total_issue_comments` + - `total_milestones` + - `total_repos` + - `total_orgs` + - `total_pages` + - `total_pull_request_comments` + - `total_pulls` + - `total_pushes` + - `total_team_members` + - `total_teams` + - `total_users` + - `total_wikis` + - `unmergeable_pulls` + +## {% data variables.product.prodname_server_statistics %} payload example + +To see an example of the response payload for the {% data variables.product.prodname_server_statistics %} API, see "[Requesting {% data variables.product.prodname_server_statistics %} using the REST API](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api)." + +To see a list of the data collected, see "[{% data variables.product.prodname_server_statistics %} data collected](#server-statistics-data-collected)." diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md new file mode 100644 index 0000000000..74f6367abd --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md @@ -0,0 +1,43 @@ +--- +title: Exporting Server Statistics +shortTitle: Export Server Statistics +intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by downloading your {% data variables.product.prodname_server_statistics %} metrics in a CSV or JSON file.' +versions: + feature: server-statistics +redirect_from: + - /early-access/github/analyze-how-your-team-works-with-server-statistics/exploring-server-statistics +--- + +{% data reusables.server-statistics.release-phase %} + +You can download up to the last 365 days of {% data variables.product.prodname_server_statistics %} data in a CSV or JSON file. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. + +Before you can download this data, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 + +To preview the metrics available to download, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)." + +To download these metrics, you must be an enterprise owner or organization owner on {% data variables.product.prodname_ghe_cloud %}. + - If {% data variables.product.product_location %} is connected to an enterprise account on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your enterprise account](#downloading-metrics-from-your-enterprise-account)." + - If {% data variables.product.product_location %} is connected to an organization on {% data variables.product.prodname_ghe_cloud %}, see "[Downloading metrics from your organization](#downloading-metrics-from-your-organization)." + +To learn more about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." + +## Downloading metrics from your enterprise account + +1. {% data variables.product.prodname_ghe_cloud %}の右上で、自分のプロフィール写真をクリックし、続いて**Your enterprises（自分のEnterprise）**をクリックしてください。 ![Drop down menu with "Your enterprises" option](/assets/images/help/enterprises/enterprise-admin-account-settings.png) + +2. Next to your desired enterprise account, click **Settings**. ![Settings button next to Enterprise admin account](/assets/images/help/enterprises/enterprise-admin-account-settings-button.png) + +3. On the left, click **GitHub Connect**. ![GitHub Connect option under enterprise admin account](/assets/images//help/enterprises/enterprise-admin-github-connect.png) + +{% data reusables.server-statistics.csv-download %} + +## Downloading metrics from your organization + +1. In the top-right corner of {% data variables.product.prodname_ghe_cloud %}, click your profile photo, then click **Your organizations**. ![Drop down menu with "Your organizations" option](/assets/images/help/enterprises/github-enterprise-cloud-organizations.png) + +2. In the list of organizations, next to the organization that's connected to {% data variables.product.product_location %}, click **Settings**. ![Settings button next to {% data variables.product.prodname_ghe_cloud %} organization](/assets/images/help/enterprises/settings-for-ghec-org.png) + +3. On the left, click **GitHub Connect**. ![GitHub Connect option in an organization account settings left sidebar](/assets/images/help/enterprises/github-connect-option-for-ghec-org.png) + +{% data reusables.server-statistics.csv-download %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md new file mode 100644 index 0000000000..507a57ae5f --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/index.md @@ -0,0 +1,12 @@ +--- +title: Analyzing how your team works with Server Statistics +shortTitle: Server Statistics +intro: 'To analyze how your team works, understand the value you get from {% data variables.product.prodname_ghe_server %}, and help us improve our products, you can use {% data variables.product.prodname_server_statistics %} to review your usage data for {% data variables.product.prodname_ghe_server %} and share this aggregate data with {% data variables.product.company_short %}.' +versions: + feature: server-statistics +children: + - /about-server-statistics + - /exporting-server-statistics + - /requesting-server-statistics-using-the-rest-api +--- + diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md new file mode 100644 index 0000000000..5bb42fb99d --- /dev/null +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api.md @@ -0,0 +1,17 @@ +--- +title: Requesting Server Statistics using the REST API +shortTitle: Server Statistics and REST API +intro: 'You can use your own tools to analyze your {% data variables.product.prodname_ghe_server %} usage over time by requesting the {% data variables.product.prodname_server_statistics %} metrics collected using the REST API.' +versions: + feature: server-statistics +redirect_from: + - /early-access/github/analyze-how-your-team-works-with-server-statistics/requesting-server-statistics-using-the-rest-api +--- + +{% data reusables.server-statistics.release-phase %} + +You can request up to 365 days of metrics in a single {% data variables.product.prodname_server_statistics %} REST API request. This data, which includes aggregate metrics on repositories, issues, and pull requests, can help you anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}. For a list of the metrics collected, see "[{% data variables.product.prodname_server_statistics %} data collected](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." + +Before you can use the {% data variables.product.prodname_server_statistics %} REST API, you must enable {% data variables.product.prodname_server_statistics %}. 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_server_statistics %}の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」を参照してください。 + +For more information about using the REST API to request server statistics, see "[Get {% data variables.product.prodname_ghe_server %} statistics](/enterprise-cloud@latest/rest/enterprise-admin/admin-stats#get-github-enterprise-server-statistics)" in the {% data variables.product.prodname_ghe_cloud %} REST API documentation. diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md index cc0e93de2b..d406c16d3c 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/index.md @@ -12,6 +12,7 @@ topics: children: - /reviewing-audit-logs-for-your-enterprise - /exploring-user-activity + - /analyzing-how-your-team-works-with-server-statistics shortTitle: Monitor activity --- diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md index f5f9693881..6dbde9bee4 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md @@ -1050,7 +1050,7 @@ topics: | `restrict_notification_delivery.disable` | Email notification restrictions for an organization or enterprise were disabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." | {%- endif %} -{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %} +{%- if custom-repository-roles %} ### `role`カテゴリアクション | アクション | 説明 | diff --git a/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md index 62b8bf6b74..c84bad29ac 100644 --- a/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/packages/configuring-package-ecosystem-support-for-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Enterprise 向けのパッケージエコシステムサポートを設定する -intro: 'Docker、RubyGems、npm、Apache Maven、Gradle、NuGet など、Enterprise の個々のパッケージエコシステムをグローバルに有効または無効にすることで、Enterprise の {% data variables.product.prodname_registry %} を設定できます。 特定のパッケージエコシステムをサポートするための他の設定要件について学びます。' +intro: 'You can configure {% data variables.product.prodname_registry %} for your enterprise by globally enabling or disabling individual package ecosystems on your enterprise, including {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, and npm. 特定のパッケージエコシステムをサポートするための他の設定要件について学びます。' redirect_from: - /enterprise/admin/packages/configuring-packages-support-for-your-enterprise - /admin/packages/configuring-packages-support-for-your-enterprise @@ -23,7 +23,10 @@ shortTitle: Configure package ecosystems {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} 1. [Ecosystem Toggles] の下で、パッケージの種類ごとに [**Enabled**]、[**Read-Only**]、または [**Disabled**] を選択します。 -{% ifversion ghes > 3.1 %} + {%- ifversion ghes > 3.4 %}{% note -%} +**Note**: Subdomain isolation must be enabled to toggle the + {% data variables.product.prodname_container_registry %} オプション. + {%- endnote %}{%- endif %}{%- ifversion ghes > 3.1 %} ![エコシステムの切り替え](/assets/images/enterprise/site-admin-settings/ecosystem-toggles.png){% else %} ![Ecosystem toggles](/assets/images/enterprise/3.1/site-admin-settings/ecosystem-toggles.png){% endif %} {% data reusables.enterprise_management_console.save-settings %} diff --git a/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md index f1d277e45e..82600b15c7 100644 --- a/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md @@ -37,10 +37,10 @@ To enable {% data variables.product.prodname_registry %} and configure third-par ## Step 3: Specify the package ecosystems to support on your instance -Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.product.product_location %}. Available options are Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." +Choose which package ecosystems you'd like to enable, disable, or set to read-only on {% data variables.product.product_location %}. Available options are {% ifversion ghes > 3.4 %}{% data variables.product.prodname_container_registry %}, {% endif %}Docker, RubyGems, npm, Apache Maven, Gradle, or NuGet. For more information, see "[Configuring package ecosystem support for your enterprise](/enterprise/admin/packages/configuring-package-ecosystem-support-for-your-enterprise)." ## Step 4: Ensure you have a TLS certificate for your package host URL, if needed -If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `npm.HOSTNAME`. Make sure each package host URL includes `https://`. +If subdomain isolation is enabled for {% data variables.product.product_location %}, you will need to create and upload a TLS certificate that allows the package host URL for each ecosystem you want to use, such as `{% data reusables.package_registry.container-registry-hostname %}`. Make sure each package host URL includes `https://`. You can create the certificate manually, or you can use _Let's Encrypt_. If you already use _Let's Encrypt_, you must request a new TLS certificate after enabling {% data variables.product.prodname_registry %}. For more information about package host URLs, see "[Enabling subdomain isolation](/enterprise/admin/configuration/enabling-subdomain-isolation)." For more information about uploading TLS certificates to {% data variables.product.product_name %}, see "[Configuring TLS](/enterprise/admin/configuration/configuring-tls)." diff --git a/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md index 5771f81c62..457f7f926d 100644 --- a/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md +++ b/translations/ja-JP/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md @@ -29,6 +29,14 @@ This quickstart shows you how to set up MinIO using Docker for use with {% data For more information about your options, see the official [MinIO docs](https://docs.min.io/). +{% warning %} + +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_registry %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +Other modes of MinIO remain available with standard support. + +{% endwarning %} + ## 2. Install, run, and sign in to MinIO 1. Set up your preferred environment variables for MinIO. diff --git a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md index 59e7b1fda2..ee0c167374 100644 --- a/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md @@ -63,13 +63,13 @@ Enterprise 内のすべての Organization に対して {% data variables.produc {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.policies-tab %} {% data reusables.enterprise-accounts.actions-tab %} -1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list. +1. "Policies（ポリシー）"の下で、{% data reusables.actions.policy-label-for-select-actions-workflows %}を選択し、必要なアクション{% if actions-workflow-policy %}と再利用可能なワークフロー{% endif %}をリストに追加してください。 {% if actions-workflow-policy %} - ![Add actions and reusable workflows to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) + ![許可リストへのアクションと再利用可能なワークフローの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list-with-workflows.png) {%- elsif ghes or ghae-issue-5094 %} - ![Add actions to the allow list](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) + ![許可リストへのアクションの追加](/assets/images/help/organizations/enterprise-actions-policy-allow-list.png) {%- elsif ghae %} - ![Add actions to the allow list](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) + ![許可リストへのアクションの追加](/assets/images/enterprise/github-ae/enterprise-actions-policy-allow-list.png) {%- endif %} ## Enforcing a policy for artifact and log retention in your enterprise @@ -132,3 +132,22 @@ You can set the default permissions for the `GITHUB_TOKEN` in the settings for y 1. **Save（保存）**をクリックして、設定を適用してください。 {% endif %} + +{% if actions-cache-policy-apis %} + +## Enforcing a policy for cache storage in your enterprise + +{% data reusables.actions.cache-default-size %} {% data reusables.actions.cache-eviction-process %} + +However, you can set an enterprise policy to customize both the default total cache size for each repository, as well as the maximum total cache size allowed for a repository. For example, you might want the default total cache size for each repository to be 5 GB, but also allow repository administrators to configure a total cache size up to 15 GB if necessary. + +People with admin access to a repository can set a total cache size for their repository up to the maximum cache size allowed by the enterprise policy setting. + +The policy settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API: + +* To view the current enterprise policy settings, see "[Get GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)." +* To change the enterprise policy settings, see "[Set GitHub Actions cache usage policy for an enterprise](/rest/actions/cache#get-github-actions-cache-usage-policy-for-an-enterprise)." + +{% data reusables.actions.cache-no-org-policy %} + +{% endif %} diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md index 8aed8da019..a5c0509a20 100644 --- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md +++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md @@ -22,23 +22,33 @@ shortTitle: Manage your organization roles You can choose to join an organization owned by your enterprise as a member or as an organization owner, change your role within the organization, or leave the organization. +{% ifversion ghec %} {% warning %} **Warning**: If an organization uses SCIM to provision users, joining the organization this way could have unintended consequences. 詳しい情報については、「[OrganizationのSCIMについて](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim-for-organizations)」を参照してください。 {% endwarning %} +{% endif %} + +For information about managing other people's roles in an organization, see "[Managing membership in your organization](/organizations/managing-membership-in-your-organization)" and "[Managing people's access to your organization with roles](/organizations/managing-peoples-access-to-your-organization-with-roles)." ## Managing your role with the enterprise settings You can join an organization owned by your enterprise and manage your role within the organization, directly from the settings for your enterprise account. +{% ifversion ghec %} + If an organization enforces SAML single sign-on (SSO), you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP). Then, you can manage your role in your enterprise settings. For more information, see "[Joining an organization that enforces SAML SSO](#joining-an-organization-that-enforces-saml-sso)." +{% endif %} + {% data reusables.enterprise-accounts.access-enterprise %} 1. On the **Organizations** tab, to the right of the organization you want to manage your role in, select the {% octicon "gear" aria-label="The gear icon" %} dropdown menu and click the action you want to take. ![Screenshot of the dropdown menu for the gear icon for an organization](/assets/images/help/business-accounts/change-role-in-org.png) +{% ifversion ghec %} + ## Joining an organization that enforces SAML SSO If an organization enforces SAML SSO, you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP). @@ -52,3 +62,5 @@ If an organization enforces SAML SSO, you cannot use the enterprise settings to `https://github.com/orgs/ORGANIZATION/sso` After you've joined the organization, you can use the enterprise settings to manage your role in the organization, such as becoming an organization owner. For more information, see "[Managing your role with the enterprise settings](#managing-your-role-with-the-enterprise-settings)." + +{% endif %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md index 4539c7f137..b0c87d6303 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md @@ -19,8 +19,9 @@ shortTitle: Authentication to GitHub To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be. You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication. - -- {% ifversion ghae %}Your identity provider (IdP){% else %}Username and password with two-factor authentication{% endif %} +{%- ifversion not fpt %} +- Your identity provider (IdP){% endif %}{% ifversion not ghae %} +- Username and password with two-factor authentication{% endif %} - Personal access token - SSH key @@ -29,14 +30,21 @@ You can access your resources in {% data variables.product.product_name %} in a You can authenticate to {% data variables.product.product_name %} in your browser {% ifversion ghae %}using your IdP. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)."{% else %}in different ways. {% ifversion fpt or ghec %} -- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your browser on {% data variables.product.prodname_dotcom_the_website %}. +- If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate to {% data variables.product.product_name %} in your browser using your IdP. For more information, see "[Authenticating as a managed user](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users#authenticating-as-a-managed-user){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} + + If you're not a member of an {% data variables.product.prodname_emu_enterprise %}, you will authenticate using your {% data variables.product.prodname_dotcom_the_website %} username and password. You may also be required to enable two-factor authentication. {% endif %} - **Username and password only** - - You'll create a password when you create your personal account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)." + - You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %} + - If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer. + + After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %} - **Two-factor authentication (2FA)** (recommended) - - If you enable 2FA, we'll also prompt you to provide a code that's generated by an application on your mobile device or sent as a text message (SMS) after you successfully enter your username and password. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." - - In addition to authentication with a mobile application or a text message, you can optionally add a secondary method of authentication with a security key using WebAuthn. For more information, see "[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)." + - If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)." + - In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% endif %}{% ifversion ghes %} +- **Identity provider (IdP) authentication** + - Your site administrator may configure {% data variables.product.product_location %} to use authentication with an IdP instead of a username and password. For more information, see "[External authentication methods](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#external-authentication)." {% endif %} ## Authenticating with {% data variables.product.prodname_desktop %} @@ -74,9 +82,10 @@ If you authenticate with {% data variables.product.prodname_cli %}, the CLI will If you authenticate without {% data variables.product.prodname_cli %}, you will need to generate an SSH public/private keypair on your local machine and add the public key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)." Every time you use Git to authenticate with {% data variables.product.product_name %}, you'll be prompted to enter your SSH key passphrase, unless you've [stored the key](/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent). +{% ifversion fpt or ghec %} ### Authorizing for SAML single sign-on -{% ifversion fpt or ghec %}To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} +To use a personal access token or SSH key to access resources owned by an organization that uses SAML single sign-on, you must also authorize the personal token or SSH key. For more information, see "[Authorizing a personal access token for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)" or "[Authorizing an SSH key for use with SAML single sign-on](/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}{% endif %} {% ifversion fpt or ghes > 3.1 or ghae or ghec %} diff --git a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md index 15cb827618..0f1543d813 100644 --- a/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md +++ b/translations/ja-JP/content/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation.md @@ -54,6 +54,8 @@ Once an authorization is revoked, any tokens associated with the authorization w The owner of an {% data variables.product.prodname_oauth_app %} can revoke an account's authorization of their app, this will also revoke any tokens associated with the authorization. For more information about revoking authorizations of your OAuth app, see "[Delete an app authorization](/rest/reference/apps#delete-an-app-authorization)." +{% data variables.product.prodname_oauth_app %} owners can also revoke individual tokens associated with an authorization. For more information about revoking individual tokens for your OAuth app, see "[Delete an app token](/rest/apps/oauth-applications#delete-an-app-token)". + ## Token revoked due to excess of tokens for an {% data variables.product.prodname_oauth_app %} with the same scope {% data reusables.apps.oauth-token-limit %} 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 006b3d6792..7e5a2848ec 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 @@ -48,8 +48,11 @@ Repository administrators can enforce required commit signing on a branch to blo {% data reusables.identity-and-permissions.verification-status-check %} -{% ifversion fpt or ghec %} -{% data variables.product.product_name %} will automatically use GPG to sign commits you make using the {% data variables.product.product_name %} web interface. Commits signed by {% data variables.product.product_name %} will have a verified status on {% data variables.product.product_name %}. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. You can optionally choose to have {% data variables.product.product_name %} sign commits you make in {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)." +{% ifversion fpt or ghec or ghes > 3.4 %} +{% ifversion ghes %}If a site administrator has enabled web commit signing, {% data variables.product.product_name %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.product_name %} will have a verified status. You can verify the signature locally using the public key available at `https://HOSTNAME/web-flow.gpg`. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." +{% else %}{% data variables.product.prodname_dotcom %} will automatically use GPG to sign commits you make using the web interface. Commits signed by {% data variables.product.prodname_dotcom %} will have a verified status. You can verify the signature locally using the public key available at https://github.com/web-flow.gpg. The full fingerprint of the key is `5DE3 E050 9C47 EA3C F04A 42D3 4AEE 18F8 3AFD EB23`. + +You can optionally choose to have {% data variables.product.prodname_dotcom %} sign commits you make in {% data variables.product.prodname_codespaces %}. For more information about enabling GPG verification for your codespaces, see "[Managing GPG verification for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-gpg-verification-for-codespaces)."{% endif %} {% endif %} ## GPG commit signature verification diff --git a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md index fea587e5f4..ad96823d4e 100644 --- a/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md +++ b/translations/ja-JP/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md @@ -19,7 +19,7 @@ shortTitle: About 2FA {% data reusables.two_fa.after-2fa-add-security-key %} {% ifversion fpt or ghec %} -In addition to security keys, you can also use {% data variables.product.prodname_mobile %} for 2FA after configuring a TOTP mobile app or text messages. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to signed in to {% data variables.product.prodname_mobile %} as your second factor. +In addition to security keys, you can also use {% data variables.product.prodname_mobile %} for 2FA after configuring a TOTP mobile app or text messages. {% data variables.product.prodname_mobile %} uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to {% data variables.product.prodname_mobile %} as your second factor. {% endif %} 2 要素認証の認証情報にアクセスできなくなった場合に備えて、追加のリカバリ方法を設定することもできます。 2FA のセットアップに関する詳しい情報については[2 要素認証の設定](/articles/configuring-two-factor-authentication)および[2 要素認証のリカバリ方法の設定](/articles/configuring-two-factor-authentication-recovery-methods)を参照してください。 diff --git a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md index 629153f9dd..93b03e1e59 100644 --- a/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md +++ b/translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md @@ -1,6 +1,6 @@ --- title: Azure サブスクリプションを Enterprise に接続する -intro: 'Microsoft Enterprise Agreement を使用して、Enterprise に含まれている金額を超える {% data variables.product.prodname_actions %} および {% data variables.product.prodname_registry %} の使用を有効化して支払うことができます。' +intro: 'You can use your Microsoft Enterprise Agreement to enable and pay for {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} usage.' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise @@ -14,7 +14,17 @@ shortTitle: Azureサブスクリプションの接続 {% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} 詳しい情報については、「[{% data variables.product.prodname_actions %} の支払いについて](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」および「[{% data variables.product.prodname_registry %} の支払いについて](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。 -Azure サブスクリプションに接続した後、利用上限を管理することもできます。 アカウントの利用上限の管理と変更については、「[{% data variables.product.prodname_registry %} の利用上限の管理](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)」および「[{% data variables.product.prodname_actions %} の利用上限の管理](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)」を参照してください。 +{% note %} + +**Note:** If your enterprise account is on a Microsoft Enterprise Agreement, connecting an Azure subscription is the only way to use {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} beyond the included amounts, or to use {% data variables.product.prodname_codespaces %} at all. + +{% endnote %} + +After you connect an Azure subscription, you can also manage your spending limits. + +- "[Managing your spending limit for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/managing-your-spending-limit-for-github-packages)" +- "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)" +- "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)" ## Azure サブスクリプションを Enterprise アカウントに接続する diff --git a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md index 2fae8de7d2..96020cb874 100644 --- a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -18,7 +18,7 @@ shortTitle: Sync license usage To ensure that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between the environments automatically, using {% data variables.product.prodname_github_connect %}. For more information about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/about-github-connect){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %} -If you don't want to enable {% data variables.product.prodname_github_connect %}, you can manually sync license usage by uploading a file from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}. +If you don't want to enable {% data variables.product.prodname_github_connect %}, you can manually sync license usage by uploading a file from {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-licensing.view-consumed-licenses %} @@ -26,9 +26,23 @@ If you don't want to enable {% data variables.product.prodname_github_connect %} ## Automatically syncing license usage -You can use {% data variables.product.prodname_github_connect %} to automatically synchronize user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %} +You can use {% data variables.product.prodname_github_connect %} to automatically synchronize user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} weekly. For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %} -## Manually syncing license usage +{% ifversion ghec or ghes > 3.4 %} +After you enable {% data variables.product.prodname_github_connect %}, license data will be automatically synchronized weekly. You can also manually synchronize your license data at any time, by triggering a license sync job. + +### Triggering a license sync job + +1. Sign in to your {% data variables.product.prodname_ghe_server %} instance. +{% data reusables.enterprise-accounts.access-enterprise %} +{% data reusables.enterprise-accounts.settings-tab %} +{% data reusables.enterprise-accounts.license-tab %} +1. Under "License sync", click {% octicon "sync" aria-label="The Sync icon" %} **Sync now**. + ![Screenshot of "Sync now" button in license sync section](/assets/images/help/enterprises/license-sync-now-ghes.png) + +{% endif %} + +## Manually uploading GitHub Enterprise Server license usage You can download a JSON file from {% data variables.product.prodname_ghe_server %} and upload the file to {% data variables.product.prodname_ghe_cloud %} to manually sync user license usage between the two deployments. @@ -39,8 +53,6 @@ You can download a JSON file from {% data variables.product.prodname_ghe_server ![Export license usage link](/assets/images/enterprise/business-accounts/export-license-usage-link.png) {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -8. In the left sidebar, click **Enterprise licensing**. - !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) {% data reusables.enterprise-accounts.license-tab %} 10. Under "Enterprise Server Instances", click **Add server usage**. ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) diff --git a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index ccef24154c..637c78f8c7 100644 --- a/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/translations/ja-JP/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -85,12 +85,19 @@ Any valid SARIF 2.1.0 output file can be uploaded, however, {% data variables.pr | Name | Description | |----|----| -| `tool.driver.name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. | -| `tool.driver.version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. | -| `tool.driver.semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. | -| `tool.driver.rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | +| `tool.driver` | **Required.** A `toolComponent` object that describes the analysis tool. For more information, see the [`toolComponent` object](#toolcomponent-object). | +| `tool.extensions[]` | **Optional.** An array of `toolComponent` objects that represent any plugins or extensions used by the tool during analysis. For more information, see the [`toolComponent` object](#toolcomponent-object). | | `results[]` | **Required.** The results of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the results on {% data variables.product.prodname_dotcom %}. For more information, see the [`result` object](#result-object). +### `toolComponent` object + +| Name | Description | +|----|----| +| `name` | **Required.** The name of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} displays the name on {% data variables.product.prodname_dotcom %} to allow you to filter results by tool. | +| `version` | **Optional.** The version of the analysis tool. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. | +| `semanticVersion` | **Optional.** The version of the analysis tool, specified by the Semantic Versioning 2.0 format. {% data variables.product.prodname_code_scanning_capc %} uses the version number to track when results may have changed due to a tool version change rather than a change in the code being analyzed. If the SARIF file includes the `semanticVersion` field, `version` is not used by {% data variables.product.prodname_code_scanning %}. For more information, see "[Semantic Versioning 2.0.0](https://semver.org/)" in the Semantic Versioning documentation. | +| `rules[]` | **Required.** An array of `reportingDescriptor` objects that represent rules. The analysis tool uses rules to find problems in the code being analyzed. For more information, see the [`reportingDescriptor` object](#reportingdescriptor-object). | + ### `reportingDescriptor` object | Name | Description | @@ -176,7 +183,7 @@ Use the category to distinguish between multiple analyses for the same tool or c - The run with an `id` of "my-analysis/tool1/" belongs to the category "my-analysis/tool1" but is not distinguished from other runs in that category. - The run whose `id` is "my-analysis for tool1 " has a unique identifier but cannot be inferred to belong to any category. -For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation. +For more information about the `runAutomationDetails` object and the `id` field, see [runAutomationDetails object](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012479) in the OASIS documentation. Note that the rest of the supported fields are ignored. @@ -302,7 +309,7 @@ This SARIF output file has example values to show all supported SARIF properties ] } }, - "automationDetails": { + "automationDetails": { "id": "my-category/" }, "results": [ diff --git a/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md index 4ae940a282..1da31684a2 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md +++ b/translations/ja-JP/content/code-security/secret-scanning/secret-scanning-patterns.md @@ -42,6 +42,8 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %} +If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)." + {% ifversion ghes > 3.1 or ghae or ghec %} {% note %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md index 8cb20e58a3..516be09209 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md @@ -1,7 +1,7 @@ --- -title: Configuring dependency review -intro: You can use dependency review to catch vulnerabilities before they are added to your project. -shortTitle: Configure dependency review +title: 依存関係レビューの設定 +intro: 依存関係レビューを使って、プロジェクトに追加される前に脆弱性を捕捉できます。 +shortTitle: 依存関係レビューの設定 versions: fpt: '*' ghes: '>= 3.2' @@ -22,28 +22,28 @@ topics: {% data reusables.dependency-review.feature-overview %} -For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" and "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." +詳しい情報については「[依存関係レビューについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)」及び「[Pull Request中での依存関係の変化のレビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)」を参照してください。 -## About configuring dependency review +## 依存関係レビューの設定について {% ifversion fpt %} -Dependency review is available in all public repositories in all products and cannot be disabled. Dependency review is available in private repositories owned by organizations that use GitHub Enterprise Cloud and have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security). 詳しい情報については[{% data variables.product.prodname_ghe_cloud %}のドキュメンテーション](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review)を参照してください。 +依存関係レビューは、すべての製品のすべてのパブリックリポジトリで利用可能であり、無効化できません。 依存関係レビューは、GitHub Enterprise Cloudを利用し、[{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)のライセンスを持っているOrganizationが所有するプライベートリポジトリで利用できます。 詳しい情報については[{% data variables.product.prodname_ghe_cloud %}のドキュメンテーション](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review)を参照してください。 {% elsif ghec %} -Dependency review is included in {% data variables.product.product_name %} for public repositories. To use dependency review in private repositories owned by organizations, you must have a license for [{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security) and have the dependency graph enabled. +依存関係レビューは、パブリックリポジトリに対して{% data variables.product.product_name %}に含まれています。 依存関係レビューをOrganizationが所有するプライベートリポジトリで使うには、[{% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)を持っていることと、依存関係グラフが有効化されていることが必要です。 {% data reusables.dependabot.enabling-disabling-dependency-graph-private-repo %} -1. If "{% data variables.product.prodname_GH_advanced_security %}" is not enabled, click **Enable** next to the feature. ![Screenshot of GitHub Advanced Security feature with "Enable" button emphasized](/assets/images/help/security/enable-ghas-private-repo.png) +1. "{% data variables.product.prodname_GH_advanced_security %}"が有効化されていない場合、その隣の**Enable（有効化）**をクリックしてください。 !["Enable" ボタンが強調されたGitHub Advanced Security機能のスクリーンショット](/assets/images/help/security/enable-ghas-private-repo.png) {% elsif ghes or ghae %} -Dependency review is available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)." +依存関係レビューは、依存関係グラフが{% data variables.product.product_location %}で有効化されており、Organizationもしくはリポジトリで{% data variables.product.prodname_advanced_security %}が有効化されている場合に利用できます。 詳しい情報については「[Enterpriseでの{% data variables.product.prodname_GH_advanced_security %}の有効化](/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise)」を参照してください。 -### Checking if the dependency graph is enabled +### 依存関係グラフが有効化されているかの確認 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %} -1. Under "Configure security and analysis features", check if the dependency graph is enabled. -1. If dependency graph is enabled, click **Enable** next to "{% data variables.product.prodname_GH_advanced_security %}" to enable {% data variables.product.prodname_advanced_security %}, including dependency review. The enable button is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% ifversion ghes < 3.3 %} ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %} ![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %} +1. "Configure security and analysis features（セキュリティと分析機能の設定）"の下で、依存関係グラフが有効化されているかを確認してください。 +1. 依存関係グラフが有効化されているなら、"{% data variables.product.prodname_GH_advanced_security %}"の隣の**Enable（有効化）**をクリックして、依存関係レビューを含む{% data variables.product.prodname_advanced_security %}を有効化してください。 Enterpriseが利用できる{% data variables.product.prodname_advanced_security %}のライセンスを持っていない場合、有効化のボタンは無効になっています。{% ifversion ghes < 3.3 %}![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.2/repository/code-security-and-analysis-enable-ghas-3.2.png){% endif %}{% ifversion ghes > 3.2 %}![Screenshot of "Code security and analysis" features"](/assets/images/enterprise/3.4/repository/code-security-and-analysis-enable-ghas-3.4.png){% endif %} {% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md index be5882befd..c6643f0264 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md @@ -1,6 +1,6 @@ --- -title: Configuring the dependency graph -intro: You can allow users to identify their projects' dependencies by enabling the dependency graph. +title: 依存関係グラフの設定 +intro: 依存関係グラフを有効にすることによって、ユーザが自分のプロジェクトの依存関係を特定できるようになります。 redirect_from: - /code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph versions: @@ -13,7 +13,7 @@ topics: - Dependency graph - Dependencies - Repositories -shortTitle: Configure dependency graph +shortTitle: 依存関係グラフの設定 --- ## 依存関係グラフについて @@ -22,10 +22,10 @@ shortTitle: Configure dependency graph 詳しい情報については、「[依存関係グラフについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)」を参照してください。 -{% ifversion fpt or ghec %} ## About configuring the dependency graph {% endif %} -{% ifversion fpt or ghec %}依存関係グラフを生成するには、{% data variables.product.product_name %} がリポジトリの依存関係のマニフェストおよびロックファイルに読み取りアクセスできる必要があります。 依存関係グラフは、パブリックリポジトリに対しては常に自動的に生成され、プライベートリポジトリに対しては有効化を選択することができます。 For more information on viewing the dependency graph, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %} +{% ifversion fpt or ghec %} ## 依存関係グラフの設定について {% endif %} +{% ifversion fpt or ghec %}依存関係グラフを生成するには、{% data variables.product.product_name %} がリポジトリの依存関係のマニフェストおよびロックファイルに読み取りアクセスできる必要があります。 依存関係グラフは、パブリックリポジトリに対しては常に自動的に生成され、プライベートリポジトリに対しては有効化を選択することができます。 依存関係グラフの表示に関する詳しい情報については「[リポジトリの依存関係の調査](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)」を参照してください。{% endif %} -{% ifversion ghes or ghae %} ## Enabling the dependency graph +{% ifversion ghes or ghae %} ## 依存関係グラフの有効化 {% data reusables.dependabot.ghes-ghae-enabling-dependency-graph %}{% endif %}{% ifversion fpt or ghec %} ### プライベートリポジトリの依存関係グラフを有効化および無効化する @@ -37,6 +37,6 @@ shortTitle: Configure dependency graph ## 参考リンク -{% ifversion ghec %}- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +{% ifversion ghec %}- 「[Organizationのインサイトの表示](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)」{% endif %} +- 「[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}の表示](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」 - 「[脆弱性のある依存関係の検出のトラブルシューティング](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)」 diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index a2947459f6..bd87958a33 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -34,13 +34,13 @@ shortTitle: 依存関係の調査 4. オプションとして、[Dependency graph] で [**Dependents**] をクリックします。 ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %} {% ifversion ghes %} -Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)." +Enterpriseのオーナーは、Enterpriseのレベルで依存関係グラフを設定できます。 詳しい情報については「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」を参照してください。 {% endif %} ### 依存関係ビュー {% ifversion fpt or ghec %} -依存関係はエコシステム別にグループ化されます。 依存関係を拡張すると、その依存関係を表示できます。 プライベートリポジトリ、プライベートパッケージ、認識できないファイルの依存関係は、プレーンテキストで表示されます。 If the package manager for the dependency is in a public repository, {% data variables.product.product_name %} will display a link to that repository. +依存関係はエコシステム別にグループ化されます。 依存関係を拡張すると、その依存関係を表示できます。 プライベートリポジトリ、プライベートパッケージ、認識できないファイルの依存関係は、プレーンテキストで表示されます。 依存関係のパッケージマネージャがパブリックリポジトリ中にある場合、{% data variables.product.product_name %}はそのリポジトリへのリンクを表示します。 リポジトリで脆弱性が検出された場合は、{% data variables.product.prodname_dependabot_alerts %}にアクセスできるユーザに、ビューの上部で表示されます。 @@ -74,10 +74,10 @@ Enterprise owners can configure the dependency graph at an enterprise level. For ## "Used by"パッケージの変更 -You may notice some repositories have a "Used by" section in the sidebar of the **Code** tab. Your repository will have a "Used by" section if: - * The dependency graph is enabled for the repository (see the above section for more details). - * Your repository contains a package that is published on a [supported package ecosystem](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems). - * Within the ecosystem, your package has a link to a _public_ repository where the source is stored. +リポジトリの中には、**Code**タブのサイドバーに"Used by"セクションを持つものがあることに気づくかもしれません。 以下の場合、リポジトリは"Used by"を持ちます: + * そのリポジトリで依存関係グラフが有効になっている（詳細については上のセクションを参照）。 + * リポジトリに、[サポートされているパッケージエコシステム](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)で公開されているパッケージが含まれている。 + * そのエコシステム内で、ソースが保存されている_パブリック_リポジトリへのリンクがパッケージ内にある。 "Used by"セクションは、見つかったパッケージに対する公開参照数を示し、依存物のプロジェクトのオーナーのアバターを表示します。 @@ -90,7 +90,7 @@ You may notice some repositories have a "Used by" section in the sidebar of the {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-code-security-and-analysis %} -4. Under "Code security and analysis", click the drop-down menu in the "Used by counter" section and choose a package. !["Used by"パッケージの選択](/assets/images/help/repository/choose-used-by-package.png) +4. "Code security and analysis（コードのセキュリティと分析）"の下で、"Used by counter"セクション内のドロップダウンメニューをクリックしてください。 !["Used by"パッケージの選択](/assets/images/help/repository/choose-used-by-package.png) {% endif %} @@ -107,6 +107,6 @@ You may notice some repositories have a "Used by" section in the sidebar of the - [依存関係グラフについて](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph) - 「[脆弱性のある依存関係に対する{% data variables.product.prodname_dependabot_alerts %}の表示](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)」{% ifversion ghec %} -- "[Viewing insights for your organization](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %}{% ifversion fpt or ghec %} +- 「[Organizationのインサイトの表示](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)」{% endif %}{% ifversion fpt or ghec %} - [{% data variables.product.prodname_dotcom %}によるデータの利用と保護の方法の理解](/get-started/privacy-on-github) {% endif %} diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md index acb6cbc0e5..17e72a032a 100644 --- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md +++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/index.md @@ -9,7 +9,7 @@ topics: - Dependency graph - Dependencies - Repositories -shortTitle: Understand your supply chain +shortTitle: サプライチェーンの理解 children: - /about-supply-chain-security - /about-the-dependency-graph diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md index 9c5cc3e98d..7315eca255 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md @@ -150,7 +150,7 @@ You can label a port to make the port more easily identifiable in a list. ## Adding a port to the codespace configuration -You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)」を参照してください。 +You can add a forwarded port to the {% data variables.product.prodname_codespaces %} configuration for the repository, so the port will automatically be forwarded for all codespaces created from the repository. After you update the configuration, any previously created codespaces must be rebuilt for the change to apply. 詳しい情報については、「[プロジェクトの {% data variables.product.prodname_codespaces %} を設定する](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-configuration-changes-to-a-codespace)」を参照してください。 `forwardPorts` プロパティで `.devcontainer.json` ファイルで転送ポートを手動で設定するか、codespace の [Ports] パネルを使用できます。 diff --git a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md index b78c5aa9de..d660632178 100644 --- a/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md +++ b/translations/ja-JP/content/codespaces/developing-in-codespaces/using-source-control-in-your-codespace.md @@ -47,7 +47,7 @@ shortTitle: ソースコントロール 1. サイドバーの上部にある省略記号(**...**) をクリックします。 ![[View] および [More Actions] の省略記号ボタン](/assets/images/help/codespaces/source-control-ellipsis-button.png) 1. ドロップダウンメニューで、[**Pull**] をクリックします。 -If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)." +If the dev container configuration has been changed since you created the codespace, you can apply the changes by rebuilding the container for the codespace. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project#applying-configuration-changes-to-a-codespace)." ## 新しい変更を自動的にフェッチするように codespace を設定する diff --git a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md index 85c36842d6..e5850f61ac 100644 --- a/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md +++ b/translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md @@ -87,7 +87,7 @@ To create codespaces with custom permissions defined, you must use one of the fo } ``` - To set all permissions for a given repository, use `read-all` or `write-all` in the `permissions` object + To set all permissions for a given repository, use `"permissions": "read-all"` or `"permissions": "write-all"` in the repository object. ```json { @@ -95,9 +95,7 @@ To create codespaces with custom permissions defined, you must use one of the fo "codespaces": { "repositories": { "my_org/my_repo": { - "permissions": { - "write-all" - } + "permissions": "write-all" } } } diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md index ac94454028..ca4d3ac16c 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -58,7 +58,20 @@ This displays the workflow run history for prebuilds for the associated branch. 1. Make the required changes to the prebuild configuration, then click **Update**. -### Delete a prebuild configuration +### Disabling a prebuild configuration + +To pause the update of prebuild templates for a configuration, you can disable workflow runs for the configuration. Disabling the workflow runs for a prebuild configuration does not delete any previously created prebuild templates for that configuration and, as a result, codespaces will continue to be generated from an existing prebuild template. + +Disabling the workflow runs for a prebuild configuration is useful if you need to investigate template creation failures. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to disable. +1. In the dropdown menu, click **Disable runs**. + + ![The 'Disable runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-disable.png) + +1. To confirm that you want to disable this configuration, click **OK**. + +### Deleting a prebuild configuration Deleting a prebuild configuration also deletes all previously created prebuild templates for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace. diff --git a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md index 15b6220a80..b1344f9e3f 100644 --- a/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md +++ b/translations/ja-JP/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md @@ -25,7 +25,7 @@ For more information, see "[Introduction to dev containers](/codespaces/setting- 1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "[Creating a codespace ](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." 1. In the codespace, check out a test branch. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)." 1. Make the required changes to the dev container configuration. -1. Apply the changes by rebuilding the container. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-changes-to-your-configuration)." +1. Apply the changes by rebuilding the container. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#applying-configuration-changes-to-a-codespace)." 1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild template for that branch. {% note %} diff --git a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md index 908e37f97f..8048f736ac 100644 --- a/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md +++ b/translations/ja-JP/content/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers.md @@ -138,7 +138,7 @@ You can add a predefined dev container configuration either while working in a c ![OK button](/assets/images/help/codespaces/prebuilt-container-ok-button.png) -1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." +1. If you are working in a codespace, apply your changes, by clicking **Rebuild now** in the message at the bottom right of the window. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." !["Codespaces: Rebuild Container" in the {% data variables.product.prodname_vscode_command_palette %}](/assets/images/help/codespaces/rebuild-prompt.png) @@ -163,7 +163,7 @@ You can add some of the most common features by selecting them when configuring ![The select additional features menu during container configuration](/assets/images/help/codespaces/select-additional-features.png) -1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-changes-to-your-configuration)." +1. To apply the changes, in the bottom right corner of the screen, click **Rebuild now**. For more information about rebuilding your container, see "[Applying changes to your configuration](#applying-configuration-changes-to-a-codespace)." !["Codespaces: Rebuild Container" in the command palette](/assets/images/help/codespaces/rebuild-prompt.png) @@ -211,7 +211,7 @@ The `devcontainer.json` file is written using the JSONC format. This allows you * Editor settings defined in the `.vscode/settings.json` file in your repository are applied as _Workspace_-scoped settings in the codespace. * Editor settings defined in the `settings` key in the `devcontainer.json` file are applied as _Remote [Codespaces]_-scoped settings in the codespace. -## Applying changes to your configuration +## Applying configuration changes to a codespace {% data reusables.codespaces.apply-devcontainer-changes %} diff --git a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md index d7efd01358..b70b7b9ac2 100644 --- a/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md +++ b/translations/ja-JP/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -57,6 +57,10 @@ Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} P * Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again. * If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch. +## Troubleshooting failed workflow runs for prebuilds + +If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)." + ## 参考リンク - "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)" diff --git a/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md index 256e48b0d5..10247b0031 100644 --- a/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md +++ b/translations/ja-JP/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md @@ -47,12 +47,14 @@ shortTitle: コメントの管理 会話に関係がない、コミュニティの行動規範{% ifversion fpt or ghec %}または GitHub の[コミュニティ ガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}に違反している場合は、コメントを編集して内容を削除するのが妥当です。 -コメントを編集する際には、削除した内容があった元の場所がわかるように記録し、オプションで削除の理由を示します。 +Sometimes it may make sense to clearly indicate edits and their justification. -リポジトリの読み取りアクセスがあれば、誰でもコミットの編集履歴を見ることができます。 コメントの上部にある [**edited**] ドロップダウンには編集履歴があり、編集したユーザとタイムスタンプが表示されます。 +That said, anyone with read access to a repository can view a comment's edit history. コメントの上部にある [**edited**] ドロップダウンには編集履歴があり、編集したユーザとタイムスタンプが表示されます。 ![内容を削除編集したというメモを追加したコメント](/assets/images/help/repository/content-redacted-comment.png) +## Redacting sensitive information + コメントの作者とリポジトリの書き込みアクセスがあるユーザは、コメントの編集履歴から機密情報を削除できます。 詳しい情報については、「[コメントの変更を追跡する](/communities/moderating-comments-and-conversations/tracking-changes-in-a-comment)」を参照してください。 1. 編集したいコメントに移動します。 @@ -65,20 +67,22 @@ shortTitle: コメントの管理 リポジトリに対する書き込み権限があるユーザは、Issue、プルリクエスト、 およびコミットに対するコメントを削除することができます。 Organization オーナー、チームメンテナ、コメント作成者は、チームのページのコメントを削除することもできます。 +Issue やプルリクエストで、会話に役立つ建設的な内容が部分的に含まれているコメントは、削除せず編集してください。 + コメントの削除は、モデレーターとしての最終手段です。 コメント全体が会話にとって建設的な内容ではない場合や、コミュニティの行動規範{% ifversion fpt or ghec %}または GitHub の[コミュニティ ガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines){% endif %}に違反している場合は、コメントを削除するのが妥当です。 コメントを削除すると、リポジトリに対する読み取りアクセスを持つユーザなら誰でも見ることのできるタイムラインイベントが作成されます。 ただし、コメントを削除したユーザの名前は、リポジトリへの書き込みアクセスを持つユーザにしか見えません。 書き込みアクセスを持たないユーザから見ると、タイムラインイベントは匿名化されています。 ![削除したコメントについて匿名化されたタイムラインイベント](/assets/images/help/issues/anonymized-timeline-entry-for-deleted-comment.png) -Issue やプルリクエストで、会話に役立つ建設的な内容が部分的に含まれているコメントは、削除せず編集してください。 - {% note %} **メモ:** Issue またはプルリクエストの最初のコメント (本文) は削除できません。 かわりに、Issue やプルリクエストの本文を編集して、不要な内容を削除してください。 {% endnote %} +### Steps to delete a comment + 1. 削除したいコメントに移動します。 2. コメントの右上隅にある {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックしてから、[**Delete**] をクリックします。 ![編集、非表示、削除、レポートのオプションが表示されている水平の kebab アイコンとコメント モデレーション メニュー](/assets/images/help/repository/comment-menu.png) 3. オプションで、コメントを削除したことを示すコメントとその理由を入力します。 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md index 76ebdb46af..e34282c087 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md @@ -26,6 +26,8 @@ The {% data variables.product.prodname_codespaces %} Education benefit gives ver To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Applying for an educator or teacher benefit](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)." +After you have confirmation that you are a verified teacher, visit [Global Campus for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team). + If you are eligible for the {% data variables.product.prodname_codespaces %} Education benefit, when you enable {% data variables.product.prodname_codespaces %} in {% data variables.product.prodname_classroom %} for your organization, GitHub automatically adds a Codespace policy to restrict machine types for all codespaces in the organization to 2 core machines. This helps you make the most of the free {% data variables.product.prodname_codespaces %} usage. However, you can change or remove these policies in your organization settings. 詳しい情報については「[マシンタイプへのアクセス制限](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)」を参照してください。 When the {% data variables.product.prodname_codespaces %} Education benefit moves out of beta, if your organization exceeds their free allowance for {% data variables.product.prodname_codespaces %} usage, your organization will be billed for additional usage. 詳しい情報については、「[{% data variables.product.prodname_codespaces %}の支払いについて](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#about-billing-for-codespaces)」を参照してください。 diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index ae99b4e34b..53c84e6964 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -25,7 +25,7 @@ shortTitle: Contribute to open source {% data variables.product.product_location %} で積極的に活動している場合は、[Explore](https://github.com/explore) での過去のコントリビューション、Star、およびその他のアクティビティに基づいて、プロジェクトについての個別の推奨事項と good first issue を見つけることができます。 Explore ニュースレターにサインアップして、あなたの興味に基づいて {% data variables.product.product_name %} にコントリビュートする機会について記載されたメールを受け取ることもできます。 サインアップするには、「[Explore メールニュースレター](https://github.com/explore/subscribe)」を参照してください。 -Keep up with recent activity from repositories you watch and people{% if for-you-feed %}, and organizations{% endif %} you follow with your personal dashboard. 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。 +Keep up with recent activity from repositories you watch, as well as people and organizations you follow, with your personal dashboard. 詳しい情報については[パーソナルダッシュボードについて](/articles/about-your-personal-dashboard)を参照してください。 {% data reusables.support.ask-and-answer-forum %} diff --git a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md index 2d2cf95ebd..0ecad65bc7 100644 --- a/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md +++ b/translations/ja-JP/content/get-started/exploring-projects-on-github/following-organizations.md @@ -17,7 +17,7 @@ topics: When you follow organizations, you'll see their public activity on your personal dashboard. 詳細は「[パーソナルダッシュボードについて](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard#staying-updated-with-activity-from-the-community)」を参照してください。 -You can unfollow an organization if you do not wish to see their public activity on {% data variables.product.product_name %}. +You can unfollow an organization if you do not wish to see their {% ifversion fpt or ghec %}public{% endif %} activity on {% data variables.product.product_name %}. ## Following an organization on {% data variables.product.product_name %} diff --git a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index aaf77fbfc8..348416cb75 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -237,6 +237,12 @@ If a task list item description begins with a parenthesis, you'll need to escape {% data variables.product.product_name %}上の人あるいは [Team](/articles/setting-up-teams/) は、@ に加えてユーザ名もしくは Team 名を入力することでメンションできます。 これにより通知がトリガーされ、会話に注意が向けられます。 コメントを編集してユーザ名や Team 名をメンションすれば、人々に通知を受信してもらえます。 通知の詳細は、{% ifversion fpt or ghes or ghae or ghec %}「[通知について](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}「[通知について](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}」を参照してください。 +{% note %} + +**Note:** A person will only be notified about a mention if the person has read access to the repository and, if the repository is owned by an organization, the person is a member of the organization. + +{% endnote %} + `@github/support これらのアップデートについてどう思いますか？` ![表示された @メンション](/assets/images/help/writing/mention-rendered.png) diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md index 128a7e7821..6fb3932273 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md @@ -47,7 +47,7 @@ Pull Requestの説明またはコミットメッセージで、サポートさ * resolves * resolved -他のPull RequestでPull Requestのコメントを参照するためにキーワードを使用すると、Pull Requestはリンクされます。 参照元のPull Requestをマージすると、参照先のPull Requestもクローズされます。 +他のPull RequestでPull Requestのコメントを参照するためにキーワードを使用すると、Pull Requestはリンクされます。 Merging the referencing pull request will also close the referenced issue. クローズするキーワードの構文は、IssueがPull Requestと同じリポジトリにあるかどうかによって異なります。 diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md index 0141ab32bd..074c7c7daa 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/creating-a-project.md @@ -163,7 +163,7 @@ topics: 6. タイプとして**Single select（単一選択）**を指定した場合は、選択肢を入力してください。 7. タイプとして**Iteration（繰り返し）**を指定した場合は、最初の繰り返しの日付と、繰り返しの期間を入力してください。 3つの繰り返しが自動的に作成され、プロジェクトの設定ページで繰り返しを追加できます。 -単一選択や繰り返しフィールドのドロップダウンの選択肢は、後から編集できます。 +You can also edit your custom fields. {% data reusables.projects.project-settings %} 1. **Fields（フィールド）**の下で、編集したいフィールドを選択してください。 diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md index 39a7cef51f..7e1669a8de 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md @@ -36,8 +36,8 @@ topics: {% data reusables.projects.access-insights %} 1. 左のメニューで、設定したいグラフをクリックしてください。 1. ページの右側で、**Configure（設定）**をクリックしてください。 パネルが右側に開きます。 -2. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 -3. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 "Time（時間）"を選択した場合、"Group by（グループ化）"は"Status（ステータス）" に変化し、"Y-Axis（Y軸）" は"Count of items（アイテム数）"に変化します。 -4. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 -5. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 -6. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 +1. グラフの種類を変更するには、**Layout（レイアウト）**ドロップダウンを選択し、使いたいグラフの種類をクリックしてください。 +1. グラフのX軸として使いたいフィールドを変更するには、**X-axis（X軸）**ドロップダウンを選択し、使いたいフィールドをクリックしてください。 +1. あるいは、X軸上のアイテムを別のフィールドでグループ化するには、**Group by（グループ化）**を選択し、使いたいフィールドをクリックするか、"None（なし）"をクリックしてグループ化を無効にしてください。 +1. あるいは、プロジェクトに数値フィールドが含まれており、Y軸でそういった数値フィールドの1つの合計、平均、最小、最大を表示したい場合には、**Y-axis（Y軸）**を選択し、選択肢をクリックしてください。 として、下に現れるドロップダウンを選択し、使いたい数値フィールドをクリックしてください。 +1. グラフを保存するには、**Save changes（変更を保存）**をクリックしてください。 diff --git a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md index b712fd998e..40c99ceccc 100644 --- a/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md +++ b/translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md @@ -77,7 +77,7 @@ To search for specific events, use the `action` qualifier in your query. Actions | [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %} | [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} | [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %} -| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% ifversion ghec %} +| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %} | [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %} | [`secret_scanning`](#secret_scanning-category-actions) | Contains organization-level configuration activities for secret scanning in existing repositories. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." | [`secret_scanning_new_repos`](#secret_scanning_new_repos-category-actions) | Contains organization-level configuration activities for secret scanning for new repositories created in the organization. {% endif %}{% ifversion fpt or ghec %} @@ -725,7 +725,7 @@ For more information, see "[Managing the publication of {% data variables.produc | `disable` | Triggered when a repository owner or person with admin access to the repository disables {% data variables.product.prodname_dependabot_alerts %}. | `enable` | Triggered when a repository owner or person with admin access to the repository enables {% data variables.product.prodname_dependabot_alerts %}. -{% endif %}{% ifversion ghec %} +{% endif %}{% if custom-repository-roles %} ### `role` category actions | Action | Description |------------------|------------------- diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md index 6c811493f9..1ca5404bd7 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md @@ -31,7 +31,7 @@ shortTitle: リポジトリロール {% ifversion fpt %} Organizationが{% data variables.product.prodname_ghe_cloud %}を使っているなら、カスタムのリポジトリロールを作成できます。 詳しい情報については、{% data variables.product.prodname_ghe_cloud %}のドキュメンテーションの「[Organizationのカスタムリポジトリロールの管理](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 -{% elsif ghec %} +{% elsif ghec or ghes > 3.4 or ghae-issue-6271 %} カスタムのリポジトリロールを作成できます。 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md index 457cee8b81..aca65983c3 100644 --- a/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md @@ -23,7 +23,7 @@ Organization のリポジトリにアクセスするとき Organization の全 Organizationのリポジトリに対する管理者アクセスがあるユーザが、リポジトリに対してそれより高いレベルのアクセスを付与すると、基本レベルのアクセスは、付与された高いアクセスによってオーバーライドされます。 -{% ifversion ghec %} +{% if custom-repository-roles %} Organizationの基本権限よりも低いアクセスを持つ継承ロールを持つカスタムのリポジトリロールを作成すると、そのロールに割り当てられたメンバーは、継承されたロールではなくOrganizationの基本権限がデフォルトになります。 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 {% endif %} diff --git a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md index 30ebdc95ae..8844932635 100644 --- a/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md +++ b/translations/ja-JP/content/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization.md @@ -13,23 +13,21 @@ topics: - Organizations - Teams shortTitle: 可視性の変更ポリシーの設定 +permissions: Organization owners can restrict repository visibility changes for an organization. --- -リポジトリの可視性を変更する資格を Organization のオーナーのみに制限すること、または可視性を変更することをリポジトリの管理者権限を所有するメンバーに許可することができます。 +You can restrict who has the ability to change the visibility of repositories in your organization, such as changing a repository from private to public. For more information about repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." + +You can restrict the ability to change repository visibility to organization owners only, or you can allow anyone with admin access to a repository to change visibility. {% warning %} -**警告**: この設定を有効にすると、管理者権限をもつユーザは、作成できるリポジトリのタイプにかかわらず、既存のリポジトリを任意の可視性に変更できるようになります。 詳しい情報については「[Organization でのリポジトリ作成の制限](/articles/restricting-repository-creation-in-your-organization)」を参照してください。 +**Warning**: If enabled, this setting allows people with admin access to choose any visibility for an existing repository, even if you do not allow that type of repository to be created. 詳しい情報については「[Organization でのリポジトリ作成の制限](/articles/restricting-repository-creation-in-your-organization)」を参照してください。 {% endwarning %} - {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.member-privileges %} 5. [Repository visibility change] の下で、[**Allow members to change repository visibilities for this organization**] の選択を解除します。 ![リポジトリ可視性変更をメンバーに許可するチェックボックス](/assets/images/help/organizations/disallow-members-to-change-repo-visibility.png) 6. [**Save**] をクリックします。 - -## 参考リンク - -- 「[リポジトリについて](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)」 diff --git a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index 57e2bf4d80..c0947122b6 100644 --- a/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/ja-JP/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -3,7 +3,7 @@ title: Organizationのカスタムリポジトリロールの管理 intro: カスタムのリポジトリロールを作成することで、Organizationのリポジトリへのアクセスをより詳細に制御できます。 permissions: Organization owners can manage custom repository roles. versions: - ghec: '*' + feature: custom-repository-roles topics: - Organizations - Teams @@ -49,6 +49,7 @@ Organization内では、ロールをOrganization、Team、リポジトリのレ 継承されたロールにまだ含まれていない場合にのみ、追加の権限を選択できます。 たとえば、継承されたロールがリポジトリへの**Write**アクセスを提供しているなら、"Close a pull request"権限は継承されたロールに既に含まれています。 +{% ifversion ghec %} ### Discussions - **Create a discussion category（ディスカッションカテゴリの作成）**: 新しいディスカッションカテゴリを作成できる。 詳しい情報については「[新しいディスカッションカテゴリの作成](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions#creating-a-category)」を参照してください。 @@ -57,6 +58,7 @@ Organization内では、ロールをOrganization、Team、リポジトリのレ - **Mark or unmark discussion answers（ディスカッションの回答のマークもしくはマーク解除）**: ディスカッションのカテゴリが回答を受け付ける藻のだった場合、ディスカッションの回答をマークできる。 詳しい情報については「[ディスカッション中のコメントを回答としてマークもしくはマーク解除する](/discussions/managing-discussions-for-your-community/moderating-discussions#marking-a-comment-as-an-answer)」を参照してください。 - **Hide or unhide discussion comments（ディスカッションコメントの非表示もしくは非表示解除）**: ディスカッションのコメントを非表示あるいは非表示解除できる。 詳しい情報については、「[ ディスカッションをモデレートする](/communities/moderating-comments-and-conversations/managing-disruptive-comments#hiding-a-comment)」を参照してください。 - **Convert issues to discussions（Issueをディスカッションに変換）**: Issueをディスカッションに変換できる。 詳しい情報については「[Issueのディスカッションへの変換](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)」を参照してください。 +{% endif %} ### IssueとPull Request @@ -86,7 +88,9 @@ Organization内では、ロールをOrganization、Team、リポジトリのレ - **Manage webhooks（webhookの管理）**: リポジトリにwebhookを追加。 - **Manage deploy keys（デプロイキーを管理）**: リポジトリにデプロイキーを追加。 - **Edit repository metadata（リポジトリのメタデータを編集）**: リポジトリの説明とともにリポジトリのトピックを更新。 +{%- ifversion ghec %} - **Set interaction limits（インタラクションの制限を設定）**: 自分のパブリックリポジトリで特定のユーザによるコメント、Issueのオープン、Pull Requestの作成を一時的に制限し、アクティビティの制限期間を施行。 詳しい情報については「[リポジトリでの操作の制限](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)」を参照してください。 +{%- endif %} - **Set the social preview（ソーシャルプレビューの設定）**: リポジトリがリンクされたときにソーシャルメディア上に表示される識別画像をリポジトリに追加。 詳細は「[リポジトリのソーシャルメディア向けプレビューをカスタマイズする](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)」を参照してください。 - **Push commits to protected branches（保護されたブランチにコミットをプッシュ）**: 保護されたブランチとしてマークされているブランチにプッシュ。 - **Create protected tags（保護されたタグの作成）**: タグの保護ルールにマッチしたタグの作成。 詳しい情報については「[タグ保護ルールの設定](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)」を参照してください。 diff --git a/translations/ja-JP/content/packages/index.md b/translations/ja-JP/content/packages/index.md index aa85790b2f..a03b3d8bbe 100644 --- a/translations/ja-JP/content/packages/index.md +++ b/translations/ja-JP/content/packages/index.md @@ -12,11 +12,11 @@ featuredLinks: - /packages/learn-github-packages/installing-a-package popular: - /packages/working-with-a-github-packages-registry/working-with-the-npm-registry - - '{% ifversion fpt or ghec%}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' + - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' - /packages/learn-github-packages - /packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry guideCards: - - '{% ifversion fpt or ghec %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' + - '{% ifversion fpt or ghec or ghes > 3.4 %}/packages/working-with-a-github-packages-registry/working-with-the-container-registry{% else %}/packages/working-with-a-github-packages-registry/working-with-the-docker-registry{% endif %}' - /packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry changelog: label: packages diff --git a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index bab8584936..360f84b646 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -8,9 +8,12 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '*' shortTitle: アクセスコントロールと可視性 --- +{% data reusables.package_registry.container-registry-ghes-beta %} + 詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。 現在は、{% data variables.product.prodname_container_registry %}でのみ詳細な権限を使うことができます。 詳細な権限は、npmレジストリなど他のパッケージレジストリではサポートされていません。 @@ -27,7 +30,7 @@ shortTitle: アクセスコントロールと可視性 パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。 -{% data reusables.package_registry.package-settings-from-user-level %} +{% data reusables.package_registry.package-settings-option %} 1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 Team には、個人アカウントが所持するコンテナイメージのアクセス権限を与えることができません。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png) 1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png) @@ -40,6 +43,7 @@ Organization が所有するコンテナイメージに対する管理者権限 パッケージがプライベートもしくはインターナルで、Organizationによって所有されているなら、あなたにできることは他のOrganizationメンバーやTeamにアクセス権を与えることだけです。 {% data reusables.package_registry.package-settings-from-org-level %} +{% data reusables.package_registry.package-settings-option %} 1. パッケージ設定ページで [**Invite teams or people**] をクリックして、アクセス権を付与するユーザの名前、ユーザ名、またはメールアドレスを入力します。 また、Organization から Team 名を入力して、全 Team メンバーにアクセスを付与することもできます。 ![コンテナアクセス権の招待ボタン](/assets/images/help/package-registry/container-access-invite.png) 1. ユーザ名または Team 名の隣にある [Role] のドロップダウンメニューで、付与する権限レベルを選択します。 ![コンテナアクセス権のオプション](/assets/images/help/package-registry/container-access-control-options.png) @@ -54,6 +58,7 @@ Organization が所有するコンテナイメージに対する管理者権限 リポジトリが同期されると、パッケージの詳細なアクセス設定にはアクセスできなくなります。 詳細なパッケージのアクセス設定を通じてパッケージの権限をカスタマイズするには、まず同期されたリポジトリを取り除かなければなりません。 {% data reusables.package_registry.package-settings-from-org-level %} +{% data reusables.package_registry.package-settings-option %} 2. "Repository source（リポジトリソース）"の下で、**Inherit access from repository (recommended)（アクセスをリポジトリから継承（推奨））**を選択してください。 ![リポジトリアクセスの継承チェックボックス](/assets/images/help/package-registry/inherit-repo-access-for-package.png) ## パッケージへのワークフローのアクセスの確保 @@ -70,7 +75,7 @@ Organization が所有するコンテナイメージに対する管理者権限 ### ユーザアカウントが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス -{% data reusables.package_registry.package-settings-from-user-level %} +{% data reusables.package_registry.package-settings-option %} 1. ひだりのサイドバーで、**Actions access（Actionsのアクセス）**をクリックしてください。 ![左メニューの"Actionsアクセス"オプション](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) 2. ワークフローがコンテナパッケージに確実にアクセスできるようにするには、ワークフローが保存されるリポジトリを追加しなければなりません。 **Add repository（リポジトリの追加）**をクリックし、追加したいリポジトリを検索してください。 !["リポジトリの追加"ボタン](/assets/images/help/package-registry/add-repository-button.png) 3. "role（ロール）"ドロップダウンメニューを使い、コンテナイメージに対してリポジトリに持たせたいデフォルトのアクセスレベルを選択してください。 ![リポジトリに与える権限アクセスレベル](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) @@ -80,12 +85,14 @@ Organization が所有するコンテナイメージに対する管理者権限 ### Organizationが所有するコンテナイメージへの{% data variables.product.prodname_actions %}のアクセス {% data reusables.package_registry.package-settings-from-org-level %} +{% data reusables.package_registry.package-settings-option %} 1. ひだりのサイドバーで、**Actions access（Actionsのアクセス）**をクリックしてください。 ![左メニューの"Actionsアクセス"オプション](/assets/images/help/package-registry/organization-repo-access-for-a-package.png) 2. **Add repository（リポジトリの追加）**をクリックし、追加したいリポジトリを検索してください。 !["リポジトリの追加"ボタン](/assets/images/help/package-registry/add-repository-button.png) 3. "role（ロール）"ドロップダウンメニューを使い、リポジトリのメンバーからコンテナイメージに対して持たせたいデフォルトのアクセスレベルを選択してください。 外部のコラボレータは含まれません。 ![リポジトリに与える権限アクセスレベル](/assets/images/help/package-registry/repository-permission-options-for-package-access-through-actions.png) コンテナイメージへのアクセスをさらにカスタマイズするには、「[Organizationのためのコンテナイメージへのアクセスの設定](#configuring-access-to-container-images-for-an-organization)」を参照してください。 +{% ifversion fpt or ghec %} ## パッケージへの{% data variables.product.prodname_codespaces %}アクセスの確保 デフォルトでは、codespaceは**Inherit access（アクセスの継承）**オプションが選択された同じリポジトリ内で公開されたパッケージなど、{% data variables.product.prodname_dotcom %} Container Registry内の特定パッケージにシームレスにアクセスできます。 自動的に設定されるアクセスに関する詳しい情報については「[{% data variables.product.prodname_dotcom %} Container Registryに保存されたイメージへのアクセス](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-github-container-registry)」を参照してください。 @@ -114,13 +121,14 @@ Organization が所有するコンテナイメージに対する管理者権限 !["リポジトリの削除"ボタン](/assets/images/help/package-registry/manage-codespaces-access-item.png) +{% endif %} ## 個人アカウントにコンテナイメージの可視性を設定する パッケージを最初に公開する際のデフォルトの可視性はプライベートで、パッケージを表示できるのは公開したユーザだけです。 アクセス設定を変更することで、プライベートやパブリックなコンテナイメージのアクセス権限を変更できます。 パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。 -{% data reusables.package_registry.package-settings-from-user-level %} +{% data reusables.package_registry.package-settings-option %} 5. [Danger Zone] の下で、可視性の設定を選択します。 - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。 {% warning %} @@ -149,6 +157,7 @@ Organization が所有するコンテナイメージに対する管理者権限 パブリックパッケージは認証なしに匿名でアクセスできます。 いったんパッケージをパブリックに設定すると、そのパッケージをプライベートに戻すことはできません。 {% data reusables.package_registry.package-settings-from-org-level %} +{% data reusables.package_registry.package-settings-option %} 5. [Danger Zone] の下で、可視性の設定を選択します。 - あらゆる人がコンテナイメージを表示できるようにするには、[**Make public**] をクリックします。 {% warning %} diff --git a/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md b/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md index 63152dc0c6..7aa0d652b6 100644 --- a/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md +++ b/translations/ja-JP/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md @@ -1,6 +1,6 @@ --- title: リポジトリのパッケージへの接続 -intro: 'リポジトリを{% data variables.product.prodname_dotcom %}上のコンテナイメージに接続できます。' +intro: 'リポジトリを{% data variables.product.product_location %}上のコンテナイメージに接続できます。' product: '{% data reusables.gated-features.packages %}' redirect_from: - /packages/managing-container-images-with-github-container-registry/connecting-a-repository-to-a-container-image @@ -8,6 +8,7 @@ redirect_from: versions: fpt: '*' ghec: '*' + ghes: '*' shortTitle: リポジトリの接続 --- @@ -25,16 +26,21 @@ shortTitle: リポジトリの接続 {% data reusables.package_registry.repository_connection_steps %} +{% ifversion fpt or ghec or ghes > 3.4 %} ## コマンドラインを使ってリポジトリをコンテナイメージに接続する -1. Dockerfile に以下の行を追加します。`OWNER` と `REPO` は、あなたの情報に置き換えてください。 +{% ifversion ghes > 3.4 %} +{% data reusables.package_registry.container-registry-ghes-beta %} +{% endif %} + +1. {% ifversion ghes %}`HOSTNAME`、{% endif %}`OWNER`、`REPO`を自分の詳細に置き換えて、Dockerfileに以下の行を加えてください。 ```shell - LABEL org.opencontainers.image.source=https://github.com/OWNER/REPO + LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/OWNER/REPO ``` - たとえば、あなたのユーザ名が `monalisa` で、`my-repo` を所有している場合は、以下の行を Dockerfile に追加します。 + たとえば、あなたがユーザ`monalisa`で`my-repo`を所有しており、{% data variables.product.product_location %}のホスト名が`github.companyname.com`なら、以下の行をDockerfileに追加することになります。 ```shell - LABEL org.opencontainers.image.source=https://github.com/monalisa/my-repo + LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}{% data reusables.package_registry.container-registry-example-hostname %}{% endif %}/monalisa/my-repo ``` 詳しい情報については、公式の Docker ドキュメンテーションの「[LABEL](https://docs.docker.com/engine/reference/builder/#label)」、および `opencontainers/image-spec` リポジトリの「[事前定義されたアノテーションキー](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys)」を参照してください。 @@ -46,33 +52,34 @@ shortTitle: リポジトリの接続 3. 必要に応じて、タグ付けする Docker イメージの情報を確認します。 ```shell $ docker images - > REPOSITORY TAG IMAGE ID CREATED SIZE - > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > hello-world latest fce289e99eb9 16 months ago 1.84kB + > REPOSITORY TAG IMAGE ID CREATED SIZE + > {% data reusables.package_registry.container-registry-example-hostname %}/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > {% data reusables.package_registry.container-registry-example-hostname %}/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > hello-world latest fce289e99eb9 16 months ago 1.84kB ``` 4. Docker イメージを任意のイメージ名とホスティング先でタグ付けします。 ```shell - $ docker tag IMAGE_NAME ghcr.io/OWNER/NEW_IMAGE_NAME:TAG + $ docker tag IMAGE_NAME {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:TAG ``` 例: ```shell - $ docker tag 38f737a91f39 ghcr.io/monalisa/hello_docker:latest + $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` 5. まだ{% data variables.product.prodname_container_registry %}で認証を受けていなければ、受けてください。 詳しい情報については「[{% data variables.product.prodname_container_registry %}で認証を受ける](/packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images#authenticating-to-the-container-registry)」を参照してください。 {% raw %} ```shell - $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin > Login Succeeded ``` {% endraw %} 6. コンテナイメージを{% data variables.product.prodname_container_registry %}にプッシュしてください。 ```shell - $ docker push ghcr.io/OWNER/IMAGE-NAME:TAG + $ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE-NAME:TAG ``` 例: ```shell - $ docker push ghcr.io/monalisa/hello_docker:latest + $ docker push {% data reusables.package_registry.container-registry-example-hostname %}/monalisa/hello_docker:latest ``` +{% endif %} 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 013c561d23..3d00a34394 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 @@ -1,6 +1,6 @@ --- -title: コンテナレジストリの利用 -intro: 'Docker及びOCIイメージを、パッケージの名前空間`https://ghcr.io`を使用する{% 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 @@ -15,107 +15,122 @@ redirect_from: versions: fpt: '*' ghec: '*' -shortTitle: コンテナレジストリ + ghes: '>= 3.5' +shortTitle: Container registry --- +{% ifversion ghes > 3.4 %} +{% note %} -## {% data variables.product.prodname_container_registry %}サポートについて +**Note**: {% data variables.product.prodname_container_registry %} is currently in beta for {% data variables.product.product_name %} and subject to change. -現在のところ、{% data variables.product.prodname_container_registry %} では以下のコンテナフォーマットをサポートしています。 +{% endnote %} +{% endif %} -* [DDocker イメージマニフェスト V2、スキーマ 2](https://docs.docker.com/registry/spec/manifest-v2-2/) -* [Open Container Initiative (OCI) 仕様](https://github.com/opencontainers/image-spec) +{% ifversion ghes > 3.4 %} +## Prerequisites -Dockerイメージをインストールあるいは公開する際には、{% data variables.product.prodname_container_registry %}はWindowsイメージのような外部レイヤーもサポートします。 +To configure and use the {% data variables.product.prodname_container_registry %} on {% data variables.product.prodname_ghe_server %}, your site administrator must first enable {% data variables.product.prodname_registry %} **and** 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 %} +## 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) Specifications](https://github.com/opencontainers/image-spec) + +When installing or publishing a Docker image, the {% data variables.product.prodname_container_registry %} supports foreign layers, such as Windows images. + +## Authenticating to the {% data variables.product.prodname_container_registry %} {% data reusables.package_registry.authenticate_with_pat_for_container_registry %} +{% 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 ghcr.io/OWNER/IMAGE_NAME:latest + $ 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 ghcr.io/OWNER/IMAGE-NAME:2.5 + $ 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 ghcr.io/OWNER/IMAGE_NAME + $ docker inspect {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME ``` -2. 必要に応じてローカルでイメージを削除します。 +2. Remove image locally as needed. ```shell - $ docker rmi ghcr.io/OWNER/IMAGE_NAME:latest + $ 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 ghcr.io/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs + $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs ``` -### 名前によるプル +### Pull by name ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME + $ 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 ghcr.io/OWNER/IMAGE_NAME:1.14.1 + $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:1.14.1 > 5e35bd43cf78: Pull complete > 0c48c2209aab: Pull complete > fd45dd1aad5a: Pull complete > db6eb50c2d36: Pull complete > Digest: sha256:ae3b135f133155b3824d8b1f62959ff8a72e9cf9e884d88db7895d8544010d8e - > Status: Downloaded newer image for ghcr.io/orgname/image-name/release:1.14.1 - > ghcr.io/orgname/image-name/release:1.14.1 + > Status: Downloaded newer image for {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1 + > {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1 ``` -### 名前と最新バージョンによるプル +### Pull by name and latest version ```shell - $ docker pull ghcr.io/OWNER/IMAGE_NAME:latest + $ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest > latest: Pulling from user/image-name > Digest: sha256:b3d3e366b55f9a54599220198b3db5da8f53592acbbb7dc7e4e9878762fc5344 - > Status: Downloaded newer image for ghcr.io/user/image-name:latest - > ghcr.io/user/image-name:latest + > Status: Downloaded newer image for {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest + > {% 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 - > ghcr.io/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB - > ghcr.io/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > {% data reusables.package_registry.container-registry-hostname %}/my-org/hello_docker latest 38f737a91f39 47 hours ago 91.7MB + > {% data reusables.package_registry.container-registry-hostname %}/my-username/hello_docker latest 38f737a91f39 47 hours ago 91.7MB > 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 ghcr.io/OWNER/NEW_IMAGE_NAME:latest + $ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest ``` diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md index 542edfc930..f5b9453f58 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -81,6 +81,16 @@ If you want to keep the source files for your site in a different location, you If you choose the `/docs` folder of any branch as your publishing source, {% data variables.product.prodname_pages %} will read everything to publish your site{% ifversion fpt or ghec %}, including the _CNAME_ file,{% endif %} from the `/docs` folder.{% ifversion fpt or ghec %} For example, when you edit your custom domain through the {% data variables.product.prodname_pages %} settings, the custom domain will write to `/docs/CNAME`. For more information about _CNAME_ files, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)."{% endif %} +{% ifversion ghec %} +## Limitations for {% data variables.product.prodname_emus %} +If you're a {% data variables.product.prodname_managed_user %}, your use of {% data variables.product.prodname_pages %} is limited. + + - {% data variables.product.prodname_pages %} sites can only be published from repositories owned by organizations. + - {% data variables.product.prodname_pages %} sites are only visible to other members of the enterprise. + +For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." +{% endif %} + ## Static site generators {% data variables.product.prodname_pages %} publishes any static files that you push to your repository. You can create your own static files or use a static site generator to build your site for you. You can also customize your own build process locally or on another server. We recommend Jekyll, a static site generator with built-in support for {% data variables.product.prodname_pages %} and a simplified build process. For more information, see "[About {% data variables.product.prodname_pages %} and Jekyll](/articles/about-github-pages-and-jekyll)." diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md index f8d6bdabeb..93bdcf0bf1 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md @@ -15,7 +15,7 @@ With access control for {% data variables.product.prodname_pages %}, you can res {% data reusables.pages.privately-publish-ghec-only %} -If your enterprise uses {% data variables.product.prodname_emus %}, all {% data variables.product.prodname_pages %} sites are privately published. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)." +If your enterprise uses {% data variables.product.prodname_emus %}, access control is not available, and all {% data variables.product.prodname_pages %} sites are only accessible to other enterprise members. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." If your organization uses {% data variables.product.prodname_ghe_cloud %} without {% data variables.product.prodname_emus %}, you can choose to publish your sites privately or publicly to anyone on the internet. Access control is available for project sites that are published from a private or internal repository that are owned by the organization. You cannot manage access control for an organization site. For more information about the types of {% data variables.product.prodname_pages %} sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index 713a82c2e3..29fa455c18 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -27,6 +27,7 @@ shortTitle: GitHub Pagesのサイトの作成 {% data reusables.repositories.create_new %} {% data reusables.repositories.owner-drop-down %} +{% indented_data_reference reusables.pages.emu-org-only spaces=3 %} {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} {% data reusables.repositories.initialize-with-readme %} diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index 778dc5a3ab..87fd626a65 100644 --- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -32,6 +32,7 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを {% data reusables.repositories.create_new %} {% data reusables.repositories.owner-drop-down %} +{% indented_data_reference reusables.pages.emu-org-only spaces=3 %} {% data reusables.pages.create-repo-name %} {% data reusables.repositories.choose-repo-visibility %} diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md index beeb02df46..7ae082fd14 100644 --- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md +++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md @@ -162,9 +162,13 @@ You can require that changes are successfully deployed to specific environments You can enable branch restrictions if your repository is owned by an organization using {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. {% endif %} -ブランチ制限を有効にすると、権限を与えられたユーザ、チーム、またはアプリのみが保護されたブランチにプッシュできます。 保護されたブランチの設定で、保護されたブランチへのプッシュアクセスを使用して、ユーザ、チーム、またはアプリを表示および編集できます。 When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging if the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required. +ブランチ制限を有効にすると、権限を与えられたユーザ、チーム、またはアプリのみが保護されたブランチにプッシュできます。 保護されたブランチの設定で、保護されたブランチへのプッシュアクセスを使用して、ユーザ、チーム、またはアプリを表示および編集できます。 When status checks are required, the people, teams, and apps that have permission to push to a protected branch will still be prevented from merging into the branch when the required checks fail. People, teams, and apps that have permission to push to a protected branch will still need to create a pull request when pull requests are required. -ユーザ、チーム、またはリポジトリへの write 権限を持つインストール済みの {% data variables.product.prodname_github_apps %} にのみ、保護されたブランチへのプッシュアクセス付与できます。 リポジトリへの管理者権限を持つユーザとアプリケーションは、いつでも保護されたブランチにプッシュできます。 +{% if restrict-pushes-create-branch %} +Optionally, you can apply the same restrictions to the creation of branches that match the rule. For example, if you create a rule that only allows a certain team to push to any branches that contain the word `release`, only members of that team would be able to create a new branch that contains the word `release`. +{% endif %} + +You can only give push access to a protected branch, or give permission to create a matching branch, to users, teams, or installed {% data variables.product.prodname_github_apps %} with write access to a repository. People and apps with admin permissions to a repository are always able to push to a protected branch or create a matching branch. ### フォースプッシュを許可 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 5efc6c6e75..61af217fe8 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 @@ -88,8 +88,9 @@ For more information about each of the available branch protection settings, see {%- endif %} 1. Optionally, select **Apply the rules above to administrators**. ![Apply the rules above to administrators checkbox](/assets/images/help/repository/include-admins-protected-branches.png) 1. 必要に応じて、{% ifversion fpt or ghec %}{% data variables.product.prodname_team %} または {% data variables.product.prodname_ghe_cloud %} を使用する Organization がリポジトリを所有している場合には、{% endif %}ブランチ制限を有効化します。 - - [**Restrict who can push to matching branches**] を選択します。 ![ブランチ制限のチェックボックス](/assets/images/help/repository/restrict-branch.png) - - 保護されたブランチにプッシュできる権限を持つユーザ、Team、またはアプリを検索し、選択します。 ![ブランチ制限の検索](/assets/images/help/repository/restrict-branch-search.png) + - [**Restrict who can push to matching branches**] を選択します。 ![Branch restriction checkbox](/assets/images/help/repository/restrict-branch.png){% if restrict-pushes-create-branch %} + - Optionally, to also restrict the creation of matching branches, select **Restrict pushes that create matching branches**. ![Branch creation restriction checkbox](/assets/images/help/repository/restrict-branch-create.png){% endif %} + - Search for and select the people, teams, or apps who will have permission to push to the protected branch or create a matching branch. ![Branch restriction search]{% if restrict-pushes-create-branch %}(/assets/images/help/repository/restrict-branch-search-with-create.png){% else %}(/assets/images/help/repository/restrict-branch-search.png){% endif %} 1. 必要に応じて、[Rules applied to everyone including administrators] で [**Allow force pushes**] を選択します。 ![フォースプッシュオプションを許可する](/assets/images/help/repository/allow-force-pushes.png) {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5624 %} Then, choose who can force push to the branch. diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index 6a418efff8..a60b6009ab 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -29,7 +29,7 @@ topics: {% endwarning %} -Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. 詳しい情報については、「[削除されたリポジトリを復元する](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)」を参照してください。 {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} +Some deleted repositories can be restored within {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif%} days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. 詳しい情報については、「[削除されたリポジトリを復元する](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)」を参照してください。 {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md b/translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md index 5c83d29d97..ddcfc56b3e 100644 --- a/translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md +++ b/translations/ja-JP/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md @@ -20,7 +20,7 @@ Anyone can restore deleted repositories that were owned by their own personal ac ## リポジトリの復元について -削除したリポジトリは、そのリポジトリが現在空ではないフォークネットワークの一部でない限り、90日以内であれば復元できます。 フォークネットワークは、親リポジトリ、リポジトリのフォーク、リポジトリのフォークのフォークで構成されます。 リポジトリがフォークネットワークの一部だった場合は、ネットワークの他のリポジトリすべてが削除されるか、ネットワークから切り離されていない限り、復元できません。 フォークに関する詳細は「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」を参照してください。 +A deleted repository can be restored within {% ifversion fpt or ghec or ghes > 3.4 %}30{% else %}90{% endif %} days, unless the repository was part of a fork network that is not currently empty. フォークネットワークは、親リポジトリ、リポジトリのフォーク、リポジトリのフォークのフォークで構成されます。 リポジトリがフォークネットワークの一部だった場合は、ネットワークの他のリポジトリすべてが削除されるか、ネットワークから切り離されていない限り、復元できません。 フォークに関する詳細は「[フォークについて](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)」を参照してください。 現在空ではないフォークネットワークの一部だったリポジトリを復元したい場合は、{% data variables.contact.contact_support %}にお問い合わせください。 diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 40af9e6a35..cd891a7545 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -63,11 +63,11 @@ You can disable {% data variables.product.prodname_actions %} for a repository, 1. Under "Actions permissions", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions to the list. {% if actions-workflow-policy%} - ![Add actions and reusable workflows to the allow list](/assets/images/help/repository/actions-policy-allow-list-with-workflows.png) + ![許可リストへのアクションと再利用可能なワークフローの追加](/assets/images/help/repository/actions-policy-allow-list-with-workflows.png) {%- elsif ghes %} - ![Add actions to the allow list](/assets/images/help/repository/actions-policy-allow-list.png) + ![許可リストへのアクションの追加](/assets/images/help/repository/actions-policy-allow-list.png) {%- else %} - ![Add actions to the allow list](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) + ![許可リストへのアクションの追加](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png) {%- endif %} 1. [**Save**] をクリックします。 @@ -156,3 +156,20 @@ You can use the steps below to configure whether {% if internal-actions%}actions {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.settings-sidebar-actions-general %} {% data reusables.actions.change-retention-period-for-artifacts-logs %} + +{% if actions-cache-policy-apis %} + +## Configuring cache storage for a repository + +{% data reusables.actions.cache-default-size %} However, these default sizes might be different if an enterprise owner has changed them. {% data reusables.actions.cache-eviction-process %} + +You can set a total cache storage size for your repository up to the maximum size allowed by the enterprise policy setting. + +The repository settings for {% data variables.product.prodname_actions %} cache storage can currently only be modified using the REST API: + +* To view the current cache storage limit for a repository, see "[Get GitHub Actions cache usage policy for a repository](/rest/actions/cache#get-github-actions-cache-usage-policy-for-a-repository)." +* To change the cache storage limit for a repository, see "[Set GitHub Actions cache usage policy for a repository](/rest/actions/cache#set-github-actions-cache-usage-policy-for-a-repository)." + +{% data reusables.actions.cache-no-org-policy %} + +{% endif %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md index fb30b71b9a..936c1ed459 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md @@ -5,9 +5,9 @@ intro: You can configure tag protection rules for your repository to prevent con product: '{% data reusables.gated-features.tag-protection-rules %}' versions: fpt: '*' - ghes: '>3.4' ghae: issue-6337 ghec: '*' + ghes: '>3.4' --- {% note %} @@ -18,7 +18,8 @@ versions: When you add a tag protection rule, all tags that match the pattern provided will be protected. Only users with admin or maintain permissions in the repository will be able to create protected tags, and only users with admin permissions in the repository will be able to delete protected tags. 詳しい情報については「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role)」を参照してください。 {% data variables.product.prodname_github_apps %} require the `Repository administration: write` permission to modify a protected tag. -Additionally, you can create custom repository roles to allow other groups of users to create or delete tags that match tag protection rules. 詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 +{% if custom-repository-roles %} +Additionally, you can create custom repository roles to allow other groups of users to create or delete tags that match tag protection rules. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)."{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/ja-JP/content/rest/actions/cache.md b/translations/ja-JP/content/rest/actions/cache.md index d4eb0cad55..aa684ed008 100644 --- a/translations/ja-JP/content/rest/actions/cache.md +++ b/translations/ja-JP/content/rest/actions/cache.md @@ -8,6 +8,7 @@ topics: versions: fpt: '*' ghec: '*' + ghes: '>3.4' --- ## Cache APIについて diff --git a/translations/ja-JP/content/rest/enterprise-admin/admin-stats.md b/translations/ja-JP/content/rest/enterprise-admin/admin-stats.md index aea84d5b28..1bac88b5b8 100644 --- a/translations/ja-JP/content/rest/enterprise-admin/admin-stats.md +++ b/translations/ja-JP/content/rest/enterprise-admin/admin-stats.md @@ -4,6 +4,8 @@ intro: 管理統計 API は、インストールに関するさまざまなメ versions: ghes: '*' ghae: '*' + ghec: '*' + fpt: '*' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/ja-JP/content/rest/repos/tags.md b/translations/ja-JP/content/rest/repos/tags.md index d024874ef1..40ff6ffa29 100644 --- a/translations/ja-JP/content/rest/repos/tags.md +++ b/translations/ja-JP/content/rest/repos/tags.md @@ -6,6 +6,7 @@ intro: '' versions: fpt: '*' ghec: '*' + ghes: '>3.4' topics: - API miniTocMaxHeadingLevel: 3 diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md index 9ad2f61497..1ea1c006ba 100644 --- a/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-discussions.md @@ -78,24 +78,6 @@ redirect_from: | comments:n | [**comments:>100**](https://github.com/search?q=comments%3A%3E100&type=Discussions) は、コメント数が 100 を超えるクローズしたディスカッションにマッチします。 | | | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Discussions)は、500 から 1,000 までの範囲のコメント数のディスカッションにマッチします。 | -## インタラクションの数で検索 - -`interactions` 修飾子を使用したインタラクションの数と、不等号や範囲の修飾子によってディスカッションをフィルタできます。 インタラクションの数は、ディスカッションに対するリアクションとコメントの数のことです。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 - -| 修飾子 | サンプル | -|:------------------------- |:----------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 以上あるディスカッションにマッチします。 | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、500～1,000 の範囲のインタラクションとのディスカッションにマッチします。 | - -## リアクションの数で検索 - -不等号や範囲の修飾子と一緒に `reactions` 修飾子を使用して、リアクションの数でディスカッションをフィルタすることができます。 詳しい情報については、「[検索構文を理解する](/github/searching-for-information-on-github/understanding-the-search-syntax)」を参照してください。 - -| 修飾子 | サンプル | -|:------------------------- |:------------------------------------------------------------------------------------------------------------------------ | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E500) は、リアクションの数が 500 以上あるディスカッションにマッチします。 | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500～1,000 の範囲のディスカッションにマッチします。 | - ## ディスカッションの作成時期または最終更新時期で検索 作成時期または最終更新時期でディスカッションをフィルタできます。 ディスカッションの作成時期については、`created` の修飾子を使います。ディスカッションの最終更新時期で表示するには、`updated` の修飾子を使います。 @@ -104,9 +86,9 @@ redirect_from: {% data reusables.search.date_gt_lt %} -| 修飾子 | サンプル | -|:-------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) は、2020 年 11 月 15 日以降に作成されたディスカッションにマッチします。 | +| 修飾子 | サンプル | +|:------------------------- |:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| created:YYYY-MM-DD | [**created:>2020-11-15**](https://github.com/search?q=created%3A%3E%3D2020-11-15&type=discussions) は、2020 年 11 月 15 日以降に作成されたディスカッションにマッチします。 | | updated:YYYY-MM-DD | [**weird in:body updated:>=2020-02-01**](https://github.com/search?q=weird+in%3Abody+updated%3A%3E%3D2020-12-01&type=Discussions) は、2020 年 12 月以降に更新された、本文に「weird」という単語を含むディスカッションにマッチします。 | ## 参考リンク diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md index e2c0849e0b..b21e4e87b7 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md @@ -73,8 +73,6 @@ Open Collective を使用して Stripe Connect を設定する方法について {% data reusables.sponsors.tax-form-information-org %} {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.settings-tab %} -{% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %} @@ -90,5 +88,6 @@ Before your organization can become a sponsored organization, you must enable 2F {% data reusables.sponsors.github-review-app %} ## 参考リンク + - [{% 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)」 diff --git a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md index 82bbcbaa48..679e17e49b 100644 --- a/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md +++ b/translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md @@ -70,8 +70,6 @@ Organization として {% data variables.product.prodname_sponsors %} に参加 {% data reusables.sponsors.tax-form-information-dev %} {% data reusables.sponsors.navigate-to-sponsors-dashboard %} -{% data reusables.sponsors.settings-tab %} -{% data reusables.sponsors.country-of-residence %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %} diff --git a/translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md b/translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md index b6d5e1071a..e1409be088 100644 --- a/translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md +++ b/translations/ja-JP/content/support/learning-about-github-support/about-github-premium-support.md @@ -49,7 +49,7 @@ There are two {% data variables.contact.premium_support %} plans: Premium and Pr | Members with support entitlements | 10 | 25 | | Resources | Priority ticket handling | | | Scheduled checks| Bi-annual health check and reporting | | -| Administration assistance| | 4 hours per month | +| Administration assistance| None | 4 hours per month | {% note %} diff --git a/translations/ja-JP/data/features/README.md b/translations/ja-JP/data/features/README.md index 7e849edcda..044b3fa416 100644 --- a/translations/ja-JP/data/features/README.md +++ b/translations/ja-JP/data/features/README.md @@ -45,7 +45,7 @@ versions: ## スキーマの適用 -The schema for validating the feature versioning lives in [`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js) and is exercised by [`tests/linting/lint-files.js`](/tests/linting/lint-files.js). +機能のバージョン管理の検証のためのスキーマは[`tests/helpers/schemas/feature-versions-schema.js`](/tests/helpers/schemas/feature-versions-schema.js)にあり、[`tests/linting/lint-files.js`](/tests/linting/lint-files.js)によって実行されます。 ## 機能タグを削除するためのスクリプト diff --git a/translations/ja-JP/data/features/actions-cache-policy-apis.yml b/translations/ja-JP/data/features/actions-cache-policy-apis.yml new file mode 100644 index 0000000000..808618d84d --- /dev/null +++ b/translations/ja-JP/data/features/actions-cache-policy-apis.yml @@ -0,0 +1,6 @@ +--- +#Reference: #6456 +#APIs to set default and max cache sizes. Only for GHES. +versions: + ghes: '>=3.5' + ghae: 'issue-6456' diff --git a/translations/ja-JP/data/features/actions-caching.yml b/translations/ja-JP/data/features/actions-caching.yml new file mode 100644 index 0000000000..6b1eea54a7 --- /dev/null +++ b/translations/ja-JP/data/features/actions-caching.yml @@ -0,0 +1,8 @@ +--- +#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' diff --git a/translations/ja-JP/data/features/custom-repository-roles.yml b/translations/ja-JP/data/features/custom-repository-roles.yml new file mode 100644 index 0000000000..c487dad981 --- /dev/null +++ b/translations/ja-JP/data/features/custom-repository-roles.yml @@ -0,0 +1,5 @@ +--- +versions: + ghec: '*' + ghes: '>=3.5' + ghae: 'issue-6271' diff --git a/translations/ja-JP/data/features/for-you-feed.yml b/translations/ja-JP/data/features/for-you-feed.yml index accb79a00c..aee851bee7 100644 --- a/translations/ja-JP/data/features/for-you-feed.yml +++ b/translations/ja-JP/data/features/for-you-feed.yml @@ -4,3 +4,4 @@ versions: fpt: '*' ghec: '*' + ghes: '>=3.5' diff --git a/translations/ja-JP/data/features/ip-exception-list.yml b/translations/ja-JP/data/features/ip-exception-list.yml new file mode 100644 index 0000000000..a6aacf815c --- /dev/null +++ b/translations/ja-JP/data/features/ip-exception-list.yml @@ -0,0 +1,3 @@ +--- +versions: + ghes: '>=3.5' diff --git a/translations/ja-JP/data/features/restrict-pushes-create-branch.yml b/translations/ja-JP/data/features/restrict-pushes-create-branch.yml new file mode 100644 index 0000000000..2ddfa5adc3 --- /dev/null +++ b/translations/ja-JP/data/features/restrict-pushes-create-branch.yml @@ -0,0 +1,8 @@ +--- +#Issue 6045 +#Restrict pushes that create matching branches option, within branch restrictions +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6045' diff --git a/translations/ja-JP/data/features/server-statistics.yml b/translations/ja-JP/data/features/server-statistics.yml new file mode 100644 index 0000000000..8b17527b8a --- /dev/null +++ b/translations/ja-JP/data/features/server-statistics.yml @@ -0,0 +1,5 @@ +--- +#Reference #6677 +#Documentation for GitHub Enterprise Server Statistics +versions: + ghes: '>=3.5' diff --git a/translations/ja-JP/data/glossaries/README.md b/translations/ja-JP/data/glossaries/README.md index 324db4ca24..7297bcd426 100644 --- a/translations/ja-JP/data/glossaries/README.md +++ b/translations/ja-JP/data/glossaries/README.md @@ -3,6 +3,6 @@ [ Crowdinの用語集](https://support.crowdin.com/glossary/)は以下のファイルから構成されます。 * `external.yml`には顧客向けの用語集のエントリが含まれます。 - * Strings within `external.yml` support Liquid conditionals. See [contributing/liquid-helpers.md](/contributing/liquid-helpers.md). + * `external.yml`内の文字列は、Liquid条件演算子をサポートします。 [contributing/liquid-helpers.md](/contributing/liquid-helpers.md)を参照。 * `internal.yml`には、翻訳者だけが使うエントリが含まれます。 これらの用語はCrowdinのUIに表示され、翻訳者に対して翻訳しているものに関する追加の文脈と、その後に対するローカライズされた文字列の提案を提供します。 * `candidates.yml`には、内部的あるいは外部的な用語集に含まれるべきではあるものの、まだ定義されていない用語が含まれます。 diff --git a/translations/ja-JP/data/glossaries/external.yml b/translations/ja-JP/data/glossaries/external.yml index 6080adab6c..9b2bea885b 100644 --- a/translations/ja-JP/data/glossaries/external.yml +++ b/translations/ja-JP/data/glossaries/external.yml @@ -210,7 +210,7 @@ description: ユーザのメールアドレスに送信される通知。 - term: Enterpriseアカウント - description: Enterprise accounts allow you to centrally manage policy and billing for multiple organizations. {% data reusables.gated-features.enterprise-accounts %} + description: Enterpriseアカウントを利用すると、複数のOrganizationのポリシーと支払いを集中管理できます。{% data reusables.gated-features.enterprise-accounts %} - term: Explorer description: >- @@ -594,9 +594,9 @@ description: >- リポジトリは GitHub の最も基本的な要素です。プロジェクトのフォルダとして最も想像しやすいものです。リポジトリ 1 つに（ドキュメントを含む）すべてのプロジェクトファイルが含まれ、各ファイルのリビジョン履歴が格納されます。リポジトリはコラボレータを複数持つことができ、またパブリックとプライベートのいずれの場合もあります。 - - term: repository cache + term: リポジトリキャッシュ description: >- - A read-only mirror of repositories for your GitHub Enterprise server instance, located near distributed teams and CI clients. + GitHub Enterprise Serverインスタンスのリポジトリの読み取り専用ミラーで、分散しているチームやCIクライアントの近くにあります。 - term: リポジトリグラフ description: リポジトリのデータの視覚的表現。 diff --git a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml index 026c8aaa4a..133a7b9400 100644 --- a/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml +++ b/translations/ja-JP/data/graphql/ghae/graphql_upcoming_changes.public-ghae.yml @@ -58,22 +58,22 @@ upcoming_changes: owner: synthead - location: Repository.defaultMergeQueue - description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.' - reason: '`defaultMergeQueue` will be removed.' + description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。' + reason: '`defaultMergeQueue`は削除されます。' date: '2022-04-01' criticality: 破壊的 owner: colinshum - location: AddPullRequestToMergeQueueInput.branch - description: '`branch` will be removed.' - reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op + description: '`branch`は削除されます。' + reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。 date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jhunschejones - location: Enterprise.userAccounts - description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.' - reason: The `Enterprise.userAccounts` field is being removed. + description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。' + reason: '`Enterprise.userAccounts`フィールドは削除されています。' date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes diff --git a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml index 785baf021e..ad7dbf4d85 100644 --- a/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/ghec/graphql_upcoming_changes.public.yml @@ -72,36 +72,36 @@ upcoming_changes: owner: synthead - location: Repository.defaultMergeQueue - description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.' - reason: '`defaultMergeQueue` will be removed.' + description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。' + reason: '`defaultMergeQueue`は削除されます。' date: '2022-04-01' criticality: 破壊的 owner: colinshum - location: AddPullRequestToMergeQueueInput.branch - description: '`branch` will be removed.' - reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op + description: '`branch`は削除されます。' + reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。 date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jhunschejones - location: Enterprise.userAccounts - description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.' - reason: The `Enterprise.userAccounts` field is being removed. + description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。' + reason: '`Enterprise.userAccounts`フィールドは削除されています。' date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Query.sponsorables.dependencyEcosystem - description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.' - reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem. + description: '`dependencyEcosystem`は削除されます。代わりにecosystem引数を使用してください。' + reason: 型はSecurityAdvisoryEcosystemからDependencyGraphEcossystemに切り替わります。 date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: UpdateProjectNextItemFieldInput.fieldWithSettingId - description: '`fieldWithSettingId` will be removed. Use `fieldConstraintId` instead' - reason: Renamed to fieldConstraintId to improve naming consistency. + description: '`fieldWithSettingId`は削除されます。代わりに`fieldConstraintId`を使用してください' + reason: 名前の一貫性を向上させるためにfieldConstraintIdに名前を変更しました。 date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: memex diff --git a/translations/ja-JP/data/graphql/ghes-3.5/graphql_previews.enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.5/graphql_previews.enterprise.yml new file mode 100644 index 0000000000..870a8b1e9c --- /dev/null +++ b/translations/ja-JP/data/graphql/ghes-3.5/graphql_previews.enterprise.yml @@ -0,0 +1,124 @@ +--- +- + title: パッケージのバージョン削除へのアクセス + description: >- + このプレビューは、プライベートパッケージバージョンの削除を有効化する、DeletePackageVersionのミューテーションのサポートを追加します。 + toggled_by: ':package-deletes-preview' + announcement: null + updates: null + toggled_on: + - Mutation.deletePackageVersion + owning_teams: + - '@github/pe-package-registry' +- + title: デプロイメント + description: >- + このプレビューは、デプロイメントのミューテーションと新しいデプロイメントの機能を追加します。 + toggled_by: ':flash-preview' + announcement: null + updates: null + toggled_on: + - DeploymentStatus.environment + - Mutation.createDeploymentStatus + - CreateDeploymentStatusInput + - CreateDeploymentStatusPayload + - Mutation.createDeployment + - CreateDeploymentInput + - CreateDeploymentPayload + owning_teams: + - '@github/c2c-actions-service' +- + title: >- + >- MergeInfoPreview - Pull Requestのマージ状態に関する詳細な情報。 + description: >- + このプレビューは、プルリクエストのマージ状態に関する詳細な情報を提供するフィールドへのアクセスのサポートを追加します。 + toggled_by: ':merge-info-preview' + announcement: null + updates: null + toggled_on: + - PullRequest.canBeRebased + - PullRequest.mergeStateStatus + owning_teams: + - '@github/pe-pull-requests' +- + title: UpdateRefsPreview - 1回の操作で複数の参照を更新します。 + description: このプレビューは、1回の操作による複数の参照の更新のサポートを追加します。 + toggled_by: ':update-refs-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateRefs + - GitRefname + - RefUpdate + - UpdateRefsInput + - UpdateRefsPayload + owning_teams: + - '@github/reponauts' +- + title: プロジェクトイベントの詳細 + description: >- + このプレビューは、プロジェクト関連のIssueイベントに対し、プロジェクト、プロジェクトカード、プロジェクト列の詳細を追加します。 + toggled_by: ':starfox-preview' + announcement: null + updates: null + toggled_on: + - AddedToProjectEvent.project + - AddedToProjectEvent.projectCard + - AddedToProjectEvent.projectColumnName + - ConvertedNoteToIssueEvent.project + - ConvertedNoteToIssueEvent.projectCard + - ConvertedNoteToIssueEvent.projectColumnName + - MovedColumnsInProjectEvent.project + - MovedColumnsInProjectEvent.projectCard + - MovedColumnsInProjectEvent.projectColumnName + - MovedColumnsInProjectEvent.previousProjectColumnName + - RemovedFromProjectEvent.project + - RemovedFromProjectEvent.projectColumnName + owning_teams: + - '@github/github-projects' +- + title: ラベルのプレビュー + description: >- + このプレビューは、ラベルの追加、更新、作成、削除のサポートを追加します。 + toggled_by: ':bane-preview' + announcement: null + updates: null + toggled_on: + - Mutation.createLabel + - CreateLabelPayload + - CreateLabelInput + - Mutation.deleteLabel + - DeleteLabelPayload + - DeleteLabelInput + - Mutation.updateLabel + - UpdateLabelPayload + - UpdateLabelInput + owning_teams: + - '@github/pe-pull-requests' +- + title: プロジェクトのインポート + description: このプレビューは、プロジェクトのインポートのサポートを追加します。 + toggled_by: ':slothette-preview' + announcement: null + updates: null + toggled_on: + - Mutation.importProject + owning_teams: + - '@github/pe-issues-projects' +- + title: Teamレビューの割り当てプレビュー + description: >- + このプレビューは、Teamレビューの割り当て設定の更新サポートを追加します + toggled_by: ':stone-crop-preview' + announcement: null + updates: null + toggled_on: + - Mutation.updateTeamReviewAssignment + - UpdateTeamReviewAssignmentInput + - TeamReviewAssignmentAlgorithm + - Team.reviewRequestDelegationEnabled + - Team.reviewRequestDelegationAlgorithm + - Team.reviewRequestDelegationMemberCount + - Team.reviewRequestDelegationNotifyTeam + owning_teams: + - '@github/pe-pull-requests' diff --git a/translations/ja-JP/data/graphql/ghes-3.5/graphql_upcoming_changes.public-enterprise.yml b/translations/ja-JP/data/graphql/ghes-3.5/graphql_upcoming_changes.public-enterprise.yml new file mode 100644 index 0000000000..0853108bea --- /dev/null +++ b/translations/ja-JP/data/graphql/ghes-3.5/graphql_upcoming_changes.public-enterprise.yml @@ -0,0 +1,114 @@ +--- +upcoming_changes: + - + location: LegacyMigration.uploadUrlTemplate + description: '`uploadUrlTemplate`は削除されます。代わりに`uploadUrl` を使ってください。' + reason: '`uploadUrlTemplate`は、標準のURLではなく、ユーザーの手順を余分に追加することになるので、削除されています。' + date: '2019-04-01T00:00:00+00:00' + criticality: 破壊的 + owner: tambling + - + location: AssignedEvent.user + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' + reason: アサインされた人を、マネキンにできるようになりました。 + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: tambling + - + location: EnterpriseBillingInfo.availableSeats + description: '`availableSeats`は削除されます。代わりにEnterpriseBillingInfo.totalAvailableLicensesを使ってください。' + reason: '`availableSeats`は、返される値をより明確にするために`totalAvailableLicenses`に置き換えられます。' + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BlakeWilliams + - + location: EnterpriseBillingInfo.seats + description: '`seats`は削除されます。代わりにEnterpriseBillingInfo.totalLicensesを使ってください。' + reason: '`seats` は、返される値をより明確にするために`totalLicenses`に置き換えられます。' + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BlakeWilliams + - + location: UnassignedEvent.user + description: '`user`は削除されます。代わりに`assignee`フィールドを使ってください。' + reason: アサインされた人を、マネキンにできるようになりました。 + date: '2020-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: tambling + - + location: EnterprisePendingMemberInvitationEdge.isUnlicensed + description: '`isUnlicensed`は削除されます。' + reason: 保留中の全メンバーはライセンスを消費します + date: '2020-07-01T00:00:00+00:00' + criticality: 破壊的 + owner: BrentWheeldon + - + location: Issue.timeline + description: '`timeline`は削除されます。代わりにIssue.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' + date: '2020-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: mikesea + - + location: PullRequest.timeline + description: '`timeline`は削除されます。代わりにPullRequest.timelineItemsを使ってください。' + reason: '`timeline`は削除されます。' + date: '2020-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: mikesea + - + location: EnterpriseMemberEdge.isUnlicensed + description: '`isUnlicensed`は削除されます。' + reason: すべてのメンバーはライセンスを消費します + date: '2021-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BrentWheeldon + - + location: EnterpriseOutsideCollaboratorEdge.isUnlicensed + description: '`isUnlicensed`は削除されます。' + reason: すべての外部コラボレータはライセンスを消費します + date: '2021-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: BrentWheeldon + - + location: MergeStateStatus.DRAFT + description: '`DRAFT`は削除されます。代わりにPullRequest.isDraftを使ってください。' + reason: DRAFTの状態はこのenumから削除されるので、代わりに`isDraft`を使わなければなりません。 + date: '2021-01-01T00:00:00+00:00' + criticality: 破壊的 + owner: nplasterer + - + location: PackageType.DOCKER + description: '`DOCKER`は削除されます。' + reason: DOCKERは、Packages REST APIでのみ使われるように移行されるので、このenumから削除されます。 + date: '2021-06-21' + criticality: 破壊的 + owner: reybard + - + location: ReactionGroup.users + description: '`users`は削除されます。代わりに`reactors`フィールドを使ってください。' + reason: リアクターは、マネキン、ボット、Organizationになることができます。 + date: '2021-10-01T00:00:00+00:00' + criticality: 破壊的 + owner: synthead + - + location: Repository.defaultMergeQueue + description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。' + reason: '`defaultMergeQueue`は削除されます。' + date: '2022-04-01' + criticality: 破壊的 + owner: colinshum + - + location: AddPullRequestToMergeQueueInput.branch + description: '`branch`は削除されます。' + reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。 + date: '2022-07-01T00:00:00+00:00' + criticality: 破壊的 + owner: jhunschejones + - + location: Enterprise.userAccounts + description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。' + reason: '`Enterprise.userAccounts`フィールドは削除されています。' + date: '2022-07-01T00:00:00+00:00' + criticality: 破壊的 + owner: jdennes diff --git a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml index 785baf021e..ad7dbf4d85 100644 --- a/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml +++ b/translations/ja-JP/data/graphql/graphql_upcoming_changes.public.yml @@ -72,36 +72,36 @@ upcoming_changes: owner: synthead - location: Repository.defaultMergeQueue - description: '`defaultMergeQueue` will be removed. Use `Repository.mergeQueue` instead.' - reason: '`defaultMergeQueue` will be removed.' + description: '`defaultMergeQueue`は削除されます。代わりに`Repository.mergeQueue`を使用してください。' + reason: '`defaultMergeQueue`は削除されます。' date: '2022-04-01' criticality: 破壊的 owner: colinshum - location: AddPullRequestToMergeQueueInput.branch - description: '`branch` will be removed.' - reason: PRs are added to the merge queue for the base branch, the `branch` argument is now a no-op + description: '`branch`は削除されます。' + reason: PRsはベースブランチのマージキューに追加されます。引数`branch`はno-opになりました。 date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jhunschejones - location: Enterprise.userAccounts - description: '`userAccounts` will be removed. Use the `Enterprise.members` field instead.' - reason: The `Enterprise.userAccounts` field is being removed. + description: '`userAccounts`は削除されます。代わりに`Enterprise.members`フィールドを使用してください。' + reason: '`Enterprise.userAccounts`フィールドは削除されています。' date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: jdennes - location: Query.sponsorables.dependencyEcosystem - description: '`dependencyEcosystem` will be removed. Use the ecosystem argument instead.' - reason: The type is switching from SecurityAdvisoryEcosystem to DependencyGraphEcosystem. + description: '`dependencyEcosystem`は削除されます。代わりにecosystem引数を使用してください。' + reason: 型はSecurityAdvisoryEcosystemからDependencyGraphEcossystemに切り替わります。 date: '2022-07-01T00:00:00+00:00' criticality: 破壊的 owner: cheshire137 - location: UpdateProjectNextItemFieldInput.fieldWithSettingId - description: '`fieldWithSettingId` will be removed. Use `fieldConstraintId` instead' - reason: Renamed to fieldConstraintId to improve naming consistency. + description: '`fieldWithSettingId`は削除されます。代わりに`fieldConstraintId`を使用してください' + reason: 名前の一貫性を向上させるためにfieldConstraintIdに名前を変更しました。 date: '2022-10-01T00:00:00+00:00' criticality: 破壊的 owner: memex diff --git a/translations/ja-JP/data/learning-tracks/actions.yml b/translations/ja-JP/data/learning-tracks/actions.yml index 9464e1258f..35e328fb76 100644 --- a/translations/ja-JP/data/learning-tracks/actions.yml +++ b/translations/ja-JP/data/learning-tracks/actions.yml @@ -38,8 +38,8 @@ deploy_to_the_cloud: - /actions/deployment/deploying-to-azure-app-service - /actions/deployment/deploying-to-google-kubernetes-engine adopting_github_actions_for_your_enterprise_ghec: - title: 'Adopt GitHub Actions for your enterprise' - description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' + title: 'GitHub ActionsをEnterpriseで採用する' + description: 'Enterpriseにおける{% data variables.product.prodname_actions %}のロールアウトの計画と実装の方法を学びましょう。' versions: ghec: '*' guides: @@ -51,8 +51,8 @@ adopting_github_actions_for_your_enterprise_ghec: - /actions/security-guides/security-hardening-for-github-actions - /billing/managing-billing-for-github-actions/about-billing-for-github-actions adopting_github_actions_for_your_enterprise_ghes_and_ghae: - title: 'Adopt GitHub Actions for your enterprise' - description: 'Learn how to plan and implement a rollout of {% data variables.product.prodname_actions %} in your enterprise.' + title: 'GitHub ActionsをEnterpriseで採用する' + description: 'Enterpriseにおける{% data variables.product.prodname_actions %}のロールアウトの計画と実装の方法を学びましょう。' versions: ghes: '*' ghae: '*' diff --git a/translations/ja-JP/data/learning-tracks/code-security.yml b/translations/ja-JP/data/learning-tracks/code-security.yml index d3ce0ebbb0..88d443221b 100644 --- a/translations/ja-JP/data/learning-tracks/code-security.yml +++ b/translations/ja-JP/data/learning-tracks/code-security.yml @@ -2,7 +2,7 @@ #Feature available only on dotcom security_advisories: title: 'セキュリティ脆弱性の修正及び開示' - description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' + description: 'リポジトリのセキュリティアドバイザリを使用して報告された脆弱性を非公開で修正し、CVEを取得してください。' featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}' guides: - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml new file mode 100644 index 0000000000..0c19cdcf13 --- /dev/null +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -0,0 +1,345 @@ +--- +date: '2022-05-10' +release_candidate: true +deprecated: false +intro: | + {% note %} + + **Note:** If {% data variables.product.product_location %} is running a release candidate build, you can't upgrade with a hotpatch. We recommend only running release candidates on test environments. + + {% endnote %} + + For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)." +sections: + features: + - + heading: IP exception list for validation testing after maintenance + notes: + - | + You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." + - + heading: Custom repository roles are generally available + notes: + - | + With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + + A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository. + + Custom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization. + + Custom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation. + - + heading: GitHub Container registry in public beta + notes: + - | + The GitHub Container registry (GHCR) is now available in GitHub Enterprise Server 3.5 as a public beta, offering developers the ability to publish, download, and manage containers. GitHub Packages container support implements the OCI standards for hosting Docker images. For more information, see "[GitHub Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." + - + heading: Dependabot updates are generally available + notes: + - | + Dependabot version and security updates are now generally available in GitHub Enterprise Server 3.5. All the popular ecosystems and features that work on GitHub.com repositories now can be set up on your GitHub Enterprise Server instance. Dependabot on GitHub Enterprise Server requires GitHub Actions and a pool of self-hosted Dependabot runners, GitHub Connect enabled, and Dependabot enabled by an admin. + + Following on from the public beta release, we will be supporting the use of GitHub Actions runners hosted on a Kubernetes setup. + + For more information, see "[Setting up Dependabot updates](https://docs.github.com/en/enterprise-server@3.5/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + - + heading: Server Statistics in public beta + notes: + - | + You can now analyze how your team works, understand the value you get from GitHub Enterprise Server, and help us improve our products by reviewing your instance's usage data and sharing this aggregate data with GitHub. You can use your own tools to analyze your usage over time by downloading your data in a CSV or JSON file or by accessing it using the REST API. To see the list of aggregate metrics collected, see "[About Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." **Server Statistics data includes no personal data nor GitHub content, such as code, issues, comments, or pull requests content. For a better understanding of how we store and secure Server Statistics data, see "[GitHub Security](https://github.com/security)."** For more information about Server Statistics, see "[Analyzing how your team works with Server Statistics](/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics)." This feature is available in public beta. + - + heading: GitHub Actions rate limiting is now configurable + notes: + - | + Site administrators can now enable and configure a rate limit for GitHub Actions. By default, the rate limit is disabled. When workflow jobs cannot immediately be assigned to an available runner, they will wait in a queue until a runner is available. However, if GitHub Actions experiences a sustained high load, the queue can back up faster than it can drain and the performance of the GitHub Enterprise Server instance may degrade. To avoid this, an administrator can configure a rate limit. When the rate limit is exceeded, additional workflow runs will fail immediately rather than being put in the queue. Once the rate has stabilized below the threshold, new runs can be queued again. For more information, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits#configuring-rate-limits-for-github-actions)." + - + heading: OpenID Connect (OIDC) for secure deployments with GitHub Actions + notes: + - | + GitHub Actions on GitHub Enterprise Server now supports OIDC for secure deployments to cloud providers, which uses short-lived tokens that are automatically rotated for each deployment. OIDC enables the following functionality. + + - Seamless authentication between cloud providers and GitHub Enterprise Server without the need for storing any long-lived cloud secrets on your instance + - Cloud administrators can rely on the security mechanisms of a particular cloud provider to ensure that GitHub Actions workflows have minimal access to cloud resources. There is no duplication of secret management between GitHub Enterprise Server and the cloud. + + For more information, see "[Security hardening your deployments](/actions/deployment/security-hardening-your-deployments)." + - + heading: Sharing GitHub Actions within your enterprise is generally available + notes: + - | + Support for GitHub Actions in internal repositories is now generally available for organizations on your GitHub Enterprise Server instance. You can innersource automation by sharing actions in internal repositories. You can manage a repository's settings or use the REST API to allow access to workflows in other repositories within the organization or in any organization on the instance. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)," "[Managing GitHub Actions settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)," and "[Actions Permissions](/rest/actions/permissions#get-the-level-of-access-for-workflows-outside-of-the-repository)" in the REST API documentation. + - + heading: Cache support for GitHub Actions on GitHub Enterprise Server is now generally available + notes: + - | + You can now use dependency caching to speed up your GitHub Actions workflows. To cache dependencies for a job, you can include the [actions/cache](https://github.com/actions/cache) action to create a cache with a unique key. You can share caches across all workflows in the same repository. These workflows can then restore the cache and run faster. + + Actions users can also use our cache APIs to: + + - Define the enterprise policy for cache size range allowed per repository. + - Query the cache usage within each repository and monitor if the total size of all caches is reaching the upper limit. + - Increase the maximum cache size for a repository within the allowed enterprise limits, based on the cache requirements of the repository. + - Monitor aggregate cache usage at organization level or at enterprise level. + + The external blob storage that is configured within your enterprise account will now be shared across workflow artifacts, logs, and also the caches. For more information, see "[Caching dependencies to speed up workflows](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)." + - + heading: Automatically sign commits made in the web UI + notes: + - | + You can now configure GitHub Enterprise Server to automatically sign commits made in the web interface, such as from editing a file or merging a pull request. Signed commits increase confidence that changes come from trusted sources. This feature allows the [Require signed commits](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-signed-commits) branch protection setting to block unsigned commits from entering a repository, while allowing entry of signed commits – even those made in the web interface. For more information, see "[Configuring web commit signing](/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing)." + - + heading: Sync license usage any time + notes: + - | + For customers that sync license usage between GitHub Enterprise Server and GitHub Enterprise Cloud automatically using GitHub Connect, you now have the ability to sync your license usage independently of the automatic weekly sync. This feature also reports the status of sync job. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud#manually-syncing-license-usage)." + - + heading: Reusable workflows for GitHub Actions are generally available + notes: + - | + Reusable workflows are now generally available. Reusable workflows help you reduce duplication by enabling you to reuse an entire workflow as if it were an action. With the general availability release, a number of improvements are now available for GitHub Enterprise Server. For more information, see "[Reusing workflows](/actions/using-workflows/reusing-workflows)." + + - You can utilize outputs to pass data from reusable workflows to other jobs in the caller workflow. + - You can pass environment secrets to reusable workflows. + - The audit log includes information about which reusable workflows are used. + - Reusable workflows in the same repository as the calling repository can be referenced with just the path and filename (`PATH/FILENAME`). The called workflow will be from the same commit as the caller workflow. + - Reusable workflows are subject to your organization's actions access policy. Previously, even if your organization had configured the "Allow select actions" policy, you were still able to use a reusable workflow from any location. Now if you use a reusable workflow that falls outside of that policy, your run will fail. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-to-restrict-the-use-of-actions-in-your-enterprise)." + - + heading: Self-hosted runners for GitHub Actions can now disable automatic updates + notes: + - | + You now have more control over when your self-hosted runners perform software updates. If you specify the `--disableupdate` flag to the runner then it will not try to perform an automatic software update if a newer version of the runner is available. This allows you to update the self-hosted runner on your own schedule, and is especially convenient if your self-hosted runner is in a container. + + For compatibility with the GitHub Actions service, you will need to manually update your runner within 30 days of a new runner version being available. For instructions on how to install the latest runner version, please see the installation instructions for [the latest release in the runner repo](https://github.com/actions/runner/releases). + - + heading: Secure self-hosted runners for GitHub Actions by limiting workflows + notes: + - | + Organization owners can now increase the security of CI/CD workflows on self-hosted runners by choosing which workflows can access a runner group. Previously, any workflow in a repository, such as an issue labeler, could access the self-hosted runners available to an organization. For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-what-workflows-can-access-a-runner-group)" and the [GitHub Blog](https://github.blog/2022-03-23-github-actions-secure-self-hosted-runners-specific-workflows/). + - + heading: Prevent GitHub Actions from approving pull requests + notes: + - | + You can now control whether GitHub Actions can approve pull requests. This feature protects against a user using GitHub Actions to satisfy the "Required approvals" branch protection requirement and merging a change that was not reviewed by another user. To prevent breaking existing workflows, **Allow GitHub Actions reviews to count towards required approval** is enabled by default. Organization owners can disable the feature in the organization's GitHub Actions settings. For more information, see "[Disabling or limiting GitHub Actions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#preventing-github-actions-from-approving-pull-requests)." + - + heading: Re-run failed or individual GitHub Actions jobs + notes: + - | + You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more information, see "[Re-running workflows and jobs](/managing-workflow-runs/re-running-workflows-and-jobs)." + - + heading: Dependency graph supports GitHub Actions + notes: + - | + The dependency graph now detects YAML files for GitHub Actions workflows. GitHub Enterprise Server will display the workflow files within the **Insights** tab's dependency graph section. Repositories that publish actions will also be able to see the number of repositories that depend on that action from the "Used By" control on the repository homepage. For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." + - + heading: Security overview for enterprises in public beta + notes: + - | + GitHub Advanced Security customers can now view an overview of security alerts at the enterprise level. The new **Security** tab at the enterprise level provides a repository-centric view of application security risks, as well as an alert-centric view of all secret scanning alerts. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + - + heading: Security view for organizations is generally available + notes: + - | + The overview of security alerts at the organization level is now generally available. GitHub Advanced Security customers can use the security overview to view a repository-centric view of application security risks, or an alert-centric view of all code scanning, Dependabot, and secret scanning alerts for all repositories in an organization. For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + - + heading: Code scanning detects more security issues, supports new language versions + notes: + - | + Code scanning now detects a larger number of CWEs, and CodeQL code scanning fully supports the standard language features in the following language releases. + + - C# 10 / .NET 6 + - Python 3.10 + - Java 17 + - TypeScript 4.5 + + For more information, see the [GitHub Blog](https://github.blog/changelog/2022-02-25-code-scanning-detects-more-security-issues-supports-new-language-versions/). + - + heading: View code scanning alerts across an organization + notes: + - | + GitHub Advanced Security customers can now view code scanning alerts in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + - | + Users can now retrieve code scanning alerts for an organization on your GitHub Enterprise Server instance via the REST API. This new API endpoint supplements the existing [endpoint for repositories](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository). For more information, see [Code Scanning](/rest/code-scanning) in the REST API documentation. + - + heading: Secret scanning available as a push protection + notes: + - | + GitHub Enterprise Server can now block any pushes where a token is detected with high confidence. Developers can bypass the block by providing details of why the secret needs to be committed via a web UI. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." + - + heading: Dry runs for custom patterns with secret scanning + notes: + - | + GitHub Advanced Security customers can now dry run custom secret scanning patterns at the organization or repository level. Dry runs allow people with owner or admin access to review and hone their patterns before publishing them and generating alerts. You can compose a pattern, then use **Save and dry run** to retrieve results. The scans typically take just a few seconds, but GitHub Enterprise Server will also notify organization owners or repository admins via email when dry run results are ready. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)" and "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." + - + heading: Secret scanning custom pattern events now in the audit log + notes: + - | + The audit log now includes events associated with secret scanning custom patterns. This data helps GitHub Advanced Security customers understand actions taken on their [repository](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#repository_secret_scanning_custom_pattern-category-actions)-, [organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization#org_secret_scanning_custom_pattern-category-actions)-, or [enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#business_secret_scanning_custom_pattern-category-actions)-level custom patterns for security and compliance audits. For more information, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)" or "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)." + - + heading: Configure permissions for secret scanning with custom repository roles + notes: + - | + You can now configure two new permissions for secret scanning when managing custom repository roles. + + - View secret scanning results + - Dismiss or reopen secret scanning results + + For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + - + heading: Secret scanning now supports archived repositories + notes: + - | + GitHub Advanced Security customers can now enable secret scanning for archived repositories via the UI and API. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-private-repositories)," "[About archived repositories](/repositories/archiving-a-github-repository/archiving-repositories)," and "[Repositories](/rest/repos/repos#update-a-repository)" in the REST API documentation. + - + heading: Secret scanning webhooks for alert locations + notes: + - | + GitHub Advanced Security customers using secret scanning can now opt to receive a webhook each time a secret is detected in a new location. The `secret_scanning_alert_location` webhook event includes location details, like the commit SHA, and the associated alert for the detection. A location is created for every new file path containing the detected secret. For more information, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#secret_scanning_alert_location)." + - + heading: View Dependabot alerts across an organization + notes: + - | + GitHub Advanced Security customers can now view Dependabot alerts in in an organization's **Security** tab. This view is available to organization owners and members of teams with the [security manager role](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization). For more information, see "[About the security overview](/code-security/security-overview/about-the-security-overview)." + - + heading: Configure permissions for Dependabot alerts with custom repository roles + notes: + - | + You can now configure two new permissions for Dependabot alerts when managing custom repository roles. + + - View Dependabot alerts + - Dismiss or reopen Dependabot alerts + + For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + - + heading: Reopen dismissed Dependabot alerts + notes: + - | + You can now reopen dismissed Dependabot alerts through the UI page for a closed alert. This does not affect Dependabot pull requests or the GraphQL API. For more information, see "[About Dependabot alerts](/code-security/dependabot/dependabot-alerts/about-dependabot-alerts)." + - + heading: Pub support for Dependabot version updates is in public beta + notes: + - | + Users of Dependabot version updates can now proactively update dependencies for Flutter or Dart projects that use the Pub package manager. + + To test [version updates](/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates) on your own Dart or Flutter repository, add the following configuration file in [.github/dependabot.yaml](/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates#enabling-dependabot-version-updates). Note the `package-ecosystem: "pub"` and `enable-beta-ecosystems: true` flags. + ```yaml + version: 2 + enable-beta-ecosystems: true + updates: + - package-ecosystem: "pub" + directory: "/" + schedule: + interval: "weekly" + ``` + - + heading: See pull request associated with a repository's Dependabot alerts via GraphQL API + notes: + - | + The new `DependabotUpdate` GraphQL object lets you view information about what happens to your repository's security updates. When GitHub Enterprise Server detects that a dependency in your repository is vulnerable, Dependabot will attempt to open a pull request to update that dependency to a non-vulnerable version. You can now see the pull request that fixes the vulnerability. In some cases, Dependabot fails to open a pull request. Previously, the error message that Dependabot generated was only visible in the "Dependabot Alerts" section of the **Security** tab. Now, if Dependabot runs into an error when trying to open a pull request for a security alert, you can determine the reason using the GraphQL API. For more information, see "[Objects](/graphql/reference/objects#dependabotupdate)" in the GraphQL API documentation. + - + heading: Access more information about Dependabot alerts via GraphQL API + notes: + - | + You can now view fixed alerts from Dependabot with the GraphQL API. You can also access and filter by state, as well as by unique numeric identifier, and you can filter by state on the vulnerability alert object. The following fields now exist for a `RepositoryVulnerabilityAlert`. + + - `number` + - `fixed_at` + - `fix_reason` + - `state` + + For more information, see "[Objects](/graphql/reference/objects#repositoryvulnerabilityalert)" in the GraphQL API documentation. + - + heading: Git events in the enterprise audit log + notes: + - | + The following Git-related events can now appear in the enterprise audit log. If you enable the feature and set an audit log retention period, the new events will be available for search via the UI and API, or export via JSON or CSV. + + - `git.clone` + - `git.fetch` + - `git.push` + + Due to the large number of Git events logged, we recommend you monitor your instance's file storage and review your related alert configurations. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)" and "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)." + - + heading: Improvements to CODEOWNERS + notes: + - | + This release includes improvements to CODEOWNERS. + + - Syntax errors are now surfaced when viewing a CODEOWNERS file from the web. Previously, when a line in a CODEOWNERS file had a syntax error, the error would be ignored or in some cases cause the entire CODEOWNERS file to not load. GitHub Apps and Actions can access the same list of errors using new REST and GraphQL APIs. For more information, see "[Repositories](/rest/repos/repos#list-codeowners-errors)" in the REST API documentation or "[Objects](/graphql/reference/objects#repositorycodeowners)" in the GraphQL API documentation. + - After someone creates a new pull request or pushes new changes to a draft pull request, any code owners that will be requested for review are now listed in the pull request under "Reviewers". This feature gives you an early look at who will be requested to review once the pull request is marked ready for review. + - Comments in CODEOWNERS files can now appear at the end of a line, not just on dedicated lines. + + For more information, see "[About code owners](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)." + - + heading: More ways to keep a pull request's topic branch up to date + notes: + - | + The **Update branch** button on the pull request page lets you update your pull request's branch with the latest changes from the base branch. This is useful for verifying your changes are compatible with the current version of the base branch before you merge. Two enhancements now give you more ways to keep your branch up-to-date. + + - When your pull request's topic branch is out of date with the base branch, you now have the option to update it by rebasing on the latest version of the base branch. Rebasing applies the changes from your branch onto the latest version of the base branch, resulting in a branch with a linear history since no merge commit is created. To update by rebasing, click the drop down menu next to the **Update Branch** button, click **Update with rebase**, and then click **Rebase branch**. Previously, **Update branch** performed a traditional merge that always resulted in a merge commit in your pull request branch. This option is still available, but now you have the choice. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)." + + - A new repository setting allows the **Update branch** button to always be available when a pull request's topic branch is not up to date with the base branch. Previously, this button was only available when the **Require branches to be up to date before merging** branch protection setting was enabled. People with admin or maintainer access can manage the **Always suggest updating pull request branches** setting from the **Pull Requests** section in repository settings. For more information, see "[Managing suggestions to update pull request branches](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches)." + - + heading: Configure custom HTTP headers for GitHub Pages sites + notes: + - | + You can now configure custom HTTP headers that apply to all GitHub Pages sites served from your GitHub Enterprise Server instance. For more information, see "[Configuring GitHub Pages for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise#configuring-github-pages-response-headers-for-your-enterprise)." + - + heading: Ignore commits in blame view + notes: + - | + It's now possible to ignore revisions in the blame view by creating a _.git-blame-ignore-revs_ file in the root of your repository. For more information, see "[Viewing a file](/repositories/working-with-files/using-files/viewing-a-file#ignore-commits-in-the-blame-view)." + - + heading: Light high contrast theme is generally available + notes: + - | + A light high contrast theme, with greater contrast between foreground and background elements, is now generally available. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings)." + - + heading: Tag protection rules + notes: + - | + Repository owners can now configure tag protection rules to protect a repository's tags. Once protected by a tag protection rule, tags matching a specified name pattern can only be created and deleted by users with the Maintain or Admin role in the repository. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." + bugs: + - | + It is now possible for GitHub Apps to upload release assets. + changes: + - | + To use the device authorization flow for OAuth and GitHub Apps, you must manually enable the feature. This change reduces the likelihood of apps being used in phishing attacks against GitHub Enterprise Server users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication. If you own or manage an OAuth App or GitHub App and you want to use the device flow, you can enable it for your app via the app's settings page. The device flow API endpoints will respond with status code `400` to apps that have not enabled this feature. For more information, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." + - | + The code scanning alert page now always shows the alert status and information for the default branch. There is a new "Affected branches" panel in the sidebar where you can see the status of the alert in other branches. If the alert does not exist in your default branch, the alert page will show the status as "In branch" or "In pull request" for the location where the alert was last seen. This improvement makes it easier to understand the status of alerts which have been introduced into your code base. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-alert-details)." + + The alert list page is not changed and can be filtered by `branch`. You can use the code scanning API to retrieve more detailed branch information for alerts. For more information, see "[Code Scanning](/rest/code-scanning)" in the REST API documentation. + - | + Code scanning now shows the details of the analysis origin of an alert. If an alert has more than one analysis origin, it is shown in the "Affected branches" sidebar and in the alert timeline. You can hover over the analysis origin icon in the "Affected branches" sidebar to see the alert status in each analysis origin. If an alert only has a single analysis origin, no information about analysis origins is displayed on the alert page. These improvements will make it easier to understand your alerts. In particular, it will help you understand those that have multiple analysis origins. This is especially useful for setups with multiple analysis configurations, such as monorepos. For more information, see "[About code scanning alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)." + - | + Lists of repositories owned by a user or organization now have an additional filter option, "Templates", making it easier to find template repositories. + - | + GitHub Enterprise Server can display several common image formats, including PNG, JPG, GIF, PSD, and SVG, and provides several ways to compare differences between versions. Now when reviewing added or changed images in a pull request, previews of those images are shown by default. Previously, you would see a message indicating that binary files could not be shown and you would need to toggle the "Display rich diff" option. For more information, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files)." + - | + New gists are now created with a default branch name of either `main` or the alternative default branch name defined in your user settings. This matches how other repositories are created on GitHub Enterprise Server. For more information, see "[About branches](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch)" and "[Managing the default branch name for your repositories](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories)." + - | + Gists now only show the 30 most recent comments when first displayed. You can click **Load earlier comments...** to view more. This allows gists that have many comments to appear more quickly. For more information, see "[Editing and sharing content with gists](/get-started/writing-on-github/editing-and-sharing-content-with-gists)." + - | + Settings pages for users, organizations, repositories, and teams have been redesigned, grouping similar settings pages into sections for improved information architecture and discoverability. For more information, see the [GitHub changelog](https://github.blog/changelog/2022-02-02-redesign-of-githubs-settings-pages/). + - | + Focusing or hovering over a label now displays the label description in a tooltip. + - | + Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)." + deprecations: + - + heading: Change to the format of authentication tokens + notes: + - | + GitHub Connect will no longer work after June 3rd for instances running GitHub Enterprise Server 3.1 or older, due to the format of GitHub authentication tokens changing. For more information, see the [GitHub changelog](https://github.blog/changelog/2021-03-31-authentication-token-format-updates-are-generally-available/). + - + heading: CodeQL runner deprecated in favor of CodeQL CLI + notes: + - | + The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." + known_issues: + - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user. + - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 + - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 + - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 + - GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。 + - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' + - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 + - Actions services need to be restarted after restoring an appliance from a backup taken on a different host. diff --git a/translations/ja-JP/data/reusables/actions/cache-default-size.md b/translations/ja-JP/data/reusables/actions/cache-default-size.md new file mode 100644 index 0000000000..c52c4250b9 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/cache-default-size.md @@ -0,0 +1 @@ +By default, the total cache storage that {% data variables.product.prodname_actions %} uses on the external storage for {% data variables.product.product_location %} is limited to a maximum of 10 GB per repository, and the maximum allowed size that can be set for a repository is 25 GB. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/cache-eviction-process.md b/translations/ja-JP/data/reusables/actions/cache-eviction-process.md new file mode 100644 index 0000000000..bd69ed40ab --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/cache-eviction-process.md @@ -0,0 +1 @@ +If you exceed the limit, {% data variables.product.prodname_dotcom %} will save the new cache but will begin evicting caches until the total size is less than the repository limit. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/cache-no-org-policy.md b/translations/ja-JP/data/reusables/actions/cache-no-org-policy.md new file mode 100644 index 0000000000..b1d6e18823 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/cache-no-org-policy.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Unlike other {% data variables.product.prodname_actions %} policy settings, there is no organization-level policy for setting the {% data variables.product.prodname_actions %} cache size. The enterprise policy is applied directly to repositories. + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/actions/caching-availability.md b/translations/ja-JP/data/reusables/actions/caching-availability.md new file mode 100644 index 0000000000..c7cfc4767f --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/caching-availability.md @@ -0,0 +1 @@ +{% data variables.product.prodname_actions %} caching is only available for repositories hosted on {% data variables.product.prodname_dotcom_the_website %} or {% data variables.product.prodname_ghe_server %} 3.5 and later. 詳しい情報については、「ワークフローを高速化するための依存関係のキャッシュ」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/comparing-artifacts-caching.md b/translations/ja-JP/data/reusables/actions/comparing-artifacts-caching.md new file mode 100644 index 0000000000..283d4d294d --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/comparing-artifacts-caching.md @@ -0,0 +1,6 @@ +## 成果物の比較と依存関係のキャッシング + +成果物とキャッシングは、{% data variables.product.prodname_dotcom %}にファイルを保存できるようにするので似ていますが、それぞれの機能のユースケースは異なっており、入れ替えて使うことはできません。 + +- Use caching when you want to reuse files that don't change often between jobs or workflow runs, such as build dependencies from a package management system. +- Use artifacts when you want to save files produced by a job to view after a workflow run has ended, such as built binaries or build logs. diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md b/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md index b146f66df1..0f5629b3f8 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md +++ b/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-needs.md @@ -31,4 +31,4 @@ jobs: needs: [job1, job2] ``` -この例では、`job3`は条件式の`always()` を使っているので、`job1`と`job2`が成功したかどうかにかかわらず、それらのジョブが完了したら常に実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#job-status-check-functions)." +この例では、`job3`は条件式の`always()` を使っているので、`job1`と`job2`が成功したかどうかにかかわらず、それらのジョブが完了したら常に実行されます。 For more information, see "[Expressions](/actions/learn-github-actions/expressions#status-check-functions)." diff --git a/translations/ja-JP/data/reusables/actions/minio-gateways-removal.md b/translations/ja-JP/data/reusables/actions/minio-gateways-removal.md new file mode 100644 index 0000000000..8094f97fd4 --- /dev/null +++ b/translations/ja-JP/data/reusables/actions/minio-gateways-removal.md @@ -0,0 +1,5 @@ +{% warning %} + +**Warning**: MinIO has announced removal of MinIO Gateways. Starting June 1st, 2022, support and bug fixes for the current MinIO NAS Gateway implementation will only be available for paid customers via their LTS support contract. If you want to continue using MinIO Gateways with {% data variables.product.prodname_actions %}, we recommend moving to MinIO LTS support. For more information, see [Scheduled removal of MinIO Gateway for GCS, Azure, HDFS](https://github.com/minio/minio/issues/14331) in the minio/minio repository. + +{% endwarning %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/actions/release-trigger-workflow.md b/translations/ja-JP/data/reusables/actions/release-trigger-workflow.md index 50cc14ca92..19319aa656 100644 --- a/translations/ja-JP/data/reusables/actions/release-trigger-workflow.md +++ b/translations/ja-JP/data/reusables/actions/release-trigger-workflow.md @@ -1 +1 @@ -{% data variables.product.prodname_dotcom %}上で新しいリリースを作成するたびに、イメージを公開するワークフローを起動できます。 以下の例のワークフローは、`created`というアクティビティの種類を持つ`release`イベントが生じた時に実行されます。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。 +{% data variables.product.product_name %}上で新しいリリースを作成するたびに、イメージを公開するワークフローを起動できます。 以下の例のワークフローは、`created`というアクティビティの種類を持つ`release`イベントが生じた時に実行されます。 `release`イベントに関する詳しい情報については「[ワークフローを起動するイベント](/actions/reference/events-that-trigger-workflows#release)」を参照してください。 diff --git a/translations/ja-JP/data/reusables/actions/supported-github-runners.md b/translations/ja-JP/data/reusables/actions/supported-github-runners.md index 57616a96a6..98a0dd538d 100644 --- a/translations/ja-JP/data/reusables/actions/supported-github-runners.md +++ b/translations/ja-JP/data/reusables/actions/supported-github-runners.md @@ -30,13 +30,22 @@ Windows Server 2019 +Ubuntu 22.04 + + +ubuntu-22.04 + + +Ubuntu 22.04 is currently in public beta. + + + + Ubuntu 20.04 ubuntu-latestまたはubuntu-20.04 - - diff --git a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md index 41a37a59e8..5cdc3ccfdb 100644 --- a/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md +++ b/translations/ja-JP/data/reusables/audit_log/audit-log-action-categories.md @@ -125,7 +125,7 @@ {%- ifversion ghec or ghes > 3.1 %} | `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise. {%- endif %} -{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %} +{%- if custom-repository-roles %} | `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization). {%- endif %} {%- ifversion ghec or ghes or ghae %} diff --git a/translations/ja-JP/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md b/translations/ja-JP/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md index 71035319c3..e9d79a4e39 100644 --- a/translations/ja-JP/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md +++ b/translations/ja-JP/data/reusables/dependabot/ghes-ghae-enabling-dependency-graph.md @@ -1 +1 @@ -If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph. For more information, see "[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)." \ No newline at end of file +If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph. 詳しい情報については「[Enterpriseでの依存関係グラフの有効化](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)」を参照してください。 \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md b/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md index 57ca31b009..f50a5571c8 100644 --- a/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md +++ b/translations/ja-JP/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md @@ -1 +1 @@ -If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} usage beyond the amounts included with your account. +If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for any {% data variables.product.prodname_codespaces %} usage, and for {% data variables.product.prodname_actions %} or {% data variables.product.prodname_registry %} usage beyond the amounts included with your account. diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md new file mode 100644 index 0000000000..915aa29d22 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/add-key-to-web-flow-user.md @@ -0,0 +1,14 @@ +1. Run the following command, replacing KEY-ID with your PGP key ID. + + ```bash{:copy} + gpg --armor --export KEY-ID + ``` +1. Copy your PGP key, beginning with `-----BEGIN PGP PUBLIC KEY BLOCK-----` and ending with `-----END PGP PUBLIC KEY BLOCK-----`. +1. Sign into {% data variables.product.prodname_ghe_server %} as the `web-flow` user. +1. Add the public PGP key to the user's profile. For more information, see "[Adding a new GPG key to your {% data variables.product.prodname_dotcom %} account](/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account)." + + {% note %} + + **Note:** Do not remove other public keys from the list of GPG keys. If a public key is deleted, any commits signed with the corresponding private key will no longer be marked as verified. + + {% endnote %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md new file mode 100644 index 0000000000..9d86ff5622 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/create-pgp-key-web-commit-signing.md @@ -0,0 +1,8 @@ +1. In the administrative shell, create a PGP key. Make note of the email address and key ID. + + ```bash{:copy} + gpg --full-generate-key --pinentry-mode=loopback + ``` + + - Use the default key type and at least `4096` bits with no expiry. + - Use `web-flow` as the username. \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/email-settings.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/email-settings.md new file mode 100644 index 0000000000..45b60ef7b1 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/email-settings.md @@ -0,0 +1,4 @@ +{% data reusables.enterprise_site_admin_settings.access-settings %} +{% data reusables.enterprise_site_admin_settings.management-console %} +2. ページの上部で**Settings（設定）**をクリックしてください。 ![設定タブ](/assets/images/enterprise/management-console/settings-tab.png) +3. 左のサイドバーで **Email（メール）**をクリックしてください。 ![メールタブ](/assets/images/enterprise/management-console/email-sidebar.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md new file mode 100644 index 0000000000..435eea88fe --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-env-variable.md @@ -0,0 +1,5 @@ +1. Define the key as a environment variable for {% data variables.product.product_name %}, replacing `` with the GPG key ID. + + ```bash{:copy} + ghe-config "secrets.gpgverify.web-signing-key" "$(gpg --export-secret-keys -a | awk '{printf "%s\\n", $0}')" + ``` \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md new file mode 100644 index 0000000000..d36ffce0fe --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/pgp-key-no-passphrase.md @@ -0,0 +1 @@ + - The PGP key **cannot** be protected by a passphrase. diff --git a/translations/ja-JP/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md new file mode 100644 index 0000000000..74d0666247 --- /dev/null +++ b/translations/ja-JP/data/reusables/enterprise_site_admin_settings/update-commit-signing-service.md @@ -0,0 +1,7 @@ +1. Update the settings for {% data variables.product.product_name %}'s commit signing service. + + ```bash{:copy} + sudo consul-template -once -template /etc/consul-templates/etc/nomad-jobs/gpgverify/gpgverify.hcl.ctmpl:/etc/nomad-jobs/gpgverify/gpgverify.hcl + + nomad job run /etc/nomad-jobs/gpgverify/gpgverify.hcl + ``` \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/gated-features/packages.md b/translations/ja-JP/data/reusables/gated-features/packages.md index 746eb94928..ae91fb6596 100644 --- a/translations/ja-JP/data/reusables/gated-features/packages.md +++ b/translations/ja-JP/data/reusables/gated-features/packages.md @@ -1,5 +1,7 @@ +{% ifversion fpt or ghec or ghes < 3.5 %} {% data variables.product.prodname_registry %} is available with {% data variables.product.prodname_free_user %}, {% data variables.product.prodname_pro %}, {% data variables.product.prodname_free_team %} for organizations, {% data variables.product.prodname_team %}, {% data variables.product.prodname_ghe_cloud %}, {% data variables.product.prodname_ghe_server %} 3.0 or higher, and {% data variables.product.prodname_ghe_managed %}.{% ifversion ghes %} For more information about upgrading your {% data variables.product.prodname_ghe_server %} instance, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)" and refer to the [{% data variables.enterprise.upgrade_assistant %}](https://support.github.com/enterprise/server-upgrade) to find the upgrade path from your current release version.{% endif %} {% ifversion fpt or ghec %}
-{% data variables.product.prodname_registry %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 また、レガシーのリポジトリごとのプランを使っているアカウントは、リポジトリごとに課金されるため、{% data variables.product.prodname_container_registry %}にはアクセスできません。 {% data reusables.gated-features.more-info %} +{% data variables.product.prodname_registry %}は、レガシーのリポジトリごとのプランを使っているアカウントが所有しているプライベートリポジトリでは利用できません。 Also, accounts using legacy per-repository plans cannot access the {% data variables.product.prodname_container_registry %} since these accounts are billed by repository. {% data reusables.gated-features.more-info %} +{% endif %} {% endif %} diff --git a/translations/ja-JP/data/reusables/gated-features/security-center.md b/translations/ja-JP/data/reusables/gated-features/security-center.md index b4ae95174b..e4eac0aad5 100644 --- a/translations/ja-JP/data/reusables/gated-features/security-center.md +++ b/translations/ja-JP/data/reusables/gated-features/security-center.md @@ -3,4 +3,4 @@ {% elsif ghec or ghes %} The security overview for your organization is available if you have a license for {% data variables.product.prodname_GH_advanced_security %}. {% data reusables.advanced-security.more-info-ghas %} {% elsif fpt %} -The security overview is available for organizations that use {% data variables.product.prodname_enterprise %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} \ No newline at end of file +The security overview is available for organizations that use {% data variables.product.prodname_enterprise %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. 詳しい情報については「[{% data variables.product.prodname_GH_advanced_security %}について](/get-started/learning-about-github/about-github-advanced-security)」を参照してください。 {% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md index 7981f11f4a..cdd67653b4 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate-to-container-registry-steps.md @@ -1,7 +1,7 @@ 1. 実行したいタスクに対して適切なスコープを持つ新しい個人アクセストークン（PAT）を作成してください。 OrganizationがSSOを必須としている場合は、新しいトークンでSSOを有効化しなければなりません。 {% warning %} - **ノート:** デフォルトでは、ユーザインターフェース内で個人アクセストークン（PAT）に対して`write:packages`スコープを選択すると、`repo`スコープも選択されます。 `repo`は不要に広いアクセス権を提供するので、特にGitHub Actionsのワークフローでの利用は避けることをおすすめします。 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)」を参照してください。 回避策として、以下のURLでユーザインターフェース内でPATに`write:packages`スコープだけを選択することができます。 `https://github.com/settings/tokens/new?scopes=write:packages` + **ノート:** デフォルトでは、ユーザインターフェース内で個人アクセストークン（PAT）に対して`write:packages`スコープを選択すると、`repo`スコープも選択されます。 `repo`は不要に広いアクセス権を提供するので、特にGitHub Actionsのワークフローでの利用は避けることをおすすめします。 詳しい情報については「[GitHub Actionsのためのセキュリティ強化](/actions/getting-started-with-github-actions/security-hardening-for-github-actions#considering-cross-repository-access)」を参照してください。 As a workaround, you can select just the `write:packages` scope for your PAT in the user interface with this url: `https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/settings/tokens/new?scopes=write:packages`. {% endwarning %} @@ -16,10 +16,10 @@ $ export CR_PAT=YOUR_TOKEN ``` 3. コンテナタイプにあったCLIを利用して、 -`ghcr.io`にある{% data variables.product.prodname_container_registry %}サービスにサインインしてください。 +{% data variables.product.prodname_container_registry %} service at `{% data reusables.package_registry.container-registry-hostname %}`. {% raw %} ```shell - $ echo $CR_PAT | docker login ghcr.io -u USERNAME --password-stdin + $ echo $CR_PAT | docker login {% endraw %}{% data reusables.package_registry.container-registry-hostname %}{% raw %} -u USERNAME --password-stdin > Login Succeeded ``` {% endraw %} diff --git a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md index 978ed2bc80..a54f9a0844 100644 --- a/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md +++ b/translations/ja-JP/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md @@ -1,8 +1,8 @@ -{% ifversion fpt or ghec %} +{% ifversion fpt or ghec or ghes > 3.4 %} -To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. If your workflow is using a personal access token (PAT) to authenticate to `ghcr.io`, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. +To authenticate to the {% data variables.product.prodname_container_registry %} within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. If your workflow is using a personal access token (PAT) to authenticate to `{% data reusables.package_registry.container-registry-hostname %}`, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`. -For guidance on updating your workflows that authenticate to `ghcr.io` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)." +{% ifversion fpt or ghec %}For guidance on updating your workflows that authenticate to `{% data reusables.package_registry.container-registry-hostname %}` with a personal access token, see "[Upgrading a workflow that accesses `ghcr.io`](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions#upgrading-a-workflow-that-accesses-ghcrio)."{% endif %} For more information about the `GITHUB_TOKEN`, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)." diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-example-hostname.md b/translations/ja-JP/data/reusables/package_registry/container-registry-example-hostname.md new file mode 100644 index 0000000000..b892c80e97 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-example-hostname.md @@ -0,0 +1 @@ +containers.github.companyname.com \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-beta.md b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-beta.md new file mode 100644 index 0000000000..c4942faf78 --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-ghes-beta.md @@ -0,0 +1,11 @@ +{% ifversion ghes > 3.4 %} + +{% note %} + +**ノート**: {% data variables.product.prodname_container_registry %}は{% data variables.product.product_name %} に対して現在ベータであり、変更されることがあります。 + +Both {% data variables.product.prodname_registry %} and subdomain isolation must be enabled to use {% data variables.product.prodname_container_registry %}. For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)." + +{% endnote %} + +{% endif %} diff --git a/translations/ja-JP/data/reusables/package_registry/container-registry-hostname.md b/translations/ja-JP/data/reusables/package_registry/container-registry-hostname.md new file mode 100644 index 0000000000..0d374afd0b --- /dev/null +++ b/translations/ja-JP/data/reusables/package_registry/container-registry-hostname.md @@ -0,0 +1 @@ +{% ifversion fpt or ghec %}ghcr.io{% elsif ghes > 3.4 %}containers.HOSTNAME{% else %}{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/package_registry/publish-docker-image.md b/translations/ja-JP/data/reusables/package_registry/publish-docker-image.md index 96fb2620a9..be03c6a689 100644 --- a/translations/ja-JP/data/reusables/package_registry/publish-docker-image.md +++ b/translations/ja-JP/data/reusables/package_registry/publish-docker-image.md @@ -8,12 +8,12 @@ on: branches: ['release'] env: - REGISTRY: ghcr.io + REGISTRY: {% data reusables.package_registry.container-registry-hostname %} IMAGE_NAME: {% raw %}${{ github.repository }}{% endraw %} jobs: build-and-push-image: - runs-on: ubuntu-latest + runs-on: {% ifversion ghes %}[self-hosted]{% else %}ubuntu-latest{% endif %} permissions: contents: read packages: write diff --git a/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md b/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md index 707735aa9c..2e0980c99e 100644 --- a/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md +++ b/translations/ja-JP/data/reusables/package_registry/visibility-and-access-permissions.md @@ -1,13 +1,11 @@ -{% ifversion fpt or ghec %} コンテナイメージへの管理権限を持っているなら、そのコンテナイメージへのアクセス権限をプライベートもしくはパブリックに設定できます。 パブリックイメージは匿名でアクセスでき、認証や CLI 経由でサインインすることなくプルできます。 あなたが管理者であれば、Organization レベルおよびリポジトリレベルに設定した権限とは別に、コンテナイメージに対してアクセス権限を付与することもできます。 For container images published and owned by a personal account, you can give any person an access role. Organization が所有し公開しているコンテナイメージには、Organization 内の任意の Team にアクセスロールを付与できます。 -| 権限 | アクセス権の内容 | -| ---- | ---------------------------------------------------------------------------------------------------- | -| 読み取り | パッケージをダウンロードできます。
メタデータの読み取りができます。 | -| 書き込み | このパッケージをアップロードおよびダウンロードできます。
パッケージのメタデータの読み取りおよび書き込みができます。 | -| 管理 | このパッケージのアップロード、ダウンロード、削除、管理ができます。
パッケージのメタデータの読み取りおよび書き込みができます。
パッケージに権限を付与できます。 | -{% endif %} +| 権限 | アクセス権の内容 | +| ----- | ---------------------------------------------------------------------------------------------------- | +| Read | パッケージをダウンロードできます。
メタデータの読み取りができます。 | +| Write | このパッケージをアップロードおよびダウンロードできます。
パッケージのメタデータの読み取りおよび書き込みができます。 | +| Admin | このパッケージのアップロード、ダウンロード、削除、管理ができます。
パッケージのメタデータの読み取りおよび書き込みができます。
パッケージに権限を付与できます。 | diff --git a/translations/ja-JP/data/reusables/pages/emu-org-only.md b/translations/ja-JP/data/reusables/pages/emu-org-only.md new file mode 100644 index 0000000000..31d7e90e85 --- /dev/null +++ b/translations/ja-JP/data/reusables/pages/emu-org-only.md @@ -0,0 +1,7 @@ +{% ifversion ghec %} +{% note %} + +**Note:** If you're a {% data variables.product.prodname_managed_user %}, you can only publish {% data variables.product.prodname_pages %} sites from repositories owned by organizations. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)」を参照してください。 + +{% endnote %} +{% endif %} \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/pre-release-program/custom-roles-public-beta.md b/translations/ja-JP/data/reusables/pre-release-program/custom-roles-public-beta.md deleted file mode 100644 index 7e414520d9..0000000000 --- a/translations/ja-JP/data/reusables/pre-release-program/custom-roles-public-beta.md +++ /dev/null @@ -1,7 +0,0 @@ -{% ifversion ghec %} -{% note %} - -**Note:** Custom repository roles are available as a public beta release and may change at any time during this period. - -{% endnote %} -{% endif %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md index a424589c40..fe024055e3 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md +++ b/translations/ja-JP/data/reusables/secret-scanning/partner-secret-list-private-repo.md @@ -1,4 +1,4 @@ -| Provider | サポートされているシークレット | APIスラッグ | +| Provider | サポートされているシークレット | Secret type | | ----------- | --------------- | ----------------- | | Adafruit IO | Adafruit IO Key | adafruit_io_key | {%- ifversion fpt or ghec or ghes > 3.1 or ghae %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md index bb5c1762bc..53fad59f40 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md +++ b/translations/ja-JP/data/reusables/secret-scanning/secret-list-private-push-protection.md @@ -1,4 +1,4 @@ -| Provider | サポートされているシークレット | APIスラッグ | +| Provider | サポートされているシークレット | Secret type | | ------------------------- | -------------------------------------------------- | -------------------------------------------------------- | | Adafruit IO | Adafruit IO Key | adafruit_io_key | | Alibaba Cloud | Alibaba Cloud Access Key ID | alibaba_cloud_access_key_id | diff --git a/translations/ja-JP/data/reusables/server-statistics/csv-download.md b/translations/ja-JP/data/reusables/server-statistics/csv-download.md new file mode 100644 index 0000000000..ca13a3f86d --- /dev/null +++ b/translations/ja-JP/data/reusables/server-statistics/csv-download.md @@ -0,0 +1 @@ +4. To start your download, under "{% data variables.product.prodname_github_connect %}", click **Export**, then choose whether you want to download a JSON or CSV file. ![Screenshot of export button under "Server Statistics" on the GitHub Connect page](/assets/images/help/server-statistics/export-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/server-statistics/release-phase.md b/translations/ja-JP/data/reusables/server-statistics/release-phase.md new file mode 100644 index 0000000000..17f100fd26 --- /dev/null +++ b/translations/ja-JP/data/reusables/server-statistics/release-phase.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** {% data variables.product.prodname_server_statistics %} is in public beta and subject to change. + +{% endnote %} diff --git a/translations/ja-JP/data/reusables/sponsors/country-of-residence.md b/translations/ja-JP/data/reusables/sponsors/country-of-residence.md deleted file mode 100644 index 6bf6614c1f..0000000000 --- a/translations/ja-JP/data/reusables/sponsors/country-of-residence.md +++ /dev/null @@ -1,2 +0,0 @@ -1. "Country or region of residence（在住している国または地域）"の下で、ドロップダウンメニューを使って居住地を選択してください。 ![在住している国または地域のドロップダウン](/assets/images/help/sponsors/country-of-residence-drop-down.png) -2. [**Save**] をクリックします。 diff --git a/translations/ja-JP/data/reusables/sponsors/tax-form-link.md b/translations/ja-JP/data/reusables/sponsors/tax-form-link.md index b35e8eab35..1e4df79f61 100644 --- a/translations/ja-JP/data/reusables/sponsors/tax-form-link.md +++ b/translations/ja-JP/data/reusables/sponsors/tax-form-link.md @@ -1,2 +1,2 @@ -1. **tax form（納税申告用紙）**をクリックしてください。 ![納税申告用紙に記入するためのリンク](/assets/images/help/sponsors/tax-form-link.png) +1. Click **tax forms**. ![納税申告用紙に記入するためのリンク](/assets/images/help/sponsors/tax-form-link.png) 2. 記入し、署名し、納税申告用紙をサブミットしてください。 diff --git a/translations/ja-JP/data/reusables/support/premium-support-features.md b/translations/ja-JP/data/reusables/support/premium-support-features.md index 43420bf87f..e6e5df5d71 100644 --- a/translations/ja-JP/data/reusables/support/premium-support-features.md +++ b/translations/ja-JP/data/reusables/support/premium-support-features.md @@ -4,4 +4,4 @@ In addition to all of the benefits of {% data variables.contact.enterprise_suppo - 初回応答時間が保証されるサービスレベルアグリーメント (SLA) - プレミアムコンテンツへのアクセス - Scheduled Health Checks - - Administration assistance hours + - Administration assistance hours ({% data variables.product.premium_plus_support_plan %} only) diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index a0a27118bc..79418696c2 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -158,6 +158,8 @@ prodname_copilot: 'GitHub Copilot' prodname_copilot_short: 'Copilot' #Command Palette prodname_command_palette: 'GitHub Command Palette' +#Server Statistics +prodname_server_statistics: 'Server Statistics' #Links product_url: >- {% ifversion fpt or ghec %}github.com{% else %}[hostname]{% endif %} diff --git a/translations/ja-JP/data/variables/release_candidate.yml b/translations/ja-JP/data/variables/release_candidate.yml index ec65ef6f94..f4379af822 100644 --- a/translations/ja-JP/data/variables/release_candidate.yml +++ b/translations/ja-JP/data/variables/release_candidate.yml @@ -1,2 +1,2 @@ --- -version: '' +version: enterprise-server@3.5 diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index e43ef3c0cd..1d5b30b2b6 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -25,7 +25,6 @@ translations/ja-JP/content/admin/configuration/configuring-network-settings/netw translations/ja-JP/content/admin/configuration/configuring-your-enterprise/accessing-the-management-console.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags -translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags @@ -35,9 +34,6 @@ translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-mach translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md,broken liquid tags translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/index.md,broken liquid tags translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,broken liquid tags -translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags -translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags -translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,broken liquid tags translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/index.md,broken liquid tags translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,broken liquid tags translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae.md,broken liquid tags @@ -190,6 +186,7 @@ translations/ja-JP/content/packages/learn-github-packages/publishing-a-package.m translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags translations/ja-JP/content/packages/quickstart.md,broken liquid tags translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags +translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags