From 61cdbeea452527a35a087cf491bf163fbb7ed27e Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Thu, 24 Feb 2022 11:32:57 -0800 Subject: [PATCH] New translation batch for cn (#25638) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check parsing * 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: Rachael Sewell --- translations/log/cn-resets.csv | 7 ++ ...tributions-not-showing-up-on-my-profile.md | 74 ++++++------ ...-collaborators-to-a-personal-repository.md | 4 +- ...uity-of-your-user-accounts-repositories.md | 2 +- ...ourself-from-a-collaborators-repository.md | 2 +- .../setting-your-commit-email-address.md | 2 +- ...does-the-available-for-hire-checkbox-do.md | 2 +- .../metadata-syntax-for-github-actions.md | 66 ++++++++--- .../about-monitoring-and-troubleshooting.md | 27 +++-- .../viewing-job-execution-time.md | 4 +- .../automatic-token-authentication.md | 2 +- .../security-hardening-for-github-actions.md | 10 ++ .../using-github-hosted-runners/index.md | 1 + .../monitoring-your-current-jobs.md | 30 +++++ .../actions/using-jobs/using-concurrency.md | 5 + ...starter-workflows-for-your-organization.md | 4 +- .../events-that-trigger-workflows.md | 38 ++++++ .../using-starter-workflows.md | 2 + .../managing-dormant-users.md | 6 - ...ut-billing-for-github-advanced-security.md | 106 +++-------------- ...ing-your-github-advanced-security-usage.md | 6 +- .../about-billing-for-codespaces.md | 6 + .../index.md | 2 +- .../about-billing-for-your-enterprise.md | 2 +- .../managing-invoices-for-your-enterprise.md | 4 +- .../about-licenses-for-github-enterprise.md | 6 +- ...rise-server-and-github-enterprise-cloud.md | 16 ++- ...ing-codeql-code-scanning-in-a-container.md | 2 +- ...tting-up-code-scanning-for-a-repository.md | 42 +++++-- ...-codeql-code-scanning-in-your-ci-system.md | 35 +++--- ...onfiguring-codeql-cli-in-your-ci-system.md | 2 +- ...ng-from-the-codeql-runner-to-codeql-cli.md | 2 +- .../zh-CN/content/code-security/guides.md | 21 ++-- .../zh-CN/content/code-security/index.md | 6 +- ...-disclosure-of-security-vulnerabilities.md | 6 +- ...b-security-advisories-for-repositories.md} | 19 +-- ...ator-to-a-repository-security-advisory.md} | 17 +-- ...ve-a-repository-security-vulnerability.md} | 15 ++- ...reating-a-repository-security-advisory.md} | 13 ++- ...editing-a-repository-security-advisory.md} | 13 ++- .../repository-security-advisories/index.md | 29 +++++ ...vels-for-repository-security-advisories.md | 45 ++++++++ ...lishing-a-repository-security-advisory.md} | 19 +-- ...or-from-a-repository-security-advisory.md} | 11 +- ...hdrawing-a-repository-security-advisory.md | 23 ++++ .../managing-alerts-from-secret-scanning.md | 4 +- .../security-advisories/index.md | 28 ----- ...rmission-levels-for-security-advisories.md | 42 ------- .../withdrawing-a-security-advisory.md | 20 ---- ...ilities-in-the-github-advisory-database.md | 3 + ...isories-in-the-github-advisory-database.md | 32 +++++ .../index.md | 1 + .../understanding-billing-for-codespaces.md | 2 + .../customizing-your-codespace/index.md | 1 - ...prebuilding-codespaces-for-your-project.md | 26 ----- .../codespaces-lifecycle.md | 4 +- .../creating-a-codespace.md | 2 + .../deleting-a-codespace.md | 2 +- .../codespaces/getting-started/deep-dive.md | 98 ++++++++-------- .../codespaces/getting-started/quickstart.md | 6 +- .../zh-CN/content/codespaces/index.md | 3 +- .../zh-CN/content/codespaces/overview.md | 28 ++--- .../about-codespaces-prebuilds.md | 44 +++++++ .../configuring-prebuilds.md | 93 +++++++++++++++ .../prebuilding-your-codespaces/index.md | 19 +++ .../managing-prebuilds.md | 109 ++++++++++++++++++ .../testing-dev-container-changes.md | 35 ++++++ ...configuring-codespaces-for-your-project.md | 6 +- ...um-specification-for-codespace-machines.md | 2 +- ...g-up-your-nodejs-project-for-codespaces.md | 6 +- .../troubleshooting/codespaces-logs.md | 68 +++++------ .../codespaces/troubleshooting/index.md | 1 + .../troubleshooting-prebuilds.md | 59 ++++++++++ ...eshooting-your-connection-to-codespaces.md | 4 +- .../working-with-support-for-codespaces.md | 30 ++--- ...g-and-authorizing-users-for-github-apps.md | 4 +- .../apply-for-a-student-developer-pack.md | 6 +- ...isual-studio-code-with-github-classroom.md | 14 +-- .../github-extensions-and-integrations.md | 8 +- .../about-github-advanced-security.md | 14 ++- .../using-github/github-command-palette.md | 4 +- .../github-cli/github-cli/about-github-cli.md | 2 +- ...-against-modern-slavery-and-child-labor.md | 2 +- .../customizing-your-organizations-profile.md | 26 ++--- .../backing-up-a-repository.md | 6 +- ...uring-commit-rebasing-for-pull-requests.md | 2 +- ...ge-for-pull-requests-in-your-repository.md | 2 +- .../deleting-a-repository.md | 4 +- .../troubleshooting-cloning-errors.md | 2 +- .../about-code-owners.md | 18 +-- .../licensing-a-repository.md | 2 +- ...ithub-actions-settings-for-a-repository.md | 38 +++--- ...lyzing-changes-to-a-repositorys-content.md | 4 +- .../managing-files/index.md | 2 +- .../managing-files/renaming-a-file.md | 6 +- .../about-git-large-file-storage.md | 2 +- .../about-large-files-on-github.md | 22 ++-- .../about-storage-and-bandwidth-usage.md | 2 +- .../getting-permanent-links-to-files.md | 2 +- .../data/features/github-runner-dashboard.yml | 4 + .../data/learning-tracks/code-security.yml | 18 +-- .../enterprise-server/3-4/0-rc1.yml | 1 + .../actions/starter-workflow-categories.md | 5 + .../starter-workflow-overview.md | 1 + .../starter-workflows-beta.md | 5 + .../data/reusables/code-scanning/billing.md | 1 + .../codespaces/billing-for-prebuilds.md | 5 + .../codespaces/prebuilds-beta-note.md | 5 + .../codespaces/prebuilds-crossreference.md | 1 + .../dormant-user-release-phase.md | 2 +- ...github-hosted-runners-check-concurrency.md | 5 + ...runners-navigate-to-repo-org-enterprise.md | 12 ++ .../github-hosted-runners-table-entry.md | 1 + .../repository-level-advisory-note.md | 7 ++ translations/zh-CN/data/ui.yml | 1 + 115 files changed, 1183 insertions(+), 619 deletions(-) create mode 100644 translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md rename translations/zh-CN/content/code-security/{security-advisories => repository-security-advisories}/about-coordinated-disclosure-of-security-vulnerabilities.md (92%) rename translations/zh-CN/content/code-security/{security-advisories/about-github-security-advisories.md => repository-security-advisories/about-github-security-advisories-for-repositories.md} (62%) rename translations/zh-CN/content/code-security/{security-advisories/adding-a-collaborator-to-a-security-advisory.md => repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md} (50%) rename translations/zh-CN/content/code-security/{security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md => repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md} (81%) rename translations/zh-CN/content/code-security/{security-advisories/creating-a-security-advisory.md => repository-security-advisories/creating-a-repository-security-advisory.md} (58%) rename translations/zh-CN/content/code-security/{security-advisories/editing-a-security-advisory.md => repository-security-advisories/editing-a-repository-security-advisory.md} (77%) create mode 100644 translations/zh-CN/content/code-security/repository-security-advisories/index.md create mode 100644 translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md rename translations/zh-CN/content/code-security/{security-advisories/publishing-a-security-advisory.md => repository-security-advisories/publishing-a-repository-security-advisory.md} (75%) rename translations/zh-CN/content/code-security/{security-advisories/removing-a-collaborator-from-a-security-advisory.md => repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md} (63%) create mode 100644 translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md delete mode 100644 translations/zh-CN/content/code-security/security-advisories/index.md delete mode 100644 translations/zh-CN/content/code-security/security-advisories/permission-levels-for-security-advisories.md delete mode 100644 translations/zh-CN/content/code-security/security-advisories/withdrawing-a-security-advisory.md create mode 100644 translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md delete mode 100644 translations/zh-CN/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md create mode 100644 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md create mode 100644 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md create mode 100644 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md create mode 100644 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md create mode 100644 translations/zh-CN/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md create mode 100644 translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md create mode 100644 translations/zh-CN/data/features/github-runner-dashboard.yml create mode 100644 translations/zh-CN/data/reusables/actions/starter-workflow-categories.md create mode 100644 translations/zh-CN/data/reusables/advanced-security/starter-workflow-overview.md create mode 100644 translations/zh-CN/data/reusables/advanced-security/starter-workflows-beta.md create mode 100644 translations/zh-CN/data/reusables/code-scanning/billing.md create mode 100644 translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds.md create mode 100644 translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md create mode 100644 translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md create mode 100644 translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md create mode 100644 translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md create mode 100644 translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md create mode 100644 translations/zh-CN/data/reusables/security-advisory/repository-level-advisory-note.md diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 7279a221dbf9..ec2eefb13df9 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -1,7 +1,9 @@ file,reason +translations/zh-CN/content/account-and-profile/index.md,broken liquid tags translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags +translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,broken liquid tags translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,parsing error translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags @@ -72,11 +74,14 @@ translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/a translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,broken liquid tags translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,broken liquid tags +translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,parsing error translations/zh-CN/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-your-github-account/discounted-subscriptions-for-github-accounts.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-your-github-account/index.md,broken liquid tags translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,parsing error translations/zh-CN/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags +translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md,parsing error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,broken liquid tags @@ -87,6 +92,7 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags +translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-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/configuring-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/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 @@ -111,6 +117,7 @@ translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-c translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags +translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md,broken liquid tags translations/zh-CN/content/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam.md,broken liquid tags translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/adding-an-existing-project-to-github-using-github-desktop.md,broken liquid tags translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/about-git-large-file-storage-and-github-desktop.md,broken liquid tags diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md index 8804745a6db9..4d8e8fa20681 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md @@ -1,5 +1,5 @@ --- -title: 为什么我的贡献没有在我的个人资料中显示？ +title: Why are my contributions not showing up on my profile? intro: Learn common reasons that contributions may be missing from your contributions graph. redirect_from: - /articles/why-are-my-contributions-not-showing-up-on-my-profile @@ -17,43 +17,43 @@ shortTitle: Missing contributions ## About your contribution graph -Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.product.product_location %}. 贡献按照协调世界时 (UTC) 而不是您当地的时区加时间戳。 只有在满足特定标准时才会计算贡献。 在某些情况下，我们可能需要重建您的图表才能显示贡献。 +Your profile contributions graph is a record of contributions you've made to repositories {% ifversion ghae %}owned by{% else %}on{% endif %} {% data variables.product.product_location %}. Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone. Contributions are only counted if they meet certain criteria. In some cases, we may need to rebuild your graph in order for contributions to appear. -## 计算的贡献 +## Contributions that are counted -### 议题、拉取请求和讨论 +### Issues, pull requests and discussions -如果议题、拉取请求和讨论在独立的仓库而不是复刻中打开，它们将在您的贡献图中显示。 +Issues, pull requests and discussions will appear on your contribution graph if they were opened in a standalone repository, not a fork. -### 提交 -如果提交符合以下**所有**条件，则会在您的贡献图中显示： +### Commits +Commits will appear on your contributions graph if they meet **all** of the following conditions: - The email address used for the commits is associated with your account on {% data variables.product.product_location %}. -- 提交在独立的仓库而不是复刻中进行。 -- 提交在以下位置进行： - - 在仓库的默认分支中 - - 在 `gh-pages` 分支中（对于包含项目站点的仓库） +- The commits were made in a standalone repository, not a fork. +- The commits were made: + - In the repository's default branch + - In the `gh-pages` branch (for repositories with project sites) -有关项目网站的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +For more information on project sites, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -此外，必须**至少**满足以下条件之一： -- 您是仓库中的协作者，或者是拥有该仓库的组织的成员。 -- 您已复刻该仓库。 -- 您已打开仓库中的拉取请求或议题。 -- 您已为仓库加星标。 +In addition, **at least one** of the following must be true: +- You are a collaborator on the repository or are a member of the organization that owns the repository. +- You have forked the repository. +- You have opened a pull request or issue in the repository. +- You have starred the repository. -## 贡献未计算的常见原因 +## Common reasons that contributions are not counted {% data reusables.pull_requests.pull_request_merges_and_contributions %} -### 24 小时内进行的提交 +### Commit was made less than 24 hours ago -进行满足计为贡献要求的提交后，您可能需要等待最长 24 小时才能看到在贡献图中显示的贡献。 +After making a commit that meets the requirements to count as a contribution, you may need to wait for up to 24 hours to see the contribution appear on your contributions graph. -### 您的本地 Git 提交电子邮件地址未连接到您的帐户 +### Your local Git commit email isn't connected to your account Commits must be made with an email address that is connected to your account on {% data variables.product.product_location %}{% ifversion fpt or ghec %}, or the {% data variables.product.prodname_dotcom %}-provided `noreply` email address provided to you in your email settings,{% endif %} in order to appear on your contributions graph.{% ifversion fpt or ghec %} For more information about `noreply` email addresses, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)."{% endif %} -您可以通过将 `.patch` 添加到提交 URL 结尾来检查用于提交的电子邮件地址，例如 https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch： +You can check the email address used for a commit by adding `.patch` to the end of a commit URL, e.g. https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch: ``` From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001 @@ -62,9 +62,9 @@ Date: Sun, 27 Apr 2014 15:36:39 +0530 Subject: [PATCH] updated index for better welcome message ``` -`From:` 字段中的电子邮件地址是在[本地 git 配置设置](/articles/set-up-git)中设置的地址。 在本例中，用于提交的电子邮件地址是 `octocat@nowhere.com`。 +The email address in the `From:` field is the address that was set in the [local git config settings](/articles/set-up-git). In this example, the email address used for the commit is `octocat@nowhere.com`. -If the email address used for the commit is not connected to your account on {% data variables.product.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.product.product_location %}. 您的贡献图将在添加新地址后自动重建。{% endif %} +If the email address used for the commit is not connected to your account on {% data variables.product.product_location %}, {% ifversion ghae %}change the email address used to author commits in Git. For more information, see "[Setting your commit email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)."{% else %}you must [add the email address](/articles/adding-an-email-address-to-your-github-account) to your account on {% data variables.product.product_location %}. Your contributions graph will be rebuilt automatically when you add the new address.{% endif %} {% warning %} @@ -72,27 +72,27 @@ If the email address used for the commit is not connected to your account on {% {% endwarning %} -### 提交没有在默认或 `gh-pages` 分支中进行 +### Commit was not made in the default or `gh-pages` branch -仅发生在默认分支或 `gh-pages` 分支（对于包含项目站点的仓库）中的提交才会计入。 更多信息请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。 +Commits are only counted if they are made in the default branch or the `gh-pages` branch (for repositories with project sites). For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)." -如果您的提交位于非默认或非 `gh-pages` 分支中，并且您希望将其计入您的贡献，则需要执行以下操作之一： -- [打开拉取请求](/articles/creating-a-pull-request)以将您的更改合并到默认分支或 `gh-pages` 分支。 -- [更改仓库的默认分支](/github/administering-a-repository/changing-the-default-branch)。 +If your commits are in a non-default or non-`gh-pages` branch and you'd like them to count toward your contributions, you will need to do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the default branch or the `gh-pages` branch. +- [Change the default branch](/github/administering-a-repository/changing-the-default-branch) of the repository. {% warning %} -**Warning**: Changing the default branch of the repository will change it for all repository collaborators. 仅当您希望新分支成为进行所有未来拉取请求和提交的基础时才执行此操作。 +**Warning**: Changing the default branch of the repository will change it for all repository collaborators. Only do this if you want the new branch to become the base against which all future pull requests and commits will be made. {% endwarning %} -### 提交在复刻中进行 +### Commit was made in a fork -在复刻中进行的提交不会计入您的贡献。 要将其计入，您必须执行以下操作之一： -- [打开拉取请求](/articles/creating-a-pull-request)以将您的更改合并到父仓库。 -- To detach the fork and turn it into a standalone repository on {% data variables.product.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. 更多信息请参阅“[关于复刻](/articles/about-forks/)”。 +Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following: +- [Open a pull request](/articles/creating-a-pull-request) to have your changes merged into the parent repository. +- To detach the fork and turn it into a standalone repository on {% data variables.product.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[About forks](/articles/about-forks/)." -## 延伸阅读 +## Further reading -- "[在个人资料中公开或隐藏私有贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" -- "[在个人资料页面中查看贡献](/articles/viewing-contributions-on-your-profile-page)" +- "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)" +- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)" diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md index c8a89835736d..b01b76019b0a 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md @@ -25,7 +25,7 @@ shortTitle: 邀请协作者 {% ifversion fpt or ghec %} -If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %} +如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员，则只能邀请企业的其他成员与您协作。 {% data reusables.enterprise-accounts.emu-more-info-account %} {% note %} @@ -47,7 +47,7 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y 5. 在左侧边栏中，单击 **Collaborators（协作者）**。 ![突出显示协作者的仓库设置侧边栏](/assets/images/help/repository/user-account-repo-settings-collaborators.png) 6. 在 "Collaborators"（协作者）下，开始输入协作者的用户名。 7. 从下拉菜单中选择协作者的用户名。 ![协作者列表下拉菜单](/assets/images/help/repository/repo-settings-collab-autofill.png) -8. 单击 **Add collaborator（添加协作者）**。 !["Add collaborator" button](/assets/images/help/repository/repo-settings-collab-add.png) +8. 单击 **Add collaborator（添加协作者）**。 !["添加协作者"按钮](/assets/images/help/repository/repo-settings-collab-add.png) {% endif %} {% ifversion fpt or ghec %} 9. 用户将会收到一封邀请他们参加仓库的电子邮件。 在接受邀请后，他们便对仓库具有协作者访问权限。 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md index 92e7e8f4c0a4..3aad87b5f557 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md @@ -23,7 +23,7 @@ shortTitle: 所有权连续性 继承者不能登录到您的帐户。 -指定的继承者在提交死亡证明并等待 7 天或者提交讣告并等待 21 天后，便可管理您的公共仓库。 For more information, see "[{% data variables.product.company_short %} Deceased User Policy](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)." +指定的继承者在提交死亡证明并等待 7 天或者提交讣告并等待 21 天后，便可管理您的公共仓库。 更多信息请参阅“[{% data variables.product.company_short %} 已故用户政策](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)”。 要请求作为继承者管理仓库，请联系 [GitHub 支持](https://support.github.com/contact?tags=docs-accounts)。 diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md index 299e9c840531..5acf5c9e69d1 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md @@ -22,7 +22,7 @@ shortTitle: 删除自己 {% data reusables.user-settings.access_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} -2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**. +2. 在侧边栏的“Code planning, and automation（代码规划和自动化）”部分中，点击 **{% octicon "repo" aria-label="The repo icon" %} Repositories（存储库）**。 {% else %} 2. 在左侧边栏中，单击 **Repositories（仓库）**。 ![仓库选项卡](/assets/images/help/settings/settings-sidebar-repositories.png) {% endif %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md index ffc8a8ddacb9..bd0009257f17 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md @@ -35,7 +35,7 @@ shortTitle: 设置提交电子邮件地址 {% note %} -**Note**: {% data reusables.user-settings.no-verification-disposable-emails %} +**注**：{% data reusables.user-settings.no-verification-disposable-emails %} {% endnote %} diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md index 3dcbab51de71..381bc5722892 100644 --- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md +++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md @@ -15,7 +15,7 @@ shortTitle: 可用于租用复选框 {% warning %} -弃用说明：GitHub Jobs 现已弃用。 最后一次发布工作日期是 2021 年 5 月 19 日。 The GitHub Jobs site has shut down entirely on August 19, 2021, and now redirects to the [GitHub blog post](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/) notice, which has more information on the now-completed deprecation of GitHub Jobs. +弃用说明：GitHub Jobs 现已弃用。 最后一次发布工作日期是 2021 年 5 月 19 日。 GitHub Jobs 网站已于 2021 年 8 月 19 日完全关闭，现在重定向到 [GitHub 博客文章](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/)通告，其中包含有关现已完成的 GitHub Jobs 弃用的更多信息。 {% endwarning %} diff --git a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md index d59a2a2c48d1..886eb87718dc 100644 --- a/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md +++ b/translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md @@ -110,6 +110,7 @@ outputs: **可选** `outputs` 使用与 `outputs.` 及 `outputs..description` 相同的参数（请参阅“用于 Docker 容器和 JavaScript 操作的 + `outputs`”），但也包括 `value` 令牌。

@@ -632,16 +633,45 @@ branding: ### `branding.icon` -要使用的 [Feather](https://feathericons.com/) 图标的名称。 - + @@ -656,7 +686,7 @@ branding: - + @@ -734,10 +764,10 @@ branding: - + - + @@ -780,14 +810,14 @@ branding: - + - + @@ -810,7 +840,7 @@ branding: - + @@ -912,7 +942,7 @@ branding: - + @@ -937,7 +967,7 @@ branding: - + @@ -949,7 +979,7 @@ branding: - + @@ -959,7 +989,7 @@ branding: - + @@ -989,15 +1019,15 @@ branding: - + - - + + @@ -1009,7 +1039,7 @@ branding: - + diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md index e6f8e413ae4a..1996d4e8fcb8 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md @@ -1,19 +1,26 @@ --- -title: About monitoring and troubleshooting -intro: 'You can use the tools in {% data variables.product.prodname_actions %} to monitor and debug your workflows.' +title: 关于监控和疑难解答 +intro: '您可以使用 {% data variables.product.prodname_actions %} 中的工具来监控和调试工作流程。' versions: fpt: '*' ghes: '*' ghae: '*' ghec: '*' -shortTitle: About monitoring and troubleshooting +shortTitle: 关于监控和疑难解答 miniTocMaxHeadingLevel: 3 --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Monitoring your workflows +## 监控工作流程 + +{% if github-runner-dashboard %} +### 监控组织或企业中的当前作业 + +{% data reusables.github-actions.github-hosted-runners-check-concurrency %} + +{% endif %} {% ifversion fpt or ghae or ghes > 3.0 or ghec %} @@ -23,7 +30,7 @@ miniTocMaxHeadingLevel: 3 ![工作流程图表](/assets/images/help/images/workflow-graph.png) -For more information, see "[Using the visualization graph](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)." +更多信息请参阅“[使用可视化图](/actions/monitoring-and-troubleshooting-workflows/using-the-visualization-graph)”。 {% endif %} @@ -36,7 +43,7 @@ For more information, see "[Using the visualization graph](/actions/monitoring-a {% ifversion fpt or ghec %} ### 查看作业执行时间 -To identify how long a job took to run, you can view its execution time. 例如： +要确定作业运行所花费的时间，可以查看其执行时间。 例如： ![运行和可计费时间详细信息链接](/assets/images/help/repository/view-run-billable-time.png) @@ -45,17 +52,17 @@ To identify how long a job took to run, you can view its execution time. 例如 ### 查看工作流程运行历史记录 -You can view the status of each job and step in a workflow. 例如： +您可以查看工作流程中每个作业和步骤的状态。 例如： ![工作流程运行的名称](/assets/images/help/repository/run-name.png) 更多信息请参阅“[查看工作流程运行历史记录](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)”。 -## Troubleshooting your workflows +## 工作流程疑难解答 ### 使用工作流程运行日志 -Each workflow run generates activity logs that you can view, search, and download. 例如： +每个工作流程运行都会生成活动日志，您可以查看、搜索和下载这些日志。 例如： ![Super linter 工作流程结果](/assets/images/help/repository/super-linter-workflow-results-updated-2.png) @@ -67,6 +74,6 @@ Each workflow run generates activity logs that you can view, search, and downloa ## 自托管运行器的监控和故障排除 -If you use self-hosted runners, you can view their activity and diagnose common issues. +如果您使用自托管运行器，则可以查看其活动并诊断常见问题。 更多信息请参阅“[自托管运行器监控和故障排除](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)”。 diff --git a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md index d1aa438095c8..a57e077bd192 100644 --- a/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md +++ b/translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md @@ -12,7 +12,7 @@ shortTitle: 查看作业执行时间 {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -Billable job execution minutes are only shown for jobs run on private repositories that use {% data variables.product.prodname_dotcom %}-hosted runners and are rounded up to the next minute. 如果在公共仓库中使用 {% data variables.product.prodname_actions %}，或在自托管的运行器中运行作业时，将没有可计费分钟数。 +计费作业执行分钟数仅显示在使用 {% data variables.product.prodname_dotcom %} 托管运行器的私有存储库上运行的作业，并四舍五入到下一分钟。 如果在公共仓库中使用 {% data variables.product.prodname_actions %}，或在自托管的运行器中运行作业时，将没有可计费分钟数。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %} @@ -22,6 +22,6 @@ Billable job execution minutes are only shown for jobs run on private repositori {% note %} - **Note:** The billable time shown does not include any minute multipliers. To view your total {% data variables.product.prodname_actions %} usage, including minute multipliers, see "[Viewing your {% data variables.product.prodname_actions %} usage](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)." + **注意：** 显示的计费时间不包括任何分钟乘数。 要查看您的 {% data variables.product.prodname_actions %} 总使用情况，包括分钟乘法，请参阅"[查看您的 {% data variables.product.prodname_actions %} 使用情况](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage)。" {% endnote %} diff --git a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md index 5f8c322fbf5f..41764e7158d7 100644 --- a/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md +++ b/translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md @@ -86,7 +86,7 @@ jobs: | 检查 | 读/写 | 无 | 读取 | | 内容 | 读/写 | 读取 | 读取 | | 部署 | 读/写 | 无 | read |{% ifversion fpt or ghec %} -| id-token | 读/写 | 无 | read +| id-token | 无 | 无 | read {% endif %} | 议题 | 读/写 | 无 | 读取 | | 元数据 | 读取 | 读取 | 读取 | diff --git a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md index 5697b4ae246a..a57c14f82217 100644 --- a/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md +++ b/translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md @@ -141,6 +141,16 @@ with: 使用此方法， {% raw %}`${{ github.event.issue.title }}`{% endraw %} 表达式的值存储在内存中用作变量，并且不与脚本生成过程交互。 此外，考虑使用双引号 shell 变量来避免 [单词拆分](https://github.com/koalaman/shellcheck/wiki/SC2086)，但这是是写入shell 脚本[的许多一般性建议之一](https://mywiki.wooledge.org/BashPitfalls)，不是专门针对 {% data variables.product.prodname_actions %} 的。 +{% ifversion fpt or ghec %} +### Using starter workflows for code scanning + +{% data reusables.advanced-security.starter-workflows-beta %} +{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available. + +For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)." + +{% endif %} + ### 限制令牌权限 为了帮助降低暴露令牌的风险，请考虑限制分配的权限。 更多信息请参阅“[修改 GITHUB_TOKEN 的权限](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)”。 diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md index afd5f999273f..61b3833948d0 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/index.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/index.md @@ -7,6 +7,7 @@ versions: ghes: '*' children: - /about-github-hosted-runners + - /monitoring-your-current-jobs - /customizing-github-hosted-runners shortTitle: 使用 GitHub 托管的运行器 --- diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md b/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md new file mode 100644 index 000000000000..ac5027e2afb7 --- /dev/null +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md @@ -0,0 +1,30 @@ +--- +title: Monitoring your current jobs +intro: 'Monitor how {% data variables.product.prodname_dotcom %}-hosted runners are processing jobs in your organization or enterprise, and identify any related constraints.' +versions: + feature: github-runner-dashboard +shortTitle: Monitoring your current jobs +--- + +{% data reusables.actions.enterprise-beta %} +{% data reusables.actions.enterprise-github-hosted-runners %} + +## Viewing active jobs in your organization or enterprise + +You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise. + +{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.github-hosted-runners-table-entry %} +1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners. + + ![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png) + +## Viewing queued jobs in your organization or enterprise + +{% data variables.product.prodname_dotcom %}-hosted runners allow you to run jobs concurrently, and the maximum number of concurrent jobs will vary depending on your plan. If you reach the maximum number of concurrent jobs, any new jobs will start to enter a queue. To find out more about the number of concurrent jobs available to your plan, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration)." + +The following procedure demonstrates how to check the maximum number of concurrent jobs you can run. + +{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %} +{% data reusables.github-actions.github-hosted-runners-table-entry %} +1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. ![Screenshot of the maximum jobs for an account](/assets/images/help/settings/github-hosted-runners-max-jobs.png) diff --git a/translations/zh-CN/content/actions/using-jobs/using-concurrency.md b/translations/zh-CN/content/actions/using-jobs/using-concurrency.md index 97e20c0ec4b8..d4f792b70713 100644 --- a/translations/zh-CN/content/actions/using-jobs/using-concurrency.md +++ b/translations/zh-CN/content/actions/using-jobs/using-concurrency.md @@ -17,3 +17,8 @@ miniTocMaxHeadingLevel: 4 {% data reusables.actions.jobs.section-using-concurrency-jobs %} +{% if github-runner-dashboard %} +## 监控组织或企业中的当前作业 + +{% data reusables.github-actions.github-hosted-runners-check-concurrency %} +{% endif %} diff --git a/translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md b/translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md index 5f6aa1a1e382..044f4a623904 100644 --- a/translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md +++ b/translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md @@ -24,12 +24,14 @@ topics: {% data reusables.actions.workflow-organization-templates %} +{% data reusables.actions.starter-workflow-categories %} + ## Creating a starter workflow Starter workflows can be created by users with write access to the organization's `.github` repository. These can then be used by organization members who have permission to create workflows. {% ifversion fpt %} -Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization). +Starter workflows created by users can only be used to create workflows in public repositories. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use starter workflows to create workflows in private repositories. 更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/actions/learn-github-actions/creating-starter-workflows-for-your-organization)。 {% endif %} {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} diff --git a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md index bfa0d4d362c3..6925a74d6dcd 100644 --- a/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md @@ -685,6 +685,25 @@ on: {% endnote %} +#### Running your workflow when a pull request merges + +When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged. + +```yaml +on: + pull_request: + types: + - closed + +jobs: + if_merged: + if: github.event.pull_request.merged == true + runs-on: ubuntu-latest + steps: + - run: | + echo The PR was merged +``` + {% data reusables.developer-site.pull_request_forked_repos_link %} ### `pull_request_comment` (use `issue_comment`) @@ -869,6 +888,25 @@ on: {% endnote %} +#### Running your workflow when a pull request merges + +When a pull request merges, the pull request is automatically closed. To run a workflow when a pull request merges, use the `pull_request_target` `closed` event type along with a conditional that checks the `merged` value of the event. For example, the following workflow will run whenever a pull request closes. The `if_merged` job will only run if the pull request was also merged. + +```yaml +on: + pull_request_target: + types: + - closed + +jobs: + if_merged: + if: github.event.pull_request_target.merged == true + runs-on: ubuntu-latest + steps: + - run: | + echo The PR was merged +``` + ### `推送` | Web 挂钩事件有效负载 | 活动类型 | `GITHUB_SHA` | `GITHUB_REF` | diff --git a/translations/zh-CN/content/actions/using-workflows/using-starter-workflows.md b/translations/zh-CN/content/actions/using-workflows/using-starter-workflows.md index 2ef7aec0d933..7036cc7643c7 100644 --- a/translations/zh-CN/content/actions/using-workflows/using-starter-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/using-starter-workflows.md @@ -28,6 +28,8 @@ topics: {% data variables.product.product_name %} offers starter workflows for a variety of languages and tooling. When you set up workflows in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow file that installs your Node.js packages and runs your tests.{% if actions-starter-template-ui %} You can search and filter to find relevant starter workflows.{% endif %} +{% data reusables.actions.starter-workflow-categories %} + You can also create your own starter workflow to share with your organization. These starter workflows will appear alongside the {% data variables.product.product_name %}-provided starter workflows. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)." ## Using starter workflows diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md index 0860cdaa1375..d9571da87745 100644 --- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md +++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users.md @@ -52,12 +52,6 @@ topics: {% data reusables.enterprise-accounts.dormant-user-release-phase %} -{% warning %} - -**注意：** 在私人测试期间，对报告下载功能的持续改进可能会限制其可用性。 - -{% endwarning %} - ## 从企业帐户下载休眠用户报告 {% data reusables.enterprise-accounts.access-enterprise %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md index c8e0d108a92b..6a8a95fbadfc 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md @@ -19,19 +19,19 @@ topics: shortTitle: Advanced Security billing --- -## 关于 {% data variables.product.prodname_GH_advanced_security %} 的计费 +## About billing for {% data variables.product.prodname_GH_advanced_security %} {% ifversion fpt %} -If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。 +If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license, available with {% data variables.product.prodname_ghe_cloud %} or {% data variables.product.prodname_ghe_server %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." {% elsif ghec %} -If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。 +If you want to use {% data variables.product.prodname_GH_advanced_security %} features on any repository apart from a public repository on {% data variables.product.prodname_dotcom_the_website %}, you will need a {% data variables.product.prodname_GH_advanced_security %} license. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." {% elsif ghes %} -您可以通过购买和上传 {% data variables.product.prodname_GH_advanced_security %} 许可为用户提供额外的代码安全功能。 有关 {% data variables.product.prodname_GH_advanced_security %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)”。 +You can make extra features for code security available to users by buying and uploading a license for {% data variables.product.prodname_GH_advanced_security %}. For more information about {% data variables.product.prodname_GH_advanced_security %}, see "[About {% data variables.product.prodname_GH_advanced_security %}](/github/getting-started-with-github/about-github-advanced-security)." {% endif %} @@ -43,7 +43,7 @@ If you want to use {% data variables.product.prodname_GH_advanced_security %} fe To discuss licensing {% data variables.product.prodname_GH_advanced_security %} for your enterprise, contact {% data variables.contact.contact_enterprise_sales %}. -## 关于 {% data variables.product.prodname_GH_advanced_security %} 的提交者数量 +## About committer numbers for {% data variables.product.prodname_GH_advanced_security %} {% data reusables.advanced-security.about-committer-numbers-ghec-ghes %} @@ -53,11 +53,11 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %} {% endif %} -您可以执行策略以允许或不允许企业帐户拥有的组织使用 {% data variables.product.prodname_advanced_security %}。 For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} +You can enforce policies to allow or disallow the use of {% data variables.product.prodname_advanced_security %} by organizations owned by your enterprise account. For more information, see "[Enforcing policies for {% data variables.product.prodname_advanced_security %} in your enterprise]({% ifversion fpt %}/enterprise-cloud@latest/{% endif %}/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %} {% ifversion fpt or ghes or ghec %} -有关查看许可使用情况的更多信息，请参阅“[查看 {% data variables.product.prodname_GH_advanced_security %} 使用情况](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)”。 +For more information on viewing license usage, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)." {% endif %} @@ -65,91 +65,13 @@ To discuss licensing {% data variables.product.prodname_GH_advanced_security %} The following example timeline demonstrates how active committer count for {% data variables.product.prodname_GH_advanced_security %} could change over time in an enterprise. For each month, you will find events, along with the resulting committer count. -
activity活动 airplay alert-circle alert-octagonalign-right anchor aperturearchive存档
arrow-down-circlecloud-rain cloud-snow cloudcode代码
command命令 compass copy corner-down-left
facebookfast-forward快进 feather file-minus
file-plus file-textfile文件 film
hard-drivehash哈希 headphones heart
repeatrewind倒回 rotate-ccw rotate-cw
shopping-cart shufflesidebar边栏 skip-back
speaker squarestar星标 stop-circle
tablet
tag标记 target terminal thermometerupload-cloud
upload上传 user-check user-minus user-plus
user-xuserusers用户用户 video-off
volume-x volumewatch查看 wifi-off
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- 日期 - - Events during the month - - Total committers -
- 15年4月 - - A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository X. Repository X has 50 committers over the past 90 days. - - 50 -
- May 1 - - Developer A leaves the team working on repository X. Developer A's contributions continue to count for 90 days. - - 50 | 50 -
- August 1 - - Developer A's contributions no longer count towards the licences required, because 90 days have passed. - - _50 - 1_
49 -
- 15年8月 - - A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository Y. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo X and do not require additional licenses. - - _49 + 10_
59 -
- 16年8月 - - A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository X. Of the 49 developers who were working on repository X, 10 still also work on repository Y, which has a total of 20 developers contributing in the last 90 days. - - _49 - 29_
20 -
+| Date | Events during the month | Total committers | +| :- | :- | -: | +| April 15 | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Repository **X** has 50 committers over the past 90 days. | **50** | +| May 1 | Developer **A** leaves the team working on repository **X**. Developer **A**'s contributions continue to count for 90 days. | **50** | **50** | +| August 1 | Developer **A**'s contributions no longer count towards the licences required, because 90 days have passed. | _50 - 1_
**49** | +| August 15 | A member of your enterprise enables {% data variables.product.prodname_GH_advanced_security %} for a second repository, repository **Y**. In the last 90 days, a total of 20 developers contributed to that repository. Of those 20 developers, 10 also recently worked on repo **X** and do not require additional licenses. | _49 + 10_
**59** | +| August 16 | A member of your enterprise disables {% data variables.product.prodname_GH_advanced_security %} for repository **X**. Of the 49 developers who were working on repository **X**, 10 still also work on repository **Y**, which has a total of 20 developers contributing in the last 90 days. | _49 - 29_
**20** | {% note %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md index 0839dac6333f..c16e40e049b6 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md @@ -35,7 +35,7 @@ shortTitle: 查看高级安全用法 {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} - “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) If you run out of seats, the section will be red and show "Limit exceeded." 您应该减少您对 {% data variables.product.prodname_GH_advanced_security %} 的使用，或者购买更多席位。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)”。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings showing "Limit exceeded"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) + “{% data variables.product.prodname_GH_advanced_security %}”部分显示了当前使用详情。 ![{% data variables.product.prodname_GH_advanced_security %} in enterprise licensing settings](/assets/images/help/enterprises/enterprise-licensing-tab-ghas.png) 如果您的席位用完了，该部分将为红色并显示“已超出限制”。 您应该减少您对 {% data variables.product.prodname_GH_advanced_security %} 的使用，或者购买更多席位。 更多信息请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %} 的计费](/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security#getting-the-most-out-of-github-advanced-security)”。 ![企业许可设置中的 {% data variables.product.prodname_GH_advanced_security %} 显示"超出限制"](/assets/images/help/enterprises/enterprise-licensing-tab-ghas-no-seats.png) 4. （可选）要查看每个组织的使用详情，请在左侧边栏中单击 **Billing（计费）**。 ![Billing tab in the enterprise account settings sidebar](/assets/images/help/business-accounts/settings-billing-tab.png) 在“{% data variables.product.prodname_GH_advanced_security %}”部分，您可以查看每个组织的提交者和唯一提交者数量。 ![企业计费设置中的 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/billing/ghas-orgs-list-enterprise-dotcom.png) 5. （可选）单击您是所有者的组织的名称，以显示组织的安全和分析设置。 ![在企业帐单设置的 {% data variables.product.prodname_GH_advanced_security %} 部分中拥有的组织](/assets/images/help/billing/ghas-orgs-list-enterprise-click-org.png) 6. 在“Security & analysis（安全性和分析）”设置页面上，滚动到“{% data variables.product.prodname_GH_advanced_security %} 仓库”部分以查看此组织的仓库使用明细。 ![{% data variables.product.prodname_GH_advanced_security %} repositories section](/assets/images/help/enterprises/settings-security-analysis-ghas-repos-list.png) 更多信息请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 @@ -53,7 +53,7 @@ shortTitle: 查看高级安全用法 {% ifversion ghec or ghes > 3.3 or ghae-issue-5378 %} -## Downloading {% data variables.product.prodname_GH_advanced_security %} license usage information +## 下载 {% data variables.product.prodname_GH_advanced_security %} 许可证使用信息 You can download a CSV file with {% data variables.product.prodname_GH_advanced_security %} license usage information at both the enterprise and organization levels. The CSV file contains information about each {% data variables.product.prodname_advanced_security %} seat that is in use, including: @@ -62,7 +62,7 @@ You can download a CSV file with {% data variables.product.prodname_GH_advanced_ - The organizations that people using seats belong to - The most recent commit dates -You can use this information for insights into how your {% data variables.product.prodname_advanced_security %} licenses are being used, such as which members of your enterprise are using an {% data variables.product.prodname_advanced_security %} seat or how {% data variables.product.prodname_advanced_security %} licenses are being consumed across your organizations. +您可以使用此信息深入了解 {% data variables.product.prodname_advanced_security %} 许可证的使用方式，例如企业的哪些成员正在使用 {% data variables.product.prodname_advanced_security %} 席位，或者您的组织中如何使用 {% data variables.product.prodname_advanced_security %} 许可证。 You can download the {% data variables.product.prodname_advanced_security %} license usage CSV through the {% data variables.product.product_name %} user interface or the REST API. diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md index 4403b3f7b416..8cf499449665 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md @@ -40,6 +40,12 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr {% data reusables.dotcom_billing.pricing_cal %} +### Billing for {% data variables.product.prodname_codespaces %} prebuilds + +{% data reusables.codespaces.prebuilds-beta-note %} + +{% data reusables.codespaces.billing-for-prebuilds %} + ## Setting a spending limit {% data reusables.codespaces.codespaces-spending-limit-requirement %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md index bd8c508a0d18..6fc8317bb3b7 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md +++ b/translations/zh-CN/content/billing/managing-billing-for-github-codespaces/index.md @@ -1,5 +1,5 @@ --- -title: Managing billing for GitHub Codespaces +title: 管理 GitHub Codespaces 的计费 shortTitle: Codespaces intro: '您可以查看您的使用情况，并为 {% data variables.product.prodname_codespaces %} 设置支出限额。' versions: diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md index 9dabd4a4e85b..2d0737167e0c 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md @@ -89,7 +89,7 @@ For more information about roles, see "[Roles in an enterprise](/admin/user-mana {% endif %} -## About synchronization of license usage +## 关于同步许可证使用情况 {% data reusables.enterprise.about-deployment-methods %} diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md index 14023f6a42f7..529023d98858 100644 --- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md +++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md @@ -30,7 +30,7 @@ topics: {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. Under "Payment Due", click **Pay invoice**. ![支付发票链接](/assets/images/help/business-accounts/pay-invoice-link.png) +4. 在“Payment Due（到期付款）”下，单击 **Pay invoice（支付发票）**。 ![支付发票链接](/assets/images/help/business-accounts/pay-invoice-link.png) 5. 在“Pay invoice（支付发票）”下，以安全形式输入您的信用卡信息，然后单击 **Pay Invoice（支付发票）**。 ![确认和支付发票](/assets/images/help/business-accounts/pay-invoice.png) ## 下载当前发票 @@ -45,4 +45,4 @@ topics: {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.billing-tab %} -4. To see a summary of your past billing activity, under "Billing", click the **Past Invoices** tab. ![查看付款历史记录选项卡](/assets/images/help/business-accounts/view-payment-history.png) +4. 要查看您过去的结算活动摘要，请在“Billing（帐单）”下，点击 **Past Invoices（过去的发票）**选项卡。 ![查看付款历史记录选项卡](/assets/images/help/business-accounts/view-payment-history.png) diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md index d458f4faffbd..08b52173e45c 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md @@ -23,9 +23,9 @@ When you purchase or renew {% data variables.product.prodname_enterprise %}, {% For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %} -If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. 需要时，您可以使用命令行实用程序备份所有数据。 For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %} +If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %} -如对续订许可有任何疑问，请联系 {% data variables.contact.contact_enterprise_sales %}。 +If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}. ## About synchronization of license usage for {% data variables.product.prodname_enterprise %} @@ -37,7 +37,7 @@ If your license expires, you won't be able to access {% data variables.product.p {% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %} -## 延伸阅读 +## Further reading - "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)" - [{% data variables.product.prodname_enterprise %} Releases](https://enterprise.github.com/releases/) website diff --git a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md index 5fd49571f873..3e8e79b851d3 100644 --- a/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md +++ b/translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md @@ -22,19 +22,23 @@ For more information about licenses and usage for {% data variables.product.prod ## Automatically syncing license usage -您可以使用 {% data variables.product.prodname_github_connect %} 在 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_ghe_cloud %} 之间自动同步用户许可数量和使用情况。 For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %} +You can use {% data variables.product.prodname_github_connect %} to automatically sync user license count and usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %} ## Manually syncing license usage -您可以从 {% data variables.product.prodname_ghe_server %} 下载 JSON 文件并将文件上传到 {% data variables.product.prodname_ghe_cloud %}，在两个部署之间手动同步用户许可使用情况。 +You can download a JSON file from {% data variables.product.prodname_ghe_server %} and upload the file to {% data variables.product.prodname_ghe_cloud %} to manually sync user license usage between the two deployments. {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.license-tab %} -5. 在“Quick links”下，要下载包含 {% data variables.product.prodname_ghe_server %} 上当前许可使用情况的文件，请单击 **Export license usage**。 ![Export license usage 链接](/assets/images/enterprise/business-accounts/export-license-usage-link.png) +5. Under "Quick links", to download a file containing your current license usage on {% data variables.product.prodname_ghe_server %}, click **Export license usage**. + ![Export license usage link](/assets/images/enterprise/business-accounts/export-license-usage-link.png) {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %} {% data reusables.enterprise-accounts.settings-tab %} -8. 在左侧边栏中，单击 **Enterprise licensing（企业许可）**。 ![企业帐户设置侧边栏中的"Enterprise licensing（企业许可）"选项卡](/assets/images/help/enterprises/enterprise-licensing-tab.png) +8. In the left sidebar, click **Enterprise licensing**. + !["Enterprise licensing" tab in the enterprise account settings sidebar](/assets/images/help/enterprises/enterprise-licensing-tab.png) {% data reusables.enterprise-accounts.license-tab %} -10. 在“Enterprise Server Instances（Enterprise Server 实例）”下，单击 **Add server usage（添加服务器使用情况）**。 ![Upload GitHub Enterprise Servers usage 链接](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) -11. 上传从 {% data variables.product.prodname_ghe_server %} 下载的 JSON 文件。 ![拖放或选择要上传的文件](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) +10. Under "Enterprise Server Instances", click **Add server usage**. + ![Upload GitHub Enterprise Servers usage link](/assets/images/help/business-accounts/upload-ghe-server-usage-link.png) +11. Upload the JSON file you downloaded from {% data variables.product.prodname_ghe_server %}. + ![Drag and drop or select a file to upload](/assets/images/help/business-accounts/upload-ghe-server-usage-file.png) diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md index 127300b3a82f..790697a8495b 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md @@ -45,7 +45,7 @@ topics: {% ifversion ghes or ghae %} {% note %} -**Note:** This article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) for information on the latest features.{% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} +**注意：**本文介绍了此版 {% data variables.product.product_name %} 的初始版本中包含的 CodeQL 操作版本和相关 CodeQL CLI 捆绑包中可用的功能。 If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container) for information on the latest features.{% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} {% endnote %} {% endif %} diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md index ba3abc88d4b6..e5d16e2cfdfc 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md @@ -33,15 +33,26 @@ You decide how to generate {% data variables.product.prodname_code_scanning %} a {% data reusables.code-scanning.enabling-options %} +{% ifversion ghes or ghae %} +{% note %} + +**Note:** If you want to use the CodeQL analysis, note that this article describes the features available with the version of the CodeQL action and associated CodeQL CLI bundle included in the initial release of this version of {% data variables.product.product_name %}. If your enterprise uses a more recent version of the CodeQL action, see the [{% data variables.product.prodname_ghe_cloud %} article](/enterprise-cloud@latest/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository) for information on the latest features. {% ifversion not ghae %} For information on using the latest version, see "[Configuring code scanning for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#configuring-codeql-analysis-on-a-server-without-internet-access)."{% endif %} + +{% endnote %} +{% endif %} + {% ifversion ghae %} ## Prerequisites -Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository. +Before setting up {% data variables.product.prodname_code_scanning %} for a repository, you must ensure that there is at least one self-hosted {% data variables.product.prodname_actions %} runner available to the repository. Enterprise owners, organization and repository administrators can add self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)." {% endif %} -## Setting up {% data variables.product.prodname_code_scanning %} using actions +{% ifversion fpt or ghec %} +## Setting up {% data variables.product.prodname_code_scanning %} using starter workflows + +{% data reusables.advanced-security.starter-workflows-beta %} {% ifversion ghes or ghae %} {% note %} @@ -51,13 +62,30 @@ Enterprise owners, organization and repository administrators can add self-hoste {% endnote %} {% endif %} -{% ifversion fpt or ghec %}Using actions to run {% data variables.product.prodname_code_scanning %} will use minutes. For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %} +{% data reusables.advanced-security.starter-workflow-overview %} {% data variables.product.prodname_code_scanning_capc %} starter workflows are only available for your repository if {% data variables.product.prodname_code_scanning %} is enabled. + +{% data reusables.code-scanning.billing %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.actions-tab %} +1. If the repository has already at least one workflow set up and running, click **New workflow** and go to step 5. If there are currently no workflows configured for the repository, go to the next step. + ![Screenshot of the New workflow button](/assets/images/help/security/actions-new-workflow-button.png) +1. Scroll down to the "Security" category and click **Configure** under the workflow you want to configure, or click **View all** to see all available security workflows. + ![Screenshot of the Actions workflows security section](/assets/images/help/security/actions-workflows-security-section.png) +1. On the right pane of the workflow page, click **Documentation** and follow the on-screen instructions to tailor the workflow to your needs. + ![Screenshot of the Documentation tab for starter workflows](/assets/images/help/security/actions-workflows-documentation.png) + For more information, see "[Using starter workflows](/actions/using-workflows/using-starter-workflows#using-starter-workflows)" and "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)." + +{% endif %} + +## Setting up {% data variables.product.prodname_code_scanning %} manually +{% data reusables.code-scanning.billing %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} 1. To the right of "{% data variables.product.prodname_code_scanning_capc %} alerts", click **Set up {% data variables.product.prodname_code_scanning %}**. {% ifversion fpt or ghes > 3.0 or ghae or ghec %}If {% data variables.product.prodname_code_scanning %} is missing, you need to ask an organization owner or repository administrator to enable {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)" or "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)."{% endif %} !["Set up {% data variables.product.prodname_code_scanning %}" button to the right of "{% data variables.product.prodname_code_scanning_capc %}" in the Security Overview](/assets/images/help/security/overview-set-up-code-scanning.png) -4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. +4. Under "Get started with {% data variables.product.prodname_code_scanning %}", click **Set up this workflow** on the {% data variables.product.prodname_codeql_workflow %} or on a third-party workflow. !["Set up this workflow" button under "Get started with {% data variables.product.prodname_code_scanning %}" heading](/assets/images/help/repository/code-scanning-set-up-this-workflow.png)Workflows are only displayed if they are relevant for the programming languages detected in the repository. The {% data variables.product.prodname_codeql_workflow %} is always displayed, but the "Set up this workflow" button is only enabled if {% data variables.product.prodname_codeql %} analysis supports the languages present in the repository. 5. To customize how {% data variables.product.prodname_code_scanning %} scans your code, edit the workflow. @@ -73,9 +101,9 @@ Enterprise owners, organization and repository administrators can add self-hoste In the default {% data variables.product.prodname_codeql_workflow %}, {% data variables.product.prodname_code_scanning %} is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, {% data variables.product.prodname_code_scanning %} will now commence. The `on:pull_request` and `on:push` triggers for code scanning are each useful for different purposes. For more information, see "[Scanning pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-pull-requests)" and "[Scanning on push](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#scanning-on-push)." -## Bulk set up of {% data variables.product.prodname_code_scanning %} +## Bulk set up of {% data variables.product.prodname_code_scanning %} -You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. +You can set up {% data variables.product.prodname_code_scanning %} in many repositories at once using a script. If you'd like to use a script to raise pull requests that add a {% data variables.product.prodname_actions %} workflow to multiple repositories, see the [`jhutchings1/Create-ActionsPRs`](https://github.com/jhutchings1/Create-ActionsPRs) repository for an example using PowerShell, or [`nickliffen/ghas-enablement`](https://github.com/NickLiffen/ghas-enablement) for teams who do not have PowerShell and instead would like to use NodeJS. ## Viewing the logging output from {% data variables.product.prodname_code_scanning %} @@ -122,7 +150,7 @@ When the {% data variables.product.prodname_code_scanning %} jobs complete, {% d {% ifversion fpt or ghes > 3.2 or ghae-issue-3891 or ghec %} ![Analysis not found for commit message](/assets/images/help/repository/code-scanning-analysis-not-found.png) -The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. +The table lists one or more categories. Each category relates to specific analyses, for the same tool and commit, performed on a different language or a different part of the code. For each category, the table shows the two analyses that {% data variables.product.prodname_code_scanning %} attempted to compare to determine which alerts were introduced or fixed in the pull request. For example, in the screenshot above, {% data variables.product.prodname_code_scanning %} found an analysis for the merge commit of the pull request, but no analysis for the head of the main branch. {% else %} diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md index 133eff16d35f..16ce02b33832 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: 关于 CI 系统中的 CodeQL 代码扫描 -shortTitle: CI 中的代码扫描 -intro: '您可以在第三方持续集成 系统中用 {% data variables.product.prodname_codeql %} 分析您的代码，并将结果上传到 {% data variables.product.product_location %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% data variables.product.product_name %} 内生成的任何警报一起显示。' +title: About CodeQL code scanning in your CI system +shortTitle: Code scanning in your CI +intro: 'You can analyze your code with {% data variables.product.prodname_codeql %} in a third-party continuous integration system and upload the results to {% data variables.product.product_location %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}.' product: '{% data reusables.gated-features.code-scanning %}' versions: fpt: '*' @@ -21,13 +21,12 @@ redirect_from: - /code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system - /code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system --- - {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -## 关于 CI 系统中的 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} +## About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." @@ -40,17 +39,17 @@ redirect_from: {% data reusables.code-scanning.upload-sarif-ghas %} -## 关于 {% data variables.product.prodname_codeql_cli %} +## About the {% data variables.product.prodname_codeql_cli %} {% data reusables.code-scanning.what-is-codeql-cli %} -使用 {% data variables.product.prodname_codeql_cli %} 分析： +Use the {% data variables.product.prodname_codeql_cli %} to analyze: -- 动态语言，例如 JavaScript 和 Python。 -- 编译的语言，例如 C/C++、C# 和 Java。 -- 以多种语言编写的代码库。 +- Dynamic languages, for example, JavaScript and Python. +- Compiled languages, for example, C/C++, C# and Java. +- Codebases written in a mixture of languages. -更多信息请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”。 +For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." {% data reusables.code-scanning.licensing-note %} @@ -67,24 +66,24 @@ Since version 2.6.3, the {% data variables.product.prodname_codeql_cli %} has ha {% ifversion ghes < 3.2 %} -将 {% data variables.product.prodname_codeql_cli %} 或 {% data variables.product.prodname_codeql_runner %} 添加到第三方系统，然后调用工具分析代码并将 SARIF 结果上传到 {% data variables.product.product_name %}。 由此产生的 {% data variables.product.prodname_code_scanning %} 警报与 {% data variables.product.product_name %} 内生成的任何警报一起显示。 +You add the {% data variables.product.prodname_codeql_cli %} or the {% data variables.product.prodname_codeql_runner %} to your third-party system, then call the tool to analyze code and upload the SARIF results to {% data variables.product.product_name %}. The resulting {% data variables.product.prodname_code_scanning %} alerts are shown alongside any alerts generated within {% data variables.product.product_name %}. [{% data variables.product.prodname_codeql_cli %}](https://github.com/github/codeql-cli-binaries/releases) version 2.6.3 is available now for {% data variables.product.prodname_ghe_server %} 3.0 and later versions. For more information on migrating to the {% data variables.product.prodname_codeql_cli %}, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." {% data reusables.code-scanning.upload-sarif-ghas %} -## 比较 {% data variables.product.prodname_codeql_cli %}与 {% data variables.product.prodname_codeql_runner %} +## Comparing {% data variables.product.prodname_codeql_cli %} and {% data variables.product.prodname_codeql_runner %} {% data reusables.code-scanning.what-is-codeql-cli %} -The {% data variables.product.prodname_codeql_runner %} is a deprecated command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. 该工具使用操作在 {% data variables.product.product_name %} 内本地模拟分析运行。 +The {% data variables.product.prodname_codeql_runner %} is a deprecated command-line tool that uses the {% data variables.product.prodname_codeql_cli %} to analyze code and upload the results to {% data variables.product.product_name %}. The tool mimics the analysis run natively within {% data variables.product.product_name %} using actions. -{% data variables.product.prodname_codeql_cli %} 2.6.3 is a complete replacement for the runner with full feature parity. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly. +{% data variables.product.prodname_codeql_cli %} 2.6.3 is a complete replacement for the runner with full feature parity. Generally, it is better to use the {% data variables.product.prodname_codeql_cli %} directly. -更多信息请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”。 +For more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)." {% data reusables.code-scanning.deprecation-codeql-runner %} -有关 {% data variables.product.prodname_codeql_runner %} 的更多信息，请参阅“[在 CI 系统中运行 {% data variables.product.prodname_codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”。 +For more information about the {% data variables.product.prodname_codeql_runner %}, see "[Running {% data variables.product.prodname_codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)." -{% endif %} +{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md index 16d884751c27..26a343456460 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md @@ -223,7 +223,7 @@ When you have decided on the most secure and reliable method for your CI server, | Option | Required | Usage | |--------|:--------:|-----| | `--repository` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the *OWNER/NAME* of the repository to upload data to. The owner must be an organization within an enterprise that has a license for {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_GH_advanced_security %} must be enabled for the repository{% ifversion fpt or ghec %}, unless the repository is public{% endif %}. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)." -| `--ref` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pulls/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pulls/NUMBER/merge`. +| `--ref` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the name of the `ref` you checked out and analyzed so that the results can be matched to the correct code. For a branch use: `refs/heads/BRANCH-NAME`, for the head commit of a pull request use `refs/pull/NUMBER/head`, or for the {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request use `refs/pull/NUMBER/merge`. | `--commit` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the full SHA of the commit you analyzed. | `--sarif` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the SARIF file to load.{% ifversion ghes > 3.0 or ghae %} | `--github-url` | {% octicon "check-circle-fill" aria-label="Required" %} | Specify the URL for {% data variables.product.product_name %}.{% endif %} diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md index dec948d833f8..24269ff515c3 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md @@ -52,7 +52,7 @@ These examples also assume that the {% data variables.product.prodname_codeql_cl In these examples, a {% data variables.product.prodname_dotcom %} token with suitable scopes is stored in the `$TOKEN` environment variable and passed to the example commands via `stdin`, or is stored in the `$GITHUB_TOKEN` environment variable. -The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pulls/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pulls/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. +The ref name and commit SHA being checked out and analyzed in these examples are known during the workflow. For a branch, use `refs/heads/BRANCH-NAME` as the ref. For the head commit of a pull request, use `refs/pull/NUMBER/head`. For a {% data variables.product.prodname_dotcom %}-generated merge commit of a pull request, use `refs/pull/NUMBER/merge`. The examples below all use `refs/heads/main`. If you use a different branch name, you must modify the sample code. ### Single non-compiled language (JavaScript) diff --git a/translations/zh-CN/content/code-security/guides.md b/translations/zh-CN/content/code-security/guides.md index 8a7328064919..9ef016eb5a45 100644 --- a/translations/zh-CN/content/code-security/guides.md +++ b/translations/zh-CN/content/code-security/guides.md @@ -47,16 +47,16 @@ includeGuides: - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - - /code-security/security-advisories/about-github-security-advisories - - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory - - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /code-security/security-advisories/creating-a-security-advisory - - /code-security/security-advisories/editing-a-security-advisory - - /code-security/security-advisories/permission-levels-for-security-advisories - - /code-security/security-advisories/publishing-a-security-advisory - - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory - - /code-security/security-advisories/withdrawing-a-security-advisory + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/about-github-security-advisories-for-repositories + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /code-security/repository-security-advisories/creating-a-repository-security-advisory + - /code-security/repository-security-advisories/editing-a-repository-security-advisory + - /code-security/repository-security-advisories/permission-levels-for-repository-security-advisories + - /code-security/repository-security-advisories/publishing-a-repository-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory - /code-security/security-overview/about-the-security-overview - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/automating-dependabot-with-github-actions @@ -72,6 +72,7 @@ includeGuides: - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-managing-vulnerable-dependencies - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database + - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-dependabot-errors diff --git a/translations/zh-CN/content/code-security/index.md b/translations/zh-CN/content/code-security/index.md index 49b26a908f4a..e6128a1dfb9e 100644 --- a/translations/zh-CN/content/code-security/index.md +++ b/translations/zh-CN/content/code-security/index.md @@ -8,7 +8,7 @@ featuredLinks: guides: - /code-security/getting-started/securing-your-repository - /code-security/getting-started/securing-your-organization - - '{% ifversion fpt %}/code-security/security-advisories/creating-a-security-advisory{% endif %}' + - '{% ifversion fpt %}/code-security/repository-security-advisories/creating-a-repository-security-advisory{% endif %}' - '{% ifversion ghes or ghae %}/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository{% endif%}' guideCards: - '{% ifversion fpt %}/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates{% endif %}' @@ -22,7 +22,7 @@ featuredLinks: popular: - '{% ifversion ghes %}/admin/release-notes{% endif %}' - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/keeping-your-actions-up-to-date-with-dependabot - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates - /code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot @@ -51,7 +51,7 @@ children: - /getting-started - /secret-scanning - /code-scanning - - /security-advisories + - /repository-security-advisories - /supply-chain-security - /security-overview - /guides diff --git a/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md b/translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md similarity index 92% rename from translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md rename to translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md index 468b0dae996c..1351bfe84204 100644 --- a/translations/zh-CN/content/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md @@ -1,6 +1,8 @@ --- title: 关于安全漏洞的协调披露 intro: 漏洞披露是安全报告者与仓库维护者之间的协调工作。 +redirect_from: + - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -63,7 +65,7 @@ shortTitle: 协调披露 如果您是维护者， 您可以在管道开始时通过为您的仓库设置安全策略来掌控这一过程，或者以其他方式使安全报告说明清楚可用，例如在项目的 README 文件中。 有关添加安全策略的更多信息，请参阅“[关于安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository#about-security-policies)”。 如果没有安全策略，漏洞报告者可能会尝试向您发送电子邮件或以其他方式私下与您联系。 或者，有人可能会开一个（公共）议题讨论安全问题的细节。 - 作为维护者，要在您的代码中披露漏洞，请先在 {% data variables.product.prodname_dotcom %} 中软件包的仓库内创建安全通告。 {% data reusables.security-advisory.security-advisory-overview %} 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 + 作为维护者，要在您的代码中披露漏洞，请先在 {% data variables.product.prodname_dotcom %} 中软件包的仓库内创建安全通告。 {% data reusables.security-advisory.security-advisory-overview %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)." - 要开始，请参阅“[创建安全通告](/github/managing-security-vulnerabilities/creating-a-security-advisory)”。 + To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." diff --git a/translations/zh-CN/content/code-security/security-advisories/about-github-security-advisories.md b/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md similarity index 62% rename from translations/zh-CN/content/code-security/security-advisories/about-github-security-advisories.md rename to translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md index 15910663bc99..242aa6b9895b 100644 --- a/translations/zh-CN/content/code-security/security-advisories/about-github-security-advisories.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md @@ -1,10 +1,11 @@ --- -title: 关于 GitHub Security Advisories +title: About GitHub Security Advisories for repositories intro: '您可以使用 {% data variables.product.prodname_security_advisories %} 来私下讨论、修复和发布有关仓库中安全漏洞的信息。' redirect_from: - /articles/about-maintainer-security-advisories - /github/managing-security-vulnerabilities/about-maintainer-security-advisories - /github/managing-security-vulnerabilities/about-github-security-advisories + - /code-security/security-advisories/about-github-security-advisories versions: fpt: '*' ghec: '*' @@ -13,7 +14,7 @@ topics: - Security advisories - Vulnerabilities - CVEs -shortTitle: 安全通告 +shortTitle: Repository security advisories --- {% data reusables.repositories.security-advisory-admin-permissions %} @@ -22,23 +23,25 @@ shortTitle: 安全通告 ## 关于 {% data variables.product.prodname_security_advisories %} -{% data reusables.security-advisory.disclosing-vulnerabilities %} 更多信息请参阅“[关于协调披露安全漏洞](/code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)”。 +{% data reusables.security-advisory.disclosing-vulnerabilities %} 更多信息请参阅“[关于协调披露安全漏洞](/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities)”。 {% data reusables.security-advisory.security-advisory-overview %} 通过 {% data variables.product.prodname_security_advisories %}，您可以： -1. 创建安全通告草稿，并使用草稿私下讨论漏洞对项目的影响。 更多信息请参阅“[创建安全通告](/github/managing-security-vulnerabilities/creating-a-security-advisory)”。 +1. 创建安全通告草稿，并使用草稿私下讨论漏洞对项目的影响。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." 2. 在临时私有复刻中私下协作以修复漏洞。 -3. 在补丁发布后发布通告向社区提醒漏洞。 更多信息请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)”。 +3. 在补丁发布后发布通告向社区提醒漏洞。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." {% data reusables.repositories.security-advisories-republishing %} -您可以向为安全通告做出贡献的个人提供积分。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)”。 +您可以向为安全通告做出贡献的个人提供积分。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)." {% data reusables.repositories.security-guidelines %} -如果您在仓库中创建了安全通告，安全通告将保留在您的仓库中。 我们在 [github.com/advantores](https://github.com/advisories) 上的 {% data variables.product.prodname_advisory_database %} 发布任何由依赖关系图支持的生态系统的安全通告。 如果安全通告是专门针对 npm 的，我们也会向 npm 安全通告发布该通告。 更多信息请参阅 [npmjs.com/advisories](https://www.npmjs.com/advisories)。 +如果您在仓库中创建了安全通告，安全通告将保留在您的仓库中。 我们在 [github.com/advantores](https://github.com/advisories) 上的 {% data variables.product.prodname_advisory_database %} 发布任何由依赖关系图支持的生态系统的安全通告。 Anyone can submit a change to an advisory published 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)." + +如果安全通告是专门针对 npm 的，我们也会向 npm 安全通告发布该通告。 更多信息请参阅 [npmjs.com/advisories](https://www.npmjs.com/advisories)。 {% data reusables.repositories.github-security-lab %} @@ -50,7 +53,7 @@ shortTitle: 安全通告 在 {% data variables.product.prodname_dotcom %} 上为公共仓库创建安全通告时，您可以选择为安全漏洞提供现有的 CVE 标识号。 {% data reusables.repositories.request-security-advisory-cve-id %} -在您发布了安全通告并且 {% data variables.product.prodname_dotcom %} 为漏洞分配 CVE 标识号后，{% data variables.product.prodname_dotcom %} 会将 CVE 发布到 MITRE 数据库。 更多信息请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory#requesting-a-cve-identification-number)”。 +在您发布了安全通告并且 {% data variables.product.prodname_dotcom %} 为漏洞分配 CVE 标识号后，{% data variables.product.prodname_dotcom %} 会将 CVE 发布到 MITRE 数据库。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." ## 对于发布的安全通告的 {% data variables.product.prodname_dependabot_alerts %} diff --git a/translations/zh-CN/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md similarity index 50% rename from translations/zh-CN/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md rename to translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md index 7abf246e5500..53699debf572 100644 --- a/translations/zh-CN/content/code-security/security-advisories/adding-a-collaborator-to-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: 添加协作者到安全通告 +title: Adding a collaborator to a repository security advisory intro: 您可以添加其他用户或团队与您协作处理安全通告。 redirect_from: - /articles/adding-a-collaborator-to-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory + - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory versions: fpt: '*' ghec: '*' @@ -13,18 +14,20 @@ topics: - Security advisories - Vulnerabilities - Collaboration -shortTitle: 向通告添加协作者 +shortTitle: Add collaborators --- 对安全通告具有管理员权限的人员可向安全通告添加协作者。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 添加协作者到安全通告 -协作者对安全通告具有写入权限。 更多信息请参阅“[安全通告的权限级别](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)”。 +协作者对安全通告具有写入权限。 For more information, see "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)." {% note %} -{% data reusables.repositories.security-advisory-collaborators-public-repositories %} 有关删除安全通告协作者的更多信息，请参阅“[从安全通告删除协作者](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)”。 +{% data reusables.repositories.security-advisory-collaborators-public-repositories %} For more information about removing a collaborator on a security advisory, see "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)." {% endnote %} @@ -37,6 +40,6 @@ shortTitle: 向通告添加协作者 ## 延伸阅读 -- "[安全通告的权限级别](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[在临时私有复刻中协作以解决安全漏洞](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" -- "[从安全通告删除协作者](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)." diff --git a/translations/zh-CN/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md b/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md similarity index 81% rename from translations/zh-CN/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md rename to translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md index 94d48abdcc57..7eead2503e08 100644 --- a/translations/zh-CN/content/code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md @@ -1,9 +1,10 @@ --- -title: 在临时私有复刻中协作以解决安全漏洞 +title: Collaborating in a temporary private fork to resolve a repository security vulnerability intro: 您可以创建临时私有复刻，以私下协作修复仓库中的安全漏洞。 redirect_from: - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - /github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability + - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability versions: fpt: '*' ghec: '*' @@ -16,9 +17,11 @@ topics: shortTitle: 临时私有复刻 --- +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 基本要求 -在临时私有复刻中进行协作之前，必须创建维护员通告草稿。 更多信息请参阅“[创建安全通告](/github/managing-security-vulnerabilities/creating-a-security-advisory)”。 +在临时私有复刻中进行协作之前，必须创建维护员通告草稿。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." ## 创建临时私有复刻 @@ -34,7 +37,7 @@ shortTitle: 临时私有复刻 ## 将协作者添加到临时私有复刻 -对安全通告具有管理员权限的任何人都可以向安全通告添加其他协作者，而安全通告的协作者可以访问临时私有复刻。 更多信息请参阅“[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)”。 +对安全通告具有管理员权限的任何人都可以向安全通告添加其他协作者，而安全通告的协作者可以访问临时私有复刻。 For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." ## 将更改添加到临时私有复刻 @@ -76,9 +79,9 @@ shortTitle: 临时私有复刻 4. 在“Security Advisories（安全通告）”列表中，单击要合并其更改的安全通告。 ![列表中的安全通告](/assets/images/help/security/security-advisory-in-list.png) 5. 要合并临时私有复刻中所有打开的拉取请求，请单击 **Merge pull requests（合并拉取请求）**。 ![合并拉取请求按钮](/assets/images/help/security/merge-pull-requests-button.png) -合并安全通告中的更改后，您可以发布安全通告，以提醒您的社区有关项目早期版本中安全漏洞的信息。 更多信息请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)”。 +合并安全通告中的更改后，您可以发布安全通告，以提醒您的社区有关项目早期版本中安全漏洞的信息。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." ## 延伸阅读 -- "[安全通告的权限级别](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)" +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/security-advisories/creating-a-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md similarity index 58% rename from translations/zh-CN/content/code-security/security-advisories/creating-a-security-advisory.md rename to translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md index d99e645cf125..86c3793c4fda 100644 --- a/translations/zh-CN/content/code-security/security-advisories/creating-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: 创建安全通告 +title: Creating a repository security advisory intro: 您可以创建安全通告草稿，以私下讨论和修复开源项目中的安全漏洞。 redirect_from: - /articles/creating-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/creating-a-security-advisory + - /code-security/security-advisories/creating-a-security-advisory versions: fpt: '*' ghec: '*' @@ -12,7 +13,7 @@ type: how_to topics: - Security advisories - Vulnerabilities -shortTitle: 创建咨询意见 +shortTitle: Create repository advisories --- 任何对仓库有管理员权限的人都可以创建安全通告。 @@ -35,7 +36,7 @@ shortTitle: 创建咨询意见 ## 后续步骤 - 评论安全通告草稿，与团队讨论漏洞。 -- 添加协作者到安全通告。 更多信息请参阅“[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-maintainer-security-advisory)”。 -- 在临时私有复刻中私下协作以修复漏洞。 更多信息请参阅“[在临时私有复刻中协作以解决安全漏洞](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”。 -- 添加因对安全通告做出贡献而应获得积分的个人。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)”。 -- 发布安全通告以向社区提醒安全漏洞。 更多信息请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)”。 +- 添加协作者到安全通告。 For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." +- 在临时私有复刻中私下协作以修复漏洞。 For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)." +- 添加因对安全通告做出贡献而应获得积分的个人。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)." +- 发布安全通告以向社区提醒安全漏洞。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)." diff --git a/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md similarity index 77% rename from translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md rename to translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md index 4f7d902c0641..2964182bf788 100644 --- a/translations/zh-CN/content/code-security/security-advisories/editing-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md @@ -1,8 +1,9 @@ --- -title: 编辑安全通告 -intro: 如果需要更新详细信息或更正错误，可以编辑安全通告的元数据和说明。 +title: Editing a repository security advisory +intro: You can edit the metadata and description for a repository security advisory if you need to update details or correct errors. redirect_from: - /github/managing-security-vulnerabilities/editing-a-security-advisory + - /code-security/security-advisories/editing-a-security-advisory versions: fpt: '*' ghec: '*' @@ -10,10 +11,12 @@ type: how_to topics: - Security advisories - Vulnerabilities -shortTitle: 编辑建议 +shortTitle: Edit repository advisories --- -对安全通告具有管理员权限的人员可以编辑安全通告。 +People with admin permissions to a repository security advisory can edit the security advisory. + +{% data reusables.security-advisory.repository-level-advisory-note %} ## 关于安全通告的积分 @@ -40,4 +43,4 @@ shortTitle: 编辑建议 ## 延伸阅读 -- "[撤销安全通告](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/index.md b/translations/zh-CN/content/code-security/repository-security-advisories/index.md new file mode 100644 index 000000000000..58bf1aeb1468 --- /dev/null +++ b/translations/zh-CN/content/code-security/repository-security-advisories/index.md @@ -0,0 +1,29 @@ +--- +title: Managing repository security advisories for vulnerabilities in your project +shortTitle: Repository security advisories +intro: 'Discuss, fix, and disclose security vulnerabilities in your repositories using repository security advisories.' +redirect_from: + - /articles/managing-security-vulnerabilities-in-your-project + - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project + - /code-security/security-advisories +versions: + fpt: '*' + ghec: '*' +topics: + - Security advisories + - Vulnerabilities + - Repositories + - CVEs +children: + - /about-coordinated-disclosure-of-security-vulnerabilities + - /about-github-security-advisories-for-repositories + - /permission-levels-for-repository-security-advisories + - /creating-a-repository-security-advisory + - /adding-a-collaborator-to-a-repository-security-advisory + - /removing-a-collaborator-from-a-repository-security-advisory + - /collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /publishing-a-repository-security-advisory + - /editing-a-repository-security-advisory + - /withdrawing-a-repository-security-advisory +--- + diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md b/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md new file mode 100644 index 000000000000..87f8778d09cd --- /dev/null +++ b/translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md @@ -0,0 +1,45 @@ +--- +title: Permission levels for repository security advisories +intro: The actions you can take in a repository security advisory depend on whether you have admin or write permissions to the security advisory. +redirect_from: + - /articles/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories + - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories + - /code-security/security-advisories/permission-levels-for-security-advisories +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Security advisories + - Vulnerabilities + - Permissions +shortTitle: 权限级别 +--- + +This article applies only to repository-level security advisories. Anyone can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. 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 reusables.repositories.security-advisory-admin-permissions %} For more information about adding a collaborator to a security advisory, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)." + +| 操作 | 写入权限 | 管理员权限 | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ----- | +| 查看安全通告草稿 | X | X | +| Add collaborators to the security advisory (see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)") | | X | +| 编辑和删除安全通告中的任何评论 | X | X | +| Create a temporary private fork in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +| Add changes to a temporary private fork in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +| Create pull requests in a temporary private fork (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | X | X | +| Merge changes in the security advisory (see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)") | | X | +| Add and edit metadata in the security advisory (see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | X | X | +| Add and remove credits for a security advisory (see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)") | X | X | +| 关闭安全通告草稿 | | X | +| Publish the security advisory (see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)") | | X | + +## 延伸阅读 + +- "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" +- "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)" +- "[Removing a collaborator from a repository security advisory](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)" +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md similarity index 75% rename from translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md rename to translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md index a58e9e02414c..a2f32349e88b 100644 --- a/translations/zh-CN/content/code-security/security-advisories/publishing-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md @@ -1,10 +1,11 @@ --- -title: 发布安全通告 +title: Publishing a repository security advisory intro: 您可以发布安全通告，向社区提醒项目中的安全漏洞。 redirect_from: - /articles/publishing-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/publishing-a-maintainer-security-advisory - /github/managing-security-vulnerabilities/publishing-a-security-advisory + - /code-security/security-advisories/publishing-a-security-advisory versions: fpt: '*' ghec: '*' @@ -14,18 +15,20 @@ topics: - Vulnerabilities - CVEs - Repositories -shortTitle: 发布咨询意见 +shortTitle: Publish repository advisories --- 对安全通告具有管理员权限的任何人都可发布安全通告。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 基本要求 -在发布安全通告或申请 CVE 标识号之前，必须创建安全通告草稿，并提供受安全漏洞影响的项目版本的相关信息。 更多信息请参阅“[创建安全通告](/github/managing-security-vulnerabilities/creating-a-security-advisory)”。 +在发布安全通告或申请 CVE 标识号之前，必须创建安全通告草稿，并提供受安全漏洞影响的项目版本的相关信息。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)." -如果您已创建安全通告，但尚未提供有关安全漏洞影响的项目版本的详细信息，则可以编辑安全通告。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 +如果您已创建安全通告，但尚未提供有关安全漏洞影响的项目版本的详细信息，则可以编辑安全通告。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." ## 关于发布安全通告 @@ -33,7 +36,7 @@ shortTitle: 发布咨询意见 {% data reusables.repositories.security-advisories-republishing %} -在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 更多信息请参阅“[在临时私有复刻中协作以解决安全漏洞](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”。 +在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)." {% warning %} @@ -60,7 +63,7 @@ shortTitle: 发布咨询意见 发布安全通告后，安全通告的 URL 将与发布安全通告之前保持相同。 对仓库具有读取权限的任何人都能看到安全通告。 安全通告的协作者可以继续查看安全通告中过去的对话，包括完整的评论流，除非有管理员权限的人从安全通告删除该协作者。 -如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 +如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)." ## 发布安全通告 @@ -78,7 +81,7 @@ shortTitle: 发布咨询意见 ## 申请 CVE 识别号（可选） -{% data reusables.repositories.request-security-advisory-cve-id %} 更多信息请参阅“[关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories#cve-identification-numbers)”。 +{% data reusables.repositories.request-security-advisory-cve-id %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories#cve-identification-numbers)." {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} @@ -89,4 +92,4 @@ shortTitle: 发布咨询意见 ## 延伸阅读 -- "[撤销安全通告](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" +- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md similarity index 63% rename from translations/zh-CN/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md rename to translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md index e4a89567094a..54c63043ee79 100644 --- a/translations/zh-CN/content/code-security/security-advisories/removing-a-collaborator-from-a-security-advisory.md +++ b/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md @@ -1,8 +1,9 @@ --- -title: 从安全通告删除协作者 -intro: 协作者从安全通告中删除后，将失去对安全通告的讨论和元数据的读取和写入权限。 +title: Removing a collaborator from a repository security advisory +intro: 'When you remove a collaborator from a repository security advisory, they lose read and write access to the security advisory''s discussion and metadata.' redirect_from: - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory + - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory versions: fpt: '*' ghec: '*' @@ -16,6 +17,8 @@ shortTitle: 删除协作者 对安全通告具有管理员权限的人员可从安全通告删除协作者。 +{% data reusables.security-advisory.repository-level-advisory-note %} + ## 从安全通告删除协作者 {% data reusables.repositories.security-advisory-collaborators-public-repositories %} @@ -29,5 +32,5 @@ shortTitle: 删除协作者 ## 延伸阅读 -- "[安全通告的权限级别](/github/managing-security-vulnerabilities/permission-levels-for-security-advisories)" -- "[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" +- "[Permission levels for repository security advisories](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)" +- "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md new file mode 100644 index 000000000000..c959b4f03a7c --- /dev/null +++ b/translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md @@ -0,0 +1,23 @@ +--- +title: Withdrawing a repository security advisory +intro: You can withdraw a repository security advisory that you've published. +redirect_from: + - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory + - /code-security/security-advisories/withdrawing-a-security-advisory +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Vulnerabilities +shortTitle: Withdraw repository advisories +--- + +{% data reusables.security-advisory.repository-level-advisory-note %} + +如果错误地发布了安全通告，可以联系 {% data variables.contact.contact_support %} 撤销。 + +## 延伸阅读 + +- "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)" diff --git a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md index 0061ea369a6a..f1fa4f176299 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-secret-scanning.md @@ -41,7 +41,7 @@ shortTitle: 管理秘密警报 {% ifversion ghae %} ![来自密码扫描的警报](/assets/images/enterprise/github-ae/repository/secret-scanning-click-alert-ghae.png) {% endif %} -1. Optionally, select the {% ifversion fpt or ghec %}"Close as"{% elsif ghes or ghae %}"Mark as"{% endif %} drop-down menu and click a reason for resolving an alert. +1. （可选）选择 {% ifversion fpt or ghec %}“Close as（关闭为）”{% elsif ghes or ghae %}“Mark as（标记为）”{% endif %} 下拉菜单，然后单击原因以解决警报。 {% ifversion fpt or ghec %} ![用于解决来自密码扫描的警报的下拉菜单](/assets/images/help/repository/secret-scanning-resolve-alert.png) {% endif %} @@ -59,7 +59,7 @@ shortTitle: 管理秘密警报 {% ifversion fpt or ghes > 3.1 or ghae-issue-4910 or ghec %} ## 配置 {% data variables.product.prodname_secret_scanning %} 警报的通知 -当检测到新的机密时，{% data variables.product.product_name %} 会根据用户的通知首选项通知对仓库安全警报具有访问权限的所有用户。 You will receive alerts if you are watching the repository, have enabled notifications for security alerts or for all the activity on the repository, are the author of the commit that contains the secret and are not ignoring the repository. +当检测到新的机密时，{% data variables.product.product_name %} 会根据用户的通知首选项通知对仓库安全警报具有访问权限的所有用户。 如果您正在关注该仓库，已为仓库的安全警报或所有活动启用通知功能， 或者您是包含机密的提交的作者且未忽略该仓库，您将会收到警报。 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”和“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。 {% endif %} diff --git a/translations/zh-CN/content/code-security/security-advisories/index.md b/translations/zh-CN/content/code-security/security-advisories/index.md deleted file mode 100644 index 770cdd6d2e34..000000000000 --- a/translations/zh-CN/content/code-security/security-advisories/index.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -title: 管理项目中的漏洞安全通告 -shortTitle: 安全通告 -intro: 使用安全通告讨论、修正和披露您仓库中的安全漏洞。 -redirect_from: - - /articles/managing-security-vulnerabilities-in-your-project - - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project -versions: - fpt: '*' - ghec: '*' -topics: - - Security advisories - - Vulnerabilities - - Repositories - - CVEs -children: - - /about-coordinated-disclosure-of-security-vulnerabilities - - /about-github-security-advisories - - /permission-levels-for-security-advisories - - /creating-a-security-advisory - - /adding-a-collaborator-to-a-security-advisory - - /removing-a-collaborator-from-a-security-advisory - - /collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /publishing-a-security-advisory - - /editing-a-security-advisory - - /withdrawing-a-security-advisory ---- - diff --git a/translations/zh-CN/content/code-security/security-advisories/permission-levels-for-security-advisories.md b/translations/zh-CN/content/code-security/security-advisories/permission-levels-for-security-advisories.md deleted file mode 100644 index 9728101ebf26..000000000000 --- a/translations/zh-CN/content/code-security/security-advisories/permission-levels-for-security-advisories.md +++ /dev/null @@ -1,42 +0,0 @@ ---- -title: 安全通告的权限级别 -intro: 您在安全通告中可以执行的操作取决于您是公告的管理员还是对其有写入权限。 -redirect_from: - - /articles/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories - - /github/managing-security-vulnerabilities/permission-levels-for-security-advisories -versions: - fpt: '*' - ghec: '*' -type: reference -topics: - - Security advisories - - Vulnerabilities - - Permissions -shortTitle: 权限级别 ---- - -## 权限概述 - -{% data reusables.repositories.security-advisory-admin-permissions %} 有关添加协作者到安全通告的更多信息，请参阅“[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)”。 - -| 操作 | 写入权限 | 管理员权限 | -| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ----- | -| 查看安全通告草稿 | X | X | -| 添加协作者到安全通告（请参阅“[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)”） | | X | -| 编辑和删除安全通告中的任何评论 | X | X | -| 在安全通告中创建临时私有复刻（请参阅“[在临时私有复刻中协作以解决安全漏洞](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”） | | X | -| 添加更改到安全通告中的临时私有复刻（请参阅“[在临时私有复刻中协作以解决安全漏洞](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”） | X | X | -| 在临时私有复刻中创建拉取请求（请参阅“[在临时私有复刻中协作以解决安全漏洞](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”） | X | X | -| 合并安全通告中的更改（请参阅“[在临时私有复刻中协作以解决安全漏洞](/articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)”） | | X | -| 在安全通告中添加和编辑元数据（请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)”） | X | X | -| 添加和删除安全通告的积分（请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory#about-credits-for-security-advisories)”） | X | X | -| 关闭安全通告草稿 | | X | -| 发布安全通告（请参阅“[发布安全通告](/github/managing-security-vulnerabilities/publishing-a-security-advisory)”） | | X | - -## 延伸阅读 - -- "[添加协作者到安全通告](/github/managing-security-vulnerabilities/adding-a-collaborator-to-a-security-advisory)" -- "[在临时私有复刻中协作以解决安全漏洞](/github/managing-security-vulnerabilities/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability)" -- "[从安全通告删除协作者](/github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory)" -- "[撤销安全通告](/github/managing-security-vulnerabilities/withdrawing-a-security-advisory)" diff --git a/translations/zh-CN/content/code-security/security-advisories/withdrawing-a-security-advisory.md b/translations/zh-CN/content/code-security/security-advisories/withdrawing-a-security-advisory.md deleted file mode 100644 index cc1d0dc4572c..000000000000 --- a/translations/zh-CN/content/code-security/security-advisories/withdrawing-a-security-advisory.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: 撤销安全通告 -intro: 您可以撤销已发布的安全通告。 -redirect_from: - - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Security advisories - - Vulnerabilities -shortTitle: 撤销咨询意见 ---- - -如果错误地发布了安全通告，可以联系 {% data variables.contact.contact_support %} 撤销。 - -## 延伸阅读 - -- [编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory) diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md index ce774b3d75bc..635a4f5ccecd 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -75,6 +75,9 @@ The database is also accessible using the GraphQL API. For more information, see {% endnote %} +## 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)." + ## 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. diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md new file mode 100644 index 000000000000..09844722d3df --- /dev/null +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database.md @@ -0,0 +1,32 @@ +--- +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 +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Security advisories + - Alerts + - Dependabot + - Vulnerabilities + - CVEs +shortTitle: Edit 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. + +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)." +## Editing advisories in the GitHub Advisory Database + +1. 导航到 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. ![Suggest improvements link](/assets/images/help/security/suggest-improvements-to-advisory.png) +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. + +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). diff --git a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md index 067cab1c4a7c..a86e842f2d82 100644 --- a/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md +++ b/translations/zh-CN/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/index.md @@ -23,6 +23,7 @@ topics: children: - /about-managing-vulnerable-dependencies - /browsing-security-vulnerabilities-in-the-github-advisory-database + - /editing-security-advisories-in-the-github-advisory-database - /about-alerts-for-vulnerable-dependencies - /configuring-notifications-for-vulnerable-dependencies - /about-dependabot-security-updates diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md index 92133bebcfdd..1f249b74f5eb 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md @@ -30,6 +30,8 @@ shortTitle: 了解计费 代码空间将根据其计算分钟数及其在磁盘上使用的存储量付费。 +If you enable prebuilding of codespaces this will incur additional charges. For more information, see "[About Codespaces prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + ### 了解什么是计算分钟数 代码空间按其处于活动状态的分钟数计费。 如果代码空间窗口空闲 30 分钟，它将自动关闭，并且代码空间的计算计费将结束，直到您再次启动代码空间。 diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md index 27710a5ad8b4..ad7169107395 100644 --- a/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md +++ b/translations/zh-CN/content/codespaces/customizing-your-codespace/index.md @@ -15,6 +15,5 @@ children: - /setting-your-default-editor-for-codespaces - /setting-your-default-region-for-codespaces - /setting-your-timeout-period-for-codespaces - - /prebuilding-codespaces-for-your-project --- diff --git a/translations/zh-CN/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md b/translations/zh-CN/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md deleted file mode 100644 index 0351991d3e1e..000000000000 --- a/translations/zh-CN/content/codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -title: Prebuilding Codespaces for your project -intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. -versions: - fpt: '*' - ghec: '*' -type: how_to -topics: - - Codespaces - - Set up - - Fundamentals -product: '{% data reusables.gated-features.codespaces %}' -shortTitle: Prebuild Codespaces ---- - -{% note %} - -**Note:** This feature is currently in private preview. - -{% endnote %} - -## About prebuilding a Codespace - -Prebuilding your codespaces allows you to be more productive and access your codespace faster. This is because any source code, editor extensions, project dependencies, commands, or configurations have already been downloaded, installed, and applied before you begin your coding session. Once you push changes to your repository, {% data variables.product.prodname_codespaces %} automatically handles configuring the builds. - -The ability to prebuild Codespaces is currently in private preview. To get access to this feature, contact codespaces@github.com. diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md index 3e7898fffcd8..3d469638d781 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md @@ -1,5 +1,5 @@ --- -title: Codespaces lifecycle +title: 代码空间生命周期 intro: 'You can develop in a {% data variables.product.prodname_codespaces %} environment and maintain your data throughout the entire codespace lifecycle.' versions: fpt: '*' @@ -23,6 +23,8 @@ If you choose to create a new codespace each time you work on a project, you sho If you choose to use a long-running codespace for your project, you should pull from your repository's default branch each time you start working in your codespace so that your environment has the latest commits. This workflow is very similar to if you were working with a project on your local machine. +{% data reusables.codespaces.prebuilds-crossreference %} + ## Saving changes in a codespace When you connect to a codespace through the web, auto-save is enabled automatically for the web editor and configured to save changes after a delay. When you connect to a codespace through {% data variables.product.prodname_vscode %} running on your desktop, you must enable auto-save. For more information, see [Save/Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save) in the {% data variables.product.prodname_vscode %} documentation. diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 79639b7257e0..9ee02aab1266 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -41,6 +41,8 @@ shortTitle: Create a codespace {% data reusables.codespaces.you-can-see-all-your-codespaces %} +{% data reusables.codespaces.prebuilds-crossreference %} + ## 访问 {% data variables.product.prodname_codespaces %} {% data reusables.codespaces.availability %} diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 39fcdc5b5a2c..3199aa52829a 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -61,4 +61,4 @@ gh codespace delete {% endcli %} ## 延伸阅读 -- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) +- [代码空间生命周期](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md index 082cfada5bf1..b4fddb94c915 100644 --- a/translations/zh-CN/content/codespaces/getting-started/deep-dive.md +++ b/translations/zh-CN/content/codespaces/getting-started/deep-dive.md @@ -1,5 +1,5 @@ --- -title: Deep dive into Codespaces +title: 深入了解代码空间 intro: '了解 {% data variables.product.prodname_codespaces %} 的工作原理.' allowTitleToDifferFromFilename: true product: '{% data reusables.gated-features.codespaces %}' @@ -11,109 +11,109 @@ topics: - Codespaces --- -{% data variables.product.prodname_codespaces %} is an instant, cloud-based development environment that uses a container to provide you with common languages, tools, and utilities for development. {% data variables.product.prodname_codespaces %} is also configurable, allowing you to create a customized development environment for your project. By configuring a custom development environment for your project, you can have a repeatable codespace configuration for all users of your project. +{% data variables.product.prodname_codespaces %} 是一个基于云的即时开发环境，它使用容器为您提供用于开发的通用语言、工具和实用程序。 {% data variables.product.prodname_codespaces %} 也是可配置的，允许您为项目创建自定义的开发环境。 通过为项目配置自定义开发环境，可以为项目的所有用户提供可重复的代码空间配置。 ## 创建代码空间 -There are a number of entry points to create a codespace. +有许多入口点可用于创建代码空间。 -- From your repository for new feature work. -- From an open pull request to explore work-in-progress. -- From a commit in the repository's history to investigate a bug at a specific point in time. -- From {% data variables.product.prodname_vscode %}. +- 从存储库进行新功能工作。 +- 从打开的拉取请求中探索正在进行的工作。 +- 从存储库历史记录中的提交到调查特定时间点的漏洞。 +- 从 {% data variables.product.prodname_vscode %}。 -Your codespace can be ephemeral if you need to test something or you can return to the same codespace to work on long-running feature work. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。 +如果需要测试某些内容，则代码空间可以是短暂的，或者可以返回到同一代码空间来处理长时间运行的功能工作。 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。 -Once you've selected the option to create a new codespace, some steps happen in the background before the codespace is available to you. +Once you've selected the option to create a new codespace, and chosen a machine type for your codespace, some steps happen in the background before the codespace is available to you. ![使用 Codespaces 打开按钮](/assets/images/help/codespaces/new-codespace-button.png) -### Step 1: VM and storage are assigned to your codespace +### 步骤 1：将虚拟机和存储分配给代码空间 -When you create a codespace, a [shallow clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) of your repository is made on a Linux virtual machine that is both dedicated and private to you. Having a dedicated VM ensures that you have the entire set of compute resources from that machine available to you. If necessary, this also allows you to have full root access to your container. +创建代码空间时，将在专用且私有的 Linux 虚拟机上创建存储库的[影子克隆](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/) 。 拥有专用虚拟机可确保您拥有该计算机中可供使用的整个计算资源集。 如有必要，这还允许您对容器具有完全根访问权限。 -### Step 2: Container is created +### 步骤 2：创建容器 -{% data variables.product.prodname_codespaces %} uses a container as the development environment. This container is created based on the configurations that you can define in a `devcontainer.json` file and/or Dockerfile in your repository. If you don't [configure a container](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project), {% data variables.product.prodname_codespaces %} uses a [default image](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration), which has many languages and runtimes available. For information on what the default image contains, see the [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux) repository. +{% data variables.product.prodname_codespaces %} 使用容器作为开发环境。 此容器是根据您可以在 `devcontainer.json` 文件和/或存储库中的 Dockerfile 中定义的配置创建的。 如果不[配置容器](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project)，{% data variables.product.prodname_codespaces %} 使用[默认映像](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project#using-the-default-configuration)，该映像有许多语言和运行时可用。 有关默认映像包含的内容的信息，请参阅存储库 [`vscode-dev-containers`](https://github.com/microsoft/vscode-dev-containers/tree/main/containers/codespaces-linux)。 {% note %} -**Note:** If you want to use Git hooks in your codespace and apply anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) to your codespace, then you must set up hooks during step 4 after the container is created. +**注意：**如果要在代码空间中使用 Git 挂钩，并将 [git 模板目录](https://git-scm.com/docs/git-init#_template_directory)中的任何内容应用于代码空间，则必须在创建容器后的步骤 4 中设置挂钩。 -Since your repository is cloned onto the host VM before the container is created, anything in the [git template directory](https://git-scm.com/docs/git-init#_template_directory) will not apply in your codespace unless you set up hooks in your `devcontainer.json` configuration file using the `postCreateCommand` in step 4. For more information, see "[Step 4: Post-creation setup](#step-4-post-creation-setup)." +由于存储库在创建容器之前已克隆到主机虚拟机上，因此 [git 模板目录](https://git-scm.com/docs/git-init#_template_directory)中的任何内容都不适用于代码空间，除非您在步骤 4 中使用 `postCreateCommand` 在 `devcontainer.json` 配置文件中设置挂钩。 更多信息请参阅“[步骤 4：创建后设置](#step-4-post-creation-setup)”。 {% endnote %} -### Step 3: Connecting to the codespace +### 步骤 3：连接到代码空间 -When your container has been created and any other initialization has run, you'll be connected to your codespace. You can connect to it through the web or via [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code), or both, if needed. +创建容器并运行任何其他初始化后，您将连接到代码空间。 如果需要，您可以通过 Web 和/或 [Visual Studio Code](/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code) 连接。 -### Step 4: Post-creation setup +### 步骤 4：创建后设置 -Once you are connected to your codespace, your automated setup may continue to build based on the configuration you specified in your `devcontainer.json` file. You may see `postCreateCommand` and `postAttachCommand` run. +连接到代码空间后，您的自动设置可能会根据您在 `devcontainer.json` 文件中指定的配置继续构建。 您可能会看到 `postCreateCommand` 和 `postAttachCommand` 运行。 -If you want to use Git hooks in your codespace, set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`. For more information, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the Visual Studio Code documentation. +如果要在代码空间中使用 Git 挂钩，请使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)设置挂钩，例如 `postCreateCommand`。 更多信息请参阅 Visual Studio Code 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) 。 -If you have a public dotfiles repository for {% data variables.product.prodname_codespaces %}, you can enable it for use with new codespaces. When enabled, your dotfiles will be cloned to the container and the install script will be invoked. 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)”。 +如果您有一个用于 {% data variables.product.prodname_codespaces %} 的公共 dotfile 存储库，则可以启用它以用于新的代码空间。 启用后，您的 dotfile 将被克隆到容器中，并且将调用安装脚本。 更多信息请参阅“[为帐户个性化 {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/personalizing-codespaces-for-your-account#dotfiles)”。 -Finally, the entire history of the repository is copied down with a full clone. +最后，使用完整克隆复制存储库的整个历史记录。 -During post-creation setup you'll still be able to use the integrated terminal and make edits to your files, but take care to avoid any race conditions between your work and the commands that are running. -## {% data variables.product.prodname_codespaces %} lifecycle +在创建后设置期间，您仍然可以使用集成终端并对文件进行编辑，但要注意避免工作与正在运行的命令之间存在任何争用条件。 +## {% data variables.product.prodname_codespaces %} 生命周期 -### Saving files in your codespace +### 在代码空间中保存文件 -As you develop in your codespace, it will save any changes to your files every few seconds. Your codespace will keep running for 30 minutes after the last activity. After that time it will stop running but you can restart it from either from the existing browser tab or the list of existing codespaces. File changes from the editor and terminal output are counted as activity and so your codespace will not stop if terminal output is continuing. +当您在代码空间中开发时，它将每隔几秒钟保存对文件所做的任何更改。 您的代码空间将在上次活动后继续运行 30 分钟。 在此之后，它将停止运行，但您可以从现有浏览器选项卡或现有代码空间列表中重新启动它。 来自编辑器和终端输出的文件更改将计为活动，因此，如果终端输出继续，您的代码空间将不会停止。 {% note %} -**Note:** Changes in a codespace in {% data variables.product.prodname_vscode %} are not saved automatically, unless you have enabled [Auto Save](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save). +**注意：**除非已启用 [Auto Save（自动保存）](https://code.visualstudio.com/docs/editor/codebasics#_save-auto-save)，否则不会自动保存 {% data variables.product.prodname_vscode %} 代码空间中的更改。 {% endnote %} -### Closing or stopping your codespace +### 关闭或停止代码空间 -To stop your codespace you can [use the {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)). If you exit your codespace without running the stop command (for example, closing the browser tab), or if you leave the codespace running without interaction, the codespace and its running processes will continue until a window of inactivity occurs, after which the codespace will stop. By default, the window of inactivity is 30 minutes. +要停止代码空间，您可以 [使用 {% data variables.product.prodname_vscode_command_palette %}](/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces#suspending-or-stopping-a-codespace) (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows))。 如果在未运行停止命令的情况下退出代码空间（例如，关闭浏览器选项卡），或者让代码空间在没有交互的情况下运行，则代码空间及其正在运行的进程将继续运行，直到出现不活动窗口，之后代码空间将停止。 默认情况下，不活动窗口为 30 分钟。 -When you close or stop your codespace, all uncommitted changes are preserved until you connect to the codespace again. +关闭或停止代码空间时，将保留所有未提交的更改，直到您再次连接到代码空间。 -## Running your application +## 运行应用程序 -通过端口转发，您可以访问在代码空间内运行的 TCP 端口。 For example, if you're running a web application on port 4000 within your codespace, you can automatically forward that port to make the application accessible from your browser. +通过端口转发，您可以访问在代码空间内运行的 TCP 端口。 例如，如果要在代码空间内的端口 4000 上运行 Web 应用程序，则可以自动转发该端口，以使该应用程序可从浏览器访问。 -Port forwarding determines which ports are made accessible to you from the remote machine. Even if you do not forward a port, that port is still accessible to other processes running inside the codespace itself. +端口转发确定可从远程计算机访问哪些端口。 即使不转发端口，在代码空间本身内运行的其他进程仍然可以访问该端口。 -![Diagram showing how port forwarding works in a codespace](/assets/images/help/codespaces/port-forwarding.png) +![显示端口转发在代码空间中的工作方式的图示](/assets/images/help/codespaces/port-forwarding.png) -When an application running inside {% data variables.product.prodname_codespaces %} outputs a port to the console, {% data variables.product.prodname_codespaces %} detects the localhost URL pattern and automatically forwards the port. You can click on the URL in the terminal or in the toast message to open the port in a browser. By default, {% data variables.product.prodname_codespaces %} forwards the port using HTTP. For more information on port forwarding, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." +当在 {% data variables.product.prodname_codespaces %} 内运行的应用程序将端口输出到控制台时，{% data variables.product.prodname_codespaces %} 会检测本地主机 URL 模式并自动转发该端口。 可以单击终端或 Toast 消息中的 URL，以在浏览器中打开端口。 默认情况下， {% data variables.product.prodname_codespaces %} 使用 HTTP 转发端口。 有关端口转发的详细信息，请参阅“[代码空间中的转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)”。 -While ports can be forwarded automatically, they are not publicly accessible to the internet. By default, all ports are private, but you can manually make a port available to your organization or public, and then share access through a URL. For more information, see "[Sharing a port](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)." +虽然端口可以自动转发，但它们不能被互联网公开访问。 默认情况下，所有端口都是私有的，但您可以手动使端口可供您的组织或公共使用，然后通过 URL 共享访问权限。 更多信息请参阅“[共享端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace#sharing-a-port)”。 -Running your application when you first land in your codespace can make for a fast inner dev loop. As you edit, your changes are automatically saved and available on your forwarded port. To view changes, go back to the running application tab in your browser and refresh it. +首次登录代码空间时运行应用程序可以实现快速的内部开发循环。 编辑时，您的更改会自动保存，并可在转发的端口上使用。 要查看更改，请返回浏览器中正在运行的应用程序选项卡并刷新它。 -## Committing and pushing your changes +## 提交和推送更改 -Git is available by default in your codespace and so you can rely on your existing Git workflow. You can work with Git in your codespace either via the Terminal or by using [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol)'s source control UI. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)" +默认情况下，Git 在代码空间中可用，因此您可以依赖现有的 Git 工作流程。 您可以通过终端或使用 [Visual Studio Code](https://code.visualstudio.com/docs/editor/versioncontrol) 的源代码管理 UI 在代码空间中使用 Git。 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)”。 -![Running git status in Codespaces Terminal](/assets/images/help/codespaces/git-status.png) +![在代码空间终端中运行 git 状态](/assets/images/help/codespaces/git-status.png) -You can create a codespace from any branch, commit, or pull request in your project, or you can switch to a new or existing branch from within your active codespace. Because {% data variables.product.prodname_codespaces %} is designed to be ephemeral, you can use it as an isolated environment to experiment, check a teammate's pull request, or fix merge conflicts. 每个仓库甚至每个分支可创建多个代码空间。 However, each user account has a limit of 10 codespaces. 如果您已达到上限，想要创建一个新的代码空间，必须先删除一个旧代码空间。 +您可以从项目中的任何分支、提交或拉取请求创建代码空间，也可以从活动代码空间中切换到新的或现有的分支。 由于 {% data variables.product.prodname_codespaces %} 设计为临时的，因此您可以将其用作隔离环境来试验、检查团队成员的拉取请求或修复合并冲突。 每个仓库甚至每个分支可创建多个代码空间。 However, each user account has a limit of 10 codespaces. 如果您已达到上限，想要创建一个新的代码空间，必须先删除一个旧代码空间。 {% note %} -**Note:** Commits from your codespace will be attributed to the name and public email configured at https://github.com/settings/profile. A token scoped to the repository, included in the environment as `GITHUB_TOKEN`, and your GitHub credentials will be used to authenticate. +**注意：**来自代码空间的提交将归因于在 https://github.com/settings/profile 配置的名称和公共电子邮件。 范围限定为存储库的令牌（作为 `GITHUB_TOKEN` 包含在环境中），您的 GitHub 凭据将用于进行身份验证。 {% endnote %} -## Personalizing your codespace with extensions +## 使用扩展个性化您的代码空间 -Using {% data variables.product.prodname_vscode %} in your codespace gives you access to the {% data variables.product.prodname_vscode %} Marketplace so that you can add any extensions you need. For information on how extensions run in {% data variables.product.prodname_codespaces %}, see [Supporting Remote Development and GitHub Codespaces](https://code.visualstudio.com/api/advanced-topics/remote-extensions) in the {% data variables.product.prodname_vscode %} docs. +在代码空间中使用 {% data variables.product.prodname_vscode %} 可以访问 {% data variables.product.prodname_vscode %} 市场，以便您可以添加所需的任何扩展。 有关扩展如何在 {% data variables.product.prodname_codespaces %} 中运行的信息，请参阅 {% data variables.product.prodname_vscode %} 文档中的[支持远程开发和 GitHub 代码空间](https://code.visualstudio.com/api/advanced-topics/remote-extensions) 。 -If you already use {% data variables.product.prodname_vscode %}, you can use [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync) to automatically sync extensions, settings, themes, and keyboard shortcuts between your local instance and any {% data variables.product.prodname_codespaces %} you create. +如果您已使用 {% data variables.product.prodname_vscode %}，则可以使用[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)在本地实例和您创建的任何 {% data variables.product.prodname_codespaces %} 之间自动同步扩展程序、设置、主题和键盘快捷键。 ## 延伸阅读 -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) -- [Setting up your project for Codespaces](/codespaces/setting-up-your-project-for-codespaces) -- [Codespaces lifecycle](/codespaces/developing-in-codespaces/codespaces-lifecycle) +- [为组织启用 {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [管理组织中的 {% data variables.product.prodname_codespaces %} 帐单](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [为代码空间设置项目](/codespaces/setting-up-your-project-for-codespaces) +- [代码空间生命周期](/codespaces/developing-in-codespaces/codespaces-lifecycle) diff --git a/translations/zh-CN/content/codespaces/getting-started/quickstart.md b/translations/zh-CN/content/codespaces/getting-started/quickstart.md index 4a52b23bbd15..e74ccf11c485 100644 --- a/translations/zh-CN/content/codespaces/getting-started/quickstart.md +++ b/translations/zh-CN/content/codespaces/getting-started/quickstart.md @@ -58,7 +58,7 @@ Once your codespace is created, your repository will be automatically cloned int {% octicon "light-bulb" aria-label="The lightbulb icon" %} If you've closed the tab, open the Ports panel and click the **Open in browser** icon for the running port. ![Port Forwarding Panel](/assets/images/help/codespaces/quickstart-forward-port.png) -## Committing and pushing your changes +## 提交和推送更改 Now that you've made a few changes, you can use the integrated terminal or the source view to commit and push the changes back to the remote. @@ -95,5 +95,5 @@ Now that you've made a few changes, you can use the integrated terminal or the s ## 延伸阅读 -- [Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) -- [Managing billing for {% data variables.product.prodname_codespaces %} in your organization](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) +- [为组织启用 {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization) +- [管理组织中的 {% data variables.product.prodname_codespaces %} 帐单](/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization) diff --git a/translations/zh-CN/content/codespaces/index.md b/translations/zh-CN/content/codespaces/index.md index 76ef71ff8a3d..d14352a6d579 100644 --- a/translations/zh-CN/content/codespaces/index.md +++ b/translations/zh-CN/content/codespaces/index.md @@ -46,9 +46,10 @@ versions: children: - /overview - /getting-started + - /developing-in-codespaces - /setting-up-your-project-for-codespaces - /customizing-your-codespace - - /developing-in-codespaces + - /prebuilding-your-codespaces - /managing-your-codespaces - /managing-codespaces-for-your-organization - /codespaces-reference diff --git a/translations/zh-CN/content/codespaces/overview.md b/translations/zh-CN/content/codespaces/overview.md index 0683c63b2c19..f982aec8379a 100644 --- a/translations/zh-CN/content/codespaces/overview.md +++ b/translations/zh-CN/content/codespaces/overview.md @@ -1,8 +1,8 @@ --- -title: GitHub Codespaces overview +title: GitHub Codespaces 概述 shortTitle: 概览 product: '{% data reusables.gated-features.codespaces %}' -intro: 'This guide introduces {% data variables.product.prodname_codespaces %} and provides details on how it works and how to use it.' +intro: '本指南介绍了 {% data variables.product.prodname_codespaces %} ，并详细介绍了它的工作原理和使用方法。' allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/about-codespaces @@ -13,31 +13,31 @@ redirect_from: versions: fpt: '*' ghec: '*' -type: quick_start +type: overview topics: - Codespaces --- -## What is a codespace? +## 什么是代码空间？ -A codespace is a development environment that's hosted in the cloud. You can customize your project for {% data variables.product.prodname_codespaces %} by committing [configuration files](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project) to your repository (often known as Configuration-as-Code), which creates a repeatable codespace configuration for all users of your project. +代码空间是托管在云中的开发环境。 您可以通过将[配置文件](/codespaces/customizing-your-codespace/configuring-codespaces-for-your-project)提交到存储库（通常称为“配置即代码”）来自定义 {% data variables.product.prodname_codespaces %} 的项目，这将为项目的所有用户创建可重复的代码空间配置。 -{% data variables.product.prodname_codespaces %} run on a variety of VM-based compute options hosted by {% data variables.product.product_location %}, which you can configure from 2 core machines up to 32 core machines. You can connect to your codespaces from the browser or locally using {% data variables.product.prodname_vscode %}. +{% data variables.product.prodname_codespaces %} 在 {% data variables.product.product_location %}托管的各种基于 VM 的计算选项上运行，您最少可以配置 2 台核心计算机，最多可以配置 32 台。 您可以从浏览器或使用 {% data variables.product.prodname_vscode %} 本地连接到代码空间。 -![A diagram showing how {% data variables.product.prodname_codespaces %} works](/assets/images/help/codespaces/codespaces-diagram.png) +![显示 {% data variables.product.prodname_codespaces %} 工作原理的图表](/assets/images/help/codespaces/codespaces-diagram.png) -## Using Codespaces +## 使用 Codespaces -You can create a codespace from any branch or commit in your repository and begin developing using cloud-based compute resources. {% data reusables.codespaces.links-to-get-started %} +您可以从存储库中的任何分支或提交创建代码空间，并使用基于云的计算资源开始开发。 {% data reusables.codespaces.links-to-get-started %} -To customize the runtimes and tools in your codespace, you can create a custom configuration to define an environment (or _dev container_) that is specific for your repository. Using a dev container allows you to specify a Docker environment for development with a well-defined tool and runtime stack that can reference an image, Dockerfile, or docker-compose. This means that anyone using the repository will have the same tools available to them when they create a codespace. +要自定义代码空间中的运行时和工具，可以创建自定义配置来定义特定于存储库的环境（或_开发容器_）。 使用开发容器，可以使用定义明确的工具和运行时堆栈指定 Docker 环境进行开发，这些工具和运行时堆栈可以引用映像、Dockerfile 或 docker-compose。 这意味着使用存储库的任何人在创建代码空间时都将拥有相同的工具。 -If you don't do any custom configuration, {% data variables.product.prodname_codespaces %} will clone your repository into an environment with the default codespace image that includes many tools, languages, and runtime environments. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +如果不执行任何自定义配置，{% data variables.product.prodname_codespaces %} 会将存储库克隆到具有默认代码空间映像的环境中，该映像包含许多工具、语言和运行时环境。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 -You can also personalize aspects of your codespace environment by using a public [dotfiles](https://dotfiles.github.io/tutorials/) repository and [Settings Sync](https://code.visualstudio.com/docs/editor/settings-sync). Personalization can include shell preferences, additional tools, editor settings, and VS Code extensions. For more information, see "[Customizing your codespace](/codespaces/customizing-your-codespace)". +您还可以通过使用公共 [dotfiles](https://dotfiles.github.io/tutorials/) 存储库和[设置同步](https://code.visualstudio.com/docs/editor/settings-sync)来个性化代码空间环境的各个方面。 个性化设置可以包括 shell 首选项、其他工具、编辑器设置和 VS Code 扩展。 更多信息请参阅“[自定义代码空间](/codespaces/customizing-your-codespace)”。 ## 关于 {% data variables.product.prodname_codespaces %} 的计费 -For information on pricing, storage, and usage for {% data variables.product.prodname_codespaces %}, see "[Managing billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." +有关 {% data variables.product.prodname_codespaces %} 的定价、存储和使用情况的信息，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)”。 -{% data reusables.codespaces.codespaces-spending-limit-requirement %} For information on how organizations owners and billing managers can manage the spending limit for {% data variables.product.prodname_codespaces %} for an organization, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)." +{% data reusables.codespaces.codespaces-spending-limit-requirement %} 有关组织所有者和帐单管理员如何管理组织的 {% data variables.product.prodname_codespaces %} 支出限制的信息，请参阅“[管理 {% data variables.product.prodname_codespaces %} 的支出限制](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)”。 diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md new file mode 100644 index 000000000000..3908ebdab370 --- /dev/null +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md @@ -0,0 +1,44 @@ +--- +title: About Codespaces prebuilds +shortTitle: About prebuilds +intro: Codespaces prebuilds help to speed up the creation of new codespaces. +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## 概览 + +Prebuilding your codespaces allows you to be more productive and access your codespace faster, regardless of the size and complexity of your project. This is because any source code, editor extensions, project dependencies, commands, and configurations have already been downloaded, installed, and applied before you create a codespace for your project. Think of a prebuild as a "ready-to-go" template for a codespace. + +Whenever you push changes to your repository, {% data variables.product.prodname_codespaces %} uses {% data variables.product.prodname_actions %} to automatically update your prebuilds. + +When prebuilds are available for a particular branch of a repository, and for your region, you'll see the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label in the machine type dialog box that's displayed when you create a codespace and multiple machine types are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +## About billing for {% data variables.product.prodname_codespaces %} prebuilds + +{% data reusables.codespaces.billing-for-prebuilds %} For details of {% data variables.product.prodname_codespaces %} storage pricing, see "[About billing for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces)." + +Use of codespaces created using prebuilds is charged at the same rate as regular codespaces. + +## About pushing changes to prebuild-enabled branches + +Each push to a branch that has a prebuild configuration results in a {% data variables.product.prodname_dotcom %}-managed Actions workflow run to update the prebuild template. The prebuild workflow has a concurrency limit of one workflow run at a time for a given prebuild configuration, unless changes were made that affect the dev container configuration for the associated repository. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)”。 If a run is already in progress, the workflow run that was queued most recently queued will run next, after the current run completes. + +This means that if there are very frequent pushes to your repository, prebuild creation will occur at least as often as it takes to run the prebuild workflow. That is, if your workflow run typically takes one hour to complete, prebuilds will be created for your repository roughly hourly, if the run succeeds, or more often if there were pushes that change the dev container on the branch. + +For example, let's imagine 5 pushes are made, in quick succession, against a branch that has a prebuild configuration. In this situation: + +* A workflow run is started for the first push, to update the prebuild template. +* If the 4 remaining pushes do not affect the dev container configuration, the workflow runs for these are queued in a "pending" state. + + If any of the remaining 4 pushes change the dev container configuration, then the service will not skip that one and will immediately run the prebuild creation workflow, updating the prebuild accordingly if it succeeds. + +* Once the first run completes, workflow runs for pushes 2, 3, and 4 will be canceled, and the last queued workflow (for push 5) will run and update the prebuild template. diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md new file mode 100644 index 000000000000..d9586df68f89 --- /dev/null +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md @@ -0,0 +1,93 @@ +--- +title: Configuring prebuilds +shortTitle: Configure prebuilds +intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: People with admin access to a repository can configure prebuilds for the repository. +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +You can set up a prebuild configuration for a specific branch of your repository. + +Any branch created from a prebuild-enabled base branch will typically also get assigned a prebuild during codespace creation. This is true if the dev container on the branch is the same as on the base branch. This is because the majority of the prebuild configuration for branches with the same dev container configuration are identical, so developers can benefit from faster codespace creation times on those branches also. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)”。 + +Typically, when you configure prebuilds for a branch, prebuilds will be available for {% data variables.product.prodname_codespaces %} machine types for that branch. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB. + +## 基本要求 + +Before you can configure prebuilds for your project the following must be true: +* {% data variables.product.prodname_github_codespaces %} must be enabled for your organization. For more information, see "[Enabling {% data variables.product.prodname_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)." +* {% data variables.product.prodname_actions %} must be enabled for your repository. Each prebuild configuration needs to be able to trigger an associated Actions workflow. 更多信息请参阅“[管理仓库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)”。 + +## Configuring a prebuild + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-settings %} +1. In the "Code & automation" section of the sidebar, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %}**. +1. Under "Prebuild configuration", click **Set up prebuild**. + + ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png) + +1. Choose the branch for which you want to set up a prebuild. + + ![The Branch drop-down menu](/assets/images/help/codespaces/prebuilds-choose-branch.png) + + {% note %} + + **Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds. For example, if you enable prebuilds for the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds. For more information, see "[Why do I get prebuilds for branches that do not have prebuilds enabled?](/codespaces/troubleshooting/troubleshooting-prebuilds#2-why-do-i-get-prebuilds-for-branches-that-do-not-have-prebuilds-enabled)" + + {% endnote %} + +1. Choose the regions in which you want to set up a prebuild. Developers must be located in a region you select to be able to create codespaces from a prebuild. Alternatively, select **All regions**. + + ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png) + + {% note %} + + **注意**： + * The prebuild template for each region will incur individual charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)." + * Developers can set their default region for {% data variables.product.prodname_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces)." + + {% endnote %} + +1. 单击 **Create（创建）**。 + + The prebuild configuration is listed on the {% data variables.product.prodname_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuild templates, based on the branch you selected, in the regions you specified. + + {% note %} + + **Note**: By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access resources in its own repository. If your project uses resources from outside of the repository, you'll need to set the `CODESPACES_PREBUILD_TOKEN` secret to grant the required access. For more information, see "[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + + {% endnote %} + +## Configuring access to resources that are not in the repository + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. If your project needs to access external resources to build the development environment, you will need to set up a personal access token (PAT) with the appropriate access scopes. + +For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## 配置环境变量 + +To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-an-organization)." + +Prebuilds do not use any user-level secrets while building your environment, because these are not added until after the codespace has been created. + +{% data variables.product.prodname_codespaces %} secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces. For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#allowing-a-prebuild-to-access-external-resources)." + +## Configuring time-consuming tasks to be included in the prebuild + +You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild template creation. For more information, see the Visual Studio Code documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)." + +`onCreateCommand` is run only once, when the prebuild template is created, whereas `updateContentCommand` is run at template creation and at subsequent template updates. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild template update. + +## 延伸阅读 + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md new file mode 100644 index 000000000000..5f3bdca59ad0 --- /dev/null +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md @@ -0,0 +1,19 @@ +--- +title: Prebuilding your codespaces +intro: 'To speed up codespace creation, you can configure your project to prebuild codespaces for specific branches in specific regions.' +product: '{% data reusables.gated-features.codespaces %}' +versions: + fpt: '*' + ghec: '*' +topics: + - Codespaces +redirect_from: + - /codespaces/customizing-your-codespace/prebuilding-codespaces-for-your-project +children: + - /about-codespaces-prebuilds + - /configuring-prebuilds + - /managing-prebuilds + - /testing-dev-container-changes +--- + +{% data reusables.codespaces.prebuilds-beta-note %} \ No newline at end of file diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md new file mode 100644 index 000000000000..90fb80ae929f --- /dev/null +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md @@ -0,0 +1,109 @@ +--- +title: Managing prebuilds +shortTitle: Manage prebuilds +intro: 'You can review, modify, and delete the prebuild configurations for your repository.' +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +## Checking, changing, and deleting your prebuild configurations + +The prebuilds that you configure are created and updated using a {% data variables.product.prodname_actions %} workflow, managed by the {% data variables.product.prodname_codespaces %} service. + +The workflow is triggered by these events: + +* Creating or updating the prebuild configuration +* Pushing a commit or a pull request to a branch that's configured to have prebuilds +* Manually triggering the workflow + +People with admin access to a repository can check the progress of prebuilds, edit, and delete prebuild configurations. + +### Viewing the progress of prebuilds +You can view the current status of the latest workflow run for each prebuild configuration you've set up on the {% data variables.product.prodname_codespaces %} page of your repository settings. For example, "Currently running" or "Last run 1 hour ago." + +To see the log output for the latest prebuild workflow run, click **See output**. + +![The 'See output' button](/assets/images/help/codespaces/prebuilds-see-output.png) + +This displays the output of the most recent run of the workflow in the **Actions** tab. + +![The prebuild workflow output](/assets/images/help/codespaces/prebuilds-log-output.png) + +Alternatively, to view all prebuild workflow runs associated with the specified branch, click the ellipsis button and choose **View runs** from the dropdown menu. + +![The 'View runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-view-runs.png) + +This displays the workflow run history for prebuilds for the associated branch. + +![The workflow run history](/assets/images/help/codespaces/prebuilds-workflow-runs.png) + +### Editing a prebuild configuration + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to edit. +1. In the dropdown menu, click **Edit**. + + ![The 'Edit' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-edit.png) + +1. Make the required changes to the prebuild configuration, then click **Update**. + +### Delete a prebuild configuration + +Deleting a prebuild configuration also deletes all previously created prebuild templates for that configuration. As a result, shortly after you delete a configuration, prebuilds generated by that configuration will no longer be available when you create a new codespace. + +After you delete a prebuild configuration, workflow runs for that configuration that have been queued or started will still run. They will be listed in the workflow run history, along with previously completed workflow runs. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration you want to delete. +1. In the dropdown menu, click **Delete**. + + ![The 'Delete' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-delete.png) + +1. Click **OK** to confirm the deletion. + +### Manually trigger prebuilds + +It may be useful to manually trigger a workflow run for a prebuild configuration. Generally this is only necessary if you are debugging a problem with the workflow for a prebuild configuration. + +1. On the {% data variables.product.prodname_codespaces %} page of your repository settings, click the ellipsis to the right of the prebuild configuration whose workflow you want to trigger. +1. In the dropdown menu, click **Manually trigger**. + + ![The 'Manually trigger' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png) + +## Allowing a prebuild to access external resources + +By default, the {% data variables.product.prodname_actions %} workflow for a prebuild configuration can only access its own repository contents. Your project may use additional resources to build the development environment, such as files in other repositories, packages, GHCR images, and APIs. To allow your prebuild setup to access these resources, you will need to create a new personal account and then use this account to create a personal access token (PAT) with the appropriate scopes. + +1. Create a new personal account on {% data variables.product.prodname_dotcom %}. + + {% warning %} + + **Warning**: Although you can generate the PAT using your existing personal account, we strongly recommend creating a new account with access only to the target repositories required for your scenario. This is because the access token's `repository` permission grants access to all of the repositories that the account has access to. For more information, see "[Signing up for a new GitHub account](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)" and "[Security hardening for {% data variables.product.prodname_actions %}](/actions/security-guides/security-hardening-for-github-actions#considering-cross-repository-access)." + + {% endwarning %} +1. Give the new account read access to the required repositories. 更多信息请参阅“[管理个人对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)”。 +1. While signed into the new account, create a PAT with the `repo` scope. Optionally, if the prebuild will need to download packages from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, also select the `read:packages` scope. 更多信息请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 + + !['repo' and 'packages' scopes selected for a PAT](/assets/images/help/codespaces/prebuilds-select-scopes.png) + + If the prebuild will use a package from the {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %}, you will need to either grant the new account access to the package or configure the package to inherit the access permissions of the repository you are prebuilding. 更多信息请参阅“[配置包的访问控制和可见性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)”。 +{% ifversion ghec %}1. Authorize the token for use with SAML single sign-on (SSO), so that it can access repositories that are owned by organizations with SSO enabled. 更多信息请参阅“[授权个人访问令牌用于 SAML 单点登录](/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on)”。 + + ![The button to configure SSO for a PAT](/assets/images/help/codespaces/configure-SSO-for-PAT.png) + +{% endif %} +1. Copy the token string. You will assign this to a {% data variables.product.prodname_codespaces %} repository secret. +1. Sign back into the account that has admin access to the repository. +1. In the repository for which you want to create {% data variables.product.prodname_codespaces %} prebuilds, create a new {% data variables.product.prodname_codespaces %} repository secret called `CODESPACES_PREBUILD_TOKEN`, giving it the value of the token you created and copied. For more information, see "[Managing encrypted secrets for your repository and organization for {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces#adding-secrets-for-a-repository)." + +The PAT will be used for all subsequent prebuild templates created for your repository. Unlike other {% data variables.product.prodname_codespaces %} repository secrets, the `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and will not be available to use in codespaces created from your repository. + +## 延伸阅读 + +- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)" diff --git a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md new file mode 100644 index 000000000000..452367610fe6 --- /dev/null +++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/testing-dev-container-changes.md @@ -0,0 +1,35 @@ +--- +title: Testing dev container configuration changes on a prebuild-enabled branch +shortTitle: Test dev container changes +allowTitleToDifferFromFilename: true +intro: When you change the dev container configuration for a branch that's enabled for prebuilds you should test your changes in a codespace. +versions: + fpt: '*' + ghec: '*' +type: how_to +topics: + - Codespaces + - Set up +product: '{% data reusables.gated-features.codespaces %}' +permissions: People with write permissions to a repository can create or edit the dev container configuration for a branch. +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +Any changes you make to the dev container configuration for a prebuild-enabled branch will result in an update to the codespace configuration and the associated prebuild template. It’s therefore important to test such changes in a codespace from a test branch before committing your changes to a branch of your repository that's actively used. This will ensure you’re not introducing breaking changes for your team. + +更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)”。 + +## Testing changes to the dev container configuration + +1. Create a codespace from the prebuild-enabled branch whose dev container you want to change. For more information, see "[Creating a codespace ](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)." +1. In the codespace, check out a test branch. For more information, see "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)." +1. Make the required changes to the dev container configuration. +1. Apply the changes by rebuilding the container. 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。 +1. After everything looks good, we also recommend creating a new codespace from your test branch to ensure everything is working. You can then commit your changes to your repository's default branch, or an active feature branch, triggering an update of the prebuild template for that branch. + + {% note %} + + **Note**: Creating this codespace will take longer than usual because it will not be created from a prebuild. + + {% endnote %} diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md index 2f4d4baa0d02..7f5e77af53e7 100644 --- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md +++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project.md @@ -164,4 +164,8 @@ For more information about the available settings for `devcontainer.json`, see [ 1. {% data reusables.codespaces.recovery-mode %} 修复配置中的错误。 ![有关恢复模式的错误消息](/assets/images/help/codespaces/recovery-mode-error-message.png) - 要通过查看创建日志来诊断错误，请单击 **View creation log（查看创建日志）**。 - 要修复日志中发现的错误，请更新您的 `devcontainer.json` 文件。 - - 要应用更改，请重建容器。 + - 要应用更改，请重建容器。 + +## 延伸阅读 + +- "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)" diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md index 665171defc0c..88bb3d4b956f 100644 --- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md +++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-a-minimum-specification-for-codespace-machines.md @@ -1,6 +1,6 @@ --- title: Setting a minimum specification for codespace machines -shortTitle: Setting a minimum machine spec +shortTitle: Set a minimum machine spec intro: 'You can avoid under-resourced machine types being used for {% data variables.product.prodname_codespaces %} for your repository.' permissions: People with write permissions to a repository can create or edit the codespace configuration. versions: diff --git a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md index 201fb3417db0..0cb2903651c3 100644 --- a/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Setting up your Node.js project for Codespaces -shortTitle: Setting up your Node.js project +title: 为代码空间设置 Node.js 项目 +shortTitle: 设置 Node.js 项目 intro: '通过创建自定义开发容器，开始在 {% data variables.product.prodname_codespaces %} 中使用 JavaScript、Node.js 或 TypeScript 项目。' product: '{% data reusables.gated-features.codespaces %}' versions: @@ -48,7 +48,7 @@ hidden: true 默认代码空间容器将支持运行 Node.js 项目，如开箱即用 [vscode-remote-try-node](https://github.com/microsoft/vscode-remote-try-node)。 通过设置自定义容器，您可以自定义在代码空间创建过程中运行的工具和脚本，并确保为仓库中的所有 {% data variables.product.prodname_codespaces %} 用户提供完全可复制的环境。 -要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 For more information on dev containers, see "[Introduction to dev containers](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)". +要使用自定义容器设置项目，您需要使用 `devcontainer.json` 文件来定义环境。 在 {% data variables.product.prodname_codespaces %} 中，您可以从模板添加它，也可以自己创建。 有关开发容器的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-codespace/configuring-codespaces-for-your-project)”。 {% data reusables.codespaces.command-palette-container %} 3. 对于此示例，单击 **Node.js**。 如果需要其他功能，您可以选择任何特定于节点或工具（如节点和 MongoDB）组合的容器。 ![从列表中选择节点选项](/assets/images/help/codespaces/add-node-prebuilt-container.png) diff --git a/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md b/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md index 2d3bba7e2388..c502390c0c52 100644 --- a/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md +++ b/translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md @@ -1,6 +1,6 @@ --- title: Codespaces 日志 -intro: 'Overview of the logging locations used by {% data variables.product.prodname_codespaces %}.' +intro: '{% data variables.product.prodname_codespaces %} 使用的日志记录位置概述。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -13,57 +13,57 @@ shortTitle: Codespaces 日志 --- -Information on {% data variables.product.prodname_codespaces %} is output to three different logs: +有关 {% data variables.product.prodname_codespaces %} 的信息将输出到三个不同的日志： -- Codespace logs -- Creation logs -- Extension logs ({% data variables.product.prodname_vscode %} desktop) or Browser console logs ({% data variables.product.prodname_vscode %} in the web) +- 代码空间日志 +- 创建日志 +- 扩展日志（{% data variables.product.prodname_vscode %} 桌面）或浏览器控制台日志（Web 中的 {% data variables.product.prodname_vscode %} ） -## Codespace logs +## 代码空间日志 -These logs contain detailed information about the codespace, the container, the session, and the {% data variables.product.prodname_vscode %} environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. +这些日志包含有关代码空间、容器、会话和 {% data variables.product.prodname_vscode %} 环境的详细信息。 它们对于诊断连接问题和其他意外行为非常有用。 例如，代码空间冻结，但“Reload Windows（重新加载 Windows）”选项可将其解冻几分钟，或者您随机断开与代码空间的连接，但能够立即重新连接。 {% webui %} -1. If you are using {% data variables.product.prodname_codespaces %} in the browser, ensure that you are connected to the codespace you want to debug. -1. Open the {% data variables.product.prodname_vscode %} Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. -1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). -1. If you are using {% data variables.product.prodname_codespaces %} in the browser, right-click on the zip archive of logs from the Explorer view and select **Download…** to download them to your local machine. +1. 如果在浏览器中使用 {% data variables.product.prodname_codespaces %} ，请确保已连接到要调试的代码空间。 +1. 打开 {% data variables.product.prodname_vscode %} 命令面板 (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) ，然后键入 **Export logs**。 从列表中选择 **odespaces: Export Logs（代码空间：导出日志）**以下载日志。 +1. 定义保存日志 zip 存档的位置，然后单击 **Save（保存）**（桌面），或单击 **OK（确定）** (web)。 +1. 如果在浏览器中使用 {% data variables.product.prodname_codespaces %} ，请右键单击资源管理器视图中日志的 zip 存档，然后选择 **Download…（下载…）**将其下载到本地计算机。 {% endwebui %} {% vscode %} -1. Open the {% data variables.product.prodname_vscode %} Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Export logs**. Select **Codespaces: Export Logs** from the list to download the logs. -1. Define where to save the zip archive of logs then click **Save** (desktop) or click **OK** (web). +1. 打开 {% data variables.product.prodname_vscode %} 命令面板 (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) ，然后键入 **Export logs**。 从列表中选择 **odespaces: Export Logs（代码空间：导出日志）**以下载日志。 +1. 定义保存日志 zip 存档的位置，然后单击 **Save（保存）**（桌面），或单击 **OK（确定）** (web)。 {% endvscode %} {% cli %} -Currently you can't use {% data variables.product.prodname_cli %} to access these logs. To access them, open your codespace in {% data variables.product.prodname_vscode %} or in a browser. +目前，您无法使用 {% data variables.product.prodname_cli %} 来访问这些日志。 要访问它们，请在 {% data variables.product.prodname_vscode %} 或浏览器中打开代码空间。 {% endcli %} -## Creation logs +## 创建日志 -These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems. +这些日志包含有关容器、开发容器及其配置的信息。 它们对于调试配置和设置问题非常有用。 {% webui %} -1. Connect to the codespace you want to debug. -2. Open the {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file. +1. 连接到要调试的代码空间。 +2. 打开 {% data variables.product.prodname_vscode_command_palette %} (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) ，然后键入 **Creation logs**。 从列表中选择 **Codespaces: View Creation Log（代码空间：查看创建日志）**以打开 `creation.log` 文件。 -If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. +如果要与支持人员共享日志，可以将创建日志中的文本复制到文本编辑器中，并将文件保存在本地。 {% endwebui %} {% vscode %} -Open the Command Palette (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows)) and type **Creation logs**. Select **Codespaces: View Creation Log** from the list to open the `creation.log` file. +打开命令面板 (`Shift + Command + P` (Mac) / `Ctrl + Shift + P` (Windows))，然后键入 **Creation logs**。 从列表中选择 **Codespaces: View Creation Log（代码空间：查看创建日志）**以打开 `creation.log` 文件。 -If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. +如果要与支持人员共享日志，可以将创建日志中的文本复制到文本编辑器中，并将文件保存在本地。 {% endvscode %} @@ -71,15 +71,15 @@ If you want to share the log with support, you can copy the text from the creati {% data reusables.cli.cli-learn-more %} -To see the creation log use the `gh codespace logs` subcommand. After entering the command choose from the list of codespaces that's displayed. +要查看创建日志，请使用 `gh codespace logs` 子命令。 输入命令后，从显示的代码空间列表中进行选择。 ```shell gh codespace logs ``` -For more information about this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_logs). +有关此命令的详细信息，请参阅 [ {% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh_codespace_logs)。 -If you want to share the log with support, you can save the output to a file: +如果要与支持人员共享日志，可以将输出保存到一个文件中： ```shell gh codespace logs -c > /path/to/logs.txt @@ -87,19 +87,19 @@ gh codespace logs -c > /path/to/logs.txt {% endcli %} -## Extension logs +## 扩展日志 -These logs are available for {% data variables.product.prodname_vscode %} desktop users only. They are useful if it seems like the {% data variables.product.prodname_codespaces %} extension or {% data variables.product.prodname_vscode %} editor are having issues that prevent creation or connection. +这些日志仅适用于 {% data variables.product.prodname_vscode %} 桌面用户。 如果看起来 {% data variables.product.prodname_codespaces %} 扩展名或 {% data variables.product.prodname_vscode %} 编辑器遇到阻止创建或连接的问题，则它们很有用。 -1. In {% data variables.product.prodname_vscode %}, open the Command Palette. -1. Type **Logs** and select **Developer: Open Extension Logs Folder** from the list to open the extension log folder in your system's file explorer. +1. 在 {% data variables.product.prodname_vscode %} 中，打开命令面板。 +1. 键入 **Logs** ，然后从列表中选择 **Developer: Open Extension Logs Folder（开发人员：打开扩展日志文件夹）**，以在系统的文件资源管理器中打开扩展日志文件夹。 -From this view, you can access logs generated by the various extensions that you use in {% data variables.product.prodname_vscode %}. You will see logs for GitHub Codespaces, GitHub Authentication, and Git, in addition to any other extensions you have enabled. +在此视图中，您可以访问由在 {% data variables.product.prodname_vscode %} 中使用的各种扩展生成的日志。 除了已启用的任何其他扩展之外，你还将看到 GitHub Codespaces、GitHub Authentication 和 Git 的日志。 -## Browser console logs +## 浏览器控制台日志 -These logs are useful only if you want to debug problems with using {% data variables.product.prodname_codespaces %} in the browser. They are useful for debugging problems creating and connecting to {% data variables.product.prodname_codespaces %}. +仅当您要调试在浏览器中使用 {% data variables.product.prodname_codespaces %} 的问题时，这些日志才有用。 它们对于调试创建和连接到 {% data variables.product.prodname_codespaces %} 的问题非常有用。 -1. In the browser window for the codespace you want to debug, open the developer tools window. -1. Display the "Console" tab and click **errors** in the left side bar to show only the errors. -1. In the log area on the right, right-click and select **Save as** to save a copy of the errors to your local machine. ![保存错误](/assets/images/help/codespaces/browser-console-log-save.png) +1. 在要调试的代码空间的浏览器窗口中，打开开发人员工具窗口。 +1. 显示“Console（控制台）”选项卡，然后单击左侧栏中的 **errors（错误）**以仅显示错误。 +1. 在右侧的日志区域中，右键单击并选择 **Save as（另存为）**将错误的副本保存到本地计算机。 ![保存错误](/assets/images/help/codespaces/browser-console-log-save.png) diff --git a/translations/zh-CN/content/codespaces/troubleshooting/index.md b/translations/zh-CN/content/codespaces/troubleshooting/index.md index a6ee7d51507a..e88a7570952b 100644 --- a/translations/zh-CN/content/codespaces/troubleshooting/index.md +++ b/translations/zh-CN/content/codespaces/troubleshooting/index.md @@ -16,6 +16,7 @@ children: - /exporting-changes-to-a-branch - /troubleshooting-creation-and-deletion-of-codespaces - /troubleshooting-your-connection-to-codespaces + - /troubleshooting-prebuilds - /troubleshooting-dotfiles-for-codespaces - /troubleshooting-port-forwarding-for-codespaces - /troubleshooting-codespaces-clients diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md new file mode 100644 index 000000000000..8ecf1e23f984 --- /dev/null +++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md @@ -0,0 +1,59 @@ +--- +title: Troubleshooting prebuilds +shortTitle: Codespaces prebuilds +intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds. +versions: + fpt: '*' + ghec: '*' +type: reference +topics: + - Codespaces +product: '{% data reusables.gated-features.codespaces %}' +miniTocMaxHeadingLevel: 3 +--- + +{% data reusables.codespaces.prebuilds-beta-note %} + +For more information about {% data variables.product.prodname_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)." + +## Checking whether a codespace was created from a prebuild? + +If multiple machine types are available when you create a codespace then a dialog box is displayed giving you a choice of machine types. This will display the "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" label beside machine types for which prebuilds are available. + +![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png) + +If you have your {% data variables.product.prodname_codespaces %} editor preference set to "Visual Studio Code for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used. Similarly, if your editor preference is "Visual Studio Code" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for Codespaces](/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces)." + +After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal: + +```shell{:copy} +gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild +``` + +This returns `true` if the codespace was created using a prebuild. + +Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild: + +```shell{:copy} +cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME' +``` + +## The "Prebuild Ready" label is sometimes missing + +You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available. + +Each time you push to a prebuild-enabled branch, the prebuild template is updated. If the push involves a change to the dev container then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the machine types dialog box. During this time you can still create codespaces without a prebuild template. + +If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container is changed on your branch, so that it's not the same as the dev container on the base branch, prebuilds will no longer be available on your branch. + +Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch: + +* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this. +* Confirm that the prebuild configuration includes your region. +* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will have to wait until the prebuild workflow run for this push completes before prebuilds are available again. +* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container, then there will be no available prebuilds for the associated branch. + +## 延伸阅读 + +- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)" +- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)" diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md index e95024856e9d..66686cf1138e 100644 --- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md +++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md @@ -8,12 +8,12 @@ versions: type: reference topics: - Codespaces -shortTitle: 连接 +shortTitle: Connection --- ## 503 codespace service unavailable -Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error. +Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error. - If a **Start** button is shown in {% data variables.product.prodname_vscode %} or in your browser window, click **Start** to reconnect to the codespace. - Reset your codespace by reloading the window. From the [command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) in {% data variables.product.prodname_vscode %}, click **Developer: Reload Window**. diff --git a/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md b/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md index dbc4cf892c04..0f0578b65d8c 100644 --- a/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md +++ b/translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md @@ -1,6 +1,6 @@ --- -title: Working with support for Codespaces -intro: 'Tips on getting the best help from support for {% data variables.product.prodname_codespaces %}.' +title: 使用对代码空间的支持 +intro: '有关从 {% data variables.product.prodname_codespaces %} 的支持中获得最佳帮助的提示。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -11,24 +11,24 @@ topics: shortTitle: 使用支持 --- -Before support can help you with problems with codespaces, you need to know the name of the codespace and its codespaces ID (identifier). In addition, support may ask you to share some logs with them. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)" and "[About GitHub Support](/github/working-with-github-support/about-github-support)." +在支持人员帮助您解决代码空间问题之前，您需要知道代码空间的名称及其代码空间 ID（标识符）。 此外，支持人员可能会要求您与他们共享一些日志。 更多信息请参阅“[代码空间日志](/codespaces/troubleshooting/codespaces-logs)”和“[关于 GitHub 支持](/github/working-with-github-support/about-github-support)”。 -### Codespace names +### 代码空间名称 -Each codespace has a unique name that is a combination of your {% data variables.product.company_short %} handle, the repository name, and some random characters. The additional characters allow you to have codespaces for different branches in the same repository. For example: `octocat-myrepo-gmc7`. +每个代码空间都有一个唯一的名称，该名称是 {% data variables.product.company_short %} 句柄、存储库名称和一些随机字符的组合。 附加字符允许您为同一存储库中的不同分支提供代码空间。 例如： `octocat-myrepo-gmc7`。 -To find the name of a codespace: +要查找代码空间的名称： -- Open the codespace in the browser. The subdomain of the URL is the name of the codespace. For example: `https://octocat-myrepo-gmc7.github.dev` is the URL for the `octocat-myrepo-gmc7` codespace. -- If you cannot open a codespace, you can access the name in {% data variables.product.product_name %} on https://github.com/codespaces. The name is shown in a pop-up when you hover over the **Open in browser** option on https://github.com/codespaces. ![Codespace name shown on hover over](/assets/images/help/codespaces/find-codespace-name-github.png) +- 在浏览器中打开代码空间。 URL 的子域是代码空间的名称。 例如： `https://octocat-myrepo-gmc7.github.dev` 是 `octocat-myrepo-gmc7` 代码空间的 URL。 +- 如果无法打开代码空间，则可以在 https://github.com/codespaces 上访问 {% data variables.product.product_name %} 中的名称。 当您将鼠标悬停在 https://github.com/codespaces 上的 **Open in browser（在浏览器中打开）**选项上时，该名称将显示在弹出窗口中。 ![将鼠标悬停在上方时显示的代码空间名称](/assets/images/help/codespaces/find-codespace-name-github.png) -The name the codespace is also included in many of the log files. For example, in the codespace logs as the value of `friendlyName`, in the {% data variables.product.prodname_github_codespaces %} extension log after `making GET request for`, and in the browser console log after `clientUrl`. For more information, see "[Codespaces logs](/codespaces/troubleshooting/codespaces-logs)." +代码空间的名称也包含在许多日志文件中。 例如，在代码空间日志中作为 `friendlyName` 的值，在 `发出 GET 请求`后的 {% data variables.product.prodname_github_codespaces %} 扩展日志中，以及在 `clientUrl` 之后的浏览器控制台日志中。 更多信息请参阅“[代码空间日志](/codespaces/troubleshooting/codespaces-logs)”。 -### Codespaces IDs +### 代码空间 ID -Every codespace also has an ID (identifier). This is not shown by default in {% data variables.product.prodname_vscode %} so you may need to update the settings for the {% data variables.product.prodname_github_codespaces %} extension before you can access the ID. +每个代码空间还有一个 ID（标识符）。 默认情况下，这在 {% data variables.product.prodname_vscode %} 中不显示，因此您可能需要先更新 {% data variables.product.prodname_github_codespaces %} 扩展的设置，然后才能访问该 ID。 -1. In {% data variables.product.prodname_vscode %}, browser or desktop, in the Activity Bar on the left, click **Remote Explorer** to show details for the codespace. -2. If the sidebar includes a "Codespace Performance" section, hover over the "Codespace ID" and click the clipboard icon to copy the ID. -3. If the information is not shown, click {% octicon "gear" aria-label="The gear icon" %}, in the bottom-left corner of the Activity Bar, to display the "Settings" tab. -4. Expand **Extensions** and click **{% data variables.product.prodname_github_codespaces %}** to display the settings for the extension. Then enable **Show Performance Explorer** to display the "Codespace Performance" section in the sidebar. ![Codespace ID and settings required to display performance information](/assets/images/help/codespaces/find-codespace-id.png) +1. 在 {% data variables.product.prodname_vscode %}、浏览器或桌面中的左侧活动栏中，单击 **Remote Explorer（远程资源管理器）**以显示代码空间的详细信息。 +2. 如果侧边栏包含“Codespace Performance（代码空间性能）”部分，请将鼠标悬停在“Codespace ID（代码空间 ID）”上，然后单击剪贴板图标以复制 ID。 +3. 如果未显示信息，请单击活动栏左下角的 {% octicon "gear" aria-label="The gear icon" %} 以显示“Settings（设置）”选项卡。 +4. 展开 **Extensions（扩展）**，然后单击 **{% data variables.product.prodname_github_codespaces %}** 以显示扩展的设置。 然后启用 **Show Performance Explorer（显示性能资源管理器）**在边栏中显示“Codespace Performance（代码空间性能）”部分。 ![显示性能信息所需的代码空间 ID 和设置](/assets/images/help/codespaces/find-codespace-id.png) diff --git a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index b80cb0dabdff..f6c04733f78f 100644 --- a/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -272,8 +272,8 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre #### Git 引用 -* [Create a reference](/rest/reference/git#create-a-reference) -* [Get a reference](/rest/reference/git#get-a-reference) +* [创建引用](/rest/reference/git#create-a-reference) +* [获取引用](/rest/reference/git#get-a-reference) * [列出匹配的引用](/rest/reference/git#list-matching-references) * [更新引用](/rest/reference/git#update-a-reference) * [删除引用](/rest/reference/git#delete-a-reference) diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md index c978ff55f007..ebb0f6161569 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md @@ -45,7 +45,11 @@ shortTitle: 申请学生包 ## 到期和续订 -在您的 {% data variables.product.prodname_student_pack %} 访问权限到期后，如果您仍有资格，您可以重新申请，但有些合作伙伴可能不提供续订服务。 合作伙伴的大多数计时特惠在您设置后便开始。 更多信息请参阅 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) 页面。 +在您的 {% data variables.product.prodname_student_pack %} 访问权限到期后，如果您仍有资格，您可以重新申请，但有些合作伙伴可能不提供续订服务。 合作伙伴的大多数计时特惠在您设置后便开始。 To reapply, simply return to https://education.github.com, click your profile picture, then click **Reverify your academic affiliation**. + +![Menu option to reverify your academic affiliation](/assets/images/help/education/reverify-academic-affiliation.png) + +更多信息请参阅 [{% data variables.product.prodname_student_pack %}](https://education.github.com/pack) 页面。 要查看您对 {% data variables.product.prodname_student_pack %} 的免费访问何时到期，请访问您帐户的[帐单设置](https://github.com/settings/billing)。 diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md index 3e56b15403db..b2a161917fc1 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-visual-studio-code-with-github-classroom.md @@ -1,19 +1,19 @@ --- -title: About using Visual Studio Code with GitHub Classroom -shortTitle: About using Visual Studio Code -intro: 'You can configure Visual Studio Code as the preferred editor for assignments in {% data variables.product.prodname_classroom %}.' +title: 关于将 Visual Studio Code 与 GitHub Classroom 配合使用 +shortTitle: 关于使用 Visual Studio Code +intro: '您可以将 Visual Studio Code 配置为 {% data variables.product.prodname_classroom %} 中任务的首选编辑器。' versions: fpt: '*' redirect_from: - /education/manage-coursework-with-github-classroom/about-using-vs-code-with-github-classroom --- -## About Visual Studio Code +## 关于 Visual Studio Code -Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux. With the [GitHub Classroom extension for Visual Studio Code](https://aka.ms/classroom-vscode-ext), students can easily browse, edit, submit, collaborate, and test their Classroom Assignments. For more information about IDEs and {% data variables.product.prodname_classroom %}, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)." +Visual Studio Code 是一个轻量级但功能强大的源代码编辑器，可在桌面上运行，适用于 Windows、macOS 和 Linux。 借助 [Visual Studio Code 的 GitHub Classroom 扩展](https://aka.ms/classroom-vscode-ext)，学生可以轻松浏览、编辑、提交、协作和测试他们的课堂作业。 有关 IDE 和 {% data variables.product.prodname_classroom %} 的更多信息，请参阅“[集成 {% data variables.product.prodname_classroom %} 与 IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide)”。 -### Your student's editor of choice -The GitHub Classroom integration with Visual Studio Code provides students with an extension pack which contains: +### 您学生的首选编辑器 +GitHub Classroom 与 Visual Studio Code 的集成为学生提供了一个扩展包，其中包含： 1. [GitHub Classroom Extension](https://aka.ms/classroom-vscode-ext) with custom abstractions that make it easy for students to navigate getting started. 2. [Visual Studio Live Share Extension](https://marketplace.visualstudio.com/items?itemName=MS-vsliveshare.vsliveshare-pack) integrating into a student view for easy access to teaching assistants and classmates for help and collaboration. diff --git a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md index 605b0a35f577..08a2af7203f1 100644 --- a/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md +++ b/translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md @@ -46,10 +46,12 @@ shortTitle: 扩展和集成 ### Slack 与 {% data variables.product.product_name %} 集成 -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 您还可以执行关闭或打开议题等活动，并在不离开 Slack 的情况下提供丰富的议题和拉取请求参考。 +The Slack + {% data variables.product.prodname_dotcom %} app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, and you can see detailed references to issues and pull requests without leaving Slack. The app will also ping you personally in Slack if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. -The {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). 更多信息请访问 Marketplace 中的 [Slack 集成应用程序](https://github.com/marketplace/slack-github)。 +The Slack + {% data variables.product.prodname_dotcom %} app is also compatible with [Slack Enterprise Grid](https://slack.com/intl/en-in/help/articles/360000281563-Manage-apps-on-Enterprise-Grid). For more information, visit the [Slack + {% data variables.product.prodname_dotcom %} app](https://github.com/marketplace/slack-github) in the marketplace. ### Microsoft Teams 与 {% data variables.product.product_name %} 集成 -You can subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. 您也可以执行一些活动，如关闭或打开议题、评论您的议题和拉取请求，以及提供丰富的议题和拉取请求引用而不离开 Microsoft Teams。 更多信息请访问 Microsoft AppSource 中的 [Microsoft Teams 集成应用程序](https://appsource.microsoft.com/en-us/product/office/WA200002077)。 +The {% data variables.product.prodname_dotcom %} for Teams app lets you subscribe to your repositories or organizations and get realtime updates about issues, pull requests, commits, discussions, releases, deployment reviews and deployment statuses. You can also perform activities like opening and closing issues, commenting on your issues and pull requests, and you can see detailed references to issues and pull requests without leaving Microsoft Teams. The app will also ping you personally in Teams if you are mentioned as part of any {% data variables.product.prodname_dotcom %} notifications that you receive in your channels or personal chats. + +For more information, visit the [{% data variables.product.prodname_dotcom %} for Teams app](https://appsource.microsoft.com/en-us/product/office/WA200002077) in Microsoft AppSource. diff --git a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md index 0231b06a5a72..3b9c4546dbe6 100644 --- a/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md +++ b/translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md @@ -24,9 +24,9 @@ shortTitle: GitHub Advanced Security A {% data variables.product.prodname_GH_advanced_security %} license provides the following additional features: -- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/github/finding-security-vulnerabilities-and-errors-in-your-code/about-code-scanning)." +- **{% data variables.product.prodname_code_scanning_capc %}** - Search for potential security vulnerabilities and coding errors in your code. For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)." -- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/github/administering-a-repository/about-secret-scanning)." +- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)." {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %} - **Dependency review** - Show the full impact of changes to dependencies and see details of any vulnerable versions before you merge a pull request. For more information, see "[About dependency review](/code-security/supply-chain-security/about-dependency-review)." @@ -95,6 +95,16 @@ If you have an enterprise account, license use for the entire enterprise is show {% endif %} +{% ifversion fpt or ghec %} +## About starter workflows for {% data variables.product.prodname_advanced_security %} + +{% data reusables.advanced-security.starter-workflows-beta %} +{% data reusables.advanced-security.starter-workflow-overview %} + +For more information on starter workflows, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)" and "[Using starter workflows](/actions/using-workflows/using-starter-workflows)." + +{% endif %} + {% ifversion ghec or ghes > 3.0 or ghae %} ## Further reading diff --git a/translations/zh-CN/content/get-started/using-github/github-command-palette.md b/translations/zh-CN/content/get-started/using-github/github-command-palette.md index 6c6a2c575005..35841a650c6b 100644 --- a/translations/zh-CN/content/get-started/using-github/github-command-palette.md +++ b/translations/zh-CN/content/get-started/using-github/github-command-palette.md @@ -210,7 +210,7 @@ These commands are available only when you open the command palette from an issu | `Edit issue title` | Open the title of the issue ready for editing. | | `Lock issue` | Limit new comments to users with write access to the repository. 更多信息请参阅“[锁定对话](/communities/moderating-comments-and-conversations/locking-conversations)”。 | | `Pin`/`unpin issue` | Change whether or not the issue is shown in the pinned issues section for the repository. 更多信息请参阅“[将议题固定到仓库](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)”。 | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this issue. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 | +| `Subscribe`/`unsubscribe` | Opt in or out of notifications for changes to this issue. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 | | `Transfer issue...` | Transfer the issue to another repository. 更多信息请参阅“[将议题转让给其他仓库](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)”。 | ### Pull request commands @@ -225,5 +225,5 @@ These commands are available only when you open the command palette from a pull | `Edit pull request body` | Open the main body of the pull request ready for editing. | | `Edit pull request title` | Open the title of the pull request ready for editing. | | `Open in new codespace` | Create and open a codespace for the head branch of the pull request. 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。 | -| `Subscribe`/`unscubscribe` | Opt in or out of notifications for changes to this pull request. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 | +| `Subscribe`/`unsubscribe` | Opt in or out of notifications for changes to this pull request. 更多信息请参阅“[关于通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)”。 | | `Update current branch` | Update the head branch of the pull request with changes from the base branch. This is available only for pull requests that target the default branch of the repository. For more information, see "[About branches](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches)." | diff --git a/translations/zh-CN/content/github-cli/github-cli/about-github-cli.md b/translations/zh-CN/content/github-cli/github-cli/about-github-cli.md index 2df96ef8ffbf..f076b6736344 100644 --- a/translations/zh-CN/content/github-cli/github-cli/about-github-cli.md +++ b/translations/zh-CN/content/github-cli/github-cli/about-github-cli.md @@ -1,5 +1,5 @@ --- -title: About GitHub CLI +title: 关于 GitHub CLI intro: '{% data reusables.cli.cli-intro %}' versions: fpt: '*' diff --git a/translations/zh-CN/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md b/translations/zh-CN/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md index 70bb6b225b70..5bb4b1d4e2e6 100644 --- a/translations/zh-CN/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md +++ b/translations/zh-CN/content/github/site-policy/github-statement-against-modern-slavery-and-child-labor.md @@ -18,7 +18,7 @@ topics: GitHub 强烈谴责现代奴隶制和童工现象的存在和延续，并严格履行自己的职责，确保现代奴隶制和童工现象不会发生在其供应链或其业务的任何部分中。 （在本声明中，“现代奴隶制”是指奴役、强迫或强制劳动、贩运、压榨以及监禁或以契约束缚劳动者。 “童工”是指雇佣 16 岁以下的孩子从事工作，或雇佣 14 岁以下的孩子从事轻型工作，但不保护孩子的上学时间，也不顾及孩子的健康福祉。） -根据[英国现代奴隶制法案](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted)，以及 [ILO 2014 年关于强迫劳动的公约协定](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029)、[ILO 关于工作基本原则和权利的声明](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm)和[联合国可持续发展目标的目标 8.7](https://sustainabledevelopment.un.org/sdg8)，介绍了 GitHub 为防止其业务或供应链中出现现代奴隶制和童工现象而采取的措施。 +In accordance with the [UK Modern Slavery Act](https://www.legislation.gov.uk/ukpga/2015/30/section/54/enacted), and in alignment with the [ILO 2014 Protocol to its Forced Labour Convention](https://www.ilo.org/dyn/normlex/en/f?p=NORMLEXPUB:12100:0::NO::P12100_ILO_CODE:P029), [ILO Declaration on Fundamental Principles and Rights at Work](https://www.ilo.org/declaration/thedeclaration/textdeclaration/lang--en/index.htm), and [United Nations Sustainable Development Goals target 8.7](https://www.unodc.org/roseap/en/sustainable-development-goals.html#:~:text=Target%208.7%20%2D%20Take%20immediate%20and,labour%20in%20all%20its%20forms), this 2018 Statement Against Modern Slavery and Child Labor ("the Statement") describes the steps GitHub has taken to prevent modern slavery and child labor from occurring in its business or supply chain. ## GitHub 的结构、业务和供应链 diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md index a221416dfb81..3d71339f600e 100644 --- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md +++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md @@ -1,6 +1,6 @@ --- -title: Customizing your organization's profile -intro: You can share information about your organization by customizing your organization's profile +title: 自定义组织的配置文件 +intro: 您可以通过自定义组织的配置文件来共享有关组织的信息 versions: fpt: '*' ghec: '*' @@ -8,22 +8,22 @@ versions: ghae: issue-4749 topics: - Organizations -shortTitle: Customize organization profile +shortTitle: 自定义组织配置文件 --- -## About your organization's profile README +## 关于组织的资料 README -You can share information about how to engage with your organization by creating an organization profile README. {% data variables.product.prodname_dotcom %} shows your organization profile README in the "Overview" tab of your organization. +您可以通过创建组织配置文件 README 来共享有关如何与组织互动的信息。 {% data variables.product.prodname_dotcom %} 在组织的“Overview（概述）”选项卡中显示组织资料 README。 -You can choose what information to include your organization profile README. Here are some examples of information that may be helpful in your organization's profile README. +您可以选择要包含组织资料 README 的信息。 下面是一些信息示例，这些信息可能对组织的资料 README 有所帮助。 -- An "About" section that describes your organization -- Guidance for getting help in the organization +- “About（关于）”部分介绍您的组织 +- 在组织中获取帮助的指南 -You can format text and include emoji, images, and GIFs in your organization profile README by using {% data variables.product.company_short %} Flavored Markdown. 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)”。 +您可以使用 {% data variables.product.company_short %} Flavored Markdown 在组织资料 README 中设置文本格式和包含表情符号、图像及 GIF。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)”。 -## Adding an organization profile README +## 添加组织资料 README -1. If your organization does not already have a public `.github` repository, create a public `.github` repository. -2. In your organization's `.github` repository, create a `README.md` file in the `profile` folder. -3. Commit the changes to the `README.md` file. The content of the `README.md` will appear on your organization's profile. +1. 如果您的组织还没有公共 `.github` 存储库，请创建一个公共 `.github` 存储库。 +2. 在组织的 `.github` 存储库中，在 `profile` 文件夹中创建 `README.md` 文件。 +3. 将更改提交到 `README.md` 文件。 `README.md` 的内容将显示在组织的资料中。 diff --git a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md index 526cd225e9ad..bfc8c103e207 100644 --- a/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md +++ b/translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md @@ -1,6 +1,6 @@ --- title: 备份仓库 -intro: 'You can use{% ifversion ghes or ghae %} Git and{% endif %} the API {% ifversion fpt or ghec %}or a third-party tool {% endif %}to back up your repository.' +intro: '可使用{% ifversion ghes or ghae %} Git 和{% endif %} API {% ifversion fpt or ghec %}或第三方工具{% endif %}备份仓库。' redirect_from: - /articles/backing-up-a-repository - /github/creating-cloning-and-archiving-repositories/backing-up-a-repository @@ -24,7 +24,7 @@ topics: - 要将仓库的 Git 数据下载到本地计算机，您需要克隆该仓库。 更多信息请参阅“[克隆仓库](/articles/cloning-a-repository)”。 - 还可以下载仓库的 wiki。 更多信息请参阅“[添加或删除 wiki 页面](/communities/documenting-your-project-with-wikis/adding-or-editing-wiki-pages)”。 -克隆仓库或 wiki 时，仅下载 Git 数据，例如项目文件和提交历史记录。 You can use our API to export other elements of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to your local machine: +克隆仓库或 wiki 时，仅下载 Git 数据，例如项目文件和提交历史记录。 您可以使用我们的 API 将 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上存储库的其他元素导出到本地计算机： - [议题](/rest/reference/issues#list-issues-for-a-repository) - [拉取请求](/rest/reference/pulls#list-pull-requests) @@ -37,7 +37,7 @@ topics: - [项目](/rest/reference/projects#list-repository-projects) {% endif %} -Once you have {% ifversion ghes or ghae %}a local version of all the content you want to back up, you can create a zip archive and {% else %}downloaded your archive, you can {% endif %}copy it to an external hard drive and/or upload it to a cloud-based backup or storage service such as [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/), [Google Drive](https://www.google.com/drive/) or [Dropbox](https://www.dropbox.com/). +拥有{% ifversion ghes or ghae %}要备份的所有内容的本地版本后，可以创建一个 zip 存档，以及在{% else %}下载存档后，可以 {% endif %}将其复制到外部硬盘驱动器和/或将其上传到基于云的备份或存储服务，例如 [Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-overview/)、[Google Drive](https://www.google.com/drive/) 或 [Dropbox](https://www.dropbox.com/)。 {% ifversion fpt or ghec %} ## 第三方备份工具 diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md index ddd27b8037b6..0d21cedcf6ea 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md @@ -19,4 +19,4 @@ shortTitle: 配置提交变基 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -3. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select **Allow rebase merging**. 这将允许贡献者通过将其个人提交变基到基本分支来合并拉取请求。 如果您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求变基提交](/assets/images/help/repository/pr-merge-rebase.png) +3. 在 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}“拉取请求”{% else %}“合并按钮”{% endif %} 下，选择 **Allow rebase merging（允许变基合并）**。 这将允许贡献者通过将其个人提交变基到基本分支来合并拉取请求。 如果您还选择了另一种合并方法，则贡献者在合并拉取请求时能够选择合并提交的类型。 {% data reusables.repositories.squash-and-rebase-linear-commit-hisitory %} ![拉取请求变基提交](/assets/images/help/repository/pr-merge-rebase.png) diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md index 02ecdc499be8..1a32f1ca938b 100644 --- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md +++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md @@ -26,4 +26,4 @@ shortTitle: 管理自动合并 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} -1. Under {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}"Pull Requests"{% else %}"Merge button"{% endif %}, select or deselect **Allow auto-merge**. ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) +1. 在 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6069 %}“拉取请求”{% else %}“合并按钮”{% endif %} 下，选择或取消选择 **Allow auto-merge（允许自动合并）**。 ![允许或禁止自动合并的复选框](/assets/images/help/pull_requests/allow-auto-merge-checkbox.png) diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md index b8fb627ea587..a9a8ee72ba90 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/deleting-a-repository.md @@ -25,11 +25,11 @@ topics: **警告**： - 删除仓库将**永久**删除发行版附件和团队权限。 此操作**必须**完成。 -- Deleting a private{% ifversion ghes or ghec or ghae %} or internal{% endif %} repository will delete all forks of the repository. +- 删除私有 {% ifversion ghes or ghec or ghae %} 或内部 {% endif %} 仓库将删除仓库的所有复刻。 {% endwarning %} -Some deleted repositories can be restored within 90 days of deletion. {% ifversion ghes or ghae %}Your site administrator may be able to restore a deleted repository for you. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% else %}For more information, see "[Restoring a deleted repository](/articles/restoring-a-deleted-repository)."{% endif %} +某些已删除的存储库可以在删除后的 90 天内恢复。 {% ifversion ghes or ghae %}站点管理员或能为您恢复已删除的存储库。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。 {% else %}更多信息请参阅“[恢复删除的仓库](/articles/restoring-a-deleted-repository)”。{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} diff --git a/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md index 0973a1286066..5c6592327439 100644 --- a/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md +++ b/translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md @@ -1,6 +1,6 @@ --- title: 排查克隆错误 -intro: 'If you''re having trouble cloning a repository, check these common errors.' +intro: 如果您在克隆存储库时遇到问题，请检查这些常见错误。 redirect_from: - /articles/error-the-requested-url-returned-error-403 - /articles/error-the-requested-url-returned-error-401 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index bf408ca1799b..38250866d570 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -18,7 +18,7 @@ topics: 具有管理员或所有者权限的人员可以在仓库中创建 CODEOWNERS 文件。 -The people you choose as code owners must have read permissions for the repository. When the code owner is a team, that team must be visible and it must have write permissions, even if all the individual members of the team already have write permissions directly, through organization membership, or through another team membership. +您选择作为代码所有者的人员必须具有仓库的读取权限。 当代码所有者是团队时，该团队必须可见且必须拥有写入权限，即使团队的所有成员都已经直接通过组织成员资格或通过另一个团队成员资格直接拥有写入权限。 ## 关于代码所有者 @@ -39,21 +39,21 @@ The people you choose as code owners must have read permissions for the reposito 为使代码所有者接收审查请求，CODEOWNERS 文件必须在拉取请求的基本分支上。 例如，如果您将 `@octocat` 分配为仓库 `gh-pages` 分支上 *.js* 文件的代码所有者，则在头部分支与 `gh-pages` 之间打开更改 *.js* 文件的拉取请求时，`@octocat` 将会收到审查请求。 {% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} -## CODEOWNERS file size +## CODEOWNERS 文件大小 -CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. +CODEOWNERS 文件大小必须低于 3MB。 将不会加载超过此限制的 CODEOWNERS 文件，这意味着不会显示代码所有者信息，并且不会要求相应的代码所有者查看拉取请求中的更改。 -To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry. +要减小 CODEOWNERS 文件的大小，请考虑使用通配符模式将多个条目合并为单个条目。 {% endif %} ## CODEOWNERS 语法 -CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用大多数规则的模式，但有[一些例外](#syntax-exceptions)。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 Users must have `read` access to the repository and teams must have explicit `write` access, even if the team's members already have access. You can also refer to a user by an email address that has been added to their account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, for example `user@example.com`. +CODEOWNERS 文件使用遵循 [gitignore](https://git-scm.com/docs/gitignore#_pattern_format) 文件中所用大多数规则的模式，但有[一些例外](#syntax-exceptions)。 模式后接一个或多个使用标准 `@username` 或 `@org/team-name` 格式的 {% data variables.product.prodname_dotcom %} 用户名或团队名称。 用户必须具有对存储库的`读取`权限，并且团队必须具有显式`写入`权限，即使团队成员已具有访问权限也是如此。 您还可以通过已添加到用户在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上帐户的电子邮件地址来引用用户，例如 `user@example.com`。 -CODEOWNERS paths are case sensitive, because {% data variables.product.prodname_dotcom %} uses a case sensitive file system. Since CODEOWNERS are evaluated by {% data variables.product.prodname_dotcom %}, even systems that are case insensitive (for example, macOS) must use paths and files that are cased correctly in the CODEOWNERS file. +CODEOWNERS 路径区分大小写，因为 {% data variables.product.prodname_dotcom %} 使用区分大小写的文件系统。 由于 CODEOWNERS 是由 {% data variables.product.prodname_dotcom %} 评估的，因此即使是不区分大小写的系统（例如 macOS）也必须使用在 CODEOWNERS 文件中正确大小写的路径和文件。 {% if codeowners-errors %} -If any line in your CODEOWNERS file contains invalid syntax, that line will be skipped. When you navigate to the CODEOWNERS file in your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, you can see any errors highlighted. A list of errors in a repository's CODEOWNERS file is also accessible via the API. 更多信息请参阅 REST API 文档中的“[仓库](/rest/reference/repos#list-codeowners-errors)”。 +如果 CODEOWNERS 文件中的任何行包含无效语法，则该行将被跳过。 当您在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上导航到存储库中的 CODEOWNERS 文件时，您可以看到突出显示的任何错误。 存储库的 CODEOWNERS 文件中的错误列表也可以通过 API 访问。 更多信息请参阅 REST API 文档中的“[仓库](/rest/reference/repos#list-codeowners-errors)”。 {% else %} 如果 CODEOWNERS 文件中的任何行包含无效语法，则该文件将不会被检测并且不会用于请求审查。 {% endif %} @@ -121,8 +121,8 @@ gitignore 文件有一些语法规则在 CODEOWNERS 文件中不起作用： - 使用 `!` 否定模式 - 使用 `[ ]` 定义字符范围 -## CODEOWNERS and branch protection -Repository owners can add branch protection rules to ensure that changed code is reviewed by the owners of the changed files. 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)”。 +## CODEOWNERS 和分支保护 +存储库所有者可以添加分支保护规则，以确保已更改文件的所有者审阅已更改的代码。 更多信息请参阅“[关于受保护分支](/github/administering-a-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)”。 ## 延伸阅读 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md index 85c6100e52ab..f5acd2f1f119 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md @@ -90,7 +90,7 @@ topics: ## 免责声明 -GitHub 开源许可的目标是提供一个起点，帮助您做出明智的决定。 GitHub 显示许可信息以帮助用户了解开源许可以及使用它们的项目。 我们希望它有帮助，但请记住，我们不是律师，像其他人一样，我们也会犯错。 For that reason, GitHub provides the information on an "as-is" basis and makes no warranties regarding any information or licenses provided on or through it, and disclaims liability for damages resulting from using the license information. 如果对适合您的代码的许可有任何疑问，或有任何其他相关的问题，最好咨询专业人员。 +GitHub 开源许可的目标是提供一个起点，帮助您做出明智的决定。 GitHub 显示许可信息以帮助用户了解开源许可以及使用它们的项目。 我们希望它有帮助，但请记住，我们不是律师，像其他人一样，我们也会犯错。 因此，GitHub“按原样”提供信息，对提供或通过其提供的任何信息或许可不做任何保证，并对使用许可信息所造成的损害不承担责任。 如果对适合您的代码的许可有任何疑问，或有任何其他相关的问题，最好咨询专业人员。 ## 延伸阅读 diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md index 2236315e27da..d43b4c742177 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md @@ -1,6 +1,6 @@ --- -title: Managing GitHub Actions settings for a repository -intro: 'You can disable or configure {% data variables.product.prodname_actions %} for a specific repository.' +title: 管理存储库的 GitHub Actions 设置 +intro: '您可以对特定仓库禁用或配置 {% data variables.product.prodname_actions %}。' redirect_from: - /github/administering-a-repository/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository - /github/administering-a-repository/managing-repository-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository @@ -16,7 +16,7 @@ topics: - Actions - Permissions - Pull requests -shortTitle: Manage GitHub Actions settings +shortTitle: 管理 GitHub Actions 设置 --- {% data reusables.actions.enterprise-beta %} @@ -38,7 +38,7 @@ shortTitle: Manage GitHub Actions settings {% note %} -**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 For more information, see "[Disabling or limiting {% data variables.product.prodname_actions %} for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)" or "[Enforcing policies for {% data variables.product.prodname_actions %} in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)." +**注：**如果您的组织有覆盖策略或由具有覆盖策略的企业帐户管理，则可能无法管理这些设置。 更多信息请参阅“[禁用或限制组织的 {% data variables.product.prodname_actions %}](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization)”或“[在企业帐户中实施 {% data variables.product.prodname_actions %} 策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-github-actions-policies-for-your-enterprise)”。 {% endnote %} @@ -73,7 +73,7 @@ shortTitle: Manage GitHub Actions settings {% data reusables.actions.workflow-run-approve-public-fork %} -You can configure this behavior for a repository using the procedure below. 修改此设置会覆盖组织或企业级别的配置集。 +您可以使用以下过程为存储库配置此行为。 修改此设置会覆盖组织或企业级别的配置集。 {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} @@ -87,7 +87,7 @@ You can configure this behavior for a repository using the procedure below. 修 {% data reusables.github-actions.private-repository-forks-overview %} -If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository. +如果为 {% ifversion ghec or ghae or ghes %}企业或{% endif %} 组织禁用了某个策略，则无法为存储库启用该策略。 {% data reusables.github-actions.private-repository-forks-options %} @@ -103,7 +103,7 @@ If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or {% data reusables.github-actions.workflow-permissions-intro %} -The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled. +默认权限也可以在组织设置中配置。 如果在组织设置中选择了更受限制的默认值，则在仓库设置中自动选择相同的选项，并禁用许可的选项。 {% data reusables.github-actions.workflow-permissions-modifying %} @@ -120,32 +120,32 @@ The default permissions can also be configured in the organization settings. If {% endif %} {% ifversion ghes > 3.3 or ghae-issue-4757 or ghec %} -## Allowing access to components in an internal repository +## 允许访问内部存储库中的组件 -Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)." +企业成员可以使用内部存储库来处理项目，而无需公开共享信息。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)”。 -You can configure whether {% if internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% if internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% endif %} +您可以配置是否可以从存储库外部访问内部存储库中的 {% if internal-actions%}操作和 {% endif %}工作流程。{% if internal-actions %} 更多信息请参阅“[与企业共享操作和工作流程](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)”。{% endif %} -1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository. -1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. 在 {% data variables.product.prodname_dotcom %} 上，导航到内部仓库的主页面。 +1. 在仓库名称下，单击 {% octicon "gear" aria-label="The gear icon" %}**Settings（设置）**。 {% data reusables.repositories.settings-sidebar-actions %} -1. Under **Access**, choose one of the access settings: +1. 在 **Access（访问）**下，选择以下访问设置之一： {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png){% else %}![Set the access to Actions components](/assets/images/enterprise/3.4/actions-access-settings.png){% endif %} - * **Not accessible** - Workflows in other repositories cannot access this repository. - * **Accessible from repositories in the 'ORGANIZATION NAME' organization** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ORGANIZATION NAME' organization can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.{% endif %} - * **Accessible from repositories in the 'ENTERPRISE NAME' enterprise** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ENTERPRISE NAME' enterprise can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.{% endif %} + * **Not accessible（无法访问）**- 其他存储库中的工作流程无法访问此存储库。 + * **可从 'ORGANIZATION NAME' 组织中的存储库访问** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}属于 'ORGANIZATION NAME' 组织的其他存储库中的工作流程可以访问此存储库中的操作和工作流程。 仅允许从私有或内部存储库进行访问。{% else %}如果其他存储库中的工作流程属于同一组织，并且其可见性是私有或内部，则可以使用此存储库中的工作流程。{% endif %} + * **可从 ''ENTERPRISE NAME' 企业中的存储库访问** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}属于 ''ENTERPRISE NAME' 企业的其他存储库中的工作流程可以访问此存储库中的操作和工作流程。 仅允许从私有或内部存储库进行访问。{% else %}如果其他存储库中的工作流程属于同一企业，并且其可见性是私有或内部，则可以使用此存储库中的工作流程。{% endif %} 1. 单击 **Save（保存）**以应用设置。 {% endif %} -## Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository +## 为仓库中构件和日志的 {% data variables.product.prodname_actions %} 配置保留期 -You can configure the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your repository. +您可以为仓库中的 {% data variables.product.prodname_actions %} 构件和日志配置保留期。 {% data reusables.actions.about-artifact-log-retention %} -You can also define a custom retention period for a specific artifact created by a workflow. For more information, see "[Setting the retention period for an artifact](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)." +您还可以为工作流程创建的特定构件自定义保留期。 更多信息请参阅“[设置构件的保留期](/actions/managing-workflow-runs/removing-workflow-artifacts#setting-the-retention-period-for-an-artifact)”。 ## 设置仓库的保留期 diff --git a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md index e0c738edf817..15ec49021af4 100644 --- a/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md +++ b/translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/analyzing-changes-to-a-repositorys-content.md @@ -20,7 +20,7 @@ versions: ghec: '*' topics: - Repositories -shortTitle: Analyze changes +shortTitle: 分析更改 --- ## 可视化仓库中的提交 @@ -41,7 +41,7 @@ shortTitle: Analyze changes {% data reusables.repositories.accessing-repository-graphs %} 3. 在左侧边栏中，单击 **Commits（提交）**。 ![提交选项卡](/assets/images/help/graphs/commits_tab.png) -## Visualizing additions and deletion to content in a repository +## 可视化仓库内容的添加和删除 代码频率图显示仓库历史记录中每周的内容添加和删除。 diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-files/index.md b/translations/zh-CN/content/repositories/working-with-files/managing-files/index.md index 699f861cd3d3..d587a43bf246 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-files/index.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-files/index.md @@ -1,6 +1,6 @@ --- title: 管理文件 -intro: 'You can create, edit, move, and delete files in a repository, directly on {% data variables.product.product_name %} or on the command line.' +intro: '您可以直接在 {% data variables.product.product_name %} 或命令行上创建、编辑、移动和删除存储库中的文件。' redirect_from: - /articles/managing-files-on-github - /github/managing-files-in-a-repository/managing-files-on-github diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-files/renaming-a-file.md b/translations/zh-CN/content/repositories/working-with-files/managing-files/renaming-a-file.md index 531e8617474f..79e3c8078889 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-files/renaming-a-file.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-files/renaming-a-file.md @@ -1,6 +1,6 @@ --- title: 重命名文件 -intro: 'You can rename any file in your repository directly in {% data variables.product.product_name %} or by using the command line.' +intro: '您可以直接在 {% data variables.product.product_name %} 中或使用命令行重命名存储库中的任何文件。' redirect_from: - /articles/renaming-a-file - /github/managing-files-in-a-repository/renaming-a-file @@ -17,9 +17,9 @@ topics: - Repositories --- -## Renaming a file on {% data variables.product.product_name %} +## 重命名 {% data variables.product.product_name %} 上的文件 -Renaming a file also gives you the opportunity to [move the file to a new location](/articles/moving-a-file-to-a-new-location) +重命名文件还使您有机会[将文件移动到新位置](/articles/moving-a-file-to-a-new-location) {% tip %} diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md index f92dda1ed5b7..cac544b55c5f 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-git-large-file-storage.md @@ -1,6 +1,6 @@ --- title: 关于 Git Large File Storage -intro: '{% data variables.product.product_name %} limits the size of files allowed in repositories. To track files beyond this limit, you can use {% data variables.large_files.product_name_long %}.' +intro: '{% data variables.product.product_name %} 限制存储库中允许的文件大小。 要跟踪超出此限制的文件，您可以使用 {% data variables.large_files.product_name_long %}。' redirect_from: - /articles/about-large-file-storage - /articles/about-git-large-file-storage diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md index 810e85e013ed..5a2061dda62b 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md @@ -1,6 +1,6 @@ --- -title: About large files on GitHub -intro: '{% data variables.product.product_name %} limits the size of files you can track in regular Git repositories. Learn how to track or remove files that are beyond the limit.' +title: 关于 GitHub 上的大文件 +intro: '{% data variables.product.product_name %} 限制了可以在常规 Git 存储库中跟踪的文件大小。 了解如何跟踪或删除超出限制的文件。' redirect_from: - /articles/distributing-large-binaries - /github/managing-large-files/distributing-large-binaries @@ -21,18 +21,18 @@ versions: ghes: '*' ghae: '*' ghec: '*' -shortTitle: Large files +shortTitle: 大文件 --- -## About size limits on {% data variables.product.product_name %} +## 关于 {% data variables.product.product_name %} 的大小限制 {% ifversion fpt or ghec %} {% data variables.product.product_name %} 尝试为所有 Git 仓库提供丰富的存储空间，尽管文件和仓库大小存在硬性限制。 为确保用户的性能和可靠性，我们积极监控整个仓库运行状况的信号。 仓库运行状况是各种交互因素共同作用的结果，包括大小、提交频率、内容和结构。 -### File size limits +### 文件大小限制 {% endif %} -{% data variables.product.product_name %} limits the size of files allowed in repositories. 如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](#removing-files-from-a-repositorys-history)”。 +{% data variables.product.product_name %} 限制存储库中允许的文件大小。 如果尝试添加或更新大于 {% data variables.large_files.warning_size %} 的文件，您将从 Git 收到警告。 更改仍将成功推送到仓库，但您可以考虑删除提交，以尽量减少对性能的影响。 更多信息请参阅“[从仓库的历史记录中删除文件](#removing-files-from-a-repositorys-history)”。 {% note %} @@ -40,16 +40,16 @@ shortTitle: Large files {% endnote %} -{% ifversion ghes %}默认情况下， {% endif %}{% data variables.product.product_name %} 阻止超过 {% data variables.large_files.max_github_size %} 的推送。 {% ifversion ghes %}但站点管理员可为您的 {% data variables.product.product_location %} 配置不同的限制。 For more information, see "[Setting Git push limits](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)."{% endif %} +{% ifversion ghes %}默认情况下， {% endif %}{% data variables.product.product_name %} 阻止超过 {% data variables.large_files.max_github_size %} 的推送。 {% ifversion ghes %}但站点管理员可为您的 {% data variables.product.product_location %} 配置不同的限制。 更多信息请参阅“[设置 Git 推送限制](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-git-push-limits)”。{% endif %} -To track files beyond this limit, you must use {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}). For more information, see "[About {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)." +要跟踪超出此限制的文件，必须使用 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %})。 更多信息请参阅“[关于 {% data variables.large_files.product_name_long %}](/repositories/working-with-files/managing-large-files/about-git-large-file-storage)”。 -If you need to distribute large files within your repository, you can create releases on {% data variables.product.product_location %} instead of tracking the files. 更多信息请参阅“[分发大型二进制文件](#distributing-large-binaries)”。 +如果需要在存储库中分发大文件，则可以在 {% data variables.product.product_location %} 上创建版本，而不是跟踪文件。 更多信息请参阅“[分发大型二进制文件](#distributing-large-binaries)”。 -Git is not designed to handle large SQL files. 要与其他开发者共享大型数据库，建议使用 [Dropbox](https://www.dropbox.com/)。 +Git 不是为处理大型 SQL 文件而设计的。 要与其他开发者共享大型数据库，建议使用 [Dropbox](https://www.dropbox.com/)。 {% ifversion fpt or ghec %} -### Repository size limits +### 存储库大小限制 建议仓库保持较小，理想情况下小于 1 GB，强烈建议小于 5 GB。 较小的仓库克隆速度更快，使用和维护更容易。 如果您的仓库过度影响我们的基础架构，您可能会收到来自 {% data variables.contact.github_support %} 的电子邮件，要求您采取纠正措施。 我们力求灵活，特别是对于拥有很多协作者的大型项目，并且尽可能与您一起找到解决方案。 您可以有效地管理仓库的大小和整体运行状况，以免您的仓库影响我们的基础架构。 在 [`github/git-sizer`](https://github.com/github/git-sizer) 仓库中可以找到用于仓库分析的建议和工具。 diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md index 3ae6164af02f..652747f9e309 100644 --- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md +++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage.md @@ -22,7 +22,7 @@ shortTitle: 存储和带宽 例如： - 如果将 500 MB 文件推送到 {% data variables.large_files.product_name_short %}，您将使用 500 MB 的分配存储空间，而不使用带宽。 如果进行 1 个字节的更改后再次推送文件，您会使用另外 500 MB 的存储空间，但仍然不使用带宽，所以两次推送的总使用量是 1 GB 存储空间和零带宽。 - 如果下载一个使用 LFS 跟踪的 500 MB 文件，您将使用仓库所有者分配的 500 MB 带宽。 如果协作者推送文件更改并将新版本拉取到本地仓库，您将使用另外 500 MB 的带宽，所以两次下载的总使用量是 1 GB 带宽。 -- If {% data variables.product.prodname_actions %} downloads a 500 MB file that is tracked with LFS, it will use 500 MB of the repository owner's allotted bandwidth. +- 如果 {% data variables.product.prodname_actions %} 下载了使用 LFS 跟踪的 500 MB 文件，它将使用存储库所有者分配的 500 MB 带宽。 {% ifversion fpt or ghec %} 如果 {% data variables.large_files.product_name_long %} ({% data variables.large_files.product_name_short %}) 对象包含在仓库的源代码存档中，则下载这些存档将会计入仓库的带宽使用量。 更多信息请参阅“[管理仓库存档中的 {% data variables.large_files.product_name_short %} 对象](/github/administering-a-repository/managing-git-lfs-objects-in-archives-of-your-repository)”。 diff --git a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md index a8456de4bfd5..65d5cbda0ebf 100644 --- a/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md +++ b/translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md @@ -33,7 +33,7 @@ shortTitle: 文件的永久链接 分支头部的文件版本可能会随着新的提交而改变，因此如果您复制常规的 URL，当以后有人查看时，文件内容可能会不同。 -## Press Y to permalink to a file in a specific commit +## 按 Y 键可永久链接到特定提交中的文件 要创建所查看文件特定版本的永久链接，不要在 URL 中使用分支名称（例如上例中的 `main` 部分），而是输入提交 id。 这将永久链接到该提交中文件的精确版本。 例如： diff --git a/translations/zh-CN/data/features/github-runner-dashboard.yml b/translations/zh-CN/data/features/github-runner-dashboard.yml new file mode 100644 index 000000000000..f5fe71ecb494 --- /dev/null +++ b/translations/zh-CN/data/features/github-runner-dashboard.yml @@ -0,0 +1,4 @@ +--- +versions: + fpt: '*' + ghec: '*' diff --git a/translations/zh-CN/data/learning-tracks/code-security.yml b/translations/zh-CN/data/learning-tracks/code-security.yml index 47c9ad1a0d7b..931afcbdea10 100644 --- a/translations/zh-CN/data/learning-tracks/code-security.yml +++ b/translations/zh-CN/data/learning-tracks/code-security.yml @@ -2,17 +2,17 @@ #Feature available only on dotcom security_advisories: title: '修复并披露安全漏洞' - description: '使用安全建议私下修复报告的漏洞并获取 CVE。' + description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.' featured_track: '{% ifversion fpt %}true{% else %}false{% endif %}' guides: - - /code-security/security-advisories/about-coordinated-disclosure-of-security-vulnerabilities - - /code-security/security-advisories/creating-a-security-advisory - - /code-security/security-advisories/adding-a-collaborator-to-a-security-advisory - - /code-security/security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability - - /code-security/security-advisories/publishing-a-security-advisory - - /code-security/security-advisories/editing-a-security-advisory - - /code-security/security-advisories/withdrawing-a-security-advisory - - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory + - /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities + - /code-security/repository-security-advisories/creating-a-repository-security-advisory + - /code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory + - /code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability + - /code-security/repository-security-advisories/publishing-a-repository-security-advisory + - /code-security/repository-security-advisories/editing-a-repository-security-advisory + - /code-security/repository-security-advisories/withdrawing-a-repository-security-advisory + - /code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory #Feature available on dotcom and GHES dependabot_alerts: title: '获取漏洞依赖项的通知' diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml index f566c33f24c9..d3f36a776df3 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml @@ -148,6 +148,7 @@ sections: - 对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。 - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。' - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail. + - Actions services needs to be restarted after restoring appliance from backup taken on a different host. deprecations: - heading: Deprecation of GitHub Enterprise Server 3.0 diff --git a/translations/zh-CN/data/reusables/actions/starter-workflow-categories.md b/translations/zh-CN/data/reusables/actions/starter-workflow-categories.md new file mode 100644 index 000000000000..cf82a899e70c --- /dev/null +++ b/translations/zh-CN/data/reusables/actions/starter-workflow-categories.md @@ -0,0 +1,5 @@ +{% data variables.product.prodname_dotcom %} provides ready-to-use starter workflows for the following high level categories: +- **Deployment (CD)**. For more information, see "[About continuous deployment](/actions/deployment/about-deployments/about-continuous-deployment)." +{% ifversion fpt or ghec %}- **Security**. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."{% endif %} +- **Continuous Integration (CI)**. 更多信息请参阅“[关于持续集成](/actions/automating-builds-and-tests/about-continuous-integration)”。 +- **Automation**. Automation starter workflows offer solutions for automating workflows, such as triaging pull requests and applying a label based on the paths that are modified in the pull request, or greeting users who are first time contributors to the repository. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/advanced-security/starter-workflow-overview.md b/translations/zh-CN/data/reusables/advanced-security/starter-workflow-overview.md new file mode 100644 index 000000000000..7425d26a2982 --- /dev/null +++ b/translations/zh-CN/data/reusables/advanced-security/starter-workflow-overview.md @@ -0,0 +1 @@ +{% data variables.product.product_name %} provides starter workflows for security features such as {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/advanced-security/starter-workflows-beta.md b/translations/zh-CN/data/reusables/advanced-security/starter-workflows-beta.md new file mode 100644 index 000000000000..54baa92fc33d --- /dev/null +++ b/translations/zh-CN/data/reusables/advanced-security/starter-workflows-beta.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** Starter workflows for {% data variables.product.prodname_advanced_security %} have been consolidated in a "Security" category in the **Actions** tab of a repository. This new configuration is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/code-scanning/billing.md b/translations/zh-CN/data/reusables/code-scanning/billing.md new file mode 100644 index 000000000000..062c1dde9574 --- /dev/null +++ b/translations/zh-CN/data/reusables/code-scanning/billing.md @@ -0,0 +1 @@ +{% ifversion fpt or ghec %}使用操作运行 {% data variables.product.prodname_code_scanning %} 将消耗分钟数。 更多信息请参阅“[关于 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions/about-billing-for-github-actions).”{% endif %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds.md b/translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds.md new file mode 100644 index 000000000000..6fa486a52926 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds.md @@ -0,0 +1,5 @@ +A {% data variables.product.prodname_actions %} workflow is triggered every time you create or update a prebuild template, or push to a prebuild-enabled branch. As with other workflows, while prebuild workflows are running they will either consume some of the Actions minutes included with your account, if you have any, or they will incur charges for Actions minutes. For more information about pricing for Actions minutes, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)." + +If you are an organization owner, you can track usage of prebuild workflows by downloading a {% data variables.product.prodname_actions %} usage report for your organization. You can identify workflow runs for prebuilds by filtering the CSV output to only include the workflow called "Create Codespaces Prebuilds." 更多信息请参阅“[查看 {% data variables.product.prodname_actions %} 使用情况](/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage#viewing-github-actions-usage-for-your-organization)”。 + +While {% data variables.product.prodname_codespaces %} prebuilds is in beta there is no charge for storage of templates. When prebuilds become generally available, you will be billed for storing prebuild templates for each prebuild configuration in each region selected for that configuration. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md b/translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md new file mode 100644 index 000000000000..7e48d1342cd4 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md @@ -0,0 +1,5 @@ +{% note %} + +**Note:** The ability to prebuild codespaces is currently in beta and subject to change. + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md b/translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md new file mode 100644 index 000000000000..e7697bec4262 --- /dev/null +++ b/translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md @@ -0,0 +1 @@ +To speed up codespace creation, repository administrators can enable {% data variables.product.prodname_codespaces %} prebuilds for a repository. For more information, see "[About {% data variables.product.prodname_codespaces %} prebuilds](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md index 8b8f769a90a4..3ac13f76079f 100644 --- a/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md +++ b/translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-release-phase.md @@ -1,5 +1,5 @@ {% note %} -**Note:** The Dormant Users report is currently in private beta so admins only have access to this feature with a special invite. To join the private beta, receive support, or address your questions, contact the {% data variables.product.company_short %} representative who helps manage your account. +**Note:** The Dormant Users report is currently in beta and subject to change. During the beta, ongoing improvements to the report download feature may limit its availability. {% endnote %} diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md new file mode 100644 index 000000000000..f216e917feaf --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-check-concurrency.md @@ -0,0 +1,5 @@ +To identify any constraints with concurrency or queuing, you can check how many jobs are currently being processed on the {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise. + +![Screenshot of a list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png) + +For more information, see "[Monitoring your current jobs](/actions/using-github-hosted-runners/monitoring-your-current-jobs)." \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md new file mode 100644 index 000000000000..3298610d5ac7 --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md @@ -0,0 +1,12 @@ +{% ifversion fpt %} +1. Navigate to the main page of the organization or repository. +1. Click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. +1. In the left sidebar, click **Actions**, then click **Runners**. +{% elsif ghec %} +1. Navigate to your runner settings: + * **In an organization or repository**: Navigate to the main page, then click {% octicon "gear" aria-label="The Settings gear" %} **Settings**. + * **If using an enterprise account**: Navigate to your enterprise account by clicking your profile photo in the top-right corner of {% data variables.product.prodname_dotcom_the_website %}, then clicking **Your enterprises**, then clicking the enterprise. +1. 导航到 {% data variables.product.prodname_actions %} 设置： + * **In an organization or repository**: Click **Actions** in the left sidebar, then click **Runners**. + * **If using an enterprise account**: In the left sidebar, click **"{% octicon "law" aria-label="The law icon" %} Policies"**, then click **Actions**, then click the **Runners** tab. +{% endif %} diff --git a/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md new file mode 100644 index 000000000000..cb4e59b206fc --- /dev/null +++ b/translations/zh-CN/data/reusables/github-actions/github-hosted-runners-table-entry.md @@ -0,0 +1 @@ +1. In the "Runners" table, click the entry for **GitHub-hosted runners**. This entry will only be present if you're using {% data variables.product.prodname_dotcom %}-hosted runners. \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/security-advisory/repository-level-advisory-note.md b/translations/zh-CN/data/reusables/security-advisory/repository-level-advisory-note.md new file mode 100644 index 000000000000..dd7f32d588fe --- /dev/null +++ b/translations/zh-CN/data/reusables/security-advisory/repository-level-advisory-note.md @@ -0,0 +1,7 @@ +{% note %} + +**Note**: This article applies to editing repository-level advisories as a repository owner. + +Users who are not repository owners can contribute to global security advisories in the {% data variables.product.prodname_advisory_database %} at [github.com/advisories](https://github.com/advisories). Edits to global advisories will not change or affect how the advisory appears on the repository. 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)." + +{% endnote %} \ No newline at end of file diff --git a/translations/zh-CN/data/ui.yml b/translations/zh-CN/data/ui.yml index 190081755ee7..4f502e6456b2 100644 --- a/translations/zh-CN/data/ui.yml +++ b/translations/zh-CN/data/ui.yml @@ -44,6 +44,7 @@ pages: miniToc: 本文内容 contributor_callout: 这篇文章的参与者和维护者是 all_enterprise_releases: All Enterprise Server releases + about_versions: About versions errors: oops: 哎呀！ something_went_wrong: 看来出现了错误。