From 3423275f9fdec9dbcee9fc1e73bc30bfa329035d Mon Sep 17 00:00:00 2001
From: docubot <67483024+docubot@users.noreply.github.com>
Date: Wed, 13 Apr 2022 08:43:18 -0700
Subject: [PATCH] New translation batch for cn (#26888)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/lint-translation-files.js --check rendering

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn

* run script/i18n/reset-known-broken-translation-files.js

* Check in cn CSV report

Co-authored-by: Mike Surowiec <mikesurowiec@users.noreply.github.com>
---
 translations/log/cn-resets.csv                |    8 +-
 ...iewing-peoples-roles-in-an-organization.md |   12 +-
 .../using-environments-for-deployment.md      |   10 +-
 .../autoscaling-with-self-hosted-runners.md   |    4 +-
 ...-hosted-runner-application-as-a-service.md |    2 +-
 .../understanding-github-actions.md           |    2 +-
 .../security-hardening-for-github-actions.md  |    9 +-
 .../about-service-containers.md               |    4 +-
 .../monitoring-your-current-jobs.md           |   22 +-
 ...hing-dependencies-to-speed-up-workflows.md |   25 +-
 .../events-that-trigger-workflows.md          |    4 +-
 .../content/admin/code-security/index.md      |    6 +-
 ...ub-advanced-security-in-your-enterprise.md |   97 +-
 ...-of-github-advanced-security-deployment.md |  260 ++--
 ...he-dependency-graph-for-your-enterprise.md |   14 +-
 ...-vulnerability-data-for-your-enterprise.md |    8 +-
 .../command-line-utilities.md                 |    2 +-
 ...nabling-and-scheduling-maintenance-mode.md |    2 +-
 .../site-admin-dashboard.md                   |    4 +-
 .../admin/enterprise-management/index.md      |    2 +-
 .../about-system-logs.md                      |   62 +
 ...ting-a-health-check-for-your-enterprise.md |   46 +-
 .../monitoring-your-appliance/index.md        |    1 +
 ...ucing-github-actions-to-your-enterprise.md |    2 +-
 translations/zh-CN/content/admin/guides.md    |   18 +-
 .../auditing-activity-in-your-enterprise.md   |   35 -
 .../index.md                                  |    1 -
 ...unts-saml-single-sign-on-recovery-codes.md |   14 +-
 .../index.md                                  |    6 +-
 translations/zh-CN/content/admin/index.md     |    5 +-
 ...talling-github-enterprise-server-on-aws.md |    5 +-
 ...ing-github-enterprise-server-on-hyper-v.md |    3 +-
 ...thub-enterprise-server-on-openstack-kvm.md |    3 +-
 ...ling-github-enterprise-server-on-vmware.md |    3 +-
 ...g-github-enterprise-server-on-xenserver.md |    3 +-
 .../activity-dashboard.md                     |    1 +
 .../exploring-user-activity/index.md          |   17 +
 .../log-forwarding.md                         |    1 +
 .../managing-global-webhooks.md               |    1 +
 .../viewing-push-logs.md                      |    3 +-
 .../index.md                                  |   17 +
 ...about-the-audit-log-for-your-enterprise.md |   61 +
 ...ssing-the-audit-log-for-your-enterprise.md |   28 +
 .../audit-log-events-for-your-enterprise.md   | 1249 +++++++++++++++++
 ...-audit-log-activity-for-your-enterprise.md |   51 +
 .../index.md                                  |   20 +
 ...ching-the-audit-log-for-your-enterprise.md |  130 ++
 ...ming-the-audit-log-for-your-enterprise.md} |   22 +-
 ...g-the-audit-log-api-for-your-enterprise.md |  143 ++
 .../content/admin/overview/system-overview.md |   36 +-
 ...-management-policies-in-your-enterprise.md |    2 +-
 .../content/admin/user-management/index.md    |    3 +-
 .../index.md                                  |    2 -
 ...n-organization-owned-by-your-enterprise.md |   38 +-
 .../restoring-a-deleted-organization.md       |   52 +-
 ...gs-for-organizations-in-your-enterprise.md |   36 -
 .../auditing-users-across-your-enterprise.md  |    2 +-
 ...izing-user-messages-for-your-enterprise.md |    2 +-
 .../impersonating-a-user.md                   |    2 +-
 .../removing-a-member-from-your-enterprise.md |   24 +-
 .../audit-logging.md                          |   48 -
 .../audited-actions.md                        |  198 ---
 .../index.md                                  |   23 -
 .../searching-the-audit-log.md                |   51 -
 ...-token-for-use-with-saml-single-sign-on.md |    2 +
 ...sh-key-for-use-with-saml-single-sign-on.md |    2 +
 .../telling-git-about-your-signing-key.md     |    2 +-
 ...ne-time-payments-for-customers-in-india.md |   46 +-
 .../configuring-code-scanning.md              |    2 +-
 ...configuring-dependabot-security-updates.md |    2 +-
 .../about-dependabot-version-updates.md       |    2 +-
 ...ion-options-for-the-dependabot.yml-file.md |   86 +-
 ...-disclosure-of-security-vulnerabilities.md |    4 +-
 ...ub-security-advisories-for-repositories.md |   14 +-
 ...rator-to-a-repository-security-advisory.md |   14 +-
 ...lve-a-repository-security-vulnerability.md |   12 +-
 ...creating-a-repository-security-advisory.md |   12 +-
 .../editing-a-repository-security-advisory.md |   10 +-
 .../repository-security-advisories/index.md   |    6 +-
 ...vels-for-repository-security-advisories.md |   42 +-
 ...blishing-a-repository-security-advisory.md |   16 +-
 ...tor-from-a-repository-security-advisory.md |    8 +-
 ...hdrawing-a-repository-security-advisory.md |    8 +-
 .../secret-scanning/about-secret-scanning.md  |    7 +
 ...g-secret-scanning-for-your-repositories.md |    6 +-
 ...ing-custom-patterns-for-secret-scanning.md |   14 +-
 .../code-security/secret-scanning/index.md    |    1 +
 .../protecting-pushes-with-secret-scanning.md |   87 ++
 .../secret-scanning-patterns.md               |   10 +-
 .../about-the-security-overview.md            |    6 +-
 ...ltering-alerts-in-the-security-overview.md |   10 +-
 .../viewing-the-security-overview.md          |    4 +-
 .../end-to-end-supply-chain-overview.md       |   26 +-
 .../end-to-end-supply-chain/index.md          |    4 +-
 .../securing-accounts.md                      |    5 +-
 .../securing-builds.md                        |   50 +-
 .../end-to-end-supply-chain/securing-code.md  |   12 +-
 .../about-dependency-review.md                |   14 +
 ...loring-the-dependencies-of-a-repository.md |    4 +-
 .../security-in-codespaces.md                 |    2 +
 .../forwarding-ports-in-your-codespace.md     |   16 +-
 .../codespaces/getting-started/quickstart.md  |    2 +-
 .../index.md                                  |    1 +
 .../restricting-access-to-machine-types.md    |    2 +-
 ...cting-the-visibility-of-forwarded-ports.md |   83 ++
 .../about-codespaces-prebuilds.md             |   36 +-
 .../configuring-prebuilds.md                  |   64 +-
 .../prebuilding-your-codespaces/index.md      |    4 +-
 .../managing-prebuilds.md                     |  104 +-
 .../testing-dev-container-changes.md          |   22 +-
 ...shooting-port-forwarding-for-codespaces.md |    2 +
 .../troubleshooting-prebuilds.md              |   44 +-
 .../blocking-a-user-from-your-organization.md |    4 +-
 ...nblocking-a-user-from-your-organization.md |    8 +-
 ...iting-interactions-in-your-organization.md |   10 +-
 ...imiting-interactions-in-your-repository.md |    5 +-
 .../managing-disruptive-comments.md           |    9 +-
 ...out-community-management-and-moderation.md |    2 +
 ...ing-issue-templates-for-your-repository.md |    2 +-
 .../configuring-a-default-editor.md           |   10 +
 .../about-discussions.md                      |   27 +-
 ...ting-with-maintainers-using-discussions.md |   18 +-
 .../participating-in-a-discussion.md          |   12 +-
 ...s-for-community-conversations-on-github.md |   15 +-
 ...itories.md => finding-your-discussions.md} |    6 +-
 ...-higher-permissions-to-top-contributors.md |    6 +-
 .../zh-CN/content/discussions/guides/index.md |    2 +-
 .../zh-CN/content/discussions/index.md        |    4 +-
 .../index.md                                  |    4 +-
 ...=> managing-categories-for-discussions.md} |   29 +-
 ...-repository.md => managing-discussions.md} |   36 +-
 .../moderating-discussions.md                 |   12 +-
 .../viewing-insights-for-your-discussions.md  |    6 +-
 .../zh-CN/content/discussions/quickstart.md   |   32 +-
 ...education-for-educators-and-researchers.md |    3 +-
 ...-for-an-educator-or-researcher-discount.md |    2 +-
 .../zh-CN/content/education/guides.md         |    2 +-
 .../create-a-group-assignment.md              |    2 +
 ...n-assignment-from-a-template-repository.md |    2 +
 .../create-an-individual-assignment.md        |    2 +
 .../teach-with-github-classroom/index.md      |    1 +
 .../manage-classrooms.md                      |    4 +-
 .../reuse-an-assignment.md                    |   38 +
 ...e-the-git-and-github-starter-assignment.md |    2 +-
 .../adding-locally-hosted-code-to-github.md   |   70 +-
 .../about-github-advanced-security.md         |    2 +-
 .../learning-about-github/githubs-products.md |    2 +-
 .../getting-started-with-github-ae.md         |    8 +-
 ...ng-started-with-github-enterprise-cloud.md |    2 +-
 ...g-started-with-github-enterprise-server.md |    2 +-
 ...se-settings-for-your-private-repository.md |    2 +-
 .../get-started/quickstart/fork-a-repo.md     |    2 +-
 .../using-github/github-command-palette.md    |    4 +-
 .../using-github/supported-browsers.md        |   25 +-
 .../basic-writing-and-formatting-syntax.md    |    6 +
 .../creating-and-highlighting-code-blocks.md  |    2 +-
 .../creating-a-branch-for-an-issue.md         |   26 +-
 .../creating-a-project.md                     |   24 +-
 .../filtering-projects.md                     |   14 +-
 .../managing-iterations.md                    |   56 +-
 .../using-insights-with-projects.md           |   40 +-
 .../accessing-your-organizations-settings.md  |    2 +-
 .../viewing-insights-for-your-organization.md |    9 +-
 .../about-team-discussions.md                 |    8 +
 ...ompliance-reports-for-your-organization.md |    7 +
 ...analysis-settings-for-your-organization.md |    3 +-
 ...ail-notifications-for-your-organization.md |    8 +
 ...ing-the-audit-log-for-your-organization.md |   44 +-
 ...ation-member-to-an-outside-collaborator.md |   10 +
 ...llaborators-access-to-your-organization.md |    2 +-
 .../repository-roles-for-an-organization.md   |   12 +-
 .../about-ssh-certificate-authorities.md      |    2 +
 .../index.md                                  |    1 +
 ...ganizations-ssh-certificate-authorities.md |    5 +-
 ...-github-discussions-for-an-organization.md |   27 +
 .../managing-organization-settings/index.md   |    1 +
 ...n-for-repositories-in-your-organization.md |    3 +-
 ...ll-request-reviews-in-your-organization.md |    2 +-
 ...epository-creation-in-your-organization.md |    4 +-
 ...ssions-for-adding-outside-collaborators.md |    3 +-
 .../index.md                                  |    1 +
 ...anaging-moderators-in-your-organization.md |   40 +
 .../roles-in-an-organization.md               |  282 ++--
 ...ess-management-with-saml-single-sign-on.md |    2 +
 .../about-scim.md                             |    4 +-
 ...saml-single-sign-on-and-scim-using-okta.md |    2 +
 ...-identity-provider-to-your-organization.md |    2 +
 ...ml-single-sign-on-for-your-organization.md |    2 +
 ...ml-single-sign-on-for-your-organization.md |    2 +
 .../index.md                                  |    1 +
 ...m-synchronization-for-your-organization.md |    2 +
 ...aml-single-sign-on-in-your-organization.md |    2 +
 .../introduction-to-github-packages.md        |    2 +-
 ...he-visibility-of-your-github-pages-site.md |    8 +-
 ...rging-a-pull-request-with-a-merge-queue.md |    2 +-
 ...ng-dependency-changes-in-a-pull-request.md |    4 +
 .../about-protected-branches.md               |    8 +
 .../managing-a-branch-protection-rule.md      |    3 +
 .../about-readmes.md                          |    4 +-
 ...g-your-repositorys-social-media-preview.md |   19 +-
 ...ing-github-discussions-for-a-repository.md |    2 +
 ...d-analysis-settings-for-your-repository.md |    8 +-
 .../configuring-tag-protection-rules.md       |   20 +-
 ...-objects-in-archives-of-your-repository.md |    4 +-
 .../configuring-git-large-file-storage.md     |   10 +-
 .../zh-CN/content/rest/overview/libraries.md  |    8 +-
 .../rest/reference/dependency-graph.md        |   16 +
 .../zh-CN/content/rest/reference/index.md     |    1 +
 .../searching-on-github/searching-code.md     |    2 +-
 .../github-acceptable-use-policies.md         |   62 +-
 .../github-active-malware-or-exploits.md      |    8 +-
 ...isrupting-the-experience-of-other-users.md |   22 +-
 .../github-doxxing-and-invasion-of-privacy.md |   28 +-
 .../github-hate-speech-and-discrimination.md  |   22 +-
 .../github-impersonation.md                   |   18 +-
 ...ithub-misinformation-and-disinformation.md |   16 +-
 .../github-sexually-obscene-content.md        |   12 +-
 ...olence-and-gratuitously-violent-content.md |   14 +-
 .../content-removal-policies/index.md         |    2 +-
 ...-against-modern-slavery-and-child-labor.md |    2 +-
 .../github-company-policies/index.md          |    2 +-
 .../github-community-forum-code-of-conduct.md |   24 +-
 .../github-community-guidelines.md            |   12 +-
 .../github-corporate-terms-of-service.md      |   34 +-
 .../github-marketplace-developer-agreement.md |    8 +-
 .../github-marketplace-terms-of-service.md    |    4 +-
 ...ms-for-additional-products-and-features.md |   22 +-
 .../github-terms/github-terms-of-service.md   |    2 +-
 .../content/site-policy/github-terms/index.md |    2 +-
 .../site-policy/other-site-policies/index.md  |    2 +-
 .../github-data-protection-agreement.md       |   24 +-
 .../github-privacy-statement.md               |    4 +-
 .../site-policy/privacy-policies/index.md     |    2 +-
 ...-disclosure-of-security-vulnerabilities.md |    6 +-
 .../site-policy/security-policies/index.md    |    2 +-
 .../index.md                                  |    1 -
 .../sponsors-for-companies.md                 |   41 -
 .../paying-for-github-sponsors-by-invoice.md  |    1 -
 .../providing-data-to-github-support.md       |    2 +-
 .../data/features/job-hooks-for-runners.yml   |    2 +
 ...ent-org-admin-add-outside-collaborator.yml |    5 +
 .../data/features/required-deployments.yml    |    8 +
 .../features/secret-scanning-org-dry-runs.yml |    7 +
 .../secret-scanning-push-protection.yml       |    7 +
 .../data/learning-tracks/code-security.yml    |    2 +-
 .../enterprise-server/3-1/19.yml              |   42 +
 .../enterprise-server/3-2/11.yml              |   44 +
 .../release-notes/enterprise-server/3-3/0.yml |    1 +
 .../release-notes/enterprise-server/3-3/1.yml |    1 +
 .../release-notes/enterprise-server/3-3/2.yml |    1 +
 .../release-notes/enterprise-server/3-3/3.yml |    1 +
 .../release-notes/enterprise-server/3-3/4.yml |    1 +
 .../release-notes/enterprise-server/3-3/5.yml |    1 +
 .../release-notes/enterprise-server/3-3/6.yml |   50 +
 .../release-notes/enterprise-server/3-4/1.yml |   93 ++
 .../secret-scanning-dry-run-results.md        |    3 +
 .../secret-scanning-push-protection-org.md    |    2 +
 .../secret-scanning-push-protection-repo.md   |    1 +
 .../audit_log/audit-log-action-categories.md  |  158 +++
 .../audit_log/audit-log-events-workflows.md   |    9 +
 .../audit-log-search-by-operation.md          |   11 +
 .../audit_log/audit-log-search-by-repo.md     |    9 +
 .../audit_log/audit-log-search-by-user.md     |    9 +
 ...audit-log-search-list-info-about-action.md |   11 +
 .../reusables/audit_log/audit-log-search.md   |   40 +-
 .../reusables/audit_log/audited-data-list.md  |    2 +-
 .../exported-git-log-keys-and-values.md       |   13 +
 .../audit_log/exported-log-keys-and-values.md |   32 +-
 .../reusables/audit_log/retention-periods.md  |    3 +
 .../classroom/reuse-assignment-link.md        |    1 +
 .../about-analysis-origins-link.md            |    2 +-
 .../codespaces/restrict-port-visibility.md    |    1 +
 .../dependabot/supported-package-managers.md  |   56 +-
 .../dependency-review-action-beta-note.md     |    5 +
 .../dependency-review-api-beta-note.md        |    5 +
 .../about-categories-and-formats.md           |    2 +-
 .../discussions/about-discussions.md          |    2 +-
 .../about-organization-discussions.md         |    5 +
 .../reusables/discussions/discussions-tab.md  |    2 +-
 ...ithub-discussions-for-your-organization.md |    5 +
 .../marking-a-comment-as-an-answer.md         |    2 +-
 .../discussions/navigate-to-repo-or-org.md    |    1 +
 .../discussions/repository-category-limit.md  |    2 +-
 .../discussions/starting-a-discussion.md      |    3 +-
 .../reusables/discussions/starting-a-poll.md  |    9 +
 .../download-recovery-codes.md                |    2 +-
 .../reusables/enterprise/link-to-ghe-trial.md |    1 +
 .../download-appliance.md                     |    6 +-
 .../download-license.md                       |    2 +-
 .../enterprise-download-procedural.md         |    1 -
 .../gated-features/more-info-org-products.md  |    2 +-
 .../gated-features/secret-scanning.md         |    2 +-
 .../reusables/organizations/block_users.md    |    2 +-
 .../organizations/moderation-settings.md      |    1 -
 .../organizations/ssh-ca-ghec-only.md         |    8 +
 ...navigate-to-code-security-and-analysis.md} |    2 +-
 .../dependency-graph/dependency-review.md     |    5 +
 .../secret-scanning/secret-scanning.md        |    2 +-
 .../reusables/saml/authorized-creds-info.md   |    2 +-
 .../zh-CN/data/reusables/saml/ghec-only.md    |    7 +
 .../saml/must-authorize-linked-identity.md    |    5 +
 .../secret-scanning/partner-program-link.md   |    2 +-
 .../secret-scanning/push-protection-beta.md   |    5 +
 .../push-protection-overview.md               |    1 +
 .../secret-list-private-push-protection.md    |   71 +
 .../repository-level-advisory-note.md         |    2 +-
 .../reusables/support/view-open-tickets.md    |    4 +-
 .../secret_scanning_alert_event_short_desc.md |    2 +-
 ...canning_alert_location_event_short_desc.md |    2 +-
 translations/zh-CN/data/variables/product.yml |    5 +-
 310 files changed, 4483 insertions(+), 1853 deletions(-)
 create mode 100644 translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
 delete mode 100644 translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md
 rename translations/zh-CN/content/admin/{user-management/monitoring-activity-in-your-enterprise => monitoring-activity-in-your-enterprise/exploring-user-activity}/activity-dashboard.md (91%)
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
 rename translations/zh-CN/content/admin/{user-management/monitoring-activity-in-your-enterprise => monitoring-activity-in-your-enterprise/exploring-user-activity}/log-forwarding.md (98%)
 rename translations/zh-CN/content/admin/{user-management/monitoring-activity-in-your-enterprise => monitoring-activity-in-your-enterprise/exploring-user-activity}/managing-global-webhooks.md (98%)
 rename translations/zh-CN/content/admin/{user-management/monitoring-activity-in-your-enterprise => monitoring-activity-in-your-enterprise/exploring-user-activity}/viewing-push-logs.md (90%)
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/index.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
 rename translations/zh-CN/content/admin/{user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md => monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md} (90%)
 create mode 100644 translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
 delete mode 100644 translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
 delete mode 100644 translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
 delete mode 100644 translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
 delete mode 100644 translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md
 delete mode 100644 translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
 create mode 100644 translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
 create mode 100644 translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
 rename translations/zh-CN/content/discussions/guides/{finding-discussions-across-multiple-repositories.md => finding-your-discussions.md} (81%)
 rename translations/zh-CN/content/discussions/managing-discussions-for-your-community/{managing-categories-for-discussions-in-your-repository.md => managing-categories-for-discussions.md} (67%)
 rename translations/zh-CN/content/discussions/managing-discussions-for-your-community/{managing-discussions-in-your-repository.md => managing-discussions.md} (67%)
 create mode 100644 translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
 create mode 100644 translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
 create mode 100644 translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
 create mode 100644 translations/zh-CN/content/rest/reference/dependency-graph.md
 delete mode 100644 translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md
 create mode 100644 translations/zh-CN/data/features/prevent-org-admin-add-outside-collaborator.yml
 create mode 100644 translations/zh-CN/data/features/required-deployments.yml
 create mode 100644 translations/zh-CN/data/features/secret-scanning-org-dry-runs.yml
 create mode 100644 translations/zh-CN/data/features/secret-scanning-push-protection.yml
 create mode 100644 translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml
 create mode 100644 translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml
 create mode 100644 translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml
 create mode 100644 translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md
 create mode 100644 translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-search-by-operation.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-search-by-repo.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-search-by-user.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/audit-log-search-list-info-about-action.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/exported-git-log-keys-and-values.md
 create mode 100644 translations/zh-CN/data/reusables/audit_log/retention-periods.md
 create mode 100644 translations/zh-CN/data/reusables/classroom/reuse-assignment-link.md
 create mode 100644 translations/zh-CN/data/reusables/codespaces/restrict-port-visibility.md
 create mode 100644 translations/zh-CN/data/reusables/dependency-review/dependency-review-action-beta-note.md
 create mode 100644 translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md
 create mode 100644 translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
 create mode 100644 translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
 create mode 100644 translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md
 create mode 100644 translations/zh-CN/data/reusables/discussions/starting-a-poll.md
 create mode 100644 translations/zh-CN/data/reusables/enterprise/link-to-ghe-trial.md
 delete mode 100644 translations/zh-CN/data/reusables/enterprise_installation/enterprise-download-procedural.md
 delete mode 100644 translations/zh-CN/data/reusables/organizations/moderation-settings.md
 create mode 100644 translations/zh-CN/data/reusables/organizations/ssh-ca-ghec-only.md
 rename translations/zh-CN/data/reusables/repositories/{navigate-to-security-and-analysis.md => navigate-to-code-security-and-analysis.md} (80%)
 create mode 100644 translations/zh-CN/data/reusables/rest-reference/dependency-graph/dependency-review.md
 create mode 100644 translations/zh-CN/data/reusables/saml/ghec-only.md
 create mode 100644 translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md
 create mode 100644 translations/zh-CN/data/reusables/secret-scanning/push-protection-beta.md
 create mode 100644 translations/zh-CN/data/reusables/secret-scanning/push-protection-overview.md
 create mode 100644 translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md

diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv
index 92090bcc42..9a4998ed98 100644
--- a/translations/log/cn-resets.csv
+++ b/translations/log/cn-resets.csv
@@ -26,7 +26,9 @@ translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-arti
 translations/zh-CN/content/actions/using-workflows/using-github-cli-in-workflows.md,broken liquid tags
 translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags
 translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,broken liquid tags
+translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/about-supply-chain-security-for-your-enterprise.md,broken liquid tags
+translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,rendering error
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags
 translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md,broken liquid tags
@@ -152,6 +154,8 @@ translations/zh-CN/content/code-security/getting-started/github-security-feature
 translations/zh-CN/content/code-security/getting-started/securing-your-organization.md,broken liquid tags
 translations/zh-CN/content/code-security/getting-started/securing-your-repository.md,broken liquid tags
 translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md,broken liquid tags
+translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md,broken liquid tags
+translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md,broken liquid tags
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,Listed in localization-support#489
 translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md,broken liquid tags
@@ -194,6 +198,7 @@ translations/zh-CN/content/get-started/customizing-your-github-workflow/explorin
 translations/zh-CN/content/get-started/customizing-your-github-workflow/index.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,broken liquid tags
 translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,broken liquid tags
+translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
 translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,broken liquid tags
 translations/zh-CN/content/get-started/learning-about-github/about-versions-of-github-docs.md,broken liquid tags
 translations/zh-CN/content/get-started/learning-about-github/githubs-products.md,rendering error
@@ -284,7 +289,6 @@ translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-
 translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/code-scanning/upload-sarif-ghas.md,broken liquid tags
 translations/zh-CN/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_installation/download-appliance.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags
 translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags
@@ -303,7 +307,7 @@ translations/zh-CN/data/reusables/rest-reference/activity/events.md,broken liqui
 translations/zh-CN/data/reusables/rest-reference/apps/marketplace.md,broken liquid tags
 translations/zh-CN/data/reusables/rest-reference/packages/packages.md,broken liquid tags
 translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489
-translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
+translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags
 translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags
 translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
 translations/zh-CN/data/reusables/sponsors/feedback.md,broken liquid tags
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
index e6ea30d81f..110fd7f44a 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization.md
@@ -35,7 +35,7 @@ shortTitle: 查看组织中的人员
 
 如果您的组织由企业帐户管理，则可以查看管理企业所有组织的帐单设置和策略的企业所有者。 有关企业帐户的详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 帐户类型](/get-started/learning-about-github/types-of-github-accounts)”。
 
-您还可以查看企业所有者是否在组织中具有特定角色。 Enterprise owners can also be an organization member, any other organization role, or be un-affiliated with the organization.
+您还可以查看企业所有者是否在组织中具有特定角色。 企业所有者也可以是组织成员、任何其他组织角色或与组织无关。
 
 {% note %}
 
@@ -43,11 +43,11 @@ shortTitle: 查看组织中的人员
 
 {% endnote %}
 
-| **企业角色** | **组织角色**                                       | **组织访问或影响**                    |
-| -------- | ---------------------------------------------- | ------------------------------ |
-| 企业所有者    | Un-affiliated or no official organization role | 无法访问组织内容或存储库，但可管理影响组织的企业设置和策略。 |
-| 企业所有者    | 组织所有者                                          | 能够配置组织设置并通过团队等管理对组织资源的访问。      |
-| 企业所有者    | 组织成员                                           | 能够访问组织资源和内容（如存储库），而无需访问组织的设置。  |
+| **企业角色** | **组织角色**    | **组织访问或影响**                    |
+| -------- | ----------- | ------------------------------ |
+| 企业所有者    | 非附属或无官方组织角色 | 无法访问组织内容或存储库，但可管理影响组织的企业设置和策略。 |
+| 企业所有者    | 组织所有者       | 能够配置组织设置并通过团队等管理对组织资源的访问。      |
+| 企业所有者    | 组织成员        | 能够访问组织资源和内容（如存储库），而无需访问组织的设置。  |
 
 要查看组织中的所有角色，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 {% ifversion ghec %} 组织成员还可以具有特定存储库的自定义角色。 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。{% endif %}
 
diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
index b836c1139b..0a9a87d96b 100644
--- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
+++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md
@@ -71,6 +71,14 @@ Environments are used to describe a general deployment target like `production`,
 
 {% data reusables.actions.permissions-statement-environment %}
 
+{% ifversion fpt or ghec %}
+{% note %}
+
+**注意：**要在私有存储库中创建环境，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.actions.sidebar-environment %}
@@ -117,7 +125,7 @@ Environments are used to describe a general deployment target like `production`,
 1. 在要删除的环境旁边，单击 {% octicon "trash" aria-label="The trash icon" %}。
 2. 单击 **I understand, delete this environment（我了解，删除此环境）**。
 
-{% ifversion fpt or ghae or ghes > 3.1 or ghec %}您也可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %}
+{% ifversion fpt or ghae or ghes > 3.1 or ghec %}您还可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %}
 
 ## 环境与部署的关系
 
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
index 5e043c8bd2..7cba4e26c8 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/autoscaling-with-self-hosted-runners.md
@@ -58,10 +58,10 @@ type: overview
 
 默认情况下，每当有新版本的运行器软件可用时，自托管运行器将自动执行软件更新。  如果在容器中使用临时运行器，则当发布新的运行器版本时，这可能会导致重复的软件更新。  关闭自动更新允许你按照自己的计划直接更新容器映像上的运行器版本。
 
-如果要关闭自动软件更新并自行安装软件更新，可以在启动运行器时指定 `--disableupdate` 参数。  例如：
+要关闭自动软件更新并自行安装软件更新，请在使用 `config.sh`注册运行器时指定 `--disableupdate` 标志。 例如：
 
 ```shell
-./run.sh --disableupdate
+./config.sh --url <em>https://github.com/octo-org</em> --token <em>example-token</em> --disableupdate
 ```
 
 如果禁用自动更新，您仍必须定期更新运行器版本。  {% data variables.product.prodname_actions %} 中的新功能需要更改 {% data variables.product.prodname_actions %} 服务_和_运行器软件 。  在没有软件更新的情况下，运行器可能无法正确处理利用 {% data variables.product.prodname_actions %} 新功能的作业。
diff --git a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
index 39fa8cbe1b..96ba97080e 100644
--- a/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
+++ b/translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md
@@ -81,7 +81,7 @@ shortTitle: 启动时运行运行器应用程序
 该命令采用可选的 `user` 参数，以其他用户身份安装服务。
 
 ```shell
-./svc.sh install --user <em>USERNAME</em>
+./svc.sh install <em>USERNAME</em>
 ```
 
 ## 启动服务
diff --git a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
index 815310a1d0..b6132e0474 100644
--- a/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md
@@ -192,7 +192,7 @@ _操作_是 {% data variables.product.prodname_actions %} 平台的自定义应
   ```
 </td>
 <td>
-<code>uses</code> 关键字指定此步骤将运行 <code>actions/checkout</code> 操作的 <code>v2</code>。  这是一个将存储库签出到运行器上的操作，允许您对代码（如生成和测试工具）运行脚本或其他操作。 每当工作流程将针对存储库的代码运行时，都应使用签出操作。
+The <code>uses</code> keyword specifies that this step will run <code>v3</code> of the <code>actions/checkout</code> action.  这是一个将存储库签出到运行器上的操作，允许您对代码（如生成和测试工具）运行脚本或其他操作。 每当工作流程将针对存储库的代码运行时，都应使用签出操作。
 </td>
 </tr>
 <tr>
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 d6f643094d..efbb783477 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
@@ -48,6 +48,12 @@ To help prevent accidental disclosure, {% data variables.product.product_name %}
 - **Consider requiring review for access to secrets**
     - You can use required reviewers to protect environment secrets. A workflow job cannot access environment secrets until approval is granted by a reviewer. For more information about storing secrets in environments or requiring reviews for environments, see "[Encrypted secrets](/actions/reference/encrypted-secrets)" and "[Using environments for deployment](/actions/deployment/using-environments-for-deployment)."
 
+{% warning %}
+
+**Warning**: Any user with write access to your repository has read access to all secrets configured in your repository. Therefore, you should ensure that the credentials being used within workflows have the least privileges required.
+
+{% endwarning %}
+
 ## Using `CODEOWNERS` to monitor changes
 
 You can use the `CODEOWNERS` feature to control how changes are made to your workflow files. For example, if all your workflow files are stored in `.github/workflows`, you can add this directory to the code owners list, so that any proposed changes to these files will first require approval from a designated reviewer.
@@ -300,7 +306,7 @@ For example, you can use the audit log to track the `org.update_actions_secret`
   ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
 
 The following tables describe the {% data variables.product.prodname_actions %} events that you can find in the audit log. For more information on using the audit log, see
-"[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
+"[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)" and "[Reviewing audit logs for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)."
 
 {% ifversion fpt or ghec %}
 ### Events for environments
@@ -318,6 +324,7 @@ The following tables describe the {% data variables.product.prodname_actions %}
 | Action | Description
 |------------------|-------------------
 | `repo.actions_enabled` | Triggered when {% data variables.product.prodname_actions %} is enabled for a repository. Can be viewed using the UI. This event is not visible when you access the audit log using the REST API. For more information, see "[Using the REST API](#using-the-rest-api)."
+| `repo.update_actions_access_settings` | Triggered when the setting to control how your repository is used by {% data variables.product.prodname_actions %} workflows in other repositories is changed.
 {% endif %}
 
 ### Events for secret management
diff --git a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
index 208f893772..9d9cfa91e0 100644
--- a/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
+++ b/translations/zh-CN/content/actions/using-containerized-services/about-service-containers.md
@@ -49,7 +49,7 @@ topics:
 
 您可以使用 `services` 关键字创建服务容器作为工作流程中作业的一部分。 更多信息请参阅 [`jobs.<job_id>.services`](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idservices)。
 
-本例在作业 `container-job` 中创建一个名为 `redis` 的服务。 本例中的 Docker 主机是 `node:10.18-jessie` 容器。
+本例在作业 `container-job` 中创建一个名为 `redis` 的服务。 本例中的 Docker 主机是 `node:16-bullseye` 容器。
 
 {% raw %}
 ```yaml{:copy}
@@ -62,7 +62,7 @@ jobs:
     # Containers must run in Linux based operating systems
     runs-on: ubuntu-latest
     # Docker Hub image that `container-job` executes in
-    container: node:10.18-jessie
+    container: node:16-bullseye
 
     # Service containers to run with `container-job`
     services:
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
index f1d8a12e1f..8abdf0f058 100644
--- 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
@@ -1,30 +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.'
+title: 监控您当前的作业
+intro: '监控 {% data variables.product.prodname_dotcom %} 托管的运行器如何处理组织或企业中的作业，并了解任何相关约束。'
 versions:
   feature: github-runner-dashboard
-shortTitle: Monitoring your current jobs
+shortTitle: 监控您当前的作业
 ---
 
 {% 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 variables.product.prodname_dotcom %} 托管的运行器上运行的所有作业列表。
 
 {% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
 {% data reusables.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.
+1. 查看“Active jobs（活动作业）”部分，其中包含当前在 {% data variables.product.prodname_dotcom %} 托管的运行器上运行的所有作业列表。
 
-  ![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png)
+  ![活动作业列表的屏幕截图](/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)."
+{% data variables.product.prodname_dotcom %} 托管的运行器允许您并发运行作业，并且并发作业的最大数量将根据您的计划而有所不同。 如果达到最大并发作业数，则任何新作业都将开始进入队列。 若要了解有关计划可用的并发作业数的详细信息，请参阅“[使用限制、计费和管理](/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.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
 {% data reusables.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)
+1. 查看“All jobs usage（所有作业使用情况）”部分，其中列出了活动作业数和可以运行的最大作业数。 在此示例中， `9` 个作业正在运行，最大作业数为 `180`。 ![帐户的最大作业数屏幕截图](/assets/images/help/settings/github-hosted-runners-max-jobs.png)
diff --git a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
index 57e8fbdb8d..f018757f32 100644
--- a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
+++ b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md
@@ -24,13 +24,13 @@ topics:
 
 要缓存作业的依赖项，您需要使用 {% data variables.product.prodname_dotcom %} 的 `cache` 操作。 该操作检索由唯一键标识的缓存。 更多信息请参阅 [`actions/cache`](https://github.com/actions/cache)。
 
-If you are caching the package managers listed below, consider using the respective setup-* actions, which require almost zero configuration and are easy to use.
+如果要缓存下面列出的包管理器，请考虑使用相应的 setup-* 操作，这些操作几乎不需要任何配置，并且易于使用。
 
 <table>
 <thead>
   <tr>
-    <th>Package managers</th>
-    <th>setup-* action for caching</th>
+    <th>包管理器</th>
+    <th>用于缓存的 setup-* 操作</th>
   </tr>
 </thead>
 <tbody>
@@ -89,7 +89,7 @@ If you are caching the package managers listed below, consider using the respect
 ### `cache` 操作的输入参数
 
 - `key`：**必要** 保存缓存时创建的键，以及用于搜索缓存的键。 可以是变量、上下文值、静态字符串和函数的任何组合。 密钥最大长度为 512 个字符，密钥长度超过最大长度将导致操作失败。
-- `path`：**必要** 运行器上缓存或还原的文件路径。 The path can be an absolute path or relative to the workspace directory.
+- `path`：**必要** 运行器上缓存或还原的文件路径。 路径可以是绝对路径或相对于工作区目录的路径。
   - 路径可以是目录或单个文件，并且支持 glob 模式。
   - 使用 `cache` 操作的 `v2`，可以指定单个路径，也可以在单独的行上添加多个路径。 例如：
 
@@ -102,7 +102,16 @@ If you are caching the package managers listed below, consider using the respect
           ~/.gradle/wrapper
     ```
   - 对于 `cache` 操作的 `v1`，仅支持单个路径，它必须是一个目录。 您不能缓存单个文件。
-- `restore-keys`：**可选** `key` 没有发生缓存命中时用于查找缓存的其他密钥顺序列表。
+- `restore-keys`：**可选** 包含备用恢复键的字符串，每个恢复键都放在新行上。 如果 `key` 未发生缓存命中，则按提供的查找和恢复缓存的顺序使用这些恢复密钥。 例如：
+
+  {% raw %}
+  ```yaml
+  restore-keys: |
+    npm-foobar-${{ hashFiles('package-lock.json') }}
+    npm-foobar-
+    npm-
+  ```
+  {% endraw %}
 
 ### `cache` 操作的输出参数
 
@@ -232,12 +241,12 @@ restore-keys: |
 
 ## 使用限制和收回政策
 
-{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. If you exceed this limit, {% data variables.product.prodname_dotcom %} will save your cache but will begin evicting caches until the total size is less than 10 GB.
+{% data variables.product.prodname_dotcom %} 将删除 7 天内未被访问的任何缓存条目。 可以存储的缓存数没有限制，但存储库中所有缓存的总大小限制为 10 GB。 如果超过此限制，{% data variables.product.prodname_dotcom %} 将保存缓存，但会开始收回缓存，直到总大小小于 10 GB。
 
 {% if actions-cache-management %}
 
-## Managing caches
+## 管理缓存
 
-You can use the {% data variables.product.product_name %} REST API to manage your caches. At present, you can use the API to see your cache usage, with more functionality expected in future updates. For more information, see the "[Actions](/rest/reference/actions#cache)" REST API documentation.
+您可以使用 {% data variables.product.product_name %} REST API 来管理缓存。 目前，您可以使用 API 来查看缓存使用情况，并期望在未来的更新中提供更多功能。 更多信息请参阅 REST API 文档中的“[操作](/rest/reference/actions#cache)”。
 
 {% endif %}
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 51237fa2e3..ca106c8fda 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
@@ -899,7 +899,7 @@ on:
 
 jobs:
   if_merged:
-    if: github.event.pull_request_target.merged == true
+    if: github.event.pull_request.merged == true
     runs-on: ubuntu-latest
     steps:
     - run: |
@@ -1081,7 +1081,7 @@ on:
 
 {% note %}
 
-**Note:** The `event_type` value is limited to 100 characters.
+**注意：** `event_type` 值限制为 100 个字符。
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/admin/code-security/index.md b/translations/zh-CN/content/admin/code-security/index.md
index ce85a61e40..e289e60d6c 100644
--- a/translations/zh-CN/content/admin/code-security/index.md
+++ b/translations/zh-CN/content/admin/code-security/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing code security for your enterprise
-shortTitle: Manage code security
-intro: 'You can build security into your developers'' workflow with features that keep secrets and vulnerabilities out of your codebase, and that maintain your software supply chain.'
+title: 管理企业的代码安全性
+shortTitle: 管理代码安全性
+intro: 您可以使用将机密和漏洞排除在代码库之外并维护软件供应链的功能，将安全性构建到开发人员的工作流程中。
 versions:
   ghes: '*'
   ghec: '*'
diff --git a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md
index 8443e15311..f8547c0cb5 100644
--- a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: 在企业中部署 GitHub Advanced Security
+title: Deploying GitHub Advanced Security in your enterprise
 intro: 'Learn how to plan, prepare, and implement a phased approach for rolling out {% data variables.product.prodname_GH_advanced_security %} (GHAS) in your enterprise.'
 product: '{% data reusables.gated-features.advanced-security %}'
 redirect_from:
@@ -82,10 +82,12 @@ We recommend you cover these topics in your internal kickoff meeting at your com
 
 - What are your business success metrics, how do you plan to measure and report on those measures?
   - If these have not been defined, please define them. If they have been defined, communicate them and talk about how you plan to provide data-driven progress updates.
-- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is expected to work for your company.
+- Review of how GHAS works within the SDLC (Software Development Life cycle) and how this is
+expected to work for your company.
 - Review of best practices if your company did not participate in the Proof of Concept exercise (or a refresher if your team finds value in this review)
   - How does this compare/contrast with your existing Application Security Program?
-- Discuss and agree how your internal team will work best together throughout rollout and implementation.
+- Discuss and agree how your internal team will work best together throughout rollout and
+implementation.
   - Align on your communications plans and frequency of meetings for your internal team
   - Review tasks for rollout and implementation completion, defining roles and responsibilities. We have outlined the majority of the tasks in this article, but there may be additional tasks your company requires we have not included.
   - Consider establishing a “Champions Program” for scaled enablement
@@ -106,7 +108,8 @@ If you’re working independently, this section outlines some things to ensure a
 Plans for process changes (if needed) and training for team members as needed:
   - Documented team assignments for roles and responsibilities. For more information on the permissions required for each feature, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#access-requirements-for-security-features)."
   - Documented plan of tasks and timelines/timeframes where possible. This should include infrastructure changes, process changes/training, and all subsequent phases of enablement of GHAS, allowing for timeframes for remediations and configuration adjustments as needed. For more information, see "[Phase 1: Pilot projects(s)](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise#--phase-1-pilot-projects)" below.
-  - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent plans for which projects/teams will come in following phases
+  - Prioritized plan for which projects/teams will have GHAS enabled first, and subsequent
+plans for which projects/teams will come in following phases
   - Success metrics based on business goals. This will be a crucial reference point following the Pilot Project(s) to gain buy-in for the full rollout.
 
 {% note %}
@@ -119,11 +122,11 @@ Plans for process changes (if needed) and training for team members as needed:
 
 For {% data variables.product.prodname_ghe_server %} customers, to help ensure your instance can support the rollout and implementation of GHAS, review the following:
 
-- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. 更多信息请参阅“[升级 {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)。”
+- While upgrading to GHES 3.0 is not required, you must upgrade to GHES 3.0 or higher to take advantage of feature combinations such as code scanning and {% data variables.product.prodname_actions %}. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
 
-- 在高性能配置中，完全冗余的次级 {% data variables.product.prodname_ghe_server %} 设备通过复制所有主要数据存储与主设备保持同步。 For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)."
+- In a high availability configuration, a fully redundant secondary {% data variables.product.prodname_ghe_server %} appliance is kept in sync with the primary appliance through replication of all major datastores. For more information on setting up high availability, see "[Configuring High Availability](/admin/enterprise-management/configuring-high-availability)."
 
-- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. 更多信息请参阅“[系统概述](/admin/overview/system-overview)”。
+- To help support any discussions regarding potential changes to your company's set up, you can review the {% data variables.product.prodname_ghe_server %} system overview. For more information, see "[System overview](/admin/overview/system-overview)."
 
 {% endif %}
 
@@ -131,10 +134,12 @@ For {% data variables.product.prodname_ghe_server %} customers, to help ensure y
 
 As your company prepares to begin your pilot project(s), it’s crucial to ensure that you have set a baseline for where your enterprise is today and have defined clear success metrics to measure your pilot project(s) progress against.
 
-There are likely key business goals your company has that will need to be measured against, but there are other metrics we can identify to help gauge your pilot’s success.
+There are likely key business goals your company has that will need to be measured
+against, but there are other metrics we can identify to help gauge your pilot’s success.
 
 As a starting point, some of these metrics might include:
-  - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and practices the pilot project(s) / team(s) utilized.
+  - The mean time to remediation for GHAS vulnerabilities versus the previous tooling and
+practices the pilot project(s) / team(s) utilized.
   - The code scanning integration's findings for the top X most critical applications.
   - The number of applications that have SAST (Static application security testing) integrated versus before the engagement.
 
@@ -143,14 +148,20 @@ If you participated in the POC exercise prior to purchasing GHAS, these objectiv
   - Security / CISO (Chief Information Security Officer)
   - Application Development Teams
 
-If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main evaluation criteria in DSOMM:
+If you’d like to take things a step further, you can look at utilizing OWASP’s DevSecOps
+Maturity Model (DSOMM) to work towards reaching a Level 1 maturity. There are four main
+evaluation criteria in DSOMM:
 
-- **Static depth:** How comprehensive is the static code scan that you’re performing within the AppSec CI pipeline
-- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the AppSec CI pipeline
+- **Static depth:** How comprehensive is the static code scan that you’re performing within
+the AppSec CI pipeline
+- **Dynamic depth:** How comprehensive is the dynamic scan that is being run within the
+AppSec CI pipeline
 - **Intensity:** Your schedule frequency for the security scans running in AppSec CI pipeline
-- **Consolidation:** Your remediation workflow for handling findings and process completeness
+- **Consolidation:** Your remediation workflow for handling findings and process
+completeness
 
-To learn more about this approach and how to implement it in GHAS, you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)."
+To learn more about this approach and how to implement it in GHAS,
+you can download our white paper "[Achieving DevSecOps Maturity with GitHub](https://resources.github.com/whitepapers/achieving-devsecops-maturity-github/)."
 
 Based on your wider company’s goals and current levels of DevSecOps maturity, we can help you determine how to best measure your pilot’s progress and success.
 
@@ -162,7 +173,9 @@ Based on your wider company’s goals and current levels of DevSecOps maturity,
 
 {% endnote %}
 
-To begin enabling GHAS across your company, we recommend beginning with a few high-impact projects or teams to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company.
+To begin enabling GHAS across your company, we recommend beginning with a few
+high-impact projects or teams to pilot an initial rollout. This will allow an initial
+group within your company to get familiar with GHAS and build a solid foundation on GHAS before rolling out to the remainder of your company.
 
 Before you start your pilot project(s), we recommend that you schedule some checkpoint meetings for your team(s), such as an initial meeting, midpoint review, and a wrap-up session when the pilot is complete. These checkpoint meetings will help you all make adjustments as needed and ensure your team(s) are prepared and supported to complete the pilot successfully.
 
@@ -182,7 +195,7 @@ You need to enable GHAS for each pilot project, either by enabling the GHAS feat
 
 The vast majority of GHAS set-up and installation is centered around enabling and configuring code scanning on your enterprise and in your repositories.
 
-Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. 更多信息请参阅“[关于代码扫描](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)”。
+Code scanning allows you to analyze code in a {% data variables.product.prodname_dotcom %} repository to find security vulnerabilities and coding errors. Code scanning can be used to find, triage, and prioritize fixes for existing problems in your code, as well as help prevent developers from introducing new problems that may otherwise reach production. For more information, see "[About code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)."
 
 ### Step 2: Set up {% data variables.product.prodname_code_scanning_capc %}
 
@@ -198,23 +211,24 @@ To set up code scanning, you must decide whether you'll run code scanning with [
 
 {% ifversion ghes %}
 
-To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)."
+To set up code scanning with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}, you'll need to provision one or more self-hosted {% data variables.product.prodname_actions %} runners in your
+environment. For more information, see "[Setting up a self-hosted runner](/admin/advanced-security/configuring-code-scanning-for-your-appliance#running-code-scanning-using-github-actions)."
 
 {% endif %}
 
-For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners)”。
+For {% data variables.product.prodname_ghe_cloud %}, you can start to create a {% data variables.product.prodname_actions %} workflow using the [CodeQL action](https://github.com/github/codeql-action/) to run code scanning on a repository. {% data variables.product.prodname_code_scanning_capc %} uses [GitHub-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners) by default, but this can be customized if you plan to host your own runner with your own hardware specifications. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners)."
 
 For more information about {% data variables.product.prodname_actions %}, see:
   - "[Learn GitHub Actions](/actions/learn-github-actions)"
   - "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)"
-  - "[触发工作流程的事件](/actions/learn-github-actions/events-that-trigger-workflows)"
+  - "[Events that trigger workflows](/actions/learn-github-actions/events-that-trigger-workflows)"
   - "[Filter Pattern Cheat Sheet](/actions/learn-github-actions/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)"
 
 #### Using a third-party CI system with the CodeQL CLI for {% data variables.product.prodname_code_scanning %}
 
 If you’re not using {% data variables.product.prodname_actions %} and have your own continuous integration system, you can use the CodeQL CLI to perform CodeQL code scanning in a third-party CI system.
 
-更多信息请参阅：
+For more information, see:
   - "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)"
 
 ### Step 3: Enable {% data variables.product.prodname_code_scanning_capc %} in repositories
@@ -227,19 +241,24 @@ For an example of a script that opens pull requests to add a {% data variables.p
 
 ### Step 4: Run code scans and review your results
 
-With code scanning enabled in the necessary repositories, you're ready to help your development team(s) understand how to run code scans and reports, view reports, and process results.
+With code scanning enabled in the necessary repositories, you're ready to help your
+development team(s) understand how to run code scans and reports, view reports, and process results.
 
 #### {% data variables.product.prodname_code_scanning_capc %}
 
-With code scanning, you can find vulnerabilities and errors in your project's code on GitHub, as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts.
+With code scanning, you can find vulnerabilities and errors in your project's code on GitHub,
+as well as view, triage, understand, and resolve the related {% data variables.product.prodname_code_scanning %} alerts.
 
-When code scanning identifies a problem in a pull request, you can review the highlighted code and resolve the alert. 更多信息请参阅“[对拉取请求中的 {% data variables.product.prodname_code_scanning %} 警报分类](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)”。
+When code scanning identifies a problem in a pull request, you can review the highlighted
+code and resolve the alert. For more information, see "[Triaging {% data variables.product.prodname_code_scanning %} alerts in pull requests](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests)."
 
-If you have write permission to a repository you can manage code scanning alerts for that repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential vulnerabilities or errors in your repository's code. 更多信息请参阅“[管理仓库的代码扫描警报](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)”。
+If you have write permission to a repository you can manage code scanning alerts for that
+repository. With write permission to a repository, you can view, fix, dismiss, or delete alerts for potential
+vulnerabilities or errors in your repository's code. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository)."
 
 #### Generate reports of {% data variables.product.prodname_code_scanning %} alerts
 
-If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. 更多信息请参阅“[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)”。
+If you’d like to create a report of your code scanning alerts, you can use the {% data variables.product.prodname_code_scanning_capc %} API. For more information, see the "[{% data variables.product.prodname_code_scanning_capc %} API](/rest/reference/code-scanning)."
 
 For an example of how to use the {% data variables.product.prodname_code_scanning_capc %} API, see the [`get-code-scanning-alerts-in-org-sample`](https://github.com/jhutchings1/get-code-scanning-alerts-in-org-sample) repository.
 
@@ -247,7 +266,7 @@ For an example of how to use the {% data variables.product.prodname_code_scannin
 
 When running initial code scans, you may find that no results are found or that an unusual number of results are returned. You may want to adjust what is flagged in future scans.
 
-更多信息请参阅“[配置代码扫描](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)”。
+For more information, see "[Configuring code scanning](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning)."
 
 If your company wants to use other third-party code analysis tools with GitHub code scanning, you can use actions to run those tools within GitHub. Alternatively, you can upload results, generated by third-party tools as SARIF files, to code scanning. For more information, see "[Integrating with code scanning](/code-security/code-scanning/integrating-with-code-scanning)."
 
@@ -269,13 +288,13 @@ To learn how to view and close alerts for secrets checked into your repository,
 
 GitHub helps you avoid using third-party software that contains known vulnerabilities. We provide the following tools for removing and avoiding vulnerable dependencies.
 
-| Dependency Management Tool                     | 描述                                                                                                                                                                                                                                                                                                                                                                                             |
-| ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Dependabot Alerts                              | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)."                          |
-| Dependency Graph                               | 依赖项图是存储在仓库中的清单和锁定文件的摘要。 它显示您的代码库所依赖的生态系统和软件包（其依赖项）以及依赖于您的项目的仓库和包（其从属项）。 更多信息请参阅“[关于依赖关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)”。 |{% ifversion ghes > 3.1 or ghec %}
-| Dependency Review                              | 如果拉取请求包含对依赖项的更改，您可以查看已更改内容摘要以及任何依赖项中是否存在已知漏洞。 For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or  "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." |{% endif %} {% ifversion ghec or ghes > 3.2 %}
-| Dependabot Security Updates                    | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)."                                                                                             |
-| Dependabot Version Updates                     | Dependabot can be used to keep the packages you use updated to the latest versions. 更多信息请参阅“[关于 Dependabot 版本更新](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)”。 | {% endif %}
+| Dependency Management Tool | Description |
+|----|----|
+| Dependabot Alerts | You can track your repository's dependencies and receive Dependabot alerts when your enterprise detects vulnerable dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." |
+| Dependency Graph | The dependency graph is a summary of the manifest and lock files stored in a repository. It shows you the ecosystems and packages your codebase depends on (its dependencies) and the repositories and packages that depend on your project (its dependents). For more information, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." |{% ifversion ghes > 3.1 or ghec %}
+| Dependency Review | If a pull request contains changes to dependencies, you can view a summary of what has changed and whether there are known vulnerabilities in any of the dependencies. For more information, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)" or  "[Reviewing Dependency Changes in a Pull Request](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)." | {% endif %} {% ifversion ghec or ghes > 3.2 %}
+| Dependabot Security Updates | Dependabot can fix vulnerable dependencies for you by raising pull requests with security updates. For more information, see "[About Dependabot security updates](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." |
+| Dependabot Version Updates | Dependabot can be used to keep the packages you use updated to the latest versions. For more information, see "[About Dependabot version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." | {% endif %}
 
 {% data reusables.dependabot.beta-security-and-version-updates-onboarding %}
 
@@ -301,7 +320,8 @@ You can learn more about [CodeQL queries](https://codeql.github.com/docs/writing
 
 All throughout the pilot phase, it’s essential to create and maintain high-quality internal documentation of the infrastructure and process changes made within your company, as well as learnings from the pilot process and configuration changes made as your team(s) progress throughout the rollout and implementation process.
 
-Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process. Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s).
+Having thorough and complete documentation helps make the remaining phases of your rollout more of a repeatable process.
+Good documentation also ensures that new teams can be onboarded consistently throughout the rollout process and as new team members join your team(s).
 
 Good documentation doesn’t end when rollout and implementation are complete. The most helpful documentation is actively updated and evolves as your teams expand their experience using GHAS and as their needs grow.
 
@@ -356,7 +376,8 @@ Based on what you learned from your pilot project(s), update the rollout plan yo
 {% note %}
 
 {% octicon "clock" aria-label="Clock" %} **Estimated timing:** We estimate that phase 3 may
-last anywhere from 2 weeks to multiple months. This range can vary largely depending on your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc.
+last anywhere from 2 weeks to multiple months. This range can vary largely depending on
+your company’s size, number of repositories/teams, level of change the GHAS rollout will be for your company, etc.
 
 {% endnote %}
 
@@ -381,11 +402,11 @@ To help support your teams, here's a recap of relevant GitHub documentation.
 
 For documentation on how to enable GHAS, see:
   - "[Enabling Advanced Security features](/get-started/learning-about-github/about-github-advanced-security)"
-  - “[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”
-  - "[管理仓库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
+  - "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)"
+  - "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)"
 
 For documentation on how to migrate to GitHub, see:
-  - “[将源代码导入到 GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)”
+  - "[Importing source code to GitHub](/github/importing-your-projects-to-github/importing-source-code-to-github)"
 
 For documentation on getting started with GitHub, see:
   - "[Get started](/get-started)"
diff --git a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md
index c310d0101e..1ead0fa6d2 100644
--- a/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md
+++ b/translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md
@@ -1,7 +1,7 @@
 ---
-title: Overview of GitHub Advanced Security deployment
-intro: 'Help your company successfully prepare to adopt {% data variables.product.prodname_GH_advanced_security %} (GHAS) by reviewing and understanding these best practices, rollout examples, and our enterprise-tested phased approach.'
-product: '{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. To learn more about the features, included in {% data variables.product.prodname_GH_advanced_security %}, see "[About GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)."'
+title: GitHub Advanced Security 部署概述
+intro: '通过查看和理解这些最佳实践、部署示例以及我们经过企业测试的分阶段方法，帮助您的公司成功准备采用 {% data variables.product.prodname_GH_advanced_security %} (GHAS)。'
+product: '{% data variables.product.prodname_GH_advanced_security %} is a set of security features designed to make enterprise code more secure. It is available for {% data variables.product.prodname_ghe_server %} 3.0 or higher, {% data variables.product.prodname_ghe_cloud %}, and open source repositories. 要了解有关 {% data variables.product.prodname_GH_advanced_security %} 中包含的功能的更多信息，请参阅“[关于GitHub Advanced Security](/get-started/learning-about-github/about-github-advanced-security)”。'
 redirect_from:
   - /admin/advanced-security/overview-of-github-advanced-security-deployment
 miniTocMaxHeadingLevel: 3
@@ -16,191 +16,191 @@ topics:
   - Security
 ---
 
-{% data variables.product.prodname_GH_advanced_security %} (GHAS) helps teams build more secure code faster using integrated tooling such as CodeQL, the world’s most advanced semantic code analysis engine. GHAS is a suite of tools that requires active participation from developers across your enterprise. To realize the best return on your investment, you must learn how to use, apply, and maintain GHAS to truly protect your code.
+{% data variables.product.prodname_GH_advanced_security %} (GHAS) 可帮助团队使用集成工具（如 CodeQL，世界上最先进的语义代码分析引擎）更快地构建更安全的代码。 GHAS 是一套工具，需要整个企业的开发人员积极参与。 为了实现最佳的投资回报，您必须学习如何使用、应用和维护 GHAS，以真正保护您的代码。
 
-One of the biggest challenges in tackling new software for an company can be the rollout and implementation process, as well as bringing about the cultural change to drive the organizational buy-in needed to make the rollout successful.
+为公司处理新软件的最大挑战之一可能是部署和实施过程，以及发生文化变革以获得部署成功所需的组织支持。
 
-To help your company better understand and prepare for this process with GHAS, this overview is aimed at:
-  - Giving you an overview of what a GHAS rollout might look like for your company.
-  - Helping you prepare your company for a rollout.
-  - Sharing key best practices to help increase your company’s rollout success.
+为帮助贵公司更好地了解和准备使用 GHAS 的这一过程，本概述旨在：
+  - 概述 GHAS 部署对您的公司来说可能是什么样子。
+  - 帮助您的公司为部署做好准备。
+  - 分享关键最佳实践，以帮助提高公司部署的成功率。
 
-To understand the security features available through {% data variables.product.prodname_GH_advanced_security %}, see "[{% data variables.product.prodname_dotcom %} security features](/code-security/getting-started/github-security-features)."
+要了解 {% data variables.product.prodname_GH_advanced_security %} 提供的安全功能，请参阅“[{% data variables.product.prodname_dotcom %} 安全功能](/code-security/getting-started/github-security-features)”。
 
-## Recommended phased approach for GHAS rollouts
+## 推荐用于 GHAS 部署的分阶段方法
 
-We’ve created a phased approach to GHAS rollouts developed from industry and GitHub best practices. You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently.
+我们创建了一种分阶段的 GHAS 部署方法，该方法根据行业和 GitHub 最佳实践开发。 You can utilize this approach for your rollout, either in partnership with {% data variables.product.prodname_professional_services %} or independently.
 
-While the phased approach is recommended, adjustments can be made based on the needs of your company. We also suggest creating and adhering to a timeline for your rollout and implementation. As you begin your planning, we can work together to identify the ideal approach and timeline that works best for your company.
+虽然建议采用分阶段方法，但可以根据公司的需求进行调整。 We also suggest creating and adhering to a timeline for your rollout and implementation. 当您开始规划时，我们可以一起确定最适合您公司的理想方法和时间表。
 
 ![Diagram showing the three phases of GitHub Advanced Security rollout and deployment, including Phase 0: Planning & Kickoff, Phase 1: Pilot projects, Phase 2: Org Buy-in and Rollout for early adopters, and Phase 3: Full org rollout & change management](/assets/images/enterprise/security/advanced-security-phased-approach-diagram.png)
 
 
-Based on our experience helping customers with a successful deployment of {% data variables.product.prodname_GH_advanced_security %}, we expect most customers will want to follow these phases. Depending on the needs of your company, you may need to modify this approach and alter or remove some phases or steps.
+根据我们帮助客户成功部署 {% data variables.product.prodname_GH_advanced_security %} 的经验，我们预计大多数客户都希望遵循这些阶段。 根据贵公司的需要，您可能需要修改此方法并更改或删除某些阶段或步骤。
 
-For a detailed guide on implementing each of these phases, see "[Deploying {% data variables.product.prodname_GH_advanced_security %} in your enterprise](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)." The next section gives you a high-level summary of each of these phases.
+关于执行每个阶段的详细指南，请参阅“[在企业中部署 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/deploying-github-advanced-security-in-your-enterprise)”。 下一节将为您提供其中每个阶段的高级摘要。
 
-### {% octicon "milestone" aria-label="The milestone icon" %} Phase 0: Planning & kickoff
+### {% octicon "milestone" aria-label="The milestone icon" %} 第 0 阶段：规划和启动
 
-During this phase, the overall goal is to plan and prepare for your rollout, ensuring that you have your people, processes, and technologies in place and ready for your rollout. You should also consider what success criteria will be used to measure GHAS adoption and usage across your teams.
+在此阶段，总体目标是为部署进行规划和准备，确保您拥有适当的人员、流程和技术，并为部署做好准备。 您还应该考虑将使用哪些成功标准来衡量整个团队的 GHAS 采用和使用情况。
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 1: Pilot project(s)
+### {% octicon "milestone" aria-label="The milestone icon" %}  第 1 阶段：试点项目
 
-To begin implementing GHAS, we recommend beginning with a few high-impact projects/teams with which to pilot an initial rollout. This will allow an initial group within your company to get familiar with GHAS, learn how to enable and configure GHAS, and build a solid foundation on GHAS before rolling out to the remainder of your company.
+要开始实施 GHAS，我们建议从几个影响力大的项目/团队开始，以便进行初始部署的试点。 这将允许您公司内的初始小组熟悉 GHAS，学习如何启用和配置 GHAS，并在部署到公司的其他部门之前在 GHAS 上建立坚实的基础。
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 2: Organizational buy-in & rollout preparation
+### {% octicon "milestone" aria-label="The milestone icon" %}  第 2 阶段：组织支持和部署准备
 
-Phase 2 is a recap of previous phases and preparing for a larger rollout across the remainder of the company. In this phase, organizational buy-in can refer to your company’s decision to move forward after the pilot project(s) or the company’s use and adoption of GHAS over time (this is most common). If your company decides to adopt GHAS over time, then phase 2 can continue into phase 3 and beyond.
+第 2 阶段是对前几阶段的回顾，并为在公司其余部分进行更大规模的部署做准备。 在此阶段，组织支持是指公司决定在试点项目后继续推进，还是在公司再使用 GHAS 一段时间（这是最常见的）。 如果您的公司决定再使用 GHAS 一段时间，则第 2 阶段可以继续进入第 3 阶段及以后。
 
-### {% octicon "milestone" aria-label="The milestone icon" %}  Phase 3: Full organizational rollout & change management
+### {% octicon "milestone" aria-label="The milestone icon" %}  第 3 阶段：部署和变更管理的全面组织部署
 
-Once your company is in alignment, you can begin rolling GHAS out to the remainder of the company based on your rollout plan. During this phase, it’s crucial to ensure that a plan has been made for any organizational changes that may need to be made during your rollout of GHAS and ensuring teams understand the need, value, and impact of the change on current workflows.
+在公司达成一致后，您就可以根据部署计划开始将 GHAS 推广到公司的其他部门。 在此阶段，请务必确保为部署 GHAS 期间可能需要进行的任何组织更改制定计划，并确保团队了解更改对当前工作流程的需求、价值和影响。
 
-## Best practices for a successful GHAS rollout
+## 成功部署 GHAS 的最佳实践
 
-We’ve found that companies that have completed successful GHAS rollouts have several similar characteristics that help drive their success. To help your company increase the success of your GHAS rollout, review these best practices.
+我们发现，已经成功完成 GHAS 部署的公司具有几个类似的特征，这些特征有助于推动其成功。 为了帮助您的公司提高 GHAS 部署的成功率，请查看这些最佳实践。
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Set clear goals for your company’s rollout
+### {% octicon "checklist" aria-label="The checklist icon" %} 为公司的部署设定明确的目标
 
-Setting goals may seem obvious, but we do see some companies that begin GHAS rollouts with no clear goals in mind. It’s more difficult for these companies to gain the true organizational buy-in that’s needed to complete the rollout process and realize the value of GHAS within their company.
+设定目标似乎是显而易见的，但我们确实看到一些公司在开始部署 GHAS 时没有明确的目标。 对于这些公司来说，要获得完成部署并在公司内部实现 GHAS 价值所需的真正组织支持，就会更加困难。
 
-As you begin planning for your rollout and implementation, begin outlining goals for GHAS within your company and ensure these are communicated to your team. Your goals can be highly detailed or something simple, as long as there is a starting point and alignment. This will help build a foundation for the direction of your company’s rollout and can help you build a plan to get there. If you need assistance with your goals, {% data variables.product.prodname_professional_services %} can help with recommendations based on our experience with your company and prior engagements with other customers.
+当您开始规划部署和实施时，请先概述公司内部 GHAS 的目标，并确保将这些目标传达给您的团队。 目标可以是非常详细，也可以很简单，但必须有起点并达成一致。 这将有助于为公司的部署方向奠定基础，并帮助您制定实现目标的计划。 如果您在实现目标方面需要帮助， {% data variables.product.prodname_professional_services %} 可以根据我们在贵公司的经验以及之前与其他客户的合作情况，为您提供建议。
 
-Here are some high-level examples of what your goals for rolling out GHAS might look like:
-  - **Reducing the number of vulnerabilities:** This may be in general, or because your  company was recently impacted by a significant vulnerability that you believe could  have been prevented by a tool like GHAS.
-  - **Identifying high-risk repositories:** Some companies may simply want to target repositories that contain the most risk, ready to begin remediating vulnerabilities and reducing risk.
-  -  **Increasing remediation rates:** This can be accomplished by driving developer adoption of findings and ensuring these vulnerabilities are remediated in a timely manner, preventing  the accumulation of security debt.
-  - **Meeting compliance requirements:** This can be as simple as creating new compliance  requirements or something more specific. We find many healthcare companies use GHAS to prevent the exposure of PHI (Personal Health Information).
-  - **Preventing secrets leakage:** This is often a goal of companies that have had (or want to  prevent) critical information leaked such as software keys, customer or financial data, etc.
-  - **Dependency management:** This is often a goal for companies that may have fallen  victim due to hacks from unpatched dependencies, or those seeking to prevent these  types of attacks by updating vulnerable dependencies.
+以下是一些简要示例，说明部署 GHAS 的目标可能是什么样子：
+  - **减少漏洞数量：** 这可能是一般目标，或者因为您的公司最近受到重大漏洞的影响，您认为可以通过 GHAS 等工具阻止这些漏洞。
+  - **识别高风险存储库：** 一些公司可能只想找到包含最大风险的存储库，以便开始修复漏洞并降低风险。
+  -  **提高修复率：** 这可以通过推动开发人员采用调查结果并确保及时修复这些漏洞，防止安全问题累积来实现。
+  - **满足合规性要求：** 这可以像创建新的合规性要求或更具体的内容一样简单。 我们发现许多医疗保健公司使用 GHAS 来防止 PHI（个人健康信息）的暴露。
+  - **防止机密泄露：** 这通常是已经（或希望防止）关键信息泄露（如软件密钥，客户或财务数据等）的公司的目标。
+  - **依赖项管理：** 对于可能由于未修补的依赖项的黑客攻击而成为受害者的公司，或者那些试图通过更新易受攻击的依赖项来防止这类攻击的公司来说，这通常是一个目标。
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Establish clear communication and alignment between your teams
+### {% octicon "checklist" aria-label="The checklist icon" %} 在团队之间建立清晰的沟通和一致性
 
-Clear communication and alignment are critical to the success of any project, and the rollout of GHAS is no different. We’ve found that companies that have clear communication and alignment between their security and development groups, as well as their executive sponsor (either CISO or VP) from the purchase of GHAS through rollout, often have more success with their rollouts.
+清晰的沟通和一致性对于任何项目的成功都至关重要，GHAS 的部署也不例外。 我们发现，从购买 GHAS 到部署期间，其安全和开发团队以及其执行发起人（CISO 或 VP）之间具有明确沟通和一致性的公司，部署通常会取得更大的成功。
 
-In addition to ensuring these groups are aligned throughout your GHAS rollout, there are a few specific areas we recommend focusing on.
+除了确保这些组在整个 GHAS 部署过程中保持一致之外，我们还建议关注一些特定领域。
 
-#### Rollout planning
+#### 部署规划
 
-How will you roll out GHAS to your company? There will likely be many ideas and opinions. Here are some questions you should consider answering and aligning on before moving  forward:
-  - What teams will be included in the pilot?
-  - What projects are focused on in the pilot?
-  - How should projects be prioritized for rollout?
-  - How do you plan to measure success in the pilot and beyond?
-  - What is the level of daily change your teams will be taking on? How will that be  communicated?
-  - How will your rollout plans be communicated across the company?
-  - How do you plan to train your teams?
-  - How do you plan to manage scan results initially? (For more information, see the next section on "Processing results")
+如何将 GHAS 推广到您的公司？ 可能会有很多想法和意见。 以下是在继续推进之前应考虑回答和调整的一些问题：
+  - 哪些团队将包含在试点中？
+  - 试点项目重点关注哪些项目？
+  - 应如何确定项目部署的优先级？
+  - 您计划如何衡量试点及以后的成功？
+  - 您的团队将会进行的日常改变程度如何？ 如何沟通这些？
+  - 您的部署计划将如何在整个公司内传达？
+  - 您计划如何培训您的团队？
+  - 您最初计划如何管理扫描结果？ （有关详细信息，请参阅下一节“处理结果”）
 
-#### Processing results
+#### 处理结果
 
-Before GHAS is rolled out to your teams, there should be clear alignment on how results  should be managed over time. We recommend initially looking at results as more informative  and non-blocking. It’s likely your company has a full CI/CD pipeline, so we recommend this  approach to avoid blocking your company’s process. As you get used to processing these  results, then you can incrementally increase the level of restriction to a point that feels more  accurate for your company.
+在向团队推出 GHAS 之前，应明确协调如何随着时间的推移管理结果。 我们建议最初将结果视为信息量更大且非阻塞的结果。 公司可能具有完整的 CI/CD 管道，因此我们建议使用此方法以避免阻止公司的流程。 当您习惯于处理这些结果时，可以逐步将限制级别提高到对您的公司来说更准确的程度。
 
-### {% octicon "checklist" aria-label="The checklist icon" %}  Lead your rollout with both your security and development groups
+### {% octicon "checklist" aria-label="The checklist icon" %}  通过安全和开发团队领导您的部署
 
-Many companies lead their GHAS rollout efforts with their security group. Often, development teams aren’t included in the rollout process until the pilot has concluded. However, we’ve found that companies that lead their rollouts with both their security and development teams tend to have more success with their GHAS rollout.
+许多公司通过其安全小组领导其 GHAS 部署工作。 通常，在试点结束之前，开发团队不会参与部署过程。 但是，我们发现，通过安全和开发团队领导其部署的公司往往在部署 GHAS 方面取得更大的成功。
 
-为什么？ GHAS takes a developer-centered approach to software security by integrating seamlessly into the developer workflow. Not having key representation from your development group early in the process increases the risk of your rollout and creates an uphill path towards organizational buy-in.
+为什么？ GHAS 采用以开发人员为中心的软件安全方法，无缝集成到开发人员工作流程中。 在流程的早期没有来自开发团队的关键代表会增大部署风险，获得组织支持也会更难。
 
-When development groups are involved earlier (ideally from purchase), security and development groups can achieve alignment early in the process. This helps to remove silos  between the two groups, builds and strengthens their working relationships, and helps shift the  groups away from a common mentality of “throwing things over the wall.” All of these things help support the overall goal to help companies shift and begin  utilizing GHAS to address security concerns earlier in the development process.
+当开发组更早参与时（最好是从购买开始），安全和开发组可以在流程的早期达成一致。 这有助于消除两个群体之间的隔离，建立和加强他们的工作关系，有助于团队摆脱“事不关己，高高挂起”的常见心态。 所有这些事情都有助于支持总体目标，即帮助公司转变并开始利用 GHAS 在开发过程的早期解决安全问题。
 
-#### {% octicon "people" aria-label="The people icon" %} Recommended key roles for your rollout team
+#### {% octicon "people" aria-label="The people icon" %} 建议的部署团队关键角色
 
-We recommend a few key roles to have on your team to ensure that your groups are well represented throughout the planning and execution of your rollout and implementation.
+我们建议您的团队设置几个关键角色，以确保您的团队在部署和实施的整个规划和执行过程中都能合适地代表公司。
 
-We highly recommend your rollout team include these roles:
-- **Executive Sponsor:** This is often the CISO, CIO, VP of Security, or VP of Engineering.
-- **Technical Security Lead:** The technical security lead provides technical support on behalf of the security team throughout the implementation process.
-- **Technical Development Lead:** The technical development lead provides technical support and will likely lead the implementation effort with the development team.
+我们强烈建议您的部署团队包括以下角色：
+- **执行发起人：** 这通常是 CISO、CIO、安全副总裁或工程副总裁。
+- **技术安全主管：** 技术安全主管在整个实施过程中代表安全团队提供技术支持。
+- **技术开发主管：** 技术开发主管提供技术支持，并可能与开发团队一起领导实施工作。
 
-We also recommend your rollout team include these roles:
-- **Project Manager:** We’ve found that the earlier a project manager can be introduced into the rollout process the higher the likelihood of success.
-- **Quality Assurance Engineer:** Including a member of your company’s Quality Assurance team helps ensure process changes are taken into account for the QA team.
+我们还建议您的部署团队包括以下角色：
+- **项目经理：** 我们发现，部署过程越早引入项目经理，成功的可能性就越高。
+- **质量保证工程师：** 公司质量保证团队的成员加入有助于确保 QA 团队考虑流程更改。
 
-### {% octicon "checklist" aria-label="The checklist icon" %} Understand key GHAS facts to prevent common misconceptions
+### {% octicon "checklist" aria-label="The checklist icon" %} 了解 GHAS 的关键事实，防止常见的误解
 
-Going into a GHAS implementation, it’s important to understand some key basic facts about what GHAS is and can do, to prevent many common misconceptions companies have going into their GHAS rollouts.
+进入 GHAS 实施，重要的是要了解 GHAS 是什么以及可以做什么等一些关键的基本事实，以防止公司在部署 GHAS 时出现许多常见的误解。
 
 {% note %}
 
-**Note:** If you’re interested in furthering your GHAS education, {% data variables.product.prodname_professional_services %} provides a variety of options for additional education and training, including topics that your company needs to prepare for GHAS. These offerings may take the form of workshops, demonstrations, and bootcamps. Topics can range from deploying GHAS and basic usage of GHAS to more advanced topics to continue to build your team’s skills. For more information on working with the {% data variables.product.prodname_professional_services_team %} team, see "[{% data variables.product.prodname_professional_services %}](#github-professional-services)."
+**注意：** 如果您有兴趣继续接受 GHAS 教育，{% data variables.product.prodname_professional_services %} 提供了多种额外的教育和培训选择，包括您的公司需要为 GHAS 做准备的主题。 这些产品可能采取研讨会、演示和训练营的形式。 主题范围可以从部署 GHAS 和 GHAS 的基本用法到更高级的主题，以继续培养团队的技能。 有关与 {% data variables.product.prodname_professional_services_team %} 团队合作的详细信息，请参阅“[{% data variables.product.prodname_professional_services %}](#github-professional-services)”。
 
 {% endnote %}
 
 
-#### Fact 1: GHAS is a suite of security tools that require action to protect your code.
+#### 事实 1：GHAS 是一套安全工具，需要采取措施来保护您的代码。
 
-It’s not security software that is installed and forgotten—just having GHAS on its own does not protect your code. GHAS is a suite of tools that increases with value when configured, maintained, used in daily  workflows, and in combination with other tools.
+它不是安装并被遗忘的安全软件 - 仅仅拥有 GHAS 本身并不能保护您的代码。 GHAS 是一套工具，在配置、维护、日常工作流程中使用以及与其他工具结合使用时，其价值会随之增加。
 
-#### Fact 2: GHAS will require adjustment out of the box.
+#### 事实 2：GHAS 需要开箱即用的调整。
 
-Once GHAS is set up on your repositories, there are additional steps that need to be taken to ensure it works for your company’s needs. Code scanning in particular requires further configuration to fine-tune your results, for example, customizing what is flagged by the scans to adjust what is picked up in future scans. Many customers find that initial scans either pick up no results or results that are not relevant based on the application's threat model and need to be adjusted to their company’s needs.
+在存储库上设置 GHAS 后，需要采取其他步骤来确保它符合您公司的需求。 代码扫描尤其需要进一步的配置来微调结果，例如，自定义扫描标记的内容以调整在将来的扫描中提取的内容。 许多客户发现，初始扫描要么没有发现任何结果，要么根据应用程序的威胁模型不相关，需要根据公司的需求进行调整。
 
-#### Fact 3: GHAS tools are most effective when used together, but the most effective AppSec programs involve the use of additional tools/activities.
+#### 事实 3：GHAS 工具在一起使用时最有效，但最有效的 AppSec 程序涉及使用其他工具/活动。
 
-GHAS is most effective when all of the tools are used together. When companies integrate GHAS with other tools and activities, such as penetration testing and dynamic scans, it further improves the effectiveness of the AppSec program. We recommend always utilizing multiple layers of protection.
+当所有工具一起使用时，GHAS 最有效。 当公司将 GHAS 与其他工具和活动（例如渗透测试和动态扫描）集成时，会进一步提高 AppSec 程序的有效性。 我们建议始终使用多层保护。
 
-#### Fact 4: Not all companies will use/need custom {% data variables.product.prodname_codeql %} queries, but they can  help you customize/target scan results.
+#### 事实 4：并非所有公司都会使用/需要自定义 {% data variables.product.prodname_codeql %} 查询，但它们可以帮助您自定义/定位扫描结果。
 
-Code scanning is powered by {% data variables.product.prodname_codeql %}—the world’s most powerful code analysis engine. While  many companies are excited at the prospect of being able to write custom queries, for a  large portion of our customers the base query set and additional queries available in the  community are typically more than sufficient. However, many companies may find the need  for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new  queries to target results your company may need.
+代码扫描由 {% data variables.product.prodname_codeql %} 提供支持，是世界上最强大的代码分析引擎。 虽然许多公司对能够编写自定义查询的前景感到兴奋，但对于我们的大部分客户来说，社区提供的基本查询集和其他查询通常绰绰有余。 但是，许多公司可能会发现需要自定义 {% data variables.product.prodname_codeql %} 查询，以帮助降低结果中的误报率，或者精心创建新查询以找到公司可能需要的结果。
 
-However, if your company is interested in writing custom {% data variables.product.prodname_codeql %} queries, we recommend  you complete your rollout and implementation of GHAS before exploring custom queries.
+但是，如果您的公司有兴趣编写自定义 {% data variables.product.prodname_codeql %} 查询，我们建议您在探索自定义查询之前完成 GHAS 的部署和实施。
 
 {% note %}
 
-**Note:** It’s crucial for your company to have a solid foundation on GHAS before diving deeper into deeper security  practices.
+**注意：** 在深入研究更深层次的安全实践之前，您的公司在GHAS上打下坚实的基础至关重要。
 
 {% endnote %}
 
-When your company is ready, our Customer Success team can help you navigate the requirements that need to be met and can help ensure your company has good use  cases for custom queries.
+当您的公司准备就绪时，我们的客户成功团队可以帮助您了解需要满足的要求，并有助于确保您的公司具有良好的自定义查询用例。
 
-#### Fact 5: {% data variables.product.prodname_codeql %} scans the whole code base, not just the changes made in a pull request.
+#### 事实 5： {% data variables.product.prodname_codeql %} 会扫描整个代码库，而不仅仅是在拉取请求中所做的更改。
 
-When code scanning is run from a pull request, the scan will include the full codebase and not just the changes made in the pull request. While this may seem unnecessary at times, this is an important step to ensure the change has been reviewed all against all interactions in the codebase.
+当从拉取请求运行代码扫描时，扫描将包括完整的代码库，而不仅仅是在拉取请求中所做的更改。 虽然这有时似乎没有必要，但这是确保更改已针对代码库中的所有交互进行审查的重要步骤。
 
-## Examples of successful {% data variables.product.prodname_GH_advanced_security %} rollouts
+## 成功部署 {% data variables.product.prodname_GH_advanced_security %} 的示例
 
-Now that you have a better understanding of some of the keys to a successful GHAS rollout  and implementation, here are some examples of how our customers made their rollouts successful. Even if your company is in a different place, {% data variables.product.prodname_dotcom %} can help you with building a customized path that suits the needs of your rollout.
+现在，您已经更好地了解了成功部署和实施 GHAS 的一些关键因素，以下是我们的客户如何成功部署的一些示例。 即使您的公司位于不同的地方，{% data variables.product.prodname_dotcom %} 也可以帮助您构建适合您的部署需求的自定义路径。
 
-### Example rollout for a mid-sized healthcare technology company
+### 中型医疗保健技术公司的部署示例
 
-A mid-sized healthcare technology company based out of San Francisco completed a successful GHAS rollout process. While they may not have  had a large number of repositories that needed to be enabled, this company’s keys to success included having a well-organized and aligned team for the rollout, with a clearly established key contact to work with {% data variables.product.prodname_dotcom %} to troubleshoot any issues during the process. This allowed them to complete their rollout within two months.
+一家位于旧金山的中型医疗保健技术公司成功完成了 GHAS 的部署过程。 虽然他们可能没有大量需要启用的存储库，但该公司成功的关键包括拥有一个组织良好且协调一致的部署团队，并有明确的关键联系人，可以与 {% data variables.product.prodname_dotcom %} 合作，以解决过程中的任何问题。 这使他们能够在两个月内完成部署。
 
-In addition, having an engaged development team allowed the company to have teams using code scanning at the pull request level following the completion of their rollout.
+此外，拥有一个敬业的开发团队可团队完成部署后在拉取请求级别使用代码扫描。
 
-### Example rollout for a mid-sized data platform company
+### 中型数据平台公司的部署示例
 
-A global data platform company has had great success with GHAS to  date. They’ve completed their initial implementation and are currently progressing through the rollout process. This company is mature in their security posture and tooling, and are well-aligned as an company. This allows them to operate very self-sufficiently and has enabled them to move quickly and smoothly through their rollout.
+时至今天，一家全球性数据平台公司使用 GHAS 取得了巨大成功。 他们已经完成了最初的实施，目前正在通过推进部署过程。 该公司在安全态势和工具方面很成熟，作为一家公司很好地达成了一致。 这使他们能够完全自主运行，并且快速、顺利地完成部署。
 
-This company's strong alignment, efficient operations, and security tooling maturity allowed them to implement GHAS quickly and build a good foundation for {% data variables.product.prodname_codeql %}. Since their implementation, they can now automatically enable {% data variables.product.prodname_codeql %} across different repositories.
+该公司强大的一致性、高效的运营和安全工具的成熟度，使他们能够快速实施 GHAS，为 {% data variables.product.prodname_codeql %} 奠定良好的基础。 自实施后，他们现在可以自动启用跨不同存储库的 {% data variables.product.prodname_codeql %}。
 
-In addition to their security and technical maturity, another critical key to this company’s success is having a project owner and single point of contact from their team to drive the project forward. Not only is having this key contact crucial, but they are incredibly resourceful and skilled, and directly contribute to the success of the rollout.
+除了安全性和技术成熟度之外，该公司成功的另一个关键是拥有项目所有者和团队的单一联系人来推动项目向前发展。 不仅拥有这样一个关键联系人，而且他们非常足智多谋和熟练，直接为部署的成功做出贡献。
 
-## Prerequisites for your company before rolling out GHAS
+## 公司在部署 GHAS 之前需满足的先决条件
 
-{% data variables.product.prodname_professional_services %} can help to provide additional support to help your company break down and understand these prerequisites and help you get prepared for the GHAS implementation process.
+{% data variables.product.prodname_professional_services %} 可以帮助提供额外的支持，帮助您的公司细分和了解这些先决条件，并帮助您为 GHAS 实施过程做好准备。
 
- ### CI/CD systems and process
+ ### CI/CD 系统和流程
 
-If your company has not yet invested in or implemented continuous integration or continuous delivery (CI/CD) systems and processes, we recommend taking this step in conjunction with moving forward with GHAS. This may be a significant shift for your company—we can work with you to provide recommendations and guidance for implementing a CI/CD system, as well as supporting any training that might be needed.
+如果您的公司尚未投资或实施持续集成或持续交付 (CI/CD) 系统和流程，我们建议您在继续使用 GHAS 的同时采取此步骤。 这对贵公司来说可能是一个重大转变 - 我们可以与您合作，为实施 CI/CD 系统提供建议和指导，并支持可能需要的任何培训。
 
-### Requirements to install {% data variables.product.prodname_GH_advanced_security %}
+### 安装 {% data variables.product.prodname_GH_advanced_security %} 的要求
 
-There are a few different paths that can be taken for your GHAS installation based on what combinations of technologies your company uses. This section outlines a quick breakdown of the different paths your company may need to take.
+根据贵公司使用的技术组合，可以采用几种不同的路径进行 GHAS 安装。 本节概述了贵公司可能需要采取的不同路径的快速细分。
 
 {% ifversion ghes %}
 
 #### {% data variables.product.prodname_ghe_server %}
 
-It’s important that you’re utilizing a version of {% data variables.product.prodname_ghe_server %} (GHES) that will support your company’s needs.
+重要的是，您使用的是支持公司需求的 {% data variables.product.prodname_ghe_server %} (GHES) 版本。
 
-If you’re using an earlier version of GHES (prior to 3.0) and would like to upgrade, there are some requirements that you’ll need to meet before moving forward with the upgrade. 更多信息请参阅：
-  - "[Upgrading {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
-  - "[Upgrade requirements](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
+如果您使用的是早期版本（3.0 之前）的 GHES 并希望升级，则在升级之前，您需要满足一些要求。 更多信息请参阅：
+  - “[升级 {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)”
+  - “[升级要求](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)”
 
-If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+如果您使用的是第三方 CI/CD 系统，并且想要使用 {% data variables.product.prodname_code_scanning %}，请确保已下载 {% data variables.product.prodname_codeql_cli %}。 For more information, see "[About CodeQL code scanning in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
-If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting.
+如果您与 {% data variables.product.prodname_professional_services %} 合作部署 GHAS ，请准备好在启动会议中详细讨论这些项目。
 
 {% endif %}
 
@@ -208,60 +208,60 @@ If you're working with {% data variables.product.prodname_professional_services
 
 #### {% data variables.product.prodname_ghe_cloud %}
 
-If you’re a {% data variables.product.prodname_ghe_cloud %} (GHEC) customer there are prerequisites that you’ll need to meet depending on what CI/CD you plan to utilize.
+如果您是 {% data variables.product.prodname_ghe_cloud %} (GHEC) 客户，则需要满足一些先决条件，具体取决于您计划使用的 CI/CD。
 
-Using {% data variables.product.prodname_actions %} for your CI/CD:
-- To ensure {% data variables.product.prodname_code_scanning %} can be integrated and utilized properly, you should have a basic understanding of {% data variables.product.prodname_actions %} before proceeding with your installation.
+对 CI/CD 使用 {% data variables.product.prodname_actions %} ：
+- 为确保可以正确集成和利用 {% data variables.product.prodname_code_scanning %} ，在继续安装之前，您应该对 {% data variables.product.prodname_actions %} 有基本的了解。
 
-Using a third-party tool for CI/CD:
-- To integrate the {% data variables.product.prodname_codeql_cli %}, you should have a basic understanding of the CI/CD system, as well as *nix and Windows—in particular how commands are executed and how success/failure is signaled. For more information about how to integrate a third-party tool, see "[Using CodeQL code scanning with your existing CI system ](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)."
+对 CI/CD 使用第三方工具：
+- 要集成 {% data variables.product.prodname_codeql_cli %}，您应该对 CI/CD 系统以及 *nix 和 Windows 有基本的了解，特别是命令的执行方式以及成功/失败的信号。 有关如何集成第三方工具的更多信息，请参阅“[将 CodeQL 代码扫描与现有 CI 系统结合使用](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)”。
 
 {% endif %}
 
-## Partnering with GitHub for your rollout
+## 与 GitHub 合作进行部署
 
-As you prepare for your GHAS implementation, it’s important to  consider what will be required from your company to make this  project successful. Our most successful implementations of GHAS  rely on shared responsibilities between both GitHub and our customers throughout the process with a clearly identified stakeholder from the customer owning the project.
+在为实施 GHAS 做准备时，请务必考虑贵公司需要做些什么才能使该项目取得成功。 我们最成功的 GHAS 实施依赖于 GitHub 和客户在整个过程中，与拥有该项目的客户明确确定的利益相关者共同承担责任。
 
-#### Success model for customer and GitHub responsibilities
+#### 客户和 GitHub 责任的成功模型
 
-**Customer responsibilities**
-- Completing infrastructure and process prerequisites
-- Managing rollout and implementation, including planning and execution
-- Internal training
-- (Optional) Contributing {% data variables.product.prodname_codeql %} queries to the GitHub Community
+**客户责任**
+- 完成基础架构和流程先决条件
+- 管理部署和实施，包括规划和执行
+- 内部培训
+- （可选）向 GitHub 社区提供 {% data variables.product.prodname_codeql %} 查询
 
-**GitHub responsibilities**
+**GitHub 责任**
 
-- Maintenance and enhancements for features, such as {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %}
-- Providing, maintaining, and delivering the following services: {% data variables.product.prodname_dotcom %} Docs, {% data variables.product.prodname_dotcom %} Community, {% data variables.product.prodname_dotcom %} Support
+- 功能的维护和增强，如 {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_GH_advanced_security %}
+- 提供、维护和交付以下服务： {% data variables.product.prodname_dotcom %} 文档、{% data variables.product.prodname_dotcom %} 社区、{% data variables.product.prodname_dotcom %} 支持
 
 {% note %}
 
-**Note:**  {% data variables.product.prodname_professional_services %} can help support many of the customer responsibilities. To learn more, see "[GitHub services and support](#github-services-and-support)."
+**注意：** {% data variables.product.prodname_professional_services %} 有助于支持履行许多客户职责。 要了解更多信息，请参阅“[GitHub 服务和支持](#github-services-and-support)”。
 
 {% endnote %}
 
-## {% data variables.product.prodname_dotcom %} services and support
+## {% data variables.product.prodname_dotcom %} 服务和支持
 
-### {% data variables.product.prodname_dotcom %} Support
+### {% data variables.product.prodname_dotcom %} 支持
 
-If you run into any issues during your implementation, you can search our deep documentation for solutions or engage with {% data variables.product.prodname_dotcom %} Support, a team of highly technical engineers that can support you as issues arise. For more information, see "[GitHub Enterprise Support](https://enterprise.github.com/support).
+如果您在实施过程中遇到任何问题，可以搜索我们的深入文档以获取解决方案，或与 {% data variables.product.prodname_dotcom %} 支持部门合作，这是一个由高技术工程师组成的团队，可以在出现问题时为您提供支持。 更多信息请参阅“[GitHub Enterprise 支持](https://enterprise.github.com/support)”。
 
-In addition, you can also try our [ {% data variables.product.prodname_gcf %}](https://github.community/).
+此外，您还可以尝试我们的 [ {% data variables.product.prodname_gcf %}](https://github.community/)。
 
-If you purchased a Premium Support plan, you can submit your ticket in the [Premium Support Portal](https://enterprise.github.com/support). If you’re unsure of which Support plan you purchased, you can reach out to your sales representative or review the plan options.
+如果您购买了高级支持计划，则可以在[高级支持门户](https://enterprise.github.com/support)提交事件单。 如果您不确定购买了哪个支持计划，可以联系您的销售代表或查看计划选项。
 
-For more information the Premium support plan options, see:
-  - "[Premium Support](https://github.com/premium-support)" {% ifversion ghec %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
+有关高级支持计划选项的详细信息，请参阅：
+  - “[高级支持](https://github.com/premium-support)” {% ifversion ghec %}
+  - “[关于 {% data variables.product.prodname_ghe_cloud %} 的 GitHub 高级支持](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)”{% endif %}{% ifversion ghes %}
+  - “[关于 {% data variables.product.prodname_ghe_server %} 的 GitHub 高级支持](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)”{% endif %}
 
 ### {% data variables.product.prodname_professional_services %}
 
-Our {% data variables.product.prodname_professional_services_team %} team can partner with you for a successful rollout and implementation of {% data variables.product.prodname_GH_advanced_security %}. We offer a variety of options for the type of guidance and support you expect to need for your implementation. We also have training and bootcamps available to help your company to optimize the value of GHAS.
+我们的 {% data variables.product.prodname_professional_services_team %} 团队可以与您合作，成功部署和实施 {% data variables.product.prodname_GH_advanced_security %}。 我们针对您的实施所需的指导和支持类型提供了多种选项。 我们还提供培训和训练营，帮助您的公司优化 GHAS 的价值。
 
-If you’d like to work with our {% data variables.product.prodname_professional_services_team %} team for your implementation, we recommend you begin thinking about your system design and infrastructure, as well as the number of repositories that you want to set up with GHAS, to begin these conversations. In addition, begin thinking about goals for what you would like to achieve with this rollout.
+如果您想与我们的 {% data variables.product.prodname_professional_services_team %} 团队合作进行部署，我们建议您开始考虑您的系统设计和基础架构，以及您希望使用 GHAS 设置的存储库数量，以开始这些对话。 此外，开始考虑您希望通过此部署实现的目标。
 
-Implementation is just one step in a successful security-driven journey where you’ll learn how to use GHAS. Once you’ve completed your implementation, there will be more to learn with the rollout throughout your infrastructure and codebases. Speak with your sales representative for more information about all the {% data variables.product.prodname_professional_services_team %} options available.
+实施只是学习如何使用 GHAS 的安全驱动型成功旅程中的一步。 完成实施后，您将进一步了解整个基础架构和代码库中的部署。 请与您的销售代表联系，以获取有关所有可用 {% data variables.product.prodname_professional_services_team %} 选项的更多信息。
 
-If you initially opted out of additional services, but find that additional support is  needed as you begin your implementation, please reach out to your sales representative to discuss what services options may be needed to support your implementation.
+如果您最初选择退出其他服务，但在开始实施时发现需要其他支持，请联系您的销售代表，讨论可能需要哪些服务选项来支持您的实施。
diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
index 65fd686122..17e9d2fb10 100644
--- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise.md
@@ -1,7 +1,7 @@
 ---
-title: Enabling the dependency graph for your enterprise
-intro: You can allow users to identify their projects' dependencies by enabling the dependency graph.
-shortTitle: Enable dependency graph
+title: 为企业启用依赖关系图
+intro: 您可以通过启用依赖项关系图来允许用户标识其项目的依赖项。
+shortTitle: 启用依赖关系图
 permissions: Site administrators can enable the dependency graph.
 versions:
   ghes: '*'
@@ -14,16 +14,16 @@ topics:
 
 ## 关于依赖项图
 
-{% data reusables.dependabot.about-the-dependency-graph %} For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"
+{% data reusables.dependabot.about-the-dependency-graph %}更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
 
-After you enable the dependency graph for your enterprise, you can enable {% data variables.product.prodname_dependabot %} to detect vulnerable dependencies in your repository{% ifversion ghes > 3.2 %} and automatically fix the vulnerabilities{% endif %}. 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。
+为企业启用依赖关系图后，可以启用 {% data variables.product.prodname_dependabot %} 以检测存储库中易受攻击的依赖项{% ifversion ghes > 3.2 %}，并自动修复漏洞{% endif %}。 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。
 
 {% ifversion ghes > 3.1 %}
-您可以通过 {% data variables.enterprise.management_console %} 或管理 shell 启用依赖关系图。 We recommend using the {% data variables.enterprise.management_console %} unless {% data variables.product.product_location %} uses clustering.
+您可以通过 {% data variables.enterprise.management_console %} 或管理 shell 启用依赖关系图。 我们建议您使用 {% data variables.enterprise.management_console %}，除非 {% data variables.product.product_location %} 使用集群。
 
 ## 通过 {% data variables.enterprise.management_console %} 启用依赖关系图
 
-If your {% data variables.product.product_location %} uses clustering, you cannot enable the dependency graph with the {% data variables.enterprise.management_console %} and must use the administrative shell instead. For more information, see "[Enabling the dependency graph via the administrative shell](#enabling-the-dependency-graph-via-the-administrative-shell)."
+如果您的 {% data variables.product.product_location %} 使用群集，则无法使用 {% data variables.enterprise.management_console %} 启用依赖关系图，而必须改用管理 shell。 更多信息请参阅“[通过管理 shell 启用依赖关系图](#enabling-the-dependency-graph-via-the-administrative-shell)”。
 
 {% data reusables.enterprise_site_admin_settings.sign-in %}
 {% data reusables.enterprise_site_admin_settings.access-settings %}
diff --git a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
index 453504d2cb..953517b46c 100644
--- a/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md
@@ -17,9 +17,11 @@ If {% data variables.product.prodname_dependabot_alerts %} are enabled for your
 
 You can manually sync vulnerability data from {% data variables.product.prodname_dotcom_the_website %} to update the list.
 
-Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. 更多信息请参阅“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”。
+Before you can view vulnerability data, you must enable {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)."
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-2. 在左侧边栏中，单击 **Vulnerabilities**。 ![站点管理员边栏中的 Vulnerabilities 选项卡](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
-3. 要同步漏洞数据，请单击 **Sync Vulnerabilities now**。 ![Sync vulnerabilities now 按钮](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
+2. In the left sidebar, click **Vulnerabilities**.
+  ![Vulnerabilities tab in the site admin sidebar](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. To sync vulnerability data, click **Sync Vulnerabilities now**.
+  ![Sync vulnerabilities now button](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
index dfa5276cbe..dda614d0f4 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md
@@ -114,7 +114,7 @@ Allows you to find the universally unique identifier (UUID) of your node in `clu
 ```
 
 {% ifversion ghes %}
-Allows you to exempt a list of users from API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
+Allows you to exempt a list of users from REST API rate limits. A hard limit of 120,000 requests will still apply to these users. For more information, see "[Resources in the REST API](/rest/overview/resources-in-the-rest-api#rate-limiting)."
 
 ``` shell
 $ ghe-config app.github.rate-limiting-exempt-users "<em>hubot</em> <em>github-actions</em>"
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
index 5732a0c5f1..d43f6ea620 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md
@@ -35,7 +35,7 @@ shortTitle: 配置维护模式
 
 ![关于已排定维护的最终用户横幅](/assets/images/enterprise/maintenance/maintenance-scheduled.png)
 
-在实例进入维护模式后，所有正常 HTTP 和 Git 访问都会遭到拒绝。 Git 提取、克隆和推送操作也会被拒绝，并显示一条错误消息，指示站点暂时不可用。 GitHub Actions 作业不会执行。 在浏览器中访问该站点会显示维护页面。
+在实例进入维护模式后，所有正常 HTTP 和 Git 访问都会遭到拒绝。 Git 提取、克隆和推送操作也会被拒绝，并显示一条错误消息，指示站点暂时不可用。 在高可用性配置中，Git 复制将暂停。 GitHub Actions 作业不会执行。 在浏览器中访问该站点会显示维护页面。
 
 ![维护模式启动屏幕](/assets/images/enterprise/maintenance/maintenance-mode-maintenance-page.png)
 
diff --git a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
index 9cb3ba1b65..6d88cf3891 100644
--- a/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
+++ b/translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md
@@ -45,9 +45,9 @@ Data for GitHub's [trending page][] is calculated into daily, weekly, and monthl
 
 {% data variables.product.product_name %} keeps a running log of audited actions that you can query.
 
-By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log](/enterprise/{{ currentVersion }}/admin/guides/installation/searching-the-audit-log)."
+By default, the audit log shows you a list of all audited actions in reverse chronological order. You can filter this list by entering key-value pairs in the **Query** text box and then clicking **Search**, as explained in "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)."
 
-For more information on audit logging in general, see "[Audit logging](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)." For a full list of audited actions, see "[Audited actions](/enterprise/{{ currentVersion }}/admin/guides/installation/audited-actions)."
+For more information on audit logging in general, see "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)." For a full list of audited actions, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
 
 ## Reports
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/index.md b/translations/zh-CN/content/admin/enterprise-management/index.md
index ea11903d31..5873a601d1 100644
--- a/translations/zh-CN/content/admin/enterprise-management/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/index.md
@@ -13,6 +13,6 @@ children:
   - /configuring-clustering
   - /configuring-high-availability
   - /caching-repositories
-shortTitle: 监控、管理和更新
+shortTitle: 监控、管理和更新您的设备
 ---
 
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
new file mode 100644
index 0000000000..5317e3764a
--- /dev/null
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/about-system-logs.md
@@ -0,0 +1,62 @@
+---
+title: About system logs
+intro: '{% data variables.product.product_name %} keeps error and message logs for system events. Logs are useful for identifying user, application and system-level actions and exceptions.'
+versions:
+  ghes: '*'
+type: overview
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+---
+
+## System logs
+
+By default, system logs for {% data variables.product.product_name %} are automatically rotated every 24 hours and are retained for seven days. System logs include system-level events, application logs, and Git events data. As log files are often being written to and can be large in size, it may be beneficial to extract and parse relevant log entries on a host separate to your {% data variables.product.prodname_ghe_server %} instance.
+
+You can forward system logs to a third-party system or server for longer retention. 更多信息请参阅“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)。”
+
+In addition to reviewing your system logs, you can monitor activity in your enterprise in other ways, such as viewing audit logs, push logs and managing global webhooks. 更多信息请参阅“[监控企业中的活动](/admin/monitoring-activity-in-your-enterprise)”。
+
+## Types of logs
+
+Listed below are the main logs used by the {% data variables.product.product_name %} appliance and their functions:
+
+| 路径                               | 描述​                                                                           |
+| -------------------------------- | ----------------------------------------------------------------------------- |
+| `/var/log/github/audit.log`      | Audited user, repository and system events.                                   |
+| `/var/log/github/unicorn.log`    | API and web interface traffic.                                                |
+| `/var/log/github/exceptions.log` | Application-level errors.                                                     |
+| `/var/log/haproxy.log`           | All IP traffic reaching the appliance.                                        |
+| `/var/log/hookshot/resqued.log`  | Webhook delivery and failures.                                                |
+| `/var/log/github/auth.log`       | Authentication requests, whether through built in, LDAP, CAS or SAML methods. |
+| `/var/log/github/gitauth.log`    | All Git authentication requests.                                              |
+
+Git activity and authentication requests are processed by the `babeld` service.
+
+Several {% data variables.product.product_name %} services, such as the `babeld` service, are containerized. Containerized logs are written to the `systemd journal`, and can be queried at any time using the `journalctl` command.
+
+## Audited system events
+
+All entries from the `audit.log` file use and can be filtered with the `github_audit` keyword.
+
+例如，此条目显示已创建的新仓库。
+
+```
+Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
+```
+
+此示例显示提交已推送到仓库。
+
+```
+Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
+```
+
+## 支持包
+
+The support bundle includes system logs and all audit information is logged to the `audit.log` file in the `github-logs` directory. For more information, see "[Providing data to {% data variables.product.prodname_dotcom %} Support](/support/contacting-github-support/providing-data-to-github-support)."
+
+## 延伸阅读
+
+- [Linux man page for the `journalctl` command](http://man7.org/linux/man-pages/man1/journalctl.1.html)
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
index df21b5a2fe..021dd007a9 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Generating a Health Check for your enterprise
-intro: 'You can gain insight into the general health and Git and API requests of {% data variables.product.product_location %} by generating a Health Check.'
+title: 为您的企业生成运行状况检查
+intro: '您可以通过生成运行状况检查来深入了解 {% data variables.product.product_location %} 的常规运行状况以及 Git 和 API 请求。'
 versions:
   ghes: '*'
 type: how_to
@@ -15,42 +15,42 @@ product: '{% data reusables.gated-features.generated-health-checks %}'
 
 {% note %}
 
-**Note:** Generating a Health Check is currently in beta for {% data variables.product.prodname_ghe_server %} and subject to change.
+**注意：** 生成运行状况检查目前正测试用于 {% data variables.product.prodname_ghe_server %}，可能会有所变化。
 
 {% endnote %}
 
-## About generated Health Checks
+## 关于生成的运行状况检查
 
-You can create a support bundle for {% data variables.product.product_location %} that contains a lot of data, such as diagnostics and log files. To help analyze and interpret this data, you can generate a Health Check. For more information about support bundles, see "[Providing data to {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)."
+您可以为包含大量数据（如诊断和日志文件）的 {% data variables.product.product_location %} 创建支持包。 为了帮助分析和解释此数据，您可以生成运行状况检查。 有关支持包的详细信息，请参阅“[向 {% data variables.contact.github_support %} 提供数据](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。
 
-A Health Check provides the following information about {% data variables.product.product_location %}.
-- Insights into the general health of {% data variables.product.product_location %}, such as upgrade status, storage, and license seat consumption
-- A security section, which focuses on subdomain isolation and user authentication
-- Analysis of Git requests, with details about the busiest repositories and Git users
-- Analysis of API requests, including the busiest times, most frequently requested endpoints, and most active callers
+运行状况检查提供有关 {% data variables.product.product_location %} 的以下信息。
+- 深入了解 {% data variables.product.product_location %} 的一般运行状况，例如升级状态、存储和许可证席位消耗
+- 安全部分，重点介绍子域隔离和用户身份验证
+- Git 请求分析，以及有关最繁忙的存储库和 Git 用户的详细信息
+- API 请求分析，包括最繁忙的时间、最常请求的终端节点和最活跃的调用方
 
-## Generating a Health Check
+## 生成运行状况检查
 
-Before you can generate a Health Check, you must create a support bundle. 更多信息请参阅“[将数据提供给 {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。
+在生成运行状况检查之前，您必须创建支持包。 更多信息请参阅“[将数据提供给 {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)”。
 
-1. Navigate to the [{% data variables.contact.support_portal %}](https://support.github.com/).
-2. In the upper-right corner of the page, click **Premium**.
+1. 导航到 [{% data variables.contact.support_portal %}](https://support.github.com/)。
+2. 在页面的右上角，单击 **Premium（高级）**。
 
-   ![Screenshot of the "Premium" link in the GitHub Support Portal header.](/assets/images/enterprise/support/support-portal-header-premium.png)
+   ![GitHub 支持门户标头中"高级"链接的屏幕截图。](/assets/images/enterprise/support/support-portal-header-premium.png)
 
-3. To the right of **Health Checks**, click **Request Health Check**.
+3. 在 **Health Checks（运行状况检查）**右侧，单击 **Request Health Check（请求运行状况检查）**。
 
-   ![Screenshot of the "Request Health Check" button.](/assets/images/enterprise/support/support-portal-request-health-check.png)
+   !["请求运行状况检查" 按钮的屏幕截图。](/assets/images/enterprise/support/support-portal-request-health-check.png)
 
-4. Under "Select an enterprise account", select the dropdown menu and click an enterprise account.
+4. 在“Select an enterprise account（选择企业帐户）”下，选择下拉菜单，然后单击企业帐户。
 
-   ![Screenshot of the "enterprise account" dropdown menu.](/assets/images/enterprise/support/health-check-dialog-ea.png)
+   !["企业帐户" 下拉菜单的屏幕截图。](/assets/images/enterprise/support/health-check-dialog-ea.png)
 
-5. Under "Upload a support bundle", click **Chose File** and choose a file to upload. Then, click **Request Health Check**.
+5. 在“Upload a support bundle（上传支持包）”下，点击 **Chose File（选择文件）** ，然后选择要上传的文件。 然后，单击 **Request Health Check（请求运行状况检查）**。
 
-   ![Screenshot of the "Choose file" and "Request Health Check" buttons.](/assets/images/enterprise/support/health-check-dialog-choose-file.png)
+   !["选择文件" 和 "请求运行状况检查" 按钮的屏幕截图。](/assets/images/enterprise/support/health-check-dialog-choose-file.png)
 
 
-After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.support_portal %}.
+请求运行状况检查后，将安排一个作业来生成运行状况检查。 几个小时到一天后，生成的运行状况检查将显示在 {% data variables.contact.support_portal %}的“运行状况检查”部分中。
 
-![Screenshot of the Health Checks section of the {% data variables.contact.support_portal %}.](/assets/images/enterprise/support/support-portal-health-checks-section.png)
+![{% data variables.contact.support_portal %}的“运行状况检查”部分的屏幕截图。](/assets/images/enterprise/support/support-portal-health-checks-section.png)
diff --git a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
index 04656927f4..25e18dc170 100644
--- a/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
+++ b/translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md
@@ -16,6 +16,7 @@ children:
   - /setting-up-external-monitoring
   - /configuring-collectd
   - /monitoring-using-snmp
+  - /about-system-logs
   - /generating-a-health-check-for-your-enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index 4c8a06890f..511d399159 100644
--- a/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -40,7 +40,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
 Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
 {% endif %}
 
-You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit logs for organizations in your enterprise](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)."{% else %}"[Searching the audit log](/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log)."{% endif %}
+You can access information about activity related to {% data variables.product.prodname_actions %} in the audit logs for your enterprise. If your business needs require retaining audit logs for longer than six months, plan how you'll export and store this data outside of {% data variables.product.prodname_dotcom %}. For more information, see {% ifversion ghec %}"[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)" and "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."{% else %}"[Log forwarding](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)."{% endif %}
 
 ![Audit log entries](/assets/images/help/repository/audit-log-entries.png)
 
diff --git a/translations/zh-CN/content/admin/guides.md b/translations/zh-CN/content/admin/guides.md
index a408499582..3bbc87a333 100644
--- a/translations/zh-CN/content/admin/guides.md
+++ b/translations/zh-CN/content/admin/guides.md
@@ -31,7 +31,6 @@ includeGuides:
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise
   - /admin/authentication/managing-identity-and-access-for-your-enterprise/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account
   - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users
-  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
   - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users
   - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users
   - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users-with-okta
@@ -75,6 +74,7 @@ includeGuides:
   - /admin/enterprise-management/setting-up-external-monitoring
   - /admin/enterprise-management/upgrade-requirements
   - /admin/enterprise-management/upgrading-github-enterprise-server
+  - /admin/enterprise-management/monitoring-your-appliance/about-system-logs
   - /admin/enterprise-support/about-github-enterprise-support
   - /admin/github-actions/about-using-actions-in-your-enterprise
   - /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
@@ -103,7 +103,6 @@ includeGuides:
   - /admin/policies/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance
   - /admin/user-management/about-migrations
   - /admin/user-management/adding-people-to-teams
-  - /admin/user-management/audited-actions
   - /admin/user-management/auditing-ssh-keys
   - /admin/user-management/auditing-users-across-your-enterprise
   - /admin/user-management/configuring-git-large-file-storage-for-your-enterprise
@@ -115,11 +114,19 @@ includeGuides:
   - /admin/user-management/exporting-migration-data-from-your-enterprise
   - /admin/user-management/importing-data-from-third-party-version-control-systems
   - /admin/user-management/managing-dormant-users
-  - /admin/user-management/managing-global-webhooks
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding
+  - /admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks
   - /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
   - /admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise
-  - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
-  - /admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise
   - /admin/user-management/managing-projects-using-jira
   - /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
   - /admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise
@@ -128,7 +135,6 @@ includeGuides:
   - /admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise
   - /admin/user-management/migrating-data-to-your-enterprise
   - /admin/user-management/migrating-to-internal-repositories
-  - /admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks
   - /admin/user-management/placing-a-legal-hold-on-a-user-or-organization
   - /admin/user-management/preparing-to-migrate-data-to-your-enterprise
   - /admin/user-management/preventing-users-from-creating-organizations
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md
deleted file mode 100644
index 6921a5e47d..0000000000
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: 审核企业中的活动
-shortTitle: 审核活动
-intro: '您可以审核企业中 {% data variables.product.prodname_managed_users %} 的活动，查看执行的操作、执行的用户以及执行时间等相关信息。'
-permissions: Enterprise owners can access the audit log.
-product: '{% data reusables.gated-features.emus %}'
-redirect_from:
-  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
-  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
-versions:
-  ghec: '*'
-topics:
-  - Accounts
-  - Enterprise
----
-
-## 关于审核日志
-
-审核日志允许企业所有者快速查看或导出企业所有者和成员执行的操作。 每个审核日志条目都显示有关事件的信息。
-
-- 可在其中执行操作的组织
-- 执行操作的用户
-- 执行操作的仓库
-- 执行的操作内容
-- 发生操作的国家/地区
-- 操作发生的日期和时间
-
-## 访问审核日志
-
-您还可以从 REST API 访问企业的审核日志。 更多信息请参阅 API 文档中的“[GitHub Enterprise 管理](/rest/reference/enterprise-admin#get-the-audit-log-for-an-enterprise)”。
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.audit-log-tab %}
-1. （可选）在事件列表上方，选择 **Export Git Events（导出 Git 事件）**或 **Export（导出）**下拉菜单，然后选择用于从审核日志中导出事件的选项。 ![企业审核日志的"导出 Git 事件"和"导出"下拉菜单](/assets/images/help/enterprises/audit-log-export-drop-down-menus.png)
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md
index c05be42df6..fae11a5017 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/index.md
@@ -17,6 +17,5 @@ children:
   - /configuring-scim-provisioning-for-enterprise-managed-users
   - /configuring-scim-provisioning-for-enterprise-managed-users-with-okta
   - /managing-team-memberships-with-identity-provider-groups
-  - /auditing-activity-in-your-enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes.md
index f6dae92be5..f4c4d486c1 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes.md
@@ -1,7 +1,7 @@
 ---
-title: Downloading your enterprise account's SAML single sign-on recovery codes
-shortTitle: Download recovery codes
-intro: 'To ensure that you can access {% data variables.product.product_name %} if your identity provider (IdP) is unavailable, you should download your enterprise account''s SAML single sign-on (SSO) recovery codes.'
+title: 下载企业帐户的 SAML 单点登录恢复代码
+shortTitle: 下载恢复代码
+intro: '为确保在身份提供程序 (IdP) 不可用时可以访问 {% data variables.product.product_name %} ，应下载企业帐户的 SAML 单点登录 (SSO) 恢复代码。'
 versions:
   ghec: '*'
 type: how_to
@@ -13,14 +13,14 @@ topics:
 permissions: Enterprise owners can download the SAML SSO recovery codes for the enterprise account.
 ---
 
-In the event that your IdP is unavailable, you can use a recovery code to sign in and access your enterprise on {% data variables.product.product_location %}. For more information, see "[Accessing your enterprise account if your identity provider is unavailable](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)."
+如果您的 IdP 不可用，您可以使用恢复代码登录并通过 {% data variables.product.product_location %} 访问您的企业。 更多信息请参阅“[在身份提供程序不可用时访问企业帐户](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/accessing-your-enterprise-account-if-your-identity-provider-is-unavailable)”。
 
-If you did not save your recovery codes when you configured SAML SSO, you can still access the codes from your enterprise's settings.
+如果在配置 SAML SSO 时未保存恢复代码，您仍然可以从企业的设置中访问这些代码。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.settings-tab %}
 {% data reusables.enterprise-accounts.security-tab %}
 
-1. Under "Require SAML authentication", click **Save your recovery codes**. ![Screenshot of the button to test SAML configuration before enforcing](/assets/images/help/enterprises/saml-recovery-codes-link.png)
+1. 在“Require SAML authentication（要求 SAML 身份验证）”下，单击 **Save your recovery codes（保存恢复代码）**。 ![用于在强制实施之前测试 SAML 配置的按钮屏幕截图](/assets/images/help/enterprises/saml-recovery-codes-link.png)
 
-2. To save your recovery codes, click **Download**, **Print**, or **Copy**. ![Screenshot of the buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
+2. 要保存恢复代码，请单击 **Download（下载）**、**Print（打印）**或 **Copy（复制）**。 ![用于下载、打印或复制恢复代码的按钮屏幕截图](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
index 52e8a21ed0..77ebda3ba7 100644
--- a/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/index.md
@@ -1,7 +1,7 @@
 ---
-title: Managing recovery codes for your enterprise
-shortTitle: Manage recovery codes
-intro: 'With SAML single sign-on recovery codes, you can access your enterprise account even when your identity provider is unavailable.'
+title: 管理企业的恢复代码
+shortTitle: 管理恢复代码
+intro: 使用 SAML 单点登录恢复代码，即使身份提供程序不可用，您也可以访问企业帐户。
 versions:
   ghec: '*'
 topics:
diff --git a/translations/zh-CN/content/admin/index.md b/translations/zh-CN/content/admin/index.md
index 0779c3cbb1..db889b0de8 100644
--- a/translations/zh-CN/content/admin/index.md
+++ b/translations/zh-CN/content/admin/index.md
@@ -100,8 +100,8 @@ featuredLinks:
     - '{% ifversion ghes %}/billing/managing-your-license-for-github-enterprise{% endif %}'
     - '{% ifversion ghes %}/admin/configuration/command-line-utilities{% endif %}'
     - '{% ifversion ghec %}/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise{% endif %}'
-    - '{% ifversion ghec %}/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise{% endif %}'
-    - '{% ifversion ghec %}/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks{% endif %}'
+    - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise{% endif %}'
+    - '{% ifversion ghec %}/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks{% endif %}'
     - '{% ifversion ghec %}/billing/managing-your-license-for-github-enterprise/using-visual-studio-subscription-with-github-enterprise/setting-up-visual-studio-subscription-with-github-enterprise{% endif %}'
     - /admin/configuration/configuring-github-connect/managing-github-connect
     - /admin/enterprise-support/about-github-enterprise-support
@@ -125,6 +125,7 @@ children:
   - /identity-and-access-management
   - /user-management
   - /policies
+  - /monitoring-activity-in-your-enterprise
   - /enterprise-management
   - /github-actions
   - /packages
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
index 4fbe447d97..26009b8f3d 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md
@@ -54,10 +54,9 @@ AMIs for {% data variables.product.prodname_ghe_server %} are available in the A
 
 ### Using the {% data variables.product.prodname_ghe_server %} portal to select an AMI
 
-{% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-appliance %}
-3. In the Select your platform drop-down menu, click **Amazon Web Services**.
-4. In the Select your AWS region drop-down menu, choose your desired region.
+3. Under "{% data variables.product.prodname_dotcom %} in the Cloud", select the "Select your platform" dropdown menu, and click **Amazon Web Services**.
+4. Select the "Select your AWS region" drop-down menu, and click your desired region.
 5. Take note of the AMI ID that is displayed.
 
 ### Using the AWS CLI to select an AMI
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
index 6b5a44aeb1..30e350f543 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-hyper-v.md
@@ -28,10 +28,9 @@ shortTitle: 在 Hyper-V 上安装
 
 ## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
-{% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **Hyper-V (VHD)**。
+4. 在“{% data variables.product.prodname_dotcom %} 本地”下，选择“Select your hypervisor（选择您的虚拟机管理程序）”下拉菜单，然后单击 **Hyper-V (VHD)**。
 5. 单击 **Download for Hyper-V (VHD)**。
 
 ## 创建 {% data variables.product.prodname_ghe_server %} 实例
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
index 5509309281..b3994b2192 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md
@@ -27,10 +27,9 @@ shortTitle: 在 OpenStack 上安装
 
 ## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
-{% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **OpenStack KVM (QCOW2)**。
+4. 在“{% data variables.product.prodname_dotcom %} 本地”下，选择“Select your hypervisor（选择您的虚拟机管理程序）”下拉菜单，然后单击 **OpenStack KVM (QCOW2)**。
 5. 单击 **Download for OpenStack KVM (QCOW2)**。
 
 ## 创建 {% data variables.product.prodname_ghe_server %} 实例
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
index 3ae5926aa8..7d8521277f 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md
@@ -31,10 +31,9 @@ shortTitle: 在 VMware 上安装
 
 ## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
-{% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **VMware ESXi/vSphere (OVA)**。
+4. 在“{% data variables.product.prodname_dotcom %} 本地”下，选择“Select your hypervisor（选择您的虚拟机管理程序）”下拉菜单，然后单击 **VMware ESXi/vSphere (OVA)**。
 5. 单击 **Download for VMware ESXi/vSphere (OVA)**。
 
 ## 创建 {% data variables.product.prodname_ghe_server %} 实例
diff --git a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
index b328bd0fea..13c33e5f14 100644
--- a/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
+++ b/translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md
@@ -34,10 +34,9 @@ shortTitle: 在 XenServer 上安装
 
 ## 下载 {% data variables.product.prodname_ghe_server %} 映像
 
-{% data reusables.enterprise_installation.enterprise-download-procedural %}
 {% data reusables.enterprise_installation.download-license %}
 {% data reusables.enterprise_installation.download-appliance %}
-4. 选择 {% data variables.product.prodname_dotcom %} 内部部署，然后单击 **XenServer (VHD)**。
+4. 在“{% data variables.product.prodname_dotcom %} 本地”下，选择“Select your hypervisor（选择您的虚拟机管理程序）”下拉菜单，然后单击 **XenServer (VHD)**。
 5. 要下载许可文件，请单击 **Download license**。
 
 ## 创建 {% data variables.product.prodname_ghe_server %} 实例
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
similarity index 91%
rename from translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
rename to translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
index 50da76d03a..d98946a390 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/activity-dashboard.md
@@ -6,6 +6,7 @@ redirect_from:
   - /enterprise/admin/installation/activity-dashboard
   - /enterprise/admin/user-management/activity-dashboard
   - /admin/user-management/activity-dashboard
+  - /admin/user-management/monitoring-activity-in-your-enterprise/activity-dashboard
 versions:
   ghes: '*'
   ghae: '*'
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
new file mode 100644
index 0000000000..d88073aa78
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/index.md
@@ -0,0 +1,17 @@
+---
+title: Exploring user activity in your enterprise
+intro: 'You can view user and system activity by leveraging dashboards, webhooks and log forwarding.'
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /activity-dashboard
+  - /viewing-push-logs
+  - /log-forwarding
+  - /managing-global-webhooks
+shortTitle: Explore user activity
+---
+
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
similarity index 98%
rename from translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
rename to translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
index e5a9096573..99bdb91a66 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding.md
@@ -7,6 +7,7 @@ redirect_from:
   - /enterprise/admin/enterprise-management/log-forwarding
   - /admin/enterprise-management/log-forwarding
   - /admin/user-management/log-forwarding
+  - /admin/user-management/monitoring-activity-in-your-enterprise/log-forwarding
 versions:
   ghes: '*'
   ghae: '*'
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
similarity index 98%
rename from translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
rename to translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
index 831cc5fd54..0b58aa42ac 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md
@@ -13,6 +13,7 @@ redirect_from:
   - /articles/configuring-webhooks-for-organization-events-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise-account/configuring-webhooks-for-organization-events-in-your-enterprise-account
   - /github/setting-up-and-managing-your-enterprise/configuring-webhooks-for-organization-events-in-your-enterprise-account
+  - /admin/user-management/monitoring-activity-in-your-enterprise/managing-global-webhooks
 versions:
   ghec: '*'
   ghes: '*'
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
similarity index 90%
rename from translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
rename to translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
index 5b895570bd..623b0da63f 100644
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md
@@ -6,6 +6,7 @@ redirect_from:
   - /enterprise/admin/installation/viewing-push-logs
   - /enterprise/admin/user-management/viewing-push-logs
   - /admin/user-management/viewing-push-logs
+  - /admin/user-management/monitoring-activity-in-your-enterprise/viewing-push-logs
 versions:
   ghes: '*'
   ghae: '*'
@@ -41,6 +42,6 @@ topics:
 {% data reusables.enterprise_installation.ssh-into-instance %}
 1. 在相应的 Git 仓库中，打开审核日志文件：
   ```shell
-  ghe-repo <em>owner</em>/<em>repository</em> -c "less audit_log"
+  ghe-repo <em>owner</em>/<em>repository</em> -c "cat audit_log"
   ```
 {% endif %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/index.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/index.md
new file mode 100644
index 0000000000..e76f794f08
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/index.md
@@ -0,0 +1,17 @@
+---
+title: 监控企业中的活动
+intro: 'You can view user and system activity by leveraging audit logs{% ifversion ghes or ghae %}, push logs, dashboards, webhooks, and log forwarding{% else %}and webhooks{% endif %}.'
+redirect_from:
+  - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /reviewing-audit-logs-for-your-enterprise
+  - /exploring-user-activity
+shortTitle: Monitor activity
+---
+
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..fde9bc57eb
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,61 @@
+---
+title: About the audit log for your enterprise
+intro: 'To support debugging and internal and external compliance, {% data variables.product.product_name %} provides logs of audited{% ifversion ghes %} system,{% endif %} user, organization, and repository events.'
+shortTitle: About audit logs
+redirect_from:
+  - /enterprise/admin/articles/audit-logging
+  - /enterprise/admin/installation/audit-logging
+  - /enterprise/admin/user-management/audit-logging
+  - /admin/user-management/audit-logging
+  - /admin/user-management/monitoring-activity-in-your-enterprise/audit-logging
+  - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
+  - /admin/authentication/managing-your-enterprise-users-with-your-identity-provider/auditing-activity-in-your-enterprise
+  - /admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/auditing-activity-in-your-enterprise
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: overview
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+---
+
+## About audit logs
+
+{% data reusables.audit_log.retention-periods %}
+
+{% data reusables.audit_log.audit-log-search-list-info-about-action %}
+
+In addition to viewing your audit log, you can monitor activity in your enterprise in other ways, such as {% ifversion ghes or ghae %}viewing push logs and {% endif %}managing global webhooks. For more information, see "[Exploring user activity in your enterprise](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity)."
+
+## Using your audit logs
+
+As an enterprise owner{% ifversion ghes %} or site administrator{% endif %}, you can interact with the audit log data for your enterprise in several ways:
+- You can view the audit log for your enterprise. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
+- You can search the audit log for specific events{% ifversion ghec %} and export audit log data{% endif %}. For more information, see "[Searching the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise)"{% ifversion ghec %} and "[Exporting the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)"{% endif %}.
+{%- ifversion ghec %}
+- 您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+{%- else %}
+- You can forward audit and system logs, from your enterprise to an third-party hosted monitoring system. 更多信息请参阅“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)。”
+{%- endif %}
+{%- ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
+- You can use the Audit log API to view actions performed in your enterprise. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
+{%- endif %}
+
+For a full list of audit log actions that may appear in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+
+{% ifversion ghec %}
+## Git events
+
+Git events data, such as cloning, fetching, and pushing is logged. For more information, see "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+
+{% endif %}
+
+## 延伸阅读
+- “[查看组织的审核日志](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)”
+{%- ifversion ghes %}
+- "[About system logs](/admin/enterprise-management/monitoring-your-appliance/about-system-logs)"
+{%- endif %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..b5bb1d3431
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,28 @@
+---
+title: Accessing the audit log for your enterprise
+intro: You can view aggregated actions from all of the organizations owned by an enterprise account in the enterprise's audit log.
+shortTitle: Access audit logs
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can access the audit log.'
+redirect_from:
+  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
+  - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+---
+
+{% data reusables.audit_log.retention-periods %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
new file mode 100644
index 0000000000..85b8c22c75
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md
@@ -0,0 +1,1249 @@
+---
+title: Audit log events for your enterprise
+intro: Learn about audit log events recorded for your enterprise.
+shortTitle: Audit log events
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can interact with the audit log.'
+miniTocMaxHeadingLevel: 4
+redirect_from:
+  - /enterprise/admin/articles/audited-actions
+  - /enterprise/admin/installation/audited-actions
+  - /enterprise/admin/user-management/audited-actions
+  - /admin/user-management/audited-actions
+  - /admin/user-management/monitoring-activity-in-your-enterprise/audited-actions
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+type: reference
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - Security
+---
+
+{%- ifversion fpt or ghec %}
+### `account` 类操作
+
+| 操作                                    | 描述                                                                                                                                                                                                                                                 |
+| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `account.billing_plan_change`         | An organization's billing cycle changed. 更多信息请参阅“[更改计费周期的持续时间](/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)”。                                                                                       |
+| `account.plan_change`                 | An organization's subscription changed. For more information, see "[About billing for GitHub accounts](/billing/managing-billing-for-your-github-account/about-billing-for-github-accounts)."                                                      |
+| `account.pending_plan_change`         | An organization owner or billing manager canceled or downgraded a paid subscription. 更多信息请参阅“[升级或降低对结算过程有何影响？](/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process)”                    |
+| `account.pending_subscription_change` | A {% data variables.product.prodname_marketplace %} free trial started or expired. For more information, see "[About billing for GitHub Marketplace](/billing/managing-billing-for-github-marketplace-apps/about-billing-for-github-marketplace)." |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `advisory_credit` 类操作
+
+| 操作                        | 描述                                                                                                                                         |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
+| `advisory_credit.accept`  | Someone accepted credit for a security advisory. 更多信息请参阅“[编辑安全通告](/github/managing-security-vulnerabilities/editing-a-security-advisory)”。 |
+| `advisory_credit.create`  | The administrator of a security advisory added someone to the credit section.                                                              |
+| `advisory_credit.decline` | Someone declined credit for a security advisory.                                                                                           |
+| `advisory_credit.destroy` | The administrator of a security advisory removed someone from the credit section.                                                          |
+{%- endif %}
+
+### `artifact` category actions
+
+| 操作                 | 描述                                            |
+| ------------------ | --------------------------------------------- |
+| `artifact.destroy` | A workflow run artifact was manually deleted. |
+
+{%- ifversion ghec %}
+### `audit_log_streaming` category actions
+
+| 操作                            | 描述                                                                                                                  |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| `audit_log_streaming.check`   | A manual check was performed of the endpoint configured for audit log streaming.                                    |
+| `audit_log_streaming.create`  | An endpoint was added for audit log streaming.                                                                      |
+| `audit_log_streaming.update`  | An endpoint configuration was updated for audit log streaming, such as the stream was paused, enabled, or disabled. |
+| `audit_log_streaming.destroy` | An audit log streaming endpoint was deleted.                                                                        |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `billing` 类操作
+
+| 操作                            | 描述                                                                                                                                                                                             |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `billing.change_billing_type` | An organization changed how it paid for {% data variables.product.prodname_dotcom %}. 更多信息请参阅“[添加或编辑付款方式](/billing/managing-your-github-billing-settings/adding-or-editing-a-payment-method)”。 |
+| `billing.change_email`        | An organization's billing email address changed. 更多信息请参阅“[设置帐单邮箱](/billing/managing-your-github-billing-settings/setting-your-billing-email)”。                                                 |
+{%- endif %}
+
+### `business` 类操作
+
+| 操作                   | 描述                                                                                                   |
+| -------------------- | ---------------------------------------------------------------------------------------------------- |
+| `business.add_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was added to an enterprise. |
+{%- ifversion ghec %}
+| `business.add_billing_manager` | A billing manager was added to an enterprise.
+{%- endif %}
+| `business.add_organization` | An organization was added to an enterprise.
+{%- ifversion ghec %}
+| `business.add_support_entitlee` | A support entitlement was added to a member of an enterprise. 更多信息请参阅“[管理企业的支持权利](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
+{%- endif %}
+{%- ifversion ghes > 3.0 or ghae %}
+| `business.advanced_security_policy_update` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} created, updated, or removed a policy for {% data variables.product.prodname_GH_advanced_security %}. 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_advanced_security %} 的策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。
+{%- endif %}
+{%- ifversion ghec %}
+| `business.cancel_admin_invitation` | An invitation for someone to be an owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was canceled. | `business.cancel_billing_manager_invitation` | An invitation for someone to be an billing manager of an enterprise was canceled.
+{%- endif %}
+{%- ifversion ghes %}
+| `business.clear_actions_settings` | An enterprise owner or site administrator cleared {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+{%- endif %}
+| `business.clear_default_repository_permission` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the base repository permission policy setting for an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)." | `business.clear_members_can_create_repos`      | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared a restriction on repository creation in organizations in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。 | `business.create`                              | An enterprise was created.
+{%- ifversion ghec %}
+| `business.disable_saml` | SAML single sign-on was disabled for an enterprise.
+{%- endif %}
+| `business.disable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was disabled.
+{%- ifversion ghec %}
+| `business.enable_saml` | SAML single sign-on was enabled for an enterprise.
+{%- endif %}
+| `business.enable_two_factor_requirement` | The requirement for members to have two-factor authentication enabled to access an enterprise was enabled.
+{%- ifversion ghec %}
+| `business.enterprise_server_license_download` | A {% data variables.product.prodname_ghe_server %} license was downloaded. | `business.import_license_usage` | License usage information was imported from a {% data variables.product.prodname_ghe_server %} instance to an enterprise account on {% data variables.product.prodname_dotcom_the_website %}. | `business.invite_admin` | An invitation for someone to be an enterprise owner{% ifversion ghes %} or site administrator{% endif %} of an enterprise was sent. | `business.invite_billing_manager` | An invitation for someone to be an billing manager of an enterprise was sent.
+{%- endif %}
+| `business.members_can_update_protected_branches.clear` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unset a policy for whether members of an enterprise can update protected branches on repositories for individual organizations. Organization administrators can choose whether to allow updating protected branches settings. | `business.members_can_update_protected_branches.disable` | The ability for enterprise members to update branch protection rules was disabled. Only enterprise owners can update protected branches. | `business.members_can_update_protected_branches.enable` | The ability for enterprise members to update branch protection rules was enabled. Enterprise owners and members can update protected branches. | `business.remove_admin` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} was removed from an enterprise.
+{%- ifversion ghes > 3.1 %}
+| `business.referrer_override_enable` | An enterprise owner or site administrator enabled the referrer policy override. 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。 | `business.referrer_override_disable` | An enterprise owner or site administrator disabled the referrer policy override. 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。
+{%- endif %}
+{%- ifversion ghec %}
+| `business.remove_billing_manager` | A billing manager was removed from an enterprise. | `business.remove_member` | A member was removed from an enterprise.
+{%- endif %}
+| `business.remove_organization` | An organization was removed from an enterprise.
+{%- ifversion ghec %}
+| `business.remove_support_entitlee` | A support entitlement was removed from a member of an enterprise. 更多信息请参阅“[管理企业的支持权利](/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
+{%- endif %}
+| `business.rename_slug` | The slug for the enterprise URL was renamed.
+{%- ifversion ghec %}
+| `business.revoke_external_identity` | The external identity for a member in an enterprise was revoked. | `business.revoke_sso_session` | The SAML single sign-on session for a member in an enterprise was revoked.
+{%- endif %}
+{%- ifversion ghec %}
+| `business.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an enterprise. 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_actions %} 的策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)”。
+{%- endif %}
+| `business.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs was changed for an enterprise. For more information, see "[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-artifact-and-log-retention-in-your-enterprise)."
+{%- ifversion ghec or ghes %}
+| `business.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "{% ifversion ghec %}[Enforcing policies for {% data variables.product.prodname_actions %} in an enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-private-repositories){% else ifversion ghes > 2.22 %}[Enabling workflows for private repository forks](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enforcing-github-actions-policies-for-your-enterprise#enabling-workflows-for-private-repository-forks){% endif %}."
+{%- endif %}
+{%- ifversion ghes %}
+| `business.update_actions_settings` | An enterprise owner or site administrator updated {% data variables.product.prodname_actions %} policy settings for an enterprise. For more information, see "[Enforcing policies for GitHub Actions in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise)."
+{%- endif %}
+| `business.update_default_repository_permission` | The base repository permission setting was updated for all organizations in an enterprise. For more information, see "[Enforcing a policy for base repository permissions](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-base-repository-permissions)." | `business.update_member_repository_creation_permission` | The repository creation setting was updated for an enterprise. For more information, see "[Enforcing a policy for repository creation](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." | `business.update_member_repository_invitation_permission` | The policy setting for enterprise members inviting outside collaborators to repositories was updated. For more information, see "[Enforcing a policy for inviting outside collaborators to repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories)."
+{%- ifversion ghec %}
+| `business.update_saml_provider_settings` | The SAML single sign-on provider settings for an enterprise were updated.
+{%- endif %}
+
+{%- if secret-scanning-audit-log-custom-patterns %}
+### `business_secret_scanning_custom_pattern` category actions
+
+| 操作 | 描述                                                                                                                                                                                                                                                                                |
+| -- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|    | `business_secret_scanning_custom_pattern.create` | An enterprise-level custom pattern is published for secret scanning. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-enterprise-account)”。 |
+|    | `business_secret_scanning_custom_pattern.delete` | An enterprise-level custom pattern is removed from secret scanning.                                                                                                                                                            |
+|    | `business_secret_scanning_custom_pattern.update` | Changes to an enterprise-level custom pattern are saved for secret scanning.                                                                                                                                                   |
+{%- endif %}
+
+### `checks` category actions
+
+| 操作                             | 描述                                                                                                                                                                                                                                                      |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `checks.auto_trigger_disabled` | Automatic creation of check suites was disabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)." |
+| `checks.auto_trigger_enabled`  | Automatic creation of check suites was enabled on a repository in the organization or enterprise. For more information, see "[Update repository preferences for check suites](/rest/reference/checks#update-repository-preferences-for-check-suites)."  |
+{%- ifversion fpt or ghec %}
+| `checks.delete_logs` | Logs in a check suite were deleted.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `codespaces` 类操作
+
+| 操作                                             | 描述                                                                                                                                                                                                                              |
+| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `codespaces.connect`                           | A codespace was started.                                                                                                                                                                                                        |
+| `codespaces.create`                            | A user [created a codespace](/github/developing-online-with-codespaces/creating-a-codespace).                                                                                                                                   |
+| `codespaces.destroy`                           | A user [deleted a codespace](/github/developing-online-with-codespaces/deleting-a-codespace).                                                                                                                                   |
+| `codespaces.allow_permissions`                 | A codespace using custom permissions from its `devcontainer.json` file was launched.                                                                                                                                            |
+| `codespaces.attempted_to_create_from_prebuild` | An attempt to create a codespace from a prebuild was made.                                                                                                                                                                      |
+| `codespaces.create_an_org_secret`              | A user created an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces)  |
+| `codespaces.update_an_org_secret`              | A user updated an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `codespaces.remove_an_org_secret`              | A user removed an organization-level [secret for {% data variables.product.prodname_codespaces %}](/github/developing-online-with-codespaces/managing-encrypted-secrets-for-codespaces#about-encrypted-secrets-for-codespaces). |
+| `codespaces.manage_access_and_security`        | A user updated [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).                                                                              |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `commit_comment` category actions
+
+| 操作                       | 描述                            |
+| ------------------------ | ----------------------------- |
+| `commit_comment.destroy` | A commit comment was deleted. |
+| `commit_comment.update`  | A commit comment was updated. |
+{%- endif %}
+
+{%- ifversion ghes %}
+### `config_entry` category actions
+
+| 操作                     | 描述                                                                                                                                                                                                                                                                                                                                                                                                        |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `config_entry.create`  | A configuration setting was created. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. |
+| `config_entry.destroy` | A configuration setting was deleted. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings. |
+| `config_entry.update`  | A configuration setting was edited. These events are only visible in the site admin audit log. The type of events recorded relate to:</br>- Enterprise settings and policies</br>- Organization and repository permissions and settings</br>- Git, Git LFS, {% data variables.product.prodname_github_connect %}, {% data variables.product.prodname_registry %}, project, and code security settings.  |
+{%- endif %}
+
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
+### `dependabot_alerts` 类操作
+
+| 操作                          | 描述                                                                                                                                                                                                                                                                                                                                                               |
+| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dependabot_alerts.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependabot_alerts.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all existing {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                          |
+
+### `dependabot_alerts_new_repos` 类操作
+
+| 操作                                    | 描述                                                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dependabot_alerts_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependabot_alerts_new_repos.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.                                                                                                                                          |
+
+### `dependabot_repository_access`category actions
+
+| 操作                                                  | 描述                                                                                              |
+| --------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| `dependabot_repository_access.repositories_updated` | The repositories that {% data variables.product.prodname_dependabot %} can access were updated. |
+{%- endif %}
+
+{%- ifversion fpt or ghec or ghes > 3.2 %}
+### `dependabot_security_updates` 类操作
+
+| 操作                                    | 描述                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dependabot_security_updates.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependabot_security_updates.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all existing repositories.                                                                                                                                          |
+
+### `dependabot_security_updates_new_repos` 类操作
+
+| 操作                                              | 描述                                                                                                                                                                                                                                                                                                                      |
+| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dependabot_security_updates_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependabot_security_updates_new_repos.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled {% data variables.product.prodname_dependabot_security_updates %} for all new repositories.                                                                                                                                          |
+{%- endif %}
+
+{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
+### `dependency_graph` 类操作
+
+| 操作                         | 描述                                                                                                                                                                                                                                                                            |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dependency_graph.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all existing repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependency_graph.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all existing repositories.                                                                                                                                          |
+
+### `dependency_graph_new_repos` 类操作
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                                       |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `dependency_graph_new_repos.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the dependency graph for all new repositories. 更多信息请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。 |
+| `dependency_graph_new_repos.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the dependency graph for all new repositories.                                                                                                                                          |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `discussion` category actions
+
+| 操作                   | 描述                             |
+| -------------------- | ------------------------------ |
+| `discussion.destroy` | A team discussion was deleted. |
+
+### `discussion_comment` category actions
+
+| 操作                           | 描述                                                                                                                                                     |
+| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `discussion_comment.destroy` | A [comment on a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment). |
+| `discussion_comment.update`  | A [comment on a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment).   |
+
+### `discussion_post` 类操作
+
+| 操作                        | 描述                                                                                                                       |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `discussion_post.destroy` | A [team discussion post was deleted](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion). |
+| `discussion_post.update`  | A [team discussion post was edited](/organizations/collaborating-with-your-team/editing-or-deleting-a-team-discussion).  |
+
+### `discussion_post_reply` 类操作
+
+| 操作                              | 描述                                                                                                                                                   |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `discussion_post_reply.destroy` | A [reply to a team discussion post was deleted](/communities/moderating-comments-and-conversations/managing-disruptive-comments#deleting-a-comment). |
+| `discussion_post_reply.update`  | A [reply to a team discussion post was edited](/communities/moderating-comments-and-conversations/managing-disruptive-comments#editing-a-comment).   |
+{%- endif %}
+
+{%- ifversion ghec or ghes %}
+### `dotcom_connection` category actions
+
+| 操作                                       | 描述                                                                                                                                                      |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dotcom_connection.create`               | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was created.          |
+| `dotcom_connection.destroy`              | A {% data variables.product.prodname_github_connect %} connection to {% data variables.product.prodname_dotcom_the_website %} was deleted.          |
+| `dotcom_connection.token_updated`        | The {% data variables.product.prodname_github_connect %} connection token for {% data variables.product.prodname_dotcom_the_website %} was updated. |
+| `dotcom_connection.upload_license_usage` | {% data variables.product.prodname_ghe_server %} license usage was manually uploaded to {% data variables.product.prodname_ghe_cloud %}.            |
+| `dotcom_connection.upload_usage_metrics` | {% data variables.product.prodname_ghe_server %} usage metrics were uploaded to {% data variables.product.prodname_dotcom_the_website %}.           |
+{%- endif %}
+
+### `enterprise` 类别操作
+
+| 操作                                               | 描述                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise.config.disable_anonymous_git_access` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled anonymous Git read access for repositories in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。                                                                                      |
+| `enterprise.config.enable_anonymous_git_access`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled anonymous Git read access for repositories in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。                                                                                       |
+| `enterprise.config.lock_anonymous_git_access`    | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} locked anonymous Git read access to prevent repository admins from changing existing anonymous Git read access settings for repositories in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。 |
+| `enterprise.config.unlock_anonymous_git_access`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} unlocked anonymous Git read access to allow repository admins to change existing anonymous Git read access settings for repositories in the enterprise. 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。     |
+| `enterprise.register_self_hosted_runner`         | A new {% data variables.product.prodname_actions %} self-hosted runner was registered. 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。                                                                                                                                                        |
+| `enterprise.remove_self_hosted_runner`           | A {% data variables.product.prodname_actions %} self-hosted runner was removed. 更多信息请参阅“[从仓库移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)”。                                                                                                                                                                         |
+| `enterprise.runner_group_created`                | A {% data variables.product.prodname_actions %} self-hosted runner group was created. 更多信息请参阅“[为组织创建自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)”。                                                                                                                    |
+| `enterprise.runner_group_removed`                | A {% data variables.product.prodname_actions %} self-hosted runner group was removed. 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。                                                                                                                                           |
+| `enterprise.runner_group_renamed`                | A {% data variables.product.prodname_actions %} self-hosted runner group was renamed. 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。                                                                                                                 |
+| `enterprise.runner_group_updated`                | The configuration of a {% data variables.product.prodname_actions %} self-hosted runner group was changed. 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。                                                                                            |
+| `enterprise.runner_group_runner_removed`         | The REST API was used to remove a {% data variables.product.prodname_actions %} self-hosted runner from a group. 更多信息请参阅“[为组织从组中删除自托管运行器](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)”。                                                                                                                                                |
+| `enterprise.runner_group_runners_added`          | A {% data variables.product.prodname_actions %} self-hosted runner was added to a group. 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。                                                                                                                                   |
+| `enterprise.runner_group_runners_updated`        | A {% data variables.product.prodname_actions %} runner group's list of members was updated. 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。                                                                                                                                                                           |
+{%- ifversion ghec %}
+| `enterprise.runner_group_visiblity_updated` | The visibility of a {% data variables.product.prodname_actions %} self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)."
+{%- endif %}
+{%- ifversion ghec or ghes > 3.1 or ghae %}
+| `enterprise.self_hosted_runner_online` | The {% data variables.product.prodname_actions %} runner application was started. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。 | `enterprise.self_hosted_runner_offline` | The {% data variables.product.prodname_actions %} runner application was stopped. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。
+{%- endif %}
+{%- ifversion ghec or ghes %}
+| `enterprise.self_hosted_runner_updated` | The {% data variables.product.prodname_actions %} runner application was updated. 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。
+{%- endif %}
+
+{%- ifversion ghec %}
+### `enterprise_domain` category actions
+
+| 操作                          | 描述                                                                                                                                                                                                                                                                                      |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise_domain.approve` | An enterprise domain was approved for an enterprise. For more information, see "[Approving a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#approving-a-domain-for-your-enterprise-account)." |
+| `enterprise_domain.create`  | An enterprise domain was added to an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)."     |
+| `enterprise_domain.destroy` | An enterprise domain was removed from an enterprise. For more information, see "[Removing an approved or verified domain](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#removing-an-approved-or-verified-domain)."               |
+| `enterprise_domain.verify`  | An enterprise domain was verified for an enterprise. For more information, see "[Verifying a domain for your enterprise account](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise#verifying-a-domain-for-your-enterprise-account)." |
+
+### `enterprise_installation` category actions
+
+| 操作                                      | 描述                                                                                                                                                                                     |
+| --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `enterprise_installation.create`        | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was created.                    |
+| `enterprise_installation.destroy`       | The {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was deleted.                    |
+| `enterprise_installation.token_updated` | The token belonging to {% data variables.product.prodname_github_app %} associated with an {% data variables.product.prodname_github_connect %} enterprise connection was updated. |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `environment` 类别操作
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                                                    |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `environment.add_protection_rule`    | A {% data variables.product.prodname_actions %} environment protection rule was created via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." |
+| `environment.create_actions_secret`  | A secret was created for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."                      |
+| `environment.delete`                 | An environment was deleted via the API. For more information, see "[Deleting an environment](/actions/deployment/targeting-different-environments/using-environments-for-deployment#deleting-an-environment)."                                                                        |
+| `environment.remove_actions_secret`  | A secret was deleted for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."                      |
+| `environment.remove_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was deleted via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." |
+| `environment.update_actions_secret`  | A secret was updated for a {% data variables.product.prodname_actions %} environment via the API. For more information, see "[Environment secrets](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-secrets)."                      |
+| `environment.update_protection_rule` | A {% data variables.product.prodname_actions %} environment protection rule was updated via the API. For more information, see "[Environment protection rules](/actions/deployment/targeting-different-environments/using-environments-for-deployment#environment-protection-rules)." |
+{%- endif %}
+
+{%- ifversion ghae %}
+### `external_group` 类操作
+
+| 操作                         | 描述                                                                                                                                                                                                                                                                |
+| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `external_group.delete`    | An Okta group was deleted. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。                                                                  |
+| `external_group.link`      | An Okta group was mapped to a {% data variables.product.prodname_ghe_managed %} team. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。     |
+| `external_group.provision` | An Okta group was mapped to a team on {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。  |
+| `external_group.unlink`    | An Okta group was unmapped from a {% data variables.product.prodname_ghe_managed %} team. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。 |
+| `external_group.update`    | An Okta group's settings were updated. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。                                                      |
+
+### `external_identity` 类操作
+| 操作                              | 描述                                                                                                                                                                                                                                                                                                                        |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `external_identity.deprovision` | A user was removed from an Okta group and was subsequently deprovisioned from {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。                  |
+| `external_identity.provision`   | An Okta user was added to an Okta group and was subsequently provisioned to the mapped team on {% data variables.product.prodname_ghe_managed %}. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。 |
+| `external_identity.update`      | An Okta user's settings were updated. 更多信息请参阅“[将 Okta 组映射到团队](/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。                                                                                                               |
+{%- endif %}
+
+### `gist` category actions
+
+| 操作                       | 描述                                   |
+| ------------------------ | ------------------------------------ |
+| `gist.create`            | A gist is created.                   |
+| `gist.destroy`           | A gist is deleted.                   |
+| `gist.visibility_change` | The visibility of a gist is changed. |
+
+### `git` 类操作
+
+| 操作          | 描述                                      |
+| ----------- | --------------------------------------- |
+| `git.clone` | A repository was cloned.                |
+| `git.fetch` | Changes were fetched from a repository. |
+| `git.push`  | Changes were pushed to a repository.    |
+
+### `hook` 类操作
+
+| 操作 | 描述 |
+| -- | -- |
+|    |    |
+{%- ifversion ghes or ghae %}
+| `hook.active_changed`             | A hook's active status was updated.
+{%- endif %}
+| `hook.config_changed`             | A hook's configuration was changed. | `hook.create`                     | A new hook was added. | `hook.destroy`                    | A hook was deleted. | `hook.events_changed`             | A hook's configured events were changed.
+
+### `integration` category actions
+
+| 操作                                 | 描述                                                                                       |
+| ---------------------------------- | ---------------------------------------------------------------------------------------- |
+| `integration.create`               | An integration was created.                                                              |
+| `integration.destroy`              | An integration was deleted.                                                              |
+| `integration.manager_added`        | A member of an enterprise or organization was added as an integration manager.           |
+| `integration.manager_removed`      | A member of an enterprise or organization was removed from being an integration manager. |
+| `integration.transfer`             | Ownership of an integration was transferred to another user or organization.             |
+| `integration.remove_client_secret` | A client secret for an integration was removed.                                          |
+| `integration.revoke_all_tokens`    | All user tokens for an integration were requested to be revoked.                         |
+| `integration.revoke_tokens`        | Token(s) for an integration were revoked.                                                |
+
+### `integration_installation`category actions
+
+| 操作                                               | 描述                                              |
+| ------------------------------------------------ | ----------------------------------------------- |
+| `integration_installation.contact_email_changed` | A contact email for an integration was changed. |
+| `integration_installation.create`                | An integration was installed.                   |
+| `integration_installation.destroy`               | An integration was uninstalled.                 |
+| `integration_installation.repositories_added`    | Repositories were added to an integration.      |
+| `integration_installation.repositories_removed`  | Repositories were removed from an integration.  |
+{%- ifversion fpt or ghec %}
+| `integration_installation.suspend` | An integration was suspended. | `integration_installation.unsuspend` | An integration was unsuspended.
+{%- endif %}
+| `integration_installation.version_updated` | Permissions for an integration were updated.
+
+### `integration_installation_request` 类操作
+
+| 操作                                        | 描述                                                                                                                                                                        |
+| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `integration_installation_request.create` | An member requested that an owner install an integration for use in an enterprise or organization.                                                                        |
+| `integration_installation_request.close`  | A request to install an integration for use in an enterprise or organization was either approved or denied by an owner, or canceled by the member who opened the request. |
+
+{%- ifversion ghec or ghae %}
+### `ip_allow_list` 类操作
+
+| 操作                                         | 描述                                                                    |
+| ------------------------------------------ | --------------------------------------------------------------------- |
+| `ip_allow_list.enable`                     | IP 允许列表已启用。                                                           |
+| `ip_allow_list.enable_for_installed_apps`  | 已为安装的 {% data variables.product.prodname_github_apps %} 启用 IP 允许列表。 |
+| `ip_allow_list.disable`                    | IP 允许列表已禁用。                                                           |
+| `ip_allow_list.disable_for_installed_apps` | 已为安装的 {% data variables.product.prodname_github_apps %} 禁用 IP 允许列表。 |
+
+### `ip_allow_list_entry` 类操作
+
+| 操作                            | 描述                  |
+| ----------------------------- | ------------------- |
+| `ip_allow_list_entry.create`  | IP 地址已添加到 IP 允许列表中。 |
+| `ip_allow_list_entry.update`  | IP 地址或描述已更改。        |
+| `ip_allow_list_entry.destroy` | IP 地址已从 IP 允许列表中删除。 |
+{%- endif %}
+
+### `issue` 类操作
+
+| 操作               | 描述                                                                                                                                                         |
+| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `issue.destroy`  | 已从仓库中删除问题。 更多信息请参阅“[删除议题](/issues/tracking-your-work-with-issues/deleting-an-issue)”。                                                                      |
+| `issue.pinned`   | An issue was pinned to a repository. 更多信息请参阅“[将议题固定到仓库](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)”。                      |
+| `issue.transfer` | An issue was transferred to another repository. 更多信息请参阅“[将议题转让给其他仓库](/issues/tracking-your-work-with-issues/transferring-an-issue-to-another-repository)”。 |
+| `issue.unpinned` | An issue was unpinned from a repository. 更多信息请参阅“[将议题固定到仓库](/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository)”。                  |
+
+### `issue_comment` category actions
+
+| 操作                       | 描述                                                     |
+| ------------------------ | ------------------------------------------------------ |
+| `issue_comment.destroy`  | A comment on an issue was deleted from the repository. |
+| `issue_comment.pinned`   | A comment on an issue was pinned to a repository.      |
+| `issue_comment.unpinned` | A comment on an issue was unpinned from a repository.  |
+| `issue_comment.update`   | 已更改问题的正文文本（初始注释）。                                      |
+
+### `issues` category actions
+
+| 操作                              | 描述                                                                                                                                                                                                                                                                                                                                                                                           |
+| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `issues.deletes_disabled`       | The ability for enterprise members to delete issues was disabled. Members cannot delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)."                       |
+| `issues.deletes_enabled`        | The ability for enterprise members to delete issues was enabled. Members can delete issues in any organizations in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)."                           |
+| `issues.deletes_policy_cleared` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing members to delete issues in an enterprise. For more information, see "[Enforcing a policy for deleting issues](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-deleting-issues)." |
+
+{%- ifversion fpt or ghec %}
+### `marketplace_agreement_signature` 类操作
+
+| 操作                                       | 描述                                                                                                                    |
+| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
+| `marketplace_agreement_signature.create` | A user signed the {% data variables.product.prodname_marketplace %} Developer Agreement on behalf of an organization. |
+
+### `marketplace_listing` 类操作
+
+| 操作                                    | 描述                                                                                                    |
+| ------------------------------------- | ----------------------------------------------------------------------------------------------------- |
+| `marketplace_listing.approve`         | A listing was approved for inclusion in {% data variables.product.prodname_marketplace %}.            |
+| `marketplace_listing.change_category` | A category for a listing for an app in {% data variables.product.prodname_marketplace %} was changed. |
+| `marketplace_listing.create`          | A listing for an app in {% data variables.product.prodname_marketplace %} was created.                |
+| `marketplace_listing.delist`          | A listing was removed from {% data variables.product.prodname_marketplace %}.                         |
+| `marketplace_listing.redraft`         | A listing was sent back to draft state.                                                               |
+| `marketplace_listing.reject`          | A listing was not accepted for inclusion in {% data variables.product.prodname_marketplace %}.        |
+{%- endif %}
+
+### `members_can_create_pages` 类操作
+
+| 操作                                 | 描述                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_pages.disable` | The ability for members to publish {% data variables.product.prodname_pages %} was disabled. Members cannot publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |
+| `members_can_create_pages.enable`  | The ability for members to publish {% data variables.product.prodname_pages %} was enabled. Members can publish {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."     |
+
+### `members_can_create_private_pages` category actions
+
+| 操作                                         | 描述                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_private_pages.disable` | The ability for members to publish private {% data variables.product.prodname_pages %} was disabled. Members cannot publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |
+| `members_can_create_private_pages.enable`  | The ability for members to publish private {% data variables.product.prodname_pages %} was enabled. Members can publish private {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."     |
+
+### `members_can_create_public_pages` category actions
+
+| 操作                                        | 描述                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_create_public_pages.disable` | The ability for members to publish public {% data variables.product.prodname_pages %} was disabled. Members cannot publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)." |
+| `members_can_create_public_pages.enable`  | The ability for members to publish public {% data variables.product.prodname_pages %} was enabled. Members can publish public {% data variables.product.prodname_pages %} in an organization. For more information, see "[Managing the publication of GitHub Pages sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)."     |
+
+{%- ifversion ghec or ghes or ghae %}
+### `members_can_delete_repos` category actions
+
+| 操作                                 | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `members_can_delete_repos.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for deleting or transfering repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)." |
+| `members_can_delete_repos.disable` | The ability for enterprise members to delete repositories was disabled. Members cannot delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)."                       |
+| `members_can_delete_repos.enable`  | The ability for enterprise members to delete repositories was enabled. Members can delete or transfer repositories in any organizations in an enterprise. For more information, see "[Enforcing a policy for repository deletion and transfer](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-deletion-and-transfer)."                           |
+
+### `members_can_view_dependency_insights` category actions
+
+| 操作                                             | 描述                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `members_can_view_dependency_insights.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for viewing dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+| `members_can_view_dependency_insights.disable` | The ability for enterprise members to view dependency insights was disabled. Members cannot view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+| `members_can_view_dependency_insights.enable`  | The ability for enterprise members to view dependency insights was enabled. Members can view dependency insights in any organizations in an enterprise.{% ifversion ghec %} For more information, see "[Enforcing a policy for visibility of dependency insights](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-dependency-insights-in-your-enterprise)."{% endif %}
+
+### `migration` category actions
+
+| 操作                       | 描述                                                                                                                                                                                                                                                                                                             |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `migration.create`       | A migration file was created for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance.    |
+| `migration.destroy_file` | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was deleted.    |
+| `migration.download`     | A migration file for transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance was downloaded. |
+{%- endif %}
+
+### `oauth_access` 类操作
+
+| 操作 | 描述 |
+| -- | -- |
+|    |    |
+
+
+`oauth_access.create`   | An [OAuth access token][] was generated for a user account. 更多信息请参阅“[创建个人访问令牌](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)”。 `oauth_access.destroy`  | An [OAuth access token][] was deleted from a user account.
+
+### `oauth_application` 类操作
+
+| 操作                          | 描述                                                                       |
+| --------------------------- | ------------------------------------------------------------------------ |
+| `oauth_application.create`  | An [OAuth application][] was created for a user or organization account. |
+| `oauth_application.destroy` | 已从用户或组织帐户中删除 [OAuth 应用程序][]。                                             |
+{%- ifversion fpt or ghec %}
+| `oauth_application.generate_client_secret`   | An [OAuth application][]'s secret key was generated. | `oauth_application.remove_client_secret`     | An [OAuth application][]'s secret key was deleted.
+{%- endif %}
+| `oauth_application.reset_secret`      | An [OAuth application][]'s secret key was reset.
+{%- ifversion fpt or ghec %}
+| `oauth_application.revoke_all_tokens` | All user tokens for an [OAuth application][] were requested to be revoked.
+{%- endif %}
+| `oauth_application.revoke_tokens`     | Token(s) for an [OAuth application][] were revoked. | `oauth_application.transfer`          | An [OAuth application][] was transferred from one user or organization account to another.
+{%- ifversion ghes or ghae %}
+| `oauth_application.unsuspend`         | An [OAuth application][] was unsuspended for a user or organization account.
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `oauth_authority` 类别操作
+
+| 操作                            | 描述                                                                                                                                                            |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `oauth_authorization.create`  | An authorization for an OAuth application was created. 更多信息请参阅“[授权 OAuth 应用程序](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)”。 |
+| `oauth_authorization.destroy` | An authorization for an OAuth application was deleted. 更多信息请参阅“[授权 OAuth 应用程序](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)”。 |
+| `oauth_authorization.update`  | An authorization for an OAuth application was updated. 更多信息请参阅“[授权 OAuth 应用程序](/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps)”。 |
+{%- endif %}
+
+### `org` 类操作
+
+| 操作                                                                                                                                                                                                                                                                                        | 描述                                                                        |
+| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- |
+| `org.accept_business_invitation`                                                                                                                                                                                                                                                          | An invitation sent to an organization to join an enterprise was accepted. |
+| {% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %} |                                                                           |
+| `org.add_billing_manager`                                                                                                                                                                                                                                                                 | A billing manager was added to an organization.                           |
+| {% ifversion fpt or ghec %}For more information, see "[Adding a billing manager to your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)."{% endif %}                                                  |                                                                           |
+| `org.add_member`                                                                                                                                                                                                                                                                          | A user joined an organization.                                            |
+{%- ifversion ghes > 3.0 or ghae or ghec %}
+| `org.advanced_security_disabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for new repositories in an organization. | `org.advanced_security_disabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was disabled for all repositories in an organization. | `org.advanced_security_enabled_for_new_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for new repositories in an organization. | `org.advanced_security_enabled_on_all_repos` | {% data variables.product.prodname_GH_advanced_security %} was enabled for all repositories in an organization. | `org.advanced_security_policy_selected_member_disabled` | An enterprise owner prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_selected_member_enabled` | An enterprise owner allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for repositories owned by the organization. {% data reusables.advanced-security.more-information-about-enforcement-policy %} | `org.advanced_security_policy_update` | An organization owner updated polices for {% data variables.product.prodname_GH_advanced_security %} in an enterprise. {% data reusables.advanced-security.more-information-about-enforcement-policy %}
+{%- endif %}
+| `org.async_delete` | A user initiated a background job to delete an organization.
+{%- ifversion ghec %}
+| `org.audit_log_export` | An organization owner created an export of the organization audit log. 如果导出包含查询，则日志将列出所使用的查询以及与该查询匹配的审核日志条目数量。 For more information, see "[Exporting audit log activity for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise)."
+{%- endif %}
+| `org.block_user` | An organization owner blocked a user from accessing the organization's repositories. |{% ifversion fpt or ghec %}For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)."{% endif %}| | `org.cancel_business_invitation` | An invitation for an organization to join an enterprise was revoked. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.cancel_invitation` | An invitation sent to a user to join an organization was revoked. | `org.clear_actions_settings` |  An organization owner cleared {% data variables.product.prodname_actions %} policy settings for an organization. For more information, see "[Managing GitHub Actions permissions for your organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#managing-github-actions-permissions-for-your-organization)." | `org.clear_default_repository_permission` | An organization owner cleared the base repository permission policy setting for an organization. For more information, see "[Setting base permissions](/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization#setting-base-permissions)." | `org.clear_member_team_creation_permission` | An organization owner cleared the new teams creation setting for an organization. 更多信息请参阅“[设置组织中的团队创建权限](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)”。 | `org.clear_reader_discussion_creation_permission` | An organization owner cleared the new discussion creation setting for an organization. |{% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}| | `org.clear_members_can_create_repos`                 | An organization owner cleared a restriction on repository creation in an organization. 更多信息请参阅“[限制在组织中创建仓库](/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization)”。 | `org.clear_members_can_invite_outside_collaborators` | An organization owner cleared the outside collaborators invitation policy for an organization. 更多信息请参阅“[设置添加外部协作者的权限](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)”。. | `org.clear_new_repository_default_branch_setting`    | An organization owner cleared the default branch name for new repositories setting for an organization. For more information, see "[Setting the default branch name](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization#setting-the-default-branch-name)."
+{%- ifversion fpt or ghec %}
+| `org.codespaces_trusted_repo_access_granted`         | {% data variables.product.prodname_codespaces %} was granted trusted repository access to all other repositories in an organization. 更多信息请参阅“[管理组织的代码空间的存储库访问](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)”。 | `org.codespaces_trusted_repo_access_revoked`         | {% data variables.product.prodname_codespaces %} trusted repository access to all other repositories in an organization was revoked. 更多信息请参阅“[管理组织的代码空间的存储库访问](/codespaces/managing-codespaces-for-your-organization/managing-repository-access-for-your-organizations-codespaces)”。
+{%- endif %}
+| `org.config.disable_collaborators_only` | The interaction limit for collaborators only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_contributors_only` | The interaction limit for prior contributors only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was disabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_collaborators_only` | The interaction limit for collaborators only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_contributors_only` | The interaction limit for prior contributors only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.config.enable_sockpuppet_disallowed` | The interaction limit for existing users only for an organization was enabled. |{% ifversion fpt or ghec %}For more information, see "[Limiting interactions in your organization](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization#limiting-interactions-in-your-organization)."{% endif %}| | `org.confirm_business_invitation` | An invitation for an organization to join an enterprise was confirmed. |{% ifversion ghec %}For more information, see "[Inviting an organization to join your enterprise account](/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise#inviting-an-organization-to-join-your-enterprise-account)."{% endif %}| | `org.create` | An organization was created. 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
+{%- ifversion fpt or ghec or ghes %}
+| `org.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for an organization. 更多信息请参阅“[为组织创建加密密码](/actions/reference/encrypted-secrets#creating-encrypted-secrets-for-an-organization)”。
+{%- endif %}
+| `org.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for an organization. | `org.delete`       | An organization was deleted by a user-initiated background job. | `org.disable_member_team_creation_permission` | An organization owner limited team creation to owners. 更多信息请参阅“[设置组织中的团队创建权限](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)”。 | `org.disable_reader_discussion_creation_permission` | An organization owner limited discussion creation to users with at least triage permission in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}
+{%- ifversion fpt or ghec %}
+| `org.disable_oauth_app_restrictions` | Third-party application access restrictions for an organization were disabled. For more information, see "[Disabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization)."
+{%- endif %}
+{%- ifversion ghec %}
+| `org.disable_saml` | An organization owner disabled SAML single sign-on for an organization.
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.disable_two_factor_requirement` | An organization owner disabled a two-factor authentication requirement for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.
+{%- endif %}
+| `org.display_commenter_full_name_disabled` | An organization owner disabled the display of a commenter's full name in an organization. Members cannot see a comment author's full name. | `org.display_commenter_full_name_enabled` | An organization owner enabled the display of a commenter's full name in an organization. Members can see a comment author's full name. | `org.enable_member_team_creation_permission` | An organization owner allowed members to create teams. 更多信息请参阅“[设置组织中的团队创建权限](/organizations/managing-organization-settings/setting-team-creation-permissions-in-your-organization)”。 | `org.enable_reader_discussion_creation_permission` | An organization owner allowed users with read access to create discussions in an organization. {% ifversion fpt or ghec %}For more information, see "[Allowing or disallowing users with read access to create discussions](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."{% endif %}
+{%- ifversion fpt or ghec %}
+| `org.enable_oauth_app_restrictions` | Third-party application access restrictions for an organization were enabled. For more information, see "[Enabling OAuth App access restrictions for your organization](/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization)."
+{%- endif %}
+{%- ifversion ghec %}
+| `org.enable_saml` | An organization owner [enabled SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization) for an organization.
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.enable_two_factor_requirement` | An organization owner requires two-factor authentication for all members{% ifversion fpt or ghec %}, billing managers,{% endif %} and outside collaborators in an organization.
+{%- endif %}
+| `org.integration_manager_added` | An organization owner granted a member access to manage all GitHub Apps owned by an organization. | `org.integration_manager_removed` | An organization owner removed access to manage all GitHub Apps owned by an organization from an organization member. | `org.invite_member` | A new user was invited to join an organization. |{% ifversion fpt or ghec %}For more information, see "[Inviting users to join your organization](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)."{% endif %}| | `org.invite_to_business` | An organization was invited to join an enterprise. | `org.members_can_update_protected_branches.clear` | An organization owner unset a policy for whether members of an organization can update protected branches on repositories in an organization. Organization administrators can choose whether to allow updating protected branches settings. | `org.members_can_update_protected_branches.disable` | The ability for enterprise members to update protected branches was disabled. Only enterprise owners can update protected branches. | `org.members_can_update_protected_branches.enable` |  The ability for enterprise members to update protected branches was enabled. Members of an organization can update protected branches.
+{%- ifversion fpt or ghec %}
+| `org.oauth_app_access_approved` | An owner [granted organization access to an {% data variables.product.prodname_oauth_app %}](/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization). | `org.oauth_app_access_denied` | An owner [disabled a previously approved {% data variables.product.prodname_oauth_app %}'s access](/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization) to an organization. | `org.oauth_app_access_requested` | An organization member requested that an owner grant an {% data variables.product.prodname_oauth_app %} access to an organization.
+{%- endif %}
+| `org.recreate` | An organization was restored. | `org.register_self_hosted_runner` | A new self-hosted runner was registered. 更多信息请参阅“[将自托管运行器添加到组织](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-organization)”。 | `org.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was removed. | `org.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was removed from an organization. | `org.remove_billing_manager` | An owner removed a billing manager from an organization. |{% ifversion fpt or ghec %}For more information, see "[Removing a billing manager from your organization](/organizations/managing-peoples-access-to-your-organization-with-roles/removing-a-billing-manager-from-your-organization)"{% endif %}{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and a billing manager didn't use 2FA or disabled 2FA.{% endif %}| | `org.remove_member` | An [owner removed a member from an organization](/organizations/managing-membership-in-your-organization/removing-a-member-from-your-organization){% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an organization member doesn't use 2FA or disabled 2FA{% endif %}. Also an [organization member removed themselves](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization) from an organization. | `org.remove_outside_collaborator` | An owner removed an outside collaborator from an organization{% ifversion not ghae %} or when [two-factor authentication was required in an organization](/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization) and an outside collaborator didn't use 2FA or disabled 2FA{% endif %}. | `org.remove_self_hosted_runner` | A self-hosted runner was removed. 更多信息请参阅“[从组织移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-an-organization)”。 | `org.rename` | An organization was renamed. | `org.restore_member` | An organization member was restored. For more information, see "[Reinstating a former member of your organization](/organizations/managing-membership-in-your-organization/reinstating-a-former-member-of-your-organization)."
+{%- ifversion ghec %}
+| `org.revoke_external_identity` | An organization owner revoked a member's linked identity. 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。 | `org.revoke_sso_session` | An organization owner revoked a member's SAML session. 更多信息请参阅“[查看和管理成员对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization#viewing-and-revoking-a-linked-identity)”。
+{%- endif %}
+| `org.runner_group_created` | A self-hosted runner group was created. 更多信息请参阅“[为组织创建自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#creating-a-self-hosted-runner-group-for-an-organization)”。 | `org.runner_group_removed` | A self-hosted runner group was removed. 更多信息请参阅“[移除自托管运行器组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#removing-a-self-hosted-runner-group)”。
+{%- ifversion fpt or ghec %}
+| `org.runner_group_renamed` | A self-hosted runner group was renamed. 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。
+{%- endif %}
+| `org.runner_group_updated` | The configuration of a self-hosted runner group was changed. 更多信息请参阅“[更改自托管运行器组的访问策略](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#changing-the-access-policy-of-a-self-hosted-runner-group)”。 | `org.runner_group_runner_removed` |  The REST API was used to remove a self-hosted runner from a group. 更多信息请参阅“[为组织从组中删除自托管运行器](/rest/reference/actions#remove-a-self-hosted-runner-from-a-group-for-an-organization)”。 | `org.runner_group_runners_added` | A self-hosted runner was added to a group. 更多信息请参阅“[将自托管运行器移动到组](/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups#moving-a-self-hosted-runner-to-a-group)”。 | `org.runner_group_runners_updated`|  A runner group's list of members was updated. 更多信息请参阅“[为组织设置组中的自托管运行器](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)”。
+{%- ifversion fpt or ghec %}
+| `org.runner_group_visiblity_updated` | The visibility of a self-hosted runner group was updated via the REST API. For more information, see "[Update a self-hosted runner group for an organization](/rest/reference/actions#update-a-self-hosted-runner-group-for-an-organization)."
+{%- endif %}
+{%- if secret-scanning-audit-log-custom-patterns %}
+| `org.secret_scanning_push_protection_disable` | An organization owner or administrator disabled push protection for secret scanning. 更多信息请参阅“[使用机密扫描保护推送](/enterprise-cloud@latest/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。 | `org.secret_scanning_push_protection_enable` | An organization owner or administrator enabled push protection for secret scanning.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| `org.self_hosted_runner_online` | The runner application was started. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。 | `org.self_hosted_runner_offline` | The runner application was stopped. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。
+{%- endif %}
+{%- ifversion fpt or ghec or ghes %}
+| `org.self_hosted_runner_updated` | The runner application was updated. 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `org.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for an organization. For more information, see "[Requiring approval for workflows from public forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#requiring-approval-for-workflows-from-public-forks)."
+{%- endif %}
+| `org.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in an organization was changed. For more information, see "[Configuring the retention period for {% data variables.product.prodname_actions %} artifacts and logs in your organization](/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization)."
+{%- ifversion fpt or ghec or ghes %}
+| `org.set_fork_pr_workflows_policy` | The policy for workflows on private repository forks was changed. For more information, see "[Enabling workflows for private repository forks](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#enabling-workflows-for-private-repository-forks)."
+{%- endif %}
+{%- ifversion ghes %}
+| `org.sso_response` | A SAML single sign-on response was generated when a member attempted to authenticate with an organization.
+{%- endif %}
+{%- ifversion not ghae %}
+| `org.transform`    | A user account was converted into an organization. For more information, see "[Converting a user into an organization](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)."
+{%- endif %}
+| `org.unblock_user` | An organization owner unblocked a user from an organization. {% ifversion fpt or ghec %}For more information, see "[Unblocking a user from your organization](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)."{% endif %}
+{%- ifversion fpt or ghec or ghes %}
+| `org.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated.
+{%- endif %}
+| `org.update_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was updated for an organization. | `org.update_default_repository_permission` | An organization owner changed the default repository permission level for organization members. | `org.update_member` | An organization owner changed a person's role from owner to member or member to owner. | `org.update_member_repository_creation_permission` | An organization owner changed the create repository permission for organization members. | `org.update_member_repository_invitation_permission` | An organization owner changed the policy setting for organization members inviting outside collaborators to repositories. 更多信息请参阅“[设置添加外部协作者的权限](/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators)”。. | `org.update_new_repository_default_branch_setting` | An organization owner changed the name of the default branch for new repositories in the organization. 更多信息请参阅“[管理组织中仓库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”。
+{%- ifversion ghec or ghae %}
+| `org.update_saml_provider_settings` | An organization's SAML provider settings were updated. | `org.update_terms_of_service` | An organization changed between the Standard Terms of Service and the Corporate Terms of Service. {% ifversion ghec %}For more information, see "[Upgrading to the Corporate Terms of Service](/organizations/managing-organization-settings/upgrading-to-the-corporate-terms-of-service)."{% endif %}
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+### `org_credential_authorization` 类操作
+
+| 操作                                                                                                                                                                     | 描述                                                                                                                                                                                                                                                                                                  |
+| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org_credential_authorization.deauthorized`                                                                                                                            | A member deauthorized credentials for use with SAML single sign-on.                                                                                                                                                                                                                                 |
+| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} |                                                                                                                                                                                                                                                                                                     |
+| `org_credential_authorization.grant`                                                                                                                                   | A member authorized credentials for use with SAML single sign-on.                                                                                                                                                                                                                                   |
+| {% ifversion ghec or ghae %}For more information, see "[Authenticating with SAML single sign-on](/authentication/authenticating-with-saml-single-sign-on)."{% endif %} |                                                                                                                                                                                                                                                                                                     |
+| `org_credential_authorization.revoke`                                                                                                                                  | An owner revoked authorized credentials. {% ifversion ghec %}For more information, see "[Viewing and managing your active SAML sessions](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)."{% endif %}
+{%- endif %}
+
+{%- if secret-scanning-audit-log-custom-patterns %}
+### `org_secret_scanning_custom_pattern` 类操作
+
+| 操作                                          | 描述                                                                                                                                                                                                                        |
+| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `org_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in an organization. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-organization)”。 |
+| `org_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in an organization. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)”。                      |
+| `org_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in an organization. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)”。              |
+{%- endif %}
+
+### `organization_default_label` category actions
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                             |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `organization_default_label.create`  | A default label for repositories in an organization was created. For more information, see "[Creating a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#creating-a-default-label)." |
+| `organization_default_label.update`  | A default label for repositories in an organization was edited. For more information, see "[Editing a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#editing-a-default-label)."    |
+| `organization_default_label.destroy` | A default label for repositories in an organization was deleted. For more information, see "[Deleting a default label](/organizations/managing-organization-settings/managing-default-labels-for-repositories-in-your-organization#deleting-a-default-label)." |
+
+{%- ifversion fpt or ghec or ghes > 3.1 %}
+### `organization_domain` category actions
+
+| 操作                            | 描述                                                                                                                                                                                                                                                                           |
+| ----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `organization_domain.approve` | An enterprise domain was approved for an organization. For more information, see "[Approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#approving-a-domain-for-your-organization)." |
+| `organization_domain.create`  | An enterprise domain was added to an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)."     |
+| `organization_domain.destroy` | An enterprise domain was removed from an organization. For more information, see "[Removing an approved or verified domain](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#removing-an-approved-or-verified-domain)."   |
+| `organization_domain.verify`  | An enterprise domain was verified for an organization. For more information, see "[Verifying a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization#verifying-a-domain-for-your-organization)." |
+
+### `organization_projects_change` category actions
+
+| 操作                                     | 描述                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| -------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `organization_projects_change.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for organization-wide project boards in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)." |
+| `organization_projects_change.disable` | Organization projects were disabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)."                                                                                |
+| `organization_projects_change.enable`  | Organization projects were enabled for all organizations in an enterprise. For more information, see "[Enforcing a policy for organization-wide project boards](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise#enforcing-a-policy-for-organization-wide-project-boards)."                                                                                 |
+{%- endif %}
+
+{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
+### `packages` 类操作
+
+| 操作                                   | 描述                                                                                                                                                                                                                                |
+| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `packages.insecure_hash`             | Maven published an insecure hash for a specific package version.                                                                                                                                                                  |
+| `packages.package_deleted`           | A package was deleted from an organization.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_published`         | A package was published or republished to an organization.                                                                                                                                                                        |
+| `packages.package_restored`          | An entire package was restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_version_deleted`   | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.package_version_published` | A specific package version was published or republished to a package.                                                                                                                                                             |
+| `packages.package_version_restored`  | A specific package version was deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `packages.part_upload`               | A specific package version was partially uploaded to an organization.                                                                                                                                                             |
+| `packages.upstream_package_fetched`  | A specific package version was fetched from the npm upstream proxy.                                                                                                                                                               |
+| `packages.version_download`          | A specific package version was downloaded.                                                                                                                                                                                        |
+| `packages.version_upload`            | A specific package version was uploaded.                                                                                                                                                                                          |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `pages_protected_domain` category actions
+
+| 操作                              | 描述                                                                                                                                                                                                                                                                                          |
+| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pages_protected_domain.create` | A {% data variables.product.prodname_pages %} verified domain was created for an organization or enterprise. 更多信息请参阅“[验证 {% data variables.product.prodname_pages %} 的自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)”。  |
+| `pages_protected_domain.delete` | A {% data variables.product.prodname_pages %} verified domain was deleted from an organization or enterprise. 更多信息请参阅“[验证 {% data variables.product.prodname_pages %} 的自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)”。 |
+| `pages_protected_domain.verify` | A {% data variables.product.prodname_pages %} domain was verified for an organization or enterprise. 更多信息请参阅“[验证 {% data variables.product.prodname_pages %} 的自定义域](/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages)”。          |
+
+### `payment_method` 类操作
+
+| 操作                      | 描述                                                                           |
+| ----------------------- | ---------------------------------------------------------------------------- |
+| `payment_method.create` | A new payment method was added, such as a new credit card or PayPal account. |
+| `payment_method.remove` | A payment method was removed.                                                |
+| `payment_method.update` | An existing payment method was updated.                                      |
+
+### `prebuild_configuration` category actions
+
+| 操作                                     | 描述                                                                                                                                                                                                                     |
+| -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `prebuild_configuration.create`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was created. 更多信息请参阅“[关于代码空间预构建](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)”。                      |
+| `prebuild_configuration.destroy`       | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was deleted. 更多信息请参阅“[关于代码空间预构建](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)”。                      |
+| `prebuild_configuration.run_triggered` | A user initiated a run of a {% data variables.product.prodname_codespaces %} prebuild configuration for a repository branch. 更多信息请参阅“[关于代码空间预构建](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)”。 |
+| `prebuild_configuration.update`        | A {% data variables.product.prodname_codespaces %} prebuild configuration for a repository was edited. 更多信息请参阅“[关于代码空间预构建](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds)”。                       |
+{%- endif %}
+
+{%- ifversion ghes %}
+### `pre_receive_environment` category actions
+
+| 操作                                 | 描述                                                                                                                                                                                                                     |
+| ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pre_receive_environment.create`   | A pre-receive hook environment was created. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."    |
+| `pre_receive_environment.destroy`  | A pre-receive hook environment was deleted. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."    |
+| `pre_receive_environment.download` | A pre-receive hook environment was downloaded. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)." |
+| `pre_receive_environment.update`   | A pre-receive hook environment was updated. For more information, see "[Creating a pre-receive hook environment](/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment)."    |
+
+### `pre_receive_hook` category actions
+
+| 操作                               | 描述                                                                                                                                                                                                                                                                                                                                                                                       |
+| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pre_receive_hook.create`        | A pre-receive hook was created. For more information, see "[Creating pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#creating-pre-receive-hooks)."                                                                                                                                       |
+| `pre_receive_hook.destroy`       | A pre-receive hook was deleted. For more information, see "[Deleting pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#deleting-pre-receive-hooks)."                                                                                                                                       |
+| `pre_receive_hook.enforcement`   | A pre-receive hook enforcement setting allowing repository and organization administrators to override the hook configuration was enabled or disabled. For more information, see "[Managing pre-receive hooks on the GitHub Enterprise Server appliance](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance)." |
+| `pre_receive_hook.rejected_push` | A pre-receive hook rejected a push.                                                                                                                                                                                                                                                                                                                                                      |
+| `pre_receive_hook.update`        | A pre-receive hook was created. For more information, see "[Editing pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks/managing-pre-receive-hooks-on-the-github-enterprise-server-appliance#editing-pre-receive-hooks)."                                                                                                                                         |
+| `pre_receive_hook.warned_push`   | A pre-receive hook warned about a push.                                                                                                                                                                                                                                                                                                                                                  |
+{%- endif %}
+
+### `private_repository_forking` category actions
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `private_repository_forking.clear`   | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} cleared the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."                                                                     |
+| `private_repository_forking.disable` | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} disabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are never allowed  to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)." |
+| `private_repository_forking.enable`  | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} enabled the policy setting for allowing forks of private and internal repositories, for a repository, organization or enterprise. Private and internal repositories are always allowed to be forked. For more information, see "[Managing the forking policy for your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-forking-policy-for-your-repository), "[Managing the forking policy for your organization](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization) and for enterprises "[Enforcing a policy for forking private or internal repositories](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-forking-private-or-internal-repositories)."  |
+
+{%- ifversion fpt or ghec %}
+### `profile_picture` 类操作
+
+| 操作                       | 描述                             |
+| ------------------------ | ------------------------------ |
+| `profile_picture.update` | A profile picture was updated. |
+{%- endif %}
+
+### `project` 类操作
+
+| 操作                               | 描述                                                                                                                                                                                                                                                                                                                                                                      |
+| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `project.access`                 | A project board visibility was changed. For more information, see "[Changing project board visibility](/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility)."                                                                                                                                                    |
+| `project.close`                  | A project board was closed. For more information, see "[Closing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/closing-a-project-board)."                                                                                                                                                                                    |
+| `project.create`                 | A project board was created. For more information, see "[Creating a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board)."                                                                                                                                                                                 |
+| `project.delete`                 | A project board was deleted. For more information, see "[Deleting a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/deleting-a-project-board)."                                                                                                                                                                                 |
+| `project.link`                   | A repository was linked to a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)."                                                                                                                                    |
+| `project.open`                   | A project board was reopened. For more information, see "[Reopening a closed project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/reopening-a-closed-project-board)."                                                                                                                                                                |
+| `project.rename`                 | A project board was renamed. For more information, see "[Editing a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/editing-a-project-board)."                                                                                                                                                                                   |
+| `project.unlink`                 | A repository was unlinked from a project board. For more information, see "[Linking a repository to a project board](/issues/organizing-your-work-with-project-boards/managing-project-boards/linking-a-repository-to-a-project-board)."                                                                                                                                |
+| `project.update_org_permission`  | The project's base-level permission for all organization members was changed or removed. For more information, see "[Managing access to a project board for organization members](/organizations/managing-access-to-your-organizations-project-boards/managing-access-to-a-project-board-for-organization-members)."                                                    |
+| `project.update_team_permission` | A team's project board permission level was changed or when a team was added or removed from a project board. For more information, see "[Managing team access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board)."                                           |
+| `project.update_user_permission` | An organization member or outside collaborator was added to or removed from a project board or had their permission level changed. For more information, see "[Managing an individual’s access to an organization project board](/organizations/managing-access-to-your-organizations-project-boards/managing-an-individuals-access-to-an-organization-project-board)." |
+
+{%- ifversion fpt or ghec %}
+### `project_field` category actions
+
+| 操作                     | 描述                                                                                                                                                                                |
+| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `project_field.create` | A field was created in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." |
+| `project_field.delete` | A field was deleted in a project board. For more information, see "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project#adding-fields)." |
+
+### `project_view` category actions
+
+| 操作                    | 描述                                                                                                                                                                                                                 |
+| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `project_view.create` | A view was created in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#creating-a-project-view)." |
+| `project_view.delete` | A view was deleted in a project board. For more information, see "[Customizing your project (beta) views](/issues/trying-out-the-new-projects-experience/customizing-your-project-views#deleting-a-saved-view)."   |
+{%- endif %}
+
+### `protected_branch` 类操作
+
+| 操作                                       | 描述                                                                     |
+| ---------------------------------------- | ---------------------------------------------------------------------- |
+| `protected_branch.create`                | Branch protection was enabled on a branch.                             |
+| `protected_branch.destroy`               | Branch protection was disabled on a branch.                            |
+| `protected_branch.dismiss_stale_reviews` | Enforcement of dismissing stale pull requests was updated on a branch. |
+{%- ifversion ghes %}
+| `protected_branch.dismissal_restricted_users_teams` | Enforcement of restricting users and/or teams who can dismiss reviews was updated on a branch.
+{%- endif %}
+| `protected_branch.policy_override` | A branch protection requirement was overridden by a repository administrator. | `protected_branch.rejected_ref_update` | A branch update attempt was rejected. | `protected_branch.required_status_override` | The required status checks branch protection requirement was overridden by a repository administrator. | `protected_branch.review_policy_and_required_status_override` | The required reviews and required status checks branch protection requirements were overridden by a repository administrator. | `protected_branch.review_policy_override` | The required reviews branch protection requirement was overridden by a repository administrator. | `protected_branch.update_admin_enforced` | Branch protection was enforced for repository administrators.
+{%- ifversion ghes %}
+| `protected_branch.update_allow_deletions_enforcement_level` | Enforcement of allowing users with push access to delete matching branches was updated on a branch. | `protected_branch.update_allow_force_pushes_enforcement_level` | Enforcement of allowing force pushes for all users with push access was updated on a branch. | `protected_branch.update_linear_history_requirement_enforcement_level` | Enforcement of requiring linear commit history was updated on a branch.
+{%- endif %}
+| `protected_branch.update_pull_request_reviews_enforcement_level` | Enforcement of required pull request reviews was updated on a branch. 可以是 `0`（已停用）、`1`（非管理员）`2`（所有人）之一。 | `protected_branch.update_require_code_owner_review` | Enforcement of required code owner review was updated on a branch. | `protected_branch.update_required_approving_review_count` | Enforcement of the required number of approvals before merging was updated on a branch. | `protected_branch.update_required_status_checks_enforcement_level` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_signature_requirement_enforcement_level` | Enforcement of required commit signing was updated on a branch. | `protected_branch.update_strict_required_status_checks_policy` | Enforcement of required status checks was updated on a branch. | `protected_branch.update_name` | A branch name pattern was updated for a branch.
+
+### `public_key` 类操作
+
+| 操作                                  | 描述                                                                                               |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------ |
+| `public_key.create`                 | An SSH key was [added][add key] to a user account or a [deploy key][] was added to a repository. |
+| `public_key.delete`                 | An SSH key was removed from a user account or a [deploy key][] was removed from a repository.    |
+| `public_key.update`                 | A user account's SSH key or a repository's [deploy key][] was updated.                           |
+| `public_key.unverification_failure` | A user account's SSH key or a repository's [deploy key][] was unable to be unverified.           |
+| `public_key.unverify`               | A user account's SSH key or a repository's [deploy key][] was unverified.                        |
+| `public_key.verification_failure`   | A user account's SSH key or a repository's [deploy key][] was unable to be verified.             |
+| `public_key.verify`                 | A user account's SSH key or a repository's [deploy key][] was verified.                          |
+
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### `pull_request` 类操作
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                                                             |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pull_request.close`                 | A pull request was closed without being merged. For more information, see "[Closing a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)."                                                                        |
+| `pull_request.converted_to_draft`    | A pull request was converted to a draft. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)."             |
+| `pull_request.create`                | A pull request was created. For more information, see "[Creating a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)."                                                                                  |
+| `pull_request.create_review_request` | A review was requested on a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."                                                                             |
+| `pull_request.in_progress`           | A pull request was marked as in progress.                                                                                                                                                                                                                                                      |
+| `pull_request.indirect_merge`        | A pull request was considered merged because the pull request's commits were merged into the target branch.                                                                                                                                                                                    |
+| `pull_request.merge`                 | A pull request was merged. 更多信息请参阅“[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)”。                                                                                                                                |
+| `pull_request.ready_for_review`      | A pull request was marked as ready for review. For more information, see "[Changing the stage of a pull request](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)." |
+| `pull_request.remove_review_request` | A review request was removed from a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."                                                                     |
+| `pull_request.reopen`                | A pull request was reopened after previously being closed.                                                                                                                                                                                                                                     |
+| `pull_request_review.delete`         | A review on a pull request was deleted.                                                                                                                                                                                                                                                        |
+| `pull_request_review.dismiss`        | A review on a pull request was dismissed. 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。                                                                                                            |
+| `pull_request_review.submit`         | A review was submitted for a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)."                                                                            |
+
+### `pull_request_review` 类操作
+
+| 操作                            | 描述                                                                                                                                                                                                                                                      |
+| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pull_request_review.delete`  | A review on a pull request was deleted.                                                                                                                                                                                                                 |
+| `pull_request_review.dismiss` | A review on a pull request was dismissed. 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。                                                                     |
+| `pull_request_review.submit`  | A review on a pull request was submitted. For more information, see "[Submitting your review](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request#submitting-your-review)." |
+
+### `pull_request_review_comment` 类操作
+
+| 操作                                   | 描述                                                                                                                                                                                                                     |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `pull_request_review_comment.create` | A review comment was added to a pull request. For more information, see "[About pull request reviews](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)." |
+| `pull_request_review_comment.delete` | A review comment on a pull request was deleted.                                                                                                                                                                        |
+| `pull_request_review_comment.update` | A review comment on a pull request was changed.                                                                                                                                                                        |
+{%- endif %}
+
+### `repo` 类操作
+
+| 操作                                                       | 描述                                                                                                                                                                                                                     |
+| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repo.access`                                            | 仓库的可见性已更改为私有{%- ifversion ghes %}、公共{% endif %} 或内部。                                                                                                                                                                   |
+| `repo.actions_enabled`                                   | {% data variables.product.prodname_actions %} was enabled for a repository.                                                                                                                                            |
+| `repo.add_member`                                        | 已向仓库添加协作者。                                                                                                                                                                                                             |
+| `repo.add_topic`                                         | A topic was added to a repository.                                                                                                                                                                                     |
+| `repo.advanced_security_disabled`                        | {% data variables.product.prodname_GH_advanced_security %} was disabled for a repository.                                                                                                                            |
+| `repo.advanced_security_enabled`                         | {% data variables.product.prodname_GH_advanced_security %} was enabled for a repository.                                                                                                                             |
+| `repo.advanced_security_policy_selected_member_disabled` | A repository administrator prevented {% data variables.product.prodname_GH_advanced_security %} features from being enabled for a repository.                                                                        |
+| `repo.advanced_security_policy_selected_member_enabled`  | A repository administrator allowed {% data variables.product.prodname_GH_advanced_security %} features to be enabled for a repository.                                                                               |
+| `repo.archived`                                          | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。                                                               |
+| `repo.code_scanning_analysis_deleted`                    | Code scanning analysis for a repository was deleted. For more information, see "[Delete a code scanning analysis from a repository](/rest/reference/code-scanning#delete-a-code-scanning-analysis-from-a-repository)." |
+| `repo.change_merge_setting`                              | Pull request merge options were changed for a repository.                                                                                                                                                              |
+| `repo.clear_actions_settings`                            | A repository administrator cleared {% data variables.product.prodname_actions %} policy settings for a repository.                                                                                                     |
+| `repo.config`                                            | A repository administrator blocked force pushes. 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。                                      |
+{%- ifversion fpt or ghec %}
+| `repo.config.disable_collaborators_only` | The interaction limit for collaborators only was disabled. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 | `repo.config.disable_contributors_only` | The interaction limit for prior contributors only was disabled in a repository. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 | `repo.config.disable_sockpuppet_disallowed` | The interaction limit for existing users only was disabled in a repository. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 | `repo.config.enable_collaborators_only` | The interaction limit for collaborators only was enabled in a repository. Users that are not collaborators or organization members were unable to interact with a repository for a set duration. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 | `repo.config.enable_contributors_only` | The interaction limit for prior contributors only was enabled in a repository. Users that are not prior contributors, collaborators or organization members were unable to interact with a repository for a set duration. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 | `repo.config.enable_sockpuppet_disallowed` | The interaction limit for existing users was enabled in a repository. New users aren't able to interact with a repository for a set duration. Existing users of the repository, contributors, collaborators or organization members are able to interact with a repository. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。
+{%- endif %}
+{%- ifversion ghes %}
+| `repo.config.disable_anonymous_git_access`| Anonymous Git read access was disabled for a repository. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)。” | `repo.config.enable_anonymous_git_access` | Anonymous Git read access was enabled for a repository. 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/enabling-anonymous-git-read-access-for-a-repository)。” | `repo.config.lock_anonymous_git_access` | A repository's anonymous Git read access setting was locked, preventing repository administrators from changing (enabling or disabling) this setting. 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。 | `repo.config.unlock_anonymous_git_access` | A repository's anonymous Git read access setting was unlocked, allowing repository administrators to change (enable or disable) this setting. 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。
+{%- endif %}
+| `repo.create` | A repository was created. | `repo.create_actions_secret` | A {% data variables.product.prodname_actions %} secret was created for a repository. 更多信息请参阅“[为仓库创建加密密码](/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository)”。 | `repo.create_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was created for a repository. | `repo.destroy` | A repository was deleted.
+{%- ifversion ghes %}
+| `repo.disk_archive`  | A repository was archived on disk. 更多信息请参阅“[存档仓库](/repositories/archiving-a-github-repository/archiving-repositories)”。
+{%- endif %}
+| `repo.download_zip` | A source code archive of a repository was downloaded as a ZIP file. | `repo.pages_cname` | A {% data variables.product.prodname_pages %} custom domain was modified in a repository. | `repo.pages_create` | A {% data variables.product.prodname_pages %} site was created. | `repo.pages_destroy` | A {% data variables.product.prodname_pages %} site was deleted. | `repo.pages_https_redirect_disabled` | HTTPS redirects were disabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_https_redirect_enabled` | HTTPS redirects were enabled for a {% data variables.product.prodname_pages %} site. | `repo.pages_source` | A {% data variables.product.prodname_pages %} source was modified. | `repo.pages_private` | A {% data variables.product.prodname_pages %} site visibility was changed to private. | `repo.pages_public` | A {% data variables.product.prodname_pages %} site visibility was changed to public. | `repo.register_self_hosted_runner` | A new self-hosted runner was registered. 更多信息请参阅“[将自托管运行器添加到仓库](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository)”。 | `repo.remove_self_hosted_runner` | A self-hosted runner was removed. 更多信息请参阅“[从仓库移除运行器](/actions/hosting-your-own-runners/removing-self-hosted-runners#removing-a-runner-from-a-repository)”。 | `repo.remove_actions_secret` | A {% data variables.product.prodname_actions %} secret was deleted for a repository. | `repo.remove_integration_secret` | A {% data variables.product.prodname_dependabot %}{% ifversion fpt or ghec %} or {% data variables.product.prodname_codespaces %}{% endif %} integration secret was deleted for a repository. | `repo.remove_member` | A collaborator was removed from a repository. | `repo.remove_topic` | A topic was removed from a repository. | `repo.rename` | A repository was renamed.
+{%- ifversion fpt or ghec %}
+| `repo.set_actions_fork_pr_approvals_policy` | The setting for requiring approvals for workflows from public forks was changed for a repository. For more information, see "[Configuring required approval for workflows from public forks](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)."
+{%- endif %}
+| `repo.set_actions_retention_limit` | The retention period for {% data variables.product.prodname_actions %} artifacts and logs in a repository was changed. 更多信息请参阅“[配置 {% 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-the-retention-period-for-github-actions-artifacts-and-logs-in-your-repository)”。
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| `repo.self_hosted_runner_online` | The runner application was started. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。 | `repo.self_hosted_runner_offline` | The runner application was stopped. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[检查自托管运行器的状态](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)”。 | `repo.self_hosted_runner_updated` | The runner application was updated. 可以使用 REST API 和 UI 查看；在 JSON /CSV 导出中不可见。 更多信息请参阅“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)”。
+{%- endif %}
+| `repo.staff_unlock` | An enterprise administrator or GitHub staff (with permission from a repository administrator) temporarily unlocked the repository. | `repo.transfer` | A user accepted a request to receive a transferred repository. | `repo.transfer_outgoing` | A repository was transferred to another repository network. | `repo.transfer_start` | A user sent a request to transfer a repository to another user or organization. | `repo.unarchived` | A repository was unarchived. 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。 | `repo.update_actions_settings` | A repository administrator changed {% data variables.product.prodname_actions %} policy settings for a repository. | `repo.update_actions_secret` | A {% data variables.product.prodname_actions %} secret was updated. | `repo.update_actions_access_settings` | The setting to control how a repository was used by {% data variables.product.prodname_actions %} workflows in other repositories was changed. | `repo.update_default_branch` | The default branch for a repository was changed. | `repo.update_integration_secret` | A {% data variables.product.prodname_dependabot %} or {% data variables.product.prodname_codespaces %} integration secret was updated for a repository. | `repo.update_member` | A user's permission to a repository was changed.
+
+{%- ifversion fpt or ghec %}
+### `repository_advisory` 类操作
+
+| 操作                                     | 描述                                                                                                                                                                               |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_advisory.close`            | Someone closed a security advisory. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 |
+| `repository_advisory.cve_request`      | Someone requested a CVE (Common Vulnerabilities and Exposures) number from {% data variables.product.prodname_dotcom %} for a draft security advisory.                           |
+| `repository_advisory.github_broadcast` | {% data variables.product.prodname_dotcom %} made a security advisory public in the {% data variables.product.prodname_advisory_database %}.                                   |
+| `repository_advisory.github_withdraw`  | {% data variables.product.prodname_dotcom %} withdrew a security advisory that was published in error.                                                                           |
+| `repository_advisory.open`             | Someone opened a draft security advisory.                                                                                                                                        |
+| `repository_advisory.publish`          | Someone publishes a security advisory.                                                                                                                                           |
+| `repository_advisory.reopen`           | Someone reopened as draft security advisory.                                                                                                                                     |
+| `repository_advisory.update`           | Someone edited a draft or published security advisory.                                                                                                                           |
+
+### `repository_content_analysis` 类操作
+
+| 操作                                    | 描述                                                                                                                                                                                              |
+| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_content_analysis.enable`  | An organization owner or repository administrator [enabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository).  |
+| `repository_content_analysis.disable` | An organization owner or repository administrator [disabled data use settings for a private repository](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository). |
+
+### `repository_dependency_graph` 类操作
+
+| 操作                                    | 描述                                                                                                                                                                                          |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_dependency_graph.disable` | A repository owner or administrator disabled the dependency graph for a private repository. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 |
+| `repository_dependency_graph.enable`  | A repository owner or administrator enabled the dependency graph for a private repository.                                                                                                  |
+{%- endif %}
+
+### `repository_image` category actions
+
+| 操作                         | 描述                                               |
+| -------------------------- | ------------------------------------------------ |
+| `repository_image.create`  | An image to represent a repository was uploaded. |
+| `repository_image.destroy` | An image to represent a repository was deleted.  |
+
+### `repository_invitation` category actions
+
+| 操作                             | 描述                                               |
+| ------------------------------ | ------------------------------------------------ |
+| `repository_invitation.accept` | An invitation to join a repository was accepted. |
+| `repository_invitation.create` | An invitation to join a repository was sent.     |
+| `repository_invitation.reject` | An invitation to join a repository was canceled. |
+
+### `repository_projects_change` category actions
+
+| 操作                                   | 描述                                                                                                                                                                                                                                                                                                                                                                             |
+| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `repository_projects_change.clear`   | The repository projects policy was removed for an organization, or all organizations in the enterprise. Organization admins can now control their repository projects settings. For more information, see "[Enforcing project board policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise)." |
+| `repository_projects_change.disable` | Repository projects were disabled for a repository, all repositories in an organization, or all organizations in an enterprise.                                                                                                                                                                                                                                                |
+| `repository_projects_change.enable`  | Repository projects were enabled for a repository, all repositories in an organization, or all organizations in an enterprise.                                                                                                                                                                                                                                                 |
+
+{%- ifversion ghec or ghes or ghae %}
+### `repository_secret_scanning` 类操作
+
+| 操作                                   | 描述                                                                                                                                                                                                             |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_secret_scanning.disable` | A repository owner or administrator disabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `repository_secret_scanning.enable`  | A repository owner or administrator enabled secret scanning for a {% ifversion ghec %}private or internal {% endif %}repository.                                                                               |
+{%- endif %}
+
+{%- if secret-scanning-audit-log-custom-patterns %}
+
+### `repository_secret_scanning_custom_pattern` 类操作
+
+| 操作                                                 | 描述                                                                                                                                                                                                                  |
+| -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_secret_scanning_custom_pattern.create` | A custom pattern is published for secret scanning in a repository. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-a-repository)”。 |
+| `repository_secret_scanning_custom_pattern.delete` | A custom pattern is removed from secret scanning in a repository. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#removing-a-custom-pattern)”。                   |
+| `repository_secret_scanning_custom_pattern.update` | Changes to a custom pattern are saved for secret scanning in a repository. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#editing-a-custom-pattern)”。           |
+
+### `repository_secret_scanning_push_protection` 类操作
+
+| 操作                                                   | 描述                                                                                                                                                                            |
+| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_secret_scanning_push_protection.disable` | A repository owner or administrator  disabled secret scanning for a repository. 更多信息请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。 |
+| `repository_secret_scanning_push_protection.enable`  | A repository owner or administrator  enabled secret scanning for a repository. 更多信息请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。  |
+{%- endif %}
+### `repository_visibility_change` category actions
+
+| 操作                                     | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_visibility_change.clear`   | The repository visibility change setting was cleared for an organization or enterprise. For more information, see "[Restricting repository visibility changes in your organization](/organizations/managing-organization-settings/restricting-repository-visibility-changes-in-your-organization)" and "[Enforcing a policy for changes to repository visibility](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-changes-to-repository-visibility) for an enterprise." |
+| `repository_visibility_change.disable` | The ability for enterprise members to update a repository's visibility was disabled. Members are unable to change repository visibilities in an organization, or all organizations in an enterprise.                                                                                                                                                                                                                                                                                                                                                              |
+| `repository_visibility_change.enable`  | The ability for enterprise members to update a repository's visibility was enabled. Members are able to change repository visibilities in an organization, or all organizations in an enterprise.                                                                                                                                                                                                                                                                                                                                                                 |
+
+{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
+### `repository_vulnerability_alert` 类操作
+
+| 操作                                       | 描述                                                                                                                                                                                                                                                                             |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `repository_vulnerability_alert.create`  | {% data variables.product.product_name %} created a {% data variables.product.prodname_dependabot %} alert for a repository that uses a vulnerable dependency. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |
+| `repository_vulnerability_alert.dismiss` | An organization owner or repository administrator dismissed a {% data variables.product.prodname_dependabot %} alert about a vulnerable dependency.                                                                                                                            |
+| `repository_vulnerability_alert.resolve` | Someone with write access to a repository pushed changes to update and resolve a vulnerability in a project dependency.                                                                                                                                                        |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `repository_vulnerability_alerts` 类操作
+
+| 操作                                                       | 描述                                                                                                                                                                                                                                                                                                                                                                               |
+| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `repository_vulnerability_alerts.authorized_users_teams` | An organization owner or repository administrator updated the list of people or teams authorized to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in the repository. 更多信息请参阅“[管理仓库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)”。 |
+| `repository_vulnerability_alerts.disable`                | A repository owner or repository administrator disabled {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                               |
+| `repository_vulnerability_alerts.enable`                 | A repository owner or repository administrator enabled {% data variables.product.prodname_dependabot_alerts %}.                                                                                                                                                                                                                                                                |
+{%- endif %}
+
+### `required_status_check` category actions
+
+| 操作                              | 描述                                                                                                                                                                                                                                                                                                                     |
+| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `required_status_check.create`  | A status check was marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)."           |
+| `required_status_check.destroy` | A status check was no longer marked as required for a protected branch. For more information, see "[Require status checks before merging](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)." |
+
+{%- ifversion ghec or ghes > 3.1 %}
+### `restrict_notification_delivery` category actions
+
+| 操作                                       | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ---------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `restrict_notification_delivery.enable`  | Email notification restrictions for an organization or enterprise were enabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."  |
+| `restrict_notification_delivery.disable` | Email notification restrictions for an organization or enterprise were disabled. For more information, see "[Restricting email notifications for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization)" and "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)." |
+{%- endif %}
+
+{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %}
+### `role` 类操作
+
+| 操作        | 描述                                                                                                                                                                                                                     |
+| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `create`  | An organization owner created a new custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。      |
+| `destroy` | An organization owner deleted a custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。          |
+| `update`  | An organization owner edited an existing custom repository role. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。 |
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+### `secret_scanning` 类操作
+
+| 操作                        | 描述                                                                                                                                                                                                            |
+| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret_scanning.disable` | An organization owner disabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `secret_scanning.enable`  | An organization owner enabled secret scanning for all existing{% ifversion ghec %} private or internal{% endif %} repositories.                                                                               |
+
+### `secret_scanning_new_repos` 类操作
+
+| 操作                                  | 描述                                                                                                                                                                                                       |
+| ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret_scanning_new_repos.disable` | An organization owner disabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 |
+| `secret_scanning_new_repos.enable`  | An organization owner enabled secret scanning for all new{% ifversion ghec %} private or internal{% endif %} repositories.                                                                               |
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+### `security_key` category actions
+
+| 操作                      | 描述                                            |
+| ----------------------- | --------------------------------------------- |
+| `security_key.register` | A security key was registered for an account. |
+| `security_key.remove`   | A security key was removed from an account.   |
+{%- endif %}
+
+{%- ifversion fpt or ghec %}
+### `sponsors` 类操作
+
+| 操作                                                     | 描述                                                                                                                                                                                                                                                                                                                      |
+| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `sponsors.agreement_sign`                              | A {% data variables.product.prodname_sponsors %} agreement was signed on behalf of an organization.                                                                                                                                                                                                                     |
+| `sponsors.custom_amount_settings_change`               | Custom amounts for {% data variables.product.prodname_sponsors %} were enabled or disabled, or the suggested custom amount was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."                        |
+| `sponsors.fiscal_host_change`                          | The fiscal host for a {% data variables.product.prodname_sponsors %} listing was updated.                                                                                                                                                                                                                               |
+| `sponsors.withdraw_agreement_signature`                | A signature was withdrawn from a {% data variables.product.prodname_sponsors %} agreement that applies to an organization.                                                                                                                                                                                              |
+| `sponsors.repo_funding_links_file_action`              | The FUNDING file in a repository was changed. 更多信息请参阅“[在仓库中显示赞助按钮](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository)”。                                                                                                          |
+| `sponsors.sponsor_sponsorship_cancel`                  | A sponsorship was canceled. For more information, see "[Downgrading a sponsorship](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)."                                                                                                                                                           |
+| `sponsors.sponsor_sponsorship_create`                  | A sponsorship was created, by sponsoring an account. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."                                                                                                          |
+| `sponsors.sponsor_sponsorship_payment_complete`        | After you sponsor an account and a payment has been processed, the sponsorship payment was marked as complete. For more information, see "[Sponsoring an open source contributor](/sponsors/sponsoring-open-source-contributors/sponsoring-an-open-source-contributor)."                                                |
+| `sponsors.sponsor_sponsorship_preference_change`       | The option to receive email updates from a sponsored account was changed. 更多信息请参阅“[管理您的赞助](/sponsors/sponsoring-open-source-contributors/managing-your-sponsorship)”。                                                                                                                                                   |
+| `sponsors.sponsor_sponsorship_tier_change`             | A sponsorship was upgraded or downgraded. 更多信息请参阅“[升级赞助](/billing/managing-billing-for-github-sponsors/upgrading-a-sponsorship)”和“[降级赞助](/billing/managing-billing-for-github-sponsors/downgrading-a-sponsorship)”。                                                                                                     |
+| `sponsors.sponsored_developer_approve`                 | A {% data variables.product.prodname_sponsors %} account was approved. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."                        |
+| `sponsors.sponsored_developer_create`                  | A {% data variables.product.prodname_sponsors %} account was created. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."                         |
+| `sponsors.sponsored_developer_disable`                 | A {% data variables.product.prodname_sponsors %} account was disabled.                                                                                                                                                                                                                                                  |
+| `sponsors.sponsored_developer_profile_update`          | You edit a sponsored organization profile. For more information, see "[Editing your profile details for {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/editing-your-profile-details-for-github-sponsors)."                                                    |
+| `sponsors.sponsored_developer_redraft`                 | A {% data variables.product.prodname_sponsors %} account was returned to draft state from approved state.                                                                                                                                                                                                               |
+| `sponsors.sponsored_developer_request_approval`        | An application for {% data variables.product.prodname_sponsors %} was submitted for approval. For more information, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)." |
+| `sponsors.sponsored_developer_tier_description_update` | The description for a sponsorship tier was changed. For more information, see "[Managing your sponsorship tiers](/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers)."                                                                                                            |
+| `sponsors.update_tier_welcome_message`                 | The welcome message for a {% data variables.product.prodname_sponsors %} tier for an organization was updated.                                                                                                                                                                                                          |
+| `sponsors.update_tier_repository`                      | A {% data variables.product.prodname_sponsors %} tier changed access for a repository.                                                                                                                                                                                                                                  |
+{%- endif %}
+
+{%- ifversion ghec or ghes or ghae %}
+### `ssh_certificate_authority` category actions
+
+| 操作                                  | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `ssh_certificate_authority.create`  | An SSH certificate authority for an organization or enterprise was created. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." |
+| `ssh_certificate_authority.destroy` | An SSH certificate authority for an organization or enterprise was deleted. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." |
+
+### `ssh_certificate_requirement` category actions
+
+| 操作                                    | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ssh_certificate_requirement.enable`  | The requirement for members to use SSH certificates to access an organization resources was enabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)."  |
+| `ssh_certificate_requirement.disable` | The requirement for members to use SSH certificates to access an organization resources was disabled. For more information, see "[Managing your organization's SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities)" and "[Managing SSH certificate authorities for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)." |
+{%- endif %}
+
+### `staff` category actions
+
+| 操作                   | 描述                                                                                                                                                               |
+| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `staff.disable_repo` | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator disabled access to a repository and all of its forks.   |
+| `staff.enable_repo`  | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator re-enabled access to a repository and all of its forks. |
+{%- ifversion ghes > 3.2 or ghae %}
+| `staff.exit_fake_login`       | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} ended an impersonation session on {% data variables.product.product_name %}. | `staff.fake_login`            | An enterprise owner{% ifversion ghes %} or site administrator{% endif %} signed into {% data variables.product.product_name %} as another user.
+{%- endif %}
+| `staff.repo_lock`             | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator locked (temporarily gained full access to) a user's private repository. | `staff.repo_unlock`           | An organization{% ifversion ghes %}, repository or site{% else %} or repository{% endif %} administrator unlocked (ended their temporary access to) a user's private repository.
+{%- ifversion ghes %}
+| `staff.search_audit_log` | A site administrator performed a search of the site admin audit log.
+{%- endif %}
+| `staff.set_domain_token_expiration` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff set the verification code expiry time for an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+{%- ifversion ghes %}
+| `staff.unlock`                | A site administrator unlocked (temporarily gained full access to) all of a user's private repositories.
+{%- endif %}
+| `staff.unverify_domain` | |{% ifversion ghes %}A site administrator or {% endif %}GitHub staff unverified an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}| | `staff.verify_domain` | {% ifversion ghes %}A site administrator or {% endif %}GitHub staff verified an organization or enterprise domain. {% ifversion ghec or ghes > 3.1 %}For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)" and "[Verifying or approving a domain for your enterprise](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)."{% endif %}
+{%- ifversion ghes %}
+| `staff.view_audit_log` | A site administrator viewed the site admin audit log.
+{%- endif %}
+
+### `team` 类操作
+
+| 操作                        | 描述                                                                                                                                                                                                                                       |
+| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `team.add_member`         | A member of an organization was added to a team. 更多信息请参阅“[将组织成员添加到团队](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)”。                                                                              |
+| `team.add_repository`     | A team was given access and permissions to a repository.                                                                                                                                                                                 |
+| `team.change_parent_team` | A child team was created or a child team's parent was changed. For more information, see "[Moving a team in your organization’s hierarchy](/organizations/organizing-members-into-teams/moving-a-team-in-your-organizations-hierarchy)." |
+| `team.change_privacy`     | A team's privacy level was changed. For more information, see "[Changing team visibility](/organizations/organizing-members-into-teams/changing-team-visibility)."                                                                       |
+| `team.create`             | 已向团队添加用户帐户或仓库。                                                                                                                                                                                                                           |
+| `team.delete`             | 已从团队中移除用户帐户或仓库。                                                                                                                                                                                                                          |
+| `team.destroy`            | 已删除团队。                                                                                                                                                                                                                                   |
+{%- ifversion ghec or ghes or ghae %}
+| `team.demote_maintainer` | A user was demoted from a team maintainer to a team member. | `team.promote_maintainer` | A user was promoted from a team member to a team maintainer. For more information, see "[Promoting an organization member to team maintainer](/organizations/organizing-members-into-teams/assigning-the-team-maintainer-role-to-a-team-member#promoting-an-organization-member-to-team-maintainer)."
+{%- endif %}
+| `team.remove_member` | A member of an organization was removed from a team. For more information, see "[Removing organization members from a team](/organizations/organizing-members-into-teams/removing-organization-members-from-a-team)." | `team.remove_repository` | A repository was no longer under a team's control. | `team.rename` | A team's name was changed. | `team.update_permission` | A team's access was changed. | `team.update_repository_permission` | A team's permission to a repository was changed.
+
+### `team_discussions` 类操作
+
+| 操作                         | 描述                                                                                                                                                                                                                                                  |
+| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `team_discussions.clear`   | An organization owner cleared the setting to allow team discussions for an organization or enterprise.                                                                                                                                              |
+| `team_discussions.disable` | An organization owner disabled team discussions for an organization. For more information, see "[Disabling team discussions for your organization](/organizations/organizing-members-into-teams/disabling-team-discussions-for-your-organization)." |
+| `team_discussions.enable`  | An organization owner enabled team discussions for an organization.                                                                                                                                                                                 |
+
+{%- ifversion ghec %}
+### `team_sync_tenant` category actions
+
+| 操作                                         | 描述                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `team_sync_tenant.disabled`                | Team synchronization with a tenant was disabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." |
+| `team_sync_tenant.enabled`                 | Team synchronization with a tenant was enabled. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)" and "[Managing team synchronization for organizations in your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."  |
+| `team_sync_tenant.update_okta_credentials` | The Okta credentials for team synchronization with a tenant were changed.                                                                                                                                                                                                                                                                                                                                                                                                        |
+{%- endif %}
+
+{%- ifversion fpt or ghes %}
+### `two_factor_authentication` 类操作
+
+| 操作                                                      | 描述                                                                         |
+| ------------------------------------------------------- | -------------------------------------------------------------------------- |
+| `two_factor_authentication.disabled`                    | [Two-factor authentication][2fa] was disabled for a user account.          |
+| `two_factor_authentication.enabled`                     | [Two-factor authentication][2fa] was enabled for a user account.           |
+| `two_factor_authentication.password_reset_fallback_sms` | A one-time password code was sent to a user account fallback phone number. |
+| `two_factor_authentication.recovery_codes_regenerated`  | Two factor recovery codes were regenerated for a user account.             |
+| `two_factor_authentication.sign_in_fallback_sms`        | A one-time password code was sent to a user account fallback phone number. |
+| `two_factor_authentication.update_fallback`             | The two-factor authentication fallback for a user account was changed.     |
+{%- endif %}
+
+{%- ifversion fpt or ghes or ghae %}
+### `user` 类操作
+
+| 操作                                  | 描述                                                                                                                                                                              |
+| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `user.add_email`                    | 已向用户帐户添加电子邮件地址。                                                                                                                                                                 |
+| `user.async_delete`                 | An asynchronous job was started to destroy a user account, eventually triggering a `user.delete` event.                                                                         |
+| `user.audit_log_export`             | Audit log entries were exported.                                                                                                                                                |
+| `user.block_user`                   | A user was blocked by another user{% ifversion ghes %} or a site administrator{% endif %}.                                                                                      |
+| `user.change_password`              | 用户已更改其密码。                                                                                                                                                                       |
+| `user.create`                       | 已创建新的用户帐户。                                                                                                                                                                      |
+| `user.creation_rate_limit_exceeded` | The rate of creation of user accounts, applications, issues, pull requests or other resources exceeded the configured rate limits, or too many users were followed too quickly. |
+| `user.delete`                       | 已通过异步作业销毁用户帐户。                                                                                                                                                                  |
+{%- ifversion ghes %}
+| `user.demote`                     | A site administrator was demoted to an ordinary user account.
+{%- endif %}
+| `user.destroy`                    | A user deleted his or her account, triggering `user.async_delete`. | `user.failed_login`               | A user tries to sign in with an incorrect username, password, or two-factor authentication code. | `user.flag_as_large_scale_contributor` | A user account was flagged as a large scale contributor. Only contributions from public repositories the user owns will be shown in their contribution graph, in order to prevent timeouts. | `user.forgot_password`            | A user requested a password reset via the sign-in page. | `user.hide_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now hidden. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)." | `user.lockout` | A user was locked out of their account. | `user.login`                      | A user signed in.
+{%- ifversion ghes or ghae %}
+| `user.mandatory_message_viewed`   | A user viewed a mandatory message. For more information see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise)" for details."
+{%- endif %}
+| `user.minimize_comment` | A comment made by a user was minimized.
+{%- ifversion ghes %}
+| `user.promote`                    | An ordinary user account was promoted to a site administrator.
+{%- endif %}
+| `user.recreate` | A user's account was restored. | `user.remove_email`               | An email address was removed from a user account. | `user.remove_large_scale_contributor_flag` | A user account was no longer flagged as a large scale contributor. | `user.rename`                     | A username was changed. | `user.reset_password` | A user reset their account password. | `user.show_private_contributions_count` | A user changed the visibility of their private contributions. The number of contributions to private repositories on the user's profile are now shown. For more information, see "[Publicizing or hiding your private contributions on your profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile)." | `user.sign_in_from_unrecognized_device` | A user signed in from an unrecognized device. | `user.sign_in_from_unrecognized_device_and_location` | A user signed in from an unrecognized device and location. | `user.sign_in_from_unrecognized_location` | A user signed in from an unrecognized location. | `user.suspend`                    | A user account was suspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}. | `user.two_factor_challenge_failure` | A 2FA challenge issued for a user account failed. | `user.two_factor_challenge_success` | A 2FA challenge issued for a user account succeeded. | `user.two_factor_recover` | A user used their 2FA recovery codes. | `user.two_factor_recovery_codes_downloaded` | A user downloaded 2FA recovery codes for their account. | `user.two_factor_recovery_codes_printed` | A user printed 2FA recovery codes for their account. | `user.two_factor_recovery_codes_viewed` | A user viewed 2FA recovery codes for their account. | `user.two_factor_requested`       | A user was prompted for a two-factor authentication code. | `user.unblock_user` | A user was unblocked another user{% ifversion ghes %} or a site administrator{% endif %}. | `user.unminimize_comment` | A comment made by a user was unminimized. | `user.unsuspend` | A user account was unsuspended by an enterprise owner {% ifversion ghes %} or site administrator{% endif %}.
+{%- endif %}
+
+{%- ifversion ghec or ghes %}
+### `user_license` category actions
+
+| 操作                     | 描述                                                           |
+| ---------------------- | ------------------------------------------------------------ |
+| `user_license.create`  | A seat license for a user in an enterprise was created.      |
+| `user_license.destroy` | A seat license for a user in an enterprise was deleted.      |
+| `user_license.update`  | A seat license type for a user in an enterprise was changed. |
+{%- endif %}
+
+{% ifversion fpt or ghec or ghes > 3.1 or ghae %}
+### `workflows` 类操作
+
+{% data reusables.audit_log.audit-log-events-workflows %}
+{%- endif %}
+
+  [OAuth access token]: /developers/apps/building-oauth-apps/authorizing-oauth-apps
+
+  [OAuth application]: /guides/basics-of-authentication/#registering-your-app
+
+  [OAuth 应用程序]: /guides/basics-of-authentication/#registering-your-app
+
+  [add key]: /authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account
+  [deploy key]: /developers/overview/managing-deploy-keys#deploy-keys
+
+  [2fa]: /authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
new file mode 100644
index 0000000000..cd2d65eab8
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md
@@ -0,0 +1,51 @@
+---
+title: Exporting audit log activity for your enterprise
+intro: You can export audit and Git events data to a file for offline analysis.
+shortTitle: Export audit logs
+permissions: Enterprise owners can export the audit log.
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+type: tutorial
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+---
+
+## About exports of audit log and Git events data
+
+You can export the audit log by downloading a JSON or CSV file from your enterprise on {% data variables.product.product_name %}. When you export audit log events, you can query by one or more of these supported qualifiers to filter for specific log events to export. For more information about search qualifiers, see "[Search based on the action performed](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise#search-based-on-the-action-performed)."
+
+You can export Git events data by downloading a JSON file from your enterprise audit log. Unlike audit log data, you cannot query for specific Git events to filter and export in the audit log user interface.
+
+{% data reusables.audit_log.exported-log-keys-and-values %}
+
+As an alternative to exporting log events, you can use the API to retrieve audit log events, or set up {% data variables.product.product_name %} to stream audit data as events are logged. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)" and "[Streaming the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise)."
+
+## Exporting audit log data
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+1. Optionally, to only export filtered results, search by one or more supported qualifiers or log filters.
+2. Select the {% octicon "download" aria-label="The Download icon" %} **Export** dropdown menu, and choose the file format (JSON or CSV) to export log events in.
+
+    ![导出按钮](/assets/images/help/organizations/org-audit-log-export.png)
+
+## Exporting Git events data
+
+You can also export Git events data by date range.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.settings-tab %}
+{% data reusables.enterprise-accounts.audit-log-tab %}
+1. Select the {% octicon "download" aria-label="The Download icon" %} **Export Git Events** dropdown menu and choose a date range to export log events for.
+
+    ![Export Git events button](/assets/images/help/organizations/org-audit-log-export-git-events.png)
+1. Click {% octicon "file-zip" aria-label="The File-zip icon" %} **Download Results** to download the file.
+1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. 例如：
+
+    ```
+    gunzip export-avocado-corp-1642896556.json.gz
+    ```
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
new file mode 100644
index 0000000000..d554271aaa
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/index.md
@@ -0,0 +1,20 @@
+---
+title: Reviewing audit logs for your enterprise
+intro: You can view user and system activity in the audit logs for your enterprise.
+shortTitle: Review audit logs
+versions:
+  ghec: '*'
+  ghes: '*'
+  ghae: '*'
+topics:
+  - Enterprise
+children:
+  - /about-the-audit-log-for-your-enterprise
+  - /accessing-the-audit-log-for-your-enterprise
+  - /searching-the-audit-log-for-your-enterprise
+  - /exporting-audit-log-activity-for-your-enterprise
+  - /streaming-the-audit-log-for-your-enterprise
+  - /using-the-audit-log-api-for-your-enterprise
+  - /audit-log-events-for-your-enterprise
+---
+
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
new file mode 100644
index 0000000000..2a951df4c4
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md
@@ -0,0 +1,130 @@
+---
+title: Searching the audit log for your enterprise
+intro: You can search an extensive list of audited actions in your enterprise.
+shortTitle: Search audit logs
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can search the audit log.'
+redirect_from:
+  - /enterprise/admin/articles/searching-the-audit-log
+  - /enterprise/admin/installation/searching-the-audit-log
+  - /enterprise/admin/user-management/searching-the-audit-log
+  - /admin/user-management/searching-the-audit-log
+  - /admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log
+versions:
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+miniTocMaxHeadingLevel: 3
+---
+
+## About search for the enterprise audit log
+
+You can search your enterprise audit log directly from the user interface by using the **Filters** dropdown, or by typing a search query.
+
+  ![搜索查询](/assets/images/enterprise/site-admin-settings/search-query.png)
+
+For more information about viewing your enterprise audit log, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)."
+
+You can also use the API to retrieve audit log events. For more information, see "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise)."
+
+请注意，无法使用文本搜索条目。 但是，您可以使用各种过滤器构建搜索查询。 查询日志时使用的许多运算符，如 `-`、`>` 或 `<`，与在 {% data variables.product.product_name %} 上搜索时的格式相同。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上搜索](/search-github/getting-started-with-searching-on-github/about-searching-on-github)”。
+
+{% note %}
+
+**注**：{% data reusables.audit_log.retention-periods %}
+
+{% endnote %}
+
+## Search query filters
+
+|                          过滤，过滤器 | 描述                                                                                                                                                                                                                                    |
+| -------------------------------:| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|          `Yesterday's activity` | All actions created in the past day.                                                                                                                                                                                                  |
+| `Enterprise account management` | All actions in the `business` category.                                                                                                                                                                                               |
+|                        `组织成员资格` | All actions for when a new user was invited to join an organization.                                                                                                                                                                  |
+|               `Team management` | All actions related to team management.<br/>- When a user account or repository was added or removed from a team<br/>- When a team maintainer was promoted or demoted<br/>-  When a team was deleted                |
+|         `Repository management` | All actions for repository management.<br/>- When a repository was created or deleted<br/>- When the repository visibility was changed<br/>- When a team was added or removed from a repository{% ifversion ghec %}
+|               `Billing updates` | All actions concerning how your enterprise pays for {% data variables.product.prodname_dotcom %} and for when your billing email address was changed.{% endif %}
+|                 `Hook activity` | All actions for webhooks and pre-receive hooks.                                                                                                                                                                                       |
+|           `Security management` | All actions concerning SSH keys, deploy keys, security keys, 2FA, and SAML single sign-on credential authorization, and vulnerability alerts for repositories.                                                                        |
+
+## 搜索查询语法
+
+You can compose a search query from one or more `key:value` pairs, separated by AND/OR logical operators. 例如，要查看自 2017 年初开始影响仓库 `octocat/Spoon-Knife` 的所有操作：
+
+  `repo:"octocat/Spoon-Knife" AND created:>=2017-01-01`
+
+The `key:value` pairs that can be used in a search query are:
+
+|              键 | 值                                                                                                                                                   |
+| --------------:| --------------------------------------------------------------------------------------------------------------------------------------------------- |
+|     `actor_id` | 发起操作的用户帐户的 ID                                                                                                                                       |
+|        `actor` | 发起操作的用户帐户的名称                                                                                                                                        |
+| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID                                                                                                                              |
+|       `action` | 已审核操作的名称                                                                                                                                            |
+|      `user_id` | 受操作影响的用户的 ID                                                                                                                                        |
+|           `用户` | 受操作影响的用户的名称                                                                                                                                         |
+|      `repo_id` | 受操作影响的仓库的 ID（若适用）                                                                                                                                   |
+|         `repo` | 受操作影响的仓库的名称（若适用）                                                                                                                                    |
+|     `actor_ip` | 发起操作的 IP 地址                                                                                                                                         |
+|      `created` | Time at which the action occurred{% ifversion ghes %}. If querying the audit log from the site admin dashboard, use `created_at` instead{% endif %}
+|         `from` | 发起操作的视图                                                                                                                                             |
+|         `note` | 事件特定的其他信息（采用纯文本或 JSON 格式）                                                                                                                           |
+|          `org` | 受操作影响的组织的名称（若适用）                                                                                                                                    |
+|       `org_id` | 受操作影响的组织的 ID（若适用）                                                                                                                                   |
+|     `business` | Name of the enterprise affected by the action (if applicable)                                                                                       |
+|  `business_id` | ID of the enterprise affected by the action (if applicable)                                                                                         |
+
+To see actions grouped by category, you can also use the action qualifier as a `key:value` pair. For more information, see "[Search based on the action performed](#search-based-on-the-action-performed)."
+
+For a full list of actions in your enterprise audit log, see "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)."
+
+## 搜索审核日志
+
+{% data reusables.audit_log.audit-log-search-by-operation %}
+
+{% data reusables.audit_log.audit-log-search-by-repo %}
+
+{% data reusables.audit_log.audit-log-search-by-user %}
+
+### 基于执行的操作搜索
+
+要搜索特定事件，请在查询中使用 `action` 限定符。 例如：
+
+  * `action:team` 会找到团队类别中的所有事件。
+  * `-action:hook` 会排除 web 挂钩类别中的所有事件。
+
+每个类别都有一组可进行过滤的关联操作。 例如：
+
+  * `action:team.create` 会找到团队创建处的所有事件。
+  * `-action:hook.events_changed` 会排除 web 挂钩上事件已经改动的所有事件。
+
+Actions that can be found in your enterprise audit log are grouped within the following categories:
+
+{% data reusables.audit_log.audit-log-action-categories %}
+### 基于操作时间搜索
+
+使用 `created` 限定符在审核日志中根据事件发生的时间过滤事件。
+
+{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}
+
+{% data reusables.search.date_gt_lt %}
+
+例如：
+
+  * `created:2014-07-08` 会找到在 2014 年 7 月 8 日发生的所有事件。
+  * `created:>=2014-07-08` 查找在 2014 年 7 月 8 日或之后发生的所有事件。
+  * `created:<=2014-07-08` 查找在 2014 年 7 月 8 日或之前发生的所有事件。
+  * `created:2014-07-01..2014-07-31` 会找到在 2014 年 7 月发生的所有事件。
+
+### 基于位置搜索
+
+使用限定符 `country`，您可以在审核日志中根据发生事件的国家/地区过滤事件。 You can use a country's two-letter short code or full name. Countries with spaces in their name will need to be wrapped in quotation marks. 例如：
+
+  * `country:de` 会找到在德国发生的所有事件。
+  * `country:Mexico` 会找到在墨西哥发生的所有事件。
+  * `country:"United States"` 会找到在美国发生的所有事件。
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
similarity index 90%
rename from translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
rename to translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
index ea9a747065..c19c3f01f7 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md
@@ -1,5 +1,5 @@
 ---
-title: 流式传输企业帐户中组织的审核日志
+title: Streaming the audit log for your enterprise
 intro: '您可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。'
 miniTocMaxHeadingLevel: 3
 versions:
@@ -10,27 +10,13 @@ topics:
   - Enterprise
   - Logging
   - Organizations
-shortTitle: 流式传输组织审核日志
+shortTitle: Stream audit logs
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
+  - /admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account
 permissions: Enterprise owners can configure audit log streaming.
 ---
 
-## 关于导出审核数据
-
-您可以通过多种方式从 {% data variables.product.prodname_dotcom %} 中提取审核日志和 Git 事件数据：
-
-* 转到 {% data variables.product.prodname_dotcom %} 中的审核日志页，然后单击 **Export（导出）**。 更多信息请参阅“[查看企业帐户中组织的审核日志](/github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account)”和“[导出审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)”。
-* 使用 API 轮询新的审核日志事件。 更多信息请参阅“[使用审核日志 API](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#using-the-audit-log-api)”。
-* 设置 {% data variables.product.product_name %} 以在记录事件时流式传输审核数据。
-
-目前，多个存储提供商支持审核日志流式处理。
-- Amazon S3
-- Azure Blob Storage
-- Azure Event Hubs
-- Google Cloud Storage
-- Splunk
-
 ## 关于审核日志流
 
 为了帮助保护您的知识产权并保持组织的合规性，您可以使用流式处理来保留审核日志数据的副本并监控：
@@ -40,7 +26,7 @@ permissions: Enterprise owners can configure audit log streaming.
 
 * **数据探索**。 您可以使用首选工具检查流事件，以查询大量数据。 流包含整个企业帐户中的审核事件和 Git 事件。
 * **数据连续性**。 您可以暂停流长达七天，而不会丢失任何审核数据。
-* **数据保留**。 您可以根据需要保留导出的审核日志和 Git 数据。
+* **数据保留**。 You can keep your exported audit logs and Git events data as long as you need to.
 
 企业所有者可以随时设置、暂停或删除流。 流导出企业中所有组织的审核数据。
 
diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
new file mode 100644
index 0000000000..c2ca7b688f
--- /dev/null
+++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md
@@ -0,0 +1,143 @@
+---
+title: Using the audit log API for your enterprise
+intro: 'You can programmatically retrieve enterprise events with the{% ifversion ghec or ghes > 3.2 %} REST or{% endif %} GraphQL API.'
+shortTitle: Audit log API
+permissions: 'Enterprise owners {% ifversion ghes %}and site administrators {% endif %}can use the audit log API.'
+miniTocMaxHeadingLevel: 3
+versions:
+  ghec: '*'
+  ghes: '>=3.0'
+  ghae: '*'
+type: tutorial
+topics:
+  - Auditing
+  - Enterprise
+  - Logging
+  - API
+---
+
+## 使用审核日志 API
+
+您可以使用 GraphQL API{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %} 或 REST API{% endif %} 与审核日志交互。
+
+Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time).
+
+{% ifversion ghec or ghes > 3.0 or ghae %}
+## Querying the audit log GraphQL API
+
+To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audit-log-api-info %}
+
+Note that you can't retrieve Git events using the {% ifversion not ghec %}audit log API.{% else %}GraphQL API. 要检索 Git 事件，请改为使用 REST API。 For more information, see `git` category actions in "[Audit log actions for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#git-category-actions)", and also the "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization) audit log endpoints in the REST API documentation."{% endif %}
+
+GraphQL 响应可包含长达 90 至 120 天的数据。
+
+### Example 1: Members added to or removed from organizations in an enterprise
+
+The query below fetches the audit logs for the `avocado-corp` enterprise and returns the first 10 organizations in the enterprise, where the only actions performed were adding or removing a member from an organization. The first 20 audit log entries for each organization are returned.
+
+This query uses the [auditlog](/graphql/reference/objects) field from the Organization object, and the [OrgAddMemberAuditEntry](/graphql/reference/objects#orgaddmemberauditentry) and [OrgRemoveMemberAuditEntry](/graphql/reference/objects#orgremovememberauditentry) objects. The  {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an organization owner for each organization within the enterprise.
+
+```shell
+{
+  enterprise(slug: "avocado-corp") {
+    organizations(first: 10, orderBy: {field: LOGIN, direction: DESC}) {
+      nodes {
+        name
+        auditLog(first: 20) {
+          edges {
+            node {
+              ... on OrgAddMemberAuditEntry {
+                action
+                actorLogin
+                createdAt
+              }
+              ... on OrgRemoveMemberAuditEntry {
+                action
+                actorLogin
+                createdAt
+              }
+            }
+          }
+        }
+      }
+      pageInfo {
+        hasNextPage
+        endCursor
+      }
+    }
+  }
+}
+```
+
+The GraphQL API will return at most 100 nodes per query. To retrieve additional results, you'll need to implement pagination. For more information, see "[Resource limitations](/graphql/overview/resource-limitations#node-limit)" in the GraphQL API documentation and [Pagination](https://graphql.org/learn/pagination/) in the official GraphQL documentation.
+### Example 2: Events in an organization, for a specific date and actor
+
+You can specify multiple search phrases, such as `created` and `actor`, by separating them in your query string with a space.
+
+The query below fetches all the audit logs for the `avocado-corp` enterprise that relate to the `octo-org` organization, where the actions were performed by the `octocat` user on or after the 1 Jan, 2022. The first 20 audit log entries are returned, with the newest log entry appearing first.
+
+This query uses the [AuditEntry](/graphql/reference/interfaces#auditentry) interface. The {% data variables.product.prodname_dotcom %} account querying the enterprise audit log must be an owner of the `octo-org` organization.
+
+```shell
+{
+  enterprise(slug: "avocado-corp") {
+    organizations(first: 1, query: "octo-org") {
+      nodes {
+        name
+        auditLog(first: 20, query: "actor:octocat created:>=2022-01-01T00:00:00.000Z", orderBy: {field: CREATED_AT, direction: DESC}) {
+          edges {
+            node {
+              ... on AuditEntry {
+                action
+                actorLogin
+                createdAt
+                user {
+                  name
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+For more query examples, see the [platform-samples repository](https://github.com/github/platform-samples/blob/master/graphql/queries).
+
+{% endif %}
+{% ifversion ghec or ghes > 3.2 or ghae-issue-6648 %}
+## Querying the audit log REST API
+
+To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
+{% data reusables.audit_log.audited-data-list %}
+
+{% data reusables.audit_log.retention-periods %}
+
+For more information about the audit log REST API, see "[Enterprise administration](/rest/reference/enterprise-admin#audit-log)" and "[Organizations](/rest/reference/orgs#get-the-audit-log-for-an-organization)."
+
+### Example 1: All events in an enterprise, for a specific date, with pagination
+
+The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and return the first page with a maximum of 100 items per page using [REST API pagination](/rest/overview/resources-in-the-rest-api#pagination):
+
+```shell
+curl -H "Authorization: token <em>TOKEN</em>" \
+--request GET \
+"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&page=1&per_page=100"
+```
+
+### Example 2: Events for pull requests in an enterprise, for a specific date and actor
+
+You can specify multiple search phrases, such as `created` and `actor`, by separating them in your formed URL with the `+` symbol or ASCII character code `%20`.
+
+The query below searches for audit log events for pull requests, where the event occurred on or after Jan 1st, 2022 in the `avocado-corp` enterprise, and the action was performed by the `octocat` user:
+
+```shell
+curl -H "Authorization: token <em>TOKEN</em>" \
+--request GET \
+"https://api.github.com/enterprises/avocado-corp/audit-log?phrase=action:pull_request+created:>=2022-01-01+actor:octocat"
+```
+
+{% endif %}
diff --git a/translations/zh-CN/content/admin/overview/system-overview.md b/translations/zh-CN/content/admin/overview/system-overview.md
index 2403137358..3fd3da904c 100644
--- a/translations/zh-CN/content/admin/overview/system-overview.md
+++ b/translations/zh-CN/content/admin/overview/system-overview.md
@@ -39,15 +39,15 @@ topics:
 
 ## 部署选项
 
-您可以将 {% data variables.product.prodname_ghe_server %} 部署为一个虚拟设备，也可采用高可用性配置。 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-github-enterprise-server-for-high-availability/)”。
+您可以将 {% data variables.product.prodname_ghe_server %} 部署为一个虚拟设备，也可采用高可用性配置。 更多信息请参阅“[配置 {% data variables.product.prodname_ghe_server %} 以实现高可用性](/admin/enterprise-management/configuring-high-availability)”。
 
-某些拥有成千上万名开发者的组织还会从使用 {% data variables.product.prodname_ghe_server %} 集群中受益。 更多信息请参阅“[关于集群](/enterprise/{{ currentVersion }}/admin/guides/clustering/about-clustering)。”
+某些拥有成千上万名开发者的组织还会从使用 {% data variables.product.prodname_ghe_server %} 集群中受益。 更多信息请参阅“[关于集群](/admin/enterprise-management/configuring-clustering/about-clustering)。”
 
 ## 数据保留和数据中心冗余
 
 {% danger %}
 
-在生产环境中使用 {% data variables.product.prodname_ghe_server %} 之前，我们强烈建议您设置备份和灾难恢复计划。 更多信息请参阅“[在设备上配置备份](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)”。
+在生产环境中使用 {% data variables.product.prodname_ghe_server %} 之前，我们强烈建议您设置备份和灾难恢复计划。 更多信息请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。
 
 {% enddanger %}
 
@@ -55,7 +55,7 @@ topics:
 
 除网络备份外，在设备处于离线或维护模式时，还支持用户存储卷的 AWS (EBS) 和 VMware 磁盘快照。 如果您的服务级别要求允许定期离线维护，可以将定期卷快照用作低成本、低复杂性的方案，代替通过 {% data variables.product.prodname_enterprise_backup_utilities %} 进行网络备份。
 
-更多信息请参阅“[在设备上配置备份](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-backups-on-your-appliance)”。
+更多信息请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。
 
 ## 安全
 
@@ -80,11 +80,11 @@ topics:
 
 目前，{% data variables.product.prodname_ghe_server %} 设备的基础是 Debian 9 (Stretch)，并接受 Debian 长期支持计划的支持。  计划在 Stretch 的 Debian LTS 期间结束前迁移到更新的基础操作系统。
 
-定期补丁更新发布在 {% data variables.product.prodname_ghe_server %} [发行](https://enterprise.github.com/releases)页面上，[发行说明](/enterprise-server/admin/release-notes)页面提供详细信息。 这些补丁一般含有经过测试并且质量经过我们工程团队批准的上游供应商和项目安全补丁。 从上游更新发布到测试以及捆绑于即将发布的 {% data variables.product.prodname_ghe_server %} 补丁版本中时，可能稍有延迟。
+定期补丁更新发布在 {% data variables.product.prodname_ghe_server %} [发行](https://enterprise.github.com/releases)页面上，[发行说明](/admin/release-notes)页面提供详细信息。 这些补丁一般含有经过测试并且质量经过我们工程团队批准的上游供应商和项目安全补丁。 从上游更新发布到测试以及捆绑于即将发布的 {% data variables.product.prodname_ghe_server %} 补丁版本中时，可能稍有延迟。
 
 ### 网络安全性
 
-{% data variables.product.prodname_ghe_server %} 的内部防火墙限制对设备服务的网络访问。 网络上仅提供设备正常运行所需的服务。 更多信息请参阅“[网络端口](/enterprise/{{ currentVersion }}/admin/guides/installation/network-ports)”。
+{% data variables.product.prodname_ghe_server %} 的内部防火墙限制对设备服务的网络访问。 网络上仅提供设备正常运行所需的服务。 更多信息请参阅“[网络端口](/admin/configuration/configuring-network-settings/network-ports)”。
 
 ### 应用程序安全性
 
@@ -92,15 +92,15 @@ topics:
 
 ### 外部服务和支持
 
-{% data variables.product.prodname_ghe_server %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务，以提供电子邮件传送、外部监控和日志转发等功能。 更多信息请参阅“[配置电子邮件通知](/admin/configuration/configuring-email-for-notifications)”、“[设置外部监控](/enterprise/{{ currentVersion }}/admin/installation/setting-up-external-monitoring)”和“[日志转发](/admin/user-management/log-forwarding)”。
+{% data variables.product.prodname_ghe_server %} 无需从网络访问外部服务也可以正常运行。 您可以选择集成外部服务，以提供电子邮件传送、外部监控和日志转发等功能。 更多信息请参阅“[配置电子邮件通知](/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications)”、“[设置外部监控](/admin/enterprise-management/monitoring-your-appliance/setting-up-external-monitoring)”和“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)”。
 
-您可以手动收集故障排除数据并发送至 {% data variables.contact.github_support %}。 更多信息请参阅“[向 {% data variables.contact.github_support %} 提供数据](/enterprise/{{ currentVersion }}/admin/enterprise-support/providing-data-to-github-support)”。
+您可以手动收集故障排除数据并发送至 {% data variables.contact.github_support %}。 更多信息请参阅“[将数据提供给 {% data variables.contact.github_support %}](/support/contacting-github-support/providing-data-to-github-support)”。
 
 ### 加密通信
 
-{% data variables.product.prodname_dotcom %} 将 {% data variables.product.prodname_ghe_server %} 设计为在公司防火墙后面运行。 为确保线路通信安全，我们建议您启用传输层安全协议 (TLS)。 {% data variables.product.prodname_ghe_server %} 在 HTTPS 流量方面支持 2048 位和更高的商业 TLS 证书。 更多信息请参阅“[配置 TLS](/enterprise/{{ currentVersion }}/admin/installation/configuring-tls)”。
+{% data variables.product.prodname_dotcom %} 将 {% data variables.product.prodname_ghe_server %} 设计为在公司防火墙后面运行。 为确保线路通信安全，我们建议您启用传输层安全协议 (TLS)。 {% data variables.product.prodname_ghe_server %} 在 HTTPS 流量方面支持 2048 位和更高的商业 TLS 证书。 更多信息请参阅“[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)”。
 
-默认情况下，该设备还为使用 Git 的仓库访问和管理目的提供安全 Shell (SSH) 访问。 更多信息请参阅“[关于 SSH](/enterprise/user/articles/about-ssh)”和“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)“。
+默认情况下，该设备还为使用 Git 的仓库访问和管理目的提供安全 Shell (SSH) 访问。 更多信息请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)“。
 
 {% ifversion ghes > 3.3 %}
 
@@ -112,24 +112,24 @@ topics:
 
 {% data variables.product.prodname_ghe_server %} 提供三种类型的帐户。
 
-- `管理员` Linux 用户帐户已控制对基础操作系统的访问，包括对直接文件系统和数据库的访问。 一小部分受信任的管理员应该有权访问此帐户，他们可以通过 SSH 访问。 更多信息请参阅“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)”。
+- `管理员` Linux 用户帐户已控制对基础操作系统的访问，包括对直接文件系统和数据库的访问。 一小部分受信任的管理员应该有权访问此帐户，他们可以通过 SSH 访问。 更多信息请参阅“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)。”
 - 设备 Web 应用程序中的用户帐户对自己的数据以及其他用户或组织明确授予权限的任何数据具有完全访问权限。
 - 设备 Web 应用程序中的站点管理员是可以管理高级 Web 应用程序和设备设置、用户和组织帐户设置以及仓库数据的用户帐户。
 
-关于 {% data variables.product.prodname_ghe_server %} 用户权限的更多信息，请参阅“[GitHub 上的访问权限](/enterprise/user/articles/access-permissions-on-github) ”。
+关于 {% data variables.product.prodname_ghe_server %} 用户权限的更多信息，请参阅“[GitHub 上的访问权限](/get-started/learning-about-github/access-permissions-on-github) ”。
 
 ### 身份验证
 
 {% data variables.product.prodname_ghe_server %} 提供四种身份验证方法。
 
-- SSH 公钥身份验证提供使用 Git 的仓库访问权限和管理 shell 的访问权限。 更多信息请参阅“[关于 SSH](/enterprise/user/articles/about-ssh)”和“[访问管理 shell (SSH)](/enterprise/{{ currentVersion }}/admin/installation/accessing-the-administrative-shell-ssh)“。
-- 使用 HTTP cookie 的用户名和密码身份验证提供 Web 应用程序访问和会话管理权限，可选择双重身份验证 (2FA)。 更多信息请参阅“[使用内置身份验证](/enterprise/{{ currentVersion }}/admin/user-management/using-built-in-authentication)”。
-- 使用 LDAP 服务、SAML 身份提供程序 (IdP) 或其他兼容服务的外部 LDAP、SAML 或 CAS 身份验证提供对 Web 应用程序的访问权限。 更多信息请参阅“[为您的 GitHub Enterprise Server 实例验证用户身份](/enterprise/{{ currentVersion }}/admin/user-management/authenticating-users-for-your-github-enterprise-server-instance)“。
+- SSH 公钥身份验证提供使用 Git 的仓库访问权限和管理 shell 的访问权限。 更多信息请参阅“[关于 SSH](/authentication/connecting-to-github-with-ssh/about-ssh)”和“[访问管理 shell (SSH)](/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh)“。
+- 使用 HTTP cookie 的用户名和密码身份验证提供 Web 应用程序访问和会话管理权限，可选择双重身份验证 (2FA)。 更多信息请参阅“[使用内置身份验证](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-built-in-authentication)”。
+- 使用 LDAP 服务、SAML 身份提供程序 (IdP) 或其他兼容服务的外部 LDAP、SAML 或 CAS 身份验证提供对 Web 应用程序的访问权限。 更多信息请参阅“[为您的 GitHub Enterprise Server 实例验证用户身份](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance)“。
 - OAuth 和个人访问令牌为外部客户端和服务提供对 Git 仓库数据和 API 的访问权限。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
 
 ### 审核和访问日志记录
 
-{% data variables.product.prodname_ghe_server %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志，永久存储在 {% data variables.product.prodname_ghe_server %} 上。 您可以通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 更多信息请参阅“[日志转发](/admin/user-management/log-forwarding)。”
+{% data variables.product.prodname_ghe_server %} 存储传统的操作系统日志和应用程序日志。 应用程序还会编写详细的审核和安全日志，永久存储在 {% data variables.product.prodname_ghe_server %} 上。 您可以通过 `syslog-ng` 协议将两种类型的日志实时转发到多个目标。 更多信息请参阅“[日志转发](/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/log-forwarding)。”
 
 访问和审核日志包括如下信息。
 
@@ -158,6 +158,6 @@ topics:
 
 ## 延伸阅读
 
-- “[设置 {% data variables.product.prodname_ghe_server %} 的试用版](/articles/setting-up-a-trial-of-github-enterprise-server)”
-- “[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-github-enterprise-server-instance)”
+- “[设置 {% data variables.product.prodname_ghe_server %} 的试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)”
+- “[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”
 - `github/roadmap` 仓库中的 [ {% data variables.product.prodname_roadmap %} ]({% data variables.product.prodname_roadmap_link %})
diff --git a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
index be965ea492..792c2c0661 100644
--- a/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
+++ b/translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md
@@ -115,7 +115,7 @@ shortTitle: 仓库管理策略
 
 ## 执行邀请{% ifversion ghec %} 外部{% endif %} 协作者参与仓库的策略
 
-在您的企业帐户拥有的所有组织中，您可以允许成员邀请{% ifversion ghec %}外部{% endif %}协作者加入仓库、将{% ifversion ghec %}外部协作者{% endif %}邀请限制为组织所有者或允许所有者在组织级别管理设置。
+在企业拥有的所有组织中，您可以允许成员邀请{% ifversion ghec %}外部{% endif %} 协作者访问存储库，限制{% ifversion ghec %}外部协作者 {% endif %}邀请组织所有者，{% if prevent-org-admin-add-outside-collaborator %}限制{% ifversion ghec %}外部协作者 {% endif %}邀请企业所有者，{% endif %}或允许组织所有者在组织级别管理设置。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
diff --git a/translations/zh-CN/content/admin/user-management/index.md b/translations/zh-CN/content/admin/user-management/index.md
index 8546570a0f..6799e8c43d 100644
--- a/translations/zh-CN/content/admin/user-management/index.md
+++ b/translations/zh-CN/content/admin/user-management/index.md
@@ -1,6 +1,6 @@
 ---
 title: 管理用户、组织和仓库
-shortTitle: 管理用户、组织和仓库
+shortTitle: 管理用户、组织和存储库
 intro: 本指南介绍了可让用户登录您的企业的身份验证方法、如何创建组织和团队以进行仓库访问和协作，并针对用户安全提供了最佳实践建议。
 redirect_from:
   - /enterprise/admin/categories/user-management
@@ -18,7 +18,6 @@ children:
   - /managing-users-in-your-enterprise
   - /managing-organizations-in-your-enterprise
   - /managing-repositories-in-your-enterprise
-  - /monitoring-activity-in-your-enterprise
   - /migrating-data-to-and-from-your-enterprise
 ---
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
index 8cd63f3225..8b64e3beee 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/index.md
@@ -23,8 +23,6 @@ children:
   - /requiring-two-factor-authentication-for-an-organization
   - /creating-teams
   - /adding-people-to-teams
-  - /viewing-the-audit-logs-for-organizations-in-your-enterprise
-  - /streaming-the-audit-logs-for-organizations-in-your-enterprise-account
   - /managing-your-role-in-an-organization-owned-by-your-enterprise
   - /removing-users-from-teams-and-organizations
   - /removing-organizations-from-your-enterprise
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
index 5333eb7d1d..ecb4362b9c 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-your-role-in-an-organization-owned-by-your-enterprise.md
@@ -1,6 +1,6 @@
 ---
-title: Managing your role in an organization owned by your enterprise
-intro: You can manage your membership in any organization owned by your enterprise and change your role within the organization.
+title: 管理您在企业拥有的组织中的角色
+intro: 您可以管理您在企业拥有的任何组织中的成员身份，并更改您在组织中的角色。
 permissions: Enterprise owners can manage their role in an organization owned by the enterprise.
 versions:
   feature: enterprise-owner-join-org
@@ -9,46 +9,46 @@ topics:
   - Administrator
   - Enterprise
   - Organizations
-shortTitle: Manage your organization roles
+shortTitle: 管理您的组织角色
 ---
 
 {% note %}
 
-**Note:** The ability for enterprise owners to manage their role in an organization owned by the enterprise is in beta and subject to change.
+**注意：** 企业所有者在企业拥有的组织中管理其角色的能力处于测试阶段，可能会发生变化。
 
 {% endnote %}
 
-## About role management
+## 关于角色管理
 
-You can choose to join an organization owned by your enterprise as a member or as an organization owner, change your role within the organization, or leave the organization.
+您可以选择以成员或组织所有者的身份加入企业拥有的组织，更改您在组织中的角色或离开组织。
 
 {% warning %}
 
-**Warning**: If an organization uses SCIM to provision users, joining the organization this way could have unintended consequences. 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
+**警告**：如果组织使用 SCIM 来预配用户，则以这种方式加入组织可能会产生意想不到的后果。 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
 {% endwarning %}
 
-## Managing your role with the enterprise settings
+## 使用企业设置管理您的角色
 
-You can join an organization owned by your enterprise and manage your role within the organization, directly from the settings for your enterprise account.
+您可以加入企业拥有的组织，并直接从企业帐户的设置中管理您在组织中的角色。
 
-If an organization enforces SAML single sign-on (SSO), you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP). Then, you can manage your role in your enterprise settings. For more information, see "[Joining an organization that enforces SAML SSO](#joining-an-organization-that-enforces-saml-sso)."
+如果组织强制实施 SAML 单点登录 (SSO)，则无法使用企业设置加入组织。 相反，您必须使用该组织的身份提供程序 (IdP) 加入组织。 然后，您可以在企业设置中管理您的角色。 更多信息请参阅“[加入强制实施 SAML SSO 的组织](#joining-an-organization-that-enforces-saml-sso)”。
 
 {% data reusables.enterprise-accounts.access-enterprise %}
-1. On the **Organizations** tab, to the right of the organization you want to manage your role in, select the {% octicon "gear" aria-label="The gear icon" %} dropdown menu and click the action you want to take.
+1. 在 **Organizations（组织）**选项卡上，在您要在其中管理角色的组织右侧，选择 {% octicon "gear" aria-label="The gear icon" %} 下拉菜单，然后单击要执行的操作。
 
-   ![Screenshot of the dropdown menu for the gear icon for an organization](/assets/images/help/business-accounts/change-role-in-org.png)
+   ![组织的齿轮图标下拉菜单的屏幕截图](/assets/images/help/business-accounts/change-role-in-org.png)
 
-## Joining an organization that enforces SAML SSO
+## 加入强制实施 SAML SSO 的组织
 
-If an organization enforces SAML SSO, you cannot use the enterprise settings to join the organization. Instead, you must join the organization using that organization's identity provider (IdP).
+如果组织强制实施 SAML SSO，则无法使用企业设置加入组织。 相反，您必须使用该组织的身份提供程序 (IdP) 加入组织。
 
-1. You must be assigned access in your IdP to the application for {% data variables.product.prodname_ghe_cloud %} that is used by the organization. If you're unable to configure your IdP yourself, contact your IdP administrator.
-1. Authenticate to the organization using SAML SSO.
+1. 您必须在 IdP 中为组织使用的 {% data variables.product.prodname_ghe_cloud %} 的应用程序分配访问权限。 如果您无法自行配置 IdP，请联系您的 IdP 管理员。
+1. 使用 SAML SSO 向组织进行身份验证。
 
-   - If the organization uses SCIM, accept the organization invitation that will be generated by the SCIM integration.
-   - If the organization does not use SCIM, visit the following URL, replacing ORGANIZATION with the name of the organization, then follow the prompts to authenticate.
+   - 如果组织使用 SCIM，请接受将由 SCIM 集成生成的组织邀请。
+   - 如果组织不使用 SCIM，请访问以下 URL，将 ORGANIZATION 替换为组织的名称，然后按照提示进行身份验证。
 
     `https://github.com/orgs/ORGANIZATION/sso`
 
-After you've joined the organization, you can use the enterprise settings to manage your role in the organization, such as becoming an organization owner. For more information, see "[Managing your role with the enterprise settings](#managing-your-role-with-the-enterprise-settings)."
+加入组织后，您可以使用企业设置来管理您在组织中的角色，例如成为组织所有者。 更多信息请参阅“[使用企业设置管理您的角色](#managing-your-role-with-the-enterprise-settings)。。
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
index eafc31b2b4..cf1c843c0e 100644
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
+++ b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md
@@ -1,6 +1,6 @@
 ---
-title: Restoring a deleted organization
-intro: 'You can partially restore an organization that was previously deleted on {% data variables.product.product_location %}.'
+title: 恢复已删除的组织
+intro: '您可以部分恢复以前在 {% data variables.product.product_location %} 上删除的组织。'
 versions:
   ghes: '*'
 type: how_to
@@ -8,46 +8,46 @@ topics:
   - Administrator
   - Enterprise
   - Organizations
-shortTitle: Restore organization
+shortTitle: 恢复组织
 permissions: 'Site administers can restore an organization on {% data variables.product.product_name %}.'
 ---
 
-## About organization restoration
+## 关于组织恢复
 
-You can use the site admin dashboard to restore an organization that was previously deleted on {% data variables.product.product_location %}, as long as the audit log Elasticsearch indices contain the data for the `org.delete` event.
+您可以使用站点管理仪表板来恢复以前在 {% data variables.product.product_location %} 上删除的组织，只要审核日志 Elasticsearch 索引包含 `org.delete` 事件的数据即可。
 
-Immediately after you restore an organization, the organization will not be exactly the same as it was prior to the deletion. You'll have to manually restore any repositories that were owned by the organization. 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。
+恢复组织后，组织与删除之前不完全相同。 您必须手动恢复组织拥有的所有存储库。 更多信息请参阅“[恢复删除的仓库](/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository)”。
 
-You can also use the audit log to help you manually re-add teams and organization members. For more information, see "[Restoring members and teams](#restoring-members-and-teams)."
+您还可以使用审核日志来帮助您手动重新添加团队和组织成员。 更多信息请参阅“[恢复成员和团队](#restoring-members-and-teams)”。
 
-## Restoring an organization
+## 恢复组织
 
 {% data reusables.enterprise_site_admin_settings.access-settings %}
-1. Under "Search users, organizations, enterprises, teams, repositories, gists, and applications", search for the organization.
+1. 在“Search users, organizations, enterprises, teams, repositories, gists, and applications（搜索用户、组织、企业、团队、存储库、要点和应用程序）”下，搜索组织。
 
-  ![Screenshot of the search field and Search button](/assets/images/enterprise/stafftools/search-field.png)
+  ![搜索字段和“搜索”按钮的屏幕截图](/assets/images/enterprise/stafftools/search-field.png)
 
-1. Under "Deleted accounts", to the right of the organization you want to restore, select the {% octicon "kebab-horizontal" aria-label="The edit icon" %} dropdown menu, then click **Recreate**.
+1. 在“Deleted accounts（已删除的帐户）”下要恢复的组织右侧，选择 {% octicon "kebab-horizontal" aria-label="The edit icon" %} 下拉菜单，然后单击 **Recreate（重新创建）**。
 
-   ![Screenshot of the dropdown menu for a deleted organization](/assets/images/enterprise/stafftools/recreate-organization.png)
+   ![已删除组织的下拉菜单屏幕截图](/assets/images/enterprise/stafftools/recreate-organization.png)
 
-## Restoring members and teams
+## 恢复成员和团队
 
-You can use the audit log to find a list of the previous members and teams of the organization, then recreate them manually. For more information about using the audit log, see "[Auditing users across your enterprise](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)."
+您可以使用审核日志查找组织中以前的成员和团队的列表，然后手动重新创建它们。 有关使用审核日志的详细信息，请参阅“[审核企业中的用户](/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise)”。
 
-In all the search phrases below, replace ORGANIZATION with the name of the organization and TEAM with the name of the team.
+在下面的所有搜索短语中，将 ORGANIZATION 替换为组织的名称，将 TEAM 替换为团队的名称。
 
-### Restoring organization members
+### 恢复组织成员
 
-1. To find all users who were added to and removed from the organization, search the audit log for `action:org.add_member org:ORGANIZATION` and `action:org.remove_member org:ORGANIZATION`.
-1. Manually add to the organization each user that should still be a member. For more information, see "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)."
+1. 若要查找在组织中添加和删除的所有用户，请在审核日志中搜索 `action:org.add_member org:ORGANIZATION` 和 `action:org.remove_member org:ORGANIZATION`。
+1. 手动将仍应是成员的每个用户添加到组织中。 更多信息请参阅“[向组织添加人员](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)”。
 
-### Restoring teams
+### 恢复团队
 
-1. To find each team name, search the audit log for `action:team.create org:ORGANIZATION`.
-1. Manually recreate the team. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
-1. To find the members that have been added to each team, search for `action:team.add_member team:"ORGANIZATION/TEAM"`.
-1. Manually re-add the team members. For more information, see "[Adding organization members to a team](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)."
-1. To find the repositories that the team was granted access to, search for `action:team.add_repository team:"ORGANIZATION/TEAM"`.
-1. To find the access level that the team was granted for each repository, search for `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`.
-1. Manually give the team access again. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+1. 若要查找每个团队名称，请在审核日志中搜索 `action:team.create org:ORGANIZATION`。
+1. 手动重新创建团队。 For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+1. 要查找已添加到每个团队的成员，请搜索 `action:team.add_member team:"ORGANIZATION/TEAM"`。
+1. 手动重新添加团队成员。 更多信息请参阅“[将组织成员添加到团队](/organizations/organizing-members-into-teams/adding-organization-members-to-a-team)”。
+1. 要查找团队被授予访问权限的存储库，请搜索 `action:team.add_repository team:"ORGANIZATION/TEAM"`。
+1. 要查找团队为每个存储库授予的访问权限级别，请搜索 `action:team.update_repository_permission team:"ORGANIZATION/TEAM"`。
+1. 再次手动授予团队访问权限。 更多信息请参阅“[管理团队的组织仓库访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。
diff --git a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
deleted file mode 100644
index 21b8cf9e6b..0000000000
--- a/translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise.md
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: 查看企业中组织的审核日志
-intro: 企业所有者可以在其审核日志中查看企业帐户拥有的所有组织的汇总操作。
-redirect_from:
-  - /github/setting-up-and-managing-your-enterprise/managing-organizations-in-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
-  - /articles/viewing-the-audit-logs-for-organizations-in-your-business-account
-  - /articles/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
-  - /github/setting-up-and-managing-your-enterprise-account/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
-  - /github/setting-up-and-managing-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise-account
-versions:
-  ghec: '*'
-type: how_to
-topics:
-  - Auditing
-  - Enterprise
-  - Logging
-  - Organizations
-shortTitle: 查看组织审核日志
----
-
-每个审核日志条目都显示有关事件的适用信息，例如：
-
-- 可在其中执行操作的组织
-- 执行操作的用户
-- 执行操作的仓库
-- 执行的操作内容
-- 发生操作的国家/地区
-- 操作发生的日期和时间
-
-您可以在审核日志中搜索特定事件并导出审核日志数据。 有关搜索审核日志和特定组织事件的更多信息，请参阅“[审查组织的审核日志](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization)”。
-
-您还可以将审核和 Git 事件数据从 {% data variables.product.prodname_dotcom %} 流式传输到外部数据管理系统。 更多信息请参阅“[流式传输企业帐户中组织的审核日志](/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account)”。
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.audit-log-tab %}
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
index 55647e6517..072f5948ec 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/auditing-users-across-your-enterprise.md
@@ -81,7 +81,7 @@ shortTitle: 审计用户
 
 ### 基于执行的操作搜索
 
-`action` 限定符可搜索特定事件（按类别组织）。 有关与这些类别相关的事件的信息，请参阅“[审核的操作](/admin/user-management/audited-actions)”。
+`action` 限定符可搜索特定事件（按类别组织）。 有关与这些类别相关的事件的信息，请参阅“[审核企业的日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)”。
 
 | 类别名称   | 描述                   |
 | ------ | -------------------- |
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
index 9614cfa9b6..b920fdca7a 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise.md
@@ -72,7 +72,7 @@ topics:
 
 如果消息中包含 Markdown 复选框，则用户必须选中所有复选框才能忽略消息。 例如，如果您在必读消息中包含服务条款，您可以要求每个用户选中复选框以确认他们阅读了这些条款。
 
-每次用户看到必读消息时，都会创建审核日志事件。 该事件包括用户看到的消息的版本。 更多信息请参阅“[已审核操作](/admin/user-management/audited-actions)”。
+每次用户看到必读消息时，都会创建审核日志事件。 该事件包括用户看到的消息的版本。 更多信息请参阅“[审核企业的日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)”。
 
 {% note %}
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
index 409fef9df1..58a84e719c 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
@@ -19,7 +19,7 @@ shortTitle: 模拟用户
 
 对于每个模拟会话，您需要提供模拟的原因。 会话限制为一小时，您将拥有与被模拟用户相同的访问权限。
 
-在模拟会话期间执行的操作将记录为企业审核日志以及模拟用户的安全日志中的事件。 当模拟会话开始时，被模拟的人员将收到电子邮件通知。 更多信息请参阅“[已审核的操作](/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions)”和“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
+在模拟会话期间执行的操作将记录为企业审核日志以及模拟用户的安全日志中的事件。 当模拟会话开始时，被模拟的人员将收到电子邮件通知。 更多信息请参阅“[审核企业的日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)”和“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
 
 ## 模拟用户
 
diff --git a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
index baac07f7a4..d880571c2e 100644
--- a/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
+++ b/translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/removing-a-member-from-your-enterprise.md
@@ -1,39 +1,39 @@
 ---
-title: Removing a member from your enterprise
-intro: You can remove a member from all organizations owned by your enterprise.
+title: 从企业中删除成员
+intro: 您可以从企业拥有的所有组织中删除成员。
 permissions: Enterprise owners can remove an enterprise member from the enterprise.
 versions:
   feature: remove-enterprise-members
 type: how_to
 topics:
   - Enterprise
-shortTitle: Remove member
+shortTitle: 删除成员
 ---
 
 {% note %}
 
-**Note:** The ability to remove enterprise members is in beta and subject to change.
+**注意：** 删除企业成员的功能处于测试阶段，可能会发生更改。
 
 {% endnote %}
 
-## About removal of enterprise members
+## 关于删除企业成员
 
-When you remove an enterprise member from your enterprise, the member is removed from all organizations owned by your enterprise.
+从企业中删除企业成员时，该成员将从企业拥有的所有组织中删除。
 
-If the enterprise member you're removing is the last owner of an organization owned by your enterprise, you will become an owner of that organization.
+如果要删除的企业成员是企业拥有的组织的最后一个所有者，您将成为该组织的所有者。
 
-If your enterprise or any of the organizations owned by your enterprise uses an identity provider (IdP) to manage organization membership, the member may be added back to the organization by the IdP. Make sure to also make any necessary changes in your IdP.
+如果您的企业或您的企业拥有的任何组织使用身份提供程序 (IdP) 来管理组织成员身份，则 IdP 可能会将成员添加回组织。 确保还要对 IdP 进行任何必要的更改。
 
-## Removing a member from your enterprise
+## 从企业中删除成员
 
 {% note %}
 
-**Note:** If an enterprise member uses only {% data variables.product.prodname_ghe_server %}, and not {% data variables.product.prodname_ghe_cloud %}, you cannot remove the enterprise member this way.
+**注意：** 如果企业成员仅使用 {% data variables.product.prodname_ghe_server %}，而不使用 {% data variables.product.prodname_ghe_cloud %}，则无法以这种方式删除企业成员。
 
 {% endnote %}
 
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.people-tab %}
-1. To the right of the person you want to remove, select the {% octicon "gear" aria-label="The gear icon" %} dropdown menu and click **Remove from enterprise**.
+1. 在要删除的人员的右侧，选择 {% octicon "gear" aria-label="The gear icon" %} 下拉菜单，然后单击 **Remove from enterprise（从企业中删除）**。
 
-   ![Screenshot of the "Remove from enterprise" option for an enterprise member](/assets/images/help/business-accounts/remove-member.png)
+   ![企业成员的 "从企业中删除" 选项的屏幕截图](/assets/images/help/business-accounts/remove-member.png)
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
deleted file mode 100644
index c672486e81..0000000000
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: 审核日志
-intro: '{% data variables.product.product_name %} 会保留已审计 {% ifversion ghes %} 系统、{% endif %}用户、组织和仓库事件的日志。 日志可用于调试以及内部和外部合规。'
-redirect_from:
-  - /enterprise/admin/articles/audit-logging
-  - /enterprise/admin/installation/audit-logging
-  - /enterprise/admin/user-management/audit-logging
-  - /admin/user-management/audit-logging
-versions:
-  ghes: '*'
-  ghae: '*'
-type: reference
-topics:
-  - Auditing
-  - Enterprise
-  - Logging
-  - Security
----
-
-有关完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。 有关查找特定操作的详细信息，请参阅“[搜索审核日志](/admin/user-management/searching-the-audit-log)”。
-
-## 推送日志
-
-会记录每个 Git 推送操作。 更多信息请参阅“[查看推送日志](/admin/user-management/viewing-push-logs)”。
-
-{% ifversion ghes %}
-## 系统事件
-
-所有审核的系统事件都将记录到 `/var/log/github/audit.log`。 日志每 24 小时自动轮换一次，并会保留七天。
-
-支持包中包含系统日志。 更多信息请参阅“[向 {% data variables.product.prodname_dotcom %} Support 提供数据](/admin/enterprise-support/providing-data-to-github-support)”。
-
-## 支持包
-
-所有审核信息均会记录到任何支持包 `github-logs` 目录的 `audit.log` 文件中。 如果已启用日志转发，您可以将此数据传输到外部 syslog 流使用者，例如 [Splunk](http://www.splunk.com/) 或 [Logstash](http://logstash.net/)。 此日志中的所有条目均使用 `github_audit` 关键词，并且可以通过该关键词进行筛选。 更多信息请参阅“[日志转发](/admin/user-management/log-forwarding)。”
-
-例如，此条目显示已创建的新仓库。
-
-```
-Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
-```
-
-此示例显示提交已推送到仓库。
-
-```
-Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
-```
-{% endif %}
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
deleted file mode 100644
index 49144d07a6..0000000000
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ /dev/null
@@ -1,198 +0,0 @@
----
-title: 审核的操作
-intro: 您可以在审核日志中搜索各种操作。
-miniTocMaxHeadingLevel: 3
-redirect_from:
-  - /enterprise/admin/articles/audited-actions
-  - /enterprise/admin/installation/audited-actions
-  - /enterprise/admin/user-management/audited-actions
-  - /admin/user-management/audited-actions
-versions:
-  ghes: '*'
-  ghae: '*'
-type: reference
-topics:
-  - Auditing
-  - Enterprise
-  - Security
----
-
-## 身份验证
-
-| 操作                                   | 描述                                               |
-| ------------------------------------ | ------------------------------------------------ |
-| `oauth_access.create`                | 已为用户帐户[生成>][generate token] [OAuth 访问令牌][]。      |
-| `oauth_access.destroy`               | 已从用户帐户中删除 [OAuth 访问令牌][]。                        |
-| `oauth_application.destroy`          | 已从用户或组织帐户中删除 [OAuth 应用程序][]。                     |
-| `oauth_application.reset_secret`     | 已重置 [OAuth 应用程序][]的密钥。                           |
-| `oauth_application.transfer`         | 已将 [OAuth 应用程序][]从一个用户或组织帐户传送到另一个用户或组织帐户。        |
-| `public_key.create`                  | 已将 SSH 密钥[添加][add key]到用户帐户中，或者已将[部署密钥][]添加到仓库中。 |
-| `public_key.delete`                  | 已从用户帐户中移除 SSH 密钥，或已从仓库中移除[部署密钥][]。               |
-| `public_key.update`                  | 已更新用户帐户的 SSH 密钥或仓库的[部署密钥][]。{% ifversion ghes %}
-| `two_factor_authentication.enabled`  | 已为用户帐户启用[双重身份验证][2fa]。                           |
-| `two_factor_authentication.disabled` | 已为用户帐户禁用[双重身份验证][2fa]。{% endif %}
-
-{% ifversion ghes %}
-## {% data variables.product.prodname_actions %}
-
-{% data reusables.actions.actions-audit-events-for-enterprise %}
-
-{% endif %}
-
-## 挂钩
-
-| 操作                    | 描述          |
-| --------------------- | ----------- |
-| `hook.create`         | 已向仓库添加新挂钩。  |
-| `hook.config_changed` | 已更改挂钩的配置。   |
-| `hook.destroy`        | 已删除挂钩。      |
-| `hook.events_changed` | 已更改挂钩的配置事件。 |
-
-## 企业配置设置
-
-| 操作                                                      | 描述                                                                                                                                                                                                                                                      |
-| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes or ghae %}
-| `business.advanced_security_policy_update`              | 站点管理员创建、更新或删除 {% data variables.product.prodname_GH_advanced_security %} 策略。 更多信息请参阅“[在企业中执行 {% data variables.product.prodname_advanced_security %} 的策略](/admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise)”。{% endif %}
-| `business.clear_members_can_create_repos`               | 站点管理员取消了对在企业中的组织中创建仓库的限制。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% ifversion ghes > 3.1 %}
-| `business.referrer_override_enable`                     | 站点管理员可以改写推荐策略。 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。                                                                                                              |
-| `business.referrer_override_disable`                    | 站点管理员可以禁用推荐策略。 更多信息请参阅“[配置企业的推荐策略](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)”。{% endif %}
-| `business.update_member_repository_creation_permission` | 站点管理员限制在企业中的组织中创建仓库。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#setting-a-policy-for-repository-creation)”。{% ifversion ghes %}
-| `enterprise.config.lock_anonymous_git_access`           | 站点管理员锁定匿名 Git 读取权限，以防止仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。                                                        |
-| `enterprise.config.unlock_anonymous_git_access`         | 站点管理员解锁匿名 Git 读取权限，以允许仓库管理员更改该企业中仓库的现有匿名 Git 读取权限设置。 更多信息请参阅“[在企业中实施仓库管理策略](/admin/policies/enforcing-repository-management-policies-in-your-enterprise#configuring-anonymous-git-read-access)”。{% endif %}
-
-{% ifversion ghae %}
-
-## IP 允许列表
-
-|                                         名称 | 描述                                                                    |
-| ------------------------------------------:| --------------------------------------------------------------------- |
-|               `ip_allow_list_entry.create` | IP 地址已添加到 IP 允许列表中。                                                   |
-|               `ip_allow_list_entry.update` | IP 地址或描述已更改。                                                          |
-|              `ip_allow_list_entry.destroy` | IP 地址已从 IP 允许列表中删除。                                                   |
-|                     `ip_allow_list.enable` | IP 允许列表已启用。                                                           |
-|  `ip_allow_list.enable_for_installed_apps` | 已为安装的 {% data variables.product.prodname_github_apps %} 启用 IP 允许列表。 |
-|                    `ip_allow_list.disable` | IP 允许列表已禁用。                                                           |
-| `ip_allow_list.disable_for_installed_apps` | 已为安装的 {% data variables.product.prodname_github_apps %} 禁用 IP 允许列表。 |
-
-{% endif %}
-
-## 议题
-
-| 操作                     | 描述                                                                                  |
-| ---------------------- | ----------------------------------------------------------------------------------- |
-| `issue.update`         | 问题的正文文本（初始注释）已更改。                                                                   |
-| `issue_comment.update` | 已更改问题的正文文本（初始注释）。                                                                   |
-| `issue.destroy`        | 已从仓库中删除问题。 更多信息请参阅“[删除议题](/github/managing-your-work-on-github/deleting-an-issue)”。 |
-
-## 组织
-
-| 操作                 | 描述                                                                                                                                           |
-| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
-| `org.async_delete` | 用户发起了删除组织的后台作业。                                                                                                                              |
-| `org.delete`       | 用户发起的背景作业删除了组织。{% ifversion not ghae %}
-| `org.transform`    | 已将用户帐户转换为组织。 更多信息请参阅“[将用户转换为组织](/github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization)”{% endif %}
-
-## 拉取请求
-
-| 操作 | 描述n | | :- | :- |{% ifversion ghes > 3.1 or ghae %} | `pull_request.create` | 创建了拉取请求。 更多信息请参阅“[创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)”。 | | `pull_request.close` | 关闭了拉取请求而未合并。 更多信息请参阅“[关闭拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request)”。 | | `pull_request.reopen` | 重新打开了之前关闭的拉取请求。 | | `pull_request.merge` | 合并了拉取请求。 更多信息请参阅“[合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request)”。 | | `pull_request.indirect_merge` | 考虑合并拉取请求，因为拉取请求的提交已合并到目标分支。 | | `pull_request.ready_for_review` | 拉取请求标记为可供审查。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review)”。 | | `pull_request.converted_to_draft` | 拉取请求转换为草稿。 更多信息请参阅“[更改拉取请求的阶段](/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft)”。 | | `pull_request.create_review_request` | 请求对拉取请求的审查。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request.remove_review_request` | 从拉取请求删除审查请求。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review.submit` | 为拉取请求提交审查。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review.discute` | 撤销对拉取请求的审查。 更多信息请参阅“[忽略拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/dismissing-a-pull-request-review)”。 | | `pull_request_review.delete` | 删除对拉取请求的审查。 | | `pull_request_review_comment.create` | 审查评论添加到拉取请求。 更多信息请参阅“[关于拉取请求审查](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews)”。 | | `pull_request_review_comment.update` | 更改拉取请求上的审查评论。 |{% endif %} | `pull_request_review_comment.delete` | 删除了拉取请求上的审查评论。 |
-
-## 受保护分支
-
-| 操作                                                                 | 描述                                                      |
-| ------------------------------------------------------------------ | ------------------------------------------------------- |
-| `protected_branch.create`                                          | 已在分支上启用分支保护。                                            |
-| `protected_branch.destroy`                                         | 已在分支上禁用分支保护。                                            |
-| `protected_branch.update_admin_enforced`                           | 已为仓库管理员强制执行分支保护。                                        |
-| `protected_branch.update_require_code_owner_review`                | 已在分支上更新必需代码所有者审查的强制执行。                                  |
-| `protected_branch.dismiss_stale_reviews`                           | 已在分支上更新忽略旧拉取请求的强制执行。                                    |
-| `protected_branch.update_signature_requirement_enforcement_level`  | 已在分支上更新必需提交签名的强制执行。                                     |
-| `protected_branch.update_pull_request_reviews_enforcement_level`   | 已在分支上更新必需拉取请求审查的强制执行。 可以是 `0`（已停用）、`1`（非管理员）`2`（所有人）之一。 |
-| `protected_branch.update_required_status_checks_enforcement_level` | 已在分支上更新必需状态检查的强制执行。                                     |
-| `protected_branch.rejected_ref_update`                             | 分支更新尝试被拒。                                               |
-| `protected_branch.policy_override`                                 | 分支保护要求被仓库管理员覆盖。                                         |
-
-## 仓库
-
-| 操作                                         | 描述                                                                                                                                                                                                        |
-| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `repo.access`                              | 仓库的可见性已更改为私有{% ifversion ghes %}、公共{% endif %} 或内部。                                                                                                                                                       |
-| `repo.archived`                            | 已存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。                                                  |
-| `repo.add_member`                          | 已向仓库添加协作者。                                                                                                                                                                                                |
-| `repo.config`                              | 站点管理员已阻止强制推送。 更多信息请参阅“[阻止对仓库进行强制推送](/enterprise/{{ currentVersion }}/admin/guides/developer-workflow/blocking-force-pushes-to-a-repository/)”。                                                            |
-| `repo.create`                              | 已创建仓库。                                                                                                                                                                                                    |
-| `repo.destroy`                             | 已删除仓库。                                                                                                                                                                                                    |
-| `repo.remove_member`                       | 已从仓库中移除协作者。                                                                                                                                                                                               |
-| `repo.rename`                              | 已重命名仓库。                                                                                                                                                                                                   |
-| `repo.transfer`                            | 用户已接受接收传输仓库的请求。                                                                                                                                                                                           |
-| `repo.transfer_start`                      | 用户已发送向另一用户或组织传输仓库的请求。                                                                                                                                                                                     |
-| `repo.unarchived`                          | 已取消存档仓库。 更多信息请参阅“[存档 {% data variables.product.prodname_dotcom %} 仓库](/github/creating-cloning-and-archiving-repositories/archiving-a-github-repository)”。{% ifversion ghes %}
-| `repo.config.disable_anonymous_git_access` | 已为仓库禁用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”                                                       |
-| `repo.config.enable_anonymous_git_access`  | 已为仓库启用匿名 Git 读取权限。 更多信息请参阅“[为仓库启用匿名 Git 读取权限](/enterprise/{{ currentVersion }}/user/articles/enabling-anonymous-git-read-access-for-a-repository)。”                                                       |
-| `repo.config.lock_anonymous_git_access`    | 已锁定仓库的匿名 Git 读取权限设置，阻止仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。            |
-| `repo.config.unlock_anonymous_git_access`  | 已解锁仓库的匿名 Git 读取权限设置，允许仓库管理员更改（启用或禁用）此设置。 更多信息请参阅“[阻止用户更改匿名 Git 读取权限](/enterprise/{{ currentVersion }}/admin/guides/user-management/preventing-users-from-changing-anonymous-git-read-access)”。{% endif %}
-
-{% if secret-scanning-audit-log-custom-patterns %}
-## 秘密扫描
-
-| 操作 | 描述                                                                                                                                                                                                                                                                                                                                                  |
-| -- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|    | `business_secret_scanning_custom_pattern.create` | Triggered when an enterprise-level custom pattern is published for secret scanning. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning#defining-a-custom-pattern-for-an-enterprise-account)." |
-|    | `business_secret_scanning_custom_pattern.update` | Triggered when changes to an enterprise-level custom pattern are saved for secret scanning.                                                                                                                                                                                                      |
-|    | `business_secret_scanning_custom_pattern.delete` | Triggered when an enterprise-level custom pattern is removed from secret scanning.                                                                                                                                                                                                               |
-{% endif %}
-
-## 站点管理员工具
-
-| 操作                      | 描述                                                                    |
-| ----------------------- | --------------------------------------------------------------------- |
-| `staff.disable_repo`    | 站点管理员已禁用对仓库及其所有复刻的访问。                                                 |
-| `staff.enable_repo`     | 站点管理员重新启用了对仓库及其所有复刻的访问权限。{% ifversion ghae or ghes > 3.2 %}
-| `staff.exit_fake_login` | 站点管理员在 {% data variables.product.product_name %} 上结束了模拟会话。            |
-| `staff.fake_login`      | 站点管理员以另一用户的身份登录 {% data variables.product.product_name %}。{% endif %}
-| `staff.repo_unlock`     | 站点管理员已解锁（临时获得完全访问权限）用户的一个私有仓库。                                        |
-| `staff.unlock`          | 站点管理员已解锁（临时获得完全访问权限）用户的所有私有仓库。                                        |
-
-## 团队
-
-| 操作                        | 描述                                          |
-| ------------------------- | ------------------------------------------- |
-| `team.create`             | 已向团队添加用户帐户或仓库。                              |
-| `team.delete`             | 用户帐户或仓库已从团队中删除。{% ifversion ghes or ghae %}
-| `team.demote_maintainer`  | 用户从团队维护员降级为团队成员。{% endif %}
-| `team.destroy`            | 团队被删除。{% ifversion ghes or ghae %}
-| `team.promote_maintainer` | 用户从团队成员晋升为团队维护员。{% endif %}
-
-## 用户
-
-| 操作                              | 描述                                                                                                            |
-| ------------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| `user.add_email`                | 已向用户帐户添加电子邮件地址。                                                                                               |
-| `user.async_delete`             | 异步作业已开始破坏用户帐户，最终触发 `user.delete`。{% ifversion ghes %}
-| `user.change_password`          | 用户已更改其密码。{% endif %}
-| `user.create`                   | 已创建新的用户帐户。                                                                                                    |
-| `user.delete`                   | 已通过异步作业销毁用户帐户。                                                                                                |
-| `user.demote`                   | 已将站点管理员降级为普通用户帐户。                                                                                             |
-| `user.destroy`                  | 用户已删除其帐户，触发 `user.async_delete`。{% ifversion ghes %}
-| `user.failed_login`             | 用户尝试登录时使用的用户名、密码或双重身份验证码不正确。                                                                                  |
-| `user.forgot_password`          | 用户通过登录页面请求了密码重置。{% endif %}
-| `user.login`                    | 用户已登录。{% ifversion ghes or ghae %}
-| `user.mandatory_message_viewed` | 用户查看必读消息（详情请参阅“[自定义用户消息](/admin/user-management/customizing-user-messages-for-your-enterprise)”）| {% endif %}
-| `user.promote`                  | 已将普通用户帐户升级为站点管理员。                                                                                             |
-| `user.remove_email`             | 已从用户帐户中移除电子邮件地址。                                                                                              |
-| `user.rename`                   | 已更改用户名。                                                                                                       |
-| `user.suspend`                  | 用户帐户被站点管理员暂停。{% ifversion ghes %}
-| `user.two_factor_requested`     | 已提示用户输入双重身份验证码。{% endif %}
-| `user.unsuspend`                | 站点管理员已取消挂起用户帐户。                                                                                               |
-
-{% ifversion ghes > 3.1 or ghae %}
-## 工作流程
-
-{% data reusables.actions.actions-audit-events-workflow %}
-{% endif %}
-
-  [add key]: /articles/adding-a-new-ssh-key-to-your-github-account
-  [部署密钥]: /guides/managing-deploy-keys/#deploy-keys
-  [generate token]: /articles/creating-an-access-token-for-command-line-use
-  [OAuth 访问令牌]: /developers/apps/authorizing-oauth-apps
-  [OAuth 应用程序]: /guides/basics-of-authentication/#registering-your-app
-  [2fa]: /articles/about-two-factor-authentication
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md
deleted file mode 100644
index c2ce48e205..0000000000
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/index.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: 监控企业中的活动
-intro: 您可以利用企业中的仪表板和日志查看活动。
-redirect_from:
-  - /enterprise/admin/installation/monitoring-activity-on-your-github-enterprise-server-instance
-  - /enterprise/admin/user-management/monitoring-activity-in-your-enterprise
-versions:
-  ghec: '*'
-  ghes: '*'
-  ghae: '*'
-topics:
-  - Enterprise
-children:
-  - /activity-dashboard
-  - /audit-logging
-  - /searching-the-audit-log
-  - /audited-actions
-  - /viewing-push-logs
-  - /log-forwarding
-  - /managing-global-webhooks
-shortTitle: 监控企业
----
-
diff --git a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md b/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
deleted file mode 100644
index 268bc9ffc2..0000000000
--- a/translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/searching-the-audit-log.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: 搜索审核日志
-intro: 站点管理员可以在企业上搜索已审核操作的广泛列表。
-redirect_from:
-  - /enterprise/admin/articles/searching-the-audit-log
-  - /enterprise/admin/installation/searching-the-audit-log
-  - /enterprise/admin/user-management/searching-the-audit-log
-  - /admin/user-management/searching-the-audit-log
-versions:
-  ghes: '*'
-  ghae: '*'
-type: how_to
-topics:
-  - Auditing
-  - Enterprise
-  - Logging
----
-
-## 搜索查询语法
-
-由一个或多个键值对（以 AND/OR 逻辑运算符分隔）构成一个搜索查询。
-
-|              键 | 值                         |
-| --------------:| ------------------------- |
-|     `actor_id` | 发起操作的用户帐户的 ID             |
-|        `actor` | 发起操作的用户帐户的名称              |
-| `oauth_app_id` | 与操作相关联的 OAuth 应用程序的 ID    |
-|       `action` | 已审核操作的名称                  |
-|      `user_id` | 受操作影响的用户的 ID              |
-|           `用户` | 受操作影响的用户的名称               |
-|      `repo_id` | 受操作影响的仓库的 ID（若适用）         |
-|         `repo` | 受操作影响的仓库的名称（若适用）          |
-|     `actor_ip` | 发起操作的 IP 地址               |
-|   `created_at` | 操作发生的时间                   |
-|         `from` | 发起操作的视图                   |
-|         `note` | 事件特定的其他信息（采用纯文本或 JSON 格式） |
-|          `org` | 受操作影响的组织的名称（若适用）          |
-|       `org_id` | 受操作影响的组织的 ID（若适用）         |
-
-例如，要查看自 2017 年初开始影响仓库 `octocat/Spoon-Knife` 的所有操作：
-
-  `repo:"octocat/Spoon-Knife" AND created_at:[2017-01-01 TO *]`
-
-有关操作的完整列表，请参阅“[审核的操作](/admin/user-management/audited-actions)”。
-
-## 搜索审核日志
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.audit-log-tab %}
-4. 输入搜索查询。 ![搜索查询](/assets/images/enterprise/site-admin-settings/search-query.png)
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
index 07df1ce996..64acaa07e5 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md
@@ -15,6 +15,8 @@ shortTitle: 使用 SAML 的 PAT
 
 您可以授权现有的个人访问令牌，或者[创建新的个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)，然后再授权。
 
+{% data reusables.saml.must-authorize-linked-identity %}
+
 {% data reusables.saml.authorized-creds-info %}
 
 {% data reusables.user-settings.access_settings %}
diff --git a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
index 61b2d55b92..e14f97f512 100644
--- a/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md
@@ -15,6 +15,8 @@ shortTitle: 使用 SAML 的 SSH 密钥
 
 您可以授权现有 SSH 密钥，或者创建新 SSH 密钥后再授权。 有关创建新 SSH 密钥的更多信息，请参阅“[生成新的 SSH 密钥并添加到 ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent)”。
 
+{% data reusables.saml.must-authorize-linked-identity %}
+
 {% data reusables.saml.authorized-creds-info %}
 
 {% note %}
diff --git a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
index 722d046642..ab415a2eaa 100644
--- a/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
+++ b/translations/zh-CN/content/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key.md
@@ -97,7 +97,7 @@ shortTitle: 将您的签名密钥告诉 Git
 {% data reusables.gpg.list-keys-with-note %}
 {% data reusables.gpg.copy-gpg-key-id %}
 {% data reusables.gpg.paste-gpg-key-id %}
-1. To add your GPG key to your `.bashrc` startup file, run the following command:
+1. 要将 GPG 密钥添加到您的 `.bashrc` 配置文件中，请运行以下命令：
   ```bash
   $ [ -f ~/.bashrc ] && echo 'export GPG_TTY=$(tty)' >> ~/.bashrc
   ```
diff --git a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
index 6ad4d1d7ce..e5d79677be 100644
--- a/translations/zh-CN/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
+++ b/translations/zh-CN/content/billing/managing-billing-for-your-github-account/one-time-payments-for-customers-in-india.md
@@ -19,48 +19,48 @@ shortTitle: 印度一次性付款
 印度储备银行 (RBI) 的一项新支付法规最近生效。 该法规对经常性在线交易提出了额外的要求，并阻止印度一些 {% data variables.product.company_short %} 客户进行定期付款。 对 {% data variables.product.product_name %} 上的任何定期交易使用印度颁布的付款方式的客户，可能会发现他们的付款被银行或发卡机构拒绝。 更多信息请参阅 [RBI 的新闻稿](https://www.rbi.org.in/Scripts/BS_PressReleaseDisplay.aspx?prid=51353)。
 
 该法规适用于所有经常性交易，包括：
-- {% data variables.product.prodname_dotcom %} plan subscriptions (Pro, Team, Enterprise)
-- {% data variables.product.prodname_marketplace %} purchases
-- {% data variables.product.prodname_sponsors %} transactions
-- Git Large File Storage purchases
-- {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %}, and {% data variables.product.prodname_codespaces %} consumption
+- {% data variables.product.prodname_dotcom %} 计划订阅（专业版、团队版、企业版）
+- {% data variables.product.prodname_marketplace %} 购买
+- {% data variables.product.prodname_sponsors %} 交易
+- Git Large File Storage 购买
+- {% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_codespaces %} 的使用
 
-In order to minimize disruption, recurring payments for our affected customers were paused on October 29th, 2021. Paid features and services have remained available to customers impacted by the RBI regulation.
+为了尽量减少中断，受影响客户的定期付款已于 2021 年 10 月 29 日暂停。 受 RBI 法规影响的客户仍然可以使用付费功能和服务。
 
-## About one-time payments on {% data variables.product.company_short %}
+## 关于 {% data variables.product.company_short %} 的一次性付款
 
-As we work with our payment gateway provider to meet the new requirements, we are providing a temporary one-time payment option for impacted customers in India. From February 15th 2022, {% data variables.product.company_short %} customers in India who have been affected by the new RBI regulation will be able to make one-time payments on their regular billing cycle cadence.
+随着我们与支付网关提供商合作以满足新要求，我们为印度受影响的客户提供临时的一次性付款选项。 从 2022 年 2 月 15 日起，受新 RBI 法规影响的印度 {% data variables.product.company_short %} 客户将能够按照其常规计费周期节奏进行一次性付款。
 
-### For customers on monthly billing
+### 对于按月计费的客户
 
-Customers on monthly billing plans will be able to make a one-time payment on the same day their billing cycle usually renews. For example, if you're usually billed on the 7th of each month, you will now be able to make a one-time payment from your account from the 7th of each month. Your first one-time payment will also include any accrued usage from October 2021 onwards.
+使用月度计费计划的客户将能够在其计费周期通常续订的同一天进行一次性付款。 例如，如果您通常在每月 7 日向您收费，那么现在可以从每月 7 日开始用您的帐户一次性付款。 您的首次一次性付款还将包括 2021 年 10 月起的任何累积使用量。
 
-If you are currently billed monthly, and would like to switch to yearly billing, you can reduce the frequency of your one-time payments. For more information, see "[Changing the duration of your billing cycle](/en/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)."
+如果您目前按月计费，并希望切换到按年计费，则可以减少一次性付款的频率。 更多信息请参阅“[更改计费周期的持续时间](/en/billing/managing-your-github-billing-settings/changing-the-duration-of-your-billing-cycle)”。
 
-### For customers on yearly billing
+### 对于按年计费的客户
 
-If you are billed yearly, and your renewal date was between October 1st, 2021 and February 14th, 2022, you will be able to make a one-time payment for your annual subscriptions from February 15th. This initial payment will include the prorated outstanding cost of your subscription for the period since your previous billing cycle ended.
+如果您按年计费，并且您的续订日期在 2021 年 10 月 1 日至 2022 年 2 月 14 日之间，则从 2 月 15 日起，您可以一次性支付年度订阅费用。 此初始付款将包括自上一个结算周期结束以来按比例计算的订阅未付费用。
 
-If your billing cycle is due to renew after February 15th, we will attempt to take the recurring payment. If the payment attempt is declined, you will then be able to make a one-time payment through your account's billing page.
+如果您的结算周期将在 2 月 15 日之后续订，我们将尝试定期付款。 如果付款尝试被拒绝，您将能够通过帐户的结算页面进行一次性付款。
 
-In the meantime, we are actively working with our payment partners to restore recurring payments for impacted customers. For more information or questions, you can contact [GitHub Support](https://support.github.com/contact).
+与此同时，我们正在积极与我们的支付合作伙伴合作，为受影响的客户恢复经常性付款。 如需更多信息或有疑问，您可以联系 [GitHub 支持](https://support.github.com/contact)。
 
-### Impact to {% data variables.product.prodname_sponsors %}
+### 对 {% data variables.product.prodname_sponsors %} 的影响
 
-Existing sponsorships will remain in place during this period and maintainers will continue to be paid out as expected. Payments for the accrued sponsorship amounts from the funding account will be collected at the same time as other accrued charges.
+在此期间，现有的赞助将继续存在，维护者将继续按预期获得报酬。 从赞助帐户中支付的应计赞助金额将与其他应计费用同时收取。
 
-## Making a one-time payment for a GitHub subscription
+## 为 GitHub 订阅进行一次性付款
 
 {% note %}
 
-**Note**: Affected customers will receive an email notification with a link to their billing settings when payment is due. Two further reminder emails will be sent 7 and 14 days later if payment has not been made. After 14 days, paid features and services will be locked until payment is made.
+**注意**：付款到期时，受影响的客户将收到一封电子邮件通知，其中包含指向其结算设置的链接。 如果未付款，将在 7 天和 14 天后再发送两封提醒电子邮件。 14 天后，付费功能和服务将被锁定，直到付款为止。
 
 {% endnote %}
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.billing_plans %}
-3. At the top of the page, click **Pay now**. ![One-time payment pay now button](/assets/images/help/billing/pay-now-button.png)
-4. Review your billing and payment information. If you need to make an edit, click **Edit** next to the relevant section. Otherwise, click **Submit payment**. ![One-time payment summary](/assets/images/help/billing/payment-summary.png)
-5. Optionally, if you clicked **Edit**, make any necessary changes, and then click **Submit payment**. ![One-time payment edit summary](/assets/images/help/billing/payment-summary-edit.png)
-6. Once payment for the current billing cycle has been successfully made, the **Pay now** button on your "Billing & plans" page will be disabled until your next payment is due. ![One-time payment pay now button disabled](/assets/images/help/billing/pay-now-button-disabled.png)
+3. 在页面顶部，单击 **Pay now（立即付款）**。 ![一次性付款立即付款按钮](/assets/images/help/billing/pay-now-button.png)
+4. 查看您的帐单和付款信息。 如果您需要进行编辑，请点击相关部分旁边的 **Edit（编辑）**。 否则，请单击 **Submit payment（提交付款）**。 ![一次性付款摘要](/assets/images/help/billing/payment-summary.png)
+5. （可选）如果您单击了 **Edit（编辑）**，请进行任何必要的更改，然后单击 **Submit payment（提交付款）**。 ![一次性付款编辑摘要](/assets/images/help/billing/payment-summary-edit.png)
+6. 成功支付当前结算周期的款项后，“Billing & plans（结算和计划）”页面上的 **Pay now（立即付款）**按钮将被停用，直到您的下一次付款到期。 ![一次性付款立即付款按钮已禁用](/assets/images/help/billing/pay-now-button-disabled.png)
   
diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
index 0381f0cad8..a87f03a201 100644
--- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
+++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md
@@ -96,7 +96,7 @@ By default, only alerts with the severity level of `Error`{% ifversion fpt or gh
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 1. Under "Code scanning", to the right of "Check Failure", use the drop-down menu to select the level of severity you would like to cause a pull request check failure. 
 {% ifversion fpt or ghes > 3.1  or ghae or ghec %}
 ![Check failure setting](/assets/images/help/repository/code-scanning-check-failure-setting.png)
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
index 6cc5ca642c..5d5ad5a63f 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md
@@ -68,7 +68,7 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
   {% ifversion fpt or ghec %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png){% else %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %}
 
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
index 195a53404f..2f839c762d 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md
@@ -49,7 +49,7 @@ shortTitle: Dependabot 版本更新
 如果您启用了安全更新，有时会看到额外的安全更新拉取请求。 这些由默认分支上依赖项的 {% data variables.product.prodname_dependabot %} 警报所触发。 {% data variables.product.prodname_dependabot %} 自动提出拉取请求以更新有漏洞的依赖项。
 
 ## 支持的仓库和生态系统
-<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported repositories or ecosystems. -->
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
 
 您可以为包含其中一个受支持包管理器的依赖项清单或锁定文件的仓库配置版本更新。 对于某些软件包管理器，您也可以配置依赖项的供应。 For more information, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#vendor)."
 {% note %}
diff --git a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
index c5dc9fef09..ccd397a29f 100644
--- a/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
+++ b/translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md
@@ -33,35 +33,37 @@ shortTitle: Configure dependabot.yml
 
 下次安全警报触发安全更新的拉取请求时将使用所有同时影响安全更新的选项。  更多信息请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)。”
 
-*dependabot.yml* 文件有两个必需的顶级密钥：`version` 和 `updates`。 您可以选择性包括一个顶级`注册表`键。 该文件必须以 `version: 2` 开头。
+*dependabot.yml* 文件有两个必需的顶级密钥：`version` 和 `updates`。 You can, optionally, include a top-level `registries` key{% ifversion fpt or ghec or ghes > 3.4 %} and/or a `enable-beta-ecosystems` key{% endif %}. 该文件必须以 `version: 2` 开头。
 
 ## 更新的配置选项
 
 顶级 `updates` 密钥是必需的。 您使用它来配置 {% data variables.product.prodname_dependabot %} 如何更新版本或项目的依赖项。 每个条目都为特定的包管理器配置更新设置。 您可以使用以下选项。
 
-| 选项                                                                         |  必选   | 描述                                                          |
-|:-------------------------------------------------------------------------- |:-----:|:----------------------------------------------------------- |
-| [`package-ecosystem`](#package-ecosystem)                                  | **X** | 要使用的包管理器                                                    |
-| [`目录`](#directory)                                                         | **X** | 包清单位置                                                       |
-| [`schedule.interval`](#scheduleinterval)                                   | **X** | 检查更新的频率                                                     |
-| [`allow`](#allow)                                                          |       | 自定义允许的更新                                                    |
-| [`assignees`](#assignees)                                                  |       | 要在拉取请求上设置的受让人                                               |
-| [`commit-message`](#commit-message)                                        |       | 提交消息首选项                                                     |
-| [`ignore`](#ignore)                                                        |       | 忽略某些依赖项或版本                                                  |
-| [`insecure-external-code-execution`](#insecure-external-code-execution)    |       | 允许或拒绝清单文件中的代码执行                                             |
-| [`labels`](#labels)                                                        |       | 要在拉取请求上设置的标签                                                |
-| [`里程碑`](#milestone)                                                        |       | 要在拉取请求上设置的里程碑                                               |
-| [`open-pull-requests-limit`](#open-pull-requests-limit)                    |       | 限制对版本更新打开的拉取请求数                                             |
-| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) |       | 更改拉取请求分支名称的分隔符                                              |
-| [`rebase-strategy`](#rebase-strategy)                                      |       | 禁用自动变基                                                      |
-| [`registries`](#registries)                                                |       | {% data variables.product.prodname_dependabot %} 可以访问的私有注册表 |
-| [`reviewers`](#reviewers)                                                  |       | 要在拉取请求上设置的审查者                                               |
-| [`schedule.day`](#scheduleday)                                             |       | 检查更新的周日期                                                    |
-| [`schedule.time`](#scheduletime)                                           |       | 每天检查更新的时间 (hh:mm)                                           |
-| [`schedule.timezone`](#scheduletimezone)                                   |       | 一天中时间的时区（区域标识符）                                             |
-| [`target-branch`](#target-branch)                                          |       | 对其创建拉取请求的分支                                                 |
-| [`vendor`](#vendor)                                                        |       | 更新供应或缓存的依赖项                                                 |
-| [`versioning-strategy`](#versioning-strategy)                              |       | 如何更新清单版本要求                                                  |
+| 选项                                                                         |  必选   | 描述                                                                                     |
+|:-------------------------------------------------------------------------- |:-----:|:-------------------------------------------------------------------------------------- |
+| [`package-ecosystem`](#package-ecosystem)                                  | **X** | 要使用的包管理器                                                                               |
+| [`目录`](#directory)                                                         | **X** | 包清单位置                                                                                  |
+| [`schedule.interval`](#scheduleinterval)                                   | **X** | 检查更新的频率                                                                                |
+| [`allow`](#allow)                                                          |       | 自定义允许的更新                                                                               |
+| [`assignees`](#assignees)                                                  |       | 要在拉取请求上设置的受让人                                                                          |
+| [`commit-message`](#commit-message)                                        |       | Commit message preferences                  |{% ifversion fpt or ghec or ghes > 3.4 %}
+| [`enable-beta-ecosystems`](#enable-beta-ecosystems)                        |       | Enable ecosystems that have beta-level support 
+{% endif %}
+| [`ignore`](#ignore)                                                        |       | 忽略某些依赖项或版本                                                                             |
+| [`insecure-external-code-execution`](#insecure-external-code-execution)    |       | 允许或拒绝清单文件中的代码执行                                                                        |
+| [`labels`](#labels)                                                        |       | 要在拉取请求上设置的标签                                                                           |
+| [`里程碑`](#milestone)                                                        |       | 要在拉取请求上设置的里程碑                                                                          |
+| [`open-pull-requests-limit`](#open-pull-requests-limit)                    |       | 限制对版本更新打开的拉取请求数                                                                        |
+| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) |       | 更改拉取请求分支名称的分隔符                                                                         |
+| [`rebase-strategy`](#rebase-strategy)                                      |       | 禁用自动变基                                                                                 |
+| [`registries`](#registries)                                                |       | {% data variables.product.prodname_dependabot %} 可以访问的私有注册表                            |
+| [`reviewers`](#reviewers)                                                  |       | 要在拉取请求上设置的审查者                                                                          |
+| [`schedule.day`](#scheduleday)                                             |       | 检查更新的周日期                                                                               |
+| [`schedule.time`](#scheduletime)                                           |       | 每天检查更新的时间 (hh:mm)                                                                      |
+| [`schedule.timezone`](#scheduletimezone)                                   |       | 一天中时间的时区（区域标识符）                                                                        |
+| [`target-branch`](#target-branch)                                          |       | 对其创建拉取请求的分支                                                                            |
+| [`vendor`](#vendor)                                                        |       | 更新供应或缓存的依赖项                                                                            |
+| [`versioning-strategy`](#versioning-strategy)                              |       | 如何更新清单版本要求                                                                             |
 
 这些选项大致分为以下类别。
 
@@ -302,7 +304,6 @@ updates:
       prefix-development: "pip dev"
       include: "scope"
 ```
-
 ### `ignore`
 
 {% data reusables.dependabot.default-dependencies-allow-ignore %}
@@ -330,7 +331,7 @@ updates:
 {% data reusables.dependabot.option-affects-security-updates %}
 
 ```yaml
-# Use `ignore` to specify dependencies that should not be updated 
+# Use `ignore` to specify dependencies that should not be updated
 
 version: 2
 updates:
@@ -356,6 +357,15 @@ updates:
 
 {% endnote %}
 
+{% ifversion fpt or ghec or ghes > 3.4 %}
+{% note %}
+
+**Note**: For the `pub` ecosystem, {% data variables.product.prodname_dependabot %} won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
+
+{% endnote %}
+
+{% endif %}
+
 ### `insecure-external-code-execution`
 
 作为版本更新过程的一部分，具有 `package-ecosystem` 值 `bundler`、`mix` 和 `pip` 的包管理器可以在清单中执行外部代码。 这可能允许受损害的软件包窃取凭据或访问已配置的注册。 当您在 `updates` 配置中添加 [`registries`](#registries) 设置时，{% data variables.product.prodname_dependabot %} 自会动阻止外部代码执行，在这种情况下，版本更新可能失败。 您可以选择覆盖此行为，并将 `insecure-external-code-execution` 设置为 `allow`，以允许 `bundler`、`mix` 和 `pip` 包管理器的执行。
@@ -504,7 +514,7 @@ updates:
 要允许 {% data variables.product.prodname_dependabot %} 使用 `bundler`、`mix` 和 `pip` 包管理器来更新私人注册表中的依赖项，您可以选择允许外部代码执行。 更多信息请参阅上面的 [`insecure-external-code-execution`](#insecure-external-code-execution)。
 
 ```yaml
-# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries 
+# Allow {% data variables.product.prodname_dependabot %} to use one of the two defined private registries
 # when updating dependency versions for this ecosystem
 
 {% raw %}
@@ -738,7 +748,7 @@ updates:
 
 version: 2
 registries:
-  dockerhub: # Define access for a private registry 
+  dockerhub: # Define access for a private registry
     type: docker-registry
     url: registry.hub.docker.com
     username: octocat
@@ -972,3 +982,23 @@ registries:
     token: ${{secrets.MY_TERRAFORM_API_TOKEN}}
 ```
 {% endraw %}
+
+{% ifversion fpt or ghec or ghes > 3.4 %}
+## Enabling support for beta-level ecosystems
+
+### `enable-beta-ecosystems`
+
+By default, {% data variables.product.prodname_dependabot %} updates the dependency manifests and lock files only for fully supported ecosystems. Use the `enable-beta-ecosystems` flag to opt in to updates for ecosystems that are not yet generally available.
+
+```yaml
+# Configure beta ecosystem
+
+version: 2
+enable-beta-ecosystems: true
+updates:
+  - package-ecosystem: "pub"
+    directory: "/"
+    schedule:
+      interval: "daily"
+```
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/repository-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
index 1351bfe842..1cc8cc1fb6 100644
--- a/translations/zh-CN/content/code-security/repository-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
@@ -65,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 %} For more information, see "[About {% data variables.product.prodname_security_advisories %} for repositories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)."
+ 作为维护者，要在您的代码中披露漏洞，请先在 {% data variables.product.prodname_dotcom %} 中软件包的仓库内创建安全通告。 {% data reusables.security-advisory.security-advisory-overview %} 更多信息请参阅“[关于存储库的 {% data variables.product.prodname_security_advisories %}](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)”。
 
 
- To get started, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
+ 要开始，请参阅“[创建仓库安全通告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md b/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
index 242aa6b989..681ab83f58 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md
@@ -1,5 +1,5 @@
 ---
-title: About GitHub Security Advisories for repositories
+title: 关于存储库的 GitHub 安全通告
 intro: '您可以使用 {% data variables.product.prodname_security_advisories %} 来私下讨论、修复和发布有关仓库中安全漏洞的信息。'
 redirect_from:
   - /articles/about-maintainer-security-advisories
@@ -14,7 +14,7 @@ topics:
   - Security advisories
   - Vulnerabilities
   - CVEs
-shortTitle: Repository security advisories
+shortTitle: 存储库安全通告
 ---
 
 {% data reusables.repositories.security-advisory-admin-permissions %}
@@ -29,17 +29,17 @@ shortTitle: Repository security advisories
 
 通过 {% data variables.product.prodname_security_advisories %}，您可以：
 
-1. 创建安全通告草稿，并使用草稿私下讨论漏洞对项目的影响。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
+1. 创建安全通告草稿，并使用草稿私下讨论漏洞对项目的影响。 更多信息请参阅“[创建存储库安全通告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
 2. 在临时私有复刻中私下协作以修复漏洞。
-3. 在补丁发布后发布通告向社区提醒漏洞。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+3. 在补丁发布后发布通告向社区提醒漏洞。 更多信息请参阅“[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
 
 {% data reusables.repositories.security-advisories-republishing %}
 
-您可以向为安全通告做出贡献的个人提供积分。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
+您可以向为安全通告做出贡献的个人提供积分。 更多信息请参阅“[编辑存储库安全通告](/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 %} 发布任何由依赖关系图支持的生态系统的安全通告。 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)."
+如果您在仓库中创建了安全通告，安全通告将保留在您的仓库中。 我们在 [github.com/advantores](https://github.com/advisories) 上的 {% data variables.product.prodname_advisory_database %} 发布任何由依赖关系图支持的生态系统的安全通告。 任何人都可以提交对 {% data variables.product.prodname_advisory_database %} 中发布的通告的更改。 更多信息请参阅“[编辑 {% data variables.product.prodname_advisory_database %} 中的安全通告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
 
 如果安全通告是专门针对 npm 的，我们也会向 npm 安全通告发布该通告。 更多信息请参阅 [npmjs.com/advisories](https://www.npmjs.com/advisories)。
 
@@ -53,7 +53,7 @@ shortTitle: Repository security advisories
 
 在 {% 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 数据库。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+在您发布了安全通告并且 {% data variables.product.prodname_dotcom %} 为漏洞分配 CVE 标识号后，{% data variables.product.prodname_dotcom %} 会将 CVE 发布到 MITRE 数据库。 更多信息请参阅“[发布存储库安全通告](/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/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
index 53699debf5..f96a46e9ad 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md
@@ -1,5 +1,5 @@
 ---
-title: Adding a collaborator to a repository security advisory
+title: 将协作者添加到仓库安全通告
 intro: 您可以添加其他用户或团队与您协作处理安全通告。
 redirect_from:
   - /articles/adding-a-collaborator-to-a-maintainer-security-advisory
@@ -14,7 +14,7 @@ topics:
   - Security advisories
   - Vulnerabilities
   - Collaboration
-shortTitle: Add collaborators
+shortTitle: 添加协作者
 ---
 
 对安全通告具有管理员权限的人员可向安全通告添加协作者。
@@ -23,11 +23,11 @@ shortTitle: Add collaborators
 
 ## 添加协作者到安全通告
 
-协作者对安全通告具有写入权限。 For more information, see "[Permission levels for repository security advisories](/code-security/repository-security-advisories/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 %} 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)."
+{% data reusables.repositories.security-advisory-collaborators-public-repositories %} 有关删除安全通告协作者的更多信息，请参阅“[从仓库安全通告删除协作者](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)”。
 
 {% endnote %}
 
@@ -40,6 +40,6 @@ shortTitle: Add collaborators
 
 ## 延伸阅读
 
-- "[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)."
+- "[仓库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
+- "[在临时私有复刻中协作以解决仓库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)"
+- “[从仓库安全通告中删除协作者](/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-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
index 7eead2503e..376fbd58ff 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-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,5 +1,5 @@
 ---
-title: Collaborating in a temporary private fork to resolve a repository security vulnerability
+title: 在临时私有复刻中协作以解决仓库安全漏洞
 intro: 您可以创建临时私有复刻，以私下协作修复仓库中的安全漏洞。
 redirect_from:
   - /articles/collaborating-in-a-temporary-private-fork-to-resolve-a-security-vulnerability
@@ -21,7 +21,7 @@ shortTitle: 临时私有复刻
 
 ## 基本要求
 
-在临时私有复刻中进行协作之前，必须创建维护员通告草稿。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
+在临时私有复刻中进行协作之前，必须创建维护员通告草稿。 更多信息请参阅“[创建存储库安全通告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
 
 ## 创建临时私有复刻
 
@@ -37,7 +37,7 @@ shortTitle: 临时私有复刻
 
 ## 将协作者添加到临时私有复刻
 
-对安全通告具有管理员权限的任何人都可以向安全通告添加其他协作者，而安全通告的协作者可以访问临时私有复刻。 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)."
+对安全通告具有管理员权限的任何人都可以向安全通告添加其他协作者，而安全通告的协作者可以访问临时私有复刻。 更多信息请参阅“[添加协作者到仓库安全通告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
 
 ## 将更改添加到临时私有复刻
 
@@ -79,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)
 
-合并安全通告中的更改后，您可以发布安全通告，以提醒您的社区有关项目早期版本中安全漏洞的信息。 For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
+合并安全通告中的更改后，您可以发布安全通告，以提醒您的社区有关项目早期版本中安全漏洞的信息。 更多信息请参阅“[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-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)"
+- "[仓库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
+- "[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)"
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
index 86c3793c4f..cca2d11551 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md
@@ -1,5 +1,5 @@
 ---
-title: Creating a repository security advisory
+title: 创建仓库安全通告
 intro: 您可以创建安全通告草稿，以私下讨论和修复开源项目中的安全漏洞。
 redirect_from:
   - /articles/creating-a-maintainer-security-advisory
@@ -13,7 +13,7 @@ type: how_to
 topics:
   - Security advisories
   - Vulnerabilities
-shortTitle: Create repository advisories
+shortTitle: 创建仓库通告
 ---
 
 任何对仓库有管理员权限的人都可以创建安全通告。
@@ -36,7 +36,7 @@ shortTitle: Create repository advisories
 ## 后续步骤
 
 - 评论安全通告草稿，与团队讨论漏洞。
-- 添加协作者到安全通告。 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)."
+- 添加协作者到安全通告。 更多信息请参阅“[添加协作者到仓库安全通告](/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/editing-a-repository-security-advisory#about-credits-for-security-advisories)”。
+- 发布安全通告以向社区提醒安全漏洞。 更多信息请参阅“[发布存储库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
diff --git a/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
index 2964182bf7..685fb85890 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
 ---
-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.
+title: 编辑仓库安全通告
+intro: 如果需要更新详细信息或更正错误，可以编辑仓库安全通告的元数据和说明。
 redirect_from:
   - /github/managing-security-vulnerabilities/editing-a-security-advisory
   - /code-security/security-advisories/editing-a-security-advisory
@@ -11,10 +11,10 @@ type: how_to
 topics:
   - Security advisories
   - Vulnerabilities
-shortTitle: Edit repository advisories
+shortTitle: 编辑仓库通告
 ---
 
-People with admin permissions to a repository security advisory can edit the security advisory.
+对仓库安全通告具有管理员权限的人员可以编辑安全通告。
 
 {% data reusables.security-advisory.repository-level-advisory-note %}
 
@@ -43,4 +43,4 @@ People with admin permissions to a repository security advisory can edit the sec
 
 ## 延伸阅读
 
-- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/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
index 58bf1aeb14..10606bf5a0 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/index.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/index.md
@@ -1,7 +1,7 @@
 ---
-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.'
+title: 管理项目中漏洞的仓库安全通告
+shortTitle: 存储库安全通告
+intro: 使用仓库安全通告讨论、修正和披露您仓库中的安全漏洞。
 redirect_from:
   - /articles/managing-security-vulnerabilities-in-your-project
   - /github/managing-security-vulnerabilities/managing-security-vulnerabilities-in-your-project
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
index 87f8778d09..d6f238523c 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-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.
+title: 仓库安全通告的权限级别
+intro: 您在仓库安全通告中可以执行的操作取决于您是公告的管理员还是对其有写入权限。
 redirect_from:
   - /articles/permission-levels-for-maintainer-security-advisories
   - /github/managing-security-vulnerabilities/permission-levels-for-maintainer-security-advisories
@@ -17,29 +17,29 @@ topics:
 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)."
+本文仅适用于存储库级别的安全通告。 任何人都可以在 [github.com/advisories](https://github.com/advisories) 上为 {% data variables.product.prodname_advisory_database %} 中的全局安全通告做出贡献。 对全局通告的编辑不会更改或影响通告在存储库中的显示方式。  更多信息请参阅“[编辑 {% data variables.product.prodname_advisory_database %} 中的安全通告](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/editing-security-advisories-in-the-github-advisory-database)”。
 
 ## 权限概述
 
-{% 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)."
+{% data reusables.repositories.security-advisory-admin-permissions %} 有关添加协作者到安全通告的更多信息，请参阅“[添加协作者到仓库安全通告](/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     |
+| 操作                                                                                                                                                                                    | 写入权限 | 管理员权限 |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ----- |
+| 查看安全通告草稿                                                                                                                                                                              | X    | X     |
+| 添加协作者到安全通告（请参阅“[添加协作者到仓库安全通告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”）                                                |      | X     |
+| 编辑和删除安全通告中的任何评论                                                                                                                                                                       | X    | X     |
+| 在安全通告中创建临时私有复刻（请参阅“[在临时私有复刻中协作以解决仓库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”）    |      | X     |
+| 添加更改到安全通告中的临时私有复刻（请参阅“[在临时私有复刻中协作以解决仓库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”） | X    | X     |
+| 在临时私有复刻中创建拉取请求（请参阅“[在临时私有复刻中协作以解决仓库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”）    | X    | X     |
+| 合并安全通告中的更改（请参阅“[在临时私有复刻中协作以解决仓库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”）        |      | X     |
+| 在安全通告中添加和编辑元数据（请参阅“[发布仓库安全通告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”）                                                              | X    | X     |
+| 添加和删除安全通告的积分（请参阅“[编辑仓库安全通告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”）                                                                   | X    | X     |
+| 关闭安全通告草稿                                                                                                                                                                              |      | X     |
+| 发布安全通告（请参阅“[发布仓库安全通告](/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)"
+- "[添加协作者到仓库安全通告](/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/removing-a-collaborator-from-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/publishing-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
index a2f32349e8..1196824796 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md
@@ -1,5 +1,5 @@
 ---
-title: Publishing a repository security advisory
+title: 发布存储库安全通告
 intro: 您可以发布安全通告，向社区提醒项目中的安全漏洞。
 redirect_from:
   - /articles/publishing-a-maintainer-security-advisory
@@ -15,7 +15,7 @@ topics:
   - Vulnerabilities
   - CVEs
   - Repositories
-shortTitle: Publish repository advisories
+shortTitle: 发布存储库通告
 ---
 
 <!--Marketing-LINK: From /features/security/software-supply-chain page "Publishing a security advisory".-->
@@ -26,9 +26,9 @@ shortTitle: Publish repository advisories
 
 ## 基本要求
 
-在发布安全通告或申请 CVE 标识号之前，必须创建安全通告草稿，并提供受安全漏洞影响的项目版本的相关信息。 For more information, see "[Creating a repository security advisory](/code-security/repository-security-advisories/creating-a-repository-security-advisory)."
+在发布安全通告或申请 CVE 标识号之前，必须创建安全通告草稿，并提供受安全漏洞影响的项目版本的相关信息。 更多信息请参阅“[创建存储库安全通告](/code-security/repository-security-advisories/creating-a-repository-security-advisory)”。
 
-如果您已创建安全通告，但尚未提供有关安全漏洞影响的项目版本的详细信息，则可以编辑安全通告。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)."
+如果您已创建安全通告，但尚未提供有关安全漏洞影响的项目版本的详细信息，则可以编辑安全通告。 更多信息请参阅“[编辑存储库安全通告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”。
 
 ## 关于发布安全通告
 
@@ -36,7 +36,7 @@ shortTitle: Publish repository advisories
 
 {% data reusables.repositories.security-advisories-republishing %}
 
-在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 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)."
+在发布安全通告之前，您可以私下协作在临时私有复刻中修复漏洞。 更多信息请参阅“[在临时私有复刻中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”。
 
 {% warning %}
 
@@ -63,7 +63,7 @@ shortTitle: Publish repository advisories
 
 发布安全通告后，安全通告的 URL 将与发布安全通告之前保持相同。 对仓库具有读取权限的任何人都能看到安全通告。 安全通告的协作者可以继续查看安全通告中过去的对话，包括完整的评论流，除非有管理员权限的人从安全通告删除该协作者。
 
-如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory)."
+如果需要更新或更正已发布的安全通告中的信息，可以编辑安全通告。 更多信息请参阅“[编辑存储库安全通告](/code-security/repository-security-advisories/editing-a-repository-security-advisory)”。
 
 ## 发布安全通告
 
@@ -81,7 +81,7 @@ shortTitle: Publish repository advisories
 
 ## 申请 CVE 识别号（可选）
 
-{% 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.request-security-advisory-cve-id %} 更多信息请参阅“[关于存储库的 {% data variables.product.prodname_security_advisories %}](/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 %}
@@ -92,4 +92,4 @@ shortTitle: Publish repository advisories
 
 ## 延伸阅读
 
-- "[Withdrawing a repository security advisory](/code-security/repository-security-advisories/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/removing-a-collaborator-from-a-repository-security-advisory.md b/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
index 54c63043ee..869625ee07 100644
--- a/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
+++ b/translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md
@@ -1,6 +1,6 @@
 ---
-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.'
+title: 从仓库安全通告删除协作者
+intro: 协作者从仓库安全通告中删除后，将失去对安全通告的讨论和元数据的读取和写入权限。
 redirect_from:
   - /github/managing-security-vulnerabilities/removing-a-collaborator-from-a-security-advisory
   - /code-security/security-advisories/removing-a-collaborator-from-a-security-advisory
@@ -32,5 +32,5 @@ shortTitle: 删除协作者
 
 ## 延伸阅读
 
-- "[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)"
+- "[仓库安全通告的权限级别](/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories)"
+- "[添加协作者到仓库安全通告](/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
index c959b4f03a..44ae8f0200 100644
--- 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
@@ -1,6 +1,6 @@
 ---
-title: Withdrawing a repository security advisory
-intro: You can withdraw a repository security advisory that you've published.
+title: 撤销存储库安全通告
+intro: 您可以撤销已发布的仓库安全通告。
 redirect_from:
   - /github/managing-security-vulnerabilities/withdrawing-a-security-advisory
   - /code-security/security-advisories/withdrawing-a-security-advisory
@@ -11,7 +11,7 @@ type: how_to
 topics:
   - Security advisories
   - Vulnerabilities
-shortTitle: Withdraw repository advisories
+shortTitle: 撤销存储库通告
 ---
 
 {% data reusables.security-advisory.repository-level-advisory-note %}
@@ -20,4 +20,4 @@ shortTitle: Withdraw repository advisories
 
 ## 延伸阅读
 
-- "[Editing a repository security advisory](/code-security/repository-security-advisories/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/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
index 9549eaaae2..ca59a10f7a 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md
@@ -38,6 +38,13 @@ If your project communicates with an external service, you might use a token or
 
 Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %}
 
+{% if secret-scanning-push-protection %}
+
+You can also enable {% data variables.product.prodname_secret_scanning %} as a push protection for a repository or an organization. When you enable this feature, {% data variables.product.prodname_secret_scanning %} prevents contributors from pushing code with a detected secret. To proceed, contributors must either remove the secret(s) from the push or, if needed, bypass the protection. For more information, see "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."
+
+{% endif %}
+
+
 {% ifversion fpt or ghec %}
 ## About {% data variables.product.prodname_secret_scanning_partner %}
 
diff --git a/translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md b/translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
index b994658259..e5dddff882 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md
@@ -28,13 +28,15 @@ shortTitle: 配置密钥扫描
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. 如果 {% data variables.product.prodname_advanced_security %} 尚未对仓库启用，请在“{% data variables.product.prodname_GH_advanced_security %}”右侧单击 **Enable（启用）**。
    {% ifversion fpt or ghec %}![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/help/repository/enable-ghas-dotcom.png)
    {% elsif ghes or ghae %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
 5. 查看启用 {% data variables.product.prodname_advanced_security %} 的影响，然后点击 **对仓库启用 {% data variables.product.prodname_GH_advanced_security %}**。
 6. 当您启用 {% data variables.product.prodname_advanced_security %} 时，{% data variables.product.prodname_secret_scanning %} 可能会因为组织的设置而自动启用。 如果 "{% data variables.product.prodname_secret_scanning_caps %}" 显示 **Enable（启用）**按钮，则您仍需通过单击 **Enable（启用）**来启用 {% data variables.product.prodname_secret_scanning %}。 如果您看到 **Disable（禁用）**按钮，则表明 {% data variables.product.prodname_secret_scanning %} 已启用。 ![为仓库启用 {% data variables.product.prodname_secret_scanning %}](/assets/images/help/repository/enable-secret-scanning-dotcom.png)
-
+{% if secret-scanning-push-protection %}
+7. （可选）如果要启用推送保护，请单击“Push protection（推送保护）”右侧的 **Enable（启用）** 。 {% data reusables.secret-scanning.push-protection-overview %} 更多信息请参阅“[使用 {% data variables.product.prodname_secret_scanning %} 保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。 ![为存储库启用推送保护](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
+{% endif %}
 {% ifversion ghae %}
 1. 在可以启用 {% data variables.product.prodname_secret_scanning %} 之前，您需要先启用 {% data variables.product.prodname_GH_advanced_security %}。 在“{% data variables.product.prodname_GH_advanced_security %}”右边单击 **Enable（启用）**。 ![为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/enterprise/github-ae/repository/enable-ghas-ghae.png)
 2. 单击**为此仓库启用 {% data variables.product.prodname_GH_advanced_security %}** 以确认操作。 ![确认为仓库启用 {% data variables.product.prodname_GH_advanced_security %}](/assets/images/enterprise/github-ae/repository/enable-ghas-confirmation-ghae.png)
diff --git a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index fbf860753f..8a6fc12866 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -64,14 +64,12 @@ topics:
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5499 %}
 1. 当您准备好测试新的自定义模式时，要识别存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并空运行）**。
-1. 空运行完成后，您将看到存储库中的结果示例（最多 1000 个）。 查看结果并确定任何误报结果。 ![显示空运行结果的屏幕截图](/assets/images/help/repository/secret-scanning-publish-pattern.png)
-1. 编辑新的自定义模式以修复结果的任何问题，然后单击 **Save and dry run（保存并空运行）**以测试更改。
-{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
 {% endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
@@ -110,11 +108,13 @@ aAAAe9
 
 在定义自定义模式之前，您必须确保在组织中为要扫描的仓库启用 {% data variables.product.prodname_secret_scanning %}。 要在组织中的所有存储库上启用 {% data variables.product.prodname_secret_scanning %} ，请参阅“[管理组织的安全和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”。
 
+{% ifversion ghes < 3.5 or ghae %}
 {% note %}
 
 **注意：** 由于没有试运行功能，我们建议您先在存储库中测试自定义模式，然后再为整个组织定义它们。 这样，可以避免创建过多的误报 {% data variables.product.prodname_secret_scanning %} 警报。
 
 {% endnote %}
+{% endif %}
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
@@ -122,6 +122,12 @@ aAAAe9
 {% data reusables.repositories.navigate-to-ghas-settings %}
 {% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
 {% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
+{%- if secret-scanning-org-dry-runs %}
+1. 当您准备好测试新的自定义模式时，要识别所选存储库中的匹配项而不创建警报，请单击 **Save and dry run（保存并试运行）**。
+1. 搜索并选择要在其中执行试运行的存储库。 您最多可以选择 10 个存储库。 ![显示为试运行选择的存储库的屏幕截图](/assets/images/help/repository/secret-scanning-dry-run-custom-pattern-select-repo.png)
+1. 当您准备好测试新的自定义模式时，请单击 **Dry run（试运行）**。
+{% data reusables.advanced-security.secret-scanning-dry-run-results %}
+{%- endif %}
 {% data reusables.advanced-security.secret-scanning-create-custom-pattern %}
 
 创建模式后，{% data variables.product.prodname_secret_scanning %} 扫描组织的仓库中的任何密钥，包括其所有分支的整个 Git 历史记录。 组织所有者和仓库管理员将会收到发现的任何密钥警报通知，并且可以审查发现密钥的仓库中的警报。 有关查看 {% data variables.product.prodname_secret_scanning %} 警报的详细信息，请参阅“[管理来自 {% data variables.product.prodname_secret_scanning %} 的警报](/code-security/secret-security/managing-alerts-from-secret-scanning)”。
diff --git a/translations/zh-CN/content/code-security/secret-scanning/index.md b/translations/zh-CN/content/code-security/secret-scanning/index.md
index 5628ae51c1..72928244d7 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/index.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/index.md
@@ -20,5 +20,6 @@ children:
   - /defining-custom-patterns-for-secret-scanning
   - /managing-alerts-from-secret-scanning
   - /secret-scanning-patterns
+  - /protecting-pushes-with-secret-scanning
 ---
 
diff --git a/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
new file mode 100644
index 0000000000..89819586ef
--- /dev/null
+++ b/translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md
@@ -0,0 +1,87 @@
+---
+title: Protecting pushes with secret scanning
+intro: 'You can use {% data variables.product.prodname_secret_scanning %} to prevent supported secrets from being pushed into your organization or repository by enabling push protection.'
+product: '{% data reusables.gated-features.secret-scanning %}'
+miniTocMaxHeadingLevel: 3
+versions:
+  feature: secret-scanning-push-protection
+redirect_from:
+  - /early-access/code-security/secret-scanning/protecting-pushes-with-secret-scanning
+type: how_to
+topics:
+  - Secret scanning
+  - Advanced Security
+  - Alerts
+  - Repositories
+shortTitle: Push protection
+---
+
+{% data reusables.secret-scanning.beta %}
+{% data reusables.secret-scanning.enterprise-enable-secret-scanning %}
+{% data reusables.secret-scanning.push-protection-beta %}
+
+## About push protection for secrets
+
+Up to now, {% data variables.product.prodname_secret_scanning_GHAS %} checks for secrets _after_ a push and alerts users to exposed secrets. {% data reusables.secret-scanning.push-protection-overview %}
+
+{% data variables.product.prodname_secret_scanning_caps %} as a push protection currently scans repositories for secrets issued by the following service providers.
+
+{% data reusables.secret-scanning.secret-list-private-push-protection %}
+
+## Enabling {% data variables.product.prodname_secret_scanning %} as a push protection
+
+For you to use {% data variables.product.prodname_secret_scanning %} as a push protection, the organization or repository needs to have both {% data variables.product.prodname_GH_advanced_security %} and {% data variables.product.prodname_secret_scanning %} enabled. For more information, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)," "[Managing security and analysis settings for your repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository)," and "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."
+
+Organization owners, security managers, and repository administrators can enable push protection for {% data variables.product.prodname_secret_scanning %} via the UI and API. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
+
+### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for an organization
+
+{% data reusables.organizations.navigate-to-org %}
+{% data reusables.organizations.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-push-protection-org %}
+
+### Enabling {% data variables.product.prodname_secret_scanning %} as a push protection for a repository
+
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.sidebar-settings %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
+{% data reusables.repositories.navigate-to-ghas-settings %}
+{% data reusables.advanced-security.secret-scanning-push-protection-repo %}
+
+
+## Using {% data variables.product.prodname_secret_scanning %} as a push protection from the command line
+
+When you attempt to push a supported secret to a repository or organization with {% data variables.product.prodname_secret_scanning %} as a push protection enabled, {% data variables.product.prodname_dotcom %} will block the push. You can remove the secret from your commit or follow a provided URL to allow the push.
+
+Up to five detected secrets will be displayed at a time on the command line. If a particular secret has already been detected in the repository and an alert already exists, {% data variables.product.prodname_dotcom %} will not block that secret.
+
+![Screenshot showing that a push is blocked when a user attempts to push a secret to a repository](/assets/images/help/repository/secret-scanning-push-protection-with-link.png)
+
+If you need to remove the secret from your latest commit (that is, `HEAD`) on the branch being pushed and any earlier commits that contain the secret, you can remove the secret from `HEAD`, then squash the commits between when the commit was introduced and the first version of `HEAD` for which the secret has been removed.
+
+{% note %}
+
+**注意**：
+
+* If your git configuration supports pushes to multiple branches, and not only to the default branch, your push may be blocked due to additional and unintended refs being pushed. For more information, see the [`push.default` options](https://git-scm.com/docs/git-config#Documentation/git-config.txt-pushdefault) in the Git Docs.
+* If {% data variables.product.prodname_secret_scanning %} upon a push times out, {% data variables.product.prodname_dotcom %} will still run a scan after the push.
+
+{% endnote %}
+
+### Allowing a blocked secret to be pushed
+
+If {% data variables.product.prodname_dotcom %} blocks a secret that you believe is safe to push, you can allow the secret and specify the reason why it should be allowed.
+
+If you confirm a secret is real and that you intend to fix it later, you should aim to remediate the secret as soon as possible. For example, you might revoke the secret and remove the secret from the repository's commit history. For more information, see "[Removing sensitive data from a repository](/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository)."
+
+When you allow a secret to be pushed, an alert is created in the "Security" tab. The alert is closed and no notifications are sent if you specify that the secret is a false positive or used only in tests. If you specify that the secret is real and that you will fix it later, the security alert remains open and notifications are sent to the author of the commit and repository administrators. For more information, see "[Managing alerts from secret scanning](/code-security/secret-scanning/managing-alerts-from-secret-scanning)."
+
+1. Visit the URL returned by {% data variables.product.prodname_dotcom %} when your push was blocked. ![Screenshot showing form with options for unblocking the push of a secret](/assets/images/help/repository/secret-scanning-unblock-form.png)
+2. Choose the option that best describes why you should be able to push the secret.
+    - If the secret is only used in tests and poses no threat, click **It's used in tests**.
+    - If the detected string is not a secret, click **It's a false positive**.
+    - If the secret is real but you intend to fix it later, click **I'll fix it later**.
+3. Click **Allow me to push this secret**.
+4. Reattempt the push on the command line within three hours. If you have not pushed within three hours, you will need to repeat this process.
diff --git a/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md b/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md
index 6dbaf24e09..4ae940a282 100644
--- a/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md
+++ b/translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md
@@ -32,7 +32,7 @@ Organizations using {% data variables.product.prodname_ghe_cloud %} with {% data
 
 ## Supported secrets for partner patterns
 
-{% data variables.product.product_name %} 当前会扫描公共仓库，查找以下服务提供商发布的密码。 有关 {% data variables.product.prodname_secret_scanning_partner %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)”。
+{% data variables.product.product_name %} currently scans public repositories for secrets issued by the following service providers. For more information about {% data variables.product.prodname_secret_scanning_partner %}, see "[About {% data variables.product.prodname_secret_scanning_partner %}](/code-security/secret-scanning/about-secret-scanning#about-secret-scanning-for-partner-patterns)."
 
 {% data reusables.secret-scanning.partner-secret-list-public-repo %}
 {% endif %}
@@ -45,7 +45,7 @@ When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% d
 {% ifversion ghes > 3.1 or ghae or ghec %}
 {% note %}
 
-**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for your repository, organization, or enterprise. 更多信息请参阅“[定义 {% data variables.product.prodname_secret_scanning %} 的自定义模式](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)”。
+**Note:** You can also define custom {% data variables.product.prodname_secret_scanning %} patterns for your repository, organization, or enterprise. For more information, see "[Defining custom patterns for {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/defining-custom-patterns-for-secret-scanning)."
 
 {% endnote %}
 {% endif %}
@@ -53,10 +53,10 @@ When {% data variables.product.prodname_secret_scanning_GHAS %} is enabled, {% d
 {% data reusables.secret-scanning.partner-secret-list-private-repo %}
 {% endif %}
 
-## 延伸阅读
+## Further reading
 
-- "[保护您的仓库](/code-security/getting-started/securing-your-repository)"
-- "[保护帐户和数据安全](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
+- "[Securing your repository](/code-security/getting-started/securing-your-repository)"
+- "[Keeping your account and data secure](/github/authenticating-to-github/keeping-your-account-and-data-secure)"
 {%- ifversion fpt or ghec %}
 - "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)"
 {%- else %}
diff --git a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
index 347212ca7b..58b79f6752 100644
--- a/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md
@@ -22,11 +22,13 @@ topics:
 shortTitle: 关于安全概述
 ---
 
+{% ifversion ghes < 3.5 or ghae-issue-4554 %}
 {% data reusables.security-center.beta %}
+{% endif %}
 
 ## 关于安全概述
 
-{% ifversion ghes or ghec or ghae %}You{% elsif fpt %}Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can use the security overview for a high-level view of the security status of {% ifversion ghes or ghec or ghae %}your  {% elsif fpt %}their{% endif %} organization or to identify problematic repositories that require intervention. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %}These organizations{% endif %} can view aggregate or repository-specific security information in the security overview. {% ifversion ghes or ghec or ghae %}You {% elsif fpt %} Organizations that use {% data variables.product.prodname_ghe_cloud %}{% endif %} can also use the security overview to see which security features are enabled for {% ifversion ghes or ghec or ghae %}your {% elsif fpt %}their {% endif %} repositories and to configure any available security features that are not currently in use. {% ifversion fpt %}For more information, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview).{% endif %}
+{% ifversion ghes or ghec or ghae %}您{% elsif fpt %}使用 {% data variables.product.prodname_ghe_cloud %}{% endif %} 的组织可以使用安全性概述来获取{% ifversion ghes or ghec or ghae %} 您的 {% elsif fpt %}其{% endif %} 组织安全状态的高级视图，或者识别需要干预的问题存储库。 {% ifversion ghes or ghec or ghae %}您 {% elsif fpt %}这些组织{% endif %} 可以在安全性概述中查看汇总或存储库特定的安全信息。 {% ifversion ghes or ghec or ghae %}您 {% elsif fpt %} 使用 {% data variables.product.prodname_ghe_cloud %} 的组织{% endif %}还可以使用安全性概述来查看 {% ifversion ghes or ghec or ghae %}您的 {% elsif fpt %}其 {% endif %} 存储库启用了哪些安全功能，并配置当前未使用的任何可用安全功能。 {% ifversion fpt %}更多信息请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/code-security/security-overview/about-the-security-overview)。{% endif %}
 
 {% ifversion ghec or ghes or ghae %}
 安全概述指示是否为组织拥有的存储库启用了 {% ifversion fpt or ghes > 3.1 or ghec %}安全{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} 功能，并合并每个功能的警报。{% ifversion fpt or ghes > 3.1 or ghec %} 安全功能包括 {% data variables.product.prodname_GH_advanced_security %} 功能，例如 {% data variables.product.prodname_code_scanning %} 和 {% data variables.product.prodname_secret_scanning %}以及 {% data variables.product.prodname_dependabot_alerts %}。{% endif %} 有关 {% data variables.product.prodname_GH_advanced_security %} 功能的详细信息，请参阅“[关于 {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)”。{% ifversion fpt or ghes > 3.1 or ghec %} 有关 {% data variables.product.prodname_dependabot_alerts %} 的详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)”。{% endif %}
@@ -77,5 +79,5 @@ shortTitle: 关于安全概述
 {% endif %}
 
 ### 关于团队级安全性概述
-在团队级别，安全概述显示团队拥有管理权限的仓库特定安全信息。 For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)."
+在团队级别，安全概述显示团队拥有管理权限的仓库特定安全信息。 更多信息请参阅“[管理团队的组织仓库访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。
 {% endif %}
diff --git a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
index bfc4b47d44..5300908d4c 100644
--- a/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md
@@ -17,7 +17,9 @@ topics:
 shortTitle: 筛选警报
 ---
 
+{% ifversion ghes < 3.5 or ghae-issue-4554 %}
 {% data reusables.security-center.beta %}
+{% endif %}
 
 ## 关于筛选安全性概述
 
@@ -121,10 +123,10 @@ shortTitle: 筛选警报
 
 在机密扫描警报视图中可用。
 
-| 限定符                            | 描述                                                                                                                                                                           |
-| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `secret-type:SERVICE_PROVIDER` | 显示指定机密和提供程序的警报。 更多信息请参阅“[{% data variables.product.prodname_secret_scanning_caps %} 模式](/code-security/secret-scanning/secret-scanning-patterns)”。                         |
-| `secret-type:CUSTOM-PATTERN`   | 显示与指定自定义模式匹配的机密的警报。 For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." |
+| 限定符                            | 描述                                                                                                                                                   |
+| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `secret-type:SERVICE_PROVIDER` | 显示指定机密和提供程序的警报。 更多信息请参阅“[{% data variables.product.prodname_secret_scanning_caps %} 模式](/code-security/secret-scanning/secret-scanning-patterns)”。 |
+| `secret-type:CUSTOM-PATTERN`   | 显示与指定自定义模式匹配的机密的警报。 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。                            |
 
 ## 按提供商筛选
 
diff --git a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
index 6ae31c82b4..16524c1a83 100644
--- a/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
+++ b/translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md
@@ -17,7 +17,9 @@ topics:
 shortTitle: 查看安全性概述
 ---
 
+{% ifversion ghes < 3.5 or ghae-issue-4554 %}
 {% data reusables.security-center.beta %}
+{% endif %}
 
 ## 查看组织的安全概述
 
@@ -39,7 +41,7 @@ shortTitle: 查看安全性概述
 ## 查看企业的安全性概述
 
 {% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
-1. 在左侧边栏中，单击 {% octicon "shield" aria-label="The shield icon" %}** 安全性**。
+1. 在左侧边栏中，单击 {% octicon "shield" aria-label="The shield icon" %} **代码安全性**。
 {% endif %}
 
 ## 查看仓库的警报
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
index f820d0efb5..6c5d8dcc9a 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview.md
@@ -1,8 +1,8 @@
 ---
-title: Securing your end-to-end supply chain
+title: 保护您的端到端供应链
 shortTitle: 概览
 allowTitleToDifferFromFilename: true
-intro: 'Introducing best practice guides on complete end-to-end supply chain security including personal accounts, code, and build processes.'
+intro: 介绍有关完整端到端供应链安全性（包括个人帐户、代码和构建流程）的最佳实践指南。
 versions:
   fpt: '*'
   ghec: '*'
@@ -15,24 +15,24 @@ topics:
   - Advanced Security
 ---
 
-## What is the end-to-end supply chain?
+## 什么是端到端供应链？
 
-At its core, end-to-end software supply chain security is about making sure the code you distribute hasn't been tampered with. Previously, attackers focused on targeting dependencies you use, for example libraries and frameworks. Attackers have now expanded their focus to include targeting user accounts and build processes, and so those systems must be defended as well.
+端到端软件供应链安全的核心是确保您分发的代码未被篡改。 以前，攻击者专注于针对您使用的依赖项，例如库和框架。 攻击者现在已经扩大了他们的关注点，包括针对用户帐户和构建过程，因此这些系统也必须得到保护。
 
-## About these guides
+## 关于这些指南
 
-This series of guides explains how to think about securing your end-to-end supply chain: personal account, code, and build processes. Each guide explains the risk to that area, and introduces the {% data variables.product.product_name %} features that can help you address that risk.
+本系列指南介绍了如何考虑保护端到端供应链：个人帐户、代码和构建流程。 每本指南都解释了该领域的风险，并介绍可帮助您解决该风险的 {% data variables.product.product_name %} 功能。
 
-Everyone's needs are different, so each guide starts with the highest impact change, and continues from there with additional improvements you should consider. You should feel free to skip around and focus on improvements you think will have the biggest benefit. The goal isn't to do everything at once but to continuously improve security in your systems over time.
+每个人的需求都是不同的，因此每本指南都从影响最大的变化开始，然后从那里继续进行您应该考虑的其他改进。 您应该自由跳过，注重于您认为会带来最大好处的改进。 目标不是一次完成所有操作，而是随着时间的推移不断提高系统的安全性。
 
-- "[Best practices for securing accounts](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)"
+- “[保护帐户的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)”
 
-- "[Best practices for securing code in your supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)"
+- “[保护供应链中代码的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)”
 
-- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
+- “[保护构建系统的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)”
 
 ## 延伸阅读
 
-- [Safeguarding artifact integrity across any software supply chain](https://slsa.dev/)
-- [Microsoft Supply Chain Integrity Model](https://github.com/microsoft/scim)
-- [Software Supply Chain Security Paper - CNCF Security Technical Advisory Group](https://github.com/cncf/tag-security/blob/main/supply-chain-security/supply-chain-security-paper/CNCF_SSCP_v1.pdf)
+- [保护任何软件供应链中的构件完整性](https://slsa.dev/)
+- [Microsoft 供应链诚信模型](https://github.com/microsoft/scim)
+- [软件供应链安全白皮书 - CNCF 安全技术咨询小组](https://github.com/cncf/tag-security/blob/main/supply-chain-security/supply-chain-security-paper/CNCF_SSCP_v1.pdf)
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
index 0cf0b8d7ad..6a283157e6 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/index.md
@@ -1,6 +1,6 @@
 ---
-title: End-to-end supply chain
-intro: 'How to think about securing your user accounts, your code, and your build process'
+title: 端到端供应链
+intro: 如何考虑保护用户帐户、代码和构建过程
 versions:
   fpt: '*'
   ghec: '*'
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
index ce7f6d5cee..ca5005c64a 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts.md
@@ -15,7 +15,6 @@ topics:
   - Security
   - Accounts
 ---
-
 ## About this guide
 
 This guide describes the highest impact changes you can make to increase account security. Each section outlines a change you can make to your processes to improve the security. The highest impact changes are listed first.
@@ -35,7 +34,7 @@ You can configure SAML authentication for an enterprise or organization account.
 
 After you configure SAML authentication, when members request access to your resources, they'll be directed to your SSO flow to ensure they are still recognized by your IdP. If they are unrecognized, their request is declined.
 
-Some IdPs support a protocol called SCIM, which can automatically provision or deprovision access on {% data variables.product.product_name %} when you make changes on your IdP. With SCIM, you can simplify administration as your team grows, and you can quickly revoke access to accounts. SCIM is available for individual organizations on {% data variables.product.product_name %}, or for enterprises that use {% data variables.product.prodname_emus %}. 更多信息请参阅“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
+Some IdPs support a protocol called SCIM, which can automatically provision or deprovision access on {% data variables.product.product_name %} when you make changes on your IdP. With SCIM, you can simplify administration as your team grows, and you can quickly revoke access to accounts. SCIM is available for individual organizations on {% data variables.product.product_name %}, or for enterprises that use {% data variables.product.prodname_emus %}. For more information, see "[About SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)."
 {% endif %}
 
 {% ifversion ghes %}
@@ -128,7 +127,7 @@ Another option is to generate SSH keys on a hardware security key. You could use
 Hardware-backed SSH keys are quite secure, but the hardware requirement might not work for some organizations. An alternative approach is to use SSH keys that are only valid for a short period of time, so even if the private key is compromised it can't be exploited for very long. This is the concept behind running your own SSH certificate authority. While this approach gives you a lot of control over how users authenticate, it also comes with the responsibility of maintaining an SSH certificate authority yourself. For more information, see "[About SSH certificate authorities](/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities)."
 {% endif %}
 
-## 后续步骤
+## Next steps
 
 - "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)"
 
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
index 21461fe8ea..59d354bb33 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds.md
@@ -1,8 +1,8 @@
 ---
-title: Best practices for securing your build system
-shortTitle: Securing builds
+title: 保护构建系统的最佳做法
+shortTitle: 保护构建
 allowTitleToDifferFromFilename: true
-intro: Guidance on how to protect the end of your supply chain—the systems you use to build and distribute artifacts.
+intro: 有关如何保护供应链末端（用于构建和分发构件的系统）的指南。
 versions:
   fpt: '*'
   ghec: '*'
@@ -15,48 +15,48 @@ topics:
   - CD
 ---
 
-## About this guide
+## 关于本指南
 
-This guide describes the highest impact changes you can make to improve the security of your build systems. Each section outlines a change you can make to your processes to improve security. The highest impact changes are listed first.
+本指南介绍为提高构建系统的安全性而可以进行的影响最大的更改。 每个部分都概述了为提高安全性而可以对流程进行的更改。 影响最大的更改列在最前面。
 
-## What's the risk?
+## 风险是什么？
 
-Some attacks on software supply chains target the build system directly. If an attacker can modify the build process, they can exploit your system without the effort of compromising personal accounts or code. It's important to make sure that you don't forget to protect the build system as well as personal accounts and code.
+对软件供应链的一些攻击直接针对构建系统。 如果攻击者可以修改构建过程，他们就可以利用您的系统，而无需攻击个人帐户或代码。 请务必确保不要忘记保护构建系统以及个人帐户和代码。
 
-## Secure your build system
+## 保护构建系统
 
-There are several security capabilities a build system should have:
+构建系统应具有以下几种安全功能：
 
-1. The build steps should be clear and repeatable.
+1. 构建步骤应清晰且可重复。
 
-2. You should know exactly what was running during the build process.
+2. 您应该确切地知道在构建过程中运行的内容。
 
-3. Each build should start in a fresh environment, so a compromised build doesn't persist to affect future builds.
+3. 每个构建都应在新的环境中启动，这样受损的构建不会持续影响将来的构建。
 
-{% data variables.product.prodname_actions %} can help you meet these capabilities. Build instructions are stored in your repository, alongside your code. You choose what environment your build runs on, including Windows, Mac, Linux, or runners you host yourself. Each build starts with a fresh virtual environment, making it difficult for an attack to persist in your build environment.
+{% data variables.product.prodname_actions %} 可以帮助您满足这些功能。 构建说明与代码一起存储在存储库中。 您可以选择在哪个环境中运行构建，包括 Windows、Mac、Linux 或您自己托管的运行器。 每个构建都从一个新的虚拟环境开始，这使得攻击很难在构建环境中持续存在。
 
-In addition to the security benefits, {% data variables.product.prodname_actions %} lets you trigger builds manually, periodically, or on git events in your repository for frequent and fast builds.
+除了安全优势之外， {% data variables.product.prodname_actions %} 还允许您手动、定期或在存储库中的 git 事件上触发构建，以实现频繁、快速的构建。
 
-{% data variables.product.prodname_actions %} is a big topic, but a good place to get started is "[Understanding GitHub Actions](/actions/learn-github-actions/understanding-github-actions)," as well as "[Choosing GitHub-hosted runners](/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners)," and "[Triggering a workflow](/actions/using-workflows/triggering-a-workflow)."
+{% data variables.product.prodname_actions %} 是一个很大的话题，但良好的开始是“[了解 GitHub Actions](/actions/learn-github-actions/understanding-github-actions)”以及“[选择 GitHub 托管的运行器](/actions/using-workflows/workflow-syntax-for-github-actions#choosing-github-hosted-runners)”和“[触发工作流程](/actions/using-workflows/triggering-a-workflow)”。
 
-## Sign your builds
+## 对构建签名
 
-After your build process is secure, you want to prevent someone from tampering with the end result of your build process. A great way to do this is to sign your builds. When distributing software publicly, this is often done with a public/private cryptographic key pair. You use the private key to sign the build, and you publish your public key so users of your software can verify the signature on the build before they use it. If the bytes of the build are modified, the signature will not verify.
+在构建过程安全之后，你希望防止有人篡改构建过程的最终结果。 执行此操作的好方法是对内部版本签名。 公开分发软件时，通常使用公共/私有加密密钥对来完成此操作。 使用私钥对构建签名，并发布公钥，以便软件用户可以在使用构建之前验证上面的签名。 如果修改了构建的字节，则不会验证签名。
 
-How exactly you sign your build will depend on what sort of code you're writing, and who your users are. Often it's difficult to know how to securely store the private key. One basic option here is to use {% data variables.product.prodname_actions %} encrypted secrets, although you'll need to be careful to limit who has access to those {% data variables.product.prodname_actions %} workflows. {% ifversion fpt or ghec %}If your private key is stored in another system accessible over the public internet (like Microsoft Azure, or HashiCorp Vault), a more advanced option is to authenticate with OpenID Connect, so you don't have to share secrets across systems.{% endif %} If your private key is only accessible from a private network, another option is to use self-hosted runners for {% data variables.product.prodname_actions %}.
+如何对构建签名取决于您编写的代码类型以及用户是谁。 通常很难知道如何安全地存储私钥。 此处的一个基本选项是使用 {% data variables.product.prodname_actions %} 加密机密，但您需要小心地限制谁有权访问这些 {% data variables.product.prodname_actions %} 工作流程。 {% ifversion fpt or ghec %}如果您的私钥存储在可通过公共互联网访问的另一个系统中（如 Microsoft Azure 或 HashiCorp Vault），则更高级的选择是使用 OpenID Connect 进行身份验证，因此您不必在系统之间共享机密。{% endif %} 如果您的私钥只能从专用网络访问，则另一种选择是对 {% data variables.product.prodname_actions %} 使用自托管运行器。
 
-For more information, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)"{% ifversion fpt or ghec %}, "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)",{% endif %} and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
+更多信息请参阅“[加密机密](/actions/security-guides/encrypted-secrets){% ifversion fpt or ghec %}”、“[关于使用 OpenID Connect 进行安全强化](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)”、{% endif %} 和“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)”。
 
-## Harden security for {% data variables.product.prodname_actions %}
+## 强化 {% data variables.product.prodname_actions %} 的安全性
 
-There are many further steps you can take to additionally secure {% data variables.product.prodname_actions %}. In particular, be careful when evaluating third-party workflows, and consider using `CODEOWNERS` to limit who can make changes to your workflows.
+您可以采取许多其他步骤来进一步保护 {% data variables.product.prodname_actions %}。 特别是，在评估第三方工作流程时要小心，并考虑使用 `CODEOWNERS` 来限制谁可以对您的工作流进行更改。
 
-For more information, see "[Security hardening for GitHub Actions](/actions/security-guides/security-hardening-for-github-actions);" particularly "[Using third-party actions](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)" and "[Using `CODEOWNERS` to monitor changes](/actions/security-guides/security-hardening-for-github-actions#using-codeowners-to-monitor-changes)."
+更多信息请参阅“[GitHub 操作的安全性强化](/actions/security-guides/security-hardening-for-github-actions)”，特别是“[使用第三方操作](/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)”和“[使用 `CODEOWNERS` 监控更改](/actions/security-guides/security-hardening-for-github-actions#using-codeowners-to-monitor-changes)”。
 
 ## 后续步骤
 
-- "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)"
+- “[保护您的端到端供应链](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)”
 
-- "[Best practices for securing accounts](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)"
+- “[保护帐户的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)”
 
-- "[Best practices for securing code in your supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)"
+- “[保护供应链中代码的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-code)”
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
index f78ce517b6..0c8c892f90 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/end-to-end-supply-chain/securing-code.md
@@ -16,11 +16,11 @@ topics:
   - Secret scanning
 ---
 
-## About this guide
+## 关于本指南
 
-This guide describes the highest impact changes you can make to improve the security of your code. Each section outlines a change you can make to your processes to improve security. The highest impact changes are listed first.
+This guide describes the highest impact changes you can make to improve the security of your code. 每个部分都概述了为提高安全性而可以对流程进行的更改。 影响最大的更改列在最前面。
 
-## What's the risk?
+## 风险是什么？
 
 Key risks in the development process include:
 
@@ -112,8 +112,8 @@ Insecure code patterns are often difficult for reviewers to spot unaided. In add
 
 ## 后续步骤
 
-- "[Securing your end-to-end supply chain](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)"
+- “[保护您的端到端供应链](/code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview)”
 
-- "[Best practices for securing accounts](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)"
+- “[保护帐户的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts)”
 
-- "[Best practices for securing your build system](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)"
+- “[保护构建系统的最佳实践](/code-security/supply-chain-security/end-to-end-supply-chain/securing-builds)”
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 0b8784ef89..bde0bcab93 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -50,3 +50,17 @@ redirect_from:
 
 启用依赖关系图时，依赖项审查功能可用。 更多信息请参阅“{% ifversion ghec %}[启用依赖关系图](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph){% elsif ghes %}[为企业启用依赖关系图](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise){% endif %}”。
 {% endif %}
+
+{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6396 %}
+## 依赖项审查实施
+
+{% data reusables.dependency-review.dependency-review-action-beta-note %}
+
+可以使用存储库中的依赖项审查 GitHub 操作对拉取请求强制执行依赖项审查。 该操作将扫描由拉取请求中的包版本更改是否引入有漏洞的依赖项版本，并向您示警相关的安全漏洞。 这便于您更好地了解拉取请求中发生的变化，并有助于防止将漏洞添加到存储库中。 更多信息请参阅 [`dependency-review-action`](https://github.com/actions/dependency-review-action)。
+
+![依赖项审查操作示例](/assets/images/help/graphs/dependency-review-action.png)
+
+依赖项审查 GitHub 操作检查在发现任何易受攻击的包时会失败，但只有在存储库所有者要求在合并之前通过检查时，才会阻止合并拉取请求。 更多信息请参阅“[关于受保护分支](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging)”。
+
+该操作使用依赖项审查 REST API 来获取基本提交和头部提交之间的依赖项更改差异。 您可以使用依赖项审查 API 来获取存储库上任意两个提交之间的依赖项更改差异（包括漏洞数据）。 更多信息请参阅“[依赖项审查](/rest/reference/dependency-graph#dependency-review)”。
+{% endif %}
diff --git a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
index abb404920a..68c739fb17 100644
--- a/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
+++ b/translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
@@ -76,7 +76,7 @@ shortTitle: 探索依赖项
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. 阅读有关授予 {% data variables.product.product_name %} 只读访问仓库数据的消息，以启用依赖关系图，然后在“Dependency Graph（依赖关系图）”旁边单击 **Enable（启用）**。 ![依赖关系图的"启用"按钮](/assets/images/help/repository/dependency-graph-enable-button.png)
 
 您可以随时单击 Security & analysis（安全性和分析）选项卡上“Dependency Graph（依赖关系图）”旁边的 **Disable（禁用）**来禁用依赖关系图。
@@ -98,7 +98,7 @@ shortTitle: 探索依赖项
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. 在“Code security and analysis（代码安全和分析）”下，单击“Used by counter（使用者计数）”部分中的下拉菜单并选择一个包。 ![选择"使用者"包](/assets/images/help/repository/choose-used-by-package.png)
 
 {% endif %}
diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
index 36de102773..b8bad48cf3 100644
--- a/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
+++ b/translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md
@@ -56,6 +56,8 @@ shortTitle: 代码空间中的安全性
 
 如果需要连接到在代码空间内运行的服务（如开发 Web 服务器），则可以配置端口转发以使该服务在互联网上可用。
 
+组织所有者可以限制公开或在组织内提供转发端口的能力。 更多信息请参阅“[限制转发端口的可见性](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)”。
+
 **私密转发端口**：可在互联网上访问，但只有代码空间创建者在向 {% data variables.product.product_name %} 验证后才可访问它们。
 
 **组织内公开转发的端口**：在通过身份验证后，可在互联网上访问，但只能由与代码空间相同的组织的成员访问 {% data variables.product.product_name %}。
diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
index a2df7f1f7e..0cbb7f6298 100644
--- a/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
+++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md
@@ -25,6 +25,12 @@ When an application running inside a codespace prints output to the terminal tha
 
 You can also forward a port manually, label forwarded ports, share forwarded ports with members of your organization, share forwarded ports publicly, and add forwarded ports to the codespace configuration.
 
+{% note %}
+
+**Note**: {% data reusables.codespaces.restrict-port-visibility %}
+
+{% endnote %}
+
 ## Forwarding a port
 
 You can manually forward a port that wasn't forwarded automatically.
@@ -85,12 +91,18 @@ To see details of forwarded ports enter `gh codespace ports` and then choose a c
 
 {% note %}
 
-**Note:** You can only make a port private to an organization if your organization uses {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}. This feature is not currently available in the beta version of {% data variables.product.prodname_codespaces %}.
+**Note:** You can only make a port private to an organization if your organization uses {% data variables.product.prodname_team %} or {% data variables.product.prodname_ghe_cloud %}.
 
 {% endnote %}
 
 If you want to share a forwarded port with others, you can either make the port private to your organization or make the port public. After you make a port private to your organization, anyone in the organization with the port's URL can view the running application. After you make a port public, anyone who knows the URL and port number can view the running application without needing to authenticate.
 
+{% note %}
+
+**Note:** Your choice of port visibility options may be limited by a policy configured for your organization. For more information, see "[Restricting the visibility of forwarded ports](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)."
+
+{% endnote %}
+
 {% webui %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
@@ -105,7 +117,7 @@ If you want to share a forwarded port with others, you can either make the port
 {% vscode %}
 
 {% data reusables.codespaces.navigate-to-ports-tab %}
-1. Right click the port you want to share, then click **Make Public**.
+1. Right click the port that you want to share, select the "Port Visibility" menu, then click **Private to Organization** or **Public**.
   ![Option to make port public in right-click menu](/assets/images/help/codespaces/make-public-option.png)
 1. To the right of the local address for the port, click the copy icon.
   ![Copy icon for port URL](/assets/images/help/codespaces/copy-icon-port-url.png)
diff --git a/translations/zh-CN/content/codespaces/getting-started/quickstart.md b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
index c32e2a2937..277fa3444d 100644
--- a/translations/zh-CN/content/codespaces/getting-started/quickstart.md
+++ b/translations/zh-CN/content/codespaces/getting-started/quickstart.md
@@ -41,7 +41,7 @@ redirect_from:
 
     如果按照其他应用程序类型进行操作，请为该项目输入相应的启动命令。
 
-2. 当应用程序启动时，代码空间会识别运行应用程序的端口，并显示转发该端口的提示，以便您可以连接到该端口。
+2. 当应用程序启动时，代码空间会识别运行应用程序的端口，并显示提示，让您知道它已被转发。
 
   ![端口转发信息框](/assets/images/help/codespaces/quickstart-port-toast.png)
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
index 0924962c6c..35b017f6c8 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/index.md
@@ -14,6 +14,7 @@ children:
   - /managing-repository-access-for-your-organizations-codespaces
   - /reviewing-your-organizations-audit-logs-for-codespaces
   - /restricting-access-to-machine-types
+  - /restricting-the-visibility-of-forwarded-ports
 shortTitle: 管理组织
 ---
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
index 5056056ded..e65db28571 100644
--- a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-access-to-machine-types.md
@@ -20,7 +20,7 @@ topics:
 
 ### 设置计算机类型约束时的行为
 
-如果存在不再符合已定义的策略的现有代码空间，则这些代码空间将继续运行，直到超时。 当用户尝试恢复代码空间时，将显示一条消息，告知他们此组织不再允许当前选择的计算机类型，并提示他们选择备用计算机类型。
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. 当用户尝试恢复代码空间时，将显示一条消息，告知他们此组织不再允许当前选择的计算机类型，并提示他们选择备用计算机类型。
 
 如果删除组织中单个存储库的 {% data variables.product.prodname_codespaces %} 配置所需的更高规范的计算机类型，则无法为该存储库创建代码空间。 当有人尝试创建代码空间时，他们将看到一条消息，告诉他们没有有效的计算机类型可以满足存储库 {% data variables.product.prodname_codespaces %} 配置的要求。
 
diff --git a/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
new file mode 100644
index 0000000000..9f4386442c
--- /dev/null
+++ b/translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports.md
@@ -0,0 +1,83 @@
+---
+title: Restricting the visibility of forwarded ports
+shortTitle: Restricting port visibility
+intro: You can set constraints on the visibility options users can choose when they forward ports from codespaces in your organization.
+product: '{% data reusables.gated-features.codespaces %}'
+permissions: 'To manage access to port visibility constraints for the repositories in an organization, you must be an organization owner.'
+versions:
+  fpt: '*'
+  ghec: '*'
+type: how_to
+topics:
+  - Codespaces
+---
+
+## 概览
+
+Typically, within a codespace you are able to forward ports privately (only to yourself), to members of your organization, or publicly (to anyone with the URL). 更多信息请参阅“[在代码空间中转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)”。
+
+As an organization owner, you may want to configure constraints on the visibility options users can set when forwarding ports. For example, for security reasons, you may want to disallow public port forwarding. 为此，您可以在组织的 {% data variables.product.prodname_codespaces %} 设置中定义一个或多个策略。
+
+### Behavior when you set a port visibility constraint
+
+If there are existing codespaces that no longer conform to a policy you have defined, these codespaces will continue to operate until they are stopped or time out. When the user resumes the codespace, it will be subject to the policy constraints.
+
+{% note %}
+
+**Note**: You can't disable private port forwarding, as private port forwarding is required by {% data variables.product.prodname_codespaces %} to continue working as designed, for example to forward SSH on port 22.
+
+{% endnote %}
+
+### 设置组织范围和存储库特定的策略
+
+创建策略时，您可以选择是将其应用于组织中的所有存储库，还是仅应用于指定的存储库。 如果设置了组织范围的策略，则为各个存储库设置的任何策略都必须在组织级别设置的限制范围内。 Adding policies makes the choice of visibility options more, not less, restrictive.
+
+For example, you could create an organization-wide policy that restricts the visibility options to organization only. You can then set a policy for Repository A that disallows both public and organization visibility, which would result in only private port forwarding being available for this repository. Setting a policy for Repository A that allowed both public and organization would result in only organization visibility, because the organization-wide policy does not allow public visibility.
+
+If you add an organization-wide policy, you should set it to the most lenient visibility option that will be available for any repository in your organization. 然后，您可以添加特定于存储库的策略以进一步限制选择。
+
+## Adding a policy to limit the port visibility options
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+1. In the "Code, planning, and automation" section of the sidebar, select **{% octicon "codespaces" aria-label="The codespaces icon" %} {% data variables.product.prodname_codespaces %}** then click **Policies**.
+1. 在“Codespace policies（代码空间策略）”页面上，单击 **Create Policy（创建策略）**。
+1. 输入新策略的名称。
+1. Click **Add constraint** and choose **Port visibility**.
+
+   ![Add a constraint for port visibility](/assets/images/help/codespaces/add-constraint-dropdown-ports.png)
+
+1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the constraint
+
+   ![Edit the port visibility constraint](/assets/images/help/codespaces/edit-port-visibility-constraint.png)
+
+1. Clear the selection of the port visibility options (**Org** or **Public**) that you don't want to be available.
+
+   ![Choose the port visibility options](/assets/images/help/codespaces/choose-port-visibility-options.png)
+
+1. 在“Change policy target（更改策略目标）”区域中，单击下拉按钮。
+1. 选择 **All repositories（所有存储库）** 或 **Selected repositories（选定的存储库）**，以确定此策略将应用于哪些存储库。
+1. 如果选择了 **Selected repositories（所选仓库）**：
+   1. 单击 {% octicon "gear" aria-label="The settings icon" %}。
+
+      ![编辑策略的设置](/assets/images/help/codespaces/policy-edit.png)
+
+   2. 选择要应用此策略的存储库。
+   3. 在存储库列表的底部，单击 **Select repositories（选择存储库）**。
+
+      ![为此策略选择存储库](/assets/images/help/codespaces/policy-select-repos.png)
+
+1. 单击 **Save（保存）**。
+
+## 编辑策略
+
+1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
+1. 单击要编辑的策略的名称。
+1. 进行所需的更改，然后单击 **Save（保存）**。
+
+## 删除策略
+
+1. 显示“Codespace policies（代码空间策略）”页。 For more information, see "[Adding a policy to limit the port visibility options](#adding-a-policy-to-limit-the-port-visibility-options)."
+1. 单击要删除的策略右侧的删除按钮。
+
+   ![策略的删除按钮](/assets/images/help/codespaces/policy-delete.png)
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
index 3908ebdab3..9ddd19ff1c 100644
--- 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
@@ -1,7 +1,7 @@
 ---
-title: About Codespaces prebuilds
-shortTitle: About prebuilds
-intro: Codespaces prebuilds help to speed up the creation of new codespaces.
+title: 关于代码空间预构建
+shortTitle: 关于预构建
+intro: 代码空间预构建有助于加快新代码空间的创建速度。
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,31 +14,31 @@ product: '{% data reusables.gated-features.codespaces %}'
 
 ## 概览
 
-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.
+每当您将更改推送到存储库时，{% data variables.product.prodname_codespaces %} 都会使用 {% data variables.product.prodname_actions %} 自动更新您的预构建。
 
-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.
+当预构建可用于存储库的特定分支以及您所在的地区时，您将在计算机类型对话框中看到“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签，该标签在您创建代码空间并且多种计算机类型可用时显示。
 
-![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png)
+![用于选择计算机类型的对话框](/assets/images/help/codespaces/choose-custom-machine-type.png)
 
-## About billing for {% data variables.product.prodname_codespaces %} prebuilds
+## 关于 {% data variables.product.prodname_codespaces %} 预构建的计费
 
-{% 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)."
+{% data reusables.codespaces.billing-for-prebuilds %} 有关 {% data variables.product.prodname_codespaces %} 存储定价的详细信息，请参阅“[关于 {% 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.
+每次推送到具有预构建配置的分支都会导致运行 {% data variables.product.prodname_dotcom %} 管理的 Actions 工作流程来更新预构建模板。 对于给定的预构建配置，预构建工作流程的并发限制为一次运行一个工作流程，除非所做的更改会影响关联存储库的开发容器配置。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project)”。 如果运行已在进行中，则最近排队的工作流程运行将在当前运行完成后运行。
 
-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:
+例如，假设对具有预构建配置的分支快速连续进行 5 次推送。 在此情况下：
 
-* 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.
+* 将对第一次推送启动工作流程运行，以更新预构建模板。
+* 如果剩余的 4 个推送不影响开发容器配置，则工作流程将针对这些推送在“挂起”状态下排队。
 
-  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.
+  如果其余 4 个推送中的任何一个更改了开发容器配置，则服务不跳过该推送，而立即运行预构建创建工作流程，如果成功，则会相应地更新预构建。
 
-* 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. 
+* 第一次运行完成后，将为推送 2、3 和 4 运行工作流程，最后排队的工作流程（对于推送 5）将运行并更新预构建模板。 
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
index 24a9e27e6d..c9f811d11d 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: 配置预构建
+shortTitle: 配置预构建
+intro: 您可以将项目配置为每次将更改推送到存储库时自动预构建代码空间。
 versions:
   fpt: '*'
   ghec: '*'
@@ -15,79 +15,79 @@ permissions: People with admin access to a repository can configure prebuilds fo
 
 {% 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)”。
+从启用了预构建的基础分支创建的任何分支通常也会在代码空间创建期间分配一个预构建。 如果分支上的开发容器与基本分支上的开发容器相同，则会出现这种情况。 这是因为具有相同开发容器配置的分支的大多数预构建配置都相同，因此开发人员也可以从这些分支上更快的代码空间创建时间中受益。 更多信息请参阅“[开发容器简介](/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.
+通常，在为分支配置预构建时，预构建将可用于该分支的 {% data variables.product.prodname_codespaces %} 计算机类型。 但是，如果存储库大于 32 GB，则预构建将不适用于 2 核和 4 核计算机类型，因为它们提供的存储限制为 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)”。
+在为项目配置预构建之前，必须满足以下条件：
+* 必须为您的组织启用 {% data variables.product.prodname_github_codespaces %}。 更多信息请参阅“[为组织启用 {% data variables.product.prodname_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization)”。
+* 必须为您的仓库启用 {% data variables.product.prodname_actions %}。 每个预构建配置都需要能够触发关联的操作工作流程。 更多信息请参阅“[管理仓库的 {% 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**.
+1. 在边栏的“Code & automation（代码和自动化）”部分中，单击 **{% octicon "codespaces" aria-label="The Codespaces icon" %}{% data variables.product.prodname_codespaces %}**。
+1. 在“Prebuild configuration（预构建配置）”下，单击 **Set up prebuild（设置预构建）**。
 
-   ![The 'Set up prebuilds' button](/assets/images/help/codespaces/prebuilds-set-up.png)
+   ![“设置预构建”按钮](/assets/images/help/codespaces/prebuilds-set-up.png)
 
-1. Choose the branch for which you want to set up a prebuild.
+1. 选择要为其设置预构建的分支。
 
-   ![The Branch drop-down menu](/assets/images/help/codespaces/prebuilds-choose-branch.png)
+   ![分支下拉菜单](/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.
+   **注意**：从启用了预构建的基本分支创建的任何分支通常也会获得预构建。 例如，如果为存储库的默认分支启用预构建，则在大多数情况下，基于默认分支的分支也将获得预构建。
 
    {% 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**.
+1. 选择要在其中设置预构建的区域。 开发人员必须位于您选择的区域中，才能从预构建创建代码空间。 或者，选择 **All regions（所有区域）**。
 
-   ![The region selection options](/assets/images/help/codespaces/prebuilds-regions.png)
+   ![区域选择选项](/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)."
+   * 每个区域的预构建模板将产生单独的费用。 因此，您应仅为已知将使用预构建的区域启用预构建。 更多信息请参阅“[关于 {% data variables.product.prodname_codespaces %} 预构建](/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds#about-billing-for-codespaces-prebuilds)”。
+   * 开发人员可以为 {% data variables.product.prodname_codespaces %} 设置其默认区域，这样您就可以为较少的区域启用预构建。 有关详细信息，请参阅“[设置 {% 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.
+   预构建配置列在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上。 {% data variables.product.prodname_actions %} 工作流程将排队，然后运行以根据您选择的分支在指定的区域中创建预构建模板。
 
    {% 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)."
+   **注意**：默认情况下，预构建配置的 {% data variables.product.prodname_actions %} 工作流程只能访问其自己的存储库中的资源。 如果您的项目使用存储库外部的资源，则需要设置 `CODESPACES_PREBUILD_TOKEN` 密钥以授予所需的访问权限。 更多信息请参阅“[允许预构建访问外部资源](/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.
+默认情况下，预构建配置的 {% data variables.product.prodname_actions %} 工作流程只能访问其自己的存储库内容。 如果项目需要访问外部资源来构建开发环境，则需要设置具有相应访问范围的个人访问令牌 (PAT)。
 
-For more information, see “[Allowing a prebuild to access external resources](/codespaces/prebuilding-your-codespaces/managing-prebuilds#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)."
+要允许预构建过程访问创建开发环境所需的环境变量，您可以将这些变量设置为 {% data variables.product.prodname_codespaces %} 存储库机密或 {% 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)”和“[为组织添加机密](/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)."
+以这种方式创建的 {% data variables.product.prodname_codespaces %} 机密将由从此存储库创建代码空间的任何人都可以访问。 如果您不希望这样做，也可以设置 `CODESPACES_PREBUILD_TOKEN` 密钥。 `CODESPACES_PREBUILD_TOKEN` 密钥仅用于预构建，其值在用户的代码空间中不可访问。 更多信息请参阅“[允许预构建访问外部资源](/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)."
+您可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时的过程作为预构建模板创建的一部分包括在内。 更多信息请参阅 Visual Studio Code 文档“[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.
+`onCreateCommand` 仅在创建预构建模板时运行一次，而 `updateContentCommand` 在模板创建和后续模板更新时运行。 增量构建应包含在 `updateContentCommand` 中，因为它们表示项目的源代码，并且需要包含在每个预构建模板更新中。
 
 ## 延伸阅读
 
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/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
index e726b2f76f..cba7bdc3f7 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/index.md
@@ -1,6 +1,6 @@
 ---
-title: Prebuilding your codespaces
-intro: 'To speed up codespace creation, you can configure your project to prebuild codespaces for specific branches in specific regions.'
+title: 预构建代码空间
+intro: 为加快代码空间的创建，可以配置项目为特定区域中的特定分支预构建代码空间。
 product: '{% data reusables.gated-features.codespaces %}'
 versions:
   fpt: '*'
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
index 90fb80ae92..b827292928 100644
--- a/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md
@@ -1,7 +1,7 @@
 ---
-title: Managing prebuilds
-shortTitle: Manage prebuilds
-intro: 'You can review, modify, and delete the prebuild configurations for your repository.'
+title: 管理预构建
+shortTitle: 管理预构建
+intro: 您可以查看、修改和删除存储库的预构建配置。
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,96 +14,96 @@ 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.
+您配置的预构建是使用 {% data variables.product.prodname_actions %} 工作流程创建和更新的，由 {% data variables.product.prodname_codespaces %} 服务管理。
 
-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."
+### 查看预构建的进度
+您可以查看在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上设置的每个预构建配置的最新工作流程运行当前状态。 例如，“正在运行”或“上次在 1 小时前运行”。
 
-To see the log output for the latest prebuild workflow run, click **See output**.
+要查看最新预构建工作流程运行的日志输出，请单击 **See output（查看输出）**。
 
-![The 'See output' button](/assets/images/help/codespaces/prebuilds-see-output.png)
+![“查看输出”按钮](/assets/images/help/codespaces/prebuilds-see-output.png)
 
-This displays the output of the most recent run of the workflow in the **Actions** tab.
+这将在 **Actions（操作）**选项卡中显示最近运行的工作流程的输出。
 
-![The prebuild workflow output](/assets/images/help/codespaces/prebuilds-log-output.png)
+![预构建工作流程输出](/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.
+或者，要查看与指定分支关联的所有预构建工作流程运行，请单击省略号按钮，然后从下拉菜单中选择 **View runs（查看运行）**。
 
-![The 'View runs' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-view-runs.png)
+![下拉菜单中的“查看运行”选项](/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)
+![工作流程运行历史记录](/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**.
+1. 在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上，单击要编辑的预构建配置右侧的省略号。
+1. 在下拉菜单中，单击 **Edit（编辑）**。
 
-   ![The 'Edit' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-edit.png)
+   ![下拉菜单中的“编辑”选项](/assets/images/help/codespaces/prebuilds-edit.png)
 
-1. Make the required changes to the prebuild configuration, then click **Update**.
+1. 对预构建配置进行所需的更改，然后单击 **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**.
+1. 在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上，单击要删除的预构建配置右侧的省略号。
+1. 在下拉菜单中，单击 **Delete（删除）**。
 
-   ![The 'Delete' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-delete.png)
+   ![下拉菜单中的“删除”选项](/assets/images/help/codespaces/prebuilds-delete.png)
 
-1. Click **OK** to confirm the deletion.
+1. 单击 **OK（确定）**以确认删除。
 
-### 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**.
+1. 在存储库设置的 {% data variables.product.prodname_codespaces %} 页面上，单击要触发其工作流程的预构建配置右侧的省略号。
+1. 在下拉菜单中，单击 **Manually trigger（手触发）**。
 
-   ![The 'Manually trigger' option in the drop-down menu](/assets/images/help/codespaces/prebuilds-manually-trigger.png)
+   ![下拉菜单中的“手动触发”选项](/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.
+默认情况下，预构建配置的 {% data variables.product.prodname_actions %} 工作流程只能访问其自己的存储库内容。 您的项目可能会使用其他资源来构建开发环境，例如其他存储库中的文件、包、GHCR 映像和 API。 要允许预构建安装程序访问这些资源，需要创建一个新的个人帐户，然后使用此帐户创建具有适当作用域的个人访问令牌 (PAT)。
 
-1. Create a new personal account on {% data variables.product.prodname_dotcom %}.
+1. 在 {% 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)."
+   **警告**：虽然您可以使用现有的个人帐户生成 PAT，但我们强烈建议您创建一个只能访问方案所需目标存储库的新帐户。 这是因为访问令牌的 `repository` 权限授予访问对帐户有权访问的所有存储库。 更多信息请参阅“[注册新的 GitHub 帐户](/get-started/signing-up-for-github/signing-up-for-a-new-github-account)”和“[ {% 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)”。
+1. 向新帐户授予对所需存储库的读取访问权限。 更多信息请参阅“[管理个人对组织仓库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)”。
+1. 登录到新帐户时，创建 `repo` 范围的 PAT。 （可选）如果预构建需要从 {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} 下载包，还要选择 `read:packages` 作用域。 更多信息请参阅“[创建个人访问令牌](/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)
+   ![为 PAT 选择的 'repo' 和 'packages' 作用域](/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)”。
+   如果预构建将使用 {% data variables.product.company_short %} {% data variables.product.prodname_container_registry %} 中的软件包，则需要向新帐户授予对软件包的访问权限，或者将软件包配置为继承要预构建的存储库的访问权限。 更多信息请参阅“[配置包的访问控制和可见性](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)”。
+{% ifversion ghec %}1. 授权令牌与 SAML 单点登录 (SSO) 一起使用，以便它可以访问启用了 SSO 的组织所拥有的存储库。 更多信息请参阅“[授权个人访问令牌用于 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)
+   ![用于为 PAT 配置 SSO 的按钮](/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)."
+1. 复制令牌字符串。 您将此密钥分配给 {% data variables.product.prodname_codespaces %} 存储库机密。
+1. 重新登录到对存储库具有管理员访问权限的帐户。
+1. 在要为其创建 {% data variables.product.prodname_codespaces %} 预构建的存储库中，创建一个名为 `CODESPACES_PREBUILD_TOKEN` 的新 {% data variables.product.prodname_codespaces %} 存储库机密，为其提供您创建和复制的令牌值。 更多信息请参阅“[管理用于 {% 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.
+PAT 将用于为存储库创建的所有后续预构建模板。 与其他 {% data variables.product.prodname_codespaces %} 存储库机密不同， `CODESPACES_PREBUILD_TOKEN` 机密仅用于预构建，不可用于从存储库创建的代码空间。
 
 ## 延伸阅读
 
-- "[Troubleshooting prebuilds](/codespaces/troubleshooting/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
index 452367610f..2a2ebcbf2d 100644
--- 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
@@ -1,8 +1,8 @@
 ---
-title: Testing dev container configuration changes on a prebuild-enabled branch
-shortTitle: Test dev container changes
+title: 在启用了预构建的分支上测试开发容器配置更改
+shortTitle: 测试开发容器更改
 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.
+intro: 更改为预构建启用的分支的开发容器配置时，应在代码空间中测试所做的更改。
 versions:
   fpt: '*'
   ghec: '*'
@@ -16,20 +16,20 @@ permissions: People with write permissions to a repository can create or edit th
 
 {% 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.
+1. 从要更改其开发容器的预构建启用分支创建代码空间。 更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace#creating-a-codespace)”。
+1. 在代码空间中，检出测试分支。 更多信息请参阅“[在代码空间中使用源控制](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace#creating-or-switching-branches)”。
+1. 对开发容器配置进行所需的更改。
+1. 通过重新构建容器来应用更改。 更多信息请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/configuring-codespaces-for-your-project#applying-changes-to-your-configuration)”。
+1. 在一切正常之后，我们还建议从测试分支创建一个新的代码空间，以确保一切正常。 然后，您可以将更改提交到存储库的默认分支或活动功能分支，从而触发该分支的预构建模板的更新。
 
    {% 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/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md
index 064c4c7c37..76f6c892d3 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md
@@ -19,3 +19,5 @@ shortTitle: 端口转发
 
 - 使用通知提示或点击终端中的 URL 打开转发的端口。 如果通过浏览器连接到代码空间，则在本地计算机中键入 `localhost:8000`（作为示例）将不起作用。
 - 确保检查应用程序是否仍在代码空间中运行。 如果代码空间在一段时间不活动后停止，则需要确保在代码空间重新启动后重新启动应用程序。
+
+通常，您可以使转发的端口可公开访问，也可以在拥有存储库的组织内访问。 更多信息请参阅“[在代码空间中转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)”。 如果公共或组织可见性选项中的一个或两个选项不可用，则表示已配置组织级策略。 更多信息请参阅“[限制转发端口的可见性](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)”。
diff --git a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
index 8ecf1e23f9..b65c67b7b0 100644
--- a/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
+++ b/translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md
@@ -1,7 +1,7 @@
 ---
-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.
+title: 预构建疑难解答
+shortTitle: 代码空间预构建
+intro: 您可以使用预构建来加速代码空间的创建。 本文提供预构建常见问题的疑难解答步骤。
 versions:
   fpt: '*'
   ghec: '*'
@@ -14,46 +14,46 @@ 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)."
+有关 {% data variables.product.prodname_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.
+如果在创建代码空间时有多个计算机类型可用，则会显示一个对话框，供您选择计算机类型。 这将在提供预构建的机器类型旁边显示“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签。
 
-![The dialog box for choosing a machine type](/assets/images/help/codespaces/choose-custom-machine-type.png)
+![用于选择计算机类型的对话框](/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)."
+如果将 {% data variables.product.prodname_codespaces %} 编辑器首选项设置为“Visual Studio Code for Web”，则“设置代码空间”页面将显示消息“找到预构建的代码空间”（如果正在使用预构建）。 同样，如果您的编辑器首选项是“Visual Studio Code”，则当您创建新代码空间时，集成终端将包含消息“您正在使用由存储库的预构建配置定义的预构建代码空间”。 更多信息请参阅“[设置代码空间的默认编辑器](/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:
+创建代码空间后，可以通过在终端中运行以下 {% data variables.product.prodname_cli %} 命令来检查它是否是从预构建创建的：
 
 ```shell{:copy}
 gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
 ```
 
-This returns `true` if the codespace was created using a prebuild.
+如果代码是使用预构建创建的，将返回 `true`。
 
-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:
+或者，如果未安装 {% data variables.product.prodname_cli %} (`gh`)，则可以使用以下命令，如果代码空间是从预构建创建的，则该命令将返回 `createFromPrebuild` ：
 
 ```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.
+您可能会注意到，有时，当您从启用了预构建的分支创建新代码空间时，“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签不会显示在用于选择计算机类型的对话框中。 这意味着预构建当前不可用。
 
-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.
+每次推送到启用了预构建的分支时，都会更新预构建模板。 如果推送涉及对开发容器的更改，则在更新过程中，将从计算机类型对话框中删除“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签。 在此期间，您仍然可以在没有预构建模板的情况下创建代码空间。
 
-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:
+以下是检查特定分支是否未显示“{% octicon "zap" aria-label="The zap icon" %} 预构建就绪”标签的事项：
 
-* 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.
+* 确认此分支存在预构建配置。 如果您不是存储库管理员，则需要联系存储库管理员进行确认。
+* 确认预构建配置包括您的区域。
+* 检查最近是否将对开发容器配置的更改推送到启用了预构建的分支。 如果是这样，则必须等到为此推送运行的预构建工作流程完成，然后预构建才会再次可用。
+* 如果最近未进行任何配置更改，请转到存储库的“ **操作** ”选项卡，单击工作流程列表中的 **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} 预构建** ，然后检查分支的预构建工作流程运行是否成功。 如果工作流程的最新运行失败，并且其中一个或多个失败的运行包含对开发容器的更改，则关联分支将没有可用的预构建。
 
 ## 延伸阅读
 
-- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
-- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
+- “[配置预构建](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)”
+- “[管理预构建](/codespaces/prebuilding-your-codespaces/managing-prebuilds)”
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
index 5b37f1cf04..4bb1fe0ccd 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: 阻止用户访问组织
-intro: 组织所有者可阻止用户以解除该用户在组织仓库中进行协作的能力。
+intro: 组织所有者和版主可以阻止任何非组织成员的人协作处理组织的存储库。
 redirect_from:
   - /articles/blocking-a-user-from-your-organization
   - /github/building-a-strong-community/blocking-a-user-from-your-organization
@@ -12,7 +12,7 @@ topics:
 shortTitle: 阻止您的组织
 ---
 
-您可以从组织的设置中或从用户发表的特定评论中阻止用户。 在评论中阻止用户时，您可以选择向该用户发送通知，以告知他们已被阻止并说明原因。 否则，用户不会直接收到您已阻止他们的通知。 被阻止的用户仍然可以删除其现有内容。
+您可以从组织的设置中或从用户发表的特定评论中阻止非成员。 在评论中阻止用户时，您可以选择向该用户发送通知，以告知他们已被阻止并说明原因。 否则，用户不会直接收到您已阻止他们的通知。 被阻止的用户仍然可以删除其现有内容。
 
 阻止用户时，您可以选择无限期或在特定时间段内阻止他们。 如果在特定时间段内阻止某人，则所选时间结束后会自动解除对他们的阻止。 如果无限期阻止某人，您可以随时手动解除阻止。 更多信息请参阅“[解除阻止用户对组织的访问](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)”。
 
diff --git a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
index fb38a9b5b6..fd736d6808 100644
--- a/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
+++ b/translations/zh-CN/content/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization.md
@@ -1,6 +1,6 @@
 ---
 title: 取消阻止用户对组织的访问
-intro: 组织所有者可以取消阻止以前阻止的用户，恢复其对组织仓库的访问权限。
+intro: 组织所有者和版主可以取消阻止以前阻止的用户，恢复其对组织仓库的访问权限。
 redirect_from:
   - /articles/unblocking-a-user-from-your-organization
   - /github/building-a-strong-community/unblocking-a-user-from-your-organization
@@ -26,15 +26,15 @@ shortTitle: 从您的组织中解除阻止
 
 1. 导航到您要取消阻止其作者的评论。
 2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Unblock user（取消阻止用户）**。 ![显示取消阻止用户选项的水平烤肉串图标和评论审核菜单](/assets/images/help/repository/comment-menu-unblock-user.png)
-3. 要确认您想要取消阻止用户，请单击 **Okay（确定）**。
+3. 要确认您想要取消阻止用户，请单击 **OK（确定）**。
 
 ## 在组织设置中取消阻止用户
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.moderation-settings %}，然后单击“**阻止的用户**”。
-5. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png)
+{% data reusables.organizations.block_users %}
+1. 在“Blocked users（已阻止的用户）”下您想要取消阻止的用户旁边，单击 **Unblock（取消阻止）**。 ![取消阻止用户按钮](/assets/images/help/organizations/org-unblock-user-button.png)
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
index 993c0bba92..bdae6bbbe6 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-permissions: Organization owners can limit interactions in an organization.
+permissions: Organization owners and moderators can limit interactions in an organization.
 topics:
   - Community
 shortTitle: 限制组织中的交互
@@ -26,14 +26,17 @@ shortTitle: 限制组织中的交互
 
 在整个组织范围内启用活动限制时，无法对个别仓库启用或禁用交互限制。 有关限制单个仓库活动的更多信息，请参阅“[限制仓库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。
 
-组织所有者也可在特定的时间段内阻止用户。 在阻止到期后，该用户会自动解除阻止。 更多信息请参阅“[阻止用户访问组织](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)”。
+组织所有者和版主也可在特定的时间段内阻止用户。 在阻止到期后，该用户会自动解除阻止。 更多信息请参阅“[阻止用户访问组织](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)”。
 
 ## 限制组织中的交互
 
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-1. 在侧边栏的“Access（访问）”部分中，选择 **{% octicon "report" aria-label="The report icon" %} 主持** 然后点击 **Interaction limits（互动限制）**。
+1. _对于组织所有者：_在侧边栏的“Access（访问）”部分中，选择 **{% octicon "report" aria-label="The report icon" %} 版主** 然后点击 **Interaction limits（互动限制）**。
+
+   _对于组织版主：_ 在边栏中，单击“**Interaction limits（交互限制）**”。
+
 {% data reusables.community.set-interaction-limit %}
   ![临时交互限制选项](/assets/images/help/organizations/organization-temporary-interaction-limits-options.png)
 
@@ -42,3 +45,4 @@ shortTitle: 限制组织中的交互
 - "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 - "[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)"
 - "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- “[管理组织中的版主](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)”
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
index d08c39760a..6f1af7e207 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository.md
@@ -8,7 +8,7 @@ redirect_from:
 versions:
   fpt: '*'
   ghec: '*'
-permissions: People with admin permissions to a repository can temporarily limit interactions in that repository.
+permissions: 'People with admin permissions to a repository, and organization moderators, can temporarily limit interactions in that repository.'
 topics:
   - Community
 shortTitle: 限制仓库中的交互
@@ -28,7 +28,7 @@ shortTitle: 限制仓库中的交互
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. 在侧边栏的“Access（访问）”部分中，选择 **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} 主持选项**，然后点击 **Interaction limits（互动限制）**。
+1. 在侧边栏中，选择 **{% octicon "comment-discussion" aria-label="The comment-discussion icon" %} 主持选项**，然后点击 **Interaction limits（互动限制）**。
 {% data reusables.community.set-interaction-limit %}
   ![临时交互限制选项](/assets/images/help/repository/temporary-interaction-limits-options.png)
 
@@ -37,3 +37,4 @@ shortTitle: 限制仓库中的交互
 - "[管理个人对组织仓库的访问](/articles/managing-an-individual-s-access-to-an-organization-repository)"
 - "[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)"
 - "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
+- “[管理组织中的版主](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)”
diff --git a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
index 4c5cfd2b31..79e2972ffd 100644
--- a/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
+++ b/translations/zh-CN/content/communities/moderating-comments-and-conversations/managing-disruptive-comments.md
@@ -18,7 +18,7 @@ shortTitle: 管理评论
 
 ## 隐藏评论
 
-对仓库具有写入权限的任何人都可以隐藏议题、拉取请求及提交上的评论。
+{% ifversion fpt or ghec %}组织版主以及对存储库有写入权限的任何人{% else %}任何人{% endif %} 都可以隐藏对议题、拉取请求和提交的评论。
 
 如果评论偏离主题、已过期或已解决，您可能想要隐藏评论，以保持讨论重点或使拉取请求更易于导航和审查。 隐藏的评论已最小化，但对仓库具有读取权限的人员可将其展开。
 
@@ -35,7 +35,7 @@ shortTitle: 管理评论
 
 ## 取消隐藏评论
 
-对仓库具有写入权限的任何人都可以取消隐藏议题、拉取请求及提交上的评论。
+{% ifversion fpt or ghec %}组织版主以及对存储库有写入权限的任何人{% else %}任何人{% endif %} 都可以取消隐藏对议题、拉取请求和提交的评论。
 
 1. 导航到您要取消隐藏的评论。
 2. 在评论右上角，单击 **{% octicon "fold" aria-label="The fold icon" %} Show comment（显示评论）**。 ![显示评论文本](/assets/images/help/repository/hidden-comment-show.png)
@@ -82,3 +82,8 @@ shortTitle: 管理评论
 1. 导航到您要删除的评论。
 2. 在评论的右上角，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Delete（删除）**。 ![显示编辑、隐藏、删除和报告选项的水平烤肉串图标和评论调解菜单](/assets/images/help/repository/comment-menu.png)
 3. 也可以说明您删除了哪些评论，为什么要删除。
+
+{% ifversion fpt or ghec %}
+## 延伸阅读
+- “[管理组织中的版主](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)”
+{% endif %} 
diff --git a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
index e8fb6c26b7..ba223e520b 100644
--- a/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
+++ b/translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/about-community-management-and-moderation.md
@@ -17,6 +17,8 @@ shortTitle: 管理和调节
 
 {% data variables.product.prodname_dotcom %} 还为仓库维护员提供在他们自己的 {% data variables.product.prodname_dotcom_the_website %} 社区制定和执行更高行为标准的工具。
 
+组织所有者可以将组织成员指定为版主。 这使这些成员可以访问为组织所有者保留的审核功能。 更多信息请参阅“[管理组织中的版主](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)”。
+
 在为社区制定行为标准后，可以通过快速、公平地响应破坏性行为来促进营造一个愉快、高效的环境。 有效的调解能在社区中建立信任，让贡献者感受到安全和热情。
 
 ## 社区调解工具
diff --git a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
index bc149aade4..819c208778 100644
--- a/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
+++ b/translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository.md
@@ -79,7 +79,7 @@ shortTitle: 配置
 
 以下是 *config.yml* 文件的一个例子：
 
-```shell{:copy}
+```yaml{:copy}
 blank_issues_enabled: false
 contact_links:
   - name: {% data variables.product.prodname_gcf %}
diff --git a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
index a108fef8aa..1912d44edc 100644
--- a/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
+++ b/translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/configuring-and-customizing-github-desktop/configuring-a-default-editor.md
@@ -35,6 +35,8 @@ shortTitle: 配置默认编辑器
 - [CodeRunner](https://coderunnerapp.com/)
 - [SlickEdit](https://www.slickedit.com/)
 - [Xcode](https://developer.apple.com/xcode/)
+- [RStudio](https://rstudio.com/)
+- [Nova](https://nova.app/)
 - [Android Studio](https://developer.android.com/studio)
 
 {% endmac %}
@@ -48,10 +50,18 @@ shortTitle: 配置默认编辑器
 - [ColdFusion Builder](https://www.adobe.com/products/coldfusion-builder.html)
 - [Typora](https://typora.io/)
 - [SlickEdit](https://www.slickedit.com/)
+- [JetBrains IntelliJ Idea](https://www.jetbrains.com/idea/)
 - [JetBrains WebStorm](https://www.jetbrains.com/webstorm/)
 - [JetBrains PhpStorm](https://www.jetbrains.com/phpstorm/)
 - [JetBrains Rider](https://www.jetbrains.com/rider/)
+- [JetBrains CLion](https://www.jetbrains.com/clion/)
+- [JetBrains PyCharm](https://www.jetbrains.com/pycharm/)
+- [JetBrains RubyMine](https://www.jetbrains.com/rubymine/)
+- [JetBrains GoLand](https://www.jetbrains.com/go/)
+- [Android Studio](https://developer.android.com/studio)
+- [Brackets](http://brackets.io/)
 - [Notepad++](https://notepad-plus-plus.org/)
+- [RStudio](https://rstudio.com/)
 
 {% endwindows %}
 
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
index 1470bba1bc..848ae45182 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/about-discussions.md
@@ -9,19 +9,34 @@ versions:
 
 ## About {% data variables.product.prodname_discussions %}
 
-With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools.
+With {% data variables.product.prodname_discussions %}, the community for your project can create and participate in conversations within the project's repository or organization. Discussions empower a project's maintainers, contributors, and visitors to gather and accomplish the following goals in a central location, without third-party tools.
 
 - Share announcements and information, gather feedback, plan, and make decisions
 - Ask questions, discuss and answer the questions, and mark the discussions as answered
+- Create polls to gauge community opinion
 - Foster an inviting atmosphere for visitors and contributors to discuss goals, development, administration, and workflows
 
 ![Discussions tab for a repository](/assets/images/help/discussions/hero.png)
 
+You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization.
+
 You don't need to close a discussion like you close an issue or a pull request.
 
-If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+If a repository administrator or project maintainer enables {% data variables.product.prodname_discussions %} for a repository, anyone who visits the repository can create and participate in discussions for the repository. If an organization owner enables {% data variables.product.prodname_discussions %} for an organization, anyone who can view the source repository can create an organization discussion.
 
-For more information about management of discussions for your repository, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)."
+Repository administrators and project maintainers can manage discussions and discussion categories in a repository, and pin discussions to increase the visibility of the discussion. Moderators and collaborators can mark comments as answers, lock discussions, and convert issues to discussions. Similarly, for organization discussions, the role of a user in the source repository determines how a user can interact with organization discussions. For more information, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)."
+
+For more information about management of discussions, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
+
+## About polls
+
+You can create polls in the polls category to gauge interest in new ideas and project direction. Anyone with read access to your repository can create polls, vote in polls, and view their results. Logged out users can view the results of polls in public repositories.
+
+Polls require a question and at least two options. You can add a maximum of eight options and the options can contain a maximum of 128 characters. 
+
+Voters cannot change their vote. Editing a poll will reset any votes that have already been cast.
+
+For more information on creating polls, see "[Creating a poll](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion#creating-a-poll)."
 
 ## About discussion organization
 
@@ -33,7 +48,7 @@ For discussions with a question/answer format, an individual comment within the
 
 {% data reusables.discussions.about-announcement-format %}
 
-For more information, see "[Managing categories for discussions in your repository](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)."
+For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
 
 {% data reusables.discussions.you-can-label-discussions %}
 
@@ -43,9 +58,9 @@ As a community member or maintainer, start a discussion to ask a question or dis
 
 Participate in a discussion to ask and answer questions, provide feedback, and engage with the project's community. For more information, see "[Participating in a discussion](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)."
 
-You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)."
+You can spotlight discussions that contain important, useful, or exemplary conversations among members in the community. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
 
-{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions in your repository](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
+{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
 
 ## Sharing feedback
 
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
index 053eee32e6..190aabfe8e 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md
@@ -2,7 +2,7 @@
 title: 使用讨论与维护者协作
 shortTitle: 与维护者协作
 intro: '您可以通过在讨论中与项目的维护者沟通，为 {% data variables.product.product_name %} 项目的目标、计划、运行状况和社区做出贡献。'
-permissions: 'People with read access to a repository can start and participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}'
+permissions: 'People with read access to a repository can start and participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can start and participate in discussions and polls in the organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
   fpt: '*'
   ghec: '*'
@@ -15,7 +15,7 @@ versions:
 
 {% data reusables.discussions.about-categories-and-formats %} {% data reusables.discussions.about-announcement-format %}
 
-仓库管理员和项目维护员可以删除讨论。 更多信息请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)”。
+Repository administrators and project maintainers can delete a discussion in that repository. Similarly, administrators and maintainers of the source repository for an organization's discussions can delete a discussion in that organization. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)."
 
 {% data reusables.discussions.github-recognizes-members %} 这些成员出现在对项目讨论最有帮助的贡献者名单中。 随着项目的发展，您可以向社区的活动成员授予更高的访问权限。 更多信息请参阅“[向顶级贡献者授予更高权限](/discussions/guides/granting-higher-permissions-to-top-contributors)”
 
@@ -25,24 +25,30 @@ versions:
 
 ## 基本要求
 
-要在讨论中与维护者合作，仓库管理员或项目维护者必须为仓库启用 {% data variables.product.prodname_discussions %}。 更多信息请参阅“[为仓库启用或禁用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
+To collaborate with maintainers in repository discussions, a repository administrator or project maintainer must enable {% data variables.product.prodname_discussions %} for the repository. 更多信息请参阅“[为仓库启用或禁用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
+
+To collaborate with maintainers in organization discussions, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
 
 ## 开始讨论
 
 {% data reusables.discussions.starting-a-discussion %}
 
+## Starting a poll
+
+{% data reusables.discussions.starting-a-poll %}
+
 ## 过滤讨论列表
 
-您可以在仓库中搜索讨论并过滤讨论列表。 更多信息请参阅“[搜索讨论](/search-github/searching-on-github/searching-discussions)”。
+You can search for discussions and filter the list of discussions in a repository or organization. 更多信息请参阅“[搜索讨论](/search-github/searching-on-github/searching-discussions)”。
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 1. 在 **Search all discussions（搜索所有讨论）** 字段中输入搜索查询。 （可选）在搜索字段右侧，单击按钮以进一步过滤结果。 ![用于过滤讨论的搜索栏和按钮](/assets/images/help/discussions/search-and-filter-controls.png)
 1. 在讨论列表中，单击要查看的讨论。 ![讨论搜索结果](/assets/images/help/discussions/search-result.png)
 
 ## 将议题转换为讨论
 
-{% data reusables.discussions.you-can-convert-an-issue %}更多信息请参阅“[主持仓库中的讨论](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion#converting-an-issue-to-a-discussion)”。
+{% data reusables.discussions.you-can-convert-an-issue %} For more information, see "[Moderating discussions](/discussions/managing-discussions-for-your-community/moderating-discussions#converting-an-issue-to-a-discussion)."
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
index 121a59a05f..a537da8a45 100644
--- a/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
+++ b/translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md
@@ -1,7 +1,7 @@
 ---
 title: 参与讨论
 intro: '您可以在仓库的论坛中与社区和维护者交流 {% data variables.product.product_name %} 上的项目。'
-permissions: 'People with read access to a repository can participate in discussions in the repository. {% data reusables.enterprise-accounts.emu-permission-interact %}'
+permissions: 'People with read access to a repository can participate in discussions and polls in the repository. People with read access to the source repository for organization discussions can participate in discussions and polls in that organization. {% data reusables.enterprise-accounts.emu-permission-interact %}'
 versions:
   fpt: '*'
   ghec: '*'
@@ -13,20 +13,24 @@ shortTitle: 参与讨论
 
 {% data reusables.discussions.about-discussions %} 更多信息请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
 
-除了开始或查看讨论之外，您还可以对讨论作者的原始评论做出响应。 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。
+In addition to starting or viewing discussions and polls, you can comment in response to the original comment from the author of the discussion. 您还可以通过回复其他社区成员在讨论中进行的个人评论，以及使用表情符号对评论做出反应来创建评论线程。
 
 您可以阻止用户并报告破坏性内容，以便自己在 {% data variables.product.product_name %} 上保持一个安全愉快的环境。 更多信息请参阅“[保持您在 {% data variables.product.prodname_dotcom %} 上的安全](/communities/maintaining-your-safety-on-github)”。
 
 ## 基本要求
 
-必须对仓库启用 {% data variables.product.prodname_discussions %}，您才可以参与仓库中的讨论。 更多信息请参阅“[为仓库启用或禁用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
+{% data variables.product.prodname_discussions %} must be enabled for the repository or organization for you to participate in a discussion in the repository or organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)" and "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
 
 ## 创建讨论
 
 {% data reusables.discussions.starting-a-discussion %}
 
+## Creating a poll
+
+{% data reusables.discussions.starting-a-poll %}
+
 ## 将评论标记为答案
 
-对于仓库具有分类角色或更高角色的讨论作者和用户可以将评论标记为仓库中讨论的答案。
+对于仓库具有分类角色或更高角色的讨论作者和用户可以将评论标记为仓库中讨论的答案。 Similarly, discussion authors and users with the triage role or greater for the source repository for organization discussions can mark a comment as the answer to a discussion in the organization.
 
 {% data reusables.discussions.marking-a-comment-as-an-answer %}
diff --git a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
index c7f2aac9c6..d5365b3485 100644
--- a/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
+++ b/translations/zh-CN/content/discussions/guides/best-practices-for-community-conversations-on-github.md
@@ -10,11 +10,11 @@ versions:
 
 ## {% data variables.product.prodname_discussions %} 中的社区对话
 
-由于 {% data variables.product.prodname_discussions %} 是一个开放的论坛，因此有机会将非代码协作引入项目的仓库，并更快地收集各种反馈和想法。 您可以通过以下方式帮助推动富有成果的对话：
+Since {% data variables.product.prodname_discussions %} is an open forum, there is an opportunity to bring non-code collaboration into a project's repository or organization and gather diverse feedback and ideas more quickly. You can help drive a productive conversation in a number of ways.
 
 - 提出针对性的问题和后续问题，以收集具体反馈
-- 获取不同的体验并提炼到要点
-- 打开议题，根据对话采取行动（如果适用）
+- Capturing a diverse experience and distilling it down to main points
+- Opening an issue to take action based on the conversation, where applicable
 
 有关打开议题和交叉引用讨论的更多信息，请参阅“[从评论打开议题](/github/managing-your-work-on-github/opening-an-issue-from-a-comment)”。
 
@@ -22,18 +22,19 @@ versions:
 
 您可以创建和参与讨论、议题及拉取请求，具体取决于您希望进行的对话类型。
 
-您可以使用 {% data variables.product.prodname_discussions %} 讨论大局想法、集思广益，并在将项目提交到议题之前，先找出项目的具体细节，然后可以确定议题的范围。 {% data variables.product.prodname_discussions %} 在以下情况下对团队有用：
+You can use {% data variables.product.prodname_discussions %} to discuss big picture ideas, brainstorm, and develop a project's specific details before committing it to an issue, which can then be scoped. {% data variables.product.prodname_discussions %} 在以下情况下对团队有用：
 - 您处于项目的发现阶段，仍在了解您的团队希望由哪个主管领导
 - 您希望从更广泛的社区收集有关项目的反馈
 - 您希望将漏洞修复、功能请求和常规对话分开
+- You want to measure interest in new ideas and gauge community opinion using polls
+
+You might use repository discussions to discuss topics that are specific to the repository. If your project spans multiple repositories, you might use organization discussions to discuss topics that aren't specific to a single repository in your organization.
 
 议题适用于讨论项目的具体细节，如漏洞修复和计划的改进。 更多信息请参阅“[关于议题](/articles/about-issues)”。 拉取请求允许您直接评论提议的更改。 更多信息请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”和“[评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”。
 
-{% data reusables.organizations.team-discussions-purpose %} 更多信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。
-
 ## 遵守参与指南
 
-在打开讨论之前，检查仓库是否有参与指南。 CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
+Before you open a discussion in an open source repository, check to see if the repository has contributing guidelines. CONTRIBUTING 文件包含仓库维护员希望您如何向项目贡献想法的信息。
 
 更多信息请参阅“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 
diff --git a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md
similarity index 81%
rename from translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md
rename to translations/zh-CN/content/discussions/guides/finding-your-discussions.md
index 0ece2dd268..ce5e1de6dc 100644
--- a/translations/zh-CN/content/discussions/guides/finding-discussions-across-multiple-repositories.md
+++ b/translations/zh-CN/content/discussions/guides/finding-your-discussions.md
@@ -1,10 +1,12 @@
 ---
-title: 在多个仓库中查找讨论
-intro: 您可以轻松地访问您在多个仓库中创建或参与的每个讨论。
+title: Finding your discussions
+intro: You can easily access every discussion you've created or participated in.
 versions:
   fpt: '*'
   ghec: '*'
 shortTitle: 查找讨论
+redirect_from:
+  - /discussions/guides/finding-discussions-across-multiple-repositories
 ---
 
 
diff --git a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
index f5cbcccaa2..b097e3d9ce 100644
--- a/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
+++ b/translations/zh-CN/content/discussions/guides/granting-higher-permissions-to-top-contributors.md
@@ -14,13 +14,13 @@ shortTitle: 授予更高权限
 
 ## 第 1 步：审核您的 {% data variables.product.prodname_discussions %} 最大贡献者
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
-1. 将贡献者列表与其访问权限进行比较，看谁有资格主持讨论。
+1. Compare the list of contributors with their access permissions to the repository or, for organization discussions, to the source repository to see who qualifies to moderate the discussion.
 
 ## 第 2 步：审查 {% data variables.product.prodname_discussions %} 的权限级别
 
-对仓库具有分类权限的人可以通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持项目的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
+People with triage permissions for a repository can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, people with triage permissions for the source repository for organization discussions can moderate the organization's discussions. 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
 
 有关仓库权限级别和 {% data variables.product.prodname_discussions %} 的更多信息，请参阅“[组织的仓库权限级别](/organizations/managing-access-to-your-organizations-repositories/repository-permission-levels-for-an-organization)”。
 
diff --git a/translations/zh-CN/content/discussions/guides/index.md b/translations/zh-CN/content/discussions/guides/index.md
index 29938e262e..46eabf532e 100644
--- a/translations/zh-CN/content/discussions/guides/index.md
+++ b/translations/zh-CN/content/discussions/guides/index.md
@@ -7,7 +7,7 @@ versions:
   ghec: '*'
 children:
   - /best-practices-for-community-conversations-on-github
-  - /finding-discussions-across-multiple-repositories
+  - /finding-your-discussions
   - /granting-higher-permissions-to-top-contributors
 ---
 
diff --git a/translations/zh-CN/content/discussions/index.md b/translations/zh-CN/content/discussions/index.md
index 73e6c3843b..cfb7e452af 100644
--- a/translations/zh-CN/content/discussions/index.md
+++ b/translations/zh-CN/content/discussions/index.md
@@ -18,9 +18,9 @@ featuredLinks:
   popular:
     - /discussions/guides/granting-higher-permissions-to-top-contributors
     - /discussions/guides/best-practices-for-community-conversations-on-github
-    - /discussions/guides/finding-discussions-across-multiple-repositories
+    - /discussions/guides/finding-your-discussions
     - /discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions
-    - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
+    - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions
 changelog:
   label: discussions
 examples_source: data/product-examples/discussions/community-examples.yml
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
index e70233b26e..a6c5cde2d9 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/index.md
@@ -6,8 +6,8 @@ versions:
   fpt: '*'
   ghec: '*'
 children:
-  - /managing-discussions-in-your-repository
-  - /managing-categories-for-discussions-in-your-repository
+  - /managing-discussions
+  - /managing-categories-for-discussions
   - /moderating-discussions
   - /viewing-insights-for-your-discussions
 ---
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
similarity index 67%
rename from translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md
rename to translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
index 4efe5c3f79..1466007873 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md
@@ -1,11 +1,13 @@
 ---
-title: 管理仓库中讨论的类别
-intro: 您可以对仓库中的讨论进行分类，以组织社区成员的对话，也可为每个类别选择格式。
-permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository.
+title: Managing categories for discussions
+intro: 'You can categorize discussions to organize conversations for your community members, and you can choose a format for each category.'
+permissions: Repository administrators and people with write or greater access to a repository can manage categories for discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage categories for discussions in the organization.
 versions:
   fpt: '*'
   ghec: '*'
 shortTitle: 管理类别
+redirect_from:
+  - /discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository
 ---
 
 
@@ -19,17 +21,18 @@ shortTitle: 管理类别
 
 ## 默认类别
 
-| 分类      | 目的                  | 格式    |
-|:------- |:------------------- |:----- |
-| 📣 公告    | 项目维护者提供的最新消息和新闻     | 公告    |
-| #️⃣ 常规  | 与项目相关的任何及所有内容       | 开放式讨论 |
-| 💡 想法    | 改变或改进项目的想法          | 开放式讨论 |
-| 🙏 问答    | 供社区回答的问题，使用问题/回答的形式 | 问题及解答 |
-| 🙌 展示和说明 | 与项目有关的创作、试验或测试      | 开放式讨论 |
+| 分类      | 目的                                                                    | 格式    |
+|:------- |:--------------------------------------------------------------------- |:----- |
+| 📣 公告    | 项目维护者提供的最新消息和新闻                                                       | 公告    |
+| #️⃣ 常规  | 与项目相关的任何及所有内容                                                         | 开放式讨论 |
+| 💡 想法    | 改变或改进项目的想法                                                            | 开放式讨论 |
+| 🗳 Polls | Polls with multiple options for the community to vote for and discuss | Polls |
+| 🙏 问答    | 供社区回答的问题，使用问题/回答的形式                                                   | 问题及解答 |
+| 🙌 展示和说明 | 与项目有关的创作、试验或测试                                                        | 开放式讨论 |
 
 ## 创建类别
 
-{% data reusables.repositories.navigate-to-repo %}
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.edit-categories %}
 1. 单击 **New category（新类别）**。 ![仓库讨论类别列表上方的"新类别"按钮](/assets/images/help/discussions/click-new-category-button.png)
@@ -40,7 +43,7 @@ shortTitle: 管理类别
 
 您可以编辑类别以更改类别的表情符号、标题、说明和讨论格式。
 
-{% data reusables.repositories.navigate-to-repo %}
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
 {% data reusables.discussions.discussions-tab %}
 1. 在列表中类别右侧，单击 {% octicon "pencil" aria-label="The pencil icon" %}。 ![仓库类别列表中类别右侧的编辑按钮](/assets/images/help/discussions/click-edit-for-category.png)
 1. {% data reusables.discussions.edit-category-details %}
@@ -51,7 +54,7 @@ shortTitle: 管理类别
 
 删除类别时，{% data variables.product.product_name %} 会将已删除类别中的所有讨论移到您选择的现有类别。
 
-{% data reusables.repositories.navigate-to-repo %}
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to create a category.
 {% data reusables.discussions.discussions-tab %}
 1. 在列表中类别右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 ![仓库类别列表中类别右侧的垃圾桶按钮](/assets/images/help/discussions/click-delete-for-category.png)
 1. 使用下拉菜单，为要删除的类别中的任何讨论选择新类别。 ![删除现有类别时用于选择新类别的下拉菜单](/assets/images/help/discussions/choose-new-category.png)
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
similarity index 67%
rename from translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md
rename to translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
index fdb5a313b2..372b660413 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md
@@ -1,11 +1,13 @@
 ---
-title: 管理仓库中的讨论
-intro: 您可以对仓库中的讨论进行分类、聚焦、转让或删除。
-permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository.
+title: 管理讨论
+intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
+permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
 versions:
   fpt: '*'
   ghec: '*'
 shortTitle: 管理讨论
+redirect_from:
+  - /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
 ---
 
 
@@ -13,7 +15,7 @@ shortTitle: 管理讨论
 
 {% data reusables.discussions.about-discussions %} 有关讨论的更多信息，请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
 
-组织所有者可以选择为组织拥有的仓库创建讨论所需的权限。 更多信息请参阅“[管理组织中仓库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。
+Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. 更多信息请参阅“[管理组织中仓库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。
 
 作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 为协作者制定行为守则或参与指南将有助于促进协作和富有成效的论坛。 有关创建社区资源的更多信息，请参阅“[为项目中添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置仓库参与者指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。
 
@@ -27,11 +29,13 @@ shortTitle: 管理讨论
 
 要管理仓库中的讨论，必须为仓库启用 {% data variables.product.prodname_discussions %}。 更多信息请参阅“[为仓库启用或禁用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
 
+To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
 ## 更改讨论类别
 
-您可以对讨论进行分类，以帮助社区成员查找相关的讨论。 更多信息请参阅“[管理仓库中讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)”。
+您可以对讨论进行分类，以帮助社区成员查找相关的讨论。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
 
-您也可以将讨论移动到另一个类别。
+您也可以将讨论移动到另一个类别。 It's not possible to move a discussion to or from the polls category.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.discussions.discussions-tab %}
@@ -41,9 +45,9 @@ shortTitle: 管理讨论
 
 ## 固定讨论
 
-您可以在仓库讨论列表上固定多达四个重要的讨论。
+You can pin up to four important discussions above the list of discussions for the repository or organization.
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %} **Pin discussion（固定讨论）**。 ![讨论右侧边栏中的"固定讨论"](/assets/images/help/discussions/click-pin-discussion.png)
@@ -52,9 +56,9 @@ shortTitle: 管理讨论
 
 ## 编辑固定的讨论
 
-编辑固定的讨论不会更改讨论的类别。 更多信息请参阅“[管理仓库中讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)”。
+编辑固定的讨论不会更改讨论的类别。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. 在右侧侧边栏中，单击 {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion（编辑固定的讨论）**。 ![讨论右侧边栏中的"编辑固定的讨论"](/assets/images/help/discussions/click-edit-pinned-discussion.png)
@@ -63,7 +67,7 @@ shortTitle: 管理讨论
 
 ## 取消固定讨论
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion（取消固定讨论）**。 ![讨论右侧边栏中的"取消固定讨论"](/assets/images/help/discussions/click-unpin-discussion.png)
@@ -71,18 +75,18 @@ shortTitle: 管理讨论
 
 ## 转让讨论
 
-要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 您无法将私有仓库的讨论转让给公共仓库。
+要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 您无法将私有仓库的讨论转让给公共仓库。
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. 在右侧边栏中，单击 {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion（转让讨论）**。 ![讨论右侧边栏中的"转让讨论"](/assets/images/help/discussions/click-transfer-discussion.png)
-1. 选择 **Choose a repository（选择仓库）**下拉菜单，并单击讨论要转让到的仓库。 !["选择仓库"下拉列表、"查找仓库"搜索字段以及列表中的仓库](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
+1. 选择 **Choose a repository（选择仓库）**下拉菜单，并单击讨论要转让到的仓库。 If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions. !["选择仓库"下拉列表、"查找仓库"搜索字段以及列表中的仓库](/assets/images/help/discussions/use-choose-a-repository-drop-down.png)
 1. 单击 **Transfer discussion（转让讨论）**。 !["转让讨论"按钮](/assets/images/help/discussions/click-transfer-discussion-button.png)
 
 ## 删除讨论
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 {% data reusables.discussions.click-discussion-in-list %}
 1. 在右侧边栏中，单击 {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion（删除讨论）**。 ![讨论右侧边栏中的"删除讨论"](/assets/images/help/discussions/click-delete-discussion.png)
@@ -92,7 +96,7 @@ shortTitle: 管理讨论
 
 您可以将具有相同标签的所有议题批量转换为讨论。 具有此标签的未来议题也将自动转换为您配置的讨论和类别。
 
-{% data reusables.repositories.navigate-to-repo %}
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
 {% data reusables.repositories.sidebar-issues %}
 {% data reusables.project-management.labels %}
 1. 在要转换为议题的标签旁边，单击 **Convert issues（转换议题）**。
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
index 269a2a3846..2b84a50900 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md
@@ -1,7 +1,7 @@
 ---
 title: 主持讨论
 intro: 您可以通过将评论标记为答案、锁定或解锁讨论、将议题转换为讨论，以及编辑或删除评论、讨论和不符合社区行为准则的类别，以促进健康的协作。
-permissions: People with triage access to a repository can moderate discussions in the repository.
+permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization.
 versions:
   fpt: '*'
   ghec: '*'
@@ -10,7 +10,7 @@ versions:
 
 ## 关于主持讨论
 
-{% data reusables.discussions.about-discussions %}如果您对仓库具有分类权限，便可通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持项目的讨论。
+{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate a repository's discussions by marking comments as answers, locking discussions that are not longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization.
 
 ## 将评论标记为答案
 
@@ -18,9 +18,9 @@ versions:
 
 ## 锁定讨论
 
-当整个对话没有建设性或者违反社区的行为准则或 {% data variables.product.prodname_dotcom %} 的[社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines)时，锁定对话是明智之举。 您还可以锁定对话，以防止对要用作社区公告的讨论发表评论。 锁定对话时，对仓库具有写入权限的人仍然可以对讨论发表评论。
+当整个对话没有建设性或者违反社区的行为准则或 {% data variables.product.prodname_dotcom %} 的[社区指导方针](/free-pro-team@latest/github/site-policy/github-community-guidelines)时，锁定对话是明智之举。 您还可以锁定对话，以防止对要用作社区公告的讨论发表评论。 When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion.
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 1. 在讨论列表中，单击要锁定的讨论。 ![锁定讨论](/assets/images/help/discussions/unanswered-discussion.png)
 1. 在讨论的右侧边缘单击 **Lock conversation（锁定对话）**。
@@ -29,9 +29,9 @@ versions:
 
 ## 将议题转换为讨论
 
-在将议题转换为讨论时，会使用议题中的内容自动创建讨论。 对仓库拥有写入权限的人可以根据标签批量转换议题。 更多信息请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)”。
+在将议题转换为讨论时，会使用议题中的内容自动创建讨论。 People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.repositories.sidebar-issues %}
 1. 在议题列表中，单击您想要转换的议题。
 1. 在议题的右侧边缘单击 **Convert to discussion（转换为讨论）**。
diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
index 5a91988a3e..5e91370512 100644
--- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
+++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/viewing-insights-for-your-discussions.md
@@ -1,7 +1,7 @@
 ---
 title: 查看讨论的见解
 intro: 讨论见解提供有关讨论的活动、视图和参与者的数据。
-permissions: Repository administrators and people with maintain access to a repository can view the discussions insights dashboard.
+permissions: Repository administrators and people with maintain access to a repository can view the insights dashboard for discussions in that repository. Repository administrators and people with maintain access to the source repository for organization discussions can view the insights dashboard for discussions in that organization.
 versions:
   fpt: '*'
   ghec: '*'
@@ -12,7 +12,7 @@ shortTitle: 查看讨论见解
 
 ## 关于讨论见解仪表板
 
-您可以使用讨论见解来帮助了解存储库讨论社区的贡献活动、页面浏览量和增长情况。
+You can use discussions insights to help understand the contribution activity, page views, and growth of your discussions community.
 - **贡献活动**显示对讨论、问题和拉取请求的贡献总数。
 - **讨论页面浏览量**显示讨论的总页面浏览量，按登录查看者与匿名查看者进行细分。
 - **讨论每日贡献者**显示每日在选定时间段内做出反应、投票、标记答案、评论或发布的唯一身份用户的每日计数。
@@ -28,7 +28,7 @@ shortTitle: 查看讨论见解
 
 ## 查看讨论见解
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.repositories.navigate-to-repo %} For organization discussions, navigate to the main page of the source repository.
 {% data reusables.repositories.accessing-repository-graphs %}
 3. 在左侧栏中，单击 **Community（社区）**。 ![左侧边栏中"社区" 选项卡的屏幕截图](/assets/images/help/graphs/graphs-sidebar-community-tab.png)
 1. （可选）在页面右上角，选择 **Period（期间）**下拉菜单，然后单击要查看数据的时间段： **30 天**、**3 个月**或 **1 年**。 ![讨论见解的日期范围选择器屏幕截图](/assets/images/help/discussions/discussions-dashboard-date-selctor.png)
diff --git a/translations/zh-CN/content/discussions/quickstart.md b/translations/zh-CN/content/discussions/quickstart.md
index 5576d9abdb..7e509d985c 100644
--- a/translations/zh-CN/content/discussions/quickstart.md
+++ b/translations/zh-CN/content/discussions/quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Discussions 快速入门
-intro: '在现有仓库上启用 {% data variables.product.prodname_discussions %} ，并发起与社区的对话。'
+intro: 'Enable {% data variables.product.prodname_discussions %} on an existing repository or organization and start conversations with your community.'
 allowTitleToDifferFromFilename: true
 versions:
   fpt: '*'
@@ -27,34 +27,50 @@ shortTitle: 快速入门
 1. 在“Start a new discussion（开始新讨论）”下，编辑模板以与要为社区设置的资源和语气保持一致。
 1. 单击 **Start discussion（开始讨论）**。 !["Start discussion（开始讨论）"按钮](/assets/images/help/discussions/new-discussion-start-discussion-button.png)
 
+## Enabling {% data variables.product.prodname_discussions %} on your organization
+
+Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.
+
+{% data reusables.discussions.about-organization-discussions %}
+
+{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %}
+
 ## 欢迎参与您的讨论
 
-您可以通过创建欢迎帖子并固定帖子到 {% data variables.product.prodname_discussions %} 页面，欢迎您的社区，并引入在仓库中沟通的新方式。 固定和锁定讨论有助于人们知道帖子是作为公告发布的。 您可以使用公告将人员链接到更多资源，并指导在社区中开始讨论。 有关固定讨论的更多信息，请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#pinning-a-discussion)”。
+You can welcome your community and introduce a new way to communicate in a repository or organization by creating a welcome post and pinning the post to your {% data variables.product.prodname_discussions %} page. 固定和锁定讨论有助于人们知道帖子是作为公告发布的。 您可以使用公告将人员链接到更多资源，并指导在社区中开始讨论。 For more information about pinning a discussion, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
 
 
 ## 为贡献者设置社区指南
 
-您可以设置参与指南，以鼓励协作者进行与仓库相关的有意义、有用的对话。 您还可以更新仓库的 README，以传达协作者何时应打开问题或讨论的期望。
+For repository discussions, you can set contributing guidelines to encourage collaborators to have meaningful, useful conversations that are relevant to the repository. 您还可以更新仓库的 README，以传达协作者何时应打开问题或讨论的期望。 有关为项目提供指南的更多信息，请参阅“[为项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
 
-有关为项目提供指南的更多信息，请参阅“[为项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和“[设置健康参与的项目](/communities/setting-up-your-project-for-healthy-contributions)”。
+For organization discussions, you share information about how to engage with your organization by creating an organization profile README. 更多信息请参阅“[自定义组织的配置文件](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)”。
 
 ## 创建新讨论
 
-任何可以查看仓库的认证用户都可以创建讨论。
+Any authenticated user who can view the repository can create a discussion in that repository. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a discussion in that organization.
 
 {% data reusables.discussions.starting-a-discussion %}
 
+## Creating a new poll
+
+Any authenticated user who can view a repository can create a poll. Similarly, since organization discussions are based on a source repository, any authenticated user who can view the source repository can create a poll in that organization.
+
+{% data reusables.discussions.starting-a-poll %}
+
 ## 组织讨论
 
-仓库所有者和具有写入权限的人可以创建新类别来保持讨论井然有序。 参与和创建新讨论的协作者可以将讨论分组到最相关的现有类别。 讨论也可以在创建后重新分类。 更多信息请参阅“[管理仓库中讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)”。
+Repository owners and people with write access to the repository can create new categories to keep discussions organized. Similarly, since organization discussions are based on a source repository, repository owners and people with write access to the source repository can create new categories for organization discussions.
+
+参与和创建新讨论的协作者可以将讨论分组到最相关的现有类别。 讨论也可以在创建后重新分类。 For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
 
 {% data reusables.discussions.you-can-label-discussions %}
 
 ## 促进健康的对话
 
-具有仓库写入权限的人可以通过固定讨论、删除不再有用或对社区有害的讨论以及将讨论转移到组织拥有的更相关的仓库，来帮助显示重要的对话。 更多信息请参阅“[管理仓库中的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)”。
+People with write permissions for the repository, or for the source repository for organization discussions, can help surface important conversations by pinning discussions, deleting discussions that are no longer useful or are damaging to the community, and transferring discussions to more relevant repositories owned by the organization. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)."
 
-对仓库具有分类权限的人可以通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发的早期阶段时将问题转换为讨论，从而帮助主持项目的讨论。 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
+People with triage permissions for the repository, or for the source repository for organization discussions, can help moderate a project's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. 更多信息请参阅“[主持讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)”。
 
 ## 后续步骤
 
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md
index 8b52f23973..5263efc924 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/about-github-education-for-educators-and-researchers.md
@@ -18,8 +18,7 @@ shortTitle: 教育工作者和研究人员
 利用 {% data variables.product.prodname_education %} 适用于各级教育者的工具和服务，您可以：
   - 使用 [{% data variables.product.prodname_classroom %}](https://classroom.github.com) 分发代码、向学生提供反馈以及收集 {% data variables.product.prodname_dotcom %} 中的作业。
   - 加入我们的 [{% data variables.product.prodname_education_community %}](https://education.github.com/forum)，以与全球各地的同行讨论技术教育的当前趋势。
-  - 访问和调整我们用于教授 Git 和 {% data variables.product.prodname_dotcom %} 的[开源课程计划](https://education.github.community/t/open-source-lesson-plans/1591)。
-  - [申请 {% data variables.product.prodname_dotcom %} swag 包](https://education.github.community/t/get-a-github-swag-bag-for-your-classroom/33)，其中包括学生用教育资料和重要工具。
+  - [申请 {% data variables.product.prodname_dotcom %} swag 包](https://github.com/orgs/github-community/discussions/13)，其中包括学生用教育资料和重要工具。
   {% data reusables.education.apply-for-team %}
 
 ## 适用于研究人员的 {% data variables.product.prodname_education %}
diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
index 3dddd6445e..ec7cd78efa 100644
--- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
+++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/apply-for-an-educator-or-researcher-discount.md
@@ -57,4 +57,4 @@ shortTitle: 申请折扣
 - "[为什么我的教育者或研究人员折扣申请未获得批准？](/articles/why-wasn-t-my-application-for-an-educator-or-researcher-discount-approved)"
 - [{% data variables.product.prodname_education %}](https://education.github.com)
 - [{% data variables.product.prodname_classroom %} 视频](https://classroom.github.com/videos)
-- [{% data variables.product.prodname_education_community %}](https://education.github.community/)
+- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
diff --git a/translations/zh-CN/content/education/guides.md b/translations/zh-CN/content/education/guides.md
index 39f2af9bfb..46c9a00faf 100644
--- a/translations/zh-CN/content/education/guides.md
+++ b/translations/zh-CN/content/education/guides.md
@@ -43,6 +43,6 @@ shortTitle: 指南
 
 参与社区，从 {% data variables.product.company_short %} 获得培训，并学习或教授新技能。
 
-- [{% data variables.product.prodname_education_community %}](https://education.github.community)
+- [{% data variables.product.prodname_education_community %}]({% data variables.product.prodname_education_forum_link %})
 - [关于 Campus Experts](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-experts)
 - [关于 Campus Advisors](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/about-campus-advisors)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
index e2c07d7d57..dad409d7d5 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md
@@ -23,6 +23,8 @@ redirect_from:
 
 有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
 
+{% data reusables.classroom.reuse-assignment-link %}
+
 ## 基本要求
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
index e3ee59fef4..3215da499e 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-assignment-from-a-template-repository.md
@@ -14,6 +14,8 @@ shortTitle: 模板仓库
 
 要将模板仓库用于作业，模板仓库必须由您的组织拥有，或者模板仓库的可见性必须是公共的。
 
+You can reuse an existing assignment, even if it uses a template repository, in any other classroom that you have admin access to, including classrooms in a different organization. For more information, see "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
+
 ## 延伸阅读
 
 - "[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)"
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
index 8d11692724..2fc0d09579 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md
@@ -20,6 +20,8 @@ shortTitle: 个人作业
 
 有关创建个人作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本知识](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
 
+{% data reusables.classroom.reuse-assignment-link %}
+
 ## 基本要求
 
 {% data reusables.classroom.assignments-classroom-prerequisite %}
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
index 8b526a35e1..5c2266cc37 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/index.md
@@ -11,6 +11,7 @@ children:
   - /use-the-git-and-github-starter-assignment
   - /create-an-individual-assignment
   - /create-a-group-assignment
+  - /reuse-an-assignment
   - /create-an-assignment-from-a-template-repository
   - /leave-feedback-with-pull-requests
   - /use-autograding
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
index 358f6a34b3..dcc38f257c 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md
@@ -25,6 +25,8 @@ redirect_from:
 
 使用完教室后，可以存档教室，以后可以参考该教室、名册和作业，或者如果您不再需要该教室，也可以将其删除。
 
+{% data reusables.classroom.reuse-assignment-link %}
+
 ## 关于教室名册
 
 每个教室都有一个名册。 名册是参加您的课程的学生的标识符列表。
@@ -45,7 +47,7 @@ redirect_from:
 1. 单击 **New classroom（新教室）**。 !["New classroom（新教室）"按钮](/assets/images/help/classroom/click-new-classroom-button.png)
 {% data reusables.classroom.guide-create-new-classroom %}
 
-创建教室后，您便可开始为学生创建作业。 更多信息请参阅“[使用 Git 和 {% data variables.product.company_short %} 起始作业](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)”、“[创建个别作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”或“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
+创建教室后，您便可开始为学生创建作业。 For more information, see "[Use the Git and {% data variables.product.company_short %} starter assignment](/education/manage-coursework-with-github-classroom/use-the-git-and-github-starter-assignment)," "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," or "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
 
 ## 为教室创建名册
 
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
new file mode 100644
index 0000000000..a32d1ac200
--- /dev/null
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment.md
@@ -0,0 +1,38 @@
+---
+title: Reuse an assignment
+intro: 'You can reuse an existing assignment in more than one classroom, including classrooms in a different organization.'
+versions:
+  fpt: '*'
+permissions: 'Organization owners who are admins for a classroom can reuse assignments from a classroom. {% data reusables.classroom.classroom-admins-link %}'
+shortTitle: Reuse an assignment
+---
+
+## About reusing assignments
+
+You can reuse an existing individual or group assignment in any other classroom you have access to, including classrooms in a different organization. If you choose to reuse an assignment, {% data variables.product.prodname_classroom %} will copy the assignment to the classroom you choose. If the assignment uses a template repository and you choose to reuse it in a classroom from a different organization, {% data variables.product.prodname_classroom %} will create a copy of the repository and its contents in the target organization.
+
+The copied assignment includes assignment details such as the name, source repository, autograding test, and preferred editor. You can edit the assignment after it has been copied to make changes. You cannot make changes to the preferred editor.
+
+## Reusing an assignment
+
+1. 登录 {% data variables.product.prodname_classroom_with_url %}。
+1. Navigate to the classroom that has the assignment that you want to reuse.
+
+   ![组织教室列表中的教室](/assets/images/help/classroom/click-classroom-in-list.png)
+
+1. In the list of assignments, click the assignment you want to reuse.
+
+   ![课堂作业列表中的作业](/assets/images/help/classroom/click-assignment-in-list.png)
+
+1. Select the **{% octicon "pencil" aria-label="The pencil icon" %} Edit** dropdown menu in the top right of the page, then click **{% octicon "sync" aria-label="The sync icon" %} Reuse assignment**.
+
+   ![Reuse assignment button](/assets/images/help/classroom/reuse-assignment-button.png)
+
+1. In "Reuse assignment" modal, use the **Choose an organization** dropdown menu to select the organization you want the assignment to be in.  Then use the **Choose a classroom** dropdown menu to select the classroom within that organization that you want to copy the assignment to.
+
+   ![Reuse assignment modal](/assets/images/help/classroom/reuse-assignment-modal.png)
+
+1. Click **Create assignment**.
+1. The assignment is copied to the selected classroom, and a confirmation message is shown. If you chose to reuse an assignment with a template repository, the copying process may take a few minutes to complete, and you may need to refresh the page to see the completed message.
+
+   ![Completed message for reused assignment](/assets/images/help/classroom/reuse-assignment-completed-message.png)
diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
index df8f505cf6..d38f12a0f2 100644
--- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
+++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md
@@ -96,7 +96,7 @@ Git 和 {% data variables.product.company_short %} 起始作业只适用于个
 
 ## 后续步骤
 
-- 根据课程定制其他作业。 更多信息请参阅“[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”和“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
+- 根据课程定制其他作业。 For more information, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)," "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)," and "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
 
 ## 延伸阅读
 
diff --git a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
index 1087e2455c..97b049d2de 100644
--- a/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
+++ b/translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md
@@ -19,11 +19,11 @@ shortTitle: Add locally hosted code
 
 If you have existing source code or repositories stored locally on your computer or private network you can add them to {% data variables.product.product_name %} by typing commands in a terminal. You can do this by typing Git commands directly, or by using {% data variables.product.prodname_cli %}.
 
-{% data variables.product.prodname_cli %} 是用于从计算机的命令行使用 {% data variables.product.prodname_dotcom %} 的开源工具。 {% data variables.product.prodname_cli %} 可以简化使用命令行将现有项目添加到 {% data variables.product.product_name %} 的过程。 要了解有关 {% data variables.product.prodname_cli %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。
+{% data variables.product.prodname_cli %} is an open source tool for using {% data variables.product.prodname_dotcom %} from your computer's command line. {% data variables.product.prodname_cli %} can simplify the process of adding an existing project to {% data variables.product.product_name %} using the command line. To learn more about {% data variables.product.prodname_cli %}, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
 
 {% tip %}
 
-**提示：**如果您最喜欢点按式用户界面，请尝试使用 {% data variables.product.prodname_desktop %} 添加项目。 更多信息请参阅 *{% data variables.product.prodname_desktop %} 帮助*中的“[从本地计算机添加仓库到 GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)”。
+**Tip:** If you're most comfortable with a point-and-click user interface, try adding your project with {% data variables.product.prodname_desktop %}. For more information, see "[Adding a repository from your local computer to GitHub Desktop](/desktop/guides/contributing-to-projects/adding-a-repository-from-your-local-computer-to-github-desktop)" in the *{% data variables.product.prodname_desktop %} Help*.
 
 {% endtip %}
 
@@ -31,8 +31,8 @@ If you have existing source code or repositories stored locally on your computer
 
 ## Adding a local repository to {% data variables.product.product_name %} with {% data variables.product.prodname_cli %}
 
-1. 在命令行中，导航到项目的根目录。
-1. 将本地目录初始化为 Git 仓库。
+1. In the command line, navigate to the root directory of your project.
+1. Initialize the local directory as a Git repository.
 
     ```shell
     git init -b main
@@ -46,40 +46,42 @@ If you have existing source code or repositories stored locally on your computer
 
 1. To create a repository for your project on GitHub, use the `gh repo create` subcommand. When prompted, select **Push an existing local repository to GitHub** and enter the desired name for your repository. If you want your project to belong to an organization instead of your user account, specify the organization name and project name with `organization-name/project-name`.
 
-1. 按照交互式提示进行操作。 To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
+1. Follow the interactive prompts. To add the remote and push the repository, confirm yes when asked to add the remote and push the commits to the current branch.
 
-1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. 有关可能的参数的详细信息，请参阅 [GitHub CLI 手册](https://cli.github.com/manual/gh_repo_create)。
+1. Alternatively, to skip all the prompts, supply the path to the repository with the `--source` flag and pass a visibility flag (`--public`, `--private`, or `--internal`). For example, `gh repo create --source=. --public`. Specify a remote with the `--remote` flag. To push your commits, pass the `--push` flag. For more information about possible arguments, see the [GitHub CLI manual](https://cli.github.com/manual/gh_repo_create).
 
 ## Adding a local repository to {% data variables.product.product_name %} using Git
 
 {% mac %}
 
-1. 在 {% data variables.product.product_location %} 上[创建新仓库](/repositories/creating-and-managing-repositories/creating-a-new-repository) 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png)
+1. [Create a new repository](/repositories/creating-and-managing-repositories/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. 将当前工作目录更改为您的本地仓库。
-4. 将本地目录初始化为 Git 仓库。
+3. Change the current working directory to your local project.
+4. Initialize the local directory as a Git repository.
   ```shell
   $ git init -b main
   ```
-5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。
+5. Add the files in your new local repository. This stages them for the first commit.
   ```shell
   $ git add .
   # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. 提交暂存在本地仓库中的文件。
+6. Commit the files that you've staged in your local repository.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面，点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. 在终端上，[添加远程仓库的 URL](/github/getting-started-with-github/managing-remote-repositories)（将在该 URL 推送本地仓库）。
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [推送更改](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)（本地仓库中）到 {% data variables.product.product_location %}。
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
   ```shell
   $ git push -u origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -89,32 +91,34 @@ If you have existing source code or repositories stored locally on your computer
 
 {% windows %}
 
-1. 在 {% data variables.product.product_location %} 上[创建新仓库](/articles/creating-a-new-repository) 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png)
+1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. 将当前工作目录更改为您的本地仓库。
-4. 将本地目录初始化为 Git 仓库。
+3. Change the current working directory to your local project.
+4. Initialize the local directory as a Git repository.
   ```shell
   $ git init -b main
   ```
-5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。
+5. Add the files in your new local repository. This stages them for the first commit.
   ```shell
   $ git add .
   # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. 提交暂存在本地仓库中的文件。
+6. Commit the files that you've staged in your local repository.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面，点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. 在命令提示中，[添加远程仓库的 URL](/github/getting-started-with-github/managing-remote-repositories)（将在该 URL 推送本地仓库）。
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In the Command prompt, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [推送更改](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)（本地仓库中）到 {% data variables.product.product_location %}。
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -124,32 +128,34 @@ If you have existing source code or repositories stored locally on your computer
 
 {% linux %}
 
-1. 在 {% data variables.product.product_location %} 上[创建新仓库](/articles/creating-a-new-repository) 为避免错误，请勿使用*自述文件*、许可或 `gitignore` 文件初始化新仓库。 您可以在项目推送到 {% data variables.product.product_name %} 之后添加这些文件。 ![创建新仓库下拉列表](/assets/images/help/repository/repo-create.png)
+1. [Create a new repository](/articles/creating-a-new-repository) on {% data variables.product.product_location %}. To avoid errors, do not initialize the new repository with *README*, license, or `gitignore` files. You can add these files after your project has been pushed to {% data variables.product.product_name %}.
+	![Create New Repository drop-down](/assets/images/help/repository/repo-create.png)
 {% data reusables.command_line.open_the_multi_os_terminal %}
-3. 将当前工作目录更改为您的本地仓库。
-4. 将本地目录初始化为 Git 仓库。
+3. Change the current working directory to your local project.
+4. Initialize the local directory as a Git repository.
   ```shell
   $ git init -b main
   ```
-5. 在新的本地仓库中添加文件。 这会暂存它们用于第一次提交。
+5. Add the files in your new local repository. This stages them for the first commit.
   ```shell
   $ git add .
   # Adds the files in the local repository and stages them for commit. {% data reusables.git.unstage-codeblock %}
   ```
-6. 提交暂存在本地仓库中的文件。
+6. Commit the files that you've staged in your local repository.
   ```shell
   $ git commit -m "First commit"
   # Commits the tracked changes and prepares them to be pushed to a remote repository. {% data reusables.git.reset-head-to-previous-commit-codeblock %}
   ```
-7. 在仓库顶部 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 的快速设置页面，点击 {% octicon "clippy" aria-label="The copy to clipboard icon" %} 以复制远程仓库 URL。 ![创建远程仓库 URL 字段](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
-8. 在终端上，[添加远程仓库的 URL](/github/getting-started-with-github/managing-remote-repositories)（将在该 URL 推送本地仓库）。
+7. At the top of your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}'s Quick Setup page, click {% octicon "clippy" aria-label="The copy to clipboard icon" %} to copy the remote repository URL.
+	![Copy remote repository URL field](/assets/images/help/repository/copy-remote-repository-url-quick-setup.png)
+8. In Terminal, [add the URL for the remote repository](/github/getting-started-with-github/managing-remote-repositories) where your local repository will be pushed.
   ```shell
   $ git remote add origin <em> &lt;REMOTE_URL> </em>
   # Sets the new remote
   $ git remote -v
   # Verifies the new remote URL
   ```
-9. [推送更改](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/)（本地仓库中）到 {% data variables.product.product_location %}。
+9. [Push the changes](/github/getting-started-with-github/pushing-commits-to-a-remote-repository/) in your local repository to {% data variables.product.product_location %}.
   ```shell
   $ git push origin main
   # Pushes the changes in your local repository up to the remote repository you specified as the origin
@@ -157,6 +163,6 @@ If you have existing source code or repositories stored locally on your computer
 
 {% endlinux %}
 
-## 延伸阅读
+## Further reading
 
-- "[添加文件到仓库](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
+- "[Adding a file to a repository](/repositories/working-with-files/managing-files/adding-a-file-to-a-repository#adding-a-file-to-a-repository-using-the-command-line)"
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 8e3054e7bd..6bf3e9b96f 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
@@ -26,7 +26,7 @@ A {% data variables.product.prodname_GH_advanced_security %} license provides th
 
 - **{% 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 %}](/code-security/secret-scanning/about-secret-scanning)."
+- **{% data variables.product.prodname_secret_scanning_caps %}** - Detect secrets, for example keys and tokens, that have been checked into the repository.{% if secret-scanning-push-protection %} If push protection is enabled, also detects secrets when they are pushed to your repository. For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)" and "[Protecting pushes with {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)."{% else %} For more information, see "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-scanning/about-secret-scanning)."{% endif %}
 
 {% ifversion fpt or ghes > 3.1 or ghec or ghae-issue-4864 %}
 - **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)."
diff --git a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
index 9f24411b45..7e8c4f4452 100644
--- a/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
+++ b/translations/zh-CN/content/get-started/learning-about-github/githubs-products.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub's products
+title: GitHub’s products
 intro: 'An overview of {% data variables.product.prodname_dotcom %}''s products and pricing plans.'
 redirect_from:
   - /articles/github-s-products
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
index 013ac1a1af..ff28a4e2b3 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md
@@ -22,10 +22,10 @@ After {% data variables.product.company_short %} creates the owner account for {
 You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise)."
 
 ### 4. Managing identity and access for {% data variables.product.product_location %}
-You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
+You can centrally manage access to {% data variables.product.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
 
 ### 5. Managing billing for {% data variables.product.product_location %}
-Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
+Owners of the subscription for {% data variables.product.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
 
 ## Part 2: Organizing and managing enterprise members
 As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.product.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
@@ -52,7 +52,7 @@ As an enterprise owner for {% data variables.product.product_name %}, you can ma
 To increase the security of {% data variables.product.product_location %}, you can monitor {% data variables.product.product_location %} and configure security and analysis features for your organizations.
 
 ### 1. Monitoring {% data variables.product.product_location %}
-You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/user-management/monitoring-activity-in-your-enterprise)."
+You can monitor {% data variables.product.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
 
 ### 2. Configuring security features for your organizations
 {% data reusables.getting-started.configuring-security-features %}
@@ -66,7 +66,7 @@ You can customize and automate work in organizations in {% data variables.produc
 ### 2. Building {% data variables.product.prodname_actions %}
 {% data reusables.getting-started.actions %}
 
-For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-github-actions-in-github-ae/getting-started-with-github-actions-for-github-ae)."
+For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
 
 ### 3. Using {% data variables.product.prodname_pages %}
 {% data reusables.getting-started.github-pages-enterprise %}
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
index 9598e02d65..79fd497876 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md
@@ -179,7 +179,7 @@ To manage and moderate your enterprise, you can set policies for organizations w
 
 You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
 #### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
-You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
+You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Reviewing audit logs for your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise)" and "[Monitoring your enterprise](/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise)."
 
 You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
 
diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
index 4637e3b623..0a92527444 100644
--- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
+++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md
@@ -72,7 +72,7 @@ You can use {% data variables.product.product_name %}'s built-in authentication
 You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
 
 ### 2. Staying in compliance
-You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[Audit logging](/admin/user-management/monitoring-activity-in-your-enterprise/audit-logging)."
+You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
 
 {% ifversion ghes %}
 ### 3. Configuring security features for your organizations
diff --git a/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
index a20b29acf5..ba5a90e637 100644
--- a/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
+++ b/translations/zh-CN/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md
@@ -37,7 +37,7 @@ When you enable data use for your private repository, you'll be able to access t
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
   !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
   !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-private.png){% endif %}
diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
index f9832ac917..cb70c53e8a 100644
--- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
+++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md
@@ -152,7 +152,7 @@ gh repo fork <em>repository</em> --clone=true
   > origin  https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_FORK</em>.git (push)
   ```
 
-6. 键入 `git remote add upstream`，然后粘贴您在第 2 步中复制的 URL 并按 **Enter** 键。 它将如下所示：
+6. Type `git remote add upstream`, and then paste the URL you copied in Step 3 and press **Enter**. 它将如下所示：
   ```shell
   $ git remote add upstream https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
   ```
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 d4310ff5a6..e9966fd4f2 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
@@ -192,10 +192,10 @@ These commands are available only when you open the command palette from a discu
 
 | Command | Behavior|
 | :- | :- |
-|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)."
+|`Delete discussion...`|Permanently delete the discussion. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)."
 |`Edit discussion body`|Open the main body of the discussion ready for editing.
 |`Subscribe`/`unsubscribe`|Opt in or out of notifications for additions to the discussion. For more information, see "[About notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications)."
-|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions in your repository](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#transferring-a-discussion)."
+|`Transfer discussion...`|Move the discussion to a different repository. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions#transferring-a-discussion)."
 
 ### Issue commands
 
diff --git a/translations/zh-CN/content/get-started/using-github/supported-browsers.md b/translations/zh-CN/content/get-started/using-github/supported-browsers.md
index d321bc0cfd..3ea85be579 100644
--- a/translations/zh-CN/content/get-started/using-github/supported-browsers.md
+++ b/translations/zh-CN/content/get-started/using-github/supported-browsers.md
@@ -6,7 +6,7 @@ redirect_from:
   - /articles/supported-browsers
   - /github/getting-started-with-github/supported-browsers
   - /github/getting-started-with-github/using-github/supported-browsers
-intro: '我们将 {% data variables.product.product_name %} 设计为支持最新的 Web 浏览器。 我们支持最新版本的 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/) 和 [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)。'
+intro: '为了获得最佳 {% data variables.product.product_name %} 体验，我们建议使用最新版本的 [Chrome](https://google.com/chrome)、[Edge](https://microsoft.com/windows/microsoft-edge)、[Firefox](https://mozilla.org/firefox) 或 [Safari](https://apple.com/safari)。'
 versions:
   fpt: '*'
   ghes: '*'
@@ -14,9 +14,28 @@ versions:
   ghec: '*'
 ---
 
-## Firefox Extended Support Release
+## 关于 Web 浏览器对 {% data variables.product.product_name %} 的支持
+
+我们在设计 {% data variables.product.product_name %} 时考虑了最新的 Web 浏览器。 我们建议您使用以下浏览器之一的最新版本。
+
+ - [Apple Safari](https://apple.com/safari)
+ - [Google Chrome](https://google.com/chrome)
+ - [Microsoft Edge](https://microsoft.com/windows/microsoft-edge)
+ - [Mozilla Firefox](https://mozilla.org/firefox)
+
+如果您使用的不是推荐的浏览器最新版本，或者您使用的浏览器未在上面列出，{% data variables.product.product_name %} 或某些功能可能无法按预期工作，或者根本无法正常工作。
+
+有关如何维护 {% data variables.product.company_short %} 产品的浏览器兼容性的更多信息，请参阅 [`github/browser-support`](https://github.com/github/browser-support) 存储库。
+## 对推荐的 Web 浏览器的扩展支持
+
+某些浏览器供应商提供扩展支持版本。 我们尽最大努力确保 {% data variables.product.product_name %} 在以下最新的扩展支持版本中正常运行：
+
+- Chrome 的[扩展稳定通道](https://support.google.com/chrome/a/answer/9027636)
+- Edge 的[扩展稳定通道](https://docs.microsoft.com/en-gb/deployedge/microsoft-edge-channels#extended-stable-channel)
+- Firefox 的[扩展支持版本](https://www.mozilla.org/en-US/firefox/organizations/) (ESR)
+
+在早期的扩展支持版本中，{% data variables.product.product_name %} 可能无法按预期工作，并且某些功能可能不可用。
 
-我们尽最大努力支持 Firefox 的最新 [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR)。 较旧版本的 Firefox 可能会禁用 {% data variables.product.product_name %} 上的某些功能，因此需要最新版本的 Firefox。
 
 ## 测试版和开发者版本
 
diff --git a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
index 3a4be5831a..b24df8a7d9 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md
@@ -190,6 +190,12 @@ git commit
      - 第二个嵌套列表项
 ```
 
+{% tip %}
+
+**注意**：在基于 Web 的编辑器中，您可以缩进或缩减一行文本，方法是首先突出显示所需的行，然后分别使用 <kbd>Tab</kbd> 或 <kbd>Shift</kbd>+<kbd>Tab</kbd>。
+
+{% endtip %}
+
 ![突出显示对齐的嵌套列表](/assets/images/help/writing/nested-list-alignment.png)
 
 ![含两级嵌套项的列表](/assets/images/help/writing/nested-list-example-1.png)
diff --git a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
index f66ccd33bf..58c40d62f8 100644
--- a/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
+++ b/translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md
@@ -50,7 +50,7 @@ Look! You can see my backticks.
 
 ## 语法突显
 
-<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported languages. -->
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
 
 您可以添加可选的语言标识符，以在围栏代码块中启用语法突显。
 
diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
index d62acd4e38..296f90b990 100644
--- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
+++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue.md
@@ -1,6 +1,6 @@
 ---
-title: Creating a branch to work on an issue
-intro: You can create a branch to work on an issue directly from the issue page and get started right away.
+title: 创建分支以处理议题
+intro: 您可以创建一个分支，直接从议题页面处理议题，然后立即开始。
 versions:
   fpt: '*'
   ghes: '>=3.5'
@@ -9,26 +9,26 @@ versions:
 allowTitleToDifferFromFilename: true
 topics:
   - Issues
-shortTitle: Create branch for issue
+shortTitle: 为议题创建分支
 ---
 
 {% note %}
 
-**Note:** The ability to create a branch for an issue is currently in public beta and subject to change.
+**注意：** 为议题创建分支的功能目前处于公开测试阶段，可能会发生更改。
 
 {% endnote %}
 
-## About branches connected to an issue
-Branches connected to an issue are shown under the "Development" section in the sidebar of an issue. When you create a pull request for one of these branches, it is automatically linked to the issue. The connection with that branch is removed and only the pull request is shown in the "Development" section. 更多信息请参阅“[将拉取请求链接到议题](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)”。
+## 关于与议题相关联的分支
+与议题相关的分支显示在议题边栏的“开发”部分下。 当您为其中一个分支创建拉取请求时，它会自动链接到议题。 与该分支的连接将被删除，并且只有拉取请求显示在“开发”部分中。 更多信息请参阅“[将拉取请求链接到议题](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)”。
 
-## Creating a branch for an issue
+## 为议题创建分支
 
-Anyone with write permission to a repository can create a branch for an issue. You can link multiple branches for an issue.
+对存储库具有写入权限的任何人都可以为议题创建分支。 您可以为一个议题链接多个分支。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-issues %}
-3. In the list of issues, click the issue that you would like to create a branch for.
-4. In the right sidebar under "Development", click **Create a branch**. If the issue already has a linked branch or pull request, click {% octicon "gear" aria-label="The Gear icon" %} and at the bottom of the drop-down menu click **Create a branch**. ![Screenshot showing Create a branch option highlighted in sidebar](/assets/images/help/issues/create-a-branch.png)
-5. By default, the new branch is created in the current repository from the default branch. Edit the branch name and details as required in the "Create a branch for this issue" dialog. ![Screenshot showing Create a branch dialog options](/assets/images/help/issues/create-a-branch-options.png)
-6. Choose whether to work on the branch locally or to open it in GitHub Desktop.
-7. When you are ready to create the branch, click **Create branch**.
+3. 在议题列表中，单击要为其创建分支的议题。
+4. 在右侧边栏的“Development（开发）”下，单击 **Create a branch（创建分支）**。 如果议题已具有链接的分支或拉取请求，请单击 {% octicon "gear" aria-label="The Gear icon" %} ，然后在下拉菜单底部单击 **Create a branch（创建分支）**。 ![显示侧边栏中突出显示的“创建分支”选项的屏幕截图](/assets/images/help/issues/create-a-branch.png)
+5. 默认情况下，新分支是从默认分支在当前存储库中创建的。 根据“Create a branch for this issue（为此议题创建分支）”对话框中的需要编辑分支名称和详细信息。 ![显示“创建分支”对话框选项的屏幕截图](/assets/images/help/issues/create-a-branch-options.png)
+6. 选择是在本地处理分支，还是在 GitHub Desktop 中打开分支。
+7. 准备好创建分支后，单击 **Create branch（创建分支）**。
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
index abbc641602..93a3488e57 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md
@@ -63,6 +63,15 @@ topics:
 3. 选择拉取请求或议题所在的仓库。 您可以输入仓库名称的一部分来缩小选项范围。
 4. 选择议题或拉取请求。 您可以键入标题的一部分以缩小选项范围。
 
+#### 从存储库添加多个议题或拉取请求
+
+1. 在 {% data variables.product.product_location %} 上，导航到包含要添加到项目中的议题或拉取请求的存储库。
+{% data reusables.repositories.sidebar-issue-pr %}
+1. 在每个议题标题的左侧，选择要添加到项目中的议题。 ![显示用于选择议题或拉取请求的复选框的屏幕截图](/assets/images/help/issues/select-issue-checkbox.png)
+1. （可选）若要选择页面上的每个议题或拉取请求，请在议题或拉取请求列表的顶部选择全部。 ![显示用于全选的复选框的屏幕截图](/assets/images/help/issues/select-all-checkbox.png)
+1. 在议题列表或拉取请求上方，单击 **Projects (beta)（项目[测试版]）**。 ![显示用于全选的复选框的屏幕截图](/assets/images/help/issues/projects-beta-assign-button.png)
+1. 单击要向其添加所选议题或拉取请求的项目。 ![显示用于全选的复选框的屏幕截图](/assets/images/help/issues/projects-beta-assign-dropdown.png)
+
 #### 从议题或拉取请求中分配项目
 
 1. 导航到要添加到项目的议题或拉取请求。
@@ -102,7 +111,20 @@ topics:
 
 ## 恢复存档的项
 
-要恢复存档的项，请导航到议题或拉取请求。 在议题或拉取请求的项目侧栏中，对要将项还原到的项目单击 **Restore（恢复）**。 草稿议题无法恢复。
+1. Navigate to your project.
+1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="the kebab icon" %}。
+1. 在菜单中，单击 **Archived items（已存档的项）**。
+1. （可选）要筛选显示的已存档项，请在项列表上方的文本框中键入筛选器。 有关可用筛选器的详细信息，请参阅“[筛选项目 （测试版）](/issues/trying-out-the-new-projects-experience/filtering-projects)”。
+
+   ![显示用于筛选已存档项的字段的屏幕截图](/assets/images/help/issues/filter-archived-items.png)
+
+1. 在每个项标题的左侧，选择要恢复的项。
+
+   ![显示已存档项旁边复选框的屏幕截图](/assets/images/help/issues/select-archived-item.png)
+
+1. 要恢复所选项，请在项列表上方单击 **Restore（恢复）**。
+
+   ![显示"恢复"按钮的屏幕截图](/assets/images/help/issues/restore-archived-item-button.png)
 
 ## 添加字段
 
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/filtering-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
index 16f9fc236b..db81820ee8 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/filtering-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Filtering projects (beta)
-intro: You can filter your projects to focus on specific information.
+title: 筛选项目（测试版）
+intro: 您可以筛选项目以专注于特定信息。
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 2
 versions:
@@ -13,14 +13,14 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About filtering projects
+## 关于筛选项目
 
-You can customize views using filters for item metadata, such as assignees and the labels applied to issues, and by the fields in your project. You can combine filters and save them as views. 更多信息请参阅“[自定义项目视图](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)”。
+您可以使用项目元数据（例如受理人和应用于议题的标签）的筛选器以及项目中的字段自定义视图。 您可以组合筛选器并将其另存为视图。 更多信息请参阅“[自定义项目视图](/issues/trying-out-the-new-projects-experience/customizing-your-project-views)”。
 
-To filter a project, click {% octicon "filter" aria-label="The Filter icon" %} and start typing the fields and values you would like to filter for. 当您输入时，可能的值将会出现。 You can also open the command pallet and type "Filter by" to choose from the available filters.
+若要筛选项目，请单击 {% octicon "filter" aria-label="The Filter icon" %}，然后开始键入要筛选的字段和值。 当您输入时，可能的值将会出现。 您也可以打开命令面板并键入“Filter by（筛选依据）”以从可用的筛选器中进行选择。
 
-The same filters are available for insights, allowing you to filter the data used to create your charts. For more information, see "[Using insights with projects](/issues/trying-out-the-new-projects-experience/using-insights-with-projects)."
+相同的筛选器可用于见解，允许您筛选用于创建图表的数据。 更多信息请参阅“[将见解用于项目](/issues/trying-out-the-new-projects-experience/using-insights-with-projects)”。
 
-## Syntax for filtering projects
+## 筛选项目的语法
 
 {% data reusables.projects.projects-filters %}
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-iterations.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
index fac2745fb9..104efec67e 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-iterations.md
@@ -1,6 +1,6 @@
 ---
-title: Managing iterations in projects (beta)
-intro: You can create iterations to plan upcoming work and group items.
+title: 管理项目中的迭代（测试版）
+intro: 您可以创建迭代来规划即将到来的工作和组项。
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 2
 versions:
@@ -13,52 +13,52 @@ topics:
 
 {% data reusables.projects.projects-beta %}
 
-## About iterations
+## 关于迭代
 
-You can create an iteration field to associate items with specific repeating blocks of time. Iterations can be set to any length of time, can include breaks, and can be individually edited to modify name and date range. With projects, you can group by iteration to visualize the balance of upcoming work, use filters to focus on a single iteration, and sort by iteration.
+您可以创建迭代字段以将项与特定的重复时间块相关联。 迭代可以设置为任何时间长度，可以包括断点，并且可以单独编辑以修改名称和日期范围。 使用项目，您可以按迭代进行分组以可视化未来工作的平衡，使用筛选器专注于单个迭代，并按迭代进行排序。
 
-When you first create an iteration field, three iterations are automatically created.  You can add additional iterations and make other changes on your project's settings page.
+首次创建迭代字段时，将自动创建三个迭代。  您可以在项目的设置页面上添加其他迭代并进行其他更改。
 
-![Screenshot showing the settings for an iteration field](/assets/images/help/issues/iterations-example.png)
+![显示迭代字段设置的屏幕截图](/assets/images/help/issues/iterations-example.png)
 
-## Creating an iteration field
+## 创建迭代字段
 
-You can create an iteration field using the command palette or the project's interface.
+您可以使用命令面板或项目的界面创建迭代字段。
 
 1. {% data reusables.projects.open-command-palette %} 开始输入 "Create new field" 的任何部分。 当 "Create new field" 显示在命令板中时，选择它。
 
    或者，单击最右侧字段标题中的 {% octicon "plus" aria-label="the plus icon" %} 。 将显示带有项目字段的下拉菜单。 单击 **New field（新建字段）**。
-1. In the text box, enter a name for the new iteration field.
-1. Select the dropdown menu below and click **Iteration**.
-1. Optionally, if you want to change the starting date from the current day, select the calendar dropdown next to "Starts on" and click on a new starting date.
-2. To change the duration of each iteration, type a new number, then select the dropdown and click either **days** or **weeks**.
-3. Click **Save & create**.
+1. 在文本框中，输入新迭代字段的名称。
+1. 选择下面的下拉菜单，然后单击 **Iteration（迭代）**。
+1. （可选）如果要更改当天的开始日期，请选择“Starts on（开始日期）”旁边的日历下拉列表，然后单击新的开始日期。
+2. 要更改每次迭代的持续时间，请键入新数字，然后选择下拉列表并单击**天**或**周**。
+3. 单击 **Save & create（保存并创建）**。
 
-## Adding new iterations
+## 添加新迭代
 
 {% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-1. To add a new iteration of the same duration, click **Add iteration**.
-1. Optionally, to customize the duration of the new iteration and when it will start, click {% octicon "triangle-down" aria-label="The triangle icon" %} next to "Add iteration", select a starting date and duration, and click **Add**.
+1. 单击您想要调整的迭代字段的名称。
+1. 要添加具有相同持续时间的新迭代，请单击 **Add iteration（添加迭代）**。
+1. （可选）要自定义新迭代的持续时间及其开始时间，请单击“Add iteration（添加迭代）”旁边的 {% octicon "triangle-down" aria-label="The triangle icon" %} ，选择开始日期和持续时间，然后单击 **Add（添加）**。
 1. 单击 **Save changes（保存更改）**。
 
-## Editing an iteration
+## 编辑迭代
 
-You can edit iterations in your project settings. You can also access the settings for an iteration field by clicking {% octicon "triangle-down" aria-label="The triangle icon" %} in the table header for the field and clicking **Edit values**.
+您可以在项目设置中编辑迭代。 您还可以访问迭代字段的设置，方法是单击字段表头中的 {% octicon "triangle-down" aria-label="The triangle icon" %} ，然后单击 **Edit values（编辑值）**。
 
 {% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-1. To change the name of an iteration, click on the name and start typing.
-1. To change the date or duration of an iteration, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
-1. Optionally, to delete an iteration, click {% octicon "trash" aria-label="The trash icon" %}.
+1. 单击您想要调整的迭代字段的名称。
+1. 要更改迭代的名称，请单击该名称并开始键入。
+1. 要更改迭代的日期或持续时间，请单击该日期以打开日历。 单击开始日期，然后单击结束日期，再单击 **Apply（应用）**。
+1. （可选）要删除迭代，请单击 {% octicon "trash" aria-label="The trash icon" %}。
 1. 单击 **Save changes（保存更改）**。
 
-## Inserting a break
+## 插入断点
 
-You can insert breaks into your iterations to communicate when you are taking time away from scheduled work. The duration of a new break defaults to the length of the most recently created iteration.
+您可以在迭代中插入断点，以便在从预定工作中抽出时间进行通信。 新断点的持续时间默认为最近创建的迭代长度。
 
 {% data reusables.projects.project-settings %}
-1. Click the name of the iteration field you want to adjust.
-2. On the dividing line above an iteration and to the right, click **Insert break**. ![Screenshot showing location of "Insert break" button](/assets/images/help/issues/iteration-insert-break.png)
-3. Optionally, to change the duration of the break, click on the date to open the calendar. Click on the start day, then click the end day, and then click **Apply**.
+1. 单击您想要调整的迭代字段的名称。
+2. 在迭代上方和右侧的分界线上，单击 **Insert break（插入断点）**。 ![显示"插入断点"按钮位置的屏幕截图](/assets/images/help/issues/iteration-insert-break.png)
+3. （可选）要更改断点的持续时间，请单击日期以打开日历。 单击开始日期，然后单击结束日期，再单击 **Apply（应用）**。
 4. 单击 **Save changes（保存更改）**。
diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
index ba16adfcc7..b5e7491360 100644
--- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
+++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md
@@ -1,6 +1,6 @@
 ---
-title: Using insights with projects (beta)
-intro: You can view and customize charts that are built from your project's data.
+title: 将见解用于项目（测试版）
+intro: 您可以查看和自定义根据项目数据生成的图表。
 allowTitleToDifferFromFilename: true
 miniTocMaxHeadingLevel: 2
 versions:
@@ -13,31 +13,31 @@ topics:
 
 {% data reusables.projects.insights-alpha %}
 
-## About insights
+## 关于见解
 
-You can use insights to view and customize charts that use the items added to your project as their source data. The default "Burn up" chart shows item status over time, allowing you to visualize progress and spot patterns over time.
+您可以使用见解来查看和自定义图表，这些图表使用添加到项目中的项作为其源数据。 默认的“燃尽”图显示一段时间内的项状态，允许您可视化一段时间内的进度和点模式。
 
-![Screenshot showing an example of the default burn up chart for the current iteration](/assets/images/help/issues/burnup-example.png)
+![显示当前迭代的默认燃尽图示例的屏幕截图](/assets/images/help/issues/burnup-example.png)
 
-You can apply filters to the default chart and also create your own charts. When you create a chart, you set the filters, chart type, and the information displayed, and the chart is available to anyone that can view the project.
+您可以将筛选器应用于默认图表，也可以创建自己的图表。 创建图表时，可以设置筛选器、图表类型和显示的信息，图表可用于能够查看项目的任何人。
 
-![Screenshot showing an stacked column chart showing item types for each iteration](/assets/images/help/issues/column-chart-example.png)
+![显示堆叠柱形图的屏幕截图，该图表显示每次迭代的项类型](/assets/images/help/issues/column-chart-example.png)
 
-## Creating a chart
+## 创建图表
 
 {% data reusables.projects.access-insights %}
-3. In the menu on the left, click **New chart**.
-4. Optionally, to change the name of the new chart, click {% octicon "triangle-down" aria-label="The triangle icon" %}, type a new name, and press <kbd>Return</kbd>.
-5. Above the chart, type filters to change the data used to build the chart. 更多信息请参阅“[筛选项目](/issues/trying-out-the-new-projects-experience/filtering-projects)”。
-6. To the right of the filter text box, click **Save changes**.
+3. 在左侧菜单中，单击 **New chart（新建图表）**。
+4. （可选）要更改新图表的名称，请单击 {% octicon "triangle-down" aria-label="The triangle icon" %}，键入新名称，然后按 <kbd>Return</kbd>。
+5. 在图表上方，键入筛选器以更改用于生成图表的数据。 更多信息请参阅“[筛选项目](/issues/trying-out-the-new-projects-experience/filtering-projects)”。
+6. 在筛选器文本框的右侧，单击 **Save changes（保存更改）**。
 
-## Configuring a chart
+## 配置图表
 
 {% data reusables.projects.access-insights %}
-1. In the menu on the left, click on the chart you would like to configure.
-1. On the right side of the page, click **Configure**. A panel will open on the right.
-2. To change the type of chart, select the **Layout** dropdown and click on the chart type you want to use.
-3. To change the field used for your chart's X-axis, select the **X-axis** dropdown and click the field you want to use. If you select "Time", "Group by" will change to "Status" and "Y-Axis" will change to "Count of items."
-4. Optionally, to group the items on your X-axis by another field, select **Group by** and click on the field you want to use, or click "None" to disable grouping.
-5. Optionally, if your project contains number fields and you want the Y-axis to display the sum, average, minimum, or maximum of one of those number fields, select **Y-axis** and click an option. Then, select the dropdown that appears beneath and click on the number field you want to use.
-6. To save your chart, click **Save changes**.
+1. 在左侧菜单中，单击要配置的图表。
+1. 在页面右侧，单击 **Configure（配置）**。 右侧将打开一个面板。
+2. 要更改图表类型，请选择 **Layout（布局）**下拉列表，然后单击要使用的图表类型。
+3. 要更改用于图表 X 轴的字段，请选择 **X-axis（X 轴）**下拉列表，然后单击要使用的字段。 如果选择“Time（时间）”，“Group by（分组依据）”将变为“Status（状态）”，“Y-Axis（Y 轴）”将变为“Count of items（项数）”。
+4. （可选）要按其他字段对 X 轴上的项目进行分组，请选择 **Group by（分组依据）**，然后单击要使用的字段，或单击“None（无）”以禁用分组。
+5. （可选）如果项目包含数字字段，并且您希望 Y 轴显示其中一个数字字段的总和、平均值、最小值或最大值，请选择 **Y-axis（Y 轴）** ，然后单击选项。 然后，选择下面显示的下拉列表，并单击要使用的数字字段。
+6. 要保存图表，请单击 **Save changes（保存更改）**。
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
index bdf982e8f7..cfc248da29 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md
@@ -25,7 +25,7 @@ shortTitle: 访问组织设置
 
 {% tip %}
 
-**提示：**只有组织所有者和帐单管理员可以查看及更改组织的帐单信息与帐户设置。 {% data reusables.organizations.new-org-permissions-more-info %}
+**提示：**只有组织所有者和帐单管理员可以查看及更改组织的帐单信息与全套帐户设置。 组织版主只能看到主持设置。 {% data reusables.organizations.new-org-permissions-more-info %}
 
 {% endtip %}
 
diff --git a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
index 8bfb16e607..1ca541a275 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization.md
@@ -12,12 +12,17 @@ topics:
   - Organizations
   - Teams
 shortTitle: 查看组织见解
+permissions: Organization members can view organization insights.
 ---
 
-组织的所有成员均可查看组织洞察。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
-
 您可以使用组织活动洞察来帮助您更好地了解组织成员如何使用 {% data variables.product.product_name %} 进行协作和处理代码。 依赖项洞察可帮助您跟踪、报告和处理组织的开源使用情况。
 
+{% note %}
+
+**注意：** 若要查看组织见解，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
 ## 查看组织活动洞察
 
 {% note %}
diff --git a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
index 47b5b5de1b..d95d559c88 100644
--- a/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
+++ b/translations/zh-CN/content/organizations/collaborating-with-your-team/about-team-discussions.md
@@ -42,6 +42,14 @@ topics:
 
 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}“[订阅和退订通知](/github/receiving-notifications-about-activity-on-github/subscribing-to-and-unsubscribing-from-notifications){% endif %}”和“[嵌套的团队](/articles/about-teams/#nested-teams)”。
 
+{% ifversion fpt or ghec %}
+
+## Organization discussions
+
+You can also use organization discussions to facilitate conversations across your organization. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
+{% endif %}
+
 ## 延伸阅读
 
 - "[{% data variables.product.prodname_dotcom %} 通信快速入门](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)"
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
index 634252b3a9..974e03f03d 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md
@@ -17,6 +17,13 @@ shortTitle: 访问合规性报告
 
 {% data reusables.security.compliance-report-list %}
 
+
+{% note %}
+
+**注意：** 若要查看合规性报告，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
 ## 访问组织的合规性报告
 
 {% data reusables.profile.access_org %}
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
index 61b87d6530..8fd6ad0d77 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md
@@ -114,8 +114,7 @@ You can enable or disable features for all repositories.
    ![Screenshot of a checkbox for enabling a feature for new repositories](/assets/images/enterprise/github-ae/organizations/security-and-analysis-enable-or-disable-secret-scanning-checkbox-ghae.png)
    {% endif %}
 
-{% ifversion ghec or ghes > 3.2 %}
-<!--TODO confirm that this functionality is intentionally not available for FPT -->
+{% ifversion fpt or ghec or ghes > 3.2 %}
 
 ## Allowing {% data variables.product.prodname_dependabot %} to access private dependencies
 
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
index 0063319bf6..653de529f3 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md
@@ -30,6 +30,14 @@ shortTitle: 限制电子邮件通知
 
 {% data reusables.notifications.email-restrictions-verification %}
 
+{% ifversion fpt or ghec %}
+{% note %}
+
+**注意：** 若要限制电子邮件通知，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
+
 外部协作者不受限于已验证或批准域的电子邮件通知。 有关外部协作者的更多信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。
 
 如果您的组织由企业帐户拥有，则组织成员除了能够接收来自组织的任何已验证或批准域的通知之外，还能够接收来自企业帐户的任何已验证或批准域的通知。 更多信息请参阅“[验证或批准企业的域](/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)”。
diff --git a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
index 07398ecdd3..265289d743 100644
--- a/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md
@@ -41,9 +41,9 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`advisory_credit`](#advisory_credit-category-actions) | Contains all activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. For more information, see "[About {% data variables.product.prodname_dotcom %} Security Advisories](/github/managing-security-vulnerabilities/about-github-security-advisories)."
 | [`billing`](#billing-category-actions) | Contains all activities related to your organization's billing.
 | [`business`](#business-category-actions) | Contains activities related to business settings for an enterprise. |
-| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
-| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
-| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.
+| [`codespaces`](#codespaces-category-actions) | Contains all activities related to your organization's codespaces. |{% endif %}{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
+| [`dependabot_alerts`](#dependabot_alerts-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+| [`dependabot_alerts_new_repos`](#dependabot_alerts_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization.{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}
 | [`dependabot_security_updates`](#dependabot_security_updates-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. For more information, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)."
 | [`dependabot_security_updates_new_repos`](#dependabot_security_updates_new_repos-category-actions) | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.{% endif %}{% ifversion fpt or ghec %}
 | [`dependency_graph`](#dependency_graph-category-actions) | Contains organization-level configuration activities for dependency graphs for repositories. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)."
@@ -63,8 +63,8 @@ To search for specific events, use the `action` qualifier in your query. Actions
 | [`org_credential_authorization`](#org_credential_authorization-category-actions) | Contains all activities related to authorizing credentials for use with SAML single sign-on.{% endif %}{% if secret-scanning-audit-log-custom-patterns %}
 | [`org_secret_scanning_custom_pattern`](#org_secret_scanning_custom_pattern-category-actions) | Contains organization-level activities related to secret scanning custom patterns. For more information, see "[Defining custom patterns for secret scanning](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)." {% endif %}{% ifversion fpt or ghes or ghae or ghec %}
 | [`organization_label`](#organization_label-category-actions) | Contains all activities related to default labels for repositories in your organization.{% endif %}
-| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.{% ifversion fpt or ghes or ghec %}
-| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% endif %}{% ifversion fpt or ghec %}
+| [`oauth_application`](#oauth_application-category-actions) | Contains all activities related to OAuth Apps.
+| [`packages`](#packages-category-actions) | Contains all activities related to {% data variables.product.prodname_registry %}.{% ifversion fpt or ghec %}
 | [`payment_method`](#payment_method-category-actions) | Contains all activities related to how your organization pays for GitHub.{% endif %}
 | [`profile_picture`](#profile_picture-category-actions) | Contains all activities related to your organization's profile picture.
 | [`project`](#project-category-actions) | Contains all activities related to project boards.
@@ -135,18 +135,17 @@ Using the qualifier `country`, you can filter events in the audit log based on t
 You can interact with the audit log using the GraphQL API{% ifversion fpt or ghec %} or the REST API{% endif %}.
 
 {% ifversion fpt or ghec %}
-The audit log API requires {% data variables.product.prodname_ghe_cloud %}.{% ifversion fpt %} {% data reusables.enterprise.link-to-ghec-trial %}{% endif %}
+
+{% note %}
+
+**Note:** To use the audit log API, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
 
 ### Using the GraphQL API
 
 {% endif %}
 
-{% note %}
-
-**Note**: The audit log GraphQL API is available for organizations using {% data variables.product.prodname_enterprise %}. {% data reusables.gated-features.more-info-org-products %}
-
-{% endnote %}
-
 To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
 {% data reusables.audit_log.audit-log-api-info %}
 
@@ -162,12 +161,6 @@ For example, you can make a GraphQL request to see all the new organization memb
 
 ### Using the REST API
 
-{% note %}
-
-**Note:** The audit log REST API is available for users of {% data variables.product.prodname_ghe_cloud %} only.
-
-{% endnote %}
-
 To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor:
 {% data reusables.audit_log.audited-data-list %}
 
@@ -236,7 +229,7 @@ An overview of some of the most common actions that are recorded as events in th
 | `manage_access_and_security` | Triggered when a user updates [which repositories a codespace can access](/github/developing-online-with-codespaces/managing-access-and-security-for-codespaces).
 {% endif %}
 
-{% ifversion fpt or ghec or ghes > 3.2 %}
+{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
 ### `dependabot_alerts` category actions
 
 | Action | Description
@@ -250,7 +243,9 @@ An overview of some of the most common actions that are recorded as events in th
 |------------------|-------------------
 | `disable` | Triggered when an organization owner disables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories. 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)."
 | `enable` | Triggered when an organization owner enables {% data variables.product.prodname_dependabot_alerts %} for all new {% ifversion fpt or ghec %}private {% endif %}repositories.
+{% endif %}
 
+{% ifversion fpt or ghec or ghes > 3.2 %}
 ### `dependabot_security_updates` category actions
 
 | Action | Description
@@ -516,18 +511,15 @@ For more information, see "[Managing the publication of {% data variables.produc
 | `revoke_tokens` | Triggered when an {% data variables.product.prodname_oauth_app %}'s user tokens are revoked.
 | `transfer` |  Triggered when an existing {% data variables.product.prodname_oauth_app %} is transferred to a new organization.
 
-{% ifversion fpt or ghes or ghec %}
 ### `packages` category actions
 
 | Action | Description |
 |--------|-------------|
 | `package_version_published` | Triggered when a package version is published. |
-| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
-| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
-| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
-| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
-
-{% endif %}
+| `package_version_deleted` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `package_deleted` | Triggered when an entire package is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `package_version_restored` | Triggered when a specific package version is deleted.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
+| `package_restored` | Triggered when an entire package is restored.{% ifversion fpt or ghec or ghes > 3.1 or ghae %} For more information, see "[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package)."{% endif %}
 
 {% ifversion fpt or ghec %}
 
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
index bebbcc7a83..1aef14f591 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md
@@ -15,6 +15,8 @@ topics:
 shortTitle: 将成员转换为协作者
 ---
 
+## 关于将组织成员转换为外部协作者
+
 {% data reusables.organizations.owners-and-admins-can %} 将组织成员转换为外部协作者。
 
 {% data reusables.organizations.outside-collaborators-use-seats %} {% data reusables.organizations.outside_collaborator_forks %}
@@ -32,6 +34,14 @@ shortTitle: 将成员转换为协作者
 
 将组织成员转换为外部协作者时，他们作为组织成员的权限将保存三个月，因此，如果您在该时间范围内{% ifversion fpt or ghec %} 邀请他们重新加入{% else %} 将他们重新添加到{% endif %} 您的组织，您可以恢复其成员权限。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。
 
+## 将组织成员转换为外部协作者
+
+{% note %}
+
+**注意：** 如果组织所有者{% ifversion not fpt %} 或企业所有者{% endif %} 限制了您添加外部协作者的能力，则您可能无法将组织成员转换为外部协作者。
+
+{% endnote %}
+
 {% data reusables.profile.access_org %}
 {% data reusables.user-settings.access_org %}
 {% data reusables.organizations.people %}
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
index 7c222a0747..0310a09e30 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md
@@ -33,7 +33,7 @@ shortTitle: 恢复协作者
 
 **提示**：
 
- - 只有组织所有者才能恢复外部协作者对组织的访问权限。 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
+ - 只有组织所有者才能恢复外部协作者对组织的访问权限。{% if prevent-org-admin-add-outside-collaborator %} 企业所有者可以进一步限制仅企业所有者才可恢复外部协作者。{% endif %} 更多信息请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
  - 恢复 {% data variables.product.product_location %} 上的成员流量可以使用术语“成员”来描述恢复外部协作者，但如果您恢复此人员并保留其以前的权限，则他们将只拥有以前的[外部协作者权限](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)。{% ifversion fpt or ghec %}
  - 如果您的组织采用付费的每用户订阅，则必须有未使用的许可才可邀请新成员加入组织或恢复前组织成员。 更多信息请参阅“[关于每用户定价](/articles/about-per-user-pricing)”。{% endif %}
 
diff --git a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
index 00da4e4122..836b4072b8 100644
--- a/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md
@@ -142,15 +142,15 @@ shortTitle: 存储库角色
 {% endif %}
 | 创建到外部资源的自动链接引用，如 Jira 或 Zendesk（请参阅“[配置自动链接以引用外部资源](/articles/configuring-autolinks-to-reference-external-resources)”）                                                                                                                                                                                                                                                                                                 |       |       |       |       |                 **X** |{% ifversion fpt or ghec %}
 | 在仓库中[启用 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)                                                                                                                                                                                                                                                               |       |       |       | **X** |                                **X**                                |
-| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions-in-your-repository)                                                                                                                                                                                                                                             |       |       |       | **X** |                                **X**                                |
-| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                             |       |       | **X** | **X** |                                **X**                                |
-| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)新仓库                                                                                                                                                                                                                                                                                                              |       |       | **X** | **X** |                                **X**                                |
-| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                                |       |       | **X** | **X** |                                **X**                                |
-| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository)                                                                                                                                                                                                                                                                                                             |       |       | **X** | **X** |                                **X**                                |
+| 为 {% data variables.product.prodname_discussions %} [创建和编辑类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)                                                                                                                                                                                                                                                                |       |       |       | **X** |                                **X**                                |
+| [将讨论移动到其他类别](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                |       |       | **X** | **X** |                                **X**                                |
+| [将讨论转移到](/discussions/managing-discussions-for-your-community/managing-discussions)新仓库                                                                                                                                                                                                                                                                                                                                 |       |       | **X** | **X** |                                **X**                                |
+| [管理置顶的讨论](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                   |       |       | **X** | **X** |                                **X**                                |
+| [批量将议题转换为讨论](/discussions/managing-discussions-for-your-community/managing-discussions)                                                                                                                                                                                                                                                                                                                                |       |       | **X** | **X** |                                **X**                                |
 | [锁定和解锁讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                                                                                 |       | **X** | **X** | **X** |                                **X**                                |
 | [单独将议题转换为讨论](/discussions/managing-discussions-for-your-community/moderating-discussions)                                                                                                                                                                                                                                                                                                                              |       | **X** | **X** | **X** |                                **X**                                |
 | [创建新的讨论并对现有讨论发表评论](/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion)                                                                                                                                                                                                                                                                                                     | **X** | **X** | **X** | **X** |                                **X**                                |
-| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository#deleting-a-discussion)                                                                                                                                                                                                                                                                                             |       | **X** |       | **X** |            **X** |{% endif %}{% ifversion fpt or ghec %}
+| [删除讨论](/discussions/managing-discussions-for-your-community/managing-discussions#deleting-a-discussion)                                                                                                                                                                                                                                                                                                                |       | **X** |       | **X** |            **X** |{% endif %}{% ifversion fpt or ghec %}
 | 创建 [codespaces](/codespaces/about-codespaces)                                                                                                                                                                                                                                                                                                                                                                          |       |       | **X** | **X** |                         **X** 
 {% endif %}
 
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
index 2e8472ae58..e76584b9a7 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -20,6 +20,8 @@ shortTitle: SSH 认证机构
 
 SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 如果使用 SSH 认证中心 (CA) 为组织成员提供已签名的 SSH 证书，您可以将 CA 添加到企业帐户或组织，以便组织成员使用其证书访问组织资源。
 
+{% data reusables.organizations.ssh-ca-ghec-only %}
+
 在将 SSH CA 添加到组织或企业帐户后，您可以使用 CA 为组织成员签名客户 SSH 证书。 组织成员可以使用已签名的证书通过 Git 访问组织的仓库（并且只访问您组织的仓库）。 （可选）您可以要求成员使用 SSH 证书访问组织资源。 更多信息请参阅“[管理组织的 SSH 认证机构](/articles/managing-your-organizations-ssh-certificate-authorities)”或“[在企业中实施安全设置策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-ssh-certificate-authorities-for-your-enterprise)”。
 
 例如，您可以构建内部系统，每天早上向开发者颁发新证书。 每个开发者可以使用其每日证书处理组织在 {% data variables.product.product_name %} 上的仓库。 在一天结束时，证书会自动到期，以保护仓库，避免证书以后被窃取。
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
index 1a0403c6d4..48f78967be 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/index.md
@@ -20,3 +20,4 @@ children:
 shortTitle: 管理 Git 权限
 ---
 
+{% data reusables.organizations.ssh-ca-ghec-only %}
diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
index 4d8bdf9131..7a5f060b62 100644
--- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
+++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md
@@ -14,12 +14,13 @@ topics:
   - Organizations
   - Teams
 shortTitle: 管理 SSH 机构
+permissions: Organization owners can manage an organization's SSH certificate authorities (CA).
 ---
 
-组织所有者可以管理组织的 SSH 认证中心 (CA)。
-
 您可以通过向组织添加 SSH CA 来允许成员使用提供的 SSH 证书访问组织的仓库。 {% data reusables.organizations.can-require-ssh-cert %} 更多信息请参阅“[关于 SSH 认证中心](/articles/about-ssh-certificate-authorities)”。
 
+{% data reusables.organizations.ssh-ca-ghec-only %}
+
 {% data reusables.organizations.add-extension-to-cert %}
 
 ## 添加 SSH 认证中心
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
new file mode 100644
index 0000000000..71cc39fb9d
--- /dev/null
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization.md
@@ -0,0 +1,27 @@
+---
+title: Enabling or disabling GitHub Discussions for an organization
+intro: 'You can use {% data variables.product.prodname_discussions %} in a organization as a place for your organization to have conversations that aren''t specific to a single repository within your organization.'
+permissions: 'Organization owners can enable {% data variables.product.prodname_discussions %} for their organization.'
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+shortTitle: Organization discussions
+---
+
+## About organization discussions
+
+{% data reusables.discussions.about-organization-discussions %}
+
+You can also manage repository discussions. For more information, see "[Enabling or disabling GitHub Discussions for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository)" and "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
+
+## Enabling or disabling {% data variables.product.prodname_discussions %} for your organization
+
+{% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-organization %}
+1. To disable discussions, under "Discussions", unselect **Enable discussions for this organization**.
+
+## 延伸阅读
+
+- "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
+- "[管理社区的讨论](/discussions/managing-discussions-for-your-community)"
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/index.md b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
index 4daf8b7a32..e0000d7a2f 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/index.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/index.md
@@ -25,6 +25,7 @@ children:
   - /configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization
   - /setting-permissions-for-adding-outside-collaborators
   - /allowing-people-to-delete-issues-in-your-organization
+  - /enabling-or-disabling-github-discussions-for-an-organization
   - /managing-discussion-creation-for-repositories-in-your-organization
   - /setting-team-creation-permissions-in-your-organization
   - /managing-scheduled-reminders-for-your-organization
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
index 90c4e15b36..4cc8347fe9 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization.md
@@ -10,7 +10,7 @@ versions:
 topics:
   - Organizations
   - Teams
-shortTitle: 管理讨论创建
+shortTitle: Manage repository discussions
 ---
 
 
@@ -28,3 +28,4 @@ shortTitle: 管理讨论创建
 
 - "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
 - "[管理社区的讨论](/discussions/managing-discussions-for-your-community)"
+- "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)"
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
index 4158e4094e..596b863fc3 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization.md
@@ -22,6 +22,6 @@ shortTitle: 管理拉取请求审查
 
 {% data reusables.profile.access_org %}
 {% data reusables.profile.org_settings %}
-{% data reusables.organizations.moderation-settings %}
+1. 在边栏的“Access（访问）”部分中，单击 **{% octicon "report" aria-label="The report icon" %} 主持**。
 1. 在“{% octicon "report" aria-label="The report icon" %} Moderation（主持）”下，单击 **Code review limits（代码审查限制）**。 ![组织代码审查限制的侧边栏项屏幕截图](/assets/images/help/organizations/code-review-limits-organizations.png)
 1. 查看屏幕上的信息。 单击 **Limit review on all repositories（限制审查所有存储库）**以将审查限于具有显式访问权限的人员，或单击 **Remove review limits from all repositories（从所有存储库删除审查限制）**以从组织中的每个公共存储库中删除限制。 ![组织的代码审查限制设置屏幕截图](/assets/images/help/organizations/code-review-limits-organizations-settings.png)
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
index 58c89d7bf3..16fadbae6d 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/restricting-repository-creation-in-your-organization.md
@@ -40,10 +40,12 @@ shortTitle: 限制仓库创建
    ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons.png)
    {%- elsif fpt %}
    ![仓库创建选项](/assets/images/help/organizations/repo-creation-perms-radio-buttons-fpt.png)
+   {%- endif %}
 
+   {% ifversion fpt or ghec %}
    {% note %}
 
-   **注意：** 要将成员限制为只能创建私有仓库，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。
+   **注意：** 要将成员限制为只能创建私有仓库，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
 
    {% endnote %}
    {%- endif %}
diff --git a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
index 90c99a680b..cb9a697b3e 100644
--- a/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
+++ b/translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md
@@ -17,7 +17,6 @@ shortTitle: 设置协作者策略
 
 默认情况下，对存储库具有管理员访问权限的任何人都可以邀请外部协作者处理存储库。 您可以选择将邀请外部协作者的能力限制为仅邀请组织所有者。
 
-
 {% ifversion ghec %}
 {% note %}
 
@@ -26,6 +25,8 @@ shortTitle: 设置协作者策略
 {% endnote %}
 {% endif %}
 
+{% ifversion ghec %}如果您的组织由企业帐户拥有，则当企业所有者在企业级别设置了策略后，您{% else %}您{% endif %} 可能无法为您的组织配置此设置。 更多信息请参阅“[在企业中强制实施存储库管理策略]{% ifversion ghec %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-collaborators-to-repositories)”{% else %}(/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-inviting-outside-collaborators-to-repositories){% endif %}”。
+
 {% data reusables.organizations.outside-collaborators-use-seats %}
 
 {% data reusables.profile.access_org %}
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
index bf06aaa30e..6a17c5b579 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/index.md
@@ -20,6 +20,7 @@ children:
   - /adding-a-billing-manager-to-your-organization
   - /removing-a-billing-manager-from-your-organization
   - /managing-security-managers-in-your-organization
+  - /managing-moderators-in-your-organization
 shortTitle: 使用角色管理访问
 ---
 
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
new file mode 100644
index 0000000000..3f7289f725
--- /dev/null
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization.md
@@ -0,0 +1,40 @@
+---
+title: Managing moderators in your organization
+intro: 'You can give an individual or team in your organization the ability to block and limit access, by assigning them to the moderator role.'
+permissions: Organization owners can assign the moderator role.
+versions:
+  fpt: '*'
+  ghec: '*'
+topics:
+  - Organizations
+  - Teams
+  - Community
+shortTitle: Managing moderators
+---
+
+## About organization moderators
+
+Sometimes it's necessary to block a contributor, or to set up interaction limits for your organization, or for individual repositories. As an organization owner, you can perform these tasks, but you may want to delegate these tasks to other members of your organization. You can do this by assigning an organization member, or a team, to the moderator role.
+
+Organization moderators can:
+* Block and unblock users from the organization. 更多信息请参阅“[阻止用户访问组织](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)”。
+* Manage organization interaction limits. 更多信息请参阅“[限制组织中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)”。
+* Manage repository interaction limits. 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。
+* Hide comments in all public repositories owned by the organization. For more information, see "[Managing disruptive comments](/communities/moderating-comments-and-conversations/managing-disruptive-comments)."
+
+Making someone an organization moderator does not give them additional abilities other than those listed above. For example, someone who only has read access to a repository will not gain write access by being made a moderator.
+
+You can add up to 10 individual people, or teams, as moderators. If you've already assigned 10 individuals and/or teams as users and you want to add more, you can group people in a moderators team and then use this to replace one or more of the existing assignments. For more information, see "[Creating a team](/organizations/organizing-members-into-teams/creating-a-team)."
+
+## Adding an organization moderator
+
+{% data reusables.profile.access_org %}
+{% data reusables.profile.org_settings %}
+{% data reusables.organizations.security-and-analysis %}
+1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation** then click **Moderators**.
+1. Under **Moderators**, search for and select the person or team you want to assign the moderator role. Each person or team you select will appear in a list below the search bar. ![The Moderators search field and list](/assets/images/help/organizations/add-moderators.png)
+
+
+## Removing an organization moderator
+
+Follow steps 1-4 above, then click **Remove moderator** beside the person or team you want to remove as a moderator.
diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
index 75674da5d9..115d3689f7 100644
--- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
+++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization.md
@@ -41,6 +41,9 @@ shortTitle: 组织中的角色
 组织中人员的默认非管理角色是组织成员。 默认情况下，组织成员具有许多权限，包括能够创建存储库和项目板。
 
 {% ifversion fpt or ghec %}
+### 组织版主
+版主是组织成员，除了其作为成员的权限外，还可以阻止和取消阻止非成员参与者、设置交互限制以及隐藏组织拥有的公共存储库中的评论。 更多信息请参阅“[管理组织中的版主](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-moderators-in-your-organization)”。
+
 ### 帐单管理员
 帐单管理员是可以管理组织的帐单设置（如付款信息）的用户。 如果组织成员通常无权访问计费资源，则这是一个有用的选项。 更多信息请参阅“[为组织添加帐单管理员](/organizations/managing-peoples-access-to-your-organization-with-roles/adding-a-billing-manager-to-your-organization)”。
 
@@ -73,162 +76,165 @@ shortTitle: 组织中的角色
 {% endif %}
 
 {% ifversion fpt or ghec %}
-<!--Dotcom and cloud version has extra column for Billing managers-->
+<!-- Free/Pro/Team and GHEC versions have extra columns for Moderators and Billing managers-->
 
-| 组织权限                                                                                                                                                                                                                                                |  所有者  |  成员   | 帐单管理员 |                 安全管理员                 |
-|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-------------------------------------:|
-| 创建仓库（详细信息请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”）                                                                                                                                                         | **X** | **X** |       |                 **X**                 |
-| 查看和编辑帐单信息                                                                                                                                                                                                                                           | **X** |       | **X** |                                       |
-| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |       |       |                                       |
-| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |       |       |                                       |
-| 从组织删除成员                                                                                                                                                                                                                                             | **X** |       |       |                                       |
-| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |       |       |                                       |
-| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |       |       |                                       |
-| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |       |       |                                       |
-| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                            | **X** |       |       |                                       |
-| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”）                                                                                                                  | **X** |       |       |                                       |
-| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |       |       |                                       |
-| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |       |       |                                       |
-| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** |       |       |                                       |
-| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |       |       |                                       |
-| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |       |       |                                       |
-| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |       |       |                                       |
-| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |       |       |                                       |
-| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** | **X** |       |                 **X**                 |
-| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |       |       |                                       |
-| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** | **X** |       |                 **X**                 |
-| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** | **X** |       |                 **X**                 |
-| @提及任何可见团队                                                                                                                                                                                                                                           | **X** | **X** |       |                 **X**                 |
-| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** | **X** |       |                 **X**                 |
-| 查看组织洞见（详细信息请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”）                                                                                                                                                                      | **X** | **X** |       |                 **X**                 |
-| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** | **X** |       |                 **X**                 |
-| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |       |       |                                       |
-| 编辑和删除**所有团队**的团队讨论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                             | **X** |       |       |                                       |
-| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** | **X** |       |                 **X**                 |
-| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |       |       |                                       |
-| 管理组织依赖项洞见的显示（详细信息请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”）                                                                                                                                 | **X** |       |       |                                       |
-| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** |       |       |                                       |
-| 赞助帐户和管理组织的赞助（更多信息请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)”）                                                                                                                                                                     | **X** |       | **X** |                 **X**                 |
-| 管理赞助帐户的电子邮件更新（更多信息请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)”）                                                                                                      | **X** |       |       |                                       |
-| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)”）                                                                                                                     | **X** |       |       |                                       |
-| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** |       |       |                                       |
-| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                                   | **X** |       |       |                 **X**                 |
-| 查看组织的安全概述（有关详细信息，请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”）                                                                                                                                                       | **X** |       |       |      **X** |{% ifversion ghec %}
-| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                          | **X** |       |       |                                       |
-| [管理用户对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)                                                                                    | **X** |       |       |                                       |
-| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |       |       |             
+| 组织权限                                                                                                                                                                                                                                          |  所有者  |  成员   |  版主   | 帐单管理员 |            安全管理员            |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:-----:|:-----:|:---------------------------:|
+| 创建仓库（请参阅“[限制在组织中创建仓库](/articles/restricting-repository-creation-in-your-organization)”）                                                                                                                                                       | **X** | **X** | **X** |       |            **X**            |
+| 查看和编辑帐单信息                                                                                                                                                                                                                                     | **X** |       |       | **X** |                             |
+| 邀请人员加入组织                                                                                                                                                                                                                                      | **X** |       |       |       |                             |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                   | **X** |       |       |       |                             |
+| 从组织删除成员                                                                                                                                                                                                                                       | **X** |       |       |       |                             |
+| 恢复组织的前成员                                                                                                                                                                                                                                      | **X** |       |       |       |                             |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                              | **X** |       |       |       |                             |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                               | **X** |       |       |       |                             |
+| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                      | **X** |       |       |       |                             |
+| 设置预定提醒（请参阅“[管理拉取请求的预定提醒](/github/setting-up-and-managing-organizations-and-teams/managing-scheduled-reminders-for-pull-requests)”）                                                                                                            | **X** |       |       |       |                             |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                | **X** |       |       |       |                             |
+| 访问组织审核日志                                                                                                                                                                                                                                      | **X** |       |       |       |                             |
+| 编辑组织的资料页面（请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                      | **X** |       |       |       |                             |
+| 验证组织的域（请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                         | **X** |       |       |       |                             |
+| 将电子邮件通知限于已经验证或批准的域名（请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                                | **X** |       |       |       |                             |
+| 删除**所有团队**                                                                                                                                                                                                                                    | **X** |       |       |       |                             |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                 | **X** |       |       |       |                             |
+| 创建团队（请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                   | **X** | **X** | **X** |       |            **X**            |
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                     | **X** |       |       |       |                             |
+| 创建项目板（请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                               | **X** | **X** | **X** |       |            **X**            |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                   | **X** | **X** | **X** |       |            **X**            |
+| @提及任何可见团队                                                                                                                                                                                                                                     | **X** | **X** | **X** |       |            **X**            |
+| 可成为*团队维护员*                                                                                                                                                                                                                                    | **X** | **X** | **X** |       |            **X**            |
+| 查看组织洞见（请参阅“[查看用于组织的洞见](/articles/viewing-insights-for-your-organization)”）                                                                                                                                                                    | **X** | **X** | **X** |       |            **X**            |
+| 查看并发布公共团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** | **X** | **X** |       |            **X**            |
+| 查看并发布私有团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** |       |       |       |                             |
+| 编辑和删除**所有团队**的团队讨论（请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                           | **X** |       |       |       |                             |
+| 对组织禁用团队讨论（请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                       | **X** |       |       |       |                             |
+| 隐藏对可写提交、拉取请求和议题的评论（请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                         | **X** | **X** | **X** |       |            **X**            |
+| 隐藏对_所有_提交、拉取请求和议题的评论（请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                       | **X** |       | **X** |       |            **X**            |
+| 阻止和取消阻止非成员贡献者（请参阅“[阻止用户参与您的组织](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)”）                                                                                                                       | **X** |       | **X** |       |                             |
+| 限制公共存储库中某些用户的交互（请参阅“[限制组织中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)”）                                                                                                               | **X** |       | **X** |       |                             |
+| 管理组织依赖项洞见的显示（请参阅“[更改组织依赖项洞见的可见性](/articles/changing-the-visibility-of-your-organizations-dependency-insights)”）                                                                                                                               | **X** |       |       |       |                             |
+| 设置**所有团队**的团队头像（请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                | **X** |       |       |       |                             |
+| 赞助帐户和管理组织的赞助（请参阅“[赞助开源贡献者](/sponsors/sponsoring-open-source-contributors)”）                                                                                                                                                                   | **X** |       |       | **X** |            **X**            |
+| 管理赞助帐户的电子邮件更新（请参阅“[管理组织赞助帐户的更新](/organizations/managing-organization-settings/managing-updates-from-accounts-your-organization-sponsors)”）                                                                                                    | **X** |       |       |       |                             |
+| 将您的赞助归因于另一个组织（更多信息请参阅“[将赞助归因于组织](/sponsors/sponsoring-open-source-contributors/attributing-sponsorships-to-your-organization)”）                                                                                                               | **X** |       |       |       |                             |
+| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”） | **X** |       |       |       |                             |
+| 管理安全性和分析设置（请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                               | **X** |       |       |       |            **X**            |
+| 查看组织的安全概述（请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”）                                                                                                                                                        | **X** |       |       |       | **X** |{% ifversion ghec %}
+| 启用并实施 [SAML 单点登录](/articles/about-identity-and-access-management-with-saml-single-sign-on)                                                                                                                                                    | **X** |       |       |       |                             |
+| [管理用户对组织的 SAML 访问](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)                                                                              | **X** |       |       |       |                             |
+| 管理组织的 SSH 认证中心（请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                      | **X** |       |       |       |        
 {% endif %}
-| 转让仓库                                                                                                                                                                                                                                                | **X** |       |       |                                       |
-| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序                                                                                                                                                                              | **X** |       |       |                                       |
-| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序                                                                                                                                                                                         | **X** |       |       |                                       |
-| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)                                                                                 | **X** |       |       |                 **X**                 |
-| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）                  | **X** |       |       |                 **X**                 |
-| [管理复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)                                                                                                                                           | **X** |       |       |                                       |
-| [限制组织中公共仓库的活动](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)                                                                                                                                       | **X** |       |       |                                       |
-| 拉取（读取）组织中的*所有存储库*                                                                                                                                                                                                                                   | **X** |       |       |                 **X**                 |
-| 推送（写入）和克隆（复制）组织中的*所有存储库*                                                                                                                                                                                                                            | **X** |       |       |                                       |
-| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                             | **X** |       |       |                                       |
-| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                         | **X** |       |       | |{% ifversion ghec or ghes or ghae %}
-| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                             | **X** |       |       |             
+| 转让仓库                                                                                                                                                                                                                                          | **X** |       |       |       |                             |
+| 购买、安装、管理其帐单以及取消 {% data variables.product.prodname_marketplace %} 应用程序                                                                                                                                                                        | **X** |       |       |       |                             |
+| 列出 {% data variables.product.prodname_marketplace %} 中的应用程序                                                                                                                                                                                   | **X** |       |       |       |                             |
+| 接收所有组织仓库[关于易受攻击的依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)                                                                           | **X** |       |       |       |            **X**            |
+| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）            | **X** |       |       |       |            **X**            |
+| [管理复刻策略](/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization)                                                                                                                                     | **X** |       |       |       |                             |
+| [限制组织中公共仓库的活动](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-organization)                                                                                                                                 | **X** |       |       |       |                             |
+| 拉取（读取）组织中的*所有存储库*                                                                                                                                                                                                                             | **X** |       |       |       |            **X**            |
+| 推送（写入）和克隆（复制）组织中的*所有存储库*                                                                                                                                                                                                                      | **X** |       |       |       |                             |
+| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                       | **X** |       |       |       |                             |
+| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                   | **X** |       |       |       |    |{% ifversion ghec %}
+| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                       | **X** |       |       |       |        
 {% endif %}
-| 管理默认分支名称（请参阅“[管理组织中仓库的默认标签](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”）                                                                                                 | **X** |       |       |                                       |
-| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |       |       |         |{% ifversion ghec %}
-| 启用团队同步（详情请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”）                                                                                                   | **X** |       |       |             
+| 管理默认分支名称（请参阅“[管理组织中仓库的默认标签](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”）                                                                                           | **X** |       |       |       |                             |
+| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                          | **X** |       |       |       |    |{% ifversion ghec %}
+| 启用团队同步（请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”）                                                                                               | **X** |       |       |       |        
 {% endif %}
-| 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”）                                                                                                                 | **X** |       |       |                                       |
+| 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”）                                                                                                           | **X** |       |       |       |                             |
 
 {% elsif ghes > 3.2 or ghae-issue-4999 %}
-<!--GHES 3.3+ and eventual GHAE release don't have the extra column for Billing managers, but have security managers-->
+<!-- GHES 3.3+ and eventual GHAE release don't have the extra columns for Moderators and Billing managers. -->
 
-| 组织操作                                                                                                                                                                                                                                                |  所有者  |  成员   |                    安全管理员                     |
-|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:--------------------------------------------:|
-| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |       |                                              |
-| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |       |                                              |
-| 从组织删除成员                                                                                                                                                                                                                                             | **X** |       |                      |                       |
-| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |       |                      |                       |
-| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |       |                                              |
-| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |       |                                              |
-| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                            | **X** |       |                                              |
-| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |       |                                              |
-| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |       |                                              |
-| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** |       |         |{% ifversion ghes > 3.1 %}
-| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |       |                                              |
-| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |       |                 
+| 组织操作                                                                                                                                                                                                                                          |  所有者  |  成员   |                    安全管理员                     |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:-----:|:--------------------------------------------:|
+| 邀请人员加入组织                                                                                                                                                                                                                                      | **X** |       |                                              |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                   | **X** |       |                                              |
+| 从组织删除成员                                                                                                                                                                                                                                       | **X** |       |                      |                       |
+| 恢复组织的前成员                                                                                                                                                                                                                                      | **X** |       |                      |                       |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                              | **X** |       |                                              |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                               | **X** |       |                                              |
+| 配置代码审查分配（请参阅“[管理团队的代码审查分配](/organizations/organizing-members-into-teams/managing-code-review-assignment-for-your-team)”）                                                                                                                      | **X** |       |                                              |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                | **X** |       |                                              |
+| 访问组织审核日志                                                                                                                                                                                                                                      | **X** |       |                                              |
+| 编辑组织的资料页面（请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                      | **X** |       |         |{% ifversion ghes > 3.1 %}
+| 验证组织的域（请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                         | **X** |       |                                              |
+| 将电子邮件通知限于已经验证或批准的域名（请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                                | **X** |       |                 
 {% endif %}
-| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |       |                                              |
-| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |       |                                              |
-| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** | **X** |                    **X**                     |
-| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** | **X** |                    **X**                     |
-| @提及任何可见团队                                                                                                                                                                                                                                           | **X** | **X** |                    **X**                     |
-| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** | **X** |                    **X**                     |
-| 转让仓库                                                                                                                                                                                                                                                | **X** |       |                                              |
-| 管理安全性和分析设置（详情请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                                   | **X** |       |      **X** |{% ifversion ghes > 3.1 %}
-| 查看组织的安全概述（有关详细信息，请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”）                                                                                                                                                       | **X** |       | **X** |{% endif %}{% ifversion ghes > 3.2 %}
-| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）                  | **X** |       |              **X** 
+| 删除**所有团队**                                                                                                                                                                                                                                    | **X** |       |                                              |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                 | **X** |       |                                              |
+| 创建团队（请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                   | **X** | **X** |                    **X**                     |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                   | **X** | **X** |                    **X**                     |
+| @提及任何可见团队                                                                                                                                                                                                                                     | **X** | **X** |                    **X**                     |
+| 可成为*团队维护员*                                                                                                                                                                                                                                    | **X** | **X** |                    **X**                     |
+| 转让仓库                                                                                                                                                                                                                                          | **X** |       |                                              |
+| 管理安全性和分析设置（请参阅“[管理组织的安全性和分析设置](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)”）                                                                                               | **X** |       |      **X** |{% ifversion ghes > 3.1 %}
+| 查看组织的安全概述（请参阅“[关于安全概述](/code-security/security-overview/about-the-security-overview)”）                                                                                                                                                        | **X** |       | **X** |{% endif %}{% ifversion ghes > 3.2 %}
+| 管理 {% data variables.product.prodname_dependabot_security_updates %}（请参阅“[关于 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)”）            | **X** |       |              **X** 
 {% endif %}
-| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |       |                                              |
-| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** | **X** |                    **X**                     |
-| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** | **X** |                    **X**                     |
-| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |       |                                              |
-| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                            | **X** |       |                      |                       |
-| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** | **X** |                    **X**                     |
-| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |       |                                              |
-| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** |       |         |{% ifversion ghes > 3.0 %}
-| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** |       |                 
+| 管理组织的 SSH 认证中心（请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                      | **X** |       |                                              |
+| 创建项目板（请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                               | **X** | **X** |                    **X**                     |
+| 查看并发布公共团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** | **X** |                    **X**                     |
+| 查看并发布私有团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** |       |                                              |
+| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                      | **X** |       |                      |                       |
+| 隐藏对提交、拉取请求和议题的评论（请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                           | **X** | **X** |                    **X**                     |
+| 对组织禁用团队讨论（请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                       | **X** |       |                                              |
+| 设置**所有团队**的团队头像（请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                | **X** |       |         |{% ifversion ghes > 3.0 %}
+| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”） | **X** |       |                 
 {% endif %}
-| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |       |                                              |
-| 拉取（读取）组织中的*所有存储库*                                                                                                                                                                                                                                   | **X** |       |                    **X**                     |
-| 推送（写入）和克隆（复制）组织中的*所有存储库*                                                                                                                                                                                                                            | **X** |       |                                              |
-| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                             | **X** |       |                                              |
-| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                         | **X** |       |                                              |
-| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                             | **X** |       |                                              |
-| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |       |    |{% if pull-request-approval-limit %}
-| 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”）                                                                                                                 | **X** |       |               |  
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                     | **X** |       |                                              |
+| 拉取（读取）组织中的*所有存储库*                                                                                                                                                                                                                             | **X** |       |                    **X**                     |
+| 推送（写入）和克隆（复制）组织中的*所有存储库*                                                                                                                                                                                                                      | **X** |       |                                              |
+| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                       | **X** |       |                                              |
+| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                   | **X** |       |                                              |
+| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                       | **X** |       |                                              |
+| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                          | **X** |       |    |{% if pull-request-approval-limit %}
+| 管理组织中的拉取请求审核（请参阅“[管理组织中的拉取请求审核](/organizations/managing-organization-settings/managing-pull-request-reviews-in-your-organization)”）                                                                                                           | **X** |       |               |  
 {% endif %}
 {% ifversion ghae %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** | |  |{% endif %}
 
 
 {% else %}
-<!--GHES and GHAE older versions don't have the extra column for Billing managers or Security managers-->
+<!-- GHES and GHAE older versions don't have columns for Moderators, Billing managers or Security managers. -->
 
-| 组织操作                                                                                                                                                                                                                                                |  所有者  |               成员               |
-|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------:|
-| 邀请人员加入组织                                                                                                                                                                                                                                            | **X** |                                |
-| 编辑和取消邀请加入组织                                                                                                                                                                                                                                         | **X** |                                |
-| 从组织删除成员                                                                                                                                                                                                                                             | **X** |               |                |
-| 恢复组织的前成员                                                                                                                                                                                                                                            | **X** |               |                |
-| 添加和删除**所有团队**的人员                                                                                                                                                                                                                                    | **X** |                                |
-| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                                     | **X** |                                |
-| 配置代码审查分配（请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”）                                                                                                                              | **X** |                                |
-| 添加协作者到**所有仓库**                                                                                                                                                                                                                                      | **X** |                                |
-| 访问组织审核日志                                                                                                                                                                                                                                            | **X** |                                |
-| 编辑组织的资料页面（详细信息请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                        | **X** | |  |{% ifversion ghes > 3.1 %}
-| 验证组织的域（详细信息请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                           | **X** |                                |
-| 将电子邮件通知限于已经验证或批准的域名（有关详细信息，请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                               | **X** |          
+| 组织操作                                                                                                                                                                                                                                          |  所有者  |               成员               |
+|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:------------------------------:|
+| 邀请人员加入组织                                                                                                                                                                                                                                      | **X** |                                |
+| 编辑和取消邀请加入组织                                                                                                                                                                                                                                   | **X** |                                |
+| 从组织删除成员                                                                                                                                                                                                                                       | **X** |               |                |
+| 恢复组织的前成员                                                                                                                                                                                                                                      | **X** |               |                |
+| 添加和删除**所有团队**的人员                                                                                                                                                                                                                              | **X** |                                |
+| 将组织成员升级为*团队维护员*                                                                                                                                                                                                                               | **X** |                                |
+| 配置代码审查分配（请参阅“[管理团队的代码审查设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”）                                                                                                                        | **X** |                                |
+| 添加协作者到**所有仓库**                                                                                                                                                                                                                                | **X** |                                |
+| 访问组织审核日志                                                                                                                                                                                                                                      | **X** |                                |
+| 编辑组织的资料页面（请参阅“[关于组织的资料](/github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-organizations-profile)”）                                                                                                      | **X** | |  |{% ifversion ghes > 3.1 %}
+| 验证组织的域（请参阅“[验证组织的域](/articles/verifying-your-organization-s-domain)”）                                                                                                                                                                         | **X** |                                |
+| 将电子邮件通知限于已经验证或批准的域名（请参阅“[限制组织的电子邮件通知](/organizations/keeping-your-organization-secure/restricting-email-notifications-for-your-organization)”）                                                                                                | **X** |          
 {% endif %}
-| 删除**所有团队**                                                                                                                                                                                                                                          | **X** |                                |
-| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                       | **X** |                                |
-| 创建团队（详细信息请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                     | **X** |             **X**              |
-| 查看所有组织成员和团队                                                                                                                                                                                                                                         | **X** |             **X**              |
-| @提及任何可见团队                                                                                                                                                                                                                                           | **X** |             **X**              |
-| 可成为*团队维护员*                                                                                                                                                                                                                                          | **X** |             **X**              |
-| 转让仓库                                                                                                                                                                                                                                                | **X** |                                |
-| 管理组织的 SSH 认证中心（详细信息请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                        | **X** |                                |
-| 创建项目板（详细信息请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                                 | **X** |            **X** |             |
-| 查看并发布公共团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |            **X** |             |
-| 查看并发布私有团队讨论到**所有团队**（详细信息请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                         | **X** |               |                |
-| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                            | **X** |               |                |
-| 隐藏对提交、拉取请求和议题的评论（详细信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                             | **X** |         **X** | **X**          |
-| 对组织禁用团队讨论（详细信息请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                         | **X** |               |                |
-| 设置**所有团队**的团队头像（详细信息请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                  | **X** | |  |{% ifversion ghes > 3.0 %}
-| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”了解详细信息） | **X** |          
+| 删除**所有团队**                                                                                                                                                                                                                                    | **X** |                                |
+| 删除组织帐户，包括所有仓库                                                                                                                                                                                                                                 | **X** |                                |
+| 创建团队（请参阅“[在组织中设置团队创建权限](/articles/setting-team-creation-permissions-in-your-organization)”）                                                                                                                                                   | **X** |             **X**              |
+| 查看所有组织成员和团队                                                                                                                                                                                                                                   | **X** |             **X**              |
+| @提及任何可见团队                                                                                                                                                                                                                                     | **X** |             **X**              |
+| 可成为*团队维护员*                                                                                                                                                                                                                                    | **X** |             **X**              |
+| 转让仓库                                                                                                                                                                                                                                          | **X** |                                |
+| 管理组织的 SSH 认证中心（请参阅“[管理组织的 SSH 认证中心](/articles/managing-your-organizations-ssh-certificate-authorities)”）                                                                                                                                      | **X** |                                |
+| 创建项目板（请参阅“[组织的项目板权限](/articles/project-board-permissions-for-an-organization)”）                                                                                                                                                               | **X** |            **X** |             |
+| 查看并发布公共团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** |            **X** |             |
+| 查看并发布私有团队讨论到**所有团队**（请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”）                                                                                                                                       | **X** |               |                |
+| 编辑和删除**所有团队**中的团队讨论（更多信息请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments)”）                                                                                                                      | **X** |               |                |
+| 隐藏对提交、拉取请求和议题的评论（请参阅“[管理破坏性评论](/communities/moderating-comments-and-conversations/managing-disruptive-comments/#hiding-a-comment)”）                                                                                                           | **X** |         **X** | **X**          |
+| 对组织禁用团队讨论（请参阅“[对组织禁用团队讨论](/articles/disabling-team-discussions-for-your-organization)”）                                                                                                                                                       | **X** |               |                |
+| 设置**所有团队**的团队头像（请参阅“[设置团队的头像](/articles/setting-your-team-s-profile-picture)”）                                                                                                                                                                | **X** | |  |{% ifversion ghes > 3.0 %}
+| 管理从组织中的仓库发布 {% data variables.product.prodname_pages %} 站点（请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”） | **X** |          
 {% endif %}
-| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                           | **X** |               |                |
-| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库*                                                                                                                                                                                                                      | **X** |                                |
-| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                             | **X** |                                |
-| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                         | **X** |                                |
-| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                             | **X** |                                |
-| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                                | **X** |                                |
+| [在组织的层次结构中移动团队](/articles/moving-a-team-in-your-organization-s-hierarchy)                                                                                                                                                                     | **X** |               |                |
+| 拉取（读取）、推送（写入）和克隆（复制）组织中的*所有仓库*                                                                                                                                                                                                                | **X** |                                |
+| 将组织成员转换为[外部协作者](#outside-collaborators)                                                                                                                                                                                                       | **X** |                                |
+| [查看对组织仓库具有访问权限的人员](/articles/viewing-people-with-access-to-your-repository)                                                                                                                                                                   | **X** |                                |
+| [导出具有组织仓库访问权限人员的列表](/articles/viewing-people-with-access-to-your-repository/#exporting-a-list-of-people-with-access-to-your-repository)                                                                                                       | **X** |                                |
+| 管理默认标签（请参阅“[管理组织中仓库的默认标签](/articles/managing-default-labels-for-repositories-in-your-organization)”）                                                                                                                                          | **X** |                                |
 {% ifversion ghae %}| 管理 IP 允许列表（请参阅“[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”）| **X** |{% endif %}
 
 {% endif %}
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
index b4bbfd56eb..1564e4da52 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on.md
@@ -18,6 +18,8 @@ shortTitle: 使用 SAML SSO 的 IAM
 
 {% data reusables.saml.dotcom-saml-explanation %}
 
+{% data reusables.saml.ghec-only %}
+
 {% data reusables.saml.saml-accounts %}
 
 组织所有者可以对单个组织强制实施 SAML SSO，企业所有者可以为企业帐户中的所有组织强制实施 SAML SSO。 更多信息请参阅“[配置企业的 SAML 单点登录](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
index e10543f3ce..30a3b932ce 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/about-scim.md
@@ -15,6 +15,8 @@ topics:
 
 如果在组织中使用 [SAML SSO](/articles/about-identity-and-access-management-with-saml-single-sign-on)，您可以实施 SCIM 来添加、管理和删除组织成员对 {% data variables.product.product_name %} 的访问权限。 例如，管理员可以使用 SCIM 撤销配置组织成员，以及从组织中自动删除成员。
 
+{% data reusables.saml.ghec-only %}
+
 如果您使用 SAML SSO 而不实施 SCIM，将不能自动撤销配置。 当组织成员的会话在其访问权限从 IdP 删除后到期时，他们就会自动从组织中删除。 即使会话已到期，通过授权的令牌也可授予对组织的访问。 要删除访问权限，组织管理员可以手动从组织删除授权的令牌，或者通过 SCIM 自动执行删除。
 
 这些身份提供程序兼容组织的 {% data variables.product.product_name %} SCIM API。 更多信息请参阅 {% ifversion ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 文档中的 [SCIM](/rest/reference/scim) 。
@@ -24,7 +26,7 @@ topics:
 
 {% note %}
 
-**注：**{% data reusables.scim.nameid-and-username-must-match %}
+**注意：** {% data reusables.scim.nameid-and-username-must-match %}
 
 {% endnote %}
 
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 040547594d..733502f3e1 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -16,6 +16,8 @@ shortTitle: 使用 Octa 配置 SAML 和 SCIM
 
 通过将组织配置为将 SAML SSO 和 SCIM 与身份提供程序 (IdP) Okta 结合使用，您可以从一个中心界面控制对您 {% data variables.product.product_location %} 和其他 Web 应用程序上的组织的访问。
 
+{% data reusables.saml.ghec-only %}
+
 SAML SSO 控制并保护对组织资源（如仓库、议题和拉取请求）的访问。 当您在 Okta 中进行更改时，SCIM 会自动添加、管理和删除成员对您在 {% data variables.product.product_location %} 上的组织的访问权限。 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”和“[关于 SCIM](/organizations/managing-saml-single-sign-on-for-your-organization/about-scim)”。
 
 启用 SCIM 后，您在 Okta 中为其分配了 {% data variables.product.prodname_ghe_cloud %} 应用程序的任何用户都可以使用以下配置。
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
index b17e1b0ad7..b53ca8c461 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/connecting-your-identity-provider-to-your-organization.md
@@ -14,6 +14,8 @@ shortTitle: 连接 IdP
 
 为您的 {% data variables.product.product_name %} 组织启用 SAML SSO时，会将您的身份提供商 (IDP) 连接到组织。 更多信息请参阅“[对组织启用并测试 SAML 单点登录](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)”。
 
+{% data reusables.saml.ghec-only %}
+
 您可以在 IdP 文档中找到 IdP 的 SAML 和 SCIM 实现详细信息。
 - Active Directory Federation Services (AD FS) [SAML](https://docs.microsoft.com/windows-server/identity/active-directory-federation-services)
 - Azure Active Directory (Azure AD) [SAML](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-tutorial) 和 [SCIM](https://docs.microsoft.com/azure/active-directory/active-directory-saas-github-provisioning-tutorial)
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
index cd8bbbf705..6bd1e8ea04 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md
@@ -16,6 +16,8 @@ shortTitle: 启用和测试 SAML SSO
 
 无需所有成员使用 SAML SSO，即可在组织中将其启用。 在组织中启用但不实施 SAML SSO 可帮助组织顺利采用 SAML SSO。 一旦组织内的大多数成员使用 SAML SSO，即可在组织内将其实施。
 
+{% data reusables.saml.ghec-only %}
+
 如果启用但不实施 SAML SSO，则选择不使用 SAML SSO 的组织成员仍可以是组织的成员。 有关实施 SAML SSO 的更多信息，请参阅“[对组织实施 SAML 单点登录](/articles/enforcing-saml-single-sign-on-for-your-organization)”。
 
 {% data reusables.saml.outside-collaborators-exemption %}
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
index 90f24dc7d3..107aa3c58a 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization.md
@@ -20,6 +20,8 @@ shortTitle: 强制 SAML 单点登录
 
 您也可以对组织实施 SAML SSO。 {% data reusables.saml.when-you-enforce %} 实施会从组织中删除尚未通过 IdP 进行身份验证的任何成员和管理员。 {% data variables.product.company_short %} 将向每个被删除的用户发送电子邮件通知。
 
+{% data reusables.saml.ghec-only %}
+
 {% data reusables.saml.removed-users-can-rejoin %} 如果用户在三个月内重新加入组织，则该用户的访问权限和设置将恢复。 更多信息请参阅“[恢复组织的前成员](/articles/reinstating-a-former-member-of-your-organization)”。
 
 未在组织的 IdP 中设置外部身份的自动程序和服务帐户在执行 SAML SSO 时也将被删除。 有关自动程序和服务帐户的更多信息，请参阅“[使用 SAML 单点登录管理自动程序和服务帐户](/articles/managing-bots-and-service-accounts-with-saml-single-sign-on)”。
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
index 167639f494..8d4faa6336 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/index.md
@@ -25,3 +25,4 @@ children:
 shortTitle: 管理 SAML 单点登录
 ---
 
+{% data reusables.saml.ghec-only %}
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
index 1d235b4652..12f040ee18 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization.md
@@ -24,6 +24,8 @@ shortTitle: 管理团队同步
 
 {% data reusables.identity-and-permissions.about-team-sync %}
 
+{% data reusables.saml.ghec-only %}
+
 {% data reusables.identity-and-permissions.supported-idps-team-sync %}
 
 {% data reusables.identity-and-permissions.sync-team-with-idp-group %}
diff --git a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
index 188901baca..c22b7b1ace 100644
--- a/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
+++ b/translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/preparing-to-enforce-saml-single-sign-on-in-your-organization.md
@@ -12,6 +12,8 @@ topics:
 shortTitle: 准备执行 SAML SSO
 ---
 
+{% data reusables.saml.ghec-only %}
+
 {% data reusables.saml.when-you-enforce %} 在组织中执行 SAML SSO 之前，您应该审核组织成员资格，启用 SAML SSO，并审核组织成员的 SAML 访问权限。 更多信息请参阅以下文章。
 
 | 任务                       | 更多信息                      |
diff --git a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
index 2f92adc46d..1ffeed2655 100644
--- a/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
+++ b/translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md
@@ -58,7 +58,7 @@ For more information, see "[About permissions for {% data variables.product.prod
 {% endif %}
 
 ## Supported clients and formats
-<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes to supported clients or formats. -->
+<!-- If you make changes to this feature, check whether any of the changes affect languages listed in /get-started/learning-about-github/github-language-support. If so, please update the language support article accordingly. -->
 
 {% data variables.product.prodname_registry %} uses the native package tooling commands you're already familiar with to publish and install package versions.
 ### Support for package registries
diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
index fae90d1a95..29c47f7a8b 100644
--- a/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
+++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md
@@ -5,7 +5,7 @@ product: '{% data reusables.gated-features.private-pages %}'
 versions:
   fpt: '*'
   ghec: '*'
-permissions: 'People with admin permissions for a repository can change the visibility of a {% data variables.product.prodname_pages %} site.'
+permissions: 'People with admin access to a repository can change the visibility of a {% data variables.product.prodname_pages %} site.'
 redirect_from:
   - /github/working-with-github-pages/changing-the-visibility-of-your-github-pages-site
 shortTitle: 更改站点可见性
@@ -15,6 +15,12 @@ shortTitle: 更改站点可见性
 
 如果对 {% data variables.product.prodname_pages %} 具有访问控制权限，您便可以通过私密发布站点来限制访问您的 {% data variables.product.prodname_pages %} 站点。 只有对发布站点的仓库具有读取权限的人才可访问私密发布的站点。 您可以使用私密发布的站点与企业成员分享您的内部文档或知识库。
 
+{% note %}
+
+**注意：** 若要私下发布 {% data variables.product.prodname_pages %} 网站，您的组织必须使用 {% data variables.product.prodname_ghe_cloud %}。 {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+
 如果您的企业使用 {% data variables.product.prodname_emus %}，则所有 {% data variables.product.prodname_pages %} 站点都是私密发布的。 有关 {% data variables.product.prodname_emus %} 的更多信息，请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
 
 如果您的组织使用 {% data variables.product.prodname_ghe_cloud %} 而没有 {% data variables.product.prodname_emus %}，您可以选择在互联网上私下或公开地向任何人发布您的站点。 从组织拥有的私人或内部仓库发布的项目站点可使用访问控制。 您无法管理组织站点的访问控制。 有关 {% data variables.product.prodname_pages %} 站点类型的更多信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
index c0bee27748..25a60c76cf 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue.md
@@ -59,7 +59,7 @@ You can view the merge queue for a base branch in various places on {% data vari
 
   ![在“拉取请求”页面中查看合并队列](/assets/images/help/pull_requests/clock-icon-in-pull-request-list.png)
 
-- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click **the merge queue** link.
+- On the pull request page when merge queue is required for merging, scroll to the bottom of the timeline and click the **merge queue** link.
 
   ![Merge queue link on pull request](/assets/images/help/pull_requests/merge-queue-link.png)
 
diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
index c3cebcbc92..0b5390b25d 100644
--- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
+++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md
@@ -35,6 +35,10 @@ shortTitle: 查看依赖项更改
 
 依赖关系审核允许您“左移”。 您可以使用所提供的预测信息在易受攻击的依赖项进入生产之前捕获它们。 更多信息请参阅“[关于依赖项审查](/code-security/supply-chain-security/about-dependency-review)”。
 
+{% ifversion fpt or ghec or ghes > 3.5 or ghae-issue-6396 %}
+可以使用依赖项审查 GitHub 操作来帮助对存储库中的拉取请求强制实施依赖项审查。 更多信息请参阅“[依赖项审查实施](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review#dependency-review-enforcement)”。
+{% endif %}
+
 ## 审查拉取请求中的依赖项
 
 {% data reusables.repositories.sidebar-pr %}
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
index a76f791cc3..09c7bbbf14 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches.md
@@ -50,6 +50,9 @@ topics:
 {% ifversion fpt or ghec %}
 - [需要合并队列](#require-merge-queue)
 {% endif %}
+{%- if required-deployments %}
+- [要求部署在合并之前成功](#require-deployments-to-succeed-before-merging)
+{%- endif %}
 - [包括管理员](#include-administrators)
 - [限制谁可以推送到匹配的分支](#restrict-who-can-push-to-matching-branches)
 - [允许强制推送](#allow-force-pushes)
@@ -144,6 +147,11 @@ remote: error: Changes have been requested.
 {% data reusables.pull_requests.merge-queue-references %}
 
 {% endif %}
+
+### 要求部署在合并之前成功
+
+您可以要求先将更改成功部署到特定环境，然后才能合并分支。 例如，可以使用此规则确保在更改合并到默认分支之前，将更改成功部署到过渡环境。
+
 ### 包括管理员
 
 默认情况下，受保护分支规则不适用于对仓库具有管理员权限的人。 您可以启用此设置将管理员纳入受保护分支规则。
diff --git a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
index dbfd3fbb55..8ef5bf1a30 100644
--- a/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
+++ b/translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md
@@ -83,6 +83,9 @@ shortTitle: 分支保护规则
 
   {% endtip %}
 {%- endif %}
+{%- if required-deployments %}
+1. （可选）要选择在合并之前必须将更改成功部署到哪些环境，请选择 **Require deployments to succeed before merging（在合并之前需要部署成功）**，然后选择环境。 ![需要成功部署选项](/assets/images/help/repository/require-successful-deployment.png)
+{%- endif %}
 1. （可选）选择 **Apply the rules above to administrators（将上述规则应用于管理员）**。 ![将上述规则应用于管理员复选框](/assets/images/help/repository/include-admins-protected-branches.png)
 1. （可选）{% ifversion fpt or ghec %}如果仓库由组织拥有，可使用 {% data variables.product.prodname_team %} 或 {% data variables.product.prodname_ghe_cloud %}{% endif %} 启用分支限制。
    - 选择 **Restrict who can push to matching branches（限制谁可以推送到匹配分支）**。 ![分支限制复选框](/assets/images/help/repository/restrict-branch.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
index 88f6328f81..b4298f3c94 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes.md
@@ -29,7 +29,9 @@ topics:
 - 用户能从何处获取项目的帮助
 - 谁维护和参与项目
 
-如果将自述文件放在仓库的根目录 `docs` 或隐藏的目录 `.github` 中，{% data variables.product.product_name %} 将会识别您的自述文件并自动向仓库访问者显示。
+如果将自述文件放在仓库隐藏的 `.github` 目录、根目录或 `docs` 目录中，{% data variables.product.product_name %} 将会识别您的自述文件并自动向仓库访问者显示。
+
+如果仓库包含多个自述文件，则按以下顺序从位置中选择显示的文件：`.github` 目录，然后是仓库的根目录，最后是 `docs` 目录。
 
 ![Github/scientist 仓库的主页面及其自述文件](/assets/images/help/repository/repo-with-readme.png)
 
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
index 0c8baf89ef..d08034d7c6 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview.md
@@ -17,10 +17,14 @@ shortTitle: 社交媒体预览
 
 在添加图像之前，请展开仓库链接以显示关于仓库和所有者头像的基本信息。 为仓库添加图像有助于在各种社交平台上识别您的项目。
 
+## 添加图像以自定义存储库的社交媒体预览
+
 {% ifversion not ghae %}您可以将映像上传到私有仓库，但您的映像只能从公共仓库分享。{% endif %}
 
 {% tip %}
-提示：您的图像应为大小在 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在 640 x 320 像素。
+
+**提示**：图像应为大小在 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在 640 x 320 像素。
+
 {% endtip %}
 
 {% data reusables.repositories.navigate-to-repo %}
@@ -30,3 +34,16 @@ shortTitle: 社交媒体预览
     - 要删除图像，请单击 **Remove image（删除图像）**
 
     ![社交预览下拉菜单](/assets/images/help/repository/social-preview.png)
+
+## 关于透明度
+
+我们支持具有透明度的 PNG 图像。 许多通信平台都支持深色模式，因此使用透明的社交预览可能会有所帮助。 下面的透明图像在深色背景上是可以接受的；但情况可能并非总是如此。
+
+使用具有透明度的图像时，请记住它在不支持透明度的不同颜色背景或平台上的外观。
+
+{% tip %}
+
+**提示：** 如果不确定，建议使用背景纯色的图像。
+{% endtip %}
+
+![社交预览透明度](/assets/images/help/repository/social-preview-transparency.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
index 099ad3de0d..fa348ddb10 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/enabling-or-disabling-github-discussions-for-a-repository.md
@@ -19,6 +19,8 @@ shortTitle: Discussions
 {% data reusables.discussions.enabling-or-disabling-github-discussions-for-your-repository %}
 1. 要禁用讨论，请在“Features（功能）”下，取消选择 **Discussions（讨论）**。
 
+You can also use organization discussions to facilitate conversations that span multiple repositories in your organization. For more information, see "[Enabling or disabling GitHub Discussions for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
+
 ## 延伸阅读
 
 - "[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)"
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
index 0992deade4..991c062242 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md
@@ -31,7 +31,7 @@ You can manage a subset of security and analysis features for public repositorie
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**.{% ifversion fpt %}
   !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-public.png){% elsif ghec %}
   !["Enable" or "Disable" button for "Configure security and analysis" features in a public repository](/assets/images/help/repository/security-and-analysis-disable-or-enable-ghec-public.png){% endif %}
@@ -47,7 +47,7 @@ You can manage the security and analysis features for your {% ifversion fpt or g
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 {% ifversion fpt or ghes or ghec %}
 4. Under "Code security and analysis", to the right of the feature, click **Disable** or **Enable**. {% ifversion not fpt %}The control for "{% data variables.product.prodname_GH_advanced_security %}" is disabled if your enterprise has no available licenses for {% data variables.product.prodname_advanced_security %}.{% endif %}{% ifversion fpt %}
   !["Enable" or "Disable" button for "Configure security and analysis" features](/assets/images/help/repository/security-and-analysis-disable-or-enable-fpt-private.png){% elsif ghec %}
@@ -84,7 +84,7 @@ Organization owners and repository administrators can only grant access to view
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", in the search field, start typing the name of the person or team you'd like to find, then click a name in the list of matches.
    {% ifversion fpt or ghec or ghes > 3.2 %}
    ![Search field for granting people or teams access to security alerts](/assets/images/help/repository/security-and-analysis-security-alerts-person-or-team-search.png)
@@ -111,7 +111,7 @@ Organization owners and repository administrators can only grant access to view
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.repositories.navigate-to-security-and-analysis %}
+{% data reusables.repositories.navigate-to-code-security-and-analysis %}
 4. Under "Access to alerts", to the right of the person or team whose access you'd like to remove, click {% octicon "x" aria-label="X symbol" %}.
    {% ifversion fpt or ghec or ghes > 3.2 %}  
    !["x" button to remove someone's access to security alerts for your repository](/assets/images/help/repository/security-and-analysis-security-alerts-username-x.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
index ba51dcc371..98aae6e36b 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules.md
@@ -1,7 +1,7 @@
 ---
-title: Configuring tag protection rules
-shortTitle: Tag protection rules
-intro: You can configure tag protection rules for your repository to prevent contributors from creating or deleting tags.
+title: 配置标记保护规则
+shortTitle: 标记保护规则
+intro: 您可以为存储库配置标记保护规则，以防止参与者创建或删除标记。
 product: '{% data reusables.gated-features.tag-protection-rules %}'
 versions:
   fpt: '*'
@@ -12,17 +12,17 @@ versions:
 
 {% note %}
 
-**Note:** Tag protection rules are currently in beta and subject to change.
+**注意：**标记保护规则目前处于测试阶段，可能会有所变化。
 
 {% endnote %}
 
-When you add a tag protection rule, all tags that match the pattern provided will be protected. Only users with admin or maintain permissions in the repository will be able to create protected tags, and only users with admin permissions in the repository will be able to delete protected tags. 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role)”。 {% data variables.product.prodname_github_apps %} require the `Repository administration: write` permission to modify a protected tag.
+添加标记保护规则时，与提供的模式匹配的所有标记都将受到保护。 只有具有存储库中管理员或维护权限的用户才能创建受保护的标记，并且只有具有存储库管理员权限的用户才能删除受保护的标记。 更多信息请参阅“[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization#permissions-for-each-role)”。 {% data variables.product.prodname_github_apps %} 需要`存储库管理：写入`权限才能修改受保护的标记。
 
-Additionally, you can create custom repository roles to allow other groups of users to create or delete tags that match tag protection rules. 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。
+此外，您还可以创建自定义存储库角色，以允许其他用户组创建或删除与标记保护规则匹配的标记。 更多信息请参阅“[管理组织的自定义仓库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. In the "Code and automation" section of the sidebar, click **{% octicon "tag" aria-label="The tag icon" %} Tags**.
-1. Click **New rule**. ![New tag protection rule](/assets/images/help/repository/new-tag-protection-rule.png)
-1. Under "Tag name pattern", type the pattern of the tags you want to protect. In this example, typing "\*" protects all tags. ![Set tag protection pattern](/assets/images/help/repository/set-tag-protection-pattern.png)
-1. Click **Add rule**. ![Add tag protection rule](/assets/images/help/repository/add-tag-protection-rule.png)
+1. 在边栏的“Code and automation（代码和自动化）”部分中，单击 **{% octicon "tag" aria-label="The tag icon" %} 标记**。
+1. 单击 **New rule（新规则）**。 ![新标记保护规则](/assets/images/help/repository/new-tag-protection-rule.png)
+1. 在“Tag name pattern（标记名称模式）”下，键入要保护的标记的模式。 在此示例中，键入“\*”可保护所有标记。 ![设置标记保护模式](/assets/images/help/repository/set-tag-protection-pattern.png)
+1. 单击 **Add rule（添加规则）**。 ![添加标记保护规则](/assets/images/help/repository/add-tag-protection-rule.png)
diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
index 45375d89a5..9231882866 100644
--- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
+++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-git-lfs-objects-in-archives-of-your-repository.md
@@ -15,11 +15,11 @@ redirect_from:
 
 ## 关于存档中的 {% data variables.large_files.product_name_short %} 对象
 
-{% data variables.product.product_name %} 以 ZIP 文件和 tarball 的形式创建仓库的源代码存档。 用户可以在您仓库的主页上下载这些存档或者将其作为发行版资产。 默认情况下，{% data variables.large_files.product_name_short %} 对象不会包含在这些存档中，只有这些对象的指针文件包含在其中。 为了提高仓库存档的可用性，您可以选择包含 {% data variables.large_files.product_name_short %} 对象。
+{% data variables.product.product_name %} 以 ZIP 文件和 tarball 的形式创建仓库的源代码存档。 用户可以在您仓库的主页上下载这些存档或者将其作为发行版资产。 默认情况下，{% data variables.large_files.product_name_short %} 对象不会包含在这些存档中，只有这些对象的指针文件包含在其中。 为了提高仓库存档的可用性，您可以选择包含 {% data variables.large_files.product_name_short %} 对象。 要包含在内，{% data variables.large_files.product_name_short %} 对象必须被提交到存储库的 *.gitattributes* 文件中的跟踪规则所覆盖。
 
 如果您选择在仓库存档中包含 {% data variables.large_files.product_name_short %} 对象，则每次下载这些存档都会计入您帐户的带宽使用量。 每个帐户每月免费获得 {% data variables.large_files.initial_bandwidth_quota %} 的带宽，您可以付费获得额外用量。 更多信息请参阅“[关于存储和带宽使用](/github/managing-large-files/about-storage-and-bandwidth-usage)”和“[管理 {% data variables.large_files.product_name_long %} 的计费](/billing/managing-billing-for-git-large-file-storage)”。
 
-如果您使用外部 LFS 服务器（在 `.lfsconfig` 中配置），则这些 LFS 文件将不会包含在存储库的存档中。 存档将仅包含已提交到 {% data variables.product.product_name %} 的文件。
+如果您使用外部 LFS 服务器（在 *.lfsconfig* 中配置），则这些 LFS 文件将不会包含在存储库的存档中。 存档将仅包含已提交到 {% data variables.product.product_name %} 的文件。
 
 ## 管理存档中的 {% data variables.large_files.product_name_short %} 对象
 
diff --git a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
index a71203dcb6..967b2fcdd8 100644
--- a/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
+++ b/translations/zh-CN/content/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage.md
@@ -39,11 +39,15 @@ shortTitle: 配置 Git LFS
   ```
   要与 {% data variables.large_files.product_name_short %} 关联的每个文件类型都需要添加 `git {% data variables.large_files.command_name %} track`。 此命令将修改仓库的 *.gitattributes* 文件，并将大文件与 {% data variables.large_files.product_name_short %} 相关联。
 
-  {% tip %}
+  {% note %}
 
-  **提示：**我们强烈建议您将本地 *.gitattributes* 文件提交到仓库中。 依赖与 {% data variables.large_files.product_name_short %} 关联的全局 *.gitattributes* 文件，可能会导致在参与其他 Git 项目时发生冲突。
+  **注意：**我们强烈建议您将本地 *.gitattributes* 文件提交到仓库中。
 
-  {% endtip %}
+    - 依赖与 {% data variables.large_files.product_name_short %} 关联的全局 *.gitattributes* 文件，可能会导致在参与其他 Git 项目时发生冲突。
+    - 在存储库中包含 *.gitattributes* 文件允许创建复刻或新克隆的人员使用 {% data variables.large_files.product_name_short %} 更轻松地进行协作。
+    - 在存储库中包含 *.gitattributes* 文件允许 {% data variables.large_files.product_name_short %} 对象选择性地包含在 ZIP 文件和压缩包存档中。
+
+  {% endnote %}
 
 4. 将文件添加到与关联的扩展名相匹配的仓库：
   ```shell
diff --git a/translations/zh-CN/content/rest/overview/libraries.md b/translations/zh-CN/content/rest/overview/libraries.md
index e0048f8af6..21d1505d2d 100644
--- a/translations/zh-CN/content/rest/overview/libraries.md
+++ b/translations/zh-CN/content/rest/overview/libraries.md
@@ -18,12 +18,18 @@ topics:
   <h1>Octokit 风格多样</h1>
   <p class="lead">使用官方的 Octokit 库，或者使用任何适用的第三方库。</p>
   <div class="octokit-links"><br/>
-     <div class="octokit-language"> <span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
+     <div class="octokit-language"><span>Ruby → </span><a href="https://github.com/octokit/octokit.rb">octokit.rb</a></div><br/>
      <div class="octokit-language"><span>.NET → </span> <a href="https://github.com/octokit/octokit.net">octokit.net</a></div><br/>
      <div class="octokit-language"><span>JavaScript → </span> <a href="https://github.com/octokit/octokit.js">octokit/octokit.js</a></div><br/>
   </div>
 </div>
 
+{% warning %}
+
+警告：截至 2021 年 10 月下旬，官方 Octokit 库目前尚未维护。
+
+{% endwarning %}
+
 # 第三方库
 
 ### Clojure
diff --git a/translations/zh-CN/content/rest/reference/dependency-graph.md b/translations/zh-CN/content/rest/reference/dependency-graph.md
new file mode 100644
index 0000000000..0ec60a6128
--- /dev/null
+++ b/translations/zh-CN/content/rest/reference/dependency-graph.md
@@ -0,0 +1,16 @@
+---
+title: 依赖关系图
+intro: 'With the Dependency Graph API, you can view dependency changes and their security impact on your repository.'
+versions:
+  fpt: '*'
+  ghes: '>=3.6'
+  ghec: '*'
+  ghae: issue-6396
+topics:
+  - API
+miniTocMaxHeadingLevel: 3
+---
+
+<!--
+  Operations are automatically generated. Markdown for this page is located in data/reusables/rest-reference/dependency-graph
+-->
diff --git a/translations/zh-CN/content/rest/reference/index.md b/translations/zh-CN/content/rest/reference/index.md
index d1620d78bb..2f211b5499 100644
--- a/translations/zh-CN/content/rest/reference/index.md
+++ b/translations/zh-CN/content/rest/reference/index.md
@@ -22,6 +22,7 @@ children:
   - /collaborators
   - /commits
   - /dependabot
+  - /dependency-graph
   - /deploy_keys
   - /deployments
   - /emojis
diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-code.md b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
index b92800fd45..4e6fd7680c 100644
--- a/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
+++ b/translations/zh-CN/content/search-github/searching-on-github/searching-code.md
@@ -32,6 +32,7 @@ topics:
 - 只有_默认分支_被索引用于代码搜索。{% ifversion fpt or ghec %}
 - 只有小于 384 KB 的文件可搜索。{% else %}* 只有小于 5 MB 的文件可搜索。
 - 只有每个文件的前 500 KB 可搜索。{% endif %}
+- 最多可搜索 4,000 个私有{% ifversion ghec or ghes or ghae %} 和内部{% endif %} 存储库。 这 4,000 个存储库将是您有权访问的前 10,000 个私有{% ifversion ghec or ghes or ghae %} 和内部{% endif %} 存储库中的最新更新。
 - 只能搜索少于 500,000 个文件的仓库。{% ifversion fpt or ghec %}
 - 只能搜索去年有活动或已在搜索结果中返回的仓库。{% endif %}
 - 除了 [`filename`](#search-by-filename) 搜索以外，搜索源代码时必须始终包括至少一个搜索词。 例如，搜索 [`language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=language%3Ajavascript&type=Code&ref=searchresults) 无效，而搜索 [`amazing language:javascript`](https://github.com/search?utf8=%E2%9C%93&q=amazing+language%3Ajavascript&type=Code&ref=searchresults) 有效。
@@ -69,7 +70,6 @@ topics:
 | <code>path:<em>PATH/TO/DIRECTORY</em></code> | [**`console path:app/public language:javascript`**](https://github.com/search?q=console+path%3A%22app%2Fpublic%22+language%3Ajavascript&type=Code) 匹配 <em>app/public</em> 目录或其任何子目录（即使其位于 <em>app/public/js/form-validators</em> 中）中且含有单词“console”的 JavaScript 文件。 |
 
 ## 按语言搜索
-<!-- If you make changes to this feature, update /getting-started-with-github/github-language-support to reflect any changes. -->
 
 您可以基于所编写的语言搜索代码。 `language` 限定符可以是语言名称或别名。 有关支持的语言及其名称和别名的完整列表，请参阅 [github/linguist repository](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml)。
 
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
index e6db63f1b4..a3732dfdf4 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md
@@ -10,64 +10,64 @@ topics:
   - Legal
 ---
 
-**短版本：** _我们托管全球各地大量的协作项目，仅当用户能够善意一起工作时，该协作才能正常进行。 While using the Service, you must comply with our Acceptable Use Policies, which include some restrictions on content and conduct on GitHub related to user safety, intellectual property, privacy, authenticity, and other limitations. 简言之，要互惠互利。_
+**短版本：** _我们托管全球各地大量的协作项目，仅当用户能够善意一起工作时，该协作才能正常进行。 在使用服务时，您必须遵守我们的可接受使用政策，其中包括对 GitHub 上的内容和行为的一些限制，这些限制与用户安全、知识产权、隐私、真实性和其他限制有关。 简言之，要互惠互利。_
 
 有使用但在可接受使用政策中未定义的重要术语，其含义请参阅我们的[服务条款](/articles/github-terms-of-service)、[公司服务条款](/articles/github-corporate-terms-of-service)和[隐私声明](/articles/github-privacy-statement)。 对于受[公司服务条款](/articles/github-corporate-terms-of-service)约束的客户，“您”和“你的”是指“客户”或“用户”。 “我们”和“我们的”是指 "GitHub"。
 
 ## 1. 符合法律法规
 您负责遵照所有相关的法律、法规以及我们所有的可接受使用政策来使用服务。 这些政策可能不时更新，请参阅下面的内容以及我们的[服务条款](/articles/github-terms-of-service)和[公司服务条款](/articles/github-corporate-terms-of-service)。
 
-## 2. User Safety
-We do not allow content or activity on GitHub that:
+## 2. 用户安全
+我们不允许 GitHub 上的内容或活动：
 
 - 非法或宣传非法活动；
 
-- is [sexually obscene](/github/site-policy/github-sexually-obscene-content) or relates to sexual exploitation or abuse, including of minors;
+- [淫秽](/github/site-policy/github-sexually-obscene-content)或与性剥削或性虐待有关，包括对未成年人的性剥削或性虐待；
 
 - 诽谤、中伤或欺诈性内容；
 
 - 对任何个人或群体有[歧视性或辱骂性](/github/site-policy/github-hate-speech-and-discrimination)；
 
-- is [false, inaccurate, or intentionally deceptive information](/github/site-policy/github-misinformation-and-disinformation) and likely to adversely affect the public interest (including health, safety, election integrity, and civic participation);
+- 属于可能对公共利益（包括健康、安全、选举廉正和公民参与）产生不利影响的[虚假、不准确或有意欺骗性信息](/github/site-policy/github-misinformation-and-disinformation)；
 
-- [harasses or abuses](/github/site-policy/github-bullying-and-harassment) another individual or group, including our employees, officers, and agents, or other users;
+- [骚扰或辱骂](/github/site-policy/github-bullying-and-harassment)其他个人或团体，包括我们的员工、管理人员和代理人或其他用户；
 
-- [threatens or incites violence](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content) toward any individual or group, especially on the basis of who they are;
+- [威胁或煽动暴力](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content)对待任何个人或群体，特别是基于他们身份而行使暴力；
 
-- [gratuitously depicts or glorifies violence](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content), including violent images; or
+- [无端描述或美化暴力](/github/site-policy/github-threats-of-violence-and-gratuitously-violent-content)，包括暴力图像；或
 
-- is off-topic, or interacts with platform features in a way that significantly or repeatedly [disrupts the experience of other users](/github/site-policy/github-disrupting-the-experience-of-other-users).
+- 偏离主题，或以明显或反复[破坏其他用户体验](/github/site-policy/github-disrupting-the-experience-of-other-users)的方式与平台功能进行交互。
 
 
-## 3. Intellectual Property, Authenticity, and Private Information
-We do not allow content or activity on GitHub that:
+## 3. 知识产权、真实性和个人信息
+我们不允许 GitHub 上的内容或活动：
 
-- infringes any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity, or other right;
+- 侵犯任何方的任何专有权利，包括专利、商标、商业秘密、版权、肖像权或其他权利；
 
-- unlawfully shares unauthorized product licensing keys, software for generating unauthorized product licensing keys, or software for bypassing checks for product licensing keys, including extension of a free license beyond its trial period;
+- 非法共享未经授权的产品许可密钥、用于生成未经授权的产品许可密钥的软件，或用于绕过产品许可密钥检查的软件，包括将免费许可证延长至试用期之后；
 
-- [impersonates any person or entity](/github/site-policy/github-impersonation), including any of our employees or representatives, including through false association with GitHub, or by fraudulently misrepresenting your identity or site's purpose; or
+- [冒充任何个人或实体](/github/site-policy/github-impersonation)，包括我们的任何员工或代表，无论是通过虚构与 GitHub 的关系，还是欺诈性误传您的身份或网站目的；或者
 
-- [violates the privacy of any third party](/github/site-policy/github-doxxing-and-invasion-of-privacy), such as by posting another person's personal information without consent.
+- [侵犯任何第三方](/github/site-policy/github-doxxing-and-invasion-of-privacy)的隐私，例如未经同意发布他人的个人信息。
 
 ## 4. GitHub 上的垃圾信息和假活动
-We do not allow content or activity on GitHub that is:
-- automated excessive bulk activity and coordinated inauthentic activity, such as
-   * spamming
-   * cryptocurrency mining;
+我们不允许在 GitHub 上发布以下内容或活动：
+- 自动执行过多的批量活动和协调的不真实活动，例如
+   * 垃圾邮件
+   * 加密货币挖矿；
 * GitHub 条款和政策禁止的促销和广告大量群分;
-* inauthentic interactions, such as fake accounts and automated inauthentic activity;
-* rank abuse, such as automated starring or following;
-* creation of or participation in secondary markets for the purpose of the proliferation of inauthentic activity;
+* 不真实的互动，例如虚假帐户和自动化的不真实活动；
+* 排名滥用，例如自动标星或关注；
+* 为传播假活动而创建或参与二级市场；
 * 将 GitHub 用作在其他平台上传播滥用的平台;
-* phishing or attempted phishing; or
-* using our servers for any form of excessive automated bulk activity, to place undue burden on our servers through automated means, or to relay any form of unsolicited advertising or solicitation through our servers, such as get-rich-quick schemes.
+* 钓鱼或试图钓鱼；或
+* 使用我们的服务器进行任何形式的过度自动化批量活动，通过自动化方式给我们的服务器带来不必要的负担，或通过我们的服务器中继任何形式的未经请求的广告或招揽，例如快速致富计划。
 
-## 5. Site Access and Safety
-We do not allow content or activity on GitHub that:
+## 5. 网站访问和安全
+我们不允许 GitHub 上的内容或活动：
 
 - 直接支持[非法的主动攻击或恶意软件活动](/github/site-policy/github-active-malware-or-exploits) ，这些活动正在造成技术伤害 - 例如使用我们的平台来提供恶意执行或作为攻击基础架构。 例如，通过组织拒绝服务攻击或管理命令和控制服务器 - 在发生滥用行为之前没有隐含或明确的双重用途目的；或
-- uses our servers to disrupt or to attempt to disrupt, or to gain or to attempt to gain unauthorized access to, any service, device, data, account or network. Please note, activities permitted under bug bounty programs, such as the [GitHub Bug Bounty program](https://bounty.github.com), are not considered “unauthorized.”
+- 使用我们的服务器来破坏或试图破坏，或获取或试图未经授权访问任何服务、设备、数据、帐户或网络。 请注意，漏洞赏金计划允许的活动，例如 [GitHub 漏洞赏金计划](https://bounty.github.com)，不被视为“未经授权”。
 
 
 ## 6. 服务使用限制
@@ -98,17 +98,17 @@ We do not allow content or activity on GitHub that:
 
 我们理解，您可能想通过在帐户中发布支持者的姓名或徽标来推广您的内容，但在帐户中或通过帐户发布到服务的内容不应侧重于广告或促销。 这包括在页面、包、仓库和服务所有其他部分或者通过它们发布的内容。 您可在与您的帐户关联的自述文件中或项目说明部分包含静态图像、链接和宣传文本，但它们必须与您在 GitHub 上托管的项目相关。 您不能在其他用户的帐户中发布广告，例如在议题中发布货币化或过多的批量内容。
 
-You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/) or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion.
+您不得宣传或分发非法或我们[服务条款](/github/site-policy/github-terms-of-service/)或[可接受使用政策](/github/site-policy/github-acceptable-use-policies/)禁止的内容或活动，包括过度的自动批量活动（例如，垃圾邮件）、快速致富计划以及与您的促销相关的虚假陈述或欺骗。
 
 如果您决定在帐户中发布任何宣传材料，您将自行负责遵守所有适用的法律和法规，包括但不限于美国联邦贸易委员会的背书和推荐准则。 联邦贸易委员会的背书和推荐准则。 我们保留删除我们单方面认为违反了任何 GitHub 条款或政策的任何宣传材料或广告的权利。
 
 ## 11. 用户保护
 不得从事明显损害其他用户的活动。
 
-We will interpret our policies and resolve disputes in favor of protecting users as a whole.
+我们将从保护全体用户利益的角度解释我们的政策和解决争端。
 
 ---
 
-**Enforcement.** GitHub retains full discretion to [take action](/github/site-policy/github-community-guidelines#what-happens-if-someone-violates-githubs-policies) in response to a violation of these policies, including account suspension, account [termination](/github/site-policy/github-terms-of-service#3-github-may-terminate), or [removal](/github/site-policy/github-terms-of-service#2-github-may-remove-content) of content. Please also see our [Community Guidelines](/site-policy/github-terms/github-community-guidelines) for actions you can take if something or someone offends you.
+**执行。** GitHub 保留完全酌情权，可针对违反这些政策的行为[采取行动](/github/site-policy/github-community-guidelines#what-happens-if-someone-violates-githubs-policies)，包括帐户暂停、帐户[终止](/github/site-policy/github-terms-of-service#3-github-may-terminate)或[删除](/github/site-policy/github-terms-of-service#2-github-may-remove-content)内容。 另请参阅我们的[社区准则](/site-policy/github-terms/github-community-guidelines)，了解当有人冒犯您时您可以采取的措施。
 
-**Reinstatement and appeal.** If your content or account has been disabled or restricted and you seek reinstatement or wish to appeal, please see our [Appeal and Reinstatement page](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) for information about the process and use our [Appeal and Reinstatement form](https://support.github.com/contact/reinstatement) to submit a request.
+**恢复和上诉。** 如果您的内容或帐户已被停用或限制，并且您寻求恢复或希望申诉，请参阅我们的[申诉和恢复页面](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement)，了解有关流程的信息，并使用我们的[申诉和恢复表单](https://support.github.com/contact/reinstatement)提交请求。
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
index e631ac51b0..a561311d23 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-active-malware-or-exploits.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Active Malware or Exploits
-shortTitle: Active Malware or Exploits
+title: GitHub 活动的恶意软件或漏洞利用
+shortTitle: 活动的恶意软件或漏洞利用
 versions:
   fpt: '*'
 topics:
@@ -11,13 +11,13 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#active-malware-or-exploits
 ---
 
-Being part of a community includes not taking advantage of other members of the community. 我们不允许任何人利用我们的平台直接支持造成技术损害的非法攻击， 例如利用 GitHub 作为提供恶意可执行文件的方式或作为攻击基础架构， 例如，组织拒绝服务攻击或管理命令和控制服务器。 技术损害是指资源过度消耗、物理损坏、停机、拒绝服务或数据丢失，在滥用之前没有隐含或明确的双重用途。
+作为社区的一部分，包括不利用社区的其他成员。 我们不允许任何人利用我们的平台直接支持造成技术损害的非法攻击， 例如利用 GitHub 作为提供恶意可执行文件的方式或作为攻击基础架构， 例如，组织拒绝服务攻击或管理命令和控制服务器。 技术损害是指资源过度消耗、物理损坏、停机、拒绝服务或数据丢失，在滥用之前没有隐含或明确的双重用途。
 
   请注意，GitHub 允许双重用途内容，并支持发布用于研究漏洞、恶意软件或漏洞的内容，因为此类内容的发布和分发具有教育价值，并为安全社区提供净收益。 我们具有积极的意图，并利用这些项目来促进和推动整个生态系统的改善。
 
   在极少数非常普遍地滥用两用内容的情况下，我们可能会限制访问该特定内容实例，以破坏利用 GitHub 平台作为漏洞或恶意软件 CDN 的持续非法攻击或恶意软件活动。 在大多数情况下，限制采取将内容置于身份验证背后的形式，但作为最后手段，可能涉及禁用访问或在不可能的情况下完全删除（例如，当作为 Gist 发布时）。 我们还将尽可能联系项目所有者了解实施的限制。
 
-  在可行的情况下，限制是暂时的，无助于永久清除或限制该平台上的任何特定两用内容或该内容的副本。 While we aim to make these rare cases of restriction a collaborative process with project owners, if you do feel your content was unduly restricted, we have an [appeals process](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement) in place.
+  在可行的情况下，限制是暂时的，无助于永久清除或限制该平台上的任何特定两用内容或该内容的副本。 尽管我们的目标是使这些罕见的限制情况成为与项目所有者的合作过程，但如果您认为您的内容受到了不适当的限制，我们也有[申诉流程](/site-policy/acceptable-use-policies/github-appeal-and-reinstatement)。
 
   为了便于项目维护者自己找到解决滥用问题的途径，在上报给 GitHub 滥用报告之前，我们建议但不要求仓库所有者在张贴可能有害的安全研究内容时采取下列步骤：
 
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
index 7fbd5546b7..77f299dacb 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-disrupting-the-experience-of-other-users.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Disrupting the Experience of Other Users
-shortTitle: Disrupting the Experience of Other Users
+title: GitHub 破坏其他用户的体验
+shortTitle: 破坏其他用户的体验
 versions:
   fpt: '*'
 topics:
@@ -11,17 +11,17 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#disrupting-the-experience-of-other-users
 ---
 
-Being part of a community includes recognizing how your behavior affects others and engaging in meaningful and productive interactions with people and the platform they rely on.
+成为社区的一部分包括认识到您的行为如何影响他人，并与他人及其依赖的平台进行有意义和富有成效的互动。
 
-We do not allow behavior that significantly or continually disrupts the experience of other users. 这包括：
+我们不允许严重或持续破坏其他用户体验的行为。 这包括：
 
-- Posting off-topic comments
-- Opening empty or meaningless issues or pull requests
-- Starring and/or following accounts or repositories in large volume in a short period of time
-- Creating nonsensical or irrelevant code reviews
-- Engaging with platform features in a way that causes excessive notifications for other users
-- Using any other platform feature in a way that creates disruption
+- 发布偏离主题的评论
+- 开立空的或无意义的议题或拉取请求
+- 在短时间内大量标星和/或关注帐户或存储库
+- 创建荒谬或不相关的代码审查
+- 以导致其他用户收到过多通知的方式与平台功能互动
+- 以造成中断的方式使用任何其他平台功能
 
 虽然我们鼓励维护人员根据个别情况调整自己的项目，但 GitHub 员工可能会对从事此类行为的帐户采取进一步的限制措施。
 
-Please note that the above conduct may also violate other restrictions in our [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies). For example, depending on the nature and severity of the activity, it may rise to the level of [bullying and harassment](/github/site-policy/github-bullying-and-harassment).
+请注意，上述行为也可能违反我们[可接受使用政策](/github/site-policy/github-acceptable-use-policies)中的其他限制。 例如，根据活动的性质和严重程度，它可能会上升到[欺凌和骚扰](/github/site-policy/github-bullying-and-harassment)的水平。
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
index a63bc27021..48470def02 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-doxxing-and-invasion-of-privacy.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Doxxing and Invasion of Privacy
-shortTitle: Doxxing and Invasion of Privacy
+title: GitHub 人肉搜索和侵犯隐私
+shortTitle: 人肉搜索和侵犯隐私
 versions:
   fpt: '*'
 topics:
@@ -11,20 +11,20 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#doxxing-and-invasion-of-privacy
 ---
 
-Don't post other people's personal information. 这包括：
+不要发布他人的个人信息。 这包括：
 
-- Personal, private email addresses
-- Phone numbers
-- Physical addresses or other private location information
-- Bank account information or credit card numbers
-- Social Security/National Identity numbers
+- 个人、私人电子邮件地址
+- 电话号码
+- 实际地址或其他私人位置信息
+- 银行账户信息或信用卡号
+- 社会保障/国民身份证号码
 - 密码
-- Voter information
-- Medical information and personal biometric data
-- Other private information that may pose a safety or security risk
+- 选民信息
+- 医疗信息和个人生物识别数据
+- 其他可能构成安全或安保风险的私人信息
 
-We may consider other information, such as photos or videos that were taken or distributed without the subject's consent, to be an invasion of privacy, especially when such material presents a safety risk to the subject, such as in the case of intimidation or harassment.
+我们可能会认为发布他人信息（例如未经当事人同意而拍摄或散发的照片或视频）是侵犯隐私的行为，特别是当此类材料会给当事人带来安全风险时，例如在恐吓或骚扰的情况下。
 
-GitHub will take context into account as well as whether the reported content is publicly available elsewhere. Please note, however, that while sharing publicly available content may not be a violation of this policy, if the information is shared with the intent to harass or incite other abusive behavior, it may violate our prohibition against [bullying and harassment](/github/site-policy/github-bullying-and-harassment).
+GitHub 将考虑上下文以及报告的内容是否在其他地方公开可用。 但请注意，虽然共享公开可用内容可能不违反本政策，但如果共享信息的目的是骚扰或煽动其他滥用行为，则可能违反我们禁止[欺凌和骚扰](/github/site-policy/github-bullying-and-harassment)的政策。
 
-For more information, or to learn how to report a violation, see our [Private Information Removal Policy](/github/site-policy/github-private-information-removal-policy) and our instructions for [Reporting Abuse](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam).
+有关更多信息或要了解如何举报违规行为，请参阅我们的[个人信息删除政策](/github/site-policy/github-private-information-removal-policy)和我们的[举报滥用](/communities/maintaining-your-safety-on-github/reporting-abuse-or-spam)说明。
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
index 41f0476c70..cd692db221 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-hate-speech-and-discrimination.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Hate Speech and Discrimination
-shortTitle: Hate Speech and Discrimination
+title: GitHub 仇恨言论和歧视
+shortTitle: 仇恨言论和歧视
 versions:
   fpt: '*'
 topics:
@@ -11,14 +11,14 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#hate-speech-and-discrimination
 ---
 
-GitHub does not tolerate speech that attacks or promotes hate toward an individual or group of people on the basis of who they are, including age, body size, ability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, sexual identity, or sexual orientation. 这包括：
+GitHub 不容忍基于个人或群体的身份（包括年龄、体型、能力、民族、性别认同和表达、经验水平、国籍、个人外表、种族、宗教、性身份或性取向）攻击或宣扬对个人或群体的仇恨言论。 这包括：
 
-- Mocking, attacking, or excluding a person or group based on their beliefs or the characteristics listed above
-- Displaying clear affiliation or identification with known terrorist or violent extremist organizations
-- Supporting or promoting hate groups or hate-based conspiracy theories
-- Sharing symbols or images synonymous with hate
-- Using harmful stereotypes, slurs, or dehumanizing speech
-- Attacking an individual based on their perceived gender
-- Dog whistling; or using coded or suggestive language and/or symbols to promote abuse or hate
+- 基于个人或团体的信仰或上述特征，嘲笑、攻击或排斥他们
+- 显示与已知的恐怖主义或暴力极端主义组织的明确隶属关系或身份
+- 支持或宣扬仇恨团体或基于仇恨的阴谋论
+- 分享与仇恨同义的符号或图像
+- 使用有害的刻板印象、诽谤或非人性化言论
+- 根据感知的性别攻击个人
+- 吹狗哨；或使用编码或暗示性语言和/或符号来宣扬虐待或仇恨
 
-While GitHub takes all instances of abuse and harassment on the platform seriously, we are especially committed to fighting hate-based abuse where it disproportionately affects communities that have historically been targeted by such abuse. We aim to make GitHub a place where all individuals feel welcome and safe. 
+虽然 GitHub 会认真对待平台上的所有滥用和骚扰事件，但我们特别致力于打击基于仇恨的滥用行为，因为它会不当地影响社区，在历史上，社区一直是此类滥用行为的目标。 我们的目标是让 GitHub 成为一个让所有人都感到受欢迎和安全的地方。 
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-impersonation.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-impersonation.md
index 32cf270aef..f91ae644c8 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-impersonation.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-impersonation.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Impersonation
-shortTitle: Impersonation
+title: GitHub 冒充
+shortTitle: 冒充
 versions:
   fpt: '*'
 topics:
@@ -11,13 +11,13 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#impersonation
 ---
 
-You may not misrepresent your identity or your association with another person or organization. This includes doing any of the following in a way that misleads or deceives others:
+您不得误传您的身份或者您与他人或组织的关系。 这包括以误导或欺骗他人的方式执行以下任何操作：
 
-- Copying another user's avatar or other personal profile information
-- Posting content under another user's email address
-- Using a deceptively similar username, organization name, or other namespace
-- Otherwise posing as another individual or organization
+- 复制其他用户的头像或其他个人资料信息
+- 在其他用户的电子邮件地址下发布内容
+- 使用看似相似的用户名、组织名称或其他命名空间
+- 以其他方式冒充其他个人或组织
 
-Impersonation is a form of harassment and violation of this policy may lead to loss of access to your account.
+冒充是一种骚扰形式，违反此政策可能会导致无法访问您的帐户。
 
-Please note, having a username similar to another is not necessarily impersonation. GitHub will take context into account. For example, as in cases involving claims of [misinformation or disinformation](/github/site-policy/github-misinformation-and-disinformation), we generally allow parody and satire that is in line with our [Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies).
+请注意，用户名与其他用户名相似并不一定是冒充。 GitHub 将考虑上下文。 例如，在涉及[错误信息或虚假信息](/github/site-policy/github-misinformation-and-disinformation)的情况下，我们通常允许符合我们[可接受使用政策](/github/site-policy/github-acceptable-use-policies)的模仿和讽刺。
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
index 021f1269ab..78ccb87401 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-misinformation-and-disinformation.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Misinformation and Disinformation
-shortTitle: Misinformation and Disinformation
+title: GitHub 错误信息和虚假信息
+shortTitle: 错误信息和虚假信息
 versions:
   fpt: '*'
 topics:
@@ -11,11 +11,11 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#misinformation-and-disinformation
 ---
 
-You may not post content that presents a distorted view of reality, whether it is inaccurate or false (misinformation) or is intentionally deceptive (disinformation), where such content is likely to result in harm to the public or to interfere with fair and equal opportunities for all to take part in a free and open society. 可能包括：
-- Inaccurate or scientifically unsupported medical claims that endanger public health or safety
-- Manipulated media, whether audio or visual, likely to mislead or deceive in a way that may harm the public interest
-- False or misleading content likely to interfere with an individual's ability to participate in civic activities
-- Unsubstantiated claims that could promote hate or targeted harassment of specific groups of people
+您不得发布歪曲现实观点的内容，无论是不准确还是虚假（错误信息）还是故意欺骗（虚假信息），此类内容可能会对公众造成伤害或干扰所有人参与自由和开放社会的公平和平等机会。 可能包括：
+- 危害公众健康或安全的不准确或未经科学支持的医疗声明
+- 操纵的媒体，无论是音频还是视频，都可能以可能损害公众利益的方式误导或欺骗
+- 可能干扰个人参与公民活动能力的虚假或误导性内容
+- 未经证实的指控，可能助长对特定人群的仇恨或针对性骚扰
 
-鼓励积极参与表达想法、观点和经验，不得质疑个人帐户或言论。 We generally allow parody and satire that is in line with our [Acceptable Use Polices](/github/site-policy/github-acceptable-use-policies), and we consider context to be important in how information is received and understood. When reviewing content under this policy, GitHub will consider the impact of various factors that may help to orient the viewer, such as whether the content has been provided with clear disclaimers, citations to credible sources, or includes other details that clarify the accuracy of the information being shared.
+鼓励积极参与表达想法、观点和经验，不得质疑个人帐户或言论。 我们通常允许符合我们[可接受使用政策](/github/site-policy/github-acceptable-use-policies)的模仿和讽刺，我们认为上下文对于如何接收和理解信息很重要。 在根据本政策审查内容时，GitHub 将考虑可能有助于引导查看者的各种因素的影响，例如内容是否提供了明确的免责声明、对可靠来源的引用，或者是否包含其他细节，以阐明所共享信息的准确性。
 
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
index dd72b2b2b7..d028cc5300 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-sexually-obscene-content.md
@@ -1,6 +1,6 @@
 ---
 title: GitHub Sexually Obscene Content
-shortTitle: Sexually Obscene Content
+shortTitle: 淫秽色情内容
 versions:
   fpt: '*'
 topics:
@@ -11,10 +11,10 @@ redirect_from:
   - /github/site-policy/github-community-guidelines#sexually-obscene-content
 ---
 
-We do not tolerate content associated with sexual exploitation or abuse of another individual, including where minors are concerned. We do not allow sexually themed or suggestive content that serves little or no purpose other than to solicit an erotic or shocking response, particularly where that content is amplified by its placement in profiles or other social contexts. 这包括：
+我们不容忍与他人性剥削或性虐待相关的内容，包括涉及未成年人的内容。 我们不允许发布以性为主题或暗示的内容，这些内容只是为招揽色情或令人震惊的回应，几乎没有或根本没有其他目的，尤其是当该内容因其在个人资料或其他社交环境中的位置而被放大时。 这包括：
 
-- Pornographic content
-- Non-consensual intimate imagery
-- Graphic depictions of sexual acts including photographs, video, animation, drawings, computer-generated images, or text-based content
+- 色情内容
+- 未经同意的亲密影像
+- 性行为的图形描述，包括照片、视频、动画、图画、计算机生成的图像或文本内容
 
-We recognize that not all nudity or content related to sexuality is obscene. We may allow visual and/or textual depictions in artistic, educational, historical or journalistic contexts, or as it relates to victim advocacy. In some cases a disclaimer can help communicate the context of the project. However, please understand that we may choose to limit the content by giving users the option to opt in before viewing.
+我们认识到，并非所有裸露或与性行为相关的内容都是淫秽的。 我们可能允许在艺术、教育、历史或新闻环境中或与受害者权益倡导相关的视觉和/或文本描绘。 在某些情况下，免责声明可以帮助传达项目的上下文。 但请理解，我们可能会选择通过为用户提供在查看之前选择加入的选项来限制内容。
diff --git a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
index 1e8f414144..f183ddbd01 100644
--- a/translations/zh-CN/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
+++ b/translations/zh-CN/content/site-policy/acceptable-use-policies/github-threats-of-violence-and-gratuitously-violent-content.md
@@ -1,6 +1,6 @@
 ---
-title: GitHub Threats of Violence and Gratuitously Violent Content
-shortTitle: Threats of Violence and Gratuitously Violent Content
+title: GitHub 暴力威胁和无端暴力内容
+shortTitle: 暴力威胁和无端暴力内容
 versions:
   fpt: '*'
 topics:
@@ -13,10 +13,10 @@ redirect_from:
 ---
 
 
-You may not use GitHub to organize, promote, encourage, threaten, or incite acts of violence. You may not post content that depicts or glorifies violence or physical harm against human beings or animals. 这包括：
+您不得使用 GitHub 组织、宣传、鼓励、威胁或煽动暴力行为。 您不得发布描绘或美化针对人类或动物的暴力或身体伤害的内容。 这包括：
 
-- Threatening another individual or group with abuse, harm, sexual violence, or death
-- Posting text, imagery, or audio content glorifying or containing a graphic depiction of violence toward oneself, another individual, group, or animal
-- Encouraging another individual to engage in self harm
+- 以虐待、伤害、性暴力或死亡威胁他人个人或群体
+- 发布美化或包含对自己、他人、团体或动物的暴力行为的文字、图像或音频内容
+- 鼓励他人进行自我伤害
 
-We do not allow violent content to be posted indiscriminately or in a way that is difficult for other users to avoid, such as a profile avatar or an issue comment. However, we understand there may be legitimate reasons to post violent content, such as for educational or documentary purposes, creative works, or depictions of historical events. In those cases, a clear warning or disclaimer can help users make an educated decision as to whether or not they want to engage with such content. Still, GitHub may decide to limit the visibility of such content to those who choose to opt in. 
+我们不允许不分青红皂白地发布暴力内容，也不允许以其他用户难以避免的方式发布，例如个人资料头像或问题评论。 但是，我们理解发布暴力内容可能有正当理由，例如出于教育或纪实目的、创意作品或对历史事件的描绘。 在这些情况下，明确的警告或免责声明可以帮助用户就是否要与此类内容互动做出明智的决定。 尽管如此，GitHub 可能会决定将此类内容的可见性限制为选择加入的人。 
diff --git a/translations/zh-CN/content/site-policy/content-removal-policies/index.md b/translations/zh-CN/content/site-policy/content-removal-policies/index.md
index 74cd4f694d..2ec0372a58 100644
--- a/translations/zh-CN/content/site-policy/content-removal-policies/index.md
+++ b/translations/zh-CN/content/site-policy/content-removal-policies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Content Removal Policies
+title: 内容删除政策
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md b/translations/zh-CN/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
index 3091150c47..1e7b840fe6 100644
--- a/translations/zh-CN/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
+++ b/translations/zh-CN/content/site-policy/github-company-policies/github-statement-against-modern-slavery-and-child-labor.md
@@ -46,7 +46,7 @@ GitHub 的供应链包括用于我们产品和运营的商品和服务，包括
 
 **GitHub 的行为标准**禁止不安全和非法的行为，包括故意使用、参与、支持或容忍现代奴隶制（奴役、强迫或强制劳动、贩运、压榨以及监禁或以契约束缚劳动者）或童工。
 
-GitHub complies with laws prohibiting trafficking and child labor in the jurisdictions in which it operates, including [U.S. 关于打击人口贩运的联邦采购法规 22.17](https://www.govinfo.gov/content/pkg/CFR-2009-title48-vol1/pdf/CFR-2009-title48-vol1-part22-subpart22-17.pdf)。
+GitHub 遵守其运营所在辖区中禁止贩运劳工和使用童工的法律，包括[美国 关于打击人口贩运的联邦采购法规 22.17](https://www.govinfo.gov/content/pkg/CFR-2009-title48-vol1/pdf/CFR-2009-title48-vol1-part22-subpart22-17.pdf)。
 
 此外，GitHub 与 FairHotel 计划建立了合作伙伴关系，这意味着 GitHub 鼓励其员工选择 FairHotel 认可的酒店，因为这种酒店的工人工资合理、福利充足且在工作中有发言权。 成为 FairHotel 合作伙伴，也意味着 GitHub 作为公平雇主为酒店提供业务。
 
diff --git a/translations/zh-CN/content/site-policy/github-company-policies/index.md b/translations/zh-CN/content/site-policy/github-company-policies/index.md
index c1b0dd22ee..1bfeb90dac 100644
--- a/translations/zh-CN/content/site-policy/github-company-policies/index.md
+++ b/translations/zh-CN/content/site-policy/github-company-policies/index.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Company Policies
+title: GitHub 公司政策
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-community-forum-code-of-conduct.md b/translations/zh-CN/content/site-policy/github-terms/github-community-forum-code-of-conduct.md
index 06ba0fdfdb..5f980f44f1 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-community-forum-code-of-conduct.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-community-forum-code-of-conduct.md
@@ -13,13 +13,13 @@ topics:
 
 ## 概述和宗旨
 
-Millions of developers across the world host millions of projects—both open and closed source—on GitHub. We're fortunate to be able to play a part in enabling collaboration across the developer community every day, which is a responsibility we don’t take lightly. Together, we all have the exciting opportunity to make this a community we can be proud of.
+全球数以百万计的开发人员在 GitHub 上托管了数百万个项目，包括开源和闭源项目。 我们很幸运能够每天促进开发人员社区的协作，这是我们很重视的责任。 走在一起，我们都有机会让这个社区成为我们值得骄傲的地方。
 
 GitHub 社区论坛旨在成为推动协作、支持和集思广益的地方。 这是一个文明荟萃之地，在这里，您可以与其他用户联系、学习新技能、分享反馈和想法、寻找您的 GitHub 项目所需的所有支持。 参与本社区，即表示您同意遵守适用于 GitHub.com 的<[服务条款](/github/site-policy/github-terms-of-service/)和 [GitHub 可接受使用政策](/github/site-policy/github-acceptable-use-policies)以及本社区特定的行为准则。
 
 我们希望通过本行为准则，帮助您了解如何在 GitHub 社区论坛中完美协作、版主的职能以及哪些类型的行为或内容可能导致暂停或永久性终止社区参与。 我们将调查任何滥用举报，并且可能会删除社区内我们确定违反了 GitHub 服务条款或本行为准则的公共内容。
 
-Our diverse user base brings different perspectives, ideas, and experiences, and ranges from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub an environment that welcomes all the different voices and perspectives our community has to offer, while maintaining a safe place for developers to do their best work.
+我们多样化的用户群带来了不同的观点、想法和经验，从上周创建第一个“Hello World”项目的人到世界上最知名的软件开发人员。 我们致力于将 GitHub 营造成一个欢迎社区提供所有不同声音和观点的环境，同时为开发人员提供一个尽其所能工作的地方。
 
 ## 承诺
 
@@ -31,23 +31,23 @@ GitHub 社区论坛提倡互相尊重。 论坛是一种共享资源 — 通过
 
 以下规则并非硬性规定，仅用于帮助我们社区的人为判断。 我们使用这些准则为文明的公众讨论提供一个窗明几净的环境。
 
-### *Best Practices for Maintaining a Strong Community*
+### *维护强大社区的最佳实践*
 
-GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 At the same time, it's important that users remain respectful and allow space for others to contribute openly. In order to foster both a safe and productive environment, we encourage our community members to look to these guidelines to inform how they interact on our platform. Below, you’ll find some suggestions for how to have successful interactions as a valued member of the GitHub community.
+GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 同时，重要的是用户保持尊重，并为其他人留出公开贡献的空间。 为了营造一个安全和富有成效的环境，我们鼓励社区成员参考这些准则，以了解如何在我们的平台上进行互动。 下面，您将找到一些有关如何作为 GitHub 社区的重要成员进行成功互动的建议。
 
-- Engage with consideration and respect.
+- 以体贴和尊重的方式参与。
 
-     - **Be welcoming and open-minded** - New users join our community each day. Some are well-established developers, while others are just beginning. Be open to other ideas and experience levels. Make room for opinions other than your own and be welcoming to new collaborators and those just getting started.
+     - **热情和开放** - 每天都有新用户加入我们的社区。 有些是成熟的开发人员，而另一些则刚入门。 请对其他想法和经验水平持开放态度。 为您自己以外的意见留出空间，欢迎新的合作者和刚入门的合作者。
 
-     - **Be respectful** - Working in a collaborative environment means disagreements may happen. 但请记住，您的批评要对事不对人。 Share thoughtful, constructive criticism and be courteous to those you interact with. If you’re unable to engage respectfully, consider taking a step back or using some of our moderation tools to deescalate a tense situation.
+     - **尊重** - 在协作环境中工作意味着可能会发生分歧。 但请记住，您的批评要对事不对人。 分享深思熟虑的、建设性的批评，并对与您互动的人保持礼貌。 如果您无法恭敬地参与，请考虑退后一步或使用我们的一些审核工具来缓解紧张局势。
 
-     - **Be empathetic** - GitHub is a global community with people from a wide variety of backgrounds and perspectives, many of which may not be your own. Try to put yourself in others’ shoes and understand their feelings before you address them. Do your best to help make GitHub a community where others feel safe to make contributions, participate in discussions, and share different ideas.
+     - **富有同情心** - GitHub 是一个全球性社区，拥有来自不同背景和观点的人，其中很多可能与您不同。 试着设身处地为他人着想，在解决问题之前，先了解他们的感受。 尽最大努力帮助 GitHub 成为一个任何人都能安全地做出贡献、参与讨论和分享不同想法的社区。
 
 - 以积极和建设性的方式参与。
   - **改善讨论。**请始终努力以某种方式改善讨论（哪怕是极小的改善），帮助我们将论坛营造成讨论的绝佳场所。 如果您不确定自己的帖子会给对话带来什么影响，请斟酌您要表达的内容，三思而后行。
 
     论坛讨论的主题对我们非常重要，我们希望您也重视这些主题。 即使您不同意其中的某些内容，但请尊重主题和讨论主题的人。
-  - **Be clear and stay on topic.** The GitHub Community Forum is for collaboration, sharing ideas, and helping each other get stuff done. 脱离主题的评论对于完成工作和取得成效是一种干扰（有时可能受欢迎，但这种情况很少）。 紧扣主题有助于产生积极和富有成效的讨论。
+  - **明确并专注于主题。** GitHub 社区论坛用于协作、分享想法和帮助彼此完成工作。 脱离主题的评论对于完成工作和取得成效是一种干扰（有时可能受欢迎，但这种情况很少）。 紧扣主题有助于产生积极和富有成效的讨论。
 
     这也适用于分享链接。 在社区论坛中分享任何链接均应以提供相关和适当的信息为目的。 不能只是为某个站点吸引流量或关注而发布链接。 链接应始终附有对链接内容和目的的充分说明。 发布没有相关且有价值背景信息的链接，特别是未经请求提供这种链接，可能被当作发广告或带有更恶意的目的。
 
@@ -68,15 +68,15 @@ GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持
 
 ### *不允许*
 
-GitHub's [Acceptable Use Policies](/site-policy/acceptable-use-policies/github-acceptable-use-policies), which are part of GitHub's [Terms of Service](/github/site-policy/github-terms-of-service/), set a baseline for what is not allowed on GitHub. In addition, these terms restrictions apply to the GitHub Community Forum in the following way:
+GitHub的 [可接受使用政策](/site-policy/acceptable-use-policies/github-acceptable-use-policies)是GitHub [服务条款](/github/site-policy/github-terms-of-service/)的一部分，为 GitHub 上不允许的内容设定了基线。 此外，这些条款限制通过以下方式应用于 GitHub 社区论坛：
 
 - **13 岁以下的任何人。**13 岁以下的孩子不得在 GitHub 社区论坛（或 GitHub）上拥有帐户。 GitHub 不会有意收集 13 岁以下孩子的信息，也没有专门为他们定制任何内容。 如果我们得知或有理由怀疑您是 13 岁以下的用户，很遗憾，我们不得不关闭您的 GitHub 社区论坛和 GitHub.com 帐户。 我们并不想阻止您学习代码，但这是规则。 有关帐户终止的信息，请参阅我们的[服务条款](/github/site-policy/github-terms-of-service/)。
 
-- **Creating new account after account restriction.** GitHub's [Terms of Service](/github/site-policy/github-terms-of-service/) state that "One person or legal entity may maintain no more than one free Account." Additional free accounts created to inquire about flagged or suspended accounts in the GitHub Community Forum will be removed.
+- **在帐户限制后创建新帐户。** GitHub 的 [服务条款](/github/site-policy/github-terms-of-service/) 规定，“一个人或法人实体最多只能维护一个免费帐户”。 为查询 GitHub 社区论坛中被标记或暂停的帐户而创建的其他免费帐户将被删除。
 
 - **在专业环境中被合理认为不适当的其他行为。**GitHub 社区论坛是一个专业环境，应按专业环境来对待它。
 
-- **Violation of Terms of Service.** If your GitHub.com account is identified in violation of [Terms of Service](/github/site-policy/github-terms-of-service/) we will have to close your GitHub Community Forum account as well.
+- **违反服务条款。** 如果您的 GitHub.com 帐户被识别为违反[服务条款](/github/site-policy/github-terms-of-service/)，我们将不得不关闭您的 GitHub 社区论坛帐户。
 
 ## 执行
 
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md b/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md
index a11a5c394f..f19f1e6d74 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-community-guidelines.md
@@ -12,9 +12,9 @@ topics:
   - Legal
 ---
 
-Millions of developers across the world host millions of projects—both open and closed source—on GitHub. We're fortunate to be able to play a part in enabling collaboration across the developer community every day, which is a responsibility we don’t take lightly. Together, we all have the exciting opportunity to make this a community we can be proud of.
+全球数以百万计的开发人员在 GitHub 上托管了数百万个项目，包括开源和闭源项目。 我们很幸运能够每天促进开发人员社区的协作，这是我们很重视的责任。 走在一起，我们都有机会让这个社区成为我们值得骄傲的地方。
 
-Our diverse user base brings different perspectives, ideas, and experiences, and ranges from people who created their first "Hello World" project last week to the most well-known software developers in the world. We are committed to making GitHub an environment that welcomes all the different voices and perspectives our community has to offer, while maintaining a safe place for developers to do their best work.
+我们多样化的用户群带来了不同的观点、想法和经验，从上周创建第一个“Hello World”项目的人到世界上最知名的软件开发人员。 我们致力于将 GitHub 营造成一个欢迎社区提供所有不同声音和观点的环境，同时为开发人员提供一个尽其所能工作的地方。
 
 By outlining what we think a [safe, welcoming, and productive community](https://opensource.guide/building-community/) looks like at GitHub, we hope to help you understand how best to interact and collaborate on our platform in line with our [Terms of Service](/github/site-policy/github-terms-of-service) and [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies).
 
@@ -23,13 +23,13 @@ We encourage our community members to communicate expectations clearly, [moderat
 
 ## Maintaining a strong community
 
-GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 At the same time, it's important that users remain respectful and allow space for others to contribute openly. In order to foster both a safe and productive environment, we encourage our community members to look to these guidelines to inform how they interact on our platform.  Below, you’ll find some suggestions for how to have successful interactions as a valued member of the GitHub community.
+GitHub 社区的主要目的是协作处理软件项目。 我们致力于维持一个用户能够自由表达意见并对彼此想法（包括技术和其他方面）提出挑战的社区。 同时，重要的是用户保持尊重，并为其他人留出公开贡献的空间。 为了营造一个安全和富有成效的环境，我们鼓励社区成员参考这些准则，以了解如何在我们的平台上进行互动。  下面，您将找到一些有关如何作为 GitHub 社区的重要成员进行成功互动的建议。
 
-* **Be welcoming and open-minded** - New users join our community each day. Some are well-established developers, while others are just beginning. Be open to other ideas and experience levels. Make room for opinions other than your own and be welcoming to new collaborators and those just getting started.
+* **热情和开放** - 每天都有新用户加入我们的社区。 有些是成熟的开发人员，而另一些则刚入门。 请对其他想法和经验水平持开放态度。 为您自己以外的意见留出空间，欢迎新的合作者和刚入门的合作者。
 
-* **Be respectful** - Working in a collaborative environment means disagreements may happen. 但请记住，您的批评要对事不对人。 Share thoughtful, constructive criticism and be courteous to those you interact with. If you’re unable to engage respectfully, consider taking a step back or using some of our moderation tools to deescalate a tense situation.
+* **尊重** - 在协作环境中工作意味着可能会发生分歧。 但请记住，您的批评要对事不对人。 分享深思熟虑的、建设性的批评，并对与您互动的人保持礼貌。 如果您无法恭敬地参与，请考虑退后一步或使用我们的一些审核工具来缓解紧张局势。
 
-* **Be empathetic** - GitHub is a global community with people from a wide variety of backgrounds and perspectives, many of which may not be your own. Try to put yourself in others’ shoes and understand their feelings before you address them. Do your best to help make GitHub a community where others feel safe to make contributions, participate in discussions, and share different ideas.
+* **富有同情心** - GitHub 是一个全球性社区，拥有来自不同背景和观点的人，其中很多可能与您不同。 试着设身处地为他人着想，在解决问题之前，先了解他们的感受。 尽最大努力帮助 GitHub 成为一个任何人都能安全地做出贡献、参与讨论和分享不同想法的社区。
 
 
 ## 如果某事或某人冒犯您会怎么样？
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-corporate-terms-of-service.md b/translations/zh-CN/content/site-policy/github-terms/github-corporate-terms-of-service.md
index b20e908fca..05c73a1248 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-corporate-terms-of-service.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-corporate-terms-of-service.md
@@ -39,45 +39,45 @@ _这些条款适用于 1) 已接受《公司服务条款》的 GitHub.com（非
 
 **“内容”**包括但不限于通过服务刊登、显示或提供的任何代码、文本、数据、文章、软件包、照片、图片、软件、应用程序、设计、功能及其他材料。
 
-**"Corporate Account"** means an account created by a User on behalf of an entity.
+**“公司帐户”**是指用户代表实体创建的帐户。
 
 **“客户”**是指通过单击“我同意”或类似按钮，或者通过访问产品，与 GitHub 签订本协议的公司或组织。
 
-**"Customer Content"** means Content that Customer creates, owns, or to which Customer holds the rights.
+**“客户内容”**是指客户创建、拥有或持有权利的内容。
 
 **“文档”**是指与 GitHub 提供给客户的产品相关的任何手册、文档及其他支持材料。
 
 **“生效日期”**是以下日期中的较早日期 (i) 单击“我同意”以接受本协议的条款和条件，或 (ii) 第一次下单购买产品。
 
-**"External User"** means an individual, not including Customer’s Users, who visit or use the Service.
+**“外部用户”**是指访问或使用服务的个人，不包括客户的用户。
 
-**"Feedback"** means any ideas, know-how, algorithms, code contributions, suggestions, enhancement requests, recommendations or any other feedback on GitHub products or services.
+**“反馈”“**是指关于 GitHub 产品或服务的任何想法、知识、算法、代码贡献、建议、增强请求、建议或任何其他反馈。
 
 **“费用”**是指客户因以下原因而必须向 GitHub 支付的费用：(i) 在适用的订阅期内使用产品，或 (ii) 获得专业服务，此类费用反映在订单或 SOW 中。
 
-**“Fork”** means to copy the Content of one repository into another repository.
+**“复刻”**是指将一个仓库的内容复制到另一个仓库。
 
 **“GitHub”**是指 GitHub, Inc.、其附属公司和代表。
 
-**"GitHub Content"** means Content that GitHub creates, owns, or to which it holds the rights.
+**“GitHub 内容”**是指 GitHub 创建、拥有或持有权利的内容。
 
-**“Machine Account”** means an account registered by an individual human who accepts the applicable terms of service on behalf of the Machine Account, provides a valid email address, and is responsible for its actions. 机器帐户专用于执行自动化任务。 多个用户可指示机器帐户的操作，但帐户所有者对机器的操作最终负责。
+**“机器帐户”**是指代表机器帐户接受适用服务条款、提供有效的电子邮件地址并负责其操作的个人注册的帐户。 机器帐户专用于执行自动化任务。 多个用户可指示机器帐户的操作，但帐户所有者对机器的操作最终负责。
 
 **“订单”**是指双方用来订购产品的书面或电子文档（包括报价）。
 
-**“Organization”** means a shared workspace that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. 用户可以是多个组织的成员。
+**“组织”**是指与一个实体或者一个或多个用户相关的共享工作空间，其中多个用户可以一次协作处理多个项目。 用户可以是多个组织的成员。
 
-**“Private Repository”** means a repository which allows a User to control access to Content.
+**“私有仓库”**是指允许用户控制内容访问权限的仓库。
 
 “**专业服务**”是指 GitHub 根据共同执行的 SOW 向客户提供的培训、咨询或实现服务。 专业服务不包括支持。
 
-**"Professional Services Credits"** means the upfront payment method for purchasing Professional Services (exclusive of travel and lodging expenses) that Customer may use over a period of twelve (12) months (unless otherwise stated in an Order Form) for Professional Services. 在购买日期起十二 (12) 个月（或订单规定的时间）结束时未使用的任何专业服务积分将自动取消，且不能退款。
+**“专业服务积分”**是指购买专业服务时的预付方式（专用于旅行和住宿费用），客户可在十二 (12) 个月内（除非订单另有规定）用来购买专业服务。 在购买日期起十二 (12) 个月（或订单规定的时间）结束时未使用的任何专业服务积分将自动取消，且不能退款。
 
-**“Public Repository”** means a repository whose Content is visible to All Users.
+**“公共仓库”**是指其内容对所有用户可见的仓库。
 
 **“代表”**是指一方的员工、高管、代理、独立承包商、顾问以及法律和财务顾问。
 
-**“Scraping”** means extracting data from the Service via an automated process, such as a bot or webcrawler, and does not include the collection of information through GitHub's API.
+**“擦除”**是指通过自动化过程（如自动程序或网络爬虫 ）从服务中提取数据，不包括通过 GitHub 的 API 收集信息。
 
 **“服务”**是指 GitHub 的托管服务和任何适用的文档。
 
@@ -89,12 +89,12 @@ _这些条款适用于 1) 已接受《公司服务条款》的 GitHub.com（非
 
 **"用户"** 是指以下个人或机器帐户 (a) 访问或使用服务，(b) 访问或使用客户帐户任何部分，或 (c) 在每种情况下代表客户指示使用客户帐户履行职能。 用户数不应超过客户购买的订阅许可数。
 
-**“User-Generated Content”** means Content created or owned by a third party or External User.
+**“用户生成的内容”**是指第三方或外部用户创建或拥有的内容。
 
 ## B. 帐户条款
 
 ### 1. 帐户控制。
-  * _用户。_客户承认，用户对其个人帐户及其中的内容保留最终的管理控制权。 [GitHub's Standard Terms of Service](/articles/github-terms-of-service) govern Users' use of the Service, except with respect to Users' activities under this Section B.
+  * _用户。_客户承认，用户对其个人帐户及其中的内容保留最终的管理控制权。 [GitHub 的标准服务条款](/articles/github-terms-of-service)管辖用户对服务的使用，但本 B 部分下所述的用户活动除外。
 
   * _组织。_根据本 B 部分，客户对代表客户创建的任何组织以及发布到其组织内仓库的用户生成内容具有最终管理控制权。本 B 部分管制客户组织的使用。
 
@@ -105,7 +105,7 @@ _这些条款适用于 1) 已接受《公司服务条款》的 GitHub.com（非
 
 *   用户登录名不能多人共享。
 
-- 客户在以下情况下不得使用产品 (a) 违反美国或任何其他司法管辖区的出口管制或制裁法律；(b) 如果位于或普通居住于遭受美国 “外国资产管制办公室”(OFAC) 全面制裁的国家或地区；或 (c) 如果客户是[特别指定的国民 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) 或代表其工作，或者是遭受类似封锁或被拒绝方禁令的个人。 For more information, please see our [Export Controls policy](/articles/github-and-export-controls).
+- 客户在以下情况下不得使用产品 (a) 违反美国或任何其他司法管辖区的出口管制或制裁法律；(b) 如果位于或普通居住于遭受美国 “外国资产管制办公室”(OFAC) 全面制裁的国家或地区；或 (c) 如果客户是[特别指定的国民 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) 或代表其工作，或者是遭受类似封锁或被拒绝方禁令的个人。 更多信息请参阅我们的[出口管制政策](/articles/github-and-export-controls)。
 
 ### 3. 帐户安全
 客户负责：(i) 在其公司帐户下发布的所有内容和发生的活动；(ii) 保持其帐户登录凭据的安全；以及 (iii) 在获悉通过其帐户对服务的任何未授权使用或访问时[及时通知 GitHub](https://github.com/contact)。  GitHub 对客户不遵守本 B 部分所造成的任何损失或损害概不负责。
@@ -250,7 +250,7 @@ _专业服务保证。_除非 SOW 中另有规定，GitHub 向客户保证，本
 
 _服务免责声明。_GitHub **“按原样”**和**“视情况”**提供服务，不含任何形式的保证。 不限于此，关于服务，GitHub 明确否认所有保证，无论是明示、暗示还是法定保证，包括但不限于任何适销性、特定目的适用性、权利、安全性、准确性和非侵权。 GitHub 不保证服务将满足客户的要求；服务不中断、及时、安全或无错；通过服务提供的信息准确、可靠或正确；任何缺陷或错误将得到更正；服务在任何特定时间或地点可用；服务没有病毒或其他有害成分。 对于因客户下载和/或使用从服务获取的文件、信息、内容或其他材料而造成的任何损失风险，GitHub 概不负责。
 
-_测试版预览。_客户可自行决定选择使用测试版预览。 测试版预览不受支持，可能随时更改而不另行通知。 测试版预览的可靠性及可用性可能不如服务。 测试版预览不像服务一样采取同样的安全措施和审核。 GitHub 不承担测试版预览引起或与之相关的责任。 **Customer uses Beta Previews at its own risk.**
+_测试版预览。_客户可自行决定选择使用测试版预览。 测试版预览不受支持，可能随时更改而不另行通知。 测试版预览的可靠性及可用性可能不如服务。 测试版预览不像服务一样采取同样的安全措施和审核。 GitHub 不承担测试版预览引起或与之相关的责任。 **客户使用测试版预览自担风险。**
 
 ## N. 责任限制
 **_间接损害。_在适用法律允许的最大范围内，对于本协议造成或与之相关的任何间接、特殊、偶发性、惩罚性或后果性损害（包括利润收入或数据损失），或者获取替代产品的费用，任一方对另一方概不负责，无论损害是何原因造成，也不管该等责任是否源自基于合同、保证、民事侵权（包括疏忽）、严格责任或其他的任何索赔，以及一方是否被告知存在此类损害的可能。**
@@ -304,7 +304,7 @@ GitHub 每天二十四 (24) 小时、每周五 (5) 天（不包括周末和美
 如果本协议的任何条款被具有合法管辖权的法院视为非法、无效或不可执行，则双方将修改或改正本协议，使该条款尽可能有效。 无法以这种方式修改或改正的任何条款将被视为删除，而本协议的其余条款将继续保持完全效力。
 
 ### 6. 修正； 全面协议； 优先顺序
-本协议只能通过 GitHub 授权代表签署的书面修订加以修改，或 GitHub 根据第 T 部分发布修订版予以修改。本协议是双方之间完整的排他性协议。 本协议取代任何口头或书面的提议或事先协议，以及双方之间关于这些条款所述主题的任何其他通信，包括任何保密或非公开协议。 如果本协议条款与任何订单或 SOW 有任何冲突，则订单或 SOW 的条款只管制该订单或 SOW。
+本协议只能通过 GitHub 授权代表签署的书面修订加以修改，或 GitHub 根据第 R 部分发布修订版予以修改。本协议是双方之间完整的排他性协议。 本协议取代任何口头或书面的提议或事先协议，以及双方之间关于这些条款所述主题的任何其他通信，包括任何保密或非公开协议。 如果本协议条款与任何订单或 SOW 有任何冲突，则订单或 SOW 的条款只管制该订单或 SOW。
 
 ### 7. 公示性
 如果客户在其帐户上公开显示其公司或组织的名称，或在其个人资料页面上公开显示其商标或标志， 则客户允许 GitHub 在宣传材料中使用其公司或组织的名称将客户识别为 GitHub 的客户。 客户可在公开显示中隐藏其公司或组织名称并书面通知 GitHub 停止在宣传材料中使用其组织名称，以此撤销此许可。 但 GitHub 没有义务删除或收回之前对宣传材料的任何使用或分发。
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-marketplace-developer-agreement.md b/translations/zh-CN/content/site-policy/github-terms/github-marketplace-developer-agreement.md
index e5f131af56..06f582c26e 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-marketplace-developer-agreement.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-marketplace-developer-agreement.md
@@ -71,7 +71,7 @@ topics:
 - 7\. 允许未经授权下载流内容或媒体；
 - 8\. 显示或链接到非法内容；
 - 9\. 骚扰、辱骂、威胁或煽动暴力对待任何个人或团体，包括 GitHub 员工、高管和代理或任何最终用户；
-- 10\. Is or contains sexually obscene content;
+- 10\. 属于或包含淫秽内容；
 - 11\. 歧视或辱骂任何个人或团体；
 - 12\. 将最终用户转到模仿 Marketplace 或冒充 Marketplace 的任何其他网站，或者提供跳转到该等网站的链接。
 
@@ -89,13 +89,13 @@ topics:
 
 **3.7** 如果 GitHub 确定开发者违反了本节（第 3 节）中的任何要求或义务，则 GitHub 有权立即终止本协议。
 
-**3.8** Nothing in this Agreement shall prevent either party from developing and/or publishing applications that are similar or otherwise compete with the other party's applications.
+**3.8** 本协议的任何规定均不得阻止任何一方开发和/或发布与另一方的应用程序相似或竞争的应用程序。
 
 ## 4.   下架
 
 **4.1** 您自行下架。 在下一个日历月第一日之前三十 (30) 天向 GitHub 发出书面通知后，您可以从 Marketplace 未来分发中删除您的产品推介，但必须遵守本协议关于 Marketplace 已分发产品的规定，包括但不限于退款要求。 从 Marketplace 未来分发中删除产品推介，不会：(a) 影响先前已购买或安装该产品的最终用户的许可权；或 (b) 改变您对于用户先前已购买或安装的产品提供交付或支持服务的义务。
 
-Notwithstanding the foregoing, in no event will GitHub maintain on any portion of Marketplace any Listing that you have removed from Marketplace and provided written notice to GitHub that such removal was due to:
+尽管有上述规定，但在任何情况下，GitHub 都不会在 Marketplace 的任何部分保留由于以下原因（通过书面通知获悉）从 Marketplace 中删除的任何产品推介：:
 
 - (i) 被指控侵犯或确实侵犯任何人的任何版权、商标、商业秘密、商业外观、专利或其他知识产权；
 - (ii) 被指控诽谤或确实诽谤；
@@ -147,7 +147,7 @@ GitHub 可能：阻止该产品推介在 Marketplace 上展示；从 Marketplace
 
 **6.1** GitHub 是最终用户通过 Marketplace 购买开发者产品的记录商。
 
-**6.2** 开发者应用程序在 Marketplace 清单上的价格应设置为美元 (USD)。 开发者对于每个上架产品的定价设置有完全控制权，但一旦设定，就无法更改。 您可以撤销现有上架产品的定价计划，然后为其添加新的定价计划，前提是新的定价计划对现有最终客户没有不利影响。 您为开发者产品设置的价格将决定您将收到的付款金额。 GitHub will remit 95% of the sale price in USD without reduction for Taxes except for any withholding taxes that are required under applicable law. The remaining 5% of the sales price will be allotted to and retained by GitHub.  每个月底，在达到最低值 500 美元后，GitHub 将汇出您的应得款项。
+**6.2** 开发者应用程序在 Marketplace 清单上的价格应设置为美元 (USD)。 开发者对于每个上架产品的定价设置有完全控制权，但一旦设定，就无法更改。 您可以撤销现有上架产品的定价计划，然后为其添加新的定价计划，前提是新的定价计划对现有最终客户没有不利影响。 您为开发者产品设置的价格将决定您将收到的付款金额。 GitHub 将以美元汇出 95% 的销售价格，不扣除税款，但适用法律要求的任何预扣税款除外。 其余 5% 的销售价格将分配给 GitHub 并由 GitHub 保留。  每个月底，在达到最低值 500 美元后，GitHub 将汇出您的应得款项。
 
 **6.3** 退款要求。 您将负责制定关于向最终客户退款的条款和条件。 在任何情况下，GitHub 都不负责为退款提供任何支持，GitHub 也没有义务支付任何退款。
 
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-marketplace-terms-of-service.md b/translations/zh-CN/content/site-policy/github-terms/github-marketplace-terms-of-service.md
index 4f681d8fe3..2021c762d3 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-marketplace-terms-of-service.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-marketplace-terms-of-service.md
@@ -18,7 +18,7 @@ topics:
 
 ## A. GitHub.com 的服务条款
 
-Marketplace is provided by GitHub, and is governed by either the [Terms of Service](/articles/github-terms-of-service/) or the [Corporate Terms of Service](/articles/github-corporate-terms-of-service/) ("GitHub Terms"), depending on the type of account you're on, as well as these Marketplace Terms. 如果您将开发者产品配置为用于 GitHub.com 网站上的一个或多个帐户，则您对开发者产品的使用也将受适用 GitHub 条款的约束。 本文档中未定义的任何大写术语将在您适用的 GitHub 条款中定义。
+Marketplace 由 GitHub 提供，受[服务条款](/articles/github-terms-of-service/)或[公司服务条款](/articles/github-corporate-terms-of-service/)（“GitHub 条款”，具体取决于您使用的帐户类型）以及这些 Marketplace 条款的约束。 如果您将开发者产品配置为用于 GitHub.com 网站上的一个或多个帐户，则您对开发者产品的使用也将受适用 GitHub 条款的约束。 本文档中未定义的任何大写术语将在您适用的 GitHub 条款中定义。
 
 使用开发者产品时不得违反适用的 GitHub 条款。 许多此类开发者产品专门用于执行自动化任务。 此外，多个用户可以指示开发者产品的操作。 但是，如果您用自己的帐户购买和/或设置开发者产品，或者您是具有集成开发者产品的帐户之所有者，则您应对在您的帐户上或通过您的帐户执行的开发者产品操作负责。
 
@@ -44,7 +44,7 @@ Marketplace is provided by GitHub, and is governed by either the [Terms of Servi
 
 ## E. 您的数据和 GitHub 隐私政策
 
-**Privacy.** When you select or use a Developer Product, GitHub may share certain Personal Information (as defined in the [GitHub Privacy Statement](/articles/github-privacy-statement/)) with the Product Provider (if any such Personal Information is received from you) in order to provide you with the Developer Product, regardless of your privacy settings. GitHub 分享信息的多少取决于您所选开发者产品的要求，最少会分享您的用户帐户名称、ID 和主电子邮件地址，最多会分享您仓库内容的访问权限，包括阅读和修改您私有数据的权限。 通过 OAuth 授予权限时，您可以查看开发者产品要求的权限范围，然后选择接受或拒绝。
+**隐私**。当您选择或使用开发者产品时，GitHub 必须与产品提供者分享某些个人信息（定义见 [GitHub 隐私声明](/articles/github-privacy-statement/)）（如果收到您的任何此类个人信息），以便为您提供开发者产品，无论您的隐私设置如何。 GitHub 分享信息的多少取决于您所选开发者产品的要求，最少会分享您的用户帐户名称、ID 和主电子邮件地址，最多会分享您仓库内容的访问权限，包括阅读和修改您私有数据的权限。 通过 OAuth 授予权限时，您可以查看开发者产品要求的权限范围，然后选择接受或拒绝。
 
 如果您停止使用开发者产品并通过帐户设置撤消访问权限，则产品提供者将无法再访问您的帐户。 产品提供者负责在其规定的时间内从其系统中删除您的个人信息。 请联系产品提供者以确保您的帐户以被正确终止。
 
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md b/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
index 4f8878d95d..6206ea0a22 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-terms-for-additional-products-and-features.md
@@ -37,23 +37,23 @@ GitHub Actions 使您能够直接在您的 GitHub 仓库中创建自定义软件
 - 任何给我们的服务器带来负担的活动，如果这种负担与提供给用户的收益不成比例（例如，不要将 Action 用作内容交付网络或作为无服务器应用程序的一部分，但收益低负担也低的 Action 可能没问题）；或
 - 如果使用 GitHub 托管的运行器，与使用 GitHub Actions 的仓库相关的软件项目创建、测试、部署或发布无关的任何其他活动。
 
-为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 Misuse of GitHub Actions may result in termination of jobs, restrictions in your ability to use GitHub Actions, disabling of repositories created to run Actions in a way that violates these Terms, or in some cases, suspension or termination of your GitHub account.
+为防止违反这些限制和滥用 GitHub Actions，GitHub 可能会监视您对 GitHub Actions 的使用。 滥用 GitHub 操作可能会导致作业终止、限制您使用 GitHub 操作的能力、禁用为以违反这些条款的方式运行操作而创建的存储库，或者在某些情况下，暂停或终止您的 GitHub 帐户。
 
-*Use for Development and Testing*
+*用于开发和测试*
 
-You may only access and use GitHub Actions to develop and test your application(s). Only one licensed user may access a virtual machine provided by Actions at any time.
+您只能访问和使用 GitHub Actions 来开发和测试您的应用程序。 任何时候都只能有一个许可用户访问 Actions 提供的虚拟机。
 
-*Authorized Developer*
+*授权的开发者*
 
-You appoint GitHub as your authorized developer with respect to Apple software included in Actions. GitHub is responsible for complying with the terms for any such software included in Actions and will keep confidential any confidential information of Apple accessed as part of Actions.
+您指定 GitHub 作为您的授权开发者，负责 Actions 中包含的 Apple 软件。 GitHub 负责遵守 Actions 中包含的任何此类软件的条款，并对作为 Actions 一部分访问的任何 Apple 机密信息保密。
 
-*Third Party Repository Service Access*
+*第三方存储库服务访问*
 
-If you grant GitHub access to your third-party repository service account(s), you authorize GitHub to scan the account(s), including the contents of your Public and Private Repositories, for purposes of providing GitHub Actions.
+如果您授予 GitHub 访问您的第三方存储库服务帐户的权限，则表示您授权 GitHub 扫描这些帐户，包括您的公共和私有存储库的内容，以便提供 GitHub Actions。
 
-*Self-Hosted Runners on GitHub Actions*
+*GitHub Actions 上的自托管运行器*
 
-If you use self-hosted runners, you have the ability to turn off automatic updates but GitHub reserves the right to override your choice for critical security updates.
+如果您使用自托管运行器，则可以关闭自动更新，但 GitHub 保留覆盖您选择的关键安全更新的权利。
 
 ## Advanced Security
 GitHub 根据高级安全许可证向客户提供额外的安全功能。 这些功能包括代码扫描、秘密扫描和依赖项审查。 [Advanced Security 文档](/github/getting-started-with-github/about-github-advanced-security)提供更多详细信息。
@@ -128,6 +128,10 @@ GitHub Pages 的使用不得违反本协议、GitHub [可接受使用政策](/gi
 
 如果您对用途或预期用途是否归入这些类别有疑问，请联系 [GitHub 支持](https://support.github.com/contact?tags=docs-policy)。 GitHub 保留随时收回任何 GitHub 子域而不承担任何责任的权利。
 
+## 预览版
+
+预览版是指为预览、评估、演示或试用目的而提供的软件、在线服务和其他产品和功能，或这些功能的预发布版本，如 Alpha 版、测试版或抢先体验版。 如果协议不包含涉及预览版的条款和条件，则以下条款适用。 GitHub 授予使用预览版非生产实例的有限权限。 预览按“原样”、“包含所有故障”和“可用”提供。 GitHub 可能随时更改或终止预览版，恕不另行通知。 我们提供的有关个人预览版的任何信息都将被视为 GitHub 的机密信息。 如果您选择提供有关预览版的评论或建议，我们可能会出于任何目的使用该反馈，而无需承担任何义务。 GitHub 的最高赔偿责任仅限于直接损害赔偿，最高 5,000 美元。 对于因您使用预览版而由第三方提出的索赔，GitHub 没有义务为您辩护、赔偿或使您免受损害。
+
 ## 赞助计划
 
 GitHub Sponsors 允许开发者社区直接在 GitHub 上为他们设计、构建和维护所需开源项目的人员及组织提供经济支持。 要成为被赞助的开发者，必须同意 [GitHub 赞助计划附加条款](/github/site-policy/github-sponsors-additional-terms)。
diff --git a/translations/zh-CN/content/site-policy/github-terms/github-terms-of-service.md b/translations/zh-CN/content/site-policy/github-terms/github-terms-of-service.md
index 9c68ee6aa6..5d772729e3 100644
--- a/translations/zh-CN/content/site-policy/github-terms/github-terms-of-service.md
+++ b/translations/zh-CN/content/site-policy/github-terms/github-terms-of-service.md
@@ -73,7 +73,7 @@ topics:
 - 一个人或一个法律实体最多可以拥有一个免费帐户（如果您选择还控制一个机器帐户，没问题，但是它只能用于运行机器）。
 - 用户必须年满 13 岁。 虽然我们很高兴看到优秀的年轻编码者热衷于学习编程，但我们必须遵守美国法律。 GitHub 并未针对 13 岁以下的儿童定制服务，因此我们不允许任何 13 岁以下的用户使用我们的服务。 如果我们发现任何用户未满 13 岁，我们将[立即终止该用户的帐户](#l-cancellation-and-termination)。 如果您是美国以外的国家/地区的居民，您所在国家/地区规定的最低年龄可能会更大；在这种情况下，您有责任遵守您所在国家/地区的法律。
 - 您的登录名只能由一个人使用，即不允许多人共享一个登录名。 付费组织只能在订阅允许的范围内向多个用户帐户提供访问权限。
-- 不得违反美国或任何其他适用司法管辖区的出口管制或制裁法律使用 GitHub。 如果您是[特别指定国民 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx)或被美国政府机构实施的类似封锁或被拒方禁令所限制的个人，或者代表他们工作，则您不得使用 GitHub。 政府机构。  GitHub 可能会根据美国政府的授权，允许某些受制裁国家或地区的人访问某些 GitHub 服务。 政府授权。  For more information, please see our [Export Controls policy](/articles/github-and-export-controls).
+- 不得违反美国或任何其他适用司法管辖区的出口管制或制裁法律使用 GitHub。 如果您是[特别指定国民 (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx)或被美国政府机构实施的类似封锁或被拒方禁令所限制的个人，或者代表他们工作，则您不得使用 GitHub。 政府机构。  GitHub 可能会根据美国政府的授权，允许某些受制裁国家或地区的人访问某些 GitHub 服务。 政府授权。  更多信息请参阅我们的[出口管制政策](/articles/github-and-export-controls)。
 
 ### 4. 用户帐户安全
 在使用我们的服务时，您负责维护您的帐户安全。 我们提供双重身份验证等工具，帮助您维护帐户的安全性，但您的帐户内容及其安全性取决于您。
diff --git a/translations/zh-CN/content/site-policy/github-terms/index.md b/translations/zh-CN/content/site-policy/github-terms/index.md
index fc202c0f41..836f31adbd 100644
--- a/translations/zh-CN/content/site-policy/github-terms/index.md
+++ b/translations/zh-CN/content/site-policy/github-terms/index.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Terms
+title: GitHub 条款
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/site-policy/other-site-policies/index.md b/translations/zh-CN/content/site-policy/other-site-policies/index.md
index 4080978c23..890fd01174 100644
--- a/translations/zh-CN/content/site-policy/other-site-policies/index.md
+++ b/translations/zh-CN/content/site-policy/other-site-policies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Other Site Policies
+title: 其他网站政策
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-agreement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-agreement.md
index d9198f8d09..fd8041b419 100644
--- a/translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-agreement.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-agreement.md
@@ -1,5 +1,5 @@
 ---
-title: GitHub Data Protection Agreement
+title: GitHub 数据保护协议
 redirect_from:
   - /github/site-policy/github-data-protection-addendum
   - /github/site-policy-deprecated/github-data-protection-addendum
@@ -11,27 +11,27 @@ versions:
 
 ## 简介
 
-The parties agree that this GitHub Data Protection Agreement (“**DPA**”) sets forth their obligations with respect to the processing and security of Personal Data and, where explicitly stated in the DPA Terms, Customer Data in connection with the Online Services provided by GitHub, Inc. (“**GitHub**”). The DPA (including its Appendix and Attachments) is between GitHub and any customer receiving Online Services from GitHub based on the GitHub Customer Agreement (“**Customer**”), and is incorporated by reference into the GitHub Customer Agreement.
+双方同意，本《GitHub 数据保护协议》（“**DPA**”）规定了他们在个人数据的处理和安全方面的义务，并在 DPA 条款中明确规定的情况下，规定了与 GitHub, Inc.（“**GitHub**”）提供的在线服务相关的客户数据。 DPA（包括其附录和附件）是 GitHub 与根据 GitHub 客户协议从 GitHub 获取在线服务的任何客户（“**客户**”）之间的协议，并引用合并到 GitHub 客户协议。
 
-In the event of any conflict or inconsistency between the DPA Terms and any other terms in the GitHub Customer Agreement, the DPA Terms will prevail. The provisions of the DPA Terms supersede any conflicting provisions of the GitHub Privacy Statement that otherwise may apply to processing of Personal Data. For clarity, the Standard Contractual Clauses prevail over any other term of the DPA Terms.
+如果 DPA 条款与 GitHub 客户协议中的任何其他条款之间存在任何冲突或不一致，则以 DPA 条款为准。 DPA 条款的规定取代 GitHub 隐私声明中可能适用于个人数据处理的任何相互冲突的规定。 为清楚起见，标准合同条款优先于 DPA 条款的任何其他条款。
 
-### Applicable DPA Terms and Updates
+### 适用的 DPA 条款和更新
 
-#### Limits on Updates
+#### 更新限制
 
-When Customer renews or purchases a new subscription to an Online Service, the then-current DPA Terms will apply and will not change during the term of that new subscription for that Online Service.
+当客户续订或购买在线服务的新订阅时，届时现行的 DPA 条款将适用，并且在该在线服务的新订阅期限内不会更改。
 
-#### New Features, Supplements, or Related Software
+#### 新功能、补充或相关软件
 
-Notwithstanding the foregoing limits on updates, when GitHub introduces features, supplements or related software that are new (i.e., that were not previously included with the subscription), GitHub may provide terms or make updates to the DPA that apply to Customer’s use of those new features, supplements or related software. If those terms include any material adverse changes to the DPA Terms, GitHub will provide Customer a choice to use the new features, supplements, or related software, without loss of existing functionality of a generally available Online Service. If Customer does not use the new features, supplements, or related software, the corresponding new terms will not apply.
+尽管有上述更新限制，但当 GitHub 引入新功能、补充或相关软件（即以前未包含在订阅中的功能、补充或相关软件）时，GitHub 可能会向 DPA 提供适用于客户使用这些新功能、补充或相关软件的条款或更新。 如果这些条款包含对 DPA 条款的任何重大不利更改，GitHub 将为客户提供使用新功能、补充或相关软件的选择，而不会丢失正式发布的在线服务的现有功能。 如果客户不使用新功能、补充或相关软件，则相应的新条款将不适用。
 
-#### Government Regulation and Requirements
+#### 政府法规和要求
 
-Notwithstanding the foregoing limits on updates, GitHub may modify or terminate an Online Service in any country or jurisdiction where there is any current or future government requirement or obligation that (1) subjects GitHub to any regulation or requirement not generally applicable to businesses operating there, (2) presents a hardship for GitHub to continue operating the Online Service without modification, and/or (3) causes GitHub to believe the DPA Terms or the Online Service may conflict with any such requirement or obligation.
+尽管有上述更新限制，如果当前或将来有以下任何政府要求或义务，GitHub 可以在任何国家或司法管辖区修改或终止在线服务：(1) 使 GitHub 受到任何一般不适用于在该地运营的企业的法规或要求的约束，(2) GitHub 难以继续运营在线服务而不进行修改，和/或 (3) 导致 GitHub 认为 DPA 条款或在线服务可能与任何此类要求或义务相冲突。
 
-### Electronic Notices
+### 电子通知
 
-GitHub may provide Customer with information and notices about Online Services electronically, including via email, or through a web site that GitHub identifies. Notice is given as of the date it is made available by GitHub.
+GitHub 可能会以电子方式（包括通过电子邮件或 GitHub 识别的网站）向客户提供有关在线服务的信息和通知。 通知自 GitHub 提供之日起发出。
 
 ### Prior Versions
 
diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
index 2654e37a24..6924fa91a9 100644
--- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md
@@ -245,7 +245,7 @@ GitHub 仅使用绝对必要的 Cookie。 Cookie 是网站通常存储在访客
 
 使用我们的服务，即表示您同意我们将这些类型的 cookie 放在您的计算机或设备上。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用我们的服务。
 
-We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies.
+我们在 [GitHub 子处理器和 Cookie](/github/site-policy/github-subprocessors-and-cookies) 页面上提供有关 [GitHub 上 Cookie](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) 的更多信息，其中描述了我们设置的 Cookie、我们对这些 Cookie 的需求以及此类 Cookie 的过期时间。
 
 ### DNT
 
@@ -322,7 +322,7 @@ GitHub 处理美国境内外的个人信息，并依靠标准合同条款作为
 
 ## 隐私声明的变更
 
-GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 For other changes to this Privacy Statement, we encourage Users to [watch](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) or to check our Site Policy repository frequently.
+GitHub 可能会不时更改我们的隐私声明，不过大多数情况都是小变动。 如果本隐私声明发生重大变更，我们会在变更生效之前至少 30 天通知用户 - 在我们网站的主页上发布通知，或者发送电子邮件到您的 GitHub 帐户中指定的主电子邮件地址。 我们还会更新我们的[站点政策仓库](https://github.com/github/site-policy/)，通过它可跟踪本政策的所有变更。 对于本隐私声明的其他更改，我们建议用户[关注](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)或经常查看我们的网站政策仓库。
 
 ## 许可
 
diff --git a/translations/zh-CN/content/site-policy/privacy-policies/index.md b/translations/zh-CN/content/site-policy/privacy-policies/index.md
index 632e7ba279..35080276e5 100644
--- a/translations/zh-CN/content/site-policy/privacy-policies/index.md
+++ b/translations/zh-CN/content/site-policy/privacy-policies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Privacy Policies
+title: 隐私政策
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md b/translations/zh-CN/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
index 4216d45fc7..d1a2dea84b 100644
--- a/translations/zh-CN/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
+++ b/translations/zh-CN/content/site-policy/security-policies/coordinated-disclosure-of-security-vulnerabilities.md
@@ -1,5 +1,5 @@
 ---
-title: Coordinated Disclosure of Security Vulnerabilities
+title: 协调披露安全漏洞
 redirect_from:
   - /responsible-disclosure
   - /coordinated-disclosure
@@ -13,10 +13,10 @@ topics:
   - Legal
 ---
 
-我们希望每个人都能安全地使用 GitHub。 If you've discovered a security vulnerability in GitHub, we appreciate your help in disclosing it to us in a coordinated manner.
+我们希望每个人都能安全地使用 GitHub。 如果您发现了 GitHub 中的安全漏洞，请以协调的方式向我们披露，我们非常感谢您的帮助。
 
 ## 赏金计划
 
-为更好地吸引安全研究人员参与，GitHub 也像其他一些大型软件公司一样提供漏洞赏金。 The idea is simple: hackers and security researchers (like you) find and report vulnerabilities through our coordinated disclosure process. 然后，为了认可这些研究人员在寻找漏洞时付出的巨大努力，我们用一些真金白银奖励他们。
+为更好地吸引安全研究人员参与，GitHub 也像其他一些大型软件公司一样提供漏洞赏金。 这个想法很简单：黑客和安全研究人员（像您一样）发现漏洞并通过我们的协调披露流程报告漏洞。 然后，为了认可这些研究人员在寻找漏洞时付出的巨大努力，我们用一些真金白银奖励他们。
 
 请查看 [GitHub 漏洞赏金](https://bounty.github.com)站点了解赏金详情，并阅读我们全面的[法律安全港政策](/articles/github-bug-bounty-program-legal-safe-harbor)条款，我们期待您大展身手！
diff --git a/translations/zh-CN/content/site-policy/security-policies/index.md b/translations/zh-CN/content/site-policy/security-policies/index.md
index 35aab7da83..3483c7443b 100644
--- a/translations/zh-CN/content/site-policy/security-policies/index.md
+++ b/translations/zh-CN/content/site-policy/security-policies/index.md
@@ -1,5 +1,5 @@
 ---
-title: Security Policies
+title: 安全政策
 versions:
   fpt: '*'
 topics:
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
index 656b608bd1..93282ec21b 100644
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
+++ b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/index.md
@@ -22,6 +22,5 @@ children:
   - /tax-information-for-github-sponsors
   - /disabling-your-github-sponsors-account
   - /unpublishing-your-github-sponsors-profile
-  - /sponsors-for-companies
 ---
 
diff --git a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md b/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md
deleted file mode 100644
index dcd2996708..0000000000
--- a/translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: 从公司赞助商接收付款
-shortTitle: 公司赞助商
-intro: 要接受来自公司赞助商服务的付款，您必须接受一些附加条款。
-allowTitleToDifferFromFilename: true
-versions:
-  fpt: '*'
-  ghec: '*'
-type: how_to
-topics:
-  - Sponsors
-  - Open Source
----
-
-{% data reusables.sponsors.beta-note-sponsors-for-companies %}
-
-## 关于公司赞助商服务
-
-创建赞助者个人资料后，您有资格获得通过信用卡计费的个人用户和组织的赞助付款。 此外，{% data variables.product.company_short %} 现在为通过发票付款的企业客户提供公司赞助商服务，包括使用 {% data variables.product.prodname_ghe_server %} 或 {% data variables.product.prodname_ghe_managed %} 的公司。
-
- 您在公司赞助商服务下获得的资金直接来自 {% data variables.product.company_short %}，并且您参与此服务受单独条款的约束：“GitHub 维护者可选数据规定附加条款”。 如果您希望从 {% data variables.product.company_short %} 公司赞助商服务下获得资金，则需要在收到任何这些资金之前完成协议。
-
-## 关于附加条款
-
-“GitHub 维护者可选数据规定附加条款”协议可从您的 [{% data variables.product.prodname_sponsors %} 仪表板](https://github.com/sponsors/accounts)获得（请参阅以下步骤）。 该协议的要点包括：
-
-* 由于服务的设置方式，您将从 {% data variables.product.company_short %} 收到付款，而不是从其他公司收到付款。
-* 如果通过此计划付款时需要预扣税款，{% data variables.product.company_short %} 将从欠款中扣除税款并将其支付给相应的税务机关。
-* 我们将在 {% data variables.product.company_short %} 仪表板上与为访问这些数据付费的公司共享有关您的项目或您参与的项目的一些汇总数据。 协议第 5 节中概述了这些数据领域。
-* 数据将被汇总，不包括任何用户个人信息（如 {% data variables.product.company_short %} [隐私声明](/free-pro-team@latest/github/site-policy/github-privacy-statement)中所定义）或来自私人仓库的任何信息。
-* 作为维护者，您可以通过提前 14 天联系我们终止协议。
-
-如果您同意“GitHub 维护者可选数据规定附加条款”协议中概述的条款，则每次公司购买服务访问权限时，您都将收到来自 {% data variables.product.company_short %} 的付款。 公司从 {% data variables.product.company_short %} 购买对仪表板的限时（例如，一个月或一年）访问权限，{% data variables.product.company_short %} 购买数据的许可证以填充仪表板。 您的财务关系是与 {% data variables.product.company_short %}，而不是参与服务的公司。
-
-## 接受附加条款
-
-您可以从 [{% data variables.product.prodname_sponsors %} 仪表板](https://github.com/sponsors/accounts)查看和接受“GitHub 维护者可选数据规定附加条款”协议。 有关加入公司赞助商服务的信息，请参阅“[按发票为 GitHub Sponsors 付款](/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice)”。
-
-{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
-3. 在“Overview（概述）”选项卡的“Optional steps（可选步骤）”下，单击 **GitHub Maintainer Additional Terms for Optional Data Provision（GitHub 维护者可选数据规定附加条款）**以显示协议。
-4. 阅读协议后，单击 **Accept（接受）**接受条款并加入公司赞助商服务。 或者，单击对话框右上角的 {% octicon "x" aria-label="The x octicon" %} 以关闭协议而不接受。
diff --git a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
index b928416fd7..b0bd844640 100644
--- a/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
+++ b/translations/zh-CN/content/sponsors/sponsoring-open-source-contributors/paying-for-github-sponsors-by-invoice.md
@@ -19,4 +19,3 @@ redirect_from:
 
 您可以联系您的销售代表或[联系我们](https://support.github.com/contact/org-sponsors-waitlist)加入此测试计划。
 
-有关从公司担保人服务接收付款的信息，请参阅“[从公司赞助商接收付款](/sponsors/receiving-sponsorships-through-github-sponsors/sponsors-for-companies)”。
diff --git a/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md b/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md
index 99ab9196b5..64f92527a9 100644
--- a/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md
+++ b/translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md
@@ -89,7 +89,7 @@ $ ssh -p122 admin@<em>hostname</em> -- 'ghe-diagnostics' > diagnostics.txt
 - `collectd/logs/collectd.log`：Collectd 日志
 - `mail-logs/mail.log`：SMTP 电子邮件交付日志
 
-更多信息请参阅“[审核日志](/enterprise/{{ currentVersion }}/admin/guides/installation/audit-logging)”。
+更多信息请参阅“[关于企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”。
 
 支持包包含过去两天的日志。 要获取过去七天的日志，您可以下载扩展支持包。 更多信息请参阅“[创建和共享扩展支持包](#creating-and-sharing-extended-support-bundles)”。
 
diff --git a/translations/zh-CN/data/features/job-hooks-for-runners.yml b/translations/zh-CN/data/features/job-hooks-for-runners.yml
index cb0891fe9b..e3d995d4e1 100644
--- a/translations/zh-CN/data/features/job-hooks-for-runners.yml
+++ b/translations/zh-CN/data/features/job-hooks-for-runners.yml
@@ -4,3 +4,5 @@
 versions:
   fpt: '*'
   ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6530'
diff --git a/translations/zh-CN/data/features/prevent-org-admin-add-outside-collaborator.yml b/translations/zh-CN/data/features/prevent-org-admin-add-outside-collaborator.yml
new file mode 100644
index 0000000000..8defc7dac4
--- /dev/null
+++ b/translations/zh-CN/data/features/prevent-org-admin-add-outside-collaborator.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  ghec: '*'
+  ghes: '>=3.6'
+  ghae: 'issue-6336'
diff --git a/translations/zh-CN/data/features/required-deployments.yml b/translations/zh-CN/data/features/required-deployments.yml
new file mode 100644
index 0000000000..3b68c82970
--- /dev/null
+++ b/translations/zh-CN/data/features/required-deployments.yml
@@ -0,0 +1,8 @@
+---
+#Issue 6384
+#Required deployments branch protection rule
+versions:
+  fpt: '*'
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-6384'
diff --git a/translations/zh-CN/data/features/secret-scanning-org-dry-runs.yml b/translations/zh-CN/data/features/secret-scanning-org-dry-runs.yml
new file mode 100644
index 0000000000..356b5b780e
--- /dev/null
+++ b/translations/zh-CN/data/features/secret-scanning-org-dry-runs.yml
@@ -0,0 +1,7 @@
+---
+#Issue #6367
+#Documentation for the "org level dry runs (Public Beta)" for custom patterns under secret scanning
+versions:
+  ghec: '*'
+  ghes: '>3.4'
+  ghae: 'issue-6367'
diff --git a/translations/zh-CN/data/features/secret-scanning-push-protection.yml b/translations/zh-CN/data/features/secret-scanning-push-protection.yml
new file mode 100644
index 0000000000..2d06565565
--- /dev/null
+++ b/translations/zh-CN/data/features/secret-scanning-push-protection.yml
@@ -0,0 +1,7 @@
+---
+#Reference: #5620.
+#Documentation for secret scanning as a push protection
+versions:
+  ghes: '>=3.5'
+  ghae: 'issue-5620'
+  ghec: '*'
diff --git a/translations/zh-CN/data/learning-tracks/code-security.yml b/translations/zh-CN/data/learning-tracks/code-security.yml
index f8abf8dc63..a30b570995 100644
--- a/translations/zh-CN/data/learning-tracks/code-security.yml
+++ b/translations/zh-CN/data/learning-tracks/code-security.yml
@@ -105,7 +105,7 @@ code_security_ci:
     - /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system
 #Feature available in all versions
 end_to_end_supply_chain:
-  title: 'End-to-end supply chain'
+  title: '端到端供应链'
   description: 'How to think about securing your user accounts, your code, and your build process.'
   guides:
     - /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml
new file mode 100644
index 0000000000..e1c803680b
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml
@@ -0,0 +1,42 @@
+---
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
+    - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
+    - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
+    - 包已更新到最新的安全版本。
+  bugs:
+    - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
+    - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
+    - A subset of internal configuration files are more reliably updated after a hotpatch.
+    - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
+    - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
+    - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
+    - In some cluster topologies, webhook delivery information was not available.
+    - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.
+    - Elasticsearch health checks would not allow a yellow cluster status when running migrations.
+    - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
+    - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.
+    - Links to inaccessible pages were removed.
+    - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
+    - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
+    - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
+    - The "Site admin mode" link in the site footer did not change state when clicked.
+  changes:
+    - Memcached connection limits were increased to better accommodate large cluster topologies.
+    - More effectively identify and delete webhook logs that are outside of the webhook log retention window.
+    - The Dependency Graph API previously ran with a statically defined port.
+    - The default shard counts for cluster-related Elasticsearch shard settings have been updated.
+    - The “Triage” and “Maintain” team roles are preserved during repository migrations.
+    - '`NotProcessedError` exceptions were occurring unnecessarily.'
+    - Performance has been improved for web requests made by enterprise owners.
+  known_issues:
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - If {% data variables.product.prodname_actions %} is enabled for {% data variables.product.prodname_ghe_server %}, teardown of a replica node with `ghe-repl-teardown` will succeed, but may return `ERROR:Running migrations`.
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml
new file mode 100644
index 0000000000..4987d617d1
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml
@@ -0,0 +1,44 @@
+---
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
+    - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
+    - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
+    - 包已更新到最新的安全版本。
+  bugs:
+    - Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
+    - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
+    - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
+    - A subset of internal configuration files are more reliably updated after a hotpatch.
+    - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
+    - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
+    - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
+    - In some cluster topologies, webhook delivery information was not available.
+    - In HA configurations, tearing down a replica would fail if {% data variables.product.prodname_actions %} had previously been enabled.
+    - Elasticsearch health checks would not allow a yellow cluster status when running migrations.
+    - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
+    - When using `ghe-migrator` or exporting from {% data variables.product.prodname_dotcom_the_website %}, a long-running export would fail when data was deleted mid-export.
+    - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
+    - Links to inaccessible pages were removed.
+    - Navigating away from a comparison of two commits in the web UI would have the diff persist in other pages.
+    - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
+    - 'The [Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API endpoint would respond with an error when attempting to remove a member managed externally by a SCIM group.'
+    - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
+    - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
+    - The "Site admin mode" link in the site footer did not change state when clicked.
+    - 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.'
+  changes:
+    - Memcached connection limits were increased to better accommodate large cluster topologies.
+    - The Dependency Graph API previously ran with a statically defined port.
+    - The default shard counts for cluster-related Elasticsearch shard settings have been updated.
+    - The “Triage” and “Maintain” team roles are preserved during repository migrations.
+    - Performance has been improved for web requests made by enterprise owners.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml
index 9f19324796..35642edada 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml
@@ -169,6 +169,7 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
   deprecations:
     - 
       heading: 弃用 GitHub Enterprise Server 2.22
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
index 9fea6fe634..8a5d8db39b 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/1.yml
@@ -14,3 +14,4 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml
index 1b726136e9..ebdf502d9f 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/2.yml
@@ -29,3 +29,4 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml
index 06aa240abb..d3cf8797f5 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/3.yml
@@ -27,3 +27,4 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml
index 2b91cfca20..dfec3aef30 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/4.yml
@@ -22,3 +22,4 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml
index f14cae4d57..bee2a27a7c 100644
--- a/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/5.yml
@@ -16,3 +16,4 @@ sections:
     - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml
new file mode 100644
index 0000000000..5e158252b5
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-3/6.yml
@@ -0,0 +1,50 @@
+---
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
+    - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
+    - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
+    - 包已更新到最新的安全版本。
+  bugs:
+    - When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.
+    - Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
+    - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
+    - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
+    - A subset of internal configuration files are more reliably updated after a hotpatch.
+    - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
+    - In a cluster environment, Git LFS operations could fail with failed internal API calls that crossed multiple web nodes.
+    - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
+    - In some cluster topologies, webhook delivery information was not available.
+    - Elasticsearch health checks would not allow a yellow cluster status when running migrations.
+    - Repositories would display a non-functional Discussions tab in the web UI.
+    - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
+    - Links to inaccessible pages were removed.
+    - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
+    - Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.
+    - LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.
+    - Following a link to a pull request from the users Pull Request dashboard would result in the repository header not loading.
+    - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
+    - The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.
+    - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
+    - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
+    - The "Site admin mode" link in the site footer did not change state when clicked.
+    - 'The `spokesctl cache-policy rm` command no longer fails with the message `error: failed to delete cache policy`.'
+  changes:
+    - Memcached connection limits were increased to better accommodate large cluster topologies.
+    - The Dependency Graph API previously ran with a statically defined port.
+    - The default shard counts for cluster-related Elasticsearch shard settings have been updated.
+    - When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.
+    - The “Triage” and “Maintain” team roles are preserved during repository migrations.
+    - Performance has been improved for web requests made by enterprise owners.
+  known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - '{% data variables.product.prodname_registry %} npm 注册表不再返回元数据响应的时间值。这样做是为了大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。'
+    - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
+    - '{% data variables.product.prodname_actions %} storage settings cannot be validated and saved in the {% data variables.enterprise.management_console %} when "Force Path Style" is selected, and must instead be configured with the `ghe-actions-precheck` command line utility.'
+    - '{% data variables.product.prodname_ghe_server %} 3.3 instances installed on Azure and provisioned with 32+ CPU cores would fail to launch, due to a bug present in the current Linux kernel. [Updated: 2022-04-08]'
diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
new file mode 100644
index 0000000000..a5aef0cc9e
--- /dev/null
+++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml
@@ -0,0 +1,93 @@
+---
+date: '2022-04-04'
+sections:
+  security_fixes:
+    - 'MEDIUM: A path traversal vulnerability was identified in {% data variables.product.prodname_ghe_server %} Management Console that allowed the bypass of CSRF protections. This vulnerability affected all versions of {% data variables.product.prodname_ghe_server %} prior to 3.5 and was fixed in versions 3.1.19, 3.2.11, 3.3.6, 3.4.1. This vulnerability was reported via the {% data variables.product.prodname_dotcom %} Bug Bounty program and has been assigned CVE-2022-23732.'
+    - 'MEDIUM: An integer overflow vulnerability was identified in the 1.x branch and the 2.x branch of `yajil` which leads to subsequent heap memory corruption when dealing with large (~2GB) inputs. This vulnerability was reported internally and has been assigned CVE-2022-24795. '
+    - Support bundles could include sensitive files if {% data variables.product.prodname_actions %} was enabled.
+    - 包已更新到最新的安全版本。
+  bugs:
+    - A workflow run may not complete if it uses composite-actions.
+    - When enabling {% data variables.product.prodname_dependabot %}, an error caused some security advisories to temporarily read as no-longer applicable.
+    - Minio processes would have high CPU usage if an old configuration option was present after upgrading {% data variables.product.prodname_ghe_server %}.
+    - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release.
+    - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time.
+    - A subset of internal configuration files are more reliably updated after a hotpatch.
+    - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly.
+    - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges.
+    - In some cluster topologies, webhook delivery information was not available.
+    - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job.
+    - Elasticsearch health checks would not allow a yellow cluster status when running migrations.
+    - When using the [Migrations API](/rest/reference/migrations), queued export jobs were not processed.
+    - Repositories would display a non-functional Discussions tab in the web UI.
+    - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account.
+    - LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously.
+    - Links to inaccessible pages were removed.
+    - Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued.
+    - Empty repositories didnt sync correctly to cache servers.
+    - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team.
+    - The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group.
+    - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail.
+    - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available.
+    - The "Site admin mode" link in the site footer did not change state when clicked.
+  changes:
+    - Memcached connection limits were increased to better accommodate large cluster topologies.
+    - The Dependency Graph API previously ran with a statically defined port.
+    - The default shard counts for cluster-related Elasticsearch shard settings have been updated.
+    - The [Migrations API](/rest/reference/migrations) now generates exports of repositories.
+    - When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved.
+    - The “Triage” and “Maintain” team roles are preserved during repository migrations.
+    - Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments.
+    - Performance has been improved for web requests made by enterprise owners.
+  known_issues:
+    - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
+    - 自定义防火墙规则在升级过程中被删除。
+    - Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
+    - 如果议题包含文件路径长于 255 个字符的同一仓库中 blob 的永久链接，则议题无法关闭。
+    - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results.
+    - '{% 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 need to be restarted after restoring appliance from backup taken on a different host.
+  deprecations:
+    - 
+      heading: Deprecation of GitHub Enterprise Server 3.0
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.0 was discontinued on February 16, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: Deprecation of GitHub Enterprise Server 3.1
+      notes:
+        - '**{% data variables.product.prodname_ghe_server %} 3.1 will be discontinued on June 3, 2022**. This means that no patch releases will be made, even for critical security issues, after this date. For better performance, improved security, and new features, [upgrade to the newest version of {% data variables.product.prodname_ghe_server %}](/enterprise-server@3.4/admin/enterprise-management/upgrading-github-enterprise-server) as soon as possible.'
+    - 
+      heading: XenServer Hypervisor 支持终止
+      notes:
+        - Starting in {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_ghe_server %} on XenServer was deprecated and is no longer supported. Please contact [GitHub Support](https://support.github.com) with questions or concerns.
+    - 
+      heading: Deprecation of the Content Attachments API preview
+      notes:
+        - Due to low usage, we have deprecated the Content References API preview in {% data variables.product.prodname_ghe_server %} 3.4. The API was previously accessible with the `corsair-preview` header. Users can continue to navigate to external URLs without this API. Any registered usages of the Content References API will no longer receive a webhook notification for URLs from your registered domain(s) and we no longer return valid response codes for attempted updates to existing content attachments.
+    - 
+      heading: Deprecation of the Codes of Conduct API preview
+      notes:
+        - 'The Codes of Conduct API preview, which was accessible with the `scarlet-witch-preview` header, is deprecated and no longer accessible in {% data variables.product.prodname_ghe_server %} 3.4. We instead recommend using the "[Get community profile metrics](/rest/reference/repos#get-community-profile-metrics)" endpoint to retrieve information about a repository''s code of conduct. For more information, see the "[Deprecation Notice: Codes of Conduct API preview](https://github.blog/changelog/2021-10-06-deprecation-notice-codes-of-conduct-api-preview/)" in the {% data variables.product.prodname_dotcom %} changelog.'
+    - 
+      heading: Deprecation of OAuth Application API endpoints and API authentication using query parameters
+      notes:
+        - |
+          Starting with {% data variables.product.prodname_ghe_server %} 3.4, the [deprecated version of the OAuth Application API endpoints](https://developer.github.com/changes/2020-02-14-deprecating-oauth-app-endpoint/#endpoints-affected) have been removed. If you encounter 404 error messages on these endpoints, convert your code to the versions of the OAuth Application API that do not have `access_tokens` in the URL. We've also disabled the use of API authentication using query parameters. We instead recommend using [API authentication in the request header](https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param/#changes-to-make).
+    - 
+      heading: Deprecation of the CodeQL runner
+      notes:
+        - The {% data variables.product.prodname_codeql %} runner is deprecated in {% data variables.product.prodname_ghe_server %} 3.4 and is no longer supported. The deprecation only affects users who use {% data variables.product.prodname_codeql %} code scanning in third party CI/CD systems; {% data variables.product.prodname_actions %} users are not affected. We strongly recommend that customers migrate to the {% data variables.product.prodname_codeql %} CLI, which is a feature-complete replacement for the {% data variables.product.prodname_codeql %} runner. For more information, see the [{% data variables.product.prodname_dotcom %} changelog](https://github.blog/changelog/2021-09-21-codeql-runner-deprecation/).
+    - 
+      heading: Deprecation of custom bit-cache extensions
+      notes:
+        - |
+          Starting in {% data variables.product.prodname_ghe_server %} 3.1, support for {% data variables.product.company_short %}'s proprietary bit-cache extensions began to be phased out. These extensions are deprecated in {% data variables.product.prodname_ghe_server %} 3.3 onwards.
+
+          Any repositories that were already present and active on {% data variables.product.product_location %} running version 3.1 or 3.2 will have been automatically updated.
+
+          Repositories which were not present and active before upgrading to {% data variables.product.prodname_ghe_server %} 3.3 may not perform optimally until a repository maintenance task is run and has successfully completed.
+
+          To start a repository maintenance task manually, browse to `https://<hostname>/stafftools/repositories/<owner>/<repository>/network` for each affected repository and click the Schedule button.
+  backups:
+    - '{% data variables.product.prodname_ghe_server %} 3.4 requires at least [GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils) for [Backups and Disaster Recovery](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance).'
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
new file mode 100644
index 0000000000..703f7837f0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-dry-run-results.md
@@ -0,0 +1,3 @@
+1. 空运行完成后，您将看到存储库中的结果示例（最多 1000 个）。 查看结果并确定任何误报结果。 ![显示空运行结果的屏幕截图](/assets/images/help/repository/secret-scanning-publish-pattern.png)
+1. Edit the new custom pattern to fix any problems with the results, then, to test your changes, click **Save and dry run**.
+{% indented_data_reference reusables.secret-scanning.beta-dry-runs spaces=3 %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md
new file mode 100644
index 0000000000..5a1eae44ce
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md
@@ -0,0 +1,2 @@
+1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**. ![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for an organization](/assets/images/help/organizations/secret-scanning-enable-push-protection.png)
+1. Optionally, click "Automatically enable for private repositories added to {% data variables.product.prodname_secret_scanning %}."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-repo.md b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
new file mode 100644
index 0000000000..df17a22901
--- /dev/null
+++ b/translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-repo.md
@@ -0,0 +1 @@
+1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable**. ![Screenshot showing how to enable push protection for {% data variables.product.prodname_secret_scanning %} for a repository](/assets/images/help/repository/secret-scanning-enable-push-protection.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
new file mode 100644
index 0000000000..6395fd89ad
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-action-categories.md
@@ -0,0 +1,158 @@
+| 类别名称 | 描述 |
+| ---- | -- |
+|      |    |
+{%- ifversion fpt or ghec %}
+| `account` | Contains activities related to an organization account. | `advisory_credit`   | Contains activities related to crediting a contributor for a security advisory in the {% data variables.product.prodname_advisory_database %}. 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。
+{%- endif %}
+| `artifact` | Contains activities related to {% data variables.product.prodname_actions %} workflow run artifacts.
+{%- ifversion ghec %}
+| `audit_log_streaming`  | Contains activities related to streaming audit logs for organizations in an enterprise account.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `billing` | Contains activities related to an organization's billing.
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `business`  | Contains activities related to business settings for an enterprise.
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `business`  | Contains activities related to business settings for an enterprise.
+{%- endif %}
+{%- if secret-scanning-audit-log-custom-patterns %}
+| `business_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an enterprise.
+{%- endif %}
+| `checks`   | Contains activities related to check suites and runs.
+{%- ifversion fpt or ghec %}
+| `codespaces` | Contains activities related to an organization's codespaces.
+{%- endif %}
+| `commit_comment` | Contains activities related to updating or deleting commit comments.
+{%- ifversion ghes %}
+| `config_entry` |  Contains activities related to configuration settings. These events are only visible in the site admin audit log.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4864 %}
+| `dependabot_alerts`  | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_alerts %} in existing repositories. 更多信息请参阅“[关于易受攻击的依赖项的警报](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 | `dependabot_alerts_new_repos`   | Contains organization-level configuration activities for  {% data variables.product.prodname_dependabot_alerts %} in new repositories created in the organization. | `dependabot_repository_access` | Contains activities related to which private repositories in an organization {% data variables.product.prodname_dependabot %} is allowed to access.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.2 %}
+| `dependabot_security_updates`   | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} in existing repositories. 更多信息请参阅“[配置 {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)。” | `dependabot_security_updates_new_repos` | Contains organization-level configuration activities for {% data variables.product.prodname_dependabot_security_updates %} for new repositories created in the organization.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
+| `dependency_graph` | Contains organization-level configuration activities for dependency graphs for repositories. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。 | `dependency_graph_new_repos`  | Contains organization-level configuration activities for new repositories created in the organization.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `discussion` | Contains activities related to team discussions. | `discussion_comment` | Contains activities related to comments posted in discussions on a team page. | `discussion_post`   | Contains activities related to discussions posted to a team page. | `discussion_post_reply`   | Contains activities related to replies to discussions posted to a team page.
+{%- endif %}
+{%- ifversion ghec or ghes %}
+| `dotcom_connection` | Contains activities related to {% data variables.product.prodname_github_connect %}. | `enterprise` | Contains activities related to enterprise settings.
+{%- endif %}
+{%- ifversion ghec %}
+| `enterprise_domain` | Contains activities related to verified enterprise domains. | `enterprise_installation` | Contains activities related to {% data variables.product.prodname_github_app %}s associated with an {% data variables.product.prodname_github_connect %} enterprise connection.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `environment` | Contains activities related to {% data variables.product.prodname_actions %} environments.
+{%- endif %}
+{%- ifversion ghae %}
+| `external_group` | Contains activities related to Okta groups. | `external_identity` | Contains activities related to a user in an Okta group.
+{%- endif %}
+| `gist` | Contains activities related to Gists. | `git` | Contains activities related to Git events. | `hook` | Contains activities related to webhooks. | `integration` | Contains activities related to integrations in an account. | `integration_installation` | Contains activities related to integrations installed in an account. | `integration_installation_request`  | Contains activities related to organization member requests for owners to approve integrations for use in the organization.
+{%- ifversion ghec or ghae %}
+| `ip_allow_list`   | Contains activities related to enabling or disabling the IP allow list for an organization. | `ip_allow_list_entry`   | Contains activities related to the creation, deletion, and editing of an IP allow list entry for an organization.
+{%- endif %}
+| `issue`  | Contains activities related to pinning, transferring, or deleting an issue in a repository. | `issue_comment` | Contains activities related to pinning, transferring, or deleting issue comments. | `issues` | Contains activities related to enabling or disabling issue creation for an organization.
+{%- ifversion fpt or ghec %}
+| `marketplace_agreement_signature` | Contains activities related to signing the {% data variables.product.prodname_marketplace %} Developer Agreement. | `marketplace_listing` | Contains activities related to listing apps in {% data variables.product.prodname_marketplace %}.
+{%- endif %}
+| `members_can_create_pages`   | Contains activities related to managing the publication of {% data variables.product.prodname_pages %} sites for repositories in the organization. 更多信息请参阅“[管理组织的 {% data variables.product.prodname_pages %} 站点发布](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)”。 | `members_can_create_private_pages` | Contains activities related to managing the publication of private {% data variables.product.prodname_pages %} sites for repositories in the organization. | `members_can_create_public_pages` | Contains activities related to managing the publication of public {% data variables.product.prodname_pages %} sites for repositories in the organization.
+{%- ifversion ghec or ghes or ghae %}
+| `members_can_delete_repos` | Contains activities related to enabling or disabling repository creation for an organization.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `members_can_view_dependency_insights` | Contains organization-level configuration activities allowing organization members to view dependency insights. | `migration` | Contains activities related to transferring data from a *source* location (such as a {% data variables.product.prodname_dotcom_the_website %} organization or a {% data variables.product.prodname_ghe_server %} instance) to a *target* {% data variables.product.prodname_ghe_server %} instance.
+{%- endif %}
+| `oauth_access` | Contains activities related to OAuth access tokens. | `oauth_application` | Contains activities related to OAuth Apps.
+{%- ifversion fpt or ghec %}
+| `oauth_authorization` | Contains activities related to authorizing OAuth Apps.
+{%- endif %}
+| `org`   | Contains activities related to organization membership.
+{%- ifversion ghec or ghes or ghae %}
+| `org_credential_authorization` | Contains activities related to authorizing credentials for use with SAML single sign-on.
+{%- endif %}
+{%- if secret-scanning-audit-log-custom-patterns %}
+| `org_secret_scanning_custom_pattern` | Contains activities related to custom patterns for secret scanning in an organization. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。 | `org.secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in an organization. 更多信息请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。
+{%- endif %}
+| `organization_default_label` | Contains activities related to default labels for repositories in an organization.
+{%- ifversion fpt or ghec or ghes > 3.1 %}
+| `organization_domain` | Contains activities related to verified organization domains. | `organization_projects_change` | Contains activities related to organization-wide project boards in an enterprise.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.0 or ghae %}
+| `packages`  | Contains activities related to {% data variables.product.prodname_registry %}.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `pages_protected_domain` | Contains activities related to verified custom domains for {% data variables.product.prodname_pages %}. | `payment_method`  | Contains activities related to how an organization pays for {% data variables.product.prodname_dotcom %}. | `prebuild_configuration` | Contains activities related to prebuild configurations for {% data variables.product.prodname_github_codespaces %}.
+{%- endif %}
+{%- ifversion ghes %}
+| `pre_receive_environment` | Contains activities related to pre-receive hook environments. | `pre_receive_hook` | Contains activities related to pre-receive hooks.
+{%- endif %}
+{%- ifversion ghes %}
+| `private_instance_encryption` | Contains activities related to enabling private mode for an enterprise.
+{%- endif %}
+| `private_repository_forking` | Contains activities related to allowing forks of private and internal repositories, for a repository, organization or enterprise.
+{%- ifversion fpt or ghec %}
+| `profile_picture`   | Contains activities related to an organization's profile picture.
+{%- endif %}
+| `project` | Contains activities related to project boards. | `project_field` | Contains activities related to field creation and deletion in a project board. | `project_view` | Contains activities related to view creation and deletion in a project board. | `protected_branch` | Contains activities related to protected branches. | `public_key` | Contains activities related to SSH keys and deploy keys.
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| `pull_request` | Contains activities related to pull requests. | `pull_request_review` | Contains activities related to pull request reviews. | `pull_request_review_comment` | Contains activities related to pull request review comments.
+{%- endif %}
+| `repo` | Contains activities related to the repositories owned by an organization.
+{%- ifversion fpt or ghec %}
+| `repository_advisory` | Contains repository-level activities related to security advisories in the {% data variables.product.prodname_advisory_database %}.  更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 安全通告](/github/managing-security-vulnerabilities/about-github-security-advisories)”。 | `repository_content_analysis`   | Contains activities related to [enabling or disabling data use for a private repository](/articles/about-github-s-use-of-your-data). | `repository_dependency_graph`   | Contains repository-level activities related to enabling or disabling the dependency graph for a {% ifversion fpt or ghec %}private {% endif %}repository. 更多信息请参阅“[关于依赖关系图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”。
+{%- endif %}
+| `repository_image` | Contains activities related to images for a repository. | `repository_invitation` | Contains activities related to invitations to join a repository. | `repository_projects_change` | Contains activities related to enabling projects for a repository or for all repositories in an organization.
+{%- ifversion ghec or ghes or ghae %}
+| `repository_secret_scanning`  | Contains repository-level activities related to secret scanning. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。
+{%- endif %}
+{%- if secret-scanning-audit-log-custom-patterns %}
+| `repository_secret_scanning_custom_pattern` | Contains activities related to secret scanning custom patterns in a repository. 更多信息请参阅“[定义机密扫描的自定义模式](/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning)”。 |{% endif %}{% if secret-scanning-audit-log-custom-patterns %}| | `repository_secret_scanning_push_protection` | Contains activities related to secret scanning custom patterns in a repository. 更多信息请参阅“[使用机密扫描保护推送](/code-security/secret-scanning/protecting-pushes-with-secret-scanning)”。
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `repository_visibility_change` | Contains activities related to allowing organization members to change repository visibilities for the organization.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes or ghae-issue-4864 %}
+| `repository_vulnerability_alert`   | Contains activities related to [{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies).
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `repository_vulnerability_alerts` | Contains repository-level configuration activities for {% data variables.product.prodname_dependabot_alerts %}. | `required_status_check` | Contains activities related to required status checks for protected branches.
+{%- endif %}
+{%- ifversion ghec or ghes > 3.1 %}
+| `restrict_notification_delivery` | Contains activities related to the restriction of email notifications to approved or verified domains for an enterprise.
+{%- endif %}
+{%- ifversion ghec or ghes > 3.4 or ghae-issue-6271 %}
+| `role` | Contains activities related to [custom repository roles](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization).
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `secret_scanning`   | Contains organization-level configuration activities for secret scanning in existing repositories. 更多信息请参阅“[关于密钥扫描](/github/administering-a-repository/about-secret-scanning)”。 | `secret_scanning_new_repos` | Contains organization-level configuration activities for secret scanning for new repositories created in the organization.
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `security_key` | Contains activities related to security keys registration and removal.
+{%- endif %}
+{%- ifversion fpt or ghec %}
+| `sponsors`  | Contains events related to sponsor buttons (see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)").
+{%- endif %}
+{%- ifversion ghec or ghes or ghae %}
+| `ssh_certificate_authority` | Contains activities related to a SSH certificate authority in an organization or enterprise. | `ssh_certificate_requirement` | Contains activities related to requiring members use SSH certificates to access organization resources.
+{%- endif %}
+| `staff` | Contains activities related to a site admin performing an action. | `team` | Contains activities related to teams in an organization. | `team_discussions` | Contains activities related to managing team discussions for an organization.
+{%- ifversion ghec %}
+| `team_sync_tenant` | Contains activities related to team synchronization with an IdP for an enterprise or organization.
+{%- endif %}
+{%- ifversion fpt or ghes %}
+| `two_factor_authentication` | Contains activities related to two-factor authentication.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes or ghae %}
+| `user` | Contains activities related to users in an enterprise or organization.
+{%- endif %}
+{%- ifversion ghec or ghes %}
+| `user_license` | Contains activities related to a user occupying a licensed seat in, and being a member of, an enterprise.
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.1 or ghae %}
+| `workflows`   | Contains activities related to {% data variables.product.prodname_actions %} workflows.
+{%- endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md b/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
new file mode 100644
index 0000000000..67ccede9e1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-events-workflows.md
@@ -0,0 +1,9 @@
+| 操作 | 描述 |
+| -- | -- |
+|    |    |
+{%- ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| `workflows.approve_workflow_job` | A workflow job was approved. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | `workflows.cancel_workflow_run` | A workflow run was cancelled. 更多信息请参阅“[取消工作流程](/actions/managing-workflow-runs/canceling-a-workflow)。 | `workflows.delete_workflow_run` | A workflow run was deleted. 更多信息请参阅“[删除工作流程运行](/actions/managing-workflow-runs/deleting-a-workflow-run)”。 | `workflows.disable_workflow` | A workflow was disabled. | `workflows.enable_workflow` | A workflow was enabled, after previously being disabled by `disable_workflow`. | `workflows.reject_workflow_job` | A workflow job was rejected. For more information, see "[Reviewing deployments](/actions/managing-workflow-runs/reviewing-deployments)." | `workflows.rerun_workflow_run` | A workflow run was re-run. 更多信息请参阅“[重新运行工作流程](/actions/managing-workflow-runs/re-running-a-workflow)。
+{%- endif %}
+{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4963 %}
+| `workflows.completed_workflow_run` | A workflow status changed to `completed`. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history). | `workflows.created_workflow_run` | A workflow run was created. 只能使用 REST API 查看；在 UI 或 JSON/CSV 导出中不可见。 更多信息请参阅“[创建示例工作流程](/actions/learn-github-actions/introduction-to-github-actions#create-an-example-workflow)”。 | `workflows.prepared_workflow_job` | A workflow job was started. 包括提供给作业的机密列表。 Can only be viewed using the REST API. It is not visible in the the {% data variables.product.prodname_dotcom %} web interface or included in the JSON/CSV export. 更多信息请参阅“[触发工作流程的事件](/actions/reference/events-that-trigger-workflows)”。
+{%- endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-operation.md b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-operation.md
new file mode 100644
index 0000000000..120bb1eae1
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-operation.md
@@ -0,0 +1,11 @@
+### 基于操作搜索
+
+使用`操作`限定符将操作限于特定类型的操作。 例如：
+
+  * `operation:access` 查找其中资源被访问过的所有事件。
+  * `operation:authentication` 查找其中执行了身份验证事件的所有事件。
+  * `operation:create` 查找在其中创建了资源的所有事件。
+  * `operation:modify` 查找在其中修改了现有资源的所有事件。
+  * `operation:remove` 查找在其中删除的现有资源的所有事件。
+  * `operation:restore` 查找在其中恢复了现有资源的所有事件。
+  * `operation:transfer` 查找在其中转移了现有资源的所有事件。
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-repo.md b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-repo.md
new file mode 100644
index 0000000000..7a3def9017
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-repo.md
@@ -0,0 +1,9 @@
+### 基于仓库搜索
+
+使用 `repo` 限定符将操作限于特定仓库。 例如：
+
+  * `repo:my-org/our-repo` 会找到在 `my-org` 组织的 `our-repo` 仓库中发生的所有事件。
+  * `repo:my-org/our-repo repo:my-org/another-repo` 会找到在 `my-org` 组织的 `our-repo` 和 `another-repo` 仓库中发生的所有事件。
+  * `-repo:my-org/not-this-repo` 会排除在 `my-org` 组织的 `not-this-repo` 仓库中发生的所有事件。
+
+请注意，您必须在 `repo` 限定符中包含帐户名称；仅搜索 `repo:our-repo` 将不起作用。
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-user.md b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-user.md
new file mode 100644
index 0000000000..78ffd31b14
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-search-by-user.md
@@ -0,0 +1,9 @@
+### 基于用户搜索
+
+`actor` 限定符可将事件范围限于执行操作的人员。 例如：
+
+  * `actor:octocat` 会找到 `octocat` 执行的所有事件。
+  * `actor:octocat actor:hubot` 会找到 `octocat` 和 `hubot` 执行的所有事件。
+  * `-actor:hubot` 会排除 `hubot` 执行的所有事件。
+
+请注意，只能使用 {% data variables.product.product_name %} 用户名，而不是个人的真实姓名。
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-search-list-info-about-action.md b/translations/zh-CN/data/reusables/audit_log/audit-log-search-list-info-about-action.md
new file mode 100644
index 0000000000..86b800ed82
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-search-list-info-about-action.md
@@ -0,0 +1,11 @@
+The name for each audit log entry is composed of the `action` object or category qualifier, followed by an operation type. For example, the `repo.create` entry refers to the `create` operation on the `repo` category.
+
+每个审核日志条目都显示有关事件的适用信息，例如：
+
+- The {% ifversion ghec or ghes or ghae %}enterprise or {% endif %}organization an action was performed in
+- The user (actor) who performed the action
+- The user affected by the action
+- 执行操作的仓库
+- 执行的操作内容
+- 发生操作的国家/地区
+- 操作发生的日期和时间
diff --git a/translations/zh-CN/data/reusables/audit_log/audit-log-search.md b/translations/zh-CN/data/reusables/audit_log/audit-log-search.md
index 3fa7739853..f52f24509f 100644
--- a/translations/zh-CN/data/reusables/audit_log/audit-log-search.md
+++ b/translations/zh-CN/data/reusables/audit_log/audit-log-search.md
@@ -1,41 +1,9 @@
-日志列出每个操作的以下信息：
-
-* 执行操作的仓库
-* 执行操作的用户
-* 执行的操作内容
-* 发生操作的国家/地区
-* 操作发生的日期和时间
+{% data reusables.audit_log.audit-log-search-list-info-about-action %}
 
 请注意，无法使用文本搜索条目。 但是，您可以使用各种过滤器构建搜索查询。 查询日志时使用的许多运算符，如 `-`、`>` 或 `<`，与在 {% data variables.product.product_name %} 上搜索时的格式相同。 更多信息请参阅“[在 {% data variables.product.prodname_dotcom %} 上搜索](/github/searching-for-information-on-github/about-searching-on-github)”。
 
-### 基于操作搜索
+{% data reusables.audit_log.audit-log-search-by-operation %}
 
-使用`操作`限定符将操作限于特定类型的操作。 例如：
+{% data reusables.audit_log.audit-log-search-by-repo %}
 
-  * `operation:access` 查找其中资源被访问过的所有事件。
-  * `operation:authentication` 查找其中执行了身份验证事件的所有事件。
-  * `operation:create` 查找在其中创建了资源的所有事件。
-  * `operation:modify` 查找在其中修改了现有资源的所有事件。
-  * `operation:remove` 查找在其中删除的现有资源的所有事件。
-  * `operation:restore` 查找在其中恢复了现有资源的所有事件。
-  * `operation:transfer` 查找在其中转移了现有资源的所有事件。
-
-### 基于仓库搜索
-
-使用 `repo` 限定符将操作限于特定仓库。 例如：
-
-  * `repo:my-org/our-repo` 会找到在 `my-org` 组织的 `our-repo` 仓库中发生的所有事件。
-  * `repo:my-org/our-repo repo:my-org/another-repo` 会找到在 `my-org` 组织的 `our-repo` 和 `another-repo` 仓库中发生的所有事件。
-  * `-repo:my-org/not-this-repo` 会排除在 `my-org` 组织的 `not-this-repo` 仓库中发生的所有事件。
-
-请注意，您必须在 `repo` 限定符中包含帐户名称；仅搜索 `repo:our-repo` 将不起作用。
-
-### 基于用户搜索
-
-`actor` 限定符可将事件范围限于执行操作的人员。 例如：
-
-  * `actor:octocat` 会找到 `octocat` 执行的所有事件。
-  * `actor:octocat actor:hubot` 会找到 `octocat` 和 `hubot` 执行的所有事件。
-  * `-actor:hubot` 会排除 `hubot` 执行的所有事件。
-
-请注意，只能使用 {% data variables.product.product_name %} 用户名，而不是个人的真实姓名。
+{% data reusables.audit_log.audit-log-search-by-user %}
diff --git a/translations/zh-CN/data/reusables/audit_log/audited-data-list.md b/translations/zh-CN/data/reusables/audit_log/audited-data-list.md
index 5901c45a7f..282c3ca009 100644
--- a/translations/zh-CN/data/reusables/audit_log/audited-data-list.md
+++ b/translations/zh-CN/data/reusables/audit_log/audited-data-list.md
@@ -1,2 +1,2 @@
 {% data reusables.audit_log.audit-log-api-info %}
-* Git 事件，如克隆、获取和推送
+{% ifversion fpt or ghec %}* Git events, such as cloning, fetching, and pushing{% endif %}
diff --git a/translations/zh-CN/data/reusables/audit_log/exported-git-log-keys-and-values.md b/translations/zh-CN/data/reusables/audit_log/exported-git-log-keys-and-values.md
new file mode 100644
index 0000000000..d20531cff0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/exported-git-log-keys-and-values.md
@@ -0,0 +1,13 @@
+将日志导出为 JSON 或 CSV 后，您将在生成的文件中看到以下键和值。
+
+| 键                   | 示例值                    |
+| ------------------- | ---------------------- |
+| `@timestamp`        | 1429548104000          |
+| `actor`             | octocat                |
+| `action`            | git.clone              |
+| `org`               | octo-org               |
+| `business`          | avocado-corp           |
+| `repo`              | octo-org/documentation |
+| `repository_public` | false                  |
+| `用户`                | codertocat             |
+| `protocol_name`     | http                   |
diff --git a/translations/zh-CN/data/reusables/audit_log/exported-log-keys-and-values.md b/translations/zh-CN/data/reusables/audit_log/exported-log-keys-and-values.md
index d1fe0f1bb2..08f3a6df0e 100644
--- a/translations/zh-CN/data/reusables/audit_log/exported-log-keys-and-values.md
+++ b/translations/zh-CN/data/reusables/audit_log/exported-log-keys-and-values.md
@@ -1,16 +1,18 @@
-将日志导出为 JSON 或 CSV 后，您将在生成的文件中看到以下键和值。
+After you export the log, you'll see the following keys and values in the resulting file.
 
-| 键                   | 示例值                                                                            |
-| ------------------- | ------------------------------------------------------------------------------ |
-| `action`            | team.create                                                                    |
-| `actor`             | octocat                                                                        |
-| `用户`                | codertocat                                                                     |
-| `org`               | octo-org                                                                       |
-| `repo`              | octo-org/documentation                                                         |
-| `created_at`        | 1429548104000 (Timestamp shows the time since Epoch with milliseconds.)        |
-| `data.hook_id`      | 245                                                                            |
-| `data.events`       | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] |
-| `data.events_were`  | ["push", "pull_request", "issues"]                                             |
-| `data.target_login` | octocat                                                                        |
-| `data.old_user`     | hubot                                                                          |
-| `data.team`         | octo-org/engineering                                                           |
+| 键                             | 示例值                                                                            |
+| ----------------------------- | ------------------------------------------------------------------------------ |
+| `action`                      | team.create                                                                    |
+| `actor`                       | octocat                                                                        |
+| `用户`                          | codertocat                                                                     |
+| `actor_location.country_code` | US                                                                             |
+| `org`                         | octo-org                                                                       |
+| `repo`                        | octo-org/documentation                                                         |
+| `created_at`                  | 1429548104000 (Timestamp shows the time since Epoch with milliseconds.)        |
+| `data.email`                  | octocat@nowhere.com                                                            |
+| `data.hook_id`                | 245                                                                            |
+| `data.events`                 | ["issues", "issue_comment", "pull_request", "pull_request_review_comment"] |
+| `data.events_were`            | ["push", "pull_request", "issues"]                                             |
+| `data.target_login`           | octocat                                                                        |
+| `data.old_user`               | hubot                                                                          |
+| `data.team`                   | octo-org/engineering                                                           |
diff --git a/translations/zh-CN/data/reusables/audit_log/retention-periods.md b/translations/zh-CN/data/reusables/audit_log/retention-periods.md
new file mode 100644
index 0000000000..dbed08d376
--- /dev/null
+++ b/translations/zh-CN/data/reusables/audit_log/retention-periods.md
@@ -0,0 +1,3 @@
+The audit log lists events triggered by activities that affect your enterprise{% ifversion not ghec %}. Audit logs for {% data variables.product.product_name %} are retained indefinitely.{% else %} within the current month and up to the previous six months. The audit log retains Git events for seven days.{% endif %}
+
+{% data reusables.audit_log.only-three-months-displayed %}
diff --git a/translations/zh-CN/data/reusables/classroom/reuse-assignment-link.md b/translations/zh-CN/data/reusables/classroom/reuse-assignment-link.md
new file mode 100644
index 0000000000..73b7419440
--- /dev/null
+++ b/translations/zh-CN/data/reusables/classroom/reuse-assignment-link.md
@@ -0,0 +1 @@
+You can reuse an existing assignment in any other classroom you have admin access to, including classrooms in a different organization. For more information, see "[Reuse an assignment](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/reuse-an-assignment)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/about-analysis-origins-link.md b/translations/zh-CN/data/reusables/code-scanning/about-analysis-origins-link.md
index 71037ed620..c81284d1aa 100644
--- a/translations/zh-CN/data/reusables/code-scanning/about-analysis-origins-link.md
+++ b/translations/zh-CN/data/reusables/code-scanning/about-analysis-origins-link.md
@@ -1 +1 @@
-If you run code scanning using multiple configurations, then sometimes an alert will have multiple analysis origins. If an alert has multiple analysis origins, you can view the status of the alert for each analysis origin on the alert page. For more information, see "[About analysis origins](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)."
\ No newline at end of file
+If you run code scanning using multiple configurations, then sometimes an alert will have multiple analysis origins. If an alert has multiple analysis origins, you can view the status of the alert for each analysis origin on the alert page. 更多信息请参阅“[关于分析源](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts#about-analysis-origins)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/codespaces/restrict-port-visibility.md b/translations/zh-CN/data/reusables/codespaces/restrict-port-visibility.md
new file mode 100644
index 0000000000..c59e929b5a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/codespaces/restrict-port-visibility.md
@@ -0,0 +1 @@
+组织所有者可以限制公开或在组织内提供转发端口的能力。 更多信息请参阅“[限制转发端口的可见性](/codespaces/managing-codespaces-for-your-organization/restricting-the-visibility-of-forwarded-ports)”。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
index 81f11ac81d..928192e4c6 100644
--- a/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
+++ b/translations/zh-CN/data/reusables/dependabot/supported-package-managers.md
@@ -4,27 +4,35 @@
 - 是否支持私有 {% data variables.product.prodname_dotcom %} 仓库或注册表中的依赖项
 - 是否支持供应的依赖项
 
-| 包管理器           | YAML 值           | 支持的版本                  | 私有仓库  | 私有注册表 |  供应   |
-| -------------- | ---------------- | ---------------------- |:-----:|:-----:|:-----:|
-| Bundler        | `bundler`        | v1, v2                 |       | **✓** | **✓** |
-| Cargo          | `cargo`          | v1                     | **✓** | **✓** |       |
-| Composer       | `composer`       | v1, v2                 | **✓** | **✓** |       |
-| Docker         | `docker`         | v1                     | **✓** | **✓** |       |
-| Hex            | `混合`             | v1                     |       | **✓** |       |
-| elm-package    | `elm`            | v0.19                  | **✓** | **✓** |       |
-| git submodule  | `gitsubmodule`   | N/A（无版本）               | **✓** | **✓** |       |
-| GitHub Actions | `github-actions` | N/A（无版本）               | **✓** | **✓** |       |
-| Go 模块          | `gomod`          | v1                     | **✓** | **✓** | **✓** |
-| Gradle         | `gradle`         | N/A（无版本）<sup>[1]</sup> | **✓** | **✓** |       |
-| Maven          | `maven`          | N/A（无版本）<sup>[2]</sup> | **✓** | **✓** |       |
-| npm            | `npm`            | v6, v7, v8             | **✓** | **✓** |       |
-| NuGet          | `nuget`          | <= 4.8<sup>[3]</sup>   | **✓** | **✓** |       |
-| pip            | `pip`            | v21.1.2                |       | **✓** |       |
-| pipenv         | `pip`            | <= 2021-05-29          |       | **✓** |       |
-| pip-compile    | `pip`            | 6.1.0                  |       | **✓** |       |
-| poetry         | `pip`            | v1                     |       | **✓** |       |
-| Terraform      | `terraform`      | >= 0.13, <= 1.0        | **✓** | **✓** |       |
-| yarn           | `npm`            | v1                     | **✓** | **✓** |       |
+| 包管理器           | YAML 值           | 支持的版本                  | 私有仓库  | 私有注册表 |                     供应                     |
+| -------------- | ---------------- | ---------------------- |:-----:|:-----:|:------------------------------------------:|
+| Bundler        | `bundler`        | v1, v2                 |       | **✓** |                   **✓**                    |
+| Cargo          | `cargo`          | v1                     | **✓** | **✓** |                                            |
+| Composer       | `composer`       | v1, v2                 | **✓** | **✓** |                                            |
+| Docker         | `docker`         | v1                     | **✓** | **✓** |                                            |
+| Hex            | `混合`             | v1                     |       | **✓** |                                            |
+| elm-package    | `elm`            | v0.19                  | **✓** | **✓** |                                            |
+| git submodule  | `gitsubmodule`   | N/A（无版本）               | **✓** | **✓** |                                            |
+| GitHub Actions | `github-actions` | N/A（无版本）               | **✓** | **✓** |                                            |
+| Go 模块          | `gomod`          | v1                     | **✓** | **✓** |                   **✓**                    |
+| Gradle         | `gradle`         | N/A（无版本）<sup>[1]</sup> | **✓** | **✓** |                                            |
+| Maven          | `maven`          | N/A（无版本）<sup>[2]</sup> | **✓** | **✓** |                                            |
+| npm            | `npm`            | v6, v7, v8             | **✓** | **✓** |                                            |
+| NuGet          | `nuget`          | <= 4.8<sup>[3]</sup>   | **✓** | **✓** |                                            |
+| pip            | `pip`            | v21.1.2                |       | **✓** |                                            |
+| pipenv         | `pip`            | <= 2021-05-29          |       | **✓** |                                            |
+| pip-compile    | `pip`            | 6.1.0                  |       | **✓** |                                            |
+| poetry         | `pip`            | v1                     |       | **✓** | |{% ifversion fpt or ghec or ghes > 3.4 %}
+| pub            | `pub`            | v2 <sup>[4]</sup>      |       |       |                
+{% endif %}
+| Terraform      | `terraform`      | >= 0.13, <= 1.0        | **✓** | **✓** |                                            |
+| yarn           | `npm`            | v1                     | **✓** | **✓** |                                            |
+
+{% tip %}
+
+**Tip:** For package managers such as `pipenv` and `poetry`, you need to use the `pip` YAML value. 例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。
+
+{% endtip %}
 
 [1] {% data variables.product.prodname_dependabot %} 不运行 Gradle，但支持更新以下文件：`build.gradle`、`build.gradle.kts`（用于 Kotlin 项目），以及通过文件名中包含 `dependencies` 的 `apply` 声明加入的文件。 Note that `apply` does not support `apply to`, recursion, or advanced syntaxes (for example, Kotlin's `apply` with `mapOf`, filenames defined by property).
 
@@ -32,4 +40,8 @@
 
 [3] {% data variables.product.prodname_dependabot %} 不运行 NuGet CLI，但支持直到版本 4.8 的大多数功能。
 
-对于包管理器，如 `pipenv` 和 `poetry`，您需要使用 `pip` YAML 值。 例如，如果您使用 `poetry` 来管理 Python 依赖项，并且希望 {% data variables.product.prodname_dependabot %} 监控新版本的依赖项清单文件，请在 *dependabot.yml* 文件中使用 `package-ecosystem: "pip"`。
+{% ifversion fpt or ghec or ghes > 3.4 %}[4] `pub` support is currently in beta. Any known limitations are subject to change. Note that {% data variables.product.prodname_dependabot %}:
+   - Doesn't support updating git dependencies for `pub`.
+   - Won't perform an update when the version that it tries to update to is ignored, even if an earlier version is available.
+
+   For information about configuring your _dependabot.yml_ file for `pub`, see "[Enabling support for beta-level ecosystems](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems)." {% endif %} 
diff --git a/translations/zh-CN/data/reusables/dependency-review/dependency-review-action-beta-note.md b/translations/zh-CN/data/reusables/dependency-review/dependency-review-action-beta-note.md
new file mode 100644
index 0000000000..c227b119b0
--- /dev/null
+++ b/translations/zh-CN/data/reusables/dependency-review/dependency-review-action-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note**: The Dependency Review GitHub Action is currently in public beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md b/translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md
new file mode 100644
index 0000000000..d93a217cd8
--- /dev/null
+++ b/translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note**: The Dependency Review API is currently in public beta and subject to change.
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md
index 551b0ad151..d9d9b15545 100644
--- a/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md
+++ b/translations/zh-CN/data/reusables/discussions/about-categories-and-formats.md
@@ -1 +1 @@
-所有讨论都必须在类别中创建。 拥有维护或管理权限的人定义仓库的类别。 每个类别都有一个格式：开放式讨论、问答或公告。
+所有讨论都必须在类别中创建。 For repository discussions, people with maintain or admin permissions to the repository define the categories for discussions in that repository. For organization discussions, people with maintain or admin permissions to the source repository define the categories for discussions in that organization. 每个类别都有一个格式：开放式讨论、问答或公告。
diff --git a/translations/zh-CN/data/reusables/discussions/about-discussions.md b/translations/zh-CN/data/reusables/discussions/about-discussions.md
index f092efd605..2d6aa2eca4 100644
--- a/translations/zh-CN/data/reusables/discussions/about-discussions.md
+++ b/translations/zh-CN/data/reusables/discussions/about-discussions.md
@@ -1 +1 @@
-{% data variables.product.prodname_discussions %} 是在 {% data variables.product.product_name %} 上供项目的维护者和社区之间进行对话的开放论坛。
+{% data variables.product.prodname_discussions %} is an open forum for conversation among maintainers and the community for a repository or organization on {% data variables.product.product_name %}.
diff --git a/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md b/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
new file mode 100644
index 0000000000..c9964a9b33
--- /dev/null
+++ b/translations/zh-CN/data/reusables/discussions/about-organization-discussions.md
@@ -0,0 +1,5 @@
+When you enable organization discussions, you will choose a repository in the organization to be the source repository for your organization discussions. You can use an existing repository or create a repository specifically to hold your organization discussions. Discussions will appear both on the discussions page for the organization and on the discussion page for the source repository.
+
+Permission to participate in or manage discussion in your organization is based on permission in the source repository. For example, a user needs write permission to the source repository in order to delete an organization discussion. This is identical to how a user needs write permission in a repository in order to delete a repository discussion.
+
+You can change the source repository at any time. If you change the source repository, discussions are not transferred to the new source repository.
diff --git a/translations/zh-CN/data/reusables/discussions/discussions-tab.md b/translations/zh-CN/data/reusables/discussions/discussions-tab.md
index 4b51342d79..0aa40f3594 100644
--- a/translations/zh-CN/data/reusables/discussions/discussions-tab.md
+++ b/translations/zh-CN/data/reusables/discussions/discussions-tab.md
@@ -1 +1 @@
-1. 在仓库名称下，单击 {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions（讨论）**。 ![仓库的"Discussions（讨论）"选项卡](/assets/images/help/discussions/repository-discussions-tab.png)
+1. Under your repository or organization name, click {% octicon "comment-discussion" aria-label="The discussion icon" %} **Discussions**. ![仓库的"Discussions（讨论）"选项卡](/assets/images/help/discussions/repository-discussions-tab.png)
diff --git a/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
new file mode 100644
index 0000000000..d78e849f9b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md
@@ -0,0 +1,5 @@
+1. 在 {% data variables.product.product_location %} 上，导航到组织的主页面。
+1. Under your organization name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. ![组织设置按钮](/assets/images/help/discussions/org-settings.png)
+1. Under "Discussions", select **Enable discussions for this organization**.
+1. Select a repository to use as the source repository for your organization discussions. ![Settings to enable discussions for an organization](/assets/images/help/discussions/enable-org-discussions.png)
+1. 单击 **Save（保存）**。
diff --git a/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md b/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md
index 2ae23ea598..e27d8c79c7 100644
--- a/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md
+++ b/translations/zh-CN/data/reusables/discussions/marking-a-comment-as-an-answer.md
@@ -6,7 +6,7 @@
 
 您不能将评论回复标记为讨论的答案。 您也不能将最小化的评论标记为讨论的答案。
 
-{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.navigate-to-repo-or-org %}
 {% data reusables.discussions.discussions-tab %}
 1. 在讨论列表中，单击要标记为已回答的未回答讨论。 ![未回答的讨论](/assets/images/help/discussions/unanswered-discussion.png)
 1. 在讨论中，找到要标记为答案的评论。
diff --git a/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md b/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md
new file mode 100644
index 0000000000..92670f998b
--- /dev/null
+++ b/translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md
@@ -0,0 +1 @@
+1. On {% data variables.product.product_location %}, navigate to the main page of the repository or organization.
diff --git a/translations/zh-CN/data/reusables/discussions/repository-category-limit.md b/translations/zh-CN/data/reusables/discussions/repository-category-limit.md
index 8a4cc3c90e..b1a8e50e1a 100644
--- a/translations/zh-CN/data/reusables/discussions/repository-category-limit.md
+++ b/translations/zh-CN/data/reusables/discussions/repository-category-limit.md
@@ -1 +1 @@
-每个仓库最多可以有 10 个类别。
+Each repository or organization can have up to 10 categories.
diff --git a/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md
index 4bb59711ca..249f53f9b0 100644
--- a/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md
+++ b/translations/zh-CN/data/reusables/discussions/starting-a-discussion.md
@@ -1,4 +1,5 @@
-{% data reusables.repositories.navigate-to-repo %}
+1. 在
+{% data variables.product.product_location %}, navigate to the main page of the repository or organization where you want to start a discussion.
 {% data reusables.discussions.discussions-tab %}
 1. 单击 **New discussion（新讨论）**。 ![仓库的"Discussions（讨论）"选项卡中的"New discussion（新讨论）"按钮](/assets/images/help/discussions/new-discussion-button.png)
 1. 选择 **Select Category（选择类别）**下拉菜单，然后单击讨论的类别。 !["Select Category（选择类别）"下拉菜单和仓库中可用类别的列表](/assets/images/help/discussions/new-discussion-select-category-dropdown-menu.png)
diff --git a/translations/zh-CN/data/reusables/discussions/starting-a-poll.md b/translations/zh-CN/data/reusables/discussions/starting-a-poll.md
new file mode 100644
index 0000000000..0ecfc99b37
--- /dev/null
+++ b/translations/zh-CN/data/reusables/discussions/starting-a-poll.md
@@ -0,0 +1,9 @@
+{% data reusables.repositories.navigate-to-repo %}
+{% data reusables.discussions.discussions-tab %}
+1. In the list of categories, click **Polls**. ![Screenshot showing "Poll" category](/assets/images/help/discussions/poll-category.png)
+1. On the right, click **Start poll**. ![Screenshot showing the "Start poll" button](/assets/images/help/discussions/start-poll-button.png)
+1. Type a title and optional body for your poll. ![Screenshot showing text fields for title and body](/assets/images/help/discussions/new-poll-title-and-body-fields.png)
+1. Type a question for your poll. ![Screenshot showing text fields for the poll's question](/assets/images/help/discussions/new-poll-question.png)
+1. Type at least two options for your poll. ![Screenshot showing text fields for the poll's options](/assets/images/help/discussions/new-poll-options.png)
+1. Optionally, to add a extra poll options, click **Add an option**. ![Screenshot showing "Add an option" button](/assets/images/help/discussions/new-poll-add-option.png)
+1. Click **Start poll**. ![Screenshot showing the "Start poll" button](/assets/images/help/discussions/new-poll-start-poll-button.png)
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/enterprise-accounts/download-recovery-codes.md b/translations/zh-CN/data/reusables/enterprise-accounts/download-recovery-codes.md
index b8a54b6098..a350cfbc75 100644
--- a/translations/zh-CN/data/reusables/enterprise-accounts/download-recovery-codes.md
+++ b/translations/zh-CN/data/reusables/enterprise-accounts/download-recovery-codes.md
@@ -1,3 +1,3 @@
 1. To ensure you can still access your enterprise in the event that your identity provider is ever unavailable in the future, click **Download**, **Print**, or **Copy** to save your recovery codes. 更多信息请参阅“[下载企业帐户的单点登录恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-saml-single-sign-on-recovery-codes)”。
 
-   ![Screenshot of the buttons to download, print, or copy your recovery codes](/assets/images/help/saml/saml_recovery_code_options.png)
+   ![用于下载、打印或复制恢复代码的按钮屏幕截图](/assets/images/help/saml/saml_recovery_code_options.png)
diff --git a/translations/zh-CN/data/reusables/enterprise/link-to-ghe-trial.md b/translations/zh-CN/data/reusables/enterprise/link-to-ghe-trial.md
new file mode 100644
index 0000000000..c85fcbf7a9
--- /dev/null
+++ b/translations/zh-CN/data/reusables/enterprise/link-to-ghe-trial.md
@@ -0,0 +1 @@
+For more information about how you can try {% data variables.product.prodname_enterprise %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)" and "[Setting up a trial of {% data variables.product.prodname_ghe_server %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server)."
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/download-appliance.md b/translations/zh-CN/data/reusables/enterprise_installation/download-appliance.md
index c06f308925..ee31ea374d 100644
--- a/translations/zh-CN/data/reusables/enterprise_installation/download-appliance.md
+++ b/translations/zh-CN/data/reusables/enterprise_installation/download-appliance.md
@@ -1 +1,5 @@
-1. Click **Get the latest release of {% data variables.product.prodname_ghe_server %}**.
+1. Navigate to the image you want to use for your new instance.
+
+   - Navigate to [Release notes](/admin/release-notes).
+   - In the right sidebar, click the version you want to download.
+   - Click **Download {% data variables.product.prodname_ghe_server %} X.X.X**.
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/download-license.md b/translations/zh-CN/data/reusables/enterprise_installation/download-license.md
index 7549d73841..5dfceec358 100644
--- a/translations/zh-CN/data/reusables/enterprise_installation/download-license.md
+++ b/translations/zh-CN/data/reusables/enterprise_installation/download-license.md
@@ -1 +1 @@
-1. 要下载许可文件，请单击 **Download license**。
+1. 下载许可. 更多信息请参阅“[下载 {% data variables.product.prodname_enterprise %} 的许可](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)”。
diff --git a/translations/zh-CN/data/reusables/enterprise_installation/enterprise-download-procedural.md b/translations/zh-CN/data/reusables/enterprise_installation/enterprise-download-procedural.md
deleted file mode 100644
index cb6b7198bc..0000000000
--- a/translations/zh-CN/data/reusables/enterprise_installation/enterprise-download-procedural.md
+++ /dev/null
@@ -1 +0,0 @@
-1. 导航到 [{% data variables.product.prodname_ghe_server %} 下载页面](https://enterprise.github.com/download)。
diff --git a/translations/zh-CN/data/reusables/gated-features/more-info-org-products.md b/translations/zh-CN/data/reusables/gated-features/more-info-org-products.md
index fc34eae464..5d9a13dda9 100644
--- a/translations/zh-CN/data/reusables/gated-features/more-info-org-products.md
+++ b/translations/zh-CN/data/reusables/gated-features/more-info-org-products.md
@@ -1 +1 @@
-{% ifversion fpt or ghec %}更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/articles/github-s-products)”。{% endif %}
+{% ifversion fpt or ghec %}更多信息请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/get-started/learning-about-github/githubs-products)”。{% endif %}
diff --git a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
index 9b3f1c97e7..01c7ff423c 100644
--- a/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
+++ b/translations/zh-CN/data/reusables/gated-features/secret-scanning.md
@@ -1,4 +1,4 @@
-<!--This reusable describes the GHAS secret scanning feature. For a reusable that also covers the free secret scanning for public repositories on GitHub.com, use `secret-scanning-parter.md`  -->
+<!--This reusable describes the GHAS secret scanning feature. For a reusable that also covers the free secret scanning for public repositories on GitHub.com, use `secret-scanning-partner.md`  -->
 
 {%- ifversion ghec or ghes %}
 {% data variables.product.prodname_secret_scanning_GHAS_caps %} is available for organization-owned repositories in {% data variables.product.product_name %} if your enterprise has a license for {% data variables.product.prodname_GH_advanced_security %}.
diff --git a/translations/zh-CN/data/reusables/organizations/block_users.md b/translations/zh-CN/data/reusables/organizations/block_users.md
index 10efc741f5..60ace89469 100644
--- a/translations/zh-CN/data/reusables/organizations/block_users.md
+++ b/translations/zh-CN/data/reusables/organizations/block_users.md
@@ -1 +1 @@
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
+1. In the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**, then click **Blocked users**.
diff --git a/translations/zh-CN/data/reusables/organizations/moderation-settings.md b/translations/zh-CN/data/reusables/organizations/moderation-settings.md
deleted file mode 100644
index b79fd4132d..0000000000
--- a/translations/zh-CN/data/reusables/organizations/moderation-settings.md
+++ /dev/null
@@ -1 +0,0 @@
-1. In the "Access" section of the sidebar, select **{% octicon "report" aria-label="The report icon" %} Moderation**
diff --git a/translations/zh-CN/data/reusables/organizations/ssh-ca-ghec-only.md b/translations/zh-CN/data/reusables/organizations/ssh-ca-ghec-only.md
new file mode 100644
index 0000000000..e87e7ff46c
--- /dev/null
+++ b/translations/zh-CN/data/reusables/organizations/ssh-ca-ghec-only.md
@@ -0,0 +1,8 @@
+{% ifversion fpt or ghec %}
+{% note %}
+
+**Note:** To use SSH certificate authorities, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md b/translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md
similarity index 80%
rename from translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
rename to translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md
index 0afeb7673c..19afc335a1 100644
--- a/translations/zh-CN/data/reusables/repositories/navigate-to-security-and-analysis.md
+++ b/translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md
@@ -1,5 +1,5 @@
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
-1. In the "Security" section of the sidebar, click **{% octicon "shield-lock" aria-label="The shield-lock icon" %} Security & analysis**.
+1. In the "Security" section of the sidebar, click **{% octicon "codescan" aria-label="code security and analysis icon" %} Code security and analysis**.
 {% else %}
 1. 在左侧边栏中，单击 **Security & analysis（安全和分析）**。 ![仓库设置中的"Security & analysis（安全和分析）"选项卡](/assets/images/help/repository/security-and-analysis-tab.png)
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/rest-reference/dependency-graph/dependency-review.md b/translations/zh-CN/data/reusables/rest-reference/dependency-graph/dependency-review.md
new file mode 100644
index 0000000000..559e0f0243
--- /dev/null
+++ b/translations/zh-CN/data/reusables/rest-reference/dependency-graph/dependency-review.md
@@ -0,0 +1,5 @@
+## 依赖项审查
+
+{% data reusables.dependency-review.dependency-review-api-beta-note %}
+
+The Dependency Review API allows you to understand dependency changes, and the security impact of these changes, before you add them to your environment. You can view the diff of dependencies between two commits of a repository, including vulnerability data for any version updates with known vulnerabilities. For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)."
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md b/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md
index d5a05c7d42..bd82db8481 100644
--- a/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md
+++ b/translations/zh-CN/data/reusables/rest-reference/secret-scanning/secret-scanning.md
@@ -2,7 +2,7 @@
 
 {% data variables.product.prodname_secret_scanning %} API 可让您{% ifversion fpt or ghec or ghes > 3.1 or ghae %}：
 
-- 对仓库启用或禁用 {% data variables.product.prodname_secret_scanning %}。 更多信息请参阅 REST API 文档中的“[仓库](/rest/reference/repos#update-a-repository)”。
+- Enable or disable {% data variables.product.prodname_secret_scanning %}{% if secret-scanning-push-protection %} and push protection{% endif %} for a repository. For more information, see "[Repositories](/rest/reference/repos#update-a-repository)" and expand the "Properties of the `security_and_analysis` object" section in the REST API documentation.
 - Retrieve and update {% data variables.product.prodname_secret_scanning_GHAS %} alerts from a repository. For further details, see the sections below.
 {%- else %} retrieve and update {% data variables.product.prodname_secret_scanning %} alerts from a repository.{% endif %}
 
diff --git a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md
index 5317091c6d..20edaeb3fa 100644
--- a/translations/zh-CN/data/reusables/saml/authorized-creds-info.md
+++ b/translations/zh-CN/data/reusables/saml/authorized-creds-info.md
@@ -1,7 +1,7 @@
 Before you can authorize a personal access token or SSH key, you must have a linked SAML identity. If you're a member of an organization where SAML SSO is enabled, you can create a linked identity by authenticating to your organization with your IdP at least once. 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on)”。
 
 After you authorize a personal access token or SSH key. The token or key will stay authorized until revoked in one of these ways.
-- An organization owner revokes the authorization.
+- An organization or enterprise owner revokes the authorization.
 - You are removed from the organization.
 - The scopes in a personal access token are edited, or the token is regenerated.
 - The personal access token expired as defined during creation.
diff --git a/translations/zh-CN/data/reusables/saml/ghec-only.md b/translations/zh-CN/data/reusables/saml/ghec-only.md
new file mode 100644
index 0000000000..dd0c53e196
--- /dev/null
+++ b/translations/zh-CN/data/reusables/saml/ghec-only.md
@@ -0,0 +1,7 @@
+{% ifversion ghec %}
+{% note %}
+
+**Note:** To use SAML single sign-on, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% endnote %}
+{% endif %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md b/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md
new file mode 100644
index 0000000000..4a28cb364a
--- /dev/null
+++ b/translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** If you have a linked identity for an organization, you can only use authorized personal access tokens and SSH keys with that organization, even if SAML is not enforced. You have a linked identity for an organization if you've ever authenticated via SAML SSO for that organization, unless an organization or enterprise owner later revoked the linked identity. For more information about revoking linked identities, see "[Viewing and managing a member's SAML access to your organization](/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization)" and "[Viewing and managing a user's SAML access to your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise)."
+
+{% endnote %}
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md b/translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md
index aad338382b..61e47fed96 100644
--- a/translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md
+++ b/translations/zh-CN/data/reusables/secret-scanning/partner-program-link.md
@@ -1,5 +1,5 @@
 {% ifversion fpt or ghec %}
 To find out about our partner program, see "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/developers/overview/secret-scanning-partner-program)."
 {% else %}
-To find out about our partner program, see "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/free-pro-team@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation
+To find out about our partner program, see "[{% data variables.product.prodname_secret_scanning_caps %} partner program](/enterprise-cloud@latest/developers/overview/secret-scanning-partner-program)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
 {% endif %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/push-protection-beta.md b/translations/zh-CN/data/reusables/secret-scanning/push-protection-beta.md
new file mode 100644
index 0000000000..ff832ea8eb
--- /dev/null
+++ b/translations/zh-CN/data/reusables/secret-scanning/push-protection-beta.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** {% data variables.product.prodname_secret_scanning_caps %} as a protection push is currently in beta and subject to change. To request access to the beta release, [contact your account management team](https://github.com/enterprise/contact).
+
+{% endnote %}
diff --git a/translations/zh-CN/data/reusables/secret-scanning/push-protection-overview.md b/translations/zh-CN/data/reusables/secret-scanning/push-protection-overview.md
new file mode 100644
index 0000000000..f0532e3e35
--- /dev/null
+++ b/translations/zh-CN/data/reusables/secret-scanning/push-protection-overview.md
@@ -0,0 +1 @@
+When you enable push protection, {% data variables.product.prodname_secret_scanning %} also checks pushes for high-confidence secrets (those identified with a low false positive rate). {% data variables.product.prodname_secret_scanning_caps %} lists any secrets it detects so the author can review the secrets and remove them or, if needed, allow those secrets to be pushed.
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md
new file mode 100644
index 0000000000..0d87d56150
--- /dev/null
+++ b/translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md
@@ -0,0 +1,71 @@
+| Provider                  | 支持的密钥                                              | API slug                                                 |
+| ------------------------- | -------------------------------------------------- | -------------------------------------------------------- |
+| Adafruit IO               | Adafruit IO 密钥                                     | adafruit_io_key                                        |
+| Alibaba Cloud             | Alibaba 云访问密钥 ID                                   | alibaba_cloud_access_key_id                          |
+| Alibaba Cloud             | Alibaba 云访问密钥机密                                    | alibaba_cloud_access_key_secret                      |
+| Amazon                    | Amazon OAuth Client ID                             | amazon_oauth_client_id                                 |
+| Amazon                    | Amazon OAuth Client Secret                         | amazon_oauth_client_secret                             |
+| Amazon Web Services (AWS) | Amazon AWS 访问密钥 ID                                 | aws_access_key_id                                      |
+| Amazon Web Services (AWS) | Amazon AWS 机密访问密钥                                  | aws_secret_access_key                                  |
+| Amazon Web Services (AWS) | Amazon AWS Session Token                           | aws_session_token                                      |
+| Amazon Web Services (AWS) | Amazon AWS Temporary Access Key ID                 | aws_temporary_access_key_id                          |
+| Asana                     | Asana 个人访问令牌                                       | asana_personal_access_token                            |
+| Atlassian                 | Bitbucket 服务器个人访问令牌                                | bitbucket_server_personal_access_token               |
+| Azure                     | Azure Active Directory 应用程序密钥                      | azure_active_directory_application_secret            |
+| Azure                     | Azure Cache for Redis Access Key                   | azure_cache_for_redis_access_key                     |
+| Azure                     | Azure DevOps 个人访问令牌                                | azure_devops_personal_access_token                   |
+| Checkout.com              | Checkout.com 生产密钥                                  | checkout_production_secret_key                         |
+| Clojars                   | Clojars 部署令牌                                       | clojars_deploy_token                                   |
+| Databricks                | Databricks 访问令牌                                    | databricks_access_token                                |
+| Discord                   | Discord 自动程序令牌                                     | discord_bot_token                                      |
+| Doppler                   | Doppler 个人令牌                                       | doppler_personal_token                                 |
+| Doppler                   | Doppler 服务令牌                                       | doppler_service_token                                  |
+| Doppler                   | Doppler CLI 令牌                                     | doppler_cli_token                                      |
+| Doppler                   | Doppler SCIM 令牌                                    | doppler_scim_token                                     |
+| Doppler                   | Doppler Audit Token                                | doppler_audit_token                                    |
+| Dropbox                   | Dropbox 短暂访问令牌                                     | dropbox_short_lived_access_token                     |
+| Duffel                    | Duffel Live Access Token                           | duffel_live_access_token                               |
+| EasyPost                  | EasyPost Production API Key                        | easypost_production_api_key                            |
+| Flutterwave               | Flutterwave Live API Secret Key                    | flutterwave_live_api_secret_key                      |
+| Fullstory                 | FullStory API Key                                  | fullstory_api_key                                      |
+| GitHub                    | GitHub 个人访问令牌                                      | github_personal_access_token                           |
+| GitHub                    | GitHub OAuth 访问令牌                                  | github_oauth_access_token                              |
+| GitHub                    | GitHub 刷新令牌                                        | github_refresh_token                                   |
+| GitHub                    | GitHub App 安装访问令牌                                  | github_app_installation_access_token                 |
+| GitHub                    | GitHub SSH 私钥                                      | github_ssh_private_key                                 |
+| Google                    | Google Cloud Storage Access Key Secret             | google_cloud_storage_access_key_secret               |
+| Google                    | Google Cloud Storage Service Account Access Key ID | google_cloud_storage_service_account_access_key_id |
+| Google                    | Google Cloud Storage User Access Key ID            | google_cloud_storage_user_access_key_id            |
+| Grafana                   | Grafana API 密钥                                     | grafana_api_key                                        |
+| Hubspot                   | Hubspot API 密钥                                     | hubspot_api_key                                        |
+| Intercom                  | Intercom 访问令牌                                      | intercom_access_token                                  |
+| Ionic                     | Ionic 个人访问令牌                                       | ionic_personal_access_token                            |
+| Ionic                     | Ionic 刷新令牌                                         | ionic_refresh_token                                    |
+| 线性                        | 线性 API 密钥                                          | linear_api_key                                         |
+| 线性                        | 线性 OAuth 访问令牌                                      | linear_oauth_access_token                              |
+| Midtrans                  | Midtrans Production Server Key                     | midtrans_production_server_key                         |
+| New Relic                 | New Relic Personal API Key                         | new_relic_personal_api_key                           |
+| New Relic                 | New Relic REST API Key                             | new_relic_rest_api_key                               |
+| New Relic                 | New Relic Insights Query Key                       | new_relic_insights_query_key                         |
+| npm                       | npm 访问令牌                                           | npm_access_token                                       |
+| NuGet                     | NuGet API 密钥                                       | nuget_api_key                                          |
+| Onfido                    | Onfido Live API Token                              | onfido_live_api_token                                  |
+| OpenAI                    | OpenAI API 密钥                                      | openai_api_key                                         |
+| PlanetScale               | PlanetScale Database Password                      | planetscale_database_password                          |
+| PlanetScale               | PlanetScale OAuth Token                            | planetscale_oauth_token                                |
+| PlanetScale               | PlanetScale Service Token                          | planetscale_service_token                              |
+| Postman                   | Postman API 密钥                                     | postman_api_key                                        |
+| Proctorio                 | Proctorio 密钥                                       | proctorio_secret_key                                   |
+| Samsara                   | Samsara API 令牌                                     | samsara_api_token                                      |
+| Samsara                   | Samsara OAuth 访问令牌                                 | samsara_oauth_access_token                             |
+| SendGrid                  | SendGrid API Key                                   | sendgrid_api_key                                       |
+| Sendinblue                | Sendinblue API Key                                 | sendinblue_api_key                                     |
+| Sendinblue                | Sendinblue SMTP Key                                | sendinblue_smtp_key                                    |
+| Shippo                    | Shippo Live API Token                              | shippo_live_api_token                                  |
+| Shopify                   | Shopify App 共享密钥                                   | shopify_app_shared_secret                              |
+| Shopify                   | Shopify 访问令牌                                       | shopify_access_token                                   |
+| Slack                     | Slack API 令牌                                       | slack_api_token                                        |
+| Stripe                    | Stripe Live API 密钥                                 | stripe_live_secret_key                                 |
+| Tencent Cloud             | 腾讯云密钥 ID                                           | tencent_cloud_secret_id                                |
+| Typeform                  | Typeform Personal Access Token                     | typeform_personal_access_token                         |
+| WorkOS                    | WorkOS Production API Key                          | workos_production_api_key                              |
\ 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
index ccba6bad40..df79b7fc6a 100644
--- 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
@@ -2,6 +2,6 @@
 
 **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)."
+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). 对全局通告的编辑不会更改或影响通告在存储库中的显示方式。 更多信息请参阅“[编辑 {% 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 %}
diff --git a/translations/zh-CN/data/reusables/support/view-open-tickets.md b/translations/zh-CN/data/reusables/support/view-open-tickets.md
index 55acd6c5f0..f94b0666a8 100644
--- a/translations/zh-CN/data/reusables/support/view-open-tickets.md
+++ b/translations/zh-CN/data/reusables/support/view-open-tickets.md
@@ -1,4 +1,6 @@
 1. Navigate to the [GitHub Support Portal](https://support.github.com/).
 1. In the header, click **My Tickets**. ![Screenshot showing "My Tickets" link in the GitHub Support Portal header.](/assets/images/help/support/my-tickets-header.png)
-1. Optionally, to view tickets associated with an organization or enterprise account, select the **My Tickets** drop-down menu and click the name of the organization or enterprise account. ![Screenshot of the "My Tickets" dropdown menu.](/assets/images/help/support/ticket-context.png)
+1. Optionally, to view tickets associated with an organization or enterprise account, select the **My Tickets** drop-down menu and click the name of the organization or enterprise account.
+
+  You must have an enterprise support entitlement to view tickets associated with an organization or enterprise account. 更多信息请参阅“[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。 ![Screenshot of the "My Tickets" dropdown menu.](/assets/images/help/support/ticket-context.png)
 1. In the list of tickets, click the subject of the ticket you want to view. ![Screenshot showing a list of support tickets with the subject highlighted.](/assets/images/help/support/my-tickets-list.png)
diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
index f248fca69a..8e3f428e59 100644
--- a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
+++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_event_short_desc.md
@@ -1 +1 @@
-与仓库中的密码扫描警报相关的活动。 活动类型在有效负载对象的操作属性中指定。 For more information, see the "[secret scanning API](rest/reference/secret-scanning)."
+与仓库中的密码扫描警报相关的活动。 活动类型在有效负载对象的操作属性中指定。 For more information, see the "[secret scanning API](/rest/reference/secret-scanning)."
diff --git a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
index a6617a5c3b..ae32db92f9 100644
--- a/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
+++ b/translations/zh-CN/data/reusables/webhooks/secret_scanning_alert_location_event_short_desc.md
@@ -1 +1 @@
-Activity related to secret scanning alert locations in a repository. 活动类型在有效负载对象的操作属性中指定。 For more information, see the "[secret scanning](rest/reference/secret-scanning)" REST API.
+Activity related to secret scanning alert locations in a repository. 活动类型在有效负载对象的操作属性中指定。 For more information, see the "[secret scanning](/rest/reference/secret-scanning)" REST API.
diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml
index 6da27d368a..791e3eab42 100644
--- a/translations/zh-CN/data/variables/product.yml
+++ b/translations/zh-CN/data/variables/product.yml
@@ -37,7 +37,8 @@ prodname_unified_search: '统一搜索'
 #GitHub Education
 prodname_education: 'GitHub Education'
 prodname_education_community: '教育社区'
-prodname_education_community_with_url: '[GitHub Education 社区](https://education.github.community)'
+prodname_education_community_with_url: '[GitHub Education 社区](https://github.com/orgs/github-community/discussions/categories/github-education)'
+prodname_education_forum_link: 'https://github.com/orgs/github-community/discussions/categories/github-education'
 prodname_classroom: 'GitHub 课堂'
 prodname_classroom_with_url: '[GitHub Classroom](https://classroom.github.com/login)'
 prodname_campus_program: 'GitHub 校园计划'
@@ -100,7 +101,7 @@ prodname_advanced_security: 'Advanced Security'
 #Codespaces
 prodname_codespaces: 'Codespaces'
 prodname_github_codespaces: 'GitHub Codespaces'
-prodname_serverless: 'web-based editor'
+prodname_serverless: '基于 Web 的编辑器'
 #GitHub resources: blog, jobs, Learning Lab
 prodname_gcf: 'GitHub Community Support'
 prodname_blog: 'GitHub 博客'