Octomerger Bot
@@ -1,31 +1,20 @@
|
||||
---
|
||||
title: パブリックフォークで実行されるワークフローの実行を承認する
|
||||
intro: 外部の共同作成者が pull request をパブリック リポジトリに送信するとき、書き込みアクセスを持つメンテナはワークフローの実行を承認する必要がある場合があります。
|
||||
title: Approving workflow runs from public forks
|
||||
intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Approve public fork runs
|
||||
ms.openlocfilehash: b995362f67d97a3e2ee6d1029cbe24227867f58a
|
||||
ms.sourcegitcommit: 5f9527483381cfb1e41f2322f67c80554750a47d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145088452'
|
||||
---
|
||||
## パブリック フォークからのワークフロー実行について
|
||||
|
||||
## About workflow runs from public forks
|
||||
|
||||
{% data reusables.actions.workflow-run-approve-public-fork %}
|
||||
|
||||
[リポジトリ](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)、[Organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks)、または [Enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise) のワークフロー承認要件を構成できます。
|
||||
You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise).
|
||||
|
||||
30 日を超えて承認を待っているワークフローの実行は自動的に削除されます。
|
||||
Workflow runs that have been awaiting approval for more than 30 days are automatically deleted.
|
||||
|
||||
## パブリック フォークからの pull request でワークフロー実行を承認する
|
||||
## Approving workflow runs on a pull request from a public fork
|
||||
|
||||
リポジトリへの書き込みアクセスを持つ保守担当者は、次の手順を使用して、承認を必要とする共同作成者からの pull request でワークフローをレビューして実行できます。
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
|
||||
1. プルリクエストで提案された変更を調べて、プルリクエストブランチでワークフローを快適に実行できることを確認します。 ワークフロー ファイルに影響を与える `.github/workflows/` ディレクトリで提案された変更には特に注意する必要があります。
|
||||
1. pull request ブランチでワークフローを実行することに慣れている場合は、{% octicon "comment-discussion" aria-label="The discussion icon" %} **[会話]** タブに戻り、[承認を待っているワークフロー] で **[承認して実行]** をクリックします。
|
||||
|
||||
|
||||
{% data reusables.actions.workflows.approve-workflow-runs %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ワークフロー実行を管理する
|
||||
shortTitle: Managing workflow runs
|
||||
shortTitle: Manage workflow runs
|
||||
intro: 'ワークフローの再実行または取り消し、{% ifversion fpt or ghes or ghae %}デプロイの確認、{% endif %}課金対象のジョブ実行時間 (分) の表示、成果物のダウンロードを行うことができます。'
|
||||
redirect_from:
|
||||
- /actions/configuring-and-managing-workflows/managing-a-workflow-run
|
||||
@@ -18,17 +18,18 @@ children:
|
||||
- /re-running-workflows-and-jobs
|
||||
- /canceling-a-workflow
|
||||
- /approving-workflow-runs-from-public-forks
|
||||
- /approving-workflow-runs-from-private-forks
|
||||
- /reviewing-deployments
|
||||
- /disabling-and-enabling-a-workflow
|
||||
- /skipping-workflow-runs
|
||||
- /deleting-a-workflow-run
|
||||
- /downloading-workflow-artifacts
|
||||
- /removing-workflow-artifacts
|
||||
ms.openlocfilehash: fe5f7c461fc03392bcc93713887b1cc1d4293207
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.openlocfilehash: 9e7d6f9c29fdfb2a387b84373c1140dbb3ef6713
|
||||
ms.sourcegitcommit: 73b91dd4cdf592eadec4252319379d6fbe92858e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145117182'
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148164091'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -49,19 +49,24 @@ For more information on workflow run artifacts, see "[Persisting workflow data u
|
||||
|
||||
## Restrictions for accessing a cache
|
||||
|
||||
A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`.
|
||||
Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags.
|
||||
Workflow runs can restore caches created in either the current branch or the default branch (usually `main`). If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. For example, if the branch `feature-b` has the base branch `feature-a`, a workflow run triggered on a pull request would have access to caches created in the default `main` branch, the base `feature-a` branch, and the current `feature-b` branch.
|
||||
|
||||
Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). On similar lines, a cache created for the tag `release-a` (from the base `main`) would not be accessible to a workflow triggered for the tag `release-b` (with the base `main`).
|
||||
Workflow runs cannot restore caches created for child branches or sibling branches. For example, a cache created for the child `feature-b` branch would not be accessible to a workflow run triggered on the parent `main` branch. Similarly, a cache created for the `feature-a` branch with the base `main` would not be accessible to its sibling `feature-c` branch with the base `main`. Workflow runs also cannot restore caches created for different tag names. For example, a cache created for the tag `release-a` with the base `main` would not be accessible to a workflow run triggered for the tag `release-b` with the base `main`.
|
||||
|
||||
Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch.
|
||||
When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref (`refs/pull/.../merge`). Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. It cannot be restored by the base branch or other pull requests targeting that base branch.
|
||||
|
||||
Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch.
|
||||
|
||||
## Using the `cache` action
|
||||
|
||||
The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure.
|
||||
The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure.
|
||||
You can optionally provide a list of `restore-keys` to use in case the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can _partially_ match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
|
||||
|
||||
If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`.
|
||||
If there is an exact match to the provided `key`, this is considered a cache hit. If no cache exactly matches the provided `key`, this is considered a cache miss. On a cache miss, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. For more information about how this is handled, see "[Cache hits and misses](#cache-hits-and-misses)."
|
||||
|
||||
You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key.
|
||||
|
||||
You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)."
|
||||
|
||||
### Input parameters for the `cache` action
|
||||
|
||||
@@ -94,6 +99,21 @@ You can optionally provide a list of `restore-keys` to use when the `key` doesn'
|
||||
|
||||
- `cache-hit`: A boolean value to indicate an exact match was found for the key.
|
||||
|
||||
### Cache hits and misses
|
||||
When `key` exactly matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
|
||||
|
||||
When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
|
||||
|
||||
When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
|
||||
|
||||
1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
|
||||
- When there is an exact match, the action restores the files in the cache to the `path` directory.
|
||||
- If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
|
||||
1. The `cache` action completes and the next step in the job runs.
|
||||
1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
|
||||
|
||||
For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)."
|
||||
|
||||
### Example using the `cache` action
|
||||
|
||||
This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file.
|
||||
@@ -136,20 +156,6 @@ jobs:
|
||||
run: npm test
|
||||
```
|
||||
|
||||
When `key` matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory.
|
||||
|
||||
When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully.
|
||||
|
||||
When a cache miss occurs, the action also searches your specified `restore-keys` for any matches:
|
||||
|
||||
1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`.
|
||||
- When there is an exact match, the action restores the files in the cache to the `path` directory.
|
||||
- If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory.
|
||||
1. The `cache` action completes and the next step in the job runs.
|
||||
1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory.
|
||||
|
||||
For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key.
|
||||
|
||||
### Using contexts to create cache keys
|
||||
|
||||
A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)."
|
||||
@@ -185,7 +191,9 @@ In the example workflow above, there is a step that lists the state of the Node
|
||||
|
||||
## Matching a cache key
|
||||
|
||||
The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches.
|
||||
The `cache` action first searches for cache hits for `key` and the cache _version_ in the branch containing the workflow run. If there is no hit, it searches for `restore-keys` and the _version_. If there are still no hits in the current branch, the `cache` action retries same steps on the default branch. Please note that the scope restrictions apply during the search. For more information, see "[Restrictions for accessing a cache](#restrictions-for-accessing-a-cache)."
|
||||
|
||||
Cache version is a way to stamp a cache with metadata of the `path` and the compression tool used while creating the cache. This ensures that the consuming workflow run uniquely matches a cache it can actually decompress and use. For more information, see [Cache Version](https://github.com/actions/cache#cache-version) in the Actions Cache documentation.
|
||||
|
||||
`restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches the `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About GitHub Connect
|
||||
intro: '{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by giving you access to additional features and workflows that rely on the power of {% data variables.product.prodname_dotcom_the_website %}.'
|
||||
title: GitHub Connect について
|
||||
intro: '{% data variables.product.prodname_github_connect %} では、{% data variables.product.prodname_dotcom_the_website %} の機能に依存する追加の機能とワークフローにアクセスできるようにすることで、{% data variables.product.product_name %} を強化します。'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -9,76 +9,66 @@ topics:
|
||||
- Enterprise
|
||||
- GitHub Connect
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: ac4ec1d8b619e56c38013f5ae38d5782b6faec88
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160817'
|
||||
---
|
||||
## {% data variables.product.prodname_github_connect %} について
|
||||
|
||||
## About {% data variables.product.prodname_github_connect %}
|
||||
{% data variables.location.product_location %} が {% data variables.product.prodname_dotcom_the_website %} の機能を限定的に利用できるようにすることで、{% data variables.product.prodname_github_connect %} により {% data variables.product.product_name %} が強化されます。 {% data variables.product.prodname_github_connect %} を有効にすると、{% data variables.product.prodname_dotcom_the_website %} に依存する追加の機能やワークフローを有効にすることができます。これには、{% data variables.product.prodname_advisory_database %} で追跡されるセキュリティの脆弱性に対する {% data variables.product.prodname_dependabot_alerts %} などが含まれます。
|
||||
|
||||
{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}.
|
||||
{% data variables.product.prodname_github_connect %} では、パブリック インターネットに対して {% data variables.location.product_location %} が開きません。 {% data variables.product.prodname_dotcom_the_website %} ユーザーには、エンタープライズのプライベート データは公開されません。 代わりに、{% data variables.product.prodname_github_connect %} は、有効にした個々の機能に必要な限られたデータのみを送信します。 ライセンス同期を有効にしない限り、{% data variables.product.prodname_github_connect %} によって個人データは送信されません。 {% data variables.product.prodname_github_connect %} によって送信されるデータの詳細については、「[{% data variables.product.prodname_github_connect %} のデータ転送](#data-transmission-for-github-connect)」を参照してください。
|
||||
|
||||
{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
|
||||
{% data variables.product.prodname_github_connect %} を有効化しても、{% data variables.product.prodname_dotcom_the_website %} のユーザーは {% data variables.product.product_name %} を変更できません。
|
||||
|
||||
Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
|
||||
{% data variables.product.prodname_github_connect %} を有効にするには、{% data variables.location.product_location %} と、{% data variables.product.prodname_ghe_cloud %} を使用する {% data variables.product.prodname_dotcom_the_website %} 上の Organization または Enterprise アカウントの間の接続を構成します。 {% data reusables.github-connect.connection-port-protocol %} 詳しくは、「[{% data variables.product.prodname_github_connect %} の管理](/admin/configuration/configuring-github-connect/managing-github-connect)」を参照してください。
|
||||
|
||||
To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
|
||||
{% data variables.product.prodname_github_connect %} を有効にすると、{% ifversion ghes %}自動ユーザー ライセンス同期や {% endif %}{% data variables.product.prodname_dependabot_alerts %} などの機能を有効にできるようになります。 使用可能なすべての機能の詳細については、「[{% data variables.product.prodname_github_connect %} 機能](#github-connect-features)」を参照してください。
|
||||
|
||||
After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
|
||||
## {% data variables.product.prodname_github_connect %} 機能
|
||||
|
||||
## {% data variables.product.prodname_github_connect %} features
|
||||
{% data variables.location.product_location %} と {% data variables.product.prodname_ghe_cloud %} の間の接続を構成した後、Enterprise に対して {% data variables.product.prodname_github_connect %} の個々の機能を有効にすることができます。
|
||||
|
||||
After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise.
|
||||
機能 | 説明 | 詳細 | ------- | ----------- | ---------------- |{% ifversion ghes %} 自動ユーザー ライセンス同期 | ユーザー ライセンスを {% data variables.location.product_location %} から {% data variables.product.prodname_ghe_cloud %} に自動的に同期することで、{% data variables.product.prodname_enterprise %} デプロイ全体のライセンス使用量を管理します。 | 「[Enterprise に対する自動ユーザー ライセンス同期の有効化](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)」{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | ユーザーが、コード依存関係の脆弱性を見つけて修正できるようにします。 | 「[エンタープライズに対して {% data variables.product.prodname_dependabot %} を有効にする](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)」{% endif %} {% data variables.product.prodname_dotcom_the_website %} アクション | ユーザーがワークフロー ファイルで {% data variables.product.prodname_dotcom_the_website %} からのアクションを使用できるようにします。 | 「[{% data variables.product.prodname_github_connect %} を使った {% data variables.product.prodname_dotcom_the_website %} アクションへの自動アクセスの有効化](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)」{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | GitHub Enterprise Server からの独自の集計データを分析して、GitHub 製品の改善に役立てます。 | 「[Enterprise に対する {% data variables.product.prodname_server_statistics %} の有効化](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)」{% endif %} Unified Search | {% data variables.location.product_location %} から検索するときに、ユーザーが検索結果に {% data variables.product.prodname_dotcom_the_website %} のリポジトリを含めることができるようになります。 | 「[Enterprise の {% data variables.enterprise.prodname_unified_search %} を有効にする](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)」統合コントリビューション | ユーザーが {% data variables.location.product_location %} に対する作業の匿名化されたコントリビューション数を、{% data variables.product.prodname_dotcom_the_website %} のコントリビューション グラフに含めることを許可します。 | 「[Enterprise に対する {% data variables.enterprise.prodname_unified_contributions %} の有効化](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)」
|
||||
|
||||
Feature | Description | More information |
|
||||
------- | ----------- | ---------------- |{% ifversion ghes %}
|
||||
Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %}
|
||||
{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %}
|
||||
Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"
|
||||
Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"
|
||||
## {% data variables.product.prodname_github_connect %} のデータ転送
|
||||
|
||||
## Data transmission for {% data variables.product.prodname_github_connect %}
|
||||
|
||||
When {% data variables.product.prodname_github_connect %} is enabled, a record on {% data variables.product.prodname_ghe_cloud %} stores information about the connection. If you enable individual features of {% data variables.product.prodname_github_connect %}, additional data is transmitted.
|
||||
{% data variables.product.prodname_github_connect %} を有効にすると、{% data variables.product.prodname_ghe_cloud %} 上のレコードに、接続に関する情報が格納されます。 {% data variables.product.prodname_github_connect %} の個々の機能を有効にすると、追加のデータが送信されます。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** No repositories, issues, or pull requests are ever transmitted from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} by {% data variables.product.prodname_github_connect %}.
|
||||
**注意:** {% data variables.product.product_name %} から {% data variables.product.prodname_dotcom_the_website %} に {% data variables.product.prodname_github_connect %} によって、リポジトリ、issue、または pull request が送信されることはありません。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Data transmitted when {% data variables.product.prodname_github_connect %} is enabled
|
||||
### {% data variables.product.prodname_github_connect %} を有効にすると送信されるデータ
|
||||
|
||||
When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection.
|
||||
{% data variables.product.prodname_github_connect %} または特定の {% data variables.product.prodname_github_connect %} 機能を有効にすると、{% data variables.product.prodname_ghe_cloud %} のレコードに、接続に関する次の情報が格納されます。
|
||||
{% ifversion ghes %}
|
||||
- The public key portion of your {% data variables.product.prodname_ghe_server %} license
|
||||
- A hash of your {% data variables.product.prodname_ghe_server %} license
|
||||
- The customer name on your {% data variables.product.prodname_ghe_server %} license
|
||||
- The version of {% data variables.location.product_location_enterprise %}{% endif %}
|
||||
- The hostname of {% data variables.location.product_location %}
|
||||
- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %}
|
||||
- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %}
|
||||
- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %}
|
||||
- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %}
|
||||
- The dormancy threshold for your enterprise
|
||||
- The number of dormant users for your enterprise
|
||||
- A count of license-consuming seats, which does not include suspended users
|
||||
- {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分
|
||||
- {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ
|
||||
- {% data variables.product.prodname_ghe_server %} ライセンスの顧客名
|
||||
- {% data variables.location.product_location_enterprise %} のバージョン{% endif %}
|
||||
- {% data variables.location.product_location %} のホスト名
|
||||
- {% data variables.location.product_location %} に接続している {% data variables.product.prodname_ghe_cloud %} 上の Organization または Enterprise アカウント
|
||||
- {% data variables.product.prodname_ghe_cloud %} への要求の発行に {% data variables.location.product_location %} で使用される認証トークン
|
||||
- トランスポート層セキュリティ (TLS) が有効で、{% data variables.location.product_location %}{% ifversion ghes %} で構成されている場合
|
||||
- {% data variables.location.product_location %} で有効になっている {% data variables.product.prodname_github_connect %} の機能と、有効化された日時{% endif %}
|
||||
- エンタープライズの休眠しきい値
|
||||
- エンタープライズの休止ユーザーの数
|
||||
- 一時停止中のユーザーを含まないライセンス消費シートの数
|
||||
|
||||
{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
|
||||
{% data variables.product.prodname_github_connect %} は、{% data variables.location.product_location %} と {% data variables.product.prodname_ghe_cloud %} の間の上記の接続データを、{% data variables.product.prodname_github_connect %} が有効になった日とおおよその時刻から毎週同期します。
|
||||
|
||||
### Data transmitted by individual features of {% data variables.product.prodname_github_connect %}
|
||||
### {% data variables.product.prodname_github_connect %} の個々の機能によって送信されるデータ
|
||||
|
||||
Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}.
|
||||
{% data variables.product.prodname_github_connect %} の個々の機能を有効にすると、追加のデータが送信されます。
|
||||
|
||||
Feature | Data | Which way does the data flow? | Where is the data used? |
|
||||
------- | ---- | --------- | ------ |{% ifversion ghes %}
|
||||
Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %}
|
||||
{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %}
|
||||
{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository<br><br>If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} | Aggregate metrics about your usage of {% data variables.product.prodname_ghe_server %}. For the complete list of metrics, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %}
|
||||
Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} |
|
||||
Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} |
|
||||
機能 | データ | データの流れ | データの使用場所 | ------- | ---- | --------- | ------ |{% ifversion ghes %} 自動ユーザー ライセンス同期 | 各 {% data variables.product.product_name %} ユーザーのユーザー ID とメール アドレス | {% data variables.product.product_name %} から {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | 脆弱性アラート | {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | 依存関係と各依存関係のリポジトリのメタデータ<br><br>依存関係が {% data variables.product.prodname_dotcom_the_website %} のプライベート リポジトリに格納されている場合、{% data variables.product.prodname_dependabot %} が構成され、そのリポジトリへのアクセスが承認されている場合のみ、データは送信されます。 | {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.product_name %} へ | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %} アクション | アクションの名前、アクション ({% data variables.product.prodname_marketplace %} からの YAML ファイル) | {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.product_name %} へ<br><br>{% data variables.product.product_name %} から {% data variables.product.prodname_dotcom_the_website %} へ | {% data variables.product.product_name %}{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | {% data variables.product.prodname_ghe_server %} の使用状況に関するメトリックの集計。 メトリックの完全なリストについては、「[{% data variables.product.prodname_server_statistics %} について](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)」を参照してください。 | {% data variables.product.product_name %} から {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} Unified Search | 検索語句、検索結果 | {% data variables.product.prodname_dotcom_the_website %} から {% data variables.product.product_name %}<br><br>{% data variables.product.product_name %} から {% data variables.product.prodname_dotcom_the_website %} へ | {% data variables.product.product_name %} | 統合コントリビューション | コントリビューション数 | {% data variables.product.product_name %} から {% data variables.product.prodname_dotcom_the_website %} へ | {% data variables.product.prodname_dotcom_the_website %} |
|
||||
|
||||
## Further reading
|
||||
## 参考資料
|
||||
|
||||
- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
|
||||
- GraphQL API ドキュメントの「[Enterprise アカウント](/graphql/guides/managing-enterprise-accounts)」
|
||||
|
||||
@@ -18,7 +18,7 @@ topics:
|
||||
|
||||
## Using the audit log API
|
||||
|
||||
You can interact with the audit log using the GraphQL API or the REST API.
|
||||
You can interact with the audit log using the GraphQL API or the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Running CodeQL runner in your CI system
|
||||
title: CIシステムでのCodeQLランナーの実行
|
||||
shortTitle: Run CodeQL runner
|
||||
intro: 'You can use the {% data variables.code-scanning.codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.'
|
||||
intro: '{% data variables.code-scanning.codeql_runner %} を使用して、サードパーティの継続的インテグレーションシステムで {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} を実行できます。'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
redirect_from:
|
||||
- /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system
|
||||
@@ -24,102 +24,102 @@ topics:
|
||||
- Integration
|
||||
- CI
|
||||
- SARIF
|
||||
ms.openlocfilehash: 7e60376ed165a3af2da7f000c37d326cb33ade99
|
||||
ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/11/2022
|
||||
ms.locfileid: '148161095'
|
||||
---
|
||||
|
||||
<!--UI-LINK: When GitHub Enterprise Server <=3.0 doesn't have GitHub Actions set up, the Security > Code scanning alerts view links to this article.-->
|
||||
|
||||
{% ifversion codeql-runner-supported %}
|
||||
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %}
|
||||
{% data reusables.code-scanning.beta %}
|
||||
{% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %}
|
||||
|
||||
## About the {% data variables.code-scanning.codeql_runner %}
|
||||
## {% data variables.code-scanning.codeql_runner %} について
|
||||
|
||||
The {% data variables.code-scanning.codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
{% data variables.code-scanning.codeql_runner %} は、サードパーティの継続的インテグレーション (CI) システム内で処理しているコードに対して {% data variables.product.prodname_code_scanning %} を実行するのに利用できるツールです。 {% data reusables.code-scanning.about-code-scanning %} 詳細については、「[{% data variables.product.prodname_codeql %} による{% data variables.product.prodname_code_scanning %}について](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)」を参照してください。
|
||||
|
||||
In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system.
|
||||
多くの場合、CIシステム内で{% data variables.product.prodname_codeql_cli %}を直接使って{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}をセットアップするのが容易です。
|
||||
|
||||
Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)."
|
||||
あるいは、{% data variables.product.prodname_actions %}を使って{% data variables.product.product_name %}内で{% data variables.product.prodname_code_scanning %}を実行することもできます。 詳細については、「[リポジトリの {% data variables.product.prodname_code_scanning %} の設定](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)」を参照してください。
|
||||
|
||||
The {% data variables.code-scanning.codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository.
|
||||
{% data variables.code-scanning.codeql_runner %} は、{% data variables.product.prodname_dotcom %} リポジトリのチェックアウト中に {% data variables.product.prodname_codeql %} 解析を実行するコマンドライン ツールです。 サードパーティーのシステムにランナーを追加し、ランナーを呼び出してコードを解析し、その結果を {% data variables.product.product_name %} にアップロードします。 この結果は、リポジトリの {% data variables.product.prodname_code_scanning %} アラートとして表示されます。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:**
|
||||
{% ifversion fpt or ghec %}
|
||||
* The {% data variables.code-scanning.codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
**注:** {% ifversion fpt or ghec %}
|
||||
* {% data variables.code-scanning.codeql_runner %} は {% data variables.product.prodname_codeql %} CLI を使ってコードを分析するので、同じライセンス条件を持ちます。 {% data variables.product.prodname_dotcom_the_website %}上で管理されるパブリックリポジトリでの使用は無料であり、{% data variables.product.prodname_advanced_security %}ライセンスを持つお客様が所有するプライベートリポジトリ上で使用できます。 詳細については、「[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} の使用条件](https://securitylab.github.com/tools/codeql/license)」および「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
|
||||
{% else %}
|
||||
* The {% data variables.code-scanning.codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license.
|
||||
{% endif %}
|
||||
{% ifversion ghae %}
|
||||
* The {% data variables.code-scanning.codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries.
|
||||
For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)."
|
||||
{% endif %}
|
||||
{% endnote %}
|
||||
* {% data variables.code-scanning.codeql_runner %} は {% data variables.product.prodname_advanced_security %} ライセンスを持つお客様にご利用いただけます。
|
||||
{% endif %} {% ifversion ghae %}
|
||||
* {% data variables.code-scanning.codeql_runner %} を {% data variables.product.prodname_codeql %} CLI と混同しないようにしてください。 {% data variables.product.prodname_codeql %} CLIは、セキュリティの研究のために{% data variables.product.prodname_codeql %}データベースを作成し、{% data variables.product.prodname_codeql %}クエリを実行できるようにしてくれるコマンドラインインターフェースです。
|
||||
詳細については、「[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
|
||||
{% endif %} {% endnote %}
|
||||
|
||||
## Downloading the {% data variables.code-scanning.codeql_runner %}
|
||||
## {% data variables.code-scanning.codeql_runner %} のダウンロード
|
||||
|
||||
You can download the {% data variables.code-scanning.codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it.
|
||||
{% data variables.code-scanning.codeql_runner %} は、 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases からダウンロードできます。 一部のオペレーティングシステムでは、ダウンロードしたファイルの実行前に、その権限を変更する必要があります。
|
||||
|
||||
On Linux:
|
||||
Linux の場合:
|
||||
|
||||
```shell
|
||||
chmod +x codeql-runner-linux
|
||||
```
|
||||
|
||||
On macOS:
|
||||
macOS の場合:
|
||||
|
||||
```shell
|
||||
chmod +x codeql-runner-macos
|
||||
sudo xattr -d com.apple.quarantine codeql-runner-macos
|
||||
```
|
||||
|
||||
On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions.
|
||||
Windows では、通常、`codeql-runner-win.exe` ファイルの権限変更は必要はありません。
|
||||
|
||||
## Adding the {% data variables.code-scanning.codeql_runner %} to your CI system
|
||||
## CI システムに {% data variables.code-scanning.codeql_runner %} を追加する
|
||||
|
||||
Once you download the {% data variables.code-scanning.codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example:
|
||||
{% data variables.code-scanning.codeql_runner %} をダウンロードし、実行できることを確認したら、{% data variables.product.prodname_code_scanning %} に使用するそれぞれの CI サーバーでランナーを利用できるようにする必要があります。 たとえば、内部的な中央の場所からランナーをコピーするよう、各サーバーを設定することになるでしょう。 あるいは、REST API を使用して {% data variables.product.prodname_dotcom %}から直接ランナーを取得することもできます。例:
|
||||
|
||||
```shell
|
||||
wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux
|
||||
chmod +x codeql-runner-linux
|
||||
```
|
||||
|
||||
In addition to this, each CI server also needs:
|
||||
これに加えて、各 CI サーバーは以下の条件も満たす必要があります。
|
||||
|
||||
- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.code-scanning.codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.code-scanning.codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)."
|
||||
- 使用する {% data variables.code-scanning.codeql_runner %} の {% data variables.product.prodname_github_app %} または {% data variables.product.pat_generic %}。 `repo` スコープがあるアクセス トークン、または `security_events` 書き込み権限、および `metadata` と `contents` の読み取り権限を持つ {% data variables.product.prodname_github_app %} を使用する必要があります。 詳しくは、「[{% data variables.product.prodname_github_apps %} を構築する](/developers/apps/building-github-apps)」と「[{% data variables.product.pat_generic %} の作成](/github/authenticating-to-github/creating-a-personal-access-token)」を参照してください。
|
||||
- {% data variables.code-scanning.codeql_runner %} のリリースに伴う {% data variables.product.prodname_codeql %} バンドルへのアクセス。 このパッケージには、{% data variables.product.prodname_codeql %} 解析に必要なクエリとライブラリ、さらにランナーによって内部的に使用される {% data variables.product.prodname_codeql %} CLI が含まれています。 詳細については、「[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)」を参照してください。
|
||||
|
||||
The options for providing access to the {% data variables.product.prodname_codeql %} bundle are:
|
||||
{% data variables.product.prodname_codeql %} バンドルにアクセスを与えるオプションは次の通りです。
|
||||
|
||||
1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.code-scanning.codeql_runner %} can download the bundle automatically.
|
||||
1. Manually download/extract the bundle, store it with other central resources, and use the <nobr>`--codeql-path`</nobr> flag to specify the location of the bundle in calls to initialize the {% data variables.code-scanning.codeql_runner %}.
|
||||
1. CI サーバーに https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action へのアクセスを許可し、{% data variables.code-scanning.codeql_runner %} によりバンドルが自動的にダウンロードされるようにします。
|
||||
1. バンドルを手動でダウンロードおよび展開し、他の中央リソースと共に格納し、<nobr>`--codeql-path`</nobr> フラグを使用して、{% data variables.code-scanning.codeql_runner %} を初期化する呼び出しでバンドルの場所を指定します。
|
||||
|
||||
## Calling the {% data variables.code-scanning.codeql_runner %}
|
||||
## {% data variables.code-scanning.codeql_runner %} の呼び出し
|
||||
|
||||
You should call the {% data variables.code-scanning.codeql_runner %} from the checkout location of the repository you want to analyze. The two main commands are:
|
||||
解析するリポジトリのチェックアウトの場所から、{% data variables.code-scanning.codeql_runner %} を呼び出す必要があります。 主なコマンドは次の 2 つです。
|
||||
|
||||
1. `init` required to initialize the runner and create a {% data variables.product.prodname_codeql %} database for each language to be analyzed. These databases are populated and analyzed by subsequent commands.
|
||||
1. `analyze` required to populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload results to {% data variables.product.product_name %}.
|
||||
1. `init` は、ランナーを初期化し、解析する言語ごとに {% data variables.product.prodname_codeql %} データベースを作成するために必要です。 このデータベースは、続くコマンドにより展開、解析されます。
|
||||
1. `analyze` は、{% data variables.product.prodname_codeql %} データベースを展開し、解析し、結果を {% data variables.product.product_name %} にアップロードするために必要です。
|
||||
|
||||
For both commands, you must specify the URL of {% data variables.product.product_name %}, the repository *OWNER/NAME*, and the {% data variables.product.prodname_github_apps %} or {% data variables.product.pat_generic %} to use for authentication. You also need to specify the location of the CodeQL bundle, unless the CI server has access to download it directly from the `github/codeql-action` repository.
|
||||
どちらのコマンドでも、{% data variables.product.product_name %} の URL、リポジトリの *OWNER/NAME*、および認証に使用する{% data variables.product.prodname_github_apps %} または {% data variables.product.pat_generic %} を指定する必要があります。 CI サーバーで `github/codeql-action` リポジトリから直接 CodeQL バンドルをダウンロードできる場合を除き、そのバンドルの場所を指定する必要もあります。
|
||||
|
||||
You can configure where the {% data variables.code-scanning.codeql_runner %} stores the CodeQL bundle for future analysis on a server using the <nobr>`--tools-dir`</nobr> flag and where it stores temporary files during analysis using <nobr>`--temp-dir`</nobr>.
|
||||
<nobr>`--tools-dir`</nobr> フラグを使用して、{% data variables.code-scanning.codeql_runner %} が今後の解析のためにサーバーに CodeQL バンドルを格納する場所を構成し、<nobr>`--temp-dir`</nobr> を使用して、解析時に一時ファイルを格納する場所を構成できます。
|
||||
|
||||
To view the command-line reference for the runner, use the `-h` flag. For example, to list all commands run: `codeql-runner-OS -h`, or to list all the flags available for the `init` command run: `codeql-runner-OS init -h` (where `OS` varies according to the executable that you are using). For more information, see "[Configuring {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)."
|
||||
ランナーのコマンドライン リファレンスを表示するには、`-h` フラグを使用します。 たとえば、すべてのコマンドを一覧表示するには、`codeql-runner-OS -h` を実行します。または、`init` コマンドで使用できるすべてのフラグを一覧表示するには、`codeql-runner-OS init -h` を実行します (ここで `OS` は、使用している実行可能ファイルによって異なります)。 詳細については、「[CI システムでの {% data variables.product.prodname_code_scanning %} の構成](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system#codeql-runner-command-reference)」を参照してください。
|
||||
|
||||
{% data reusables.code-scanning.upload-sarif-alert-limit %}
|
||||
|
||||
### Basic example
|
||||
### 基本的な例
|
||||
|
||||
This example runs {% data variables.product.prodname_codeql %} analysis on a Linux CI server for the `octo-org/example-repo` repository hosted on `{% data variables.command_line.git_url_example %}`. The process is very simple because the repository contains only languages that can be analyzed by {% data variables.product.prodname_codeql %} directly, without being built (that is, Go, JavaScript, Python, and TypeScript).
|
||||
この例では、`{% data variables.command_line.git_url_example %}` でホストされている `octo-org/example-repo` リポジトリに対して、Linux CI サーバーで {% data variables.product.prodname_codeql %} 解析を実行します。 このリポジトリには、{% data variables.product.prodname_codeql %} により直接解析でき、ビルドされていない言語 (Go、JavaScript、Python、TypeScript) のみが含まれているため、プロセスは非常に単純です。
|
||||
|
||||
In this example, the server has access to download the {% data variables.product.prodname_codeql %} bundle directly from the `github/codeql-action` repository, so there is no need to use the `--codeql-path` flag.
|
||||
この例では、サーバーで `github/codeql-action` リポジトリから直接 {% data variables.product.prodname_codeql %} バンドルをダウンロードできるので、`--codeql-path` フラグを使う必要はありません。
|
||||
|
||||
1. Check out the repository to analyze.
|
||||
1. Move into the directory where the repository is checked out.
|
||||
1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
1. 解析するリポジトリをチェックアウトします。
|
||||
1. リポジトリがチェックアウトされるディレクトリに移動します。
|
||||
1. {% data variables.code-scanning.codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
|
||||
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo
|
||||
@@ -131,13 +131,13 @@ In this example, the server has access to download the {% data variables.product
|
||||
|
||||
{% data reusables.code-scanning.codeql-runner-analyze-example %}
|
||||
|
||||
### Compiled language example
|
||||
### コンパイル型言語の例
|
||||
|
||||
This example is similar to the previous example, however this time the repository has code in C/C++, C#, or Java. To create a {% data variables.product.prodname_codeql %} database for these languages, the CLI needs to monitor the build. At the end of the initialization process, the runner reports the command you need to set up the environment before building the code. You need to run this command, before calling the normal CI build process, and then running the `analyze` command.
|
||||
この例は前の例と似ていますが、今回のリポジトリには C/C++、C#、または Java のコードがあります。 これらの言語用に {% data variables.product.prodname_codeql %} データベースを作成するには、CLI でビルドをモニターする必要があります。 初期化プロセスの最後に、ランナーはコードをビルドする前に環境をセットアップするために必要なコマンドを報告します。 通常の CI ビルド プロセスを呼び出す前にこのコマンドを実行してから、`analyze` コマンドを実行する必要があります。
|
||||
|
||||
1. Check out the repository to analyze.
|
||||
1. Move into the directory where the repository is checked out.
|
||||
1. Initialize the {% data variables.code-scanning.codeql_runner %} and create {% data variables.product.prodname_codeql %} databases for the languages detected.
|
||||
1. 解析するリポジトリをチェックアウトします。
|
||||
1. リポジトリがチェックアウトされるディレクトリに移動します。
|
||||
1. {% data variables.code-scanning.codeql_runner %} を初期化し、検出された言語用の {% data variables.product.prodname_codeql %} データベースを作成します。
|
||||
```shell
|
||||
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux init --repository octo-org/example-repo-2
|
||||
--github-url {% data variables.command_line.git_url_example %} --github-auth-stdin
|
||||
@@ -148,37 +148,37 @@ This example is similar to the previous example, however this time the repositor
|
||||
Please export these variables to future processes so that CodeQL can monitor the build, for example by running
|
||||
". /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh".
|
||||
```
|
||||
1. Source the script generated by the `init` action to set up the environment to monitor the build. Note the leading dot and space in the following code snippet.
|
||||
1. `init` アクションによって生成されたスクリプトを入手し、ビルドを監視する環境を設定します。 次のコードには、先頭にドットとスペースがあることに注意してください。
|
||||
|
||||
```shell
|
||||
$ . /srv/checkout/example-repo-2/codeql-runner/codeql-env.sh
|
||||
```
|
||||
|
||||
1. Build the code. On macOS, you need to prefix the build command with the environment variable `$CODEQL_RUNNER`. For more information, see "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)."
|
||||
1. コードをビルドする。 macOS では、ビルド コマンドの前に環境変数 `$CODEQL_RUNNER` を付ける必要があります。 詳しくは、「[CI システムでの {% data variables.code-scanning.codeql_runner %} のトラブルシューティング](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system#no-code-found-during-the-build)」を参照してください。
|
||||
|
||||
{% data reusables.code-scanning.codeql-runner-analyze-example %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you use a containerized build, you need to run the {% data variables.code-scanning.codeql_runner %} in the container where your build task takes place.
|
||||
**注:** コンテナー化されたビルドを使用している場合、ビルド タスクを行うコンテナーで {% data variables.code-scanning.codeql_runner %} を実行する必要があります。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
## 参考資料
|
||||
|
||||
- "[Configuring {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)"
|
||||
- "[Troubleshooting {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)"
|
||||
- [CI システムでの {% data variables.code-scanning.codeql_runner %} の構成](/code-security/secure-coding/configuring-codeql-runner-in-your-ci-system)
|
||||
- [CI システムでの {% data variables.code-scanning.codeql_runner %} のトラブルシューティング](/code-security/secure-coding/troubleshooting-codeql-runner-in-your-ci-system)
|
||||
|
||||
{% else %}
|
||||
|
||||
## About the {% data variables.code-scanning.codeql_runner %}
|
||||
## {% data variables.code-scanning.codeql_runner %} について
|
||||
|
||||
The {% data variables.code-scanning.codeql_runner %} has been deprecated. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.7.6 has complete feature parity.
|
||||
{% data variables.code-scanning.codeql_runner %} は非推奨となりました。 [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) バージョン 2.7.6 には完全な機能パリティがあります。
|
||||
|
||||
For information on migrating to {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)."
|
||||
{% data variables.product.prodname_codeql_cli %} への移行については、「[CodeQL ランナーから CodeQL CLI への移行](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)」を参照してください。
|
||||
|
||||
## Further reading
|
||||
## 参考資料
|
||||
|
||||
- [CodeQL runner deprecation](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/) in the GitHub Blog
|
||||
- GitHub ブログの [CodeQL ランナーの廃止](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/)
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -463,7 +463,13 @@ jobs:
|
||||
|
||||
### Enable auto-merge on a pull request
|
||||
|
||||
If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when all required tests and approvals are successfully met. For more information on auto-merge, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)."
|
||||
If you want to allow maintainers to mark certain pull requests for auto-merge, you can use {% data variables.product.prodname_dotcom %}'s auto-merge functionality. This enables the pull request to be merged when any tests and approvals required by the branch protection rules are successfully met. For more information, see "[Automatically merging a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you use status checks to test pull requests, you should enable **Require status checks to pass before merging** for the target branch for {% data variables.product.prodname_dependabot %} pull requests. This branch protection rule ensures that pull requests are not merged unless all the required status checks pass. For more information, see "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can instead use {% data variables.product.prodname_actions %} and the {% data variables.product.prodname_cli %}. Here is an example that auto merges all patch updates to `my-dependency`:
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: GitHub Codespaces overview
|
||||
title: GitHub Codespaces の概要
|
||||
shortTitle: Overview
|
||||
intro: 'This guide introduces {% data variables.product.prodname_github_codespaces %} and provides details on how it works and how to use it.'
|
||||
intro: 'このガイドでは、{% data variables.product.prodname_github_codespaces %} について紹介し、そのしくみと使用方法について詳しく説明します。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /codespaces/codespaces-reference/about-codespaces
|
||||
@@ -15,52 +15,57 @@ versions:
|
||||
type: overview
|
||||
topics:
|
||||
- Codespaces
|
||||
ms.openlocfilehash: a1618c86671bc5b06474c41803c6b34576a897aa
|
||||
ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: '148160801'
|
||||
---
|
||||
## codespace とは
|
||||
|
||||
## What is a codespace?
|
||||
codespace は、クラウドでホストされている開発環境です。 [構成ファイル](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)をリポジトリにコミットすることで、{% data variables.product.prodname_github_codespaces %} のプロジェクトをカスタマイズできます (コードとしての構成とよく呼ばれます)。これにより、プロジェクトのすべてのユーザーに対して繰り返し可能な codespace 構成が作成されます。
|
||||
|
||||
A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_github_codespaces %} by committing [configuration files](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project.
|
||||
各 codespace は、{% data variables.product.prodname_dotcom %} によってホストされる仮想マシン上で実行されます。 必要なリソースに応じて、使用するマシンの種類を選ぶことができます。 2 コア プロセッサ、4 GB の RAM、32 GB のストレージから始まるさまざまな種類のマシンをお使いいただけます。
|
||||
|
||||
Each codespace runs on a virtual machine hosted by {% data variables.product.prodname_dotcom %}. You can choose the type of machine you want to use, depending on the resources you need. Various types of machine are available, starting with a 2-core processor, 4 GB of RAM, and 32 GB of storage.
|
||||
codespace への接続には、ブラウザー、{% data variables.product.prodname_vscode %}、JetBrains Gateway アプリケーション、または {% data variables.product.prodname_cli %} を使うことができます。
|
||||
|
||||
You can connect to your codespaces from your browser, from {% data variables.product.prodname_vscode %}, from the JetBrains Gateway application, or by using {% data variables.product.prodname_cli %}.
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_github_codespaces %} の使用
|
||||
|
||||
## Using {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
To begin developing using cloud-based compute resources, you can create a codespace from a template or from any branch or commit in a repository. When you create a codespace from a template, you can start from a blank template or choose a template suitable for the work you're doing.
|
||||
クラウドベースのコンピューティング リソースを使用して開発を開始するには、テンプレートまたは任意のブランチから codespace を作成するか、リポジトリにコミットします。 テンプレートから codespace を作成する場合は、空白のテンプレートから開始するか、作業に適したテンプレートを選ぶことができます。
|
||||
|
||||
{% data reusables.codespaces.links-to-get-started %}
|
||||
|
||||
### Using codespaces owned by your personal account
|
||||
### 個人アカウントが所有する codespace の使用
|
||||
|
||||
All personal {% data variables.product.prodname_dotcom_the_website %} accounts have a monthly quota of free use of {% data variables.product.prodname_github_codespaces %} included in the Free or Pro plan. You can get started using {% data variables.product.prodname_github_codespaces %} on your personal account without changing any settings or providing payment details.
|
||||
すべての個人 {% data variables.product.prodname_dotcom_the_website %} アカウントには、無料または Pro プランに含まれる {% data variables.product.prodname_github_codespaces %} の無料使用の月次クォータがあります。 設定を変更したり、支払いの詳細を指定したりせずに、個人アカウントで {% data variables.product.prodname_github_codespaces %} を使い始めることができます。
|
||||
|
||||
You can create and use a codespace for any repository you can clone. You can also use a template to create codespaces that are not initially associated with a repository. If you create a codespace from an organization-owned repository, use of the codespace will either be charged to the organization (if the organization is configured for this), or to your personal account. Codespaces created from templates are always charged to your personal account.
|
||||
クローンできる任意のリポジトリに対して codespace を作成して使うことができます。 テンプレートを使用して、最初はリポジトリに関連付けられていない codespace を作成することもできます。 Organization 所有のリポジトリから codespace を作成した場合、codespace の使用は Organization (Organization がこれに対して構成されている場合) または個人アカウントに対して課金されます。 テンプレートから作成された codespace は、常に個人アカウントに課金されます。
|
||||
|
||||
{% data reusables.codespaces.codespaces-continue-by-paying %}
|
||||
|
||||
### Using organization-owned codespaces
|
||||
### Organization 所有の codespace の使用
|
||||
|
||||
Organization owners can enable use of {% data variables.product.prodname_github_codespaces %}, billable to the organization or enterprise account. This applies to codespaces created from repositories owned by the organization. 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)." You can set a spending limit for use of {% data variables.product.prodname_github_codespaces %} on your organization or enterprise account. For more information, see "[Managing spending limits for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)."
|
||||
Organization の所有者は、{% data variables.product.prodname_github_codespaces %} の使用を有効にすることができ、Organization または Enterprise アカウントに対して課金できます。 これは、Organization が所有するリポジトリから作成された codespace に適用されます。 詳しくは、「[Organization での {% data variables.product.prodname_github_codespaces %} の有効化](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)」をご覧ください。 Organization または Enterprise アカウントで {% data variables.product.prodname_github_codespaces %} を使用するための使用制限を設定できます。 詳しくは、「[{% data variables.product.prodname_github_codespaces %} の利用上限の管理](/billing/managing-billing-for-github-codespaces/managing-the-spending-limit-for-github-codespaces)」をご覧ください。
|
||||
|
||||
If use of a codespace will be billed to an organization or enterprise, this is shown when the codespace is created. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)." Codespaces that are billed to an organization, or its parent enterprise, are owned by the organization and can be deleted an organization owner. For more information, see "[Deleting a codespace](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)."
|
||||
codespace の使用が Organization または Enterprise に課金される場合は、codespace の作成時に表示されます。 詳しくは、「[リポジトリの codespace を作成する](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)」を参照してください。 Organization またはその親 Enterprise に課金される codespace は、Organization が所有しており Organization の所有者を削除できます。 詳細については、「[codespace の削除](/codespaces/developing-in-codespaces/deleting-a-codespace#deleting-codespaces-in-your-organization)」を参照してください。
|
||||
|
||||
### Customizing {% data variables.product.prodname_github_codespaces %}
|
||||
### {% data variables.product.prodname_github_codespaces %} のカスタマイズ
|
||||
|
||||
To customize the runtimes and tools in your codespace, you can create one or more dev container configurations for your repository. Adding dev container configurations to your repository allows you to define a choice of different development environments that are appropriate for the work people will do in your repository.
|
||||
codespace のランタイムとツールをカスタマイズするには、リポジトリ用に 1 つ以上の開発コンテナー構成を作成できます。 開発コンテナー構成をリポジトリに追加すると、ユーザーがリポジトリで実行する作業に適したさまざまな開発環境の選択肢を定義できます。
|
||||
|
||||
If you create a codespace from a repository without any dev container configurations, {% data variables.product.prodname_github_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. If you create a codespace from a template, you might start with some initial configuration on top of the default image. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
開発コンテナーを構成せずに、リポジトリから codespace を作成する場合、{% data variables.product.prodname_github_codespaces %} によって、多くのツール、言語、ランタイム環境が含まれる既定の codespace イメージを含む環境に、リポジトリがクローンされます。 テンプレートから codespace を作成する場合は、既定のイメージの上のいくつかの初期構成から開始できます。 詳細については、[開発コンテナーの概要](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)に関するページをご覧ください。
|
||||
|
||||
You can personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository. You can use dotfiles to set shell aliases and preferences, or to install your personal preference of the tools you like to use. If you use {% data variables.product.prodname_github_codespaces %} in the browser, or in {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to give your codespace editor the same settings, keyboard shortcuts, snippets, and extensions that you have set up in your local installation of {% data variables.product.prodname_vscode %}.
|
||||
パブリック [ドットファイル](https://dotfiles.github.io/tutorials/) リポジトリを使用して、codespace 環境の側面をカスタマイズできます。 ドットファイルを使用して、シェルのエイリアスと基本設定を設定したり、使用するツールの個人用設定をインストールしたりすることができます。 ブラウザーまたは {% data variables.product.prodname_vscode %} で {% data variables.product.prodname_github_codespaces %} を使う場合は、[設定同期](https://code.visualstudio.com/docs/editor/settings-sync) を使用して、{% data variables.product.prodname_vscode %} のローカル インストールで設定したのと同じ設定、キーボード ショートカット、スニペット、拡張機能を codespace エディターに付与できます。
|
||||
|
||||
For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)".
|
||||
詳細については、「[codespace のカスタマイズ](/codespaces/customizing-your-codespace)」を参照してください。
|
||||
|
||||
## Billing for {% data variables.product.prodname_codespaces %}
|
||||
## {% data variables.product.prodname_codespaces %} への請求
|
||||
|
||||
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 variables.product.prodname_github_codespaces %} の価格、ストレージ、使用方法について詳しくは、「[{% data variables.product.prodname_github_codespaces %} の課金について](/billing/managing-billing-for-github-codespaces/about-billing-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)."
|
||||
{% data reusables.codespaces.codespaces-monthly-billing %} Organization オーナーと課金マネージャーが Organization での {% data variables.product.prodname_github_codespaces %} の利用制限を管理する方法については、「[{% data variables.product.prodname_github_codespaces %} の利用制限の管理](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces)」を参照してください。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Organization からのユーザのブロック
|
||||
intro: Organization のオーナーとモデレーターは、Organization のメンバーではないユーザーが Organization のリポジトリで共同作業を行うことをブロックできます。
|
||||
title: Blocking a user from your organization
|
||||
intro: Organization owners and moderators can block anyone who is not a member of the organization from collaborating on the organization's repositories.
|
||||
redirect_from:
|
||||
- /articles/blocking-a-user-from-your-organization
|
||||
- /github/building-a-strong-community/blocking-a-user-from-your-organization
|
||||
@@ -10,71 +10,68 @@ versions:
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Block from your org
|
||||
ms.openlocfilehash: 3264bb71f157c2ec34f42b859857eed4253379f3
|
||||
ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/10/2022
|
||||
ms.locfileid: '145090298'
|
||||
---
|
||||
組織の設定内、もしくはユーザーが作成した特定のコメントから、メンバー以外の人をブロックできます。 コメント内でユーザをブロックした場合、そのユーザに、ブロックされたこととその理由を説明する通知を送信できます。 そうしない場合、ブロックされたことはユーザには直接通知されません。 ユーザは、ブロックされても既存のコンテンツを削除できます。
|
||||
|
||||
ユーザをブロックする際には、無期限にブロックするか、一定の期間だけブロックするかを選択できます。 誰かを一定の期間だけブロックした場合、その期間が過ぎると自動的にブロックは解除されます。 無期限にブロックした場合、ブロックはいつでも手動で解除できます。 詳細については、「[組織からユーザーのブロックを解除する](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)」を参照してください。
|
||||
You can block non-members from within your organization's settings or from a specific comment made by a user. When you block a user in a comment, you can choose to send the user a notification explaining that they were blocked and why. Otherwise, the user is not directly notified that you've blocked them. Blocked users can still delete their existing content.
|
||||
|
||||
{% data reusables.organizations.blocking-a-user %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** 過熱した会話を鎮めるためにユーザーをブロックする場合、会話をロックすることにより、コラボレーターだけがコメントできるようになります。 詳細については、[会話のロック](/communities/moderating-comments-and-conversations/locking-conversations)に関するページを参照してください。
|
||||
**Tip:** If you're blocking a user because of a heated conversation, consider locking the conversation so only collaborators can comment. For more information, see "[Locking conversations](/communities/moderating-comments-and-conversations/locking-conversations)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
ユーザを Organization からブロックすると、以下のようになります:
|
||||
- そのユーザによる Organization のリポジトリの Watch は停止します。
|
||||
- そのユーザによる Star 付けや Issue 割り当てはリポジトリから削除されます。
|
||||
- Organization のリポジトリ内のディスカッションまたはコメントに対するユーザの投票が削除されます
|
||||
- そのユーザは、Organization のリポジトリのコラボレーターではなくなります。
|
||||
- Organization のリポジトリへのユーザのコントリビューションがカウントされなくなります
|
||||
- ブロックされたユーザへの保留中のリポジトリまたは Organization の招待はキャンセルされます
|
||||
At the time that you block a user from your organization:
|
||||
- The user stops watching your organization's repositories
|
||||
- The user's stars and issue assignments are removed from your repositories
|
||||
- The user's votes on discussions or comments in your organization's repositories are deleted
|
||||
- The user is removed as a collaborator on your organization's repositories
|
||||
- The user's contributions to your organization's repositories are no longer counted as contributions for them
|
||||
- Any pending repository or organization invitations to the blocked user are cancelled
|
||||
|
||||
ユーザを Organization からブロックすると、そのユーザは以下のことができなくなります:
|
||||
- Organization のリポジトリをコメント中でクロス参照すること
|
||||
- Organization のリポジトリのフォーク、Watch、ピン留め、Star 付け
|
||||
After you've blocked a user from your organization, they cannot:
|
||||
- Cross-reference your organization's repositories in comments
|
||||
- Fork, watch, pin, or star your organization's repositories
|
||||
|
||||
また、ブロックされたユーザは Organization のリポジトリで以下のことができません:
|
||||
- Issue のオープン
|
||||
- プルリクエストの送信、クローズ、マージ
|
||||
- Issue、プルリクエスト、あるいはコメントにコメントする
|
||||
- ウィキページを追加または編集する
|
||||
In your organization's repositories, blocked users also cannot:
|
||||
- Open issues
|
||||
- Send, close, or merge pull requests
|
||||
- Comment on issues, pull requests, or commits
|
||||
- Add or edit wiki pages
|
||||
|
||||
## コメントでユーザをブロックする
|
||||
## Blocking a user in a comment
|
||||
|
||||
1. ブロックしたい作者のコメントへ移動します。
|
||||
2. コメントの右上で {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} をクリックし、次に **[Block user]** をクリックします。
|
||||
|
||||
3. ブロックに期限を設定したい場合には、[Block user] ドロップダウンメニューを使い、ユーザをブロックしたい期間を選択します。
|
||||
|
||||
4. 組織内でそのユーザーが書いたすべてのコメントを隠したい場合は、 **[Hide this user's comments]\(このユーザーのコメントを隠す\)** を選択し、理由を選択します。
|
||||
|
||||
5. ブロックする理由をユーザーに通知したい場合は、 **[Send a notification to this user]\(このユーザーに通知を送信\)** を選択します。
|
||||
|
||||
6. ユーザーをブロックするには、 **[Block user from organization]\(Organization からユーザーをブロック\)** または **[Block user from organization and send message]\(Organization からユーザーをブロックしてメッセージを送信\)** をクリックします。
|
||||
![[ユーザーのブロック] ボタン](/assets/images/help/organizations/org-block-user-button-in-comment.png)
|
||||
1. Navigate to the comment whose author you would like to block.
|
||||
2. In the upper-right corner of the comment, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Block user**.
|
||||
|
||||
3. If you'd like to set a time limit for the block, use the Block user drop-down menu, and select the amount of time you'd like to block the user.
|
||||
|
||||
4. If you'd like to hide all of the comments the user has made in the organization, select **Hide this user's comments** and choose a reason.
|
||||
|
||||
5. If you'd like to notify the user why they're being blocked, select **Send a notification to this user**.
|
||||
|
||||
6. To block the user, click **Block user from organization** or **Block user from organization and send message**.
|
||||
|
||||
|
||||
## Organization 設定でユーザをブロックする
|
||||
## Blocking a user in the organization settings
|
||||
|
||||
1. 組織メンバーをブロックするにはまず、組織から[ユーザーを削除](/articles/removing-a-member-from-your-organization)します。
|
||||
1. To block an organization member, first [remove the user](/articles/removing-a-member-from-your-organization) from the organization.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.block_users %}
|
||||
6. [Block a user] の下で、ブロックしたいユーザ名を入力します。
|
||||
|
||||
7. ブロックに期限を設定したい場合には、[Block option] ドロップダウンメニューを使い、ユーザをブロックする期間を選択します。
|
||||
|
||||
8. **[Block user]** をクリックします。
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.block_users %}
|
||||
6. Under "Block a user", type the username of the user you'd like to block.
|
||||
|
||||
7. If you'd like to set a time limit for the block, use the Block options drop-down menu, and select the amount of time you'd like to block the user.
|
||||
|
||||
8. Click **Block user**.
|
||||
|
||||
|
||||
## 参考資料
|
||||
## Further reading
|
||||
|
||||
- "[組織からブロックされているユーザーの表示](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)"
|
||||
- "[組織からユーザーのブロックを解除する](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
|
||||
- "[個人アカウントからのユーザーのブロック](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
|
||||
- "[個人アカウントからユーザーのブロックを解除する](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
|
||||
- "[悪用あるいはスパムをレポートする](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
|
||||
- "[Viewing users who are blocked from your organization](/communities/maintaining-your-safety-on-github/viewing-users-who-are-blocked-from-your-organization)"
|
||||
- "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)"
|
||||
- "[Blocking a user from your personal account](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-personal-account)"
|
||||
- "[Unblocking a user from your personal account](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-personal-account)"
|
||||
- "[Reporting abuse or spam](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)"
|
||||
|
||||
@@ -80,7 +80,8 @@ Name | Description
|
||||
**`admin:enterprise`** | Gives full control of enterprise functionality. For more information, see "[Managing enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation.<br><br>Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`.
|
||||
 `manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %}
|
||||
 `manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %}
|
||||
 `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}
|
||||
 `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}{% ifversion read-audit-scope %}
|
||||
**`read:audit_log`** | Read audit log data.{% endif %}
|
||||
{% note %}
|
||||
|
||||
**Note:** Your OAuth App can request the scopes in the initial redirection. You
|
||||
|
||||
@@ -20,6 +20,8 @@ As a discussions maintainer, you can create community resources to encourage dis
|
||||
|
||||
When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
|
||||
|
||||
You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
|
||||
|
||||
For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
|
||||
|
||||
{% data reusables.discussions.you-can-label-discussions %}
|
||||
@@ -40,23 +42,63 @@ You can also move a discussion to a different category. It's not possible to mov
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click a category.
|
||||
|
||||
|
||||
|
||||
|
||||
## Pinning a discussion
|
||||
|
||||
You can pin up to four important discussions above the list of discussions for the repository or organization.
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
|
||||
|
||||
This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
|
||||
|
||||
|
||||
|
||||
### Pinning a discussion globally
|
||||
{% endif %}
|
||||
|
||||
You can pin up to four important discussions above the list of discussions for the repository or organization.
|
||||
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Optionally, customize the look of the pinned discussion.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Pin discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
### Pinning a discussion to a category
|
||||
|
||||
You can pin up to four important discussions above the list of discussions in a specific category.
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
|
||||
|
||||
|
||||
|
||||
2. To confirm, click **Pin to CATEGORY**.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Editing a pinned discussion
|
||||
|
||||
@@ -66,21 +108,60 @@ Editing a pinned discussion will not change the discussion's category. For more
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
 {% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Customize the look of the pinned discussion.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Pin discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Unpinning a discussion
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
|
||||
|
||||
### Unpinning a globally pinned discussion
|
||||
|
||||
You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Read the warning, then click **Unpin discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
### Unpinning a discussion from a category
|
||||
|
||||
You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
|
||||
|
||||
|
||||
|
||||
1. Read the warning, then click **Unpin from this category**.
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Transferring a discussion
|
||||
|
||||
@@ -89,12 +170,21 @@ To transfer a discussion, you must have permissions to create discussions in the
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**.
|
||||
|
||||
1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
 {% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Transfer discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Deleting a discussion
|
||||
|
||||
@@ -102,9 +192,16 @@ To transfer a discussion, you must have permissions to create discussions in the
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Read the warning, then click **Delete this discussion**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Converting issues based on labels
|
||||
|
||||
|
||||
@@ -1,41 +1,47 @@
|
||||
---
|
||||
title: ディスカッションをモデレートする
|
||||
intro: 'コメントを回答としてマークする、ディスカッションをロックまたはロック解除する、Issue をディスカッションに変換する、{% ifversion fpt or ghec %}コミュニティの行動規範{% elsif ghes > 3.5 %}Organization のコントリビューション ガイドライン{% endif %}に合わないコメント、ディスカッション、カテゴリの編集または削除を行うことで、健全なコラボレーションを促進することができます。'
|
||||
title: Moderating discussions
|
||||
intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
|
||||
permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
|
||||
versions:
|
||||
feature: discussions
|
||||
ms.openlocfilehash: 7d128c9beadb190f9c22c345cf0c3124b1dfcfcb
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147410116'
|
||||
---
|
||||
## ディスカッションのモデレートについて
|
||||
|
||||
{% data reusables.discussions.about-discussions %} リポジトリのトリアージ権限をお持ちの場合は、コメントを回答としてマークし、コミュニティに有益ではなくなった、または損害を与えているディスカッションをロックし、アイデアがまだ開発の初期段階にあるときに Issue をディスカッションに変換することで、リポジトリのディスカッションをモデレートするのに役立ちます。 同様に、Organization ディスカッションのソースリポジトリのトリアージ許可がある場合、その Organization のディスカッションをモデレートできます。
|
||||
|
||||
## コメントを回答としてマークする
|
||||
## About moderating discussions
|
||||
|
||||
{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
|
||||
|
||||
## Marking a comment as an answer
|
||||
|
||||
{% data reusables.discussions.marking-a-comment-as-an-answer %}
|
||||
|
||||
## ディスカッションをロックする
|
||||
## Locking discussions
|
||||
|
||||
会話全体が建設的でない場合や、コミュニティの行動規範または {% data variables.product.prodname_dotcom %} の[コミュニティ ガイドライン](/free-pro-team@latest/github/site-policy/github-community-guidelines)に違反している場合は、会話をロックするのが適切です。 会話をロックして、コミュニティへのお知らせとして使用するディスカッションへのコメントを防ぐこともできます。 会話をロックすると、リポジトリ (Organization ディスカッションのリースリポジトリ) への書き込み許可のあるユーザーは、ディスカッションで引き続きコメントできます。
|
||||
It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion.
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %}
|
||||
1. ディスカッションのリストで、ロックするディスカッションをクリックします。
|
||||
|
||||
1. ディスカッションの右余白で、 **[会話のロック]** をクリックします。
|
||||
1. 会話のロックに関する情報を読み、 **[このディスカッションでの会話をロック]** をクリックします。
|
||||
1. 会話のロックを解除する準備ができたら、 **[会話のロック解除]** をクリックし、 **[このディスカッションでの会話のロック解除]** をクリックします。
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
1. In the list of discussions, click the discussion you want to lock.
|
||||
|
||||
1. In the right margin of a discussion, click **Lock conversation**.
|
||||
1. Read the information about locking conversations and click **Lock conversation on this discussion**.
|
||||
1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**.
|
||||
|
||||
## Issue をディスカッションに変換する
|
||||
## Converting an issue to a discussion
|
||||
|
||||
Issue をディスカッションに変換すると、その Issue のコンテンツを使用してディスカッションが自動的に作成されます。 リポジトリ (Organization ディスカッションのリースリポジトリ) への書き込み許可のあるユーザーは、ラベルに基づき、issue を一括変換できます。 詳しくは、「[ディスカッションの管理](/discussions/managing-discussions-for-your-community/managing-discussions)」を参照してください。
|
||||
When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.repositories.sidebar-issues %}
|
||||
1. Issue のリストで、変換する Issue をクリックします。
|
||||
1. Issue の右余白にある **[ディスカッションに変換]** をクリックします。
|
||||
1. **[カテゴリの選択]** ドロップダウン メニューを選択し、ディスカッションのカテゴリをクリックします。
|
||||
1. **[わかりました、この Issue をディスカッションに変換します]** をクリックします。
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.repositories.sidebar-issues %}
|
||||
1. In the list of issues, click the issue you'd like to convert.
|
||||
1. In the right margin of an issue, click **Convert to discussion**.
|
||||
1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
|
||||
1. Click **I understand, convert this issue to a discussion**.
|
||||
|
||||
{% ifversion discussions-hide-comments-on-block %}
|
||||
## Blocking a user from your organization
|
||||
|
||||
Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."
|
||||
|
||||
{% data reusables.organizations.blocking-a-user %}
|
||||
{% endif %}
|
||||
|
||||
@@ -33,15 +33,16 @@ Once you are a verified {% data variables.product.prodname_global_campus %} stud
|
||||
- Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand.
|
||||
- Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)."
|
||||
|
||||
A free subscription for {% data variables.product.prodname_copilot %} is available to verified students with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
|
||||
|
||||
{% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
|
||||
{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits.
|
||||
- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)."
|
||||
- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)"
|
||||
|
||||
@@ -212,8 +212,8 @@ $ git remote rm destination
|
||||
# Remove remote
|
||||
$ git remote -v
|
||||
# Verify it's gone
|
||||
> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push)
|
||||
> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push)
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
@@ -23,7 +23,7 @@ versions:
|
||||
ghec: '*'
|
||||
layout: product-landing
|
||||
introLinks:
|
||||
quickstart: /github/getting-started-with-github/quickstart
|
||||
quickstart: /get-started/quickstart
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /github/getting-started-with-github/githubs-products
|
||||
|
||||
@@ -29,7 +29,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
|
||||
3. Select an owner for the forked repository.
|
||||
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.
|
||||
|
||||
5. Optionally, add a description of your fork.
|
||||
|
||||
@@ -184,7 +184,7 @@ For more information about how to push changes in {% data variables.product.prod
|
||||
|
||||
At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back.
|
||||
|
||||
To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://www.github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
|
||||
To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://github.com/<your_username>/Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**.
|
||||
|
||||
{% data variables.product.product_name %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**.
|
||||
|
||||
|
||||
@@ -23,11 +23,11 @@ children:
|
||||
- /about-your-organizations-news-feed
|
||||
- /viewing-insights-for-your-organization
|
||||
shortTitle: Collaborate with groups
|
||||
ms.openlocfilehash: 84851a7282452c4a8d31c420a4f82991cf1b6bd3
|
||||
ms.sourcegitcommit: 505b84dc7227e8a5d518a71eb5c7eaa65b38ce0e
|
||||
ms.openlocfilehash: dd6c9950c29328c2170f58045f3a0dfeafe03637
|
||||
ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147878682'
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148163467'
|
||||
---
|
||||
|
||||
|
||||
@@ -144,7 +144,7 @@ Organizations that use {% data variables.product.prodname_ghe_cloud %} can inter
|
||||
|
||||
{% else %}
|
||||
|
||||
You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.
|
||||
You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
|
||||
@@ -183,18 +183,18 @@ By default, you can only use npm packages hosted on your enterprise, and you wil
|
||||
{% data reusables.package_registry.authenticate-step %}
|
||||
{% data reusables.package_registry.create-npmrc-owner-step %}
|
||||
{% data reusables.package_registry.add-npmrc-to-repo-step %}
|
||||
4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency.
|
||||
1. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. Replace `<organization_name>/<package_name>` with your package dependency.
|
||||
|
||||
```json
|
||||
{
|
||||
"name": "@my-org/server",
|
||||
"version": "1.0.0",
|
||||
"description": "Server app that uses the @octo-org/octo-app package",
|
||||
"description": "Server app that uses the <organization_name>/<package_name> package",
|
||||
"main": "index.js",
|
||||
"author": "",
|
||||
"license": "MIT",
|
||||
"dependencies": {
|
||||
"@octo-org/octo-app": "1.0.0"
|
||||
"<organization_name>/<package_name>": "1.0.0"
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
@@ -26,11 +26,11 @@ children:
|
||||
- /deleting-a-repository
|
||||
- /restoring-a-deleted-repository
|
||||
shortTitle: Create & manage repositories
|
||||
ms.openlocfilehash: ec9aa9879765356ab7a1ba0f74017f55b18425a6
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.openlocfilehash: 06a0bfa43ca81b6b1feb2e796cacac051fb11749
|
||||
ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: '145132295'
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148163559'
|
||||
---
|
||||
|
||||
|
||||
@@ -32,6 +32,7 @@ Code navigation uses the open source [`tree-sitter`](https://github.com/tree-sit
|
||||
| PHP | ✅ | |
|
||||
| Python | ✅ | ✅ |
|
||||
| Ruby | ✅ | |
|
||||
| Rust | ✅ | |
|
||||
| TypeScript | ✅ | |
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Dependency review
|
||||
intro: 'The Dependency review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment.'
|
||||
title: 依存関係の確認
|
||||
intro: 依存関係の確認 API を使用すると、依存関係の変更やこの変更がセキュリティに及ぼす影響を把握したうえで、この変更を環境に追加することができます。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.6'
|
||||
@@ -10,8 +10,13 @@ topics:
|
||||
- API
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 9988c87ed4b0dcbe9c8a0694ebe0ca43d5bc336e
|
||||
ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148164231'
|
||||
---
|
||||
## 依存関係の確認 API について
|
||||
|
||||
## About the Dependency review API
|
||||
|
||||
The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
依存関係レビュー API を使用すると、依存関係の変更やこの変更がセキュリティに及ぼす影響を把握したうえで、この変更を環境に追加することができます。 既知の脆弱性を含むすべてのバージョン アップデートの脆弱性データを含め、リポジトリの 2 つのコミット間の依存関係の差分を確認することができます。 依存関係レビューの詳細については、「[依存関係のレビューについて](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)」を参照してください。
|
||||
|
||||
@@ -1,10 +1,7 @@
|
||||
---
|
||||
ms.openlocfilehash: 3def1c7efad50b8bfda097251abf28dd4a5f46df
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145089343"
|
||||
---
|
||||
1. **[Fork pull request workflows]\(pull request ワークフローのフォーク\)** で、オプションを選択します。 例: 
|
||||
1. **[保存]** をクリックして設定を適用します。
|
||||
1. Under **Fork pull request workflows**, select your options. For example:
|
||||
{% ifversion actions-private-fork-workflow-approvals %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
@@ -1,11 +1,4 @@
|
||||
---
|
||||
ms.openlocfilehash: 6c1dd36680cbcbf04fda2d18f14a828249715ff7
|
||||
ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 09/11/2022
|
||||
ms.locfileid: "145068146"
|
||||
---
|
||||
- **フォーク pull request からワークフローを実行する** - 読み取り専用権限を持ち、シークレットへのアクセス権を持たない `GITHUB_TOKEN` を使用して、フォーク pull request からワークフローを実行できます。
|
||||
- **pull request からワークフローに書き込みトークンを送信する** - フォークからの pull request で書き込み権限を持つ `GITHUB_TOKEN` を使用できます。
|
||||
- **pull request からワークフローにシークレットを送信する** - すべてのシークレットを pull request で利用できるようにします。
|
||||
- **Run workflows from fork pull requests** - Allows users to run workflows from fork pull requests, using a `GITHUB_TOKEN` with read-only permission, and with no access to secrets.
|
||||
- **Send write tokens to workflows from pull requests** - Allows pull requests from forks to use a `GITHUB_TOKEN` with write permission.
|
||||
- **Send secrets to workflows from pull requests** - Makes all secrets available to the pull request.{% ifversion actions-private-fork-workflow-approvals %}
|
||||
- **Require approval for fork pull request workflows** - Workflow runs on pull requests from collaborators without write permission will require approval from someone with write permission before they will run.{% endif %}
|
||||
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
ms.openlocfilehash: fec57b88af5ef5b7227d88a8c70e5a4b4bb9c769
|
||||
ms.sourcegitcommit: fdc4466e89467a7b13239e26c6042dc1428946b6
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: "148163826"
|
||||
---
|
||||
リポジトリへの書き込みアクセスを持つ保守担当者は、次の手順を使用して、承認を必要とする共同作成者からの pull request でワークフローをレビューして実行できます。
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
|
||||
1. プルリクエストで提案された変更を調べて、プルリクエストブランチでワークフローを快適に実行できることを確認します。 ワークフロー ファイルに影響を与える `.github/workflows/` ディレクトリで提案された変更には特に注意する必要があります。
|
||||
1. pull request ブランチでワークフローを実行することに慣れている場合は、{% octicon "comment-discussion" aria-label="The discussion icon" %} **[会話]** タブに戻り、[承認を待っているワークフロー] で **[承認して実行]** をクリックします。
|
||||
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 323e67dec23f2baa8b6e43779ed89e549d5ca198
|
||||
ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160776"
|
||||
---
|
||||
{% data variables.enterprise.prodname_managed_users_caps %}では、{% data variables.product.prodname_copilot %} を使うことができません。
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 1acdedabde1b516be6b8953861ed20cf6254ddb8
|
||||
ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: "148163482"
|
||||
---
|
||||
メンバーがユーザー アカウントを作成して管理できるようにするか、Enterprise で {% data variables.product.prodname_emus %} を使用してメンバーのアカウントを作成、管理できるようにするかを選ぶことができます。 メンバーが自分のアカウントを管理できるようにする場合は、SAML 認証を構成して、チームで使用される Web アプリケーションのセキュリティを強化し、ID とアクセスを一元化することもできます。
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
ms.openlocfilehash: adefefb787099214cf17f7b2276a8f44f3fe8e56
|
||||
ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f
|
||||
ms.openlocfilehash: 6dfaad4dc9dc813104183b2c9db41e480c9b27fb
|
||||
ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/10/2022
|
||||
ms.locfileid: "148160573"
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: "148163578"
|
||||
---
|
||||
1. Git に SSH 署名キーを設定するには、次のテキストを貼り付けて、 **/PATH/TO/KEY.PUB** の部分を、使いたい公開キーへのパスに置き換えます。
|
||||
```bash
|
||||
$ git config --global user.signingkey=/PATH/TO/.SSH/KEY.PUB
|
||||
$ git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: 44fb7593fc71c38604cb0e7b96ea0439c7028a1f
|
||||
ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: "148164226"
|
||||
---
|
||||
ユーザをブロックする際には、無期限にブロックするか、一定の期間だけブロックするかを選択できます。 誰かを一定の期間だけブロックした場合、その期間が過ぎると自動的にブロックは解除されます。 無期限にブロックした場合、ブロックはいつでも手動で解除できます。 詳細については、「[組織からユーザーのブロックを解除する](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)」を参照してください。
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
ms.openlocfilehash: a4b1ca4e0548ebc2be12a34e0bb1687e9e650038
|
||||
ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: ja-JP
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: "148163451"
|
||||
---
|
||||
README ファイルをリポジトリに追加して、プロジェクトに関する重要な情報を伝えることができます。 README は、リポジトリ ライセンス、引用ファイル{% ifversion fpt or ghec %}、コントリビューション ガイドライン、倫理規定{% elsif ghes %}、コントリビューション ガイドライン{% endif %}と並んで、プロジェクトに期待されるものを伝え、コントリビューションを管理しやすくします。
|
||||
@@ -505,6 +505,7 @@ translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-
|
||||
translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
|
||||
translations/ja-JP/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
|
||||
translations/ja-JP/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
|
||||
translations/ja-JP/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,broken liquid tags
|
||||
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
|
||||
@@ -530,7 +531,6 @@ translations/ja-JP/content/admin/code-security/managing-github-advanced-security
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
|
||||
translations/ja-JP/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
|
||||
@@ -720,7 +720,6 @@ translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scannin
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
|
||||
translations/ja-JP/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
|
||||
translations/ja-JP/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
|
||||
@@ -794,7 +793,6 @@ translations/ja-JP/content/codespaces/managing-your-codespaces/managing-encrypte
|
||||
translations/ja-JP/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/overview.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags
|
||||
translations/ja-JP/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags
|
||||
@@ -817,6 +815,7 @@ translations/ja-JP/content/codespaces/troubleshooting/working-with-support-for-g
|
||||
translations/ja-JP/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
|
||||
translations/ja-JP/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
|
||||
translations/ja-JP/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
|
||||
translations/ja-JP/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags
|
||||
translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
|
||||
translations/ja-JP/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
|
||||
@@ -847,6 +846,7 @@ translations/ja-JP/content/discussions/collaborating-with-your-community-using-d
|
||||
translations/ja-JP/content/discussions/guides/finding-your-discussions.md,broken liquid tags
|
||||
translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
|
||||
translations/ja-JP/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags
|
||||
translations/ja-JP/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,broken liquid tags
|
||||
translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
|
||||
translations/ja-JP/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags
|
||||
translations/ja-JP/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
|
||||
@@ -881,7 +881,7 @@ translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md,re
|
||||
translations/ja-JP/content/get-started/quickstart/create-a-repo.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/signing-up-for-a-new-github-account.md,rendering error
|
||||
translations/ja-JP/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
@@ -1014,7 +1014,6 @@ translations/ja-JP/content/rest/activity/notifications.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/apps/oauth-applications.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/codespaces/codespaces.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/dependency-graph/dependency-review.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/announcement.md,broken liquid tags
|
||||
translations/ja-JP/content/rest/enterprise-admin/billing.md,broken liquid tags
|
||||
@@ -1092,6 +1091,8 @@ translations/ja-JP/data/reusables/actions/ip-allow-list-self-hosted-runners.md,b
|
||||
translations/ja-JP/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/more-resources-for-ghes.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/private-repository-forks-configure.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/private-repository-forks-options.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/ref_name-description.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
|
||||
translations/ja-JP/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
|
||||
|
||||
|
Reference in New Issue
Block a user