New translation batch for cn (#29409)
* Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report Co-authored-by: Robert Sese <734194+rsese@users.noreply.github.com>
This commit is contained in:
docubot
@@ -16,7 +16,6 @@ translations/zh-CN/content/actions/hosting-your-own-runners/adding-self-hosted-r
|
||||
translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/removing-workflow-artifacts.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/reviewing-deployments.md,Listed in localization-support#489
|
||||
translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md,broken liquid tags
|
||||
@@ -159,7 +158,9 @@ translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scannin
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md,rendering error
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-dependabot-alerts.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/dependabot/index.md,broken liquid tags
|
||||
@@ -213,10 +214,10 @@ translations/zh-CN/content/developers/overview/secret-scanning-partner-program.m
|
||||
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/discussions/quickstart.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
|
||||
translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/index.md,broken liquid tags
|
||||
translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md,broken liquid tags
|
||||
translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom.md,broken liquid tags
|
||||
@@ -267,6 +268,7 @@ translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.m
|
||||
translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/quickstart.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
|
||||
@@ -374,6 +376,7 @@ translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph-
|
||||
translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dependency-submission/about-dependency-submission.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/education/access-github-community-exchange.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
|
||||
translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md,broken liquid tags
|
||||
@@ -383,7 +386,7 @@ translations/zh-CN/data/reusables/enterprise_installation/hardware-consideration
|
||||
translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/packages.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags
|
||||
@@ -406,9 +409,9 @@ translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-
|
||||
translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_repositories_warning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/select-marketplace-apps.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/saml-session-oauth.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/saml-session-oauth.md,rendering error
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
|
||||
translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md,broken liquid tags
|
||||
|
||||
|
@@ -51,6 +51,8 @@ shortTitle: 构建和测试 Java & Gradle
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Java CI
|
||||
|
||||
on: [push]
|
||||
|
||||
@@ -380,6 +380,8 @@ jobs:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Upload Python Package
|
||||
|
||||
on:
|
||||
|
||||
@@ -38,6 +38,8 @@ shortTitle: 构建和测试Ruby
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Ruby
|
||||
|
||||
on:
|
||||
@@ -102,6 +104,8 @@ strategy:
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Ruby CI
|
||||
|
||||
on:
|
||||
@@ -206,6 +210,8 @@ steps:
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Matrix Testing
|
||||
|
||||
on:
|
||||
@@ -239,6 +245,8 @@ jobs:
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Linting
|
||||
|
||||
on: [push]
|
||||
@@ -265,6 +273,8 @@ jobs:
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Ruby Gem
|
||||
|
||||
on:
|
||||
|
||||
@@ -68,8 +68,12 @@ jobs:
|
||||
您可以将作业配置为在矩阵中使用多个版本的 Swift。
|
||||
|
||||
```yaml{:copy}
|
||||
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
|
||||
name: Swift
|
||||
|
||||
on: [push]
|
||||
|
||||
@@ -92,6 +92,8 @@ Ensure that you provide your own values for all the variables in the `env` key o
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Deploy to Amazon ECS
|
||||
|
||||
on:
|
||||
|
||||
@@ -81,6 +81,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy a container to an Azure Web App
|
||||
|
||||
env:
|
||||
|
||||
@@ -67,6 +67,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy JAR app to Azure Web App
|
||||
|
||||
env:
|
||||
|
||||
@@ -66,6 +66,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy ASP.Net Core app to an Azure Web App
|
||||
|
||||
env:
|
||||
|
||||
@@ -72,6 +72,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
|
||||
@@ -66,6 +66,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy PHP app to Azure Web App
|
||||
|
||||
env:
|
||||
|
||||
@@ -69,6 +69,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy Python app to Azure Web App
|
||||
|
||||
env:
|
||||
|
||||
@@ -55,6 +55,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and deploy to Azure Kubernetes Service
|
||||
|
||||
env:
|
||||
|
||||
@@ -54,6 +54,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Deploy web app to Azure Static Web Apps
|
||||
|
||||
env:
|
||||
|
||||
@@ -137,6 +137,8 @@ Kustomize 是用于管理 YAML 规范的可选工具。 在创建 `kustomization
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Build and Deploy to GKE
|
||||
|
||||
on:
|
||||
|
||||
@@ -172,25 +172,27 @@ jobs:
|
||||
{% data reusables.actions.github-context-warning %}
|
||||
{% data reusables.actions.context-injection-warning %}
|
||||
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| -------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `github` | `对象` | 工作流程中任何作业或步骤期间可用的顶层上下文。 此对象包含下面列出的所有属性。 |
|
||||
| `github.action` | `字符串` | 当前运行的操作的名称，或步骤的 [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid)。 {% data variables.product.prodname_dotcom %} 将删除特殊字符，并在当前步骤运行没有 `id` 的脚本时使用名称 `__run`。 如果在同一作业中多次使用相同的操作，则名称将包含一个前面跟序号和下划线的后缀。 例如，运行的第一个脚本名称 `__run`，则第二个脚本将命名为 `__run_2`。 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 |
|
||||
| `github.action_path` | `字符串` | 操作所在的路径。 此属性仅在复合操作中受支持。 您可以使用此路径访问与操作位于同一存储库中的文件。 |
|
||||
| `github.action_ref` | `字符串` | 对于执行操作的步骤，这是正在执行的操作的引用。 例如 `v2`。 |
|
||||
| `github.action_repository` | `字符串` | 对于执行操作的步骤，这是操作的所有者和存储库名称。 例如 `actions/checkout`。 |
|
||||
| `github.action_status` | `字符串` | 对于复合操作，这是复合操作的当前结果。 |
|
||||
| `github.actor` | `字符串` | 发起工作流程运行的用户的用户名。 |
|
||||
| `github.api_url` | `字符串` | {% data variables.product.prodname_dotcom %} REST API 的 URL。 |
|
||||
| `github.base_ref` | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 |
|
||||
| `github.env` | `字符串` | 运行器上从工作流程命令到设置环境变量的文件路径。 此文件对于当前步骤是唯一的，并且是作业中每个步骤的不同文件。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)”。 |
|
||||
| `github.event` | `对象` | 完整事件 web 挂钩有效负载。 您可以使用上下文访问事件的个别属性。 此对象与触发工作流运行的事件的 web 挂钩有效负载相同，并且对于每个事件都是不同的。 每个 {% data variables.product.prodname_actions %} 事件的 web 挂钩都链接在“[触发工作流程](/articles/events-that-trigger-workflows/)”的事件中。 例如，对于由 [`push` 事件](/actions/using-workflows/events-that-trigger-workflows#push)触发的工作流程运行，此对象包含[push webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) 的内容。 |
|
||||
| `github.event_name` | `字符串` | 触发工作流程运行的事件的名称。 |
|
||||
| `github.event_path` | `字符串` | 运行器上包含完整事件 web 挂钩负载的文件的路径。 |
|
||||
| `github.graphql_url` | `字符串` | {% data variables.product.prodname_dotcom %} GraphQL API 的 URL。 |
|
||||
| `github.head_ref` | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 |
|
||||
| `github.job` | `字符串` | 当前作业的 [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 <br /> 注意：此上下文属性由 Actions 运行器设置，并且仅在作业的执行 `steps` 中可用。 否则，此属性的值将为 `null`。 |
|
||||
| `github.ref` | `字符串` | {% data reusables.actions.ref-description %}
|
||||
| 属性名称 | 类型 | 描述 |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `github` | `对象` | 工作流程中任何作业或步骤期间可用的顶层上下文。 此对象包含下面列出的所有属性。 |
|
||||
| `github.action` | `字符串` | 当前运行的操作的名称，或步骤的 [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid)。 {% data variables.product.prodname_dotcom %} 将删除特殊字符，并在当前步骤运行没有 `id` 的脚本时使用名称 `__run`。 如果在同一作业中多次使用相同的操作，则名称将包含一个前面跟序号和下划线的后缀。 例如，运行的第一个脚本名称 `__run`，则第二个脚本将命名为 `__run_2`。 同样，`actions/checkout` 第二次调用时将变成 `actionscheckout2`。 |
|
||||
| `github.action_path` | `字符串` | 操作所在的路径。 此属性仅在复合操作中受支持。 您可以使用此路径访问与操作位于同一存储库中的文件。 |
|
||||
| `github.action_ref` | `字符串` | 对于执行操作的步骤，这是正在执行的操作的引用。 例如 `v2`。 |
|
||||
| `github.action_repository` | `字符串` | 对于执行操作的步骤，这是操作的所有者和存储库名称。 例如 `actions/checkout`。 |
|
||||
| `github.action_status` | `字符串` | 对于复合操作，这是复合操作的当前结果。 |
|
||||
| `github.actor` | `字符串` | |
|
||||
| {% ifversion actions-stable-actor-ids %}The username of the user that triggered the initial workflow run. If the workflow run is a re-run, this value may differ from `github.triggering_actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges.{% else %}The username of the user that initiated the workflow run.{% endif %} | | |
|
||||
| | | |
|
||||
| `github.api_url` | `字符串` | {% data variables.product.prodname_dotcom %} REST API 的 URL。 |
|
||||
| `github.base_ref` | `字符串` | 工作流程运行中拉取请求的 `base_ref` 或目标分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 |
|
||||
| `github.env` | `字符串` | 运行器上从工作流程命令到设置环境变量的文件路径。 此文件对于当前步骤是唯一的，并且是作业中每个步骤的不同文件。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的工作流程命令](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)”。 |
|
||||
| `github.event` | `对象` | 完整事件 web 挂钩有效负载。 您可以使用上下文访问事件的个别属性。 此对象与触发工作流运行的事件的 web 挂钩有效负载相同，并且对于每个事件都是不同的。 每个 {% data variables.product.prodname_actions %} 事件的 web 挂钩都链接在“[触发工作流程](/articles/events-that-trigger-workflows/)”的事件中。 例如，对于由 [`push` 事件](/actions/using-workflows/events-that-trigger-workflows#push)触发的工作流程运行，此对象包含[push webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push) 的内容。 |
|
||||
| `github.event_name` | `字符串` | 触发工作流程运行的事件的名称。 |
|
||||
| `github.event_path` | `字符串` | 运行器上包含完整事件 web 挂钩负载的文件的路径。 |
|
||||
| `github.graphql_url` | `字符串` | {% data variables.product.prodname_dotcom %} GraphQL API 的 URL。 |
|
||||
| `github.head_ref` | `字符串` | 工作流程运行中拉取请求的 `head_ref` 或来源分支。 此属性仅在触发工作流程运行的事件为 `pull_request` 或 `pull_request_target` 时才可用。 |
|
||||
| `github.job` | `字符串` | 当前作业的 [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id)。 <br /> 注意：此上下文属性由 Actions 运行器设置，并且仅在作业的执行 `steps` 中可用。 否则，此属性的值将为 `null`。 |
|
||||
| `github.ref` | `字符串` | {% data reusables.actions.ref-description %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
|
||||
| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} | | `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} | | `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %}
|
||||
{%- endif %}
|
||||
@@ -198,7 +200,7 @@ jobs:
|
||||
{%- ifversion fpt or ghec or ghes > 3.5 or ghae-issue-4722 %}
|
||||
| `github.run_attempt` | `string` | 在存储库中运行的特定工作流程的每次尝试的唯一编号。 对于工作流程运行的第一次尝试，此数字从 1 开始，并随着每次重新运行而递增。 |
|
||||
{%- endif %}
|
||||
| `github.server_url` | `string` | GitHub 服务器的 URL。 例如：`https://github.com`。 | | `github.sha` | `string` | 触发工作流运行的提交 SHA。 | | `github.token` | `string` | 用于代表存储库上安装的 GitHub 应用进行身份验证的令牌。 这在功能上等同于 `GITHUB_TOKEN` 密码。 更多信息请参阅“[自动令牌身份验证](/actions/security-guides/automatic-token-authentication)”。 <br /> 注意：此上下文属性由 Actions 运行器设置，并且仅在作业的执行 `steps` 中可用。 否则，此属性的值将为 `null`。 | | `github.workflow` | `string` | 工作流程的名称。 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `string` | 运行器上步骤的默认工作目录，以及使用[`检出`](https://github.com/actions/checkout)操作时存储库的默认位置。 |
|
||||
| `github.server_url` | `string` | GitHub 服务器的 URL。 例如：`https://github.com`。 | | `github.sha` | `string` | 触发工作流运行的提交 SHA。 | | `github.token` | `string` | 用于代表存储库上安装的 GitHub 应用进行身份验证的令牌。 这在功能上等同于 `GITHUB_TOKEN` 密码。 更多信息请参阅“[自动令牌身份验证](/actions/security-guides/automatic-token-authentication)”。 <br /> 注意：此上下文属性由 Actions 运行器设置，并且仅在作业的执行 `steps` 中可用。 否则，此属性的值将为 `null`。 |{% ifversion actions-stable-actor-ids %} | `github.triggering_actor` | `string` | The username of the user that initiated the workflow run. If the workflow run is a re-run, this value may differ from `github.actor`. Any workflow re-runs will use the privileges of `github.actor`, even if the actor initiating the re-run (`github.triggering_actor`) has different privileges. |{% endif %} | `github.workflow` | `string` | The name of the workflow. 如果工作流程文件未指定 `name`，此属性的值将是仓库中工作流程文件的完整路径。 | | `github.workspace` | `string` | 运行器上步骤的默认工作目录，以及使用[`检出`](https://github.com/actions/checkout)操作时存储库的默认位置。 |
|
||||
|
||||
### `github` 上下文的示例内容
|
||||
|
||||
|
||||
@@ -32,6 +32,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
|
||||
|
||||
{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
|
||||
|
||||
name: Label issues
|
||||
on:
|
||||
issues:
|
||||
|
||||
@@ -33,6 +33,8 @@ shortTitle: 添加标签以评论议题
|
||||
```yaml{:copy}
|
||||
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
|
||||
|
||||
{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
|
||||
|
||||
name: Add comment
|
||||
on:
|
||||
issues:
|
||||
|
||||
@@ -34,6 +34,8 @@ shortTitle: 移动分配的议题
|
||||
```yaml{:copy}
|
||||
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
|
||||
|
||||
{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
|
||||
|
||||
name: Move assigned card
|
||||
on:
|
||||
issues:
|
||||
|
||||
@@ -30,10 +30,11 @@ shortTitle: 添加卡片时删除标签
|
||||
2. 选择属于仓库的项目。 此工作流程不能用于属于用户或组织的项目。 您可以使用现有项目，也可以创建新项目。 有关创建项目的更多信息，请参阅“[创建项目板](/github/managing-your-work-on-github/creating-a-project-board)”。
|
||||
3. {% data reusables.actions.make-workflow-file %}
|
||||
4. 将以下 YAML 内容复制到工作流程文件中。
|
||||
|
||||
```yaml{:copy}
|
||||
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
|
||||
|
||||
{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
|
||||
|
||||
name: Remove labels
|
||||
on:
|
||||
project_card:
|
||||
|
||||
@@ -32,6 +32,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}
|
||||
|
||||
{% indented_data_reference reusables.actions.actions-use-sha-pinning-comment spaces=4 %}
|
||||
|
||||
name: Weekly Team Sync
|
||||
on:
|
||||
schedule:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Re-running workflows and jobs
|
||||
intro: 'You can re-run a workflow run{% ifversion re-run-jobs %}, all failed jobs in a workflow run, or specific jobs in a workflow run{% endif %} up to 30 days after its initial run.'
|
||||
title: 重新运行工作流程和作业
|
||||
intro: '您可以工作流程运行初始运行后最长 30 天内重新运行工作流程运行{% ifversion re-run-jobs %}、工作流程运行中所有失败的作业或工作流程运行中的特定作业{% endif %}。'
|
||||
permissions: People with write permissions to a repository can re-run workflows in the repository.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
@@ -15,11 +15,11 @@ versions:
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About re-running workflows and jobs
|
||||
## 关于重新运行工作流程和作业
|
||||
|
||||
Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} uses the same `GITHUB_SHA` (commit SHA) and `GITHUB_REF` (Git ref) of the original event that triggered the workflow run. You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. For more information, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)."{% endif %}{% ifversion debug-reruns %} When you re-run a workflow or jobs in a workflow, you can enable debug logging for the re-run. This will enable runner diagnostic logging and step debug logging for the re-run. For more information about debug logging, see "[Enabling debug logging](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)."{% endif %}
|
||||
重新运行工作流程{% ifversion re-run-jobs %} 或工作流程中的作业{% endif %} 会使用触发工作流程运行的原始事件的 `GITHUB_SHA`（提交 SHA）和 `GITHUB_REF` (Git ref)。 {% ifversion actions-stable-actor-ids %}The workflow will use the privileges of the actor who initially triggered the workflow, not the privileges of the actor who initiated the re-run. {% endif %}You can re-run a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %} for up to 30 days after the initial run.{% ifversion re-run-jobs %} You cannot re-run jobs in a workflow once its logs have passed their retention limits. 更多信息请参阅“[使用限制、计费和管理](/actions/learn-github-actions/usage-limits-billing-and-administration#artifact-and-log-retention-policy)”。{% endif %}{% ifversion debug-reruns %} 当您重新运行工作流程或工作流程中的作业时，您可以为重新运行启用调试日志记录。 这将为重新运行启用运行程序诊断日志记录和步骤调试日志记录。 有关调试日志记录的更多信息，请参阅“[启用调试日志记录](/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging)”。{% endif %}
|
||||
|
||||
## Re-running all the jobs in a workflow
|
||||
## 重新运行工作流程中的所有作业
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -28,14 +28,12 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
|
||||
1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。
|
||||
|
||||
If no jobs failed, you will not see the **Re-run jobs** drop-down menu. Instead, click **Re-run all jobs**.
|
||||
|
||||
如果没有作业失败，您将不会看到 **重新运行作业（Re-run jobs）**下拉菜单。 相反，请单击 **Re-run all jobs（重新运行所有作业）**。 
|
||||
{% endif %}
|
||||
{% ifversion ghes < 3.5 or ghae %}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run all jobs**.
|
||||
|
||||
1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run all jobs（重新运行所有作业）**。 
|
||||
{% endif %}
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
@@ -45,7 +43,7 @@ Re-running a workflow{% ifversion re-run-jobs %} or jobs in a workflow{% endif %
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To re-run a failed workflow run, use the `run rerun` subcommand. Replace `run-id` with the ID of the failed run that you want to re-run. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
要重新运行失败的工作流程运行，请使用 `run rerun` 子命令。 将 `run-id` 替换为您想要重新运行的已失败运行的 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em>
|
||||
@@ -60,7 +58,7 @@ gh run rerun <em>run-id</em> --debug
|
||||
|
||||
{% endif %}
|
||||
|
||||
To view the progress of the workflow run, use the `run watch` subcommand and select the run from the interactive list.
|
||||
要查看工作流程运行的进度，请使用 `run watch` 子命令，并从交互式列表中选择运行。
|
||||
|
||||
```shell
|
||||
gh run watch
|
||||
@@ -69,9 +67,9 @@ gh run watch
|
||||
{% endcli %}
|
||||
|
||||
{% ifversion re-run-jobs %}
|
||||
## Re-running failed jobs in a workflow
|
||||
## 重新运行工作流程中失败的作业
|
||||
|
||||
If any jobs in a workflow run failed, you can re-run just the jobs that failed. When you re-run failed jobs in a workflow, a new workflow run will start for all failed jobs and their dependents. Any outputs for any successful jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run.
|
||||
如果工作流程运行中的任何作业失败，您可以仅重新运行失败的作业。 在重新运行工作流程中失败的作业时，将为所有失败的作业及其依赖项启动新的工作流程运行。 上一个工作流程运行中任何成功作业的任何输出都将用于重新运行。 在初始运行中创建的任何构件都将在重新运行中可用。 在上一次运行中通过的任何环境保护规则都将自动在重新运行中通过。
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -79,15 +77,14 @@ If any jobs in a workflow run failed, you can re-run just the jobs that failed.
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
1. In the upper-right corner of the workflow, use the **Re-run jobs** drop-down menu, and select **Re-run failed jobs**.
|
||||
|
||||
1. 在工作流程的右上角，使用 **Re-run jobs（重新运行作业）**下拉菜单，并选择 **Re-run failed jobs（重新运行失败的作业）**。 
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
To re-run failed jobs in a workflow run, use the `run rerun` subcommand with the `--failed` flag. Replace `run-id` with the ID of the run for which you want to re-run failed jobs. If you don't specify a `run-id`, {% data variables.product.prodname_cli %} returns an interactive menu for you to choose a recent failed run.
|
||||
要重新运行工作流程运行中失败的作业，请使用 `run rerun` 子命令与 `--failed` 标志。 将 `run-id` 替换为要为其重新运行失败作业的运行 ID。 如果您没有指定 `run-id`，{% data variables.product.prodname_cli %} 将返回一个交互式菜单，供您选择最近失败的运行。
|
||||
|
||||
```shell
|
||||
gh run rerun <em>run-id</em> --failed
|
||||
@@ -103,9 +100,9 @@ gh run rerun <em>run-id</em> --failed --debug
|
||||
{% endif %}
|
||||
{% endcli %}
|
||||
|
||||
## Re-running a specific job in a workflow
|
||||
## 重新运行工作流程中的特定作业
|
||||
|
||||
When you re-run a specific job in a workflow, a new workflow run will start for the job and any dependents. Any outputs for any other jobs in the previous workflow run will be used for the re-run. Any artifacts that were created in the initial run will be available in the re-run. Any environment protection rules that passed in the previous run will automatically pass in the re-run.
|
||||
重新运行工作流程中的特定作业时，将为该作业和任何依赖项启动新的工作流程运行。 上一个工作流程运行中任何其他作业的任何输出都将用于重新运行。 在初始运行中创建的任何构件都将在重新运行中可用。 在上一次运行中通过的任何环境保护规则都将自动在重新运行中通过。
|
||||
|
||||
{% webui %}
|
||||
|
||||
@@ -113,18 +110,16 @@ When you re-run a specific job in a workflow, a new workflow run will start for
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
1. Next to the job that you want to re-run, click {% octicon "sync" aria-label="The re-run icon" %}.
|
||||
|
||||
1. 在要重新运行的作业旁边，单击 {% octicon "sync" aria-label="The re-run icon" %}。 
|
||||
|
||||
Alternatively, click on a job to view the log. In the log, click {% octicon "sync" aria-label="The re-run icon" %}.
|
||||
|
||||
或者，单击作业以查看日志。 在日志中，单击 {% octicon "sync" aria-label="The re-run icon" %}。 
|
||||
{% data reusables.actions.enable-debug-logging %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
{% cli %}
|
||||
|
||||
To re-run a specific job in a workflow run, use the `run rerun` subcommand with the `--job` flag. Replace `job-id` with the ID of the job that you want to re-run.
|
||||
要重新运行工作流程运行中的特定作业，请使用 `run rerun` 子命令与 `--job` 标志。 将 `job-id` 替换为您想要重新运行的作业的 ID。
|
||||
|
||||
```shell
|
||||
gh run rerun --job <em>job-id</em>
|
||||
@@ -144,28 +139,26 @@ gh run rerun --job <em>job-id</em> --debug
|
||||
|
||||
{% ifversion partial-reruns-with-reusable %}
|
||||
|
||||
## Re-running workflows and jobs with reusable workflows
|
||||
## 使用可重用工作流程重新运行工作流程和作业
|
||||
|
||||
{% data reusables.actions.partial-reruns-with-reusable %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.4 or ghae-issue-4721 or ghec %}
|
||||
## Reviewing previous workflow runs
|
||||
## 查看以前的工作流程运行
|
||||
|
||||
You can view the results from your previous attempts at running a workflow. You can also view previous workflow runs using the API. For more information, see ["Get a workflow run"](/rest/reference/actions#get-a-workflow-run).
|
||||
您可以查看以前尝试运行工作流程的结果。 您还可以使用 API 查看以前的工作流程运行。 更多信息请参阅“[获取工作流程运行](/rest/reference/actions#get-a-workflow-run)”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
{% data reusables.repositories.navigate-to-workflow %}
|
||||
{% data reusables.repositories.view-run %}
|
||||
{%- ifversion re-run-jobs %}
|
||||
1. Any previous run attempts are shown in the **Latest** drop-down menu.
|
||||
|
||||
1. 任何以前的运行尝试都显示在 **Latest（最新）**下拉菜单中。 
|
||||
{%- else %}
|
||||
1. Any previous run attempts are shown in the left pane.
|
||||
|
||||
1. 任何以前的运行尝试都显示在左窗格中。 
|
||||
{%- endif %}
|
||||
1. Click an entry to view its results.
|
||||
1. 单击某个条目以查看其结果。
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -410,6 +410,8 @@ workflows:
|
||||
```yaml
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Containers
|
||||
|
||||
on: [push]
|
||||
|
||||
@@ -69,6 +69,8 @@ Docker Hub 需要的 `build-push-action` 选项包括：
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish Docker image
|
||||
|
||||
on:
|
||||
@@ -142,9 +144,12 @@ jobs:
|
||||
上述工作流程通过推送到“发行版”分支触发。 它会检出 GitHub 仓库，并使用 `login-action` 登录到 {% data variables.product.prodname_container_registry %}。 然后，它将提取 Docker 映像的标签和标记。 最后，它使用 `build-push-action` 操作来构建映像并在 {% data variables.product.prodname_container_registry %} 上发布。
|
||||
|
||||
{% else %}
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish Docker image
|
||||
|
||||
on:
|
||||
@@ -194,6 +199,8 @@ jobs:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish Docker image
|
||||
|
||||
on:
|
||||
|
||||
@@ -77,8 +77,11 @@ publishing {
|
||||
使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库。 在部署步骤中，您需要为用于向 Maven 仓库验证身份的用户名和密码或令牌设置环境变量。 更多信息请参阅“[创建和使用加密密码](/github/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)”。
|
||||
|
||||
```yaml{:copy}
|
||||
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish package to the Maven Central Repository
|
||||
on:
|
||||
release:
|
||||
@@ -146,8 +149,11 @@ publishing {
|
||||
使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 {% data variables.product.prodname_registry %}。
|
||||
|
||||
```yaml{:copy}
|
||||
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish package to GitHub Packages
|
||||
on:
|
||||
release:
|
||||
@@ -224,8 +230,11 @@ publishing {
|
||||
使用此配置可创建一个工作流程，以通过运行 `gradle publish` 命令将包发布到 Maven 中心仓库和 {% data variables.product.prodname_registry %}。
|
||||
|
||||
```yaml{:copy}
|
||||
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Publish package to the Maven Central Repository and GitHub Packages
|
||||
on:
|
||||
release:
|
||||
|
||||
@@ -447,7 +447,7 @@ on:
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注意**：此事件对项目（测试版）不会发生。 更多信息请参阅“[关于项目（测试版）](/issues/trying-out-the-new-projects-experience/about-projects)”。
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -485,7 +485,7 @@ on:
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注意**：此事件对项目（测试版）不会发生。 更多信息请参阅“[关于项目（测试版）](/issues/trying-out-the-new-projects-experience/about-projects)”。
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -523,7 +523,7 @@ on:
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注意**：此事件对项目（测试版）不会发生。 更多信息请参阅“[关于项目（测试版）](/issues/trying-out-the-new-projects-experience/about-projects)”。
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
@@ -31,16 +31,12 @@ shortTitle: 配置 DNS 服务器
|
||||
|
||||
{% data reusables.enterprise_installation.ssh-into-instance %}
|
||||
|
||||
2. 要编辑域名服务器，请输入：
|
||||
2. To edit your nameservers, use the `ghe-setup-network` command in visual mode. 更多信息请参阅“[命令行实用程序](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-setup-network)”。
|
||||
|
||||
```shell
|
||||
sudo vim /etc/resolvconf/resolv.conf.d/head
|
||||
ghe-setup-network -v
|
||||
```
|
||||
|
||||
{% data reusables.enterprise_installation.preventing-nameservers-change %}
|
||||
|
||||
3. 附加任何 `nameserver` 条目，然后保存文件。
|
||||
4. 验证变更后，请保存文件。
|
||||
5. 要向 {% data variables.product.product_location %} 添加新的域名服务器条目，请运行以下命令：
|
||||
|
||||
```shell
|
||||
|
||||
@@ -343,6 +343,18 @@ With `ghe-set-password`, you can set a new password to authenticate into the [{%
|
||||
ghe-set-password <new_password>
|
||||
```
|
||||
|
||||
### ghe-setup-network
|
||||
|
||||
This utility allows you to configure the primary network interface.
|
||||
|
||||
To enter visual mode, which will guide you through configuration of network settings:
|
||||
|
||||
```shell
|
||||
$ ghe-setup-network -v
|
||||
```
|
||||
|
||||
Use the -h flag for additional options.
|
||||
|
||||
### ghe-ssh-check-host-keys
|
||||
|
||||
This utility checks the existing SSH host keys against the list of known leaked SSH host keys.
|
||||
|
||||
@@ -74,14 +74,14 @@ shortTitle: 配置电子邮件通知
|
||||
{% data reusables.enterprise_site_admin_settings.wait-for-configuration-run %}
|
||||
|
||||
{% ifversion require-tls-for-smtp %}
|
||||
## Enforcing TLS for SMTP connections
|
||||
## 对 SMTP 连接强制实施 TLS
|
||||
|
||||
You can enforce TLS encryption for all incoming SMTP connections, which can help satisfy an ISO-27017 certification requirement.
|
||||
您可以对所有传入的 SMTP 连接强制实施 TLS 加密，这有助于满足 ISO-27017 认证要求。
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.email-settings %}
|
||||
1. Under "Authentication," select **Enforce TLS auth (recommended)**.
|
||||
1. 在“Authentication（身份验证）”下，选择 **Enforce TLS auth (recommended)（强制实施 TLS 身份验证[推荐]）**。
|
||||
|
||||
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
{% endif %}
|
||||
|
||||
@@ -92,7 +92,7 @@ You can enforce TLS encryption for all incoming SMTP connections, which can help
|
||||
1. 确保您的 SMTP 服务器可以访问实例上的端口 25。
|
||||
2. 创建一个指向 `reply.[hostname]` 的 A 记录。 根据您的 DNS 提供商和实例主机配置，您可以创建一个指向 `*.[hostname]` 的 A 记录。
|
||||
3. 创建一个指向 `reply.[hostname]` 的 MX 记录，以便发送到该域的电子邮件可以路由到实例。
|
||||
4. 创建一个将 `noreply.[hostname]` 指向 `[hostname]` 的 MX 记录，以便对通知电子邮件中 `cc` 地址的回复可以路由到实例。 For more information, see {% ifversion ghes %}"[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}"[About email notifications](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}."
|
||||
4. 创建一个将 `noreply.[hostname]` 指向 `[hostname]` 的 MX 记录，以便对通知电子邮件中 `cc` 地址的回复可以路由到实例。 更多信息请参阅{% ifversion ghes %}"[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications){% else %}“[关于电子邮件通知](/github/receiving-notifications-about-activity-on-github/about-email-notifications){% endif %}。”
|
||||
|
||||
## 排查电子邮件递送问题
|
||||
|
||||
|
||||
@@ -119,6 +119,7 @@ includeGuides:
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise
|
||||
- /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise
|
||||
|
||||
@@ -35,7 +35,8 @@ topics:
|
||||
|
||||
作为企业所有者{% ifversion ghes %} 或站点管理员{% endif %}，您可以通过多种方式与企业的审核日志数据进行交互：
|
||||
- 您可以查看企业的审核日志。 更多信息请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)”。
|
||||
- 您可以在审核日志中搜索特定事件{% ifversion ghec %} 并导出审核日志数据{% endif %}。 更多信息请参阅“[搜索企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)”{% ifversion ghec %} 和“[导出企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)”{% endif %}。
|
||||
- 您可以在审核日志中搜索特定事件{% ifversion ghec %} 并导出审核日志数据{% endif %}。 For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.{% ifversion audit-data-retention-tab %}
|
||||
- You can configure settings, such as the retention period for audit log events{% ifversion enable-git-events %} and whether Git events are included{% endif %}. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)."{% endif %}
|
||||
{%- ifversion enterprise-audit-log-ip-addresses %}
|
||||
- 您可以在审核日志中显示与事件关联的 IP 地址。 更多信息请参阅“[在企业的审核日志中显示 IP 地址](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise)”。
|
||||
{%- endif %}
|
||||
|
||||
@@ -392,9 +392,15 @@ Action | Description
|
||||
| `gist.destroy` | A gist is deleted.
|
||||
| `gist.visibility_change` | The visibility of a gist is changed.
|
||||
|
||||
{% ifversion ghec or ghes > 3.4 or ghae-issue-6724 %}
|
||||
{% ifversion git-events-audit-log %}
|
||||
## `git` category actions
|
||||
|
||||
{% ifversion enable-git-events %}
|
||||
Before you'll see `git` category actions, you must enable Git events in the audit log. For more information, see "[Configuring the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise#managing-git-events-in-the-audit-log)."
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.audit_log.git-events-not-in-search-results %}
|
||||
|
||||
| Action | Description
|
||||
|--------|-------------
|
||||
| `git.clone` | A repository was cloned.
|
||||
@@ -889,20 +895,20 @@ Action | Description
|
||||
| `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)."
|
||||
| `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)."
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
{%- ifversion projects-v2 %}
|
||||
## `project_field` category actions
|
||||
|
||||
| Action | Description
|
||||
|--------|-------------
|
||||
| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)."
|
||||
| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)."
|
||||
| `project_field.create` | A field was created in a project board. For more information, see "[Understanding field types](/issues/planning-and-tracking-with-projects/understanding-field-types)."
|
||||
| `project_field.delete` | A field was deleted in a project board. For more information, see "[Deleting fields](/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields)."
|
||||
|
||||
## `project_view` category actions
|
||||
|
||||
| Action | Description
|
||||
|--------|-------------
|
||||
| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)."
|
||||
| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)."
|
||||
| `project_view.create` | A view was created in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
|
||||
| `project_view.delete` | A view was deleted in a project board. For more information, see "[Managing your views](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/managing-your-views)."
|
||||
{%- endif %}
|
||||
|
||||
## `protected_branch` category actions
|
||||
|
||||
@@ -0,0 +1,56 @@
|
||||
---
|
||||
title: Configuring the audit log for your enterprise
|
||||
intro: You can configure settings for your enterprise's audit log.
|
||||
shortTitle: Configure audit logs
|
||||
permissions: Enterprise owners can configure the audit log.
|
||||
versions:
|
||||
feature: audit-data-retention-tab
|
||||
type: how_to
|
||||
topics:
|
||||
- Auditing
|
||||
- Enterprise
|
||||
- Logging
|
||||
---
|
||||
|
||||
## About audit log configuration
|
||||
|
||||
You can configure a retention period for audit log data and see index storage details.
|
||||
|
||||
{% ifversion enable-git-events %}
|
||||
After you configure a retention period, you can enable or disable Git-related events from appearing in the audit log.
|
||||
{% endif %}
|
||||
|
||||
## Configuring a retention period for audit log data
|
||||
|
||||
You can configure a retention period for audit log data for {% data variables.product.product_location %}. Data that exceeds the period you configure will be permanently removed from disk.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.audit-log-tab %}
|
||||
{% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. Under "Configure audit log retention settings", select the dropdown menu and click a retention period.
|
||||
|
||||
|
||||
1. 单击 **Save（保存）**。
|
||||
|
||||
{% ifversion enable-git-events %}
|
||||
## Managing Git events in the audit log
|
||||
|
||||
You can enable or disable Git-related events, such as `git.clone` and `git.push`, from appearing in your audit log. For a list of the Git events are are logged, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)."
|
||||
|
||||
If you do enable Git events, due to the large number of Git events that are logged, we recommend monitoring your instance's file storage and reviewing your related alert configurations. For more information, see "[Monitoring storage](/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds#monitoring-storage)."
|
||||
|
||||
Before you can enable Git events in the audit log, you must configure a retention period for audit log data other than "infinite." For more information, see "[Configuring a retention period for audit log data](#configuring-a-retention-period-for-audit-log-data)."
|
||||
|
||||
{% data reusables.audit_log.git-events-not-in-search-results %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.audit-log-tab %}
|
||||
{% data reusables.audit_log.audit-data-retention-tab %}
|
||||
1. Under "Git event opt-in", select or deselect **Enable git events in the audit-log**.
|
||||
|
||||
|
||||
1. 单击 **Save（保存）**。
|
||||
|
||||
{% endif %}
|
||||
@@ -11,6 +11,7 @@ topics:
|
||||
children:
|
||||
- /about-the-audit-log-for-your-enterprise
|
||||
- /accessing-the-audit-log-for-your-enterprise
|
||||
- /configuring-the-audit-log-for-your-enterprise
|
||||
- /displaying-ip-addresses-in-the-audit-log-for-your-enterprise
|
||||
- /searching-the-audit-log-for-your-enterprise
|
||||
- /exporting-audit-log-activity-for-your-enterprise
|
||||
|
||||
@@ -29,9 +29,11 @@ miniTocMaxHeadingLevel: 3
|
||||
|
||||
有关查看企业审核日志的更多信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)”。
|
||||
|
||||
{% data reusables.audit_log.git-events-not-in-search-results %}
|
||||
|
||||
还可以使用 API 检索审核日志事件。 更多信息请参阅“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)”。
|
||||
|
||||
请注意，无法使用文本搜索条目。 但是，您可以使用各种过滤器构建搜索查询。 查询日志时使用的许多运算符，如 `-`、`>` 或 `<`，与在 {% data variables.product.product_name %} 上搜索时的格式相同。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
|
||||
You cannot search for entries using text. 但是，您可以使用各种过滤器构建搜索查询。 查询日志时使用的许多运算符，如 `-`、`>` 或 `<`，与在 {% data variables.product.product_name %} 上搜索时的格式相同。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -16,11 +16,11 @@ topics:
|
||||
|
||||
## 关于 {% data variables.product.prodname_container_registry %}
|
||||
|
||||
{% data reusables.package_registry.container-registry-benefits %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)."
|
||||
{% data reusables.package_registry.container-registry-benefits %} 更多信息请参阅[使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)”。
|
||||
|
||||
For more information about configuring {% data variables.product.prodname_registry %} for {% data variables.product.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
|
||||
## About migration from the Docker registry
|
||||
## 关于从 Docker 注册表迁移
|
||||
|
||||
{% data reusables.package_registry.container-registry-replaces-docker-registry %} If the Docker registry on {% data variables.product.product_location %} contains images, you must manually migrate the images to the {% data variables.product.prodname_container_registry %}.
|
||||
|
||||
|
||||
@@ -205,22 +205,22 @@ shortTitle: 仓库管理策略
|
||||
|
||||
{% ifversion profile-name-enterprise-setting %}
|
||||
|
||||
## Enforcing a policy for the display of member names in your repositories
|
||||
## 强制实施在存储库中显示成员名称的策略
|
||||
|
||||
Across all organizations owned by your enterprise, you can allow members to see a comment author's profile name, in addition to their username, in issues and pull requests for public and internal repositories.
|
||||
在企业拥有的所有组织中，您可以允许成员在公共和内部存储库的问题和拉取请求中查看评论作者的个人资料名称，以及他们的用户名。
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** When this policy is enforced for all repositories in the enterprise, it overrides the organization setting for private repositories. For more information, see "[Managing the display of member names in your organization](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)".
|
||||
**注意：** 对企业中的所有存储库强制实施此策略时，它将覆盖私有存储库的组织设置。 更多信息请参阅“[管理组织中成员名称的显示](/organizations/managing-organization-settings/managing-the-display-of-member-names-in-your-organization)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.options-tab %}
|
||||
4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. 
|
||||
4. Under "Allow members to see the comment author's profile name in public and internal repositories", select the dropdown menu and click a policy. 
|
||||
5. Optionally, to enforce the display of profile names for all repositories in your enterprise, select **Enforce for all repositories on the instance**. 
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -17,7 +17,7 @@ shortTitle: 添加新的 SSH 密钥
|
||||
|
||||
## About addition of SSH keys to your account
|
||||
|
||||
{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
|
||||
{% data reusables.ssh.about-ssh %} 更多信息请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”。
|
||||
|
||||
After you generate an SSH key pair, you must add the public key to {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable SSH access for your account.
|
||||
|
||||
|
||||
@@ -17,11 +17,11 @@ topics:
|
||||
shortTitle: 生成新 SSH 密钥
|
||||
---
|
||||
|
||||
## About SSH key passphrases
|
||||
## 关于 SSH 密钥密码
|
||||
|
||||
{% data reusables.ssh.about-ssh %} For more information, see "[About SSH](/authentication/connecting-to-github-with-ssh/about-ssh)."
|
||||
{% data reusables.ssh.about-ssh %} 更多信息请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”。
|
||||
|
||||
When you generate an SSH key, you can add a passphrase to further secure the key. Whenever you use the key, you must enter the passphrase. If your key has a passphrase and you don't want to enter the passphrase every time you use the key, you can add your key to the SSH agent. The SSH agent manages your SSH keys and remembers your passphrase.
|
||||
生成 SSH 密钥时，可以添加密码以进一步保护密钥。 无论何时使用密钥，都必须输入密码。 如果您的密钥具有密码，并且您不想在每次使用密钥时都输入密码，则可以将密钥添加到 SSH 代理。 SSH 代理管理您的 SSH 密钥并记住您的密码。
|
||||
|
||||
如果您还没有 SSH 密钥，则必须生成新 SSH 密钥用于身份验证。 如果不确定是否已经拥有 SSH 密钥，您可以检查现有密钥。 更多信息请参阅“[检查现有 SSH 密钥](/github/authenticating-to-github/checking-for-existing-ssh-keys)”。
|
||||
|
||||
@@ -29,7 +29,7 @@ When you generate an SSH key, you can add a passphrase to further secure the key
|
||||
|
||||
## 生成新 SSH 密钥
|
||||
|
||||
You can generate a new SSH key on your local machine. After you generate the key, you can add the key to your account on {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} to enable authentication for Git operations over SSH.
|
||||
您可以在本地计算机上生成新的 SSH 密钥。 生成密钥后，可以将密钥添加到您在 {% ifversion fpt or ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上的帐户，以便为通过 SSH 的 Git 操作启用身份验证。
|
||||
|
||||
{% data reusables.ssh.key-type-support %}
|
||||
|
||||
@@ -126,9 +126,9 @@ You can generate a new SSH key on your local machine. After you generate the key
|
||||
|
||||
**注意：**
|
||||
|
||||
- If you chose not to add a passphrase to your key, you should omit the `UseKeychain` line.
|
||||
- 如果您选择不向密钥添加密码，应该省略 `UseKeychain` 行。
|
||||
|
||||
- If you see a `Bad configuration option: usekeychain` error, add an additional line to the configuration's' `Host *` section.
|
||||
- 如果您看到 `Bad configuration option: usekeychain` 错误，请在配置的 `Host *` 部分另外添加一行。
|
||||
|
||||
```
|
||||
Host *
|
||||
|
||||
@@ -17,9 +17,9 @@ topics:
|
||||
shortTitle: SSH 密钥密码
|
||||
---
|
||||
|
||||
## About passphrases for SSH keys
|
||||
## 关于 SSH 密钥的密码
|
||||
|
||||
With SSH keys, if someone gains access to your computer, the attacker can gain access to every system that uses that key. 要添加额外的安全层，可以向 SSH 密钥添加密码。 To avoid entering the passphrase every time you connect, you can securely save your passphrase in the SSH agent.
|
||||
使用 SSH 密钥时，如果有人获得了对您的计算机的访问权限，攻击者就可以访问使用该密钥的每个系统。 要添加额外的安全层，可以向 SSH 密钥添加密码。 为避免每次连接时都输入密码，您可以在 SSH 代理中安全地保存密码。
|
||||
|
||||
## 添加或更改密码
|
||||
|
||||
|
||||
@@ -68,7 +68,7 @@ When you want to use an {% data variables.product.prodname_oauth_app %} that int
|
||||
| Personal user data | User data includes information found in your user profile, like your name, e-mail address, and location. |
|
||||
| Repositories | Repository information includes the names of contributors, the branches you've created, and the actual files within your repository. Apps can request access for either public or private repositories on a user-wide level. |
|
||||
| Repository delete | Apps can request to delete repositories that you administer, but they won't have access to your code. |{% ifversion projects-oauth-scope %}
|
||||
| Projects | Access to user and organization projects (beta). Apps can request either read/write or read only access. |{% endif %}
|
||||
| Projects | Access to user and organization {% data variables.projects.projects_v2 %}. Apps can request either read/write or read only access. |{% endif %}
|
||||
|
||||
## Requesting updated permissions
|
||||
|
||||
|
||||
@@ -22,6 +22,9 @@ redirect_from:
|
||||
{% data reusables.organizations.billing-settings %}
|
||||
{% data reusables.dotcom_billing.codespaces-minutes %}
|
||||
{% data reusables.dotcom_billing.actions-packages-report-download-org-account %}
|
||||
1. Filter the report to show only rows that mention "Codespaces" in the `Product` field.
|
||||
|
||||
|
||||
|
||||
{% ifversion ghec %}
|
||||
## 查看企业帐户的 {% data variables.product.prodname_codespaces %} 使用情况
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: 浏览 GitHub Advisory 数据库中的安全通告
|
||||
intro: '您可以浏览 {% data variables.product.prodname_advisory_database %} ，查找有关托管在 {% data variables.product.company_short %} 上的开源项目中的安全风险的公告。'
|
||||
shortTitle: 浏览公告数据库
|
||||
title: Browsing security advisories in the GitHub Advisory Database
|
||||
intro: 'You can browse the {% data variables.product.prodname_advisory_database %} to find advisories for security risks in open source projects that are hosted on {% data variables.product.company_short %}.'
|
||||
shortTitle: Browse Advisory Database
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database
|
||||
@@ -21,127 +21,143 @@ topics:
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
---
|
||||
|
||||
<!--Marketing-LINK: From /features/security/software-supply-chain page "Browsing security vulnerabilities in the GitHub Advisory Database".-->
|
||||
|
||||
## 关于 {% data variables.product.prodname_advisory_database %}
|
||||
## About the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
The {% data variables.product.prodname_advisory_database %} contains a list of known security vulnerabilities {% ifversion GH-advisory-db-supports-malware %}and malware, {% endif %}grouped in two categories: {% data variables.product.company_short %}-reviewed advisories and unreviewed advisories.
|
||||
|
||||
{% data reusables.repositories.tracks-vulnerabilities %}
|
||||
|
||||
## 关于安全公告的类型
|
||||
## About types of security advisories
|
||||
|
||||
{% data reusables.advisory-database.beta-malware-advisories %}
|
||||
|
||||
Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
|
||||
Each advisory in the {% data variables.product.prodname_advisory_database %} is for a vulnerability in open source projects{% ifversion GH-advisory-db-supports-malware %} or for malicious open source software{% endif %}.
|
||||
|
||||
{% data reusables.repositories.a-vulnerability-is %} 代码中的漏洞通常是偶然引入的，在发现后不久就被修复。 您应该在依赖项的固定版本可用时立即更新代码以使用该版本。
|
||||
{% data reusables.repositories.a-vulnerability-is %} Vulnerabilities in code are usually introduced by accident and fixed soon after they are discovered. You should update your code to use the fixed version of the dependency as soon as it is available.
|
||||
|
||||
{% ifversion GH-advisory-db-supports-malware %}
|
||||
|
||||
相反，恶意软件或恶意软件是故意设计用于执行不需要或有害功能的代码。 恶意软件可能以硬件、软件、机密数据或使用恶意软件的任何应用程序的用户为目标。 您需要从项目中删除恶意软件，并找到依赖项的替代，更安全的替代品。
|
||||
In contrast, malicious software, or malware, is code that is intentionally designed to perform unwanted or harmful functions. The malware may target hardware, software, confidential data, or users of any application that uses the malware. You need to remove the malware from your project and find an alternative, more secure replacement for the dependency.
|
||||
|
||||
{% endif %}
|
||||
|
||||
### {% data variables.product.company_short %} 审核的公告
|
||||
### {% data variables.product.company_short %}-reviewed advisories
|
||||
|
||||
{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. 我们会仔细审查每个公告的有效性，确保它们具有完整的描述，并包含生态系统和软件包信息。
|
||||
{% data variables.product.company_short %}-reviewed advisories are security vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} that have been mapped to packages in ecosystems we support. We carefully review each advisory for validity and ensure that they have a full description, and contain both ecosystem and package information.
|
||||
|
||||
通常，我们以软件编程语言的关联包注册表命名支持的生态系统。 如果公告针对来自受支持注册表的程序包中的漏洞，我们会对其进行审查。
|
||||
Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
|
||||
|
||||
- Composer (registry: https://packagist.org/){% ifversion GH-advisory-db-erlang-support %}
|
||||
- Erlang (registry: https://hex.pm/){% endif %}
|
||||
- Go（注册表：https://pkg.go.dev/）
|
||||
- Maven（注册表：https://repo1.maven.org/maven2/org）
|
||||
- npm（注册表：https://www.npmjs.com/）
|
||||
- NuGet（注册表：https://www.nuget.org/）
|
||||
- pip（注册表：https://pypi.org/）
|
||||
- RubyGems（注册表：https://rubygems.org/）
|
||||
- Rust（注册表：https://crates.io/）
|
||||
- Go (registry: https://pkg.go.dev/)
|
||||
- Maven (registry: https://repo1.maven.org/maven2/org/)
|
||||
- npm (registry: https://www.npmjs.com/)
|
||||
- NuGet (registry: https://www.nuget.org/)
|
||||
- pip (registry: https://pypi.org/)
|
||||
- RubyGems (registry: https://rubygems.org/)
|
||||
- Rust (registry: https://crates.io/)
|
||||
|
||||
如果您对我们应该支持的新生态系统有任何建议，请打开[议题](https://github.com/github/advisory-database/issues)进行讨论。
|
||||
If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
|
||||
|
||||
If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”。
|
||||
If you enable {% data variables.product.prodname_dependabot_alerts %} for your repositories, you are automatically notified when a new {% data variables.product.company_short %}-reviewed advisory reports a vulnerability {% ifversion GH-advisory-db-supports-malware %}or malware{% endif %} for a package you depend on. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."
|
||||
|
||||
### 未审核的公告
|
||||
### Unreviewed advisories
|
||||
|
||||
未审核的公告是我们直接从国家漏洞数据库源自动发布到 {% data variables.product.prodname_advisory_database %} 的安全漏洞。
|
||||
Unreviewed advisories are security vulnerabilites that we publish automatically into the {% data variables.product.prodname_advisory_database %}, directly from the National Vulnerability Database feed.
|
||||
|
||||
{% data variables.product.prodname_dependabot %} 不会为未审核的公告创建 {% data variables.product.prodname_dependabot_alerts %}，因为不会检查此类公告的有效性或完成情况。
|
||||
{% data variables.product.prodname_dependabot %} doesn't create {% data variables.product.prodname_dependabot_alerts %} for unreviewed advisories as this type of advisory isn't checked for validity or completion.
|
||||
|
||||
## 关于安全公告中的信息
|
||||
## About information in security advisories
|
||||
|
||||
Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. 此外，国家漏洞数据库列表中的公告包含 CVE 记录链接，通过链接可以查看漏洞、其 CVSS 得分及其质化严重等级的更多详细信息。 更多信息请参阅国家标准和技术研究所 (National Institute of Standards and Technology) 的“[国家漏洞数据库](https://nvd.nist.gov/)”。
|
||||
Each security advisory contains information about the vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware,{% endif %} which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "[National Vulnerability Database](https://nvd.nist.gov/)" from the National Institute of Standards and Technology.
|
||||
|
||||
我们在[常见漏洞评分系统 (CVSS) 第 5 节](https://www.first.org/cvss/specification-document)中定义了以下四种可能的严重性等级。
|
||||
- 低
|
||||
- 中
|
||||
- 高
|
||||
- 关键
|
||||
The severity level is one of four possible levels defined in the "[Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document)."
|
||||
- Low
|
||||
- Medium/Moderate
|
||||
- High
|
||||
- Critical
|
||||
|
||||
{% data variables.product.prodname_advisory_database %} 使用上述 CVSS 级别。 如果 {% data variables.product.company_short %} 获取 CVE，{% data variables.product.prodname_advisory_database %} 将使用 CVSS 版本 3.1。 如果 CVE 是导入的，则 {% data variables.product.prodname_advisory_database %} 支持 CVSS 版本 3.0 和 3.1。
|
||||
The {% data variables.product.prodname_advisory_database %} uses the CVSS levels described above. If {% data variables.product.company_short %} obtains a CVE, the {% data variables.product.prodname_advisory_database %} uses CVSS version 3.1. If the CVE is imported, the {% data variables.product.prodname_advisory_database %} supports both CVSS versions 3.0 and 3.1.
|
||||
|
||||
{% data reusables.repositories.github-security-lab %}
|
||||
|
||||
## 访问 {% data variables.product.prodname_advisory_database %} 中的通告
|
||||
## Accessing an advisory in the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
1. 导航到 https://github.com/advisories。
|
||||
2. （可选）要过滤列表，请使用任意下拉菜单。 
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Optionally, to filter the list, use any of the drop-down menus.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**您可以使用左侧的边栏分别浏览 {% data variables.product.company_short %} 已审核和未审核的公告。
|
||||
**Tip:** You can use the sidebar on the left to explore {% data variables.product.company_short %}-reviewed and unreviewed advisories separately.
|
||||
|
||||
{% endtip %}
|
||||
3. Click an advisory to view details. 默认情况下，您将看到 {% data variables.product.company_short %} 已审核的安全漏洞公告。 {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
|
||||
3. Click an advisory to view details. By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. {% ifversion GH-advisory-db-supports-malware %}To show malware advisories, use `type:malware` in the search bar.{% endif %}
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
也可以使用 GraphQL API 访问数据库。 {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
|
||||
The database is also accessible using the GraphQL API. {% ifversion GH-advisory-db-supports-malware %}By default, queries will return {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities unless you specify `type:malware`.{% endif %} For more information, see the "[`security_advisory` webhook event](/webhooks/event-payloads/#security_advisory)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 在 {% data variables.product.prodname_advisory_database %} 中编辑公告
|
||||
您可以对 {% data variables.product.prodname_advisory_database %} 中的任何公告提出改进建议。 更多信息请参阅“[编辑 {% data variables.product.prodname_advisory_database %} 中的安全通告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
|
||||
## Editing an advisory in the {% data variables.product.prodname_advisory_database %}
|
||||
You can suggest improvements to any advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Editing security advisories in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)."
|
||||
|
||||
## 搜索 {% data variables.product.prodname_advisory_database %}
|
||||
## Searching the {% data variables.product.prodname_advisory_database %}
|
||||
|
||||
您可以搜索数据库，并使用限定符缩小搜索范围。 例如，您可以搜索在特定日期、特定生态系统或特定库中创建的通告。
|
||||
You can search the database, and use qualifiers to narrow your search. For example, you can search for advisories created on a certain date, in a specific ecosystem, or in a particular library.
|
||||
|
||||
{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
|
||||
|
||||
{% data reusables.search.date_gt_lt %}
|
||||
|
||||
| 限定符 | 示例 |
|
||||
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| `type:reviewed` | [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) 将显示 {% data variables.product.company_short %} 已审核的安全漏洞公告。 |
|
||||
| Qualifier | Example |
|
||||
| ------------- | ------------- |
|
||||
| `type:reviewed`| [**type:reviewed**](https://github.com/advisories?query=type%3Areviewed) will show {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. |
|
||||
{% ifversion GH-advisory-db-supports-malware %}| `type:malware` | [**type:malware**](https://github.com/advisories?query=type%3Amalware) will show {% data variables.product.company_short %}-reviewed advisories for malware. |
|
||||
{% endif %}| `type:unreviewed`| [**type:unreviewed**](https://github.com/advisories?query=type%3Aunreviewed) will show unreviewed advisories. |
|
||||
| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. | | `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. | | `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. | | `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. | | `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. | | `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. | | `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. | | `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. | | `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. | | `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. | | `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. | | `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. | | `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. | | `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
|
||||
| `GHSA-ID`| [**GHSA-49wp-qq6x-g2rf**](https://github.com/advisories?query=GHSA-49wp-qq6x-g2rf) will show the advisory with this {% data variables.product.prodname_advisory_database %} ID. |
|
||||
| `CVE-ID`| [**CVE-2020-28482**](https://github.com/advisories?query=CVE-2020-28482) will show the advisory with this CVE ID number. |
|
||||
| `ecosystem:ECOSYSTEM`| [**ecosystem:npm**](https://github.com/advisories?utf8=%E2%9C%93&query=ecosystem%3Anpm) will show only advisories affecting NPM packages. |
|
||||
| `severity:LEVEL`| [**severity:high**](https://github.com/advisories?utf8=%E2%9C%93&query=severity%3Ahigh) will show only advisories with a high severity level. |
|
||||
| `affects:LIBRARY`| [**affects:lodash**](https://github.com/advisories?utf8=%E2%9C%93&query=affects%3Alodash) will show only advisories affecting the lodash library. |
|
||||
| `cwe:ID`| [**cwe:352**](https://github.com/advisories?query=cwe%3A352) will show only advisories with this CWE number. |
|
||||
| `credit:USERNAME`| [**credit:octocat**](https://github.com/advisories?query=credit%3Aoctocat) will show only advisories credited to the "octocat" user account. |
|
||||
| `sort:created-asc`| [**sort:created-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-asc) will sort by the oldest advisories first. |
|
||||
| `sort:created-desc`| [**sort:created-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Acreated-desc) will sort by the newest advisories first. |
|
||||
| `sort:updated-asc`| [**sort:updated-asc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-asc) will sort by the least recently updated first. |
|
||||
| `sort:updated-desc`| [**sort:updated-desc**](https://github.com/advisories?utf8=%E2%9C%93&query=sort%3Aupdated-desc) will sort by the most recently updated first. |
|
||||
| `is:withdrawn`| [**is:withdrawn**](https://github.com/advisories?utf8=%E2%9C%93&query=is%3Awithdrawn) will show only advisories that have been withdrawn. |
|
||||
| `created:YYYY-MM-DD`| [**created:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=created%3A2021-01-13) will show only advisories created on this date. |
|
||||
| `updated:YYYY-MM-DD`| [**updated:2021-01-13**](https://github.com/advisories?utf8=%E2%9C%93&query=updated%3A2021-01-13) will show only advisories updated on this date. |
|
||||
|
||||
## 查看有漏洞的仓库
|
||||
## Viewing your vulnerable repositories
|
||||
|
||||
For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 要查看有漏洞的仓库，您必须有权访问该仓库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。
|
||||
For any {% data variables.product.company_short %}-reviewed advisory in the {% data variables.product.prodname_advisory_database %}, you can see which of your repositories are affected by that security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
|
||||
1. 导航到 https://github.com/advisories。
|
||||
2. 单击通告。
|
||||
3. 在通告页面的顶部，单击 **Dependabot alerts（Dependabot 警报）**。 
|
||||
4. （可选）要过滤列表，请使用搜索栏或下拉菜单。 “Organization（组织）”下拉菜单用于按所有者（组织或用户）过滤 {% data variables.product.prodname_dependabot_alerts %}。 
|
||||
5. 有关公告的更多详细信息，以及有关如何修复有漏洞的仓库的建议，请单击仓库名称。
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Click an advisory.
|
||||
3. At the top of the advisory page, click **Dependabot alerts**.
|
||||
|
||||
4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
|
||||
|
||||
5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
|
||||
|
||||
{% ifversion security-advisories-ghes-ghae %}
|
||||
## Accessing the local advisory database on {% data variables.product.product_location %}
|
||||
|
||||
If your site administrator has enabled {% data variables.product.prodname_github_connect %} for {% data variables.product.product_location %}, you can also browse reviewed advisories locally. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)".
|
||||
|
||||
You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
|
||||
You can use your local advisory database to check whether a specific security vulnerability is included, and therefore whether you'd get alerts for vulnerable dependencies. You can also view any vulnerable repositories.
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. （可选）要过滤列表，请使用任意下拉菜单。 
|
||||
2. Optionally, to filter the list, use any of the drop-down menus.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
|
||||
**Note:** Only reviewed advisories will be listed. Unreviewed advisories can be viewed in the {% data variables.product.prodname_advisory_database %} on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Accessing an advisory in the GitHub Advisory Database](#accessing-an-advisory-in-the-github-advisory-database)".
|
||||
|
||||
{% endnote %}
|
||||
3. Click an advisory to view details.{% ifversion GH-advisory-db-supports-malware %} By default, you will see {% data variables.product.company_short %}-reviewed advisories for security vulnerabilities. To show malware advisories, use `type:malware` in the search bar.{% endif %}
|
||||
@@ -152,16 +168,18 @@ You can also suggest improvements to any advisory directly from your local advis
|
||||
|
||||
{% data reusables.repositories.enable-security-alerts %}
|
||||
|
||||
In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. 要查看有漏洞的仓库，您必须有权访问该仓库的 {% data variables.product.prodname_dependabot_alerts %}。 更多信息请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %} 警报](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)”。
|
||||
In the local advisory database, you can see which repositories are affected by each security vulnerability{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %}. To see a vulnerable repository, you must have access to {% data variables.product.prodname_dependabot_alerts %} for that repository. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#access-to-dependabot-alerts)."
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. 单击通告。
|
||||
3. 在通告页面的顶部，单击 **Dependabot alerts（Dependabot 警报）**。 
|
||||
4. （可选）要过滤列表，请使用搜索栏或下拉菜单。 “Organization（组织）”下拉菜单用于按所有者（组织或用户）过滤 {% data variables.product.prodname_dependabot_alerts %}。 
|
||||
5. 有关公告的更多详细信息，以及有关如何修复有漏洞的仓库的建议，请单击仓库名称。
|
||||
2. Click an advisory.
|
||||
3. At the top of the advisory page, click **Dependabot alerts**.
|
||||
|
||||
4. Optionally, to filter the list, use the search bar or the drop-down menus. The "Organization" drop-down menu allows you to filter the {% data variables.product.prodname_dependabot_alerts %} per owner (organization or user).
|
||||
|
||||
5. For more details about the advisory, and for advice on how to fix the vulnerable repository, click the repository name.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- MITRE 的[“漏洞”定义](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
|
||||
- MITRE's [definition of "vulnerability"](https://www.cve.org/ResourcesSupport/Glossary#vulnerability)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 在 GitHub Advisory 数据库中编辑安全通告
|
||||
intro: '您可以对 {% data variables.product.prodname_advisory_database %} 中发布的任何公告提出改进建议。'
|
||||
title: Editing security advisories in the GitHub Advisory Database
|
||||
intro: 'You can submit improvements to any advisory published in the {% data variables.product.prodname_advisory_database %}.'
|
||||
redirect_from:
|
||||
- /code-security/security-advisories/editing-security-advisories-in-the-github-advisory-database
|
||||
- /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database
|
||||
@@ -16,32 +16,34 @@ topics:
|
||||
- Dependabot
|
||||
- Vulnerabilities
|
||||
- CVEs
|
||||
shortTitle: 编辑公告数据库
|
||||
shortTitle: Edit Advisory Database
|
||||
---
|
||||
|
||||
## 关于在 {% data variables.product.prodname_advisory_database %} 中编辑公告
|
||||
[github.com/advisories](https://github.com/advisories) {% data variables.product.prodname_advisory_database %} 中的安全公告被视为全局公告。 任何人都可以在 {% data variables.product.prodname_advisory_database %} 中对任何全局安全公告提出改进建议。 您可以编辑或添加任何详细信息，包括其他受影响的生态系统、严重性级别或受影响者的描述。 {% data variables.product.prodname_security %} 管理团队将审查提交的改进，并在接受时将其发布到 {% data variables.product.prodname_advisory_database %} 上。
|
||||
## About editing advisories in the {% data variables.product.prodname_advisory_database %}
|
||||
Security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories) are considered global advisories. Anyone can suggest improvements on any global security advisory in the {% data variables.product.prodname_advisory_database %}. You can edit or add any detail, including additionally affected ecosystems, severity level or description of who is impacted. The {% data variables.product.prodname_security %} curation team will review the submitted improvements and publish them onto the {% data variables.product.prodname_advisory_database %} if accepted.
|
||||
{% ifversion fpt or ghec %}
|
||||
只有存储库所有者和管理员才能编辑存储库级别的安全公告。 For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
|
||||
Only repository owners and administrators can edit repository-level security advisories. For more information, see "[Editing a repository security advisory](/code-security/security-advisories/editing-a-security-advisory)."{% endif %}
|
||||
|
||||
## 在 GitHub Advisory 数据库中编辑通告
|
||||
## Editing advisories in the GitHub Advisory Database
|
||||
|
||||
1. 导航到 https://github.com/advisories。
|
||||
2. 选择您要参与的安全公告。
|
||||
3. 在页面右侧，单击 **Suggest improvements for this vulnerability（建议对此漏洞的改进）**链接。 
|
||||
4. 在贡献表单中，进行所需的改进。 您可以编辑或添加任何详细信息。
|
||||
5. 完成对公告的编辑后，单击 **Submit improvements（提交改进）**。
|
||||
6. 提交改进后，将创建一个包含您的更改的拉取请求，以供 {% data variables.product.prodname_security %} 策展团队在 [github/advisory-database](https://github.com/github/advisory-database) 中进行审核。 如果公告源自 {% data variables.product.prodname_dotcom %} 存储库，我们还将标记原始发布者以提供可选评论。 您可以查看拉取请求，并在其更新或关闭时收到通知。
|
||||
1. Navigate to https://github.com/advisories.
|
||||
2. Select the security advisory you would like to contribute to.
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability** link.
|
||||
|
||||
4. In the contribution form, make the desired improvements. You can edit or add any detail.
|
||||
5. When you finish editing the advisory, click **Submit improvements**.
|
||||
6. Once you submit your improvements, a pull request containing your changes will be created for review in [github/advisory-database](https://github.com/github/advisory-database) by the {% data variables.product.prodname_security %} curation team. If the advisory originated from a {% data variables.product.prodname_dotcom %} repository, we will also tag the original publisher for optional commentary. You can view the pull request and get notifications when it is updated or closed.
|
||||
|
||||
您还可以直接在 [github/advisory-database](https://github.com/github/advisory-database) 存储库中的公告文件上打开拉取请求。 更多信息请参阅[参与指南](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md)。
|
||||
You can also open a pull request directly on an advisory file in the [github/advisory-database](https://github.com/github/advisory-database) repository. For more information, see the [contribution guidelines](https://github.com/github/advisory-database/blob/main/CONTRIBUTING.md).
|
||||
|
||||
{% ifversion security-advisories-ghes-ghae %}
|
||||
## Editing advisories from {% data variables.product.product_location %}
|
||||
|
||||
If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
|
||||
If you have {% data variables.product.prodname_github_connect %} enabled for {% data variables.product.product_location %}, you will be able to see advisories by adding `/advisories` to the instance url.
|
||||
|
||||
1. Navigate to `https://HOSTNAME/advisories`.
|
||||
2. 选择您要参与的安全公告。
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}. 
|
||||
2. Select the security advisory you would like to contribute to.
|
||||
3. On the right-hand side of the page, click the **Suggest improvements for this vulnerability on Github.com.** link. A new tab opens with the same security advisory on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
4. Edit the advisory, following steps four through six in "[Editing advisories in the GitHub Advisory Database](#editing-advisories-in-the-github-advisory-database)" above.
|
||||
{% endif %}
|
||||
|
||||
@@ -43,6 +43,8 @@ For workflows initiated by {% data variables.product.prodname_dependabot %} (`gi
|
||||
For workflows initiated by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`) using the `pull_request_target` event, if the base ref of the pull request was created by {% data variables.product.prodname_dependabot %} (`github.actor == "dependabot[bot]"`), the `GITHUB_TOKEN` will be read-only and secrets are not available.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion actions-stable-actor-ids %}These restrictions apply even if the workflow is re-run by a different actor.{% endif %}
|
||||
|
||||
For more information, see ["Keeping your GitHub Actions and workflows secure: Preventing pwn requests"](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/).
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.3 %}
|
||||
@@ -224,8 +226,16 @@ jobs:
|
||||
|
||||
### Manually re-running a workflow
|
||||
|
||||
{% ifversion actions-stable-actor-ids %}
|
||||
|
||||
When you manually re-run a Dependabot workflow, it will run with the same privileges as before even if the user who initiated the rerun has different privileges. For more information, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)."
|
||||
|
||||
{% else %}
|
||||
|
||||
You can also manually re-run a failed Dependabot workflow, and it will run with a read-write token and access to secrets. Before manually re-running a failed workflow, you should always check the dependency being updated to ensure that the change doesn't introduce any malicious or unintended behavior.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Common Dependabot automations
|
||||
|
||||
Here are several common scenarios that can be automated using {% data variables.product.prodname_actions %}.
|
||||
@@ -466,7 +476,8 @@ on: pull_request_target
|
||||
|
||||
permissions:
|
||||
contents: write
|
||||
|
||||
pull-requests: write
|
||||
|
||||
jobs:
|
||||
dependabot:
|
||||
runs-on: ubuntu-latest
|
||||
@@ -497,6 +508,7 @@ on: pull_request
|
||||
|
||||
permissions:
|
||||
contents: write
|
||||
pull-requests: write
|
||||
|
||||
jobs:
|
||||
dependabot:
|
||||
|
||||
@@ -24,8 +24,16 @@ shortTitle: 推送保护
|
||||
|
||||
到目前为止，{% data variables.product.prodname_secret_scanning_GHAS %} 在推送_后_检查机密，并向用户提醒暴露的机密。 {% data reusables.secret-scanning.push-protection-overview %}
|
||||
|
||||
If a contributor bypasses a push protection block for a secret, {% data variables.product.prodname_dotcom %}:
|
||||
- generates an alert.
|
||||
- creates an alert in the "Security" tab of the repository.
|
||||
- adds the bypass event to the audit log.{% ifversion secret-scanning-push-protection-email %}
|
||||
- sends an email alert to organization owners, security managers, and repository administrators, with a link to the related secret and the reason why it was allowed.{% endif %}
|
||||
|
||||
{% data variables.product.prodname_secret_scanning_caps %} 作为推送保护，当前会扫描存储库中查找由以下服务提供商颁发的机密。
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
{% data reusables.secret-scanning.secret-list-private-push-protection %}
|
||||
|
||||
## 启用 {% data variables.product.prodname_secret_scanning %} 作为推送保护
|
||||
@@ -78,6 +86,8 @@ shortTitle: 推送保护
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-email %}
|
||||
|
||||
1. 访问 {% data variables.product.prodname_dotcom %} 在推送被阻止时返回的 URL。 
|
||||
{% data reusables.secret-scanning.push-protection-choose-allow-secret-options %}
|
||||
1. 单击 **Allow me to push this secret（允许我推送此机密）**。
|
||||
@@ -102,6 +112,8 @@ shortTitle: 推送保护
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-secrets-alerts %}
|
||||
|
||||
{% data reusables.secret-scanning.push-protection-allow-email %}
|
||||
|
||||
如果确认某个机密是真实的，并且打算稍后修复它，则应尽快修复。
|
||||
|
||||
1. 在 {% data variables.product.prodname_dotcom %} 阻止提交时显示在页面顶部的横幅中，单击 **Bypass protection（绕过保护）**。
|
||||
|
||||
@@ -34,6 +34,8 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
|
||||
|
||||
{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
{% data reusables.secret-scanning.partner-secret-list-public-repo %}
|
||||
{% endif %}
|
||||
|
||||
@@ -42,6 +44,8 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
|
||||
|
||||
When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% data variables.product.prodname_dotcom %} scans for secrets issued by the following service providers. {% ifversion ghec %}For more information about {% data variables.product.prodname_secret_scanning_GHAS %}, see "[About {% data variables.product.prodname_secret_scanning_GHAS %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-advanced-security)."{% endif %}
|
||||
|
||||
{% data reusables.secret-scanning.secret-scanning-pattern-pair-matches %}
|
||||
|
||||
If you use the REST API for secret scanning, you can use the `Secret type` to report on secrets from specific issuers. For more information, see "[Secret scanning](/enterprise-cloud@latest/rest/secret-scanning)."
|
||||
|
||||
{% ifversion ghes or ghae or ghec %}
|
||||
|
||||
@@ -57,7 +57,7 @@ topics:
|
||||
|
||||
## 保护您的通信令牌
|
||||
|
||||
代码通常需要通过网络与其他系统通信，并且需要机密（如密码或 API 密钥）进行身份验证。 系统需要访问这些机密才能运行，但最佳做法是不将它们包含在源代码中。 This is especially important for repositories to which many people might have access{% ifversion not ghae %} and critical for public repositories{% endif %}.
|
||||
代码通常需要通过网络与其他系统通信，并且需要机密（如密码或 API 密钥）进行身份验证。 系统需要访问这些机密才能运行，但最佳做法是不将它们包含在源代码中。 这对于许多人可能有权访问的存储库尤其重要{% ifversion not ghae %} 对于公共存储库{% endif %} 至关重要。
|
||||
|
||||
### 自动检测提交到存储库的机密
|
||||
|
||||
|
||||
@@ -52,6 +52,8 @@ The dependency review feature becomes available when you enable the dependency g
|
||||
|
||||
The action is available for all {% ifversion fpt or ghec %}public repositories, as well as private {% endif %}repositories that have {% data variables.product.prodname_GH_advanced_security %} enabled.
|
||||
|
||||
{% data reusables.dependency-review.action-enterprise %}
|
||||
|
||||
You can use the {% data variables.product.prodname_dependency_review_action %} in your repository to enforce dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository. For more information, see [`dependency-review-action`](https://github.com/actions/dependency-review-action).
|
||||
|
||||
|
||||
@@ -61,7 +63,7 @@ By default, the {% data variables.product.prodname_dependency_review_action %} c
|
||||
The action uses the Dependency Review REST API to get the diff of dependency changes between the base commit and head commit. You can use the Dependency Review API to get the diff of dependency changes, including vulnerability data, between any two commits on a repository. For more information, see "[Dependency review](/rest/reference/dependency-graph#dependency-review)."
|
||||
|
||||
{% ifversion dependency-review-action-configuration %}
|
||||
You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs. For example, you can specify the severity level that will make the action fail, or set an allow or deny list for licenses to scan. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)."
|
||||
You can configure the {% data variables.product.prodname_dependency_review_action %} to better suit your needs. For example, you can specify the severity level that will make the action fail{% ifversion dependency-review-action-licenses %}, or set an allow or deny list for licenses to scan{% endif %}. For more information, see "[Configuring dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review#configuring-the-dependency-review-github-action)."
|
||||
{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -56,17 +56,21 @@ topics:
|
||||
|
||||
以下是可用的配置选项：
|
||||
|
||||
| 选项 | 必选 | 用法 |
|
||||
| ------------------ | -- | ----------------------------------------------------------------------------------------------- |
|
||||
| `fail-on-severity` | 可选 | 定义严重性级别的阈值（`低`、`中`、`高`、`严重`）。</br>对于引入指定严重性级别或更高级别的漏洞的任何拉取请求，该操作都将失败。 |
|
||||
| `allow-licenses` | 可选 | 包含允许的许可证的列表。 您可以在 API 文档的[许可证](/rest/licenses)页面中找到此参数的可能值。</br>对于引入与列表不匹配的许可证的依赖项的拉取请求，该操作将失败。 |
|
||||
| `deny-licenses` | 可选 | 包含禁止的许可证列表。 您可以在 API 文档的[许可证](/rest/licenses)页面中找到此参数的可能值。</br>对于引入与列表匹配的许可证的依赖项的拉取请求，该操作将失败。 |
|
||||
| 选项 | 必选 | 用法 |
|
||||
| ------------------ | -- | --------------------------------------------------------------------- |
|
||||
| `fail-on-severity` | 可选 | 定义严重性级别的阈值（`低`、`中`、`高`、`严重`）。</br>对于引入指定严重性级别或更高级别的漏洞的任何拉取请求，该操作都将失败。 |
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `allow-licenses` | Optional | Contains a list of allowed licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that do not match the list.|{% endif %}
|
||||
{%- ifversion dependency-review-action-licenses %}
|
||||
| `deny-licenses` | Optional | Contains a list of prohibited licenses. You can find the possible values for this parameter in the [Licenses](/rest/licenses) page of the API documentation.</br>The action will fail on pull requests that introduce dependencies with licenses that match the list.|{% endif %}
|
||||
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
{% tip %}
|
||||
|
||||
**提示：** `allow-licenses` 和 `deny-licenses` 选项是互斥的。
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
|
||||
此 {% data variables.product.prodname_dependency_review_action %} 示例文件说明了如何使用这些配置选项。
|
||||
|
||||
@@ -88,6 +92,7 @@ jobs:
|
||||
with:
|
||||
# Possible values: "critical", "high", "moderate", "low"
|
||||
fail-on-severity: critical
|
||||
{% ifversion dependency-review-action-licenses %}
|
||||
# You can only can only include one of these two options: `allow-licenses` and `deny-licences`
|
||||
# ([String]). Only allow these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
@@ -96,6 +101,7 @@ jobs:
|
||||
# ([String]). Block the pull request on these licenses (optional)
|
||||
# Possible values: Any `spdx_id` value(s) from https://docs.github.com/en/rest/licenses
|
||||
# deny-licenses: LGPL-2.0, BSD-2-Clause
|
||||
{% endif %}
|
||||
```
|
||||
|
||||
有关配置选项的更多详细信息，请参阅 [`dependency-review-action`](https://github.com/actions/dependency-review-action#readme)。
|
||||
|
||||
@@ -75,6 +75,22 @@ shortTitle: 加密机密
|
||||
1. 在“Codespaces secrets（代码空间密码）”下您要删除的密码右侧，单击 **Delete（删除）**。 
|
||||
1. 阅读警告，然后单击 **OK（确定）**。 
|
||||
|
||||
## 使用密码
|
||||
|
||||
A secret is exported as an environment variable into the user's terminal session.
|
||||
|
||||
|
||||
|
||||
You can use secrets in a codespace after the codespace is built and is running. For example, a secret can be used:
|
||||
|
||||
* When launching an application from the integrated terminal or ssh session.
|
||||
* Within a dev container lifecycle script that is run after the codespace is running. For more information about dev container lifecycle scripts, see the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#lifecycle-scripts).
|
||||
|
||||
Codespace secrets cannot be used during:
|
||||
|
||||
* Codespace build time (that is, within a Dockerfile or custom entry point).
|
||||
* Within a dev container feature. For more information, see the `features` attribute in the documentation on containers.dev: [Specification](https://containers.dev/implementors/json_reference/#general-properties).
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[管理用于 {% data variables.product.prodname_github_codespaces %} 的仓库和组织的加密密钥](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces)"
|
||||
|
||||
@@ -34,8 +34,8 @@ shortTitle: 阻止您的帐户
|
||||
- 您在他们仓库协作者的身份被删除
|
||||
- 他们与您的赞助关系被取消
|
||||
- 任何对被阻止用户的待处理仓库或帐户继承者邀请或来自该用户的邀请都被取消
|
||||
- 用户作为协作者将从您拥有的所有项目板和项目（测试版）中删除
|
||||
- 您作为协作者将从该用户拥有的所有项目板和项目（测试版）中删除
|
||||
- The user is removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by you
|
||||
- You are removed as a collaborator from all the projects and {% data variables.projects.projects_v1_boards %} owned by the user
|
||||
|
||||
您阻止用户后，他们无法：
|
||||
- 向您发送任何通知，包括 [@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)您的用户名
|
||||
@@ -48,8 +48,8 @@ shortTitle: 阻止您的帐户
|
||||
- 在评论中交叉引用您的仓库
|
||||
- 复刻、关注、固定您的仓库或对其标星
|
||||
- 赞助您
|
||||
- 将您添加为其项目板和项目（测试版）的协作者
|
||||
- 对公共项目板和项目进行更改（测试版）
|
||||
- Add you as a collaborator on their projects and {% data variables.projects.projects_v1_boards %}
|
||||
- Make changes to your public projects and {% data variables.projects.projects_v1_boards %}
|
||||
|
||||
在您拥有的仓库中，被阻止的用户也不能：
|
||||
- 打开议题
|
||||
|
||||
@@ -39,45 +39,45 @@ X-Accepted-OAuth-Scopes: user
|
||||
|
||||
## 可用作用域
|
||||
|
||||
| 名称 | 描述 |
|
||||
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
|
||||
| 名称 | 描述 |
|
||||
| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion not ghae %}
|
||||
| **`（无作用域）`** | 授予对公共信息的只读访问权限（包括用户个人资料信息、公共仓库信息和 gist）{% endif %}{% ifversion ghes or ghae %}
|
||||
| **`site_admin`** | 授予站点管理员对 [{% data variables.product.prodname_ghe_server %} 管理 API 端点](/rest/reference/enterprise-admin)的访问权限。{% endif %}
|
||||
| **`repo`** | 授予对仓库（包括私有仓库）的完全访问权限。 这包括对仓库和组织的代码、提交状态、仓库和组织项目、邀请、协作者、添加团队成员身份、部署状态以及仓库 web 挂钩的读取/写入权限。 还授予管理用户项目的权限。 |
|
||||
|  `repo:status` | 授予对{% ifversion fpt %}公共和私有{% elsif ghec or ghes %}公共、私有和内部{% elsif ghae %}私有和内部{% endif %}仓库中的提交状态的读/写访问权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 |
|
||||
| **`repo`** | Grants full access to public{% ifversion ghec or ghes or ghae %}, internal,{% endif %} and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. **Note**: In addition to repository related resources, the `repo` scope also grants access to manage organization-owned resources including projects, invitations, team memberships and webhooks. This scope also grants the ability to manage projects owned by users. |
|
||||
|  `repo:status` | 授予对{% ifversion fpt %}公共和私有{% elsif ghec or ghes %}公共、私有和内部{% elsif ghae %}私有和内部{% endif %}仓库中的提交状态的读/写访问权限。 仅在授予其他用户或服务对私有仓库提交状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。 |
|
||||
|  `repo_deployment` | 授予对{% ifversion not ghae %}公共{% else %}内部{% endif %}和私有仓库的[部署状态](/rest/reference/repos#deployments)的访问权限。 仅在授予其他用户或服务对部署状态的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% ifversion not ghae %}
|
||||
|  `public_repo` | 将访问权限限制为公共仓库。 这包括对公共仓库和组织的代码、提交状态、仓库项目、协作者以及部署状态的读取/写入权限。 标星公共仓库也需要此权限。{% endif %}
|
||||
|  `repo:invite` | 授予接受/拒绝仓库协作邀请的权限。 仅在授予其他用户或服务对邀请的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% ifversion fpt or ghes or ghec %}
|
||||
|  `security_events` | 授予：<br/>对 [{% data variables.product.prodname_code_scanning %} API](/rest/reference/code-scanning) 中安全事件的读取和写入权限<br/>对 {%- ifversion ghec %}[{% data variables.product.prodname_secret_scanning %} API](/rest/reference/secret-scanning) 中安全事件的读取和写入权限<br/>{%- endif %}仅在授予其他用户或服务对安全事件的访问权限而*不*授予对代码的访问权限时，才需要此作用域。{% endif %}
|
||||
| **`admin:repo_hook`** | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中仓库挂钩的读取、写入、ping 和删除访问权限。 `repo` {% ifversion fpt or ghec or ghes %}和 `public_repo` 范围授予{% else %}范围授予{% endif %}对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 |
|
||||
|  `write:repo_hook` | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中挂钩的读取、写入和 ping 访问权限。 |
|
||||
|  `read:repo_hook` | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中挂钩的读取和 ping 访问权限。 |
|
||||
| **`admin:org`** | 全面管理组织及其团队、项目和成员。 |
|
||||
|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 |
|
||||
|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 |
|
||||
| **`admin:public_key`** | 全面管理公钥。 |
|
||||
|  `write:public_key` | 创建、列出和查看公钥的详细信息。 |
|
||||
|  `read:public_key` | 列出和查看公钥的详细信息。 |
|
||||
| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 |
|
||||
| **`gist`** | 授予对 gist 的写入权限。 |
|
||||
| **`通知`** | 授予：<br/>* 对用户通知的读取权限 <br/>* 对线程的标记读取权限 <br/>* 对仓库的关注和取消关注权限，以及<br/>* 对线程订阅的读取、写入和删除权限。 |
|
||||
| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 |
|
||||
|  `read:user` | 授予读取用户个人资料数据的权限。 |
|
||||
|  `user:email` | 授予对用户电子邮件地址的读取权限。 |
|
||||
| **`admin:repo_hook`** | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中仓库挂钩的读取、写入、ping 和删除访问权限。 `repo` {% ifversion fpt or ghec or ghes %}和 `public_repo` 范围授予{% else %}范围授予{% endif %}对仓库（包括仓库挂钩）的完全访问权限。 使用 `admin:repo_hook` 作用域将访问权限限制为仅仓库挂钩。 |
|
||||
|  `write:repo_hook` | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中挂钩的读取、写入和 ping 访问权限。 |
|
||||
|  `read:repo_hook` | 授予对{% ifversion fpt %}公共或私有{% elsif ghec or ghes %}公共、私有或内部{% elsif ghae %}私有或内部{% endif %}仓库中挂钩的读取和 ping 访问权限。 |
|
||||
| **`admin:org`** | 全面管理组织及其团队、项目和成员。 |
|
||||
|  `write:org` | 对组织成员身份、组织项目和团队成员身份的读取和写入权限。 |
|
||||
|  `read:org` | 对组织成员身份、组织项目和团队成员身份的只读权限。 |
|
||||
| **`admin:public_key`** | 全面管理公钥。 |
|
||||
|  `write:public_key` | 创建、列出和查看公钥的详细信息。 |
|
||||
|  `read:public_key` | 列出和查看公钥的详细信息。 |
|
||||
| **`admin:org_hook`** | 授予对组织挂钩的读取、写入、ping 和删除权限。 **注：**OAuth 令牌只能对由 OAuth 应用程序创建的组织挂钩执行这些操作。 个人访问令牌只能对用户创建的组织挂钩执行这些操作。 |
|
||||
| **`gist`** | 授予对 gist 的写入权限。 |
|
||||
| **`通知`** | 授予：<br/>* 对用户通知的读取权限 <br/>* 对线程的标记读取权限 <br/>* 对仓库的关注和取消关注权限，以及<br/>* 对线程订阅的读取、写入和删除权限。 |
|
||||
| **`用户`** | 仅授予对个人资料的读取/写入权限。 请注意，此作用域包括 `user:email` 和 `user:follow`。 |
|
||||
|  `read:user` | 授予读取用户个人资料数据的权限。 |
|
||||
|  `user:email` | 授予对用户电子邮件地址的读取权限。 |
|
||||
|  `user:follow` | 授予关注或取消关注其他用户的权限。{% ifversion projects-oauth-scope %}
|
||||
| **`project`** | 授予对用户和组织项目（测试版）的读/写访问权限。 |
|
||||
|  `read:project` | 授予对用户和组织项目（测试版）的只读访问权限。{% endif %}
|
||||
| **`delete_repo`** | 授予删除可管理仓库的权限。 |
|
||||
| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 |
|
||||
|  `read:discussion` | 允许对团队讨论进行读取访问。 |
|
||||
| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 |
|
||||
| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 |
|
||||
| **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 |
|
||||
| **`admin:gpg_key`** | 全面管理 GPG 密钥。 |
|
||||
|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 |
|
||||
| **`project`** | Grants read/write access to user and organization {% data variables.projects.projects_v2 %}. |
|
||||
|  `read:project` | Grants read only access to user and organization {% data variables.projects.projects_v2 %}.{% endif %}
|
||||
| **`delete_repo`** | 授予删除可管理仓库的权限。 |
|
||||
| **`write:discussion`** | 授予对团队讨论的读取和写入权限。 |
|
||||
|  `read:discussion` | 允许对团队讨论进行读取访问。 |
|
||||
| **`write:packages`** | 授予在 {% data variables.product.prodname_registry %} 中上传或发布包的权限。 更多信息请参阅“[发布包](/github/managing-packages-with-github-packages/publishing-a-package)”。 |
|
||||
| **`read:packages`** | 授予从 {% data variables.product.prodname_registry %} 下载或安装包的权限。 更多信息请参阅“[安装包](/github/managing-packages-with-github-packages/installing-a-package)”。 |
|
||||
| **`delete:packages`** | 授予从 {% data variables.product.prodname_registry %} 删除包的权限。 更多信息请参阅“[删除和恢复软件包](/packages/learn-github-packages/deleting-and-restoring-a-package)”。 |
|
||||
| **`admin:gpg_key`** | 全面管理 GPG 密钥。 |
|
||||
|  `write:gpg_key` | 创建、列出和查看 GPG 密钥的详细信息。 |
|
||||
|  `read:gpg_key` | 列出和查看 GPG 密钥的详细信息。{% ifversion fpt or ghec %}
|
||||
| **`代码空间`** | 授予创建和管理代码空间的能力。 Codespaces 可以暴露可能有不同范围集的 GITHUB_TOKEN。 更多信息请参阅“[{% data variables.product.prodname_github_codespaces %} 中的安全性](/codespaces/codespaces-reference/security-in-github-codespaces#authentication)”。{% endif %}
|
||||
| **`工作流程`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可以暴露可能有不同范围集的 `GITHUB_TOKEN`。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。 |
|
||||
| **`工作流程`** | 授予添加和更新 {% data variables.product.prodname_actions %} 工作流程文件的权限。 如果在同一仓库中的另一个分支上存在相同的文件(具有相同的路径和内容)，则工作流程文件可以在没有此作用域的情况下提交。 工作流程文件可以暴露可能有不同范围集的 `GITHUB_TOKEN`。 更多信息请参阅“[工作流程中的身份验证](/actions/reference/authentication-in-a-workflow#permissions-for-the-github_token)。 |
|
||||
|
||||
{% note %}
|
||||
|
||||
|
||||
@@ -891,10 +891,10 @@ Key | Type | Description
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: This event does not occur for Projects (beta).
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -923,10 +923,10 @@ Key | Type | Description
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: This event does not occur for Projects (beta).
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
@@ -953,6 +953,14 @@ Key | Type | Description
|
||||
- Organization webhooks
|
||||
- {% data variables.product.prodname_github_apps %} with the `repository_projects` or `organization_projects` permission
|
||||
|
||||
{% ifversion projects-v2 %}
|
||||
{% note %}
|
||||
|
||||
**Note**: This event only occurs for {% data variables.product.prodname_projects_v1 %}.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
### Webhook payload object
|
||||
|
||||
{% data reusables.webhooks.project_column_properties %}
|
||||
@@ -971,11 +979,11 @@ Key | Type | Description
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Webhook events for Projects (beta) are currently in beta and subject to change. To share feedback about Projects (beta) webhooks with {% data variables.product.product_name %}, see the [Projects (beta) webhook feedback discussion](https://github.com/github/feedback/discussions/17405).
|
||||
**Note:** Webhook events for {% data variables.projects.projects_v2 %} are currently in beta and subject to change. To share feedback about {% data variables.projects.projects_v2 %} webhooks with {% data variables.product.product_name %}, see the [Projects webhook feedback discussion](https://github.com/github/feedback/discussions/17405).
|
||||
|
||||
{% endnote %}
|
||||
|
||||
Activity related to items in a Projects (beta) project. {% data reusables.webhooks.action_type_desc %} For more information, see "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)."
|
||||
Activity related to items in a {% data variables.projects.project_v2 %}. {% data reusables.webhooks.action_type_desc %} For more information, see "[About {% data variables.projects.projects_v2 %}](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
|
||||
### Availability
|
||||
|
||||
@@ -987,7 +995,7 @@ Activity related to items in a Projects (beta) project. {% data reusables.webhoo
|
||||
Key | Type | Description
|
||||
----|------|-------------
|
||||
`action`|`string` | The action that was performed on the project item. Can be one of `archived`, `converted`, `created`, `edited`, `restored`, `deleted`, or `reordered`.
|
||||
`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects (beta)](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)."
|
||||
`projects_v2_item`|`object` | The project item itself. To find more information about the project item, you can use `node_id` (the node ID of the project item) and `project_node_id` (the node ID of the project) to query information in the GraphQL API. For more information, see "[Using the API to manage projects](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)."
|
||||
`changes`|`object` | The changes to the project item.
|
||||
{% data reusables.webhooks.org_desc %}
|
||||
{% data reusables.webhooks.app_desc %}
|
||||
|
||||
@@ -14,7 +14,7 @@ shortTitle: 参与讨论
|
||||
|
||||
除了开始或查看讨论和投票之外，您还可以根据讨论作者的原始评论发表评论。 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。
|
||||
|
||||
{% ifversion fpt or ghec %}You can block users and report disruptive content to maintain a safe and pleasant environment for yourself on {% data variables.product.product_name %}. For more information, see "[Maintaining your safety on {% data variables.product.prodname_dotcom %}](/communities/maintaining-your-safety-on-github)."{% endif %}
|
||||
{% ifversion fpt or ghec %}您可以阻止用户并报告破坏性内容，以便自己在 {% data variables.product.product_name %} 上保持一个安全愉快的环境。 更多信息请参阅“[保持您在 {% data variables.product.prodname_dotcom %} 上的安全](/communities/maintaining-your-safety-on-github)”。{% endif %}
|
||||
|
||||
## 基本要求
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ versions:
|
||||
|
||||
您可以创建和参与讨论、议题及拉取请求，具体取决于您希望进行的对话类型。
|
||||
|
||||
您可以使用 {% data variables.product.prodname_discussions %} 讨论大局想法、集思广益，并在将项目提交到议题之前，先找出项目的具体细节，然后可以确定议题的范围。 {% data variables.product.prodname_discussions %} is useful for teams in a number of scenarios.
|
||||
您可以使用 {% data variables.product.prodname_discussions %} 讨论大局想法、集思广益，并在将项目提交到议题之前，先找出项目的具体细节，然后可以确定议题的范围。 {% data variables.product.prodname_discussions %} 在许多情况下对团队有用：
|
||||
- 您处于项目的发现阶段，仍在了解您的团队希望由哪个主管领导
|
||||
- 您希望从更广泛的社区收集有关项目的反馈
|
||||
- 您希望将漏洞修复、功能请求和常规对话分开
|
||||
@@ -33,7 +33,7 @@ versions:
|
||||
|
||||
## 遵守参与指南
|
||||
|
||||
Before you open a discussion in a repository, check to see if the repository has contributing guidelines. CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
|
||||
在存储库中打开讨论之前，请检查该存储库是否有参与指南。 CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
|
||||
|
||||
更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
|
||||
|
||||
|
||||
@@ -15,11 +15,11 @@ shortTitle: 授予更高权限
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion. 
|
||||
1. 将贡献者列表与其对存储库的访问权限进行比较，或者，对于组织讨论，比较源存储库，以查看谁有资格主持讨论。 
|
||||
|
||||
## 第 2 步：审查 {% data variables.product.prodname_discussions %} 的权限级别
|
||||
|
||||
People with triage permissions for a repository can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. 同样，对组织讨论的源存储库具有分类权限的人员可以主持组织的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
|
||||
对仓库具有分类权限的人可以通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持仓库的讨论。 同样，对组织讨论的源存储库具有分类权限的人员可以主持组织的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
|
||||
|
||||
有关仓库权限级别和 {% data variables.product.prodname_discussions %} 的更多信息，请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: GitHub Discussions 文档
|
||||
shortTitle: GitHub Discussions
|
||||
intro: '{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an{% ifversion fpt or ghec %} open source or{% endif %} internal project. 社区成员可以提出和回答问题，分享更新，进行开放式对话，并关注影响社区工作方式的决策。'
|
||||
intro: '{% data variables.product.prodname_discussions %} 是一个围绕{% ifversion fpt or ghec %}开源或{% endif %}内部项目为社区提供协作沟通的论坛。 社区成员可以提出和回答问题，分享更新，进行开放式对话，并关注影响社区工作方式的决策。'
|
||||
introLinks:
|
||||
quickstart: /discussions/quickstart
|
||||
featuredLinks:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 主持讨论
|
||||
intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.'
|
||||
intro: '您可以通过将评论标记为答案、锁定或解锁讨论、将议题转换为讨论，以及编辑或删除评论、讨论和不符合{% ifversion fpt or ghec %} 社区行为准则{% elsif ghes > 3.5 %} 组织的参与指南{% endif %} 的类别，以促进健康的协作。'
|
||||
permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
|
||||
versions:
|
||||
feature: discussions
|
||||
@@ -9,7 +9,7 @@ versions:
|
||||
|
||||
## 关于主持讨论
|
||||
|
||||
{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. 同样，如果您具有组织讨论的源存储库的分类权限，则可以主持该组织的讨论。
|
||||
{% data reusables.discussions.about-discussions %}如果您对仓库具有分类权限，便可通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持仓库的讨论。 同样，如果您具有组织讨论的源存储库的分类权限，则可以主持该组织的讨论。
|
||||
|
||||
## 将评论标记为答案
|
||||
|
||||
|
||||
@@ -1,76 +1,80 @@
|
||||
---
|
||||
title: GitHub Discussions 快速入门
|
||||
intro: '在现有仓库或组织上启用 {% data variables.product.prodname_discussions %} ，并发起与社区的对话。'
|
||||
title: Quickstart for GitHub Discussions
|
||||
intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
feature: discussions
|
||||
shortTitle: 快速入门
|
||||
shortTitle: Quickstart
|
||||
---
|
||||
|
||||
|
||||
## 简介
|
||||
## Introduction
|
||||
|
||||
{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. 不像 {% data variables.product.prodname_github_issues %}，讨论用于需要透明和可访问的对话，但不需要在项目板上进行跟踪，并且与代码无关。 讨论使公共论坛中能够进行流畅、公开的对话。
|
||||
{% data variables.product.prodname_discussions %} is a collaborative communication forum for the community around an open source or internal project. Discussions are for conversations that need to be transparent and accessible but do not need to be tracked on a project board and are not related to code, unlike {% data variables.product.prodname_github_issues %}. Discussions enable fluid, open conversation in a public forum.
|
||||
|
||||
通过连接和提供更集中的区域来连接和查找信息，讨论为更多协作对话提供了空间。
|
||||
Discussions give a space for more collaborative conversations by connecting and giving a more centralized area to connect and find information.
|
||||
|
||||
## 在仓库中启用 {% data variables.product.prodname_discussions %}
|
||||
## Enabling {% data variables.product.prodname_discussions %} on your repository
|
||||
|
||||
Repository owners and people with write access can enable {% data variables.product.prodname_discussions %} for a community on their public{% ifversion ghes > 3.5 %}, internal{% endif %} and private repositories. The visibility of a discussion is inherited from the repository the discussion is created in.
|
||||
|
||||
当您首次启用 {% data variables.product.prodname_discussions %} 时，将邀请您配置欢迎帖子。
|
||||
When you first enable {% data variables.product.prodname_discussions %}, you will be invited to configure a welcome post.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %} **Settings（设置）**。 
|
||||
1. 在“Features（功能）”下，单击 **Set up discussions（设置讨论）**。 
|
||||
1. 在“Start a new discussion（开始新讨论）”下，编辑模板以与要为社区设置的资源和语气保持一致。
|
||||
1. 单击 **Start discussion（开始讨论）**。 
|
||||
1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %}
|
||||
**Settings**.
|
||||
|
||||
1. Under "Features", click **Set up discussions**.
|
||||
|
||||
1. Under "Start a new discussion," edit the template to align with the resources and tone you want to set for your community.
|
||||
1. Click **Start discussion**.
|
||||
|
||||
|
||||
## 在组织上启用 {% data variables.product.prodname_discussions %}
|
||||
## Enabling {% data variables.product.prodname_discussions %} on your organization
|
||||
|
||||
组织所有者可以为其组织启用 {% data variables.product.prodname_discussions %}。
|
||||
Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.
|
||||
|
||||
{% data reusables.discussions.about-organization-discussions %}
|
||||
|
||||
{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %}
|
||||
|
||||
## 欢迎参与您的讨论
|
||||
## Welcoming contributions to your discussions
|
||||
|
||||
您可以欢迎您的社区，并通过创建欢迎帖子并将帖子固定到您的 {% data variables.product.prodname_discussions %} 页面，在存储库或组织中引入一种新的沟通方式。 固定和锁定讨论有助于人们知道帖子是作为公告发布的。 您可以使用公告将人员链接到更多资源，并指导在社区中开始讨论。 有关固定讨论的详细信息，请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)”。
|
||||
You can welcome your community and introduce a new way to communicate in a repository or organization by creating a welcome post and pinning the post to your {% data variables.product.prodname_discussions %} page. Pinning and locking discussions helps people know that a post is meant as an announcement. You can use announcements as a way to link people to more resources and offer guidance for opening discussions in your community. For more information about pinning a discussion, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
|
||||
|
||||
|
||||
## 为贡献者设置社区指南
|
||||
## Setting up community guidelines for contributors
|
||||
|
||||
对于仓库讨论，您可以设置参与指南，以鼓励协作者进行与仓库相关的有意义、有用的对话。 您还可以更新仓库的 README，以传达协作者何时应打开问题或讨论的期望。 For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. You can also update the repository's README to communicate expectations on when collaborators should open an issue or discussion. For more information about providing guidelines for your project, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)" and{% endif %} "[Setting up your project for healthy contributions](/communities/setting-up-your-project-for-healthy-contributions)."
|
||||
|
||||
对于组织讨论，您可以通过创建组织配置文件 README 来共享有关如何与组织互动的信息。 更多信息请参阅“[自定义组织的配置文件](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)”。
|
||||
For organization discussions, you share information about how to engage with your organization by creating an organization profile README. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
|
||||
|
||||
## 创建新讨论
|
||||
## Creating a new discussion
|
||||
|
||||
任何可以查看仓库的认证用户都可以在该仓库中创建讨论。 同样，由于组织讨论基于源存储库，因此任何可以查看源存储库的经过身份验证的用户都可以在该组织中创建讨论。
|
||||
Any authenticated user who can view the repository can create a discussion in that repository. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a discussion in that organization.
|
||||
|
||||
{% data reusables.discussions.starting-a-discussion %}
|
||||
|
||||
## 创建新投票
|
||||
## Creating a new poll
|
||||
|
||||
任何可以查看仓库的认证用户都可以创建投票。 同样，由于组织讨论基于源存储库，因此任何可以查看源存储库的经过身份验证的用户都可以在该组织中创建投票。
|
||||
Any authenticated user who can view a repository can create a poll. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a poll in that organization.
|
||||
|
||||
{% data reusables.discussions.starting-a-poll %}
|
||||
|
||||
## 组织讨论
|
||||
## Organizing discussions
|
||||
|
||||
仓库所有者和对仓库具有写入权限的人可以创建新类别来保持讨论井然有序。 同样，由于组织讨论基于源存储库，因此存储库所有者和对源存储库具有写入访问权限的人员可以为组织讨论创建新类别。
|
||||
Repository owners and people with write access to the repository can create new categories to keep discussions organized. Similarly, since organization discussions are based on a source repository, repository owners and people with write access to the source repository can create new categories for organization discussions.
|
||||
|
||||
Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. 讨论也可以在创建后重新分类。 更多信息请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
|
||||
Collaborators participating in and creating new discussions can group discussions into the most relevant existing categories. Discussions can also be recategorized after they are created. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
|
||||
|
||||
{% data reusables.discussions.you-can-label-discussions %}
|
||||
|
||||
## 促进健康的对话
|
||||
## Promoting healthy conversations
|
||||
|
||||
对存储库或组织讨论的源存储库具有写入权限的人员可以通过固定讨论、删除不再有用或对社区有害的讨论，以及将讨论转移到组织拥有的更相关的存储库，来帮助显示重要的对话。 更多信息请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions)”。
|
||||
People with write permissions for the repository, or for the source repository for organization discussions, can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
|
||||
|
||||
对存储库或组织讨论的源存储库具有分类权限的人员，可以通过将评论标记为答案、锁定不再有用或对社区有害的讨论，以及在想法仍处于开发的早期阶段时将议题转换为讨论，来帮助调节项目的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
|
||||
People with triage permissions for the repository, or for the source repository for organization discussions, can help moderate a project's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)."
|
||||
|
||||
## 后续步骤
|
||||
## Next steps
|
||||
|
||||
一旦有明确的路径来确定范围以及将想法从概念变为现实，您就可以创建议题并开始跟踪进度。 有关从讨论创建议题的更多信息，请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
|
||||
Once there is a clear path to scope work out and move an idea from concept to reality, you can create an issue and start tracking your progress. For more information on creating an issue from a discussion, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions)."
|
||||
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
title: Getting started with GitHub Community Exchange
|
||||
shortTitle: 入门
|
||||
intro: 'Learn how to access {% data variables.product.prodname_community_exchange %} and submit your repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
---
|
||||
|
||||
## 简介
|
||||
|
||||
{% data reusables.education.about-github-community-exchange-intro %} {% data variables.product.prodname_community_exchange %} can help you make your first open source contribution or grow your own open source project.
|
||||
|
||||
For more information about how {% data variables.product.prodname_community_exchange %} can help you as a student, see "[About {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)."
|
||||
|
||||
## Accessing {% data variables.product.prodname_community_exchange %}
|
||||
|
||||
{% data reusables.education.access-github-community-exchange %}
|
||||
|
||||
## Finding interesting repositories
|
||||
|
||||
You can browse repositories submitted to {% data variables.product.prodname_community_exchange %} from the gallery page.
|
||||
|
||||
As you think about what open source repositories may be interesting, consider if you're wanting to learn or collaborate, or if there are particular topics or languages that could be a good starting point.
|
||||
|
||||
When exploring repositories in the {% data variables.product.prodname_community_exchange %} gallery, you can filter available repositories by purpose, topics, or languages, and search for repositories by name and description. You can sort the list of repositories in the gallery by submission date, or by the number of stars, forks, or issues a repository has.
|
||||
|
||||
|
||||
|
||||
## Starring repositories
|
||||
|
||||
You can star repositories listed in the {% data variables.product.prodname_community_exchange %} gallery. Starring makes it easy to find a repository in the gallery again later. 对仓库加星标也可表示赞赏仓库维护员的工作。
|
||||
|
||||
Repository listings in the {% data variables.product.prodname_community_exchange %} gallery can be sorted on the number of stars a repository has.
|
||||
|
||||
To star a repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to star, and click {% octicon "star" aria-label="The star icon" %} **Star** button found right by its name.
|
||||
|
||||
## Reporting abuse
|
||||
|
||||
The {% data variables.product.prodname_community_exchange %} community moderates repository submissions. You can report abusive repositories, spammy, or disruptive content at any time.
|
||||
|
||||
To report an abusive repository: Go to your {% data variables.product.prodname_community_exchange %} home page, find the repository you want to report, click the {% octicon "kebab-horizontal" aria-label="The edit icon" %} drop-down right by its name, then click {% octicon "report" aria-label="The report symbol" %} **Report abuse**.
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于 {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)"
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
title: Contribute with GitHub Community Exchange
|
||||
shortTitle: '{% data variables.product.prodname_community_exchange %}'
|
||||
intro: 'With {% data variables.product.prodname_community_exchange %}, you can use {% data variables.product.product_name %} to contribute to open source and build your portfolio.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
children:
|
||||
- /getting-started-with-github-community-exchange
|
||||
- /submitting-your-repository-to-github-community-exchange
|
||||
- /managing-your-submissions-to-github-community-exchange
|
||||
---
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: Managing your submissions to GitHub Community Exchange
|
||||
shortTitle: Manage your submissions
|
||||
intro: 'You can manage the purpose, topics, and offers assigned to each of your repositories in the {% data variables.product.prodname_community_exchange %} gallery, or delete your repository submissions.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
---
|
||||
|
||||
## About your submissions
|
||||
|
||||
During the {% data variables.product.prodname_community_exchange %} submission process, you will choose a purpose, topics, and offers for your repository. Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published with these details. For more information, see "[Submitting your repository to GitHub Community Exchange](/education/contribute-with-github-community-exchange/submitting-your-repository-to-github-community-exchange)."
|
||||
|
||||
After you've submitted, you can still edit the topics and offers associated with your repository. You can also update the purpose of your repository by changing the corresponding topic(s). 更多信息请参阅“[使用主题对仓库分类](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)”。
|
||||
|
||||
The language associated with your repository is the primary language used and is automatically determined by {% data variables.product.prodname_dotcom %}. For more information, see "[About repository languages](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-repository-languages)."
|
||||
|
||||
The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
|
||||
|
||||
## Managing your submissions
|
||||
|
||||
1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
|
||||
1. Above the list of repositories, click the **Submissions** tab. 
|
||||
1. Optionally, edit your submitted repository. To the right of the repository you want to edit, click {% octicon "pencil" aria-label="The edit icon" %} to go directly to your repository homepage. From there, you can update the purpose, topics, and offers assigned to your repository.
|
||||
1. Optionally, delete a submitted repository from the gallery. To the right of the repository submission you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
@@ -0,0 +1,48 @@
|
||||
---
|
||||
title: Submitting your repository to GitHub Community Exchange
|
||||
shortTitle: Submit your repository
|
||||
intro: 'You can submit your repository to {% data variables.product.prodname_community_exchange %} for others to view or contribute to.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
---
|
||||
|
||||
## About repository submissions
|
||||
|
||||
Only public repositories owned by personal accounts can be submitted to {% data variables.product.prodname_community_exchange %}.
|
||||
|
||||
There are three types of repository submissions:
|
||||
|
||||
- **Learn.** A repository to share step-by-step instructions to build a project.
|
||||
- **Collaborate.** A repository seeking collaborators to work on a project.
|
||||
- **Learn and Collaborate.** A repository which is a combination of `Learn` and `Collaborate`.
|
||||
|
||||
Consider what the main purpose of your repository is when choosing the type of submission for your repository.
|
||||
|
||||
To promote your project and make it more discoverable to other students, you should assign one or more topics and {% data variables.product.prodname_student_pack %} offers to your repository. 更多信息请参阅“[使用主题对仓库分类](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/classifying-your-repository-with-topics)”。
|
||||
|
||||
Once a repository has been submitted to {% data variables.product.prodname_community_exchange %}, it will be published immediately with the purpose, topics, and offers you've chosen. The {% data variables.product.prodname_community_exchange %} community moderates all repository submissions.
|
||||
|
||||
### Submission requirements
|
||||
|
||||
Your repository must meet a minimum set of requirements for a submission to be accepted. During the submission process, if the submission criteria hasn't been met for your selected repository, you will be notified of the missing items.
|
||||
|
||||
For a submission with a purpose of `Learn`, your repository must have:
|
||||
- A description.
|
||||
- A LEARN.md file to provide step-by-step instructions, with text and/or media, on how you built your project. Ideally, your LEARN.md file will deconstruct your project into small components and provide thorough details of each step, so that other students can code their project by following your instructions.
|
||||
- A README.md file to provide a detailed description of your project.
|
||||
|
||||
For a submission with a purpose of `Collaborate`, your repository must have:
|
||||
- A description.
|
||||
- A README.md file to provide a detailed description of your project.
|
||||
- One or more issues for collaborators to work on.
|
||||
|
||||
A good repository submission for both `Learn` and `Collaborate` purposes, is a repository that follows community standards. For more information, see "[About community profiles for public repositories](/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)."
|
||||
|
||||
## Submitting your repository
|
||||
|
||||
1. From your {% data variables.product.prodname_global_campus %} dashboard, navigate to the {% data variables.product.prodname_community_exchange %} home page.
|
||||
1. Above the list of repositories, to the right of the search and dropdown filters, click **Add repository**. 
|
||||
1. Use the **What is the purpose of your submission?** drop-down menu and select one or more entries matching your submission. 
|
||||
1. Use the **Which repository would you like to use?** drop-down menu and select the repository for your submission. If the submission criteria hasn't been met, you will be notified of the missing items. 
|
||||
1. Use the **Which offers did you use for your project?** drop-down menu and select one or more entries matching your submission. 
|
||||
1. Click **Submit the project**.
|
||||
@@ -1,30 +1,30 @@
|
||||
---
|
||||
title: About GitHub Community Exchange
|
||||
intro: 'As a student, learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
|
||||
title: 关于 GitHub Community Exchange
|
||||
intro: 'Learn the skills you need to contribute to open source projects and grow your own portfolio, with {% data variables.product.prodname_community_exchange %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
shortTitle: Community Exchange
|
||||
shortTitle: About Community Exchange
|
||||
---
|
||||
|
||||
## About {% data variables.product.prodname_community_exchange %}
|
||||
## 关于 {% data variables.product.prodname_community_exchange %}
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} is a student community within the {% data variables.product.prodname_global_campus %} portal. As a student, it's a place where you can get exposure for your project and discover other student repositories in need of collaborators and maintainers.
|
||||
{% data reusables.education.about-github-community-exchange-intro %}
|
||||
|
||||
|
||||
|
||||
|
||||
You can help your peers learn open source skills, become a project maintainer, and grow your {% data variables.product.prodname_dotcom %} portfolio and network within a safe and verified community platform.
|
||||
您可以帮助同行学习开源技能，成为项目维护者，并在安全且经过验证的社区平台中发展您的 {% data variables.product.prodname_dotcom %} 组合和网络。
|
||||
|
||||
{% data variables.product.prodname_community_exchange %} allows you to:
|
||||
- Discover student created repositories
|
||||
- Star repositories of interest
|
||||
- Submit a repository in need of collaborators
|
||||
- Submit a repository to teach new skills
|
||||
- Manage your repository submissions
|
||||
{% data variables.product.prodname_community_exchange %} 允许您：
|
||||
- 发现学生创建的存储库
|
||||
- 对感兴趣的存储库标星
|
||||
- 提交需要协作者的存储库
|
||||
- 提交存储库以教授新技能
|
||||
- 管理存储库提交
|
||||
|
||||
To access {% data variables.product.prodname_community_exchange %}, visit your {% data variables.product.prodname_global_campus %} dashboard at https://education.github.com.
|
||||
For more information, see "[Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)."
|
||||
|
||||
If you're a student or faculty member at an accredited educational institution, you can apply for {% data variables.product.prodname_education %} benefits, which includes access to {% data variables.product.prodname_community_exchange %} within {% data variables.product.prodname_global_campus %}.
|
||||
{% data reusables.education.access-github-community-exchange %}
|
||||
|
||||
- If you’re a student and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [student application form]( https://education.github.com/discount_requests/student_application). For more information, see "[About GitHub Education for students](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students)."
|
||||
## 延伸阅读
|
||||
|
||||
- If you’re an educator and you haven't joined {% data variables.product.prodname_education %} yet, apply using the [teacher application form]( https://education.github.com/discount_requests/teacher_application). For more information, see "[About GitHub Education for educators](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount)."
|
||||
- "[开始使用 {% data variables.product.prodname_community_exchange %}](/education/contribute-with-github-community-exchange/getting-started-with-github-community-exchange)"
|
||||
|
||||
@@ -46,3 +46,5 @@ shortTitle: 指南
|
||||
- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
|
||||
- [关于 Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
|
||||
- [关于 Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
|
||||
- [关于 {% data variables.product.prodname_community_exchange %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange)
|
||||
- [Contribute with GitHub Community Exchange](/education/contribute-with-github-community-exchange)
|
||||
|
||||
@@ -27,6 +27,7 @@ versions:
|
||||
children:
|
||||
- /quickstart
|
||||
- /explore-the-benefits-of-teaching-and-learning-with-github-education
|
||||
- /contribute-with-github-community-exchange
|
||||
- /manage-coursework-with-github-classroom
|
||||
- /guides
|
||||
---
|
||||
|
||||
@@ -26,7 +26,17 @@ topics:
|
||||
|
||||
1. 导航到 `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife。
|
||||
2. 单击 **Fork（复刻）**。 
|
||||
1. {% data variables.product.product_name %} 将带您进入 Spoon-Knife 存储库的副本（您的复刻）。
|
||||
3. Select an owner for the forked repository. 
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
|
||||
5. Optionally, add a description of your fork. 
|
||||
6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. 
|
||||
7. Click **Create fork**. 
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. 更多信息请参阅“[创建和删除仓库中的分支](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 克隆复刻
|
||||
|
||||
|
||||
@@ -57,7 +57,17 @@ topics:
|
||||
您可能为了对上游或原始仓库提议更改而复刻项目。 在这种情况下，最好定期将您的复刻与上游仓库同步。 为此，您需要在命令行上使用 Git。 您可以使用刚才复刻的 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 仓库练习设置上游仓库。
|
||||
|
||||
1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %} 上，导航到 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 存储库。
|
||||
2. 在页面的右上角，单击 **Fork（复刻）**。 
|
||||
2. In the top-right corner of the page, click **Fork**. 
|
||||
3. Select an owner for the forked repository. 
|
||||
4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. 
|
||||
5. Optionally, add a description of your fork. 
|
||||
6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied. 
|
||||
7. Click **Create fork**. 
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you want to copy additional branches from the parent repository, you can do so from the **Branches** page. For more information, see "[Creating and deleting branches within your repository](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository)."{% endnote %}
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
|
||||
@@ -39,8 +39,8 @@ When you open the command palette, it shows your location at the top left and us
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).
|
||||
- If you are working on a project (beta), a project-specific command palette is displayed instead. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)."
|
||||
- If you are editing Markdown text, open the command palette with <kbd>Ctrl</kbd>+<kbd>Alt</kbd>+<kbd>K</kbd> (Windows and Linux) or <kbd>Command</kbd>+<kbd>Option</kbd>+<kbd>K</kbd> (Mac).{% ifversion projects-v2 %}
|
||||
- If you are working on a {% data variables.projects.project_v2 %}, a project-specific command palette is displayed instead. For more information, see "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)."{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -151,7 +151,7 @@ These commands are available from all scopes.
|
||||
|`Import repository`|Create a new repository by importing a project from another version control system. For more information, see "[Importing a repository with GitHub importer](/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer)." |
|
||||
|`New gist`|Open a new gist. For more information, see "[Creating a gist](/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists)." |
|
||||
|`New organization`|Create a new organization. For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)." |
|
||||
|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/trying-out-the-new-projects-experience/creating-a-project)." |
|
||||
|`New project`|Create a new project board. For more information, see "[Creating a project](/issues/planning-and-tracking-with-projects/creating-projects/creating-a-project)." |
|
||||
|`New repository`|Create a new repository from scratch. For more information, see "[Creating a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository)." |
|
||||
|`Switch theme to <theme name>`|Change directly to a different theme for the UI. For more information, see "[Managing your theme settings](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-your-theme-settings)." |
|
||||
|
||||
|
||||
@@ -146,7 +146,34 @@ versions:
|
||||
| <kbd>Alt</kbd> 并单击 | 通过按下 <kbd>Alt</kbd> 并单击 **Show outdated（显示已过期）**或 **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)”。 |
|
||||
|
||||
## 项目板
|
||||
{% ifversion projects-v2 %}
|
||||
|
||||
## {% data variables.projects.projects_v2_caps %}
|
||||
|
||||
### Navigating a project
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ------------------------------------------------------------------------------- | ---------------------------- |
|
||||
| <kbd>⌘</kbd>+<kbd>f</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>f</kbd> (Windows/Linux) | Focus filter field |
|
||||
| <kbd>←</kbd> | Move cell focus to the left |
|
||||
| <kbd>→</kbd> | Move cell focus to the right |
|
||||
| <kbd>↑</kbd> | Move cell focus up |
|
||||
| <kbd>↓</kbd> | Move cell focus down |
|
||||
|
||||
### Manipulating a project
|
||||
|
||||
| 键盘快捷键 | 描述 |
|
||||
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------- |
|
||||
| <kbd>Enter</kbd> | Toggle edit mode for the focused cell |
|
||||
| <kbd>Escape</kbd> | Cancel editing for the focused cell |
|
||||
| <kbd>⌘</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Mac) or <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>\</kbd> (Windows/Linux) | Open row actions menu |
|
||||
| <kbd>Shift</kbd>+<kbd>Space</kbd> | 选择项目 |
|
||||
| <kbd>Space</kbd> | Open selected item |
|
||||
| <kbd>e</kbd> | Archive selected items |
|
||||
|
||||
{% endif %}
|
||||
|
||||
## {% data variables.product.prodname_projects_v1_caps %}
|
||||
|
||||
### 移动列
|
||||
|
||||
|
||||
@@ -16,11 +16,7 @@ topics:
|
||||
- Pull requests
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：** 如果将文件附加到拉取请求或发出注释，则任何人都可以在不进行身份验证的情况下查看匿名 URL，即使拉取请求位于私有存储库中{% ifversion ghes %}，或者启用了私有模式{% endif %}。 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt or ghec %}有关匿名 URL 的更多信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %}
|
||||
|
||||
{% endwarning %}
|
||||
{% data reusables.repositories.anyone-can-view-anonymized-url %}
|
||||
|
||||
要将文件附加到议题或拉取请求对话，请将它拖放到评论框中。 或者，您也可以单击评论框底部的栏来浏览、选择和添加计算机中的文件。
|
||||
|
||||
|
||||
@@ -45,6 +45,15 @@ shortTitle: 自动链接的引用
|
||||
如果您在列表中引用议题、拉取请求或讨论，则引用将展开以显示标题和状态。 有关任务列表的更多信息，请参阅“[关于任务列表](/issues/tracking-your-work-with-issues/creating-issues/about-task-lists)”。
|
||||
{% endif %}
|
||||
|
||||
## 标签
|
||||
When referencing the URL of a label in Markdown, the label is automatically rendered. Only labels of the same repository are rendered, URLs pointing to a label from a different repository are rendered as any [URL](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls#urls).
|
||||
|
||||
The URL of a label can be found by navigating to the labels page and clicking on a label. For example, the URL of the label "enhancement" in our public [docs repository](https://github.com/github/docs/) is
|
||||
|
||||
```md
|
||||
https://github.com/github/docs/labels/enhancement
|
||||
```
|
||||
|
||||
## 提交 SHA
|
||||
|
||||
对提交 SHA 哈希的引用会自动转换为指向 {% data variables.product.product_name %} 上提交的短链接。
|
||||
|
||||
@@ -40,9 +40,9 @@ graph TD;
|
||||
|
||||
## 创建 GeoJSON 和 TopoJSON 地图
|
||||
|
||||
You can use GeoJSON/TopoJSON syntax to create interactive maps. To create a map, add GeoJSON or TopoJSON inside a fenced code block with the `geojson` or `topojson` syntax identifier. 更多信息请参阅“[创建和突出显示代码块](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)”。
|
||||
您可以使用 GeoJSON/TopoJSON 语法来创建交互式映射。 要创建映射，请在具有 `geojson` 或 `topojson` 语法标识符的受防护代码块中添加 GeoJSON 或 TopoJSON。 更多信息请参阅“[创建和突出显示代码块](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)”。
|
||||
|
||||
### Using GeoJSON
|
||||
### 使用 GeoJSON
|
||||
|
||||
例如，您可以创建一个简单的地图：
|
||||
|
||||
@@ -77,9 +77,9 @@ You can use GeoJSON/TopoJSON syntax to create interactive maps. To create a map,
|
||||
|
||||
|
||||
|
||||
### Using TopoJSON
|
||||
### 使用 TopoJSON
|
||||
|
||||
For example, you can create a simple TopoJSON map:
|
||||
例如，您可以创建一个简单的 TopoJSON 映射：
|
||||
|
||||
<pre>
|
||||
```topojson
|
||||
|
||||
@@ -10,11 +10,11 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
includeGuides:
|
||||
- /issues/trying-out-the-new-projects-experience/automating-projects
|
||||
- /issues/trying-out-the-new-projects-experience/creating-a-project
|
||||
- /issues/trying-out-the-new-projects-experience/customizing-your-project-views
|
||||
- /issues/trying-out-the-new-projects-experience/quickstart
|
||||
- /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
|
||||
- /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
|
||||
- /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects
|
||||
- /issues/tracking-your-work-with-issues/quickstart
|
||||
- /issues/tracking-your-work-with-issues/creating-an-issue
|
||||
- /issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests
|
||||
|
||||
@@ -8,18 +8,19 @@ introLinks:
|
||||
featuredLinks:
|
||||
guides:
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/creating-an-issue
|
||||
- /issues/trying-out-the-new-projects-experience/quickstart
|
||||
- /issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/quickstart-for-projects
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects
|
||||
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
|
||||
- /issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project
|
||||
guideCards:
|
||||
- /issues/trying-out-the-new-projects-experience/automating-projects
|
||||
- /issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/linking-a-pull-request-to-an-issue
|
||||
- '{% ifversion ghes or ghae %}/issues/organizing-your-work-with-project-boards/managing-project-boards/configuring-automation-for-project-boards{% endif %}'
|
||||
- /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
|
||||
- /issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions
|
||||
popular:
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/about-issues
|
||||
- /issues/trying-out-the-new-projects-experience/about-projects
|
||||
- /issues/planning-and-tracking-with-projects/learning-about-projects/about-projects
|
||||
- /issues/planning-and-tracking-with-projects/creating-projects/creating-a-project
|
||||
- /issues/tracking-your-work-with-issues/creating-issues/about-task-lists
|
||||
- /communities/using-templates-to-encourage-useful-issues-and-pull-requests/about-issue-and-pull-request-templates
|
||||
- /issues/using-labels-and-milestones-to-track-work/managing-labels
|
||||
@@ -32,8 +33,8 @@ featuredLinks:
|
||||
href: 'https://www.youtube-nocookie.com/embed/HwpVvDURHKw'
|
||||
- title: Issue Forms for open source – Luke Hefson
|
||||
href: 'https://www.youtube-nocookie.com/embed/2Yh8ueUE0oY'
|
||||
videosHeading: GitHub Universe 2021 videos
|
||||
product_video: 'https://www.youtube-nocookie.com/embed/uiaLWluYJsA'
|
||||
videosHeading: Videos
|
||||
product_video: '{% ifversion projects-v2 %}https://www.youtube-nocookie.com/embed/yFQ-p6wMS_Y{% else %}https://www.youtube-nocookie.com/embed/uiaLWluYJsA{% endif %}'
|
||||
layout: product-landing
|
||||
beta_product: false
|
||||
versions:
|
||||
@@ -43,7 +44,7 @@ versions:
|
||||
ghec: '*'
|
||||
children:
|
||||
- /tracking-your-work-with-issues
|
||||
- /trying-out-the-new-projects-experience
|
||||
- /planning-and-tracking-with-projects
|
||||
- /organizing-your-work-with-project-boards
|
||||
- /using-labels-and-milestones-to-track-work
|
||||
- /guides
|
||||
|
||||
@@ -1,12 +1,10 @@
|
||||
---
|
||||
title: 使用项目板组织工作
|
||||
shortTitle: 项目板
|
||||
intro: '在 {% data variables.product.prodname_dotcom %} 上使用项目板管理工作'
|
||||
title: 'Organizing your work with {% data variables.product.prodname_projects_v1 %}'
|
||||
shortTitle: '{% data variables.product.prodname_projects_v1_caps %}'
|
||||
intro: 'Use {% data variables.product.prodname_projects_v1 %} to manage your work on {% data variables.product.prodname_dotcom %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Issues
|
||||
- Projects
|
||||
|
||||
@@ -1,31 +1,29 @@
|
||||
---
|
||||
title: 关于项目板的自动化
|
||||
intro: 您可以配置自动工作流程来保持项目板卡状态与相关的议题及拉取请求同步。
|
||||
title: 'About automation for {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can configure automatic workflows to keep the status of {% data variables.projects.projects_v1_board %} cards in sync with the associated issues and pull requests.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/about-automation-for-project-boards
|
||||
- /articles/about-automation-for-project-boards
|
||||
- /github/managing-your-work-on-github/about-automation-for-project-boards
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 项目板的自动化
|
||||
shortTitle: 'Automation for {% data variables.product.prodname_projects_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% data reusables.project-management.automate-project-board-permissions %} 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。
|
||||
{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[{% data variables.product.prodname_projects_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
您可以根据项目板列的触发事件自动执行操作。 这可以节省项目板管理过程中的一些手动任务。 例如，您可以配置 "To do"（待处理）列，其中您添加到项目板的任何新议题或拉取请求都会自动移至配置的列。 更多信息请参阅“[配置项目板的自动化](/articles/configuring-automation-for-project-boards)”。
|
||||
You can automate actions based on triggering events for {% data variables.projects.projects_v1_board %} columns. This eliminates some of the manual tasks in managing a {% data variables.projects.projects_v1_board %}. For example, you can configure a "To do" column, where any new issues or pull requests you add to a {% data variables.projects.projects_v1_board %} are automatically moved to the configured column. For more information, see "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)."
|
||||
|
||||
{% data reusables.project-management.use-automated-template %}
|
||||
|
||||
{% data reusables.project-management.copy-project-boards %}
|
||||
|
||||
项目板自动化通过为某些操作创建标准工作流程，也可帮助团队对项目板的目的和团队开发流程达成一致的理解。
|
||||
{% data variables.projects.projects_v1_board_caps %} automation can also help teams develop a shared understanding of a {% data variables.projects.projects_v1_board %}'s purpose and the team's development process by creating a standard workflow for certain actions.
|
||||
|
||||
{% data reusables.project-management.resync-automation %}
|
||||
|
||||
@@ -39,10 +37,10 @@ shortTitle: 项目板的自动化
|
||||
|
||||
## 项目进度跟踪
|
||||
|
||||
您可以跟踪项目板上的进度。 "To do"（待处理）、"In progress"（进行中）或 "Done"（完成）列中的卡计入总体项目进度。 {% data reusables.project-management.project-progress-locations %}
|
||||
You can track the progress on your {% data variables.projects.projects_v1_board %}. "To do"（待处理）、"In progress"（进行中）或 "Done"（完成）列中的卡计入总体项目进度。 {% data reusables.project-management.project-progress-locations %}
|
||||
|
||||
更多信息请参阅“[跟踪项目板上的进度](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)”。
|
||||
For more information, see "[Tracking progress on your {% data variables.product.prodname_project_v1 %}](/github/managing-your-work-on-github/tracking-progress-on-your-project-board)."
|
||||
|
||||
## 延伸阅读
|
||||
- "[配置项目板的自动化](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
|
||||
- "[复制项目板](/articles/copying-a-project-board)"{% endif %}
|
||||
- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"{% ifversion fpt or ghec %}
|
||||
- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
|
||||
|
||||
@@ -1,55 +1,53 @@
|
||||
---
|
||||
title: 关于项目板
|
||||
intro: '{% data variables.product.product_name %} 上的项目板帮助您组织工作和排列工作的优先级。 您可以为特定功能工作、全面的路线图甚至发布检查列表创建项目板。 通过项目板可以灵活地创建适合需求的自定义工作流程。'
|
||||
title: '关于 {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: '{% data variables.product.prodname_projects_v1_caps %} on {% data variables.product.product_name %} help you organize and prioritize your work. You can create {% data variables.projects.projects_v1_boards %} for specific feature work, comprehensive roadmaps, or even release checklists. With {% data variables.product.prodname_projects_v1 %}, you have the flexibility to create customized workflows that suit your needs.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/about-project-boards
|
||||
- /articles/about-projects
|
||||
- /articles/about-project-boards
|
||||
- /github/managing-your-work-on-github/about-project-boards
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
项目板包括议题、拉取请求和注释，在选择的列中分类为卡片。 您可以拖放或使用键盘快捷键对列中的卡片重新排序，在不同列之间移动卡片，以及更改列的顺序。
|
||||
{% data variables.projects.projects_v1_boards_caps %} are made up of issues, pull requests, and notes that are categorized as cards in columns of your choosing. 您可以拖放或使用键盘快捷键对列中的卡片重新排序，在不同列之间移动卡片，以及更改列的顺序。
|
||||
|
||||
项目板卡片包含议题和拉取请求的相关数据，如标签、受理人、状态和打开者。 {% data reusables.project-management.edit-in-project %}
|
||||
{% data variables.projects.projects_v1_board_caps %} cards contain relevant metadata for issues and pull requests, like labels, assignees, the status, and who opened it. {% data reusables.project-management.edit-in-project %}
|
||||
|
||||
您可以在列中创建注释以用作任务提醒，引用 {% data variables.product.product_location %} 上任何仓库中的议题和拉取请求，或者添加与项目板相关的信息。 您可以在注释中添加链接，创建另一个项目的参考卡。 如果注释不足以满足您的需求，您可以将其转换为议题。 有关将项目板注释转换为议题的更多信息，请参阅“[添加注释到项目板](/articles/adding-notes-to-a-project-board)”。
|
||||
You can create notes within columns to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_location %}, or to add information related to the {% data variables.projects.projects_v1_board %}. You can create a reference card for another {% data variables.projects.projects_v1_board %} by adding a link to a note. 如果注释不足以满足您的需求，您可以将其转换为议题。 For more information on converting notes to issues, see "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
|
||||
|
||||
项目板的类型：
|
||||
|
||||
- **用户拥有的项目板**可以包含任何个人仓库中的议题和拉取请求。
|
||||
- **组织范围的项目板**可以包含属于组织的任何仓库中的议题和拉取请求。 {% data reusables.project-management.link-repos-to-project-board %}更多信息请参阅“[将仓库链接到项目板](/articles/linking-a-repository-to-a-project-board)”。
|
||||
- **仓库项目板**范围是单一仓库中的议题和拉取请求。 它们也可包含引用其他仓库中议题和拉取请求的注释。
|
||||
- **User-owned {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any personal repository.
|
||||
- **Organization-wide {% data variables.projects.projects_v1_board %}** can contain issues and pull requests from any repository that belongs to an organization. {% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %}](/articles/linking-a-repository-to-a-project-board)."
|
||||
- **Repository {% data variables.projects.projects_v1_board %}** are scoped to issues and pull requests within a single repository. 它们也可包含引用其他仓库中议题和拉取请求的注释。
|
||||
|
||||
## 创建和查看项目板
|
||||
## Creating and viewing {% data variables.projects.projects_v1_boards %}
|
||||
|
||||
要为组织创建项目板，您必须是组织成员。 组织所有者以及具有项目板管理员权限的人员可以自定义对项目板的访问权限。
|
||||
To create a {% data variables.projects.projects_v1_board %} for your organization, you must be an organization member. Organization owners and people with {% data variables.projects.projects_v1_board %} admin permissions can customize access to the {% data variables.projects.projects_v1_board %}.
|
||||
|
||||
如果组织拥有的项目板包含您没有查看权限的仓库中的议题和拉取请求，该卡片将被重新指定。 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。
|
||||
If an organization-owned {% data variables.projects.projects_v1_board %} includes issues or pull requests from a repository that you don't have permission to view, the card will be redacted. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
活动视图显示项目板的最近历史记录，例如某人创建的卡或在列之间移动的卡。 要访问活动视图，请单击 **Menu（菜单）**并向下滚动。
|
||||
The activity view shows the {% data variables.projects.projects_v1_board %}'s recent history, such as cards someone created or moved between columns. 要访问活动视图，请单击 **Menu（菜单）**并向下滚动。
|
||||
|
||||
要查找项目板上的特定卡或查看卡的子集，可以过滤项目板卡。 更多信息请参阅“[过滤项目板卡](/articles/filtering-cards-on-a-project-board)”。
|
||||
To find specific cards on a {% data variables.projects.projects_v1_board %} or view a subset of the cards, you can filter {% data variables.projects.projects_v1_board %} cards. For more information, see "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)."
|
||||
|
||||
为简化工作流程并从项目板移除已完成的任务，您可以对板卡存档。 更多信息请参阅“[对项目板卡存档](/articles/archiving-cards-on-a-project-board)”。
|
||||
To simplify your workflow and keep completed tasks off your {% data variables.projects.projects_v1_board %}, you can archive cards. For more information, see "[Archiving cards on a {% data variables.product.prodname_project_v1 %}](/articles/archiving-cards-on-a-project-board)."
|
||||
|
||||
如果您已完成所有项目板任务或不再需要使用项目板，可以关闭项目板。 更多信息请参阅“[关闭项目板](/articles/closing-a-project-board)”。
|
||||
If you've completed all of your {% data variables.projects.projects_v1_board %} tasks or no longer need to use your {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
|
||||
|
||||
如果要以不同的方式跟踪您的工作，您也可以[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)或[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)。
|
||||
You can also [disable {% data variables.projects.projects_v1_boards %} in a repository](/articles/disabling-project-boards-in-a-repository) or [disable {% data variables.projects.projects_v1_boards %} in your organization](/articles/disabling-project-boards-in-your-organization), if you prefer to track your work in a different way.
|
||||
|
||||
{% data reusables.project-management.project-board-import-with-api %}
|
||||
|
||||
## 项目板模板
|
||||
## Templates for {% data variables.projects.projects_v1_boards %}
|
||||
|
||||
您可以使用模板快速设置新的项目板。 在使用模板创建项目板时，新板将包含列以及具有项目板使用提示的卡。 您也可以选择已配置自动化的模板。
|
||||
You can use templates to quickly set up a new {% data variables.projects.projects_v1_board %}. When you use a template to create a {% data variables.projects.projects_v1_board %}, your new board will include columns as well as cards with tips for using {% data variables.product.prodname_projects_v1 %}. 您也可以选择已配置自动化的模板。
|
||||
|
||||
| 模板 | 描述 |
|
||||
| --------- | --------------------------------------------------------------------- |
|
||||
@@ -58,17 +56,17 @@ topics:
|
||||
| 带审查的自动化看板 | 板卡自动在 To do（待处理）、In progress（进行中）和 Done（已完成）列之间移动，并且包含拉取请求审查状态的附加触发条件 |
|
||||
| 漏洞查验 | 通过 To do（待处理）、In progress（进行中）和 Done（已完成）列查验漏洞并排列优先级 |
|
||||
|
||||
有关项目板自动化的更多信息，请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards)”。
|
||||
For more information on automation for {% data variables.product.prodname_projects_v1 %}, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.project-management.copy-project-boards %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[创建项目板](/articles/creating-a-project-board)"
|
||||
- "[编辑项目板](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
|
||||
- "[复制项目板](/articles/copying-a-project-board)"{% endif %}
|
||||
- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[创建 {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
|
||||
- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"{% ifversion fpt or ghec %}
|
||||
- "[Copying a {% data variables.product.prodname_project_v1 %}](/articles/copying-a-project-board)"{% endif %}
|
||||
- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[键盘快捷键](/articles/keyboard-shortcuts/#project-boards)"
|
||||
|
||||
@@ -1,18 +1,16 @@
|
||||
---
|
||||
title: 更改项目板可见性
|
||||
intro: '作为组织所有者或项目板管理员，您可以将项目板设为{% ifversion ghae %}内部{% else %}公共{% endif %}或私有。'
|
||||
title: 'Changing {% data variables.product.prodname_project_v1 %} visibility'
|
||||
intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can make a {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %} or private.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/changing-project-board-visibility
|
||||
- /articles/changing-project-board-visibility
|
||||
- /github/managing-your-work-on-github/changing-project-board-visibility
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 更改可见性
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
@@ -21,7 +19,7 @@ shortTitle: 更改可见性
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**将项目板设为{% ifversion ghae %}内部{% else %}公共{% endif %}时，组织成员默认获得读取权限。 您可以为特定组织成员提供写入或管理权限，方法是为他们所在的团队提供项目板访问权限或将他们作为协作者添加到项目板。 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”。
|
||||
**Tip:** When you make your {% data variables.projects.projects_v1_board %} {% ifversion ghae %}internal{% else %}public{% endif %}, organization members are given read access by default. You can give specific organization members write or admin permissions by giving access to teams they're on or by adding them to the {% data variables.projects.projects_v1_board %} as a collaborator. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
@@ -1,34 +1,32 @@
|
||||
---
|
||||
title: 关闭项目板
|
||||
intro: 如果您已完成项目板中所有任务或不再需要使用项目板，可以关闭项目板。
|
||||
title: 'Closing a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'If you''ve completed all the tasks in a {% data variables.projects.projects_v1_board %} or no longer need to use a {% data variables.projects.projects_v1_board %}, you can close the {% data variables.projects.projects_v1_board %}.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/closing-a-project-board
|
||||
- /articles/closing-a-project
|
||||
- /articles/closing-a-project-board
|
||||
- /github/managing-your-work-on-github/closing-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
关闭项目板时，默认情况下任何已配置的工作流程自动化都会暂停。
|
||||
When you close a {% data variables.projects.projects_v1_board %}, any configured workflow automation will pause by default.
|
||||
|
||||
如果重新打开项目板，您可以选择*同步*自动化，以便根据为项目板配置的自动化设置来更新板上卡的位置。 更多信息请参阅“[重新打开已关闭的项目板](/articles/reopening-a-closed-project-board)”或“[关于项目板自动化](/articles/about-automation-for-project-boards)”。
|
||||
If you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board. For more information, see "[Reopening a closed {% data variables.product.prodname_project_v1 %}](/articles/reopening-a-closed-project-board)" or "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
|
||||
|
||||
1. 导航到仓库或组织中或由个人帐户拥有的项目板列表。
|
||||
2. 在项目列表中，在要关闭的项目板旁边单击 {% octicon "chevron-down" aria-label="The chevron icon" %}。 
|
||||
1. Navigate to the list of {% data variables.projects.projects_v1_boards %} in your repository or organization, or owned by your personal account.
|
||||
2. In the projects list, next to the {% data variables.projects.projects_v1_board %} you want to close, click {% octicon "chevron-down" aria-label="The chevron icon" %}. 
|
||||
3. 单击 **Close（关闭）**。 
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- “[删除项目板](/articles/deleting-a-project-board)”
|
||||
- “[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)”
|
||||
- “[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)”
|
||||
- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
|
||||
- "[Disabling {% data variables.product.prodname_projects_v1 %} in a repository](/articles/disabling-project-boards-in-a-repository)"
|
||||
- "[Disabling {% data variables.product.prodname_projects_v1 %} in your organization](/articles/disabling-project-boards-in-your-organization)"
|
||||
- "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
|
||||
@@ -1,15 +1,12 @@
|
||||
---
|
||||
title: 配置项目板的自动化
|
||||
intro: 您可以设置自动工作流程 - 在发生指定事件时将议题和拉取请求移动到项目板的列中。
|
||||
title: 'Configuring automation for {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can set up automatic workflows to move issues and pull requests to a {% data variables.projects.projects_v1_board %} column when a specified event occurs.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/configuring-automation-for-project-boards
|
||||
- /articles/configuring-automation-for-project-boards
|
||||
- /github/managing-your-work-on-github/configuring-automation-for-project-boards
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
- Projects
|
||||
@@ -17,11 +14,12 @@ topics:
|
||||
- Project management
|
||||
shortTitle: 配置自动化
|
||||
type: how_to
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% data reusables.project-management.automate-project-board-permissions %} 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards)”。
|
||||
{% data reusables.project-management.automate-project-board-permissions %} For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
|
||||
|
||||
{% data reusables.project-management.use-automated-template %}
|
||||
|
||||
@@ -33,7 +31,7 @@ type: how_to
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 导航到要自动化的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to automate.
|
||||
2. 在要自动化的列中，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 
|
||||
3. 单击 **Manage automation（管理自动化）**。 
|
||||
4. 使用 Preset（预设）下拉菜单，选择一个自动化预设。 
|
||||
@@ -41,4 +39,4 @@ type: how_to
|
||||
6. 单击 **Update automation（更新自动化）**。
|
||||
|
||||
## 延伸阅读
|
||||
- “[关于项目板的自动化](/articles/about-automation-for-project-boards)”
|
||||
- "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 复制项目板
|
||||
intro: 您可以复制项目板以快速创建新项目。 复制常用或高度定制的项目板有助于标准化您的工作流程。
|
||||
title: 'Copying a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can copy a {% data variables.projects.projects_v1_board %} to quickly create a new project. Copying frequently used or highly customized {% data variables.projects.projects_v1_boards %} helps standardize your workflow.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/copying-a-project-board
|
||||
- /articles/copying-a-project-board
|
||||
@@ -10,23 +10,24 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Pull requests
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
复制项目板可以重用项目板的标题、说明和自动化配置。 您可以复制项目板以消除为类似工作流程创建新项目板的手动过程。
|
||||
Copying a {% data variables.projects.projects_v1_board %} allows you to reuse a {% data variables.projects.projects_v1_board %}'s title, description, and automation configuration. You can copy {% data variables.projects.projects_v1_boards %} to eliminate the manual process of creating new {% data variables.projects.projects_v1_boards %} for similar workflows.
|
||||
|
||||
必须对项目板具有读取权限才能将其复制到您具有写入权限的仓库或组织。
|
||||
You must have read access to a {% data variables.projects.projects_v1_board %} to copy it to a repository or organization where you have write access.
|
||||
|
||||
将项目板复制到组织时，项目板的可见性将默认为私密，您可以选择更改可见性。 更多信息请参阅“[更改项目板可见性](/articles/changing-project-board-visibility/)”。
|
||||
When you copy a {% data variables.projects.projects_v1_board %} to an organization, the {% data variables.projects.projects_v1_board %}'s visibility will default to private, with an option to change the visibility. For more information, see "[Changing {% data variables.product.prodname_project_v1 %} visibility](/articles/changing-project-board-visibility/)."
|
||||
|
||||
默认情况下也会启用项目板的自动化。 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards/)”。
|
||||
A {% data variables.projects.projects_v1_board %}'s automation is also enabled by default. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards/)."
|
||||
|
||||
1. 导航到要复制的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to copy.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
3. 单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Copy（复制）**。 
|
||||
4. 在“Owner（所有者）”下，使用下拉菜单并单击要复制项目板的仓库或组织。 
|
||||
5. （可选）在“Project board name（项目板名称）”下，键入所复制项目板的名称。 
|
||||
5. Optionally, under "Project board name", type the name of the copied {% data variables.projects.projects_v1_board %}. 
|
||||
6. （可选）在“Description（说明）”下，键入其他人将看到的有关所复制项目板的说明。 
|
||||
7. （可选）在“Automation settings（自动化设置）”下，选择是否要复制已配置的自动工作流程。 默认情况下会启用此选项。 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards/)”。 
|
||||
{% data reusables.project-management.choose-visibility %}
|
||||
|
||||
@@ -1,22 +1,20 @@
|
||||
---
|
||||
title: 创建项目板
|
||||
intro: 项目板可用于创建满足您需求的自定义工作流程，例如对特定功能工作、全面路线图甚至发布检查清单进行跟踪和排列优先级。
|
||||
title: '创建 {% data variables.product.prodname_project_v1 %}'
|
||||
intro: '{% data variables.projects.projects_v1_boards_caps %} can be used to create customized workflows to suit your needs, like tracking and prioritizing specific feature work, comprehensive roadmaps, or even release checklists.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/creating-a-project-board
|
||||
- /articles/creating-a-project
|
||||
- /articles/creating-a-project-board
|
||||
- /github/managing-your-work-on-github/creating-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
- Issues
|
||||
- Projects
|
||||
- Project management
|
||||
type: how_to
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
@@ -25,20 +23,21 @@ type: how_to
|
||||
|
||||
{% data reusables.project-management.copy-project-boards %}
|
||||
|
||||
{% data reusables.project-management.link-repos-to-project-board %}更多信息请参阅“[将仓库链接到项目板](/articles/linking-a-repository-to-a-project-board)”。
|
||||
{% data reusables.project-management.link-repos-to-project-board %} For more information, see "[Linking a repository to a {% data variables.product.prodname_project_v1 %} ](/articles/linking-a-repository-to-a-project-board)."
|
||||
|
||||
创建项目板后，您可以向其添加议题、拉取请求和备注。 更多信息请参阅“[向项目板添加议题和拉取请求](/articles/adding-issues-and-pull-requests-to-a-project-board)”和“[向项目板添加备注](/articles/adding-notes-to-a-project-board)”。
|
||||
Once you've created your {% data variables.projects.projects_v1_board %}, you can add issues, pull requests, and notes to it. For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)" and "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)."
|
||||
|
||||
还可以配置工作流程自动化，使项目板与议题和拉取请求的状态保持同步。 更多信息请参阅“[关于项目板的自动化](/articles/about-automation-for-project-boards)”。
|
||||
You can also configure workflow automations to keep your {% data variables.projects.projects_v1_board %} in sync with the status of issues and pull requests. For more information, see "[About automation for {% data variables.product.prodname_projects_v1 %}](/articles/about-automation-for-project-boards)."
|
||||
|
||||
{% data reusables.project-management.project-board-import-with-api %}
|
||||
|
||||
## 创建用户拥有的项目板
|
||||
## Creating a user-owned {% data variables.projects.projects_v1_board %}
|
||||
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 
|
||||
2. 在个人资料页面顶部的主导航栏中，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 {% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
{% data reusables.project-management.choose-template %}
|
||||
@@ -54,13 +53,14 @@ type: how_to
|
||||
|
||||
{% data reusables.project-management.edit-project-columns %}
|
||||
|
||||
## 创建组织范围的项目板
|
||||
## Creating an organization-wide {% data variables.projects.projects_v1_board %}
|
||||
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
{% data reusables.project-management.choose-template %}
|
||||
@@ -76,12 +76,13 @@ type: how_to
|
||||
|
||||
{% data reusables.project-management.edit-project-columns %}
|
||||
|
||||
## 创建仓库项目板
|
||||
## Creating a repository {% data variables.projects.projects_v1_board %}
|
||||
|
||||
{% data reusables.projects.classic-project-creation %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. 在仓库名称下，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 
|
||||
2. 在仓库名称下，单击 {% octicon "project" aria-label="The project board icon" %} **Projects（项目）**。 {% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.click-new-project %}
|
||||
{% data reusables.project-management.create-project-name-description %}
|
||||
{% data reusables.project-management.choose-template %}
|
||||
|
||||
@@ -1,29 +1,27 @@
|
||||
---
|
||||
title: 删除项目板
|
||||
intro: 如果您不再需要访问现有项目板的内容，可将其删除。
|
||||
title: 'Deleting a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can delete an existing {% data variables.projects.projects_v1_board %} if you no longer need access to its contents.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/deleting-a-project-board
|
||||
- /articles/deleting-a-project
|
||||
- /articles/deleting-a-project-board
|
||||
- /github/managing-your-work-on-github/deleting-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：如果您希望保留对已完成或不需要项目板的访问权限，而不是去对其内容的访问权限，可以[关闭项目板](/articles/closing-a-project-board)而非将其删除。
|
||||
**Tip**: If you'd like to retain access to a completed or unneeded {% data variables.projects.projects_v1_board %} without losing access to its contents, you can [close the {% data variables.projects.projects_v1_board %}](/articles/closing-a-project-board) instead of deleting it.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 导航到要删除的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to delete.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
|
||||
4. 单击 **Delete project（删除项目）**。 
|
||||
@@ -31,6 +29,6 @@ topics:
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关闭项目板](/articles/closing-a-project-board)"
|
||||
- “[在仓库中禁用项目板](/articles/disabling-project-boards-in-a-repository)”
|
||||
- “[在组织中禁用项目板](/articles/disabling-project-boards-in-your-organization)”
|
||||
- "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)"
|
||||
- "[Disabling {% data variables.product.prodname_project_v1_caps %} in a repository](/articles/disabling-project-boards-in-a-repository)"
|
||||
- "[Disabling {% data variables.product.prodname_project_v1_caps %} in your organization](/articles/disabling-project-boards-in-your-organization)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 编辑项目板
|
||||
intro: 您可以编辑现有项目板的标题和说明。
|
||||
title: 'Editing a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can edit the title and description of an existing {% data variables.projects.projects_v1_board %}.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/editing-a-project-board
|
||||
- /articles/editing-a-project
|
||||
@@ -8,29 +8,27 @@ redirect_from:
|
||||
- /articles/editing-a-project-board
|
||||
- /github/managing-your-work-on-github/editing-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**有关添加、删除或编辑项目板中列的详细信息，请参阅 “[创建项目板](/articles/creating-a-project-board)”。
|
||||
**Tip:** For details on adding, removing, or editing columns in your {% data variables.projects.projects_v1_board %}, see "[Creating a {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 导航到要编辑的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to edit.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
|
||||
4. 根据需要修改项目板名称和说明，然后单击 **Save project（保存项目）**。 
|
||||
4. Modify the {% data variables.projects.projects_v1_board %} name and description as needed, then click **Save project**. 
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- “[删除项目板](/articles/deleting-a-project-board)”
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- "[Deleting a {% data variables.product.prodname_project_v1 %}](/articles/deleting-a-project-board)"
|
||||
|
||||
@@ -1,12 +1,9 @@
|
||||
---
|
||||
title: 管理项目板
|
||||
shortTitle: 管理项目板
|
||||
intro: 了解如何创建和管理项目板
|
||||
title: '管理 {% data variables.product.prodname_projects_v1 %}'
|
||||
shortTitle: '管理 {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'Learn how to create and manage {% data variables.projects.projects_v1_boards %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Issues
|
||||
- Projects
|
||||
@@ -24,6 +21,7 @@ children:
|
||||
- /deleting-a-project-board
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
@@ -1,27 +1,25 @@
|
||||
---
|
||||
title: 将仓库链接到项目板
|
||||
intro: 您可以将仓库链接到组织或个人帐户的项目板。
|
||||
title: 'Linking a repository to a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can link a repository to your organization''s or personal account''s {% data variables.projects.projects_v1_board %}.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/linking-a-repository-to-a-project-board
|
||||
- /articles/linking-a-repository-to-a-project-board
|
||||
- /github/managing-your-work-on-github/linking-a-repository-to-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 将仓库链接到板
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
对项目板具有写入权限的任何人都可以将该组织或个人帐户拥有的仓库链接到项目板。 更多信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization/)”或“[用户拥有的项目板的权限级别](/articles/permission-levels-for-user-owned-project-boards/)”。
|
||||
Anyone with write permissions to a {% data variables.projects.projects_v1_board %} can link repositories owned by that organization or personal account to the {% data variables.projects.projects_v1_board %}. For more information, see "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization/)" or "[Permission levels for user-owned {% data variables.product.prodname_projects_v1 %}](/articles/permission-levels-for-user-owned-project-boards/)."
|
||||
|
||||
{% data reusables.project-management.link-repos-to-project-board %} 您可以在卡中输入议题或拉取请求 URL，从任何未链接的仓库添加议题和拉取请求。 更多信息请参阅“[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)”。
|
||||
{% data reusables.project-management.link-repos-to-project-board %} 您可以在卡中输入议题或拉取请求 URL，从任何未链接的仓库添加议题和拉取请求。 For more information, see "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)."
|
||||
|
||||
1. 导航到您要在其中链接仓库的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to link a repository.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
4. 在左侧边栏中，单击 **Linked repositories（链接的仓库）**。 
|
||||
@@ -31,10 +29,10 @@ shortTitle: 将仓库链接到板
|
||||
|
||||
{% note %}
|
||||
|
||||
**注：**要将仓库链接到组织或用户拥有的项目板，仓库需要启用议题。 也就是说，仓库有一个“议题”选项卡（在复刻的仓库中默认禁用议题）。 有关如何对仓库启用或禁用议题的信息，请参阅“[对仓库禁用议题](/github/managing-your-work-on-github/disabling-issues)”。
|
||||
**Note:** In order to link a repository to your organization or user owned {% data variables.projects.projects_v1_board %} the repository needs to have issues enabled. 也就是说，仓库有一个“议题”选项卡（在复刻的仓库中默认禁用议题）。 有关如何对仓库启用或禁用议题的信息，请参阅“[对仓库禁用议题](/github/managing-your-work-on-github/disabling-issues)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
|
||||
@@ -1,32 +1,30 @@
|
||||
---
|
||||
title: 重新打开关闭的项目板
|
||||
intro: 您可以重新打开关闭的项目板，并重新启动为项目板配置的任何工作流程自动化。
|
||||
title: 'Reopening a closed {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can reopen a closed {% data variables.projects.projects_v1_board %} and restart any workflow automation that was configured for the {% data variables.projects.projects_v1_board %}.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/managing-project-boards/reopening-a-closed-project-board
|
||||
- /articles/reopening-a-closed-project-board
|
||||
- /github/managing-your-work-on-github/reopening-a-closed-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 重新打开项目板
|
||||
shortTitle: 'Reopen {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
关闭项目板时，默认情况下，为项目板配置的任何工作流程自动化都将暂停。 更多信息请参阅“[关闭项目板](/articles/closing-a-project-board)”。
|
||||
When you close a {% data variables.projects.projects_v1_board %}, any workflow automation that was configured for the {% data variables.projects.projects_v1_board %} will pause by default. For more information, see "[Closing a {% data variables.product.prodname_project_v1 %}](/articles/closing-a-project-board)."
|
||||
|
||||
重新打开项目板时，您可以选择*同步*自动化，以便根据为项目板配置的自动化设置来更新板上卡的位置。
|
||||
When you reopen a {% data variables.projects.projects_v1_board %}, you have the option to *sync* automation, which updates the position of the cards on the board according to the automation settings configured for the board.
|
||||
|
||||
1. 导航到要重新打开的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} you want to reopen.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
3. 选择是同步项目板的自动化还是重新打开项目板而不同步。
|
||||
- 要重新打开项目板并同步自动化，请单击 **Reopen and sync project（重新打开并同步项目）**。 
|
||||
- 要重新打开项目板而不同步自动化，请使用重新打开下拉菜单，单击 **Reopen only（仅重新打开）**， 然后单击 **Reopen only（仅重新打开）**。 
|
||||
3. Choose whether to sync automation for your {% data variables.projects.projects_v1_board %} or reopen your {% data variables.projects.projects_v1_board %} without syncing.
|
||||
- To reopen your {% data variables.projects.projects_v1_board %} and sync automation, click **Reopen and sync project**. 
|
||||
- To reopen your {% data variables.projects.projects_v1_board %} without syncing automation, using the reopen drop-down menu, click **Reopen only**. 然后单击 **Reopen only（仅重新打开）**。 
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- “[配置项目板的自动化](/articles/configuring-automation-for-project-boards)”
|
||||
- "[Configuring automation for {% data variables.product.prodname_projects_v1 %}](/articles/configuring-automation-for-project-boards)"
|
||||
|
||||
@@ -1,27 +1,25 @@
|
||||
---
|
||||
title: 添加议题和拉取请求到项目板
|
||||
intro: 您可以通过卡片的形式将议题和拉取请求添加到项目板，并且分类到各列中。
|
||||
title: 'Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can add issues and pull requests to a {% data variables.projects.projects_v1_board %} in the form of cards and triage them into columns.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-issues-and-pull-requests-to-a-project-board
|
||||
- /articles/adding-issues-and-pull-requests-to-a-project
|
||||
- /articles/adding-issues-and-pull-requests-to-a-project-board
|
||||
- /github/managing-your-work-on-github/adding-issues-and-pull-requests-to-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 将议题和 PR 添加到板中
|
||||
shortTitle: 'Add issues & PRs to {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
您可通过以下方式将议题或拉取请求卡添加到项目板：
|
||||
You can add issue or pull request cards to your {% data variables.projects.projects_v1_board %} by:
|
||||
- 从侧栏的 **Triage（分类）**部分拖动卡片。
|
||||
- 在卡片中输入议题或拉取请求 URL。
|
||||
- 在项目板搜索侧栏中搜索议题或拉取请求。
|
||||
- Searching for issues or pull requests in the {% data variables.projects.projects_v1_board %} search sidebar.
|
||||
|
||||
每个项目列中最多可以输入 2,500 张卡片。 如果一列已经达到最大卡片数，则无法将卡片移入该列。
|
||||
|
||||
@@ -29,28 +27,28 @@ shortTitle: 将议题和 PR 添加到板中
|
||||
|
||||
{% note %}
|
||||
|
||||
**注：**您可以添加注释到项目板以用作任务提醒，引用 {% data variables.product.product_name %} 上任何仓库中的议题和拉取请求，或者添加与项目板相关的信息。 更多信息请参阅“[添加注释到项目板](/articles/adding-notes-to-a-project-board)”。
|
||||
**Note:** You can also add notes to your project board to serve as task reminders, references to issues and pull requests from any repository on {% data variables.product.product_name %}, or to add related information to your {% data variables.projects.projects_v1_board %}. 更多信息请参阅“[添加注释到项目板](/articles/adding-notes-to-a-project-board)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.project-management.edit-in-project %}
|
||||
|
||||
{% data reusables.project-management.link-repos-to-project-board %} 在搜索要添加到项目板的议题和拉取请求时，搜索会自动将范围限于您链接的仓库。 您可以删除这些限定符以搜索所有组织仓库。 更多信息请参阅“[链接仓库到项目板](/articles/linking-a-repository-to-a-project-board)”。
|
||||
{% data reusables.project-management.link-repos-to-project-board %} When you search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %}, the search automatically scopes to your linked repositories. 您可以删除这些限定符以搜索所有组织仓库。 更多信息请参阅“[链接仓库到项目板](/articles/linking-a-repository-to-a-project-board)”。
|
||||
|
||||
## 添加议题和拉取请求到项目板
|
||||
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. 导航到您要在其中添加议题和拉取请求的项目板。
|
||||
2. 在项目板中，单击 {% octicon "plus" aria-label="The plus icon" %} **Add cards（添加卡）**。 
|
||||
3. 使用搜索限定符搜索要添加到项目板的议题和拉取请求。 有关您可以使用的搜索限定符的更多信息，请参阅“[搜索议题](/articles/searching-issues)”。 
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add issues and pull requests.
|
||||
2. In your {% data variables.projects.projects_v1_board %}, click {% octicon "plus" aria-label="The plus icon" %} **Add cards**. 
|
||||
3. Search for issues and pull requests to add to your {% data variables.projects.projects_v1_board %} using search qualifiers. 有关您可以使用的搜索限定符的更多信息，请参阅“[搜索议题](/articles/searching-issues)”。 
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**
|
||||
- 您也可以通过在卡中输入 URL 来添加议题或拉取请求。
|
||||
- 如果您在使用特定功能，可以将标签贴到该功能的每个相关议题或拉取请求，然后通过搜索标签名称轻松地将卡片添加到项目板。 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests)”。
|
||||
- If you're working on a specific feature, you can apply a label to each related issue or pull request for that feature, and then easily add cards to your {% data variables.projects.projects_v1_board %} by searching for the label name. 更多信息请参阅“[应用标签到议题和拉取请求](/articles/applying-labels-to-issues-and-pull-requests)”。
|
||||
|
||||
{% endtip %}
|
||||
4. 从过滤的议题和拉取请求列表，将要添加到项目板的卡片拖放到正确的列中。 也可以使用键盘快捷键移动卡片。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
|
||||
4. From the filtered list of issues and pull requests, drag the card you'd like to add to your {% data variables.projects.projects_v1_board %} and drop it in the correct column. 也可以使用键盘快捷键移动卡片。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -58,16 +56,16 @@ shortTitle: 将议题和 PR 添加到板中
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 从侧栏添加议题和拉取请求到项目板
|
||||
## Adding issues and pull requests to a {% data variables.projects.projects_v1_board %} from the sidebar
|
||||
|
||||
1. 在议题或拉取请求右侧单击 **Projects（项目）{% octicon "gear" aria-label="The Gear icon" %}**。 
|
||||
2. 单击要添加到其中的项目板对应的 **Recent（最近）**、**Repository（仓库）**、**User（用户）**或 **Organization（组织）**选项卡。 
|
||||
2. Click the **Recent**, **Repository**,**User**, or **Organization** tab for the {% data variables.projects.projects_v1_board %} you would like to add to. 
|
||||
3. 在 **Filter projects（过滤项目）**字段中输入项目的名称。 
|
||||
4. 选择要添加议题或拉取请求的一个或多个项目板。 
|
||||
5. 单击 {% octicon "triangle-down" aria-label="The down triangle icon" %}，然后单击您希望议题或拉取请求所在的列。 该卡将移到您选择的项目板列的底部。 
|
||||
4. Select one or more {% data variables.projects.projects_v1_boards %} where you want to add the issue or pull request. 
|
||||
5. 单击 {% octicon "triangle-down" aria-label="The down triangle icon" %}，然后单击您希望议题或拉取请求所在的列。 The card will move to the bottom of the {% data variables.projects.projects_v1_board %} column you select. 
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- "[编辑项目板](/articles/editing-a-project-board)"
|
||||
- "[过滤项目板上的卡](/articles/filtering-cards-on-a-project-board)"
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
|
||||
- "[Filtering cards on a {% data variables.product.prodname_project_v1 %}](/articles/filtering-cards-on-a-project-board)"
|
||||
|
||||
@@ -1,19 +1,17 @@
|
||||
---
|
||||
title: 添加注释到项目板
|
||||
intro: 您可以添加注释到项目板以用作任务提醒，或者添加与项目板相关的信息。
|
||||
title: 'Adding notes to a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can add notes to a {% data variables.projects.projects_v1_board %} to serve as task reminders or to add information related to the {% data variables.projects.projects_v1_board %}.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/adding-notes-to-a-project-board
|
||||
- /articles/adding-notes-to-a-project
|
||||
- /articles/adding-notes-to-a-project-board
|
||||
- /github/managing-your-work-on-github/adding-notes-to-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 添加备注到板
|
||||
shortTitle: 'Add notes to {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
@@ -23,17 +21,17 @@ shortTitle: 添加备注到板
|
||||
**提示：**
|
||||
- 您可以使用 Markdown 语法格式化注释。 例如，可以使用标题、链接、任务列表或表情符号。 更多信息请参阅“[基本撰写和格式语法](/articles/basic-writing-and-formatting-syntax)”。
|
||||
- 可以通过拖放或键盘快捷键对注释重新排序以及在列之间移动它们。 {% data reusables.project-management.for-more-info-project-keyboard-shortcuts %}
|
||||
- 项目板必须至少有一列才可添加注释。 更多信息请参阅“[创建项目板](/articles/creating-a-project-board)”。
|
||||
- Your {% data variables.projects.projects_v1_board %} must have at least one column before you can add notes. 更多信息请参阅“[创建项目板](/articles/creating-a-project-board)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
在注释中添加议题、拉取请求或另一个项目板的 URL 时，在文本下面的摘要卡中会看到预览。
|
||||
When you add a URL for an issue, pull request, or another {% data variables.projects.projects_v1_board %} to a note, you'll see a preview in a summary card below your text.
|
||||
|
||||
|
||||
|
||||
## 添加注释到项目板
|
||||
## Adding notes to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. 导航到您要在其中添加注释的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to add notes.
|
||||
2. 在要添加注释的列中，单击 {% octicon "plus" aria-label="The plus icon" %}。 
|
||||
3. 输入您的注释，然后单击 **Add（添加）**。 
|
||||
|
||||
@@ -51,17 +49,17 @@ shortTitle: 添加备注到板
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**您可以添加注释正文的内容以 @提及某人、链接到其他议题或拉取请求，以及添加表情符号。 这些 {% data variables.product.prodname_dotcom %} Flavored Markdown 功能在项目板注释中不受支持，但在注释转换为议题之后，它们会正确显示。 有关使用这些功能的更多信息，请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/about-writing-and-formatting-on-github)”。
|
||||
**提示：**您可以添加注释正文的内容以 @提及某人、链接到其他议题或拉取请求，以及添加表情符号。 These {% data variables.product.prodname_dotcom %} Flavored Markdown features aren't supported within {% data variables.projects.projects_v1_board %} notes, but once your note is converted to an issue, they'll appear correctly. 有关使用这些功能的更多信息，请参阅“[关于在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/articles/about-writing-and-formatting-on-github)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 导航到您要转换为议题的注释。
|
||||
{% data reusables.project-management.project-note-more-options %}
|
||||
3. 单击 **Convert to issue（转换为议题）**。 
|
||||
4. 如果卡在全组织项目板上，请从下拉菜单中选择要添加议题到其中的仓库。 
|
||||
4. If the card is on an organization-wide {% data variables.projects.projects_v1_board %}, in the drop-down menu, choose the repository you want to add the issue to. 
|
||||
5. 可以选择编辑预填的议题标题，并输入议题正文。 
|
||||
6. 单击 **Convert to issue（转换为议题）**。
|
||||
7. 该注释会自动转换为议题。 在项目板中，新议题卡与之前注释的位置一样。
|
||||
7. 该注释会自动转换为议题。 In the {% data variables.projects.projects_v1_board %}, the new issue card will be in the same location as the previous note.
|
||||
|
||||
## 编辑和删除注释
|
||||
|
||||
@@ -72,7 +70,7 @@ shortTitle: 添加备注到板
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- "[创建项目板](/articles/creating-a-project-board)"
|
||||
- "[编辑项目板](/articles/editing-a-project-board)"
|
||||
- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
- "[创建 {% data variables.product.prodname_project_v1 %}](/articles/creating-a-project-board)"
|
||||
- "[Editing a {% data variables.product.prodname_project_v1 %}](/articles/editing-a-project-board)"
|
||||
- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
|
||||
@@ -1,31 +1,29 @@
|
||||
---
|
||||
title: 存档项目板上的卡
|
||||
intro: 您可以存档项目板卡，以整理工作流程而不失去项目的历史上下文。
|
||||
title: 'Archiving cards on a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can archive {% data variables.projects.projects_v1_board %} cards to declutter your workflow without losing the historical context of a project.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/archiving-cards-on-a-project-board
|
||||
- /articles/archiving-cards-on-a-project-board
|
||||
- /github/managing-your-work-on-github/archiving-cards-on-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 存档内置卡
|
||||
shortTitle: 'Archive cards on {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
项目板中的自动化不适用于存档的项目板卡。 例如，如果您关闭项目板存档中的议题，存档的卡不会自动移到 "Done"（完成）列。 从项目板存档恢复卡时，该卡将回到存档它的列。
|
||||
Automation in your {% data variables.projects.projects_v1_board %} does not apply to archived {% data variables.projects.projects_v1_board %} cards. For example, if you close an issue in a {% data variables.projects.projects_v1_board %}'s archive, the archived card does not automatically move to the "Done" column. When you restore a card from the {% data variables.projects.projects_v1_board %} archive, the card will return to the column where it was archived.
|
||||
|
||||
## 存档项目板上的卡
|
||||
## Archiving cards on a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
1. 在项目板中，找到要存档的卡片，然后单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}。 
|
||||
1. In a {% data variables.projects.projects_v1_board %}, find the card you want to archive, then click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}. 
|
||||
2. 单击 **Archive（存档）**。 
|
||||
|
||||
## 从侧栏恢复项目板中的卡
|
||||
## Restoring cards on a {% data variables.projects.projects_v1_board %} from the sidebar
|
||||
|
||||
{% data reusables.project-management.click-menu %}
|
||||
2. 单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **View archive（查看存档）**。 
|
||||
3. 在要取消存档的项目板卡上方，单击 **Restore（恢复）**。 
|
||||
3. Above the {% data variables.projects.projects_v1_board %} card you want to unarchive, click **Restore**. 
|
||||
|
||||
@@ -1,25 +1,23 @@
|
||||
---
|
||||
title: 过滤项目板上的卡
|
||||
intro: 您可以过滤项目板上的卡以搜索特定卡或查看卡的子集。
|
||||
title: 'Filtering cards on a {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can filter the cards on a {% data variables.projects.projects_v1_board %} to search for specific cards or view a subset of the cards.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/filtering-cards-on-a-project-board
|
||||
- /articles/filtering-cards-on-a-project-board
|
||||
- /github/managing-your-work-on-github/filtering-cards-on-a-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 在板上筛选卡
|
||||
shortTitle: 'Filter cards on {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
在卡上，您可以单击任意受理人、里程碑或标签，以便按该限定符过滤项目板。 要清除搜索，您可以再次单击相同的受理人、里程碑或标签。
|
||||
On a card, you can click any assignee, milestone, or label to filter the {% data variables.projects.projects_v1_board %} by that qualifier. 要清除搜索，您可以再次单击相同的受理人、里程碑或标签。
|
||||
|
||||
也可使用每个项目板顶部的“Filter cards（过滤卡）”搜索栏来搜索卡。 您可以使用以下搜索限定符的任意组合来过滤卡，或者直接输入您要搜索的某些文本。
|
||||
You can also use the "Filter cards" search bar at the top of each {% data variables.projects.projects_v1_board %} to search for cards. 您可以使用以下搜索限定符的任意组合来过滤卡，或者直接输入您要搜索的某些文本。
|
||||
|
||||
- 使用 `author:USERNAME` 按作者过滤卡
|
||||
- 使用 `assignee:USERNAME` 或 `no:assignee` 按受理人过滤卡
|
||||
@@ -31,9 +29,9 @@ shortTitle: 在板上筛选卡
|
||||
- 使用 `type:issue`、`type:pr` 或 `type:note` 按类型过滤卡
|
||||
- 使用 `is:open`、`is:closed` 或 `is:merged` 和 `is:issue`、`is:pr` 或 `is:note` 按状态和类型过滤卡
|
||||
- 使用 `linked:pr`，按通过结束引用链接到拉取请求的问题筛选卡片
|
||||
- 使用 `repo:ORGANIZATION/REPOSITORY` 在组织范围的项目板中按仓库过滤卡
|
||||
- Filter cards by repository in an organization-wide {% data variables.projects.projects_v1_board %} using `repo:ORGANIZATION/REPOSITORY`
|
||||
|
||||
1. 导航到包含要过滤的卡的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} that contains the cards you want to filter.
|
||||
2. 在项目卡列上方，单击“Filter cards（过滤卡）”搜索栏并键入搜索查询以过滤卡。 
|
||||
|
||||
{% tip %}
|
||||
@@ -44,6 +42,6 @@ shortTitle: 在板上筛选卡
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[关于项目板](/articles/about-project-boards)"
|
||||
- "[添加议题和拉取请求到项目板](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- “[添加注释到项目板](/articles/adding-notes-to-a-project-board)”
|
||||
- "[关于 {% data variables.product.prodname_projects_v1 %}](/articles/about-project-boards)"
|
||||
- "[Adding issues and pull requests to a {% data variables.product.prodname_project_v1 %}](/articles/adding-issues-and-pull-requests-to-a-project-board)"
|
||||
- "[Adding notes to a {% data variables.product.prodname_project_v1 %}](/articles/adding-notes-to-a-project-board)"
|
||||
|
||||
@@ -1,12 +1,9 @@
|
||||
---
|
||||
title: 跟踪项目板上的进度
|
||||
shortTitle: 跟踪项目
|
||||
intro: 了解如何跟踪您在项目板上的工作
|
||||
title: 'Tracking progress on your {% data variables.product.prodname_projects_v1 %}'
|
||||
shortTitle: 'Tracking {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'Learn how to track your work on {% data variables.projects.projects_v1_board %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Issues
|
||||
- Projects
|
||||
@@ -18,6 +15,7 @@ children:
|
||||
- /archiving-cards-on-a-project-board
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
@@ -1,25 +1,23 @@
|
||||
---
|
||||
title: 跟踪项目板上的进度
|
||||
intro: 您可以在进度条中看到项目的总体进度。
|
||||
title: 'Tracking progress on your {% data variables.product.prodname_project_v1 %}'
|
||||
intro: 'You can see the overall progress of your {% data variables.projects.projects_v1_board %} in a progress bar.'
|
||||
redirect_from:
|
||||
- /github/managing-your-work-on-github/tracking-the-progress-of-your-work-with-project-boards/tracking-progress-on-your-project-board
|
||||
- /articles/tracking-progress-on-your-project-board
|
||||
- /github/managing-your-work-on-github/tracking-progress-on-your-project-board
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v1
|
||||
topics:
|
||||
- Pull requests
|
||||
shortTitle: 跟踪进度
|
||||
shortTitle: 'Track progress on {% data variables.product.prodname_project_v1 %}'
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% data reusables.project-management.project-progress-locations %}
|
||||
|
||||
1. 导航到您想在其中启用或禁用项目进度跟踪的项目板。
|
||||
1. Navigate to the {% data variables.projects.projects_v1_board %} where you want to enable or disable project progress tracking.
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.click-edit-sidebar-menu-project-board %}
|
||||
4. 选择或取消选择 **Track project progress（跟踪项目进度）**。
|
||||
|
||||
@@ -1,33 +1,18 @@
|
||||
---
|
||||
title: 自动化项目（测试版）
|
||||
intro: '您可以使用内置工作流程或 API 和 {% data variables.product.prodname_actions %} 来管理项目。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
title: 'Automating {% data variables.product.prodname_projects_v2 %} using Actions'
|
||||
shortTitle: Automating with Actions
|
||||
intro: 'You can use {% data variables.product.prodname_actions %} to automate your projects.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
feature: projects-v2
|
||||
redirect_from:
|
||||
- /issues/trying-out-the-new-projects-experience/automating-projects
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
- Workflows
|
||||
- Project management
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data reusables.projects.projects-beta %}
|
||||
|
||||
{% data reusables.projects.graphql-deprecation %}
|
||||
|
||||
## 简介
|
||||
|
||||
您可以添加自动化来帮助管理项目。 项目（测试版）包括可通过 UI 配置的内置工作流程。 此外，您可以使用 GraphQL API 和 {% data variables.product.prodname_actions %} 编写自定义工作流程。
|
||||
|
||||
## 内置工作流程
|
||||
|
||||
{% data reusables.projects.about-workflows %}
|
||||
|
||||
您可以为项目启用或禁用内置工作流程。
|
||||
|
||||
{% data reusables.projects.enable-basic-workflow %}
|
||||
|
||||
## {% data variables.product.prodname_actions %} 工作流程
|
||||
|
||||
@@ -39,11 +24,13 @@ topics:
|
||||
|
||||
本文假设您基本了解 {% data variables.product.prodname_actions %}。 有关 {% data variables.product.prodname_actions %} 的更多信息，请参阅“[{% data variables.product.prodname_actions %}](/actions)”。
|
||||
|
||||
有关可以通过 API 对项目进行的其他更改的更多信息，请参阅“[使用 API 管理项目](/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects)”。
|
||||
有关可以通过 API 对项目进行的其他更改的更多信息，请参阅“[使用 API 管理项目](/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects)”。
|
||||
|
||||
You may also want to use the **actions/add-to-project** workflow, which is maintained by {% data variables.product.company_short %} and will add the current issue or pull request to the project specified. For more information, see the [actions/add-to-project](https://github.com/actions/add-to-project) repository and README.
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：** `GITHUB_TOKEN` 的范围限定为存储库级别，无法访问项目（测试版）。 要访问项目（测试版），可以创建 {% data variables.product.prodname_github_app %} （建议用于组织项目）或个人访问令牌（建议用于用户项目）。 下面显示了这两种方法的工作流程示例。
|
||||
**Note:** `GITHUB_TOKEN` is scoped to the repository level and cannot access {% data variables.projects.projects_v2 %}. To access {% data variables.projects.projects_v2 %} you can either create a {% data variables.product.prodname_github_app %} (recommended for organization projects) or a personal access token (recommended for user projects). 下面显示了这两种方法的工作流程示例。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -66,6 +53,8 @@ topics:
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
|
||||
{% data reusables.actions.actions-use-sha-pinning-comment %}
|
||||
|
||||
name: Add PR to project
|
||||
on:
|
||||
pull_request:
|
||||
@@ -0,0 +1,16 @@
|
||||
---
|
||||
title: 'Automating your {% data variables.projects.project_v2 %}'
|
||||
shortTitle: 'Automating {% data variables.projects.projects_v2 %}'
|
||||
intro: 'Learn how to use the built-in workflows, {% data variables.product.prodname_actions %}, and the API to automate your projects.'
|
||||
versions:
|
||||
feature: projects-v2
|
||||
topics:
|
||||
- Issues
|
||||
- Projects
|
||||
children:
|
||||
- /using-the-built-in-automations
|
||||
- /using-the-api-to-manage-projects
|
||||
- /automating-projects-using-actions
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
@@ -1,22 +1,22 @@
|
||||
---
|
||||
title: 使用 API 管理项目（测试版）
|
||||
intro: 您可以使用 GraphQL API 来查找有关项目的信息并更新项目。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
title: 'Using the API to manage {% data variables.product.prodname_projects_v2 %}'
|
||||
shortTitle: Automating with the API
|
||||
intro: You can use the GraphQL API to automate your projects.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
allowTitleToDifferFromFilename: true
|
||||
type: how_to
|
||||
versions:
|
||||
feature: projects-v2
|
||||
redirect_from:
|
||||
- /issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
本文演示如何使用 GraphQL API 来管理项目。 For more information about how to use the API in a {% data variables.product.prodname_actions %} workflow, see "[Automating {% data variables.product.prodname_projects_v2 %} using Actions](/issues/planning-and-tracking-with-projects/automating-your-project/automating-projects-using-actions)." 有关可用数据类型的完整列表，请参阅“[参考](/graphql/reference)”。
|
||||
|
||||
{% data reusables.projects.graphql-deprecation %}
|
||||
|
||||
本文演示如何使用 GraphQL API 来管理项目。 有关如何在 {% data variables.product.prodname_actions %} 工作流程中使用 API 的详细信息，请参阅“[自动化项目（测试版）](/issues/trying-out-the-new-projects-experience/automating-projects)”。 有关可用数据类型的完整列表，请参阅“[参考](/graphql/reference)”。
|
||||
|
||||
{% data reusables.projects.projects-beta %}
|
||||
|
||||
## 身份验证
|
||||
|
||||
{% curl %}
|
||||
@@ -714,3 +714,7 @@ gh api graphql -f query='
|
||||
}'
|
||||
```
|
||||
{% endcli %}
|
||||
|
||||
## Using webhooks
|
||||
|
||||
You can use webhooks to subscribe to events taking place in your project. For example, when an item is edited, {% data variables.product.product_name %} can send a HTTP POST payload to the webhook's configured URL which can trigger automation on your server. For more information about webhooks, see "[About webhooks](/developers/webhooks-and-events/webhooks/about-webhooks)." To learn more about the `projects_v2_item` webhook event, see "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#projects_v2_item)."
|
||||
@@ -0,0 +1,23 @@
|
||||
---
|
||||
title: Using the built-in automations
|
||||
shortTitle: Using built-in automations
|
||||
intro: You can use built-in workflows to automate your projects.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Built-in workflows are available as part of a limited beta.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.about-workflows %}
|
||||
|
||||
您可以为项目启用或禁用内置工作流程。
|
||||
|
||||
{% data reusables.projects.enable-basic-workflow %}
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: '创建 {% data variables.projects.project_v2 %}'
|
||||
intro: Learn how to create an organization or user project.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
redirect_from:
|
||||
- /issues/trying-out-the-new-projects-experience/creating-a-project
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
---
|
||||
|
||||
{% data variables.product.prodname_projects_v2 %} are an adaptable collection of items that stay up-to-date with {% data variables.product.company_short %} data. Your projects can track issues, pull requests, and ideas that you note down. 您可以添加自定义字段并为特定目的创建视图。
|
||||
|
||||
## 创建项目
|
||||
|
||||
### 创建组织项目
|
||||
|
||||
Organization projects can track issues and pull requests from the organization's repositories.
|
||||
|
||||
{% data reusables.projects.create-project %}
|
||||
|
||||
### 创建用户项目
|
||||
|
||||
User projects can track issues and pull requests from the repositories owned by your personal account.
|
||||
|
||||
{% data reusables.projects.create-user-project %}
|
||||
|
||||
## 更新项目描述和 README
|
||||
|
||||
{% data reusables.projects.project-description %}
|
||||
|
||||
## 延伸阅读
|
||||
|
||||
- "[Adding your project to a repository](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository)"
|
||||
- "[Adding items to your project](/issues/planning-and-tracking-with-projects/managing-items-in-your-project/adding-items-to-your-project)"
|
||||
- "[Customizing a view](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view)"
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user