Octomerger Bot
@@ -29,7 +29,7 @@ translations/zh-CN/content/admin/code-security/managing-github-advanced-security
|
||||
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags
|
||||
@@ -199,6 +199,7 @@ translations/zh-CN/content/developers/github-marketplace/github-marketplace-over
|
||||
translations/zh-CN/content/developers/github-marketplace/using-the-github-marketplace-api-in-your-app/handling-new-purchases-and-free-trials.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/webhooks-and-events/webhooks/about-webhooks.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md,broken liquid tags
|
||||
translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,broken liquid tags
|
||||
translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-github-campus-program.md,broken liquid tags
|
||||
@@ -319,6 +320,8 @@ translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml,broken liquid
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/0.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/github-ae/2021-03/2021-03-03.yml,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/actions-use-policy-settings.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
|
||||
@@ -337,6 +340,7 @@ translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.
|
||||
translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
|
||||
|
||||
|
@@ -129,8 +129,8 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
| --- | --- |
|
||||
| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
|
||||
| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
|
||||
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li>{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li>{% endif %}<li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
||||
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are: <ul><li>`assign`: You were assigned to an issue or pull request.</li><li>`author`: You created an issue or pull request.</li><li>`ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.</li><li>`comment`: You commented on an issue or pull request.</li><li>`manual`: There was an update to an issue or pull request you manually subscribed to.</li><li>`mention`: You were mentioned on an issue or pull request.</li><li>`push`: Someone committed to a pull request you're subscribed to.</li><li>`review_requested`: You or a team you're a member of was requested to review a pull request.</li>{% ifversion fpt or ghes or ghae or ghec %}<li>`security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.</li>{% endif %}<li>`state_change`: An issue or pull request you're subscribed to was either closed or opened.</li><li>`subscribed`: There was an update in a repository you're watching.</li><li>`team_mention`: A team you belong to was mentioned on an issue or pull request.</li><li>`your_activity`: You opened, commented on, or closed an issue or pull request.</li></ul> |
|
||||
| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `<repository name>.<repository owner>.{% data variables.command_line.backticks %}`. |{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:<ul><li>`low`</li><li>`moderate`</li><li>`high`</li><li>`critical`</li></ul>For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |{% endif %}
|
||||
|
||||
## Choosing your notification settings
|
||||
@@ -139,7 +139,7 @@ Email notifications from {% data variables.product.product_location %} contain t
|
||||
{% data reusables.notifications-v2.manage-notifications %}
|
||||
3. On the notifications settings page, choose how you receive notifications when:
|
||||
- There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
|
||||
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
- You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% endif %} {% ifversion fpt or ghec %}
|
||||
- There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}
|
||||
- There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
|
||||
@@ -194,7 +194,7 @@ If you are a member of more than one organization, you can configure each one to
|
||||
5. Select one of your verified email addresses, then click **Save**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## {% data variables.product.prodname_dependabot_alerts %} notification options
|
||||
|
||||
{% data reusables.notifications.vulnerable-dependency-notification-enable %}
|
||||
|
||||
@@ -112,13 +112,13 @@ shortTitle: 从收件箱管理
|
||||
- `is:gist`
|
||||
- `is:issue-or-pull-request`
|
||||
- `is:release`
|
||||
- `is:repository-invitation`{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
- `is:repository-invitation`{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- `is:repository-vulnerability-alert`{% endif %}{% ifversion fpt or ghec %}
|
||||
- `is:repository-advisory`{% endif %}
|
||||
- `is:team-discussion`{% ifversion fpt or ghec %}
|
||||
- `is:discussion`{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
有关减少 {% data variables.product.prodname_dependabot_alerts %} 通知干扰的信息，请参阅“[配置漏洞依赖项的通知](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)”。
|
||||
{% endif %}
|
||||
|
||||
@@ -133,20 +133,20 @@ shortTitle: 从收件箱管理
|
||||
|
||||
要根据收到更新的原因过滤通知，您可以使用 `reason:` 查询。 例如，要查看当您（或您所属团队）被请求审查拉取请求时的通知，请使用 `reason:review-requested`。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#reasons-for-receiving-notifications)”。
|
||||
|
||||
| 查询 | 描述 |
|
||||
| ------------------------- | ------------------------------------------------------------------------ |
|
||||
| `reason:assign` | 分配给您的议题或拉取请求有更新时。 |
|
||||
| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 |
|
||||
| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 |
|
||||
| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 |
|
||||
| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 |
|
||||
| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 |
|
||||
| `reason:mention` | 您被直接@提及。 |
|
||||
| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| 查询 | 描述 |
|
||||
| ------------------------- | ------------------------------------------------------------- |
|
||||
| `reason:assign` | 分配给您的议题或拉取请求有更新时。 |
|
||||
| `reason:author` | 当您打开拉取请求或议题并且有更新或新评论时。 |
|
||||
| `reason:comment` | 当您评论了议题、拉取请求或团队讨论时。 |
|
||||
| `reason:participating` | 当您评论了议题、拉取请求或团队讨论或者被@提及时。 |
|
||||
| `reason:invitation` | 当您被邀请加入团队、组织或仓库时。 |
|
||||
| `reason:manual` | 当您在尚未订阅的议题或拉取请求上单击 **Subscribe（订阅）**时。 |
|
||||
| `reason:mention` | 您被直接@提及。 |
|
||||
| `reason:review-requested` | 您或您所属的团队被请求审查拉取请求。{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `reason:security-alert` | 为仓库发出安全警报时。{% endif %}
|
||||
| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 |
|
||||
| `reason:team-mention` | 您所在的团队被@提及时。 |
|
||||
| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 |
|
||||
| `reason:state-change` | 当拉取请求或议题的状态改变时。 例如，议题已关闭或拉取请求合并时。 |
|
||||
| `reason:team-mention` | 您所在的团队被@提及时。 |
|
||||
| `reason:ci-activity` | 当仓库有 CI 更新时，例如新的工作流程运行状态。 |
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### 支持的 `author:` 查询
|
||||
@@ -161,7 +161,7 @@ shortTitle: 从收件箱管理
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## {% data variables.product.prodname_dependabot %} 自定义过滤器
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
@@ -173,7 +173,7 @@ shortTitle: 从收件箱管理
|
||||
有关 {% data variables.product.prodname_dependabot %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.3 or ghae-issue-4864 %}
|
||||
{% ifversion ghes < 3.3 or ghae %}
|
||||
|
||||
如果使用 {% data variables.product.prodname_dependabot %} 来告知易受攻击的依赖项，则可以使用并保存这些自定义筛选器来显示 {% data variables.product.prodname_dependabot_alerts %} 的通知：
|
||||
- `is:repository_vulnerability_alert`
|
||||
|
||||
@@ -91,10 +91,7 @@ The contribution activity section includes a detailed timeline of your work, inc
|
||||
|
||||
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|
||||
## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.product.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -18,7 +18,7 @@ shortTitle: 管理主题设置
|
||||
|
||||
您可能需要使用深色主题来减少某些设备的功耗，以在低光条件下减小眼睛的压力，或者因为您更喜欢主题的外观。
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}如果您视力不佳，则可以从前景和背景元素之间对比度更高的高对比度主题中受益。{% endif %}{% ifversion fpt or ghae-issue-4619 or ghec %} 如果您有色盲，可能会从我们的浅色盲和深色盲主题中受益。
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}如果您视力不佳，则可以从前景和背景元素之间对比度更高的高对比度主题中受益。{% endif %}{% ifversion fpt or ghae or ghec %} 如果您有色盲，可能会从我们的浅色盲和深色盲主题中受益。
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -31,10 +31,10 @@ shortTitle: 管理主题设置
|
||||
1. 单击想要使用的主题。
|
||||
- 如果您选择单个主题，请单击一个主题。
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}{% else %}{% endif %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %}
|
||||
- 如果您选择遵循系统设置，请单击白天主题和夜间主题。
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4618 or ghec %}{% else %}{% endif %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %}
|
||||
{% ifversion fpt or ghec %}
|
||||
- 如果您想选择当前处于公开测试阶段的主题，则首先需要通过功能预览启用它。 更多信息请参阅“[通过功能预览了解早期访问版本](/get-started/using-github/exploring-early-access-releases-with-feature-preview)”。{% endif %}
|
||||
|
||||
|
||||
@@ -47,7 +47,7 @@ shortTitle: 权限用户仓库
|
||||
| 删除和恢复包 | “[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”
|
||||
{% endif %}
|
||||
| 自定义仓库的社交媒体预览 | "[自定义仓库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" |
|
||||
| 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| 从仓库创建模板 | "[创建模板仓库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)" |{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| 控制对易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %} 访问 | "[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %}
|
||||
| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | "[查看漏洞依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" |
|
||||
| 管理私有仓库的数据使用 | “[管理私有仓库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)”
|
||||
|
||||
@@ -273,7 +273,7 @@ runs:
|
||||
|
||||
### `runs.steps`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
|
||||
**必要** 您计划在此操作中的步骤。 这些步骤可以是 `run` 步骤或 `uses` 步骤。
|
||||
@@ -288,7 +288,7 @@ runs:
|
||||
|
||||
#### `runs.steps[*].run`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
|
||||
**可选** 您想要运行的命令。 这可以是内联的，也可以是操作仓库中的脚本：
|
||||
@@ -332,7 +332,7 @@ runs:
|
||||
|
||||
#### `runs.steps[*].shell`
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
|
||||
**可选** 您想要在其中运行命令的 shell。 您可以使用[这里](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsshell)列出的任何 shell。 如果设置了 `run`，则必填。
|
||||
@@ -407,7 +407,7 @@ steps:
|
||||
|
||||
**可选** 指定命令在其中运行的工作目录。
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4853 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
|
||||
#### `runs.steps[*].uses`
|
||||
|
||||
@@ -69,7 +69,7 @@ You can use any machine as a self-hosted runner as long at it meets these requir
|
||||
* The machine has enough hardware resources for the type of workflows you plan to run. The self-hosted runner application itself only requires minimal resources.
|
||||
* If you want to run workflows that use Docker container actions or service containers, you must use a Linux machine and Docker must be installed.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghec or ghae-issue-4462 %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghec or ghae %}
|
||||
## Autoscaling your self-hosted runners
|
||||
|
||||
You can automatically increase or decrease the number of self-hosted runners in your environment in response to the webhook events you receive. For more information, see "[Autoscaling with self-hosted runners](/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners)."
|
||||
|
||||
@@ -5,7 +5,7 @@ versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.2'
|
||||
ghae: issue-4462
|
||||
ghae: '*'
|
||||
type: overview
|
||||
---
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ shortTitle: 触发工作流程的事件
|
||||
|
||||
某些事件具有多种活动类型。 对于这些事件，您可以指定将触发工作流程运行的活动类型。 有关每个活动类型的含义的详细信息，请参阅“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhook-events-and-payloads)”。 请注意，并非所有 web 挂钩事件都会触发工作流程。
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4968 %}
|
||||
{% ifversion fpt or ghec or ghes > 3.3 or ghae %}
|
||||
### `branch_protection_rule`
|
||||
|
||||
| Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` |
|
||||
|
||||
@@ -99,18 +99,18 @@ core.setOutput('SELECTED_COLOR', 'green');
|
||||
|
||||
下表显示了在工作流程中可用的工具包功能：
|
||||
|
||||
| 工具包函数 | 等效工作流程命令 |
|
||||
| --------------------- | --------------------------------------------------------------------- |
|
||||
| `core.addPath` | 可使用环境文件 `GITHUB_PATH` 访问 |
|
||||
| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
|
||||
| 工具包函数 | 等效工作流程命令 |
|
||||
| --------------------- | ---------------------------------------------------------- |
|
||||
| `core.addPath` | 可使用环境文件 `GITHUB_PATH` 访问 |
|
||||
| `core.debug` | `debug` |{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
| `core.notice` | `notice`
|
||||
{% endif %}
|
||||
| `core.error` | `error` |
|
||||
| `core.endGroup` | `endgroup` |
|
||||
| `core.exportVariable` | 可使用环境文件 `GITHUB_ENV` 访问 |
|
||||
| `core.getInput` | 可使用环境变量 `INPUT_{NAME}` 访问 |
|
||||
| `core.getState` | 可使用环境变量 `STATE_{NAME}` 访问 |
|
||||
| `core.isDebug` | 可使用环境变量 `RUNNER_DEBUG` 访问 |
|
||||
| `core.error` | `error` |
|
||||
| `core.endGroup` | `endgroup` |
|
||||
| `core.exportVariable` | 可使用环境文件 `GITHUB_ENV` 访问 |
|
||||
| `core.getInput` | 可使用环境变量 `INPUT_{NAME}` 访问 |
|
||||
| `core.getState` | 可使用环境变量 `STATE_{NAME}` 访问 |
|
||||
| `core.isDebug` | 可使用环境变量 `RUNNER_DEBUG` 访问 |
|
||||
{%- if actions-job-summaries %}
|
||||
| `core.summary` | 可使用环境变量 `GITHUB_STEP_SUMMARY` 访问 |
|
||||
{%- endif %}
|
||||
@@ -170,7 +170,7 @@ Write-Output "::debug::Set the Octocat variable"
|
||||
|
||||
{% endpowershell %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
## 设置通知消息
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ intro: 您可以使用将机密和漏洞排除在代码库之外并维护软件
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Enterprise
|
||||
children:
|
||||
|
||||
@@ -5,7 +5,7 @@ shortTitle: About supply chain security
|
||||
permissions: ''
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -4,7 +4,7 @@ shortTitle: 供应链安全
|
||||
intro: 您可以可视化、维护和保护开发人员软件供应链中的依赖项。
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Enterprise
|
||||
children:
|
||||
|
||||
@@ -5,7 +5,7 @@ shortTitle: View vulnerability data
|
||||
permissions: 'Site administrators can view vulnerability data on {% data variables.product.product_location %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -12,7 +12,7 @@ topics:
|
||||
|
||||
## About {% data variables.product.prodname_github_connect %}
|
||||
|
||||
{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}.
|
||||
{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}.
|
||||
|
||||
{% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
|
||||
|
||||
@@ -28,7 +28,7 @@ After you configure the connection between {% data variables.product.product_loc
|
||||
|
||||
Feature | Description | More information |
|
||||
------- | ----------- | ---------------- |{% ifversion ghes %}
|
||||
Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %}
|
||||
Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %}
|
||||
{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% if server-statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %}
|
||||
@@ -64,7 +64,7 @@ Additional data is transmitted if you enable individual features of {% data vari
|
||||
|
||||
Feature | Data | Which way does the data flow? | Where is the data used? |
|
||||
------- | ---- | --------- | ------ |{% ifversion ghes %}
|
||||
Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %}
|
||||
Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %}
|
||||
{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% if dependabot-updates-github-connect %}
|
||||
{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository<br><br>If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% if server-statistics %}
|
||||
|
||||
@@ -15,7 +15,7 @@ redirect_from:
|
||||
permissions: 'Enterprise owners can enable {% data variables.product.prodname_dependabot %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
|
||||
@@ -34,7 +34,7 @@ topics:
|
||||
## 配置存储库缓存
|
||||
|
||||
{% ifversion ghes = 3.3 %}
|
||||
1. On your primary {% data variables.product.prodname_ghe_server %} appliance, enable the feature flag for repository caching.
|
||||
1. 在主 {% data variables.product.prodname_ghe_server %} 设备上，为存储库缓存启用功能标志。
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
@@ -48,7 +48,7 @@ topics:
|
||||
$ ssh -p 122 admin@<em>REPLICA IP</em>
|
||||
```
|
||||
{%- ifversion ghes = 3.3 %}
|
||||
1. On your cache replica, enable the feature flag for repository caching.
|
||||
1. 在缓存副本上，为存储库缓存启用功能标志。
|
||||
|
||||
```
|
||||
$ ghe-config cluster.cache-enabled true
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: Getting started with self-hosted runners for your enterprise
|
||||
shortTitle: Self-hosted runners
|
||||
intro: You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}.
|
||||
intro: 'You can configure a runner machine for your enterprise so your developers can start automating workflows with {% data variables.product.prodname_actions %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
permissions: Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise.
|
||||
permissions: 'Enterprise owners can configure policies for {% data variables.product.prodname_actions %} and add self-hosted runners to the enterprise.'
|
||||
type: quick_start
|
||||
topics:
|
||||
- Actions
|
||||
@@ -32,7 +32,7 @@ This guide shows you how to apply a centralized management approach to self-host
|
||||
1. Deploy a self-hosted runner for your enterprise
|
||||
1. Create a group to manage access to the runners available to your enterprise
|
||||
1. Optionally, further restrict the repositories that can use the runner
|
||||
{%- ifversion ghec or ghae-issue-4462 or ghes > 3.2 %}
|
||||
{%- ifversion ghec or ghae or ghes > 3.2 %}
|
||||
1. Optionally, build custom tooling to automatically scale your self-hosted runners
|
||||
{% endif %}
|
||||
|
||||
@@ -122,7 +122,7 @@ Optionally, organization owners can further restrict the access policy of the ru
|
||||
|
||||
For more information, see "[Managing access to self-hosted runners using groups](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)."
|
||||
|
||||
{% ifversion ghec or ghae-issue-4462 or ghes > 3.2 %}
|
||||
{% ifversion ghec or ghae or ghes > 3.2 %}
|
||||
|
||||
## 5. Automatically scale your self-hosted runners
|
||||
|
||||
|
||||
@@ -46,7 +46,7 @@ Before enabling access to all actions from {% data variables.product.prodname_do
|
||||
|
||||
1. {% data reusables.actions.enterprise-limit-actions-use %}
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae-issue-4815 %}
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
|
||||
## Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website %}
|
||||
|
||||
|
||||
@@ -33,7 +33,7 @@ If your machine has access to both systems at the same time, you can do the sync
|
||||
|
||||
The `actions-sync` tool can only download actions from {% data variables.product.prodname_dotcom_the_website %} that are stored in public repositories.
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae-issue-4815 %}
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The `actions-sync` tool is intended for use in systems where {% data variables.product.prodname_github_connect %} is not enabled. If you run the tool on a system with {% data variables.product.prodname_github_connect %} enabled, you may see the error `The repository <repo_name> has been retired and cannot be reused`. This indicates that a workflow has used that action directly on {% data variables.product.prodname_dotcom_the_website %} and the namespace is retired on {% data variables.product.product_location %}. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
@@ -47,7 +47,7 @@ Once {% data variables.product.prodname_github_connect %} is configured, you can
|
||||
1. Configure your workflow's YAML to use `{% data reusables.actions.action-checkout %}`.
|
||||
1. Each time your workflow runs, the runner will use the specified version of `actions/checkout` from {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% ifversion ghes > 3.2 or ghae-issue-4815 %}
|
||||
{% ifversion ghes > 3.2 or ghae %}
|
||||
{% note %}
|
||||
|
||||
**Note:** The first time the `checkout` action is used from {% data variables.product.prodname_dotcom_the_website %}, the `actions/checkout` namespace is automatically retired on {% data variables.product.product_location %}. If you ever want to revert to using a local copy of the action, you first need to remove the namespace from retirement. For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Audit log events for your enterprise
|
||||
intro: Learn about audit log events recorded for your enterprise.
|
||||
shortTitle: Audit log events
|
||||
permissions: Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.
|
||||
permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.'
|
||||
miniTocMaxHeadingLevel: 4
|
||||
redirect_from:
|
||||
- /enterprise/admin/articles/audited-actions
|
||||
@@ -202,7 +202,7 @@ Action | Description
|
||||
| `config_entry.update` | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
### `dependabot_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -240,7 +240,7 @@ Action | Description
|
||||
| `dependabot_security_updates_new_repos.enable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
|
||||
{%- ifversion fpt or ghec or ghes or ghae %}
|
||||
### `dependency_graph` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -1145,7 +1145,7 @@ Action | Description
|
||||
| `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise.
|
||||
| `repository_visibility_change.enable` | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise.
|
||||
|
||||
{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
|
||||
{%- ifversion fpt or ghec or ghes or ghae %}
|
||||
### `repository_vulnerability_alert` category actions
|
||||
|
||||
| Action | Description
|
||||
|
||||
@@ -66,7 +66,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
|
||||
1. Under "Policies", select {% data reusables.actions.policy-label-for-select-actions-workflows %} and add your required actions{% if actions-workflow-policy %} and reusable workflows{% endif %} to the list.
|
||||
{% if actions-workflow-policy %}
|
||||
|
||||
{%- elsif ghes or ghae-issue-5094 %}
|
||||
{%- elsif ghes or ghae %}
|
||||
|
||||
{%- elsif ghae %}
|
||||
|
||||
|
||||
@@ -16,7 +16,7 @@ shortTitle: Authentication to GitHub
|
||||
---
|
||||
## About authentication to {% data variables.product.prodname_dotcom %}
|
||||
|
||||
To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be.
|
||||
To keep your account secure, you must authenticate before you can access{% ifversion not ghae %} certain{% endif %} resources on {% data variables.product.product_name %}. When you authenticate to {% data variables.product.product_name %}, you supply or confirm credentials that are unique to you to prove that you are exactly who you declare to be.
|
||||
|
||||
You can access your resources in {% data variables.product.product_name %} in a variety of ways: in the browser, via {% data variables.product.prodname_desktop %} or another desktop application, with the API, or via the command line. Each way of accessing {% data variables.product.product_name %} supports different modes of authentication.
|
||||
{%- ifversion not fpt %}
|
||||
@@ -48,8 +48,8 @@ You can authenticate to {% data variables.product.product_name %} in your browse
|
||||
- **Username and password only**
|
||||
- You'll create a password when you create your account on {% data variables.product.product_name %}. We recommend that you use a password manager to generate a random and unique password. For more information, see "[Creating a strong password](/github/authenticating-to-github/creating-a-strong-password)."{% ifversion fpt or ghec %}
|
||||
- If you have not enabled 2FA, {% data variables.product.product_name %} will ask for additional verification when you first sign in from an unrecognized device, such as a new browser profile, a browser where the cookies have been deleted, or a new computer.
|
||||
|
||||
After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the GitHub Mobile application installed, you'll receive a notification there instead.{% endif %}
|
||||
|
||||
After providing your username and password, you will be asked to provide a verification code that we will send to you via email. If you have the {% data variables.product.prodname_mobile %} application installed, you'll receive a notification there instead. For more information, see "[{% data variables.product.prodname_mobile %}](/get-started/using-github/github-mobile)."{% endif %}
|
||||
- **Two-factor authentication (2FA)** (recommended)
|
||||
- If you enable 2FA, after you successfully enter your username and password, we'll also prompt you to provide a code that's generated by a time-based one time password (TOTP) application on your mobile device{% ifversion fpt or ghec %} or sent as a text message (SMS){% endif %}. For more information, see "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/github/authenticating-to-github/accessing-github-using-two-factor-authentication#providing-a-2fa-code-when-signing-in-to-the-website)."
|
||||
- In addition to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}, you can optionally add an alternative method of authentication with {% ifversion fpt or ghec %}{% data variables.product.prodname_mobile %} or{% endif %} a security key using WebAuthn. For more information, see {% ifversion fpt or ghec %}"[Configuring two-factor authentication with {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile)" and {% endif %}"[Configuring two-factor authentication using a security key](/github/authenticating-to-github/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."{% ifversion ghes %}
|
||||
@@ -61,14 +61,13 @@ You can authenticate to {% data variables.product.product_name %} in your browse
|
||||
{% endif %}
|
||||
|
||||
## Authenticating with {% data variables.product.prodname_desktop %}
|
||||
|
||||
You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[Authenticating to {% data variables.product.prodname_dotcom %}](/desktop/getting-started-with-github-desktop/authenticating-to-github)."
|
||||
|
||||
## Authenticating with the API
|
||||
|
||||
You can authenticate with the API in different ways.
|
||||
|
||||
- **Personal access tokens**
|
||||
- **Personal access tokens**
|
||||
- In limited situations, such as testing, you can use a personal access token to access the API. Using a personal access token enables you to revoke access at any time. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
- **Web application flow**
|
||||
- For OAuth Apps in production, you should authenticate using the web application flow. For more information, see "[Authorizing OAuth Apps](/apps/building-oauth-apps/authorizing-oauth-apps/#web-application-flow)."
|
||||
@@ -81,7 +80,7 @@ You can access repositories on {% data variables.product.product_name %} from th
|
||||
|
||||
### HTTPS
|
||||
|
||||
You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy.
|
||||
You can work with all repositories on {% data variables.product.product_name %} over HTTPS, even if you are behind a firewall or proxy.
|
||||
|
||||
If you authenticate with {% data variables.product.prodname_cli %}, you can either authenticate with a personal access token or via the web browser. For more information about authenticating with {% data variables.product.prodname_cli %}, see [`gh auth login`](https://cli.github.com/manual/gh_auth_login).
|
||||
|
||||
|
||||
@@ -44,7 +44,7 @@ A token with no assigned scopes can only access public information. To use your
|
||||
{% data reusables.user-settings.personal_access_tokens %}
|
||||
{% data reusables.user-settings.generate_new_token %}
|
||||
5. Give your token a descriptive name.
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
|
||||
{% endif %}
|
||||
7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
|
||||
@@ -82,5 +82,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
|
||||
- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
|
||||
|
||||
@@ -28,15 +28,11 @@ shortTitle: 安全日志
|
||||
1. 在用户设置侧边栏中，单击 **Security log（安全日志）**。 
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
## 搜索安全日志
|
||||
|
||||
{% data reusables.audit_log.audit-log-search %}
|
||||
|
||||
### 基于执行的操作搜索
|
||||
{% else %}
|
||||
## 了解安全日志中的事件
|
||||
{% endif %}
|
||||
|
||||
安全日志中列出的事件由您的操作触发。 操作分为以下几类：
|
||||
|
||||
@@ -109,10 +105,10 @@ shortTitle: 安全日志
|
||||
|
||||
### `oauth_authority` 类别操作
|
||||
|
||||
| 操作 | 描述 |
|
||||
| --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `create` | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。 |
|
||||
| `destroy` | 当您 [撤销 {% data variables.product.prodname_oauth_app %}对您帐户的访问](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %} 时，以及当 [授权被吊销或过期](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)时触发。{% else %}.{% endif %}
|
||||
| 操作 | 描述 |
|
||||
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
| `create` | 当您[授予 {% data variables.product.prodname_oauth_app %} 访问权限](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps)时触发。 |
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae or ghes > 3.2 or ghec %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ redirect_from:
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation
|
||||
---
|
||||
|
||||
当令牌 {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}已过期或 {% endif %} 已被吊销时，它不能再用于对 Git 和 API 请求进行身份验证。 无法还原过期或已吊销的令牌，您或应用程序将需要创建新令牌。
|
||||
当令牌 {% ifversion fpt or ghae or ghes > 3.2 or ghec %}已过期或 {% endif %} 已被吊销时，它不能再用于对 Git 和 API 请求进行身份验证。 无法还原过期或已吊销的令牌，您或应用程序将需要创建新令牌。
|
||||
|
||||
本文介绍了 {% data variables.product.product_name %} 令牌可能被吊销或过期的可能原因。
|
||||
|
||||
@@ -24,7 +24,7 @@ redirect_from:
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
|
||||
{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
## 令牌在到达其到期日期后被吊销
|
||||
|
||||
创建个人访问令牌时，建议为令牌设置过期时间。 到达令牌的到期日期后，令牌将自动吊销。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。
|
||||
|
||||
@@ -57,7 +57,7 @@ shortTitle: 更新访问凭据
|
||||
|
||||
{% ifversion not ghae %}
|
||||
|
||||
如果您已重置帐户密码，并且还希望触发从 GitHub Mobile 应用注销，则可以撤销对“GitHub iOS”或“GitHub Android”OAuth 应用的授权。 有关其他信息，请参阅“[>审查授权的集成](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”。
|
||||
If you have reset your account password and would also like to trigger a sign-out from the {% data variables.product.prodname_mobile %} app, you can revoke your authorization of the "GitHub iOS" or "GitHub Android" OAuth App. This will sign out all instances of the {% data variables.product.prodname_mobile %} app associated with your account. 有关其他信息，请参阅“[>审查授权的集成](/authentication/keeping-your-account-and-data-secure/reviewing-your-authorized-integrations)”。
|
||||
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -48,7 +48,7 @@ shortTitle: GitHub Actions 的计费
|
||||
|
||||
仓库使用的存储空间是 {% data variables.product.prodname_actions %} 构件和 {% data variables.product.prodname_registry %} 使用的存储空间总计。 您的存储成本是您帐户拥有的所有帐户的总使用量。 有关 {% data variables.product.prodname_registry %} 定价的更多信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。
|
||||
|
||||
如果您的帐户使用量超出了这些限额，并且您设置的支出限额高于 0 美元，则每月的每 GB 存储用量和每分钟用量需要支付 0.25 美元，具体取决于 {% data variables.product.prodname_dotcom %} 托管运行器使用的操作系统。 {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数舍入到最接近的分钟整数。
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数舍入到最接近的分钟整数。
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -49,9 +49,9 @@ All data transferred out, when triggered by {% data variables.product.prodname_a
|
||||
|
||||
Storage usage is shared with build artifacts produced by {% data variables.product.prodname_actions %} for repositories owned by your account. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
|
||||
|
||||
{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.25 USD per GB of storage and $0.50 USD per GB of data transfer.
|
||||
{% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the package is published. If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and $0.50 USD per GB of data transfer.
|
||||
|
||||
For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.25 USD per GB or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD.
|
||||
For example, if your organization uses {% data variables.product.prodname_team %}, allows unlimited spending, uses 150GB of storage, and has 50GB of data transfer out during a month, the organization would have overages of 148GB for storage and 40GB for data transfer for that month. The storage overage would cost $0.008 USD per GB per day or $37 USD. The overage for data transfer would cost $0.50 USD per GB or $20 USD.
|
||||
|
||||
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_packages %}
|
||||
|
||||
|
||||
@@ -73,7 +73,7 @@ By default, the {% data variables.product.prodname_codeql_workflow %} uses the `
|
||||
|
||||
If you scan on push, then the results appear in the **Security** tab for your repository. For more information, see "[Managing code scanning alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository#viewing-the-alerts-for-a-repository)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
Additionally, when an `on:push` scan returns results that can be mapped to an open pull request, these alerts will automatically appear on the pull request in the same places as other pull request alerts. The alerts are identified by comparing the existing analysis of the head of the branch to the analysis for the target branch. For more information on {% data variables.product.prodname_code_scanning %} alerts in pull requests, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
{% endif %}
|
||||
|
||||
@@ -85,7 +85,7 @@ For more information about the `pull_request` event, see "[Events that trigger w
|
||||
|
||||
If you scan pull requests, then the results appear as alerts in a pull request check. For more information, see "[Triaging code scanning alerts in pull requests](/code-security/secure-coding/triaging-code-scanning-alerts-in-pull-requests)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
Using the `pull_request` trigger, configured to scan the pull request's merge commit rather than the head commit, will produce more efficient and accurate results than scanning the head of the branch on each push. However, if you use a CI/CD system that cannot be configured to trigger on pull requests, you can still use the `on:push` trigger and {% data variables.product.prodname_code_scanning %} will map the results to open pull requests on the branch and add the alerts as annotations on the pull request. For more information, see "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)."
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -155,9 +155,9 @@ The names of the {% data variables.product.prodname_code_scanning %} analysis ch
|
||||
|
||||
|
||||
|
||||
When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
|
||||
When the {% data variables.product.prodname_code_scanning %} jobs complete, {% data variables.product.prodname_dotcom %} works out whether any alerts were added by the pull request and adds the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" entry to the list of checks. After {% data variables.product.prodname_code_scanning %} has been performed at least once, you can click **Details** to view the results of the analysis. If you used a pull request to add {% data variables.product.prodname_code_scanning %} to the repository, you will initially see {% ifversion fpt or ghes > 3.2 or ghae or ghec %}an "Analysis not found"{% else %}a "Missing analysis"{% endif %} message when you click **Details** on the "{% data variables.product.prodname_code_scanning_capc %} results / TOOL NAME" check.
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
|
||||
|
||||
The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request.
|
||||
@@ -167,13 +167,13 @@ For example, in the screenshot above, {% data variables.product.prodname_code_sc
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
### Reasons for the "Analysis not found" message
|
||||
{% else %}
|
||||
### Reasons for the "Missing analysis" message
|
||||
{% endif %}
|
||||
|
||||
After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message.
|
||||
After {% data variables.product.prodname_code_scanning %} has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows {% data variables.product.prodname_code_scanning %} to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add {% data variables.product.prodname_code_scanning %} to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the {% ifversion fpt or ghes > 3.2 or ghae or ghec %}"Analysis not found"{% else %}"Missing analysis for base commit SHA-HASH"{% endif %} message.
|
||||
|
||||
There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
|
||||
|
||||
|
||||
@@ -28,7 +28,7 @@ topics:
|
||||
## 关于拉取请求上的 {% data variables.product.prodname_code_scanning %} 结果
|
||||
|
||||
在仓库中，如果 {% data variables.product.prodname_code_scanning %} 被配置为拉取请求检查，则 {% data variables.product.prodname_code_scanning %} 将检查拉取请求中的代码。 默认情况下，这仅限于针对默认分支的拉取请求，但是您可以在 {% data variables.product.prodname_actions %} 或第三方 CI/CD 系统中更改此配置。 如果合并分支给目标分支带来新的 {% data variables.product.prodname_code_scanning %} 警报，这些警报将在拉取请求中被报告为检查结果。 警报还将在拉取请求的 **Files changed（文件已更改）**选项卡中显示为注释。 如果您拥有仓库的写入权限，您可以在 **Security（安全）**选项卡中查看任何现有的 {% data variables.product.prodname_code_scanning %} 警报。 有关仓库警报的更多信息，请参阅“[管理仓库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-5093 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
在 {% data variables.product.prodname_code_scanning %} 配置为在每次推送代码时扫描的存储库中，{% data variables.product.prodname_code_scanning %} 还会将结果映射到任何打开的拉取请求，并将警报作为注释添加到与其他拉取请求检查相同的位置。 更多信息请参阅“[在推送时扫描](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)”。
|
||||
{% endif %}
|
||||
|
||||
@@ -42,7 +42,7 @@ topics:
|
||||
|
||||
对于 {% data variables.product.prodname_code_scanning %} 的所有配置，包含 {% data variables.product.prodname_code_scanning %} 结果的检查为：**{% data variables.product.prodname_code_scanning_capc %} 结果**。 所使用的每个分析工具的结果将单独显示。 由拉取请求中的更改引起的任何新警报都显示为注释。
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4902 or ghec %} 要查看所分析分支的完整警报集，请单击“**查看所有分支警报**”。 这将打开完整的警报视图，您可以在其中按类型、严重性、标记等筛选分支上的所有警报。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)”。
|
||||
{% ifversion fpt or ghes > 3.2 or ghae or ghec %} To see the full set of alerts for the analyzed branch, click **View all branch alerts**. 这将打开完整的警报视图，您可以在其中按类型、严重性、标记等筛选分支上的所有警报。 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-and-searching-for-code-scanning-alerts)”。
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -10,7 +10,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
|
||||
@@ -5,7 +5,7 @@ shortTitle: 配置 Dependabot 警报
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -9,7 +9,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
@@ -31,7 +31,7 @@ topics:
|
||||
{% ifversion fpt or ghec %}如果您是组织所有者，您可以对组织中的所有仓库一键启用或禁用 {% data variables.product.prodname_dependabot_alerts %}。 您也可以设置是否对新建的仓库启用或禁用有漏洞依赖项检测。 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#enabling-or-disabling-a-feature-for-all-new-repositories-when-they-are-added)”。
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghae-issue-4864 %}
|
||||
{% ifversion ghes or ghae %}
|
||||
默认情况下，如果您的企业所有者已配置电子邮件以获取有关企业的通知，您将收到 {% data variables.product.prodname_dependabot_alerts %} 电子邮件。
|
||||
|
||||
企业所有者也可以在没有通知的情况下启用 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。
|
||||
|
||||
@@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Dependabot
|
||||
|
||||
@@ -11,7 +11,7 @@ shortTitle: 查看 Dependabot 警报
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
@@ -55,7 +55,7 @@ topics:
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：** 在测试版期间，此功能仅适用于在 2022 年 4 月 14 日*之后*创建的新 Python 公告，以及历史 Python 公告的子集。 GitHub 正在努力回填其他历史 Python 公告的数据，这些公告是滚动添加的。 有漏洞的调用仅在 {% data variables.product.prodname_dependabot_alerts %} 页面上突出显示。
|
||||
**注意：** 在测试版期间，此功能仅适用于在 2022 年 4 月 14 日*之后*创建的新 Python 公告，以及历史 Python 公告的子集。 {% data variables.product.prodname_dotcom %} is working to backfill data across additional historical Python advisories, which are added on a rolling basis. 有漏洞的调用仅在 {% data variables.product.prodname_dependabot_alerts %} 页面上突出显示。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -65,7 +65,7 @@ topics:
|
||||
|
||||
对于检测到有漏洞的调用的警报，警报详细信息页面将显示其他信息：
|
||||
|
||||
- 显示函数使用位置或者在有多个调用时显示对函数的第一次调用的代码块。
|
||||
- One or more code blocks showing where the function is used.
|
||||
- 列出函数本身以及指向调用函数的行的链接的注释。
|
||||
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ shortTitle: Dependabot 版本更新
|
||||
|
||||
{% data variables.product.prodname_dependabot %} 负责维护您的依赖项。 您可以使用它来确保仓库自动跟上它所依赖的包和应用程序的最新版本。
|
||||
|
||||
通过将 a _dependabot.yml_configuration 文件检入仓库，可启用 {% data variables.product.prodname_dependabot_version_updates %}。 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
|
||||
You enable {% data variables.product.prodname_dependabot_version_updates %} by checking a _dependabot.yml_ configuration file into your repository. 配置文件指定存储在仓库中的清单或其他包定义文件的位置。 {% data variables.product.prodname_dependabot %} 使用此信息来检查过时的软件包和应用程序。 {% data variables.product.prodname_dependabot %} 确定依赖项是否有新版本，它通过查看依赖的语义版本 ([semver](https://semver.org/)) 来决定是否应更新该版本。 对于某些软件包管理器，{% data variables.product.prodname_dependabot_version_updates %} 也支持供应。 供应（或缓存）的依赖项是检入仓库中特定目录的依赖项，而不是在清单中引用的依赖项。 即使包服务器不可用，供应的依赖项在生成时也可用。 {% data variables.product.prodname_dependabot_version_updates %} 可以配置为检查为新版本供应的依赖项，并在必要时更新它们。
|
||||
|
||||
当 {% data variables.product.prodname_dependabot %} 发现过时的依赖项时，它会发起拉取请求以将清单更新到依赖项的最新版本。 对于供应和依赖项，{% data variables.product.prodname_dependabot %} 提出拉取请求以直接将过时的依赖项替换为新版本。 检查测试是否通过，查看拉取请求摘要中包含的更改日志和发行说明，然后合并它。 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot %} 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)”。
|
||||
|
||||
|
||||
@@ -6,7 +6,7 @@ allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Dependabot
|
||||
|
||||
@@ -9,7 +9,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
@@ -36,7 +36,7 @@ topics:
|
||||
* {% data variables.product.prodname_dependabot %} scans any push, to the default branch, that contains a manifest file. When a new vulnerability record is added, it scans all existing repositories and generates an alert for each vulnerable repository. {% data variables.product.prodname_dependabot_alerts %} are aggregated at the repository level, rather than creating one alert per vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
* {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} are triggered when you receive an alert about a vulnerable dependency in your repository. Where possible, {% data variables.product.prodname_dependabot %} creates a pull request in your repository to upgrade the vulnerable dependency to the minimum possible secure version needed to avoid the vulnerability. For more information, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" and "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)."
|
||||
|
||||
{% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae-issue-4864 %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
|
||||
{% endif %}{% data variables.product.prodname_dependabot %} doesn't scan repositories for vulnerable dependencies on a schedule, but rather when something changes. For example, a scan is triggered when a new dependency is added ({% data variables.product.prodname_dotcom %} checks for this on every push), or when a new vulnerability is added to the advisory database{% ifversion ghes or ghae %} and synchronized to {% data variables.product.product_location %}{% endif %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
|
||||
|
||||
## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles?
|
||||
|
||||
|
||||
@@ -20,7 +20,7 @@ topics:
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that you can view, search, and filter. {% data reusables.security-advisory.link-browsing-advisory-db %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## Available for all repositories
|
||||
{% endif %}
|
||||
### Security policy
|
||||
@@ -41,7 +41,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie
|
||||
and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes < 3.3 or ghae-issue-4864 %}
|
||||
{% ifversion ghes < 3.3 or ghae %}
|
||||
### {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% data reusables.dependabot.dependabot-alerts-beta %}
|
||||
@@ -55,7 +55,7 @@ View alerts about dependencies that are known to contain security vulnerabilitie
|
||||
Use {% data variables.product.prodname_dependabot %} to automatically raise pull requests to keep your dependencies up-to-date. This helps reduce your exposure to older versions of dependencies. Using newer versions makes it easier to apply patches if security vulnerabilities are discovered, and also makes it easier for {% data variables.product.prodname_dependabot_security_updates %} to successfully raise pull requests to upgrade vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_version_updates %}](/github/administering-a-repository/about-dependabot-version-updates)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
### Dependency graph
|
||||
The dependency graph allows you to explore the ecosystems and packages that your repository depends on and the repositories and packages that depend on your repository.
|
||||
|
||||
@@ -100,13 +100,13 @@ Available only with a license for {% data variables.product.prodname_GH_advanced
|
||||
Automatically detect tokens or credentials that have been checked into a repository. You can view alerts for any secrets that {% data variables.product.company_short %} finds in your code, so that you know which tokens or credentials to treat as compromised. For more information, see "[About secret scanning](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
### Dependency review
|
||||
|
||||
Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 or ghae-issue-4554 %}
|
||||
{% ifversion ghec or ghes > 3.1 or ghae %}
|
||||
### Security overview for organizations{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}, enterprises,{% endif %} and teams
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -33,7 +33,7 @@ You can create a default security policy that will display in any of your organi
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## Managing {% data variables.product.prodname_dependabot_alerts %} and the dependency graph
|
||||
|
||||
{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %} detects vulnerabilities in public repositories and displays the dependency graph. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} for all public repositories owned by your organization. You can enable or disable {% data variables.product.prodname_dependabot_alerts %} and the dependency graph for all private repositories owned by your organization.
|
||||
@@ -51,7 +51,7 @@ You can create a default security policy that will display in any of your organi
|
||||
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
## Managing dependency review
|
||||
|
||||
@@ -138,7 +138,7 @@ You can view and manage alerts from security features to address dependencies an
|
||||
{% ifversion fpt or ghec %}If you have a security vulnerability, you can create a security advisory to privately discuss and fix the vulnerability. For more information, see "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" and "[Creating a security advisory](/code-security/security-advisories/creating-a-security-advisory)."
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4554 %}{% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae-issue-4554 %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae-issue-4554 %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghec or ghae %}{% ifversion ghes > 3.1 or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can view, filter, and sort security alerts for repositories owned by {% ifversion ghes > 3.1 or ghec or ghae %}your{% elsif fpt %}their{% endif %} organization in the security overview. For more information, see{% ifversion ghes or ghec or ghae %} "[About the security overview](/code-security/security-overview/about-the-security-overview)."{% elsif fpt %} "[About the security overview](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}{% endif %}
|
||||
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -44,7 +44,7 @@ From the main page of your repository, click **{% octicon "gear" aria-label="The
|
||||
|
||||
For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## Managing the dependency graph
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
@@ -61,7 +61,7 @@ For more information, see "[Exploring the dependencies of a repository](/code-se
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## Managing {% data variables.product.prodname_dependabot_alerts %}
|
||||
|
||||
{% data variables.product.prodname_dependabot_alerts %} are generated when {% data variables.product.prodname_dotcom %} identifies a dependency in the dependency graph with a vulnerability. {% ifversion fpt or ghec %}You can enable {% data variables.product.prodname_dependabot_alerts %} for any repository.{% endif %}
|
||||
@@ -79,7 +79,7 @@ For more information, see "[About {% data variables.product.prodname_dependabot_
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
## Managing dependency review
|
||||
|
||||
Dependency review lets you visualize dependency changes in pull requests before they are merged into your repositories. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: 关于安全概述
|
||||
intro: 您可以在一个位置查看、筛选和排序组织或团队拥有的存储库的安全警报：“安全概述”页。
|
||||
permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for.
|
||||
permissions: '{% data reusables.security-center.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
redirect_from:
|
||||
- /code-security/security-overview/exploring-security-alerts
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: issue-4554
|
||||
ghae: '*'
|
||||
ghes: '>3.1'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -22,7 +22,7 @@ topics:
|
||||
shortTitle: 关于安全概述
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae-issue-4554 %}
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
{% data reusables.security-center.beta %}
|
||||
{% endif %}
|
||||
|
||||
@@ -69,7 +69,7 @@ shortTitle: 关于安全概述
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae-issue-6199 %}
|
||||
### 关于企业级安全性概述
|
||||
在企业级别，安全性概述显示企业的综合和存储库特定的安全信息。 您可以查看企业拥有的具有安全警报的存储库，也可以查看整个企业的所有 {% data variables.product.prodname_secret_scanning %} 警报。
|
||||
在企业级别，安全性概述显示企业的综合和存储库特定的安全信息。 You can view repositories owned by your enterprise that have security alerts, view all security alerts, or security feature-specific alerts from across your enterprise.
|
||||
|
||||
企业中组织的组织所有者和安全管理员对企业级安全概述的访问权限也有限。 他们只能查看他们具有完全访问权限的组织的存储库和警报。
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 筛选安全性概述中的警报
|
||||
intro: 使用筛选器查看特定类别的警报
|
||||
permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for.
|
||||
permissions: '{% data reusables.security-center.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
versions:
|
||||
ghae: issue-4554
|
||||
ghae: '*'
|
||||
ghes: '>3.1'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
@@ -17,7 +17,7 @@ topics:
|
||||
shortTitle: 筛选警报
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae-issue-4554 %}
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
{% data reusables.security-center.beta %}
|
||||
{% endif %}
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ intro: 在一个位置查看、排序和过滤整个组织的安全警报。
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: issue-4554
|
||||
ghae: '*'
|
||||
ghes: '>3.1'
|
||||
ghec: '*'
|
||||
topics:
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 查看安全性概述
|
||||
intro: 导航到安全概述中可用的不同视图
|
||||
permissions: Organization owners and security managers can access the security overview for organizations. Members of a team can see the security overview for repositories that the team has admin privileges for.
|
||||
permissions: '{% data reusables.security-center.permissions %}'
|
||||
product: '{% data reusables.gated-features.security-center %}'
|
||||
versions:
|
||||
ghae: issue-5503
|
||||
@@ -17,7 +17,7 @@ topics:
|
||||
shortTitle: 查看安全性概述
|
||||
---
|
||||
|
||||
{% ifversion ghes < 3.5 or ghae-issue-4554 %}
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
{% data reusables.security-center.beta %}
|
||||
{% endif %}
|
||||
|
||||
@@ -28,7 +28,8 @@ shortTitle: 查看安全性概述
|
||||
1. 要查看有关警报类型的汇总信息，请单击 **Show more（显示更多）**。 
|
||||
{% data reusables.organizations.filter-security-overview %}
|
||||
{% if security-overview-views %}
|
||||
1. 或者，也可以使用左侧边栏按安全功能筛选信息。 在每个页面上，您可以使用特定于每个功能的筛选器来微调搜索。 
|
||||
{% data reusables.organizations.security-overview-feature-specific-page %}
|
||||
|
||||
|
||||
## 查看整个组织中的警报
|
||||
|
||||
@@ -42,6 +43,9 @@ shortTitle: 查看安全性概述
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
|
||||
1. 在左侧边栏中，单击 {% octicon "shield" aria-label="The shield icon" %} **代码安全性**。
|
||||
{% if security-overview-feature-specific-alert-page %}
|
||||
{% data reusables.organizations.security-overview-feature-specific-page %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## 查看仓库的警报
|
||||
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Dependabot
|
||||
|
||||
@@ -6,7 +6,7 @@ shortTitle: 依赖项审查
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>= 3.2'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
|
||||
@@ -8,7 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
|
||||
@@ -7,7 +7,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: overview
|
||||
topics:
|
||||
|
||||
@@ -5,7 +5,7 @@ shortTitle: 配置依赖项审查
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>= 3.2'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -6,7 +6,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -12,7 +12,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -3,7 +3,7 @@ title: 了解您的软件供应链
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Dependency graph
|
||||
|
||||
@@ -5,7 +5,7 @@ shortTitle: Troubleshoot dependency graph
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
@@ -59,4 +59,4 @@ Yes, the dependency graph has two categories of limits:
|
||||
- "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)"
|
||||
- "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)"
|
||||
- "[Troubleshooting the detection of vulnerable dependencies](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
|
||||
- "[Troubleshooting {% data variables.product.prodname_dependabot %} errors](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %}
|
||||
|
||||
@@ -36,9 +36,7 @@ shortTitle: 关于模板
|
||||
通过议题表单，您可以使用 {% data variables.product.prodname_dotcom %} 表单架构创建具有 Web 表单字段的模板。 当贡献者使用议题表单打开议题时，表单输入将转换为标准 Markdown 议题评论。 您可以指定不同的输入类型并根据需要设置输入，以帮助贡献者打开仓库中可操作的议题。 更多信息请参阅“[为仓库配置议题模板](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms)”和“[议题表单的语法](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)”。
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
{% data reusables.repositories.issue-template-config %}更多信息请参阅“[为仓库配置议题模板](/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser)”。
|
||||
{% endif %}
|
||||
|
||||
议题模板存储在仓库的默认分支的隐藏目录 `.github/ISSUE_TEMPLATE` 中。 如果您在另一个分支中创建模板，协作者将无法使用。 议题模板文件名不区分大小写，并且需要 *.md* 扩展名。{% ifversion fpt or ghec %} 使用议题表单创建的议题模板需要 *.yml* 扩展名。{% endif %} {% data reusables.repositories.valid-community-issues %}
|
||||
|
||||
|
||||
@@ -21,12 +21,8 @@ shortTitle: 配置
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
|
||||
## 创建议题模板
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. 在“Features（功能）”部分的“Issues（议题）”下，单击 **Set up templates（设置模板）**。 
|
||||
@@ -62,7 +58,6 @@ shortTitle: 配置
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
## 配置模板选择器
|
||||
|
||||
{% data reusables.repositories.issue-template-config %}
|
||||
@@ -99,7 +94,6 @@ contact_links:
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose_commit_branch %}
|
||||
{% data reusables.files.propose_new_file %}
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
|
||||
@@ -89,7 +89,7 @@ shortTitle: 应用程序创建查询参数
|
||||
| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | 授予对[内容 API](/rest/reference/repos#contents) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 |
|
||||
| [`标星`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | 授予对[标星 API](/rest/reference/activity#starring) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 |
|
||||
| [`状态`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | 授予对[状态 API](/rest/reference/commits#commit-statuses) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。 |
|
||||
| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | 授予对[团队讨论 API](/rest/reference/teams#discussions) 和[团队讨论注释 API](/rest/reference/teams#discussion-comments) 的访问权限。 可以是以下项之一：`none`、`read` 或 `write`。{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `vulnerability_alerts` | 授予接收存储库中易受攻击的依赖项 {% data variables.product.prodname_dependabot_alerts %}。 请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)”以了解更多信息。 可以是以下项之一：`none` 或 `read`。{% endif %}
|
||||
| `关注` | 授予列出和更改用户订阅的仓库的权限。 可以是以下项之一：`none`、`read` 或 `write`。 |
|
||||
|
||||
|
||||
@@ -239,8 +239,8 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
|
||||
* [列出部署](/rest/reference/deployments#list-deployments)
|
||||
* [创建部署](/rest/reference/deployments#create-a-deployment)
|
||||
* [获取部署](/rest/reference/deployments#get-a-deployment){% ifversion fpt or ghes or ghae or ghec %}
|
||||
* [删除部署](/rest/reference/deployments#delete-a-deployment){% endif %}
|
||||
* [Get a deployment](/rest/reference/deployments#get-a-deployment)
|
||||
* [Delete a deployment](/rest/reference/deployments#delete-a-deployment)
|
||||
|
||||
#### 事件
|
||||
|
||||
@@ -422,14 +422,12 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
* [删除组织的预接收挂钩实施](/enterprise/user/rest/reference/enterprise-admin#remove-pre-receive-hook-enforcement-for-an-organization)
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
#### 组织团队项目
|
||||
|
||||
* [列出团队项目](/rest/reference/teams#list-team-projects)
|
||||
* [检查项目的团队权限](/rest/reference/teams#check-team-permissions-for-a-project)
|
||||
* [添加或更新团队项目权限](/rest/reference/teams#add-or-update-team-project-permissions)
|
||||
* [从团队删除项目](/rest/reference/teams#remove-a-project-from-a-team)
|
||||
{% endif %}
|
||||
|
||||
#### 组织团队仓库
|
||||
|
||||
@@ -575,7 +573,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
|
||||
#### 反应
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}* [删除反应](/rest/reference/reactions#delete-a-reaction-legacy){% else %}* [删除反应](/rest/reference/reactions#delete-a-reaction){% endif %}
|
||||
* [Delete a reaction](/rest/reference/reactions)
|
||||
* [列出提交注释的反应](/rest/reference/reactions#list-reactions-for-a-commit-comment)
|
||||
* [创建提交注释的反应](/rest/reference/reactions#create-reaction-for-a-commit-comment)
|
||||
* [列出议题的反应](/rest/reference/reactions#list-reactions-for-an-issue)
|
||||
@@ -587,13 +585,13 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
* [列出团队讨论注释的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion-comment)
|
||||
* [创建团队讨论注释的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion-comment)
|
||||
* [列出团队讨论的反应](/rest/reference/reactions#list-reactions-for-a-team-discussion)
|
||||
* [创建团队讨论的反应](/rest/reference/reactions#create-reaction-for-a-team-discussion){% ifversion fpt or ghes or ghae or ghec %}
|
||||
* [Create reaction for a team discussion](/rest/reference/reactions#create-reaction-for-a-team-discussion)
|
||||
* [删除提交注释反应](/rest/reference/reactions#delete-a-commit-comment-reaction)
|
||||
* [删除议题反应](/rest/reference/reactions#delete-an-issue-reaction)
|
||||
* [删除对提交注释的反应](/rest/reference/reactions#delete-an-issue-comment-reaction)
|
||||
* [删除拉取请求注释反应](/rest/reference/reactions#delete-a-pull-request-comment-reaction)
|
||||
* [删除团队讨论反应](/rest/reference/reactions#delete-team-discussion-reaction)
|
||||
* [删除团队讨论注释反应](/rest/reference/reactions#delete-team-discussion-comment-reaction){% endif %}
|
||||
* [Delete team discussion comment reaction](/rest/reference/reactions#delete-team-discussion-comment-reaction)
|
||||
|
||||
#### 仓库
|
||||
|
||||
@@ -707,11 +705,9 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre
|
||||
* [获取仓库自述文件](/rest/reference/repos#get-a-repository-readme)
|
||||
* [获取仓库许可](/rest/reference/licenses#get-the-license-for-a-repository)
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
#### 仓库事件调度
|
||||
|
||||
* [创建仓库调度事件](/rest/reference/repos#create-a-repository-dispatch-event)
|
||||
{% endif %}
|
||||
|
||||
#### 仓库挂钩
|
||||
|
||||
|
||||
@@ -333,7 +333,7 @@ http://127.0.0.1:1234/path
|
||||
|
||||
* "[对授权请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
|
||||
* "[对 OAuth 应用程序访问令牌请求错误进行故障排除](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
|
||||
* "[设备流错误](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 or ghec %}
|
||||
* "[设备流错误](#error-codes-for-the-device-flow)"{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
* "[令牌到期和撤销](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
@@ -84,7 +84,7 @@ Keep these ideas in mind when using personal access tokens:
|
||||
* You can perform one-off cURL requests.
|
||||
* You can run personal scripts.
|
||||
* Don't set up a script for your whole team or company to use.
|
||||
* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 or ghec %}
|
||||
* Don't set up a shared personal account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae or ghec %}
|
||||
* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %}
|
||||
|
||||
## Determining which integration to build
|
||||
|
||||
@@ -89,4 +89,4 @@ end
|
||||
|
||||
* **不建议**使用普通的 `==` 运算符。 像 [`secure_compare`][secure_compare] 这样的方法执行“恒定时间”字符串比较，这有助于减轻针对常规相等运算符的某些定时攻击。
|
||||
|
||||
[secure_compare]: https://rubydoc.info/github/rack/rack/master/Rack/Utils:secure_compare
|
||||
[secure_compare]: https://rubydoc.info/github/rack/rack/main/Rack/Utils:secure_compare
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -81,14 +81,10 @@ When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote reposit
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|
||||
## Cloning with {% data variables.product.prodname_cli %}
|
||||
|
||||
You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## Cloning with Subversion
|
||||
|
||||
|
||||
@@ -30,7 +30,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
|
||||
|
||||
- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %}
|
||||
{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
|
||||
- **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)."
|
||||
{% endif %}
|
||||
|
||||
@@ -113,4 +113,4 @@ For more information on starter workflows, see "[Setting up {% data variables.pr
|
||||
- "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise account](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)"
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
@@ -116,7 +116,6 @@ This example shows the {% data variables.product.prodname_discussions %} welcome
|
||||
This community maintainer started a discussion to welcome the community, and to ask members to introduce themselves. This post fosters an inviting atmosphere for visitors and contributors. The post also clarifies that the team's happy to help with contributions to the repository.
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
### Scenarios for team discussions
|
||||
|
||||
- I have a question that's not necessarily related to specific files in the repository.
|
||||
@@ -139,8 +138,6 @@ The `octocat` team member posted a team discussion, informing the team of variou
|
||||
- There is a blog post describing how the teams use {% data variables.product.prodname_actions %} to produce their docs.
|
||||
- Material about the April All Hands is now available for all team members to view.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Next steps
|
||||
|
||||
These examples showed you how to decide which is the best tool for your conversations on {% data variables.product.product_name %}. But this is only the beginning; there is so much more you can do to tailor these tools to your needs.
|
||||
|
||||
@@ -25,10 +25,13 @@ With {% data variables.product.prodname_mobile %} you can:
|
||||
- Read, review, and collaborate on issues and pull requests
|
||||
- Search for, browse, and interact with users, repositories, and organizations
|
||||
- Receive a push notification when someone mentions your username
|
||||
{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication{% endif %}
|
||||
{% ifversion fpt or ghec %}- Secure your GitHub.com account with two-factor authentication
|
||||
- Verify your sign in attempts on unrecognized devices{% endif %}
|
||||
|
||||
For more information about notifications for {% data variables.product.prodname_mobile %}, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#enabling-push-notifications-with-github-mobile)."
|
||||
|
||||
{% ifversion fpt or ghec %}- For more information on two-factor authentication using {% data variables.product.prodname_mobile %}, see "[Configuring {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-github-mobile) and [Authenticating using {% data variables.product.prodname_mobile %}](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication##verifying-with-github-mobile)." {% endif %}
|
||||
|
||||
## Installing {% data variables.product.prodname_mobile %}
|
||||
|
||||
To install {% data variables.product.prodname_mobile %} for Android or iOS, see [{% data variables.product.prodname_mobile %}](https://github.com/mobile).
|
||||
|
||||
@@ -28,11 +28,11 @@ versions:
|
||||
|
||||
## 站点快捷键
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <kbd>S</kbd> 或 <kbd>/</kbd> | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 |
|
||||
| <kbd>G</kbd> <kbd>N</kbd> | 转到您的通知。 更多信息请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。 |
|
||||
| <kbd>Esc</kbd> | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 |
|
||||
| 键盘快捷键 | 描述 |
|
||||
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <kbd>S</kbd> 或 <kbd>/</kbd> | 聚焦于搜索栏。 更多信息请参阅“[关于在 {% data variables.product.company_short %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。 |
|
||||
| <kbd>G</kbd> <kbd>N</kbd> | 转到您的通知。 更多信息请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”。 |
|
||||
| <kbd>Esc</kbd> | 当聚焦于用户、议题或拉取请求悬停卡时，关闭悬停卡并重新聚焦于悬停卡所在的元素 |
|
||||
|
||||
{% if command-palette %}
|
||||
|
||||
@@ -106,7 +106,6 @@ versions:
|
||||
{% endif %}
|
||||
| <kbd>R</kbd> | 在您的回复中引用所选的文本。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax#quoting-text)”。 |
|
||||
|
||||
|
||||
## 议题和拉取请求列表
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
@@ -135,16 +134,15 @@ versions:
|
||||
|
||||
## 拉取请求中的更改
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <kbd>C</kbd> | 在拉取请求中打开提交列表 |
|
||||
| <kbd>T</kbd> | 在拉取请求中打开已更改文件列表 |
|
||||
| <kbd>J</kbd> | 将所选内容在列表中向下移动 |
|
||||
| <kbd>K</kbd> | 将所选内容在列表中向上移动 |
|
||||
| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | 添加一条有关拉取请求差异的评论 |
|
||||
| <kbd>Alt</kbd> 并单击 | 通过按下 <kbd>Alt</kbd> 并单击 **Show outdated（显示已过期）**或 **Hide outdated（隐藏已过期）**，在折叠和展开拉取请求中所有过期的审查评论之间切换。{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| 单击，然后按住 <kbd>Shift</kbd> 并单击 | 单击一个行号，按住 <kbd>Shift</kbd>，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)。”
|
||||
{% endif %}
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <kbd>C</kbd> | 在拉取请求中打开提交列表 |
|
||||
| <kbd>T</kbd> | 在拉取请求中打开已更改文件列表 |
|
||||
| <kbd>J</kbd> | 将所选内容在列表中向下移动 |
|
||||
| <kbd>K</kbd> | 将所选内容在列表中向上移动 |
|
||||
| <kbd>Command</kbd>+<kbd>Shift</kbd>+<kbd>Enter</kbd> | 添加一条有关拉取请求差异的评论 |
|
||||
| <kbd>Alt</kbd> 并单击 | Toggle between collapsing and expanding all outdated review comments in a pull request by holding down <kbd>Alt</kbd> and clicking **Show outdated** or **Hide outdated**. |
|
||||
| 单击，然后按住 <kbd>Shift</kbd> 并单击 | 单击一个行号，按住 <kbd>Shift</kbd>，然后单击另一行号，便可对拉取请求的多行发表评论。 更多信息请参阅“[评论拉取请求](/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#adding-line-comments-to-a-pull-request)”。 |
|
||||
|
||||
## 项目板
|
||||
|
||||
@@ -200,7 +198,7 @@ versions:
|
||||
{% endif %}
|
||||
|
||||
## 通知
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ----------------------------- | ----- |
|
||||
| <kbd>E</kbd> | 标记为完成 |
|
||||
@@ -208,13 +206,6 @@ versions:
|
||||
| <kbd>Shift</kbd>+<kbd>I</kbd> | 标记为已读 |
|
||||
| <kbd>Shift</kbd>+<kbd>M</kbd> | 取消订阅 |
|
||||
|
||||
{% else %}
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ------------------------------------------ | ----- |
|
||||
| <kbd>E</kbd> 或 <kbd>I</kbd> 或 <kbd>Y</kbd> | 标记为已读 |
|
||||
| <kbd>Shift</kbd>+<kbd>M</kbd> | 静音线程 |
|
||||
{% endif %}
|
||||
|
||||
## 网络图
|
||||
|
||||
|
||||
@@ -60,7 +60,6 @@ Gist supports mapping GeoJSON files. These maps are displayed in embedded gists,
|
||||
|
||||
Follow the steps below to create a gist.
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
{% note %}
|
||||
|
||||
You can also create a gist using the {% data variables.product.prodname_cli %}. For more information, see "[`gh gist create`](https://cli.github.com/manual/gh_gist_create)" in the {% data variables.product.prodname_cli %} documentation.
|
||||
@@ -68,7 +67,6 @@ You can also create a gist using the {% data variables.product.prodname_cli %}.
|
||||
Alternatively, you can drag and drop a text file from your desktop directly into the editor.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
1. Sign in to {% data variables.product.product_name %}.
|
||||
2. Navigate to your {% data variables.gists.gist_homepage %}.
|
||||
|
||||
@@ -29,7 +29,6 @@ shortTitle: 基本格式语法
|
||||
|
||||
|
||||
|
||||
|
||||
## 样式文本
|
||||
|
||||
您可以在评论字段和 `.md` 文件中以粗体、斜体或删除线的文字表示强调。
|
||||
@@ -235,7 +234,7 @@ git commit
|
||||
|
||||
## 提及人员和团队
|
||||
|
||||
您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 <kbd>@</kbd> 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的更多信息，请参阅{% ifversion fpt or ghes or ghae or ghec %}"[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”。
|
||||
您可以在 {% data variables.product.product_name %} 上提及人员或[团队](/articles/setting-up-teams/)，方法是键入 <kbd>@</kbd> 加上其用户名或团队名称。 这将触发通知并提请他们注意对话。 如果您在编辑的评论中提及某人的用户名或团队名称，该用户也会收到通知。 有关通知的详细信息，请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”。
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -296,7 +295,7 @@ git commit
|
||||
|
||||
通过在文本行之间留一个空白行，可创建新段落。
|
||||
|
||||
{% ifversion fpt or ghae-issue-5180 or ghes > 3.2 or ghec %}
|
||||
{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
|
||||
## 脚注
|
||||
|
||||
您可以使用此括号语法为您的内容添加脚注：
|
||||
|
||||
@@ -15,7 +15,7 @@ topics:
|
||||
|
||||
## 将拉取请求链接到议题
|
||||
|
||||
要将拉取请求链接到议题以{% ifversion fpt or ghes or ghae or ghec %} 显示正在进行的修复，并且{% endif %} 当有人合并拉取请求时自动关闭议题，请键入以下关键字之一，然后引用议题。 例如 `Closes #10` 或 `Fixes octo-org/octo-repo#100`。
|
||||
To link a pull request to an issue to show that a fix is in progress and to automatically close the issue when someone merges the pull request, type one of the following keywords followed by a reference to the issue. 例如 `Closes #10` 或 `Fixes octo-org/octo-repo#100`。
|
||||
|
||||
* close
|
||||
* closes
|
||||
|
||||
@@ -30,8 +30,8 @@ shortTitle: 在板上筛选卡
|
||||
- 使用 `status:pending`、`status:success` 或 `status:failure` 按检查状态过滤
|
||||
- 使用 `type:issue`、`type:pr` 或 `type:note` 按类型过滤卡
|
||||
- 使用 `is:open`、`is:closed` 或 `is:merged` 和 `is:issue`、`is:pr` 或 `is:note` 按状态和类型过滤卡
|
||||
- 使用 `linked:pr` 关闭引用，按链接到拉取请求的议题过滤卡{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- 使用 `repo:ORGANIZATION/REPOSITORY` 在组织范围的项目板中按仓库过滤卡{% endif %}
|
||||
- Filter cards by issues that are linked to a pull request by a closing reference using `linked:pr`
|
||||
- 使用 `repo:ORGANIZATION/REPOSITORY` 在组织范围的项目板中按仓库过滤卡
|
||||
|
||||
1. 导航到包含要过滤的卡的项目板。
|
||||
2. 在项目卡列上方，单击“Filter cards（过滤卡）”搜索栏并键入搜索查询以过滤卡。 
|
||||
|
||||
@@ -22,7 +22,7 @@ topics:
|
||||
|
||||
议题让您可以在进行开发的 {% data variables.product.company_short %} 上跟踪您的工作。 当您在议题中提到另一个议题或拉取请求时，该议题的时间表会反映交叉参考，以便你能够跟踪相关的工作。 要表示工作正在进行中，您可以将议题链接到拉取请求。 当拉取请求合并时，链接的议题会自动关闭。
|
||||
|
||||
有关关键词的更多信息，请参阅“[将拉取请求链接到议题](issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)”。
|
||||
有关关键词的更多信息，请参阅“[将拉取请求链接到议题](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)”。
|
||||
|
||||
## 快速创建议题
|
||||
|
||||
@@ -36,7 +36,7 @@ topics:
|
||||
|
||||
## 保持更新
|
||||
|
||||
为保持更新议题中的最新评论，您可以订阅议题以接收关于最新评论的通知。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 更多信息请参阅 {% ifversion fpt or ghes or ghae or ghec %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}”[关于通知](/github/receiving-notifications-about-activity-on-github/about-notifications){% endif %}”和“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
|
||||
为保持更新议题中的最新评论，您可以订阅议题以接收关于最新评论的通知。 要快速查找指向您订阅的最新议题的链接，请访问仪表板。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
## 社区管理
|
||||
|
||||
|
||||
@@ -19,9 +19,9 @@ shortTitle: 分配议题和 PR
|
||||
|
||||
## 关于议题和拉取请求受理人
|
||||
|
||||
You can assign multiple people to each issue or pull request, including yourself, anyone who has commented on the issue or pull request, anyone with write permissions to the repository, and organization members with read permissions to the repository. 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
|
||||
每个议题和拉取请求可分配给多个人，包括您自己、 任何评论了议题或拉取请求的人、任何对仓库有写入权限的人以及对仓库有读取权限的组织成员 。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
|
||||
|
||||
Issues and pull requests in public repositories, and in private repositories for a paid account, can have up to 10 people assigned. Private repositories on the free plan are limited to one person per issue or pull request.
|
||||
公共仓库和付费帐户的私有仓库中的议题和拉取请求最多可以分配 10 个人。 免费计划中的私有仓库限制为每个议题或拉取请求一个人。
|
||||
|
||||
## 分配单个议题或拉取请求
|
||||
|
||||
|
||||
@@ -173,11 +173,9 @@ gh pr list --search "team:octo-org/octo-team"
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
对于议题，您还可以使用搜索来：
|
||||
|
||||
- 通过关闭引用过滤链接到拉取请求的议题：`linked:pr`
|
||||
{% endif %}
|
||||
|
||||
对于拉取请求，您还可以使用搜索来：
|
||||
- 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft`
|
||||
@@ -188,8 +186,8 @@ gh pr list --search "team:octo-org/octo-team"
|
||||
- 按[审查者](/articles/about-pull-request-reviews/)过滤拉取请求：`state:open type:pr reviewed-by:octocat`
|
||||
- 按[请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)的特定用户过滤拉取请求：`state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %}
|
||||
- 过滤有人直接要求您审核的拉取请求：`state:open type:pr user-review-requested:@me`{% endif %}
|
||||
- 按申请审查的团队过滤拉取请求：`state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`{% endif %}
|
||||
- 按请求审查的团队过滤拉取请求：`state:open type:pr team-review-requested:github/atom`
|
||||
- 过滤链接到拉取请求可能关闭的议题的拉取请求：`linked:issue`
|
||||
|
||||
## 排序议题和拉取请求
|
||||
|
||||
@@ -211,7 +209,6 @@ gh pr list --search "team:octo-org/octo-team"
|
||||
|
||||
要清除您的排序选择，请单击 **Sort（排序）<**>**Newest（最新）**。
|
||||
|
||||
|
||||
## 共享过滤器
|
||||
|
||||
当您过滤或排序议题和拉取请求时，浏览器的 URL 自动更新以匹配新视图。
|
||||
|
||||
@@ -27,7 +27,7 @@ shortTitle: 将 PR 链接到议题
|
||||
|
||||
## 关于链接的议题和拉取请求
|
||||
|
||||
您可以{% ifversion fpt or ghes or ghae or ghec %}手动或{% endif %}使用拉取请求说明中支持的关键词将议题链接到拉取请求。
|
||||
You can link an issue to a pull request manually or using a supported keyword in the pull request description.
|
||||
|
||||
当您将拉取请求链接到拉取请求指向的议题，如果有人正在操作该议题，协作者可以看到。
|
||||
|
||||
@@ -57,11 +57,10 @@ shortTitle: 将 PR 链接到议题
|
||||
| 不同仓库中的议题 | *KEYWORD* *OWNER*/*REPOSITORY*#*ISSUE-NUMBER* | `Fixes octo-org/octo-repo#100` |
|
||||
| 多个议题 | 对每个议题使用完整语法 | `Resolves #10, resolves #123, resolves octo-org/octo-repo#100` |
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}只有手动链接的拉取请求才能手动取消链接。 要取消链接您使用关键词链接的议题，必须编辑拉取请求说明以删除该关键词。{% endif %}
|
||||
Only manually linked pull requests can be manually unlinked. To unlink an issue that you linked using a keyword, you must edit the pull request description to remove the keyword.
|
||||
|
||||
您也可以在提交消息中使用关闭关键词。 议题将在提交合并到默认分支时关闭，但包含提交的拉取请求不会列为链接的拉取请求。
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
## 手动将拉取请求链接到议题
|
||||
|
||||
对仓库有写入权限的任何人都可以手动将拉取请求链接到议题。
|
||||
@@ -77,7 +76,6 @@ shortTitle: 将 PR 链接到议题
|
||||
4. 在右侧边栏中，单击 **Linked issues（链接的议题）**。 
|
||||
{% endif %}
|
||||
5. 单击要链接到拉取请求的议题。 
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
|
||||
@@ -25,4 +25,4 @@ type: how_to
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- {% ifversion fpt or ghes or ghae or ghec %}”[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching){% else %}”[列出您关注的仓库](/github/receiving-notifications-about-activity-on-github/listing-the-repositories-youre-watching){% endif %}"
|
||||
- "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions#reviewing-repositories-that-youre-watching)"
|
||||
|
||||
@@ -35,7 +35,7 @@ shortTitle: 组织仪表板
|
||||
|
||||
在消息馈送的“All activity（所有活动）”部分，您可以查看来自组织中其他团队和仓库的更新。
|
||||
|
||||
“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 更多信息请参阅{% ifversion fpt or ghes or ghae or ghec %}“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications){% else %}“[关注和取消关注仓库](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}”和“[关注人员](/articles/following-people)”。
|
||||
“All activity（所有活动）”部分显示组织中所有最近的活动，包括您未订阅的仓库中以及您未关注的人员的活动。 For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications)" and "[Following people](/articles/following-people)."
|
||||
|
||||
例如，当组织中有人执行以下操作时，组织消息馈送会显示更新：
|
||||
- 创建新分支。
|
||||
|
||||
@@ -32,7 +32,7 @@ topics:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”和“[关于 web 通知](/github/receiving-notifications-about-activity-on-github/about-web-notifications){% endif %}”。
|
||||
**提示：**根据通知设置，您将通过电子邮件和/或 {% data variables.product.product_name %} 上的 web 通知页面收到更新。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -40,7 +40,7 @@ topics:
|
||||
|
||||
要关闭团队讨论的通知，您可以取消订阅特定的讨论帖子，或者更改通知设置，以取消关注或完全忽略特定团队的讨论。 即使您取消关注团队的讨论，也可订阅特定讨论帖子的通知。
|
||||
|
||||
更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”和“[嵌套的团队](/articles/about-teams/#nested-teams)”。
|
||||
For more information, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)" and "[Nested teams](/articles/about-teams/#nested-teams)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
@@ -162,5 +162,5 @@ You can manage access to {% data variables.product.prodname_GH_advanced_security
|
||||
|
||||
- "[Securing your repository](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %}
|
||||
- "[About secret scanning](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %}
|
||||
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %}
|
||||
- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae %}
|
||||
- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %}
|
||||
|
||||
@@ -41,7 +41,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
|
||||
| [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.
|
||||
| [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
|
||||
| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
| [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
|
||||
@@ -61,8 +61,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`members_can_create_pages`](#members_can_create_pages-category-actions) | Contains all activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." | {% endif %}
|
||||
| [`org`](#org-category-actions) | Contains activities related to organization membership.{% ifversion ghec %}
|
||||
| [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %}
|
||||
| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %}
|
||||
| [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}
|
||||
| [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.
|
||||
| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.
|
||||
| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %}
|
||||
| [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}
|
||||
@@ -75,7 +75,7 @@ To search for specific events, use the `action` qualifier in your query. Actions
|
||||
| [`repository_dependency_graph`](#repository_dependency_graph-category-actions) | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae or ghec %}
|
||||
| [`repository_secret_scanning`](#repository_secret_scanning-category-actions) | Contains repository-level activities related to secret scanning. For more information, see "[About secret scanning](/github/administering-a-repository/about-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %}
|
||||
| [`repository_secret_scanning_custom_pattern`](#respository_secret_scanning_custom_pattern-category-actions) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% if secret-scanning-audit-log-custom-patterns %}
|
||||
| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| [`repository_secret_scanning_push_protection`](#respository_secret_scanning_push_protection) | Contains repository-level activities related to secret scanning custom patterns. For more information, see "[Protecting pushes with secert scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| [`repository_vulnerability_alert`](#repository_vulnerability_alert-category-actions) | Contains all activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).{% endif %}{% ifversion fpt or ghec %}
|
||||
| [`repository_vulnerability_alerts`](#repository_vulnerability_alerts-category-actions) | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}.{% endif %}{% if custom-repository-roles %}
|
||||
| [`role`](#role-category-actions) | Contains all activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).{% endif %}{% ifversion ghes or ghae or ghec %}
|
||||
@@ -236,7 +236,7 @@ An overview of some of the most common actions that are recorded as events in th
|
||||
| `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
|
||||
{% ifversion fpt or ghec or ghes > 3.2 or ghae %}
|
||||
### `dependabot_alerts` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -497,7 +497,6 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| `delete` | Triggered when a custom pattern is removed from secret scanning in an organization. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)."
|
||||
|
||||
{% endif %}
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
### `organization_label` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -506,8 +505,6 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| `update` | Triggered when a default label is edited.
|
||||
| `destroy` | Triggered when a default label is deleted.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### `oauth_application` category actions
|
||||
|
||||
| Action | Description
|
||||
@@ -572,11 +569,10 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| `update_required_status_checks_enforcement_level ` | Triggered when enforcement of required status checks is updated on a branch.
|
||||
| `update_strict_required_status_checks_policy` | Triggered when the requirement for a branch to be up to date before merging is changed.
|
||||
| `rejected_ref_update ` | Triggered when a branch update attempt is rejected.
|
||||
| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| `policy_override ` | Triggered when a branch protection requirement is overridden by a repository administrator.
|
||||
| `update_allow_force_pushes_enforcement_level ` | Triggered when force pushes are enabled or disabled for a protected branch.
|
||||
| `update_allow_deletions_enforcement_level ` | Triggered when branch deletion is enabled or disabled for a protected branch.
|
||||
| `update_linear_history_requirement_enforcement_level ` | Triggered when required linear commit history is enabled or disabled for a protected branch.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
|
||||
@@ -707,7 +703,7 @@ For more information, see "[Managing the publication of {% data variables.produc
|
||||
| `disable` | Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "[Protecting pushes with secret scanning](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
|
||||
| `enable` | Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository.
|
||||
|
||||
{% endif %}{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
{% endif %}{% ifversion fpt or ghes or ghae or ghec %}
|
||||
### `repository_vulnerability_alert` category actions
|
||||
|
||||
| Action | Description
|
||||
|
||||
@@ -158,25 +158,25 @@ shortTitle: 存储库角色
|
||||
|
||||
在本节中，您可以找到一些安全功能所需的访问权限，例如 {% data variables.product.prodname_advanced_security %} 功能。
|
||||
|
||||
| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 |
|
||||
|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae-issue-4864 or ghec %}
|
||||
| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **X** |
|
||||
| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}<!--Not available for FPT-->
|
||||
| 仓库操作 | 读取 | 分类 | 写入 | 维护 | 管理员 |
|
||||
|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:------------------------------------------------------:|:------------------------------------------------------:|:-------------------------------------------------------------------------------------------------:|{% ifversion fpt or ghes or ghae or ghec %}
|
||||
| 接收仓库中[易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies) | | | | | **X** |
|
||||
| [忽略 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %}<!--Not available for FPT-->
|
||||
|
|
||||
| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
|
||||
| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
|
||||
| [指定其他人员或团队接收安全警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}
|
||||
| 创建[安全通告](/code-security/security-advisories/about-github-security-advisories) | | | | | **X** |{% endif %}{% ifversion ghes or ghae or ghec %} <!--Not available for FPT-->
|
||||
|
|
||||
| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
|
||||
| 管理 {% data variables.product.prodname_GH_advanced_security %} 功能的访问权限（请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”） | | | | | **X** |{% endif %}{% ifversion fpt or ghec %}<!--Set at site-level for GHES and GHAE-->
|
||||
|
|
||||
| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae-issue-4864 or ghec %}
|
||||
| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X**
|
||||
| 为私有仓库[启用依赖关系图](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository) | | | | | **X** |{% endif %}{% ifversion ghes > 3.1 or ghae or ghec %}
|
||||
| [查看依赖项审查](/code-security/supply-chain-security/about-dependency-review) | **X** | **X** | **X** | **X** | **X**
|
||||
{% endif %}
|
||||
| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** |
|
||||
| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |
|
||||
| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% ifversion ghes or ghae or ghec %}<!--Not available for FPT-->
|
||||
| [查看拉取请求上的 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/triaging-code-scanning-alerts-in-pull-requests) | **X** | **X** | **X** | **X** | **X** |
|
||||
| [列出、忽略和删除 {% data variables.product.prodname_code_scanning %} 警报](/github/finding-security-vulnerabilities-and-errors-in-your-code/managing-code-scanning-alerts-for-your-repository) | | | **X** | **X** | **X** |
|
||||
| [查看仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% ifversion ghes or ghae or ghec %}<!--Not available for FPT-->
|
||||
|
|
||||
| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae-issue-4864 or ghec %}
|
||||
| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X**
|
||||
| [解决、撤销或重新打开 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-alerts-from-secret-scanning) | | | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X**{% ifversion not ghae %}<sup>[1]</sup>{% endif %} | **X** |{% endif %}{% ifversion ghes or ghae or ghec %}
|
||||
| [指定其他人员或团队接收仓库中的 {% data variables.product.prodname_secret_scanning %} 警报](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) | | | | | **X**
|
||||
{% endif %}
|
||||
|
||||
[1] 仓库作者和维护者只能看到他们自己提交的警报信息。
|
||||
|
||||
@@ -28,7 +28,7 @@ permissions: Organization owners can assign the security manager role.
|
||||
其他功能（包括组织的安全概述）在将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_advanced_security %} 一起使用的组织中可用。 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization)。
|
||||
{% endif %}
|
||||
|
||||
如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)."{% else %}."{% endif %}
|
||||
如果团队具有安全管理员角色，则对团队和特定存储库具有管理员访问权限的人员可以更改团队对该存储库的访问级别，但不能删除访问权限。 更多信息请参阅“[管理团队对组织存储库的访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository){% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5974 %}”和“[管理有权访问存储库的团队和人员](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)”。{% else %}”。{% endif %}
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -146,7 +146,7 @@ shortTitle: 组织中的角色
|
||||
{% endif %}
|
||||
| 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”） | **X** | | | | |
|
||||
|
||||
{% elsif ghes > 3.2 or ghae-issue-4999 %}
|
||||
{% elsif ghes > 3.2 or ghae %}
|
||||
<!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
|
||||
|
||||
| 组织操作 | 所有者 | 成员 | 安全管理员 |
|
||||
|
||||
@@ -31,11 +31,10 @@ permissions: Organization owners can promote team members to team maintainers.
|
||||
- [删除团队讨论](/articles/managing-disruptive-comments/#deleting-a-comment)
|
||||
- [添加组织成员到团队](/articles/adding-organization-members-to-a-team)
|
||||
- [从团队中删除组织成员](/articles/removing-organization-members-from-a-team)
|
||||
- 删除团队对仓库的访问权限{% ifversion fpt or ghes or ghae or ghec %}
|
||||
- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% endif %}{% ifversion fpt or ghec %}
|
||||
- 删除团队对仓库的访问权限
|
||||
- [管理团队的代码审查任务](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team){% ifversion fpt or ghec %}
|
||||
- [管理拉取请求的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team){% endif %}
|
||||
|
||||
|
||||
## 将组织成员升级为团队维护员
|
||||
|
||||
在将组织成员提升为团队维护员之前，该人员必须已经是团队的成员。
|
||||
|
||||
@@ -1,7 +1,34 @@
|
||||
---
|
||||
title: GitHub Pages 文档
|
||||
shortTitle: GitHub Pages
|
||||
intro: '您可以直接从 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的仓库创建网站。'
|
||||
intro: 'Learn how to create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. Explore website building tools like Jekyll and troubleshoot issues with your {% data variables.product.prodname_pages %} site.'
|
||||
introLinks:
|
||||
quickstart: /pages/quickstart
|
||||
overview: /pages/getting-started-with-github-pages/about-github-pages
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site
|
||||
- /pages/getting-started-with-github-pages/creating-a-github-pages-site
|
||||
- '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site{% endif %}'
|
||||
- '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll{% endif %}'
|
||||
- '{% ifversion ghec %}/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site{% endif %}'
|
||||
- '{% ifversion fpt %}/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser{% endif %}'
|
||||
- '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll{% endif %}'
|
||||
popular:
|
||||
- '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages{% endif %}'
|
||||
- /pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)
|
||||
- '{% ifversion fpt or ghec %}/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages{% endif %}'
|
||||
- '{% ifversion fpt or ghec %}/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https{% endif %}'
|
||||
- '{% ifversion ghes or ghae %}/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site{% endif %}'
|
||||
- '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll{% endif %}'
|
||||
- '{% ifversion ghes or ghae %}/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll{% endif %}'
|
||||
guideCards:
|
||||
- /pages/getting-started-with-github-pages/creating-a-custom-404-page-for-your-github-pages-site
|
||||
- /pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll
|
||||
- /pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites
|
||||
changelog:
|
||||
label: pages
|
||||
layout: product-landing
|
||||
redirect_from:
|
||||
- /categories/20/articles
|
||||
- /categories/95/articles
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 更改拉取请求的阶段
|
||||
intro: '您可以将拉取请求草稿标记为可供审查{% ifversion fpt or ghae or ghes or ghec %}或将拉取请求转换为草稿{% endif %}。'
|
||||
intro: You can mark a draft pull request as ready for review or convert a pull request to a draft.
|
||||
permissions: People with write permissions to a repository and pull request authors can change the stage of a pull request.
|
||||
product: '{% data reusables.gated-features.draft-prs %}'
|
||||
redirect_from:
|
||||
@@ -22,20 +22,16 @@ shortTitle: 更改状态
|
||||
|
||||
{% data reusables.pull_requests.mark-ready-review %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
{% tip %}
|
||||
|
||||
**提示**：您也可以使用 {% data variables.product.prodname_cli %} 将拉取请求标记为可供审查。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh pr 准备`](https://cli.github.com/manual/gh_pr_ready)”。
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
2. 在“Pull Requests（拉取请求）”列表中，单击要标记为可供审查的拉取请求。
|
||||
3. 在合并框中，单击 **Ready for review（可供审查）**。 
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
|
||||
## 将拉取请求转换为草稿
|
||||
|
||||
您可以随时将拉取请求转换为草稿。 例如，如果您意外打开了拉取请求而不是草稿，或者收到了需要解决的关于拉取请求的反馈，则可将拉取请求转换为草稿，以表示需要进一步更改。 再次将拉取请求标记为可供审查之前，任何人都不能合并拉取请求。 将拉取请求转换为草稿时，已订阅拉取请求通知的用户将不会取消订阅。
|
||||
@@ -45,8 +41,6 @@ shortTitle: 更改状态
|
||||
3. 在右侧边栏中的“Reviewers（审查者）”下下单击 **Convert to draft（转换为草稿）**。 
|
||||
4. 单击 **Convert to draft（转换为草稿）**。 
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于拉取请求](/github/collaborating-with-issues-and-pull-requests/about-pull-requests)"
|
||||
|
||||
@@ -21,7 +21,7 @@ shortTitle: 请求 PR 审查
|
||||
|
||||
要将审阅者分配给拉取请求，您需要对存储库具有写入权限。 有关仓库访问权限的更多信息，请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)”。 如果您具有写入权限，则可以将具有读取访问权限的任何人分配到存储库作为审阅者。
|
||||
|
||||
具有写入权限的组织成员还可以将拉取请求审阅分配给对存储库具有读取访问权限的任何人员或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% ifversion fpt or ghae or ghes or ghec %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。{% endif %}
|
||||
具有写入权限的组织成员还可以将拉取请求审阅分配给对存储库具有读取访问权限的任何人员或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ shortTitle: 关于 PR 审查
|
||||
|
||||
{% if pull-request-approval-limit %}{% data reusables.pull_requests.code-review-limits %}{% endif %}
|
||||
|
||||
仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)”。 {% ifversion fpt or ghae or ghes or ghec %}您可以指定自动分配一部分团队成员，而不是分配整个团队。 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。{% endif %}
|
||||
仓库所有者和协作者可向具体的个人申请拉取请求审查。 组织成员也可向具有仓库读取权限的团队申请拉取请求审查。 更多信息请参阅“[申请拉取请求审查](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)”。 You can specify a subset of team members to be automatically assigned in the place of the whole team. 更多信息请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。
|
||||
|
||||
审查允许讨论提议的更改，帮助确保更改符合仓库的参与指南及其他质量标准。 您可以在 CODEOWNERS 文件中定义哪些个人或团队拥有代码的特定类型或区域。 当拉取请求修改定义了所有者的代码时，该个人或团队将自动被申请为审查者。 更多信息请参阅“[关于代码所有者](/articles/about-code-owners/)”。
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.dependency-review %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>= 3.2'
|
||||
ghae: issue-4864
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
|
||||
@@ -31,9 +31,9 @@ versions:
|
||||
|
||||
## 比较标记
|
||||
|
||||
比较发行版标记将显示自上次发布以来您对仓库的更改。 {% ifversion fpt or ghae or ghes or ghec %} 更多信息请参阅“[比较发行版](/github/administering-a-repository/comparing-releases)”。{% endif %}
|
||||
比较发行版标记将显示自上次发布以来您对仓库的更改。 For more information, see "[Comparing releases](/github/administering-a-repository/comparing-releases)."
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}要比较标记，可以从页面顶部的 `compare` 下拉菜单选择标记名称。{% else %} 不是键入分支名称，而是键入 `compare` 下拉菜单中的标记名称。{% endif %}
|
||||
To compare tags, you can select a tag name from the `compare` drop-down menu at the top of the page.
|
||||
|
||||
此处是[在两个标记之间进行比较](https://github.com/octocat/linguist/compare/v2.2.0...octocat:v2.3.3)的示例。
|
||||
|
||||
|
||||
@@ -27,8 +27,7 @@ shortTitle: 关于合并方法
|
||||
|
||||
{% data reusables.pull_requests.default_merge_option %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。{% endif %}
|
||||
默认合并方法创建合并提交。 通过强制实施线性提交历史记录，可以防止任何人将合并提交推送到受保护分支。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/about-protected-branches#require-linear-history)”。
|
||||
|
||||
## 压缩合并提交
|
||||
|
||||
|
||||
@@ -37,14 +37,11 @@ remote: error: Required status check "ci-build" is failing
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
|
||||
## 头部提交与测试合并提交之间的冲突
|
||||
|
||||
有时，测试合并提交与头部提交的状态检查结果存在冲突。 如果测试合并提交具有状态，则测试合并提交必须通过。 否则，必须传递头部提交的状态后才可合并该分支。 有关测试合并提交的更多信息，请参阅“[拉取](/rest/reference/pulls#get-a-pull-request)”。
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 处理已跳过但需要检查
|
||||
|
||||
|
||||
@@ -26,17 +26,15 @@ topics:
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
{% tip %}
|
||||
|
||||
**提示**：您也可以使用 {% data variables.product.prodname_cli %} 创建仓库。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 仓库创建`](https://cli.github.com/manual/gh_repo_create)”。
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. （可选）要创建具有现有仓库的目录结构和文件的仓库，请使用 **Choose a template（选择模板）**下拉菜单并选择一个模板仓库。 您将看到由您和您所属组织拥有的模板仓库，或者您以前使用过的模板仓库。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 {% ifversion fpt or ghae or ghes or ghec %}
|
||||
3. （可选）如果您选择使用模板，要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 {% endif %}
|
||||
2. （可选）要创建具有现有仓库的目录结构和文件的仓库，请使用 **Choose a template（选择模板）**下拉菜单并选择一个模板仓库。 您将看到由您和您所属组织拥有的模板仓库，或者您以前使用过的模板仓库。 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。 
|
||||
3. （可选）如果您选择使用模板，要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 
|
||||
3. 在“Owner（所有者）”下拉菜单中，选择要在其上创建仓库的帐户。 
|
||||
{% data reusables.repositories.repo-name %}
|
||||
{% data reusables.repositories.choose-repo-visibility %}
|
||||
|
||||
@@ -19,17 +19,13 @@ shortTitle: 从模板创建
|
||||
|
||||
任何对模板仓库具有读取权限的人都可以从该模板创建仓库。 更多信息请参阅“[创建模板仓库](/articles/creating-a-template-repository)”。
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
{% tip %}
|
||||
|
||||
**提示**：您也可以使用 {% data variables.product.prodname_cli %} 从模板创建仓库。 更多信息请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh 仓库创建`](https://cli.github.com/manual/gh_repo_create)”。
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。 从模板创建的分支具有不相关的历史记录，这意味着您无法创建拉取请求或在分支之间合并。
|
||||
{% endif %}
|
||||
|
||||
从模板创建仓库类似于创建仓库的复刻，但存在一些重要差异：
|
||||
- 新的复刻包含父仓库的整个提交历史记录，而从模板创建的仓库从一个提交开始记录。
|
||||
@@ -44,7 +40,7 @@ shortTitle: 从模板创建
|
||||
2. 在文件列表上方，单击 **Use this template（使用此模板）**。 
|
||||
{% data reusables.repositories.owner-drop-down %}
|
||||
{% data reusables.repositories.repo-name %}
|
||||
{% data reusables.repositories.choose-repo-visibility %}{% ifversion fpt or ghae or ghes or ghec %}
|
||||
6. （可选）要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 {% endif %}
|
||||
{% data reusables.repositories.choose-repo-visibility %}
|
||||
6. （可选）要包括模板中所有分支的目录结构和文件，而不仅仅是默认分支，请选择 **Include all branches（包括所有分支）**。 
|
||||
{% data reusables.repositories.select-marketplace-apps %}
|
||||
8. 单击 **Create repository from template（从模板创建仓库）**。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 创建模板仓库
|
||||
intro: '您可以将现有仓库设置为模板，以便您与其他人能够生成目录结构相同的新仓库{% ifversion fpt or ghae or ghes or ghec %}、分支{% endif %} 和文件。'
|
||||
intro: 'You can make an existing repository a template, so you and others can generate new repositories with the same directory structure, branches, and files.'
|
||||
permissions: Anyone with admin permissions to a repository can make the repository a template.
|
||||
redirect_from:
|
||||
- /articles/creating-a-template-repository
|
||||
@@ -24,7 +24,7 @@ shortTitle: 创建模板仓库
|
||||
|
||||
要创建模板仓库，必须先创建一个仓库，然后将该仓库设置为模板。 关于创建仓库的更多信息，请参阅“[创建新仓库](/articles/creating-a-new-repository)”。
|
||||
|
||||
将仓库设置为模板后，有权访问仓库的任何人都可以生成与默认分支具有相同目录结构和文件的新仓库。{% ifversion fpt or ghae or ghes or ghec %} 他们还可以选择包含您的仓库中的所有其他分支。 从模板创建的分支具有不相关的历史记录，因此您无法创建拉取请求或在分支之间合并。{% endif %} 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。
|
||||
After you make your repository a template, anyone with access to the repository can generate a new repository with the same directory structure and files as your default branch. They can also choose to include all the other branches in your repository. Branches created from a template have unrelated histories, so you cannot create pull requests or merge between the branches. 更多信息请参阅“[从模板创建仓库](/articles/creating-a-repository-from-a-template)”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
|
||||
@@ -31,7 +31,7 @@ shortTitle: 用于推送的电子邮件通知
|
||||
- 作为提交一部分所更改的文件
|
||||
- 提交消息
|
||||
|
||||
您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications){% else %}”[关于通知电子邮件](/github/receiving-notifications-about-activity-on-github/about-email-notifications)”。 您还可以对推送关闭电子邮件通知。 更多信息请参阅“[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications){% endif %}”。
|
||||
您可以过滤因推送到仓库而收到的电子邮件通知。 更多信息请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)”。
|
||||
|
||||
## 对推送到仓库启用电子邮件通知
|
||||
|
||||
@@ -43,10 +43,5 @@ shortTitle: 用于推送的电子邮件通知
|
||||
7. 单击 **Setup notifications（设置通知）**。 
|
||||
|
||||
## 延伸阅读
|
||||
{% ifversion fpt or ghae or ghes or ghec %}
|
||||
- "[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)"
|
||||
{% else %}
|
||||
- "[关于通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-notifications)"
|
||||
- "[选择通知的递送方式](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)"
|
||||
- "[关于电子邮件通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-email-notifications)"
|
||||
- "[关于 web 通知](/enterprise/{{ currentVersion }}/user/github/receiving-notifications-about-activity-on-github/about-web-notifications)"{% endif %}
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user