зеркало из https://github.com/github/docs.git
New translation batch for ja (#30079)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report Co-authored-by: Peter Bengtsson <peterbe@github.com>
This commit is contained in:
docubot
GitHub
Родитель
8765c628ff
Коммит
1ab6e00328
|
|
@ -66,7 +66,7 @@ shortTitle: Your profile README
|
|||
- リポジトリがプライベートである。
|
||||
- リポジトリ名がユーザ名とマッチしなくなった。
|
||||
|
||||
The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. リポジトリをプライベートにする方法については、「[リポジトリの可視性を変更する](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)」を参照してください。
|
||||
The method you choose is dependant upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
|
||||
|
||||
## 参考リンク
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
## About accessibility settings
|
||||
|
||||
To accommodate your vision, hearing, motor, cognitive, or learning needs, you can customize the user interface for {% data variables.product.product_location %}.
|
||||
To create an experience on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} that fits your needs, you can customize the user interface. Accessibility settings can be essential for people with disabilities, but can be useful to anyone. For example, customization of keyboard shortcuts is essential to people who navigate using voice control, but can be useful to anyone when a keyboard shortcut for {% data variables.product.product_name %} clashes with another application shortcut.
|
||||
|
||||
## Managing accessibility settings
|
||||
|
||||
|
|
@ -20,7 +20,7 @@ You can decide whether you want to use some or all keyboard shortcuts on {% ifve
|
|||
|
||||
### Managing keyboard shortcuts
|
||||
|
||||
You can perform actions across the {% data variables.product.product_name %} website without using your mouse by using your keyboard instead. Keyboard shortcuts can be useful to save time for some people, but may interfere with accessibility if you don't intend to use the shortcuts.
|
||||
You can perform actions across the {% data variables.product.product_name %} website by using your keyboard alone. Keyboard shortcuts can be useful to save time, but can be activated accidentally or interfere with assistive technology.
|
||||
|
||||
By default, all keyboard shortcuts are enabled on {% data variables.product.product_name %}. 詳細は「[キーボードのショートカット](/get-started/using-github/keyboard-shortcuts)」を参照してください。
|
||||
|
||||
|
|
@ -28,16 +28,17 @@ By default, all keyboard shortcuts are enabled on {% data variables.product.prod
|
|||
{% data reusables.user-settings.accessibility_settings %}
|
||||
1. Under "Keyboard shortcuts", manage settings for your keyboard shortcuts.
|
||||
|
||||
- Optionally, to disable or enable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**. If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
|
||||
{%- ifversion command-palette %}
|
||||
- Optionally, to customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
|
||||
- To disable shortcut keys that don't use modifiers keys like <kbd>Control</kbd> or <kbd>Command</kbd>, under "General", deselect **Character keys**.
|
||||
- If you disable character keys, you may still be able to trigger shortcuts for your web browser, and you can still trigger shortcuts for {% data variables.product.product_name %} that use a modifier key.
|
||||
{%- ifversion command-palette %}
|
||||
- To customize the keyboard shortcuts for triggering the command palette, under "Command palette", use the drop-down menus to choose a keyboard shortcut. For more information, see "[{% data variables.product.company_short %} Command Palette](/get-started/using-github/github-command-palette)."
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion motion-management %}
|
||||
|
||||
### Managing motion
|
||||
|
||||
You can control how {% data variables.product.product_name %} displays animated images.
|
||||
You can control how {% data variables.product.product_name %} displays animated _.gif_ images.
|
||||
|
||||
By default, {% data variables.product.product_name %} syncs with your system-level preference for reduced motion. For more information, see the documentation or settings for your operating system.
|
||||
|
||||
|
|
@ -45,6 +46,6 @@ By default, {% data variables.product.product_name %} syncs with your system-lev
|
|||
{% data reusables.user-settings.accessibility_settings %}
|
||||
1. Under "Motion", manage settings for motion.
|
||||
|
||||
- Optionally, to control how {% data variables.product.product_name %} displays animaged images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
|
||||
- To control how {% data variables.product.product_name %} displays animated images, under "Autoplay animated images", select **Sync with system**, **Enabled**, or **Disabled**.
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -32,6 +32,15 @@ You may want to use a dark theme to reduce power consumption on certain devices,
|
|||
1. 使いたいテーマをクリックしてください。
|
||||
- If you chose a single theme, click a theme.
|
||||
|
||||
{%- ifversion ghes = 3.5 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: The light high contrast theme was unavailable in {% data variables.product.product_name %} 3.5.0, 3.5.1, 3.5.2, and 3.5.3. The theme is available in 3.5.4 and later. アップグレードに関する詳しい情報については、サイト管理者にお問い合わせください。
|
||||
|
||||
使用している{% data variables.product.product_name %}のバージョンの判断に関する詳しい情報については「[{% data variables.product.prodname_docs %}のバージョンについて](/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server)」を参照してください。
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %}
|
||||
- If you chose to follow your system settings, click a day theme and a night theme.
|
||||
|
||||
|
|
|
|||
|
|
@ -433,7 +433,7 @@ runs:
|
|||
|
||||
`entrypoint`の実行に関する詳しい情報については、「[{% data variables.product.prodname_actions %}のDockerfileサポート](/actions/creating-actions/dockerfile-support-for-github-actions/#entrypoint)」を参照してください。
|
||||
|
||||
### `post-entrypoint`
|
||||
### `runs.post-entrypoint`
|
||||
|
||||
**オプション** `run.entrypoint`アクションが完了した後に、クリーンアップスクリプトを実行できるようにしてくれます。 {% data variables.product.prodname_actions %}はこのアクションを起動するのに`docker run`を使います。 {% data variables.product.prodname_actions %}はスクリプトを同じベースイメージを使って新しいコンテナ内で実行するので、ランタイムの状態はメインの`entrypoint`コンテナとは異なります。 必要な状態には、ワークスペースや`HOME`内、あるいは`STATE_`変数としてアクセスできます。 The `post-entrypoint:` action always runs by default but you can override this using [`runs.post-if`](#runspost-if).
|
||||
|
||||
|
|
@ -475,7 +475,7 @@ runs:
|
|||
|
||||
## `branding`
|
||||
|
||||
アクションをパーソナライズして見分けられるようにするために、カラーと[Feather](https://feathericons.com/)アイコンを使ってバッジを作ることができます。 バッジは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)内のアクション名の隣に表示されます。
|
||||
**Optional** You can use a color and [Feather](https://feathericons.com/) icon to create a badge to personalize and distinguish your action. バッジは、[{% data variables.product.prodname_marketplace %}](https://github.com/marketplace?type=actions)内のアクション名の隣に表示されます。
|
||||
|
||||
### Example: Configuring branding for an action
|
||||
|
||||
|
|
|
|||
|
|
@ -457,6 +457,8 @@ jobs:
|
|||
{% endif %}
|
||||
| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %}
|
||||
| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}
|
||||
| `runner.debug` | `string` | {% data reusables.actions.runner-debug-description %}
|
||||
|
||||
{%- comment %}
|
||||
The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility. | `runner.workspace` | `string` | |
|
||||
{%- endcomment %}
|
||||
|
|
@ -506,7 +508,7 @@ jobs:
|
|||
|
||||
## `secrets` context
|
||||
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. シークレットに関する詳しい情報については「[暗号化されたシークレット](/actions/security-guides/encrypted-secrets)」を参照してください。
|
||||
The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
|
||||
|
||||
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. 詳しい情報については「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。
|
||||
|
||||
|
|
@ -538,13 +540,13 @@ The following example contents of the `secrets` context shows the automatic `GIT
|
|||
|
||||
For workflows with a matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
|
||||
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)」を参照してください。 |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `string` | `matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 詳細については、「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)」を参照してください。 |
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `strategy` | `オブジェクト` | このコンテキストは、実行しているジョブごとに異なります。 You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
|
||||
| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." |
|
||||
| `strategy.job-index` | `string` | The index of the current job in the matrix. **Note:** This number is a zero-based number. The first job's index in the matrix is `0`. |
|
||||
| `strategy.job-total` | `string` | The total number of jobs in the matrix. **Note:** This number **is not** a zero-based number. For example, for a matrix with four jobs, the value of `job-total` is `4`. |
|
||||
| `strategy.max-parallel` | `string` | `matrix`ジョブ戦略を使用するとき、同時に実行できるジョブの最大数。 For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)." |
|
||||
|
||||
### Example contents of the `strategy` context
|
||||
|
||||
|
|
@ -634,7 +636,7 @@ jobs:
|
|||
|
||||
## `needs`コンテキスト
|
||||
|
||||
`needs`コンテキストは、現在のジョブの依存関係として定義されたすべてのジョブからの出力を含みます。 ジョブの依存関係の定義に関する詳しい情報については「[{% data variables.product.prodname_actions %}のワークフロー構文](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)」を参照してください。
|
||||
`needs`コンテキストは、現在のジョブの依存関係として定義されたすべてのジョブからの出力を含みます。 For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)."
|
||||
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| -------------------------------------------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|
|
|
|||
|
|
@ -155,7 +155,7 @@ The default environment variables that {% data variables.product.prodname_dotcom
|
|||
{%- ifversion actions-runner-arch-envvars %}
|
||||
| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
|
||||
{%- endif %}
|
||||
| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} For example, `Hosted Agent` | | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} For example, `Windows` | | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} For example, `D:\a\_temp` |
|
||||
| `RUNNER_DEBUG` | {% data reusables.actions.runner-debug-description %} | | `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} For example, `Hosted Agent` | | `RUNNER_OS` | {% data reusables.actions.runner-os-description %} For example, `Windows` | | `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} For example, `D:\a\_temp` |
|
||||
{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %} For example, `C:\hostedtoolcache\windows` |{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ miniTocMaxHeadingLevel: 3
|
|||
|
||||
## About expressions
|
||||
|
||||
You can use expressions to programmatically set environment variables in workflow files and access contexts. 式で使えるのは、リテラル値、コンテキストへの参照、関数の組み合わせです。 リテラル、コンテキストへの参照、および関数を組み合わせるには、演算子を使います。 For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
|
||||
You can use expressions to programmatically set environment variables in workflow files and access contexts. 式で使えるのは、リテラル値、コンテキストへの参照、関数の組み合わせです。 リテラル、コンテキストへの参照、および関数を組み合わせるには、演算子を使います。 コンテキストに関する詳しい情報については「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。
|
||||
|
||||
式は、ステップを実行すべきか判断するための `if` 条件キーワードをワークフローファイル内に記述して使用するのが一般的です。 `if`条件が`true`になれば、ステップは実行されます。
|
||||
|
||||
|
|
@ -125,14 +125,22 @@ env:
|
|||
|
||||
`search`が`item` を含む場合、`true` を返します。 `search`が配列の場合、`item`が配列の要素であれば、この関数は`true`を返します。 `search`が文字列の場合、`item`が`search`の部分文字列であれば、この関数は`true`を返します。 この関数は大文字と小文字を区別しません。 値を文字列にキャストします。
|
||||
|
||||
#### 配列の利用例
|
||||
|
||||
`contains(github.event.issue.labels.*.name, 'bug')` returns whether the issue related to the event has a label "bug".
|
||||
|
||||
#### 文字列の使用例
|
||||
|
||||
`contains('Hello world', 'llo')` returns `true`.
|
||||
|
||||
#### Example using an object filter
|
||||
|
||||
`contains(github.event.issue.labels.*.name, 'bug')` returns `true` if the issue related to the event has a label "bug".
|
||||
|
||||
For more information, see "[Object filters](#object-filters)."
|
||||
|
||||
#### Example matching an array of strings
|
||||
|
||||
Instead of writing `github.event_name == "push" || github.event_name == "pull_request"`, you can use `contains()` with `fromJson()` to check if an array of strings contains an `item`.
|
||||
|
||||
For example, `contains(fromJson('["push", "pull_request"]'), github.event_name)` returns `true` if `github.event_name` is "push" or "pull_request".
|
||||
|
||||
### startsWith
|
||||
|
||||
`startsWith( searchString, searchValue )`
|
||||
|
|
@ -221,7 +229,7 @@ jobs:
|
|||
needs: job1
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix: ${{fromJSON(needs.job1.outputs.matrix)}}
|
||||
matrix: ${{ fromJSON(needs.job1.outputs.matrix) }}
|
||||
steps:
|
||||
- run: build
|
||||
```
|
||||
|
|
@ -235,7 +243,7 @@ jobs:
|
|||
```yaml
|
||||
name: print
|
||||
on: push
|
||||
env:
|
||||
env:
|
||||
continue: true
|
||||
time: 3
|
||||
jobs:
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ jobs:
|
|||
{% raw %}${{ runner.os }}-build-{% endraw %}
|
||||
{% raw %}${{ runner.os }}-{% endraw %}
|
||||
|
||||
- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == 'false' }}{% endraw %}
|
||||
- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
|
||||
name: List the state of node modules
|
||||
continue-on-error: true
|
||||
run: npm list
|
||||
|
|
@ -172,12 +172,12 @@ npm-d5ea0750
|
|||
|
||||
### Using the output of the `cache` action
|
||||
|
||||
You can use the output of the `cache` action to do something based on whether a cache hit or miss occurred. If there is a cache miss (an exact match for a cache was not found for the specified `key`), the `cache-hit` output is set to `false`.
|
||||
You can use the output of the `cache` action to do something based on whether a cache hit or miss occurred. When an exact match is found for a cache for the specified `key`, the `cache-hit` output is set to `true`.
|
||||
|
||||
In the example workflow above, there is a step that lists the state of the Node modules if a cache miss occurred:
|
||||
|
||||
```yaml
|
||||
- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit == 'false' }}{% endraw %}
|
||||
- if: {% raw %}${{ steps.cache-npm.outputs.cache-hit != 'true' }}{% endraw %}
|
||||
name: List the state of node modules
|
||||
continue-on-error: true
|
||||
run: npm list
|
||||
|
|
|
|||
|
|
@ -180,7 +180,7 @@ jobs:
|
|||
gh pr comment $PR --body 'It looks like you edited `package*.json`, `.github/CODEOWNERS`, or `.github/workflows/**`. We do not allow contributions to these files. Please review our [contributing guidelines](https://github.com/octo-org/octo-repo/blob/main/CONTRIBUTING.md) for what contributions are accepted.'
|
||||
```
|
||||
|
||||
For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)." For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
|
||||
コンテキストに関する詳しい情報については「[コンテキスト](/actions/learn-github-actions/contexts)」を参照してください。 For more information about event payloads, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads)."
|
||||
|
||||
## Further controlling how your workflow will run
|
||||
|
||||
|
|
|
|||
|
|
@ -20,9 +20,7 @@ After you purchase or start a trial of {% data variables.product.product_name %}
|
|||
|
||||
## 必要な環境
|
||||
|
||||
- Before you can deploy {% data variables.product.product_name %}, you must request access from your {% data variables.product.company_short %} account team. {% data variables.product.company_short %} will enable deployment of {% data variables.product.product_name %} for your Azure subscription. If you haven't already purchased {% data variables.product.product_name %}, you can contact {% data variables.contact.contact_enterprise_sales %} to check your eligibility for a trial.
|
||||
|
||||
- You must have permission to perform the `/register/action` operation for the resource provider in Azure. The permission is included in the `Contributor` and `Owner` roles. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in the Microsoft documentation.
|
||||
You must have permission to perform the `/register/action` operation for the resource provider in Azure. The permission is included in the `Contributor` and `Owner` roles. For more information, see [Azure resource providers and types](https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/resource-providers-and-types#register-resource-provider) in the Microsoft documentation.
|
||||
|
||||
## Deploying {% data variables.product.product_name %} with the {% data variables.actions.azure_portal %}
|
||||
|
||||
|
|
@ -40,7 +38,7 @@ The {% data variables.actions.azure_portal %} allows you to deploy the {% data v
|
|||
1. To review a summary of the proposed changes, click **Review + create**.
|
||||
1. After the validation process has completed, click **Create**.
|
||||
|
||||
The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. 詳しい情報については、「[{% data variables.product.product_name %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
|
||||
The email address you entered above will receive instructions on how to access your enterprise. After you have access, you can get started by following the initial setup steps. 詳しい情報については「[{% data variables.product.product_name %}の初期化](/admin/configuration/initializing-github-ae)」を参照してください。
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -57,7 +55,7 @@ You can use the {% data variables.actions.azure_portal %} to navigate to your {%
|
|||
|
||||
## 次のステップ
|
||||
|
||||
- Once your deployment has been provisioned, the next step is to initialize {% data variables.product.product_name %}. 詳しい情報については、「[{% data variables.product.product_name %} を初期化する](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
|
||||
- Once your deployment has been provisioned, the next step is to initialize {% data variables.product.product_name %}. 詳しい情報については「[{% data variables.product.product_name %}の初期化](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
|
||||
- If you're trying {% data variables.product.product_name %}, you can upgrade to a full license at any time during the trial period by contacting contact {% data variables.contact.contact_enterprise_sales %}. If you haven't upgraded by the last day of your trial, then the deployment is automatically deleted. {% data variables.product.product_name %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
|
||||
|
||||
## 参考リンク
|
||||
|
|
|
|||
|
|
@ -33,7 +33,8 @@ This article explains how site administrators can configure {% data variables.pr
|
|||
|
||||
## Review hardware requirements
|
||||
|
||||
{%- ifversion ghes %}
|
||||
|
||||
{%- ifversion ghes < 3.6 %}
|
||||
|
||||
The CPU and memory resources available to {% data variables.product.product_location %} determine the number of jobs that can be run concurrently without performance loss. {% data reusables.actions.minimum-hardware %}
|
||||
|
||||
|
|
@ -41,6 +42,13 @@ The peak quantity of concurrent jobs running without performance loss depends on
|
|||
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghes > 3.5 %}
|
||||
|
||||
The CPU and memory resources available to {% data variables.product.product_location %} determine the number of runners that can be configured without performance loss. {% data reusables.actions.minimum-hardware %}
|
||||
|
||||
The peak quantity of connected runners without performance loss depends on such factors as job duration, artifact usage, number of repositories running Actions, and how much other work your instance is doing not related to Actions. Internal testing at GitHub demonstrated the following performance targets for GitHub Enterprise Server on a range of CPU and memory configurations:
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- ifversion ghes = 3.2 %}
|
||||
|
||||
|
|
@ -80,6 +88,23 @@ Maximum concurrency was measured using multiple repositories, job duration of ap
|
|||
|
||||
{%- endif %}
|
||||
|
||||
|
||||
{%- ifversion ghes = 3.6 %}
|
||||
|
||||
{% data reusables.actions.hardware-requirements-3.6 %}
|
||||
|
||||
{% data variables.product.company_short %} measured maximum connected runners using multiple repositories, job duration of approximately 10 minutes, and 10 MB artifact uploads. You may experience different performance depending on the overall levels of activity on your instance.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
|
||||
- Beginning with {% data variables.product.prodname_ghe_server %} 3.6, {% data variables.product.company_short %} documents connected runners as opposed to concurrent jobs. Connected runners represents the most runners you can connect and expect to utilize. It should also be noted that connecting more runners than you can expect to utilize can negatively impact performance.
|
||||
|
||||
- Beginning with {% data variables.product.prodname_ghe_server %} 3.5, {% data variables.product.company_short %}'s internal testing uses 3rd generation CPUs to better reflect a typical customer configuration. This change in CPU represents a small portion of the changes to performance targets in this version of {% data variables.product.prodname_ghe_server %}.
|
||||
{% endnote %}
|
||||
{%- endif %}
|
||||
|
||||
If you plan to enable {% data variables.product.prodname_actions %} for the users of an existing instance, review the levels of activity for users and automations on the instance and ensure that you have provisioned adequate CPU and memory for your users. For more information about monitoring the capacity and performance of {% data variables.product.prodname_ghe_server %}, see "[Monitoring your appliance](/admin/enterprise-management/monitoring-your-appliance)."
|
||||
|
||||
For more information about minimum hardware requirements for {% data variables.product.product_location %}, see the hardware considerations for your instance's platform.
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ topics:
|
|||
permissions: Enterprise owners can use a recovery code to access an enterprise account.
|
||||
---
|
||||
|
||||
You can use a recovery code to access your enterprise account when a authentication configuration error or an issue with your identity provider (IdP) prevents you from using SSO.
|
||||
You can use a recovery code to access your enterprise account when an authentication configuration error or an issue with your identity provider (IdP) prevents you from using SSO.
|
||||
|
||||
In order to access your enterprise account this way, you must have previously downloaded and stored the recovery codes for your enterprise. For more information, see "[Downloading your enterprise account's single sign-on recovery codes](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes)."
|
||||
|
||||
|
|
|
|||
|
|
@ -85,6 +85,12 @@ For information on creating or accessing your access key ID and secret key, see
|
|||
{% ifversion streaming-oidc-s3 %}
|
||||
#### Setting up streaming to S3 with OpenID Connect
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Streaming to Amazon S3 with OpenID Connect is currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. In AWS, add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM. For more information, see [Creating OpenID Connect (OIDC) identity providers](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html) in the AWS documentation.
|
||||
|
||||
- For the provider URL, use `https://oidc-configuration.audit-log.githubusercontent.com`.
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@ For more information about billing for {% ifversion ghec %}{% data variables.pro
|
|||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.prodname_enterprise %} offers two deployment options. In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
|
||||
{% data variables.product.prodname_enterprise %}は、2つのデプロイメントの選択肢を提供します。 In addition to {% data variables.product.prodname_ghe_cloud %}, you can use {% data variables.product.prodname_ghe_server %} to host development work for your enterprise in your data center or supported cloud provider. {% endif %}Enterprise owners on {% data variables.product.prodname_dotcom_the_website %} can use an enterprise account to manage payment and licensing for {% data variables.product.prodname_ghe_server %} instances. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products#github-enterprise)" and "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -75,11 +75,3 @@ Prior to migration, if a user has created a package in the {% data variables.pro
|
|||
{% data reusables.enterprise-accounts.packages-tab %}
|
||||
1. To the right of the number of packages to migrate, click **Re-run migration**. During the migration, {% data variables.product.product_name %} will display progress on this page.
|
||||
1. If the migration fails again, start from step 1 and re-run the migration.
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
## Monitoring traffic to the registries
|
||||
|
||||
You can use visualize traffic to the Docker registry and {% data variables.product.prodname_container_registry %} from {% data variables.product.product_location %}'s monitor dashboard. The "GitHub Container Package Registry" graph can help you confirm that you've successfully migrated all images to the {% data variables.product.prodname_container_registry %}. In the graph, "v1" represents traffic to the Docker registry, and "v2" represents traffic to the {% data variables.product.prodname_container_registry %}. 詳しい情報については、「[モニターダッシュボードへのアクセス](/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard)」を参照してください。
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ shortTitle: Policies for security settings
|
|||
|
||||
## About policies for security settings in your enterprise
|
||||
|
||||
You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. For more information, see "[Keeping your organization secure](/organizations/keeping-your-organization-secure)."
|
||||
You can enforce policies to control the security settings for organizations owned by your enterprise on {% data variables.product.product_name %}. By default, organization owners can manage security settings. 詳しい情報については「[Organizationをセキュアに保つ](/organizations/keeping-your-organization-secure)」を参照してください。
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ Before you can require 2FA for all organizations owned by your enterprise, you m
|
|||
|
||||
- When you require two-factor authentication for your enterprise, members, outside collaborators, and billing managers (including bot accounts) in all organizations owned by your enterprise who do not use 2FA will be removed from the organization and lose access to its repositories. Organization のプライベートリポジトリのフォークへのアクセスも失います。 You can reinstate their access privileges and settings if they enable two-factor authentication for their account within three months of their removal from your organization. 詳しい情報については、「[Organization の以前のメンバーを回復する](/articles/reinstating-a-former-member-of-your-organization)」を参照してください。
|
||||
- Any organization owner, member, billing manager, or outside collaborator in any of the organizations owned by your enterprise who disables 2FA for their account after you've enabled required two-factor authentication will automatically be removed from the organization.
|
||||
- If you're the sole owner of a enterprise that requires two-factor authentication, you won't be able to disable 2FA for your user account without disabling required two-factor authentication for the enterprise.
|
||||
- If you're the sole owner of an enterprise that requires two-factor authentication, you won't be able to disable 2FA for your user account without disabling required two-factor authentication for the enterprise.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
title: Enterprise の人を表示する
|
||||
intro: Enterprise が所有するリソースやユーザライセンスの利用を監査するため、Enterprise のオーナーは、すべての Enterprise の管理者およびメンバーを表示できます。
|
||||
permissions: Enterprise owners can view the people in an enterprise.
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise-account/viewing-people-in-your-enterprise-account
|
||||
- /articles/viewing-people-in-your-enterprise-account
|
||||
|
|
@ -21,6 +22,20 @@ To audit access to your enterprise's resources and manage license usage, you can
|
|||
|
||||
You can see all current enterprise members and enterprise administrators{% ifversion ghec %}, as well as pending invitations to become members and administrators{% endif %}. To make it easier to consume this information, you can search and filter the lists.
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If {% data variables.product.prodname_github_connect %} is configured for your enterprise, when you filter a list of people in your enterprise, the following limitations apply.
|
||||
|
||||
- The filter for two-factor authentication (2FA) status does not show people who only have an account on a {% data variables.product.prodname_ghe_server %} instance.
|
||||
- If you combine the filter for accounts on {% data variables.product.prodname_ghe_server %} instances with either the filter for organizations or 2FA status, you will not see any results.
|
||||
|
||||
For more information about {% data variables.product.prodname_github_connect %}, see the following articles.
|
||||
|
||||
- "[About {% data variables.product.prodname_github_connect %}](/enterprise-server/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_server %} documentation
|
||||
- "[About {% data variables.product.prodname_github_connect %}](/github-ae@latest/admin/configuration/configuring-github-connect/about-github-connect)" in the {% data variables.product.prodname_ghe_managed %} documentation
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Viewing enterprise administrators
|
||||
|
||||
You can view all the current enterprise owners{% ifversion ghec %} and billing managers{% endif %} for your enterprise.{% ifversion enterprise-membership-view-improvements %} You can see useful information about each administrator{% ifversion ghec %} and filter the list by role{% endif %}.{% endif %} You can find a specific person by searching for their username or display name.
|
||||
|
|
|
|||
|
|
@ -18,4 +18,4 @@ shortTitle: GitHub Copilotの支払い
|
|||
|
||||
{% data variables.product.prodname_copilot %}プランは、月次もしくは年次のサイクルで利用できます。 月次の支払いサイクルを選択した場合、カレンダーの月ごとに$10が請求されます。 年次の支払いサイクルを選択した場合、年間で$100が請求されます。 支払いサイクルはいつでも変更でき、変更は次の支払いサイクルの開始時点から反映されます。
|
||||
|
||||
{% data variables.product.prodname_copilot %}の無料プランは、確認済みの学生、及び{% data variables.product.company_short %}上の人気のあるオープンソースリポジトリのメンテナが利用できます。 オープンソースメンテナとしての基準を満たしているなら、{% data variables.product.prodname_copilot %}プランのページにアクセスすると自動的に通知されます。 学生として現在{% data variables.product.prodname_student_pack %}を受け取っている場合、{% data variables.product.prodname_copilot %}プランのページにアクセスすると無料のプランも提供されます。 {% data variables.product.prodname_student_pack %}に関する詳しい情報については「[学生向け開発者パックへの応募](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack)」を参照してください。
|
||||
{% data variables.product.prodname_copilot %}の無料プランは、確認済みの学生、及び{% data variables.product.company_short %}上の人気のあるオープンソースリポジトリのメンテナが利用できます。 オープンソースメンテナとしての基準を満たしているなら、{% data variables.product.prodname_copilot %}プランのページにアクセスすると自動的に通知されます。 学生として現在{% data variables.product.prodname_student_pack %}を受け取っている場合、{% data variables.product.prodname_copilot %}プランのページにアクセスすると無料のプランも提供されます。 {% data variables.product.prodname_student_pack %}に関する詳しい情報については「[学生としての{% data variables.product.prodname_global_campus %}への応募](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)」を参照してください。
|
||||
|
|
|
|||
|
|
@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a
|
|||
|
||||
Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
|
||||
|
||||
{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer.
|
||||
{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage per day and $0.50 USD per GB of data transfer.
|
||||
|
||||
For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD.
|
||||
For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD.
|
||||
|
||||
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %}
|
||||
|
||||
|
|
|
|||
|
|
@ -29,11 +29,11 @@ shortTitle: 割引されたサブスクリプション
|
|||
|
||||
## 個人アカウントへの割引
|
||||
|
||||
{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 詳しい情報については、「[学生向け開発者パックに応募する](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)」を参照してください。
|
||||
{% data variables.product.prodname_free_user %} で学生と教員が無制限のパブリックリポジトリとプライベートリポジトリを使用できることに加えて、検証済みの学生は {% data variables.product.prodname_student_pack %} に申請し、{% data variables.product.prodname_dotcom %} パートナーからのさらなるメリットを受けていただけます。 詳しい情報については「[学生としての{% data variables.product.prodname_global_campus %}への応募](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)」を参照してください。
|
||||
|
||||
## 学校・大学向け割引
|
||||
|
||||
検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 詳しい情報については、「[教室や研究で {% data variables.product.prodname_dotcom %} を使う](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」を参照してください。 また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。
|
||||
検証済みの教職員は教育や学術研究の目的で {% data variables.product.prodname_team %} に申し込むことができます。 詳しい情報については「[教師のための{% data variables.product.prodname_global_campus %}](/free-pro-team@latest/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)」を参照してください。 また、学生のために教材をお求めいただくこともできます。 詳しい情報については [{% data variables.product.prodname_education %}](https://education.github.com/) にアクセスして下さい。
|
||||
|
||||
## 非営利目的や図書館への割引
|
||||
|
||||
|
|
|
|||
|
|
@ -204,15 +204,14 @@ To dismiss {% ifversion delete-code-scanning-alerts %}or delete{% endif %} alert
|
|||
|
||||
{% endif %}{% endif %}
|
||||
1. If you want to dismiss an alert, it's important to explore the alert first, so that you can choose the correct dismissal reason. Click the alert you'd like to explore.
|
||||
|
||||
|
||||
|
||||
1. Review the alert, then click {% ifversion comment-dismissed-code-scanning-alert %}**Dismiss alert** and choose, or type, a reason for closing the alert.
|
||||
|
||||
{% else %}**Dismiss** and choose a reason for closing the alert.
|
||||
{%- ifversion comment-dismissed-code-scanning-alert %}
|
||||
1. Review the alert, then click **Dismiss alert** and choose, or type, a reason for closing the alert.
|
||||
|
||||
{%- else %}
|
||||
1. Review the alert, then click **Dismiss** and choose a reason for closing the alert.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.code-scanning.choose-alert-dismissal-reason %}
|
||||
|
||||
{% data reusables.code-scanning.false-positive-fix-codeql %}
|
||||
|
|
|
|||
|
|
@ -118,7 +118,7 @@ Anyone with push access to a pull request can fix a {% data variables.product.pr
|
|||
|
||||
An alternative way of closing an alert is to dismiss it. You can dismiss an alert if you don't think it needs to be fixed. {% data reusables.code-scanning.close-alert-examples %} If you have write permission for the repository, the **Dismiss** button is available in code annotations and in the alerts summary. When you click **Dismiss** you will be prompted to choose a reason for closing the alert.
|
||||
{% ifversion comment-dismissed-code-scanning-alert %}
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -173,19 +173,28 @@ topics:
|
|||
|
||||
## クローズされたアラートの表示と更新
|
||||
|
||||
{% tip %}
|
||||
|
||||
**参考:** 再オープンできるアラートは、以前に却下したものだけです。 既に修復済みのクローズされたアラートは、再オープンできません。
|
||||
{% endtip %}
|
||||
オープンなすべてのアラートを見ることができ、以前に却下されたアラートを再オープンできます。 既に修復済みのクローズされたアラートは、再オープンできません。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-dependabot-alerts %}
|
||||
1. クローズされたアラートを表示だけするなら、**Closed（クローズ済み）**をクリックしてください。{% ifversion dependabot-bulk-alerts %} {% else %}
|
||||
{% endif %}
|
||||
1. 表示もしくは更新したいアラートをクリックしてください。{% ifversion dependabot-bulk-alerts %} {% else %}
|
||||
{% endif %}
|
||||
2. あるいはアラートが却下されていて、再度オープンしたい場合は、**Reopen（再オープン）**をクリックしてください。 既に修正済みのアラートは再オープンできません。 
|
||||
1. クローズされたアラートを単に表示するには**Closed（クローズ済み）**をクリックしてください。
|
||||
|
||||
{%- ifversion dependabot-bulk-alerts %}
|
||||
|
||||
{%- else %}
|
||||
|
||||
{%- endif %}
|
||||
1. 表示もしくは更新したいアラートをクリックしてください。
|
||||
|
||||
{%- ifversion dependabot-bulk-alerts %}
|
||||
|
||||
{%- else %}
|
||||
 {%- endif %}
|
||||
2. あるいはアラートが却下されていて、再度オープンしたい場合は、**Reopen（再オープン）**をクリックしてください。 既に修正済みのアラートは再オープンできません。
|
||||
|
||||
{% indented_data_reference reusables.enterprise.3-5-missing-feature spaces=3 %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -28,6 +28,8 @@ includeGuides:
|
|||
- /code-security/secret-scanning/configuring-secret-scanning-for-your-repositories
|
||||
- /code-security/secret-scanning/defining-custom-patterns-for-secret-scanning
|
||||
- /code-security/secret-scanning/managing-alerts-from-secret-scanning
|
||||
- /code-security/secret-scanning/protecting-pushes-with-secret-scanning
|
||||
- /code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection
|
||||
- /code-security/secret-scanning/secret-scanning-patterns
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
|
||||
|
|
|
|||
|
|
@ -21,5 +21,6 @@ children:
|
|||
- /managing-alerts-from-secret-scanning
|
||||
- /secret-scanning-patterns
|
||||
- /protecting-pushes-with-secret-scanning
|
||||
- /pushing-a-branch-blocked-by-push-protection
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Protecting pushes with secret scanning
|
||||
intro: 'You can use {% data variables.product.prodname_secret_scanning %} to prevent supported secrets from being pushed into your organization or repository by enabling push protection.'
|
||||
title: Secret scanningでのプッシュの保護
|
||||
intro: '{% data variables.product.prodname_secret_scanning %}を使い、プッシュ保護を有効化することによって、サポートされているシークレットがOrganizationもしくはリポジトリにプッシュされるのを避けることができます。'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
|
|
@ -13,36 +13,32 @@ topics:
|
|||
- Advanced Security
|
||||
- Alerts
|
||||
- Repositories
|
||||
shortTitle: Push protection
|
||||
shortTitle: プッシュ保護の有効化
|
||||
---
|
||||
|
||||
{% data reusables.secret-scanning.beta %}
|
||||
{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
|
||||
{% data reusables.secret-scanning.push-protection-beta %}
|
||||
|
||||
## About push protection for secrets
|
||||
## シークレットのプッシュ保護について
|
||||
|
||||
Up to now, {% data variables.product.prodname_secret_scanning_GHAS %} checks for secrets _after_ a push and alerts users to exposed secrets. {% data reusables.secret-scanning.push-protection-overview %}
|
||||
これまでのところ、{% data variables.product.prodname_secret_scanning_GHAS %}はプッシュの_後に_シークレットをチェックし、公開されたシークレットについてユーザにアラートします。 {% data reusables.secret-scanning.push-protection-overview %}
|
||||
|
||||
If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
|
||||
- generates an alert.
|
||||
- creates an alert in the "Security" tab of the repository.
|
||||
- adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
|
||||
コントリビューターがシークレットに対するプッシュ保護のブロックをバイパスした場合、{% data variables.product.prodname_dotcom %}は:
|
||||
- アラートを生成します。
|
||||
- リポジトリの "Security"タブにアラートを生成します。
|
||||
- Audit logにバイパスイベントを追加します。{% ifversion secret-scanning-push-protection-email %}
|
||||
- Organizationのオーナー、セキュリティ管理者、リポジトリ管理者に、関連するシークレットへのリンクと、プッシュが許可された理由を付けてメールアラートを送信します。{% endif %}
|
||||
|
||||
{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers.
|
||||
プッシュ保護でサポートされているシークレットとサービスプロバイダに関する情報については「[{% data variables.product.prodname_secret_scanning_caps %}パターン](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-push-protection)」を参照してください。
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
## プッシュ保護としての{% data variables.product.prodname_secret_scanning %}の有効化
|
||||
|
||||
{% data reusables.secret-scanning.secret-list-private-push-protection %}
|
||||
{% data variables.product.prodname_secret_scanning %}をプッシュ保護として使うには、Organizationもしくはリポジトリで{% data variables.product.prodname_GH_advanced_security %}と{% data variables.product.prodname_secret_scanning %}がどちらも有効化されていなければなりません。 詳しい情報については「[Organizationのセキュリティ及び分析設定の管理](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)」、「[リポジトリのセキュリティ及び分析設定の管理](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)」、「[{% data variables.product.prodname_GH_advanced_security %}について](/get-started/learning-about-github/about-github-advanced-security)」を参照してください。
|
||||
|
||||
## Enabling {% data variables.product.prodname_secret_scanning %} as a push protection
|
||||
組織の所有者、セキュリティマネージャー、およびリポジトリ管理者は、UI と API を介して {% data variables.product.prodname_secret_scanning %} のプッシュ保護を有効にできます。 詳しい情報については「[リポジトリ](/rest/reference/repos#update-a-repository)」を参照し、REST APIドキュメンテーションの「`security_and_analysis`のプロパティ」セクションを展開してください。
|
||||
|
||||
For you to use {% data variables.product.prodname_secret_scanning %} as a push protection, the organization or repository needs to have both {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_secret_scanning %} enabled. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)," "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)," and "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
|
||||
|
||||
Organization owners, security managers, and repository administrators can enable push protection for {% data variables.product.prodname_secret_scanning %} via the UI and API. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
|
||||
|
||||
### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for an organization
|
||||
### Organizationでのプッシュ保護としての{% data variables.product.prodname_secret_scanning %}の有効化
|
||||
|
||||
{% data reusables.organizations.navigate-to-org %}
|
||||
{% data reusables.organizations.org_settings %}
|
||||
|
|
@ -50,7 +46,7 @@ Organization owners, security managers, and repository administrators can enable
|
|||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.advanced-security.secret-scanning-push-protection-org %}
|
||||
|
||||
### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for a repository
|
||||
### リポジトリでのプッシュ保護としての{% data variables.product.prodname_secret_scanning %}の有効化
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
|
|
@ -58,70 +54,63 @@ Organization owners, security managers, and repository administrators can enable
|
|||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.advanced-security.secret-scanning-push-protection-repo %}
|
||||
|
||||
## プッシュ保護としてのSecret scanningのコマンドラインからの利用
|
||||
|
||||
## Using {% data variables.product.prodname_secret_scanning %} as a push protection from the command line
|
||||
{% data reusables.secret-scanning.push-protection-command-line-choice %}
|
||||
|
||||
When you attempt to push a supported secret to a repository or organization with {% data variables.product.prodname_secret_scanning %} as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the push. You can remove the secret from your commit or follow a provided URL to allow the push.
|
||||
コマンドラインでは、一度に最大で5つの検出されたシークレットが表示されます。 特定のシークレットが既にリポジトリ中で検出されており、アラートが既に存在するなら、{% data variables.product.prodname_dotcom %}はそのシークレットをブロックしません。
|
||||
|
||||
Up to five detected secrets will be displayed at a time on the command line. If a particular secret has already been detected in the repository and an alert already exists, {% data variables.product.prodname_dotcom %} will not block that secret.
|
||||
|
||||
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-remove-secret %} ブロックされたシークレットの修復に関する詳しい情報については「[プッシュ保護によってブロックされたブランチのプッシュ](/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection#resolving-a-blocked-push-on-the-command-line)」を参照してください。
|
||||
|
||||
If you need to remove the secret from your latest commit (that is, `HEAD`) on the branch being pushed and any earlier commits that contain the secret, you can remove the secret from `HEAD`, then squash the commits between when the commit was introduced and the first version of `HEAD` for which the secret has been removed.
|
||||
シークレットが本物であることが確認され、後で修復しようと考えているなら、できるかぎり早くそのシークレットを修復すべきです。 たとえば、そのシークレットを取り消して、リポジトリのコミット履歴から削除することになるでしょう。 露出してしまった実際のシークレットは、不正アクセスを避けるために取り消さなければなりません。 取り消す前にシークレットをまずローテートすることを検討すべきかもしれません。 詳しい情報については「[センシティブなデータをリポジトリから削除する](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)」を参照してください。
|
||||
|
||||
{% note %}
|
||||
{% data reusables.secret-scanning.push-protection-multiple-branch-note %}
|
||||
|
||||
**Notes**:
|
||||
### ブロックされたシークレットのプッシュの許可
|
||||
|
||||
* If your git configuration supports pushes to multiple branches, and not only to the default branch, your push may be blocked due to additional and unintended refs being pushed. For more information, see the [`push.default` options](https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault) in the Git Docs.
|
||||
* If {% data variables.product.prodname_secret_scanning %} upon a push times out, {% data variables.product.prodname_dotcom %} will still run a scan after the push.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Allowing a blocked secret to be pushed
|
||||
|
||||
If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
|
||||
|
||||
If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible. For example, you might revoke the secret and remove the secret from the repository's commit history. For more information, see "[Removing sensitive data from a repository](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
|
||||
プッシュしても安全だと信じられるシークレットを{% data variables.product.prodname_dotcom %}がブロックした場合、そのシークレットを許可し、許可されるべき理由を指定できます。
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-email %}
|
||||
|
||||
1. Visit the URL returned by {% data variables.product.prodname_dotcom %} when your push was blocked.
|
||||
|
||||
1. プッシュがブロックされたときに{% data variables.product.prodname_dotcom %}が返したURLにアクセスしてください。 
|
||||
{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
|
||||
1. Click **Allow me to push this secret**.
|
||||
2. Reattempt the push on the command line within three hours. If you have not pushed within three hours, you will need to repeat this process.
|
||||
1. **Allow me to push this secret（このシークレットのプッシュを許可）**をクリックしてください。
|
||||
2. 3時間以内のコマンドラインからプッシュを再試行してください。 3時間以内にプッシュをしなかった場合には、このプロセスを繰り返す必要があります。
|
||||
|
||||
{% ifversion secret-scanning-push-protection-web-ui %}
|
||||
## Using secret scanning as a push protection from the web UI
|
||||
## Web UIからのプッシュ保護としてのSecret scanningの利用
|
||||
|
||||
When you use the web UI to attempt to commit a supported secret to a repository or organization with secret scanning as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the commit. You will see a banner at the top of the page with information about the secret's location, and the secret will also be underlined in the file so you can easily find it.
|
||||
{% data reusables.secret-scanning.push-protection-web-ui-choice %}
|
||||
|
||||
|
||||
Web UIでは、{% data variables.product.prodname_dotcom %}は検出されたシークレットを一度に1つだけしか表示しません。 特定のシークレットが既にリポジトリ中で検出されており、アラートが既に存在するなら、{% data variables.product.prodname_dotcom %}はそのシークレットをブロックしません。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} will only display one detected secret at a time in the web UI. If a particular secret has already been detected in the repository and an alert already exists, {% data variables.product.prodname_dotcom %} will not block that secret.
|
||||
Web UIを使って、シークレットをファイルから削除できます。 シークレットを削除すると、ページ上部のバナーは変化し、変更をコミットできるようになったことを知らせてくれます。
|
||||
|
||||
You can remove the secret from the file using the web UI. Once you remove the secret, the banner at the top of the page will change and tell you that you can now commit your changes.
|
||||
|
||||
|
||||
|
||||
### シークレットに対するプッシュ保護のバイパス
|
||||
|
||||
### Bypassing push protection for a secret
|
||||
{% data reusables.secret-scanning.push-protection-remove-secret %} ブロックされたシークレットの修復に関する詳しい情報については「[プッシュ保護によってブロックされたブランチのプッシュ](/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection#resolving-a-blocked-push-in-the-web-ui)」を参照してください。
|
||||
|
||||
If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed. If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible.
|
||||
シークレットが本物であることが確認され、後で修復しようと考えているなら、できるかぎり早くそのシークレットを修復すべきです。 詳しい情報については「[センシティブなデータをリポジトリから削除する](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)」を参照してください。
|
||||
|
||||
プッシュしても安全だと信じられるシークレットを{% data variables.product.prodname_dotcom %}がブロックした場合、そのシークレットを許可し、許可されるべき理由を指定できます。
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-email %}
|
||||
|
||||
If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible.
|
||||
シークレットが本物であることが確認され、後で修復しようと考えているなら、できるかぎり早くそのシークレットを修復すべきです。
|
||||
|
||||
1. In the banner that appeared at the top of the page when {% data variables.product.prodname_dotcom %} blocked your commit, click **Bypass protection**.
|
||||
1. {% data variables.product.prodname_dotcom %}がコミットをブロックした際にページの上部に表示されるバナー内で、**Bypass protection（保護のバイパス）**をクリックしてください。
|
||||
{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Allow secret**.
|
||||
1. **Allow secret（シークレットの許可）**をクリックしてください。
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -0,0 +1,56 @@
|
|||
---
|
||||
title: プッシュ保護によってブロックされたブランチのプッシュ
|
||||
intro: '{% data variables.product.prodname_secret_scanning %}のプッシュ保護の機能は、リポジトリで漏洩したシークレットに対して積極的に保護を行います。 ブロックされたプッシュを解決し、検出されたシークレットが取り除かれれば、コマンドラインもしくはWeb UIから作業ブランチへ変更をプッシュできます。'
|
||||
product: '{% data reusables.gated-features.secret-scanning %}'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: secret-scanning-push-protection
|
||||
type: how_to
|
||||
topics:
|
||||
- Secret scanning
|
||||
- Advanced Security
|
||||
- Alerts
|
||||
- Repositories
|
||||
shortTitle: ブロックされたブランチのプッシュ
|
||||
---
|
||||
|
||||
## {% data variables.product.prodname_secret_scanning %}のプッシュ保護について
|
||||
|
||||
{% data variables.product.prodname_secret_scanning %}のプッシュ保護の機能は、リポジトリに変更をプッシュする前にシークレットをスキャンすることによって、セキュリティ漏洩を防ぐのに役立ちます。 {% data reusables.secret-scanning.push-protection-overview %} プッシュ保護でサポートされているシークレットとサービスプロバイダに関する情報については「[{% data variables.product.prodname_secret_scanning_caps %}パターン](/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-push-protection)」を参照してください。
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-remove-secret %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント** プッシュしても安全だと信じているシークレットを{% data variables.product.prodname_dotcom %}がブロックした場合、そのシークレットを許可してその理由を指定できます。 シークレットに対するプッシュ保護のバイパスに関する情報については、コマンドラインとWeb UIについてそれぞれ「[ブロックされたシークレットのプッシュの許可](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#allowing-a-blocked-secret-to-be-pushed)」及び「[シークレットのプッシュ保護のバイパス](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)を参照してください。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## ブロックされたプッシュのコマンドラインでの解決
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-command-line-choice %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-multiple-branch-note %}
|
||||
|
||||
ブロックされたシークレットが最新のコミットでブランチに導入されたなら、以下のガイダンスに従うことができます。
|
||||
|
||||
1. シークレットをコードから削除します。
|
||||
1. `git commit --amend`を使って変更をコミットします。
|
||||
1. `git push`で変更をプッシュします。
|
||||
|
||||
シークレットがGit履歴の以前のコミットに現れている場合でも、シークレットを削除できます。
|
||||
|
||||
1. `git log`を使ってプッシュのエラーに現れたどのコミットが履歴中の最初に来ているかを判断します。
|
||||
1. `git rebase -i <commit-id>~1`でインタラクティブなリベースを開始します。 <commit-id> commit-idはステップ1のコミットのidです。
|
||||
1. エディタに表示されたテキストの先頭行の`pick`を`edit`に変更して、編集するコミットを特定します。
|
||||
1. シークレットをコードから削除します。
|
||||
1. `git commit --amend`で変更をコミットします。
|
||||
1. `git rebase --continue`を実行してリベースを完了します。
|
||||
|
||||
## Web UIでのブロックされたコミットの解決
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-web-ui-choice %}
|
||||
|
||||
ブロックされたコミットをWeb UIで解決するには、シークレットをファイルから削除するか、**Bypass protection（保護のバイパス）**ドロップダウンを使ってシークレットを許可しなければなりません。 Web UIからのプッシュ保護のバイパスに関する詳しい情報については「[Secret scanningでのプッシュの保護](/code-security/secret-scanning/protecting-pushes-with-secret-scanning#bypassing-push-protection-for-a-secret)」を参照してください。
|
||||
|
||||
シークレットが本物であることを確認した場合、そのシークレットをファイルから削除しなければなりません。 シークレットを削除すると、ページ上部のバナーは変化し、変更をコミットできるようになったことを知らせてくれます。
|
||||
|
|
@ -21,10 +21,11 @@ redirect_from:
|
|||
{% ifversion fpt or ghec %}
|
||||
## About {% data variables.product.prodname_secret_scanning %} patterns
|
||||
|
||||
{% data variables.product.product_name %} maintains two different sets of {% data variables.product.prodname_secret_scanning %} patterns:
|
||||
{% data variables.product.product_name %} maintains these different sets of {% data variables.product.prodname_secret_scanning %} patterns:
|
||||
|
||||
1. **Partner patterns.** Used to detect potential secrets in all public repositories. For details, see "[Supported secrets for partner patterns](#supported-secrets-for-partner-patterns)."
|
||||
2. **Advanced security patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} enabled. {% ifversion ghec %} For details, see "[Supported secrets for advanced security](#supported-secrets-for-advanced-security)."{% endif %}
|
||||
2. **Advanced security patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} enabled. {% ifversion ghec %} For details, see "[Supported secrets for advanced security](#supported-secrets-for-advanced-security)."{% endif %}{% ifversion secret-scanning-push-protection %}
|
||||
3. **Push protection patterns.** Used to detect potential secrets in repositories with {% data variables.product.prodname_secret_scanning %} as a push protection enabled. For details, see "[Supported secrets for push protection](#supported-secrets-for-push-protection)."{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_GH_advanced_security %} can enable {% data variables.product.prodname_secret_scanning_GHAS %} on their repositories. For details of these patterns, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/secret-scanning/secret-scanning-patterns#supported-secrets-for-advanced-security).
|
||||
|
|
@ -59,6 +60,16 @@ If you use the REST API for secret scanning, you can use the `Secret type` to re
|
|||
{% data reusables.secret-scanning.partner-secret-list-private-repo %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion secret-scanning-push-protection %}
|
||||
## Supported secrets for push protection
|
||||
|
||||
{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers.
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
{% data reusables.secret-scanning.secret-list-private-push-protection %}
|
||||
|
||||
{% endif %}
|
||||
## Further reading
|
||||
|
||||
- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
|
||||
|
|
|
|||
|
|
@ -96,7 +96,8 @@ The recommended formats explicitly define which versions are used for all direct
|
|||
{% endif %}
|
||||
|
||||
{% ifversion github-actions-in-dependency-graph %}
|
||||
[†] {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions)."
|
||||
[†] {% data reusables.enterprise.3-5-missing-feature %} {% data variables.product.prodname_actions %} workflows must be located in the `.github/workflows/` directory of a repository to be recognized as manifests. Any actions or workflows referenced using the syntax `jobs[*].steps[*].uses` or `jobs.<job_id>.uses` will be parsed as dependencies. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
[‡] If you list your Python dependencies within a `setup.py` file, we may not be able to parse and list every dependency in your project.
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ children:
|
|||
- /developing-in-a-codespace
|
||||
- /using-source-control-in-your-codespace
|
||||
- /using-github-codespaces-for-pull-requests
|
||||
- /renaming-a-codespace
|
||||
- /deleting-a-codespace
|
||||
- /forwarding-ports-in-your-codespace
|
||||
- /default-environment-variables-for-your-codespace
|
||||
|
|
|
|||
|
|
@ -0,0 +1,54 @@
|
|||
---
|
||||
title: Renaming a codespace
|
||||
intro: 'You can use the {% data variables.product.prodname_cli %} to change the codespace display name to one of your choice.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Rename a codespace
|
||||
---
|
||||
|
||||
## About renaming a codespace
|
||||
|
||||
Each codespace is assigned an auto-generated display name. If you have multiple codespaces, the display name helps you to differentiate between codespaces. For example: `literate space parakeet`. You can change the display name for your codespace.
|
||||
|
||||
To find the display name of a codespace:
|
||||
|
||||
- On {% data variables.product.product_name %}, view your list of codespaces at https://github.com/codespaces.
|
||||
|
||||
|
||||
|
||||
- In the {% data variables.product.prodname_vscode %} desktop application, or the {% data variables.product.prodname_vscode_shortname %} web client, click the Remote Explorer. The display name is shown below the repository name. For example: `symmetrical space telegram` in the screenshot below.
|
||||
|
||||
|
||||
|
||||
- In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
|
||||
### Permanent codespace names
|
||||
|
||||
In addition to the display name, when you create a codespace, a permanent name is also assigned to the codespace. The name is a combination of your {% data variables.product.company_short %} handle, the repository name, and some random characters. For example: `octocat-myrepo-gmc7`. You can't change this name.
|
||||
|
||||
To find the permanent name of a codespace:
|
||||
|
||||
* On {% data variables.product.product_name %}, the permanent name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces.
|
||||
|
||||
|
||||
|
||||
* In a codespace, use this command in the terminal: `echo $CODESPACE_NAME`.
|
||||
* In a terminal window on your local machine, use this {% data variables.product.prodname_cli %} command: `gh codespace list`.
|
||||
|
||||
## Renaming a codespace
|
||||
|
||||
Changing the display name of a codespace can be useful if you have multiple codespaces that you will be using for an extended period. An appropriate name helps you identify a codespace that you use for a particular purpose. You can change the display name for your codespace by using the {% data variables.product.prodname_cli %}.
|
||||
|
||||
To rename a codespace, use the `gh codespace edit` subcommand:
|
||||
|
||||
```shell
|
||||
gh codespace edit -c <em>permanent name of the codespace</em> -d <em>new display name</em>
|
||||
```
|
||||
|
||||
In this example, replace `permanent name of the codespace` with the permanent name of the codespace. Replace `new display name` with the desired display name.
|
||||
|
|
@ -26,7 +26,7 @@ topics:
|
|||
ページでサポートされている標準的なマークアップや MediaWiki の構文を使ってウィキにリンクを作成できます。 例:
|
||||
|
||||
- ページが Markdown でレンダリングされる場合、リンクの構文は `[Link Text](full-URL-of-wiki-page)` です。
|
||||
- MediaWiki 構文では、リンクの構文は `[[Link Text|nameofwikipage]]` となります。
|
||||
- With MediaWiki syntax, the link syntax is `[[nameofwikipage|Link Text]]`.
|
||||
|
||||
## 画像の追加
|
||||
|
||||
|
|
|
|||
|
|
@ -59,7 +59,7 @@ You can create default contribution guidelines for your organization{% ifversion
|
|||
最初は悩むかもしれませんが、以下のコントリビューションガイドラインの例を役立ててください:
|
||||
|
||||
- Atom エディタ [コントリビューションガイドライン](https://github.com/atom/atom/blob/master/CONTRIBUTING.md)。
|
||||
- Ruby on Rails [コントリビューションガイドライン](https://github.com/rails/rails/blob/master/CONTRIBUTING.md).
|
||||
- Ruby on Rails [コントリビューションガイドライン](https://github.com/rails/rails/blob/main/CONTRIBUTING.md).
|
||||
- オープンガバメント [コントリビューションガイドライン](https://github.com/opengovernment/opengovernment/blob/master/CONTRIBUTING.md).
|
||||
|
||||
## 参考リンク
|
||||
|
|
|
|||
|
|
@ -42,4 +42,4 @@ To report an abusive repository: Go to your {% data variables.product.prodname_c
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- 「[{% data variables.product.prodname_community_exchange %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)」
|
||||
- ""[{% data variables.product.prodname_community_exchange %}について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)""
|
||||
|
|
|
|||
|
|
@ -1,12 +1,14 @@
|
|||
---
|
||||
title: About GitHub Community Exchange
|
||||
intro: 'Learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
|
||||
redirect_from:
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: About Community Exchange
|
||||
---
|
||||
|
||||
## {% data variables.product.prodname_community_exchange %}について
|
||||
## {% data variables.product.prodname_community_exchange %} について
|
||||
|
||||
{% data reusables.education.about-github-community-exchange-intro %}
|
||||
|
||||
|
|
@ -0,0 +1,40 @@
|
|||
---
|
||||
title: About GitHub Global Campus for students
|
||||
intro: '{% data variables.product.prodname_education %} は学生に対し、{% data variables.product.prodname_dotcom %} のパートナーからのさまざまな開発者ツールへの無料アクセスを含む実世界の体験を提供します。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-github-education-for-students
|
||||
- /github/teaching-and-learning-with-github-education/about-github-education-for-students
|
||||
- /articles/about-github-education-for-students
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: For students
|
||||
---
|
||||
|
||||
学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 As a student, you can also apply for {% data variables.product.prodname_education %} student benefits. Your {% data variables.product.prodname_education %} student benefits and resources are all included in {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits, all in one place. For more information, see "[Apply to GitHub Global Campus as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)" and [{% data variables.product.prodname_education %}](https://education.github.com/).
|
||||
|
||||
Before applying for Global Campus, check if your learning community is already partnered with us as a {% data variables.product.prodname_campus_program %} school. 詳しい情報については、「[{% data variables.product.prodname_campus_program %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)」を参照してください。
|
||||
|
||||
If you're a member of a school club, a teacher can apply for {% data variables.product.prodname_global_campus %} so your team can collaborate using {% data variables.product.prodname_team %}, which allows unlimited users and private repositories, for free. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
|
||||
|
||||
Once you are a verified {% data variables.product.prodname_global_campus %} student, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
|
||||
|
||||
|
||||
|
||||
## {% data variables.product.prodname_global_campus %} features for students
|
||||
|
||||
{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, students can:
|
||||
- Connect with a local Campus Expert. For more information on campus experts, see "[About Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-experts)."
|
||||
- Explore and claim offers for free industry tools from the [Student Developer Pack](https://education.github.com/pack).
|
||||
- See upcoming in-person and virtual events for students, curated by {% data variables.product.prodname_education %} and student leaders.
|
||||
- View assignments from [GitHub Classroom](https://classroom.github.com/) with upcoming due dates.
|
||||
- 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)."
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- "[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)"
|
||||
- 「[{% data variables.product.prodname_community_exchange %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)」
|
||||
|
|
@ -1,21 +1,22 @@
|
|||
---
|
||||
title: 学生向け開発者パックへの応募
|
||||
intro: '学生は {% data variables.product.prodname_student_pack %} に応募できます。これには {% data variables.product.prodname_dotcom %} パートナーからの特典が含まれます。'
|
||||
title: Apply to GitHub Global Campus as a student
|
||||
intro: 'As a student, you can apply to join {% data variables.product.prodname_global_campus %} and receive access to the student resources and benefits offered by {% data variables.product.prodname_education %}'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/apply-for-a-student-developer-pack
|
||||
- /github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack
|
||||
- /articles/applying-for-a-student-developer-pack
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Apply for a student pack
|
||||
shortTitle: Apply to Global Campus
|
||||
---
|
||||
|
||||
{% data reusables.education.about-github-education-link %}
|
||||
|
||||
## 要件
|
||||
|
||||
{% data variables.product.prodname_student_pack %} に適格であるには、以下を満たしていなければなりません:
|
||||
To be eligible for {% data variables.product.prodname_global_campus %}, including {% data variables.product.prodname_student_pack %} and other benefits, you must:
|
||||
- 高等学校、中等学校、大学、ホームスクールまたはそれに類似した教育機関で、学位を取得できるコースに現在在籍している
|
||||
- 学校が発行した検証可能なメールアドレスを持っているか、現在の在学状況を証明するドキュメントをアップロードしている
|
||||
- Have a [{% data variables.product.prodname_dotcom %} personal account](/articles/signing-up-for-a-new-github-account)
|
||||
|
|
@ -31,9 +32,9 @@ shortTitle: Apply for a student pack
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% data variables.product.prodname_student_pack %}の更新に関する詳しい情報については[期限切れと更新](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack/#expiration-and-renewals)を参照してください。
|
||||
For information about renewing your {% data variables.product.prodname_global_campus %} access, see "[Expiration and renewals](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student/#expiration-and-renewals)."
|
||||
|
||||
## {% data variables.product.prodname_student_pack %} への応募
|
||||
## Applying to {% data variables.product.prodname_global_campus %}
|
||||
|
||||
{% data reusables.education.benefits-page %}
|
||||
3. [Which best describes your academic status?（学業の状況を最もよく述べているのは？）] の下で、[** Student（学生）**] を選択してください。 
|
||||
|
|
@ -45,7 +46,7 @@ shortTitle: Apply for a student pack
|
|||
|
||||
## 期限切れと更新
|
||||
|
||||
{% data variables.product.prodname_student_pack %}アクセスが期限切れになった場合、まだあなたが適格であれば再応募できる場合があります。ただし、弊社のパートナーからの提供されているものの中には更新できないものがあります。 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 To reapply, simply return to https://education.github.com, click your profile picture, then click **Reverify your academic affiliation**.
|
||||
Once your {% data variables.product.prodname_global_campus %} access expires, you may reapply if you're still eligible, although some of our partner offers for {% data variables.product.prodname_student_pack %} cannot renew. 弊社のパートナーから期限付きで提供されているもののほとんどは、セットアップ後に開始されます。 To reapply, simply return to https://education.github.com, click your profile picture, then click **Reverify your academic affiliation**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -1,17 +1,18 @@
|
|||
---
|
||||
title: 学業でのGitHubの使用
|
||||
title: GitHub Global Campus for students
|
||||
intro: '学生として、{% data variables.product.prodname_dotcom %} を使用して学校のプロジェクトで共同作業を行い、現場経験を積んでください。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/use-github-for-your-schoolwork
|
||||
- /github/teaching-and-learning-with-github-education/using-github-for-your-schoolwork
|
||||
- /articles/using-github-for-your-schoolwork
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork
|
||||
versions:
|
||||
fpt: '*'
|
||||
children:
|
||||
- /about-github-education-for-students
|
||||
- /apply-for-a-student-developer-pack
|
||||
- /why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /about-github-global-campus-for-students
|
||||
- /apply-to-github-global-campus-as-a-student
|
||||
- /why-wasnt-my-application-to-global-campus-for-students-approved
|
||||
- /about-github-community-exchange
|
||||
shortTitle: For your schoolwork
|
||||
shortTitle: About Global Campus for students
|
||||
---
|
||||
|
||||
|
|
@ -0,0 +1,74 @@
|
|||
---
|
||||
title: Why wasn't my application to Global Campus for students approved?
|
||||
intro: 'Review common reasons that applications for {% data variables.product.prodname_global_campus %} are not approved and learn tips for reapplying successfully.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /articles/why-was-my-application-for-a-student-developer-pack-denied
|
||||
- /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved
|
||||
- /articles/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Application not approved
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**ヒント:** {% data reusables.education.about-github-education-link %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 所属文書の不明確な証明
|
||||
|
||||
アップロードした画像に記載されている日付またはスケジュールが資格条件に適合していない場合、在学状況の証明が追加で必要です。
|
||||
|
||||
アップロードした画像が、あなたの現在の在学状況を明示していない場合や、アップロードした画像が不鮮明な場合は、在学状況の証明が追加で必要です。 {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
## 未確認ドメインを持つ学術メールの使用
|
||||
|
||||
学術メールアドレスに未検証ドメインが含まれている場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
## 緩い電子メールポリシーを持つ学校からの学術電子メールの使用
|
||||
|
||||
学校が有料学生登録の前にメールアドレスを発行する場合、学術ステータスのさらなる証明が必要となります。 {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
学校のドメインに関するその他の質問や懸念がある場合は、学校の IT スタッフにお問い合わせください。
|
||||
|
||||
## すでに使用されている学術メールアドレス
|
||||
|
||||
If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**メモ:** 複数の個別アカウントを維持することは、{% data variables.product.prodname_dotcom %} [利用規約](/articles/github-terms-of-service/#3-account-requirements)に反しています。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you have more than one personal account, you must merge your accounts. 割引を保持するには、割引を付与されたアカウントをそのままにします。 すべてのメールアドレスを保持アカウントに追加することで、保持アカウントの名前を変更したり、コントリビューション履歴を保存したりできます。
|
||||
|
||||
詳しい情報については、以下を参照してください。
|
||||
- "[Merging multiple personal accounts](/articles/merging-multiple-user-accounts)"
|
||||
- 「[{% data variables.product.prodname_dotcom %} ユーザ名を変更する](/articles/changing-your-github-username)」
|
||||
- 「[メールアドレスを {% data variables.product.prodname_dotcom %} アカウントに追加する](/articles/adding-an-email-address-to-your-github-account)」
|
||||
|
||||
## 対象外の学生ステータス
|
||||
|
||||
以下の場合、{% data variables.product.prodname_student_pack %} の対象外となります:
|
||||
- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study.
|
||||
- 取得を目指している学位が、現学期で終わる場合。
|
||||
- 13 歳未満の場合。
|
||||
|
||||
インストラクターは、教室での使用に対して、{% data variables.product.prodname_education %} 割引を適用できます。 If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %}
|
||||
- "[Apply to {% data variables.product.prodname_global_campus %} as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)"
|
||||
|
|
@ -0,0 +1,35 @@
|
|||
---
|
||||
title: About GitHub Global Campus for teachers
|
||||
intro: '{% data variables.product.prodname_global_campus %} offers teachers a central place to access tools and resources for working more effectively inside and outside of the classroom.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers
|
||||
- /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
|
||||
- /articles/about-github-education-for-educators-and-researchers
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: For teachers
|
||||
---
|
||||
|
||||
As a faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_global_campus %}, which includes {% data variables.product.prodname_education %} benefits and resources. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
|
||||
|
||||
{% data variables.product.prodname_global_campus %} is a portal that allows the GitHub Education Community to access their education benefits, all in one place. Once you are a verified {% data variables.product.prodname_global_campus %} teacher, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
|
||||
|
||||
|
||||
|
||||
個人の割引を適用する前に、あなたの学習コミュニティがすでに弊社と{% data variables.product.prodname_campus_program %}学校としてパートナーになっているかを確認してください。 詳しい情報については、「[{% data variables.product.prodname_campus_program %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program)」を参照してください。
|
||||
|
||||
## {% data variables.product.prodname_global_campus %} features for teachers
|
||||
|
||||
{% data variables.product.prodname_global_campus %} is a portal from which you can access your {% data variables.product.prodname_education %} benefits and resources, all in one place. On the {% data variables.product.prodname_global_campus %} portal, teachers of all levels can:
|
||||
{% data reusables.education.apply-for-team %}
|
||||
- View an overview of your active [{% data variables.product.prodname_classroom %}](https://classroom.github.com), including recent assignments and your class's progress at a glance, as well as links to {% data variables.product.prodname_classroom %}.
|
||||
- View and interact with [{% data variables.product.prodname_discussions %}](https://github.com/orgs/community/discussions/categories/github-education) posted by your peers from around the world to discuss current trends in technology education, and see the latest posts from our [{% data variables.product.prodname_education %} blog](https://github.blog/category/education/).
|
||||
- See student events curated by {% data variables.product.prodname_education %} and student leaders.
|
||||
- Stay in the know on what the student 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.
|
||||
- Request a {% data variables.product.prodname_dotcom %} swag bag with educational materials and goodies for your students.
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- [学生向け {% data variables.product.prodname_global_campus %}について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 教育者割引または研究者割引への応募
|
||||
intro: '教育者もしくは研究者は、Organization アカウントに対して無料で {% data variables.product.prodname_team %} を受けるために応募できます。'
|
||||
title: Apply to GitHub Global Campus as a teacher
|
||||
intro: 'If you''re a teacher, you can apply to join {% data variables.product.prodname_global_campus %} and receive access to the resources and benefits of {% data variables.product.prodname_education %}.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/apply-for-an-educator-or-researcher-discount
|
||||
- /github/teaching-and-learning-with-github-education/applying-for-an-educator-or-researcher-discount
|
||||
|
|
@ -10,12 +10,13 @@ redirect_from:
|
|||
- /articles/applying-for-a-discount-for-your-first-robotics-team
|
||||
- /articles/applying-for-an-educator-or-researcher-discount
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Apply for a discount
|
||||
shortTitle: Apply to Global Campus
|
||||
---
|
||||
|
||||
## 教育者および研究者に対する割引について
|
||||
## About teacher discounts
|
||||
|
||||
{% data reusables.education.about-github-education-link %}
|
||||
|
||||
|
|
@ -23,7 +24,7 @@ shortTitle: Apply for a discount
|
|||
|
||||
For more information about personal accounts on {% data variables.product.product_name %}, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/github/getting-started-with-github/signing-up-for-a-new-github-account)."
|
||||
|
||||
## 教育者割引または研究者割引に応募する
|
||||
## Applying to {% data variables.product.prodname_global_campus %}
|
||||
|
||||
{% data reusables.education.benefits-page %}
|
||||
{% data reusables.education.click-get-teacher-benefits %}
|
||||
|
|
@ -35,7 +36,7 @@ For more information about personal accounts on {% data variables.product.produc
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- [教育者あるいは研究者割引が承認されなかった理由は？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)
|
||||
- "[Why wasn't my application to Global Campus for teachers approved?](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
|
||||
- [{% data variables.product.prodname_education %}](https://education.github.com)
|
||||
- [{% data variables.product.prodname_classroom %}ビデオ](https://classroom.github.com/videos)
|
||||
- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
title: GitHub Global Campus for teachers
|
||||
intro: 'As a teacher, use {% data variables.product.prodname_dotcom %} to collaborate on your work in a classroom, student or research group, and more.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research
|
||||
- /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research
|
||||
- /articles/using-github-in-your-classroom-and-research
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research
|
||||
versions:
|
||||
fpt: '*'
|
||||
children:
|
||||
- /about-github-global-campus-for-teachers
|
||||
- /apply-to-github-global-campus-as-a-teacher
|
||||
- why-wasnt-my-application-to-global-campus-for-teachers-approved
|
||||
shortTitle: 'About Global Campus for teachers'
|
||||
---
|
||||
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: 教育者または研究者割引の申請が承認されなかったのはなぜですか？
|
||||
intro: 教育者または研究者割引の申請が承認されていない一般的な理由を確認し、正常に再申請するためのヒントを学びます。
|
||||
title: Why wasn't my application to Global Campus for teachers approved?
|
||||
intro: 'Review common reasons that applications for {% data variables.product.prodname_global_campus %} are not approved and learn tips for reapplying successfully.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
- /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
|
|
@ -8,6 +8,7 @@ redirect_from:
|
|||
- /articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved
|
||||
- /articles/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Application not approved
|
||||
|
|
@ -41,8 +42,8 @@ shortTitle: Application not approved
|
|||
|
||||
## 学生以外が Student Developer Pack を申請する
|
||||
|
||||
教育者や研究者は、[{% data variables.product.prodname_student_pack %}](https://education.github.com/pack)に付属のパートナーオファーの対象にはなりません。 再度申し込む際には、ご自身の学術ステータスを説明するものとして必ず [**Faculty**] (教職員) を選択してください。
|
||||
Teachers are not eligible for the partner offers that come with the [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack). 再度申し込む際には、ご自身の学術ステータスを説明するものとして必ず [**Faculty**] (教職員) を選択してください。
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- 「[教育者・研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」
|
||||
- "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)"
|
||||
|
|
@ -10,7 +10,7 @@ versions:
|
|||
fpt: '*'
|
||||
children:
|
||||
- /use-github-at-your-educational-institution
|
||||
- /use-github-for-your-schoolwork
|
||||
- /use-github-in-your-classroom-and-research
|
||||
- /github-global-campus-for-students
|
||||
- /github-global-campus-for-teachers
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,23 +0,0 @@
|
|||
---
|
||||
title: Campus Advisorsについて
|
||||
intro: 'インストラクターあるいはメンターとして、Campus Advisorsトレーニング及びサポートと共に学校での{% data variables.product.prodname_dotcom %}の利用について学んでください。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-campus-advisors
|
||||
- /github/teaching-and-learning-with-github-education/about-campus-advisors
|
||||
- /articles/about-campus-advisors
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors
|
||||
versions:
|
||||
fpt: '*'
|
||||
---
|
||||
|
||||
教授、教師、メンバーはCampus Advisorsオンライントレーニングを使ってGitと{% data variables.product.prodname_dotcom %}をマスターし、{% data variables.product.prodname_dotcom %}で生徒に教えるためのベストプラクティスを学ぶことができます。 詳しい情報については[Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈:** インストラクターとして、学生のために {% data variables.product.product_location %} でアカウントを作成することはできません。 学生は {% data variables.product.product_location %} で自分のアカウントを作成する必要があります。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
教師は{% data variables.product.prodname_education %}でソフトウェア開発のコースを管理できます。 {% data variables.product.prodname_classroom %}では、{% data variables.product.product_name %}を使用してコードの配布、フィードバックの提供、コースワークの管理が行えます。 詳しい情報については、「[{% data variables.product.prodname_classroom %}でのコースワーク管理](/education/manage-coursework-with-github-classroom)」を参照してください。
|
||||
|
||||
あなたの学校が {% data variables.product.prodname_dotcom %} と {% data variables.product.prodname_campus_program %} スクールとしてパートナーになっていない場合は、個別に {% data variables.product.prodname_dotcom %} の利用の割引を申請できます。 詳しい情報については、「[学校の勉強での {% data variables.product.prodname_dotcom %} の使用](/education/teach-and-learn-with-github-education/use-github-for-your-schoolwork)」または「[クラスや勉強での {% data variables.product.prodname_dotcom %} の使用](/education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research/)」を参照してください。
|
||||
|
|
@ -12,4 +12,4 @@ versions:
|
|||
|
||||
{% data variables.product.prodname_dotcom %}Campus Expertsとして、公の場でのスピーチのスキル、テクニカルライティング、コミュニティのリーダーシップ、ソフトウェア開発のスキルを学んでください。
|
||||
|
||||
学生のリーダー及び教師に対するトレーニングプログラムについて詳しく学ぶには、[{% data variables.product.prodname_dotcom %}Campus Experts](https://education.github.com/students/experts)及び[ Campus Advisors](https://education.github.com/teachers/advisors)を参照してください。
|
||||
To learn more about training programs for student leaders, see "[{% data variables.product.prodname_dotcom %} Campus Experts](https://education.github.com/students/experts)."
|
||||
|
|
|
|||
|
|
@ -7,6 +7,7 @@ redirect_from:
|
|||
- /articles/about-github-education
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-campus-program
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: GitHub Campus Program
|
||||
|
|
@ -15,7 +16,7 @@ shortTitle: GitHub Campus Program
|
|||
|
||||
- No-cost access to {% data variables.product.prodname_ghe_cloud %} and {% data variables.product.prodname_ghe_server %} for all of your technical and academic departments
|
||||
- 50,000 {% data variables.product.prodname_actions %} minutes and 50 GB {% data variables.product.prodname_registry %} storage
|
||||
- Teacher training to master Git and {% data variables.product.prodname_dotcom %} with our [Campus Advisor program](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
|
||||
- Teacher training to master Git and {% data variables.product.prodname_dotcom %}
|
||||
- Exclusive access to new features, GitHub Education-specific swag, and free developer tools from {% data variables.product.prodname_dotcom %} partners
|
||||
- Automated access to premium {% data variables.product.prodname_education %} features, like the {% data variables.product.prodname_student_pack %}
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,6 @@ versions:
|
|||
children:
|
||||
- /about-github-campus-program
|
||||
- /about-campus-experts
|
||||
- /about-campus-advisors
|
||||
shortTitle: At your institution
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -1,25 +0,0 @@
|
|||
---
|
||||
title: 学生のためのGitHub Educationについて
|
||||
intro: '{% data variables.product.prodname_education %} は学生に対し、{% data variables.product.prodname_dotcom %} のパートナーからのさまざまな開発者ツールへの無料アクセスを含む実世界の体験を提供します。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-github-education-for-students
|
||||
- /github/teaching-and-learning-with-github-education/about-github-education-for-students
|
||||
- /articles/about-github-education-for-students
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-students
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: For students
|
||||
---
|
||||
|
||||
{% data reusables.education.about-github-education-link %}
|
||||
|
||||
学校のプロジェクトで{% data variables.product.prodname_dotcom %}を利用することは、他者とコラボレーションして実世界の体験を見てもらうためのポートフォリオを構築するための実際的な方法です。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} アカウントを持つ誰もが、{% data variables.product.prodname_free_user %} での無制限のパブリックおよびプライベートリポジトリで協業できます。 As a student, you can also apply for GitHub Student benefits. 詳しい情報については、「[学生向け開発者パックへの応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)」および [{% data variables.product.prodname_education %}](https://education.github.com/) を参照してください。
|
||||
|
||||
あなたが FIRST robotics club のメンバーなら、あなたの指導者はチームが {% data variables.product.prodname_team %} を使って協力し合うことができるよう、教育者割引に応募できます。これによって、無制限のユーザとプライベートリポジトリが無料で提供されます。 詳しい情報については、 「[教育者割引または研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)」を参照してください。
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- [教育者および研究者のための {% data variables.product.prodname_education %} について](/articles/about-github-education-for-educators-and-researchers)
|
||||
- 「[{% data variables.product.prodname_community_exchange %} について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)」
|
||||
|
|
@ -1,72 +0,0 @@
|
|||
---
|
||||
title: Why wasn't my application for a student developer pack approved?
|
||||
intro: 'Review common reasons that applications for the {% data variables.product.prodname_student_pack %} are not approved and learn tips for reapplying successfully.'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /github/teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /articles/why-was-my-application-for-a-student-developer-pack-denied
|
||||
- /articles/why-wasn-t-my-application-for-a-student-developer-pack-approved
|
||||
- /articles/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/why-wasnt-my-application-for-a-student-developer-pack-approved
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Application not approved
|
||||
---
|
||||
{% tip %}
|
||||
|
||||
**Tip:** {% data reusables.education.about-github-education-link %}
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Unclear academic affiliation documents
|
||||
|
||||
If the dates or schedule mentioned in your uploaded image do not match our eligibility criteria, we require further proof of your academic status.
|
||||
|
||||
If the image you uploaded doesn't clearly identify your current academic status or if the uploaded image is blurry, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
## Using an academic email with an unverified domain
|
||||
|
||||
If your academic email address has an unverified domain, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
## Using an academic email from a school with lax email policies
|
||||
|
||||
If your school issues email addresses prior to paid student enrollment, we require further proof of your academic status. {% data reusables.education.upload-proof-reapply %}
|
||||
|
||||
{% data reusables.education.pdf-support %}
|
||||
|
||||
If you have other questions or concerns about the school domain please ask your school IT staff to contact us.
|
||||
|
||||
## Academic email address already used
|
||||
|
||||
If your academic email address was already used to request a {% data variables.product.prodname_student_pack %} for a different {% data variables.product.prodname_dotcom %} account, you cannot reuse the academic email address to successfully apply for another {% data variables.product.prodname_student_pack %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** It is against the {% data variables.product.prodname_dotcom %} [Terms of Service](/articles/github-terms-of-service/#3-account-requirements) to maintain more than one individual account.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
If you have more than one personal account, you must merge your accounts. To retain the discount, keep the account that was granted the discount. You can rename the retained account and keep your contribution history by adding all your email addresses to the retained account.
|
||||
|
||||
For more information, see:
|
||||
- "[Merging multiple personal accounts](/articles/merging-multiple-user-accounts)"
|
||||
- "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)"
|
||||
- "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/articles/adding-an-email-address-to-your-github-account)"
|
||||
|
||||
## Ineligible student status
|
||||
|
||||
You're ineligible for a {% data variables.product.prodname_student_pack %} if:
|
||||
- You're enrolled in an informal learning program that is not part of the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools) and not enrolled in a degree or diploma granting course of study.
|
||||
- You're pursuing a degree which will be terminated in the current academic session.
|
||||
- You're under 13 years old.
|
||||
|
||||
Your instructor may still apply for a {% data variables.product.prodname_education %} discount for classroom use. If you're a student at a coding school or bootcamp, you will become eligible for a {% data variables.product.prodname_student_pack %} if your school joins the [{% data variables.product.prodname_campus_program %}](https://education.github.com/schools).
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[How to get the GitHub Student Developer Pack without a student ID](https://github.blog/2019-07-30-how-to-get-the-github-student-developer-pack-without-a-student-id/)" on {% data variables.product.prodname_blog %}
|
||||
- "[Apply for a student developer pack](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)"
|
||||
|
|
@ -1,33 +0,0 @@
|
|||
---
|
||||
title: 教育者と研究者のためのGitHub Educationについて
|
||||
intro: '{% data variables.product.prodname_education %}は、教室の内外で教育者や研究者がより効率的に働くことを支援するための様々なツールを提供します。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/about-github-education-for-educators-and-researchers
|
||||
- /github/teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
|
||||
- /articles/about-github-education-for-educators-and-researchers
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-github-education-for-educators-and-researchers
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Educators & researchers
|
||||
---
|
||||
|
||||
{% data reusables.education.about-github-education-link %}
|
||||
|
||||
## 教育者のための{% data variables.product.prodname_education %}
|
||||
|
||||
あらゆるレベルの教育者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます:
|
||||
- [{% data variables.product.prodname_classroom %}](https://classroom.github.com) を使ってコードを配布し、学生にフィードバックを与え、{% data variables.product.prodname_dotcom %} 上の課題を収集する。
|
||||
- 弊社の [{% data variables.product.prodname_education_community %}](https://github.com/orgs/community/discussions/categories/github-education) に加わり、世界中の相手と技術教育における現在のトレンドについて議論する。
|
||||
- 学生の教育のための素材が入った [{% data variables.product.prodname_dotcom %} のスワッグバッグをリクエスト](https://github.com/orgs/community/discussions/13)する。
|
||||
{% data reusables.education.apply-for-team %}
|
||||
|
||||
## 研究者のための {% data variables.product.prodname_education %}
|
||||
|
||||
研究者のための {% data variables.product.prodname_education %} のツールとサービスで、以下のことができます:
|
||||
- {% data variables.product.prodname_dotcom %} 上で世界中の人々と研究作業についてコラボレートする。
|
||||
- 世界中のアカデミックな組織が研究に {% data variables.product.prodname_dotcom %} をどのように使っているかを[学ぶ](https://education.github.com/stories)。
|
||||
{% data reusables.education.apply-for-team %}
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- [学生向け {% data variables.product.prodname_education %}について](/articles/about-github-education-for-students)
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
---
|
||||
title: 教室や研究におけるGitHubの使用
|
||||
intro: '教育者または研究者として、{% data variables.product.prodname_dotcom %} を使用して、教室、学生または研究グループなどで共同作業を行います。'
|
||||
redirect_from:
|
||||
- /education/teach-and-learn-with-github-education/use-github-in-your-classroom-and-research
|
||||
- /github/teaching-and-learning-with-github-education/using-github-in-your-classroom-and-research
|
||||
- /articles/using-github-in-your-classroom-and-research
|
||||
versions:
|
||||
fpt: '*'
|
||||
children:
|
||||
- /about-github-education-for-educators-and-researchers
|
||||
- /apply-for-an-educator-or-researcher-discount
|
||||
- /why-wasnt-my-application-for-an-educator-or-researcher-discount-approved
|
||||
shortTitle: Classroom & research
|
||||
---
|
||||
|
||||
|
|
@ -13,14 +13,15 @@ shortTitle: ガイド
|
|||
|
||||
- [新しい{% data variables.product.prodname_dotcom %}アカウントへのサインアップ](/github/getting-started-with-github/signing-up-for-a-new-github-account)
|
||||
- [Gitと{% data variables.product.prodname_dotcom %}のクイックスタート ](/github/getting-started-with-github/quickstart)
|
||||
- [学生のためのGitHub Educationについて](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)
|
||||
- [教育者割引または研究者割引への応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount)
|
||||
- [学生向け開発者パックへの応募](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack)
|
||||
- [About {% data variables.product.prodname_global_campus %} for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)
|
||||
- [Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)
|
||||
- [Apply to {% data variables.product.prodname_global_campus %} as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)
|
||||
|
||||
## {% data variables.product.company_short %}でソフトウェア開発コースを運営する
|
||||
|
||||
{% data variables.product.prodname_classroom %}で、クラスルームを管理し、学生への課題割り当てやレビューを行い、新世代のソフトウェア開発を教えましょう。
|
||||
|
||||
- [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)
|
||||
- [{% data variables.product.prodname_classroom %}のセットアップの基本 ](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)
|
||||
- [クラスルームの管理](/education/manage-coursework-with-github-classroom/manage-classrooms)
|
||||
- [Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)
|
||||
|
|
@ -35,7 +36,7 @@ shortTitle: ガイド
|
|||
{% data variables.product.prodname_dotcom %}を教育に取り入れ、プロと同じツールを使いましょう。
|
||||
|
||||
- [Gitと{% data variables.product.prodname_dotcom %}の学習リソース](/github/getting-started-with-github/git-and-github-learning-resources)
|
||||
- [学業での{% data variables.product.prodname_dotcom %}の使用](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork)
|
||||
- [{% data variables.product.prodname_global_campus %} for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students)
|
||||
- [{% data variables.product.prodname_desktop %}を使ってみる](/desktop)
|
||||
- [{% data variables.product.prodname_cli %}を使ってみる](/github/getting-started-with-github/github-cli)
|
||||
|
||||
|
|
@ -44,7 +45,6 @@ shortTitle: ガイド
|
|||
コミュニティに参加して、 {% data variables.product.company_short %}からトレーニングを受け、新しいスキルを学んだり教えたりしましょう。
|
||||
|
||||
- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
|
||||
- [About {% data variables.product.prodname_global_campus %} for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students)
|
||||
- [Campus Expertsについて](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
|
||||
- [Campus Advisorsについて](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
|
||||
- [{% data variables.product.prodname_community_exchange %}について](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)
|
||||
- [Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)
|
||||
|
|
|
|||
|
|
@ -6,16 +6,16 @@ introLinks:
|
|||
quickstart: /education/quickstart
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-a-student-developer-pack
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/apply-for-an-educator-or-researcher-discount
|
||||
- education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution
|
||||
guideCards:
|
||||
- /github/getting-started-with-github/signing-up-for-a-new-github-account
|
||||
- /github/getting-started-with-github/git-and-github-learning-resources
|
||||
- /education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom
|
||||
popular:
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students
|
||||
- /education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers
|
||||
- /desktop
|
||||
- /github/getting-started-with-github/github-cli
|
||||
- /education/manage-coursework-with-github-classroom/teach-with-github-classroom
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ The {% data variables.product.prodname_codespaces %} Education benefit gives ver
|
|||
|
||||
{% data reusables.classroom.free-limited-codespaces-for-verified-teachers-beta-note %}
|
||||
|
||||
To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Applying for an educator or teacher benefit](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount#applying-for-an-educator-or-researcher-discount)."
|
||||
To become a verified teacher, you need to be approved for an educator or teacher benefit. For more information, see "[Apply to {% data variables.product.prodname_global_campus %} as a teacher](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/apply-to-github-global-campus-as-a-teacher)."
|
||||
|
||||
After you have confirmation that you are a verified teacher, visit [{% data variables.product.prodname_global_campus %} for Teachers](https://education.github.com/globalcampus/teacher) to upgrade the organization to GitHub Team. For more information, see [GitHub's products](/get-started/learning-about-github/githubs-products#github-team).
|
||||
|
||||
|
|
|
|||
|
|
@ -151,6 +151,6 @@ The assignment overview page displays information about your assignment acceptan
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
|
||||
- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
|
||||
- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
|
||||
- {% data variables.product.prodname_education %} Communityの、[Using Existing Teams in Group Assignments? (グループ課題における既存チームの使用)](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)
|
||||
|
|
|
|||
|
|
@ -130,5 +130,5 @@ The assignment overview page provides an overview of your assignment acceptances
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
|
||||
- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
|
||||
- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
|
||||
|
|
|
|||
|
|
@ -100,5 +100,5 @@ The Git & {% data variables.product.company_short %} starter assignment is only
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- 「[教室や研究で{% data variables.product.prodname_dotcom %}を使う](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research)」
|
||||
- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
|
||||
- 「[学習管理システムを{% data variables.product.prodname_classroom %}に接続する](/education/manage-coursework-with-github-classroom/connect-a-learning-management-system-to-github-classroom)」
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ shortTitle: クイックスタート
|
|||
|
||||
{% tip %}
|
||||
|
||||
**ヒント**: アカデミック割引を利用したい学生の方は、「 [学生向け開発者パックに応募する](/github/teaching-and-learning-with-github-education/applying-for-a-student-developer-pack)」を参照してください。
|
||||
**Tip**: If you're a student and you'd like to take advantage of an academic discount, see "[Apply to {% data variables.product.prodname_global_campus %} as a student](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/apply-to-github-global-campus-as-a-student)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
|
@ -35,9 +35,9 @@ After you create your personal account, create a free organization account. {% d
|
|||
|
||||
詳しい情報については、「[{% data variables.product.prodname_dotcom %}アカウントの種類](/github/getting-started-with-github/types-of-github-accounts)」を参照してください。"
|
||||
|
||||
## 教育者割引に応募する
|
||||
## Applying for teacher benefits
|
||||
|
||||
次に、{% data variables.product.company_short %}からの割引およびサービスにサインアップします。 {% data reusables.education.educator-requirements %}
|
||||
Next, you'll sign up for teacher benefits and resources from {% data variables.product.company_short %} by applying to {% data variables.product.prodname_global_campus %}, a portal that allows you to access your education benefits all in one place. {% data reusables.education.educator-requirements %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
|
@ -53,6 +53,8 @@ After you create your personal account, create a free organization account. {% d
|
|||
{% data reusables.education.plan-to-use-github %}
|
||||
{% data reusables.education.submit-application %}
|
||||
|
||||
Once you are a verified {% data variables.product.prodname_global_campus %} educator, you can access {% data variables.product.prodname_global_campus %} anytime by going to the [{% data variables.product.prodname_education %} website](https://education.github.com).
|
||||
|
||||
## {% data variables.product.prodname_classroom %}をセットアップする
|
||||
|
||||
With your personal account and organization account, you're ready to get started with {% data variables.product.prodname_classroom %}. {% data variables.product.prodname_classroom %}の使用は無料です。 課題の追跡および管理、課題の自動採点、および学生へのフィードバックを行うことができます。
|
||||
|
|
|
|||
|
|
@ -27,7 +27,6 @@ introLinks:
|
|||
featuredLinks:
|
||||
guides:
|
||||
- /github/getting-started-with-github/githubs-products
|
||||
- /github/getting-started-with-github/create-a-repo
|
||||
- /get-started/onboarding/getting-started-with-your-github-account
|
||||
- /get-started/onboarding/getting-started-with-github-team
|
||||
- /get-started/onboarding/getting-started-with-github-enterprise-cloud
|
||||
|
|
@ -39,9 +38,7 @@ featuredLinks:
|
|||
- /github/getting-started-with-github/set-up-git
|
||||
- /get-started/learning-about-github/about-versions-of-github-docs
|
||||
- /github/getting-started-with-github/github-glossary
|
||||
- /github/getting-started-with-github/fork-a-repo
|
||||
- /github/getting-started-with-github/keyboard-shortcuts
|
||||
- /github/getting-started-with-github/saving-repositories-with-stars
|
||||
guideCards:
|
||||
- /github/getting-started-with-github/types-of-github-accounts
|
||||
- /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github
|
||||
|
|
|
|||
|
|
@ -31,6 +31,8 @@ Types of project boards:
|
|||
|
||||
To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}.
|
||||
|
||||
{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
|
||||
|
||||
If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. To access the activity view, click **Menu** and scroll down.
|
||||
|
|
|
|||
|
|
@ -17,11 +17,14 @@ allowTitleToDifferFromFilename: true
|
|||
|
||||
{% data reusables.project-management.project-board-visibility %}
|
||||
|
||||
{% tip %}
|
||||
{% note %}
|
||||
|
||||
**参考::** {% data variables.projects.projects_v1_board %}を{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}にすると、デフォルトではOrganizationのメンバーには読み取りアクセスが付与されます。 Organizationの特定のメンバーに対して、その人が所属するTeamにアクセスを付与するか、その人をコラボレータとして{% data variables.projects.projects_v1_board %}に追加することによって、書き込みあるいは管理権限を付与することができます。 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。
|
||||
**{% ifversion classic-project-visibility-permissions %}Notes{% else %}Note{% endif %}:** {% ifversion classic-project-visibility-permissions %}
|
||||
|
||||
{% endtip %}
|
||||
* {% data reusables.projects.owners-can-limit-visibility-permissions %}
|
||||
* {% endif %}When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. Organizationの特定のメンバーに対して、その人が所属するTeamにアクセスを付与するか、その人をコラボレータとして{% data variables.projects.projects_v1_board %}に追加することによって、書き込みあるいは管理権限を付与することができます。 詳しい情報については[Organizationの{% data variables.product.prodname_project_v1_caps %}の権限](/articles/project-board-permissions-for-an-organization)」を参照してください。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. {% ifversion ghae %}インターナル{% else %}パブリック{% endif %}もしくはプライベートにしたいプロジェクトボードにアクセスしてください。
|
||||
{% data reusables.project-management.click-menu %}
|
||||
|
|
|
|||
|
|
@ -57,6 +57,14 @@ allowTitleToDifferFromFilename: true
|
|||
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% ifversion classic-project-visibility-permissions %}
|
||||
{% note %}
|
||||
|
||||
**ノート:** {% data reusables.projects.owners-can-limit-visibility-permissions %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
|
||||
|
|
|
|||
|
|
@ -305,7 +305,7 @@ gh api graphql -f query='
|
|||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}'
|
||||
```
|
||||
{% endcli %}
|
||||
|
||||
|
|
|
|||
|
|
@ -39,6 +39,8 @@ Organizationのオーナーと{% data variables.projects.projects_v1_board %}の
|
|||
|
||||
## {% data variables.projects.projects_v1_board_caps %}の可視性
|
||||
|
||||
{% ifversion classic-project-visibility-permissions %}{% data reusables.projects.owners-can-limit-visibility-permissions %}{% endif %}
|
||||
|
||||
{% data reusables.project-management.project-board-visibility %}{% data variables.projects.projects_v1_board %}の可視性をプライベートから{% ifversion ghae %}インターナル{% else %}パブリック{% endif %}に変更したり、元に戻したりすることができます。 詳しい情報については「[{% data variables.product.prodname_project_v1 %}の可視性の変更](/articles/changing-project-board-visibility)」を参照してください。
|
||||
|
||||
## 参考リンク
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
---
|
||||
title: Organizationでのプロジェクトの可視性の変更の許可
|
||||
intro: Organizationのオーナーは、管理権限を持つメンバーに、Organization内のプロジェクトの可視性の調整を許可できます。
|
||||
intro: 'Organization owners can allow members with admin permissions to adjust the visibility of {% data variables.projects.projects_v2_and_v1 %} in their organization.'
|
||||
versions:
|
||||
feature: projects-v2
|
||||
feature: classic-project-visibility-permissions-or-projects-v2
|
||||
topics:
|
||||
- Organizations
|
||||
- Projects
|
||||
shortTitle: プロジェクトの可視性の権限
|
||||
allowTitleToDifferFromFilename: true
|
||||
permissions: Organization owners can allow project visibility changes for an organization.
|
||||
permissions: 'Organization owners can allow {% data variables.projects.project_v2_and_v1 %} visibility changes for an organization.'
|
||||
---
|
||||
|
||||
メンバーがプロジェクトをプライベートからパブリックに変更するのを制限するように、Organizationでのプロジェクトの可視性を変更できる人を制限できます。
|
||||
You can restrict who has the ability to change the visibility of {% data variables.projects.projects_v2_and_v1 %} in your organization, such as restricting members from changing {% data variables.projects.projects_v2_and_v1 %} from private to public.
|
||||
|
||||
プロジェクトの可視性を変更できるのをOrganizationのオーナーだけに制限したり、プロジェクトの管理権限を持つ人なら誰でも可視性を変更できるようにしたりできます。
|
||||
You can limit the ability to change {% data variables.projects.project_v2_and_v1 %} visibility to just organization owners, or you can allow anyone granted admin permissions to change the visibility.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
|
|
@ -23,4 +23,8 @@ permissions: Organization owners can allow project visibility changes for an org
|
|||
|
||||
## 参考リンク
|
||||
|
||||
- 「[プロジェクトの可視性の管理](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)」
|
||||
{% ifversion projects-v2 %}
|
||||
- "[Managing visibility of your {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects)"
|
||||
{%- endif %}{%- ifversion projects-v1 %}
|
||||
- 「[{% data variables.product.prodname_project_v1 %}の可視性の変更](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)」
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -232,6 +232,8 @@ Your NuGet package may fail to push if the `RepositoryUrl` in *.csproj* is not s
|
|||
|
||||
If you're using a nuspec file, ensure that it has a `repository` element with the required `type` and `url` attributes.
|
||||
|
||||
If you're using a `GITHUB_TOKEN` to authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, the token cannot access private repository-based packages in a different repository other than where the workflow is running in. To access packages associated with other repositories, instead generate a PAT with the `read:packages` scope and pass this token in as a secret.
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
|
|
|
|||
|
|
@ -16,22 +16,36 @@ topics:
|
|||
- Pull requests
|
||||
---
|
||||
|
||||
## Merge your commits
|
||||
|
||||
{% data reusables.pull_requests.default_merge_option %}
|
||||
|
||||
## プルリクエストのコミットのsquashとマージ
|
||||
## Squash and merge your commits
|
||||
|
||||
{% data reusables.pull_requests.squash_and_merge_summary %}
|
||||
|
||||
### squash マージのマージメッセージ
|
||||
|
||||
{% ifversion default-merge-squash-commit-message %}
|
||||
When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. Depending on how the repository is configured and the number of commits in the pull request, not including merge commits, this message may include the pull request title, pull request description, or information about the commits.
|
||||
{% else %}
|
||||
When you squash and merge, {% data variables.product.prodname_dotcom %} generates a default commit message, which you can edit. The default message depends on the number of commits in the pull request, not including merge commits.
|
||||
|
||||
| コミット数 | 概要 | 説明 |
|
||||
| ------- | --------------------------------------- | ------------------------------------ |
|
||||
| 単一のコミット | 単一のコミットのコミットメッセージのタイトルと、その後に続くプルリクエスト番号 | 単一のコミットのコミットメッセージの本文テキスト |
|
||||
| 複数のコミット | プルリクエストのタイトルと、その後に続くプルリクエスト番号 | squash されたすべてのコミットのコミットメッセージの日付順のリスト |
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}
|
||||
| コミット数 | 概要 | 説明 |
|
||||
| ------- | --------------------------------------- | ------------------------------------ |
|
||||
| 単一のコミット | 単一のコミットのコミットメッセージのタイトルと、その後に続くプルリクエスト番号 | 単一のコミットのコミットメッセージの本文テキスト |
|
||||
| 複数のコミット | プルリクエストのタイトルと、その後に続くプルリクエスト番号 | squash されたすべてのコミットのコミットメッセージの日付順のリスト |
|
||||
|
||||
{% ifversion default-merge-squash-commit-message %}
|
||||
People with maintainer or admin access to a repository can configure their repository's default merge message for all squashed commits to use the pull request title, the pull request title and commit details, or the pull request title and description. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".{% endif %}
|
||||
|
||||
{% ifversion ghes = 3.6 %}
|
||||
People with admin access to a repository can configure the repository to use the title of the pull request as the default merge message for all squashed commits. For more information, see "[Configure commit squashing](/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests)".
|
||||
{% endif %}
|
||||
|
||||
|
|
@ -43,7 +57,7 @@ People with admin access to a repository can configure the repository to use the
|
|||
|
||||
このコミットはベースブランチのみで行われ、head ブランチでは行われないため、2 つのブランチの共通の先祖は変更されません。 head ブランチでの作業を続行し、2 つのブランチ間に新しいプルリクエストを作成すると、プルリクエストには、共通の先祖以降のすべてのコミットが含まれます。これには、前のプルリクエストで squash してマージしたコミットも含まれます。 コンフリクトがない場合は、これらのコミットを安全にマージできます。 ただし、このワークフローでは高確率でマージコンフリクトが発生します。 長時間にわたる head ブランチのプルリクエストを squash してマージし続ける場合は、同じコンフリクトを繰り返し解決する必要があります。
|
||||
|
||||
## プルリクエストコミットのリベースとマージ
|
||||
## Rebase and merge your commits
|
||||
|
||||
{% data reusables.pull_requests.rebase_and_merge_summary %}
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ shortTitle: Comment on a PR
|
|||
|
||||
プルリクエストの [**Files changed**] タブにあるファイルの、特定のセクションに、行コメントまたは [Pull Request レビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)の一部としてコメントすることも可能です。 行コメントを追加することは、インプリメンテーションについての問題を話し合ったり、作者にフィードバックを行ったりする上でよい方法です。
|
||||
|
||||
Pull Request レビューへの行コメント追加に関する 詳しい情報については、「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。
|
||||
For more information on adding line comments to a pull request review, see "[Reviewing proposed changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)."
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,30 @@
|
|||
---
|
||||
title: Configuring commit merging for pull requests
|
||||
intro: 'You can enforce, allow, or disable merging with a merge commit for all pull request merges on {% data variables.product.product_location %} in your repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Configure commit merging
|
||||
---
|
||||
|
||||
{% data reusables.pull_requests.configure_pull_request_merges_intro %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow merge commits**. This allows contributors to merge a pull request with a full history of commits.{% ifversion default-merge-squash-commit-message %} {% endif %}{% ifversion ghes = 3.6 %} {% endif %}
|
||||
{% ifversion ghes < 3.6 %}
|
||||
{% endif %}
|
||||
{% ifversion default-merge-squash-commit-message %}
|
||||
1. Optionally, under **Allow merge commits**, use the dropdown to choose the format of the commit message presented to contributors when merging. The default message includes the pull request number and title. For example, `Merge pull request #123 from patch-1`. You can also choose to use just the pull request title, or the pull request title and description. 
|
||||
{% endif %}
|
||||
|
||||
If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- [プルリクエストのマージについて](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)
|
||||
- [プルリクエストのマージ](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)
|
||||
|
|
@ -19,4 +19,10 @@ shortTitle: Configure commit rebasing
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. これにより、コントリビューターが個々のコミットをベースブランチにリベースすることでプルリクエストをマージできるようになります。 ここで他のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} 
|
||||
3. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. これにより、コントリビューターが個々のコミットをベースブランチにリベースすることでプルリクエストをマージできるようになります。
|
||||
{% ifversion default-merge-squash-commit-message %}
|
||||
{% endif %}{% ifversion ghes = 3.6 %} {% endif %}
|
||||
{% ifversion ghes < 3.6 %}
|
||||
{% endif %}
|
||||
|
||||
ここで他のマージ方法も選択した場合、コラボレーターはプルリクエストをマージする時にコミットのマージ方法を選択できます。 {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
|
||||
|
|
|
|||
|
|
@ -21,11 +21,14 @@ shortTitle: Configure commit squashing
|
|||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, optionally select **Allow merge commits**. これにより、コントリビューターがコミットの全ての履歴と共にプルリクエストをマージできるようになります。 
|
||||
4. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. これにより、コントリビューターが全てのコミットを 1 つのコミットに squash してプルリクエストをマージできるようになります。 The squash message automatically defaults to the title of the pull request if it contains more than one commit. {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-7042 %}If you want to use the title of the pull request as the default merge message for all squashed commits, regardless of the number of commits in the pull request, select **Default to PR title for squash merge commits**. {% else %}
|
||||
{% endif %}
|
||||
1. Under {% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow squash merging**. これにより、コントリビューターが全てのコミットを 1 つのコミットに squash してプルリクエストをマージできるようになります。 The default commit message presented to contributors when merging is the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. {% ifversion ghes = 3.6 %} To always use the title of the pull request regardless of the number of commits in the pull request select **Default to PR title for squash merge commits**.{% endif %}{% ifversion default-merge-squash-commit-message %} {% endif %}{% ifversion ghes = 3.6 %} {% endif %}
|
||||
{% ifversion ghes < 3.6 %}
|
||||
{% endif %}
|
||||
{% ifversion default-merge-squash-commit-message %}
|
||||
1. Optionally, under **Allow squash merging**, use the dropdown to choose the format of the default squash commit message presented to contributors when merging. The default message uses the commit title and message if the pull request contains only 1 commit, or the pull request title and list of commits if the pull request contains 2 or more commits. You can also choose to use just the pull request title, the pull request title and commit details, or the pull request title and description. 
|
||||
{% endif %}
|
||||
|
||||
If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %}
|
||||
If you select more than one merge method, collaborators can choose which type of merge commit to use when they merge a pull request. {% data reusables.repositories.squash-and-rebase-linear-commit-history %}
|
||||
|
||||
## 参考リンク
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ topics:
|
|||
- Repositories
|
||||
children:
|
||||
- /about-merge-methods-on-github
|
||||
- /configuring-commit-merging-for-pull-requests
|
||||
- /configuring-commit-squashing-for-pull-requests
|
||||
- /configuring-commit-rebasing-for-pull-requests
|
||||
- /managing-a-merge-queue
|
||||
|
|
|
|||
|
|
@ -16,6 +16,8 @@ permissions: People with maintainer permissions can enable or disable the settin
|
|||
|
||||
If you enable the setting to always suggest updating pull request branches in your repository, people with write permissions will always have the ability, on the pull request page, to update a pull request's head branch when it's not up to date with the base branch. When not enabled, the ability to update is only available when the base branch requires branches to be up to date before merging and the branch is not up to date. For more information, see "[Keeping your pull request in sync with the base branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch)."
|
||||
|
||||
{% data reusables.enterprise.3-5-missing-feature %}
|
||||
|
||||
## Managing suggestions to update a pull request branch
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
|
|
|
|||
|
|
@ -9,6 +9,7 @@ redirect_from:
|
|||
- /github/managing-files-in-a-repository/adding-a-file-to-a-repository-using-the-command-line
|
||||
- /github/managing-files-in-a-repository/managing-files-on-github/adding-a-file-to-a-repository
|
||||
- /github/managing-files-in-a-repository/managing-files-using-the-command-line/adding-a-file-to-a-repository-using-the-command-line
|
||||
- /github/managing-large-files/about-large-files-on-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
|
@ -21,7 +22,7 @@ shortTitle: Add a file
|
|||
|
||||
## Adding a file to a repository on {% data variables.product.product_name %}
|
||||
|
||||
ブラウザを介してリポジトリに追加できるファイルのサイズは、1 ファイルあたり {% data variables.large_files.max_github_browser_size %}までです。 コマンドラインからは、より大きいサイズのファイルを追加でき、1 ファイルあたり {% data variables.large_files.max_github_size %}までです。 詳しい情報については[コマンドラインを使用してリポジトリにファイルを追加する](#adding-a-file-to-a-repository-using-the-command-line)を参照してください。
|
||||
ブラウザを介してリポジトリに追加できるファイルのサイズは、1 ファイルあたり {% data variables.large_files.max_github_browser_size %}までです。 コマンドラインからは、より大きいサイズのファイルを追加でき、1 ファイルあたり {% data variables.large_files.max_github_size %}までです。 詳しい情報については[コマンドラインを使用してリポジトリにファイルを追加する](#adding-a-file-to-a-repository-using-the-command-line)を参照してください。 To add files larger than {% data variables.large_files.max_github_size %}, you must use {% data variables.large_files.product_name_long %}. For more information, see "[About large files on {% data variables.product.product_name %}](/repositories/working-with-files/managing-large-files/about-large-files-on-github)."
|
||||
|
||||
{% tip %}
|
||||
|
||||
|
|
|
|||
|
|
@ -0,0 +1,7 @@
|
|||
#Issue 7720
|
||||
#Organization owners can restrict public classic projects /OR/ Projects V2
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7720'
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
#Issue 7720
|
||||
#Organization owners can restrict public classic projects.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7720'
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
#Reference: issue #7597
|
||||
#Admin can control default PR merge/ squash commit messages
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7597'
|
||||
|
|
@ -61,6 +61,8 @@ secret_scanning:
|
|||
- '{% ifversion not fpt %}/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning{% endif %}'
|
||||
- '{% ifversion not fpt %}/code-security/secret-scanning/managing-alerts-from-secret-scanning{% endif %}'
|
||||
- '{% ifversion not fpt %}/code-security/secret-scanning/secret-scanning-patterns{% endif %}'
|
||||
- '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/protecting-pushes-with-secret-scanning{% endif %}'
|
||||
- '{% ifversion secret-scanning-push-protection %}/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection{% endif %}'
|
||||
#Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
|
||||
security_alerts:
|
||||
title: 'セキュリティアラートの調査と管理'
|
||||
|
|
|
|||
|
|
@ -273,6 +273,7 @@ sections:
|
|||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
||||
deprecations:
|
||||
- heading: Deprecation of GitHub Enterprise Server 2.21
|
||||
|
|
|
|||
|
|
@ -26,3 +26,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -14,3 +14,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -42,3 +42,4 @@ sections:
|
|||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -22,3 +22,4 @@ sections:
|
|||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -26,3 +26,4 @@ sections:
|
|||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -21,3 +21,4 @@ sections:
|
|||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -17,3 +17,4 @@ sections:
|
|||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -15,3 +15,12 @@ sections:
|
|||
- '`ghe-set-password`コマンドラインユーティリティは、インスタンスがリカバリモードで起動されているときに自動的に必要なサービスを起動します。'
|
||||
- バックグラウンドプロセスの`aqueduct`のメトリクスは、転送してManagement Consoleで表示するためにCollectdに収集されます。
|
||||
- データベースの移行及び設定の実行ログ`/data/user/common/ghe-config.log`の場所は、進行中の移行の詳細を示すページに表示されるようになりました。
|
||||
known_issues:
|
||||
- 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。
|
||||
- アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
|
||||
- Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
|
||||
- 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
|
||||
- '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。'
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -0,0 +1,9 @@
|
|||
date: '2022-08-11'
|
||||
sections:
|
||||
security_fixes:
|
||||
- |
|
||||
**重要**: GitHub Enterprise ServerのElasticsearchコンテナは、悪意あるXSLTスタイルシートを処理する際に整数切り捨ての問題に対して脆弱なバージョンのOpenJDK 8を使用していました。この脆弱性は[CVE-2022-34169](https://github.com/advisories/GHSA-9339-86wc-4qgf)として追跡されています。
|
||||
- |
|
||||
**高**: ユーザアカウントに以前にインストールされたアプリケーションは、ユーザアカウントがOrganizationアカウントに変換されたあとに、スコープ付きのアクセストークンでOrganizationにアクセスする権限を自動的に付与されました。この脆弱性は[GitHub Bug Bountyプログラム](https://bounty.github.com)から報告されました。
|
||||
bugs:
|
||||
- カスタムの休眠の閾値がインスタンスに設定された場合、すべての休眠ユーザをサスペンドしても、その閾値を確実に踏まえません。休眠に関する詳しい情報については「[休眠ユーザの管理](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)」を参照してください。
|
||||
|
|
@ -21,3 +21,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -28,3 +28,4 @@ sections:
|
|||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
@ -28,3 +28,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -26,3 +26,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -12,3 +12,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -21,3 +21,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -24,3 +24,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -18,3 +18,4 @@ sections:
|
|||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -253,7 +253,7 @@ sections:
|
|||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
|
||||
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
deprecations:
|
||||
- heading: Deprecation of GitHub Enterprise Server 2.22
|
||||
notes:
|
||||
|
|
|
|||
|
|
@ -15,3 +15,4 @@ sections:
|
|||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data variables.product.prodname_actions %}のストレージ設定は、"Force Path Style（パススタイルの強制）"が選択されている場合、検証できず{% data variables.enterprise.management_console %}に保存できません。その代わりに、`ghe-actions-precheck`コマンドラインユーティリティで設定しなければなりません。'
|
||||
- '現在のLinuxカーネルにあるバグのために、Azureにインストールされ、32以上のCPUコアをプロビジョニングされた{% data variables.product.prodname_ghe_server %} 3.3インスタンスが起動に失敗します。[更新:2022年04月08日]'
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
|
|
@ -19,3 +19,4 @@ sections:
|
|||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- '{% data variables.product.prodname_actions %}のストレージ設定は、"Force Path Style（パススタイルの強制）"が選択されている場合、検証できず{% data variables.enterprise.management_console %}に保存できません。その代わりに、`ghe-actions-precheck`コマンドラインユーティリティで設定しなければなりません。'
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче