Octomerger Bot
2
.github/workflows/crowdin-cleanup.yml
vendored
2
.github/workflows/crowdin-cleanup.yml
vendored
@@ -41,7 +41,7 @@ jobs:
|
||||
run: script/i18n/homogenize-frontmatter.js
|
||||
|
||||
- name: Check in homogenized files
|
||||
uses: EndBug/add-and-commit@756d9ea820f11931e591eaf57f25e0f5b903d5b2
|
||||
uses: EndBug/add-and-commit@050a66787244b10a4874a2a5f682130263edc192
|
||||
with:
|
||||
# The arguments for the `git add` command
|
||||
add: 'translations'
|
||||
|
||||
2
.github/workflows/openapi-decorate.yml
vendored
2
.github/workflows/openapi-decorate.yml
vendored
@@ -54,7 +54,7 @@ jobs:
|
||||
run: script/rest/update-files.js --decorate-only
|
||||
|
||||
- name: Check in the decorated files
|
||||
uses: EndBug/add-and-commit@756d9ea820f11931e591eaf57f25e0f5b903d5b2
|
||||
uses: EndBug/add-and-commit@050a66787244b10a4874a2a5f682130263edc192
|
||||
with:
|
||||
# The arguments for the `git add` command
|
||||
add: '["lib/rest/static/apps", "lib/rest/static/decorated"]'
|
||||
|
||||
@@ -73,7 +73,7 @@ The following table indicates where each context and special function can be use
|
||||
| <code>concurrency</code> | <code>github, inputs</code> | |
|
||||
| <code>env</code> | <code>github, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
|
||||
| <code>jobs.<job_id>.container</code> | <code>github, needs, strategy, matrix, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.container</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.container.credentials</code> | <code>github, needs, strategy, matrix, env, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.container.env.<env_id></code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.continue-on-error</code> | <code>github, needs, strategy, matrix, inputs</code> | |
|
||||
@@ -199,7 +199,7 @@ jobs:
|
||||
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
|
||||
| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
|
||||
{%- endif %}
|
||||
| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
|
||||
| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. | | `github.sha` | `string` | The commit SHA that triggered the workflow run. | | `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. これは機能的に`GITHUB_TOKEN`シークレットに等価です。 詳しい情報については「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。 | | `github.workflow` | `string` | The name of the workflow. ワークフローファイルで `name` を指定していない場合、このプロパティの値は、リポジトリ内にあるワークフローファイルのフルパスになります。 | | `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
|
||||
|
||||
### Example contents of the `github` context
|
||||
|
||||
@@ -513,15 +513,15 @@ jobs:
|
||||
|
||||
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. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
|
||||
`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)」を参照してください。
|
||||
|
||||
{% data reusables.actions.secrets-redaction-warning %}
|
||||
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `secrets` | `オブジェクト` | This context is the same for each job in a workflow run. このコンテキストには、ジョブのあらゆるステップからアクセスできます。 This object contains all the properties listed below. |
|
||||
| `secrets.GITHUB_TOKEN` | `string` | Automatically created token for each workflow run. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." |
|
||||
| `secrets.<secret_name>` | `string` | The value of a specific secret. |
|
||||
| プロパティ名 | 種類 | 説明 |
|
||||
| ----------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `secrets` | `オブジェクト` | This context is the same for each job in a workflow run. このコンテキストには、ジョブのあらゆるステップからアクセスできます。 This object contains all the properties listed below. |
|
||||
| `secrets.GITHUB_TOKEN` | `string` | Automatically created token for each workflow run. 詳しい情報については「[自動トークン認証](/actions/security-guides/automatic-token-authentication)」を参照してください。 |
|
||||
| `secrets.<secret_name>` | `string` | The value of a specific secret. |
|
||||
|
||||
### Example contents of the `secrets` context
|
||||
|
||||
|
||||
@@ -73,7 +73,11 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
||||
|
||||
{% cli %}
|
||||
|
||||
You cannot re-run all failed jobs through the {% data variables.product.prodname_cli %} at this time. Instead, use the {% data variables.product.product_name %} web browser interface.
|
||||
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. `run-id` を指定しない場合、{% data variables.product.prodname_cli %} は、最近失敗した実行を選択するためのインタラクティブメニューを返します。
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
@@ -95,7 +99,11 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
|
||||
{% cli %}
|
||||
|
||||
You cannot re-run a single job through the {% data variables.product.prodname_cli %} at this time. Instead, use the {% data variables.product.product_name %} browser interface.
|
||||
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em>
|
||||
```
|
||||
|
||||
{% endcli %}
|
||||
|
||||
|
||||
@@ -23,7 +23,7 @@ At the start of each workflow run, {% data variables.product.prodname_dotcom %}
|
||||
|
||||
When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_github_app %} installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."
|
||||
|
||||
Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. The token expires when the job is finished.
|
||||
Before each job begins, {% data variables.product.prodname_dotcom %} fetches an installation access token for the job. {% data reusables.actions.github-token-expiration %}
|
||||
|
||||
The token is also available in the `github.token` context. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
|
||||
|
||||
|
||||
@@ -234,3 +234,11 @@ restore-keys: |
|
||||
## 利用制限と退去のポリシー
|
||||
|
||||
{% data variables.product.prodname_dotcom %}は、7日間以上アクセスされていないキャッシュエントリを削除します。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
|
||||
|
||||
{% if actions-cache-management %}
|
||||
|
||||
## Managing caches
|
||||
|
||||
You can use the {% data variables.product.product_name %} REST API to manage your caches. At present, you can use the API to see your cache usage, with more functionality expected in future updates. For more information, see the "[Actions](/rest/reference/actions#cache)" REST API documentation.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -64,7 +64,7 @@ Use `on.workflow_call` to define the inputs and outputs for a reusable workflow.
|
||||
|
||||
When using the `workflow_call` keyword, you can optionally specify inputs that are passed to the called workflow from the caller workflow. For more information about the `workflow_call` keyword, see "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events)."
|
||||
|
||||
In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. For more information, see [`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype).
|
||||
In addition to the standard input parameters that are available, `on.workflow_call.inputs` requires a `type` parameter. 詳しい情報については[`on.workflow_call.inputs.<input_id>.type`](#onworkflow_callinputsinput_idtype)を参照してください。
|
||||
|
||||
If a `default` parameter is not set, the default value of the input is `false` for a boolean, `0` for a number, and `""` for a string.
|
||||
|
||||
@@ -714,6 +714,12 @@ steps:
|
||||
|
||||
If the timeout exceeds the job execution time limit for the runner, the job will be canceled when the execution time limit is met instead. For more information about job execution time limits, see {% ifversion fpt or ghec or ghes %}"[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration#usage-limits)" for {% data variables.product.prodname_dotcom %}-hosted runners and {% endif %}"[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits){% ifversion fpt or ghec or ghes %}" for self-hosted runner usage limits.{% elsif ghae %}."{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.actions.github-token-expiration %} For self-hosted runners, the token may be the limiting factor if the job timeout is greater than 24 hours. For more information on the `GITHUB_TOKEN`, see "[About the `GITHUB_TOKEN` secret](/actions/security-guides/automatic-token-authentication#about-the-github_token-secret)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## `jobs.<job_id>.strategy`
|
||||
|
||||
{% data reusables.actions.jobs.section-using-a-build-matrix-for-your-jobs-strategy %}
|
||||
|
||||
@@ -23,6 +23,8 @@ shortTitle: About configuration
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
To get started with {% data variables.product.product_name %}, you first need to deploy {% data variables.product.product_name %}. For more information, see "[Deploying {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae)."
|
||||
|
||||
The first time you access your enterprise, you will complete an initial configuration to get {% data variables.product.product_name %} ready to use. 初期設定には、Enterprise とアイデンティティプロバイダ (IdP) の接続、SAML SSO による認証、Enterprise 内のリポジトリと Organization のポリシーの設定、および送信メール用の SMTP の設定が含まれます。 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
|
||||
|
||||
後で、サイトアドミンのダッシュボードと Enterprise 設定を使用して、さらに Enterprise の設定を行い、ユーザ、Organization、およびリポジトリを管理し、リスクを軽減して品質を向上させるポリシーを設定できます。
|
||||
|
||||
@@ -0,0 +1,66 @@
|
||||
---
|
||||
title: Deploying GitHub AE
|
||||
intro: 'You can deploy {% data variables.product.product_name %} to an available Azure region.'
|
||||
versions:
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
- Enterprise
|
||||
type: how_to
|
||||
shortTitle: Deploy GitHub AE
|
||||
redirect_from:
|
||||
- /get-started/signing-up-for-github/setting-up-a-trial-of-github-ae
|
||||
---
|
||||
|
||||
## About deployment of {% data variables.product.product_name %}
|
||||
|
||||
{% data reusables.github-ae.github-ae-enables-you %} 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} について](/admin/overview/about-github-ae)」を参照してください。
|
||||
|
||||
After you purchase or start a trial of {% data variables.product.product_name %}, you can deploy {% data variables.product.product_name %} to an available Azure region. This guide refers to the Azure resource that contains the deployment of {% data variables.product.product_name %} as the {% data variables.product.product_name %} account. You'll use the Azure portal at [https://portal.azure.com](https://portal.azure.com) to deploy the {% data variables.product.product_name %} account.
|
||||
|
||||
## 必要な環境
|
||||
|
||||
- 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.
|
||||
|
||||
## Deploying {% data variables.product.product_name %} with the {% data variables.actions.azure_portal %}
|
||||
|
||||
The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.product_name %} account in your Azure resource group.
|
||||
|
||||
1. Click one of the following two links to begin deployment of {% data variables.product.product_name %}. The link you should click depends on the Azure cloud where you plan to deploy {% data variables.product.product_name %}. For more information about Azure Government, see [What is Azure Government?](https://docs.microsoft.com/en-us/azure/azure-government/documentation-government-welcome) in the Microsoft documentation.
|
||||
|
||||
- [Deploy {% data variables.product.product_name %} to Azure Commercial](https://aka.ms/create-github-ae-instance)
|
||||
- [Deploy {% data variables.product.product_name %} to Azure Government](https://aka.ms/create-github-ae-instance-gov)
|
||||
1. To begin the process of adding a new {% data variables.product.product_name %} account, click **Create GitHub AE account**.
|
||||
1. Complete the "Project details" and "Instance details" fields. 
|
||||
- **Account name:** The hostname for your enterprise
|
||||
- **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.product_name %}
|
||||
- **Administrator email:** The email address that will receive the login information
|
||||
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)」を参照してください。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Software updates for your {% data variables.product.product_name %} deployment are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Navigating to your enterprise
|
||||
|
||||
You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.product_name %} deployment. The resulting list includes all the {% data variables.product.product_name %} deployments in your Azure region.
|
||||
|
||||
1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
|
||||
1. From the available filters, click **All types**, then deselect **Select all** and select **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 %} に連絡して延長をリクエストしてください。
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.product_name %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
|
||||
- "[{% data variables.product.product_name %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)"
|
||||
@@ -16,6 +16,7 @@ topics:
|
||||
- Enterprise
|
||||
children:
|
||||
- /about-enterprise-configuration
|
||||
- /deploying-github-ae
|
||||
- /initializing-github-ae
|
||||
- /accessing-the-management-console
|
||||
- /accessing-the-administrative-shell-ssh
|
||||
|
||||
@@ -54,7 +54,7 @@ If your IdP supports encrypted assertions, you can configure encrypted assertion
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈**: ユーザの `NameID` が IdP で変更された場合、ユーザが {% data variables.product.prodname_ghe_server %} インスタンスにサインインしようとすると、エラーメッセージが表示されます。 {% ifversion ghes %}To restore the user's access, you'll need to update the user account's `NameID` mapping. 詳しい情報については、「[ユーザの SAML `NameID` を更新する](#updating-a-users-saml-nameid)」を参照してください。{% else %} 詳しい情報については、「[エラー: '別のユーザーがすでにアカウントを所有しています'](#error-another-user-already-owns-the-account)」を参照してください。{% endif %}
|
||||
**Note**: If the `NameID` for a user does change on the IdP, the user will see an error message when they try to sign into {% data variables.product.product_location %}. To restore the user's access, you'll need to update the user account's `NameID` mapping. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -96,6 +96,14 @@ To specify more than one value for an attribute, use multiple `<saml2:AttributeV
|
||||
|
||||
## SAMLの設定
|
||||
|
||||
You can enable or disable SAML authentication for {% data variables.product.product_location %}, or you can edit an existing configuration. You can view and edit authentication settings for {% data variables.product.product_name %} in the {% data variables.enterprise.management_console %}. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: {% data reusables.enterprise.test-in-staging %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.authentication %}
|
||||
@@ -118,19 +126,11 @@ To specify more than one value for an attribute, use multiple `<saml2:AttributeV
|
||||
1. {% data variables.product.product_location %} 上のユーザの管理者権限を SAML プロバイダに決めさせたく**ない**場合、[**Disable administrator demotion/promotion**] を選択します。
|
||||
|
||||
|
||||
1. Optionally, to allow {% data variables.product.product_location %} to send and receive encrypted assertions to and from your SAML IdP, select **Require encrypted assertions**. For more information, see "[Enabling encrypted assertions](#enabling-encrypted-assertions)."
|
||||
{%- ifversion ghes > 3.3 %}
|
||||
1. Optionally, to allow {% data variables.product.product_location %} to receive encrypted assertions from your SAML IdP, select **Require encrypted assertions**. You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.product.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](#enabling-encrypted-assertions)."
|
||||
|
||||
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: Incorrectly configuring encrypted assertions can cause all authentication to {% data variables.product.product_location %} to fail.
|
||||
|
||||
- You must ensure that your IdP supports encrypted assertions and that the encryption and key transport methods in the management console match the values configured on your IdP. You must also provide {% data variables.product.product_location %}'s public certificate to your IdP. For more information, see "[Enabling encrypted assertions](#enabling-encrypted-assertions)."
|
||||
|
||||
- Before enabling encrypted assertions, {% data variables.product.company_short %} recommends testing encrypted assertions in a staging environment, and confirming that SAML authentication functions as you expect. 詳しい情報については "[ステージングインスタンスのセットアップ](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)"を参照してください。
|
||||
|
||||
{% endwarning %}
|
||||
{%- endif %}
|
||||
1. In the **Single sign-on URL** field, type the HTTP or HTTPS endpoint on your IdP for single sign-on requests. この値はIdpの設定によって決まります。 If the host is only available from your internal network, you may need to [configure {% data variables.product.product_location %} to use internal nameservers](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-dns-nameservers/).
|
||||
|
||||
|
||||
@@ -153,37 +153,38 @@ To specify more than one value for an attribute, use multiple `<saml2:AttributeV
|
||||
|
||||
To enable encrypted assertions, your SAML IdP must also support encrypted assertions. You must provide {% data variables.product.product_location %}'s public certificate to your IdP, and configure encryption settings that match your IdP.
|
||||
|
||||
{% warning %}
|
||||
{% note %}
|
||||
|
||||
**Warning**: Incorrectly configuring encrypted assertions can cause all authentication to {% data variables.product.product_location %} to fail. {% data variables.product.company_short %} strongly recommends testing your SAML configuration in a staging environment. For more information about staging instances, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
|
||||
**Note**: {% data reusables.enterprise.test-in-staging %}
|
||||
|
||||
{% endwarning %}
|
||||
{% endnote %}
|
||||
|
||||
1. Configure SAML for {% data variables.product.product_location %}. For more information, see "[Configuring SAML settings](#configuring-saml-settings)."
|
||||
{% data reusables.enterprise_installation.ssh-into-instance %}
|
||||
1. Run the following command to output {% data variables.product.product_location %}'s public certificate.
|
||||
|
||||
openssl pkcs12 -in /data/user/common/saml-sp.p12 -nokeys -passin pass:
|
||||
1. In the output, copy the text beginning with `-----BEGIN CERTIFICATE-----` and ending with `-----END CERTIFICATE-----`, and paste the output into a plaintext file.
|
||||
1. Sign into your SAML IdP as an administrator.
|
||||
1. In the application for {% data variables.product.product_location %}, enable encrypted assertions.
|
||||
- Note the encryption method and key transport method.
|
||||
- Provide the public certificate from step 3.
|
||||
1. Optionally, enable SAML debugging. SAML debugging records verbose entries in {% data variables.product.product_name %}'s authentication log, and may help you troubleshoot failed authentication attempts. For more information, see "[Configuring SAML debugging](#configuring-saml-debugging)."
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.authentication %}
|
||||
1. Select **Require encrypted assertions**.
|
||||
|
||||
|
||||
1. To the right of "Encryption Method", select the encryption method for your IdP from step 5.
|
||||
1. To the right of "Encryption Certificate", click **Download** to save a copy of {% data variables.product.product_location %}'s public certificate on your local machine.
|
||||
|
||||
|
||||
1. Sign into your SAML IdP as an administrator.
|
||||
1. In the application for {% data variables.product.product_location %}, enable encrypted assertions.
|
||||
- Note the encryption method and key transport method.
|
||||
- Provide the public certificate you downloaded in step 7.
|
||||
1. Return to the management console on {% data variables.product.product_location %}.
|
||||
1. To the right of "Encryption Method", select the encryption method for your IdP from step 9.
|
||||
|
||||
|
||||
1. To the right of "Key Transport Method", select the key transport method for your IdP from step 5.
|
||||
1. To the right of "Key Transport Method", select the key transport method for your IdP from step 9.
|
||||
|
||||
|
||||
1. **Save settings（設定の保存）**をクリックしてください。
|
||||
{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
|
||||
|
||||
If you enabled SAML debugging to test authentication with encrypted assertions, disable SAML debugging when you're done testing. For more information, see "[Configuring SAML debugging](#configuring-saml-debugging)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Updating a user's SAML `NameID`
|
||||
@@ -240,11 +241,11 @@ To enable encrypted assertions, your SAML IdP must also support encrypted assert
|
||||
|
||||
> 別のユーザが既にアカウントを所有しています。 管理者に認証ログを確認するようご依頼ください。
|
||||
|
||||
このメッセージは通常、その人のユーザ名またはメールアドレスが IdP で変更されたということを示します。 {% ifversion ghes %}Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. 詳しい情報については、「[ユーザの SAML `NameID` の更新](#updating-a-users-saml-nameid)」を参照してください。{% else %} `NameID` マッピングの更新については、{% data variables.contact.contact_ent_support %} にお問い合わせください。{% endif %}
|
||||
このメッセージは通常、その人のユーザ名またはメールアドレスが IdP で変更されたということを示します。 Ensure that the `NameID` mapping for the user account on {% data variables.product.prodname_ghe_server %} matches the user's `NameID` on your IdP. For more information, see "[Updating a user's SAML `NameID`](#updating-a-users-saml-nameid)."
|
||||
|
||||
### SAMLレスポンスが署名されていなかった場合、あるいは署名が内容とマッチしなかった場合、authログに以下のエラーメッセージが残されます。
|
||||
|
||||
If the `Recipient` does not match the ACS URL for your {% data variables.product.prodname_ghe_server %} instance, one of the following two error messages will appear in the authentication log when a user attempts to authenticate.
|
||||
If the `Recipient` does not match the ACS URL for {% data variables.product.product_location %}, one of the following two error messages will appear in the authentication log when a user attempts to authenticate.
|
||||
|
||||
```
|
||||
Recipient in the SAML response must not be blank.
|
||||
@@ -254,7 +255,7 @@ Recipient in the SAML response must not be blank.
|
||||
Recipient in the SAML response was not valid.
|
||||
```
|
||||
|
||||
IdP の `Recipient` の値を、{% data variables.product.prodname_ghe_server %} インスタンスの完全な ACS URL に設定してください。 For example, `https://ghe.corp.example.com/saml/consume`.
|
||||
Ensure that you set the value for `Recipient` on your IdP to the full ACS URL for {% data variables.product.product_location %}. For example, `https://ghe.corp.example.com/saml/consume`.
|
||||
|
||||
### エラー:「SAML レスポンスが署名されていないか、変更されています」
|
||||
|
||||
@@ -274,4 +275,40 @@ IdP のレスポンスに `Audience` の値がないか、または正しくな
|
||||
Audience is invalid. Audience attribute does not match https://<em>YOUR-INSTANCE-URL</em>
|
||||
```
|
||||
|
||||
IdP の `Audience` の値を、{% data variables.product.prodname_ghe_server %} インスタンスの `EntityId` に設定してください。これは、{% data variables.product.prodname_ghe_server %} インスタンスへの完全な URL です。 For example, `https://ghe.corp.example.com`.
|
||||
Ensure that you set the value for `Audience` on your IdP to the `EntityId` for {% data variables.product.product_location %}, which is the full URL to {% data variables.product.product_location %}. For example, `https://ghe.corp.example.com`.
|
||||
|
||||
### Configuring SAML debugging
|
||||
|
||||
You can configure {% data variables.product.product_name %} to write verbose debug logs to _/var/log/github/auth.log_ for every SAML authentication attempt. You may be able to troubleshoot failed authentication attempts with this extra output.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**:
|
||||
|
||||
- Only enable SAML debugging temporarily, and disable debugging immediately after you finish troubleshooting. If you leave debugging enabled, the size of your log may increase much faster than usual, which can negatively impact the performance of {% data variables.product.product_name %}.
|
||||
- Test new authentication settings for {% data variables.product.product_location %} in a staging environment before you apply the settings in your production environment. 詳しい情報については "[ステージングインスタンスのセットアップ](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)"を参照してください。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.options-tab %}
|
||||
1. Under "SAML debugging", select the drop-down and click **Enabled**.
|
||||
|
||||
|
||||
|
||||
1. Attempt to sign into {% data variables.product.product_location %} through your SAML IdP.
|
||||
|
||||
1. Review the debug output in _/var/log/github/auth.log_ on {% data variables.product.product_location %}.
|
||||
|
||||
1. When you're done troubleshooting, select the drop-down and click **Disabled**.
|
||||
|
||||
|
||||
|
||||
### Decoding responses in _auth.log_
|
||||
|
||||
Some output in _auth.log_ may be Base64-encoded. You can access the administrative shell and use the `base64` utility on {% data variables.product.product_location %} to decode these responses. For more information, see "[Accessing the administrative shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)."
|
||||
|
||||
```shell
|
||||
$ base64 --decode <em>ENCODED OUTPUT</em>
|
||||
```
|
||||
|
||||
@@ -96,7 +96,7 @@ featuredLinks:
|
||||
- '{% ifversion ghae %}/admin/identity-and-access-management/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad{% endif %}'
|
||||
- '{% ifversion ghae %}/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise{% endif %}'
|
||||
- '{% ifversion ghae %}/admin/overview/about-upgrades-to-new-releases{% endif %}'
|
||||
- '{% ifversion ghae %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae{% endif %}'
|
||||
- '{% ifversion ghae %}/admin/configuration/configuring-your-enterprise/deploying-github-ae{% endif %}'
|
||||
- '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
|
||||
- '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
|
||||
- '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
|
||||
|
||||
@@ -37,7 +37,7 @@ You can disable {% data variables.product.prodname_dependabot_security_updates %
|
||||
|
||||
## Supported repositories
|
||||
|
||||
{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites.
|
||||
{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -59,7 +59,7 @@ If security updates are not enabled for your repository and you don't know why,
|
||||
|
||||
You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below).
|
||||
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)."
|
||||
|
||||
@@ -68,7 +68,7 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**.
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
|
||||
{% ifversion fpt or ghec %}{% else %}{% endif %}
|
||||
|
||||
|
||||
|
||||
@@ -84,7 +84,7 @@ The recommended formats explicitly define which versions are used for all direct
|
||||
{%- endif %}
|
||||
| Maven | Java, Scala | `pom.xml` | `pom.xml` |
|
||||
| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`|
|
||||
| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
|
||||
| pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %}
|
||||
| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
|
||||
| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
|
||||
|
||||
@@ -46,7 +46,8 @@ topics:
|
||||
|
||||
{% endif %}
|
||||
1. デフォルトでは、アプリケーションのセキュリティを高めるため、アプリケーションは期限付きのユーザ認可トークンを使用します。 期限付きのユーザトークンの使用をオプトアウトするには、[Expire user authorization tokens] の選択を解除する必要があります。 リフレッシュトークンフローの設定と、期限付きユーザトークンの利点に関する詳細については、「[ユーザからサーバーに対するアクセストークンをリフレッシュする](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)」を参照してください。 
|
||||
1. アプリケーションが OAuth フローを使用してユーザを認可する場合、[**Request user authorization (OAuth) during installation**] を選択して、ユーザーかアプリをインストール時に認可するようにできます。 このオプションを選択した場合、[Setup URL] が利用できなくなり、アプリケーションのインストール後にユーザはあなたが設定した [User authorization callback URL] にリダイレクトされます。 詳しい情報については「[インストール中にユーザを認可する](/apps/installing-github-apps/#authorizing-users-during-installation)」を参照してください。 
|
||||
1. アプリケーションが OAuth フローを使用してユーザを認可する場合、[**Request user authorization (OAuth) during installation**] を選択して、ユーザーかアプリをインストール時に認可するようにできます。 このオプションを選択した場合、[Setup URL] が利用できなくなり、アプリケーションのインストール後にユーザはあなたが設定した [User authorization callback URL] にリダイレクトされます。 詳しい情報については「[インストール中にユーザを認可する](/apps/installing-github-apps/#authorizing-users-during-installation)」を参照してください。 {% if device-flow-is-opt-in %}
|
||||
1. If your GitHub App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." {% endif %}
|
||||
1. インストール後に追加の設定が必要な場合、[Setup URL] を追加して、アプリケーションをインストールした後にユーザをリダイレクトします。 
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -127,7 +127,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
|
||||
デバイスフローを使えば、CLIツールやGit認証情報マネージャーなどのヘッドレスアプリケーションのユーザを認可できます。
|
||||
|
||||
デバイスフローを使ったユーザの認可については、「[OAuth App の認可](/developers/apps/authorizing-oauth-apps#device-flow)」を参照してください。
|
||||
{% if device-flow-is-opt-in %}Before you can use the device flow to identify and authorize users, you must first enable it in your app's settings. For more information on enabling device flow, see "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)." {% endif %}For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)."
|
||||
|
||||
## ユーザがアクセスできるインストールされたリソースの確認
|
||||
|
||||
|
||||
@@ -125,6 +125,12 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
|
||||
The device flow allows you to authorize users for a headless app, such as a CLI tool or Git credential manager.
|
||||
|
||||
{% if device-flow-is-opt-in %}
|
||||
|
||||
Before you can use the device flow to authorize and identify users, you must first enable it in your app's settings. For more information about enabling the device flow in your app, see "[Modifying an OAuth App](/developers/apps/managing-oauth-apps/modifying-an-oauth-app)" for OAuth Apps and "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)" for GitHub Apps.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Overview of the device flow
|
||||
|
||||
1. Your app requests device and user verification codes and gets the authorization URL where the user will enter the user verification code.
|
||||
@@ -254,10 +260,12 @@ If you make more than one access token request (`POST {% data variables.product.
|
||||
| `unsupported_grant_type` | The grant type must be `urn:ietf:params:oauth:grant-type:device_code` and included as an input parameter when you poll the OAuth token request `POST {% data variables.product.oauth_host_code %}/login/oauth/access_token`.
|
||||
| `incorrect_client_credentials` | For the device flow, you must pass your app's client ID, which you can find on your app settings page. The `client_secret` is not needed for the device flow.
|
||||
| `incorrect_device_code` | The device_code provided is not valid.
|
||||
| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.
|
||||
| `access_denied` | When a user clicks cancel during the authorization process, you'll receive a `access_denied` error and the user won't be able to use the verification code again.{% if device-flow-is-opt-in %}
|
||||
| `device_flow_disabled` | Device flow has not been enabled in the app's settings. For more information, see "[Device flow](#device-flow)."{% endif %}
|
||||
|
||||
For more information, see the "[OAuth 2.0 Device Authorization Grant](https://tools.ietf.org/html/rfc8628#section-3.5)."
|
||||
|
||||
|
||||
## Non-Web application flow
|
||||
|
||||
Non-web authentication is available for limited situations like testing. If you need to, you can use [Basic Authentication](/rest/overview/other-authentication-methods#basic-authentication) to create a personal access token using your [Personal access tokens settings page](/articles/creating-an-access-token-for-command-line-use). This technique enables the user to revoke access at any time.
|
||||
|
||||
@@ -49,5 +49,6 @@ topics:
|
||||
**注釈:** {% data variables.product.prodname_github_apps %} と異なり、OAuth App は複数のコールバック URL を持つことはできません。
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
10. **Register application** をクリックする。 
|
||||
{% endif %}{% if device-flow-is-opt-in %}
|
||||
1. If your OAuth App will use the device flow to identify and authorize users, click **Enable Device Flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." {% endif %}
|
||||
2. **Register application** をクリックする。 
|
||||
|
||||
@@ -18,5 +18,6 @@ topics:
|
||||
{% data reusables.user-settings.developer_settings %}
|
||||
{% data reusables.user-settings.github_apps %}
|
||||
{% data reusables.user-settings.modify_github_app %}
|
||||
5. 「Basic information（基本情報）」で、修正したいGitHub Appの情報を変更してください。 
|
||||
5. 「Basic information（基本情報）」で、修正したいGitHub Appの情報を変更してください。 {% if device-flow-is-opt-in %}
|
||||
1. If your GitHub App will use the device flow to identify and authorize users, click **Enable device flow**. For more information about the device flow, see "[Authorizing OAuth Apps](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)." {% endif %}
|
||||
6. [**Save changes**] をクリックします。 
|
||||
|
||||
@@ -46,17 +46,17 @@ webhookの`POST`リクエストには、特別なヘッダがあります。 詳
|
||||
|
||||
`plan`オブジェクトには以下のキーがあります。
|
||||
|
||||
| キー | 種類 | 説明 |
|
||||
| ------------------------ | ------------------ | ------------------------------------------------------ |
|
||||
| `id` | `integer` | このプランの一意の識別子。 |
|
||||
| `name` | `string` | プラン名。 |
|
||||
| `説明` | `string` | プランの説明。 |
|
||||
| `monthly_price_in_cents` | `integer` | このプランのセント (米国の通貨) 単位の月額。 たとえば、月額10米ドルのリストは1000セントです。 |
|
||||
| `yearly_price_in_cents` | `integer` | このプランのセント (米国の通貨) 単位の年額。 たとえば、月額100米ドルのリストは10000セントです。 |
|
||||
| `price_model` | `string` | このリストの価格モデル。 `flat-rate`、`per-unit`、`free`のいずれかです。 |
|
||||
| `has_free_trial` | `boolean` | このリストが無料トライアルを提供する場合は`true`になります。 |
|
||||
| `unit_name` | `string` | ユニットの名前。 価格モデルが`per-unit`でない場合、これは`nil`になります。 |
|
||||
| `bullet` | `array of strings` | 価格プランに設定されている箇条書きの名前。 |
|
||||
| キー | 種類 | 説明 |
|
||||
| ------------------------ | ------------------ | ------------------------------------------------------- |
|
||||
| `id` | `integer` | このプランの一意の識別子。 |
|
||||
| `name` | `string` | プラン名。 |
|
||||
| `説明` | `string` | プランの説明。 |
|
||||
| `monthly_price_in_cents` | `integer` | このプランのセント (米国の通貨) 単位の月額。 たとえば、月額10米ドルのリストは1000セントです。 |
|
||||
| `yearly_price_in_cents` | `integer` | このプランのセント (米国の通貨) 単位の年額。 たとえば、月額100米ドルのリストは120000セントです。 |
|
||||
| `price_model` | `string` | このリストの価格モデル。 `flat-rate`、`per-unit`、`free`のいずれかです。 |
|
||||
| `has_free_trial` | `boolean` | このリストが無料トライアルを提供する場合は`true`になります。 |
|
||||
| `unit_name` | `string` | ユニットの名前。 価格モデルが`per-unit`でない場合、これは`nil`になります。 |
|
||||
| `bullet` | `array of strings` | 価格プランに設定されている箇条書きの名前。 |
|
||||
|
||||
<br/>
|
||||
|
||||
|
||||
@@ -16,6 +16,5 @@ children:
|
||||
- /verifying-your-email-address
|
||||
- /setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /setting-up-a-trial-of-github-enterprise-server
|
||||
- /setting-up-a-trial-of-github-ae
|
||||
---
|
||||
|
||||
|
||||
@@ -1,66 +0,0 @@
|
||||
---
|
||||
title: Setting up a trial of GitHub AE
|
||||
intro: '{% data variables.product.prodname_ghe_managed %} のトライアルは無料でできます。'
|
||||
versions:
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: GitHub AE trial
|
||||
---
|
||||
|
||||
## About the {% data variables.product.prodname_ghe_managed %} trial
|
||||
|
||||
You can set up a 90-day trial to evaluate {% data variables.product.prodname_ghe_managed %}. This process allows you to deploy a {% data variables.product.prodname_ghe_managed %} account in your existing Azure region.
|
||||
|
||||
- **{% data variables.product.prodname_ghe_managed %} account**: The Azure resource that contains the deployment of {% data variables.product.prodname_ghe_managed %}.
|
||||
- **{% data variables.product.prodname_ghe_managed %} portal**: The Azure management tool at [https://portal.azure.com](https://portal.azure.com). This is used to deploy the {% data variables.product.prodname_ghe_managed %} account.
|
||||
|
||||
## {% data variables.product.prodname_ghe_managed %} のトライアルを設定する
|
||||
|
||||
|
||||
Before you can start your trial of {% data variables.product.prodname_ghe_managed %}, you must request access by contacting your {% data variables.product.prodname_dotcom %} account team. {% data variables.product.prodname_dotcom %} will enable the {% data variables.product.prodname_ghe_managed %} trial for your Azure subscription.
|
||||
|
||||
Contact {% data variables.contact.contact_enterprise_sales %} to check your eligibility for a {% data variables.product.prodname_ghe_managed %} trial.
|
||||
|
||||
## Deploying {% data variables.product.prodname_ghe_managed %} with the {% data variables.actions.azure_portal %}
|
||||
|
||||
The {% data variables.actions.azure_portal %} allows you to deploy the {% data variables.product.prodname_ghe_managed %} account in your Azure resource group.
|
||||
|
||||
1. On the {% data variables.actions.azure_portal %}, type `GitHub AE` in the search field. Then, under _Services_, click {% data variables.product.prodname_ghe_managed %}. 
|
||||
1. To begin the process of adding a new {% data variables.product.prodname_ghe_managed %} account, click **Create GitHub AE account**.
|
||||
1. Complete the "Project details" and "Instance details" fields. 
|
||||
- **Account name:** The hostname for your enterprise
|
||||
- **Administrator username:** A username for the initial enterprise owner that will be created in {% data variables.product.prodname_ghe_managed %}
|
||||
- **Administrator email:** The email address that will receive the login information
|
||||
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.prodname_ghe_managed %} を初期化する](/admin/configuration/initializing-github-ae)」を参照してください。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Software updates for your {% data variables.product.prodname_ghe_managed %} deployment are performed by {% data variables.product.prodname_dotcom %}. For more information, see "[About upgrades to new releases](/admin/overview/about-upgrades-to-new-releases)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Navigating to your enterprise
|
||||
|
||||
You can use the {% data variables.actions.azure_portal %} to navigate to your {% data variables.product.prodname_ghe_managed %} deployment. The resulting list includes all the {% data variables.product.prodname_ghe_managed %} deployments in your Azure region.
|
||||
|
||||
1. On the {% data variables.actions.azure_portal %}, in the left panel, click **All resources**.
|
||||
1. From the available filters, click **All types**, then deselect **Select all** and select **GitHub AE**: 
|
||||
|
||||
## 次のステップ
|
||||
|
||||
Once your deployment has been provisioned, the next step is to initialize {% data variables.product.prodname_ghe_managed %}. 詳しい情報については、「[{% data variables.product.prodname_ghe_managed %} を初期化する](/github-ae@latest/admin/configuration/configuring-your-enterprise/initializing-github-ae)」を参照してください。
|
||||
|
||||
## トライアルを終了する
|
||||
|
||||
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.prodname_ghe_managed %} を評価するための時間がさらに必要な場合は、{% data variables.contact.contact_enterprise_sales %} に連絡して延長をリクエストしてください。
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- "[Enabling {% data variables.product.prodname_advanced_security %} features on {% data variables.product.prodname_ghe_managed %}](/github/getting-started-with-github/about-github-advanced-security#enabling-advanced-security-features-on-github-ae)"
|
||||
- "[{% data variables.product.prodname_ghe_managed %} release notes](/github-ae@latest/admin/overview/github-ae-release-notes)"
|
||||
@@ -17,7 +17,11 @@ shortTitle: Transfer an issue
|
||||
---
|
||||
To transfer an open issue to another repository, you must have write access to the repository the issue is in and the repository you're transferring the issue to. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
|
||||
|
||||
You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}You can't transfer an issue from a private repository to a public repository.{% endif %}
|
||||
{% note %}
|
||||
|
||||
**Note**: You can only transfer issues between repositories owned by the same user or organization account. {% ifversion fpt or ghes or ghec %}A private repository issue cannot be transferred to a public repository.{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
When you transfer an issue, comments, labels and assignees are retained. The issue's milestones are not retained. This issue will stay on any user-owned or organization-wide project boards and be removed from any repository project boards. For more information, see "[About project boards](/articles/about-project-boards)."
|
||||
|
||||
|
||||
@@ -508,10 +508,10 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| Action | Description |
|
||||
|--------|-------------|
|
||||
| `package_version_published` | Triggered when a package version is published. |
|
||||
| `package_version_deleted` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
|
||||
| `package_deleted` | Triggered when an entire package is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
|
||||
| `package_version_restored` | Triggered when a specific package version is deleted. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
|
||||
| `package_restored` | Triggered when an entire package is restored. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."
|
||||
| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -47,8 +47,7 @@ shortTitle: 権限について
|
||||
|
||||
例:
|
||||
- リポジトリからパッケージをダウンロードしてインストールするには、トークンは`read:packages`スコープを持っていなければならず、ユーザアカウントは読み取り権限を持っていなければなりません。
|
||||
- {% ifversion fpt or ghes or ghec %}{% data variables.product.product_name %}上のパッケージを削除するには、トークンが少なくとも`delete:packages`と`read:packages`のスコープを持っている必要があります。 repoのスコープがあるパッケージでは、`repo`スコープも必要です。{% elsif ghae %}{% data variables.product.product_name %}上の、パッケージの特定バージョンを削除するには、トークンが`delete:packages`と`repo`スコープを持っている必要があります。{% endif %}詳しい情報については「[パッケージの削除と復元](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。
|
||||
|
||||
- |{% ifversion fpt or ghes > 3.1 or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
| スコープ | 説明 | 必要な権限 |
|
||||
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------- | ------------ |
|
||||
| `read:packages` | {% data variables.product.prodname_registry %}からのパッケージのダウンロードとインストール | 読み取り |
|
||||
|
||||
@@ -9,7 +9,7 @@ redirect_from:
|
||||
- /packages/guides/deleting-a-container-image
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghes: '>=3.2'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
shortTitle: パッケージの削除と復元
|
||||
|
||||
@@ -108,7 +108,7 @@ You can delete a private or public package in the {% data variables.product.prod
|
||||
You can delete a version of a package in the {% data variables.product.product_name %} user interface or using the GraphQL API.
|
||||
{% endif %}
|
||||
|
||||
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and "[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql)."
|
||||
When you use the GraphQL API to query and delete private packages, you must use the same token you use to authenticate to {% data variables.product.prodname_registry %}. For more information, see {% ifversion fpt or ghec or ghes > 3.1 or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" and {% endif %}"[Forming calls with GraphQL]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/guides/forming-calls-with-graphql)."
|
||||
|
||||
You can configure webhooks to subscribe to package-related events, such as when a package is published or updated. For more information, see the "[`package` webhook event](/webhooks/event-payloads/#package)."
|
||||
|
||||
|
||||
@@ -190,5 +190,5 @@ To install an Apache Maven package from {% data variables.product.prodname_regis
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
- "[Working with the Gradle registry](/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry)"{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"{% endif %}
|
||||
|
||||
@@ -261,8 +261,12 @@ $ docker pull <em>HOSTNAME/OWNER/REPOSITORY/IMAGE_NAME:TAG_NAME</em>
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% endif %} <!-- End of main versioning block -->
|
||||
|
||||
@@ -215,5 +215,5 @@ To use a published package from {% data variables.product.prodname_registry %},
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
- "[Working with the Apache Maven registry](/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry)"{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"{% endif %}
|
||||
|
||||
@@ -27,7 +27,7 @@ If you publish over 1,000 npm package versions to {% data variables.product.prod
|
||||
|
||||
In the future, to improve performance of the service, you won't be able to publish more than 1,000 versions of a package on {% data variables.product.prodname_dotcom %}. Any versions published before hitting this limit will still be readable.
|
||||
|
||||
If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" or "[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
|
||||
If you reach this limit, consider deleting package versions or contact Support for help. When this limit is enforced, our documentation will be updated with a way to work around this limit. For more information, see {% ifversion fpt or ghec or ghes > 3.1 or ghae %}"[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)" or {% endif %}"[Contacting Support](/packages/learn-github-packages/about-github-packages#contacting-support)."
|
||||
|
||||
## Authenticating to {% data variables.product.prodname_registry %}
|
||||
|
||||
@@ -212,7 +212,3 @@ If your instance has subdomain isolation disabled:
|
||||
|
||||
{% data variables.product.prodname_registry %} allows you to access the official NPM registry at `registry.npmjs.com`, if your {% data variables.product.prodname_ghe_server %} administrator has enabled this feature. For more information, see [Connecting to the official NPM registry](/admin/packages/configuring-packages-support-for-your-enterprise#connecting-to-the-official-npm-registry).
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
|
||||
@@ -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.
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
## Further reading
|
||||
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
{% endif %}
|
||||
|
||||
@@ -151,6 +151,10 @@ You can use gems from {% data variables.product.prodname_registry %} much like y
|
||||
$ gem install octo-gem --version "0.1.1"
|
||||
```
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)"
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ライブラリ
|
||||
intro: 'You can use the official Octokit library and other third-party libraries to extend and simplify how you use the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API.'
|
||||
intro: '公式のOctokitライブラリや、その他のサードパーティライブラリを使い、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIの使い方を拡張し、シンプルにすることができます。'
|
||||
redirect_from:
|
||||
- /libraries
|
||||
- /v3/libraries
|
||||
|
||||
@@ -17,7 +17,7 @@ shortTitle: GitHub Appの権限
|
||||
|
||||
### {% data variables.product.prodname_github_app %}の権限について
|
||||
|
||||
{% data variables.product.prodname_github_apps %} are created with a set of permissions. {% data variables.product.prodname_github_app %}がAPIを介してアクセスできるリソースが、権限によって決まります。 詳細は、「[GitHub Appの権限の設定](/apps/building-github-apps/setting-permissions-for-github-apps/)」を参照してください。
|
||||
{% data variables.product.prodname_github_apps %}は、一連の権限を付けて作成されます。 {% data variables.product.prodname_github_app %}がAPIを介してアクセスできるリソースが、権限によって決まります。 詳細は、「[GitHub Appの権限の設定](/apps/building-github-apps/setting-permissions-for-github-apps/)」を参照してください。
|
||||
|
||||
### メタデータ権限
|
||||
|
||||
@@ -121,6 +121,9 @@ _検索_
|
||||
- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#get-an-artifact) (:read)
|
||||
- [`DELETE /repos/:owner/:repo/actions/artifacts/:artifact_id`](/rest/reference/actions#delete-an-artifact) (:write)
|
||||
- [`GET /repos/:owner/:repo/actions/artifacts/:artifact_id/zip`](/rest/reference/actions#download-an-artifact) (:read)
|
||||
{% if actions-cache-management -%}
|
||||
- [`GET /repos/:owner/:repo/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-a-repository) (:read)
|
||||
{% endif -%}
|
||||
- [`GET /repos/:owner/:repo/actions/jobs/:job_id`](/rest/reference/actions#get-a-job-for-a-workflow-run) (:read)
|
||||
- [`GET /repos/:owner/:repo/actions/jobs/:job_id/logs`](/rest/reference/actions#download-job-logs-for-a-workflow-run) (:read)
|
||||
- [`GET /repos/:owner/:repo/actions/runs`](/rest/reference/actions#list-workflow-runs-for-a-repository) (:read)
|
||||
@@ -644,6 +647,10 @@ _Team_
|
||||
### "organization administration"に対する権限
|
||||
|
||||
- [`PATCH /orgs/:org`](/rest/reference/orgs#update-an-organization) (:write)
|
||||
{% if actions-cache-management -%}
|
||||
- [`GET /orgs/:org/actions/cache/usage`](/rest/reference/actions#get-github-actions-cache-usage-for-an-organization) (:read)
|
||||
- [`GET /orgs/:org/actions/cache/usage-by-repository`](/rest/reference/actions#list-repositories-with-github-actions-cache-usage-for-an-organization) (:read)
|
||||
{% endif -%}
|
||||
{% ifversion fpt -%}
|
||||
- [`GET /orgs/:org/interaction-limits`](/rest/reference/interactions#get-interaction-restrictions-for-an-organization) (:read)
|
||||
{% endif -%}
|
||||
@@ -880,7 +887,7 @@ _Team_
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3%}
|
||||
### Permission on "dependabot_secrets"
|
||||
### "dependabot_secrets"に対する権限
|
||||
- [`GET /repos/:owner/:repo/dependabot/secrets/public-key`](/rest/reference/dependabot#get-a-repository-public-key) (:read)
|
||||
- [`GET /repos/:owner/:repo/dependabot/secrets`](/rest/reference/dependabot#list-repository-secrets) (:read)
|
||||
- [`GET /repos/:owner/:repo/dependabot/secrets/:secret_name`](/rest/reference/dependabot#get-a-repository-secret) (:read)
|
||||
|
||||
@@ -614,14 +614,14 @@ JavaScript ハンドラを記述して、コールバックを処理できます
|
||||
|
||||
## タイムゾーン
|
||||
|
||||
新しいコミットの作成など、新しいデータを作成する一部のリクエストでは、タイムスタンプを指定または生成するときにタイムゾーン情報を提供できます。 We apply the following rules, in order of priority, to determine timezone information for such API calls.
|
||||
新しいコミットの作成など、新しいデータを作成する一部のリクエストでは、タイムスタンプを指定または生成するときにタイムゾーン情報を提供できます。 そういったAPI 呼び出しのタイムゾーン情報を決定する際に、優先順位に従って次のルールを適用します。
|
||||
|
||||
* [ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する](#explicitly-providing-an-iso-8601-timestamp-with-timezone-information)
|
||||
* [`Time-Zone` ヘッダを使用する](#using-the-time-zone-header)
|
||||
* [ユーザが最後に認識されたタイムゾーンを使用する](#using-the-last-known-timezone-for-the-user)
|
||||
* [他のタイムゾーン情報を含まない UTC をデフォルトにする](#defaulting-to-utc-without-other-timezone-information)
|
||||
|
||||
Note that these rules apply only to data passed to the API, not to data returned by the API. As mentioned in "[Schema](#schema)," timestamps returned by the API are in UTC time, ISO 8601 format.
|
||||
これらのルールは、APIに渡されたデータに対してのみ適用され、APIが返す日付には適用されないことに注意してください。 「[スキーマ](#schema)」にあるように、APIが返すタイムスタンプはUTCでISO8601フォーマットです。
|
||||
|
||||
### ISO 8601 タイムスタンプにタイムゾーン情報を明示的に提供する
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ API で不可解な問題が発生した場合、発生したと思われる問
|
||||
|
||||
通常、クライアントが正しく認証されていない場合、`404` エラーが送信されます。 このような場合、`403 Forbidden` が表示されるはずであると考えるかもしれません。 しかし、プライベートリポジトリに関する_いずれの_情報も提供されないため、API は代わりに `404` エラーを返します。
|
||||
|
||||
To troubleshoot, ensure [you're authenticating correctly](/guides/getting-started/), [your OAuth access token has the required scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/), [third-party application restrictions][oap-guide] are not blocking access, and that [the token has not expired or been revoked](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
トラブルシューティングを行うには、[正しく認証されていること](/guides/getting-started/)、[OAuth アクセストークンに必要なスコープがあること](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)、[サードパーティアプリケーションの制限][oap-guide]によってアクセスがブロックされていないこと、そして[トークンが期限切れになっていたり取り消されたりしてない](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)ことを確認してください。
|
||||
|
||||
## 表示されない結果がある
|
||||
|
||||
@@ -63,9 +63,9 @@ curl -u my_username:my_password -X POST "https://api.github.com/authorizations"
|
||||
|
||||
次に、[Web アプリケーションフロー](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)に切り替えて、アクセストークンを生成します。
|
||||
|
||||
## Timeouts
|
||||
## タイムアウト
|
||||
|
||||
If {% data variables.product.product_name %} takes more than 10 seconds to process an API request, {% data variables.product.product_name %} will terminate the request and you will receive a timeout response.
|
||||
{% data variables.product.product_name %}がAPIを処理するのに10秒以上かかると、{% data variables.product.product_name %}はリクエストを終了させ、タイムアウトのレスポンスが返されます。
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: アクション
|
||||
intro: 'With the Actions API, you can manage and control {% data variables.product.prodname_actions %} for an organization or repository.'
|
||||
intro: 'Actions APIを使うと、Organizationやリポジトリの{% data variables.product.prodname_actions %}を管理し、制御できます。'
|
||||
redirect_from:
|
||||
- /v3/actions
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: アクティビティ
|
||||
intro: 'The Activity API allows you to list events and feeds and manage notifications, starring, and watching for the authenticated user.'
|
||||
intro: Activity APIを使うと、イベントやフィードをリストし、通知、Star、認証されたユーザのWatchを管理できます。
|
||||
redirect_from:
|
||||
- /v3/activity
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: アプリ
|
||||
intro: The GitHub Apps API enables you to retrieve the information about the installation as well as specific information about GitHub Apps.
|
||||
intro: GitHub Apps APIを使うと、インストールに関する情報や、GitHub Appに関する特定の情報を取得できます。
|
||||
redirect_from:
|
||||
- /v3/apps
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 支払い
|
||||
intro: 'With the Billing API, you can monitor the charges and usage {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} for a user or organization.'
|
||||
intro: 'Billing APIを使うと、ユーザやOrganizationに対する{% data variables.product.prodname_actions %}や{% data variables.product.prodname_registry %}の確認と使用状況をモニターできます。'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ブランチ
|
||||
intro: The branches API allows you to modify branches and their protection settings.
|
||||
intro: ブランチAPIを使うと、ブランチとブランチの保護設定を変更できます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: チェック
|
||||
intro: 'With the Checks API, you can build {% data variables.product.prodname_github_apps %} that run powerful checks against the code changes in a repository.'
|
||||
intro: 'Checks APIを使用すると、リポジトリでのコード変更に対して強力なチェックを行う{% data variables.product.prodname_github_apps %}を構築できます。'
|
||||
redirect_from:
|
||||
- /v3/checks
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Code scanning
|
||||
intro: The Code Scanning API enables you to retrieve and update the code scanning alerts and analyses from a repository.
|
||||
intro: Code Scanning APIを使うと、リポジトリからCode scanningのアラートと分析を取得し、更新できます。
|
||||
redirect_from:
|
||||
- /v3/code-scanning
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 行動規範
|
||||
intro: The Codes of Conduct API lets you to retrieve the information about a particular repository's code of conduct.
|
||||
intro: Codes of Conduct APIを使うと、特定のリポジトリの行動規範に関する情報を取得できます。
|
||||
redirect_from:
|
||||
- /v3/codes_of_conduct
|
||||
- /v3/codes-of-conduct
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Codespaces
|
||||
intro: 'The {% data variables.product.prodname_codespaces %} API enables you to manage your codespaces using the REST API.'
|
||||
intro: '{% data variables.product.prodname_codespaces %} APIを使うと、REST APIを利用してCodespacesを管理できます。'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -12,4 +12,4 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
<!--
|
||||
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/codespaces
|
||||
-->
|
||||
-->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: コラボレータ
|
||||
intro: 'The collaborators API allows you to add, invite, and remove collaborators from a repository.'
|
||||
intro: コラボレータAPIを使うと、リポジトリでコラボレータの追加、招待、削除が行えます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: コミット
|
||||
intro: 'The commits API allows you to list, view, and compare commits in a repository. You can also interact with commit comments and commit statuses.'
|
||||
intro: コミットAPIを使うと、リポジトリ内のコミットのリスト、表示、比較ができます。 コミットコメントやコミットのステータスの操作もできます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Dependabot
|
||||
intro: 'With the {% data variables.product.prodname_dependabot %} Secrets API, you can manage and control {% data variables.product.prodname_dependabot %} secrets for an organization or repository.'
|
||||
intro: '{% data variables.product.prodname_dependabot %} Secrets APIを使うと、Organizationあるいはリポジトリの{% data variables.product.prodname_dependabot %}sjシークレットを管理し、制御できます。'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.4'
|
||||
@@ -12,4 +12,4 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
<!--
|
||||
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/dependabot
|
||||
-->
|
||||
-->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: デプロイメント
|
||||
intro: 'The deployments API allows you to create and delete deploy keys, deployments, and deployment environments.'
|
||||
intro: デプロイメントAPIを使うと、デプロイーキー、デプロイメント、デプロイメント環境の作成と削除ができます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 絵文字
|
||||
intro: 'With the Emojis API, you can list and view all the available emojis to use in {% data variables.product.product_name %}.'
|
||||
intro: 'Emojis APIを使用すると、{% data variables.product.product_name %}で利用できるすべての絵文字のリストと表示ができます。'
|
||||
redirect_from:
|
||||
- /v3/emojis
|
||||
- /v3/misc
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Gist
|
||||
intro: 'The Gists API enables the authorized user to list, create, update and delete the public gists on {% data variables.product.product_name %}.'
|
||||
intro: 'Gists APIを使うと、認可されたユーザは{% data variables.product.product_name %}上のパブリックGistのリスト、作成、、更新、削除ができます。'
|
||||
redirect_from:
|
||||
- /v3/gists
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Git データベース
|
||||
intro: 'The Git Database API enables you to read and write raw Git objects to your Git database on {% data variables.product.product_name %} and to list and update Git references (branch heads and tags).'
|
||||
intro: 'Git Database APIを使うと、{% data variables.product.product_name %}上のGitデータベースに対してRaw形式のGitオブジェクトを読み書きしたり、リファレンス (ブランチheadやタグ) をリストおよび更新したりできます。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /v3/git
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Gitignore
|
||||
intro: The Gitignore API fetches `.gitignore` templates that can be used to ignore files and directories.
|
||||
intro: Gitignore APIは、ファイルやディレクトリを無視するために利用できる`.gitignore`テンプレートをフェッチします。
|
||||
redirect_from:
|
||||
- /v3/gitignore
|
||||
versions:
|
||||
@@ -15,4 +15,4 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
<!--
|
||||
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/gitignore
|
||||
-->
|
||||
-->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: インタラクション
|
||||
intro: 'With the Interactions API, people with owner or admin access can set the interaction limit for the users in their organizations and repositories.'
|
||||
intro: Interactions APIを使うと、オーナーもしくは管理アクセスを持つ人が、Organizationやリポジトリ内のユーザの操作制限を設定できます。
|
||||
redirect_from:
|
||||
- /v3/interactions
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Issue
|
||||
intro: 'The Issues API enables you to view and manage issues, including issue assignees, comments, labels, and milestones.'
|
||||
intro: Issues APIを使うと、Issueにアサインされた人、コメント、ラベル、マイルストーンを含め、Issueの表示と管理ができます。
|
||||
redirect_from:
|
||||
- /v3/issues
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: ライセンス
|
||||
intro: The Licenses API lets you to retrieve popular open source licenses and information about a particular project's license file.
|
||||
intro: Licenses API は、広く利用されているオープンソースライセンスと、特定のプロジェクトのライセンスファイルに関する情報を返します。
|
||||
redirect_from:
|
||||
- /v3/licenses
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Markdown
|
||||
intro: The Markdown API enables you to render a markdown document as an HTML page or as raw text.
|
||||
intro: MarkdownAPIを使うと、MarkdownドキュメントをHTMLページあるいは生のテキストとしてレンダリングできます。
|
||||
redirect_from:
|
||||
- /v3/markdown
|
||||
versions:
|
||||
@@ -15,4 +15,4 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
<!--
|
||||
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/markdown
|
||||
-->
|
||||
-->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: メタ情報
|
||||
intro: 'The Meta API returns meta information about {% data variables.product.product_name %} including the IP addresses of {% data variables.product.product_name %} services.'
|
||||
intro: 'Meta APIは、{% data variables.product.product_name %}サービスのIPアドレスを含む{% data variables.product.product_name %}に関するメタ情報を返します。'
|
||||
redirect_from:
|
||||
- /v3/meta
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Metrics
|
||||
intro: 'The repository metrics API allows you to retrieve community profile, statistics, and traffic for your repository.'
|
||||
title: メトリクス
|
||||
intro: リポジトリメトリクスAPIを使うと、リポジトリのコミュニティプロフィール、統計、トラフィックを取得できます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /rest/reference/repository-metrics
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 移行
|
||||
intro: 'The Migration API lets you migrate the repositories and users of your organization from {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.prodname_ghe_server %}.'
|
||||
intro: 'Migration APIを使うと、{% data variables.product.prodname_dotcom_the_website %}から{% data variables.product.prodname_ghe_server %}へ、Organizaitonのリポジトリとユーザを移行できます。'
|
||||
redirect_from:
|
||||
- /v3/migrations
|
||||
- /v3/migration
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Organization
|
||||
intro: 'The Organizations API gives you access to control and manage all your {% data variables.product.product_name %} organizations.'
|
||||
intro: 'Organizations APIを使うと、自分のすべての{% data variables.product.product_name %} Organizationの制御と管理のためのアクセスができます。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /v3/orgs
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: パッケージ
|
||||
intro: 'With the {% data variables.product.prodname_registry %} API, you can manage packages for your {% data variables.product.prodname_dotcom %} repositories and organizations.'
|
||||
intro: '{% data variables.product.prodname_registry %} APIを使うと、{% data variables.product.prodname_dotcom %}の自分のリポジトリとOrganizationのパッケージの管理ができます。'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Pages
|
||||
intro: The GitHub Pages API allows you to interact with GitHub Pages sites and build information.
|
||||
intro: GitHub Pages APIを使うと、GitHub Pagesのサイトとビルド情報の操作ができます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -14,4 +14,4 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
<!--
|
||||
Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/pages
|
||||
-->
|
||||
-->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: プロジェクト
|
||||
intro: 'The Projects API lets you create, list, update, delete and customize projects in a repository.'
|
||||
intro: Projects APIを使うと、リポジトリ内のプロジェクトの作成、リスト、更新、削除、カスタマイズができます。
|
||||
redirect_from:
|
||||
- /v3/projects
|
||||
versions:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: リリース
|
||||
intro: 'The releases API allows you to create, modify, and delete releases and release assets.'
|
||||
intro: リリースAPIを使うと、リリースとリリースアセットの作成、変更、削除ができます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: リポジトリ
|
||||
intro: 'The Repos API allows to create, manage and control the workflow of public and private {% data variables.product.product_name %} repositories.'
|
||||
intro: 'Repos APIを使うと、パブリック及びプライベートの{% data variables.product.product_name %}リポジトリのワークフローの作成、管理、制御ができます。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /v3/repos
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Secret scanning
|
||||
intro: 'Use the secret scanning API to retrieve and update secret alerts from a repository.'
|
||||
intro: Secret scanning APIを使うと、リポジトリのシークレットアラートの取得と更新ができます。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: webhook
|
||||
intro: The webhooks API allows you to create and manage webhooks for your repositories.
|
||||
intro: webhooks APIを使うと、リポジトリのwebhookの作成と管理ができます。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
#Reference: #6154
|
||||
#Documentation for Actions cache management APIs (initial ship)
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '> 3.4'
|
||||
ghae: 'issue-6154'
|
||||
@@ -0,0 +1,6 @@
|
||||
---
|
||||
#docs-content 6307. OAuth device auth flow is opt in.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghae: 'issue-6307'
|
||||
@@ -7,6 +7,7 @@ get_started_with_github_ae:
|
||||
guides:
|
||||
- /admin/overview/about-github-ae
|
||||
- /admin/overview/about-data-residency
|
||||
- /admin/configuration/configuring-your-enterprise/deploying-github-ae
|
||||
- /admin/configuration/initializing-github-ae
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-github-ae
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
date: '2022-02-15'
|
||||
release_candidate: true
|
||||
deprecated: false
|
||||
deprecated: true
|
||||
intro: |
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -0,0 +1,188 @@
|
||||
---
|
||||
date: '2022-03-15'
|
||||
intro: |
|
||||
|
||||
For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
|
||||
> This release is dedicated to our colleague and friend John, a Hubber who was always there to help. You will be greatly missed.
|
||||
>
|
||||
> **John "Ralph" Wiebalk 1986–2021**
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
heading: Secret scanning REST API now returns locations
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve commit details of secrets detected in private repository scans. The new endpoint returns details of a secret's first detection within a file, including the secret's location and commit SHA. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.
|
||||
-
|
||||
heading: Export license data of committer-based billing for GitHub Advanced Security
|
||||
notes:
|
||||
- |
|
||||
Enterprise and organization owners can now export their {% data variables.product.prodname_GH_advanced_security %} license usage data to a CSV file. The {% data variables.product.prodname_advanced_security %} billing data can also be retrieved via billing endpoints in the REST API. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-11-export-github-advanced-security-license-usage-data/)."
|
||||
-
|
||||
heading: GitHub Actions reusable workflows in public beta
|
||||
notes:
|
||||
- |
|
||||
You can now reuse entire workflows as if they were an action. This feature is available in public beta. Instead of copying and pasting workflow definitions across repositories, you can now reference an existing workflow with a single line of configuration. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-05-github-actions-dry-your-github-actions-configuration-by-reusing-workflows/)."
|
||||
-
|
||||
heading: Dependabot security and version updates in public beta
|
||||
notes:
|
||||
- |
|
||||
{% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/github/feedback/discussions/categories/dependabot-feedback). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
|
||||
changes:
|
||||
-
|
||||
heading: 管理に関する変更
|
||||
notes:
|
||||
- Users can now choose the number of spaces a tab is equal to, by setting their preferred tab size in the "Appearance" settings of their user account. All code with a tab indent will render using the preferred tab size.
|
||||
- The {% data variables.product.prodname_github_connect %} data connection record now includes a count of the number of active and dormant users and the configured dormancy period.
|
||||
- You can now give users access to enterprise-specific links by adding custom footers to {% data variables.product.prodname_ghe_server %}. For more information, see "[Configuring custom footers](/admin/configuration/configuring-your-enterprise/configuring-custom-footers)."
|
||||
-
|
||||
heading: Performance Changes
|
||||
notes:
|
||||
- WireGuard, used to secure communication between {% data variables.product.prodname_ghe_server %} instances in a High Availability configuration, has been migrated to the Kernel implementation.
|
||||
-
|
||||
heading: Notification Changes
|
||||
notes:
|
||||
- Organization owners can now unsubscribe from email notifications when new deploy keys are added to repositories belonging to their organizations. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
|
||||
- 'Notification emails from newly created issues and pull requests now include `(Issue #xx)` or `(PR #xx)` in the email subject, so you can recognize and filter emails that reference these types of issues.'
|
||||
-
|
||||
heading: Organization Changes
|
||||
notes:
|
||||
- Organizations can now display a `README.md` file on their profile Overview. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-14-readmes-for-organization-profiles/)."
|
||||
- 'Members of organizations can now view a list of their enterprise owners under the organization''s "People" tab. The enterprise owners list is also now accessible using the GraphQL API. For more information, see the "[`enterpriseOwners`](/graphql/reference/objects#organization)" field under the Organization object in the GraphQL API documentation.'
|
||||
-
|
||||
heading: リポジトリの変更
|
||||
notes:
|
||||
- |
|
||||
A "Manage Access" section is now shown on the "Collaborators and teams" page in your repository settings. The new section makes it easier for repository administrators to see and manage who has access to their repository, and the level of access granted to each user. Administrators can now:
|
||||
|
||||
* Search all members, teams and collaborators who have access to the repository.
|
||||
* View when members have mixed role assignments, granted to them directly as individuals or indirectly via a team. This is visualized through a new "mixed roles" warning, which displays the highest level role the user is granted if their permission level is higher than their assigned role.
|
||||
* Manage access to popular repositories reliably, with page pagination and fewer timeouts when large groups of users have access.
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the repository invitation experience, such as notifications for private repository invites, a UI prompt when visiting a private repository you have a pending invitation for, and a banner on a public repository overview page when there is an pending invitation.'
|
||||
- 'You can now use single-character prefixes for custom autolinks. Autolink prefixes also now allow `.`, `-`, `_`, `+`, `=`, `:`, `/`, and `#` characters, as well as alphanumerics. For more information about custom autolinks, see "[Configuring autolinks to reference external resources](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources)."'
|
||||
- A `CODE_OF_CONDUCT.md` file in the root of a repository is now highlighted in the "About" sidebar on the repository overview page.
|
||||
-
|
||||
heading: 'Releases changes'
|
||||
notes:
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.4 includes improvements to the Releases UI, such as automatically generated release notes which display a summary of all the pull requests for a given release. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-20-improvements-to-github-releases-generally-available/)."'
|
||||
- When a release is published, an avatar list is now displayed at the bottom of the release. Avatars for all user accounts mentioned in the release notes are shown. For more information, see "[Managing releases in a repository](/repositories/releasing-projects-on-github/managing-releases-in-a-repository)."
|
||||
-
|
||||
heading: 'Markdownの変更'
|
||||
notes:
|
||||
- You can now use the new "Accessibility" settings page to manage your keyboard shortcuts. You can choose to disable keyboard shortcuts that only use single characters like <kbd>S</kbd>, <kbd>G</kbd> <kbd>C</kbd>, and <kbd>.</kbd> (the period key). For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-16-managing-keyboard-shortcuts-using-accessibility-settings/)."
|
||||
- You can now choose to use a fixed-width font in Markdown-enabled fields, like issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-12-fixed-width-font-support-in-markdown-enabled-fields/)."
|
||||
- You can now paste a URL on selected text to quickly create a Markdown link. This works in all Markdown-enabled fields, such as issue comments and pull request descriptions. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-linkify-selected-text-on-url-paste/)."
|
||||
- 'An image URL can now be appended with a theme context, such as `#gh-dark-mode-only`, to define how the Markdown image is displayed to a viewer. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-specify-theme-context-for-images-in-markdown/)."'
|
||||
- When creating or editing a gist file with the Markdown (`.md`) file extension, you can now use the "Preview" or "Preview Changes" tab to display a Markdown rendering of the file contents. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-17-preview-the-markdown-rendering-of-gists/)."
|
||||
- When typing the name of a {% data variables.product.prodname_dotcom %} user in issues, pull requests and discussions, the @mention suggester now ranks existing participants higher than other {% data variables.product.prodname_dotcom %} users, so that it's more likely the user you're looking for will be listed.
|
||||
- Right-to-left languages are now supported natively in Markdown files, issues, pull requests, discussions, and comments.
|
||||
-
|
||||
heading: 'Issues and pull requests changes'
|
||||
notes:
|
||||
- The diff setting to hide whitespace changes in the pull request "Files changed" tab is now retained for your user account for that pull request. The setting you have chosen is automatically reapplied if you navigate away from the page and then revisit the "Files changed" tab of the same pull request.
|
||||
- When using auto assignment for pull request code reviews, you can now choose to only notify requested team members independently of your auto assignment settings. This setting is useful in scenarios where many users are auto assigned but not all users require notification. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-team-member-pull-request-review-notifications-can-be-configured-independently-of-auto-assignment/)."
|
||||
-
|
||||
heading: 'Branches changes'
|
||||
notes:
|
||||
- 'Organization and repository administrators can now trigger webhooks to listen for changes to branch protection rules on their repositories. For more information, see the "[branch_protection_rule](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#branch_protection_rule)" event in the webhooks events and payloads documentation.'
|
||||
- When configuring protected branches, you can now enforce that a required status check is provided by a specific {% data variables.product.prodname_github_app %}. If a status is then provided by a different application, or by a user via a commit status, merging is prevented. This ensures all changes are validated by the intended application. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-01-ensure-required-status-checks-provided-by-the-intended-app/)."
|
||||
- Only users with administrator permissions are now able to rename protected branches and modify branch protection rules. Previously, with the exception of the default branch, a collaborator could rename a branch and consequently any non-wildcard branch protection rules that applied to that branch were also renamed. For more information, see "[Renaming a branch](/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch)" and "[Managing a branch protection rule](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule)."
|
||||
- Administrators can now allow only specific users and teams to bypass pull request requirements. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-19-allow-bypassing-required-pull-requests/)."
|
||||
- Administrators can now allow only specific users and teams to force push to a repository. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-12-21-specify-who-can-force-push-to-a-repository/)."
|
||||
- When requiring pull requests for all changes to a protected branch, administrators can now choose if approved reviews are also a requirement. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-require-pull-requests-without-requiring-reviews/)."
|
||||
-
|
||||
heading: 'GitHub Actions changes'
|
||||
notes:
|
||||
- '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} for the `create`, `deployment`, and `deployment_status` events now always receive a read-only token and no secrets. Similarly, workflows triggered by {% data variables.product.prodname_dependabot %} for the `pull_request_target` event on pull requests where the base ref was created by {% data variables.product.prodname_dependabot %}, now always receive a read-only token and no secrets. These changes are designed to prevent potentially malicious code from executing in a privileged workflow. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
|
||||
- Workflow runs on `push` and `pull_request` events triggered by {% data variables.product.prodname_dependabot %} will now respect the permissions specified in your workflows, allowing you to control how you manage automatic dependency updates. The default token permissions will remain read-only. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-06-github-actions-workflows-triggered-by-dependabot-prs-will-respect-permissions-key-in-workflows/)."
|
||||
- '{% data variables.product.prodname_actions %} workflows triggered by {% data variables.product.prodname_dependabot %} will now be sent the {% data variables.product.prodname_dependabot %} secrets. You can now pull from private package registries in your CI using the same secrets you have configured for {% data variables.product.prodname_dependabot %} to use, improving how {% data variables.product.prodname_actions %} and {% data variables.product.prodname_dependabot %} work together. For more information, see "[Automating {% data variables.product.prodname_dependabot %} with {% data variables.product.prodname_actions %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions)."'
|
||||
- You can now manage runner groups and see the status of your self-hosted runners using new Runners and Runner Groups pages in the UI. The Actions settings page for your repository or organization now shows a summary view of your runners, and allows you to deep dive into a specific runner to edit it or see what job it may be currently running. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-20-github-actions-experience-refresh-for-the-management-of-self-hosted-runners/)."
|
||||
- 'Actions authors can now have their action run in Node.js 16 by specifying [`runs.using` as `node16` in the action''s `action.yml`](/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions). This is in addition to the existing Node.js 12 support; actions can continue to specify `runs.using: node12` to use the Node.js 12 runtime.'
|
||||
- 'For manually triggered workflows, {% data variables.product.prodname_actions %} now supports the `choice`, `boolean`, and `environment` input types in addition to the default `string` type. For more information, see "[`on.workflow_dispatch.inputs`](/actions/using-workflows/workflow-syntax-for-github-actions#onworkflow_dispatchinputs)."'
|
||||
- Actions written in YAML, also known as composite actions, now support `if` conditionals. This lets you prevent specific steps from executing unless a condition has been met. Like steps defined in workflows, you can use any supported context and expression to create a conditional.
|
||||
- The search order behavior for self-hosted runners has now changed, so that the first available matching runner at any level will run the job in all cases. This allows jobs to be sent to self-hosted runners much faster, especially for organizations and enterprises with lots of self-hosted runners. Previously, when running a job that required a self-hosted runner, {% data variables.product.prodname_actions %} would look for self-hosted runners in the repository, organization, and enterprise, in that order.
|
||||
- 'Runner labels for {% data variables.product.prodname_actions %} self-hosted runners can now be listed, added and removed using the REST API. For more information about using the new APIs at a repository, organization, or enterprise level, see "[Repositories](/rest/reference/actions#list-labels-for-a-self-hosted-runner-for-a-repository)", "[Organizations](/rest/reference/actions#add-custom-labels-to-a-self-hosted-runner-for-an-organization)", and "[Enterprises](/rest/reference/enterprise-admin#list-labels-for-a-self-hosted-runner-for-an-enterprise)" in the REST API documentation.'
|
||||
-
|
||||
heading: 'Dependabot and Dependency graph changes'
|
||||
notes:
|
||||
- Dependency graph now supports detecting Python dependencies in repositories that use the Poetry package manager. Dependencies will be detected from both `pyproject.toml` and `poetry.lock` manifest files.
|
||||
- When configuring {% data variables.product.prodname_dependabot %} security and version updates on GitHub Enterprise Server, we recommend you also enable {% data variables.product.prodname_dependabot %} in {% data variables.product.prodname_github_connect %}. This will allow {% data variables.product.prodname_dependabot %} to retrieve an updated list of dependencies and vulnerabilities from {% data variables.product.prodname_dotcom_the_website %}, by querying for information such as the changelogs of the public releases of open source code that you depend upon. For more information, see "[Enabling the dependency graph and Dependabot alerts for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
|
||||
- '{% data variables.product.prodname_dependabot_alerts %} alerts can now be dismissed using the GraphQL API. For more information, see the "[dismissRepositoryVulnerabilityAlert](/graphql/reference/mutations#dismissrepositoryvulnerabilityalert)" mutation in the GraphQL API documentation.'
|
||||
-
|
||||
heading: 'Code scanning and secret scanning changes'
|
||||
notes:
|
||||
- The {% data variables.product.prodname_codeql %} CLI now supports including markdown-rendered query help in SARIF files, so that the help text can be viewed in the {% data variables.product.prodname_code_scanning %} UI when the query generates an alert. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-23-display-help-text-for-your-custom-codeql-queries-in-code-scanning/)."
|
||||
- The {% data variables.product.prodname_codeql %} CLI and {% data variables.product.prodname_vscode %} extension now support building databases and analyzing code on machines powered by Apple Silicon, such as Apple M1. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-10-codeql-now-supports-apple-silicon-m1/)."
|
||||
- |
|
||||
The depth of {% data variables.product.prodname_codeql %}'s analysis has been improved by adding support for more [libraries and frameworks](https://codeql.github.com/docs/codeql-overview/supported-languages-and-frameworks/) from the Python ecosystem. As a result, {% data variables.product.prodname_codeql %} can now detect even more potential sources of untrusted user data, steps through which that data flows, and potentially dangerous sinks where the data could end up. This results in an overall improvement of the quality of {% data variables.product.prodname_code_scanning %} alerts. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-11-24-codeql-code-scanning-now-recognizes-more-python-libraries-and-frameworks/)."
|
||||
- Code scanning with {% data variables.product.prodname_codeql %} now includes beta support for analyzing code in all common Ruby versions, up to and including 3.02. For more information, see the "[{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-10-27-codeql-code-scanning-adds-beta-support-for-ruby/)."
|
||||
- |
|
||||
Several improvements have been made to the {% data variables.product.prodname_code_scanning %} API:
|
||||
|
||||
* The `fixed_at` timestamp has been added to alerts. This timestamp is the first time that the alert was not detected in an analysis.
|
||||
* Alert results can now be sorted using `sort` and `direction` on either `created`, `updated` or `number`. For more information, see "[List code scanning alerts for a repository](/rest/reference/code-scanning#list-code-scanning-alerts-for-a-repository)."
|
||||
* A `Last-Modified` header has been added to the alerts and alert endpoint response. For more information, see [`Last-Modified`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Last-Modified) in the Mozilla documentation.
|
||||
* The `relatedLocations` field has been added to the SARIF response when you request a code scanning analysis. The field may contain locations which are not the primary location of the alert. See an example in the [SARIF spec](https://docs.oasis-open.org/sarif/sarif/v2.1.0/cs01/sarif-v2.1.0-cs01.html#_Toc16012616) and for more information see "[Get a code scanning analysis for a repository](/rest/reference/code-scanning#get-a-code-scanning-analysis-for-a-repository)."
|
||||
* Both `help` and `tags` data have been added to the webhook response alert rule object. For more information, see "[Code scanning alert webhooks events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#code_scanning_alert)."
|
||||
* Personal access tokens with the `public_repo` scope now have write access for code scanning endpoints on public repos, if the user has permission.
|
||||
|
||||
For more information, see "[Code scanning](/rest/reference/code-scanning)" in the REST API documentation.
|
||||
- '{% data variables.product.prodname_GH_advanced_security %} customers can now use the REST API to retrieve private repository secret scanning results at the enterprise level. The new endpoint supplements the existing repository-level and organization-level endpoints. For more information, see "[Secret scanning](/rest/reference/secret-scanning)" in the REST API documentation.'
|
||||
#No security/bug fixes for the GA release
|
||||
#security_fixes:
|
||||
#- PLACEHOLDER
|
||||
#bugs:
|
||||
#- PLACEHOLDER
|
||||
known_issues:
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。
|
||||
- Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。
|
||||
- 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。
|
||||
- GitHub Connectで"Users can search GitHub.com"が有効化されている場合、GitHub.comの検索結果にプライベート及びインターナルリポジトリのIssueが含まれません。
|
||||
- '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。'
|
||||
- pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。
|
||||
- Actions services needs to be restarted after restoring appliance from backup taken on a different host.
|
||||
deprecations:
|
||||
-
|
||||
heading: Deprecation of GitHub Enterprise Server 3.0
|
||||
notes:
|
||||
- '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
|
||||
-
|
||||
heading: Deprecation of GitHub Enterprise Server 3.1
|
||||
notes:
|
||||
- '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
|
||||
-
|
||||
heading: XenServer Hypervisorサポートの非推奨化
|
||||
notes:
|
||||
- Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
|
||||
-
|
||||
heading: Deprecation of the Content Attachments API preview
|
||||
notes:
|
||||
- Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
|
||||
-
|
||||
heading: Deprecation of the Codes of Conduct API preview
|
||||
notes:
|
||||
- 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
|
||||
-
|
||||
heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
|
||||
notes:
|
||||
- |
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
|
||||
-
|
||||
heading: Deprecation of the CodeQL runner
|
||||
notes:
|
||||
- The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
|
||||
-
|
||||
heading: Deprecation of custom bit-cache extensions
|
||||
notes:
|
||||
- |
|
||||
Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
|
||||
|
||||
Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.
|
||||
|
||||
Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
|
||||
|
||||
To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
|
||||
backups:
|
||||
- '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
|
||||
@@ -0,0 +1 @@
|
||||
The `GITHUB_TOKEN` expires when a job finishes or after a maximum of 24 hours.
|
||||
@@ -0,0 +1 @@
|
||||
{% data variables.product.company_short %} strongly recommends that you verify any new configuration for authentication in a staging environment. An incorrect configuration could result in downtime for {% data variables.product.product_location %}. 詳しい情報については "[ステージングインスタンスのセットアップ](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)"を参照してください。
|
||||
@@ -0,0 +1,3 @@
|
||||
## キャッシュ
|
||||
|
||||
The cache API allows you to query and manage the {% data variables.product.prodname_actions %} cache for repositories. 詳しい情報については、「[ワークフローを高速化するための依存関係のキャッシュ](/actions/advanced-guides/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)」を参照してください。
|
||||
@@ -1,4 +1,4 @@
|
||||
{% data variables.product.prodname_registry %} APIでは、REST APIを使ってパッケージを管理できます。 パッケージのリストアや削除についてさらに学ぶには、「[パッケージのリストアと削除](/packages/learn-github-packages/deleting-and-restoring-a-package)」を参照してください。
|
||||
The {% data variables.product.prodname_registry %} API enables you to manage packages using the REST API.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} To learn more about restoring or deleting packages, see "[Restoring and deleting packages](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
|
||||
|
||||
このAPIを使うには、個人アクセストークンを使って認証を受けなければなりません。
|
||||
- パッケージメタデータにアクセスするには、トークンに`read:packages`スコープが含まれていなければなりません。
|
||||
|
||||
@@ -103,6 +103,8 @@ products:
|
||||
notes: 注釈
|
||||
parameters: パラメータ
|
||||
response: レスポンス
|
||||
error_codes: Error Codes
|
||||
http_status_code: HTTP Status Code
|
||||
code_sample: コードサンプル
|
||||
code_samples: コードサンプル
|
||||
preview_notice: プレビュー通知
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
---
|
||||
version: enterprise-server@3.4
|
||||
version: ''
|
||||
|
||||
@@ -67,10 +67,12 @@ translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md
|
||||
translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/promoting-or-demoting-a-site-administrator.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise.md,parsing error
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-githubcom.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
|
||||
@@ -222,7 +224,7 @@ translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken
|
||||
translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/rest/reference/enterprise-admin.md,broken liquid tags
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md,broken liquid tags
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,parsing error
|
||||
translations/zh-CN/content/sponsors/getting-started-with-github-sponsors/about-github-sponsors.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/about-github-sponsors-for-open-source-contributors.md,broken liquid tags
|
||||
translations/zh-CN/content/support/contacting-github-support/creating-a-support-ticket.md,broken liquid tags
|
||||
|
||||
|
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Developing a third party CLI action
|
||||
shortTitle: CLI setup action
|
||||
intro: 'Learn how to develop an action to set up a CLI on {% data variables.product.prodname_actions %} runners.'
|
||||
title: 开发第三方 CLI 操作
|
||||
shortTitle: CLI 设置操作
|
||||
intro: '了解如何开发操作以在 {% data variables.product.prodname_actions %} 运行器上设置 CLI。'
|
||||
redirect_from: []
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -13,27 +13,27 @@ topics:
|
||||
|
||||
## 简介
|
||||
|
||||
You can write an action to provide a way for users to access your servers via a configured CLI environment on {% data variables.product.prodname_actions %} runners.
|
||||
您可以编写操作，为用户提供一种通过 {% data variables.product.prodname_actions %} 运行器上配置的 CLI 环境访问服务器的方法。
|
||||
|
||||
Your action should:
|
||||
您的操作应：
|
||||
|
||||
- Make it simple for users to specify the version of the CLI to install
|
||||
- Support multiple operating systems
|
||||
- Run in an efficient fashion to minimize run-time and associated costs
|
||||
- Work across {% data variables.product.product_name %}-hosted and self-hosted runners
|
||||
- Leverage community tooling when possible
|
||||
- 使用户能够轻松指定要安装的 CLI 版本
|
||||
- 支持多种操作系统
|
||||
- 以高效的方式运行，以最大限度地减少运行时间和相关成本
|
||||
- 跨 {% data variables.product.product_name %} 托管和自托管运行器工作
|
||||
- 尽可能利用社区工具
|
||||
|
||||
This article will demonstrate how to write an action that retrieves a specific version of your CLI, installs it, adds it to the path, and (optionally) caches it. This type of action (an action that sets up a tool) is often named `setup-$TOOL`.
|
||||
本文将演示如何编写一个操作来检索特定版本的 CLI、安装它、将其添加到路径以及（可选）缓存它。 这种类型的操作（设置工具的操作）通常命名为 `setup-$TOOL`。
|
||||
|
||||
## 基本要求
|
||||
|
||||
You should have an understanding of how to write a custom action. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions)". For a more detailed guide on how to write a custom action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)."
|
||||
您应该了解如何编写自定义操作。 更多信息请参阅“[关于自定义操作](/actions/creating-actions/about-custom-actions)”。 有关如何编写自定义操作的更详细指南，请参阅“[创建 JavaScript 操作](/actions/creating-actions/creating-a-javascript-action)”。
|
||||
|
||||
## 示例
|
||||
|
||||
The following script demonstrates how you can get a user-specified version as input, download and extract the specific version of your CLI, then add the CLI to the path.
|
||||
以下脚本演示如何获取用户指定的版本作为输入，下载并提取 CLI 的特定版本，然后将 CLI 添加到路径中。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides [`actions/toolkit`](https://github.com/actions/toolkit), which is a set of packages that helps you create actions. This example uses the [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) and [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) packages.
|
||||
{% data variables.product.prodname_dotcom %} 提供了 [`actions/toolkit`](https://github.com/actions/toolkit)，这是一组可帮助您创建操作的包。 此示例使用 [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) 和 [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) 包。
|
||||
|
||||
{% raw %}
|
||||
```javascript{:copy}
|
||||
@@ -58,13 +58,13 @@ module.exports = setup
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
To use this script, replace `getDownloadURL` with a function that downloads your CLI. You will also need to create an actions metadata file (`action.yml`) that accepts a `version` input and that runs this script. For full details about how to create an action, see "[Creating a JavaScript action](/actions/creating-actions/creating-a-javascript-action)."
|
||||
要使用此脚本，请将 `getDownloadURL` 替换为下载 CLI 的函数。 您还需要创建接受 `version` 输入并运行此脚本的操作元数据文件 (`action.yml`)。 有关如何创建操作的完整详细信息，请参阅“[创建 JavaScript 操作](/actions/creating-actions/creating-a-javascript-action)”。
|
||||
|
||||
For a full example of how to set up this action, see [example-setup-gh](https://github.com/github-developer/example-setup-gh).
|
||||
有关如何设置此操作的完整示例，请参阅 [example-setup-gh](https://github.com/github-developer/example-setup-gh)。
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
This pattern is employed in several actions. For more examples, see:
|
||||
此模式用于多个操作。 有关更多示例，请参阅：
|
||||
|
||||
* [`ruby/setup-ruby`](https://github.com/ruby/setup-ruby)
|
||||
* [`google-github-actions/setup-gcloud`](https://github.com/google-github-actions/setup-gcloud)
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Guides for GitHub Actions
|
||||
title: GitHub Actions 指南
|
||||
intro: '{% data variables.product.prodname_actions %} 的这些指南包含具体的使用案例和示例来帮助您配置工作流程。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
layout: product-guides
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 跳过工作流程运行
|
||||
intro: You can skip workflow runs triggered by the `push` and `pull_request` events by including a command in your commit message.
|
||||
intro: 您可以通过在提交消息中包含命令来跳过由 `push` 和 `pull_request` 事件触发的工作流程运行。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -30,4 +30,4 @@ shortTitle: 跳过工作流程运行
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Skip instructions only apply to the workflow run(s) that would be triggered by the commit that contains the skip instructions. You can also disable a workflow from running. 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。
|
||||
跳过指令仅适用于由包含跳过指令的提交触发的工作流程运行。 您还可以禁用工作流程的运行。 更多信息请参阅“[禁用和启用工作流程](/actions/managing-workflow-runs/disabling-and-enabling-a-workflow)。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 工作流程运行通知
|
||||
intro: You can subscribe to notifications about workflow runs that you trigger.
|
||||
intro: 您可以订阅有关触发的工作流程运行的通知。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -23,7 +23,7 @@ shortTitle: 关于配置
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
To get started with {% data variables.product.product_name %}, you first need to deploy {% data variables.product.product_name %}. For more information, see "[Deploying {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae)."
|
||||
要开始使用 {% data variables.product.product_name %}，需要先部署 {% data variables.product.product_name %}。 更多信息请参阅“[部署 {% data variables.product.product_name %}](/admin/configuration/configuring-your-enterprise/deploying-github-ae)”。
|
||||
|
||||
第一次访问您的企业时，您将完成初始配置，以便 {% data variables.product.product_name %} 可供使用。 初始配置包括连接您的企业与身份提供程序 (IdP) 连接、通过 SAML SSO 进行身份验证、配置企业中仓库和组织的策略，以及为出站电子邮件配置 SMTP。 更多信息请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/initializing-github-ae)。”
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enforcing policies for dependency insights in your enterprise
|
||||
intro: 'You can enforce policies for dependency insights within your enterprise''s organizations, or allow policies to be set in each organization.'
|
||||
title: 在企业中实施依赖性见解的策略
|
||||
intro: 您可以在企业组织内执行依赖性见解策略，或允许在每个组织中设置策略。
|
||||
permissions: Enterprise owners can enforce policies for dependency insights in an enterprise.
|
||||
redirect_from:
|
||||
- /articles/enforcing-a-policy-on-dependency-insights
|
||||
@@ -16,19 +16,19 @@ topics:
|
||||
- Enterprise
|
||||
- Organizations
|
||||
- Policies
|
||||
shortTitle: Policies for dependency insights
|
||||
shortTitle: 依赖性见解策略
|
||||
---
|
||||
|
||||
## About policies for dependency insights in your enterprise
|
||||
## 关于企业中的依赖性见解策略
|
||||
|
||||
Dependency insights show all packages that repositories within your enterprise's organizations depend on. Dependency insights include aggregated information about security advisories and licenses. 更多信息请参阅“[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)”。
|
||||
依赖性见解显示企业组织内的存储库所依赖的所有包。 依赖性见解包括有关安全公告和许可的汇总信息。 更多信息请参阅“[查看用于组织的洞见](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)”。
|
||||
|
||||
## Enforcing a policy for visibility of dependency insights
|
||||
## 实施依赖性见解的可见性策略
|
||||
|
||||
Across all organizations owned by your enterprise, you can control whether organization members can view dependency insights. You can also allow owners to administer the setting on the organization level. 更多信息请参阅“[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)”。
|
||||
在企业拥有的所有组织中，您可以控制组织成员是否可以查看依赖性见解。 您还可以允许所有者在组织级别管理设置。 更多信息请参阅“[更改组织依赖项洞察的可见性](/organizations/managing-organization-settings/changing-the-visibility-of-your-organizations-dependency-insights)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
3. In the left sidebar, click **Organizations**. 
|
||||
3. 在左侧栏中，单击，单击 **Organizations（组织）**。 
|
||||
4. 在“Organization policies”（组织政策）下。审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
5. 在“Organization projects”（组织项目）下，使用下拉菜单并选择策略。 
|
||||
|
||||
@@ -27,21 +27,21 @@ shortTitle: GitHub Actions policies
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
|
||||
## 关于企业中 {% data variables.product.prodname_actions %} 的策略
|
||||
## About policies for {% data variables.product.prodname_actions %} in your enterprise
|
||||
|
||||
{% data variables.product.prodname_actions %} helps members of your enterprise automate software development workflows on {% data variables.product.product_name %}. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions)."
|
||||
|
||||
{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. 您可以执行策略来控制 {% data variables.product.product_name %} 上的企业成员如何使用 {% data variables.product.prodname_actions %}。 By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)."
|
||||
{% ifversion ghes %}If you enable {% data variables.product.prodname_actions %}, any{% else %}Any{% endif %} organization on {% data variables.product.product_location %} can use {% data variables.product.prodname_actions %}. You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} use {% data variables.product.prodname_actions %}. By default, organization owners can manage how members use {% data variables.product.prodname_actions %}. For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)."
|
||||
|
||||
## Enforcing a policy to restrict the use of actions in your enterprise
|
||||
|
||||
您可以选择对企业中的所有组织禁用 {% data variables.product.prodname_actions %}，或只允许特定的组织。 您还可以限制公共操作的使用，以使人们只能使用您的企业中存在的本地操作。
|
||||
You can choose to disable {% data variables.product.prodname_actions %} for all organizations in your enterprise, or only allow specific organizations. You can also limit the use of public actions, so that people can only use local actions that exist in your enterprise.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
{% data reusables.actions.enterprise-actions-permissions %}
|
||||
1. 单击 **Save（保存）**。
|
||||
1. Click **Save**.
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
@@ -52,11 +52,11 @@ shortTitle: GitHub Actions policies
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
1. 在 **Policies（策略）**下，选择 **Allow select actions（允许选择操作）**并将所需操作添加到列表中。
|
||||
1. Under **Policies**, select **Allow select actions** and add your required actions to the list.
|
||||
{%- ifversion ghes or ghae-issue-5094 %}
|
||||
|
||||
|
||||
{%- elsif ghae %}
|
||||
|
||||
|
||||
{%- endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -117,14 +117,15 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled
|
||||
|
||||
{% data reusables.actions.workflow-permissions-intro %}
|
||||
|
||||
您可以在企业、组织或仓库的设置中为 `GITHUB_TOKEN` 设置默认权限。 如果您在企业设置中选择受限制的选项为默认值，这将防止在组织或仓库设置中选择更多的允许设置。
|
||||
You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
|
||||
|
||||
{% data reusables.actions.workflow-permissions-modifying %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.actions-tab %}
|
||||
1. 在 **Workflow permissions（工作流程权限）**下，选择您是否想要 `GITHUB_TOKENN` 读写所有范围限， 或者只读`内容`范围。 
|
||||
1. 单击 **Save（保存）**以应用设置。
|
||||
1. Under **Workflow permissions**, choose whether you want the `GITHUB_TOKEN` to have read and write access for all scopes, or just read access for the `contents` scope.
|
||||
|
||||
1. Click **Save** to apply the settings.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enforcing policies for security settings in your enterprise
|
||||
intro: 'You can enforce policies to manage security settings in your enterprise''s organizations, or allow policies to be set in each organization.'
|
||||
title: 为企业中的安全设置实施策略
|
||||
intro: 您可以实施策略来管理企业组织中的安全设置，或允许在每个组织中设置策略。
|
||||
permissions: Enterprise owners can enforce policies for security settings in an enterprise.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -20,28 +20,28 @@ topics:
|
||||
- Enterprise
|
||||
- Policies
|
||||
- Security
|
||||
shortTitle: Policies for security settings
|
||||
shortTitle: 安全设置策略
|
||||
---
|
||||
|
||||
## 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)."
|
||||
您可以在 {% data variables.product.product_name %} 上实施策略以控制企业拥有的组织的安全设置。 默认情况下，组织所有者可以管理安全设置。 更多信息请参阅“[保护组织安全](/organizations/keeping-your-organization-secure)”。
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
|
||||
## Requiring two-factor authentication for organizations in your enterprise
|
||||
## 要求企业中的组织进行双重身份验证
|
||||
|
||||
Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise use two-factor authentication to secure their personal accounts.
|
||||
企业所有者可以要求企业拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。
|
||||
|
||||
Before you can require 2FA for all organizations owned by your enterprise, you must enable two-factor authentication for your own account. 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa/)”。
|
||||
您必须为自己的帐户启用双重身份验证，然后才能对企业拥有的所有组织都要求 2FA。 更多信息请参阅“[使用双重身份验证 (2FA) 保护您的帐户](/articles/securing-your-account-with-two-factor-authentication-2fa/)”。
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**
|
||||
|
||||
- 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. 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以恢复其访问权限和设置。 更多信息请参阅“[恢复组织的前成员](/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 personal 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 personal account without disabling required two-factor authentication for the enterprise.
|
||||
- 当您需要为企业进行双重身份验证时，不使用 2FA 的企业拥有的所有组织中的成员、外部协作者和帐单管理员（包括自动程序帐户）将从组织中删除，并失去对其仓库的访问权限。 他们还会失去对组织私有仓库的复刻的访问权限。 如果他们在从您的组织中删除后的三个月内为其个人帐户启用双重身份验证，您可以恢复其访问权限和设置。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。
|
||||
- 为其个人帐户禁用 2FA 的企业拥有的任何组织中的任何组织所有者、成员、帐单管理员或外部协作者在您启用所需的双重身份验证后将自动从组织中删除。
|
||||
- 如果您是某个要求双重身份验证的企业的唯一所有者，则在不为企业禁用双重身份验证要求的情况下，您将无法为个人帐户禁用 2FA。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -52,22 +52,22 @@ Before you can require 2FA for all organizations owned by your enterprise, you m
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
4. 在“Two-factor authentication（双重身份验证）”下，审查有关更改设置的信息。 {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
|
||||
5. 在“Two-factor authentication（双重身份验证）”下，选择 **Require two-factor authentication for all organizations in your business（对您企业中的所有组织要求双重身份验证）**，然后单击 **Save（保存）**。 
|
||||
6. If prompted, read the information about members and outside collaborators who will be removed from the organizations owned by your enterprise. To confirm the change, type your enterprise's name, then click **Remove members & require two-factor authentication**. 
|
||||
7. Optionally, if any members or outside collaborators are removed from the organizations owned by your enterprise, we recommend sending them an invitation to reinstate their former privileges and access to your organization. 每个人都必须启用双重身份验证，然后才能接受您的邀请。
|
||||
6. 如果出现提示，请阅读有关将从企业所拥有的组织中删除的成员和外部协作者的信息。 要确认更改，请输入企业的名称，然后单击 **Remove members & require two-factor authentication（删除成员并要求双重身份验证）**。 
|
||||
7. （可选）如果从您的企业拥有的组织中删除了任何成员或外部协作者，我们建议向他们发送邀请，以恢复其以前对组织的权限和访问权限。 每个人都必须启用双重身份验证，然后才能接受您的邀请。
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec or ghae %}
|
||||
|
||||
## Managing allowed IP addresses for organizations in your enterprise
|
||||
## 管理企业中组织允许的 IP 地址
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
You can restrict network traffic to your enterprise on {% data variables.product.product_name %}. 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。
|
||||
您可以在 {% data variables.product.product_name %}上限制到企业的网络流量。 更多信息请参阅“[限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)”。
|
||||
|
||||
{% elsif ghec %}
|
||||
|
||||
Enterprise owners can restrict access to private assets owned by organizations in an enterprise by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
企业所有者可以通过为特定 IP 地址配置允许列表，来限制对企业中组织拥有的私有资产的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
|
||||
|
||||
@@ -122,15 +122,15 @@ Enterprise owners can restrict access to private assets owned by organizations i
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Managing SSH certificate authorities for your enterprise
|
||||
## 管理企业的 SSH 认证机构
|
||||
|
||||
You can use a SSH certificate authorities (CA) to allow members of any organization owned by your enterprise to access that organization's repositories using SSH certificates you provide. {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。
|
||||
您可以使用 SSH 认证机构 (CA) 来允许企业拥有的任何组织的成员使用您提供的 SSH 证书访问该组织的存储库。 {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)”。
|
||||
|
||||
{% data reusables.organizations.add-extension-to-cert %}
|
||||
|
||||
### 添加 SSH 认证中心
|
||||
|
||||
If you require SSH certificates for your enterprise, enterprise members should use a special URL for Git operations over SSH. 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。
|
||||
如果您的企业需要 SSH 证书，企业成员应使用特殊的 URL 通过 SSH 进行 Git 操作。 更多信息请参阅“[关于 SSH 认证中心](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities#about-ssh-urls-with-ssh-certificates)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
@@ -150,6 +150,6 @@ If you require SSH certificates for your enterprise, enterprise members should u
|
||||
{% ifversion ghec or ghae %}
|
||||
## 延伸阅读
|
||||
|
||||
- "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
|
||||
- "[Accessing compliance reports for your enterprise](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
|
||||
- "[关于企业的身份和访问权限管理](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)"{% ifversion ghec %}
|
||||
- "[访问企业的合规性报告](/admin/overview/accessing-compliance-reports-for-your-enterprise)"{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enforcing project board policies in your enterprise
|
||||
intro: 'You can enforce policies for projects within your enterprise''s organizations, or allow policies to be set in each organization.'
|
||||
title: 在企业中实施项目板策略
|
||||
intro: 您可以在企业组织内执行项目策略，或允许在每个组织中设置策略。
|
||||
permissions: Enterprise owners can enforce policies for project boards in an enterprise.
|
||||
redirect_from:
|
||||
- /articles/enforcing-project-board-settings-for-organizations-in-your-business-account
|
||||
@@ -18,16 +18,16 @@ topics:
|
||||
- Enterprise
|
||||
- Policies
|
||||
- Projects
|
||||
shortTitle: Project board policies
|
||||
shortTitle: 项目板策略
|
||||
---
|
||||
|
||||
## About policies for project boards in your enterprise
|
||||
## 关于企业中项目板的策略
|
||||
|
||||
You can enforce policies to control how members of your enterprise on {% data variables.product.product_name %} manage project boards. You can also allow organization owners to manage policies for project boards. 更多信息请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。
|
||||
您可以执行策略来控制企业在 {% data variables.product.product_name %} 上的企业成员如何管理项目板。 您也可以允许组织所有者管理项目板策略。 更多信息请参阅“[关于项目板](/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards)”。
|
||||
|
||||
## 实施组织范围项目板的策略
|
||||
|
||||
Across all organizations owned by your enterprise, you can enable or disable organization-wide project boards, or allow owners to administer the setting on the organization level.
|
||||
在企业拥有的所有组织中，可以启用或禁用组织范围的项目板，或允许所有者在组织级别管理设置。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
@@ -37,7 +37,7 @@ Across all organizations owned by your enterprise, you can enable or disable org
|
||||
|
||||
## 实施仓库项目板的策略
|
||||
|
||||
Across all organizations owned by your enterprise, you can enable or disable repository-level project boards, or allow owners to administer the setting on the organization level.
|
||||
在企业拥有的所有组织中，可以启用或禁用仓库级项目板，或允许所有者在组织级别管理设置。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Adding organizations to your enterprise
|
||||
intro: You can create new organizations or invite existing organizations to manage within your enterprise.
|
||||
title: 将组织添加到企业
|
||||
intro: 您可以创建新的组织或邀请现有组织来管理您的企业。
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/adding-organizations-to-your-enterprise-account
|
||||
- /articles/adding-organizations-to-your-enterprise-account
|
||||
@@ -18,17 +18,17 @@ shortTitle: 添加组织
|
||||
|
||||
## 关于组织
|
||||
|
||||
Your enterprise account can own organizations. Members of your enterprise can collaborate across related projects within an organization. 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
|
||||
您的企业帐户可以拥有组织。 企业成员可以跨组织内的相关项目进行协作。 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
|
||||
|
||||
Enterprise owners can create new organizations within an enterprise account's settings or invite existing organizations to join an enterprise. To add an organization to your enterprise, you must create the organization from within the enterprise account settings.
|
||||
企业所有者可以在企业帐户设置内创建新组织，或邀请现有组织加入企业。 要将组织添加到企业，必须在企业帐户设置中创建组织。
|
||||
|
||||
You can only add organizations this way to an existing enterprise account. {% data reusables.enterprise.create-an-enterprise-account %} For more information, see "[Creating an enterprise account](/admin/overview/creating-an-enterprise-account)."
|
||||
您只能以这种方式将组织添加到现有企业帐户。 {% data reusables.enterprise.create-an-enterprise-account %} 更多信息请参阅“[创建企业帐户](/admin/overview/creating-an-enterprise-account)”。
|
||||
|
||||
## 在企业帐户中创建组织
|
||||
|
||||
在企业帐户设置中创建的新组织包含在企业帐户的 {% data variables.product.prodname_ghe_cloud %} 订阅中。
|
||||
|
||||
创建企业帐户所拥有的组织的企业所有者自动成为组织所有者。 For more information about organization owners, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
创建企业帐户所拥有的组织的企业所有者自动成为组织所有者。 有关组织所有者的更多信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **New organization（新组织）**。 
|
||||
@@ -39,12 +39,12 @@ You can only add organizations this way to an existing enterprise account. {% da
|
||||
|
||||
## 邀请组织加入您的企业帐户
|
||||
|
||||
企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有，则在上一个企业放弃对组织的所有权之前，您将无法发出邀请。 For more information, see "[Removing an organization from your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)."
|
||||
企业所有者可以邀请现有组织加入其企业帐户。 如果您要邀请的组织已经归其他企业所有，则在上一个企业放弃对组织的所有权之前，您将无法发出邀请。 更多信息请参阅“[从企业中删除组织](/admin/user-management/managing-organizations-in-your-enterprise/removing-organizations-from-your-enterprise)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
2. 在 **Organizations（组织）**选项卡中的组织列表上方，单击 **Invite organization（邀请组织）**。 
|
||||
3. 在“Organization name（组织名称）”下，开始键入要邀请的组织名称，并在它出现在下拉列表中时选择它。 
|
||||
4. 单击 **Invite organization（邀请组织）**。
|
||||
5. The organization owners will receive an email inviting them to join the enterprise. 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 
|
||||
5. 组织所有者将收到一封邀请他们加入企业的电子邮件。 至少有一个所有者接受邀请才能继续该过程。 您可以在所有者批准邀请之前随时取消或重新发送邀请。 
|
||||
6. 一旦组织所有者批准了邀请，您可以在待定邀请列表中查看其状态。 
|
||||
7. 点击 **Approve（批准）**完成传输，或点击 **Cancel（取消）**予以取消。 
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Managing unowned organizations in your enterprise
|
||||
title: 管理企业中没有所有者的组织
|
||||
intro: 您可以成为企业帐户中目前没有所有者的组织的所有者。
|
||||
permissions: Enterprise owners can manage unowned organizations in an enterprise account.
|
||||
redirect_from:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Streaming the audit logs for organizations in your enterprise account
|
||||
intro: 'You can stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system.'
|
||||
title: 流式传输企业帐户中组织的审核日志
|
||||
intro: '您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
ghec: '*'
|
||||
@@ -10,43 +10,43 @@ topics:
|
||||
- Enterprise
|
||||
- Logging
|
||||
- Organizations
|
||||
shortTitle: Stream organization audit logs
|
||||
shortTitle: 流式传输组织审核日志
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
permissions: Enterprise owners can configure audit log streaming.
|
||||
---
|
||||
|
||||
## About exporting audit data
|
||||
## 关于导出审核数据
|
||||
|
||||
You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways:
|
||||
您可以通过多种方式从 {% data variables.product.prodname_dotcom %} 中提取审核日志和 Git 事件数据：
|
||||
|
||||
* Go to the Audit log page in {% data variables.product.prodname_dotcom %} and click **Export**. For more information, see "[Viewing the audit logs for organizations in your enterprise account](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)" and "[Exporting the audit log](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)."
|
||||
* Use the API to poll for new audit log events. For more information, see "[Using the audit log API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)."
|
||||
* Set up {% data variables.product.product_name %} to stream audit data as events are logged.
|
||||
* 转到 {% data variables.product.prodname_dotcom %} 中的审核日志页，然后单击 **Export（导出）**。 更多信息请参阅“[查看企业帐户中组织的审核日志](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)”和“[导出审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)”。
|
||||
* 使用 API 轮询新的审核日志事件。 更多信息请参阅“[使用审核日志 API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)”。
|
||||
* 设置 {% data variables.product.product_name %} 以在记录事件时流式传输审核数据。
|
||||
|
||||
Currently, audit log streaming is supported for multiple storage providers.
|
||||
目前，多个存储提供商支持审核日志流式处理。
|
||||
- Amazon S3
|
||||
- Azure Blob Storage
|
||||
- Azure Event Hubs
|
||||
- Google Cloud Storage
|
||||
- Splunk
|
||||
|
||||
## About audit log streaming
|
||||
## 关于审核日志流
|
||||
|
||||
To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
|
||||
为了帮助保护您的知识产权并保持组织的合规性，您可以使用流式处理来保留审核日志数据的副本并监控：
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
The benefits of streaming audit data include:
|
||||
流式传输审计数据的好处包括：
|
||||
|
||||
* **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.
|
||||
* **Data continuity**. You can pause the stream for up to seven days without losing any audit data.
|
||||
* **Data retention**. You can keep your exported audit logs and Git data as long as you need to.
|
||||
* **数据探索**。 您可以使用首选工具检查流事件，以查询大量数据。 流包含整个企业帐户中的审核事件和 Git 事件。
|
||||
* **数据连续性**。 您可以暂停流长达七天，而不会丢失任何审核数据。
|
||||
* **数据保留**。 您可以根据需要保留导出的审核日志和 Git 数据。
|
||||
|
||||
Enterprise owners can set up, pause, or delete a stream at any time. The stream exports the audit data for all of the organizations in your enterprise.
|
||||
企业所有者可以随时设置、暂停或删除流。 流导出企业中所有组织的审核数据。
|
||||
|
||||
## Setting up audit log streaming
|
||||
## 设置审核日志流
|
||||
|
||||
You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
|
||||
您可以按照提供程序的说明在 {% data variables.product.product_name %} 上设置审核日志流。
|
||||
|
||||
- [Amazon S3](#setting-up-streaming-to-amazon-s3)
|
||||
- [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage)
|
||||
@@ -54,192 +54,192 @@ You set up the audit log stream on {% data variables.product.product_name %} by
|
||||
- [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
|
||||
- [Splunk](#setting-up-streaming-to-splunk)
|
||||
|
||||
### Setting up streaming to Amazon S3
|
||||
### 设置流式传输到 Amazon S3
|
||||
|
||||
To stream audit logs to Amazon's S3 endpoint, you must have a bucket and access keys. For more information, see [Creating, configuring, and working with Amazon S3 buckets](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html) in the the AWS documentation. Make sure to block public access to the bucket to protect your audit log information.
|
||||
要将审核日志流式传输到 Amazon 的 S3 终端节点，您必须拥有存储桶和访问密钥。 更多信息请参阅 AWS 文档中的[创建、配置和使用 Amazon S3 存储桶](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-buckets-s3.html)。 请务必阻止对存储桶的公共访问，以保护您的审核日志信息。
|
||||
|
||||
To set up audit log streaming from {% data variables.product.prodname_dotcom %} you will need:
|
||||
* The name of your Amazon S3 bucket
|
||||
* Your AWS access key ID
|
||||
* Your AWS secret key
|
||||
要设置来自 {% data variables.product.prodname_dotcom %} 审核日志流式处理，您需要：
|
||||
* Amazon S3 存储桶的名称
|
||||
* AWS 访问密钥 ID
|
||||
* AWS 密钥
|
||||
|
||||
For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
|
||||
有关创建或访问访问密钥 ID 和密钥的信息，请参阅 AWS 文档中的[了解和获取您的 AWS 凭据](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html)。
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Amazon S3**.
|
||||
1. 单击 **Configure stream（配置流）**，然后选择 **Amazon S3**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the configuration page, enter:
|
||||
* The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
|
||||
* Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
|
||||
* Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
|
||||
1. 在配置页面上，输入：
|
||||
* 要流式传输到的存储桶的名称。 例如，`auditlog-streaming-test`。
|
||||
* 您的访问密钥 ID。 例如，`ABCAIOSFODNN7EXAMPLE1`。
|
||||
* 您的密钥。 例如，`aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Amazon S3 endpoint.
|
||||
1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Amazon S3 端点。
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Setting up streaming to Azure Blob Storage
|
||||
### 设置流式传输到 Azure Blob Storage
|
||||
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)."
|
||||
在 {% data variables.product.prodname_dotcom %} 中设置流之前，必须先在 Microsoft Azure 中创建存储帐户和容器。 有关详细信息，请参阅 Microsoft 文档中的“[Azure Blob Storage 简介](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)”。
|
||||
|
||||
To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
|
||||
要在 {% data variables.product.prodname_dotcom %} 配置流，需要 SAS 令牌的 URL。
|
||||
|
||||
**On Microsoft Azure portal**:
|
||||
1. On the Home page, click **Storage Accounts**.
|
||||
2. Click the name of the storage account you want to use, then click **Containers**.
|
||||
**在 Microsoft Azure 门户中**：
|
||||
1. 在主页上，单击 **Storage Accounts（存储帐户）**。
|
||||
2. 单击要使用的存储帐户的名称，然后单击 **Containers（容器）**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click the name of the container you want to use.
|
||||
1. Click **Shared access tokens**.
|
||||
1. 单击要使用的容器的名称。
|
||||
1. 单击 **Shared access tokens（共享访问令牌）**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
|
||||
1. 在 **Permissions（权限）**下拉菜单中，将权限更改为仅允许`创建`和`写入`。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Set an expiry date that complies with your secret rotation policy.
|
||||
1. Click **Generate SAS token and URL**.
|
||||
1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
|
||||
1. 设置符合机密轮换策略的到期日期。
|
||||
1. 单击 **Generate SAS token and URL（生成 SAS 令牌和 URL）**。
|
||||
1. 复制显示的 **Blob SAS URL** 字段的值。 您将在 {% data variables.product.prodname_dotcom %} 中使用此 URL。
|
||||
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
**在 {% data variables.product.prodname_dotcom %} 上**：
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Blob Storage**.
|
||||
1. 单击 **Configure stream（配置流）**，然后选择 **Azure Blob Storage**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
|
||||
1. 在配置页上，输入在 Azure 中复制的 blob SAS URL。 **Container（容器）**字段将根据 URL 自动填充。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
|
||||
1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Azure Blob Storage 端点。
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Setting up streaming to Azure Event Hubs
|
||||
### 设置流式传输到 Azure Event Hub
|
||||
|
||||
Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have an event hub namespace in Microsoft Azure. Next, you must create an event hub instance within the namespace. You'll need the details of this event hub instance when you set up the stream. For details, see the Microsoft documentation, "[Quickstart: Create an event hub using Azure portal](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)."
|
||||
在 {% data variables.product.prodname_dotcom %} 中设置流之前，必须先在 Microsoft Azure 中具有事件中心命名空间。 接下来，必须在命名空间中创建事件中心实例。 设置流时，需要此事件中心实例的详细信息。 有关详细信息，请参阅 Microsoft 文档“[快速入门：使用 Azure 门户创建事件中心](https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-create)”。
|
||||
|
||||
You need two pieces of information about your event hub: its instance name and the connection string.
|
||||
需要有关事件中心的两条信息：其实例名称和连接字符串。
|
||||
|
||||
**On Microsoft Azure portal**:
|
||||
1. Search for "Event Hubs".
|
||||
**在 Microsoft Azure 门户中**：
|
||||
1. 搜索“事件中心”。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Select **Event Hubs**. The names of your event hubs are listed.
|
||||
1. 选择 **Event Hubs（事件中心）**。 将列出事件中心的名称。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Make a note of the name of the event hub you want to stream to.
|
||||
1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
|
||||
1. Select a shared access policy in the list of policies, or create a new policy.
|
||||
1. 记下要流式传输到的事件中心的名称。
|
||||
1. 单击所需的事件中心。 然后，在左侧菜单中，选择 **Shared Access Policies（共享访问策略）**。
|
||||
1. 在策略列表中选择共享访问策略，或创建新策略。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
|
||||
1. 单击 **Connection string-primary key（连接字符串 - 主键）**字段右侧的按钮以复制连接字符串。
|
||||
|
||||
|
||||
|
||||
|
||||
**On {% data variables.product.prodname_dotcom %}**:
|
||||
**在 {% data variables.product.prodname_dotcom %} 上**：
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Azure Event Hubs**.
|
||||
1. 单击 **Configure stream（配置流）**，然后选择 **Azure Event Hubs**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the configuration page, enter:
|
||||
* The name of the Azure Event Hubs instance.
|
||||
* The connection string.
|
||||
1. 在配置页面上，输入：
|
||||
* Azure Event Hubs 实例的名称。
|
||||
* 连接字符串。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
|
||||
1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Azure Event Hubs 端点。
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Setting up streaming to Google Cloud Storage
|
||||
### 设置流式传输到 Google Cloud Storage
|
||||
|
||||
To set up streaming to Google Cloud Storage, you must create a service account in Google Cloud with the appropriate credentials and permissions, then configure audit log streaming in {% data variables.product.product_name %} using the service account's credentials for authentication.
|
||||
要设置流式传输到 Google Cloud Storage，您必须在 Google Cloud 中使用适当的凭据和权限创建一个服务帐户，然后使用服务帐户的凭据在 {% data variables.product.product_name %} 中配置审核日志流以进行身份验证。
|
||||
|
||||
1. Create a service account for Google Cloud. You do not need to set access controls or IAM roles for the service account. For more information, see [Creating and managing service accounts](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating) in the Google Cloud documentation.
|
||||
1. Create a JSON key for the service account, and store the key securely. For more information, see [Creating and managing service account keys](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating) in the Google Cloud documentation.
|
||||
1. If you haven't created a bucket yet, create the bucket. For more information, see [Creating storage buckets](https://cloud.google.com/storage/docs/creating-buckets) in the Google Cloud documentation.
|
||||
1. Give the service account the Storage Object Creator role for the bucket. For more information, see [Using Cloud IAM permissions](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add) in the Google Cloud documentation.
|
||||
1. 为 Google Cloud 创建一个服务帐户。 您无需为服务帐户设置访问控制或 IAM 角色。 更多信息请参阅 Google Cloud 文档中的[创建和管理服务帐户](https://cloud.google.com/iam/docs/creating-managing-service-accounts#creating)。
|
||||
1. 创建服务帐户的 JSON 密钥，并安全地存储该密钥。 更多信息请参阅 Google Cloud 文档中的[创建和管理服务帐户密钥](https://cloud.google.com/iam/docs/creating-managing-service-account-keys#creating)。
|
||||
1. 如果您尚未创建存储桶，请创建存储桶。 更多信息请参阅 Google Cloud 文档中的[创建存储桶](https://cloud.google.com/storage/docs/creating-buckets)。
|
||||
1. 为服务帐户分配存储桶的存储对象创建者角色。 更多信息请参阅 Google Cloud 文档中和[使用 Cloud IAM 权限](https://cloud.google.com/storage/docs/access-control/using-iam-permissions#bucket-add)。
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Select the Configure stream drop-down menu and click **Google Cloud Storage**.
|
||||
1. 选择配置流下拉菜单，然后单击 **Google Cloud Storage**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under "Bucket", type the name of your Google Cloud Storage bucket.
|
||||
1. 在“Bucket（存储桶）”下，键入 Google Cloud Storage 存储桶的名称。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under "JSON Credentials", paste the entire contents of the file for your service account's JSON key.
|
||||
1. 在“JSON Credentials（JSON 凭据）”下，粘贴服务帐户的 JSON 密钥文件的全部内容。
|
||||
|
||||
|
||||
|
||||
|
||||
1. To verify that {% data variables.product.prodname_dotcom %} can connect and write to the Google Cloud Storage bucket, click **Check endpoint**.
|
||||
1. 要验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Google Cloud Storage 存储桶，请单击 **Check endpoint（检查端点）**。
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
### Setting up streaming to Splunk
|
||||
### 设置流式传输到 Splunk
|
||||
|
||||
To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
|
||||
要将审核日志流式传输到 Splunk 的 HTTP 事件收集器 (HEC) 端点，必须确保将终端节点配置为接受 HTTPS 连接。 更多信息请参阅 Splunk 文档中的[在 Splunk Web 中设置和使用 HTTP 事件收集器](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector)。
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Configure stream** and select **Splunk**.
|
||||
1. 单击 **Configure stream（配置流）**，然后选择 **Splunk**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the configuration page, enter:
|
||||
* The domain on which the application you want to stream to is hosted.
|
||||
1. 在配置页面上，输入：
|
||||
* 要流式传输到的应用程序所在的域。
|
||||
|
||||
If you are using Splunk Cloud, `Domain` should be `http-inputs-<host>`, where `host` is the domain you use in Splunk Cloud. 例如：`http-inputs-mycompany.splunkcloud.com`。
|
||||
如果您使用的是 Splunk Cloud，`Domain` 应为 `http-inputs-<host>`，其中 `host` 是您在 Splunk Cloud 中使用的域。 例如：`http-inputs-mycompany.splunkcloud.com`。
|
||||
|
||||
* The port on which the application accepts data.<br>
|
||||
* 应用程序接受数据的端口。<br>
|
||||
|
||||
If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
|
||||
如果您使用的是 Splunk Cloud，`Port` 应为 `443`（如果您尚未更改端口配置）。 如果您使用的是 Splunk Cloud 的免费试用版，`Port` 应为 `8088`。
|
||||
|
||||
* A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
|
||||
* {% data variables.product.prodname_dotcom %} 可用来验证第三方应用程序的令牌。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Leave the **Enable SSL verification** check box selected.
|
||||
1. 选中 **Enable SSL verification（启用 SSL 验证）**复选框。
|
||||
|
||||
Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
|
||||
1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. 
|
||||
审核日志始终作为加密数据进行流式传输，但是，如果选择此选项， {% data variables.product.prodname_dotcom %} 在传递事件时会验证 Splunk 实例的 SSL 证书。 SSL 验证有助于确保将事件安全地传递到 URL 端点。 您可以清除此选项的选择，但我们建议您将 SSL 验证保留为启用状态。
|
||||
1. 单击 **Check endpoint（检查端点）**以验证 {% data variables.product.prodname_dotcom %} 是否可以连接并写入 Splunk 端点。 
|
||||
{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
|
||||
|
||||
## Pausing audit log streaming
|
||||
## 暂停审核日志流
|
||||
|
||||
Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
|
||||
暂停流允许您对接收应用程序执行维护，而不会丢失审核数据。 审核日志在 {% data variables.product.product_location %} 上最多存储七天，然后在取消暂停流时导出。
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Pause stream**.
|
||||
1. 单击 **Pause stream（暂停流）**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. A confirmation message is displayed. Click **Pause stream** to confirm.
|
||||
1. 将显示一条确认消息。 单击 **Pause stream（暂停流）**以确认。
|
||||
|
||||
When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
|
||||
当应用程序准备好再次接收审核日志时，单击 **Resume stream（恢复流）**以重新启动流式处理审核日志。
|
||||
|
||||
## Deleting the audit log stream
|
||||
## 删除审核日志流
|
||||
|
||||
{% data reusables.enterprise.navigate-to-log-streaming-tab %}
|
||||
1. Click **Delete stream**.
|
||||
1. 单击 **Delete stream（删除流）**。
|
||||
|
||||
|
||||
|
||||
|
||||
1. A confirmation message is displayed. Click **Delete stream** to confirm.
|
||||
1. 将显示一条确认消息。 单击 **Delete stream（删除流）**以确认。
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Viewing the audit logs for organizations in your enterprise
|
||||
title: 查看企业中组织的审核日志
|
||||
intro: 企业所有者可以在其审核日志中查看企业帐户拥有的所有组织的汇总操作。
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
|
||||
@@ -29,7 +29,7 @@ shortTitle: 查看组织审核日志
|
||||
|
||||
您可以在审核日志中搜索特定事件并导出审核日志数据。 有关搜索审核日志和特定组织事件的更多信息，请参阅“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)”。
|
||||
|
||||
You can also stream audit and Git events data from {% data variables.product.prodname_dotcom %} to an external data management system. For more information, see "[Streaming the audit logs for organizations in your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."
|
||||
您还可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 更多信息请参阅“[流式传输企业帐户中组织的审核日志](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)”。
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
|
||||
@@ -43,7 +43,7 @@ shortTitle: 邀请人员进行管理
|
||||
|
||||
## {% ifversion ghec %}邀请{% elsif ghes %}添加{% endif %} 企业管理员到您的企业帐户
|
||||
|
||||
{% ifversion ghec %}在邀请别人加入企业帐户后，他们必须接受电子邮件邀请，然后才可访问企业帐户。 Pending invitations will expire after 7 days.{% endif %}
|
||||
{% ifversion ghec %}在邀请别人加入企业帐户后，他们必须接受电子邮件邀请，然后才可访问企业帐户。 待处理的邀请将在 7 天后过期。{% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
@@ -66,10 +66,10 @@ shortTitle: 邀请人员进行管理
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
{% data reusables.enterprise-accounts.administrators-tab %}
|
||||
1. Next to the username of the person you'd like to remove, click {% octicon "gear" aria-label="The Settings gear" %}, then click {% ifversion ghes %}**Remove owner**{% elsif ghec %}**Convert to member**{% endif %}.
|
||||
1. 在您要删除的人员用户名旁边，单击 {% octicon "gear" aria-label="The Settings gear" %}，然后单击 {% ifversion ghes %}**Remove owner（删除所有者）**{% elsif ghec %}**Convert to member（转换为成员）**{% endif %}。
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
{% endif %}
|
||||
1. Read the confirmation, then click {% ifversion ghes %}**Remove owner**{% elsif ghec %}**Yes, convert USERNAME to member**{% endif %}.
|
||||
1. 阅读确认信息，然后单击 {% ifversion ghes %}**Remove owner（删除所有者）**{% elsif ghec %}**Yes, convert USERNAME to member（是，将 [用户名] 转换为成员）**{% endif %}。
|
||||
|
||||
@@ -15,7 +15,7 @@ shortTitle: 管理支持权利
|
||||
|
||||
拥有企业帐户支持权限的人员可以使用支持门户打开、查看和评论与企业帐户相关的支持事件单。
|
||||
|
||||
企业所有人和帐单管理员自动拥有支持权利。 Enterprise owners can add support entitlements to up to 20 additional members of organizations owned by their enterprise account.
|
||||
企业所有人和帐单管理员自动拥有支持权利。 企业所有者可以向企业帐户拥有的最多 20 个额外组织成员添加支持权利。
|
||||
|
||||
## 向企业成员添加支持权利
|
||||
|
||||
@@ -28,8 +28,8 @@ shortTitle: 管理支持权利
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
3. 在“Settings（设置）”下，单击 **Support（支持）**。 
|
||||
4. 在“Add support member（添加支持成员）”下，开始键入要提供支持权利的人员的名称或用户名。 在匹配列表中单击其名称。 
|
||||
5. 单击 **Add support entitlement（添加支持权利）**。 
|
||||
4. 在“Add support member（添加支持成员）”下，开始键入要提供支持权利的人员的名称或用户名。 在匹配列表中单击其名称。 
|
||||
5. 单击 **Add support entitlement（添加支持权利）**。 
|
||||
|
||||
## 从企业成员删除支持权利
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 企业中的角色
|
||||
intro: 企业中的每个人都是企业的成员。 要控制对企业的设置和数据的访问权限，您可以为企业成员分配不同的角色。
|
||||
title: Roles in an enterprise
|
||||
intro: 'Everyone in an enterprise is a member of the enterprise. To control access to your enterprise''s settings and data, you can assign different roles to members of your enterprise.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise
|
||||
- /github/setting-up-and-managing-your-enterprise-account/roles-for-an-enterprise-account
|
||||
@@ -15,68 +15,68 @@ topics:
|
||||
- Enterprise
|
||||
---
|
||||
|
||||
## 关于企业中的角色
|
||||
## About roles in an enterprise
|
||||
|
||||
企业中的每个人都是企业的成员。 您还可以为企业成员分配管理角色。 每个管理员角色都映射到业务职能，并提供在企业中执行特定任务的权限。
|
||||
Everyone in an enterprise is a member of the enterprise. You can also assign administrative roles to members of your enterprise. Each administrator role maps to business functions and provides permissions to do specific tasks within the enterprise.
|
||||
|
||||
{% data reusables.enterprise-accounts.enterprise-administrators %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
如果您的企业没有使用 {% data variables.product.prodname_emus %}，您可以邀请他人使用他们控制的 {% data variables.product.product_name %} 用户帐户来管理角色。 For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
If your enterprise does not use {% data variables.product.prodname_emus %}, you can invite someone to an administrative role using a user account on {% data variables.product.product_name %} that they control. For more information, see "[Inviting people to manage your enterprise](/github/setting-up-and-managing-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
在使用 {% data variables.product.prodname_emus %} 的企业中，必须通过身份提供商预配新所有者和成员。 企业所有者和组织所有者不能使用 {% data variables.product.prodname_dotcom %} 向企业添加新成员或所有者。 您可以使用 IdP 选择成员的企业角色，它不能在 {% data variables.product.prodname_dotcom %} 上更改。 您可以在 {% data variables.product.prodname_dotcom %} 上选择成员在组织中的角色。 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
|
||||
In an enterprise using {% data variables.product.prodname_emus %}, new owners and members must be provisioned through your identity provider. Enterprise owners and organization owners cannot add new members or owners to the enterprise using {% data variables.product.prodname_dotcom %}. You can select a member's enterprise role using your IdP and it cannot be changed on {% data variables.product.prodname_dotcom %}. You can select a member's role in an organization on {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
|
||||
{% else %}
|
||||
有关向企业添加人员的更多信息，请参阅“[身份验证](/admin/authentication)”。
|
||||
For more information about adding people to your enterprise, see "[Authentication](/admin/authentication)".
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Enterprise owners
|
||||
|
||||
企业所有者可以完全控制企业，并可以采取所有操作，包括：
|
||||
- 管理管理员
|
||||
Enterprise owners have complete control over the enterprise and can take every action, including:
|
||||
- Managing administrators
|
||||
- {% ifversion ghec %}Adding and removing {% elsif ghae or ghes %}Managing{% endif %} organizations {% ifversion ghec %}to and from {% elsif ghae or ghes %} in{% endif %} the enterprise{% if remove-enterprise-members %}
|
||||
- Removing enterprise members from all organizations owned by the enterprise{% endif %}
|
||||
- 管理企业设置
|
||||
- 在组织范围内强制实施政策
|
||||
{% ifversion ghec %}- 管理帐单设置{% endif %}
|
||||
- Managing enterprise settings
|
||||
- Enforcing policy across organizations
|
||||
{% ifversion ghec %}- Managing billing settings{% endif %}
|
||||
|
||||
{% if enterprise-owner-join-org %}
|
||||
Enterprise owners do not have access to organization settings or content by default. To gain access, enterprise owners can join any organization owned by their enterprise. For more information, see "[Managing your role in an organization owned by your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise)."
|
||||
|
||||
Owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
|
||||
{% else %}
|
||||
企业所有者无法访问组织设置或内容，除非将其设为组织所有者或授予直接访问组织所拥有仓库的权限。 同样，除非您将其设为企业所有者，否则企业中的组织所有者无权访问企业。
|
||||
Enterprise owners cannot access organization settings or content unless they are made an organization owner or given direct access to an organization-owned repository. Similarly, owners of organizations in your enterprise do not have access to the enterprise itself unless you make them enterprise owners.
|
||||
{% endif %}
|
||||
|
||||
企业所有者仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}企业所有者必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。{% endif %} 作为最佳实践，我们建议只将少数人设为公司的企业所有者，以降低业务风险。
|
||||
An enterprise owner will only consume a license if they are an owner or member of at least one organization within the enterprise. Even if an enterprise owner has a role in multiple organizations, they will consume a single license. {% ifversion ghec %}Enterprise owners must have a personal account on {% data variables.product.prodname_dotcom %}.{% endif %} As a best practice, we recommend making only a few people in your company enterprise owners, to reduce the risk to your business.
|
||||
|
||||
## 企业成员
|
||||
## Enterprise members
|
||||
|
||||
您的企业所拥有组织的成员也会自动成为企业的成员。 成员可以在组织中进行协作，也可以是组织所有者，但成员无法访问或配置企业设置{% ifversion ghec %}，包括计费设置{% endif %}。
|
||||
Members of organizations owned by your enterprise are also automatically members of the enterprise. Members can collaborate in organizations and may be organization owners, but members cannot access or configure enterprise settings{% ifversion ghec %}, including billing settings{% endif %}.
|
||||
|
||||
企业中的人员可能对您的企业拥有的各种组织以及这些组织中的仓库具有不同级别的访问权限。 您可以查看每个人具有访问权限的资源。 更多信息请参阅“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)”。
|
||||
People in your enterprise may have different levels of access to the various organizations owned by your enterprise and to repositories within those organizations. You can view the resources that each person has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
|
||||
|
||||
For more information about organization-level permissions, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
对组织所拥有仓库具有外部协作者访问权限的人员也会在企业的 People（人员）选项卡中列出，但他们不是企业成员，也没有对企业的任何访问权限。 For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
People with outside collaborator access to repositories owned by your organization are also listed in your enterprise's People tab, but are not enterprise members and do not have any access to the enterprise. For more information about outside collaborators, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## 帐单管理员
|
||||
## Billing managers
|
||||
|
||||
帐单管理员只能访问企业的帐单设置。 企业的帐单管理员可以：
|
||||
- 查看和管理用户许可证、{% data variables.large_files.product_name_short %} 包以及其他计费设置
|
||||
- 查看帐单管理员列表
|
||||
- 添加或删除其他帐单管理员
|
||||
Billing managers only have access to your enterprise's billing settings. Billing managers for your enterprise can:
|
||||
- View and manage user licenses, {% data variables.large_files.product_name_short %} packs and other billing settings
|
||||
- View a list of billing managers
|
||||
- Add or remove other billing managers
|
||||
|
||||
帐单管理员仅在他们是企业中至少一个组织的所有者或成员时才可使用许可证。 帐单管理员无权访问企业中的组织或仓库，也无法添加或删除企业所有者。 帐单管理员必须在 {% data variables.product.prodname_dotcom %} 上拥有个人帐户。
|
||||
Billing managers will only consume a license if they are an owner or member of at least one organization within the enterprise. Billing managers do not have access to organizations or repositories in your enterprise, and cannot add or remove enterprise owners. Billing managers must have a personal account on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
## 关于支持权利
|
||||
## About support entitlements
|
||||
|
||||
{% data reusables.enterprise-accounts.support-entitlements %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[关于企业帐户](/admin/overview/about-enterprise-accounts)”
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -31,7 +31,7 @@ shortTitle: 连接 Azure 订阅
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.product.company_short %}'s Subscription Permission Validation requests read-only access to display the list of available subscriptions. To select an Azure subscription, you must have owner permissions to the subscription. If the default tenant does not have the right permissions, you may need to specify a different tenant ID. For more information, see [Microsoft identity platform and OAuth 2.0 authorization code flow](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code) in Microsoft Docs.
|
||||
**注意：**{% data variables.product.company_short %}的订阅权限验证请求只读访问权限以显示可用订阅的列表。 要选择 Azure 订阅，必须对订阅拥有所有者权限。 如果默认租户没有正确的权限，则可能需要指定其他租户 ID。 更多信息请参阅 Microsoft 文档中的 [Microsoft 身份平台和 OAuth 2.0 授权代码流](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code)。
|
||||
|
||||
{% endnote %}
|
||||
1. 单击 **Connect（连接）**。
|
||||
|
||||
@@ -37,7 +37,7 @@ You can disable {% data variables.product.prodname_dependabot_security_updates %
|
||||
|
||||
## Supported repositories
|
||||
|
||||
{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites.
|
||||
{% data variables.product.prodname_dotcom %} automatically enables {% data variables.product.prodname_dependabot_security_updates %} for every repository that meets these prerequisites.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -59,7 +59,7 @@ If security updates are not enabled for your repository and you don't know why,
|
||||
|
||||
You can enable or disable {% data variables.product.prodname_dependabot_security_updates %} for an individual repository (see below).
|
||||
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
You can also enable or disable {% data variables.product.prodname_dependabot_security_updates %} for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
|
||||
{% data variables.product.prodname_dependabot_security_updates %} require specific repository settings. For more information, see "[Supported repositories](#supported-repositories)."
|
||||
|
||||
@@ -68,7 +68,7 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** or **Disable**.
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
|
||||
{% ifversion fpt or ghec %}{% else %}{% endif %}
|
||||
|
||||
|
||||
|
||||
@@ -84,7 +84,7 @@ The recommended formats explicitly define which versions are used for all direct
|
||||
{%- endif %}
|
||||
| Maven | Java, Scala | `pom.xml` | `pom.xml` |
|
||||
| npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`|
|
||||
| Python PIP | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
|
||||
| pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}<sup>[2]</sup>{% else %}<sup>[1]</sup>{% endif %} |
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %}
|
||||
| Python Poetry | Python | `poetry.lock` | `poetry.lock`, `pyproject.toml` |{% endif %}
|
||||
| RubyGems | Ruby | `Gemfile.lock` | `Gemfile.lock`, `Gemfile`, `*.gemspec` |
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user