зеркало из https://github.com/github/docs.git
New translation batch for ja (#31723)
This commit is contained in:
docubot
GitHub
Родитель
ff371ff29e
Коммит
1ca93007e6
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: ユーザを Organization に変換する
|
||||
title: Converting a user into an organization
|
||||
redirect_from:
|
||||
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
|
||||
- /articles/explaining-the-account-transformation-warning
|
||||
|
|
@ -8,7 +8,7 @@ redirect_from:
|
|||
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
|
||||
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
|
||||
intro: 個人アカウントを Organization に変換できます。 これにより、Organization に属するリポジトリに対して、より細かく権限を設定できます。
|
||||
intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -17,60 +17,58 @@ versions:
|
|||
topics:
|
||||
- Accounts
|
||||
shortTitle: User into an organization
|
||||
ms.openlocfilehash: 8b99bd119a9fa061c025a4fcc299d7ace31d23eb
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147687128'
|
||||
---
|
||||
{% warning %}
|
||||
|
||||
**警告**: ユーザーを Organization に変換する前に、以下の点にご注意ください。
|
||||
**Warning**: Before converting a user into an organization, keep these points in mind.
|
||||
|
||||
* 変換した個人アカウントには、サインイン **できなくなります**。
|
||||
* 変換した個人アカウントが所有していた gist を作成や変更することが **できなくなります**。
|
||||
* Organization からユーザーに変換 **することはできません**。
|
||||
* SSH キー、OAuth トークン、ジョブ プロフィール、リアクション、関連するユーザー情報は、Organization に移譲 **されません**。 これは、変換された個人アカウントのみに該当し、個人アカウントのコラボレーターには該当しません。
|
||||
* 変換した個人アカウントによるコミットは、アカウントに **リンクされなくなります**。 コミット自体はそのまま **残ります**。
|
||||
* 変換した個人アカウントによるあらゆる既存のコメントは、アカウントに **リンクされなくなります**。 コメント自体はそのまま **残ります** が、`ghost` ユーザーに関連付けられます。
|
||||
* 変換された個人アカウントで作成されたプライベート リポジトリのフォークはすべて削除されます。
|
||||
* You will **no longer** be able to sign into the converted personal account.
|
||||
* You will **no longer** be able to create or modify gists owned by the converted personal account.
|
||||
* An organization **cannot** be converted back to a user.
|
||||
* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
|
||||
* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
|
||||
* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
|
||||
* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
|
||||
* Any forks of private repositories made with the converted personal account will be deleted.
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
## 個人アカウントを保ち、新しい組織を手動で作成する
|
||||
## Keep your personal account and create a new organization manually
|
||||
|
||||
組織の名前を、個人アカウントが使用しているものと同じにしたい場合や、個人のアカウント情報をそのまま残しておきたい場合は、個人アカウントを組織に変換するのではなく、新しい組織を作成して、そこへリポジトリを移譲する必要があります。
|
||||
If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
|
||||
|
||||
1. 現在の個人アカウント名を個人的に使いたい場合は、[個人アカウント名を変更し](/articles/changing-your-github-username)、新しくて素敵な名前を付けましょう。
|
||||
2. 個人アカウントの元の名前で[新しい組織を作成](/articles/creating-a-new-organization-from-scratch)します。
|
||||
3. 新しい Organization アカウントに[リポジトリを転送します](/articles/transferring-a-repository)。{% endif %}
|
||||
1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
|
||||
2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
|
||||
3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
|
||||
|
||||
## 個人アカウントを Organization に自動で変換する
|
||||
## Convert your personal account into an organization automatically
|
||||
|
||||
個人アカウントを組織に直接変換することも可能です。 アカウントを変換すると、以下のことが起こります:
|
||||
- リポジトリはそのまま保持されます。他のアカウントに手動で移譲する必要はありません。
|
||||
- コラボレーターを、Team に自動的に招待します。コラボレーターの権限は、以前のものがそのまま引き継がれます。{% ifversion fpt or ghec %}- {% data variables.product.prodname_pro %} の個人アカウントでは、いつでも支払い情報の再入力、支払いサイクルの調整、二重支払いをすることなく、自動的に[有料 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) に移行できます。{% endif %}
|
||||
You can also convert your personal account directly into an organization. Converting your account:
|
||||
- Preserves the repositories as they are without the need to transfer them to another account manually
|
||||
- Automatically invites collaborators to teams with permissions equivalent to what they had before
|
||||
{% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
|
||||
|
||||
1. GitHub にサインインし、変換後に Organization やリポジトリにアクセスするために使う、新しい個人アカウントを作成します。
|
||||
2. 変換する個人アカウントが参加している[組織は、そのままにしておきます](/articles/removing-yourself-from-an-organization)。
|
||||
{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
|
||||
5. [アカウントの変換] で、 **[<username> を組織に変換]** をクリックします。
|
||||
|
||||
6. [Account Transformation Warning] ダイアログボックスで、変換に関する情報を読み、変換を確定します。 このボックスに記載されている情報は、この記事で上述したものと同じです。
|
||||
|
||||
7. [Transform your user into an organization] ページの、[Choose an organization owner] で、前のセクションで作成したセカンダリの個人アカウントか、Organization の管理を信頼して任せられる他のユーザを選択します。
|
||||
|
||||
8. 入力を求められた場合、Organization の新しいプランを選択し、支払い情報を入力します。
|
||||
9. **[Organization の作成]** をクリックします。
|
||||
10. ステップ 1 で作成した、新しい個人アカウントにサインインし、コンテキスト スイッチャーを使って新しい組織にアクセスします。
|
||||
1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
|
||||
2. [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
|
||||
{% data reusables.user-settings.access_settings %}
|
||||
{% data reusables.user-settings.organizations %}
|
||||
5. Under "Transform account", click **Turn <username> into an organization**.
|
||||
|
||||
6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
|
||||
|
||||
7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
|
||||
|
||||
8. Choose your new organization's subscription and enter your billing information if prompted.
|
||||
9. Click **Create Organization**.
|
||||
10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**: ユーザー アカウントを組織に変換した場合、アカウントに属していたリポジトリのコラボレーターは、新しい組織に *外部コラボレーター* として追加されます。 希望する場合は、*外部コラボレーター* を招待して新しい Organization のメンバーにすることができます。 詳細については、「[Organization のロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)」を参照してください。
|
||||
**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 参考資料
|
||||
- 「[Team の設定](/articles/setting-up-teams)」 {% ifversion fpt or ghec %}- [Organization にユーザーを招待する](/articles/inviting-users-to-join-your-organization){% endif %}
|
||||
- [Organization へのアクセス](/articles/accessing-an-organization)
|
||||
## Further reading
|
||||
- "[Setting up teams](/articles/setting-up-teams)"
|
||||
{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
|
||||
- "[Accessing an organization](/articles/accessing-an-organization)"
|
||||
|
|
|
|||
|
|
@ -791,7 +791,7 @@ jobs:
|
|||
{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
|
||||
## `inputs` context
|
||||
|
||||
The `inputs` context contains input properties passed to a reusable workflow{% ifversion actions-unified-inputs %} or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
|
||||
The `inputs` context contains input properties passed to an action{% ifversion actions-unified-inputs %},{% else %} or{% endif %} to a reusable workflow{% ifversion actions-unified-inputs %}, or to a manually triggered workflow{% endif %}. {% ifversion actions-unified-inputs %}For reusable workflows, the{% else %}The{% endif %} input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow. {% ifversion actions-unified-inputs %}For manually triggered workflows, the inputs are defined in the [`workflow_dispatch` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow_dispatch) of a workflow.{% endif %}
|
||||
|
||||
There are no standard properties in the `inputs` context, only those which are defined in the workflow file.
|
||||
|
||||
|
|
|
|||
|
|
@ -1,50 +1,65 @@
|
|||
---
|
||||
title: ワークフローの無効化と有効化
|
||||
intro: '{% data variables.product.prodname_dotcom %} UI、REST API、または {% data variables.product.prodname_cli %} を使用して、ワークフローを無効化したり再度有効化したりすることができます。'
|
||||
title: Disabling and enabling a workflow
|
||||
intro: 'You can disable and re-enable a workflow using the {% data variables.product.prodname_dotcom %} UI, the REST API, or {% data variables.product.prodname_cli %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Disable & enable a workflow
|
||||
ms.openlocfilehash: 1c0ebc0f56ba8c337648670e0f07d8a56e2fc326
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145125949'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
ワークフローを無効にすると、リポジトリからファイルを削除することなく、ワークフローがトリガーされないようにすることができます。 {% data variables.product.prodname_dotcom %} でワークフローを簡単に再度有効にすることができます。
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
ワークフローを一時的に無効にすると、多くのシナリオで役立つことがあります。 以下は、ワークフローを無効すると便利な場合の例の一部です。
|
||||
Disabling a workflow allows you to stop a workflow from being triggered without having to delete the file from the repo. You can easily re-enable the workflow again on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
- リクエストが多すぎるまたは間違っていて、外部サービスに悪影響を与えるワークフローエラー。
|
||||
- 重要ではないが、アカウントの時間を消費しすぎるワークフロー。
|
||||
- ダウンしているサービスにリクエストを送信するワークフロー。
|
||||
- フォークされたリポジトリ上の不要なワークフロー（スケジュールされたワークフローなど）。
|
||||
Temporarily disabling a workflow can be useful in many scenarios. These are a few examples where disabling a workflow might be helpful:
|
||||
|
||||
- A workflow error that produces too many or wrong requests, impacting external services negatively.
|
||||
- A workflow that is not critical and is consuming too many minutes on your account.
|
||||
- A workflow that sends requests to a service that is down.
|
||||
- Workflows on a forked repository that aren't needed (for example, scheduled workflows).
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告:** {% data reusables.actions.scheduled-workflows-disabled %}
|
||||
**Warning:** {% data reusables.actions.scheduled-workflows-disabled %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
REST API を使用して、ワークフローを無効化または有効化することもできます。 詳しくは、[Actions REST API](/rest/reference/actions#workflows) に関する記事をご覧ください。
|
||||
You can also disable and enable a workflow using the REST API. For more information, see the "[Actions REST API](/rest/reference/actions#workflows)."
|
||||
|
||||
## ワークフローの無効化
|
||||
## Disabling a workflow
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
|
||||
1. 左サイドバーで、無効にするワークフローをクリックします。
|
||||
|
||||
1. {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックします。
|
||||
|
||||
1. **[Disable workflow]\(ワークフローを無効にする\)** をクリックします。
|
||||
 無効なワークフローは、その状態を示す {% octicon "stop" aria-label="The stop icon" %} でマークされます。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workflow you want to disable.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
{%- endif %}
|
||||
1. Click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
{%- endif %}
|
||||
1. Click **Disable workflow**.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
|
||||
The disabled workflow is marked {% octicon "stop" aria-label="The stop icon" %} to indicate its status.
|
||||
|
||||
|
||||
{%- endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
|
|
@ -52,34 +67,45 @@ REST API を使用して、ワークフローを無効化または有効化す
|
|||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
ワークフローを無効にするには、`workflow disable` サブコマンドを使います。 `workflow` を、無効にするワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
|
||||
To disable a workflow, use the `workflow disable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to disable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
|
||||
|
||||
```shell
|
||||
gh workflow disable <em>workflow</em>
|
||||
gh workflow disable WORKFLOW
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## ワークフローの有効化
|
||||
## Enabling a workflow
|
||||
|
||||
{% webui %}
|
||||
|
||||
以前、無効化したワークフローを再度有効化することができます。
|
||||
You can re-enable a workflow that was previously disabled.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
|
||||
1. 左サイドバーで、有効にするワークフローをクリックします。
|
||||
|
||||
1. **[Enable workflow]\(ワークフローを有効にする\)** をクリックします。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workflow you want to enable.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
{%- endif %}
|
||||
1. Click **Enable workflow**.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
{%- endif %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
ワークフローを有効にするには、`workflow enable` サブコマンドを使います。 `workflow` を、有効にするワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
|
||||
To enable a workflow, use the `workflow enable` subcommand. Replace `workflow` with either the name, ID, or file name of the workflow you want to enable. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
|
||||
|
||||
```shell
|
||||
gh workflow enable <em>workflow</em>
|
||||
gh workflow enable WORKFLOW
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
|
|
|||
|
|
@ -1,38 +1,40 @@
|
|||
---
|
||||
title: ワークフローの手動実行
|
||||
intro: 'ワークフローが `workflow_dispatch` イベントで実行されるように設定されている場合、{% data variables.product.prodname_dotcom %}、{% data variables.product.prodname_cli %}、または REST API の [Actions]\(アクション\) タブを使用してワークフローを実行できます。'
|
||||
title: Manually running a workflow
|
||||
intro: 'When a workflow is configured to run on the `workflow_dispatch` event, you can run the workflow using the Actions tab on {% data variables.product.prodname_dotcom %}, {% data variables.product.prodname_cli %}, or the REST API.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Manually run a workflow
|
||||
ms.openlocfilehash: 22717c31a6bc2599f066b0e870f0aa652c18cc6f
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145117181'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## ワークフローを手動実行する設定
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
ワークフローを手動で実行するには、`workflow_dispatch` イベントで実行するようにワークフローを設定する必要があります。 `workflow_dispatch` イベントをトリガーするには、ワークフローが既定のブランチに存在する必要があります。 `workflow_dispatch` イベントの構成の詳細については、「[ワークフローをトリガーするイベント](/actions/reference/events-that-trigger-workflows#workflow_dispatch)」を参照してください。
|
||||
## Configuring a workflow to run manually
|
||||
|
||||
To run a workflow manually, the workflow must be configured to run on the `workflow_dispatch` event. To trigger the `workflow_dispatch` event, your workflow must be in the default branch. For more information about configuring the `workflow_dispatch` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#workflow_dispatch)".
|
||||
|
||||
{% data reusables.repositories.permissions-statement-write %}
|
||||
|
||||
## ワークフローの実行
|
||||
## Running a workflow
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
|
||||
1. 左のサイドバーで、実行したいワークフローをクリックしてください。
|
||||
|
||||
1. ワークフロー実行の一覧の上にある **[ワークフローの実行]** を選択します。
|
||||
|
||||
1. **[分岐]** ドロップダウンを使用してワークフローのブランチを選択し、入力パラメーターを入力します。 **[ワークフローの実行]** をクリックします。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workflow you want to run.
|
||||
|
||||
{% ifversion workflow-nav-2022 -%}
|
||||
|
||||
{%- else -%}
|
||||
|
||||
{%- endif %}
|
||||
1. Above the list of workflow runs, select **Run workflow**.
|
||||
|
||||
1. Use the **Branch** dropdown to select the workflow's branch, and type the input parameters. Click **Run workflow**.
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
|
|
@ -40,31 +42,31 @@ ms.locfileid: '145117181'
|
|||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
ワークフローを実行するには、`workflow run` サブコマンドを使用します。 `workflow` パラメーターを、実行するワークフローの名前、ID、またはファイル名のいずれかに置き換えます。 たとえば、「`"Link Checker"`」、「`1234567`」、「`"link-check-test.yml"`」のように指定します。 ワークフローを指定しない場合、{% data variables.product.prodname_cli %} はワークフローを選択するためのインタラクティブメニューを返します。
|
||||
To run a workflow, use the `workflow run` subcommand. Replace the `workflow` parameter with either the name, ID, or file name of the workflow you want to run. For example, `"Link Checker"`, `1234567`, or `"link-check-test.yml"`. If you don't specify a workflow, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a workflow.
|
||||
|
||||
```shell
|
||||
gh workflow run <em>workflow</em>
|
||||
gh workflow run WORKFLOW
|
||||
```
|
||||
|
||||
ワークフローに入力可能な場合、{% data variables.product.prodname_cli %} は入力を求めるプロンプトを表示します。 または、`-f` または `-F` を使用して `key=value` 形式の入力を追加できます。 `-F` を使用してファイルから読み取ります。
|
||||
If your workflow accepts inputs, {% data variables.product.prodname_cli %} will prompt you to enter them. Alternatively, you can use `-f` or `-F` to add an input in `key=value` format. Use `-F` to read from a file.
|
||||
|
||||
```shell
|
||||
gh workflow run greet.yml -f name=mona -f greeting=hello -F data=@myfile.txt
|
||||
```
|
||||
|
||||
標準入力を使用して、入力を JSON として渡すこともできます。
|
||||
You can also pass inputs as JSON by using standard input.
|
||||
|
||||
```shell
|
||||
echo '{"name":"mona", "greeting":"hello"}' | gh workflow run greet.yml --json
|
||||
```
|
||||
|
||||
リポジトリの既定のブランチ以外のブランチでワークフローを実行するには、`--ref` フラグを使用します。
|
||||
To run a workflow on a branch other than the repository's default branch, use the `--ref` flag.
|
||||
|
||||
```shell
|
||||
gh workflow run <em>workflow</em> --ref <em>branch-name</em>
|
||||
gh workflow run WORKFLOW --ref BRANCH
|
||||
```
|
||||
|
||||
ワークフロー実行の進行状況を表示するには、`run watch` サブコマンドを使用して、インタラクティブ リストから実行を選択します。
|
||||
To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
|
||||
|
||||
```shell
|
||||
gh run watch
|
||||
|
|
@ -72,14 +74,14 @@ gh run watch
|
|||
|
||||
{% endcli %}
|
||||
|
||||
## REST API を使用してワークフローを実行する
|
||||
## Running a workflow using the REST API
|
||||
|
||||
REST API を使用する場合は、要求本文パラメーターとして `inputs` と `ref` を構成します。 入力を省略すると、ワークフロー ファイルで定義されているデフォルト値が使用されます。
|
||||
When using the REST API, you configure the `inputs` and `ref` as request body parameters. If the inputs are omitted, the default values defined in the workflow file are used.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** 1 つの `workflow_dispatch` イベントに対して最大 10 個の `inputs` を定義できます。
|
||||
**Note:** You can define up to 10 `inputs` for a `workflow_dispatch` event.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
REST API の使用の詳細については、「[ワークフロー ディスパッチ イベントの作成](/rest/reference/actions/#create-a-workflow-dispatch-event)」を参照してください。
|
||||
For more information about using the REST API, see the "[Create a workflow dispatch event](/rest/reference/actions/#create-a-workflow-dispatch-event)."
|
||||
|
|
|
|||
|
|
@ -28,16 +28,18 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
|||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
{% ifversion fpt or ghes > 3.4 or ghae or ghec %}
|
||||
{% ifversion fpt or ghes > 3.4 or ghae or ghec -%}
|
||||
1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run all jobs**.
|
||||
|
||||
If no jobs failed, you will not see the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
|
||||
|
||||
|
||||
{%- endif %}
|
||||
{% ifversion ghes < 3.5 or ghae -%}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
|
||||
|
||||
If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
{% endwebui %}
|
||||
|
|
@ -80,8 +82,9 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
|||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
|
||||
|
||||
1. In the upper-right corner of the workflow, use the **{% octicon "sync" aria-label="The sync icon" %} Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
|
||||
|
||||
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
{% endwebui %}
|
||||
|
|
|
|||
|
|
@ -1,29 +1,29 @@
|
|||
---
|
||||
title: ジョブの実行時間を表示する
|
||||
intro: ジョブの実行時間 (ジョブの発生した支払対象の分を含む) を表示できます。
|
||||
title: Viewing job execution time
|
||||
shortTitle: View job execution time
|
||||
intro: 'You can view the execution time of a job, including the billable minutes that a job accrued.'
|
||||
redirect_from:
|
||||
- /actions/managing-workflow-runs/viewing-job-execution-time
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
shortTitle: View job execution time
|
||||
ms.openlocfilehash: 8293c36519dd727942d7cec0e1c1a2fa430ce112
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145121221'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
請求可能なジョブ実行時間 (分) は、{% data variables.product.prodname_dotcom %} ホストランナーを使用するプライベートリポジトリで実行されるジョブに対してのみ表示され、次の分に切り上げられます。 パブリックリポジトリで {% data variables.product.prodname_actions %} を使用する場合、またはセルフホストランナーで実行されるジョブの場合、請求対象となる実行時間はありません。
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} {% data reusables.repositories.navigate-to-workflow %} {% data reusables.repositories.view-run %}
|
||||
1. ジョブの概要の下で、ジョブの実行時間を表示できます。 請求可能なジョブの実行時間に関する詳細を表示するには、 **[請求可能な時間]** の下の時間をクリックしてください。
|
||||
|
||||
Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. There are no billable minutes when using {% data variables.product.prodname_actions %} in public repositories or for jobs run on self-hosted runners.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
1. Under the job summary, you can view the job's execution time. To view details about the billable job execution time, in the left sidebar under "Run details", click **{% octicon "stopwatch" aria-label="The stopwatch icon" %} Usage**.
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**注:** 表示された課金対象時間には分乗数は含まれません。 分乗数を含む、{% data variables.product.prodname_actions %} 使用状況の合計を表示するには、「[{% data variables.product.prodname_actions %} 使用状況の表示](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)」を参照してください。
|
||||
|
||||
|
||||
**Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)."
|
||||
|
||||
{% endnote %}
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ If you use {% data variables.product.prodname_codeql %} {% data variables.produc
|
|||
{% ifversion ghes %}
|
||||
If you want to use actions to run {% data variables.product.prodname_code_scanning %} on {% data variables.product.prodname_ghe_server %}, the actions must be available on your appliance.
|
||||
|
||||
The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} has access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
|
||||
The {% data variables.product.prodname_codeql %} action is included in your installation of {% data variables.product.prodname_ghe_server %}. If both {% data variables.product.prodname_ghe_server %} {{ allVersions[currentVersion].currentRelease }} and your {% data variables.product.prodname_actions %} runner have access to the internet, the action will automatically download the {% data variables.product.prodname_codeql %} {% data variables.product.codeql_cli_ghes_recommended_version %} bundle required to perform analysis. Alternatively, you can use a synchronization tool to make the latest released version of the {% data variables.product.prodname_codeql %} analysis bundle available locally. For more information, see "[Configuring {% data variables.product.prodname_codeql %} analysis on a server without internet access](#configuring-codeql-analysis-on-a-server-without-internet-access)" below.
|
||||
|
||||
You can also make third-party actions available to users for {% data variables.product.prodname_code_scanning %}, by setting up {% data variables.product.prodname_github_connect %}. For more information, see "[Configuring {% data variables.product.prodname_github_connect %} to sync {% data variables.product.prodname_actions %}](/enterprise/admin/configuration/configuring-code-scanning-for-your-appliance#configuring-github-connect-to-sync-github-actions)" below.
|
||||
|
||||
|
|
|
|||
|
|
@ -41,6 +41,10 @@ You can make extra features for code security available to users by buying and u
|
|||
|
||||
{% data reusables.advanced-security.license-overview %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
You can determine how many licenses you'll need for {% data variables.product.prodname_GH_advanced_security %} by generating a count of your instance's active committers in the site admin dashboard. For more information, see "[Site admin dashboard](/admin/configuration/configuring-your-enterprise/site-admin-dashboard#advanced-security-committers)."
|
||||
{% endif %}
|
||||
|
||||
To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
## About committer numbers for {% data variables.product.prodname_GH_advanced_security %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: ユーザごとの価格付けについて
|
||||
intro: '{% ifversion fpt or ghec %}Organization{% ifversion ghec %} と Enterprise{% endif %} の場合、{% else %}{% endif %}課金はお客様が選んだライセンス シートの数から始まります。'
|
||||
title: About per-user pricing
|
||||
intro: '{% ifversion fpt or ghec %}For organizations{% ifversion ghec %} and enterprises{% endif %}, your {% else %}Your {% endif %}bill begins with the number of licensed seats you choose.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
|
||||
- /articles/about-per-user-pricing
|
||||
|
|
@ -15,109 +15,138 @@ topics:
|
|||
- Enterprise
|
||||
- Licensing
|
||||
- Organizations
|
||||
ms.openlocfilehash: 037e0e0cfbb04552a370cf8fd0f3e05c2e09423f
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145910839'
|
||||
---
|
||||
## ユーザごとの価格付けについて
|
||||
|
||||
{% ifversion fpt %}{% data variables.product.prodname_dotcom_the_website %} 上の新しい Organization は、{% data variables.product.prodname_free_team %} でパブリックのオープンソース プロジェクトを構築するか、ユーザーごとに料金がかかる有料製品にアップグレードすることができます。 詳細については、「[{% data variables.product.company_short %} の製品](/get-started/learning-about-github/githubs-products)」および「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
|
||||
## About per-user pricing
|
||||
|
||||
2016 年 5 月 11 日以前に有料プランを使っていた Organization は、既存のリポジトリ単位のプランに留まるか、ユーザごとの価格付けに切り替えることができます。 {% data variables.product.company_short %}は、プランへの強制的な変更の前に12ヶ月間通知します。 サブスクリプションの切り替えに関する詳細については、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
|
||||
{% ifversion fpt %}
|
||||
|
||||
New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
|
||||
|
||||
Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
|
||||
|
||||
{% else %}
|
||||
|
||||
課金の基になるのは、お客様が{% ifversion ghec %} Organization または{% endif %} Enterprise に対して選んだ標準ライセンス シートの数です。
|
||||
The foundation of your bill is the number of standard licensed seats that you choose for your{% ifversion ghec %} organization or{% endif %} enterprise.
|
||||
|
||||
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
|
||||
|
||||
同じユーザーが複数の Enterprise デプロイで複数のライセンスを使わないようにするには、{% data variables.product.prodname_ghe_server %} 環境と {% data variables.product.prodname_ghe_cloud %} 環境の間でライセンスの使用状況を同期できます。 詳しくは、「[GitHub Enterprise のライセンスについて](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)」をご覧ください。
|
||||
To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. For more information, see "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
|
||||
|
||||
ライセンス シートに加えて、課金には {% data variables.product.prodname_GH_advanced_security %} などの他の料金が含まれる場合があります。 詳しくは、「[Enterprise の支払いについて](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)」をご覧ください。
|
||||
In addition to licensed seats, your bill may include other charges, such as {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
## ライセンスを使用するユーザー
|
||||
## People that consume a license
|
||||
|
||||
各ユーザーは 1 つのライセンスを使い、{% data variables.product.company_short %} はプライマリ メール アドレスによって個人を識別します。
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% data variables.product.company_short %} は、次のユーザーに課金します。
|
||||
{% data variables.product.company_short %} bills for the following people:
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- エンタープライズ内の少なくとも 1 つの組織のメンバーまたは所有者である Enterprise 所有者 {%- endif %}
|
||||
- 所有者を含む組織のメンバー
|
||||
- フォークを除く、組織が所有するプライベート{% ifversion ghec %}または内部{% endif %}のリポジトリでの外部コラボレーター
|
||||
- 組織の所有者かメンバーになるための保留中の招待があるユーザー
|
||||
- フォークを除く、組織が所有するプライベート{% ifversion ghec %}または内部{% endif %}のリポジトリで、外部コラボレーターになるための保留中の招待があるユーザー{%- ifversion ghec %}
|
||||
- デプロイした {% data variables.product.prodname_ghe_server %} インスタンス上の各ユーザー{%- endif %}
|
||||
- 休眠ユーザ
|
||||
|
||||
{% data variables.product.company_short %} は、次のどのユーザーに対しても課金しません。
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- エンタープライズ内の少なくとも 1 つの組織のメンバーまたは所有者でない Enterprise 所有者
|
||||
- Enterprise 課金マネージャー{%- endif %}
|
||||
- {% ifversion ghec %}{% data variables.product.prodname_ghe_cloud %} 上の個々の{% endif %}組織の課金マネージャー
|
||||
- {% ifversion ghec %}エンタープライズまたは{% endif %}組織の課金マネージャーになるための保留中の招待があるユーザー
|
||||
- Organization が所有するパブリック リポジトリの外部コラボレーターになるための保留中の招待があるユーザー {%- ifversion ghes %}
|
||||
- 停止されたユーザー {%- endif %}
|
||||
- Organization members, including owners
|
||||
- Outside collaborators on private repositories owned by your organization, excluding forks
|
||||
- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
|
||||
- Dormant users
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**: {% data reusables.organizations.org-invite-scim %}
|
||||
**Notes:**
|
||||
- {% data variables.product.company_short %} counts each outside collaborator once for billing purposes, even if the user account has access to multiple repositories owned by your organization.
|
||||
- {% data reusables.organizations.org-invite-scim %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
詳しくは、{% ifversion not fpt %}「[Enterprise でのロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」または{% endif %}「[Organization でのロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」をご覧ください。
|
||||
{% data variables.product.company_short %} does not bill for the following people:
|
||||
|
||||
ユーザー アカウントが {% ifversion not fpt %}Enterprise 内の複数の Organization のメンバーになっているか、または {% endif %}Organization によって所有される複数のリポジトリにアクセスできる場合であっても、{% data variables.product.company_short %} では、各{% ifversion not fpt %}メンバーまたは{% endif %}外部コラボレーターが課金のためにカウントされるのは 1 回だけです。 外部コラボレーターの詳細については、「[外部のコラボレータを Organization のリポジトリに追加する](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)」を参照してください。
|
||||
|
||||
{% ifversion ghes %}停止されているユーザーは、シートを使用しているライセンス ユーザーの数を計算するときにカウントされません。 詳しくは、「[ユーザーの一時停止と一時停止解除](/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users)」をご覧ください。{% endif %}
|
||||
|
||||
休眠ユーザーは、シート ライセンスを占有します。{% ifversion ghes %}そのため、休眠ユーザーを停止してユーザー ライセンスを解放することができます。{% endif %}詳しくは、「[休眠ユーザーの管理](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)」をご覧ください。
|
||||
|
||||
## プランの変更について
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% data variables.product.prodname_dotcom %}プランは、いつでも変更できます。
|
||||
|
||||
### ユーザごとのプランのOrganizationでの変更について
|
||||
|
||||
{% endif %}
|
||||
|
||||
いつでも、{% ifversion fpt or ghec %}Organization{% endif %}{% ifversion ghec %} または {% endif %}{% ifversion ghec or ghes %}Enterprise{% endif %} にライセンス シートを追加できます。 使われている数より多くのシートに支払っている場合は、シートの数を減らすこともできます。{% ifversion fpt %}詳しくは、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」と「[{% data variables.product.prodname_dotcom %} サブスクリプションのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」をご覧ください。
|
||||
|
||||
プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
|
||||
|
||||
チームのコラボレーション機能をさらにサポートするために、SAML シングル サインオンや高度な監査のような機能を含む {% data variables.product.prodname_ghe_cloud %} にアップグレードできます。 {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
ユーザー 1 人あたりの {% data variables.product.prodname_ghe_cloud %} の支払い関する詳細については、[{% data variables.product.prodname_ghe_cloud %} ドキュメント](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)を参照してください。
|
||||
- Billing managers
|
||||
- Anyone with a pending invitation to become a billing manager
|
||||
- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
|
||||
|
||||
{% else %}
|
||||
|
||||
{% data variables.product.prodname_dotcom_the_website %}でEnterpriseアカウントを使用しており、プランの変更に関する疑問がある場合は、{% data variables.contact.contact_enterprise_sales %}にお問い合わせください。
|
||||
{% data variables.product.company_short %} bills for the following accounts for each deployment of {% data variables.product.prodname_enterprise %}.
|
||||
|
||||
{% endif %} {% ifversion ghec %}
|
||||
### Accounts that consume a license on {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %}上の個々のOrganizationを使っている場合は、プランをアップグレードもしくはダウングレードできます。 詳細については、「[{% data variables.product.prodname_dotcom %} サブスクリプションのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」または「[{% data variables.product.prodname_dotcom %} サブスクリプションのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」を参照してください。 プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
|
||||
{% data variables.product.company_short %} bills for each of the following accounts on {% data variables.product.prodname_ghe_cloud %}:
|
||||
|
||||
- Enterprise owners who are a member or owner of at least one organization in the enterprise
|
||||
- Organization members, including owners
|
||||
- Outside collaborators on private or internal repositories owned by your organization, excluding forks
|
||||
- Anyone with a pending invitation to become an organization owner or member
|
||||
- Anyone with a pending invitation to become an outside collaborator on private or internal repositories owned by your organization, excluding forks
|
||||
- Dormant users
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
- {% data variables.product.company_short %} counts each member or outside collaborator once for billing purposes, even if the user account has membership in multiple organizations in an enterprise or access to multiple repositories owned by your organization.
|
||||
- {% data reusables.organizations.org-invite-scim %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data variables.product.company_short %} does not bill for any of the following accounts:
|
||||
|
||||
- {% data variables.product.prodname_managed_users_caps %} that are suspended
|
||||
- Enterprise owners who are not a member or owner of at least one organization in the enterprise
|
||||
- Enterprise billing managers
|
||||
- Billing managers for individual organizations
|
||||
- Anyone with a pending invitation to become a billing manager
|
||||
- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
|
||||
|
||||
### Accounts that consume a license on {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
Each user account on {% data variables.product.prodname_ghe_server %} consumes a seat.
|
||||
|
||||
Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
|
||||
|
||||
Dormant users do occupy a seat license. As such, you can choose to suspend dormant users to release user licenses. For more information, see "[Managing dormant users]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users){% ifversion not ghes %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% else %}."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About changes to your subscription
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
You can change your {% data variables.product.prodname_dotcom %} subscription at any time.
|
||||
|
||||
### About changes for organizations on per-user plans
|
||||
|
||||
{% endif %}
|
||||
|
||||
You can add more licensed seats to your {% ifversion fpt or ghec %} organization{% endif %}{% ifversion ghec %} or{% endif %}{% ifversion ghec or ghes %} enterprise{% endif %} at any time. If you pay for more seats than are being used, you can also reduce the number of seats.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
|
||||
|
||||
If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
|
||||
|
||||
To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like SAML single sign-on and advanced auditing. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
For more information about per-user pricing for {% data variables.product.prodname_ghe_cloud %}, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
|
||||
|
||||
{% else %}
|
||||
|
||||
If you use an enterprise account on {% data variables.product.prodname_dotcom_the_website %} and have questions about changes to your subscription, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec %}
|
||||
|
||||
If you use an individual organization on {% data variables.product.prodname_ghe_cloud %}, you can upgrade or downgrade your subscription. For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" or "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)." If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
### リポジトリごとのプランのOrganizationの変更について
|
||||
### About changes for organizations on per-repository plans
|
||||
|
||||
レガシーの有料プラン間でのアップグレード及びダウングレードは、Organizationの支払い設定から行えます。 より多くのプライベートリポジトリを持つプランにアップグレードするなら、{% data variables.product.company_short %}は即座にアカウントを新しいプランに移行し、支払いサイクル中に残っている日数に比例した価格の差異を課金します。
|
||||
You can upgrade or downgrade between legacy paid plans in your organization's billing settings. When you upgrade to a plan with more private repositories, {% data variables.product.company_short %} immediately moves your account to your new plan and bills you for the difference in price, prorated for the number of days left in your billing cycle.
|
||||
|
||||
プライベートリポジトリ数が少ないレガシーの有料プランにダウングレードする場合、新しいプランは次の支払日に有効になります。 新しいプランで利用できる以上のプライベートリポジトリを持っている場合、新しいプランが有効になった時点でプライベートリポジトリはロックされます。 プライベートリポジトリの数を減らすには、プライベートリポジトリの一部をパブリックにするか、プライベートリポジトリをローカルにクローンして {% data variables.product.prodname_dotcom %} 上のコピーを削除します。
|
||||
When you downgrade to a legacy paid plan with fewer private repositories, your new plan will take effect on your next billing date. If you have more private repositories than your new plan allows for, your private repositories will be locked when your new plan takes effect. To reduce your number of private repositories, you can make some of your private repositories public, or you can clone your private repositories locally and delete the copies on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
{%- ifversion not fpt %}
|
||||
- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」 {%- endif %}
|
||||
- 「[リポジトリについて](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)」
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
- "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)"
|
||||
{%- endif %}
|
||||
- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
|
||||
- "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Only repository owners and administrators can edit repository-level security adv
|
|||
|
||||
|
||||
|
||||
1. In the contribution form, make the desired improvements. You can edit or add any detail.{% ifversion security-advisories-reason-for-change %}
|
||||
1. In the "Improve security advisory" form, make the desired improvements. You can edit or add any detail.{% ifversion fpt or ghec %} For information about correctly specifying information on the form, including affected versions, see "[Best practices for writing repository security advisories](/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories)."{% endif %}{% ifversion security-advisories-reason-for-change %}
|
||||
1. Under **Reason for change**, explain why you want to make this improvement. If you include links to supporting material this will help our reviewers.
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -63,6 +63,7 @@ includeGuides:
|
|||
- /code-security/repository-security-advisories/publishing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory
|
||||
- /code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories
|
||||
- /code-security/security-overview/about-the-security-overview
|
||||
- /code-security/security-overview/filtering-alerts-in-the-security-overview
|
||||
- /code-security/security-overview/viewing-the-security-overview
|
||||
|
|
|
|||
|
|
@ -25,6 +25,7 @@ children:
|
|||
- /publishing-a-repository-security-advisory
|
||||
- /editing-a-repository-security-advisory
|
||||
- /withdrawing-a-repository-security-advisory
|
||||
- /best-practices-for-writing-repository-security-advisories
|
||||
ms.openlocfilehash: 43efe7ceaf307da4a8a7c02c45f744a4967b05b0
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ You cannot change the configuration of {% data variables.product.prodname_secret
|
|||
## About {% data variables.product.prodname_secret_scanning %} on {% data variables.product.product_name %}
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
|
||||
{% data variables.product.prodname_secret_scanning_GHAS_caps %} is available on all organization-owned repositories as part of {% data variables.product.prodname_GH_advanced_security %}. It is not available on user-owned repositories. When you enable {% data variables.product.prodname_secret_scanning %} for a repository, {% data variables.product.prodname_dotcom %} scans the code for patterns that match secrets used by many service providers. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} will also periodically run a full git history scan of existing content in {% data variables.product.prodname_GH_advanced_security %} repositories where {% data variables.product.prodname_secret_scanning %} is enabled, and send alert notifications following the {% data variables.product.prodname_secret_scanning %} alert notification settings. {% endif %}For more information, see "{% ifversion ghec %}[Supported secrets for advanced security](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security){% else %}[{% data variables.product.prodname_secret_scanning_caps %} patterns](/code-security/secret-scanning/secret-scanning-patterns){% endif %}."
|
||||
|
||||
If you're a repository administrator you can enable {% data variables.product.prodname_secret_scanning_GHAS %} for any repository{% ifversion ghec or ghes > 3.4 or ghae > 3.4 %}, including archived repositories{% endif %}. Organization owners can also enable {% data variables.product.prodname_secret_scanning_GHAS %} for all repositories or for all new repositories within an organization. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ If you're a repository administrator you can enable {% data variables.product.pr
|
|||
{% endif %}
|
||||
### About {% data variables.product.prodname_secret_scanning %} alerts
|
||||
|
||||
When you push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}.
|
||||
When you enable {% data variables.product.prodname_secret_scanning %} for a repository or push commits to a repository with {% data variables.product.prodname_secret_scanning %} enabled, {% data variables.product.prodname_dotcom %} scans the contents of those commits for secrets that match patterns defined by service providers{% ifversion ghes or ghae or ghec %} and any custom patterns defined in your enterprise, organization, or repository{% endif %}. {% ifversion secret-scanning-backfills %}{% data variables.product.prodname_dotcom %} also periodically runs a scan of all historical content in repositories with {% data variables.product.prodname_secret_scanning %} enabled.{% endif%}
|
||||
|
||||
If {% data variables.product.prodname_secret_scanning %} detects a secret, {% data variables.product.prodname_dotcom %} generates an alert.
|
||||
|
||||
|
|
|
|||
|
|
@ -267,6 +267,7 @@ translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-pers
|
|||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
|
||||
translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
|
||||
translations/ja-JP/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
|
||||
translations/ja-JP/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
|
||||
|
|
@ -294,7 +295,10 @@ translations/ja-JP/content/actions/learn-github-actions/environment-variables.md
|
|||
translations/ja-JP/content/actions/learn-github-actions/expressions.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
|
||||
translations/ja-JP/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
translations/ja-JP/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/publishing-packages/publishing-docker-images.md,rendering error
|
||||
translations/ja-JP/content/actions/quickstart.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/security-guides/automatic-token-authentication.md,rendering error
|
||||
|
|
@ -347,6 +351,7 @@ translations/ja-JP/content/billing/managing-billing-for-github-codespaces/managi
|
|||
translations/ja-JP/content/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
|
||||
|
|
@ -499,12 +504,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/about-permissions-for-github-packages.md,rendering error
|
||||
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/learn-github-packages/introduction-to-github-packages.md,rendering error
|
||||
translations/ja-JP/content/packages/learn-github-packages/viewing-packages.md,rendering error
|
||||
translations/ja-JP/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
|
||||
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
|
||||
|
|
|
|||
|
Загрузка…
Ссылка в новой задаче