New translation batch for ja (#31687)
This commit is contained in:
docubot
@@ -169,6 +169,8 @@ Sets an action's output parameter.
|
||||
|
||||
Optionally, you can also declare output parameters in an action's metadata file. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)."
|
||||
|
||||
You can escape multiline strings for setting an output parameter by creating an environment variable and using it in a workflow command. For more information, see "[Setting an environment variable](#setting-an-environment-variable)."
|
||||
|
||||
### Example: Setting an output parameter
|
||||
|
||||
{% bash %}
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: アプライアンスでのバックアップの設定
|
||||
title: Configuring backups on your appliance
|
||||
shortTitle: Configuring backups
|
||||
redirect_from:
|
||||
- /enterprise/admin/categories/backups-and-restores
|
||||
@@ -14,7 +14,7 @@ redirect_from:
|
||||
- /enterprise/admin/installation/configuring-backups-on-your-appliance
|
||||
- /enterprise/admin/configuration/configuring-backups-on-your-appliance
|
||||
- /admin/configuration/configuring-backups-on-your-appliance
|
||||
intro: 'ディザスター リカバリー計画の一部として、自動バックアップを構成して {% data variables.product.product_location %}の運用データを保護できます。'
|
||||
intro: 'As part of a disaster recovery plan, you can protect production data on {% data variables.product.product_location %} by configuring automated backups.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
@@ -23,162 +23,158 @@ topics:
|
||||
- Enterprise
|
||||
- Fundamentals
|
||||
- Infrastructure
|
||||
ms.openlocfilehash: 4403ec24aa3da63f6700ae4bfcd2392ec0cfd194
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147861653'
|
||||
---
|
||||
## {% data variables.product.prodname_enterprise_backup_utilities %}について
|
||||
## About {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} は、個別のホストにインストールするバックアップ システムで、{% data variables.product.product_location %} のバックアップ スナップショットをセキュアな SSH ネットワーク接続経由で定期的に取得します。 スナップショットを使用して、既存の {% data variables.product.prodname_ghe_server %} インスタンスをバックアップホストから以前の状態に復元できます。
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} is a backup system you install on a separate host, which takes backup snapshots of {% data variables.product.product_location %} at regular intervals over a secure SSH network connection. You can use a snapshot to restore an existing {% data variables.product.prodname_ghe_server %} instance to a previous state from the backup host.
|
||||
|
||||
ネットワーク経由で転送されるのは最後のスナップショット以降に追加されたデータのみで、追加の物理ストレージ領域もその分だけしか占めません。 パフォーマンスへの影響を最小化するために、バックアップは最低のCPU/IO優先度の下でオンライン実行されます。 バックアップを行うために、メンテナンスウィンドウをスケジューリングする必要はありません。
|
||||
Only data added since the last snapshot will transfer over the network and occupy additional physical storage space. To minimize performance impact, backups are performed online under the lowest CPU/IO priority. You do not need to schedule a maintenance window to perform a backup.
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} のメジャー リリースとバージョン番号は、{% data variables.product.product_name %} の機能リリースと一致します。 両方の製品の最新バージョン 4 つをサポートしています。 詳しい情報については、「[{% data variables.product.product_name %} のリリース](/admin/all-releases)」をご覧ください。
|
||||
Major releases and version numbers for {% data variables.product.prodname_enterprise_backup_utilities %} align with feature releases of {% data variables.product.product_name %}. We support the four most recent versions of both products. For more information, see "[{% data variables.product.product_name %} releases](/admin/all-releases)."
|
||||
|
||||
機能、要件、および高度な使用方法について詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) を参照してください。
|
||||
For more detailed information on features, requirements, and advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## 前提条件
|
||||
## Prerequisites
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} を利用するには、{% data variables.product.product_location %} とは別の Linux もしくは Unix ホスト システムが必要です。
|
||||
To use {% data variables.product.prodname_enterprise_backup_utilities %}, you must have a Linux or Unix host system separate from {% data variables.product.product_location %}.
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %}は、重要なデータのための長期的な恒久ストレージの既存環境に統合することもできます。
|
||||
You can also integrate {% data variables.product.prodname_enterprise_backup_utilities %} into an existing environment for long-term permanent storage of critical data.
|
||||
|
||||
バックアップ ホストと {% data variables.product.product_location %} は、地理的に離れたところに配置することをおすすめします。 そうすることで、プライマリのサイトにおける大規模な災害やネットワーク障害に際してもリカバリにバックアップが利用できることが保証されます。
|
||||
We recommend that the backup host and {% data variables.product.product_location %} be geographically distant from each other. This ensures that backups are available for recovery in the event of a major disaster or network outage at the primary site.
|
||||
|
||||
物理的なストレージの要求は、Gitリポジトリのディスク利用状況と予想される成長パターンによって異なります。
|
||||
Physical storage requirements will vary based on Git repository disk usage and expected growth patterns:
|
||||
|
||||
| ハードウェア | 推奨 |
|
||||
| Hardware | Recommendation |
|
||||
| -------- | --------- |
|
||||
| **vCPU 数** | 2 |
|
||||
| **[メモリ]** | 2 GB |
|
||||
| **Storage** | プライマリインスタンスに割り当てられたストレージの5倍 |
|
||||
| **vCPUs** | 2 |
|
||||
| **Memory** | 2 GB |
|
||||
| **Storage** | Five times the primary instance's allocated storage |
|
||||
|
||||
ユーザのアクティビティや他の製品との結合といった利用方法によっては、さらに多くのリソースが必要になることがあります。
|
||||
More resources may be required depending on your usage, such as user activity and selected integrations.
|
||||
|
||||
詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの「[{% data variables.product.prodname_enterprise_backup_utilities %} の要件](https://github.com/github/backup-utils/blob/master/docs/requirements.md)」を参照してください。
|
||||
For more information, see [{% data variables.product.prodname_enterprise_backup_utilities %} requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## {% data variables.product.prodname_enterprise_backup_utilities %}のインストール
|
||||
## Installing {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
バックアップ ホストに {% data variables.product.prodname_enterprise_backup_utilities %} をインストールするには、プロジェクトの Git リポジトリを複製することをお勧めします。 この方法では、Git を使用して新しいリリースを直接フェッチすることができ、新しいバージョンをインストールするときに既存のバックアップ構成ファイル `backup.config` が保持されます。
|
||||
To install {% data variables.product.prodname_enterprise_backup_utilities %} on your backup host, we recommend cloning the project's Git repository. This approach allows you to fetch new releases directly using Git, and your existing backup configuration file, `backup.config`, will be preserved when installing a new version.
|
||||
|
||||
または、ホスト マシンがインターネットにアクセスできない場合は、圧縮アーカイブとして各 {% data variables.product.prodname_enterprise_backup_utilities %} リリースをダウンロードし、コンテンツを抽出してインストールできます。 詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの「[概要](https://github.com/github/backup-utils/blob/master/docs/getting-started.md)」を参照してください。
|
||||
Alternatively, if the host machine can't access the internet, you can download each {% data variables.product.prodname_enterprise_backup_utilities %} release as a compressed archive, then extract and install the contents. For more information, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
バックアップ スナップショットは、`backup.config` ファイル内の`GHE_DATA_DIR` データ ディレクトリ変数によって設定されたディスク パスに書き込まれます。 スナップショットは、シンボリック リンクとハード リンクをサポートするファイル システムに格納する必要があります。
|
||||
Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data directory variable in your `backup.config` file. Snapshots need to be stored on a filesystem which supports symbolic and hard links.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** {% data variables.product.prodname_enterprise_backup_utilities %} バージョンをアップグレードするときに誤ってデータ ディレクトリが上書きされないように、スナップショットが {% data variables.product.prodname_enterprise_backup_utilities %} インストール ディレクトリのサブディレクトリに保持されないようにすることをお勧めします。
|
||||
**Note:** We recommend ensuring your snapshots are not kept in a subdirectory of the {% data variables.product.prodname_enterprise_backup_utilities %} installation directory, to avoid inadvertently overwriting your data directory when upgrading {% data variables.product.prodname_enterprise_backup_utilities %} versions.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. [{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト リポジトリ](https://github.com/github/backup-utils/)をバックアップ ホスト上のローカル ディレクトリに複製するには、次のコマンドを実行します。
|
||||
1. To clone the [{% data variables.product.prodname_enterprise_backup_utilities %} project repository](https://github.com/github/backup-utils/) to a local directory on your backup host, run the following command.
|
||||
|
||||
```
|
||||
$ git clone https://github.com/github/backup-utils.git /path/to/target/directory/backup-utils
|
||||
```
|
||||
1. ローカル リポジトリ ディレクトリに移動するには、次のコマンドを実行します。
|
||||
1. To change into the local repository directory, run the following command.
|
||||
|
||||
```
|
||||
cd backup-utils
|
||||
```
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
1. インクルードされた `backup.config-example` ファイルを `backup.config` にコピーするには、次のコマンドを実行します。
|
||||
1. To copy the included `backup.config-example` file to `backup.config`, run the following command.
|
||||
|
||||
```shell
|
||||
cp backup.config-example backup.config
|
||||
```
|
||||
1. 構成をカスタマイズするには、テキスト エディターで `backup.config` を編集します。
|
||||
1. `GHE_HOSTNAME` の値をプライマリの {% data variables.product.prodname_ghe_server %} インスタンスのホスト名あるいは IP アドレスに設定します。
|
||||
1. To customize your configuration, edit `backup.config` in a text editor.
|
||||
1. Set the `GHE_HOSTNAME` value to your primary {% data variables.product.prodname_ghe_server %} instance's hostname or IP address.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** {% data variables.product.product_location %} がクラスターとして、またはロード バランサーを使用する高可用性構成に展開されている場合は、{% data variables.product.product_location %} への SSH アクセス (ポート 122 上) が許可されている限り、`GHE_HOSTNAME` をロード バランサーのホスト名に指定できます。
|
||||
**Note:** If {% data variables.product.product_location %} is deployed as a cluster or in a high availability configuration using a load balancer, the `GHE_HOSTNAME` can be the load balancer hostname, as long as it allows SSH access (on port 122) to {% data variables.product.product_location %}.
|
||||
|
||||
復旧されたアプライアンスがすぐに利用できることを保証するために、geo レプリケーション構成の場合であってもプライマリ インスタンスをターゲットとしたバックアップを実行してください。
|
||||
To ensure a recovered appliance is immediately available, perform backups targeting the primary instance even in a geo-replication configuration.
|
||||
|
||||
{% endnote %}
|
||||
1. `GHE_DATA_DIR` の値をバックアップ スナップショットを保存したいファイルシステムの場所に設定します。 手順 1 で Git リポジトリを複製した場所以外の、バックアップ ホストと同じファイル システム上の場所を選ぶことをお勧めします。
|
||||
1. バックアップ ホストにインスタンスへのアクセスを許可するには、プライマリ インスタンスの設定ページ `http(s)://HOSTNAME/setup/settings` を開き、承認された SSH キーの一覧にバックアップ ホストの SSH キーを追加します。 詳細については、「[管理シェル (SSH) にアクセスする](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)」を参照してください。
|
||||
1. バックアップ ホストで、`ghe-host-check` コマンドを使用して、{% data variables.product.product_location %} との SSH 接続を確認します。
|
||||
1. Set the `GHE_DATA_DIR` value to the filesystem location where you want to store backup snapshots. We recommend choosing a location on the same filesystem as your backup host, but outside of where you cloned the Git repository in step 1.
|
||||
1. To grant your backup host access to your instance, open your primary instance's settings page at `http(s)://HOSTNAME/setup/settings` and add the backup host's SSH key to the list of authorized SSH keys. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh#enabling-access-to-the-administrative-shell-via-ssh)."
|
||||
1. On your backup host, verify SSH connectivity with {% data variables.product.product_location %} with the `ghe-host-check` command.
|
||||
|
||||
```shell
|
||||
./bin/ghe-host-check
|
||||
```
|
||||
1. 最初の完全バックアップを作成するには、次のコマンドを実行します。
|
||||
```
|
||||
1. To create an initial full backup, run the following command.
|
||||
|
||||
```shell
|
||||
./bin/ghe-backup
|
||||
```
|
||||
|
||||
高度な使用方法について詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) を参照してください。
|
||||
For more information on advanced usage, see the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#readme) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## {% data variables.product.prodname_enterprise_backup_utilities %} のアップグレード
|
||||
## Upgrading {% data variables.product.prodname_enterprise_backup_utilities %}
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} をアップグレードするときは、現在のバージョンの {% data variables.product.product_name %} で動作するリリースを選ぶ必要があります。 {% data variables.product.prodname_enterprise_backup_utilities %} のインストールは、少なくとも {% data variables.product.product_location %} と同じバージョンである必要があり、3 つ以上先のバージョンにインストールすることはできません。 詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの「[{% data variables.product.prodname_ghe_server %} バージョン要件](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements)」を参照してください。
|
||||
最新の変更をフェッチしてチェックアウトすることで、Git リポジトリの {% data variables.product.prodname_enterprise_backup_utilities %} をアップグレードできます。
|
||||
When upgrading {% data variables.product.prodname_enterprise_backup_utilities %}, you must choose a release that will work with your current version of {% data variables.product.product_name %}. Your installation of {% data variables.product.prodname_enterprise_backup_utilities %} must be at least the same version as {% data variables.product.product_location %}, and cannot be more than two versions ahead. For more information, see [{% data variables.product.prodname_ghe_server %} version requirements](https://github.com/github/backup-utils/blob/master/docs/requirements.md#github-enterprise-server-version-requirements) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
You can upgrade {% data variables.product.prodname_enterprise_backup_utilities %} in a Git repository by fetching and checking out the latest changes.
|
||||
|
||||
または、インストールに Git リポジトリを使用しない場合は、新しいアーカイブを抽出することも、代わりに Git リポジトリを使用するように方法を変更することもできます。
|
||||
Alternatively, if you don't use a Git repository for your installation, you can extract a new archive into place, or you can change your approach to use a Git repository instead.
|
||||
|
||||
### インストールの種類の確認
|
||||
### Verifying the installation type
|
||||
|
||||
{% data variables.product.prodname_enterprise_backup_utilities %} のインストール方法を確認し、インストールをアップグレードする最適な方法を決定できます。
|
||||
You can verify the installation method for {% data variables.product.prodname_enterprise_backup_utilities %} and determine the best way to upgrade your installation.
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
1. 有効な作業ディレクトリが Git リポジトリ内に存在するかどうかを確認するには、次のコマンドを実行します。
|
||||
1. To check if a valid working directory exists inside a Git repository, run the following command.
|
||||
|
||||
```
|
||||
git rev-parse --is-inside-work-tree
|
||||
```
|
||||
|
||||
出力が `true` の場合、{% data variables.product.prodname_enterprise_backup_utilities %} は、プロジェクトの Git リポジトリを複製することによってインストールされました。 出力に `fatal: not a git repository (or any of the parent directories)` が含まれている場合、{% data variables.product.prodname_enterprise_backup_utilities %} は、圧縮アーカイブ ファイルを抽出することによってインストールされたと考えられます。
|
||||
インストールが Git リポジトリにある場合は、Git を使用して最新バージョンをインストールできます。 インストールが圧縮アーカイブ ファイルから行われた場合は、最新バージョンをダウンロードして抽出するか、Git を使用して {% data variables.product.prodname_enterprise_backup_utilities %} を再インストールして、将来のアップグレードを簡略化できます。
|
||||
If the output is `true`, {% data variables.product.prodname_enterprise_backup_utilities %} was installed by cloning the project's Git repository. If the output includes `fatal: not a git repository (or any of the parent directories)`, {% data variables.product.prodname_enterprise_backup_utilities %} was likely installed by extracting a compressed archive file.
|
||||
If your installation is in a Git repository, you can install the latest version using Git. If the installation is from a compressed archive file, you can either download and extract the latest version, or you can reinstall {% data variables.product.prodname_enterprise_backup_utilities %} using Git to simplify future upgrades.
|
||||
|
||||
- [Git リポジトリでのインストールのアップグレード](#upgrading-an-installation-in-a-git-repository)
|
||||
- [圧縮アーカイブの代わりに Git を使用してアーカイブする](#using-git-instead-of-compressed-archives-for-upgrades)
|
||||
- [Upgrading an installation in a Git repository](#upgrading-an-installation-in-a-git-repository)
|
||||
- [Using Git instead of compressed archives for upgrades](#using-git-instead-of-compressed-archives-for-upgrades)
|
||||
|
||||
### Git リポジトリでのインストールのアップグレード
|
||||
### Upgrading an installation in a Git repository
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %} {% note %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
{% note %}
|
||||
|
||||
**注:** {% data variables.product.prodname_enterprise_backup_utilities %} をアップグレードする前に、既存の `backup.config` ファイルのコピーを `$HOME/backup.config` のような一時的な場所に作成することをお勧めします。
|
||||
**Note:** We recommend creating a copy of your existing `backup.config` file in a temporary location, like `$HOME/backup.config`, before upgrading {% data variables.product.prodname_enterprise_backup_utilities %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. `git fetch` コマンドを実行して、最新のプロジェクト更新プログラムをダウンロードします。
|
||||
1. Download the latest project updates by running the `git fetch` command.
|
||||
|
||||
```shell
|
||||
git fetch
|
||||
```
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %} {% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
|
||||
### 圧縮アーカイブの代わりに Git を使用してアーカイブする
|
||||
### Using Git instead of compressed archives for upgrades
|
||||
|
||||
バックアップ ホストにインターネット接続があり、以前に圧縮アーカイブ (`.tar.gz`) を使用して {% data variables.product.prodname_enterprise_backup_utilities %} をインストールまたはアップグレードした場合は、代わりにインストールに Git リポジトリを使用することをお勧めします。 Git を使用してアップグレードすると、作業が少なくなり、バックアップ構成が保持されます。
|
||||
If your backup host has internet connectivity and you previously used a compressed archive (`.tar.gz`) to install or upgrade {% data variables.product.prodname_enterprise_backup_utilities %}, we recommend using a Git repository for your installation instead. Upgrading using Git requires less work and preserves your backup configuration.
|
||||
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
|
||||
1. 既存の {% data variables.product.prodname_enterprise_backup_utilities %} の構成をバックアップするには、現在の `backup.config` ファイルをホーム ディレクトリなどの安全な場所にコピーします。
|
||||
1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
|
||||
|
||||
```
|
||||
$ cp backup.config $HOME/backup.config.saved-$(date +%Y%m%d-%H%M%S)
|
||||
```
|
||||
|
||||
1. {% data variables.product.prodname_enterprise_backup_utilities %} Git リポジトリをインストールするバックアップ ホスト上のローカル ディレクトリに移動します。
|
||||
1. [プロジェクト リポジトリ](https://github.com/github/backup-utils/)をバックアップ ホスト上のディレクトリに複製するには、次のコマンドを実行します。
|
||||
1. Change to the local directory on your backup host where you want to install the {% data variables.product.prodname_enterprise_backup_utilities %} Git repository.
|
||||
1. To clone the [project repository](https://github.com/github/backup-utils/) to the directory on your backup host, run the following command.
|
||||
|
||||
```
|
||||
git clone https://github.com/github/backup-utils.git
|
||||
```
|
||||
1. 複製されたリポジトリに移動するには、次のコマンドを実行します。
|
||||
1. To change into the cloned repository, run the following command.
|
||||
|
||||
```
|
||||
cd backup-utils
|
||||
```
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
|
||||
1. 前の手順からバックアップ構成を復元するには、既存のバックアップ構成ファイルをローカル リポジトリ ディレクトリにコピーします。 コマンドのパスを、手順 2 で保存したファイルの場所に置き換えます。
|
||||
1. To restore your backup configuration from earlier, copy your existing backup configuration file to the local repository directory. Replace the path in the command with the location of the file saved in step 2.
|
||||
|
||||
```
|
||||
$ cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
|
||||
@@ -186,44 +182,44 @@ ms.locfileid: '147861653'
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** 複製後にバックアップ構成ファイルを復元する場所を選ぶことができます。 構成ファイルを配置できる場所について詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの「[概要](https://github.com/github/backup-utils/blob/master/docs/getting-started.md)」を参照してください。
|
||||
**Note:** You can choose where to restore your backup configuration file to after cloning. For more information about where configuration files can be located, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. バックアップ構成ファイル内のディレクトリまたはスクリプトのパスが正しいことを確認するには、テキスト エディターでファイルを確認します。
|
||||
1. To confirm that the paths to directories or scripts in your backup configuration file are correct, review the file in a text editor.
|
||||
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
|
||||
1. 手順 1 から古い GitHub Enterprise Server Backup Utilities ディレクトリ (圧縮アーカイブのインストール場所) を削除します。
|
||||
1. Delete your old GitHub Enterprise Server Backup Utilities directory from step 1 (where the compressed archive installation was located).
|
||||
|
||||
## バックアップのスケジューリング
|
||||
## Scheduling a backup
|
||||
|
||||
`cron(8)` コマンドや同様のコマンド スケジューリング サービスを使用して、バックアップ ホストで定期的なバックアップをスケジュール設定できます。 設定されたバックアップ頻度によって、リカバリー計画での最悪の目標復旧ポイント (RPO) が決まります。 たとえば、毎日午前 0 時にバックアップを実行するようにスケジュール設定した場合、災害のシナリオで最大 24 時間分のデータが失われる可能性があります。 プライマリサイトのデータが破壊された場合に、最悪でも最大 1 時間分のデータ損失で収まることが保証されるように、1 時間ごとのバックアップスケジュールから始めることをおすすめします。
|
||||
You can schedule regular backups on the backup host using the `cron(8)` command or a similar command scheduling service. The configured backup frequency will dictate the worst case recovery point objective (RPO) in your recovery plan. For example, if you have scheduled the backup to run every day at midnight, you could lose up to 24 hours of data in a disaster scenario. We recommend starting with an hourly backup schedule, guaranteeing a worst case maximum of one hour of data loss if the primary site data is destroyed.
|
||||
|
||||
バックアップの試行が重複すると、`ghe-backup` コマンドはエラー メッセージを表示して中断し、同時バックアップが存在することを示します。 そのような場合は、スケジュール設定したバックアップの頻度を減らすことをおすすめします。 詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups) を参照してください。
|
||||
If backup attempts overlap, the `ghe-backup` command will abort with an error message, indicating the existence of a simultaneous backup. If this occurs, we recommended decreasing the frequency of your scheduled backups. For more information, see the "Scheduling backups" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#scheduling-backups) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
|
||||
## バックアップの復元
|
||||
## Restoring a backup
|
||||
|
||||
プライマリ サイトで長時間の停止または壊滅的なイベントが発生した場合は、別の {% data variables.product.prodname_enterprise %} アプライアンスをプロビジョニングしてバックアップ ホストから復元することで、{% data variables.product.product_location %} を復元できます。 アプライアンスを復元する前に、バックアップホストの SSH キーをターゲットの {% data variables.product.prodname_enterprise %} アプライアンスに認証済み SSH キーとして追加する必要があります。
|
||||
In the event of prolonged outage or catastrophic event at the primary site, you can restore {% data variables.product.product_location %} by provisioning another {% data variables.product.prodname_enterprise %} appliance and performing a restore from the backup host. You must add the backup host's SSH key to the target {% data variables.product.prodname_enterprise %} appliance as an authorized SSH key before restoring an appliance.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意:** {% data variables.product.product_location %} へのバックアップを復元する場合は、同じバージョンのサポート ルールが適用されます。 最大 2 つ前の機能リリースからしかデータを復元できません。
|
||||
**Note:** When performing backup restores to {% data variables.product.product_location %}, the same version supportability rules apply. You can only restore data from at most two feature releases behind.
|
||||
|
||||
たとえば、{% data variables.product.product_name %} 3.0.x からバックアップを取得した場合、バックアップを {% data variables.product.product_name %} 3.2.x インスタンスに復元できます。 {% data variables.product.product_name %} 2.22.x のバックアップから 3.2.x を実行しているインスタンスにデータを復元することはできません。これは、バージョンを 3 回ジャンプするためです (2.22 から 3.0、3.1、3.2 の順)。 最初に 3.1.x を実行しているインスタンスに復元してから、3.2.x にアップグレードする必要があります。
|
||||
For example, if you take a backup from {% data variables.product.product_name %} 3.0.x, you can restore the backup to a {% data variables.product.product_name %} 3.2.x instance. You cannot restore data from a backup of {% data variables.product.product_name %} 2.22.x to an instance running 3.2.x, because that would be three jumps between versions (2.22 to 3.0 to 3.1 to 3.2). You would first need to restore to an instance running 3.1.x, and then upgrade to 3.2.x.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
最後に成功したスナップショットから {% data variables.product.product_location %} を復元するには、`ghe-restore` コマンドを使用します。
|
||||
To restore {% data variables.product.product_location %} from the last successful snapshot, use the `ghe-restore` command.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** バックアップを復元する前に、次のことを確認してください。
|
||||
- プライマリ インスタンスでメンテナンス モードが有効になり、すべてのアクティブなプロセスが完了している。 詳細については、「[メンテナンス モードの有効化](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)」を参照してください。
|
||||
- 高可用性構成のすべてのレプリカでレプリケーションが停止している。 詳しくは、「[高可用性構成について](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)」の `ghe-repl-stop` コマンドを参照してください。
|
||||
- {% data variables.product.product_location %} で {% data variables.product.prodname_actions %} が有効になっている場合は、まず交換用アプライアンスで {% data variables.product.prodname_actions %} 外部ストレージ プロバイダーを構成する必要があります。 詳細については、「[{% data variables.product.prodname_actions %} を有効にして、{% data variables.product.prodname_ghe_server %} をバックアップおよび復元する](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)」を参照してください。
|
||||
**Note:** Prior to restoring a backup, ensure:
|
||||
- Maintenance mode is enabled on the primary instance and all active processes have completed. For more information, see "[Enabling maintenance mode](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)."
|
||||
- Replication is stopped on all replicas in high availability configurations. For more information, see the `ghe-repl-stop` command in "[About high availability configuration](/admin/enterprise-management/configuring-high-availability/about-high-availability-configuration#ghe-repl-stop)."
|
||||
- If {% data variables.product.product_location %} has {% data variables.product.prodname_actions %} enabled, you must first configure the {% data variables.product.prodname_actions %} external storage provider on the replacement appliance. For more information, see "[Backing up and restoring {% data variables.product.prodname_ghe_server %} with {% data variables.product.prodname_actions %} enabled](/admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
`ghe-restore` コマンドを実行すると、次のような出力が表示されます。
|
||||
When running the `ghe-restore` command, you should see output similar to this:
|
||||
|
||||
```shell
|
||||
$ ghe-restore -c 169.154.1.1
|
||||
@@ -242,15 +238,20 @@ $ ghe-restore -c 169.154.1.1
|
||||
> Visit https://169.154.1.1/setup/settings to review appliance configuration.
|
||||
```
|
||||
|
||||
{% ifversion ip-exception-list %}必要に応じて復元を検証するには、指定した IP アドレスのリストへのアクセスを許可するように IP 例外リストを構成します。 詳細については、「[IP 例外リストを使い、メンテナンス モードで変更を検証する](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)」を参照してください。
|
||||
{% ifversion 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 %}
|
||||
|
||||
**注意:** ネットワーク設定はバックアップ スナップショットから除外されます。 ご使用の環境に合わせて、ターゲットの {% data variables.product.prodname_ghe_server %} アプライアンスでネットワークを手動で設定する必要があります。
|
||||
**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.
|
||||
|
||||
- When restoring to new disks on an existing or empty {% data variables.product.prodname_ghe_server %} instance, stale UUIDs may be present, resulting in Git and/or Alambic replication reporting as out of sync. Stale server entry IDs can be the result of a retired node in a high availability configuration still being present in the application database, but not in the restored replication configuration. To remediate, stale UUIDs can be torn down using `ghe-repl-teardown` once the restore has completed and prior to starting replication. In this scenario, contact {% data variables.contact.contact_ent_support %} for further assistance.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
`ghe-restore` コマンドでは、次の追加オプションを使用できます。
|
||||
- `-c` フラグは、既に設定されている場合でも、ターゲット ホストで設定、証明書、およびライセンス データを上書きします。 テストのためにステージングインスタンスを設定しており、ターゲット上の依存の設定を残しておきたい場合には、このフラグを省いてください。 詳しくは、{% data variables.product.prodname_enterprise_backup_utilities %} プロジェクト ドキュメントの [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) の「バックアップと復旧コマンドの使用」セクションを参照してください。
|
||||
- `-s` フラグにより、異なるバックアップ スナップショットを選択できます。
|
||||
You can use these additional options with `ghe-restore` command:
|
||||
- The `-c` flag overwrites the settings, certificate, and license data on the target host even if it is already configured. Omit this flag if you are setting up a staging instance for testing purposes and you wish to retain the existing configuration on the target. For more information, see the "Using backup and restore commands" section of the [{% data variables.product.prodname_enterprise_backup_utilities %} README](https://github.com/github/backup-utils#using-the-backup-and-restore-commands) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
|
||||
- The `-s` flag allows you to select a different backup snapshot.
|
||||
|
||||
@@ -93,7 +93,7 @@ Optionally, if you use {% data variables.product.prodname_registry %} on your pr
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_actions %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
**Warning**: If you don't configure {% data variables.product.prodname_registry %} on the staging instance before restoring your production backup, your staging instance will use your production instance's external storage, which could result in loss of data. We strongly recommended that you use different external storage for your staging instance.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -128,7 +128,7 @@ Optionally, if you use {% data variables.product.prodname_registry %} on your pr
|
||||
|
||||
Use the `ghe-restore` command to restore the rest of the data from the backup. For more information, see "[Restoring a backup](/admin/configuration/configuring-backups-on-your-appliance#restoring-a-backup)."
|
||||
|
||||
If the staging instance is already configured and you're about to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
If the staging instance is already configured and you want to overwrite settings, certificate, and license data, add the `-c` option to the command. For more information about the option, see [Using the backup and restore commands](https://github.com/github/backup-utils/blob/master/docs/usage.md#restoring-settings-tls-certificate-and-license) in the {% data variables.product.prodname_enterprise_backup_utilities %} documentation.
|
||||
|
||||
### 6. Review the instance's configuration
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ Jobs that run on Windows and macOS runners that {% data variables.product.prodna
|
||||
|
||||
The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
|
||||
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes each job uses up to the nearest minute.
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -3,6 +3,7 @@ title: About billing for GitHub Codespaces
|
||||
shortTitle: About billing
|
||||
intro: 'View pricing and see how to manage {% data variables.product.prodname_github_codespaces %} billing for your organization.'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -13,40 +14,105 @@ topics:
|
||||
- Billing
|
||||
redirect_from:
|
||||
- /billing/managing-billing-for-github-codespaces/about-billing-for-codespaces
|
||||
- /github/developing-online-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md
|
||||
---
|
||||
|
||||
## {% data variables.product.prodname_github_codespaces %} pricing
|
||||
|
||||
Charges are incurred for the use of {% data variables.product.prodname_github_codespaces %} for repositories owned by organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}. These accounts do not include any free minutes or storage for {% data variables.product.prodname_github_codespaces %}. Repositories in personal accounts are not currently billed for {% data variables.product.prodname_github_codespaces %} usage.
|
||||
Charges are incurred for the use of {% data variables.product.prodname_github_codespaces %} for repositories owned by organization and enterprise accounts on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %}. These accounts do not include any free minutes or storage for {% data variables.product.prodname_github_codespaces %}. Personal accounts are not currently billed for {% data variables.product.prodname_github_codespaces %} usage.
|
||||
|
||||
A {% data variables.product.prodname_github_codespaces %} instance (a "codespace") incurs charges for compute time, while it is active, and for the amount of storage it uses on disk.
|
||||
|
||||
{% data variables.product.prodname_github_codespaces %} usage is billed according to the units of measure in the following table:
|
||||
|
||||
| Product | SKU | Unit of measure | Price |
|
||||
| ------------------- | -------- | --------------- | ----- |
|
||||
| Codespaces Compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
| | 8 core | 1 hour | $0.72 |
|
||||
| | 16 core | 1 hour | $1.44 |
|
||||
| | 32 core | 1 hour | $2.88 |
|
||||
| Codespaces Storage | Storage | 1 GB-month | $0.07 |
|
||||
| Component | Machine type | Unit of measure | Price |
|
||||
| ------------------- | ------------ | --------------- | ----- |
|
||||
| Codespaces compute | 2 core | 1 hour | $0.18 |
|
||||
| | 4 core | 1 hour | $0.36 |
|
||||
| | 8 core | 1 hour | $0.72 |
|
||||
| | 16 core | 1 hour | $1.44 |
|
||||
| | 32 core | 1 hour | $2.88 |
|
||||
| Codespaces storage | Storage | 1 GB-month<sup>*</sup> | $0.07 |
|
||||
|
||||
<sup>*</sup> See "[Billing for storage usage](#billing-for-storage-usage)" below for details of the GB-month unit of measure.
|
||||
|
||||
If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[Billing for {% data variables.product.prodname_codespaces %} prebuilds](#billing-for-codespaces-prebuilds)."
|
||||
|
||||
## About billing for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-billing %}
|
||||
{% data variables.product.prodname_github_codespaces %} is billed in US dollars (USD) according to their compute and storage usage. {% data reusables.codespaces.codespaces-monthly-billing %} xxx
|
||||
|
||||
Your {% data variables.product.prodname_github_codespaces %} usage shares your organization or enterprise account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
|
||||
Your {% data variables.product.prodname_github_codespaces %} usage shares your organization or enterprise account's existing payment method, and receipt. For more information, see "[Viewing your subscriptions and billing date](/articles/viewing-your-subscriptions-and-billing-date)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
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_github_codespaces %} usage. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_codespaces %}
|
||||
### Billing for compute usage
|
||||
The compute usage of a codespace is the number of minutes for which that codespace is active. Total compute usage is calculated by summing the number of minutes used by all codespaces that are billable to the organization or enterprise. These totals are reported to the billing service every hour, and are billed monthly.
|
||||
|
||||
As an example, if a codespace is active for 1 hour and 15 minutes, then the compute cost will be the hourly cost of the codespace, as determined by its machine type, multiplied by 1.25.
|
||||
|
||||
You can restrict compute usage by stopping your codespaces. For information, see "[Stopping and starting a codespace](/codespaces/developing-in-codespaces/stopping-and-starting-a-codespace)." Codespaces are stopped automatically after a configurable period of inactivity. The timeout period can be configured by the user, or at the organization level. For more information, see "[Setting your timeout period for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-timeout-period-for-github-codespaces)" and "[Restricting the idle timeout period](/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period)."
|
||||
|
||||
### Billing for storage usage
|
||||
For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces and prebuilds in your account. This includes any files used by the codespaces, such as cloned repositories, configuration files, and extensions, among others. Storage is billed for all of your existing codespaces, regardless of whether they are active or stopped. The storage billing for a codespace ends when it is deleted.
|
||||
|
||||
Codespace storage is reported in GB-months. Your billing month runs from a fixed day in one month until the same day in the next month. In most cases the day of the month is determined by the day you started on your current {% data variables.product.prodname_dotcom %} plan. Your GB-month storage, is calculated as follows. Once every hour, the storage used by all of your currently active and stopped codespaces is assessed. This figure is then divided by the number of hours in the current billing month: `total storage size / hours this month`. The result is added to the running total for codespace storage for the month.
|
||||
|
||||
For example, if you have one codespace that uses 100 GB of storage and has existed for one hour you will have used `100 / (24 * 30) = 0.1388` GB-months of storage in a 30-day month. If your use of GitHub Codespaces during a 30-day month consists of two 100 GB codespaces that both existed for three full days then there will be `24 * 3` hourly reports for the storage of these codespaces, giving a total of: `(24 * 3) * 200 / (24 * 30) = 20` GB-months.
|
||||
|
||||
For each hourly report, the storage usage for the previous hour is calculated in seconds. As a result, you won't be charged for a full hour of storage if a codespace did not exist for the full 60 minutes. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB.
|
||||
|
||||
As an organization owner, you can:
|
||||
- List the currently active and stopped codespaces for your organization. For more information, see "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)." In addition to the cost of these codespaces, the cost of {% data variables.product.prodname_github_codespaces %} for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
|
||||
- See the total {% data variables.product.prodname_github_codespaces %} compute and storage usage for your organization for the current month to date. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
- Configure your organization settings to manage the cost of {% data variables.product.prodname_github_codespaces %}. For more information, see "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)."
|
||||
|
||||
To estimate the costs for metered services, you can use the {% data variables.product.prodname_dotcom %} [pricing calculator](https://github.com/pricing/calculator?feature=codespaces).
|
||||
|
||||
### Billing for {% data variables.product.prodname_codespaces %} prebuilds
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-default %}
|
||||
{% data reusables.codespaces.prebuilds-definition %} For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds)."
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-reducing %}
|
||||
#### {% data variables.product.prodname_actions %} costs for prebuilds
|
||||
|
||||
Prebuilds are created and updated by running a {% data variables.product.prodname_actions %} workflow on a {% data variables.product.prodname_dotcom %}-hosted runner. By default, prebuilds are updated every time you modify the prebuild configuration, or push changes to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." There is no associated {% data variables.product.prodname_codespaces %} compute cost for creating or updating prebuilds.
|
||||
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of previous versions of each prebuild that are retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
If you are an organization or enterprise owner, you can track usage of prebuild workflows and storage by downloading a usage report for your organization or enterprise. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_github_codespaces %} Prebuilds." For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)."
|
||||
|
||||
#### Storage costs for prebuilds
|
||||
|
||||
In addition to {% data variables.product.prodname_actions %} minutes, you will also be billed for the storage of prebuilds associated with each prebuild configuration for a given repository and region. Storage of prebuilds is billed at the same rate as storage of codespaces.
|
||||
|
||||
The storage cost for a prebuild in a single region will be similar to the storage cost that will be incurred for storing a single codespace created from that prebuild. The storage cost for the generated codespace may be more than the cost for the prebuild if, for example, the `updateContentCommand` and `postCreateCommand` commands are used during codespace creation to download more files to the dev container.
|
||||
|
||||
The total storage costs associated with a prebuild template will depend on:
|
||||
|
||||
* The price of storage per GB. See the table above.
|
||||
* The size of the generated prebuild in GB.
|
||||
* The number of regions in which the prebuild is available (because a copy of the prebuild is stored in each region).
|
||||
* The number of older versions of the prebuild that are retained.
|
||||
|
||||
The storage cost for a prebuild is therefore calculated as: `price per GB * size (GB) * regions * versions`.
|
||||
|
||||
To limit the storage costs associated with prebuilds, you can choose to create prebuilds only in selected regions, and you can specify the number of older versions of prebuilds that will be retained. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Prebuilds may be updated several times during a billing month. Newer versions of a prebuild may be larger or smaller than the previous versions. This will affect the storage charges. For details of how storage is calculated during a billing month, see "[Billing for storage usage](#billing-for-storage-usage)" above.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### Cost of codespaces created from prebuilds
|
||||
|
||||
Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.
|
||||
|
||||
## Setting a spending limit
|
||||
|
||||
@@ -72,7 +138,7 @@ For example, a user in an organization can fork a repository within that organiz
|
||||
|
||||
## How billing is handled when a repository is transferred
|
||||
|
||||
Usage is billed and reported on every hour. As such, you pay for any usage when a repository is within your organization. When a repository is transferred out of your organization, any codespaces in that repository are removed as part of the transfer process.
|
||||
Usage is calculated every hour. An organization pays for usage of codespaces created from any repository owned by the organization, where the organization settings permit the organization to be billed. For more information, see "[Enabling GitHub Codespaces for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization#choose-who-can-create-codespaces-that-are-billed-to-your-organization)." When a repository is transferred out of your organization, ownership and billing responsibility for any codespaces associated with that repository will change accordingly.
|
||||
|
||||
## What happens when users are removed
|
||||
|
||||
|
||||
@@ -11,4 +11,3 @@ children:
|
||||
- /viewing-your-github-codespaces-usage
|
||||
- /managing-spending-limits-for-github-codespaces
|
||||
---
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ redirect_from:
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %}
|
||||
|
||||
Once you've reached your spending limit, your organization or repository will no longer be able to create new codespaces, and won't be able to start existing codespaces. Any existing codespaces that are still running will not be shutdown; if you don't change the spending limit, you will not be charged for the amount that exceeds the limit.
|
||||
|
||||
For more information about pricing for {% data variables.product.prodname_github_codespaces %} usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
@@ -67,4 +69,4 @@ You can disable these notifications anytime by navigating to the bottom of the *
|
||||
## Further reading
|
||||
|
||||
- "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
|
||||
@@ -21,8 +21,21 @@ Organization owners and billing managers can view {% data variables.product.prod
|
||||
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
1. Under "{% data variables.product.prodname_codespaces %}", view the details of the compute hours and storage used so far this month.
|
||||
|
||||
|
||||
|
||||
|
||||
You can also see and update your current spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
* The costs shown here are the cumulative costs within the current monthly billing period. The metered costs for {% data variables.product.prodname_github_codespaces %} shown on this page are reset to zero at the start of each monthly billing period. Outstanding costs from previous months are not shown.
|
||||
* The figures on this page are updated every hour.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
|
||||
The data used for this report is updated daily.
|
||||
1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
|
||||
|
||||
|
||||
@@ -38,3 +51,7 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
|
||||
1. Under "{% data variables.product.prodname_codespaces %} monthly usage", view the usage details of each organization in your enterprise account.
|
||||
{% data reusables.enterprise-accounts.actions-packages-report-download-enterprise-accounts %}
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
@@ -14,23 +14,23 @@ shortTitle: Private image registry
|
||||
|
||||
A registry is a secure space for storing, managing, and fetching private container images. You may use one to store one or more images. There are many examples of registries, such as {% data variables.product.prodname_container_registry %}, {% data variables.product.prodname_npm_registry %}, Azure Container Registry, or DockerHub.
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} can be configured to allow container images to be pulled seamlessly into {% data variables.product.prodname_github_codespaces %} during codespace creation, without having to provide any authentication credentials. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_github_codespaces %} to access images stored in that registry.
|
||||
{% data variables.packages.prodname_ghcr_and_npm_registry %} can be configured to allow container images to be pulled seamlessly into {% data variables.product.prodname_github_codespaces %} during codespace creation, without having to provide any authentication credentials. For other image registries, you must create secrets in {% data variables.product.prodname_dotcom %} to store the access details, which will allow {% data variables.product.prodname_github_codespaces %} to access images stored in that registry.
|
||||
|
||||
## Accessing images stored in {% data variables.product.prodname_ghcr_and_npm_registry %}
|
||||
## Accessing images stored in {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} provide the easiest way for {% data variables.product.prodname_github_codespaces %} to consume dev container images.
|
||||
{% data variables.packages.prodname_ghcr_and_npm_registry %} provide the easiest way for {% data variables.product.prodname_github_codespaces %} to consume dev container images.
|
||||
|
||||
For more information, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)" and "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry)".
|
||||
|
||||
### Accessing an image published to the same repository as the codespace
|
||||
|
||||
If you publish a container image to {% data variables.product.prodname_ghcr_or_npm_registry %} in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
|
||||
If you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %} in the same repository that the codespace is being launched in, you will automatically be able to fetch that image on codespace creation. You won't have to provide any additional credentials, unless the **Inherit access from repo** option was unselected when the container image was published.
|
||||
|
||||
#### Inheriting access from the repository from which an image was published
|
||||
|
||||
By default, when you publish a container image to {% data variables.product.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
|
||||
By default, when you publish a container image to {% data variables.packages.prodname_ghcr_or_npm_registry %}, the image inherits the access setting of the repository from which the image was published. For example, if the repository is public, the image is also public. If the repository is private, the image is also private, but is accessible from the repository.
|
||||
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.product.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT).
|
||||
This behavior is controlled by the **Inherit access from repo** option. **Inherit access from repo** is selected by default when publishing via {% data variables.product.prodname_actions %}, but not when publishing directly to {% data variables.packages.prodname_ghcr_or_npm_registry %} using a Personal Access Token (PAT).
|
||||
|
||||
If the **Inherit access from repo** option was not selected when the image was published, you can manually add the repository to the published container image's access controls. For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#inheriting-access-for-a-container-image-from-a-repository)."
|
||||
|
||||
@@ -46,13 +46,13 @@ If you want to allow a subset of an organization's repositories to access a cont
|
||||
|
||||
### Publishing a container image from a codespace
|
||||
|
||||
Seamless access from a codespace to {% data variables.product.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
|
||||
Seamless access from a codespace to {% data variables.packages.prodname_ghcr_or_npm_registry %} is limited to pulling container images. If you want to publish a container image from inside a codespace, you must use a personal access token (PAT) with the `write:packages` scope.
|
||||
|
||||
We recommend publishing images via {% data variables.product.prodname_actions %}. For more information, see "[Publishing Docker images](/actions/publishing-packages/publishing-docker-images)" and "[Publishing Node.js packages](/actions/publishing-packages/publishing-nodejs-packages)."
|
||||
|
||||
## Accessing images stored in other container registries
|
||||
|
||||
If you are accessing a container image from a registry that isn't {% data variables.product.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace.
|
||||
If you are accessing a container image from a registry that isn't {% data variables.packages.prodname_ghcr_or_npm_registry %}, {% data variables.product.prodname_github_codespaces %} checks for the presence of three secrets, which define the server name, username, and personal access token (PAT) for a container registry. If these secrets are found, {% data variables.product.prodname_github_codespaces %} will make the registry available inside your codespace.
|
||||
|
||||
- `<*>_CONTAINER_REGISTRY_SERVER`
|
||||
- `<*>_CONTAINER_REGISTRY_USER`
|
||||
|
||||
@@ -6,7 +6,6 @@ versions:
|
||||
ghec: '*'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
children:
|
||||
- /understanding-billing-for-github-codespaces
|
||||
- /allowing-your-codespace-to-access-a-private-image-registry
|
||||
- /using-github-copilot-in-github-codespaces
|
||||
- /using-the-vs-code-command-palette-in-codespaces
|
||||
|
||||
@@ -1,63 +0,0 @@
|
||||
---
|
||||
title: Understanding billing for GitHub Codespaces
|
||||
intro: 'Learn how your {% data variables.product.prodname_github_codespaces %} usage is billed.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
redirect_from:
|
||||
- /github/developing-online-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/getting-started-with-codespaces/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/about-billing-for-codespaces
|
||||
- /codespaces/codespaces-reference/understanding-billing-for-codespaces
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
- Billing
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
shortTitle: Understanding billing
|
||||
---
|
||||
|
||||
This article explains how billing works for your codespaces, and explains how your organization's billing manager can help.
|
||||
|
||||
## Getting access to {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
Your organization's administrator might limit {% data variables.product.prodname_github_codespaces %} usage to only specific personal accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
|
||||
|
||||
## How much it costs to use {% data variables.product.prodname_codespaces %}
|
||||
|
||||
To see the pricing for {% data variables.product.prodname_github_codespaces %} usage, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
|
||||
|
||||
## How your codespace usage is billed
|
||||
|
||||
Your codespace is billed for its compute minutes and for the amount of storage it uses on disk.
|
||||
|
||||
If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)."
|
||||
|
||||
### Understanding what compute minutes are
|
||||
Your codespace is billed for the number of minutes that it's active. If your codespaces window is left idle for 30 minutes, it will automatically shutdown, and compute billing for the codespace will end until you start the codespace again.
|
||||
|
||||
### Understanding how codespace storage is billed
|
||||
For {% data variables.product.prodname_github_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces.
|
||||
|
||||
## How spending limits work
|
||||
|
||||
Before your organization can use {% data variables.product.prodname_github_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
## Exporting changes when you have reached your spending limit
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
|
||||
## Checking your current usage and limits
|
||||
If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
## Codespaces can be automatically deleted
|
||||
|
||||
Your codespace will be automatically deleted when you are removed from an organization or repository.
|
||||
|
||||
## Deleting your unused codespaces
|
||||
|
||||
You can manually delete your codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, you can manually delete files using the terminal or from within {% data variables.product.prodname_vscode %}.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
@@ -71,7 +71,7 @@ If you try to delete a codespace with unpushed git commits, your editor will not
|
||||
|
||||
Codespaces that have been stopped and remain inactive for a specified period of time will be deleted automatically. By default, inactive codespaces are deleted after 30 days, but you can customize your codespace retention period. For more information, see "[Configuring automatic deletion of your codespaces](/codespaces/customizing-your-codespace/configuring-automatic-deletion-of-your-codespaces)."
|
||||
|
||||
You will be charged for the storage of all your codespaces. When you delete a codespace, you will no longer be charged.
|
||||
If you create a codespace, it will continue to accrue storage charges until it is deleted, irrespective of whether it is active or stopped. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-storage-usage)." Deleting a codespace does not reduce the current billable amount for {% data variables.product.prodname_github_codespaces %}, which accumulates during each monthly billing cycle. For more information, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
For more information on deleting a codespace, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace)."
|
||||
|
||||
|
||||
@@ -11,12 +11,12 @@ children:
|
||||
- /codespaces-lifecycle
|
||||
- /developing-in-a-codespace
|
||||
- /creating-a-codespace
|
||||
- /deleting-a-codespace
|
||||
- /opening-an-existing-codespace
|
||||
- /using-source-control-in-your-codespace
|
||||
- /using-github-codespaces-for-pull-requests
|
||||
- /stopping-and-starting-a-codespace
|
||||
- /renaming-a-codespace
|
||||
- /deleting-a-codespace
|
||||
- /forwarding-ports-in-your-codespace
|
||||
- /default-environment-variables-for-your-codespace
|
||||
- /connecting-to-a-private-network
|
||||
|
||||
@@ -117,6 +117,6 @@ If you already use {% data variables.product.prodname_vscode_shortname %}, you c
|
||||
## Further reading
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
- "[Add a dev container configuration to your repository](/codespaces/setting-up-your-project-for-codespaces/setting-up-your-project-for-codespaces)"
|
||||
- "[Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle)"
|
||||
|
||||
@@ -111,4 +111,4 @@ You've successfully created, personalized, and run your first application within
|
||||
## Further reading
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)"
|
||||
- "[Managing billing for {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization)"
|
||||
- "[Managing the cost of {% data variables.product.prodname_github_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-the-cost-of-github-codespaces-in-your-organization)"
|
||||
|
||||
@@ -11,7 +11,7 @@ topics:
|
||||
children:
|
||||
- /enabling-github-codespaces-for-your-organization
|
||||
- /listing-the-codespaces-in-your-organization
|
||||
- /managing-billing-for-github-codespaces-in-your-organization
|
||||
- /managing-the-cost-of-github-codespaces-in-your-organization
|
||||
- /managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces
|
||||
- /managing-repository-access-for-your-organizations-codespaces
|
||||
- /reviewing-your-organizations-audit-logs-for-github-codespaces
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 組織内の codespace を一覧表示する
|
||||
title: Listing the codespaces in your organization
|
||||
shortTitle: List organization codespaces
|
||||
intro: 組織に対して現在アクティブになっているまたは停止している codespace をすべて一覧表示できます。
|
||||
intro: 'You can list all of the currently active or stopped codespaces for your organization.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To list all of the current codespaces for your organization, you must be an organization owner.'
|
||||
versions:
|
||||
@@ -11,34 +11,31 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Administrator
|
||||
ms.openlocfilehash: 72d59c35641dd77b4d3623cc70b12b5be880be34
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147865220'
|
||||
---
|
||||
## 概要
|
||||
|
||||
組織の所有者は、組織に対して現在アクティブになっているまたは停止している codespace をすべて一覧表示できます。 これを行って、ユーザーが作成している codespace の数を確認し、不要なコストが発生していないことを確認することをお勧めします。
|
||||
## Overview
|
||||
|
||||
組織用の codespace を一覧表示する最も簡単な方法は、{% data variables.product.prodname_cli %} を使用することです。 REST API を使用することもできます。これにより、各 codespace に関する詳しい情報を確認できます。
|
||||
As an organization owner, you can list all of the currently active and stopped codespaces for your organization. You might want to do this to check how many codespaces users are creating, to make sure they aren't incurring unnecessary costs. For information about pricing, see "[About billing for GitHub Codespaces](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
### {% data variables.product.prodname_cli %} を使用して codespace を一覧表示する
|
||||
The easiest way to list the codespaces for an organization is by using {% data variables.product.prodname_cli %}. You can also use the REST API, which provides more information about each codespace.
|
||||
|
||||
指定した組織に対する現在の codespace をすべて一覧表示するには、次のコマンドを使用します。
|
||||
For information on how to see the current total {% data variables.product.prodname_codespaces %} usage for your organization or enterprise, and generate a detailed report, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
### Using {% data variables.product.prodname_cli %} to list codespaces
|
||||
|
||||
To list all of the current codespaces for a specified organization, use the following command.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace list --org ORGANIZATION
|
||||
```
|
||||
|
||||
このコマンドを実行すると、codespace ごとに次の情報を含むリストが返されます。
|
||||
- 名前と表示名
|
||||
- codespace を作成したユーザー
|
||||
- リポジトリとブランチ
|
||||
- codespace の現在の状態
|
||||
This command returns a list that includes the following information for each codespace:
|
||||
- The name and display name
|
||||
- The user who created the codespace
|
||||
- The repository and branch
|
||||
- The current state of the codespace
|
||||
|
||||
特定のユーザーによって作成された、組織向けの現在の codespace をすべて一覧表示するには、次のコマンドを使用します。
|
||||
To list all of the current codespaces for an organization that were created by a specific user, use the following command.
|
||||
|
||||
```shell{:copy}
|
||||
gh codespace list --org ORGANIZATION --user USER
|
||||
@@ -46,12 +43,12 @@ gh codespace list --org ORGANIZATION --user USER
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**: 上記のコマンドでは、`ORGANIZATION` を、クエリを実行する組織の名前に置き換えます。 組織の所有者でなければなりません。
|
||||
**Note**: In the above commands, replace `ORGANIZATION` with the name of the organization you are querying. You must be an owner of the organization.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### REST API を使用して codespace を一覧表示する
|
||||
### Using the REST API to list codespaces
|
||||
|
||||
組織に対する現在の codespace を一覧表示する別の方法として、`/orgs/{org}/codespaces` API エンドポイントを使用することもできます。 これを使用すると、{% data variables.product.prodname_cli %} よりも多くの情報が返されます。たとえば、マシンの種類に関する詳しい情報などです。
|
||||
You can use the `/orgs/{org}/codespaces` API endpoint as an alternative method of listing the current codespaces for an organization. This returns more information than {% data variables.product.prodname_cli %}; for example, the machine type details.
|
||||
|
||||
このエンドポイントについて詳しくは、「[Codespaces Organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)」を参照してください。
|
||||
For more information about this endpoint, see "[Codespaces organizations](/rest/codespaces/organizations#list-codespaces-for-the-organization)."
|
||||
@@ -1,62 +0,0 @@
|
||||
---
|
||||
title: Managing billing for GitHub Codespaces in your organization
|
||||
shortTitle: Manage billing
|
||||
intro: 'You can check your {% data variables.product.prodname_github_codespaces %} usage and set usage limits.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
permissions: 'To manage billing for {% data variables.product.prodname_github_codespaces %} for an organization, you must be an organization owner or a billing manager.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
- Billing
|
||||
redirect_from:
|
||||
- /codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
To learn about pricing for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-billing %}
|
||||
|
||||
- As an organization owner or a billing manager, you can manage {% data variables.product.prodname_github_codespaces %} billing for your organization: ["About billing for Codespaces"](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)
|
||||
- As an organization owner, you can list the currently active and stopped codespaces for your organization. In addition to these codespaces, costs for the current month may include costs for codespaces that existed earlier in the current month but have since been deleted.
|
||||
- For users, there is a guide that explains how billing works: ["Understanding billing for {% data variables.product.prodname_github_codespaces %}"](/codespaces/codespaces-reference/understanding-billing-for-github-codespaces)
|
||||
|
||||
## Usage limits
|
||||
|
||||
You can set a usage limit for the codespaces in your organization or repository. This limit is applied to the compute and storage usage for {% data variables.product.prodname_github_codespaces %}:
|
||||
|
||||
- **Compute minutes:** Compute usage is calculated by the actual number of minutes used by all {% data variables.product.prodname_github_codespaces %} instances while they are active. These totals are reported to the billing service daily, and is billed monthly. You can set a spending limit for {% data variables.product.prodname_github_codespaces %} usage in your organization. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
- **Storage usage:** For {% data variables.product.prodname_github_codespaces %} billing purposes, this includes all storage used by all codespaces in your account. This includes resources such as cloned repositories, configuration files, and extensions, among others. These totals are reported to the billing service daily, and is billed monthly. At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. To check how many compute minutes and storage GB have been used by {% data variables.product.prodname_github_codespaces %}, see "[Viewing your {% data variables.product.prodname_github_codespaces %} usage"](/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage)."
|
||||
|
||||
## Disabling or limiting {% data variables.product.prodname_codespaces %}
|
||||
|
||||
You can disable all use of {% data variables.product.prodname_github_codespaces %} that would be billed to your organization. Alternatively, you can specify which organization members or collaborators can use {% data variables.product.prodname_codespaces %} at your organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-disabling-org-billing %}
|
||||
|
||||
You can configure which repositories can be accessed from codespaces created for a particular repository. For more information, see "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces)."
|
||||
|
||||
You can limit the choice of types of machine that are available for codespaces created from repositories owned by your organization. This allows you to prevent people using overly resourced machines for their codespaces, and incurring unnecessary charges. For more information, see "[Restricting access to machine types](/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types)."
|
||||
|
||||
You can also restrict how long a codespace can remain unused before it is automatically deleted. This can help to reduce storage costs for {% data variables.product.prodname_codespaces %}. For more information, see "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)."
|
||||
|
||||
## Deleting unused codespaces
|
||||
|
||||
Your users can delete their own codespaces in https://github.com/codespaces and from within {% data variables.product.prodname_vscode %}. To reduce the size of a codespace, users can manually delete files using the terminal or from within {% data variables.product.prodname_vscode_shortname %}.
|
||||
|
||||
As an organization owner, you can delete any codespace in your organization. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Codespaces are automatically deleted after they have been stopped and have remained inactive for a defined number of days. For more information, see "[Restricting the retention period for codespaces](/codespaces/managing-codespaces-for-your-organization/restricting-the-retention-period-for-codespaces)." A codespace can only be manually deleted by the person who created the codespace.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Listing the codespaces in your organization](/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization)"
|
||||
@@ -40,6 +40,8 @@ You can also personalize aspects of your codespace environment by using a public
|
||||
|
||||
For information on pricing, storage, and usage for {% data variables.product.prodname_github_codespaces %}, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
{% data reusables.codespaces.codespaces-spending-limit-requirement %}
|
||||
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_github_codespaces %} for an organization, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)."
|
||||
|
||||
You can see who will pay for a codespace before you create it. For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)."
|
||||
@@ -14,7 +14,9 @@ redirect_from:
|
||||
|
||||
## Overview
|
||||
|
||||
Prebuilding your codespaces allows you to be more productive and access your codespace faster, particularly if your repository is large or complex and new codespaces currently take more than 2 minutes to start. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace.
|
||||
{% data reusables.codespaces.prebuilds-definition %}
|
||||
|
||||
If it currently takes more than 2 minutes to create a codespace for a repository, you are likely to benefit from using prebuilds. This is because, with a prebuild, any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace.
|
||||
|
||||
By default, whenever you push changes to your repository, {% data variables.product.prodname_github_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds.
|
||||
|
||||
@@ -28,16 +30,10 @@ To create a prebuild you set up a prebuild configuration. When you save the conf
|
||||
|
||||
When a prebuild configuration workflow runs, {% data variables.product.prodname_dotcom %} creates a temporary codespace, performing setup operations up to and including any `onCreateCommand` and `updateContentCommand` commands in the `devcontainer.json` file. No `postCreateCommand` commands are run during the creation of a prebuild. For more information about these commands, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation. A snapshot of the generated container is then taken and stored.
|
||||
|
||||
As with other Actions workflows, running a prebuild configuration workflow will either consume some of the Actions minutes included with your account, if you have any, or it will incur charges for Actions minutes. Storage of codespace prebuilds is billed in the same way as storage of active or stopped codespaces. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
|
||||
|
||||
When you create a codespace from a prebuild, {% data variables.product.prodname_dotcom %} downloads the existing container snapshot from storage and deploys it on a fresh virtual machine, completing the remaining commands specified in the dev container configuration. Since many operations have already been performed, such as cloning the repository, creating a codespace from a prebuild can be substantially quicker than creating one without a prebuild. This is true where the repository is large and/or `onCreateCommand` commands take a long time to run.
|
||||
|
||||
## About billing for {% data variables.product.prodname_codespaces %} prebuilds
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-default %} For details of {% data variables.product.prodname_github_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.billing-for-prebuilds-reducing %}
|
||||
|
||||
Use of codespaces created using prebuilds is charged at the same rate as regular codespaces.
|
||||
|
||||
## About pushing changes to prebuild-enabled branches
|
||||
|
||||
By default, each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)." If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes.
|
||||
|
||||
@@ -61,7 +61,7 @@ Before you can configure prebuilds for your project the following must be true:
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
* The prebuild for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_github_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)."
|
||||
* The prebuild for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
|
||||
* Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 自動リンクされた参照と URL
|
||||
intro: URL、Issue、プルリクエスト、コミットへの参照は、自動的に短縮されてリンクに変換されます。
|
||||
title: Autolinked references and URLs
|
||||
intro: 'References to URLs, issues, pull requests, and commits are automatically shortened and converted into links.'
|
||||
redirect_from:
|
||||
- /articles/autolinked-references-and-urls
|
||||
- /github/writing-on-github/autolinked-references-and-urls
|
||||
@@ -11,68 +11,68 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Auto linked references
|
||||
ms.openlocfilehash: 6f6548dbe931a7a6adb809aa4e5616db4358c242
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147419690'
|
||||
---
|
||||
## URL
|
||||
## URLs
|
||||
|
||||
{% data variables.product.product_name %}は自動的に標準的な URL からリンクを生成します。
|
||||
{% data variables.product.product_name %} automatically creates links from standard URLs.
|
||||
|
||||
`Visit https://github.com`
|
||||
|
||||
|
||||
|
||||
|
||||
リンクの作成の詳細については、「[基本的な書き方とフォーマットの構文](/articles/basic-writing-and-formatting-syntax/#links)」を参照してください。
|
||||
For more information on creating links, see "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax/#links)."
|
||||
|
||||
## Issue およびプルリクエスト
|
||||
## Issues and pull requests
|
||||
|
||||
{% data variables.product.product_name %} 上の会話の中では、Issue やプルリクエストへの参照は自動的に短縮リンクに変換されます。
|
||||
Within conversations on {% data variables.product.product_name %}, references to issues and pull requests are automatically converted to shortened links.
|
||||
|
||||
{% note %}
|
||||
|
||||
**メモ:** 自動リンクされた参照は、ウィキやリポジトリ中のファイルでは作成されません。
|
||||
**Note:** Autolinked references are not created in wikis or files in a repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
| 参照の種類 | 未処理の参照 | ショート リンク |
|
||||
| Reference type | Raw reference | Short link |
|
||||
| --- | --- | --- |
|
||||
| イシューまたは pull request の URL | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `#` と、イシューまたは pull request の番号 | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `GH-` と、イシューまたは pull request の番号 | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `Username/Repository#` と、イシューまたは pull request の番号 | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `Organization_name/Repository#` と、イシューまたは pull request の番号 | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039)
|
||||
| Issue or pull request URL | https://github.com/jlord/sheetsee.js/issues/26 | [#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `#` and issue or pull request number | #26 | [#26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `GH-` and issue or pull request number | GH-26 | [GH-26](https://github.com/jlord/sheetsee.js/issues/26) |
|
||||
| `Username/Repository#` and issue or pull request number | jlord/sheetsee.js#26 | [jlord/sheetsee.js#26](https://github.com/jlord/sheetsee.js/issues/26)
|
||||
| `Organization_name/Repository#` and issue or pull request number | github/linguist#4039 | [github/linguist#4039](https://github.com/github/linguist/pull/4039)
|
||||
|
||||
{% ifversion fpt or ghec %} リストで issue、pull request、ディスカッションを参照すると、その参照はタイトルと状態を表示するように展開されます。 タスク リストの詳細については、「[タスク リストについて](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)」を参照してください。
|
||||
{% ifversion fpt or ghec %}
|
||||
If you reference an issue, pull request, or discussion in a list, the reference will unfurl to show the title and state instead. For more information about task lists, see "[About task lists](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)."
|
||||
{% endif %}
|
||||
|
||||
## ラベル
|
||||
Markdown でラベルの URL を参照すると、ラベルが自動的にレンダリングされます。 同じリポジトリのラベルのみがレンダリングされ、別のリポジトリのラベルを指す URL は任意の [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls) としてレンダリングされます。
|
||||
## Labels
|
||||
When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
|
||||
|
||||
ラベルの URL は、ラベル ページに移動し、ラベルをクリックすることで見つけることができます。 たとえば、パブリック [ドキュメント リポジトリ](https://github.com/github/docs/)内のラベル "enhancement" の URL は次のようになります
|
||||
The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
|
||||
|
||||
```md
|
||||
https://github.com/github/docs/labels/enhancement
|
||||
```
|
||||
{% note %}
|
||||
|
||||
## コミット SHA
|
||||
**Note:** If the label name contains a period (`.`), the label will not automatically render from the label URL.
|
||||
|
||||
コミットの SHA ハッシュへの参照は、{% data variables.product.product_name %}上のコミットへの短縮リンクに自動的に変換されます。
|
||||
{% endnote %}
|
||||
|
||||
| 参照の種類 | 未処理の参照 | ショート リンク |
|
||||
## Commit SHAs
|
||||
|
||||
References to a commit's SHA hash are automatically converted into shortened links to the commit on {% data variables.product.product_name %}.
|
||||
|
||||
| Reference type | Raw reference | Short link |
|
||||
| --- | --- | --- |
|
||||
| コミット URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| Commit URL | [`https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| SHA | a5c3785ed8d6a35868bc169f07e40e889087fd2e | [a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
| User@SHA | jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e | [jlord@a5c3785](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e)
|
||||
| `Username/Repository@SHA` | `jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e` | [`jlord/sheetsee.js@a5c3785`](https://github.com/jlord/sheetsee.js/commit/a5c3785ed8d6a35868bc169f07e40e889087fd2e) |
|
||||
|
||||
## 外部リソースへのカスタム自動リンク
|
||||
## Custom autolinks to external resources
|
||||
|
||||
{% data reusables.repositories.autolink-references %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- [Basic writing and formatting syntax (基本的な書き方とフォーマットの構文)](/articles/basic-writing-and-formatting-syntax)
|
||||
- "[Basic writing and formatting syntax](/articles/basic-writing-and-formatting-syntax)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Packagesの権限について
|
||||
intro: パッケージの権限の管理方法を学んでください。
|
||||
title: About permissions for GitHub Packages
|
||||
intro: Learn about how to manage permissions for your packages.
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -8,83 +8,80 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: About permissions
|
||||
ms.openlocfilehash: 1663fa3bfc8fd6149e43fd9cf09a8362739c7341
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147704940'
|
||||
---
|
||||
{% ifversion fpt or ghec %} パッケージの権限は、リポジトリ スコープかユーザー/組織スコープです。
|
||||
{% endif %}
|
||||
|
||||
## リポジトリスコープのパッケージの権限
|
||||
|
||||
リポジトリスコープのパッケージは、パッケージを所有するリポジトリの権限と可視性を継承します。 リポジトリをスコープとするパッケージは、リポジトリのメインページにアクセスし、ページ右にある **パッケージ** リンクをクリックすれば見つかります。 {% ifversion fpt or ghec %}詳細については、「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。{% endif %}
|
||||
|
||||
以下の {% data variables.product.prodname_registry %} レジストリでは、リポジトリ スコープのアクセス許可 **のみ** を使います。
|
||||
|
||||
{% ifversion not fpt or ghec %}- Docker レジストリ (`docker.pkg.github.com`){% endif %} {% ifversion packages-npm-v2 %}{% else %}- npm レジストリ{% endif %}
|
||||
- RubyGemsレジストリ
|
||||
- Apache Mavenレジストリ
|
||||
- NuGetレジストリ
|
||||
|
||||
{% ifversion packages-npm-v2 %}{% data variables.product.prodname_ghcr_and_npm_registry %}の場合、パッケージのスコープをユーザー、組織に設定、またはリポジトリにリンクすることを許可できます。{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## ユーザ/Organizationスコープのパッケージの詳細な権限
|
||||
The permissions for packages are either repository-scoped or user/organization-scoped.
|
||||
{% endif %}
|
||||
|
||||
詳細な権限を持つパッケージは、個人ユーザもしくはOrganizationアカウントをスコープとします。 パッケージのアクセス制御と可視性は、パッケージに接続された（あるいはリンクされた）リポジトリは別個に変更できます。
|
||||
## Permissions for repository-scoped packages
|
||||
|
||||
現在のところ、{% data variables.product.prodname_ghcr_and_npm_registry %}でコンテナ イメージ パッケージに関する細かいアクセス許可を提供しています。
|
||||
A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
|
||||
|
||||
## コンテナイメージの可視性とアクセス権限
|
||||
The {% data variables.product.prodname_registry %} registries below **only** use repository-scoped permissions:
|
||||
|
||||
{% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
|
||||
{% ifversion packages-npm-v2 %}{% else %}- npm registry{% endif %}
|
||||
- RubyGems registry
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Granular permissions for user/organization-scoped packages
|
||||
|
||||
Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
|
||||
|
||||
Currently, the {% data variables.packages.prodname_ghcr_and_npm_registry %} offer granular permissions for your container image packages.
|
||||
|
||||
## Visibility and access permissions for container images
|
||||
|
||||
{% data reusables.package_registry.visibility-and-access-permissions %}
|
||||
|
||||
詳細については、「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
|
||||
For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## パッケージの管理
|
||||
## About scopes and permissions for package registries
|
||||
|
||||
パッケージ レジストリでホストされているパッケージを使用もしくは管理するためには、適切なスコープを持つトークンを使わなければならず、個人用アカウントが適切な権限を持っていなければなりません。
|
||||
To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your personal account must have appropriate permissions.
|
||||
|
||||
次に例を示します。
|
||||
- リポジトリからパッケージをダウンロードしてインストールするには、トークンに `read:packages` スコープが設定されていなければならず、ユーザー アカウントには読み取り権限が設定されていなければなりません。
|
||||
- {% ifversion fpt or ghes or ghec %}{% data variables.product.product_name %} 上のパッケージを削除するには、ご利用のトークンに少なくとも `delete:packages` および `read:packages` スコープが設定されている必要があります。 リポジトリをスコープとするパッケージには、`repo` スコープも必要です。 詳細については、「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。{% elsif ghae %}{% data variables.product.product_name %} で指定したバージョンのパッケージを削除するには、ご利用のトークンに `delete:packages` および `repo` スコープが設定されている必要があります。 詳細については、「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。{% endif %}
|
||||
For example:
|
||||
- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
|
||||
- {% ifversion fpt or ghes or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
|
||||
| Scope | 説明 | 必要な権限 |
|
||||
| Scope | Description | Required permission |
|
||||
| --- | --- | --- |
|
||||
|`read:packages`| {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り |
|
||||
|`write:packages`| {% data variables.product.prodname_registry %}へのパッケージのアップロードと公開 | 書き込み |
|
||||
| `delete:packages` | {% ifversion fpt or ghes or ghec %} {% data variables.product.prodname_registry %}からのパッケージの削除{% elsif ghae %}{% data variables.product.prodname_registry %}からの指定したバージョンのパッケージの削除{% endif %} | admin |
|
||||
| `repo` | パッケージをアップロードおよび削除する (`write:packages` または `delete:packages` と一緒に) | 書き込みもしくは読み取り |
|
||||
|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read |
|
||||
|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write |
|
||||
| `delete:packages` | {% ifversion fpt or ghes or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin |
|
||||
| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin |
|
||||
|
||||
{% data variables.product.prodname_actions %} ワークフローを作成する際には、`GITHUB_TOKEN` を使って {% data variables.product.prodname_registry %} にパッケージを公開してインストールでき、個人用アクセス トークンを保存して管理する必要はありません。
|
||||
When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
|
||||
|
||||
詳細については、以下を参照してください: {% ifversion fpt or ghec %}
|
||||
- "[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
|
||||
- "[{% data variables.product.prodname_actions %} を使用したパッケージの発行とインストール](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
|
||||
- 「[個人用アクセス トークンを作成する](/github/authenticating-to-github/creating-a-personal-access-token/)」
|
||||
- "[利用できるスコープ](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
|
||||
For more information, see:{% ifversion fpt or ghec %}
|
||||
- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
|
||||
- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
|
||||
- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
|
||||
- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
|
||||
|
||||
## {% data variables.product.prodname_actions %}ワークフローでのパッケージへのアクセスのメンテナンス
|
||||
## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
|
||||
|
||||
ワークフローがパッケージへのアクセスを確実に維持するためには、確実にワークフローで正しいアクセストークンを使用し、パッケージへの{% data variables.product.prodname_actions %}アクセスを有効化してください。
|
||||
To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
|
||||
|
||||
{% data variables.product.prodname_actions %} の概念的背景や、ワークフローでパッケージを使用する例については、「[GitHub Actions ワークフローを利用した GitHub Packages の管理](/packages/managing-github-packages-using-github-actions-workflows)」を参照してください。
|
||||
For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
|
||||
|
||||
### アクセス トークン
|
||||
### Access tokens
|
||||
|
||||
- ワークフロー リポジトリに関連付けられているパッケージを発行するには、`GITHUB_TOKEN` を使用します。
|
||||
- `GITHUB_TOKEN`がアクセスできない他のプライベート リポジトリに関連するパッケージをインストールするには、個人用アクセス トークンを使用してください。
|
||||
- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
|
||||
- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
|
||||
|
||||
{% data variables.product.prodname_actions %} ワークフローで使用される `GITHUB_TOKEN` の詳細については、「[ワークフローで認証する](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
|
||||
For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### コンテナイメージに対する{% data variables.product.prodname_actions %}アクセス
|
||||
### {% data variables.product.prodname_actions %} access for container images
|
||||
|
||||
ワークフローがコンテナイメージに確実にアクセスできるようにするには、ワークフローが実行されるリポジトリへの{% data variables.product.prodname_actions %}アクセスを有効化しなければなりません。 この設定は、パッケージの設定ページにあります。 詳細については、「[パッケージへのワークフローのアクセスの確保](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)」を参照してください。
|
||||
To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -15,7 +15,7 @@ shortTitle: Access control & visibility
|
||||
|
||||
Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of a package separately from the repository that it is connected (or linked) to.
|
||||
|
||||
Currently, you can only use granular permissions with the {% data variables.product.prodname_ghcr_and_npm_registry %}. Granular permissions are not supported in our other package registries, such as the RubyGems registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
|
||||
Currently, you can only use granular permissions with the {% data variables.packages.prodname_ghcr_and_npm_registry %}. Granular permissions are not supported in our other package registries, such as the RubyGems registry.{% ifversion docker-ghcr-enterprise-migration %} For more information about migration to the {% data variables.product.prodname_container_registry %}, see "[Migrating to the {% data variables.product.prodname_container_registry %} from the Docker registry](/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry)."{% endif %}
|
||||
|
||||
For more information about permissions for repository-scoped packages, packages-related scopes for PATs, or managing permissions for your actions workflows, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages)."
|
||||
|
||||
@@ -105,7 +105,7 @@ To further customize access to your container image, see "[Configuring access to
|
||||
{% ifversion fpt or ghec %}
|
||||
## Ensuring {% data variables.product.prodname_github_codespaces %} access to your package
|
||||
|
||||
By default, a codespace can seamlessly access certain packages in the {% data variables.product.prodname_ghcr_and_npm_registry %}, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Allowing your codespace to access a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-container-registry-and-npm-registry)."
|
||||
By default, a codespace can seamlessly access certain packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, such as those published in the same repository with the **Inherit access** option selected. For more information on which access is automatically configured, see "[Allowing your codespace to access a private image registry](/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry#accessing-images-stored-in-container-registry-and-npm-registry)."
|
||||
|
||||
Otherwise, to ensure that a codespace has access to your package, you must grant access to the repository where the codespace is being launched.
|
||||
|
||||
|
||||
@@ -62,7 +62,7 @@ The {% data variables.product.prodname_registry %} registries below **only** use
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.product.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
{% ifversion packages-npm-v2 %}For {% data variables.packages.prodname_ghcr_and_npm_registry %}, you can choose to allow packages to be scoped to a user, an organization, or linked to a repository.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Packages の概要
|
||||
intro: '{% data variables.product.prodname_registry %} はソフトウェア パッケージのホスティング サービスであり、ソフトウェア パッケージをプライベートに{% ifversion ghae %}特定のユーザーに対して、または Enterprise に対して内部的に{% else %}またはパブリックに{% endif %}ホストでき、パッケージをプロジェクト中で依存関係として使えるようになります。'
|
||||
title: Introduction to GitHub Packages
|
||||
intro: '{% data variables.product.prodname_registry %} is a software package hosting service that allows you to host your software packages privately {% ifversion ghae %} for specified users or internally for your enterprise{% else %}or publicly{% endif %} and use packages as dependencies in your projects.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /articles/about-github-package-registry
|
||||
@@ -16,118 +16,122 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Introduction
|
||||
ms.openlocfilehash: a141c93378f836eebf5ff33b0ced482409d6e577
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147704948'
|
||||
---
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
## {% data variables.product.prodname_registry %} について
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
{% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
{% data variables.product.prodname_registry %} は、コンテナーやその他の依存関係を含むパッケージをホストおよび管理するためのプラットフォームです。 {% data variables.product.prodname_registry %}は、ソースコードとパッケージを 1 か所にまとめ、統合された権限管理{% ifversion fpt or ghec %}と支払い{% endif %}を提供し、{% data variables.product.product_name %} 上でのソフトウェア開発を一元化できるようにします。
|
||||
## About {% data variables.product.prodname_registry %}
|
||||
|
||||
{% data variables.product.prodname_registry %}は、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、webhookと統合して、コード、CI、デプロイメントのソリューションを含むエンドツーエンドのDevOpsワークフローを作成できます。
|
||||
{% data variables.product.prodname_registry %} is a platform for hosting and managing packages, including containers and other dependencies. {% data variables.product.prodname_registry %} combines your source code and packages in one place to provide integrated permissions management{% ifversion fpt or ghec %} and billing{% endif %}, so you can centralize your software development on {% data variables.product.product_name %}.
|
||||
|
||||
{% data variables.product.prodname_registry %}は、nmp、RubyGems、Apache Maven、Gradle、Docker、NuGetといった、広く使われているパッケージマネージャーに対する様々なパッケージレジストリを提供しています。 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} の {% data variables.product.prodname_container_registry %} はコンテナーに最適化されており、Docker と OCI イメージをサポートします。{% endif %} {% data variables.product.prodname_registry %} がサポートするさまざまなパッケージ レジストリについての詳しい情報は、「[{% data variables.product.prodname_registry %} レジストリの操作](/packages/working-with-a-github-packages-registry)」をご覧ください。
|
||||
You can integrate {% data variables.product.prodname_registry %} with {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs, {% data variables.product.prodname_actions %}, and webhooks to create an end-to-end DevOps workflow that includes your code, CI, and deployment solutions.
|
||||
|
||||
{% data variables.product.prodname_registry %} offers different package registries for commonly used package managers, such as npm, RubyGems, Apache Maven, Gradle, Docker, and NuGet. {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}'s {% data variables.product.prodname_container_registry %} is optimized for containers and supports Docker and OCI images.{% endif %} For more information on the different package registries that {% data variables.product.prodname_registry %} supports, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.product_name %}では、ライセンスのようなメタデータやパッケージのREADMEを表示したり、統計をダウンロードしたり、バージョン履歴を見たりできます。 詳しくは、「[パッケージの表示](/packages/manage-packages/viewing-packages)」をご覧ください。
|
||||
You can view a package's README, as well as metadata such as licensing, download statistics, version history, and more on {% data variables.product.product_name %}. For more information, see "[Viewing packages](/packages/manage-packages/viewing-packages)."
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% data variables.product.product_name %} での {% data variables.product.prodname_registry %} の構成について詳しくは、「[Enterprise 向けの {% data variables.product.prodname_registry %} を使い始める](/admin/packages/getting-started-with-github-packages-for-your-enterprise)」を参照してください。
|
||||
For more information about the configuration of {% data variables.product.prodname_registry %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
### パッケージの権限と可視性の概要
|
||||
### Overview of package permissions and visibility
|
||||
|
||||
| | |
|
||||
|--------------------|--------------------|
|
||||
| アクセス許可 | {% ifversion fpt or ghec %}パッケージの権限は、パッケージがホストされているリポジトリから継承したり、{% data variables.product.prodname_ghcr_and_npm_registry %}内のパッケージの場合は特定のユーザーまたは Organization アカウントに対して定義したりできます。 詳しくは、「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。 {% else %}それぞれのパッケージは、ホストされているリポジトリの権限を継承します。 <br> <br> たとえば、リポジトリの読み取り権限を持つ人であれば、プロジェクトに依存関係としてパッケージをインストールでき、書き込み権限を持つ人であれば、新しいパッケージバージョンを公開できます。{% endif %} |
|
||||
| 視程 | {% data reusables.package_registry.public-or-private-packages %} |
|
||||
| Permissions | {% ifversion fpt or ghec %}The permissions for a package are either inherited from the repository where the package is hosted or, for packages in the {% data variables.packages.prodname_ghcr_and_npm_registry %}, they can be defined for specific user or organization accounts. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)." {% else %}Each package inherits the permissions of the repository where the package is hosted. <br> <br> For example, anyone with read permissions for a repository can install a package as a dependency in a project, and anyone with write permissions can publish a new package version.{% endif %} |
|
||||
| Visibility | {% data reusables.package_registry.public-or-private-packages %} |
|
||||
|
||||
詳細については、「[{% data variables.product.prodname_registry %} のアクセス許可について](/packages/learn-github-packages/about-permissions-for-github-packages)」を参照してください。
|
||||
For more information, see "[About permissions for {% data variables.product.prodname_registry %}](/packages/learn-github-packages/about-permissions-for-github-packages)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## {% data variables.product.prodname_registry %} の請求について
|
||||
## About billing for {% data variables.product.prodname_registry %}
|
||||
|
||||
{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} 詳しくは、「[{% data variables.product.prodname_registry %} の請求について](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。
|
||||
{% data reusables.package_registry.packages-billing %} {% data reusables.package_registry.packages-spending-limit-brief %} For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## サポートされているクライアントとフォーマット
|
||||
## Supported clients and formats
|
||||
<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
|
||||
|
||||
{% data variables.product.prodname_registry %}は、パッケージのバージョンの公開とインストールに、すでにおなじみのネイティブのパッケージツールコマンドを使います。
|
||||
### パッケージレジストリのサポート
|
||||
{% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
|
||||
### Support for package registries
|
||||
|
||||
| Language | 説明 | パッケージの形式 | パッケージクライアント |
|
||||
| Language | Description | Package format | Package client |
|
||||
| --- | --- | --- | --- |
|
||||
| JavaScript | Nodeのパッケージマネージャー | `package.json` | `npm` |
|
||||
| Ruby | RubyGemsパッケージマネージャー | `Gemfile` | `gem` |
|
||||
| Java | Apache Mavenのプロジェクト管理及び包括的ツール | `pom.xml` | `mvn` |
|
||||
| Java | Java用のGradleビルド自動化ツール | `build.gradle` または `build.gradle.kts` | `gradle` |
|
||||
| .NET | .NET用のNuGetパッケージ管理 | `nupkg` | `dotnet` CLI |
|
||||
| 該当なし | Dockerコンテナ管理プラットフォーム | `Dockerfile` | `Docker` |
|
||||
| JavaScript | Node package manager | `package.json` | `npm` |
|
||||
| Ruby | RubyGems package manager | `Gemfile` | `gem` |
|
||||
| Java | Apache Maven project management and comprehension tool | `pom.xml` | `mvn` |
|
||||
| Java | Gradle build automation tool for Java | `build.gradle` or `build.gradle.kts` | `gradle` |
|
||||
| .NET | NuGet package management for .NET | `nupkg` | `dotnet` CLI |
|
||||
| N/A | Docker container management | `Dockerfile` | `Docker` |
|
||||
|
||||
{% ifversion ghes %} {% note %}
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
|
||||
**注:** Docker レジストリを有効にする場合は、サブドメインの分離も有効にすることを強くお勧めします。 詳細については、「[サブドメイン分離の有効化](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)」を参照してください。
|
||||
**Note:** When enabling the Docker registry, we highly recommend also enabling subdomain isolation. For more information, see "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.prodname_registry %} と使用するようにパッケージ クライアントを構成する方法について詳しくは、「[{% data variables.product.prodname_registry %} レジストリの操作](/packages/working-with-a-github-packages-registry)」をご覧ください。
|
||||
For more information about configuring your package client for use with {% data variables.product.prodname_registry %}, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
|
||||
|
||||
{% ifversion fpt or ghec %}Docker と {% data variables.product.prodname_container_registry %} について詳しくは、「[コンテナー レジストリの操作](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)」を参照してください。
|
||||
{% ifversion fpt or ghec %}
|
||||
For more information about Docker and the {% data variables.product.prodname_container_registry %}, see "[Working with the Container registry](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
|
||||
{% endif %}
|
||||
## {% data variables.product.prodname_registry %} への認証を行う
|
||||
## Authenticating to {% data variables.product.prodname_registry %}
|
||||
|
||||
{% data reusables.package_registry.authenticate-packages %}
|
||||
|
||||
{% data reusables.package_registry.authenticate-packages-github-token %}
|
||||
|
||||
## パッケージを管理する
|
||||
## Managing packages
|
||||
|
||||
{% ifversion fpt or ghec %}{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} ユーザー インターフェイスまたは REST API を使用して、パッケージを削除できます。 詳しくは、「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」および [{% data variables.product.prodname_registry %} API](/rest/reference/packages) に関するページをご覧ください。
|
||||
{% ifversion fpt or ghec %}
|
||||
You can delete a package in the {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} user interface or using the REST API. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and the "[{% data variables.product.prodname_registry %} API](/rest/reference/packages)."
|
||||
|
||||
{% data reusables.package_registry.no-graphql-to-delete-packages %} {% endif %}
|
||||
|
||||
{% ifversion ghes %} {% data variables.product.product_name %} のユーザー インターフェイスでは、非公開あるいはパブリック パッケージを削除できます。 また、repoスコープのパッケージでは、GraphQLを使用してプライベートパッケージのバージョンを削除できます。
|
||||
{% data reusables.package_registry.no-graphql-to-delete-packages %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %} パッケージのバージョンは、{% data variables.product.product_name %} ユーザー インターフェイス内で、または GraphQL API を使って削除できます。
|
||||
{% ifversion ghes %}
|
||||
You can delete a private or public package in the {% data variables.product.product_name %} user interface. Or for repo-scoped packages, you can delete a version of a private package using GraphQL.
|
||||
{% endif %}
|
||||
|
||||
GraphQL APIを使ってプライベートパッケージに対するクエリや削除を行う場合、{% data variables.product.prodname_registry %}の認証に使うのと同じトークンを使わなければなりません。
|
||||
{% ifversion ghae %}
|
||||
You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
|
||||
{% endif %}
|
||||
|
||||
詳しくは、{% ifversion ghes or ghae %}「[パッケージを削除および復元する](/packages/learn-github-packages/deleting-and-restoring-a-package)」および{% endif %}「[GraphQL での呼び出しの作成](/graphql/guides/forming-calls-with-graphql)」をご覧ください。
|
||||
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}.
|
||||
|
||||
webhookを設定して、パッケージの公開や更新といったパッケージ関連のイベントにサブスクライブできます。 詳細については、「[`package` webhook イベント](/webhooks/event-payloads/#package)」を参照してください。
|
||||
For more information, see {% ifversion ghes or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and {% endif %}"[Forming calls with GraphQL](/graphql/guides/forming-calls-with-graphql)."
|
||||
|
||||
## サポートへの問い合わせ
|
||||
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
|
||||
|
||||
{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} に対するフィードバックや機能の要求がある場合は、[{% data variables.product.prodname_github_community %} ディスカッション](https://github.com/orgs/community/discussions/categories/actions-and-packages)をお使いください。
|
||||
## Contacting support
|
||||
|
||||
次の場合は、[お問い合わせフォーム](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages)を使用して、{% data variables.product.prodname_registry %} について {% data variables.contact.github_support %} にお問い合わせください。
|
||||
{% ifversion fpt or ghec %}
|
||||
If you have feedback or feature requests for {% data variables.product.prodname_registry %}, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/actions-and-packages).
|
||||
|
||||
* ドキュメンテーションに反する何らかの体験をした時
|
||||
* 漠然とした、あるいは不明確なエラーを体験した時
|
||||
* GDPR違反、APIキー、個人を識別する情報といったセンシティブなデータを含むパッケージを公開した時
|
||||
Contact {% data variables.contact.github_support %} about {% data variables.product.prodname_registry %} using [our contact form](https://support.github.com/contact?form%5Bsubject%5D=Re:%20GitHub%20Packages) if:
|
||||
|
||||
{% else %}{% data variables.product.prodname_registry %} のサポートが必要な場合は、サイト管理者にお問い合わせください。
|
||||
* You experience anything that contradicts the documentation
|
||||
* You encounter vague or unclear errors
|
||||
* Your published package contains sensitive data, such as GDPR violations, API Keys, or personally identifying information
|
||||
|
||||
{% else %}
|
||||
If you need support for {% data variables.product.prodname_registry %}, please contact your site administrators.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: パッケージの表示
|
||||
intro: リポジトリに公開されたパッケージの詳細を表示し、Organization またはユーザごとに結果を絞り込むことができます。
|
||||
title: Viewing packages
|
||||
intro: 'You can see details about packages published to a repository, and narrow results by organization or user.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /articles/viewing-a-repositorys-packages
|
||||
@@ -14,54 +14,56 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
ms.openlocfilehash: 75e3d0a69a06274e803fc59affc959b2cb5abee3
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147704996'
|
||||
---
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
## リポジトリのパッケージを表示する
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
{% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
パッケージを見ることができるかどうかは、いくつかの要素に依存します。 デフォルトでは、公開したパッケージはすべて見ることができます。
|
||||
## About package views
|
||||
|
||||
リポジトリをスコープとするパッケージは、そのパッケージを所有するリポジトリから権限と可視性を継承します。 以下のレジストリでは、この種類のアクセス許可 **のみ** が使用されます。{% ifversion not fpt or ghec %}
|
||||
- Docker レジストリ (`docker.pkg.github.com`){% endif %} {% ifversion packages-npm-v2 %}{% else %}- npm レジストリ{% endif %}
|
||||
- RubyGemsレジストリ
|
||||
- Apache Mavenレジストリ
|
||||
- NuGetレジストリ
|
||||
Your ability to view a package depends on several factors. By default, you can view all packages you have published.
|
||||
|
||||
{% ifversion fpt or ghec %} {% data variables.product.prodname_ghcr_and_npm_registry %}では、個人ユーザーまたは組織アカウントが所有する各パッケージごとにカスタマイズできる、細かいアクセス許可と可視性設定のオプションが提供されます。 詳細な権限を利用することも、パッケージをレジストリに接続してその権限を継承することもできます。 詳細については、「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。
|
||||
Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below **only** use this type of permissions:{% ifversion not fpt or ghec %}
|
||||
- Docker registry (`docker.pkg.github.com`){% endif %}
|
||||
{% ifversion packages-npm-v2 %}{% else %}- npm registry{% endif %}
|
||||
- RubyGems registry
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry %} offer you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
|
||||
{% endif %}
|
||||
|
||||
詳細については、「[GitHub Packages の権限について](/packages/learn-github-packages/about-permissions-for-github-packages){% ifversion fpt or ghec %}」および「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}」を参照してください。
|
||||
For more information, see "[About permissions for GitHub Packages](/packages/learn-github-packages/about-permissions-for-github-packages){% ifversion fpt or ghec %}" and "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility){% endif %}."
|
||||
|
||||
{% data reusables.package_registry.package-page-info %}
|
||||
|
||||
## リポジトリのパッケージを表示する
|
||||
## Viewing a repository's packages
|
||||
|
||||
特定のリポジトリにあるパッケージを見つけて表示できます。
|
||||
You can find and view a package located in a particular repository.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Organization のパッケージを表示する
|
||||
|
||||
自分が所属するOrganizationのリポジトリにあるパッケージを見つけて表示できます。
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
|
||||
3. 組織名の下にある {% octicon "package" aria-label="The package icon" %} **[パッケージ]** をクリックします。
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.package_registry.packages-from-code-tab %}
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## パッケージを表示する
|
||||
## Viewing an organization's packages
|
||||
|
||||
すべてのOrganization及びリポジトリで、自分が公開したパッケージを見つけて表示できます。
|
||||
You can find and view a package located in the repositories of an organization you belong to.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} **Packages**.
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Viewing your packages
|
||||
|
||||
You can find and view any package you've published across all organizations and repositories.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. プロファイル ページの一番上のメイン ナビゲーションにある **[パッケージ]** をクリックします。
|
||||
![[プロジェクト] タブ](/assets/images/help/package-registry/user-packages-tab.png) {% data reusables.package_registry.navigate-to-packages %}
|
||||
2. On the top of the profile page, in the main navigation, click **Packages**.
|
||||
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- 「[パッケージを検索する](/search-github/searching-on-github/searching-for-packages)」
|
||||
- "[Searching for packages](/search-github/searching-on-github/searching-for-packages)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: GitHub Actionsでのパッケージの公開とインストール
|
||||
intro: '{% data variables.product.prodname_actions %}でのワークフローを、自動的にパッケージをに公開もしくは{% data variables.product.prodname_registry %}からインストールするように設定できます。'
|
||||
title: Publishing and installing a package with GitHub Actions
|
||||
intro: 'You can configure a workflow in {% data variables.product.prodname_actions %} to automatically publish or install a package from {% data variables.product.prodname_registry %}.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /github/managing-packages-with-github-packages/using-github-packages-with-github-actions
|
||||
@@ -12,84 +12,81 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Publish & install with Actions
|
||||
ms.openlocfilehash: 4996d6c180b3e54608184ce4c40b8e0595f60d3e
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147705044'
|
||||
---
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
## {% data variables.product.prodname_actions %}との{% data variables.product.prodname_registry %}について
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
{% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} 詳しい情報については「[{% data variables.product.prodname_actions %} について](/github/automating-your-workflow-with-github-actions/about-github-actions)」を参照してください。
|
||||
## About {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}
|
||||
|
||||
ワークフローの一部としてパッケージの公開やインストールを行うことで、リポジトリのCI及びCDの機能を拡張できます。
|
||||
{% data reusables.repositories.about-github-actions %} {% data reusables.repositories.actions-ci-cd %} For more information, see "[About {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/about-github-actions)."
|
||||
|
||||
You can extend the CI and CD capabilities of your repository by publishing or installing packages as part of your workflow.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### {% data variables.product.prodname_ghcr_and_npm_registry %} に対する認証
|
||||
### Authenticating to the {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
{% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.prodname_dotcom %} 上のパッケージレジストリを認証する
|
||||
### Authenticating to package registries on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% ifversion fpt or ghec %}ワークフローが {% data variables.product.prodname_registry %} に対して認証されるようにして、{% data variables.product.product_location %} 上の {% data variables.product.prodname_container_registry %} 以外のパッケージ レジストリにアクセスできるようにしたい場合は、{% else %}{% data variables.product.product_name %} 上のパッケージ レジストリに対して認証を行いたい場合は、{% endif %}、認証用の個人用アクセス トークンではなく、{% data variables.product.prodname_actions %} を有効化する際に {% data variables.product.product_name %} でリポジトリに対して自動的に作成される、`GITHUB_TOKEN` を使用することをお勧めします。 ワークフロー ファイルでこのアクセス トークンにアクセス許可を設定して、`contents` スコープに対する読み取りアクセス権と、`packages` スコープに対する書き込みアクセス権を付与する必要があります。 フォークの場合、`GITHUB_TOKEN` には親リポジトリの読み取りアクセス権が付与されます。 詳細については、「[GITHUB_TOKEN を使用した認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
|
||||
{% ifversion fpt or ghec %}If you want your workflow to authenticate to {% data variables.product.prodname_registry %} to access a package registry other than the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_location %}, then{% else %}To authenticate to package registries on {% data variables.product.product_name %},{% endif %} we recommend using the `GITHUB_TOKEN` that {% data variables.product.product_name %} automatically creates for your repository when you enable {% data variables.product.prodname_actions %} instead of a personal access token for authentication. You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. For forks, the `GITHUB_TOKEN` is granted read access for the parent repository. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
|
||||
|
||||
ワークフロー ファイル内の `GITHUB_TOKEN` は、{% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} コンテキストを使って参照できます。 詳細については、「[GITHUB_TOKEN を使用した認証](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)」を参照してください。
|
||||
You can reference the `GITHUB_TOKEN` in your workflow file using the {% raw %}`{{secrets.GITHUB_TOKEN}}`{% endraw %} context. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
|
||||
|
||||
## リポジトリが所有するパッケージに対する権限とパッケージアクセスについて
|
||||
## About permissions and package access for repository-owned packages
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** RubyGems、{% ifversion packages-npm-v2 %}{% else %}npm、{% endif %}Apache Maven、NuGet、{% ifversion fpt or ghec %}、Gradle{% else %}Gradle、名前空間 `docker.pkg.github.com` を使用する Docker パッケージ{% endif %}などの一部のレジストリでは、レポジトリ所有のパッケージのみが許可されます。 {% data variables.product.prodname_ghcr_and_npm_registry_full %} を使用すると、ユーザーまたは Organization がパッケージを所有できるようにするか、リポジトリにリンクできるようにするかを選択できます。
|
||||
**Note:** Some registries, such as RubyGems, {% ifversion packages-npm-v2 %}{% else %}npm, {% endif %}Apache Maven, NuGet, {% ifversion fpt or ghec %}and Gradle{% else %}Gradle, and Docker packages that use the package namespace `docker.pkg.github.com`{% endif %}, only allow repository-owned packages. With {% data variables.packages.prodname_ghcr_and_npm_registry_full %} you can choose to allow packages to be owned by a user, an organization, or linked to a repository.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
GitHub Actionsを有効化すると、GitHubはリポジトリにGitHub Appをインストールします。 `GITHUB_TOKEN` シークレットは、GitHub App インストール アクセス トークンです。 このインストールアクセストークンは、リポジトリにインストールされたGitHub Appの代わりに認証を受けるために使うことができます。 このトークンの権限は、ワークフローを含むリポジトリに限定されます。 詳細については、「[GITHUB_TOKEN のアクセス許可](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)」を参照してください。
|
||||
When you enable GitHub Actions, GitHub installs a GitHub App on your repository. The `GITHUB_TOKEN` secret is a GitHub App installation access token. You can use the installation access token to authenticate on behalf of the GitHub App installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#about-the-github_token-secret)."
|
||||
|
||||
{% data variables.product.prodname_registry %} を使用すると、{% data variables.product.prodname_actions %} ワークフローで利用できる `GITHUB_TOKEN` を通じてパッケージをプッシュしたりプルしたりできます。
|
||||
{% data variables.product.prodname_registry %} allows you to push and pull packages through the `GITHUB_TOKEN` available to a {% data variables.product.prodname_actions %} workflow.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## {% data variables.product.prodname_ghcr_and_npm_registry %} の権限とパッケージ アクセスについて
|
||||
## About permissions and package access for {% data variables.packages.prodname_ghcr_and_npm_registry %}
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry_full %} を使うと、ユーザーは Organization レベルの自立リソースとしてパッケージを作成し、管理できます。 Organization または個人アカウントがパッケージを所有でき、それぞれのパッケージへのアクセスはリポジトリ権限とは別にカスタマイズできます。
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry_full %} allows users to create and administer packages as free-standing resources at the organization level. Packages can be owned by an organization or personal account and you can customize access to each of your packages separately from repository permissions.
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} にアクセスするすべてのワークフローは、個人用アクセス トークンではなく `GITHUB_TOKEN` を使う必要があります。 セキュリティのベスト プラクティスについて詳しくは、「[GitHub Actions のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)」を参照してください。
|
||||
All workflows accessing the {% data variables.packages.prodname_ghcr_and_npm_registry %} should use the `GITHUB_TOKEN` instead of a personal access token. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
|
||||
|
||||
## ワークフローを通じて変更されたコンテナに対するデフォルトの権限及びアクセス設定
|
||||
## Default permissions and access settings for containers modified through workflows
|
||||
|
||||
ワークフローを通じてコンテナを作成、インストール、変更、削除する場合、管理者がワークフローに確実にアクセスできるようにするために使われるデフォルトの権限及びアクセス設定があります。 これらのアクセス設定も調整できます。
|
||||
When you create, install, modify, or delete a container through a workflow, there are some default permission and access settings used to ensure admins have access to the workflow. You can adjust these access settings as well.
|
||||
|
||||
たとえば既定では、ワークフローで `GITHUB_TOKEN` を使用してコンテナーが作成された場合:
|
||||
- コンテナはワークフローが実行されたリポジトリの可視性と権限モデルを継承します。
|
||||
- ワークフローが実行されたリポジトリの管理者は、コンテナが作成されるとそのコンテナの管理者になります。
|
||||
For example, by default if a workflow creates a container using the `GITHUB_TOKEN`, then:
|
||||
- The container inherits the visibility and permissions model of the repository where the workflow is run.
|
||||
- Repository admins where the workflow is run become the admins of the container once the container is created.
|
||||
|
||||
パッケージを管理するワークフローに対してデフォルトの権限の働き方の例は、もっとあります。
|
||||
These are more examples of how default permissions work for workflows that manage packages.
|
||||
|
||||
| {% data variables.product.prodname_actions %}ワークフロータスク | 既定のアクセス許可とアクセス |
|
||||
| {% data variables.product.prodname_actions %} workflow task | Default permissions and access |
|
||||
|----|----|
|
||||
| 既存のコンテナのダウンロード | - コンテナがパブリックなら、任意のリポジトリで実行された任意のワークフローがコンテナをダウンロードできる。 <br> - コンテナーがインターナルなら、エンタープライズ アカウントが所有する任意のリポジトリ内で実行されるすべてのワークフローがコンテナーをダウンロードできる。 エンタープライズが所有する組織の場合は、エンタープライズ内の任意のリポジトリを読み取ることができる <br> - コンテナーがプライベートなら、そのコンテナーへの読み取り権限を与えられているリポジトリ内で動作するワークフローのみが、そのコンテナーをダウンロードできる。 <br>
|
||||
| 新しいバージョンの既存のコンテナへのアップロード | - コンテナがプライベート、インターナル、パブリックなら、そのコンテナへの書き込み権限を与えられたリポジトリで動作するワークフローだけが新バージョンをそのコンテナにアップロードできる。
|
||||
| コンテナもしくはコンテナのバージョンの削除 | - コンテナがプライベート、インターナル、パブリックなら、削除権限を与えられたリポジトリ内で動作するワークフローのみがコンテナの既存のバージョンを削除できる。
|
||||
| Download an existing container | - If the container is public, any workflow running in any repository can download the container. <br> - If the container is internal, then all workflows running in any repository owned by the Enterprise account can download the container. For enterprise-owned organizations, you can read any repository in the enterprise <br> - If the container is private, only workflows running in repositories that are given read permission on that container can download the container. <br>
|
||||
| Upload a new version to an existing container | - If the container is private, internal, or public, only workflows running in repositories that are given write permission on that container can upload new versions to the container.
|
||||
| Delete a container or versions of a container | - If the container is private, internal, or public, only workflows running in repositories that are given delete permission can delete existing versions of the container.
|
||||
|
||||
コンテナへのアクセスをもっと詳細に調整したり、デフォルトの権限動作の一部を調整したりすることもできます。 詳しくは、「[パッケージのアクセス制御と可視性の設定](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)」を参照してください。
|
||||
You can also adjust access to containers in a more granular way or adjust some of the default permissions behavior. For more information, see "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## アクションを使ったパッケージの公開
|
||||
## Publishing a package using an action
|
||||
|
||||
継続的インテグレーション (CI) フローの一環として、{% data variables.product.prodname_actions %}を使用してパッケージを自動的に公開できます。 この継続的デプロイメント (CD) に対するアプローチにより、コードが品質基準を満たしている場合に新しいパッケージの作成を自動化できます。 たとえば、開発者が特定のブランチにプッシュするたびに CI テストを実行するワークフローを作成してはいかがでしょう。 テストにパスすると、このワークフローは新しいパッケージバージョンを{% data variables.product.prodname_registry %}に公開できます。
|
||||
You can use {% data variables.product.prodname_actions %} to automatically publish packages as part of your continuous integration (CI) flow. This approach to continuous deployment (CD) allows you to automate the creation of new package versions, if the code meets your quality standards. For example, you could create a workflow that runs CI tests every time a developer pushes code to a particular branch. If the tests pass, the workflow can publish a new package version to {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% data reusables.package_registry.actions-configuration %}
|
||||
|
||||
以下の例では、{% data variables.product.prodname_actions %}を使用してアプリケーションのビルド{% ifversion not fpt or ghec %}とテスト{% endif %}を行い、それから自動的にDockerイメージを作成して{% data variables.product.prodname_registry %}に公開する方法を示しています。
|
||||
The following example demonstrates how you can use {% data variables.product.prodname_actions %} to build {% ifversion not fpt or ghec %}and test{% endif %} your app, and then automatically create a Docker image and publish it to {% data variables.product.prodname_registry %}.
|
||||
|
||||
リポジトリに新しいワークフロー ファイル (`.github/workflows/deploy-image.yml` など) を作成し、以下の YAML を追加します。
|
||||
Create a new workflow file in your repository (such as `.github/workflows/deploy-image.yml`), and add the following YAML:
|
||||
|
||||
{% ifversion fpt or ghec %} {% data reusables.package_registry.publish-docker-image %}
|
||||
{% ifversion fpt or ghec %}
|
||||
{% data reusables.package_registry.publish-docker-image %}
|
||||
|
||||
{% else %}
|
||||
|
||||
@@ -166,12 +163,13 @@ jobs:
|
||||
```
|
||||
{% endif %}
|
||||
|
||||
上記に関連する設定については、次の表で説明しています。 ワークフロー内の各要素の詳細については、「[{% data variables.product.prodname_actions %} のワークフロー構文](/actions/reference/workflow-syntax-for-github-actions)」を参照してください。
|
||||
The relevant settings are explained in the following table. For full details about each element in a workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)."
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
on:
|
||||
push:
|
||||
branches: ['release']
|
||||
@@ -179,7 +177,7 @@ on:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
<code>release</code> というブランチに変更をプッシュするたびに、<code>Create and publish a Docker image</code> ワークフローを実行するよう設定します。
|
||||
Configures the <code>Create and publish a Docker image</code> workflow to run every time a change is pushed to the branch called <code>release</code>.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -196,7 +194,7 @@ env:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
ワークフローに2つのカスタムの環境変数を定義します。 これらは{% data variables.product.prodname_container_registry %}ドメイン、そしてこのワークフローがビルドするDockerイメージの名前として使われます。
|
||||
Defines two custom environment variables for the workflow. These are used for the {% data variables.product.prodname_container_registry %} domain, and a name for the Docker image that this workflow builds.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -211,7 +209,7 @@ jobs:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
このワークフロー中には1つのジョブがあります。 これは、Ubuntuの利用可能な最新バージョンで実行されるよう設定されています。
|
||||
There is a single job in this workflow. It's configured to run on the latest available version of Ubuntu.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -237,7 +235,7 @@ run-npm-build:
|
||||
|
||||
</td>
|
||||
<td>
|
||||
このジョブではNPMをインストールし、それをアプリケーションのビルドに使用します。
|
||||
This job installs NPM and uses it to build the app.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -272,13 +270,14 @@ run-npm-test:
|
||||
|
||||
</td>
|
||||
<td>
|
||||
このジョブでは <code>npm test</code> を使用してコードをテストします。 <code>needs: run-npm-build</code> コマンドにより、このジョブは <code>run-npm-build</code> ジョブに依存するようになります。
|
||||
This job uses <code>npm test</code> to test the code. The <code>needs: run-npm-build</code> command makes this job dependent on the <code>run-npm-build</code> job.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
build-and-push-image:
|
||||
runs-on: ubuntu-latest
|
||||
needs: run-npm-test
|
||||
@@ -286,7 +285,7 @@ build-and-push-image:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
このジョブはパッケージを公開します。 <code>needs: run-npm-test</code> コマンドにより、このジョブは <code>run-npm-test</code> ジョブに依存するようになります。
|
||||
This job publishes the package. The <code>needs: run-npm-test</code> command makes this job dependent on the <code>run-npm-test</code> job.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -294,7 +293,8 @@ build-and-push-image:
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
permissions:
|
||||
contents: read
|
||||
packages: write
|
||||
@@ -302,14 +302,15 @@ permissions:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
<code>GITHUB_TOKEN</code> に付与されているアクセス許可をこのジョブ内のアクション用に設定します。
|
||||
Sets the permissions granted to the <code>GITHUB_TOKEN</code> for the actions in this job.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
- name: Log in to the Container registry
|
||||
uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
|
||||
with:
|
||||
@@ -320,13 +321,14 @@ permissions:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
パッケージを公開するアカウントとパスワードを使ってレジストリにログインする <code>Log in to the {% data variables.product.prodname_container_registry %}</code> というステップを作成します。 いったん公開されると、パッケージはここで定めたアカウントが所有することになります。
|
||||
Creates a step called <code>Log in to the {% data variables.product.prodname_container_registry %}</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
- name: Extract metadata (tags, labels) for Docker
|
||||
id: meta
|
||||
uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
|
||||
@@ -336,14 +338,15 @@ permissions:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
このステップは <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> を使って、指定されたイメージに適用されるタグとラベルを抽出します。 <code>id</code> "meta"は、このステップの出力が以降のステップから参照できるようにします。 <code>images</code> の値は、タグとラベルのためのベース名を提供します。
|
||||
This step uses <code><a href="https://github.com/docker/metadata-action#about">docker/metadata-action</a></code> to extract tags and labels that will be applied to the specified image. The <code>id</code> "meta" allows the output of this step to be referenced in a subsequent step. The <code>images</code> value provides the base name for the tags and labels.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
{% else %}
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
- name: Log in to GitHub Docker Registry
|
||||
uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
|
||||
with:
|
||||
@@ -354,70 +357,75 @@ permissions:
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
パッケージを公開するアカウントとパスワードを使ってレジストリにログインする <code>Log in to GitHub Docker Registry</code> という新しいステップを作成します。 いったん公開されると、パッケージはここで定めたアカウントが所有することになります。
|
||||
Creates a new step called <code>Log in to GitHub Docker Registry</code>, which logs in to the registry using the account and password that will publish the packages. Once published, the packages are owned by the account defined here.
|
||||
</td>
|
||||
</tr>
|
||||
{% endif %}
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
- name: Build and push Docker image
|
||||
```
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
<code>Build and push Docker image</code> という新しいステップを作成します。 このステップは、<code>build-and-push-image</code> ジョブの一部として実行されます。
|
||||
Creates a new step called <code>Build and push Docker image</code>. This step runs as part of the <code>build-and-push-image</code> job.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
|
||||
```
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
Docker の <code>build-push-action</code> アクションを使用して、リポジトリの <code>Dockerfile</code> を元にイメージをビルドします。 ビルドが成功すると、イメージを{% data variables.product.prodname_registry %}にプッシュします。
|
||||
Uses the Docker <code>build-push-action</code> action to build the image, based on your repository's <code>Dockerfile</code>. If the build succeeds, it pushes the image to {% data variables.product.prodname_registry %}.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
with:
|
||||
```
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
必要なパラメーターを <code>build-push-action</code> アクションに送信します。 これらは以降の行で定義されます。
|
||||
Sends the required parameters to the <code>build-push-action</code> action. These are defined in the subsequent lines.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
context: .
|
||||
```
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
ビルドのコンテキストを、指定されたパス内にあるファイル群として定義します。 詳細については、「<a href="https://github.com/docker/build-push-action#usage">使用</a>」を参照してください。
|
||||
Defines the build's context as the set of files located in the specified path. For more information, see "<a href="https://github.com/docker/build-push-action#usage">Usage</a>."
|
||||
</td>
|
||||
</tr>
|
||||
{% endif %}
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
{% raw %} ```yaml
|
||||
{% raw %}
|
||||
```yaml
|
||||
push: true
|
||||
```
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
ビルドに成功したら、このイメージをレジストリにプッシュします。
|
||||
Pushes this image to the registry if it is built successfully.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
@@ -432,66 +440,73 @@ labels: ${{ steps.meta.outputs.labels }}
|
||||
{% endraw %}
|
||||
</td>
|
||||
<td>
|
||||
"meta"ステップで抽出されたタグとラベルを追加します。
|
||||
Adds the tags and labels extracted in the "meta" step.
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
{% else %}
|
||||
<tr>
|
||||
<td>
|
||||
{% ifversion ghae %} {% raw %} ```yaml
|
||||
{% ifversion ghae %}
|
||||
{% raw %}
|
||||
```yaml
|
||||
tags: |
|
||||
docker.YOUR-HOSTNAME.com/${{ github.repository }}/octo-image:${{ github.sha }}
|
||||
```
|
||||
{% endraw %} {% else %} {% raw %} ```yaml
|
||||
{% endraw %}
|
||||
{% else %}
|
||||
{% raw %}
|
||||
```yaml
|
||||
tags: |
|
||||
docker.pkg.github.com/${{ github.repository }}/octo-image:${{ github.sha }}
|
||||
```
|
||||
{% endraw %} {% endif %}
|
||||
{% endraw %}
|
||||
{% endif %}
|
||||
</td>
|
||||
<td>
|
||||
ワークフローをトリガーしたコミットのSHAでイメージにタグ付けします。
|
||||
Tags the image with the SHA of the commit that triggered the workflow.
|
||||
</td>
|
||||
</tr>
|
||||
{% endif %}
|
||||
|
||||
</table>
|
||||
|
||||
この新しいワークフローは、リポジトリの `release` という名前のブランチに変更をプッシュするたびに自動的に実行されます。 **[アクション]** タブで、この進捗を表示できます。
|
||||
This new workflow will run automatically every time you push a change to a branch named `release` in the repository. You can view the progress in the **Actions** tab.
|
||||
|
||||
ワークフローが完成すると、その数分後にリポジトリで新しいパッケージが表示されます。 使用可能なパッケージを見つけるには、「[リポジトリのパッケージを表示する](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)」を参照してください。
|
||||
A few minutes after the workflow has completed, the new package will visible in your repository. To find your available packages, see "[Viewing a repository's packages](/packages/publishing-and-managing-packages/viewing-packages#viewing-a-repositorys-packages)."
|
||||
|
||||
## アクションを使ったパッケージのインストール
|
||||
## Installing a package using an action
|
||||
|
||||
{% data variables.product.prodname_actions %}を使い、CIフローの一部としてパッケージをインストールできます。 たとえば、開発者がコードをプルリクエストにプッシュすると、いつでもワークフローが{% data variables.product.prodname_registry %}によってホストされているパッケージをダウンロードしてインストールすることで、依存関係を解決するようにワークフローを設定できます。 そして、ワークフローはその依存関係を必要とするCIテストを実行できます。
|
||||
You can install packages as part of your CI flow using {% data variables.product.prodname_actions %}. For example, you could configure a workflow so that anytime a developer pushes code to a pull request, the workflow resolves dependencies by downloading and installing packages hosted by {% data variables.product.prodname_registry %}. Then, the workflow can run CI tests that require the dependencies.
|
||||
|
||||
{% data variables.product.prodname_actions %} を通じて {% data variables.product.prodname_registry %} がホストするパッケージをインストールするには、`GITHUB_TOKEN` を使う際に最小限の設定もしくは追加の認証が必要です。{% ifversion fpt or ghec %}アクションがパッケージをインストールする場合、データ転送も無料です。 詳細については、「[{% data variables.product.prodname_registry %} の課金について](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)」を参照してください。{% endif %}
|
||||
Installing packages hosted by {% data variables.product.prodname_registry %} through {% data variables.product.prodname_actions %} requires minimal configuration or additional authentication when you use the `GITHUB_TOKEN`.{% ifversion fpt or ghec %} Data transfer is also free when an action installs a package. For more information, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."{% endif %}
|
||||
|
||||
{% data reusables.package_registry.actions-configuration %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## PAT を使用してレジストリにアクセスするワークフローのアップグレード
|
||||
## Upgrading a workflow that accesses a registry using a PAT
|
||||
|
||||
{% data variables.product.prodname_ghcr_and_npm_registry %} は、ワークフロー内での、簡単でセキュリティで保護された認証のために `GITHUB_TOKEN` をサポートしています。 お使いのワークフローで個人アクセス トークン (PAT) を使用してレジストリの認証を受ける場合、`GITHUB_TOKEN` を使用するようにワークフローを更新することを強くお勧めします。
|
||||
The {% data variables.packages.prodname_ghcr_and_npm_registry %} support the `GITHUB_TOKEN` for easy and secure authentication in your workflows. If your workflow is using a personal access token (PAT) to authenticate to the registry, then we highly recommend you update your workflow to use the `GITHUB_TOKEN`.
|
||||
|
||||
`GITHUB_TOKEN` の詳細については「[ワークフローで認証する](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)」を参照してください。
|
||||
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)."
|
||||
|
||||
PAT の代わりに `repo` スコープを含む `GITHUB_TOKEN` を使えば、ワークフローが実行されるリポジトリへの不要なアクセスを提供する長期間有効な PAT を使う必要がなくなるので、リポジトリのセキュリティが向上します。 セキュリティのベスト プラクティスについて詳しくは、「[GitHub Actions のセキュリティ強化](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)」を参照してください。
|
||||
Using the `GITHUB_TOKEN` instead of a PAT, which includes the `repo` scope, increases the security of your repository as you don't need to use a long-lived PAT that offers unnecessary access to the repository where your workflow is run. For more information about security best practices, see "[Security hardening for GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#using-secrets)."
|
||||
|
||||
1. パッケージのランディングページにアクセスしてください。
|
||||
1. 左側のサイドバーで、 **[アクションのアクセス]** をクリックします。
|
||||
![左側のメニューの [アクションのアクセス] オプション](/assets/images/help/package-registry/organization-repo-access-for-a-package.png)
|
||||
1. コンテナパッケージがワークフローに確実にアクセスできるようにするためには、ワークフローが保存されているリポジトリをコンテナに追加しなければなりません。 **[リポジトリの追加]** をクリックして、追加するリポジトリを検索します。
|
||||
![[リポジトリの追加] ボタン](/assets/images/help/package-registry/add-repository-button.png) {% note %}
|
||||
1. Navigate to your package landing page.
|
||||
1. In the left sidebar, click **Actions access**.
|
||||
|
||||
1. To ensure your container package has access to your workflow, you must add the repository where the workflow is stored to your container. Click **Add repository** and search for the repository you want to add.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** **[アクションのアクセス]** メニュー オプションを使用してコンテナーにリポジトリを追加する操作は、コンテナーをリポジトリに接続する操作とは異なります。 詳細については、「[パッケージへのワークフローのアクセスの確保](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)」と「[リポジトリのパッケージへの接続](/packages/learn-github-packages/connecting-a-repository-to-a-package)」を参照してください。
|
||||
**Note:** Adding a repository to your container through the **Actions access** menu option is different than connecting your container to a repository. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)" and "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."
|
||||
|
||||
{% endnote %}
|
||||
1. あるいは"role（ロール）"ドロップダウンメニューを使い、コンテナイメージに対してリポジトリに持たせたいデフォルトのアクセスレベルを選択してください。
|
||||
|
||||
1. ワークフローファイルを開いてください。 レジストリへのログインの行で、お使いの PAT を {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} に置き換えてください。
|
||||
1. Optionally, using the "role" drop-down menu, select the default access level that you'd like the repository to have to your container image.
|
||||
|
||||
1. Open your workflow file. On the line where you log in to the registry, replace your PAT with {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %}.
|
||||
|
||||
たとえば、このワークフローでは、Docker イメージを {% data variables.product.prodname_container_registry %} に公開し、{% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} を使って認証します。
|
||||
For example, this workflow publishes a Docker image to the {% data variables.product.prodname_container_registry %} and uses {% raw %}`${{ secrets.GITHUB_TOKEN }}`{% endraw %} to authenticate.
|
||||
|
||||
```yaml{:copy}
|
||||
name: Demo Push
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -8,7 +8,6 @@ topics:
|
||||
children:
|
||||
- /github-privacy-statement
|
||||
- /global-privacy-practices
|
||||
- /github-data-protection-agreement
|
||||
- /github-subprocessors-and-cookies
|
||||
- /github-codespaces-privacy-statement
|
||||
- /github-candidate-privacy-policy
|
||||
|
||||
@@ -1,11 +1 @@
|
||||
---
|
||||
ms.openlocfilehash: 39b050df26b1192db1f0d539b2bd789f90c022d1
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: "147763985"
|
||||
---
|
||||
プライベート リポジトリでは、{% data variables.actions.hosted_runner %} のみ使うことをお勧めします。
|
||||
- ワークフロー内でコードを実行する pull request を作成することで、リポジトリのフォークによって、{% data variables.actions.hosted_runner %} 上で危険なコードが実行される可能性があります。
|
||||
- フォークされたリポジトリを使って {% data variables.actions.hosted_runner %} 上でジョブを実行できるようにすると、予測しないコストが発生する可能性があります。
|
||||
If you are using a Fixed IP range, we recommend that you only use {% data variables.actions.hosted_runner %}s with private repositories. Forks of your repository can potentially run dangerous code on your {% data variables.actions.hosted_runner %} by creating a pull request that executes the code in a workflow.
|
||||
|
||||
@@ -1,11 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 0036dd5cf979531479a7ddf523c7475391b29c0a
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: "147548009"
|
||||
---
|
||||
既定では、プレビルドを作成または更新するたびに、またはプレビルドが有効なブランチにプッシュするたびに、{% data variables.product.prodname_actions %} ワークフローがトリガーされます。 他のワークフローと同様に、プレビルド ワークフローが実行されている間、アカウントに含まれているアクションの分数がある場合はその一部を消費するか、アクションの分数の料金が発生します。 アクション分の価格の詳細については、「[{% data variables.product.prodname_actions %} の課金について](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)」を参照してください。
|
||||
|
||||
{% data variables.product.prodname_actions %} の利用時間 (分) と併せて、特定のリポジトリとリージョンに対する各プレビルド構成に関連付けられているプレビルドのストレージについても課金されます。 プレビルドのストレージは、codespace のストレージと同じレートで課金されます。
|
||||
@@ -1,3 +0,0 @@
|
||||
To reduce consumption of Actions minutes, you can set a prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. You can also manage your storage usage by adjusting the number of template versions to be retained for your prebuild configurations. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-a-prebuild)."
|
||||
|
||||
If you are an organization or enterprise owner, you can track usage of prebuild workflows and storage by downloading a {% data variables.product.prodname_actions %} usage report for your organization or enterprise. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create {% data variables.product.prodname_github_codespaces %} Prebuilds." For more information, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)."
|
||||
@@ -1,17 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 845c770a8a03c57a4c10a84d28fd4d3d78282042
|
||||
ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "147111123"
|
||||
---
|
||||
{% data variables.product.prodname_codespaces %} は、コンピューティングとストレージの使用量に応じて米ドル (USD) で課金されます。
|
||||
|
||||
### コンピューティング使用量の計算
|
||||
コンピューティング使用量は、{% data variables.product.prodname_github_codespaces %} インスタンスがアクティブであるアップタイム時間 (分) の合計として定義されます。 コンピューティング使用量は、すべての codespace で実際に使われた分数を合計することで計算されます。 これらの合計は、毎日課金サービスに報告され、毎月請求されます。
|
||||
|
||||
アップタイムを制御するには、codespace を停止します。これは、手動で行うか、開発者が指定した非アクティブ期間の後に自動的に行うことができます。 詳細については、「[codespace の終了または停止](/codespaces/getting-started/deep-dive#closing-or-stopping-your-codespace)」を参照してください。
|
||||
|
||||
### ストレージ使用量の計算
|
||||
{% data variables.product.prodname_github_codespaces %} の課金目的の場合、アカウント内のすべての codespace で使用されるすべてのストレージが含まれます。 これには、codespace に使われるすべてのファイル (クローンされたリポジトリ、構成ファイル、拡張機能など) が含まれます。 これらの合計は、毎日課金サービスに報告され、毎月請求されます。 月末に、{% data variables.product.prodname_dotcom %}はストレージ使用量を最も近いGBに丸めます。
|
||||
@@ -5,5 +5,3 @@
|
||||
{% endnote %}
|
||||
|
||||
By default, your organization or enterprise will have a {% data variables.product.prodname_github_codespaces %} spending limit of $0. This prevents new codespaces from being created, or existing codespaces from being opened, if this would incur a billable cost to your organization or enterprise. To allow your users to create codespaces in your organization, set the limit to a value higher than $0.
|
||||
|
||||
{% data reusables.billing.overages-billed-monthly %}
|
||||
|
||||
@@ -1,11 +1,5 @@
|
||||
After you connect your account on {% data variables.product.product_location %} to the {% data variables.product.prodname_github_codespaces %} extension, you can create a new codespace. For more information about the {% data variables.product.prodname_github_codespaces %} extension, see the [{% data variables.product.prodname_vs_marketplace_shortname %} marketplace](https://marketplace.visualstudio.com/items?itemName=GitHub.codespaces).
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Currently, {% data variables.product.prodname_vscode_shortname %} doesn't allow you to choose a dev container configuration when you create a codespace. If you want to choose a specific dev container configuration, use the {% data variables.product.prodname_dotcom %} web interface to create your codespace. For more information, click the **Web browser** tab at the top of this page.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.click-remote-explorer-icon-vscode %}
|
||||
2. Click the Add icon: {% octicon "plus" aria-label="The plus icon" %}.
|
||||
|
||||
|
||||
@@ -1,9 +0,0 @@
|
||||
---
|
||||
ms.openlocfilehash: 86ebb6e0ab13cf7daf5fb580792bf8f4606eb054
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "147881917"
|
||||
---
|
||||
消費型サービスのコストを見積もるために、{% data variables.product.prodname_dotcom %} [料金計算ツール](https://github.com/pricing/calculator?feature=codespaces)を使用できます。
|
||||
@@ -83,6 +83,7 @@ translations/ja-JP/content/code-security/dependabot/dependabot-alerts/browsing-s
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,file deleted because it no longer exists in main
|
||||
@@ -93,6 +94,7 @@ translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-
|
||||
translations/ja-JP/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md,file deleted because it no longer exists in main
|
||||
@@ -181,6 +183,7 @@ translations/ja-JP/content/rest/reference/secret-scanning.md,file deleted becaus
|
||||
translations/ja-JP/content/rest/reference/teams.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/rest/reference/users.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/rest/reference/webhooks.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/site-policy/privacy-policies/github-data-protection-agreement.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/glossaries/internal.yml,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
|
||||
@@ -192,7 +195,10 @@ translations/ja-JP/data/reusables/billing/per-user-pricing-reference.md,file del
|
||||
translations/ja-JP/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/beta-functionality-limited.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds-default.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds-reducing.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/codespaces-billing.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/concurrent-codespace-limit.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
|
||||
@@ -200,6 +206,7 @@ translations/ja-JP/data/reusables/codespaces/unsupported-repos.md,file deleted b
|
||||
translations/ja-JP/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/education/upgrade-organization.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
|
||||
@@ -252,7 +259,7 @@ translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifi
|
||||
translations/ja-JP/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/setting-your-profile-to-private.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
|
||||
@@ -304,6 +311,7 @@ translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-
|
||||
translations/ja-JP/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,rendering error
|
||||
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-rate-limits.md,rendering error
|
||||
translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
|
||||
translations/ja-JP/content/admin/github-actions/advanced-configuration-and-troubleshooting/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled.md,broken liquid tags
|
||||
@@ -382,10 +390,9 @@ translations/ja-JP/content/code-security/supply-chain-security/understanding-you
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,rendering error
|
||||
translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,rendering error
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/disaster-recovery-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/using-github-copilot-in-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace.md,broken liquid tags
|
||||
@@ -404,7 +411,7 @@ translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-code
|
||||
translations/ja-JP/content/codespaces/developing-in-codespaces/using-github-codespaces-with-github-cli.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/getting-started/deep-dive.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/getting-started/quickstart.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/listing-the-codespaces-in-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces.md,rendering error
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md,rendering error
|
||||
translations/ja-JP/content/codespaces/managing-codespaces-for-your-organization/restricting-the-idle-timeout-period.md,rendering error
|
||||
@@ -465,6 +472,7 @@ translations/ja-JP/content/get-started/using-github/troubleshooting-connectivity
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error
|
||||
translations/ja-JP/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
|
||||
translations/ja-JP/content/graphql/overview/about-the-graphql-api.md,rendering error
|
||||
@@ -472,7 +480,7 @@ translations/ja-JP/content/issues/planning-and-tracking-with-projects/automating
|
||||
translations/ja-JP/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags
|
||||
translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
translations/ja-JP/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
|
||||
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/ja-JP/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error
|
||||
translations/ja-JP/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,rendering error
|
||||
@@ -491,8 +499,12 @@ translations/ja-JP/content/organizations/managing-peoples-access-to-your-organiz
|
||||
translations/ja-JP/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
|
||||
translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,broken liquid tags
|
||||
translations/ja-JP/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/packages/learn-github-packages/about-permissions-for-github-packages.md,broken liquid tags
|
||||
translations/ja-JP/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
|
||||
translations/ja-JP/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,rendering error
|
||||
translations/ja-JP/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
|
||||
translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md,broken liquid tags
|
||||
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/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
|
||||
translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
|
||||
translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
|
||||
@@ -582,6 +594,7 @@ translations/ja-JP/data/reusables/actions/changing-the-access-policy-of-a-runner
|
||||
translations/ja-JP/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/create-runner-group.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/hosted-runner-security.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/ref_name-description.md,broken liquid tags
|
||||
@@ -611,7 +624,6 @@ translations/ja-JP/data/reusables/code-scanning/autobuild-add-build-steps.md,bro
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
|
||||
translations/ja-JP/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
|
||||
translations/ja-JP/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/codespaces/billing-for-prebuilds-reducing.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/codespaces/codespaces-api-beta-note.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/codespaces/codespaces-policy-targets.md,rendering error
|
||||
translations/ja-JP/data/reusables/codespaces/codespaces-spending-limit-requirement.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user