diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv
index c22481fd30..467467a974 100644
--- a/translations/log/msft-cn-resets.csv
+++ b/translations/log/msft-cn-resets.csv
@@ -1,1057 +1 @@
file,reason
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/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.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,file deleted because it no longer exists in main
-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,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md,file deleted because it no longer exists in main
-translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/deploying-github-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/overview-of-github-advanced-security-deployment.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-ssl-errors.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/configuring-authentication-and-provisioning-with-your-identity-provider/index.md,file deleted because it no longer exists in main
-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,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/managing-team-memberships-with-identity-provider-groups.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-xenserver.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-advanced-security-in-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-project-board-policies-in-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/managing-unowned-organizations-in-your-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-new-gpg-key-to-your-github-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/updating-an-expired-gpg-key.md,file deleted because it no longer exists in main
-translations/zh-CN/content/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-github-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage.md,file deleted because it no longer exists in main
-translations/zh-CN/content/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/dependabot/dependabot-alerts/editing-security-advisories-in-the-github-advisory-database.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/about-github-security-advisories-for-repositories.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/best-practices-for-writing-repository-security-advisories.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/creating-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/editing-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/permission-levels-for-repository-security-advisories.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/publishing-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/removing-a-collaborator-from-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/repository-security-advisories/withdrawing-a-repository-security-advisory.md,file deleted because it no longer exists in main
-translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/allowing-your-codespace-to-access-a-private-image-registry.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/disaster-recovery-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/security-in-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/understanding-billing-for-github-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/codespaces-reference/using-github-copilot-in-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-codespaces-for-your-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-editor-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/renaming-a-codespace.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/the-codespace-lifecycle.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-for-pull-requests.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-codespaces-in-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-billing-for-github-codespaces-in-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/reviewing-your-organizations-audit-logs-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/troubleshooting/codespaces-logs.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-codespaces-clients.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-port-forwarding-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/communities/moderating-comments-and-conversations/limiting-interactions-for-your-user-account.md,file deleted because it no longer exists in main
-translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/changing-a-remotes-url-from-github-desktop.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-at-your-educational-institution/about-campus-advisors.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-community-exchange.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/about-github-education-for-students.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/apply-for-a-student-developer-pack.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,file deleted because it no longer exists in main
-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,file deleted because it no longer exists in main
-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,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-in-your-classroom-and-research/why-wasnt-my-application-for-an-educator-or-researcher-discount-approved.md,file deleted because it no longer exists in main
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-to-github-classroom.md,file deleted because it no longer exists in main
-translations/zh-CN/content/github/copilot/about-github-copilot-telemetry.md,file deleted because it no longer exists in main
-translations/zh-CN/content/github/copilot/github-copilot-telemetry-terms.md,file deleted because it no longer exists in main
-translations/zh-CN/content/github/copilot/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/github/copilot/research-recitation.md,file deleted because it no longer exists in main
-translations/zh-CN/content/github/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-date-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-iteration-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-single-select-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/about-text-and-number-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/deleting-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/planning-and-tracking-with-projects/understanding-field-types/renaming-fields.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/tracking-your-work-with-issues/about-task-lists.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/about-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/automating-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/best-practices-for-managing-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/creating-a-project.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/customizing-your-project-views.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/filtering-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-iterations.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/migrating-your-project.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/quickstart.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-insights-with-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/issues/trying-out-the-new-projects-experience/using-the-api-to-manage-projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/adding-github-app-managers-in-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-apps/removing-github-app-managers-from-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/canceling-an-invitation-to-become-an-outside-collaborator-in-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-organization-member-to-an-outside-collaborator.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/converting-an-outside-collaborator-to-an-organization-member.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/reinstating-a-former-outside-collaborators-access-to-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/removing-an-outside-collaborator-from-an-organization-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/setting-base-permissions-for-an-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/about-oauth-app-access-restrictions.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/approving-oauth-apps-for-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/content/organizations/restricting-access-to-your-organizations-data/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md,file deleted because it no longer exists in main
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/configuring-a-remote-for-a-fork.md,file deleted because it no longer exists in main
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/working-with-forks/merging-an-upstream-repository-into-your-fork.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/guides/traversing-with-pagination.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/actions.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/activity.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/apps.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/billing.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/branches.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/checks.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/code-scanning.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/codes-of-conduct.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/collaborators.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/commits.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/dependabot.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/dependency-graph.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/deployments.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/emojis.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/enterprise-admin.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/gists.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/git.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/gitignore.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/index.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/interactions.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/issues.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/licenses.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/markdown.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/meta.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/metrics.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/migrations.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/oauth-authorizations.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/orgs.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/packages.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/pages.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/projects.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/pulls.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/rate-limit.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/reactions.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/releases.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/repos.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/scim.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/search.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/secret-scanning.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/teams.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/users.md,file deleted because it no longer exists in main
-translations/zh-CN/content/rest/reference/webhooks.md,file deleted because it no longer exists in main
-translations/zh-CN/content/site-policy/privacy-policies/github-data-protection-agreement.md,file deleted because it no longer exists in main
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
-translations/zh-CN/data/features/ip-allow-list-address-check.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/features/security-overview-views.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/glossaries/internal.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/graphql/ghes-3.2/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/0.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/1.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/17.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/19.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/2.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/20.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/21.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/22.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/23.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/24.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/3.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/4.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/6.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/7.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/8.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-20/9.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/0.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/1.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/15.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/19.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/2.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/20.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/21.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/22.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/23.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/3.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/4.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/7.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/8.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-21/9.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/15.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/17.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/19.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/20.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/21.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/4.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/2-22/6.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc1.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/0-rc2.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/15.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/17.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/19.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/20.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/21.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/22.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/23.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/24.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/25.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/4.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/6.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/7.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/8.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-0/9.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/0-rc1.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/15.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/17.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/19.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/20.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/21.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/22.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/3.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/6.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/7.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/8.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-1/9.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/1.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/10.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/11.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/12.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/13.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/14.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/15.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/16.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/18.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/2.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/3.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/4.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/5.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/6.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/7.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/8.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/release-notes/enterprise-server/3-2/9.yml,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/enterprise-s3-support-warning.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/hardware-requirements-3.6.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/minio-gateways-removal.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/reusable-workflows-ghes-beta.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/self-hosted-runner-create-group.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/self-hosted-runner-groups-add-to-enterprise-first-steps.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/billing/about-invoices-for-enterprises.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/billing/per-user-pricing-reference.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/about-billing-for-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/about-personalization.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/apply-devcontainer-changes.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/availability.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/beta-functionality-limited.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds-default.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds-reducing.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/billing-for-prebuilds.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/codespaces-api-beta-note.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/codespaces-billing.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/concurrent-codespace-limit.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/prebuilds-beta-note.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/prebuilds-not-available.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/review-pr.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/unsupported-repos.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/codespaces/vscode-settings-order.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dependabot/beta-security-and-version-updates-onboarding.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dependabot/create-dependabot-yml.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dependabot/dependabot-secrets-button.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dependency-review/beta.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dependency-review/dependency-review-api-beta-note.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/desktop/paste-email-git-config.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dotcom_billing/codespaces-minutes.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dotcom_billing/monthly-spending-limit-codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/dotcom_billing/pricing_calculator/pricing_cal_codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/education/upgrade-organization.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/education/upgrade-page.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise-accounts/oidc-beta-notice.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise-accounts/repository-visibility-policy.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise/upgrade-ghes-for-actions.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/enterprise_management_console/username_normalization_sample.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/gated-features/advanced-security.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/gated-features/codespaces.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/gated-features/discussions.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/gated-features/security-center.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/getting-started/learning-lab-enterprise.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/getting-started/learning-lab.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/organizations/organizations_include.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_container_registry.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/enterprise-admin/audit-log.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/enterprise-admin/billing.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/interactions/interactions.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/issues/assignees.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/issues/labels.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/issues/milestones.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/metrics/community.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/orgs/members.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/orgs/outside-collaborators.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/projects/cards.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/projects/collaborators.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/projects/columns.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/pulls/review-requests.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/repos/forks.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/repos/lfs.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/users/blocking.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/users/emails.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/users/followers.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/users/keys.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/rest-reference/webhooks/repos.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/security-center/beta.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/security-center/permissions.md,file deleted because it no longer exists in main
-translations/zh-CN/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,broken liquid tags
-translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,broken liquid tags
-translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
-translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
-translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/about-deployments/deploying-with-github-actions.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-docker-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-java-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-net-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-nodejs-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-php-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-python-to-azure-app-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-kubernetes-service.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-azure/deploying-to-azure-static-web-app.md,broken liquid tags
-translations/zh-CN/content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-google-kubernetes-engine.md,broken liquid tags
-translations/zh-CN/content/actions/examples/using-concurrency-expressions-and-a-test-matrix.md,broken liquid tags
-translations/zh-CN/content/actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service.md,broken liquid tags
-translations/zh-CN/content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md,broken liquid tags
-translations/zh-CN/content/actions/hosting-your-own-runners/removing-self-hosted-runners.md,broken liquid tags
-translations/zh-CN/content/actions/hosting-your-own-runners/running-scripts-before-or-after-a-job.md,broken liquid tags
-translations/zh-CN/content/actions/learn-github-actions/expressions.md,broken liquid tags
-translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-actions.md,broken liquid tags
-translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,broken liquid tags
-translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
-translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
-translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
-translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,broken liquid tags
-translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
-translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,broken liquid tags
-translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
-translations/zh-CN/content/actions/quickstart.md,broken liquid tags
-translations/zh-CN/content/actions/security-guides/security-hardening-for-github-actions.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/about-workflows.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/events-that-trigger-workflows.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md,broken liquid tags
-translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.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/enabling-github-advanced-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/enabling-automatic-user-license-sync-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
-translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
-translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-azure-blob-storage.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,broken liquid tags
-translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/index.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-azure-ad.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-authentication-and-provisioning-for-your-enterprise-using-okta.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-with-scim-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
-translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-aws.md,broken liquid tags
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,broken liquid tags
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,broken liquid tags
-translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,broken liquid tags
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/overview/about-data-residency.md,broken liquid tags
-translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
-translations/zh-CN/content/admin/overview/system-overview.md,broken liquid tags
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
-translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
-translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
-translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
-translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,broken liquid tags
-translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,broken liquid tags
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,broken liquid tags
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md,broken liquid tags
-translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
-translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,broken liquid tags
-translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,broken liquid tags
-translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
-translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
-translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
-translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-github-copilot/index.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/managing-invoices-for-your-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
-translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
-translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,broken liquid tags
-translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
-translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md,broken liquid tags
-translations/zh-CN/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.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/configuring-secret-scanning-for-your-repositories.md,broken liquid tags
-translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.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/end-to-end-supply-chain/securing-code.md,broken liquid tags
-translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md,broken liquid tags
-translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md,broken liquid tags
-translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
-translations/zh-CN/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
-translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,broken liquid tags
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
-translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
-translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
-translations/zh-CN/content/copilot/configuring-github-copilot/configuring-github-copilot-in-visual-studio-code.md,broken liquid tags
-translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags
-translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags
-translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
-translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags
-translations/zh-CN/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags
-translations/zh-CN/content/copilot/quickstart.md,broken liquid tags
-translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
-translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
-translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
-translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,broken liquid tags
-translations/zh-CN/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,broken liquid tags
-translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
-translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
-translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
-translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
-translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
-translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
-translations/zh-CN/content/developers/overview/about-githubs-apis.md,broken liquid tags
-translations/zh-CN/content/developers/overview/managing-deploy-keys.md,broken liquid tags
-translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
-translations/zh-CN/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
-translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
-translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
-translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags
-translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags
-translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
-translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
-translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
-translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
-translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
-translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
-translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.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/getting-started-with-git/why-is-git-always-asking-for-my-password.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/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
-translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
-translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
-translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
-translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
-translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
-translations/zh-CN/content/get-started/quickstart/be-social.md,broken liquid tags
-translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags
-translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
-translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,broken liquid tags
-translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags
-translations/zh-CN/content/get-started/using-github/github-mobile.md,broken liquid tags
-translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
-translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags
-translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,broken liquid tags
-translations/zh-CN/content/github-cli/github-cli/quickstart.md,broken liquid tags
-translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md,broken liquid tags
-translations/zh-CN/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
-translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
-translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
-translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
-translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/integrating-jira-with-your-organization-project-board.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,broken liquid tags
-translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
-translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/about-permissions-for-github-packages.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/connecting-a-repository-to-a-package.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/installing-a-package.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,broken liquid tags
-translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md,broken liquid tags
-translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-docker-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-gradle-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md,broken liquid tags
-translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-nuget-registry.md,broken liquid tags
-translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
-translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
-translations/zh-CN/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,broken liquid tags
-translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,broken liquid tags
-translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,broken liquid tags
-translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,broken liquid tags
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
-translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,broken liquid tags
-translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md,broken liquid tags
-translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule.md,broken liquid tags
-translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,broken liquid tags
-translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,broken liquid tags
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
-translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md,broken liquid tags
-translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-releases.md,broken liquid tags
-translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,broken liquid tags
-translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
-translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
-translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
-translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
-translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags
-translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
-translations/zh-CN/content/rest/codespaces/machines.md,broken liquid tags
-translations/zh-CN/content/rest/codespaces/repository-secrets.md,broken liquid tags
-translations/zh-CN/content/rest/codespaces/secrets.md,broken liquid tags
-translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/announcement.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/billing.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/global-webhooks.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/index.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/ldap.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/license.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/management-console.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/org-pre-receive-hooks.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/orgs.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/pre-receive-environments.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/pre-receive-hooks.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/repo-pre-receive-hooks.md,broken liquid tags
-translations/zh-CN/content/rest/enterprise-admin/users.md,broken liquid tags
-translations/zh-CN/content/rest/guides/working-with-comments.md,broken liquid tags
-translations/zh-CN/content/rest/migrations/source-imports.md,broken liquid tags
-translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags
-translations/zh-CN/content/rest/packages.md,broken liquid tags
-translations/zh-CN/content/rest/pages.md,broken liquid tags
-translations/zh-CN/content/rest/projects/cards.md,broken liquid tags
-translations/zh-CN/content/rest/projects/collaborators.md,broken liquid tags
-translations/zh-CN/content/rest/projects/columns.md,broken liquid tags
-translations/zh-CN/content/rest/projects/index.md,broken liquid tags
-translations/zh-CN/content/rest/projects/projects.md,broken liquid tags
-translations/zh-CN/content/rest/reactions.md,broken liquid tags
-translations/zh-CN/content/rest/scim.md,broken liquid tags
-translations/zh-CN/content/rest/teams/team-sync.md,broken liquid tags
-translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,broken liquid tags
-translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
-translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
-translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
-translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
-translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md,broken liquid tags
-translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,broken liquid tags
-translations/zh-CN/data/glossaries/external.yml,broken liquid tags
-translations/zh-CN/data/learning-tracks/actions.yml,broken liquid tags
-translations/zh-CN/data/learning-tracks/admin.yml,broken liquid tags
-translations/zh-CN/data/learning-tracks/code-security.yml,broken liquid tags
-translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-3/0.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-3/12.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/1.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/2.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/3.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/4.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/5.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/6.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/7.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-4/8.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
-translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
-translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
-translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/cache-default-size.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/create-runner-group.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/disabling-github-actions.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/github-connect-resolution.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/reusable-workflows.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/self-hosted-runner-management-permissions-required.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/self-hosted-runner-ports-protocols.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-general.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runners.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md,broken liquid tags
-translations/zh-CN/data/reusables/actions/workflow-template-overview.md,broken liquid tags
-translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
-translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
-translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,broken liquid tags
-translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protection-org.md,broken liquid tags
-translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
-translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,broken liquid tags
-translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,broken liquid tags
-translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
-translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
-translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
-translations/zh-CN/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
-translations/zh-CN/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
-translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
-translations/zh-CN/data/reusables/codespaces/secrets-on-start.md,broken liquid tags
-translations/zh-CN/data/reusables/command_line/provide-an-access-token.md,broken liquid tags
-translations/zh-CN/data/reusables/copilot/copilot-prerequisites.md,broken liquid tags
-translations/zh-CN/data/reusables/copilot/dotcom-settings.md,broken liquid tags
-translations/zh-CN/data/reusables/copilot/install-copilot-in-neovim.md,broken liquid tags
-translations/zh-CN/data/reusables/dependabot/default-dependencies-allow-ignore.md,broken liquid tags
-translations/zh-CN/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,broken liquid tags
-translations/zh-CN/data/reusables/dependency-review/action-enterprise.md,broken liquid tags
-translations/zh-CN/data/reusables/dependency-review/dependency-review-action-beta-note.md,broken liquid tags
-translations/zh-CN/data/reusables/dependency-review/dependency-review-action-overview.md,broken liquid tags
-translations/zh-CN/data/reusables/desktop/get-an-account.md,broken liquid tags
-translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
-translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
-translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
-translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
-translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-gist.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/repo-creation-policy.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise/apply-configuration.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise/rate_limit.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise/test-in-staging.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_installation/download-package.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/hotpatching-explanation.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
-translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
-translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/copilot-billing.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/copilot.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,broken liquid tags
-translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/actions.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/creating-organizations.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
-translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
-translations/zh-CN/data/reusables/git/git-push.md,broken liquid tags
-translations/zh-CN/data/reusables/large_files/storage_assets_location.md,broken liquid tags
-translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
-translations/zh-CN/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
-translations/zh-CN/data/reusables/notifications/shared_state.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/billing_plans.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/member-privileges.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/navigate-to-org.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/repository-defaults.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/security-and-analysis.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/security.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/teams_sidebar.md,broken liquid tags
-translations/zh-CN/data/reusables/organizations/verified-domains.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/authenticate_with_pat_for_v2_registry.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/no-graphql-to-delete-packages.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/packages-billing.md,broken liquid tags
-translations/zh-CN/data/reusables/package_registry/required-scopes.md,broken liquid tags
-translations/zh-CN/data/reusables/pages/build-failure-email-server.md,broken liquid tags
-translations/zh-CN/data/reusables/pages/emu-org-only.md,broken liquid tags
-translations/zh-CN/data/reusables/pages/sidebar-pages.md,broken liquid tags
-translations/zh-CN/data/reusables/pages/visit-site.md,broken liquid tags
-translations/zh-CN/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
-translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
-translations/zh-CN/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/changed-files.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/deploy-keys.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/repository-branches.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/sidebar-notifications.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/suggest-changes.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/tracks-vulnerabilities.md,broken liquid tags
-translations/zh-CN/data/reusables/repositories/you-can-fork.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/about-linked-identities.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/authorized-creds-info.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
-translations/zh-CN/data/reusables/saml/saml-ghes-account-revocation.md,broken liquid tags
-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/scim/enterprise-account-scim.md,broken liquid tags
-translations/zh-CN/data/reusables/scim/supported-idps.md,broken liquid tags
-translations/zh-CN/data/reusables/search/syntax_tips.md,broken liquid tags
-translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
-translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
-translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
-translations/zh-CN/data/reusables/ssh/about-ssh.md,broken liquid tags
-translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
-translations/zh-CN/data/reusables/support/help_resources.md,broken liquid tags
-translations/zh-CN/data/reusables/support/submit-a-ticket.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/access_applications.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/account_settings.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/appearance-settings.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/developer_settings.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/emails.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/organizations.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/personal_access_tokens.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/removes-personal-access-tokens.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/repo-tab.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/saved_replies.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/security-analysis.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/security.md,broken liquid tags
-translations/zh-CN/data/reusables/user-settings/ssh.md,broken liquid tags
-translations/zh-CN/data/reusables/webhooks/repository_vulnerability_alert_short_desc.md,broken liquid tags
-translations/zh-CN/data/reusables/webhooks/workflow_run_properties.md,broken liquid tags
-translations/zh-CN/data/ui.yml,broken liquid tags
-translations/zh-CN/data/variables/product.yml,broken liquid tags
-translations/zh-CN/data/variables/projects.yml,broken liquid tags
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
index 3b470c37a4..8238366d3b 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -1,6 +1,6 @@
---
-title: Managing your subscriptions
-intro: 'To help you manage your notifications efficiently, there are several ways to unsubscribe.'
+title: 管理订阅
+intro: 为帮助您有效地管理通知,提供了多种取消订阅的方法。
versions:
fpt: '*'
ghes: '*'
@@ -12,73 +12,79 @@ redirect_from:
- /github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions
- /github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions
shortTitle: Manage your subscriptions
+ms.openlocfilehash: 750a3a9ad87ff9aa709b84a98f548d85d53072ee
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145087363'
---
-To help you understand your subscriptions and decide whether to unsubscribe, see "[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)."
+为了帮助了解订阅并决定是否取消订阅,请参阅“[查看订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions)”。
{% note %}
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+注意:可以选择忽略存储库,而不是取消订阅。 如果忽略仓库,将不会收到任何通知。 不建议忽略存储库,因为如果你被 @mentioned,你将不会收到通知。 {% ifversion fpt or ghec %} 如果遇到滥用行为并想要忽略存储库,请联系 {% data variables.contact.contact_support %} 以获取帮助。 {% data reusables.policies.abuse %}{% endif %}
{% endnote %}
-## Choosing how to unsubscribe
+## 选择如何取消订阅
-To unwatch (or unsubscribe from) repositories quickly, navigate to [github.com/watching](https://github.com/watching) to see all the repositories you're following. For more information, see "[Unwatching repositories](#unwatching-repositories)."
+若要快速取消关注(或取消订阅)存储库,请导航至 [github.com/watching](https://github.com/watching)查看你所关注的所有存储库。 有关详细信息,请参阅“[取消关注存储库](#unwatching-repositories)”。
-To unsubscribe from multiple notifications at the same time, you can unsubscribe using your inbox or on the subscriptions page. Both of these options offer more context about your subscriptions than the "Watched repositories" page.
+要同时取消订阅多个通知,您可以使用收件箱或订阅页面上取消订阅。 相比“Watched repositories(已关注仓库)”页面,这两个选项可提供有关您的订阅的更多上下文。
-### Benefits of unsubscribing from your inbox
+### 从收件箱中取消订阅的优点
-When you unsubscribe from notifications in your inbox, you have several other triaging options and can filter your notifications by custom filters and discussion types. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)."
+在收件箱中取消订阅通知时,您还有其他一些分类选项,并且可以按自定义过滤器和讨论类型来过滤通知。 有关详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。
-### Benefits of unsubscribing from the subscriptions page
+### 从订阅页面取消订阅的优点
-When you unsubscribe from notifications on the subscriptions page, you can see more of the notifications you're subscribed to and sort them by "Most recently subscribed" or "Least recently subscribed".
+在订阅页面上取消订阅通知时,您可以查看更多已订阅的通知,并且可以按“最多最近订阅”或“最少最近订阅”对它们进行排序。
-The subscriptions page shows you all of the notifications that you're currently subscribed to, including notifications that you have marked as **Done** in your inbox.
+订阅页将显示当前订阅的所有通知,包括在收件箱中标记为“完成”的通知。
-You can only filter your subscriptions by repository and the reason you're receiving the notification.
+您只能按仓库和接收通知的原因过滤订阅。
-## Unsubscribing from notifications in your inbox
+## 在收件箱中取消订阅通知
-When you unsubscribe from notifications in your inbox, they will automatically disappear from your inbox.
+当您取消订阅收件箱中的通知时,它们将自动从您的收件箱中消失。
{% data reusables.notifications.access_notifications %}
-1. From the notifications inbox, select the notifications you want to unsubscribe to.
-2. Click **Unsubscribe.**
- 
+1. 从通知收件箱中选择您想要取消订阅的通知。
+2. 单击“取消订阅”。
+ 
-## Unsubscribing from notifications on the subscriptions page
+## 从订阅页面取消订阅通知
{% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Subscriptions**.
- 
+1. 在左侧边栏存储库列表下的“管理通知”下拉菜单中单击“订阅”。
+ 
-2. Select the notifications you want to unsubscribe to. In the top right, click **Unsubscribe.**
- 
+2. 选择要取消订阅的通知。 单击右上角的“取消订阅”。
+ 
-## Unwatching repositories
+## 取消关注仓库
-When you unwatch a repository, you unsubscribe from future updates from that repository unless you participate in a conversation or are @mentioned.
+如果取消关注存储库,将取消订阅该存储库的未来更新,除非参与对话或被 @mentioned。
{% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down to click **Watched repositories**.
+1. 在左侧边栏存储库列表下的“管理通知”下拉菜单中单击“已关注的存储库”。
- 
+ 
-2. On the watched repositories page, after you've evaluated the repositories you're watching, choose whether to:
+2. 在关注的仓库页面上,评估您关注的仓库后,选择是否:
- - Unwatch a repository
- - Ignore all notifications for a repository
- - If enabled, customize the types of event you receive notifications for ({% data reusables.notifications-v2.custom-notification-types %})
+ - 取消关注仓库
+ - 忽略某仓库的所有通知
+ - 如有启用,请自定义接收通知的事件类型({% data reusables.notifications-v2.custom-notification-types %})
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
-1. Optionally, to unsubscribe from all repositories owned by a given user or organization, select the **Unwatch all** dropdown and click the organization whose repositories you'd like to unsubscribe from. The button to unwatch all repositories is only available if you are watching all activity or custom notifications on over 10 repositories.
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5819 %}
+1. (可选)要取消订阅指定用户或组织拥有的所有存储库,请选择“全部取消关注”下拉列表,然后单击要取消订阅其存储库的组织 ****。 取消关注所有存储库的按钮仅在您正在关注超过 10 个存储库上的所有活动或自定义通知时才可用。
- 
+ 
- - Click **Unwatch** to confirm that you want to unwatch the repositories owned by the selected user or organization, or click **Cancel** to cancel.
+ - 单击“取消关注”以确认要取消关注所选用户或组织拥有的存储库,或单击“取消”以取消关注 。
- 
+ 
{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
index 8d2d85b673..60de88d807 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md
@@ -1,6 +1,6 @@
---
-title: Viewing your subscriptions
-intro: 'To understand where your notifications are coming from and your notifications volume, we recommend reviewing your subscriptions and watched repositories regularly.'
+title: 查看订阅
+intro: 为了解通知来自何处以及通知量,建议定期查看订阅和关注的仓库。
redirect_from:
- /articles/subscribing-to-conversations
- /articles/unsubscribing-from-conversations
@@ -24,61 +24,63 @@ versions:
topics:
- Notifications
shortTitle: View subscriptions
+ms.openlocfilehash: 34faad79004d34f5beb14e8992b9aff4e6a3ab39
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '145099202'
---
-You receive notifications for your subscriptions of ongoing activity on {% data variables.product.product_name %}. There are many reasons you can be subscribed to a conversation. For more information, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)."
+接收 {% data variables.product.product_name %} 上长期活动的订阅通知。 有很多原因可能导致您订阅对话。 有关详细信息,请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notifications-and-subscriptions)”。
-We recommend auditing and unsubscribing from your subscriptions as a part of a healthy notifications workflow. For more information about your options for unsubscribing, see "[Managing subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+我们建议将审核订阅和取消订阅作为健康通知工作流程的一部分。 有关取消订阅的选项的详细信息,请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
-## Diagnosing why you receive too many notifications
+## 诊断收到太多通知的原因
-When your inbox has too many notifications to manage, consider whether you have oversubscribed or how you can change your notification settings to reduce the subscriptions you have and the types of notifications you're receiving. For example, you may consider disabling the settings to automatically watch all repositories and all team discussions whenever you've joined a team or repository.
+当收件箱中要管理的通知过多时,请考虑您是否订阅过多,或者如何更改通知设置以减少订阅数量和接收的通知类型。 例如,您可以考虑禁用在加入团队或仓库时自动关注所有仓库和所有团队讨论的设置。
-{% ifversion update-notification-settings-22 %}
-
-{% else %}
-{% endif %}
+
-For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)."
+有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#automatic-watching)”。
-To see an overview of your repository subscriptions, see "[Reviewing repositories that you're watching](#reviewing-repositories-that-youre-watching)."
-{% tip %}
+若要查看存储库订阅概述,请参阅“[查看正在关注的存储库](#reviewing-repositories-that-youre-watching)”。 {% tip %}
-**Tip:** You can select the types of event to be notified of by using the **Custom** option of the **Watch/Unwatch** dropdown list in your [watching page](https://github.com/watching) or on any repository page on {% data variables.product.product_name %}. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)."
+**提示:** 你可以在 [关注页面](https://github.com/watching)或 {% data variables.product.product_name %} 上的任何存储库页面,使用“关注/取消关注”下拉列表中的“自定义”选项选择要通知的事件类型 。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository)”。
{% endtip %}
-Many people forget about repositories that they've chosen to watch in the past. From the "Watched repositories" page you can quickly unwatch repositories. For more information on ways to unsubscribe, see "[Unwatch recommendations](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)" on {% data variables.product.prodname_blog %} and "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)." You can also create a triage workflow to help with the notifications you receive. For guidance on triage workflows, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+许多人忘记了他们过去选择关注的仓库。 从“Watched repositories(已关注仓库)”页面,您可以快速取消关注仓库。 有关取消订阅的方式的详细信息,请参阅 {% data variables.product.prodname_blog %} 上的“[取消关注建议](https://github.blog/changelog/2020-11-10-unwatch-recommendations/)”和“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。 您也可以创建分类工作流程来帮助整理收到的通知。 有关分类工作流的指导,请参阅“[自定义对通知进行分类的工作流](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。
-## Reviewing all of your subscriptions
+## 查看所有订阅
{% data reusables.notifications.access_notifications %}
-1. In the left sidebar, under the list of repositories that you have notifications from, use the "Manage notifications" drop-down to click **Subscriptions**.
- 
+1. 在左侧边栏中你接收其通知的存储库列表下,在“管理通知”下拉菜单中单击“订阅”。
+ 
-2. Use the filters and sort to narrow the list of subscriptions and begin unsubscribing to conversations you no longer want to receive notifications for.
+2. 使用过滤器和排序来缩小订阅列表,并开始取消订阅您不想再接收其通知的对话。
- 
+ 
{% tip %}
-**Tips:**
-- To review subscriptions you may have forgotten about, sort by "least recently subscribed."
+**提示:**
+- 要查看您可能忘记了的订阅,请按“least recently subscribed(最近最少订阅)”进行排序。
-- To review a list of repositories that you can still receive notifications for, see the repository list in the "filter by repository" drop-down menu.
+- 要查看您仍然可以接收其通知的仓库列表,请查看“filter by repository(按仓库过滤)”下拉菜单中的仓库列表。
{% endtip %}
-## Reviewing repositories that you're watching
+## 查看您目前关注的仓库
-1. In the left sidebar, under the list of repositories, use the "Manage notifications" drop-down menu and click **Watched repositories**.
- 
-2. Evaluate the repositories that you are watching and decide if their updates are still relevant and helpful. When you watch a repository, you will be notified of all conversations for that repository.
-
+1. 在左侧边栏的存储库列表下,在“管理通知”下拉菜单中单击“已关注的存储库”。
+ 
+2. 评估您正在关注的仓库,确定它们更新是否仍然相关和有用。 关注某仓库后,您将收到该仓库所有对话的通知。
+
{% tip %}
- **Tip:** Instead of watching a repository, consider only receiving notifications when there are updates to {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository), or any combination of these options, or completely unwatching a repository.
+ **提示:** 不要关注存储库,而是考虑仅当 {% data reusables.notifications-v2.custom-notification-types %}(如已为存储库启用)或这些选项的任意组合有更新时接收通知,或者完全取消关注存储库。
- When you unwatch a repository, you can still be notified when you're @mentioned or participating in a thread. When you configure to receive notifications for certain event types, you're only notified when there are updates to these event types in the repository, you're participating in a thread, or you or a team you're on is @mentioned.
+ 取消关注存储库后,当你被 @mentioned 或参与帖子时仍然会收到通知。 当配置为接收某些事件类型的通知时,仅当存储库中有这些事件类型的更新、你参与了线程或者你或你所在团队被 @mentioned 时才会收到通知。
{% endtip %}
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
index 18798d0d6f..d9234f8cc1 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md
@@ -1,6 +1,6 @@
---
-title: About notifications
-intro: 'Notifications provide updates about the activity on {% data variables.location.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
+title: 关于通知
+intro: '通知提供有关你在 {% data variables.product.product_location %} 上已订阅活动的更新。 可以使用通知收件箱来自定义、分类和管理更新。'
redirect_from:
- /articles/notifications
- /articles/about-notifications
@@ -14,86 +14,90 @@ versions:
ghec: '*'
topics:
- Notifications
+ms.openlocfilehash: 87034df88eb94c1d880806f01cb8748ed555a284
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147432022'
---
+## 通知和订阅
-## Notifications and subscriptions
+可选择通过订阅接收有关 {% data variables.product.product_location %} 上的特定活动的持续更新。 通知是您收到的已订阅特定活动的更新。
-You can choose to receive ongoing updates about specific activity on {% data variables.location.product_location %} through a subscription. Notifications are updates that you receive for specific activity that you are subscribed to.
+### 订阅选项
-### Subscription options
+您可以选择订阅关于以下内容的通知:
+- 关于特定议题、拉取请求或 Gist 的对话。
+- 仓库或团队讨论中的所有活动。
+- CI 活动,例如仓库中使用 {% data variables.product.prodname_actions %} 设置的工作流程的状态。
+- 仓库 {% data reusables.notifications-v2.custom-notification-types %} (如果启用)。
-You can choose to subscribe to notifications for:
-- A conversation in a specific issue, pull request, or gist.
-- All activity in a repository or team discussion.
-- CI activity, such as the status of workflows in repositories set up with {% data variables.product.prodname_actions %}.
-- Repository {% data reusables.notifications-v2.custom-notification-types %} (if enabled).
+您也可以选择自动关注所有您有推送访问权限的仓库,但复刻除外。 可单击“关注”来手动关注你有权访问的任何其他存储库。
-You can also choose to automatically watch all repositories that you have push access to, except forks. You can watch any other repository you have access to manually by clicking **Watch**.
+如果您的某项对话不再感兴趣,您可以取消订阅、取消关注或自定义以后接收的通知类型。 例如,如果不想再接收特定存储库的通知,可单击“取消订阅”。 有关详细信息,请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
-If you're no longer interested in a conversation, you can unsubscribe, unwatch, or customize the types of notifications you'll receive in the future. For example, if you no longer want to receive notifications from a particular repository, you can click **Unsubscribe**. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+### 默认订阅
-### Default subscriptions
+一般来说,默认在以下情况下自动订阅对话:
+- 在通知设置中未禁用自动关注您加入的仓库或团队。 默认情况下,此设置处于启用状态。
+- 被分配了议题或拉取请求。
+- 打开了拉取请求、议题或创建了团队讨论帖子。
+- 在帖子中发表了评论。
+- 通过单击“关注”或“订阅”手动订阅了帖子 。
+- 向你的用户名执行了 @mentioned。
+- 更改了帖子的状态,例如通过关闭议题或合并拉取请求。
+- 向你所属的团队执行了 @mentioned。
-In general, you are automatically subscribed to conversations by default when you have:
-- Not disabled automatic watching for repositories or teams you've joined in your notification settings. This setting is enabled by default.
-- Been assigned to an issue or pull request.
-- Opened a pull request, issue, or created a team discussion post.
-- Commented on a thread.
-- Subscribed to a thread manually by clicking **Watch** or **Subscribe**.
-- Had your username @mentioned.
-- Changed the state of a thread, such as by closing an issue or merging a pull request.
-- Had a team you're a member of @mentioned.
+默认情况下,还会自动关注你创建的以及你的个人帐户所拥有的所有存储库。
-By default, you also automatically watch all repositories that you create and are owned by your personal account.
+要取消订阅自动订阅的对话,可更改通知设置,或者直接取消订阅或取消关注 {% data variables.product.product_location %} 上的活动。 有关详细信息,请参阅“[管理订阅](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)”。
-To unsubscribe from conversations you're automatically subscribed to, you can change your notification settings or directly unsubscribe or unwatch activity on {% data variables.location.product_location %}. For more information, see "[Managing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/managing-your-subscriptions)."
+## 自定义通知和订阅
-## Customizing notifications and subscriptions
+可选择通过 [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} 上和 {% data variables.product.prodname_mobile %} 应用中的通知收件箱查看通知{% endif %},或者通过电子邮件或这些选项的某种组合进行查看。
-You can choose to view your notifications through the notifications inbox at [https://github.com/notifications](https://github.com/notifications){% ifversion fpt or ghes or ghec %} and in the {% data variables.product.prodname_mobile %} app{% endif %}, through your email, or some combination of these options.
+要自定义您希望接收的更新类型以及将这些更新发送至何处,请配置通知设置。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。
-To customize the types of updates you'd like to receive and where to send those updates, configure your notification settings. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)."
+要保持订阅的可管理性,请审查您的订阅和关注的仓库,并根据需要取消订阅。 有关详细信息,请参阅“[在 GitHub 上管理活动的订阅](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)”。
-To keep your subscriptions manageable, review your subscriptions and watched repositories and unsubscribe as needed. For more information, see "[Managing subscriptions for activity on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+要自定义如何接收特定拉取请求或议题的更新,可以在议题或拉取请求中配置首选项。 有关详细信息,请参阅“[对单个通知进行分类](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)”。
-To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see "[Triaging a single notification](/github/managing-subscriptions-and-notifications-on-github/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request)."
-
-{% ifversion fpt or ghes or ghec %}
-You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)."
+{% ifversion fpt or ghes or ghec %} 可在 {% data variables.product.prodname_mobile %} 应用中自定义和安排推送通知。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#managing-your-notification-settings-with-github-mobile)”。
{% endif %}
-## Reasons for receiving notifications
+## 接收通知的原因
-Your inbox is configured with default filters, which represent the most common reasons that people need to follow-up on their notifications. For more information about inbox filters, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)."
+您的收件箱配置了默认过滤器,它们代表人们需要跟进通知的最常见原因。 有关收件箱筛选器的详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#default-notification-filters)”。
-Your inbox shows the `reasons` you're receiving notifications as a label.
+收件箱以标签形式显示你接收通知的 `reasons`。
-
+
-You can filter your inbox by the reason you're subscribed to notifications. For example, to only see pull requests where someone requested your review, you can use the `review-requested` query filter.
+您可以按订阅通知的原因过滤收件箱。 例如,要仅查看有人请求你审查的拉取请求,可使用 `review-requested` 查询筛选器。
-
+
-If you've configured notifications to be sent by email and believe you're receiving notifications that don't belong to you, consider troubleshooting with email headers, which show the intended recipient. For more information, see "[Configuring notifications](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)."
+如果您已将通知配置为通过电子邮件发送,但认为您收到了不属于自己的通知,请考虑使用显示预期收件人的电子邮件标头排除故障。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#filtering-email-notifications)”。
-## Triaging notifications from your inbox
+## 从收件箱分类通知
-To effectively manage your notifications, you can triage your inbox with options to:
-- Remove a notification from the inbox with **Done**. You can review **Done** notifications all in one place by clicking **Done** in the sidebar or by using the query `is:done`.
-- Mark a notification as read or unread.
-- **Save** a notification for later review. **Saved** notifications are flagged in your inbox. You can review **Saved** notifications all in one place in the sidebar by clicking **Saved** or by using the query `is:saved`.
-- Automatically unsubscribe from this notification and future updates from this conversation. Unsubscribing also removes the notification from your inbox. If you unsubscribe from a conversation and someone mentions your username or a team you're on that you're receiving updates for, then you will start to receive notifications from this conversation again.
+为了有效地管理通知,您可以使用以下选项对收件箱进行分类:
+- 从收件箱中删除带有“完成”标记的通知。 可单击边栏中的“完成”或使用 `is:done` 查询集中查看所有“已完成”的通知 。
+- 将通知标记为已读或未读。
+- 保存通知供以后查看。 已保存的通知会在收件箱中标记。 可在边栏中单击“已保存”或使用 `is:saved` 查询集中查看所有“已保存”的通知 。
+- 自动取消订阅此通知和此对话的未来更新。 取消订阅还会从收件箱中删除通知。 如果您取消订阅了对话,但有人在此对话中提及您的用户名或您所在的团队(您正在为其接收更新),则您将再次开始接收此对话的通知。
-From your inbox you can also triage multiple notifications at once. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)."
+您还可以从收件箱中一次分类多个通知。 有关详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox#triaging-multiple-notifications-at-the-same-time)”。
-## Customizing your notifications inbox
+## 自定义通知收件箱
-To focus on a group of notifications in your inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} or {% data variables.product.prodname_mobile %}{% endif %}, you can create custom filters. For example, you can create a custom filter for an open source project you contribute to and only see notifications for that repository in which you are mentioned. For more information, see "[Managing notifications from your inbox](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)." For more examples of how to customize your triaging workflow, see "[Customizing a workflow for triaging your notifications](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)."
+要在 {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 或 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱中关注一组通知,可创建自定义筛选器。 例如,您可以为您参与的开源项目创建自定义过滤器,只查看您被提及的仓库的通知。 有关详细信息,请参阅“[管理收件箱中的通知](/github/managing-subscriptions-and-notifications-on-github/managing-notifications-from-your-inbox)”。 有关如何自定义分类工作流的更多示例,请参阅“[自定义对通知进行分类的工作流](/github/managing-subscriptions-and-notifications-on-github/customizing-a-workflow-for-triaging-your-notifications)”。
-## Notification retention policy
+## 通知保留策略
-Notifications that are not marked as **Saved** are kept for 5 months. Notifications marked as **Saved** are kept indefinitely. If your saved notification is older than 5 months and you unsave it, the notification will disappear from your inbox within a day.
+未标记为“已保存”的通知将保留 5 个月。 标记为“已保存”的通知将无限期保留。 如果已保存通知超过 5 个月后,您取消保存它,则该通知将在一天之内从收件箱中消失。
-## Feedback and support
+## 反馈和支持
-If you have feedback or feature requests for notifications, use a [{% data variables.product.prodname_github_community %} discussion](https://github.com/orgs/community/discussions/categories/general).
+如果你有针对通知的反馈或功能请求,请使用 [{% data variables.product.prodname_github_community %} 讨论](https://github.com/orgs/community/discussions/categories/general)。
diff --git a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
index ee9ed4f6aa..6108895268 100644
--- a/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
+++ b/translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md
@@ -1,6 +1,6 @@
---
-title: Configuring notifications
-intro: 'Choose the type of activity on {% data variables.product.prodname_dotcom %} that you want to receive notifications for and how you want these updates delivered.'
+title: 配置通知
+intro: '选择 {% data variables.product.prodname_dotcom %} 上您想要接收其通知的活动类型以及您希望如何发送这些更新。'
redirect_from:
- /articles/about-web-notifications
- /format-of-notification-emails
@@ -22,88 +22,78 @@ versions:
ghec: '*'
topics:
- Notifications
+ms.openlocfilehash: b7822a7db40455476c5fc5ac6f779e45d7f558a9
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147060760'
---
+## 通知递送选项
-## Notification delivery options
+可以在以下位置的 {% data variables.product.product_location %} 上接收活动的通知。
-You can receive notifications for activity on {% data variables.location.product_location %} in the following locations.
+ - {% data variables.product.product_location %} Web 界面{% ifversion fpt or ghes or ghec %}中的通知收件箱
+ - {% data variables.product.prodname_mobile %} 上的通知收件箱,它与 {% data variables.product.product_location %} 上的收件箱同步{% endif %}
+ - 使用经验证电子邮件地址的电子邮件客户端,也可以与 {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 及 {% data variables.product.prodname_mobile %} 上的通知收件箱同步{% endif %}
- - The notifications inbox in the {% data variables.location.product_location %} web interface{% ifversion fpt or ghes or ghec %}
- - The notifications inbox on {% data variables.product.prodname_mobile %}, which syncs with the inbox on {% data variables.location.product_location %}{% endif %}
- - An email client that uses a verified email address, which can also sync with the notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %}
-
-{% ifversion fpt or ghes or ghec %}
-{% data reusables.notifications-v2.notifications-inbox-required-setting %} For more information, see "[Choosing your notification settings](#choosing-your-notification-settings)."
+{% ifversion fpt or ghes or ghec %} {% data reusables.notifications-v2.notifications-inbox-required-setting %} 有关详细信息,请参阅“[选择通知设置](#choosing-your-notification-settings)”。
{% endif %}
{% data reusables.notifications.shared_state %}
-### Benefits of the notifications inbox
+### 通知收件箱的优点
-The notifications inbox on {% data variables.location.product_location %}{% ifversion fpt or ghes or ghec %} and {% data variables.product.prodname_mobile %}{% endif %} includes triaging options designed specifically for your {% data variables.product.prodname_dotcom %} notifications flow, including options to:
- - Triage multiple notifications at once.
- - Mark completed notifications as **Done** and remove them from your inbox. To view all of your notifications marked as **Done**, use the `is:done` query.
- - Save a notification to review later. Saved notifications are flagged in your inbox and kept indefinitely. To view all of your saved notifications, use the `is:saved` query.
- - Unsubscribe and remove a notification from your inbox.
- - Preview the issue, pull request, or team discussion where the notification originates on {% data variables.location.product_location %} from within the notifications inbox.
- - See one of the latest reasons you're receiving a notification from your inbox with a `reasons` label.
- - Create custom filters to focus on different notifications when you want.
- - Group notifications in your inbox by repository or date to get a quick overview with less context switching
+{% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 和 {% data variables.product.prodname_mobile %}{% endif %} 上的通知收件箱包含专为你的 {% data variables.product.prodname_dotcom %} 通知流程设计的分类选项,包括:
+ - 一次分类多个通知。
+ - 将已完成的通知标记为“完成”并将其从收件箱中删除。 要查看标记为“完成”的所有通知,请使用 `is:done` 查询。
+ - 保存通知以供以后查看。 已保存的通知会在收件箱中标记并无限期保留。 要查看保存的所有通知,请使用 `is:saved` 查询。
+ - 取消订阅并从收件箱中删除通知。
+ - 从通知收件箱预览 {% data variables.product.product_location %} 上产生通知的议题、拉取请求或团队讨论。
+ - 查看你从收件箱收到带有 `reasons` 标签的通知的最新原因之一。
+ - 创建自定义筛选器,以便在需要时关注不同的通知。
+ - 按仓库或日期对收件箱中的通知进行分组,以快速概览通知,减少上下文切换
-{% ifversion fpt or ghes or ghec %}
-In addition, you can receive and triage notifications on your mobile device with {% data variables.product.prodname_mobile %}. For more information, see "[Managing your notification settings with GitHub Mobile](#managing-your-notification-settings-with-github-mobile)" or "[GitHub Mobile](/get-started/using-github/github-mobile)."
+{% ifversion fpt or ghes or ghec %} 此外,可以通过 {% data variables.product.prodname_mobile %} 在移动设备上接收和分类通知。 有关详细信息,请参阅“[使用 GitHub Mobile 管理通知设置](#managing-your-notification-settings-with-github-mobile)”或“[GitHub Mobile](/get-started/using-github/github-mobile)”。
{% endif %}
-### Benefits of using an email client for notifications
+### 对通知使用电子邮件客户端的优点
-One benefit of using an email client is that all of your notifications can be kept indefinitely depending on your email client's storage capacity. Your inbox notifications are only kept for 5 months on {% data variables.product.prodname_dotcom %} unless you've marked them as **Saved**. **Saved** notifications are kept indefinitely. For more information about your inbox's retention policy, see "[About notifications](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)."
+使用电子邮件客户端的一个好处是,可以无限期地保留所有通知,具体取决于电子邮件客户端的存储容量。 收件箱通知在 {% data variables.product.prodname_dotcom %} 上仅保留 5 个月,除非将它们标记为“已保存”。 “已保存”通知将无限期保留。 有关收件箱保留策略的详细信息,请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications#notification-retention-policy)”。
-Sending notifications to your email client also allows you to customize your inbox according to your email client's settings, which can include custom or color-coded labels.
+向电子邮件客户端发送通知还允许您根据电子邮件客户端的设置(可以包括自定义或颜色编码的标签)自定义收件箱。
-Email notifications also allow flexibility with the types of notifications you receive and allow you to choose different email addresses for updates. For example, you can send certain notifications for a repository to a verified personal email address. For more information, about your email customization options, see "[Customizing your email notifications](#customizing-your-email-notifications)."
+电子邮件通知还允许您灵活地设置收到的通知类型,并允许您选择不同的电子邮件地址进行更新。 例如,您可以向经验证的个人电子邮件地址发送仓库的某些通知。 有关电子邮件自定义选项的详细信息,请参阅“[自定义电子邮件通知](#customizing-your-email-notifications)”。
-## About participating and watching notifications
+## 关于参与和查看通知
-When you watch a repository, you're subscribing to updates for activity in that repository. Similarly, when you watch a specific team's discussions, you're subscribing to all conversation updates on that team's page. For more information, see "[About team discussions](/organizations/collaborating-with-your-team/about-team-discussions)."
+关注仓库,意味着订阅该仓库中的活动更新。 同样,关注特定团队的讨论,意味着订阅该团队页面上的所有对话更新。 有关详细信息,请参阅“[关于团队讨论](/organizations/collaborating-with-your-team/about-team-discussions)”。
-To see repositories that you're watching, go to your [watching page](https://github.com/watching). For more information, see "[Managing subscriptions and notifications on GitHub](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)."
+若要查看正在监视的存储库,请参阅[监视页面](https://github.com/watching)。 有关详细信息,请参阅“[在 GitHub 上管理订阅和通知](/github/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github)”。
{% ifversion ghae %}
-### Configuring notifications
-{% endif %}
-You can configure notifications for a repository on the repository page, or on your watching page.
+### 配置通知
+{% endif %} 可以在存储库页面上或在监视页面上为存储库配置通知。
-### About custom notifications
-You can customize notifications for a repository. For example, you can choose to only be notified when updates to one or more types of events ({% data reusables.notifications-v2.custom-notification-types %}) happen within a repository, or ignore all notifications for a repository. For more information, see "[Configuring your watch settings for an individual repository](#configuring-your-watch-settings-for-an-individual-repository)" below.
+### 关于自定义通知
+您可以自定义仓库的通知。 例如,您可以选择仅在仓库中发生一类或多类事件 ({% data reusables.notifications-v2.custom-notification-types %}) 的更新时收到通知,或者忽略仓库的所有通知。 有关详细信息,请参阅下方的“[为单个存储库配置监视设置](#configuring-your-watch-settings-for-an-individual-repository)”。
-### Participating in conversations
-Anytime you comment in a conversation or when someone @mentions your username, you are _participating_ in a conversation. By default, you are automatically subscribed to a conversation when you participate in it. You can unsubscribe from a conversation you've participated in manually by clicking **Unsubscribe** on the issue or pull request or through the **Unsubscribe** option in the notifications inbox.
+### 参与对话
+每当你在对话中发表评论或有人 @mentions你的用户名时,你都在参与对话。 默认情况下,当您参与对话时,会自动订阅该对话。 你可以通过单击议题或拉取请求上的“取消订阅”或通过通知收件箱中的“取消订阅”选项,手动取消订阅已参与的对话 。
-{% ifversion update-notification-settings-22 %}For conversations you're watching or participating in, you can choose whether you want to receive notifications on {% data variables.product.company_short %} or by email in your notification settings. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+对于你监视或参与的对话,你可以选择是通过电子邮件还是 {% data variables.product.product_location %}{% ifversion fpt or ghes or ghec %} 和 {% data variables.product.prodname_mobile %}{% endif %} 上的收件箱接收通知。
-
+
-{% else %}
+例如:
+ - 如果不希望将通知发送到你的电子邮件地址,请取消选中“电子邮件”以便参与和监视通知。
+ - 如果希望在参与对话时通过电子邮件接收通知,则可以选中“参与”下的“电子邮件”。
-For conversations you're watching or participating in, you can choose whether you want to receive notifications by email or through the notifications inbox on {% data variables.location.product_location %}{% ifversion ghes %} and {% data variables.product.prodname_mobile %}{% endif %}. For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+如果未对 Web{% ifversion fpt or ghes or ghec %} 和移动{% endif %}启用监视或参与通知,则你的通知收件箱不会收到任何更新。
-{% endif %}
+## 自定义电子邮件通知
-
-
-For example:
- - If you don't want notifications to be sent to your email, unselect **email** for participating and watching notifications.
- - If you want to receive notifications by email when you've participated in a conversation, then you can select **email** under "Participating".
-
-{% ifversion update-notification-settings-22 %}If you do not enable "Notify me: On GitHub" for watching or participating notifications, then your notifications inbox will not have any updates.
-
-{% else %}
-
-If you do not enable watching or participating notifications for web{% ifversion ghes %} and mobile{% endif %}, then your notifications inbox will not have any updates.{% endif %}
-
-## Customizing your email notifications
-
-After enabling email notifications, {% data variables.location.product_location %} will send notifications to you as multipart emails that contain both HTML and plain text copies of the content. Email notification content includes any Markdown, @mentions, emojis, hash-links, and more, that appear in the original content on {% data variables.location.product_location %}. If you only want to see the text in the email, you can configure your email client to display the plain text copy only.
+在启用电子邮件通知后,{% data variables.product.product_location %} 将以多部分电子邮件向你发送通知,其中包含内容的 HTML 和纯文本副本。 电子邮件通知内容包含出现在 {% data variables.product.product_location %} 上的原始内容中的任何 Markdown、@mentions、表情符号、哈希链接等。 如果您只想查看电子邮件中的文本,可以配置电子邮件客户端只显示明文副本。
{% data reusables.notifications.outbound_email_tip %}
@@ -111,194 +101,150 @@ After enabling email notifications, {% data variables.location.product_location
{% ifversion fpt or ghec %}
-If you're using Gmail, you can click a button beside the notification email to visit the original issue or pull request that generated the notification.
+如果您使用 Gmail,可以单击通知电子邮件旁边的按钮访问生成该通知的原始议题或拉取请求。
-
+
{% endif %}
-Choose a default email address where you want to send updates for conversations you're participating in or watching. You can also specify which activity on {% data variables.location.product_location %} you want to receive updates for using your default email address. For example, choose whether you want updates to your default email from:
- - Comments on issues and pull requests.
- - Pull request reviews.
- - Pull request pushes.
- - Your own updates, such as when you open, comment on, or close an issue or pull request.
+选择一个默认电子邮件地址,用于发送您参与或关注的对话的更新。 还可以指定希望使用默认电子邮件地址接收 {% data variables.product.product_location %} 上哪些活动的更新。 例如,选择您的默认电子邮件地址是否要接收以下更新:
+ - 对问题和拉取请求的评论。
+ - 拉取请求评审。
+ - 拉取请求推送。
+ - 您自己的更新,例如当您打开、评论或关闭议题或拉取请求时。
-Depending on the organization that owns the repository, you can also send notifications to different email addresses. Your organization may require the email address to be verified for a specific domain. For more information, see "[Choosing where your organization’s email notifications are sent](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)."
+您还可以向不同电子邮件地址发送通知,具体取决于拥有仓库的组织。 您的组织可能要求验证特定域的电子邮件地址。 有关详细信息,请参阅“[选择接收组织的电子邮件通知的位置](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#choosing-where-your-organizations-email-notifications-are-sent)”。
-You can also send notifications for a specific repository to an email address. For more information, see "[About email notifications for pushes to your repository](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)."
+您也可以将特定仓库的通知发送到电子邮件地址。 有关详细信息,请参阅“[关于推送到存储库的电子邮件通知](/github/administering-a-repository/about-email-notifications-for-pushes-to-your-repository)”。
{% data reusables.notifications-v2.email-notification-caveats %}
-## Filtering email notifications
+## 过滤电子邮件通知
-Each email notification that {% data variables.location.product_location %} sends contains header information. The header information in every email is consistent, so you can use it in your email client to filter or forward all {% data variables.product.prodname_dotcom %} notifications, or certain types of {% data variables.product.prodname_dotcom %} notifications.
+{% data variables.product.product_location %} 发送的每封电子邮件通知都包含标头信息。 每封电子邮件的标头信息都是一致的,因此可用于在电子邮件客户端中筛选或转发所有 {% data variables.product.prodname_dotcom %} 通知,或特定类型的 {% data variables.product.prodname_dotcom %} 通知。
-If you believe you're receiving notifications that don't belong to you, examine the `X-GitHub-Recipient` and `X-GitHub-Recipient-Address` headers. These headers show who the intended recipient is. Depending on your email setup, you may receive notifications intended for another user.
+如果你认为你收到不属于你的通知,请检查 `X-GitHub-Recipient` 和 `X-GitHub-Recipient-Address` 标题。 这些标头显示预期的收件人。 根据您的电子邮件设置,您可能会收到预期发给其他用户的通知。
-Email notifications from {% data variables.location.product_location %} contain the following header information:
+来自 {% data variables.product.product_location %} 的电子邮件通知包含以下标头信息:
-| Header | Information |
+| 标头 | 信息 |
| --- | --- |
-| `From` address | This address will always be {% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}'the no-reply email address configured by your site administrator'{% endif %}. |
-| `To` field | This field connects directly to the thread.{% ifversion not ghae %} If you reply to the email, you'll add a new comment to the conversation.{% endif %} |
-| `Cc` address | {% data variables.product.product_name %} will `Cc` you if you're subscribed to a conversation. The second `Cc` email address matches the notification reason. The suffix for these notification reasons is {% data variables.notifications.cc_address %}. The possible notification reasons are:
- `assign`: You were assigned to an issue or pull request.
- `author`: You created an issue or pull request.
- `ci_activity`: A {% data variables.product.prodname_actions %} workflow run that you triggered was completed.
- `comment`: You commented on an issue or pull request.
- `manual`: There was an update to an issue or pull request you manually subscribed to.
- `mention`: You were mentioned on an issue or pull request.
- `push`: Someone committed to a pull request you're subscribed to.
- `review_requested`: You or a team you're a member of was requested to review a pull request.
- `security_alert`: {% data variables.product.prodname_dotcom %} detected a vulnerability in a repository you receive alerts for.
- `state_change`: An issue or pull request you're subscribed to was either closed or opened.
- `subscribed`: There was an update in a repository you're watching.
- `team_mention`: A team you belong to was mentioned on an issue or pull request.
- `your_activity`: You opened, commented on, or closed an issue or pull request.
|
-| `mailing list` field | This field identifies the name of the repository and its owner. The format of this address is always `..{% data variables.command_line.backticks %}`. |
-| `X-GitHub-Severity` field | {% data reusables.repositories.security-alerts-x-github-severity %} The possible severity levels are:- `low`
- `moderate`
- `high`
- `critical`
For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)." |
+| `From` 地址 | 此地址始终是{% ifversion fpt or ghec %}'`notifications@github.com`'{% else %}“站点管理员配置的无需回复电子邮件地址”{% endif %}。 |
+| `To` 字段 | 此字段直接连接到线程。{% ifversion not ghae %} 如果你回复电子邮件,将在对话中添加一个新的评论。{% endif %} |
+| `Cc` 地址 | 如果你订阅了对话,{% data variables.product.product_name %} 将会 `Cc` 给你。 第二个 `Cc` 电子邮件地址与通知原因匹配。 这些通知原因的后缀是 {% data variables.notifications.cc_address %}。 可能的通知原因包括: - `assign`:为你分配了一个议题或拉取请求。
- `author`:你创建了议题或拉取请求。
- `ci_activity`:你触发的 {% data variables.product.prodname_actions %} 工作流程运行已完成。
- `comment`:你对议题或拉取请求发表了评论。
- `manual`:你手动订阅的议题或拉取请求有更新。
- `mention`:有人在议题或拉取请求中提及了你。
- `push`:有人提交了你订阅的拉取请求。
- `review_requested`:有人申请你或你所在的团队评审拉取请求。
- `security_alert`:{% data variables.product.prodname_dotcom %} 检测到你要接收其漏洞警报的存储库中存在漏洞。
- `state_change`:你订阅的议题或拉取请求已关闭或打开。
- `subscribed`:你监视的存储库有更新。
- `team_mention`:你所属的团队在议题或拉取请求中被提及。
- `your_activity`:你打开、评论或关闭了议题或拉取请求。
|
+| `mailing list` 字段 | 此字段识别仓库名称及其所有者。 此地址的格式始终为 `..{% data variables.command_line.backticks %}`。 |
+| `X-GitHub-Severity` 字段 | {% data reusables.repositories.security-alerts-x-github-severity %} 可能的严重程度等级包括:- `low`
- `moderate`
- `high`
- `critical`
有关详细信息,请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。 |
-## Choosing your notification settings
+## 选择通知设置
-{% data reusables.notifications.access_notifications %}
-{% data reusables.notifications-v2.manage-notifications %}
-3. On the notifications settings page, choose how you receive notifications when:
- - There are updates in repositories or team discussions you're watching or in a conversation you're participating in. For more information, see "[About participating and watching notifications](#about-participating-and-watching-notifications)."
- - You gain access to a new repository or you've joined a new team. For more information, see "[Automatic watching](#automatic-watching)."
- - There are new {% data variables.product.prodname_dependabot_alerts %} in your repository. For more information, see "[{% data variables.product.prodname_dependabot_alerts %} notification options](#dependabot-alerts-notification-options)." {% ifversion fpt or ghec %}
- - There are workflow runs updates on repositories set up with {% data variables.product.prodname_actions %}. For more information, see "[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)."{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
- - There are new deploy keys added to repositories that belong to organizations that you're an owner of. For more information, see "[Organization alerts notification options](#organization-alerts-notification-options)."{% endif %}
+{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %}
+3. 在通知设置页面上,选择在以下情况下如何接收通知:
+ - 在您关注的仓库或团队讨论或参与的对话中发生了更新。 有关详细信息,请参阅“[关于参与和监视通知](#about-participating-and-watching-notifications)”。
+ - 您获得了新仓库的访问权限或加入了新团队。 有关详细信息,请参阅“[自动监视](#automatic-watching)”。
+ - 存储库中有新的 {% data variables.product.prodname_dependabot_alerts %}。 有关详细信息,请参阅“[{% data variables.product.prodname_dependabot_alerts %} 通知选项](#dependabot-alerts-notification-options)”。 {% ifversion fpt or ghec %}
+ - 在使用 {% data variables.product.prodname_actions %} 设置的仓库上有工作流程运行更新。 有关详细信息,请参阅“[{% data variables.product.prodname_actions %} notification options](#github-actions-notification-options)”。{% endif %}{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}
+ - 新部署密钥已添加到属于您作为其所有者的组织的仓库。 有关详细信息,请参阅“[组织警报通知选项](#organization-alerts-notification-options)”。{% endif %}
-## Automatic watching
+## 自动关注
-By default, anytime you gain access to a new repository, you will automatically begin watching that repository. Anytime you join a new team, you will automatically be subscribed to updates and receive notifications when that team is @mentioned. If you don't want to automatically be subscribed, you can unselect the automatic watching options in your notification settings.
+默认情况下,每当您获得新仓库的访问权限时,您将会自动开始关注该仓库。 每当你加入新团队时,你都会自动订阅更新,并在该团队被 @mentioned时收到通知。 如果不想自动订阅,您可以取消选择自动关注选项。
-{% ifversion update-notification-settings-22 %}
-
-{% else %}
-{% endif %}
+ 
-If "Automatically watch repositories" is disabled, then you will not automatically watch your own repositories. You must navigate to your repository page and choose the watch option.
+如果禁用了“Automatically watch repositories(自动关注仓库)”,您将不会自动关注自己拥有的仓库。 您必须导航到仓库页面,然后选择关注选项。
-For more information, see "[Choosing your notification settings](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#choosing-your-notification-settings)."
+## 配置单个仓库的关注设置
-## Configuring your watch settings for an individual repository
-
-You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of certain event types such as {% data reusables.notifications-v2.custom-notification-types %} (if enabled for the repository) , or completely ignore an individual repository.
+您可以选择关注还是取消关注单个仓库。 您还可以选择仅接收某些事件类型的通知,例如 {% data reusables.notifications-v2.custom-notification-types %} (如果为存储库启用),或者完全忽略单个存储库。
{% data reusables.repositories.navigate-to-repo %}
-2. In the upper-right corner, select the "Watch" drop-down menu to click a watch option.
- 
+2. 在右上角,选择“Watch(关注)”下拉菜单以单击关注选项。
+{% ifversion fpt or ghes or ghae-issue-4910 or ghec %} 
- The **Custom** option allows you to further customize notifications so that you're only notified when specific events happen in the repository, in addition to participating and @mentions.
- 
- If you select "Issues", you will be notified about, and subscribed to, updates on every issue (including those that existed prior to you selecting this option) in the repository. If you're @mentioned in a pull request in this repository, you'll receive notifications for that too, and you'll be subscribed to updates on that specific pull request, in addition to being notified about issues.
+ “自定义”选项可用于进一步自定义通知,以便除了参与和 @mentions之外,你仅在存储库中发生特定事件时才收到通知。
+{% else %} {% endif %} {% ifversion fpt or ghes or ghae-issue-4910 or ghec %}  如果选择“议题”,你将收到存储库中每个议题(包括在你选择此选项之前存在的议题)的更新通知并订阅这些更新。 如果你在此存储库中的拉取请求中被 @mentioned,则除了收到有关议题的通知外,你还将收到有关该特定拉取请求的通知并订阅其更新。
+ {% endif %}
-## Choosing where your organization’s email notifications are sent
+## 选择接收组织的电子邮件通知的位置
-If you belong to an organization, you can choose the email account you want notifications for organization activity sent to. For example, if you belong to an organization for work, you may want your notifications sent to your work email address, rather than your personal address.
+如果您属于某个组织,您可以选择要接收组织活动通知的电子邮件帐户。 例如,如果您属于某个工作组织,您可能希望通知发送到您的工作电子邮件地址,而不是您的个人地址。
{% data reusables.notifications-v2.email-notification-caveats %}
-{% data reusables.notifications.access_notifications %}
-{% data reusables.notifications-v2.manage-notifications %}
+{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %}
+3. 在“Default notification email(默认通知电子邮件)”下,选择要接收通知的电子邮件地址。
+
+4. 单击“ **保存**”。
-3. Under "Default notification email", select the email address you'd like notifications sent to.
-{% ifversion update-notification-settings-22 %}
+### 自定义每个组织的电子邮件路由
- 
+如果您是多个组织的成员,您可以配置每个组织发送通知到任何{% ifversion fpt or ghec %} 您已验证的电子邮件地址{% else %} 帐户的电子邮件地址{% endif %}。 {% ifversion fpt or ghec %} 有关详细信息,请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。{% endif %}
-{% else %}
+{% data reusables.notifications.access_notifications %} {% data reusables.notifications-v2.manage-notifications %}
+3. 在“Custom routing(自定义路由)”下,在列表中找到您组织的名称。
+
+4. 单击要更改的电子邮件地址旁边的“编辑”。
+
+5. 选择一个经验证的电子邮件地址,然后单击“保存”。
+
- {% endif %}
-{% ifversion ghes or ghae %}
-4. Click **Save**.{% endif %}
+## {% data variables.product.prodname_dependabot_alerts %} 通知选项
-### Customizing email routes per organization
+{% data reusables.notifications.vulnerable-dependency-notification-enable %} {% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %} {% data reusables.notifications.vulnerable-dependency-notification-options %}
-If you are a member of more than one organization, you can configure each one to send notifications to any of{% ifversion fpt or ghec %} your verified email addresses{% else %} the email addresses for your account{% endif %}. {% ifversion fpt or ghec %} For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."{% endif %}
+若要详细了解可用的通知传递方法,并查看关于优化 {% data variables.product.prodname_dependabot_alerts %} 通知的建议,请参阅“[为 {% data variables.product.prodname_dependabot_alerts %} 配置通知](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)”。
-{% data reusables.notifications.access_notifications %}
-{% data reusables.notifications-v2.manage-notifications %}
-{% ifversion update-notification-settings-22 %}
-3. Under "Default notifications email", click **Custom routing**.
+{% ifversion fpt or ghes or ghec %}
+## {% data variables.product.prodname_actions %} 通知选项
- 
+选择您希望如何接收所关注仓库的工作流程运行更新,通过 {% data variables.product.prodname_actions %} 设置。 您也可以选择仅接收关于失败的工作流程运行的通知。
-4. Click **Add new route**.
+ 
- 
+{% endif %}
-5. Click **Pick organization**, then select the organization you want to customize from the dropdown.
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5668 %}
+## 组织警报通知选项
- 
-
-6. Select one of your verified email addresses, then click **Save**.
-
- 
-
-{% else %}
-3. Under "Custom routing," find your organization's name in the list.
-
- 
-
-4. Click **Edit** next to the email address you want to change.
-
- 
-
-5. Select one of your verified email addresses, then click **Save**.
-
- {% endif %}
-
-## {% data variables.product.prodname_dependabot_alerts %} notification options
-
-{% data reusables.notifications.vulnerable-dependency-notification-enable %}
-{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization2 %}
-{% data reusables.notifications.vulnerable-dependency-notification-options %}
-
-For more information about the notification delivery methods available to you, and advice on optimizing your notifications for {% data variables.product.prodname_dependabot_alerts %}, see "[Configuring notifications for {% data variables.product.prodname_dependabot_alerts %}](/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts)."
-
-{% ifversion update-notification-settings-22 or ghes %}
-## {% data variables.product.prodname_actions %} notification options
-
-Choose how you want to receive workflow run updates for repositories that you are watching that are set up with {% data variables.product.prodname_actions %}. You can also choose to only receive notifications for failed workflow runs.{% endif %}
-
-{% ifversion update-notification-settings-22 %}
-{% endif %}
-
-{% ifversion ghes %}
- {% endif %}
-
-
-{% ifversion fpt or ghec or ghes > 3.3 or ghae > 3.3 %}
-## Organization alerts notification options
-
-If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**.
+如果您是组织所有者,则当组织成员向组织内的存储库添加新的部署密钥时,默认情况下,您将收到电子邮件通知。 您可以取消订阅这些通知。 在通知设置页面上的“组织警报”下,取消选择“电子邮件”。
{% endif %}
{% ifversion fpt or ghes or ghec %}
-## Managing your notification settings with {% data variables.product.prodname_mobile %}
+## 使用 {% data variables.product.prodname_mobile %} 管理通知设置
-When you install {% data variables.product.prodname_mobile %}, you will automatically be opted into web notifications. Within the app, you can enable push notifications for the following events.
-- Direct mentions
-- Assignments to issues or pull requests
-- Requests to review a pull request
-- Requests to approve a deployment
+安装 {% data variables.product.prodname_mobile %} 时,您将自动选择 web 通知。 在应用程序中,您可以为以下事件启用推送通知。
+- 直接提及
+- 分配到议题或拉取请求
+- 请求审核拉取请求
+- 请求批准部署
-You can also schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device.
+您还可以安排 {% data variables.product.prodname_mobile %} 何时向移动设备发送推送通知。
{% data reusables.mobile.push-notifications-on-ghes %}
-### Managing your notification settings with {% data variables.product.prodname_ios %}
+### 使用 {% data variables.product.prodname_ios %} 管理通知设置
-1. In the bottom menu, tap **Profile**.
-2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
-3. To update your notification settings, tap **Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
-4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
+1. 在底部菜单中,点击“配置文件”。
+2. 要查看设置,请点击 {% octicon "gear" aria-label="The Gear icon" %}。
+3. 要更新通知设置,请点击“通知”,然后使用切换开关来启用或禁用首选类型的推送通知。
+4. (可选)要安排 {% data variables.product.prodname_mobile %} 何时向移动设备发送推送通知,请点击“工作时间”,使用“自定义工作时间”切换开关,然后选择何时接收推送通知 。
-### Managing your notification settings with {% data variables.product.prodname_android %}
+### 使用 {% data variables.product.prodname_android %} 管理通知设置
-1. In the bottom menu, tap **Profile**.
-2. To view your settings, tap {% octicon "gear" aria-label="The Gear icon" %}.
-3. To update your notification settings, tap **Configure Notifications** and then use the toggles to enable or disable your preferred types of push notifications.
-4. Optionally, to schedule when {% data variables.product.prodname_mobile %} will send push notifications to your mobile device, tap **Working Hours**, use the **Custom working hours** toggle, and then choose when you would like to receive push notifications.
+1. 在底部菜单中,点击“配置文件”。
+2. 要查看设置,请点击 {% octicon "gear" aria-label="The Gear icon" %}。
+3. 要更新通知设置,请点击“配置通知”,然后使用切换开关来启用或禁用首选类型的推送通知。
+4. (可选)要安排 {% data variables.product.prodname_mobile %} 何时向移动设备发送推送通知,请点击“工作时间”,使用“自定义工作时间”切换开关,然后选择何时接收推送通知 。
-## Configuring your watch settings for an individual repository with {% data variables.product.prodname_mobile %}
+## 使用 {% data variables.product.prodname_mobile %} 配置个别仓库的关注设置
-You can choose whether to watch or unwatch an individual repository. You can also choose to only be notified of {% ifversion fpt or ghec %}certain event types such as issues, pull requests, discussions (if enabled for the repository) and {% endif %}new releases, or completely ignore an individual repository.
+您可以选择关注还是取消关注单个仓库。 你也可以选择接收{% ifversion fpt or ghec %}特定事件类型,如议题、拉取请求、讨论(如已对存储库启用)以及{% endif %}新版本的通知,或者完全忽略单个存储库。
-1. On {% data variables.product.prodname_mobile %}, navigate to the main page of the repository.
-2. Tap **Watch**.
- 
-3. To choose what activities you receive notifications for, tap your preferred watch settings.
- 
+1. 在 {% data variables.product.prodname_mobile %} 上,导航到存储库的主页面。
+2. 点击“监视”。
+ 
+3. 要选择接收通知的活动,请点击首选的关注设置。
+ 
{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
index b7f02b36e0..1b6126e3d2 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
@@ -1,6 +1,6 @@
---
-title: Managing your profile README
-intro: 'You can add a README to your {% data variables.product.prodname_dotcom %} profile to tell other people about yourself.'
+title: 管理个人资料自述文件
+intro: '可以向您的 {% data variables.product.prodname_dotcom %} 个人资料添加自述文件以向其他人介绍自己。'
versions:
fpt: '*'
ghes: '*'
@@ -11,67 +11,71 @@ redirect_from:
- /github/setting-up-and-managing-your-github-profile/managing-your-profile-readme
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme
shortTitle: Your profile README
+ms.openlocfilehash: 587bcea1e1a0f96aad8882b41196afcc6e433363
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147578898'
---
-## About your profile README
+## 关于您的个人资料自述文件
-You can share information about yourself with the community on {% data variables.location.product_location %} by creating a profile README. {% data variables.product.prodname_dotcom %} shows your profile README at the top of your profile page.
+你可以通过创建个人资料自述文件,在 {% data variables.product.product_location %} 上与社区分享有关你自己的信息。 {% data variables.product.prodname_dotcom %} 在个人资料页面的顶部显示您的个人资料自述文件。
-You decide what information to include in your profile README, so you have full control over how you present yourself on {% data variables.product.prodname_dotcom %}. Here are some examples of information that visitors may find interesting, fun, or useful in your profile README.
+您决定在个人资料自述文件中包含哪些信息,因此您可以完全控制如何在 {% data variables.product.prodname_dotcom %} 上展示自己。 以下是访客可能在您的个人资料自述文件中找到感兴趣、有趣或有用信息的一些示例。
-- An "About me" section that describes your work and interests
-- Contributions you're proud of, and context about those contributions
-- Guidance for getting help in communities where you're involved
+- “About me(关于我)”部分介绍您的工作和兴趣。
+- 您引以为豪的贡献以及这些贡献的背景信息
+- 在您参与的社区获得帮助的指南
-
+
-You can format text and include emoji, images, and GIFs in your profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)." For a hands-on guide to customizing your profile README, see "[Quickstart for writing on {% data variables.product.prodname_dotcom %}](/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github)."
+您可以使用 {% data variables.product.company_short %} Flavored Markdown 在个人资料自述文件中设置文本格式和包含表情符号、图像及 GIF。 有关详细信息,请参阅“[在 {% data variables.product.prodname_dotcom %} 上编写和设置格式入门](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)”。
-## Prerequisites
+## 先决条件
-GitHub will display your profile README on your profile page if all of the following are true.
+如果满足以下所有条件,GitHub 将在您的个人资料页面显示您的个人资料自述文件。
-- You've created a repository with a name that matches your {% data variables.product.prodname_dotcom %} username.
-- The repository is public.
-- The repository contains a file named README.md in its root.
-- The README.md file contains any content.
+- 您使用与您的 {% data variables.product.prodname_dotcom %} 用户名匹配的名称创建了仓库。
+- 该仓库为公共仓库。
+- 仓库的根目录中包含名为 README.md 的文件。
+- README.md 文件包含任何内容。
{% note %}
-**Note**: If you created a public repository with the same name as your username before July 2020, {% data variables.product.prodname_dotcom %} won't automatically show the repository's README on your profile. You can manually share the repository's README to your profile by going to the repository on {% data variables.product.prodname_dotcom_the_website %} and clicking **Share to profile**.
+注意:如果你在 2020 年 7 月之前创建了一个与你的用户名同名的公共存储库,{% data variables.product.prodname_dotcom %} 将不会自动在你的个人资料中显示该存储库的自述文件。 可以通过转到 {% data variables.product.prodname_dotcom_the_website %} 上的存储库并单击“共享到配置文件”,手动将存储库的自述文件共享到配置文件。
-
+
{% endnote %}
-## Adding a profile README
+## 添加个人资料自述文件
{% data reusables.repositories.create_new %}
-2. Under "Repository name", type a repository name that matches your {% data variables.product.prodname_dotcom %} username. For example, if your username is "octocat", the repository name must be "octocat".
- 
-3. Optionally, add a description of your repository. For example, "My personal repository."
- 
-4. Select **Public**.
- 
-{% data reusables.repositories.initialize-with-readme %}
-{% data reusables.repositories.create-repo %}
-7. Above the right sidebar, click **Edit README**.
- 
+2. 在“Repository name(仓库名称)”下,输入与您的 {% data variables.product.prodname_dotcom %} 用户名匹配的仓库名称。 例如,如果您的用户名是 "octocat",则仓库名称必须为 "octocat"。
+ 
+3. 可以选择性地添加存储库的说明。 例如,“My personal repository(我的个人仓库)”。
+ 
+4. 选择“公共”。
+  {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
+7. 在右边栏上方,单击“编辑自述文件”。
+ 
- The generated README file is pre-populated with a template to give you some inspiration for your profile README.
- 
+ 生成的自述文件用模板预先填充,为您创建个人资料自述文件提供一些启发。
+ 
-For a summary of all the available emojis and their codes, see "[Emoji cheat sheet](https://www.webfx.com/tools/emoji-cheat-sheet/)."
+有关所有可用表情符号及其代码的摘要,请参阅“[表情符号备忘单](https://www.webfx.com/tools/emoji-cheat-sheet/)”。
-## Removing a profile README
+## 删除个人资料自述文件
-The profile README is removed from your {% data variables.product.prodname_dotcom %} profile if any of the following apply:
+如果以下任何一项适用,个人资料自述文件将从您的 {% data variables.product.prodname_dotcom %} 个人资料中被删除:
-- The README file is empty or doesn't exist.
-- The repository is private.
-- The repository name no longer matches your username.
+- 自述文件为空或不存在。
+- 该仓库为私有仓库。
+- 仓库名称不再与您的用户名匹配。
-The method you choose depends upon your needs, but if you're unsure, we recommend making your repository private. For steps on how to make your repository private, see "[Changing a repository's visibility](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)."
+您选择的方法取决于您的需求,但如果您不确定,我们建议您将仓库设为私有。 有关如何将存储库设为专用的步骤,请参阅“[更改存储库的可见性](/github/administering-a-repository/setting-repository-visibility#changing-a-repositorys-visibility)”。
-## Further reading
+## 延伸阅读
-- [About READMEs](/github/creating-cloning-and-archiving-repositories/about-readmes)
+- [关于自述文件](/github/creating-cloning-and-archiving-repositories/about-readmes)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
index 2d9b69cef2..296d00bcf1 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -1,6 +1,6 @@
---
-title: Personalizing your profile
-intro: 'You can share information about yourself with other {% data variables.product.product_name %} users by setting a profile picture and adding a bio to your profile.'
+title: 个性化您的个人资料
+intro: '你可以在个人资料中设置头像和添加个人简历,与其他 {% data variables.product.product_name %} 用户共享你自己的信息。'
redirect_from:
- /articles/adding-a-bio-to-your-profile
- /articles/setting-your-profile-picture
@@ -18,186 +18,156 @@ versions:
topics:
- Profiles
shortTitle: Personalize
+ms.openlocfilehash: c12fccd91144428fe9aad2f01d2c0b0941fdd4d4
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '146681051'
---
-## Changing your profile picture
+## 更改头像
-Your profile picture helps identify you across {% data variables.product.product_name %} in pull requests, comments, contributions pages, and graphs.
+您的头像可帮助在 {% data variables.product.product_name %} 的拉取请求、评论、参与页面及图形中识别您。
-When you sign up for an account, {% data variables.product.product_name %} provides you with a randomly generated "identicon". [Your identicon](https://github.com/blog/1586-identicons) generates from a hash of your user ID, so there's no way to control its color or pattern. You can replace your identicon with an image that represents you.
+在注册帐户时,{% data variables.product.product_name %} 会提供一个随机生成的“默认肖像”。 [哈希头像](https://github.com/blog/1586-identicons)根据用户 ID 的哈希生成,因此无法控制其颜色或模式。 您可以将默认肖像替换为能代表您的图片。
{% note %}
-**Note{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %}
+注意{% ifversion ghec %}s{% endif %}:{% ifversion ghec %}
-* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
-{% ifversion ghec %}* Gravatar profile pictures are not supported with {% data variables.product.prodname_emus %}.{% endif %}
+* {% endif %}个人资料图片应为 PNG、JPG 或 GIF 文件,其大小必须小于 1 MB,且小于 3000 x 3000 像素。 为获取质量最佳的渲染,建议图像的像素保持在大约 500 x 500 像素。
+{% ifversion ghec %}* {% data variables.product.prodname_emus %} 不支持 Gravatar 头像。{% endif %}
{% endnote %}
-### Setting a profile picture
+### 设置头像
{% data reusables.user-settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-
-3. Click **Upload a photo...**.{% ifversion not ghae %}
-{% endif %}
-3. Crop your picture. When you're done, click **Set new profile picture**.
- 
+2. 在“个人资料图片”下,单击 {% octicon "pencil" aria-label="The edit icon" %}“编辑” 。
+
+3. 单击“上传照片...”。{% ifversion not ghae %}{% endif %}
+3. 裁剪图片。 完成后,单击“设置新的个人资料图片”。
+ 
-### Resetting your profile picture to the identicon
+### 将头像重置为默认肖像
{% data reusables.user-settings.access_settings %}
-2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
-
-3. To revert to your identicon, click **Remove photo**. {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
-{% endif %}
+2. 在“个人资料图片”下,单击 {% octicon "pencil" aria-label="The edit icon" %}“编辑” 。
+
+3. 要还原为哈希头像,请单击“删除照片”。 {% ifversion not ghae %}如果电子邮件地址与 [Gravatar](https://en.gravatar.com/) 相关联,则无法还原为默认肖像。 此时请单击“还原为 Gravatar”。
+{% endif %}
-## Changing your profile name
+## 更改个人资料名称
-You can change the name that is displayed on your profile. This name may also be displayed next to comments you make on private repositories owned by an organization. For more information, see "[Managing the display of member names in your organization](/articles/managing-the-display-of-member-names-in-your-organization)."
+您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 有关详细信息,请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。
-{% ifversion fpt or ghec %}
-{% note %}
+{% ifversion fpt or ghec %} {% note %}
-**Note:** If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, any changes to your profile name must be made through your identity provider instead of {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+注意:如果你是 {% data variables.product.prodname_emu_enterprise %} 的成员,则必须通过你的标识提供者而不是 {% data variables.product.prodname_dotcom_the_website %} 对个人资料名称进行任何更改。 {% data reusables.enterprise-accounts.emu-more-info-account %}
-{% endnote %}
-{% endif %}
+{% endnote %} {% endif %}
{% data reusables.user-settings.access_settings %}
-2. Under "Name", type the name you want to be displayed on your profile.
- 
+2. 在“Name(名称)”下,键入要显示在个人资料中的名称。
+ 
-## Adding a bio to your profile
+## 在个人资料中添加个人简历
-Add a bio to your profile to share information about yourself with other {% data variables.product.product_name %} users. With the help of [@mentions](/articles/basic-writing-and-formatting-syntax) and emoji, you can include information about where you currently or have previously worked, what type of work you do, or even what kind of coffee you drink.
+在个人资料中添加个人简历,与其他 {% data variables.product.product_name %} 用户共享您自己的信息。 借助 [@mentions](/articles/basic-writing-and-formatting-syntax) 和表情符号,你可以在简历中包括以下信息:目前或以前工作的工作地点、从事的工作类型,甚至是喜欢的咖啡种类。
{% ifversion fpt or ghes or ghec %}
-For a longer-form and more prominent way of displaying customized information about yourself, you can also use a profile README. For more information, see "[Managing your profile README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)."
+要以更长和更突出的方式显示有关自己的自定义信息,您还可以使用个人资料自述文件。 有关详细信息,请参阅“[管理个人资料 README](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。
{% endif %}
{% note %}
-**Note:**
- If you have the activity overview section enabled for your profile and you @mention an organization you're a member of in your profile bio, then that organization will be featured first in your activity overview. For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+注意:如果你为个人资料启用了活动概述部分,并且在个人资料的个人简历中 @mention 你所属的组织,那么该组织将首先出现在你的活动概述中。 有关详细信息,请参阅“[在个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
{% endnote %}
{% data reusables.user-settings.access_settings %}
-2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
- 
+2. 在“个人简历”下,添加要在个人资料中显示的内容。 个人资料字段限于 160 个字符。
+ 
{% tip %}
- **Tip:** When you @mention an organization, only those that you're a member of will autocomplete. You can still @mention organizations that you're not a member of, like a previous employer, but the organization name won't autocomplete for you.
+ 提示:当你 @mention 组织时,只有你所属的组织才会自动填写。 你也可 @mention 不是其成员的组织(例如前雇主),但该组织名称不会自动填写。
{% endtip %}
-{% data reusables.profile.update-profile %}
+3. 单击“更新个人资料”。
+ 
-{% ifversion profile-time-zone %}
+## 设置状态
-## Setting your location and time zone
+您可以设置状态以显示您当前在 {% data variables.product.product_name %} 上的可用性。 您的状态将会显示:
+- 在您的 {% data variables.product.product_name %} 个人资料页面上。
+- 当有人在 {% data variables.product.product_name %} 上将鼠标放在您的用户名或头像上时。
+- 在您属于其成员的团队页面上时。 有关详细信息,请参阅“[关于团队](/articles/about-teams/#team-pages)”。
+- 在您属于其成员的组织的组织仪表板上。 有关详细信息,请参阅“[关于组织仪表板](/articles/about-your-organization-dashboard/)”。
-You can set a location and time zone on your profile to show other people your local time. Your location and time zone will be visible:
-- on your {% data variables.product.product_name %} profile page.
-- when people hover over your username or avatar on {% data variables.product.product_name %}.
+在设置状态时,您也可以让人们知道您在 {% data variables.product.product_name %} 上的可用性有限。
-When you view your profile, you will see your location, local time, and your time zone in relation to Universal Time Coordinated.
+
- 
+
-When others view your profile, they will see your location, local time, and the time difference in hours from their own local time.
+如果选择“忙碌”选项,当人们 @mention 你的用户名、分配给你问题或拉取请求或者请求你对拉取请求进行评审时,你的用户名旁边将会出现一条表示你在忙碌的注释。 您还将被排除在分配给您所属的任何团队的拉取请求的自动审核任务之外。 有关详细信息,请参阅“[管理团队的代码评审设置](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)”。
- 
-
-{% data reusables.user-settings.access_settings %}
-1. Under **Location**, type the location you want to be displayed on your profile.
-
- 
-
-1. Optionally, to display the current local time on your profile, select **Display current local time**.
-
- 
-
- - Select the **Time zone** dropdown menu, then click your local time zone.
-
- 
-
-{% data reusables.profile.update-profile %}
-
-{% endif %}
-
-## Setting a status
-
-You can set a status to display information about your current availability on {% data variables.product.product_name %}. Your status will show:
-- on your {% data variables.product.product_name %} profile page.
-- when people hover over your username or avatar on {% data variables.product.product_name %}.
-- on a team page for a team where you're a team member. For more information, see "[About teams](/articles/about-teams/#team-pages)."
-- on the organization dashboard in an organization where you're a member. For more information, see "[About your organization dashboard](/articles/about-your-organization-dashboard/)."
-
-When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
-
-
-
-
-
-If you select the "Busy" option, when people @mention your username, assign you an issue or pull request, or request a pull request review from you, a note next to your username will show that you're busy. You will also be excluded from automatic review assignment for pull requests assigned to any teams you belong to. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
-
-1. In the top right corner of {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %}, click your profile photo, then click **Set status** or, if you already have a status set, click your current status.
- 
-2. To add custom text to your status, click in the text field and type a status message.
- 
-3. Optionally, to set an emoji status, click the smiley icon and select an emoji from the list.
- 
-4. Optionally, if you'd like to share that you have limited availability, select "Busy."
- 
-5. Use the **Clear status** drop-down menu, and select when you want your status to expire. If you don't select a status expiration, you will keep your status until you clear or edit your status.
- 
-6. Use the drop-down menu and click the organization you want your status visible to. If you don't select an organization, your status will be public.
- 
-7. Click **Set status**.
- 
+1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_name %}{% endif %} 的右上角,单击你的个人资料照片,然后单击“设置状态”,或者,如果已设置状态,则单击当前状态。
+ 
+2. 要添加自定义文本到状态,请单击文本字段,然后输入状态消息。
+ 
+3. (可选)要设置表情符号状态,请单击笑脸图标并从列表中选择表情符号。
+ 
+4. (可选)如果想表示您的可用性受限,请选择“Busy(忙碌)”。
+ 
+5. 使用“清除状态”下拉菜单,选择状态的到期时间。 如果不选择状态到期时间,您的状态将保持到您清除或编辑状态为止。
+ 
+6. 使用下拉菜单,单击您要向其显示状态的组织。 如果不选择组织,您的状态将是公共的。
+ 
+7. 单击“设置状态”。
+ 
{% ifversion fpt or ghec %}
-## Displaying badges on your profile
+## 在个人资料中显示徽章
-When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
+当您参与某些计划时, {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
-| Badge | Program | Description |
+| 徽章 | 节目 | 说明 |
| --- | --- | --- |
-| {% octicon "cpu" aria-label="The Developer Program icon" %} | **Developer Program Member** | If you're a registered member of the {% data variables.product.prodname_dotcom %} Developer Program, building an app with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, you'll get a Developer Program Member badge on your profile. For more information on the {% data variables.product.prodname_dotcom %} Developer Program, see [GitHub Developer](/program/). |
-| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | If you use {% data variables.product.prodname_pro %} you'll get a PRO badge on your profile. For more information about {% data variables.product.prodname_pro %}, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products#github-pro)." |
-| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | If you helped out hunting down security vulnerabilities, you'll get a Security Bug Bounty Hunter badge on your profile. For more information about the {% data variables.product.prodname_dotcom %} Security program, see [{% data variables.product.prodname_dotcom %} Security](https://bounty.github.com/). |
-| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} Campus Expert** | If you participate in the {% data variables.product.prodname_campus_program %}, you will get a {% data variables.product.prodname_dotcom %} Campus Expert badge on your profile. For more information about the Campus Experts program, see [Campus Experts](https://education.github.com/experts). |
-| {% octicon "shield" aria-label="The shield icon" %} | **Security advisory credit** | If a security advisory you submit to the [{% data variables.product.prodname_dotcom %} Advisory Database](https://github.com/advisories) is accepted, you'll get a Security advisory credit badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Security Advisories, see [{% data variables.product.prodname_dotcom %} Security Advisories](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories). |
-| {% octicon "check" aria-label="The check icon" %} | **Discussion answered** | If your reply to a discussion is marked as the answer, you'll get a Discussion answered badge on your profile. For more information about {% data variables.product.prodname_dotcom %} Discussions, see [About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions). |
+| {% octicon "cpu" aria-label="The Developer Program icon" %} | **开发人员计划成员** | 如果您是 {% data variables.product.prodname_dotcom %} 开发者计划的注册成员,使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 构建应用程序,您的个人资料上将获得开发者计划成员徽章。 有关 {% data variables.product.prodname_dotcom %} 开发人员计划的更多信息,请参阅 [GitHub 开发人员](/program/)。 |
+| {% octicon "star-fill" aria-label="The star icon" %} | **Pro** | 如果您使用 {% data variables.product.prodname_pro %},您的个人资料中将获得一个 PRO 徽章。 有关 {% data variables.product.prodname_pro %} 的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products#github-pro)”。 |
+| {% octicon "lock" aria-label="The lock icon" %} | **Security Bug Bounty Hunter** | 如果你帮助寻找安全漏洞,您的个人资料上将获得 Security Bug Bounty Hunter 徽章。 有关 {% data variables.product.prodname_dotcom %} 安全计划的详细信息,请参阅 [{% data variables.product.prodname_dotcom %} 安全性](https://bounty.github.com/)。 |
+| {% octicon "mortar-board" aria-label="The mortar-board icon" %} | **{% data variables.product.prodname_dotcom %} 校园专家** | 如果您参加 {% data variables.product.prodname_campus_program %},您的个人资料上将获得 {% data variables.product.prodname_dotcom %} 校园专家徽章。 有关校园专家计划的详细信息,请参阅[校园专家](https://education.github.com/experts)。 |
+| {% octicon "shield" aria-label="The shield icon" %} | 安全公告信用 | 如果你提交到 [{% data variables.product.prodname_dotcom %} 公告数据库](https://github.com/advisories)的安全公告被接受,你的个人资料上将获得一个安全公告信用徽章。 有关 {% data variables.product.prodname_dotcom %} 安全公告的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 安全公告](/code-security/repository-security-advisories/about-github-security-advisories-for-repositories)”。 |
+| {% octicon "check" aria-label="The check icon" %} | 已回答的讨论 | 如果对讨论的答复标记为答案,你将在个人资料上获得“已回答的讨论”徽章。 有关 {% data variables.product.prodname_dotcom %} 的详细信息,请参阅[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)。 |
{% endif %}
{% ifversion fpt or ghec %}
-## Earning Achievements
+## 获得成就
-Achievements celebrate specific events and actions that happen on {% data variables.product.prodname_dotcom %}. They will appear as small badges listed in the sidebar of your profile. Clicking or hovering on an achievement will show a detailed view that hints at how the achievement was earned, with a short description and links to the contributing events. The event links will only be visible to users that have access to the repository or organization that the event took place in. Event links will appear inaccessible to all users without access.
+成就庆祝 {% data variables.product.prodname_dotcom %} 上发生的特定事件和操作。 它们将显示为你的个人资料边栏中列出的小徽章。 单击或悬停在成就上将显示一个详细视图,该视图提示如何获得成就,并提供简短说明和参与事件的链接。 事件链接将仅对有权访问发生事件的存储库或组织的用户可见。 对于没有访问权限的所有用户,事件链接将不可访问。
-To stop private contributions from counting toward your Achievements, or to turn off Achievements entirely, see "[Showing your private contributions and Achievements on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+若要阻止私人贡献计入成就,或完全关闭成就,请参阅“[在个人资料上显示你的私人贡献和成就](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。
{% note %}
-**Note:** This feature is currently in beta and subject to change.
+注意:此功能目前为 beta 版本,可能会有变动。
{% endnote %}
{% endif %}
-## List of qualifying repositories for Mars 2020 Helicopter Contributor achievement
+## Mars 2020 Helicopter 贡献者成就的合格仓库列表
-If you authored any commit(s) present in the commit history for the listed tag of one or more of the repositories below, you'll receive the Mars 2020 Helicopter Contributor achievement on your profile. The authored commit must be with a verified email address, associated with your account at the time {% data variables.product.prodname_dotcom %} determined the eligible contributions, in order to be attributed to you. You can be the original author or [one of the co-authors](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors) of the commit. Future changes to verified emails will not have an effect on the badge. We built the list based on information received from NASA's Jet Propulsion Laboratory.
+如果你为下面一个或多个仓库列出的标记撰写了提交历史记录中的任何提交,你的个人资料中将获得 Mars 2020 Helicopter 贡献者成就。 撰写的提交必须有验证过的电子邮件地址,该电子邮件地址在 {% data variables.product.prodname_dotcom %} 确定符合条件的贡献时与您帐户关联,表示该贡献归属于您。 你可以是提交的原始作者或[共同作者之一](/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors)。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
-| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
+| {% data variables.product.prodname_dotcom %} 仓库 | 版本 | 标记 |
|---|---|---|
| [torvalds/linux](https://github.com/torvalds/linux) | 3.4 | [v3.4](https://github.com/torvalds/linux/releases/tag/v3.4) |
| [python/cpython](https://github.com/python/cpython) | 3.9.2 | [v3.9.2](https://github.com/python/cpython/releases/tag/v3.9.2) |
@@ -268,6 +238,6 @@ If you authored any commit(s) present in the commit history for the listed tag o
| [locationtech/jts](https://github.com/locationtech/jts) | 1.15.0 | [jts-1.15.0](https://github.com/locationtech/jts/releases/tag/jts-1.15.0) |
| [apache/logging-log4j2](https://github.com/apache/logging-log4j2) | 2.11 | [log4j-2.11.0](https://github.com/apache/logging-log4j2/releases/tag/log4j-2.11.0) |
-## Further reading
+## 延伸阅读
-- "[About your profile](/articles/about-your-profile)"
+- [关于个人资料](/articles/about-your-profile)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md
new file mode 100644
index 0000000000..d5f4a266ac
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/index.md
@@ -0,0 +1,28 @@
+---
+title: 管理个人资料中的贡献图
+intro: Your contributions, including commits, proposed pull requests, and opened issues, are displayed on your profile so people can easily see the work you've done.
+redirect_from:
+- /articles/managing-contribution-graphs-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+children:
+- /viewing-contributions-on-your-profile
+- /showing-an-overview-of-your-activity-on-your-profile
+- /publicizing-or-hiding-your-private-contributions-on-your-profile
+- /sending-enterprise-contributions-to-your-githubcom-profile
+- /why-are-my-contributions-not-showing-up-on-my-profile
+- /troubleshooting-commits-on-your-timeline
+shortTitle: Manage contribution graph
+ms.openlocfilehash: 87780d97656aa27b4d60fb06a5550f042a0f8f96
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145066986"
+---
diff --git a/translations/zh-CN/content/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.md b/translations/zh-CN/content/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.md
new file mode 100644
index 0000000000..2ed420d0f1
--- /dev/null
+++ b/translations/zh-CN/content/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.md
@@ -0,0 +1,43 @@
+---
+title: 在个人资料中公开或隐藏您的私人贡献
+intro: Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.
+redirect_from:
+- /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: Private contributions
+ms.openlocfilehash: d3ca9c3bef9324baa73b96eb6dc26bdd75960b37
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145066983"
+---
+如果公开您的私有贡献,对您处理的私有仓库没有访问权限的人员将无法查看您的私有贡献详情, 而只能看到您在指定日期的贡献数。 您的公共贡献会包含详细信息。 有关详细信息,请参阅“[查看个人资料页面上的贡献](/articles/viewing-contributions-on-your-profile-page)”。
+
+{% note %}
+
+**注意:** {% ifversion fpt or ghes or ghec %}在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %} 上,你的个人资料上的公共贡献{% ifversion fpt or ghec %}对世界上能访问 {% data variables.product.prodname_dotcom_the_website %} 的任何人{% elsif ghes %}仅对其他 {% data variables.product.product_location%} 用户{% endif %}可见。{% elsif ghae %}在 {% data variables.product.prodname_ghe_managed %} 上,只有你企业的其他成员才可看到你的个人资料上的贡献。{% endif %}
+
+{% endnote %}
+
+## 更改私有贡献的可见性
+
+{% data reusables.profile.access_profile %}
+1. 在个人资料中公开或隐藏您的私有贡献:
+ - 要公开你的私有贡献,在贡献图上方,使用“贡献设置”下拉菜单,然后选择“私有贡献” 。 访问者将会看到您的私有贡献数,但没有更多详细信息。
+ 
+ - 要隐藏你的私有贡献,在贡献图上方,使用“贡献设置”下拉菜单,然后取消选择“私有贡献” 。 访问者将只看到你的公共贡献。
+ 
+
+## 延伸阅读
+
+- “[在个人资料页中查看贡献](/articles/viewing-contributions-on-your-profile-page)”
+- “[为什么我的贡献未显示在我的个人资料上?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
new file mode 100644
index 0000000000..fbbc8f2df5
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md
@@ -0,0 +1,63 @@
+---
+title: 将企业贡献发送到您的 GitHub.com 个人资料
+intro: You can highlight your work on {% data variables.product.prodname_enterprise %} by sending the contribution counts to your {% data variables.product.prodname_dotcom_the_website %} profile.
+redirect_from:
+- /articles/sending-your-github-enterprise-contributions-to-your-github-com-profile
+- /articles/sending-your-github-enterprise-server-contributions-to-your-github-com-profile
+- /articles/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+- /github/setting-up-and-managing-your-github-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-your-github-enterprise-server-contributions-to-your-githubcom-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: Send enterprise contributions
+ms.openlocfilehash: 19b26c9e274b66df16434727e42c5c291bacfea7
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085058"
+---
+## 关于 {% data variables.product.prodname_dotcom_the_website %} 个人资料上的企业贡献
+
+您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料显示过去 90 天内 {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} 贡献计数。 {% data reusables.github-connect.sync-frequency %} {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} 的贡献计数被视为私人贡献。 提交详细信息将仅显示贡献计数,这些贡献是在 {% data variables.product.prodname_dotcom_the_website %} 以外的 {% data variables.product.prodname_enterprise %} 环境中进行的。
+
+您可以决定是否在个人资料中显示私人贡献的计数。 有关详细信息,请参阅“[在个人资料中公开或隐藏你的私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile/)”。
+
+有关如何计算贡献的详细信息,请参阅“[管理个人资料中的贡献图](/articles/managing-contribution-graphs-on-your-profile/)”。
+
+{% note %}
+
+**注意:**
+- 帐户之间的连接受 [GitHub 的隐私声明](/free-pro-team@latest/github/site-policy/github-privacy-statement/)约束,启用连接即表示用户同意 [GitHub 的服务条款](/free-pro-team@latest/github/site-policy/github-terms-of-service)。
+
+- 在将 {% ifversion fpt or ghec %}{% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} 配置文件连接到 {% data variables.product.prodname_dotcom_the_website %} 配置文件之前,企业所有者必须启用 {% data variables.product.prodname_github_connect %} 并启用环境之间的贡献共享。 有关详细信息,请与企业所有者联系。
+
+{% endnote %}
+
+## 将您的企业贡献发送到您的 {% data variables.product.prodname_dotcom_the_website %} 个人资料
+
+{% ifversion fpt or ghec %}
+
+- 若要将来自 {% data variables.product.prodname_ghe_server %} 的企业贡献发送到你的 {% data variables.product.prodname_dotcom_the_website %} 个人资料,请参阅 {% data variables.product.prodname_ghe_server %} 文档中的“[将企业贡献发送到你的 {% data variables.product.prodname_dotcom_the_website %} 个人资料](/enterprise-server/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。
+- 若要将来自 {% data variables.product.prodname_ghe_managed %} 的企业贡献发送到你的 {% data variables.product.prodname_dotcom_the_website %} 个人资料,请参阅 {% data variables.product.prodname_ghe_managed %} 文档中的“[将企业贡献发送到你的 {% data variables.product.prodname_dotcom_the_website %} 个人资料](/github-ae@latest/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。
+
+{% elsif ghes %}
+
+1. 登录到 {% data variables.product.prodname_ghe_server %} 和 {% data variables.product.prodname_dotcom_the_website %}。
+1. 在 {% data variables.product.prodname_ghe_server %} 任意页的右上角,单击个人资料照片,然后单击“设置”。
+  {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %}
+1. 查看 {% data variables.product.prodname_ghe_server %} 将从你的 {% data variables.product.prodname_dotcom_the_website %} 帐户访问的资源,然后单击“授权”。
+  {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
+
+{% elsif ghae %}
+
+1. 登录到 {% data variables.product.prodname_ghe_managed %} 和 {% data variables.product.prodname_dotcom_the_website %}。
+1. 在 {% data variables.product.prodname_ghe_managed %} 任意页的右上角,单击个人资料照片,然后单击“设置”。
+  {% data reusables.github-connect.github-connect-tab-user-settings %} {% data reusables.github-connect.connect-dotcom-and-enterprise %} {% data reusables.github-connect.authorize-connection %} {% data reusables.github-connect.send-contribution-counts-to-githubcom %}
+
+{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md
new file mode 100644
index 0000000000..1848f8ab00
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile.md
@@ -0,0 +1,29 @@
+---
+title: 在个人资料中显示活动概览
+intro: You can enable the activity overview section on your profile to give viewers more context about the types of contributions you make.
+redirect_from:
+- /articles/showing-an-overview-of-your-activity-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/showing-an-overview-of-your-activity-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/showing-an-overview-of-your-activity-on-your-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: Show an overview
+ms.openlocfilehash: a87650ceff7e49269f117a1dd9d8ab3c7b53dcce
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085057"
+---
+{% data reusables.profile.activity-overview-summary %} 有关更多信息,请参阅“[在个人资料中查看贡献](/articles/viewing-contributions-on-your-profile)”。
+
+
+
+{% data reusables.profile.access_profile %}
+2. 在贡献图上方,使用“贡献设置”下拉菜单,然后选择或取消选择“活动概述” 。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md
new file mode 100644
index 0000000000..4635fd2fd8
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline.md
@@ -0,0 +1,74 @@
+---
+title: 对时间表上的提交进行故障排除
+intro: You can view details for commits from your profile's timeline. If you don't see commits you expect on your profile or can't find commit details from your profile page, the commit date and the commit author date may be different.
+redirect_from:
+- /articles/troubleshooting-commits-on-your-timeline
+- /github/setting-up-and-managing-your-github-profile/troubleshooting-commits-on-your-timeline
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/troubleshooting-commits-on-your-timeline
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: Troubleshoot commits
+ms.openlocfilehash: 78adf6a92412c89180adeb49f7a5f446f7ce7f17
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085055"
+---
+## 查看提交详细信息的预期行为
+
+在个人资料页面的时间表中,您可以单击特定仓库旁边的提交数量,以查看关于该时间段内提交的更多详细信息,包括仓库中进行的特定更改的差异。
+
+
+
+
+
+## 时间表中的提交缺少提交详细信息
+
+如果单击个人资料页面中的提交链接而没有在仓库的提交页面上看到所有预期的提交,则可能会重写 Git 中的提交历史记录,并且提交创作日期和提交日期会不同。
+
+
+
+## GitHub 如何使用 Git 创作日期和提交日期
+
+在 Git 中,创作日期是有人首次使用 `git commit` 创建提交的时间。 除非有人使用 `git commit --amend`、强制推送、变基或其他 Git 命令更改提交日期,否则提交日期与创作日期相同。
+
+在个人资料页面上,创作日期用于计算进行提交的时间。 而在仓库中,提交日期用于计算在仓库中进行提交的时间。
+
+通常,创作日期和提交日期是相同的,但如果提交历史记录发生变化,您可能会注意到提交顺序将被打乱。 有关详细信息,请参阅“[为什么我的贡献没有在我的个人资料中显示?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
+
+## 查看时间表中提交缺少的提交详细信息
+
+可以将 `git show` 命令与 `--pretty=fuller` 标志一起使用,以检查提交创作日期和提交日期是否不同。
+
+```shell
+$ git show Your commit SHA number --pretty=fuller
+commit Your commit SHA number
+Author: octocat user email
+AuthorDate: Tue Apr 03 02:02:30 2018 +0900
+Commit: Sally Johnson user email
+CommitDate: Tue Apr 10 06:25:08 2018 +0900
+```
+
+如果创作和提交日期不同,您可以在 URL 中手动更改提交日期以查看提交详细信息。
+
+例如:
+- 以下 URL 使用的创作日期为 `2018-04-03`:
+
+ `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-03T00:00:00Z&until=2018-04-03T23:59:59Z`
+- 以下 URL 使用的提交日期为 `2018-04-10`:
+
+ `https://github.com/your-organization-or-personal-account/your-repository/commits?author=octocat&since=2018-04-10T00:00:00Z&until=2018-04-10T23:59:59Z`
+
+使用修改后的提交日期打开 URL 时,您可以看到提交详细信息。
+
+
+
+## 时间表中缺少预期的提交
+
+如果没有在时间表中看到预期的提交,则可能 Git 中的提交历史记录已重写,并且提交创作日期与提交日期不同。 有关其他可能性,请参阅“[为什么我的贡献没有在我的个人资料中显示?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
new file mode 100644
index 0000000000..0248315487
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile.md
@@ -0,0 +1,103 @@
+---
+title: 在个人资料中查看贡献
+intro: Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories as well as{% endif %} a graph of your repository contributions over the past year.
+redirect_from:
+- /articles/viewing-contributions
+- /articles/viewing-contributions-on-your-profile-page
+- /articles/viewing-contributions-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/viewing-contributions-on-your-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/viewing-contributions-on-your-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: View contributions
+ms.openlocfilehash: fccf691bc2fa865dd6ebcdebd112cbe6da02e0b5
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145098711"
+---
+{% ifversion fpt or ghes or ghec %} 贡献图显示公共存储库的活动。 {% endif %}可以选择显示 {% ifversion fpt or ghes or ghec %} 公共和 {% endif %} 私有存储库的活动,并将私有存储库中活动的具体详细信息匿名化。 有关详细信息,请参阅“[在配置文件中公开或隐藏私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。
+
+{% note %}
+
+注意:仅当用于创作提交的电子邮件地址与在 {% data variables.product.product_name %} 上的帐户相连时,提交才会显示在你的贡献图中。 有关详细信息,请参阅“[为什么我的贡献没有在我的配置文件中显示?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)”
+
+{% endnote %}
+
+## 计为贡献的内容
+
+在您的个人资料页面上,某些操作计为贡献:
+
+- 提交到存储库的默认分支或 `gh-pages` 分支
+- 创建问题
+- 打开讨论
+- 回答讨论
+- 提议拉取请求
+- 提交拉取请求审查 {% ifversion ghes or ghae %}
+- 合作创作存储库默认分支或 `gh-pages` 分支中的提交{% endif %}
+
+{% data reusables.pull_requests.pull_request_merges_and_contributions %}
+
+## 受欢迎的仓库
+
+此部分显示具有最多查看者的仓库。 {% ifversion fpt or ghes or ghec %}[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)后,此部分将更改为“固定的存储库”。{% endif %}
+
+
+
+{% ifversion fpt or ghes or ghec %}
+
+## 固定的仓库
+
+此部分显示最多六个公共仓库,并可包括您的仓库以及您对其做出贡献的仓库。 为便于查看关于你选择提供的存储库的重要详细信息,此部分中的每个存储库均包括所做工作的摘要、存储库已收到的[星号](/articles/saving-repositories-with-stars/)数量以及存储库中使用的主要编程语言。 有关详细信息,请参阅“[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)”。
+
+
+
+{% endif %}
+
+## 贡献日历
+
+您的贡献日历会显示贡献活动。
+
+### 查看特定时间的贡献
+
+- 单击某个日期的方块可显示该 24 小时期间内所做的贡献。
+- 按“Shift”并单击任意日期的方块可显示该时间范围内所做的贡献。
+
+{% note %}
+
+注意:可以在贡献日历中选择最多一个月的范围。 如果您选择更大的时间范围,我们将仅显示一个月的贡献。
+
+{% endnote %}
+
+
+
+### 如何计算贡献事件时间
+
+对于提交和拉取请求,时间戳的计算方式不同:
+- “提交”使用提交时间戳中的时区信息。 有关详细信息,请参阅“[排查日程表上的提交问题](/articles/troubleshooting-commits-on-your-timeline)”。
+- {% data variables.product.product_name %} 上打开的“拉取请求”和“议题”使用浏览器的时区 。 通过 API 打开的内容使用 [API 调用中指定的](https://developer.github.com/changes/2014-03-04-timezone-handling-changes)时间戳或时区。
+
+## 活动概述
+
+{% data reusables.profile.activity-overview-summary %} 有关详细信息,请参阅“[在配置文件中显示活动概览](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
+
+
+
+活动概览中提供的组织根据您在组织中的活跃程度确定优先级。 如果在配置文件简历中 @mention 某个组织,并且你是组织成员,则该组织首先在活动概览中确定优先级。 有关详细信息,请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”或“[将个人简介添加到配置文件](/articles/adding-a-bio-to-your-profile/)”。
+
+## 贡献活动
+
+贡献活动部分包括工作的详细时间表,包括您进行或合作的提交、您提议的拉取请求以及您打开的议题。 可通过单击贡献活动底部的“Show more activity(显示更多活动)”或通过在查看页面右侧时单击你感兴趣的年份来查看一段时间内你的贡献。 重要时刻(如您加入组织、提议第一个拉取请求或打开一个备受瞩目议题的日期)将在贡献活动中突出显示。 如果您在时间表中无法看到某些事件,请检查以确保您仍具有事件发生位置组织或仓库的访问权限。
+
+
+
+## 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.prodname_enterprise %} 中的贡献
+
+如果使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} 或 {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} 并且你的企业所有者启用 {% data variables.product.prodname_unified_contributions %},可以向 {% data variables.product.prodname_dotcom_the_website %} 配置文件发送企业贡献计数。 有关详细信息,请参阅“[将企业贡献发送到自己的 {% data variables.product.prodname_dotcom_the_website %} 配置文件](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。
+
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
new file mode 100644
index 0000000000..b445c459aa
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -0,0 +1,105 @@
+---
+title: 为什么我的贡献没有在我的个人资料中显示?
+intro: Learn common reasons that contributions may be missing from your contributions graph.
+redirect_from:
+- /articles/why-are-my-contributions-not-showing-up-on-my-profile
+- /github/setting-up-and-managing-your-github-profile/why-are-my-contributions-not-showing-up-on-my-profile
+- /github/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Profiles
+shortTitle: Missing contributions
+ms.openlocfilehash: c3921897284e16c979542c5f7629690ded2b841e
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145099743"
+---
+## 关于您的贡献图
+
+您的个人资料贡献图是您参与{% data variables.product.product_location %}{% ifversion ghae %}拥有{% else %}上{% endif %} 的存储库的记录。 贡献按照协调世界时 (UTC) 而不是您当地的时区加时间戳。 只有在满足特定标准时才会计算贡献。 在某些情况下,我们可能需要重建您的图表才能显示贡献。
+
+如果您是使用 SAML 单点登录 (SSO) 的组织的成员,则在没有活动的 SSO 会话时,您将无法在配置文件上看到来自该组织的贡献活动。 从组织外部查看您个人资料的用户将看到您组织的贡献活动的匿名贡献活动。
+
+## 计算的贡献
+
+### 议题、拉取请求和讨论
+
+如果议题、拉取请求和讨论在独立的仓库而不是复刻中打开,它们将在您的贡献图中显示。
+
+### 提交
+如果提交符合以下所有条件,则会在贡献图中显示:
+- 用于提交的电子邮件地址与您在 {% data variables.product.product_location %} 上的帐户关联。
+- 提交在独立的仓库而不是复刻中进行。
+- 提交在以下位置进行:
+ - 在仓库的默认分支中
+ - 在 `gh-pages` 分支(对于具有项目网站的存储库)中
+
+有关项目网站的详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。
+
+此外,以下至少一项必须为 true:
+- 您是仓库中的协作者,或者是拥有该仓库的组织的成员。
+- 您已复刻该仓库。
+- 您已打开仓库中的拉取请求或议题。
+- 您已为仓库加星标。
+
+## 贡献未计算的常见原因
+
+{% data reusables.pull_requests.pull_request_merges_and_contributions %}
+
+### 24 小时内进行的提交
+
+进行满足计为贡献要求的提交后,您可能需要等待最长 24 小时才能看到在贡献图中显示的贡献。
+
+### 您的本地 Git 提交电子邮件地址未连接到您的帐户
+
+提交必须使用与你在 {% data variables.product.product_location %}{% ifversion fpt or ghec %} 上的帐户连接的电子邮件地址进行,或者使用在电子邮件设置中提供给你的 {% data variables.product.prodname_dotcom %} 提供的 `noreply` 电子邮件地址进行,{% endif %}才能显示在你的贡献图上。{% ifversion fpt or ghec %} 有关 `noreply` 电子邮件地址的详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#about-commit-email-addresses)”。{% endif %}
+
+可以通过将 `.patch` 添加到提交 URL 的末尾(例如 https://github.com/octocat/octocat.github.io/commit/67c0afc1da354d8571f51b6f0af8f2794117fd10.patch)来检查用于提交的电子邮件地址:
+
+```
+From 67c0afc1da354d8571f51b6f0af8f2794117fd10 Mon Sep 17 00:00:00 2001
+From: The Octocat
+Date: Sun, 27 Apr 2014 15:36:39 +0530
+Subject: [PATCH] updated index for better welcome message
+```
+
+`From:` 字段中的电子邮件地址是在[本地 git 配置设置](/articles/set-up-git)中设置的地址。 在此示例中,用于提交的电子邮件地址为 `octocat@nowhere.com`。
+
+如果用于提交的电子邮件地址未连接到您的 {% data variables.product.product_location %} 帐户,{% ifversion ghae %}请更改用于在 Git 中创作提交的电子邮件地址。 有关详细信息,请参阅“[设置提交电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address#setting-your-commit-email-address-in-git)”。{% else %}必须[将电子邮件地址添加](/articles/adding-an-email-address-to-your-github-account)到 {% data variables.product.product_location %} 上的帐户。 您的贡献图将在添加新地址后自动重建。{% endif %}
+
+{% warning %}
+
+警告:通用电子邮件地址(如 `jane@computer.local`)无法添加到 {% data variables.product.prodname_dotcom %} 帐户。 如果为您的提交使用这类电子邮件,则提交不会链接到您的 {% data variables.product.prodname_dotcom %} 个人资料,并且不会在您的贡献图中显示。
+
+{% endwarning %}
+
+### 未在默认分支或 `gh-pages` 分支中执行提交
+
+仅发生在默认分支或 `gh-pages` 分支(对于包含项目网站的存储库)中的提交才会计入。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#types-of-github-pages-sites)”。
+
+如果提交位于非默认或非 `gh-pages` 分支中,并且你希望将其计入你的贡献,则需要执行以下操作之一:
+- [打开拉取请求](/articles/creating-a-pull-request),将更改合并到默认分支或 `gh-pages` 分支中。
+- [更改存储库的默认分支](/github/administering-a-repository/changing-the-default-branch)。
+
+{% warning %}
+
+警告:更改存储库的默认分支将会更改所有存储库协作者的默认分支。 仅当您希望新分支成为进行所有未来拉取请求和提交的基础时才执行此操作。
+
+{% endwarning %}
+
+### 提交在复刻中进行
+
+在复刻中进行的提交不会计入您的贡献。 要将其计入,您必须执行以下操作之一:
+- [打开拉取请求](/articles/creating-a-pull-request),将更改合并到父存储库中。
+- 要分离复刻并将其变为 {% data variables.product.product_location %} 上独立的仓库,请联系 {% data variables.contact.contact_support %}。 如果该复刻有自己的复刻,让 {% data variables.contact.contact_support %} 了解这些复刻是随您的仓库移入新网络还是留在当前网络中。 有关详细信息,请参阅“[关于分支](/articles/about-forks/)”。
+
+## 延伸阅读
+
+- [在个人资料中公开或隐藏你的私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)
+- [在个人资料页中查看贡献](/articles/viewing-contributions-on-your-profile-page)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
index e88e940a1c..8d844b851e 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md
@@ -1,6 +1,6 @@
---
-title: Showing your private contributions and achievements on your profile
-intro: 'Your {% data variables.product.product_name %} profile shows a graph of your repository contributions over the past year. You can choose to show anonymized activity from {% ifversion fpt or ghes or ghec %}private and internal{% else %}private{% endif %} repositories{% ifversion fpt or ghes or ghec %} in addition to the activity from public repositories{% endif %}.'
+title: 在个人资料上显示你的私有贡献和成就
+intro: '您的 {% data variables.product.product_name %} 个人资料显示过去一年中您的仓库贡献图。 除公共存储库{% endif %}中的活动外,还可选择显示{% ifversion fpt or ghes or ghec %}专用和内部{% else %}专用{% endif %}存储库{% ifversion fpt or ghes or ghec %}中的匿名活动。'
redirect_from:
- /articles/publicizing-or-hiding-your-private-contributions-on-your-profile
- /github/setting-up-and-managing-your-github-profile/publicizing-or-hiding-your-private-contributions-on-your-profile
@@ -14,42 +14,40 @@ versions:
topics:
- Profiles
shortTitle: Private contributions and achievements
+ms.openlocfilehash: b40e3835bf1548ff4ced75d1207de9a5b493dc90
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147079534'
---
-
-If you publicize your private contributions, people without access to the private repositories you work in won't be able to see the details of your private contributions. Instead, they'll see the number of private contributions you made on any given day. Your public contributions will include detailed information. For more information, see "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)."
+如果公开您的私有贡献,对您处理的私有仓库没有访问权限的人员将无法查看您的私有贡献详情, 而只能看到您在指定日期的贡献数。 您的公共贡献会包含详细信息。 有关详细信息,请参阅“[查看个人资料页面上的贡献](/articles/viewing-contributions-on-your-profile-page)”。
{% note %}
-**Note:** {% ifversion fpt or ghes or ghec %}On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %}, public contributions on your profile are visible {% ifversion fpt or ghec %}to anyone in the world who can access {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}only to other users of {% data variables.location.product_location%}{% endif %}.{% elsif ghae %}On {% data variables.product.prodname_ghe_managed %}, only other members of your enterprise can see the contributions on your profile.{% endif %}
+**注意:** {% ifversion fpt or ghes or ghec %}在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_name %}{% endif %} 上,你的个人资料上的公共贡献{% ifversion fpt or ghec %}对世界上能访问 {% data variables.product.prodname_dotcom_the_website %} 的任何人{% elsif ghes %}仅对其他 {% data variables.product.product_location%} 用户{% endif %}可见。{% elsif ghae %}在 {% data variables.product.prodname_ghe_managed %} 上,只有你企业的其他成员才可看到你的个人资料上的贡献。{% endif %}
{% endnote %}
-## Changing the visibility of your private contributions
+## 更改私有贡献的可见性
{% data reusables.profile.access_profile %}
-1. Publicize or hide your private contributions on your profile:
- - To publicize your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and select **Private contributions**. Visitors will see your private contribution counts without further details.
- 
- - To hide your private contributions, above your contributions graph, use the **Contribution settings** drop-down menu, and unselect **Private contributions.** Visitors will only see your public contributions.
- 
+1. 在个人资料中公开或隐藏您的私有贡献:
+ - 要公开你的私有贡献,在贡献图上方,使用“贡献设置”下拉菜单,然后选择“私有贡献” 。 访问者将会看到您的私有贡献数,但没有更多详细信息。
+ 
+ - 要隐藏你的私有贡献,在贡献图上方,使用“贡献设置”下拉菜单,然后取消选择“私有贡献” 。 访问者将只看到你的公共贡献。
+ 
-## Changing the visibility of Achievements
+## 更改成就的可见性
{% data reusables.user-settings.access_settings %}
-1. Show or hide Achievements on your profile:
- - To show Achievements on your profile, navigate to **Profile settings**, and select the checkbox next to **Show Achievements on my profile.**
- 
- - To hide Achievements from your profile, navigate to **Profile settings**, and unselect the checkbox next to **Show Achievements on my profile.**
- 
-{% ifversion hide-individual-achievements %}
-1. Optionally, to hide individual Achievements from your profile:
- {% data reusables.profile.access_profile %}
- 1. Navigate to the Achievements section on the left sidebar of your profile and select the Achievements header. 
- 2. Open the detail view of the achievement you'd like to hide by clicking on the achievement.
- 3. Once in the detail view, click the {% octicon "eye" aria-label="The eye icon" %} icon to hide the achievement.  When hidden, badges will be marked by the {% octicon "eye-closed" aria-label="The eye closed icon" %} icon and are only visible to you. 
+1. 在个人资料上显示或隐藏成就:
+ - 要在个人资料上显示成就,请导航到“个人资料设置”,然后选择“在我的个人资料上显示成就”旁边的复选框。
+ 
+ - 要在个人资料上隐藏成就,请导航到“个人资料设置”,然后取消选中“在我的个人资料上显示成就”旁边的复选框。
+ 
-{% endif %}
-## Further reading
+## 延伸阅读
-- "[Viewing contributions on your profile page](/articles/viewing-contributions-on-your-profile-page)"
-- "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)"
+- “[在个人资料页中查看贡献](/articles/viewing-contributions-on-your-profile-page)”
+- “[为什么我的贡献未显示在我的个人资料上?](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
index 5581d21cd0..8ee42c95d4 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md
@@ -1,6 +1,6 @@
---
-title: Viewing contributions on your profile
-intro: 'Your {% data variables.product.product_name %} profile shows off {% ifversion fpt or ghes or ghec %}your pinned repositories, Achievements, and{% endif %} a graph of your repository contributions over the past year.'
+title: 在个人资料中查看贡献
+intro: '你的 {% data variables.product.product_name %} 个人资料显示{% ifversion fpt or ghes or ghec %}你的固定存储库、成就和{% endif %}过去一年中存储库贡献的图。'
redirect_from:
- /articles/viewing-contributions
- /articles/viewing-contributions-on-your-profile-page
@@ -15,83 +15,89 @@ versions:
topics:
- Profiles
shortTitle: View contributions
+ms.openlocfilehash: 81b2242e0c7a07d8941375d044cacc65ca8dd56d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147079523'
---
-{% ifversion fpt or ghes or ghec %}Your contribution graph and Achievements show activity from public repositories. {% endif %}You can choose to show activity from {% ifversion fpt or ghes or ghec %}both public and {% endif %}private repositories, with specific details of your activity in private repositories anonymized. For more information, see "[Publicizing or hiding your private contributions on your profile](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)."
+{% ifversion fpt or ghes or ghec %}你的贡献图和“成就”显示公共存储库的活动。 {% endif %}可以选择显示 {% ifversion fpt or ghes or ghec %} 公共和 {% endif %} 私有存储库的活动,并将私有存储库中活动的具体详细信息匿名化。 有关详细信息,请参阅“[在配置文件中公开或隐藏私人贡献](/articles/publicizing-or-hiding-your-private-contributions-on-your-profile)”。
{% note %}
-**Note:** Commits will only appear on your contributions graph if the email address you used to author the commits is connected to your account on {% data variables.product.product_name %}. For more information, see "[Why are my contributions not showing up on my profile?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)"
+注意:仅当用于创作提交的电子邮件地址与在 {% data variables.product.product_name %} 上的帐户相连时,提交才会显示在你的贡献图中。 有关详细信息,请参阅“[为什么我的贡献没有在我的配置文件中显示?](/articles/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)”
{% endnote %}
-## What counts as a contribution
+## 计为贡献的内容
-On your profile page, certain actions count as contributions:
+在您的个人资料页面上,某些操作计为贡献:
-- Committing to a repository's default branch or `gh-pages` branch
-- Opening an issue
-- Opening a discussion
-- Answering a discussion
-- Proposing a pull request
-- Submitting a pull request review{% ifversion ghes or ghae %}
-- Co-authoring commits in a repository's default branch or `gh-pages` branch{% endif %}
+- 提交到存储库的默认分支或 `gh-pages` 分支
+- 创建问题
+- 打开讨论
+- 回答讨论
+- 提议拉取请求
+- 提交拉取请求审查 {% ifversion ghes or ghae %}
+- 合作创作存储库默认分支或 `gh-pages` 分支中的提交{% endif %}
{% data reusables.pull_requests.pull_request_merges_and_contributions %}
-## Popular repositories
+## 受欢迎的仓库
-This section displays your repositories with the most watchers. {% ifversion fpt or ghes or ghec %}Once you [pin repositories to your profile](/articles/pinning-repositories-to-your-profile), this section will change to "Pinned repositories."{% endif %}
+此部分显示具有最多查看者的仓库。 {% ifversion fpt or ghes or ghec %}[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)后,此部分将更改为“固定的存储库”。{% endif %}
-
+
{% ifversion fpt or ghes or ghec %}
-## Pinned repositories
+## 固定的仓库
-This section displays up to six public repositories and can include your repositories as well as repositories you've contributed to. To easily see important details about the repositories you've chosen to feature, each repository in this section includes a summary of the work being done, the number of [stars](/articles/saving-repositories-with-stars/) the repository has received, and the main programming language used in the repository. For more information, see "[Pinning repositories to your profile](/articles/pinning-repositories-to-your-profile)."
+此部分显示最多六个公共仓库,并可包括您的仓库以及您对其做出贡献的仓库。 为便于查看关于你选择提供的存储库的重要详细信息,此部分中的每个存储库均包括所做工作的摘要、存储库已收到的[星号](/articles/saving-repositories-with-stars/)数量以及存储库中使用的主要编程语言。 有关详细信息,请参阅“[将存储库固定到配置文件](/articles/pinning-repositories-to-your-profile)”。
-
+
{% endif %}
-## Contributions calendar
+## 贡献日历
-Your contributions calendar shows your contribution activity.
+您的贡献日历会显示贡献活动。
-### Viewing contributions from specific times
+### 查看特定时间的贡献
-- Click on a day's square to show the contributions made during that 24-hour period.
-- Press *Shift* and click on another day's square to show contributions made during that time span.
+- 单击某个日期的方块可显示该 24 小时期间内所做的贡献。
+- 按“Shift”并单击任意日期的方块可显示该时间范围内所做的贡献。
{% note %}
-**Note:** You can select up to a one-month range on your contributions calendar. If you select a larger time span, we will only display one month of contributions.
+注意:可以在贡献日历中选择最多一个月的范围。 如果您选择更大的时间范围,我们将仅显示一个月的贡献。
{% endnote %}
-
+
-### How contribution event times are calculated
+### 如何计算贡献事件时间
-Timestamps are calculated differently for commits and pull requests:
-- **Commits** use the time zone information in the commit timestamp. For more information, see "[Troubleshooting commits on your timeline](/articles/troubleshooting-commits-on-your-timeline)."
-- **Pull requests** and **issues** opened on {% data variables.product.product_name %} use your browser's time zone. Those opened via the API use the timestamp or time zone [specified in the API call](https://developer.github.com/changes/2014-03-04-timezone-handling-changes).
+对于提交和拉取请求,时间戳的计算方式不同:
+- “提交”使用提交时间戳中的时区信息。 有关详细信息,请参阅“[排查日程表上的提交问题](/articles/troubleshooting-commits-on-your-timeline)”。
+- {% data variables.product.product_name %} 上打开的“拉取请求”和“议题”使用浏览器的时区 。 通过 API 打开的内容使用 [API 调用中指定的](https://developer.github.com/changes/2014-03-04-timezone-handling-changes)时间戳或时区。
-## Activity overview
+## 活动概述
-{% data reusables.profile.activity-overview-summary %} For more information, see "[Showing an overview of your activity on your profile](/articles/showing-an-overview-of-your-activity-on-your-profile)."
+{% data reusables.profile.activity-overview-summary %} 有关详细信息,请参阅“[在配置文件中显示活动概览](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
-
+
-The organizations featured in the activity overview are prioritized according to how active you are in the organization. If you @mention an organization in your profile bio, and you’re an organization member, then that organization is prioritized first in the activity overview. For more information, see "[Mentioning people and teams](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)" or "[Adding a bio to your profile](/articles/adding-a-bio-to-your-profile/)."
+活动概览中提供的组织根据您在组织中的活跃程度确定优先级。 如果在配置文件简历中 @mention 某个组织,并且你是组织成员,则该组织首先在活动概览中确定优先级。 有关详细信息,请参阅“[提及人员和团队](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)”或“[将个人简介添加到配置文件](/articles/adding-a-bio-to-your-profile/)”。
-## Contribution activity
+## 贡献活动
-The contribution activity section includes a detailed timeline of your work, including commits you've made or co-authored, pull requests you've proposed, and issues you've opened. You can see your contributions over time by either clicking **Show more activity** at the bottom of your contribution activity or by clicking the year you're interested in viewing on the right side of the page. Important moments, like the date you joined an organization, proposed your first pull request, or opened a high-profile issue, are highlighted in your contribution activity. If you can't see certain events in your timeline, check to make sure you still have access to the organization or repository where the event happened.
+贡献活动部分包括工作的详细时间表,包括您进行或合作的提交、您提议的拉取请求以及您打开的议题。 可通过单击贡献活动底部的“Show more activity(显示更多活动)”或通过在查看页面右侧时单击你感兴趣的年份来查看一段时间内你的贡献。 重要时刻(如您加入组织、提议第一个拉取请求或打开一个备受瞩目议题的日期)将在贡献活动中突出显示。 如果您在时间表中无法看到某些事件,请检查以确保您仍具有事件发生位置组织或仓库的访问权限。
-
+
-## Viewing contributions from {% data variables.product.prodname_enterprise %} on {% data variables.product.prodname_dotcom_the_website %}
+## 在 {% data variables.product.prodname_dotcom_the_website %} 上查看 {% data variables.product.prodname_enterprise %} 中的贡献
-If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} or {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} and your enterprise owner enables {% data variables.enterprise.prodname_unified_contributions %}, you can send enterprise contribution counts from to your {% data variables.product.prodname_dotcom_the_website %} profile. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+如果使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_server %}{% ifversion ghae %} 或 {% data variables.product.prodname_ghe_managed %}{% endif %}{% else %}{% data variables.product.product_name %}{% endif %} 并且你的企业所有者启用 {% data variables.product.prodname_unified_contributions %},可以向 {% data variables.product.prodname_dotcom_the_website %} 配置文件发送企业贡献计数。 有关详细信息,请参阅“[将企业贡献发送到自己的 {% data variables.product.prodname_dotcom_the_website %} 配置文件](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)”。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md
new file mode 100644
index 0000000000..772ee7395a
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/index.md
@@ -0,0 +1,26 @@
+---
+title: 设置和管理 GitHub 用户帐户
+intro: You can manage settings in your GitHub personal account including email preferences, collaborator access for personal repositories, and organization memberships.
+shortTitle: Personal accounts
+redirect_from:
+- /categories/setting-up-and-managing-your-github-user-account
+- /github/setting-up-and-managing-your-github-user-account
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+children:
+- /managing-user-account-settings
+- /managing-email-preferences
+- /managing-access-to-your-personal-repositories
+- /managing-your-membership-in-organizations
+ms.openlocfilehash: 36e4d1280fdc48a7165199e40830417904ae1790
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085080"
+---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
new file mode 100644
index 0000000000..1c3f983db6
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md
@@ -0,0 +1,30 @@
+---
+title: 管理对个人仓库的访问
+intro: You can give people collaborator access to repositories owned by your personal account.
+redirect_from:
+- /categories/101/articles
+- /categories/managing-repository-collaborators
+- /articles/managing-access-to-your-personal-repositories
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Repositories
+children:
+- /inviting-collaborators-to-a-personal-repository
+- /removing-a-collaborator-from-a-personal-repository
+- /removing-yourself-from-a-collaborators-repository
+- /maintaining-ownership-continuity-of-your-user-accounts-repositories
+shortTitle: Access to your repositories
+ms.openlocfilehash: fd4ab3f5e29b35c1a222287471a2b310d0240322
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087339"
+---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
new file mode 100644
index 0000000000..920e22c853
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -0,0 +1,65 @@
+---
+title: 邀请协作者参加个人仓库
+intro: You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.
+redirect_from:
+- /articles/how-do-i-add-a-collaborator
+- /articles/adding-collaborators-to-a-personal-repository
+- /articles/inviting-collaborators-to-a-personal-repository
+- /github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Repositories
+shortTitle: Invite collaborators
+ms.openlocfilehash: 6db661abfc48b87ae7eae2c515be2e14e3717ec4
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085079"
+---
+组织拥有的仓库可授予更细致的访问权限。 有关详细信息,请参阅“[对 {% data variables.product.prodname_dotcom %} 的访问权限](/articles/access-permissions-on-github)”。
+
+{% data reusables.organizations.org-invite-expiration %}
+
+{% ifversion fpt or ghec %}
+
+如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则只能邀请企业的其他成员与您协作。 {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% note %}
+
+注意:{% data variables.product.company_short %} 会限制在 24 小时内可受邀加入存储库的人数。 如果您超过此限制,请等待 24 小时后再邀请,或者创建一个组织以与更多的人协作。
+
+{% endnote %}
+
+{% endif %}
+
+1. 询问你邀请作为协助者的用户名。{% ifversion fpt or ghec %} 如果他们还没有用户名,他们可以注册 {% data variables.product.prodname_dotcom %}。有关详细信息,请参阅“[注册新的 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%} {% data reusables.repositories.click-collaborators-teams %}
+1. 单击“邀请协作者”。
+ 
+2. 在搜索字段中,开始键入您想邀请的人员的姓名,然后单击匹配列表中的姓名。
+ 
+3. 单击“将 添加到存储库”。
+  {% else %}
+5. 在左侧边栏中,单击“协作者”。
+
+6. 在 "Collaborators"(协作者)下,开始输入协作者的用户名。
+7. 从下拉菜单中选择协作者的用户名。
+ 
+8. 单击“添加协作者”。
+  {% endif %} {% ifversion fpt or ghec %}
+9. 用户将会收到一封邀请他们参加仓库的电子邮件。 在接受邀请后,他们便对仓库具有协作者访问权限。
+{% endif %}
+
+## 延伸阅读
+
+- “[个人帐户存储库的权限级别](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account)”
+- [从个人存储库中删除协作者](/articles/removing-a-collaborator-from-a-personal-repository)
+- [从协作者的存储库中删除你自己](/articles/removing-yourself-from-a-collaborator-s-repository)
+- [将成员组织为团队](/organizations/organizing-members-into-teams)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
new file mode 100644
index 0000000000..8baed36585
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories.md
@@ -0,0 +1,44 @@
+---
+title: 保持用户帐户仓库的所有权连续性
+intro: You can invite someone to manage your user owned repositories if you are not able to.
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Repositories
+redirect_from:
+- /github/setting-up-and-managing-your-github-user-account/maintaining-ownership-continuity-of-your-user-accounts-repositories
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-user-accounts-repositories
+shortTitle: Ownership continuity
+ms.openlocfilehash: f958e3ca640a1180db03361457ec7c185e4ce7ba
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085078"
+---
+## 关于继承者
+
+如果您无法管理您的用户拥有的仓库,建议邀请其他 {% data variables.product.company_short %} 用户作为继承者管理。 作为继承者,他们拥有以下权限:
+
+- 存档您的公共仓库。
+- 将公共仓库转移到他们自己的用户拥有的帐户。
+- 将您的公共仓库转移到他们可在其中创建仓库的组织。
+
+继承者不能登录到您的帐户。
+
+指定的继承者在提交死亡证明并等待 7 天或者提交讣告并等待 21 天后,便可管理您的公共仓库。 有关详细信息,请参阅“[{% data variables.product.company_short %} 已故用户政策](/free-pro-team@latest/github/site-policy/github-deceased-user-policy)”。
+
+要请求作为继承者管理存储库,请联系 [GitHub 支持](https://support.github.com/contact?tags=docs-accounts)。
+
+## 邀请继承者
+您邀请作为继承者的人必须拥有 {% data variables.product.company_short %} 帐户。
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %}
+3. 要邀请继承者,在“Successor settings(继承者设置)”下开始输入用户名、全名或电子邮件地址,然后单击出现的姓名。
+ 
+4. 单击“添加继承者”。
+{% data reusables.user-settings.sudo-mode-popup %}
+5. 您邀请的用户将被列为“Pending(待定)”,直到他们同意成为您的继承者。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
new file mode 100644
index 0000000000..98b0017e90
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -0,0 +1,47 @@
+---
+title: 从个人仓库中删除协作者
+intro: When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.
+redirect_from:
+- /articles/how-do-i-remove-a-collaborator
+- /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
+- /articles/removing-a-collaborator-from-a-private-repository
+- /articles/deleting-a-private-fork-of-a-private-user-repository
+- /articles/how-do-i-delete-a-fork-of-my-private-repository
+- /articles/removing-a-collaborator-from-a-personal-repository
+- /github/setting-up-and-managing-your-github-user-account/removing-a-collaborator-from-a-personal-repository
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository
+product: '{% data reusables.gated-features.user-repo-collaborators %}'
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Repositories
+shortTitle: Remove a collaborator
+ms.openlocfilehash: eafe4f8bb1cea085910179a95f17c0b4a1358ad2
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087340"
+---
+## 删除私有仓库的复刻
+
+尽管删除协作者时将删除私有仓库的复刻,但此人员将仍保留您仓库的任何本地克隆。
+
+## 删除为仓库做出贡献的人员的协作者权限
+
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %}
+4. 在要移除的协作者的右侧,单击 {% octicon "trash" aria-label="The trash icon" %}。
+  {% else %}
+3. 在左侧边栏中,单击“协作者和团队”。
+ 
+4. 在要移除的协作者旁边,单击“X”图标。
+  {% endif %}
+
+## 延伸阅读
+
+- [从团队中移除组织成员](/articles/removing-organization-members-from-a-team)
+- [从组织存储库中移除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
new file mode 100644
index 0000000000..e80e3ab9e7
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -0,0 +1,36 @@
+---
+title: 从协作者的仓库中删除您自己
+intro: If you no longer want to be a collaborator on someone else's repository, you can remove yourself.
+redirect_from:
+- /leave-a-collaborative-repo
+- /leave-a-repo
+- /articles/removing-yourself-from-a-collaborator-s-repo
+- /articles/removing-yourself-from-a-collaborator-s-repository
+- /articles/removing-yourself-from-a-collaborators-repository
+- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Repositories
+shortTitle: Remove yourself
+ms.openlocfilehash: dc9739d84d1794e3111f3b61e0dfd9a7c4bec11b
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085075"
+---
+{% data reusables.user-settings.access_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+2. 在边栏的“代码、规划和自动化”部分,单击“{% octicon "repo" aria-label="The repo icon" %} 存储库”。
+{% else %}
+2. 在左侧边栏中,单击“存储库”。
+  {% endif %}
+3. 在要离开的存储库旁边,单击“离开”。
+ 
+4. 仔细阅读警告,然后单击“I understand, leave this repository(我已了解,离开此仓库)”。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md
new file mode 100644
index 0000000000..5c59ec7fc5
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account.md
@@ -0,0 +1,39 @@
+---
+title: 添加电子邮件地址到 GitHub 帐户
+intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."'
+redirect_from:
+- /articles/adding-an-email-address-to-your-github-account
+- /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/adding-an-email-address-to-your-github-account
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Add an email address
+ms.openlocfilehash: 3d7efd2e72ed1ab23ccf2e686f4a1c1c7653cc1f
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087335"
+---
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+**注释**:
+ - {% data reusables.user-settings.no-verification-disposable-emails %}
+ - 如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则无法在 {% data variables.product.prodname_dotcom_the_website %} 上更改您的电子邮件地址。 {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endnote %}
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}
+
+## 延伸阅读
+
+- [管理电子邮件首选项](/articles/managing-email-preferences/)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md
new file mode 100644
index 0000000000..b0559ee079
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address.md
@@ -0,0 +1,32 @@
+---
+title: 阻止会暴露个人电子邮件地址的命令行推送
+intro: If you've chosen to keep your email address private when performing web-based operations, you can also choose to block command line pushes that may expose your personal email address.
+redirect_from:
+- /articles/blocking-command-line-pushes-that-expose-your-personal-email-address
+- /github/setting-up-and-managing-your-github-user-account/blocking-command-line-pushes-that-expose-your-personal-email-address
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/blocking-command-line-pushes-that-expose-your-personal-email-address
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Block push with personal email
+ms.openlocfilehash: e085c19339cc530537626d9bf987125aebfd3427
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085074"
+---
+从命令行推送提交时,[在 Git 中设置](/articles/setting-your-commit-email-address)的电子邮件地址与提交相关联。 如果您启用此设置,则每当您推送到 GitHub 时,我们将检查最近的提交。 如果提交的作者电子邮件地址是您的 GitHub 帐户上的私人电子邮件地址,我们将阻止推送并警告这样会暴露您的私人电子邮件地址。
+
+{% data reusables.user-settings.about-commit-email-addresses %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.keeping_your_email_address_private %}
+4. 要使你的电子邮件地址在你通过命令行推送的提交中保持私密,请选择阻止会公开个人电子邮件地址的命令行推送。
+
+
+## 延伸阅读
+
+- [设置提交电子邮件地址](/articles/setting-your-commit-email-address)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md
new file mode 100644
index 0000000000..719646474b
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address.md
@@ -0,0 +1,37 @@
+---
+title: 更改主电子邮件地址
+intro: You can change the email address associated with your personal account at any time.
+redirect_from:
+- /articles/changing-your-primary-email-address
+- /github/setting-up-and-managing-your-github-user-account/changing-your-primary-email-address
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/changing-your-primary-email-address
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Primary email address
+ms.openlocfilehash: af1443f1f23b8038d2cf1f4e42a1ab0a83214edb
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087332"
+---
+{% note %}
+
+注意:不能将主电子邮件地址更改为已设置为备份电子邮件地址的电子邮件。
+
+{% endnote %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %}
+3. 如果要添加新电子邮件地址以设置为主电子邮件地址,请在“添加电子邮件地址”下键入新电子邮件地址,然后单击“添加”。
+ 
+4. 在“主要电子邮件地址”下,使用下拉菜单单击要设置为主电子邮件地址的电子邮件地址,然后单击“保存”。
+ 
+5. 要从帐户删除旧电子邮件地址,请在旧电子邮件地址旁边,单击 {% octicon "trash" aria-label="The trash symbol" %}。
+{% ifversion fpt or ghec %}
+6. 验证新的主电子邮件地址。 如果没有经验证的电子邮件地址,您将无法使用 {% data variables.product.product_name %} 的所有功能。 有关详细信息,请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。
+{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
new file mode 100644
index 0000000000..ee4aa65a8c
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md
@@ -0,0 +1,32 @@
+---
+title: 管理电子邮件首选项
+intro: You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.
+redirect_from:
+- /categories/managing-email-preferences
+- /articles/managing-email-preferences
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+children:
+- /adding-an-email-address-to-your-github-account
+- /changing-your-primary-email-address
+- /setting-a-backup-email-address
+- /setting-your-commit-email-address
+- /blocking-command-line-pushes-that-expose-your-personal-email-address
+- /remembering-your-github-username-or-email
+- /types-of-emails-github-sends
+- /managing-marketing-emails-from-github
+shortTitle: Manage email preferences
+ms.openlocfilehash: ec9c71468c235b07a3e4588c33d791f25e50d7d8
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085073"
+---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md
new file mode 100644
index 0000000000..1db919078c
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github.md
@@ -0,0 +1,39 @@
+---
+title: 管理来自 GitHub 的营销电子邮件
+intro: In addition to notifications and account emails, {% data variables.product.prodname_dotcom %} occasionally sends marketing emails with news and information about our products. If you unsubscribe from existing marketing emails, you won't be included in future campaigns unless you change your {% data variables.product.prodname_dotcom %} email settings.
+redirect_from:
+- /articles/managing-marketing-emails-from-github
+- /github/setting-up-and-managing-your-github-user-account/managing-marketing-emails-from-github
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/managing-marketing-emails-from-github
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Marketing emails
+ms.openlocfilehash: e7563a5c35ea60b63fb4b8aa1393e7cec8635781
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087331"
+---
+## 退订 {% data variables.product.prodname_dotcom %} 营销电子邮件
+
+{% tip %}
+
+提示:如果退订所有营销电子邮件,然后订阅 Explore 通讯,只会收到 Explore 通讯,而不会收到其他营销电子邮件。
+
+{% endtip %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %}
+3. 在“电子邮件首选项”下,选择“只接收帐户相关的电子邮件和我订阅的电子邮件”。
+ 
+4. 单击“保存电子邮件首选项”。
+ 
+
+## 延伸阅读
+
+- [GitHub 发送的电子邮件类型](/articles/types-of-emails-github-sends)
+- [配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
new file mode 100644
index 0000000000..0044010291
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -0,0 +1,80 @@
+---
+title: 记住您的 GitHub 用户名或电子邮件
+intro: Are you signing in to {% data variables.product.product_location %} for the first time in a while? If so, welcome back! If you can't remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.
+redirect_from:
+- /articles/oh-noes-i-ve-forgotten-my-username-email
+- /articles/oh-noes-i-ve-forgotten-my-username-or-email
+- /articles/remembering-your-github-username-or-email
+- /github/setting-up-and-managing-your-github-user-account/remembering-your-github-username-or-email
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/remembering-your-github-username-or-email
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Find your username or email
+ms.openlocfilehash: 79cb3ba65390e384272540bd32a1ec9e598517f4
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085072"
+---
+{% mac %}
+
+## {% data variables.product.prodname_desktop %} 用户
+
+1. 在“GitHub 桌面”菜单中,单击“首选项” 。
+2. 在 Preferences(首选项)窗口中,验证以下内容:
+ - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。
+ - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
+
+{% endmac %}
+
+{% windows %}
+
+## {% data variables.product.prodname_desktop %} 用户
+
+1. 在“文件”菜单中,单击“选项” 。
+2. 在 Options(选项)窗口中,验证以下内容:
+ - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。
+ - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
+
+{% endwindows %}
+
+## 在 `user.name` 配置中查找用户名
+
+在设置期间,你可能已[在 Git 中设置用户名](/github/getting-started-with-github/setting-your-username-in-git)。 如果这样,您可以查看此配置设置的值:
+
+```shell
+$ git config user.name
+# View the setting
+YOUR_USERNAME
+```
+
+## 在远程仓库的 URL 中查找您的用户名
+
+如果您有已创建或已复刻的个人仓库的任何本地副本,则可以检查远程仓库的 URL。
+
+{% tip %}
+
+提示:此方法仅当你拥有原始存储库或其他人存储库中你自己的分叉时才有效。 如果您克隆其他人的仓库,将显示他们的用户名而不是您的用户名。 类似地,组织仓库将显示组织的名称,而不是远程 URL 中的特定用户。
+
+{% endtip %}
+
+```shell
+$ cd YOUR_REPOSITORY
+# Change directories to the initialized Git repository
+$ git remote -v
+origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch)
+origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push)
+```
+
+用户名紧跟在 `https://{% data variables.command_line.backticks %}/` 后。
+
+{% ifversion fpt or ghec %}
+## 延伸阅读
+
+- “[验证电子邮件地址](/articles/verifying-your-email-address)”{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md
new file mode 100644
index 0000000000..8220b890ff
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address.md
@@ -0,0 +1,32 @@
+---
+title: 设置备用电子邮件地址
+intro: Use a backup email address as an additional destination for security-relevant account notifications{% ifversion not ghae %} and to securely reset your password if you can no longer access your primary email address{% endif %}.
+redirect_from:
+- /articles/setting-a-backup-email-address
+- /github/setting-up-and-managing-your-github-user-account/setting-a-backup-email-address
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-a-backup-email-address
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Set backup email address
+ms.openlocfilehash: 735e78c8f9e58dd6f6fea0f7c81334d8d8206d5a
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087328"
+---
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %}
+3. 在“Backup email address(备用电子邮件地址)”下,使用下拉菜单选择您要设置为备用电子邮件地址的地址。
+
+4. 单击“ **保存**”。
+
+## 延伸阅读
+
+- [管理电子邮件首选项](/articles/managing-email-preferences/)
+- [更新 GitHub 访问凭据](/articles/updating-your-github-access-credentials/)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
new file mode 100644
index 0000000000..cb1ddecbab
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md
@@ -0,0 +1,106 @@
+---
+title: 设置提交电子邮件地址
+intro: You can set the email address that is used to author commits on {% data variables.product.product_location %} and on your computer.
+redirect_from:
+- /articles/keeping-your-email-address-private
+- /articles/setting-your-commit-email-address-on-github
+- /articles/about-commit-email-addresses
+- /articles/git-email-settings
+- /articles/setting-your-email-in-git
+- /articles/set-your-user-name-email-and-github-token
+- /articles/setting-your-commit-email-address-in-git
+- /articles/setting-your-commit-email-address
+- /github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Set commit email address
+ms.openlocfilehash: da47c240cc53e18d5f5537f20dd8c1eb2f4127bf
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085070"
+---
+## 关于提交电子邮件地址
+
+{% data variables.product.prodname_dotcom %} 使用您的提交电子邮件地址将提交与您的 {% data variables.product.product_location %} 关联。 您可以选择要与从命令行以及基于 web 的 Git 操作推送的提交相关联的电子邮件地址。
+
+对于基于 Web 的 Git 操作,您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上设置提交电子邮件地址。 对于从命令行推送的提交,您可以在 Git 中设置提交电子邮件地址。
+
+{% ifversion fpt or ghec %} 在更改提交电子邮件地址之前进行的提交仍与之前的电子邮件地址关联。{% else %} 在 {% data variables.product.product_name %} 上更改提交电子邮件地址后,新电子邮件地址默认在所有未来基于 Web 的 Git 操作中可见。 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+注意:{% data reusables.user-settings.no-verification-disposable-emails %}
+
+{% endnote %}
+
+{% endif %}
+
+{% ifversion fpt or ghec %} 如果想将个人电子邮件地址设为私密,则可以使用 {% data variables.product.product_name %} 的 `no-reply` 电子邮件地址作为提交电子邮件地址。 要将 `noreply` 电子邮件地址用于从命令行推送的提交,请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 Web 的 Git 操作,请在 GitHub 上设置提交电子邮件地址并选择“对我的电子邮件地址保密”。
+
+您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 有关详细信息,请参阅“[阻止会暴露个人电子邮件的命令行推送](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)。”{% endif %}
+
+为确保提交归因于你并且出现在你的贡献图中,请使用已连接到你在 {% data variables.product.product_location %} 上的帐户的电子邮件地址{% ifversion fpt or ghec %},或者在电子邮件设置中提供给你的 `noreply` 电子邮件地址{% endif %}。 {% ifversion not ghae %} 有关详细信息,请参阅“[将电子邮件地址添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)”。{% endif %}
+
+{% ifversion fpt or ghec %}
+
+{% note %}
+
+注意:如果于 2017 年 7 月 18 日之后在 {% data variables.product.product_location %} 上创建了帐户,则用于 {% data variables.product.product_name %} 的 `no-reply` 电子邮件地址是一个七位数的 ID 号以及格式为 ID+username@users.noreply.github.com 的用户名。 如果于 2017 年 7 月 18 日之前在 {% data variables.product.product_location %} 上创建了帐户,则来自 {% data variables.product.product_name %} 的 `no-reply` 电子邮件地址是 username@users.noreply.github.com。 可以通过在电子邮件设置中选择(或取消选择并重新选择)“对我的电子邮件地址保密”,为 {% data variables.product.product_name %} 获取基于 ID 的 `no-reply` 电子邮件地址。
+
+{% endnote %}
+
+如果使用 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址进行提交,然后[更改用户名](/articles/changing-your-github-username),则这些提交将不会与你在 {% data variables.product.product_location %} 上的帐户相关联。 如果使用的是基于 ID 的 {% data variables.product.product_name %} `noreply` 地址,则不适用。 有关详细信息,请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)。”{% endif %}
+
+## 在 {% data variables.product.prodname_dotcom %} 上设置提交电子邮件地址
+
+{% data reusables.files.commit-author-email-options %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} {% data reusables.user-settings.keeping_your_email_address_private %}{% endif %}
+
+## 在 Git 中设置您的提交电子邮件地址
+
+可以使用 `git config` 命令更改与 Git 提交关联的电子邮件地址。 设置的新电子邮件地址将在从命令行推送到 {% data variables.product.product_location %} 的任何未来提交中显示。 在您更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。
+
+### 为计算机上的每个仓库设置电子邮件地址
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. {% data reusables.user-settings.set_your_email_address_in_git %}
+ ```shell
+ $ git config --global user.email "email@example.com"
+ ```
+3. {% data reusables.user-settings.confirm_git_email_address_correct %}
+ ```shell
+ $ git config --global user.email
+ email@example.com
+ ```
+4. {% data reusables.user-settings.link_email_with_your_account %}
+
+### 为一个仓库设置电子邮件地址
+
+{% data variables.product.product_name %} 使用在您的本地 Git 配置中设置的电子邮件地址将从命令行推送的提交与您在 {% data variables.product.product_location %} 上的帐户相关联。
+
+您可以更改与您在一个仓库中所进行的提交关联的电子邮件地址。 此操作将覆盖这一个仓库中的全局 Git 配置设置,但不会影响任何其他仓库。
+
+{% data reusables.command_line.open_the_multi_os_terminal %}
+2. 将当前工作目录更改为您想要在其中配置与 Git 提交关联的电子邮件地址的本地仓库。
+3. {% data reusables.user-settings.set_your_email_address_in_git %}
+ ```shell
+ $ git config user.email "email@example.com"
+ ```
+4. {% data reusables.user-settings.confirm_git_email_address_correct %}
+ ```shell
+ $ git config user.email
+ email@example.com
+ ```
+5. {% data reusables.user-settings.link_email_with_your_account %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md
new file mode 100644
index 0000000000..f9b7172675
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends.md
@@ -0,0 +1,59 @@
+---
+title: GitHub 发送的电子邮件类型
+intro: There are several types of emails you can receive from {% data variables.product.product_name %}, including notifications, account information, customer research invitations, and marketing communications.
+redirect_from:
+- /articles/types-of-emails-github-sends
+- /github/setting-up-and-managing-your-github-user-account/types-of-emails-github-sends
+- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences/types-of-emails-github-sends
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+- Notifications
+shortTitle: Emails from GitHub
+ms.openlocfilehash: e06708966ccd9f33564985e7964409fd1e1c55eb
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087327"
+---
+## 通知电子邮件
+
+您可以选择通过电子邮件接收部分或全部活动通知。 有关详细信息,请参阅“[关于通知](/github/managing-subscriptions-and-notifications-on-github/about-notifications)”。 通知电子邮件可包括:
+
+- 您具有管理员访问权限的仓库的安全相关活动
+- 您正在查看的仓库的活动
+- 您正在参与的对话
+- 你被 @mentioned 的对话
+- 您正在参与的拉取请求的推送
+- 要在组织或仓库中协作的邀请
+- 您自己的活动,例如打开、评论或关闭议题和拉取请求
+
+您还可以在您正在参与或观看的对话中选择希望接收哪种类型的电子邮件更新。 有关详细信息,请参阅“[配置通知](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications)”。
+
+## 帐户电子邮件
+
+如果您已升级为付费产品或功能,则将在帐户的主电子邮件地址收到帐单收据。 有关详细信息,请参阅“[设置计费电子邮件](/articles/setting-your-billing-email)”。
+
+## 客户研究电子邮件
+
+{% data variables.product.product_name %} 有时会寻求客户参加研究会议,以帮助我们构建更好的 GitHub。 这些会议是远程进行的,对世界各地的客户开放,可能包括:
+
+- 反馈调查
+- 研究访谈
+- 可用性测试会议
+- 预览早期原型或概念
+
+这些电子邮件并不常见,您可以选择是否参与。 如果您对参加研究会议的机会感兴趣,您可以加入 GitHub 客户研究小组。 有关详细信息,请参阅“[GitHub 客户体验研究](https://cxr.github.com)”。
+
+## 营销电子邮件
+
+{% data variables.product.product_name %} 偶尔会发送以下类型的营销电子邮件:
+
+- 使用帐户的提示和技巧
+- 有关参与项目或新功能的自定义信息
+- 您订阅的简报,例如 {% data variables.explore.explore_github %}
+
+有关详细信息,请参阅“[管理来自 GitHub 的营销电子邮件](/articles/managing-marketing-emails-from-github)”。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
new file mode 100644
index 0000000000..23b04a73f8
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md
@@ -0,0 +1,98 @@
+---
+title: 关于个人仪表板
+redirect_from:
+- /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github
+- /articles/opting-into-the-public-beta-for-a-new-dashboard
+- /articles/about-your-personal-dashboard
+- /github/setting-up-and-managing-your-github-user-account/about-your-personal-dashboard
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard
+intro: You can visit your personal dashboard to keep track of issues and pull requests you're working on or following, navigate to your top repositories and team pages, stay updated on recent activities in organizations and repositories you're subscribed to, and explore recommended repositories.
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Your personal dashboard
+ms.openlocfilehash: a6c91f68a30f06bbc5b3b7bc8a0b95dddfbae64a
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085069"
+---
+## 访问个人仪表板
+
+个人仪表板是登录 {% data variables.product.product_name %} 时显示的第一页。
+
+登录后若要访问个人仪表板,请单击 {% data variables.product.product_name %} 上任何页面左上角的 {% octicon "mark-github" aria-label="The github octocat logo" %}。
+
+## 查找近期活动
+
+在消息馈送的“Recent activity(最近活动)”部分,您可以快速找到并跟进最近更新的议题和您正在处理的拉取请求。 在“最近活动”下,最多可以预览过去两周内的 4 次最近更新。
+
+{% data reusables.dashboard.recent-activity-qualifying-events %}
+
+## 查找常用仓库和团队
+
+在仪表板的左侧栏中,可以访问常用仓库和团队。
+
+
+
+常用仓库列表自动生成,可以包括您与之交互的任何仓库,无论它是否由您的帐户直接拥有。 交互包括提交和打开或评论议题和拉取请求。 常用仓库列表无法编辑,但其中的仓库将在您最后一次与之交互 4 个月后从列表中删除。
+
+您也可以点击 {% data variables.product.product_name %} 上任何页面顶部的搜索栏,查找近期访问过的仓库、团队及项目板列表。
+
+## 了解社区中活动的最新信息
+
+{% if for-you-feed %} 仪表板的主要部分有两个活动源:
+
+- 关注:您关注的人员和您关注的存储库的活动。
+- 为您推荐:根据您的 {% data variables.product.product_name %} 网络开展的活动和推荐。
+
+### 关注订阅源
+
+此订阅源通过关注用户或存储库,显示来自您表现出直接兴趣的存储库和用户的活动。 例如,当您关注的用户执行以下操作时,您会看到更新:
+
+{% else %} 在新闻源的“所有活动”部分,可查看所监视的存储库和关注的用户的更新。
+
+当你关注的用户执行以下操作时,会在新闻源中看到更新:{% endif %}
+
+
+- 对仓库标星。
+- 关注其他用户。{% ifversion fpt or ghes or ghec %}
+- 创建公共仓库。{% endif %}
+- 在您关注的仓库上打开具有“需要帮助”或“良好的第一个议题”标签的议题或拉取请求。
+- 将提交内容推送到你关注的存储库。{% ifversion fpt or ghes or ghec %}
+- 复刻公共仓库。{% endif %}
+- 发布新版本。
+
+若要详细了解如何关注人员和监视存储库,请参阅“[关注他人](/get-started/exploring-projects-on-github/following-people)”和“[社交化](/get-started/quickstart/be-social)”。
+
+{% if for-you-feed %}
+### 供您订阅
+
+{% note %}
+
+注意:这个新选项卡目前为公共 beta 版本,可能会发生更改。
+
+{% endnote %}
+
+此订阅源根据您在 {% data variables.product.product_name %} 上的网络显示活动和建议。 它旨在提供更新,以激励您,让您保持最新状态,并帮助您找到想要参与的新社区。 您的网络包括:
+
+- 您已加星标的存储库
+- 您参与的存储库
+- 您关注或赞助的用户
+- 与您协作的用户
+- 您关注的组织
+
+{% endif %}
+
+## 探索推荐的仓库
+
+在仪表板右侧的“Explore repositories(浏览仓库)”部分,您可以浏览社区中推荐的仓库。 推荐内容基于你已加注星标或访问过的存储库、所关注的人员以及有权访问的存储库中的活动。{% ifversion fpt or ghec %}有关详细信息,请参阅“[查找在 {% data variables.product.prodname_dotcom %} 上参与开放源代码的方法](/github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github)”。{% endif %}
+
+## 延伸阅读
+
+- [关于组织仪表板](/articles/about-your-organization-dashboard)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md
new file mode 100644
index 0000000000..1c792a403a
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company.md
@@ -0,0 +1,45 @@
+---
+title: 关于离开公司的最佳实践
+intro: If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.
+redirect_from:
+- /articles/best-practices-for-leaving-your-company
+- /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Leaving your company
+ms.openlocfilehash: 4384955c0b81e887cb2671a537291b438664e621
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145087324"
+---
+在离开公司之前,请确保在个人帐户中更新以下信息:
+
+- 通过[在电子邮件设置中删除公司电子邮件地址](/articles/changing-your-primary-email-address)来取消其验证。 然后,您可以在不验证的情况下重新添加它,以保留与您的帐户相关联的所有相关提交。
+- [将你的主电子邮件地址](/articles/changing-your-primary-email-address)从公司电子邮件地址更改为个人电子邮件地址。
+{% ifversion fpt or ghec %}
+- [验证新的主电子邮件地址](/articles/verifying-your-email-address)。
+{% endif %}
+- [更改你的 GitHub 用户名](/articles/changing-your-github-username)以删除对公司或组织的任何引用(如有必要)。
+
+## 离开组织
+
+如果你在使用属于组织的存储库,则应[删除自己的组织成员身份](/articles/removing-yourself-from-an-organization)。 请注意,如果你是组织所有者,应先将[组织的所有权转让](/articles/transferring-organization-ownership)给其他人。
+
+## 删除与个人仓库的职业关联
+
+如果你在属于其他人的个人帐户的存储库中与其进行了专业协作,则应从这些存储库中[删除自己的协作者身份](/articles/removing-yourself-from-a-collaborator-s-repository)。
+
+- [停止关注与工作相关的存储库](https://github.com/watching)。 您不再需要这些通知了!
+- [转让你拥有的存储库](/articles/how-to-transfer-a-repository),在你离开后,其他人可能需要继续使用该存储库处理工作。
+- [删除与你的工作相关且属于你的分支](/articles/deleting-a-repository)。 不用担心,删除复刻不会删除上游仓库。
+- 删除您的计算机上可能存在的复刻本地副本:
+
+```shell
+$ rm -rf work_directory
+```
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
new file mode 100644
index 0000000000..9826acb880
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md
@@ -0,0 +1,95 @@
+---
+title: 更改 GitHub 用户名
+intro: You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} if your instance uses built-in authentication{% endif %}.
+redirect_from:
+- /articles/how-to-change-your-username
+- /articles/changing-your-github-user-name
+- /articles/renaming-a-user
+- /articles/what-happens-when-i-change-my-username
+- /articles/changing-your-github-username
+- /github/setting-up-and-managing-your-github-user-account/changing-your-github-username
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Change your username
+ms.openlocfilehash: 30139a0dab508f1e8db0f33174d6e25ec28afef4
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145085068"
+---
+{% ifversion ghec or ghes %}
+
+{% note %}
+
+{% ifversion ghec %}
+
+注意:{% data variables.product.prodname_emu_enterprise %} 成员不能更改用户名。 企业的 IdP 管理员控制您的 {% data variables.product.product_name %} 用户名。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
+
+{% elsif ghes %}
+
+注意:如果你使用 LDAP 凭据或单一登录 (SSO) 登录 {% data variables.product.product_location %},则只有你的本地管理员才能更改你的用户名。 有关 {% data variables.product.product_name %} 身份验证方法的详细信息,请参阅“[对 {% data variables.product.product_location %} 的用户进行身份验证](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)”。
+
+{% endif %}
+
+{% endnote %}
+
+{% endif %}
+
+## 关于用户名更改
+
+您可以将用户名更改为当前未使用的其他用户名。{% ifversion fpt or ghec %} 如果所需的用户名不可用,请考虑其他名称或唯一变体。 使用数字、连字符或其他拼写可能有助于您找到仍可用的类似用户名。
+
+如果你拥有该用户名的商标,可以在我们的[商标政策](/free-pro-team@latest/github/site-policy/github-trademark-policy)页面上找到有关提出商标投诉的更多信息。
+
+如果您没有该名称的商标,则可以选择其他用户名或保留当前用户名。 {% data variables.contact.github_support %} 无法为您释放不可用的用户名。 有关详细信息,请参阅“[更改用户名](#changing-your-username)”。{% endif %}
+
+更改用户名后,您的旧用户名即可供其他人申请使用。 对旧用户名下仓库的大多数引用会自动更改为新用户名。 不过,指向您个人资料的某些链接不会自动重定向。
+
+{% data variables.product.product_name %} 无法为以下各项设置重定向:
+- 使用旧用户名的 [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- 包含旧用户名的 [gists](/articles/creating-gists) 链接
+
+{% ifversion fpt or ghec %}
+
+如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则无法更改用户名。 {% data reusables.enterprise-accounts.emu-more-info-account %}
+
+{% endif %}
+
+## 仓库引用
+
+您更改用户名后,{% data variables.product.product_name %} 自动将引用重定向到您的仓库。
+- 指向现有仓库的 Web 链接仍然有效。 进行更改后,可能需要几分钟时间才能完成。
+- 从本地仓库克隆推送到旧的远程跟踪 URL 的命令行仍然有效。
+
+如果旧用户名的新所有者创建与您的仓库同名的仓库,则会覆盖重定向条目,并且您的重定向将停止工作。 由于这种可能性,我们建议您在更改用户名后更新所有现有的远程仓库 URL。 有关详细信息,请参阅“[管理远程存储库](/github/getting-started-with-github/managing-remote-repositories)”。
+
+## 指向以前的个人资料页面的链接
+
+更改用户名后,指向以前的配置文件页面的链接(例如 `https://{% data variables.command_line.backticks %}/previoususername`)将返回 404 错误。 我们建议从其他位置更新指向 {% data variables.product.product_location %} 帐户的所有链接{% ifversion fpt or ghec %},例如您的 LinkedIn 或 Twitter 个人资料{% endif %}。
+
+## 您的 Git 提交
+
+{% ifversion fpt or ghec %}与你的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址关联的 Git 提交不会归于新的用户名,并且不会在你的贡献图中显示。{% endif %}如果你的 Git 提交与你已[添加到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)的其他电子邮件地址关联,{% ifversion fpt or ghec %}包括基于 ID 的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址,{% endif %}它们在你更改用户名后将继续归于你并在你的贡献图中显示。 有关设置电子邮件地址的详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。
+
+## 更改用户名
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %}
+3. 在“更改用户名”部分中,单击“更改用户名”。
+ {% ifversion fpt or ghec %}
+4. 阅读有关更改用户名的警告。 如果你仍要更改用户名,请单击“我了解,让我们更改用户名”。
+ 
+5. 键入新的用户名。
+ 
+6. 如果你选择的用户名可用,请单击“更改用户名”。 如果您选择的用户名不可用,可以尝试其他用户名或您看到的建议之一。
+  {% endif %}
+
+## 延伸阅读
+
+- [我的提交为什么链接到错误的用户?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user){% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_dotcom %} 用户名策略](/free-pro-team@latest/github/site-policy/github-username-policy){% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
new file mode 100644
index 0000000000..ff2c1f513c
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization.md
@@ -0,0 +1,72 @@
+---
+title: 将用户转换为组织
+redirect_from:
+- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
+- /articles/explaining-the-account-transformation-warning
+- /articles/converting-a-user-into-an-organization
+- /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
+intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: User into an organization
+ms.openlocfilehash: 0c167e3e389230e6ac2dccb9f1f2f3dc67791bd0
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145066883"
+---
+{% warning %}
+
+警告:在将用户转换为组织之前,请记住以下几点:
+
+ - 你将无法再登录转换后的个人帐户。
+ - 你将无法再创建或修改转换后的个人帐户所拥有的 Gist。
+ - 组织无法转换回用户。
+ - 不会将 SSH 密钥、OAuth 标记、作业配置文件、反应和关联的用户信息传输到组织。 这只适用于被转换的个人帐户,而不适用于该个人帐户的任何协作者。
+ - 使用转换后的个人帐户所做的任何提交将不再链接到该帐户。 提交本身将保持不变。
+ - 将删除使用转换后的个人帐户创建的任何专用存储库的分支。
+
+{% endwarning %}
+
+## 保留个人帐户并手动创建新组织
+
+如果希望组织的名称与目前用于个人帐户的名称相同,或者要保留个人帐户的信息不变,则必须创建一个新组织,然后将存储库转让给该组织,而不是将个人帐户转换为组织。
+
+1. 要保留当前个人帐户名称以供个人使用,[请将个人帐户名称更改为](/articles/changing-your-github-username)一个好听的新名称。
+2. 使用个人帐户的原始名称[创建新组织](/articles/creating-a-new-organization-from-scratch)。
+3. [将存储库转移到](/articles/transferring-a-repository)新的组织帐户。
+
+## 自动将个人帐户转换为组织
+
+也可以将个人帐户直接转换为组织。 转换帐户:
+ - 按原样保留仓库,无需手动将其转让给另一个帐户
+ - 自动邀请协作者加入具有与其之前相同权限的团队 {% ifversion fpt or ghec %}- 对于 {% data variables.product.prodname_pro %} 上的个人帐户,自动将计费转换到[付费的 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts),无需重新输入付款信息、调整计费周期或随时双倍付款{% endif %}
+
+1. 创建新的个人帐户,转换后您将用它来登录 GitHub 以及访问组织和仓库。
+2. [退出组织](/articles/removing-yourself-from-an-organization)(你要转换的个人帐户已加入的组织)。
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
+5. 在“转换帐户”下,单击“将 转换为组织”。
+ 
+6. 在 Account Transformation Warning(帐户转换警告)对话框中,查看并确认转换。 请注意,此框中的信息与本文顶部的警告信息相同。
+ 
+7. 在“Transform your user into an organization(将用户转换为组织)”页面的“Choose an organization owner(选择组织所有者)”下,选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。
+ 
+8. 选择新组织的订阅,并在提示时输入帐单信息。
+9. 单击“创建组织”。
+10. 登录在第一步中创建的新个人帐户,然后使用上下文切换器访问新组织。
+
+{% tip %}
+
+提示:将个人帐户转换为组织时,我们会将属于该帐户的存储库中的协作者作为外部协作者添加到新组织。 然后,你可以根据需要邀请外部协作者成为新组织的成员。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。
+
+{% endtip %}
+
+## 延伸阅读
+- [设置团队](/articles/setting-up-teams) {% ifversion fpt or ghec %}- [邀请用户加入组织](/articles/inviting-users-to-join-your-organization){% endif %}
+- [访问组织](/articles/accessing-an-organization)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
new file mode 100644
index 0000000000..82bb4772c2
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md
@@ -0,0 +1,54 @@
+---
+title: 删除用户帐户
+intro: You can delete your personal account on {% data variables.product.product_name %} at any time.
+redirect_from:
+- /articles/deleting-a-user-account
+- /articles/deleting-your-user-account
+- /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Delete your personal account
+ms.openlocfilehash: fe18309f93bdb4124fa5a58d22ab7a93b451e6e1
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084774"
+---
+删除个人帐户将删除帐户所拥有的所有存储库、专用存储库的分支、Wiki、问题、拉取请求和页面。 {% ifversion fpt or ghec %} 在其他用户拥有的存储库中创建的问题和拉取请求以及所做的评论不会被删除,而是与我们的 [Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的存储库中创建的问题和拉取请求以及所做的评论不会被删除。{% endif %}
+
+{% ifversion fpt or ghec %} 当您删除帐户时,我们会停止对您计费。 与该帐户关联的电子邮件地址可用于 {% data variables.product.product_location %} 上不同的帐户。 90 天后,该帐户名称也可供其他任何人用于新帐户。 {% endif %}
+
+如果你是组织的唯一所有者,则必须先将所有权转让给其他人或删除该组织,然后才能删除个人帐户。 如果组织中有其他所有者,则必须先从组织中删除自己,然后才能删除个人帐户。
+
+有关详细信息,请参阅:
+- [转让组织所有权](/articles/transferring-organization-ownership)
+- [删除组织帐户](/articles/deleting-an-organization-account)
+- [从组织中删除自己](/articles/removing-yourself-from-an-organization/)
+
+## 备份帐户数据
+
+在删除个人帐户之前,请复制帐户所拥有的所有存储库、专用分支、Wiki、问题和拉取请求。
+
+{% warning %}
+
+警告:删除个人帐户后,GitHub 将无法还原内容。
+
+{% endwarning %}
+
+## 删除个人帐户
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %}
+3. 在帐户设置页面底部的“删除帐户”下,单击“删除帐户”。 在删除个人帐户之前:
+ - 如果您是组织中的唯一所有者,则必须将所有权转让给其他人或删除您的组织。
+ - 如果组织中有其他组织所有者,则必须将自己从组织中删除。
+ 
+4. 在“确认要执行此操作”对话框中,完成相关步骤以确认你了解删除帐户的后果: {% ifversion fpt or ghec %}- 重新确认帐户拥有的所有存储库、专用存储库分支、wiki、问题、拉取请求和 {% data variables.product.prodname_pages %} 站点都将删除,计费将立即结束,并且 90 天后任何人都可在 {% data variables.product.product_name %} 上使用你的用户名。
+ {% else %}- 重新考虑一下,您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除,并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。
+ {% endif %}- 在第一个字段中,输入您的 {% data variables.product.product_name %} 用户名或电子邮件。
+ - 在第二个字段中,键入提示短语。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
new file mode 100644
index 0000000000..e8a374b5d3
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md
@@ -0,0 +1,40 @@
+---
+title: 管理用户帐户设置
+intro: You can change several settings for your personal account, including changing your username and deleting your account.
+redirect_from:
+- /categories/29/articles
+- /categories/user-accounts
+- /articles/managing-user-account-settings
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+children:
+- /about-your-personal-dashboard
+- /managing-your-theme-settings
+- /managing-your-tab-size-rendering-preference
+- /changing-your-github-username
+- /merging-multiple-user-accounts
+- /converting-a-user-into-an-organization
+- /deleting-your-user-account
+- /permission-levels-for-a-user-account-repository
+- /permission-levels-for-user-owned-project-boards
+- /managing-accessibility-settings
+- /managing-the-default-branch-name-for-your-repositories
+- /managing-security-and-analysis-settings-for-your-user-account
+- /managing-access-to-your-user-accounts-project-boards
+- /integrating-jira-with-your-personal-projects
+- /best-practices-for-leaving-your-company
+- /what-does-the-available-for-hire-checkbox-do
+shortTitle: Personal account settings
+ms.openlocfilehash: 2d62699cda16ed9387e1f19aab5bb6bde4376b7b
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084771"
+---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
new file mode 100644
index 0000000000..adc2f90553
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects.md
@@ -0,0 +1,32 @@
+---
+title: 将 Jira 与个人项目集成
+intro: You can integrate Jira Cloud with your personal account to scan commits and pull requests, creating relevant metadata and hyperlinks in any mentioned Jira issues.
+redirect_from:
+- /articles/integrating-jira-with-your-personal-projects
+- /github/setting-up-and-managing-your-github-user-account/integrating-jira-with-your-personal-projects
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/integrating-jira-with-your-personal-projects
+versions:
+ ghes: '*'
+ ghae: '*'
+shortTitle: Integrate Jira with projects
+ms.openlocfilehash: a9106d979aa0f219bd20fc5b27042dfe8e81fc8c
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084769"
+---
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.developer_settings %} {% data reusables.user-settings.oauth_apps %}
+1. 单击“注册新应用程序”。
+2. 在“应用程序名称”下,键入“Jira”。
+3. 在“主页 URL”下,键入 Jira 实例的完整 URL。
+4. 在“授权回叫 URL”下,键入 Jira 实例的完整 URL。
+5. 单击“注册应用程序”。
+
+8. 在“开发人员应用程序”下,记下“客户端 ID”和“客户端机密”值。
+{% data reusables.user-settings.jira_help_docs %}
+
+## 延伸阅读
+
+- [集成 Jira 与组织项目板](/articles/integrating-jira-with-your-organization-project-board)
+- 将 Jira Cloud 连接到 GitHub(Atlassian 文档)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
new file mode 100644
index 0000000000..44a3abb293
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards.md
@@ -0,0 +1,38 @@
+---
+title: 管理对用户帐户项目板的访问
+intro: As a project board owner, you can add or remove a collaborator and customize their permissions to a project board.
+redirect_from:
+- /articles/managing-project-boards-in-your-repository-or-organization
+- /articles/managing-access-to-your-user-account-s-project-boards
+- /articles/managing-access-to-your-user-accounts-project-boards
+- /github/setting-up-and-managing-your-github-user-account/managing-access-to-your-user-accounts-project-boards
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-access-to-your-user-accounts-project-boards
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Manage access project boards
+ms.openlocfilehash: 5a5cf08169fec04a896b05b7934c80cfe9f2eded
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084768"
+---
+协作者是对您拥有的项目板具有访问权限的个人。 协作者的权限默认为读取权限。 有关详细信息,请参阅“[用户拥有的项目板的权限级别](/articles/permission-levels-for-user-owned-project-boards)”。
+
+## 邀请协作者参加用户拥有的项目板
+
+1. 导航到您要在其中添加协作者的项目板。
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %}
+5. 在 "Search by username, full name or email address"(按用户名、全名或电子邮件地址搜索)下,输入协作者的姓名、用户名或 {% data variables.product.prodname_dotcom %} 电子邮件地址。
+  {% data reusables.project-management.add-collaborator %}
+7. 新协作者默认具有读取权限。 在新协作者名称旁边,可以选择使用下拉菜单选择不同的权限级别。
+ 
+
+## 从用户拥有的项目板删除协作者
+
+{% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %} {% data reusables.project-management.collaborator-option %} {% data reusables.project-management.remove-collaborator %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
new file mode 100644
index 0000000000..36cb88f8e3
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md
@@ -0,0 +1,24 @@
+---
+title: 管理辅助功能设置
+intro: You can disable character key shortcuts on {% data variables.product.prodname_dotcom %} in your accessibility settings.
+versions:
+ feature: keyboard-shortcut-accessibility-setting
+ms.openlocfilehash: 9cd1aa981642a9372731fcbf39a614e5b93b1273
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084767"
+---
+## 关于辅助功能设置
+
+{% data variables.product.product_name %} 包括各种键盘快捷键,便于您在整个站点中执行操作,而无需使用鼠标进行导航。 虽然快捷方式有助于节省时间,但它们有时会使 {% data variables.product.prodname_dotcom %} 更难使用且更难以访问。
+
+默认情况下,所有键盘快捷键都在 {% data variables.product.product_name %} 上启用,但您可以选择在辅助功能设置中禁用字符键快捷键。 此设置不影响 Web 浏览器提供的键盘快捷方式,或者使用修改键(如 Control 或 Command)的 {% data variables.product.prodname_dotcom %} 快捷方式。
+
+## 管理字符键快捷方式
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.accessibility_settings %}
+1. 选中或取消选中“启用字符键快捷方式”复选框。
+ 
+2. 单击“保存” 。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
new file mode 100644
index 0000000000..aafdd463bc
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account.md
@@ -0,0 +1,57 @@
+---
+title: 管理用户帐户的安全和分析设置
+intro: You can control features that secure and analyze the code in your projects on {% data variables.product.prodname_dotcom %}.
+versions:
+ fpt: '*'
+ ghec: '*'
+ ghes: '>3.2'
+topics:
+- Accounts
+redirect_from:
+- /github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account
+shortTitle: Manage security & analysis
+ms.openlocfilehash: 1a025a46dc42252a2e3c0facbe6b3beffa48cf45
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084764"
+---
+## 关于安全性和分析设置的管理
+
+{% data variables.product.prodname_dotcom %} 可保护您的仓库。 本主题介绍如何管理所有现有或新仓库的安全和分析功能。
+
+您仍然可以管理单个仓库的安全和分析功能。 有关详细信息,请参阅“[管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)”。
+
+你还可以查看个人帐户上所有活动的安全日志。 有关详细信息,请参阅“[查看安全日志](/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log)”。
+
+{% data reusables.security.some-security-and-analysis-features-are-enabled-by-default %}
+
+{% data reusables.security.security-and-analysis-features-enable-read-only %}
+
+有关存储库级安全性的概述,请参阅“[保护存储库](/code-security/getting-started/securing-your-repository)”。
+
+## 启用或禁用现有仓库的功能
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
+3. 在“代码安全和分析”下,单击功能右侧的“全部禁用”或“全部启用” 。
+ {% ifversion ghes > 3.2 %}{% else %}{% endif %}
+6. (可选)默认情况下为您拥有的新存储库启用该功能。
+ {% ifversion ghes > 3.2 %}{% else %}{% endif %}
+7. 单击“禁用功能”或“启用功能”,以为所拥有的所有存储库禁用或启用该功能 。
+ {% ifversion ghes > 3.2 %}{% else %}{% endif %}
+
+{% data reusables.security.displayed-information %}
+
+## 对新仓库启用或禁用功能
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.security-analysis %}
+3. 在“Code security and analysis(代码安全和分析)”下,在功能右侧,默认为您拥有的新存储库启用或禁用该功能。
+ {% ifversion ghes > 3.2 %}{% else %}{% endif %}
+
+## 延伸阅读
+
+- “[关于依赖项图](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)”
+- “[关于 {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)”
+- “[自动更新依赖项](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md
new file mode 100644
index 0000000000..76ac51a289
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md
@@ -0,0 +1,40 @@
+---
+title: 管理仓库的默认分支名称
+intro: You can set the default branch name for new repositories that you create on {% data variables.product.product_location %}.
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+redirect_from:
+- /github/setting-up-and-managing-your-github-user-account/managing-the-default-branch-name-for-your-repositories
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
+shortTitle: Manage default branch name
+ms.openlocfilehash: 5bf934f246a2d0e447a99d0f63888b5b87ecc033
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084763"
+---
+## About the default branch name
+
+当您在 {% data variables.product.product_location %} 上创建一个新仓库时,仓库将包含一个分支,它就是默认分支。 您可以更改 {% data variables.product.product_name %} 用于您新建仓库中默认分支的名称。 有关默认分支的详细信息,请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。
+
+{% data reusables.branches.change-default-branch %}
+
+## 设置默认分支名称
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %}
+3. 在“存储库默认分支”下,单击“立即更改默认分支名称”。
+ 
+4. 键入要用于新分支的默认名称。
+ 
+5. 单击“更新”。
+ 
+
+## 延伸阅读
+
+- “[管理组织中存储库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
new file mode 100644
index 0000000000..c1a7f03f9c
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -0,0 +1,24 @@
+---
+title: 管理选项卡大小呈现首选项
+intro: You can manage the number of spaces a tab is equal to for your personal account.
+versions:
+ fpt: '*'
+ ghae: issue-5083
+ ghes: '>=3.4'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Managing your tab size
+ms.openlocfilehash: 2313c9e09d7f203f88ad2536aaffd3f508e15b79
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084762"
+---
+如果您觉得在 {% data variables.product.product_name %} 上呈现的选项卡式代码缩进占用了太多或太少的空间,可以在设置中更改。
+
+{% data reusables.user-settings.access_settings %}
+1. 在左侧边栏中,单击“{% octicon "paintbrush" aria-label="The paintbrush icon" %} 外观”。
+2. 在“Tab size preference(选项卡大小首选项)”下,选择下拉菜单,然后选择您的首选项。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
new file mode 100644
index 0000000000..924683eb21
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md
@@ -0,0 +1,56 @@
+---
+title: 管理主题设置
+intro: You can manage how {% data variables.product.product_name %} looks to you by setting a theme preference that either follows your system settings or always uses a light or dark mode.
+versions:
+ fpt: '*'
+ ghae: '*'
+ ghes: '>=3.2'
+ ghec: '*'
+topics:
+- Accounts
+redirect_from:
+- /github/setting-up-and-managing-your-github-user-account/managing-your-theme-settings
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings
+shortTitle: Manage theme settings
+ms.openlocfilehash: 238af803ead331a9323e9457024a85dff05fc5d4
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084757"
+---
+为了选择和灵活地使用 {% data variables.product.product_name %},您可以配置主题设置来更改 {% data variables.product.product_name %} 的外观。 您可以在浅色和深色两个主题中进行选择,也可以配置 {% data variables.product.product_name %} 遵循系统设置。
+
+您可能需要使用深色主题来减少某些设备的功耗,以在低光条件下减小眼睛的压力,或者因为您更喜欢主题的外观。
+
+{% ifversion fpt or ghes > 3.2 or ghae or ghec %}如果你视力低下,你可能会受益于高对比度主题,其前景和背景元素之间的对比度更高。{% endif %}{% ifversion fpt or ghae or ghec %} 如果你有色盲,你可能会从我们的浅色和深色色盲主题中受益。
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.appearance-settings %}
+
+1. 在“Theme mode(主题模式)”下,选择下拉菜单,然后单击主题首选项。
+
+ 
+1. 单击想要使用的主题。
+ - 如果您选择单个主题,请单击一个主题。
+
+ {% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %}
+ - 如果您选择遵循系统设置,请单击白天主题和夜间主题。
+
+ {% ifversion fpt or ghes > 3.2 or ghae or ghec %}{% else %}{% endif %} {% ifversion fpt or ghec %}
+ - 如果您想选择当前处于公开测试阶段的主题,则首先需要通过功能预览启用它。 有关详细信息,请参阅“[使用功能预览探索抢先体验版](/get-started/using-github/exploring-early-access-releases-with-feature-preview)”。{% endif %}
+
+{% if command-palette %}
+
+{% note %}
+
+注意:你还可以使用命令面板更改主题设置。 有关详细信息,请参阅“[{% data variables.product.prodname_command_palette %}](/get-started/using-github/github-command-palette)”。
+
+{% endnote %}
+
+{% endif %}
+
+## 延伸阅读
+
+- [为 {% data variables.product.prodname_desktop %} 设置主题](/desktop/installing-and-configuring-github-desktop/setting-a-theme-for-github-desktop)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
new file mode 100644
index 0000000000..b9bbd3273f
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md
@@ -0,0 +1,52 @@
+---
+title: 合并多个用户帐户
+intro: If you have separate accounts for work and personal use, you can merge the accounts.
+redirect_from:
+- /articles/can-i-merge-two-accounts
+- /articles/keeping-work-and-personal-repositories-separate
+- /articles/merging-multiple-user-accounts
+- /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Merge multiple personal accounts
+ms.openlocfilehash: 128a6c99f8a6208150067bb2c3668557b184c255
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084756"
+---
+{% tip %}
+
+{% ifversion ghec %}
+
+提示:{% data variables.product.prodname_emus %} 允许企业通过标识提供者 (IdP) 为其成员预配唯一的个人帐户。 有关详细信息,请参阅“[关于企业托管用户](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)”。 对于其他用例,我们建议仅使用一个个人帐户来管理个人和专业存储库。
+
+{% else %}
+
+提示:我们建议仅使用一个个人帐户来管理个人和专业存储库。
+
+{% endif %}
+
+{% endtip %}
+
+{% warning %}
+
+**警告:**
+- 组织和存储库访问权限不能在帐户之间转让。 如果要删除的帐户具有现有访问权限,则组织所有者或存储库管理员将需要邀请您要保留的帐户。
+- 无法将使用 GitHub 提供的 `noreply` 电子邮件地址创作的任何提交从一个帐户转移到另一个帐户。 如果要删除的帐户使用了“将我的电子邮件地址设为私有”选项,则无法将要删除的帐户创作的提交转移到要保留的帐户。
+
+{% endwarning %}
+
+1. [将任何存储库从要删除的帐户转移](/articles/how-to-transfer-a-repository)到要保留的帐户。 议题、拉取请求和 wiki 也会转让。 确认要保留的帐户中存在仓库。
+2. [更新已移动存储库的任何本地克隆中的远程 URL](/github/getting-started-with-github/managing-remote-repositories)。
+3. [删除不会再使用的帐户](/articles/deleting-your-user-account)。
+4. 要将过去的提交归因于新帐户,请将用于创作提交的电子邮件地址添加到要保留的帐户。 有关详细信息,请参阅“[为什么我的贡献没有在我的个人资料中显示?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)”
+
+## 延伸阅读
+
+- [{% data variables.product.prodname_dotcom %} 帐户类型](/articles/types-of-github-accounts)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
new file mode 100644
index 0000000000..5b36934f99
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md
@@ -0,0 +1,96 @@
+---
+title: 用户帐户仓库的权限级别
+intro: 'A repository owned by a personal account has two permission levels: the repository owner and collaborators.'
+redirect_from:
+- /articles/permission-levels-for-a-user-account-repository
+- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-a-user-account-repository
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Permission user repositories
+ms.openlocfilehash: 3fed88f8c31f5d3dd788f7b977c214499856f27e
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084752"
+---
+## 关于个人帐户存储库的权限级别
+
+个人帐户拥有的存储库有一个所有者。 所有权权限无法与其他个人帐户共享。
+
+还可以{% ifversion fpt or ghec %}邀请{% else %}添加{% endif %} {% data variables.product.product_name %} 上的用户成为存储库的协作者。 有关详细信息,请参阅“[邀请协作者访问个人存储库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository)”。
+
+{% tip %}
+
+提示:如果需要对个人帐户拥有的存储库实施更精细的访问控制,请考虑将存储库转让给组织。 有关详细信息,请参阅“[转让存储库](/github/administering-a-repository/transferring-a-repository#transferring-a-repository-owned-by-your-personal-account)”。
+
+{% endtip %}
+
+## 所有者对个人帐户拥有的存储库的权限
+
+仓库所有者对仓库具有完全控制权。 除了任何协作者可以执行的操作外,仓库所有者还可以执行以下操作。
+
+| 操作 | 详细信息 |
+| :- | :- |
+| {% ifversion fpt or ghec %}邀请协作者{% else %}添加协作者{% endif %} | [邀请协作者加入个人存储库](/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) |
+| 更改仓库的可见性 | [设置存储库可见性](/github/administering-a-repository/setting-repository-visibility) |{% ifversion fpt or ghec %}
+| 限制与仓库的交互 | [限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) |{% endif %}
+| 重命名分支,包括默认分支 | [重命名分支](/github/administering-a-repository/renaming-a-branch) |
+| 合并受保护分支上的拉取请求(即使没有批准审查) | [关于受保护分支](/github/administering-a-repository/about-protected-branches) |
+| 删除仓库 | [删除存储库](/repositories/creating-and-managing-repositories/deleting-a-repository) |
+| 管理仓库的主题 | [使用主题对存储库分类](/github/administering-a-repository/classifying-your-repository-with-topics) |{% ifversion fpt or ghec %}
+| 管理仓库的安全性和分析设置 | [管理存储库的安全和分析设置](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository) |{% endif %}{% ifversion fpt or ghec %}
+| 为私有仓库启用依赖项图 | [探索存储库的依赖项](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository) |{% endif %}{% ifversion fpt or ghes > 3.1 or ghec or ghae %}
+| 删除和恢复包 | [删除和恢复包](/packages/learn-github-packages/deleting-and-restoring-a-package) |{% endif %}
+| 自定义仓库的社交媒体预览 | [自定义存储库的社交媒体预览](/github/administering-a-repository/customizing-your-repositorys-social-media-preview) |
+| 从仓库创建模板 | [创建模板存储库](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository) |{% ifversion fpt or ghes or ghae or ghec %}
+| 控制对易受攻击依赖项的 {% data variables.product.prodname_dependabot_alerts %} 访问 | [管理存储库的安全和分析设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts) |{% endif %}{% ifversion fpt or ghec %}
+| 忽略仓库中的 {% data variables.product.prodname_dependabot_alerts %} | [查看漏洞依赖项的 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository) |
+| 管理私有仓库的数据使用 | [管理专用存储库的数据使用设置](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)|{% endif %}
+| 定义仓库的代码所有者 | [关于代码所有者](/github/creating-cloning-and-archiving-repositories/about-code-owners) |
+| 存档仓库 | [存档存储库](/repositories/archiving-a-github-repository/archiving-repositories) |{% ifversion fpt or ghec %}
+| 创建安全通告 | [关于 {% data variables.product.prodname_security_advisories %}](/github/managing-security-vulnerabilities/about-github-security-advisories) |
+| 显示赞助按钮 | [在存储库中显示赞助者按钮](/github/administering-a-repository/displaying-a-sponsor-button-in-your-repository) |{% endif %}
+| 允许或禁止自动合并拉取请求 | [管理存储库中拉取请求的自动合并](/github/administering-a-repository/managing-auto-merge-for-pull-requests-in-your-repository) |
+
+## 协作者对个人帐户拥有的存储库的权限
+
+个人仓库的协作者可以拉取(读取)仓库的内容并向仓库推送(写入)更改。
+
+{% note %}
+
+注意:在专用存储库中,存储库所有者只能为协作者授予写入权限。 协作者不能对个人帐户拥有的存储库具有只读权限。
+
+{% endnote %}
+
+协作者还可以执行以下操作。
+
+| 操作 | 详细信息 |
+| :- | :- |
+| 为存储库创建分支 | [关于分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) |{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
+| 重命名除默认分支以外的分支 | [重命名分支](/github/administering-a-repository/renaming-a-branch) |{% endif %}
+| 在仓库中创建、编辑和删除关于提交、拉取请求和议题的评论 | - [关于问题](/github/managing-your-work-on-github/about-issues)
- [评论拉取请求](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)
- [管理中断性注释](/communities/moderating-comments-and-conversations/managing-disruptive-comments)
|
+| 在仓库中创建、分配、关闭和重新打开议题 | [使用问题管理工作](/github/managing-your-work-on-github/managing-your-work-with-issues) |
+| 在仓库中管理议题和拉取请求的标签 | [标记问题和拉取请求](/github/managing-your-work-on-github/labeling-issues-and-pull-requests) |
+| 在仓库中管理议题和拉取请求的里程碑 | [创建和编辑问题和拉取请求的里程碑](/github/managing-your-work-on-github/creating-and-editing-milestones-for-issues-and-pull-requests) |
+| 将仓库中的议题或拉取请求标记为重复项 | [关于重复的问题和拉取请求](/github/managing-your-work-on-github/about-duplicate-issues-and-pull-requests) |
+| 在仓库中创建、合并和关闭拉取请求 | [通过拉取请求提议工作更改](/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) |
+| 启用或禁用自动合并拉取请求 | [自动合并拉取请求](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request)
+| 将建议的更改应用于仓库中的拉取请求 |[在拉取请求中加入反馈](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request) |
+| 从仓库的复刻创建拉取请求 | [从分支创建拉取请求](/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork) |
+| 提交影响拉取请求可合并性的拉取请求审查 | [查看拉取请求中的建议更改](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request) |
+| 为仓库创建和编辑 wiki | [关于 Wiki](/communities/documenting-your-project-with-wikis/about-wikis) |
+| 为仓库创建和编辑发行版 | [管理存储库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository) |
+| 作为仓库的代码所有者 | [关于代码所有者](/articles/about-code-owners) |{% ifversion fpt or ghae or ghec %}
+| 发布、查看或安装包 | [发布和管理包](/github/managing-packages-with-github-packages/publishing-and-managing-packages) |{% endif %}
+| 作为仓库协作者删除自己 | [从协作者的存储库中删除你自己](/github/setting-up-and-managing-your-github-user-account/removing-yourself-from-a-collaborators-repository) |
+
+## 延伸阅读
+
+- [组织的存储库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md
new file mode 100644
index 0000000000..00965455c7
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards.md
@@ -0,0 +1,69 @@
+---
+title: 用户拥有的项目板的权限级别
+intro: 'A project board owned by a personal account has two permission levels: the project board owner and collaborators.'
+redirect_from:
+- /articles/permission-levels-for-user-owned-project-boards
+- /github/setting-up-and-managing-your-github-user-account/permission-levels-for-user-owned-project-boards
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-user-owned-project-boards
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Permission user project boards
+ms.openlocfilehash: 535ef830e9ee0d8d5a3bb81ea208711cf4060943
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084751"
+---
+## 权限概述
+
+用户拥有的项目板只有一个所有者,此权限无法与其他个人帐户共享。 除了所有者之外,其他人可以在项目板上协作。
+
+项目板协作者有三种权限级别:
+
+{% data reusables.project-management.project-board-permissions %}
+
+## 用户拥有的项目板的所有者和管理员权限
+
+项目板所有者和具有管理员权限的协作者对项目板有完全控制权限。 除了项目板协作者拥有的所有权限之外,项目板所有者和具有管理员权限的协作者还可以:
+
+- [管理、查看和添加协作者](/articles/managing-access-to-your-user-account-s-project-boards)
+- [将项目板配置为{% ifversion ghae %}内部{% else %}公共{% endif %}或专用](/articles/changing-project-board-visibility)
+- [删除项目板](/articles/deleting-a-project-board/)
+- [关闭项目板](/articles/closing-a-project-board/)
+- [重新打开关闭的项目板](/articles/reopening-a-closed-project-board)
+
+## 用户拥有的项目板的读取和写入权限
+
+对用户拥有的项目板具有读取权限的协作者可以:
+
+- 查看项目板
+- 复制项目板
+- 过滤项目板上的卡
+
+对用户拥有的项目板具有写入权限的协作者可以:
+
+- 查看项目板
+- 复制项目板
+- 过滤项目板上的卡
+- 编辑项目板
+- 将仓库链接到项目板
+- 配置项目板的自动化
+- 复制项目板
+- 添加议题和拉取请求到项目板
+- 添加注释到项目板
+- 跟踪项目板上的进度
+- 存档项目板上的卡
+
+## 项目板可见性
+
+可以将项目板的可见性从专用更改为{% ifversion ghae %}内部{% else %}公共{% endif %},反之亦然。 默认情况下,用户拥有的项目板为私有。 有关详细信息,请参阅“[更改项目板可见性](/articles/changing-project-board-visibility)”。
+
+## 延伸阅读
+
+ - “[管理对个人帐户的项目板的访问权限](/articles/managing-access-to-your-user-account-s-project-boards)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md
new file mode 100644
index 0000000000..067f217471
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do.md
@@ -0,0 +1,33 @@
+---
+title: “招聘职位”复选框有什么作用?
+intro: Use the **Available for hire** checkbox to view GitHub Jobs posts within GitHub.
+redirect_from:
+- /articles/what-does-the-available-for-hire-checkbox-do
+- /github/setting-up-and-managing-your-github-user-account/what-does-the-available-for-hire-checkbox-do
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/what-does-the-available-for-hire-checkbox-do
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Available for hire checkbox
+ms.openlocfilehash: d3acf444423db8aacce8d33d1062b32e435a751a
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084750"
+---
+{% warning %}
+
+弃用说明:GitHub Jobs 现已弃用。 最后一次发布工作日期是 2021 年 5 月 19 日。 GitHub Jobs 网站已于 2021 年 8 月 19 日完全关闭,现在重定向到 [GitHub 博客文章](https://github.blog/changelog/2021-04-19-deprecation-notice-github-jobs-site/)通知,其中包含有关 GitHub Jobs 现已完成的弃用的详细信息。
+
+{% endwarning %}
+
+[GitHub Jobs](https://jobs.github.com/) 板是找到技术方面的工作的不错方法。 您可选择查看在 GitHub 仪表板上发布的职位。
+
+
+
+{% data reusables.user-settings.access_settings %}
+2. 在“工作简介”下,选择“可供雇用”,然后单击“保存工作简介” 。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
new file mode 100644
index 0000000000..79e9e167f5
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership.md
@@ -0,0 +1,58 @@
+---
+title: 关于组织成员资格
+intro: You can become a member of an organization to collaborate with coworkers or open-source contributors across many repositories at once.
+redirect_from:
+- /articles/about-organization-membership
+- /github/setting-up-and-managing-your-github-user-account/about-organization-membership
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/about-organization-membership
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Organization membership
+ms.openlocfilehash: 6a7afd8aee12e2c471f564122fb21f07d710f808
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084749"
+---
+组织所有者可邀请您作为成员、帐单管理员或所有者加入其组织。 组织所有者或者对仓库具有管理员权限的成员可邀请您作为外部协作者,协作处理一个或多个仓库。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。
+
+您可以在个人资料页面上访问您是其成员的组织。 有关详细信息,请参阅“[访问组织](/articles/accessing-an-organization)”。
+
+当您接受加入组织的邀请后,组织所有者可能会看到:
+
+- 您的公共资料信息
+- 你的电子邮件地址
+- 您是否启用双重身份验证
+- 您在组织内可以访问的仓库以及您的权限级别
+- 组织内的特定活动
+- 申请来源国家/地区
+- 您的 IP 地址
+
+有关详细信息,请参阅 {% data variables.product.prodname_dotcom %} 隐私声明。
+
+ {% note %}
+
+ 注意:所有者无法在组织的审核日志中查看成员 IP 地址。 在发生安全事件时,例如帐户被盗或因疏忽而共享敏感数据,组织所有者可能会申请详细访问私有仓库。 我们返回的信息可能包含您的 IP 地址。
+
+ {% endnote %}
+
+默认情况下,您的组织成员资格可见性会设为私密。 您可以选择在您的个人资料中公开个人组织成员资格。 有关详细信息,请参阅“[公开或隐藏组织成员身份](/articles/publicizing-or-hiding-organization-membership)”。
+
+{% ifversion fpt or ghec %}
+
+如果您的组织属于某个企业帐户,您会自动成为该企业帐户的成员,企业帐户所有者能够看到您。 有关详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts){% ifversion fpt %}”。{% else %}."{% endif %}
+
+{% endif %}
+
+您可以随时离开组织。 有关详细信息,请参阅“[从组织中删除自己](/articles/removing-yourself-from-an-organization)”。
+
+## 延伸阅读
+
+- [关于组织](/articles/about-organizations)
+- [管理组织中的成员身份](/articles/managing-your-membership-in-organizations)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
new file mode 100644
index 0000000000..9936b5ac46
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md
@@ -0,0 +1,31 @@
+---
+title: 访问组织
+intro: To access an organization that you're a member of, you must sign in to your personal account.
+redirect_from:
+- /articles/error-cannot-log-in-that-account-is-an-organization
+- /articles/cannot-log-in-that-account-is-an-organization
+- /articles/how-do-i-access-my-organization-account
+- /articles/accessing-an-organization
+- /github/setting-up-and-managing-your-github-user-account/accessing-an-organization
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+ms.openlocfilehash: 61d05267792ec59cef5f5b41d7680d1dc4c3f9fe
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084746"
+---
+{% tip %}
+
+提示:只有组织所有者才可查看和更改组织的帐户设置。
+
+{% endtip %}
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md
new file mode 100644
index 0000000000..c9cbf0db88
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/index.md
@@ -0,0 +1,29 @@
+---
+title: 管理组织中的成员资格
+intro: If you're a member of an organization, you can publicize or hide your membership, view other people's roles, and remove yourself from the organization.
+redirect_from:
+- /articles/managing-your-membership-in-organizations
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+children:
+- /about-organization-membership
+- /accessing-an-organization
+- /viewing-peoples-roles-in-an-organization
+- /requesting-organization-approval-for-oauth-apps
+- /publicizing-or-hiding-organization-membership
+- /managing-your-scheduled-reminders
+- /removing-yourself-from-an-organization
+shortTitle: Manage organization membership
+ms.openlocfilehash: cb0fbd62c63098fb3cbf5a786147499aa6d63c61
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084745"
+---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
new file mode 100644
index 0000000000..253cc5493f
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders.md
@@ -0,0 +1,53 @@
+---
+title: 管理您的预定提醒
+intro: Get reminders in Slack when you or your team have pull requests waiting for review.
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+redirect_from:
+- /github/setting-up-and-managing-your-github-user-account/managing-your-scheduled-reminders
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/managing-your-scheduled-reminders
+shortTitle: Manage scheduled reminders
+ms.openlocfilehash: 41670a8c8b8aa1e6eade16c42f5a146f1ec0f5ee
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084744"
+---
+## 关于用户的预定提醒
+
+预定提醒用于确保用户将重点放在需要他们关注的最重要审查请求上。 拉取请求的预定提醒将会在指定的时间在 Slack 中向您发送一条消息,提醒已经打开、需要您审查的拉取请求。 例如,您可以设置预定提醒,以便每天早上 10 点在 Slack 中向您发送消息,提醒需要由您或您的一个团队审查的拉取请求。
+
+对于某些事件,您还可以为预定提醒启用实时警报。 实时警报会在重要事件(例如分配审查时)发生时立即发送到您的 Slack 通道。
+
+对于您所在组织的拉取请求,您可以为个人或团队级审查请求设置预定提醒。 组织所有者必须先授权您的 Slack 工作区,然后您才可为自己创建预定提醒。 有关详细信息,请参阅“[管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)”。
+
+{% data reusables.reminders.scheduled-reminders-limitations %}
+
+## 为你的个人帐户创建预定提醒
+
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. 在要预定提醒的组织旁边,单击“编辑”。
+ {% data reusables.reminders.add-reminder %} {% data reusables.reminders.authorize-slack %} {% data reusables.reminders.days-dropdown %} {% data reusables.reminders.times-dropdowns %}
+8. 或者,要对分配给你的审查接收预定提醒,请选择“审查分配给你的请求”。
+
+9. 或者,要对分配给你所属团队的审查接受预定提醒,请选择“审查分配给你的团队的请求”。
+ {% data reusables.reminders.real-time-alerts %}  {% data reusables.reminders.create-reminder %}
+
+## 为你的个人帐户管理预定提醒
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. 在要编辑预定提醒的组织旁边,单击“编辑”。
+ {% data reusables.reminders.edit-page %} {% data reusables.reminders.update-buttons %}
+
+## 为你的个人帐户删除预定提醒
+{% data reusables.user-settings.access_settings %} {% data reusables.reminders.scheduled-reminders %}
+1. 在要删除提醒的组织旁边,单击“编辑”。
+ {% data reusables.reminders.delete %}
+
+## 延伸阅读
+
+- [管理组织的预定提醒](/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization)
+- [管理团队的预定提醒](/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
new file mode 100644
index 0000000000..93a5bcc368
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership.md
@@ -0,0 +1,34 @@
+---
+title: 公开或隐藏组织成员关系
+intro: If you'd like to tell the world which organizations you belong to, you can display the avatars of the organizations on your profile.
+redirect_from:
+- /articles/publicizing-or-concealing-organization-membership
+- /articles/publicizing-or-hiding-organization-membership
+- /github/setting-up-and-managing-your-github-user-account/publicizing-or-hiding-organization-membership
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/publicizing-or-hiding-organization-membership
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Show or hide membership
+ms.openlocfilehash: a85c9c40f24506ef2e8a9673093b8d7821954cb3
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084740"
+---
+
+
+## 更改组织成员关系的可见性
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. 在成员列表中找到您的用户名。 如果列表很长,可在搜索框中搜索您的用户名。
+
+5. 在用户名右边的菜单中,选择新的可见性选项:
+ - 若要公开成员身份,请选择“公开”。
+ - 若要隐藏成员身份,请选择“隐藏”。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
new file mode 100644
index 0000000000..6067ba970e
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization.md
@@ -0,0 +1,38 @@
+---
+title: 从组织中删除自己
+intro: If you're an outside collaborator or a member of an organization, you can leave the organization at any time.
+redirect_from:
+- /articles/how-do-i-remove-myself-from-an-organization
+- /articles/removing-yourself-from-an-organization
+- /github/setting-up-and-managing-your-github-user-account/removing-yourself-from-an-organization
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/removing-yourself-from-an-organization
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Leave an organization
+ms.openlocfilehash: 72fcc393be287ace20d6c1412f769505117ccef9
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084739"
+---
+{% ifversion fpt or ghec %}
+
+{% warning %}
+
+警告:如果你目前在组织中负责为 {% data variables.product.product_name %} 付款,从组织中删除自己不会更新组织的存档帐单信息 。 如果你目前负责计费,则必须让组织的其他所有者或帐单管理员[更新组织的付款方式](/articles/adding-or-editing-a-payment-method)。
+
+有关详细信息,请参阅“[转让组织所有权](/articles/transferring-organization-ownership)”。
+
+{% endwarning %}
+
+{% endif %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
+3. 在“组织”下,找到你想要从中删除自己的组织,然后单击“离开”。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
new file mode 100644
index 0000000000..f95bb05828
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md
@@ -0,0 +1,35 @@
+---
+title: 请求组织批准 OAuth 应用程序
+intro: Organization members can request that an owner approve access to organization resources for {% data variables.product.prodname_oauth_app %}.
+redirect_from:
+- /articles/requesting-organization-approval-for-third-party-applications
+- /articles/requesting-organization-approval-for-your-authorized-applications
+- /articles/requesting-organization-approval-for-oauth-apps
+- /github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Request OAuth App approval
+ms.openlocfilehash: 4e0f553ebbf8655da6230474e3d2051b6dc5ff2d
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084735"
+---
+## 请求组织批准您已为个人帐户授权的 {% data variables.product.prodname_oauth_app %}
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.access_applications %} {% data reusables.user-settings.access_authorized_oauth_apps %}
+3. 在应用程序列表中,单击您想要请求访问权限的 {% data variables.product.prodname_oauth_app %}的名称。
+
+4. 在你想要 {% data variables.product.prodname_oauth_app %} 访问的组织旁边,单击“请求访问权限”。
+
+5. 审查关于请求 {% data variables.product.prodname_oauth_app %} 访问权限的信息后,单击“请求所有者的批准”。
+
+
+## 延伸阅读
+
+- [关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)
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
new file mode 100644
index 0000000000..a10ce75bcb
--- /dev/null
+++ 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
@@ -0,0 +1,67 @@
+---
+title: 查看组织中人员的角色
+intro: You can view a list of the people in your organization and filter by their role. For more information on organization roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
+permissions: Organization members can see people's roles in the organization.
+redirect_from:
+- /articles/viewing-people-s-roles-in-an-organization
+- /articles/viewing-peoples-roles-in-an-organization
+- /github/setting-up-and-managing-your-github-user-account/viewing-peoples-roles-in-an-organization
+- /github/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: View people in an organization
+ms.openlocfilehash: d492821546b16a7c863d96867ef431362e7056ce
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145084733"
+---
+## 查看组织角色
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. 您将看到组织中人员的列表。 若要按角色筛选列表,请单击“角色”并选择要搜索的角色。
+ 
+
+{% ifversion fpt %}
+
+如果您的组织使用 {% data variables.product.prodname_ghe_cloud %},您还可以查看管理所有企业组织的计费设置和策略的企业所有者。 有关详细信息,请参阅 [{% data variables.product.prodname_ghe_cloud %} 文档](/enterprise-cloud@latest/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/viewing-peoples-roles-in-an-organization#view-enterprise-owners-and-their-roles-in-an-organization)。
+
+{% endif %}
+
+{% if enterprise-owners-visible-for-org-members %}
+## 查看企业所有者及其在组织中的角色
+
+如果您的组织由企业帐户管理,则可以查看管理企业所有组织的帐单设置和策略的企业所有者。 有关企业帐户的详细信息,请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”。
+
+您还可以查看企业所有者是否在组织中具有特定角色。 企业所有者也可以是组织成员、任何其他组织角色,或者是与组织无关的角色。
+
+{% note %}
+
+**注意:** 如果你是组织所有者,还可以邀请企业所有者在组织中担任角色。 如果企业所有者接受邀请,则会从企业的可用许可证中使用组织中的席位或许可证。 有关许可工作原理的详细信息,请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)”。
+
+{% endnote %}
+
+| **企业角色** | **组织角色** | **组织访问或影响** |
+|----|----|----|----|
+| 企业所有者 | 非附属角色或非官方组织角色 | 无法访问组织内容或存储库,但可管理影响组织的企业设置和策略。 |
+| 企业所有者 | 组织所有者 | 能够配置组织设置并通过团队等管理对组织资源的访问。 |
+| 企业所有者 | 组织成员 | 能够访问组织资源和内容(如存储库),而无需访问组织的设置。 |
+
+若要查看组织中的所有角色,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 {% if custom-repository-roles %} 组织成员还可以具有特定存储库的自定义角色。 有关详细信息,请参阅“[管理组织的自定义存储库角色](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)”。{% endif %}
+
+有关企业所有者角色的详细信息,请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-owner)”。
+
+{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.people %}
+4. 在左侧边栏的“企业权限”下,单击“企业所有者”。
+ 
+5. 查看企业的企业所有者列表。 如果企业所有者也是您组织的成员,则您可以看到他们在组织中的角色。
+
+ 
+
+{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
index cd599dfdc0..80e3259548 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md
@@ -1,6 +1,6 @@
---
-title: Inviting collaborators to a personal repository
-intro: 'You can {% ifversion fpt or ghec %}invite users to become{% else %}add users as{% endif %} collaborators to your personal repository.'
+title: 邀请协作者参加个人仓库
+intro: '你可以{% ifversion fpt or ghec %}邀请用户成为{% else %}添加用户作为{% endif %}个人存储库的协作者。'
redirect_from:
- /articles/how-do-i-add-a-collaborator
- /articles/adding-collaborators-to-a-personal-repository
@@ -18,50 +18,49 @@ topics:
- Accounts
- Repositories
shortTitle: Invite collaborators
+ms.openlocfilehash: b8cf147e94d4dd0a76d0bebcb07a58d03d7cbc9e
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/11/2022
+ms.locfileid: '145164797'
---
-Repositories owned by an organization can grant more granular access. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/articles/access-permissions-on-github)."
+组织拥有的仓库可授予更细致的访问权限。 有关详细信息,请参阅“[对 {% data variables.product.prodname_dotcom %} 的访问权限](/articles/access-permissions-on-github)”。
{% data reusables.organizations.org-invite-expiration %}
{% ifversion fpt or ghec %}
-If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you can only invite other members of your enterprise to collaborate with you. {% data reusables.enterprise-accounts.emu-more-info-account %}
+如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则只能邀请企业的其他成员与您协作。 {% data reusables.enterprise-accounts.emu-more-info-account %}
{% note %}
-**Note:** {% data variables.product.company_short %} limits the number of people who can be invited to a repository within a 24-hour period. If you exceed this limit, either wait 24 hours or create an organization to collaborate with more people.
+注意:{% data variables.product.company_short %} 会限制在 24 小时内可受邀加入存储库的人数。 如果您超过此限制,请等待 24 小时后再邀请,或者创建一个组织以与更多的人协作。
{% endnote %}
{% endif %}
-1. Ask for the username of the person you're inviting as a collaborator.{% ifversion fpt or ghec %} If they don't have a username yet, they can sign up for {% data variables.product.prodname_dotcom %} For more information, see "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)".{% endif %}
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4%}
-{% data reusables.repositories.click-collaborators-teams %}
-1. Click **Invite a collaborator**.
- 
-2. In the search field, start typing the name of person you want to invite, then click a name in the list of matches.
- 
-3. Click **Add NAME to REPOSITORY**.
- 
-{% else %}
-5. In the left sidebar, click **Collaborators**.
-
-6. Under "Collaborators", start typing the collaborator's username.
-7. Select the collaborator's username from the drop-down menu.
- 
-8. Click **Add collaborator**.
- 
-{% endif %}
-{% ifversion fpt or ghec %}
-9. The user will receive an email inviting them to the repository. Once they accept your invitation, they will have collaborator access to your repository.
+1. 询问你邀请作为协助者的用户名。{% ifversion fpt or ghec %} 如果他们还没有用户名,他们可以注册 {% data variables.product.prodname_dotcom %}。有关详细信息,请参阅“[注册新的 {% data variables.product.prodname_dotcom %} 帐户](/articles/signing-up-for-a-new-github-account)”。{% endif %} {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658%} {% data reusables.repositories.click-collaborators-teams %}
+1. 单击“邀请协作者”。
+ 
+2. 在搜索字段中,开始键入您想邀请的人员的姓名,然后单击匹配列表中的姓名。
+ 
+3. 单击“将 添加到存储库”。
+  {% else %}
+5. 在左侧边栏中,单击“协作者”。
+
+6. 在 "Collaborators"(协作者)下,开始输入协作者的用户名。
+7. 从下拉菜单中选择协作者的用户名。
+ 
+8. 单击“添加协作者”。
+  {% endif %} {% ifversion fpt or ghec %}
+9. 用户将会收到一封邀请他们参加仓库的电子邮件。 在接受邀请后,他们便对仓库具有协作者访问权限。
{% endif %}
-## Further reading
+## 延伸阅读
-- "[Permission levels for a personal account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account)"
-- "[Removing a collaborator from a personal repository](/articles/removing-a-collaborator-from-a-personal-repository)"
-- "[Removing yourself from a collaborator's repository](/articles/removing-yourself-from-a-collaborator-s-repository)"
-- "[Organizing members into teams](/organizations/organizing-members-into-teams)"
+- “[个人帐户存储库的权限级别](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-personal-account)”
+- [从个人存储库中删除协作者](/articles/removing-a-collaborator-from-a-personal-repository)
+- [从协作者的存储库中删除你自己](/articles/removing-yourself-from-a-collaborator-s-repository)
+- [将成员组织为团队](/organizations/organizing-members-into-teams)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
index e194eea8cd..7c367428f3 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md
@@ -1,6 +1,6 @@
---
-title: Removing a collaborator from a personal repository
-intro: 'When you remove a collaborator from your project, they lose read/write access to your repository. If the repository is private and the person has created a fork, then that fork is also deleted.'
+title: 从个人仓库中删除协作者
+intro: 当您从项目中删除协作者时,他们将失去对您仓库的读取/写入权限。 如果仓库为私有并且该人员已创建复刻,则该复刻也将删除。
redirect_from:
- /articles/how-do-i-remove-a-collaborator
- /articles/what-happens-when-i-remove-a-collaborator-from-my-private-repository
@@ -21,27 +21,28 @@ topics:
- Accounts
- Repositories
shortTitle: Remove a collaborator
+ms.openlocfilehash: 24b128b5858c695b0e559302fac05812d3218b8c
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164728'
---
-## Deleting forks of private repositories
+## 删除私有仓库的复刻
-While forks of private repositories are deleted when a collaborator is removed, the person will still retain any local clones of your repository.
+尽管删除协作者时将删除私有仓库的复刻,但此人员将仍保留您仓库的任何本地克隆。
-## Removing collaborator permissions from a person contributing to a repository
+## 删除为仓库做出贡献的人员的协作者权限
-{% data reusables.repositories.navigate-to-repo %}
-{% data reusables.repositories.sidebar-settings %}
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
-{% data reusables.repositories.click-collaborators-teams %}
-4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
- 
-{% else %}
-3. In the left sidebar, click **Collaborators & teams**.
- 
-4. Next to the collaborator you want to remove, click the **X** icon.
- 
-{% endif %}
+{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %} {% data reusables.repositories.click-collaborators-teams %}
+4. 在要移除的协作者的右侧,单击 {% octicon "trash" aria-label="The trash icon" %}。
+  {% else %}
+3. 在左侧边栏中,单击“协作者和团队”。
+ 
+4. 在要移除的协作者旁边,单击“X”图标。
+  {% endif %}
-## Further reading
+## 延伸阅读
-- "[Removing organization members from a team](/articles/removing-organization-members-from-a-team)"
-- "[Removing an outside collaborator from an organization repository](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
+- [从团队中移除组织成员](/articles/removing-organization-members-from-a-team)
+- [从组织存储库中移除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
index 8e297db83f..02c29e65db 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md
@@ -1,6 +1,6 @@
---
-title: Removing yourself from a collaborator's repository
-intro: 'If you no longer want to be a collaborator on someone else''s repository, you can remove yourself.'
+title: 从协作者的仓库中删除您自己
+intro: 如果您不再想要成为其他人仓库中的协作者,您可以删除自己。
redirect_from:
- /leave-a-collaborative-repo
- /leave-a-repo
@@ -19,15 +19,19 @@ topics:
- Accounts
- Repositories
shortTitle: Remove yourself
+ms.openlocfilehash: 3b760d7947d734d8fa6e1e366795ce698f9c0b7f
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164723'
---
-{% data reusables.user-settings.access_settings %}
-{% ifversion fpt or ghec or ghes > 3.4 or ghae > 3.4 %}
-2. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "repo" aria-label="The repo icon" %} Repositories**.
+{% data reusables.user-settings.access_settings %} {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5658 %}
+2. 在边栏的“代码、规划和自动化”部分,单击“{% octicon "repo" aria-label="The repo icon" %} 存储库”。
{% else %}
-2. In the left sidebar, click **Repositories**.
- 
-{% endif %}
-3. Next to the repository you want to leave, click **Leave**.
- 
-4. Read the warning carefully, then click "I understand, leave this repository."
- 
+2. 在左侧边栏中,单击“存储库”。
+  {% endif %}
+3. 在要离开的存储库旁边,单击“离开”。
+ 
+4. 仔细阅读警告,然后单击“I understand, leave this repository(我已了解,离开此仓库)”。
+ 
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
index 0d8d4fd6b1..ceb6a337d5 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md
@@ -1,6 +1,6 @@
---
-title: Adding an email address to your GitHub account
-intro: '{% data variables.product.product_name %} allows you to add as many email addresses to your account as you like. If you set an email address in your local Git configuration, you will need to add it to your account settings in order to connect your commits to your account. For more information about your email address and commits, see "[Setting your commit email address](/articles/setting-your-commit-email-address/)."'
+title: 添加电子邮件地址到 GitHub 帐户
+intro: '{% data variables.product.product_name %} 允许您根据需要为帐户添加多个电子邮件地址。 如果在本地 Git 配置中设置电子邮件地址,您需要将其添加到帐户设置,以将提交连接到帐户。 有关电子邮件地址和提交的详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address/)”。'
redirect_from:
- /articles/adding-an-email-address-to-your-github-account
- /github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account
@@ -14,24 +14,27 @@ topics:
- Accounts
- Notifications
shortTitle: Add an email address
+ms.openlocfilehash: 082326d96da4b36d1f29830491223ce9b649a15d
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164618'
---
{% ifversion fpt or ghec %}
{% note %}
-**Notes**:
+**注释**:
- {% data reusables.user-settings.no-verification-disposable-emails %}
- - If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your email address on {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.enterprise-accounts.emu-more-info-account %}
+ - 如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则无法在 {% data variables.product.prodname_dotcom_the_website %} 上更改您的电子邮件地址。 {% data reusables.enterprise-accounts.emu-more-info-account %}
{% endnote %}
{% endif %}
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.emails %}
-{% data reusables.user-settings.add_and_verify_email %}
-{% data reusables.user-settings.select_primary_email %}
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}
-## Further reading
+## 延伸阅读
-- "[Managing email preferences](/articles/managing-email-preferences/)"
+- [管理电子邮件首选项](/articles/managing-email-preferences/)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
index a45d2f7f77..8b5f8be27f 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md
@@ -1,6 +1,6 @@
---
-title: Managing email preferences
-intro: 'You can add or change the email addresses associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
+title: 管理电子邮件首选项
+intro: '您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上添加或更改与您的帐户关联的电子邮件地址。 您也可以管理从 {% data variables.product.product_name %} 收到的电子邮件。'
redirect_from:
- /categories/managing-email-preferences
- /articles/managing-email-preferences
@@ -24,5 +24,11 @@ children:
- /types-of-emails-github-sends
- /managing-marketing-emails-from-github
shortTitle: Manage email preferences
+ms.openlocfilehash: 8295d9884f7b2a9bfdef329f693c6492db636a61
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164719'
---
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
index d8d8d78c24..d8c266b968 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md
@@ -1,6 +1,6 @@
---
-title: Remembering your GitHub username or email
-intro: 'Are you signing in to {% data variables.location.product_location %} for the first time in a while? If so, welcome back! If you can''t remember the username for your personal account on {% data variables.product.product_name %}, you can try these methods for remembering it.'
+title: 记住您的 GitHub 用户名或电子邮件
+intro: '是否距离您第一次登录 {% data variables.product.product_location %} 已经有一段时间? 如果是这样,欢迎回来! 如果无法记住 {% data variables.product.product_name %} 上个人帐户的用户名,可以尝试使用以下方法来记住它。'
redirect_from:
- /articles/oh-noes-i-ve-forgotten-my-username-email
- /articles/oh-noes-i-ve-forgotten-my-username-or-email
@@ -16,61 +16,66 @@ topics:
- Accounts
- Notifications
shortTitle: Find your username or email
+ms.openlocfilehash: e65ba973a5ca7865aa642ce5d64f8efa0a996742
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164771'
---
{% mac %}
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %} 用户
-1. In the **GitHub Desktop** menu, click **Preferences**.
-2. In the Preferences window, verify the following:
- - To view your {% data variables.product.product_name %} username, click **Accounts**.
- - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. 在“GitHub 桌面”菜单中,单击“首选项” 。
+2. 在 Preferences(首选项)窗口中,验证以下内容:
+ - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。
+ - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
{% endmac %}
{% windows %}
-## {% data variables.product.prodname_desktop %} users
+## {% data variables.product.prodname_desktop %} 用户
-1. In the **File** menu, click **Options**.
-2. In the Options window, verify the following:
- - To view your {% data variables.product.product_name %} username, click **Accounts**.
- - To view your Git email, click **Git**. Note that this email is not guaranteed to be [your primary {% data variables.product.product_name %} email](/articles/changing-your-primary-email-address).
+1. 在“文件”菜单中,单击“选项” 。
+2. 在 Options(选项)窗口中,验证以下内容:
+ - 若要查看 {% data variables.product.product_name %} 用户名,请单击“帐户”。
+ - 若要查看 Git 电子邮件,请单击“Git”。 请注意,此电子邮件不保证是 [主要 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
{% endwindows %}
-## Finding your username in your `user.name` configuration
+## 在 `user.name` 配置中查找用户名
-During set up, you may have [set your username in Git](/github/getting-started-with-github/setting-your-username-in-git). If so, you can review the value of this configuration setting:
+在设置期间,你可能已[在 Git 中设置用户名](/github/getting-started-with-github/setting-your-username-in-git)。 如果这样,您可以查看此配置设置的值:
```shell
$ git config user.name
# View the setting
-YOUR_USERNAME
+YOUR_USERNAME
```
-## Finding your username in the URL of remote repositories
+## 在远程仓库的 URL 中查找您的用户名
-If you have any local copies of personal repositories you have created or forked, you can check the URL of the remote repository.
+如果您有已创建或已复刻的个人仓库的任何本地副本,则可以检查远程仓库的 URL。
{% tip %}
-**Tip**: This method only works if you have an original repository or your own fork of someone else's repository. If you clone someone else's repository, their username will show instead of yours. Similarly, organization repositories will show the name of the organization instead of a particular user in the remote URL.
+提示:此方法仅当你拥有原始存储库或其他人存储库中你自己的分叉时才有效。 如果您克隆其他人的仓库,将显示他们的用户名而不是您的用户名。 类似地,组织仓库将显示组织的名称,而不是远程 URL 中的特定用户。
{% endtip %}
```shell
-$ cd YOUR_REPOSITORY
+$ cd YOUR_REPOSITORY
# Change directories to the initialized Git repository
$ git remote -v
-origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch)
-origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push)
+origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (fetch)
+origin https://{% data variables.command_line.codeblock %}/YOUR_USERNAME/YOUR_REPOSITORY.git (push)
```
-Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
+用户名紧跟在 `https://{% data variables.command_line.backticks %}/` 后。
{% ifversion fpt or ghec %}
-## Further reading
+## 延伸阅读
-- "[Verifying your email address](/articles/verifying-your-email-address)"
-{% endif %}
+- “[验证电子邮件地址](/articles/verifying-your-email-address)”{% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
index d7da946ab7..14a934c114 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md
@@ -1,6 +1,6 @@
---
-title: Setting your commit email address
-intro: 'You can set the email address that is used to author commits on {% data variables.location.product_location %} and on your computer.'
+title: 设置提交电子邮件地址
+intro: '你可以设置用于在 {% data variables.product.product_location %} 和计算机上创作提交的电子邮件地址。'
redirect_from:
- /articles/keeping-your-email-address-private
- /articles/setting-your-commit-email-address-on-github
@@ -22,61 +22,63 @@ topics:
- Accounts
- Notifications
shortTitle: Set commit email address
+ms.openlocfilehash: 76b0af2a1afa776281434c36cf33fa0e082c2c56
+ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '146338947'
---
-## About commit email addresses
+## 关于提交电子邮件地址
-{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.location.product_location %}. You can choose the email address that will be associated with the commits you push from the command line as well as web-based Git operations you make.
+{% data variables.product.prodname_dotcom %} 使用您的提交电子邮件地址将提交与您的 {% data variables.product.product_location %} 关联。 您可以选择要与从命令行以及基于 web 的 Git 操作推送的提交相关联的电子邮件地址。
-For web-based Git operations, you can set your commit email address on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.location.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
+对于基于 Web 的 Git 操作,您可以在 {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} 上设置提交电子邮件地址。 对于从命令行推送的提交,您可以在 Git 中设置提交电子邮件地址。
-{% ifversion fpt or ghec %}Any commits you made prior to changing your commit email address are still associated with your previous email address.{% else %}After changing your commit email address on {% data variables.product.product_name %}, the new email address will be visible in all of your future web-based Git operations by default. Any commits you made prior to changing your commit email address are still associated with your previous email address.{% endif %}
+{% ifversion fpt or ghec %} 在更改提交电子邮件地址之前进行的提交仍与之前的电子邮件地址关联。{% else %} 在 {% data variables.product.product_name %} 上更改提交电子邮件地址后,新电子邮件地址默认在所有未来基于 Web 的 Git 操作中可见。 在更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。{% endif %}
{% ifversion fpt or ghec %}
{% note %}
-**Note**: {% data reusables.user-settings.no-verification-disposable-emails %}
+注意:{% data reusables.user-settings.no-verification-disposable-emails %}
{% endnote %}
{% endif %}
-{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `noreply` email address from {% data variables.product.product_name %} as your commit email address. To use your `noreply` email address for commits you push from the command line, use that email address when you set your commit email address in Git. To use your `noreply` address for web-based Git operations, set your commit email address on GitHub and choose to **Keep my email address private**.
+{% ifversion fpt or ghec %} 如果想将个人电子邮件地址设为私密,则可以使用 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址作为提交电子邮件地址。 要将 `noreply` 电子邮件地址用于从命令行推送的提交,请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 Web 的 Git 操作,请在 GitHub 上设置提交电子邮件地址并选择“对我的电子邮件地址保密”。
-You can also choose to block commits you push from the command line that expose your personal email address. For more information, see "[Blocking command line pushes that expose your personal email](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)."{% endif %}
+您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 有关详细信息,请参阅“[阻止会暴露个人电子邮件的命令行推送](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)。”{% endif %}
-To ensure that commits are attributed to you and appear in your contributions graph, use an email address that is connected to your account on {% data variables.location.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% endif %}. {% ifversion not ghae %}For more information, see "[Adding an email address to your {% data variables.product.prodname_dotcom %} account](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)."{% endif %}
+为确保提交归因于你并且出现在你的贡献图中,请使用已连接到你在 {% data variables.product.product_location %} 上的帐户的电子邮件地址{% ifversion fpt or ghec %},或者在电子邮件设置中提供给你的 `noreply` 电子邮件地址{% endif %}。 {% ifversion not ghae %} 有关详细信息,请参阅“[将电子邮件地址添加到 {% data variables.product.prodname_dotcom %} 帐户](/github/setting-up-and-managing-your-github-user-account/adding-an-email-address-to-your-github-account)”。{% endif %}
{% ifversion fpt or ghec %}
{% note %}
-**Note:** If you created your account on {% data variables.location.product_location %} _after_ July 18, 2017, your `noreply` email address for {% data variables.product.product_name %} is an ID number and your username in the form of ID+USERNAME@users.noreply.github.com. If you created your account on {% data variables.location.product_location %} _prior to_ July 18, 2017, your `noreply` email address from {% data variables.product.product_name %} is USERNAME@users.noreply.github.com. You can get an ID-based `noreply` email address for {% data variables.product.product_name %} by selecting (or deselecting and reselecting) **Keep my email address private** in your email settings.
+注意:如果于 2017 年 7 月 18 日之后在 {% data variables.product.product_location %} 上创建了帐户,则用于 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址是一个七位数的 ID 号以及格式为 ID+username@users.noreply.github.com 的用户名。 如果于 2017 年 7 月 18 日之前在 {% data variables.product.product_location %} 上创建了帐户,则来自 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址是 username@users.noreply.github.com。 可以通过在电子邮件设置中选择(或取消选择并重新选择)“对我的电子邮件地址保密”,为 {% data variables.product.product_name %} 获取基于 ID 的 `noreply` 电子邮件地址。
{% endnote %}
-If you use your `noreply` email address for {% data variables.product.product_name %} to make commits and then [change your username](/articles/changing-your-github-username), those commits will not be associated with your account on {% data variables.location.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. For more information, see "[Changing your {% data variables.product.prodname_dotcom %} username](/articles/changing-your-github-username)."{% endif %}
+如果使用 {% data variables.product.product_name %} 的 `noreply` 电子邮件地址进行提交,然后[更改用户名](/articles/changing-your-github-username),则这些提交将不会与你在 {% data variables.product.product_location %} 上的帐户相关联。 如果使用的是基于 ID 的 {% data variables.product.product_name %} `noreply` 地址,则不适用。 有关详细信息,请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)。”{% endif %}
-## Setting your commit email address on {% data variables.product.prodname_dotcom %}
+## 在 {% data variables.product.prodname_dotcom %} 上设置提交电子邮件地址
{% data reusables.files.commit-author-email-options %}
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.emails %}
-{% data reusables.user-settings.add_and_verify_email %}
-{% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %}
-{% data reusables.user-settings.keeping_your_email_address_private %}{% endif %}
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.emails %} {% data reusables.user-settings.add_and_verify_email %} {% data reusables.user-settings.select_primary_email %}{% ifversion fpt or ghec %} {% data reusables.user-settings.keeping_your_email_address_private %}{% endif %}
-## Setting your commit email address in Git
+## 在 Git 中设置您的提交电子邮件地址
-You can use the `git config` command to change the email address you associate with your Git commits. The new email address you set will be visible in any future commits you push to {% data variables.location.product_location %} from the command line. Any commits you made prior to changing your commit email address are still associated with your previous email address.
+可以使用 `git config` 命令更改与 Git 提交关联的电子邮件地址。 设置的新电子邮件地址将在从命令行推送到 {% data variables.product.product_location %} 的任何未来提交中显示。 在您更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。
-### Setting your email address for every repository on your computer
+### 为计算机上的每个仓库设置电子邮件地址
{% data reusables.command_line.open_the_multi_os_terminal %}
2. {% data reusables.user-settings.set_your_email_address_in_git %}
```shell
- $ git config --global user.email "YOUR_EMAIL"
+ $ git config --global user.email "email@example.com"
```
3. {% data reusables.user-settings.confirm_git_email_address_correct %}
```shell
@@ -85,17 +87,17 @@ You can use the `git config` command to change the email address you associate w
```
4. {% data reusables.user-settings.link_email_with_your_account %}
-### Setting your email address for a single repository
+### 为一个仓库设置电子邮件地址
-{% data variables.product.product_name %} uses the email address set in your local Git configuration to associate commits pushed from the command line with your account on {% data variables.location.product_location %}.
+{% data variables.product.product_name %} 使用在您的本地 Git 配置中设置的电子邮件地址将从命令行推送的提交与您在 {% data variables.product.product_location %} 上的帐户相关联。
-You can change the email address associated with commits you make in a single repository. This will override your global Git configuration settings in this one repository, but will not affect any other repositories.
+您可以更改与您在一个仓库中所进行的提交关联的电子邮件地址。 此操作将覆盖这一个仓库中的全局 Git 配置设置,但不会影响任何其他仓库。
{% data reusables.command_line.open_the_multi_os_terminal %}
-2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
+2. 将当前工作目录更改为您想要在其中配置与 Git 提交关联的电子邮件地址的本地仓库。
3. {% data reusables.user-settings.set_your_email_address_in_git %}
```shell
- $ git config user.email "YOUR_EMAIL"
+ $ git config user.email "email@example.com"
```
4. {% data reusables.user-settings.confirm_git_email_address_correct %}
```shell
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md
new file mode 100644
index 0000000000..ff4df24a63
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/best-practices-for-leaving-your-company.md
@@ -0,0 +1,47 @@
+---
+title: 关于离开公司的最佳实践
+intro: 如果你的 {% data variables.product.product_name %} 帐户同时用于个人和工作用途,那么你在离开公司或组织的时候需要注意一些问题。
+redirect_from:
+- /articles/best-practices-for-leaving-your-company
+- /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/best-practices-for-leaving-your-company
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Leaving your company
+ms.openlocfilehash: e7de0fa01082731ae54e988ed49310b5ce6afbea
+ms.sourcegitcommit: 8544f120269257d01adfe4a27b62f08fc8691727
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 08/02/2022
+ms.locfileid: "147444643"
+---
+在离开公司之前,请确保在个人帐户中更新以下信息:
+
+- 通过[在电子邮件设置中删除公司电子邮件地址](/articles/changing-your-primary-email-address)来取消其验证。 然后,您可以在不验证的情况下重新添加它,以保留与您的帐户相关联的所有相关提交。
+- [将你的主电子邮件地址](/articles/changing-your-primary-email-address)从公司电子邮件地址更改为个人电子邮件地址。
+- [验证新的主电子邮件地址](/articles/verifying-your-email-address)。
+- [更改你的 GitHub 用户名](/articles/changing-your-github-username)以删除对公司或组织的任何引用(如有必要)。
+- 如果为个人帐户启用了双重 (2FA) 身份验证,请确保由自己(而不是你的公司)控制你已配置的 2FA 身份验证方法。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。
+
+## 离开组织
+
+如果你在使用属于组织的存储库,则应[删除自己的组织成员身份](/articles/removing-yourself-from-an-organization)。 请注意,如果你是组织所有者,应先将[组织的所有权转让](/articles/transferring-organization-ownership)给其他人。
+
+除非使用的是 {% data variables.product.prodname_managed_user %},否则即使离开组织,你仍然可以访问你的个人帐户。 有关 {% data variables.product.prodname_emus %} 的详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}”。{% else %}。{% endif %}
+
+## 删除与个人仓库的职业关联
+
+如果你在属于其他人的个人帐户的存储库中与其进行了专业协作,则应从这些存储库中[删除自己的协作者身份](/articles/removing-yourself-from-a-collaborator-s-repository)。
+
+- [停止关注与工作相关的存储库](https://github.com/watching)。 您不再需要这些通知了!
+- [转让你拥有的存储库](/articles/how-to-transfer-a-repository),在你离开后,其他人可能需要继续使用该存储库处理工作。
+- [删除与你的工作相关且属于你的分支](/articles/deleting-a-repository)。 不用担心,删除复刻不会删除上游仓库。
+- 删除您的计算机上可能存在的复刻本地副本:
+
+```shell
+$ rm -rf work_directory
+```
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
index aad324c45b..dbcb75bc72 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md
@@ -1,6 +1,6 @@
---
-title: Changing your GitHub username
-intro: 'You can change the username for your account on {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.location.product_location %} if your instance uses built-in authentication{% endif %}.'
+title: 更改 GitHub 用户名
+intro: '如果您的实例使用内置身份验证{% endif %},则可以在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %} 上更改帐户的用户名。'
redirect_from:
- /articles/how-to-change-your-username
- /articles/changing-your-github-user-name
@@ -17,19 +17,24 @@ versions:
topics:
- Accounts
shortTitle: Change your username
+ms.openlocfilehash: 28f4d0ea1a16fed0e44f34312abfd507e2f991b7
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145164758'
---
-
{% ifversion ghec or ghes %}
{% note %}
{% ifversion ghec %}
-**Note**: Members of an {% data variables.enterprise.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
+注意:{% data variables.product.prodname_emu_enterprise %} 成员不能更改用户名。 企业的 IdP 管理员控制您的 {% data variables.product.product_name %} 用户名。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
{% elsif ghes %}
-**Note**: If you sign into {% data variables.location.product_location %} with LDAP credentials or single sign-on (SSO), only your local administrator can change your username. For more information about authentication methods for {% data variables.product.product_name %}, see "[Authenticating users for {% data variables.location.product_location %}](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)."
+注意:如果你使用 LDAP 凭据或单一登录 (SSO) 登录 {% data variables.product.product_location %},则只有你的本地管理员才能更改你的用户名。 有关 {% data variables.product.product_name %} 身份验证方法的详细信息,请参阅“[对 {% data variables.product.product_location %} 的用户进行身份验证](/admin/authentication/authenticating-users-for-your-github-enterprise-server-instance)”。
{% endif %}
@@ -37,61 +42,55 @@ shortTitle: Change your username
{% endif %}
-## About username changes
+## 关于用户名更改
-You can change your username to another username that is not currently in use.{% ifversion fpt or ghec %} If the username you want is not available, consider other names or unique variations. Using a number, hyphen, or an alternative spelling might help you find a similar username that's still available.
+您可以将用户名更改为当前未使用的其他用户名。{% ifversion fpt or ghec %} 如果所需的用户名不可用,请考虑其他名称或唯一变体。 使用数字、连字符或其他拼写可能有助于您找到仍可用的类似用户名。
-If you hold a trademark for the username, you can find more information about making a trademark complaint on our [Trademark Policy](/free-pro-team@latest/github/site-policy/github-trademark-policy) page.
+如果你拥有该用户名的商标,可以在我们的[商标政策](/free-pro-team@latest/github/site-policy/github-trademark-policy)页面上找到有关提出商标投诉的更多信息。
-If you do not hold a trademark for the name, you can choose another username or keep your current username. {% data variables.contact.github_support %} cannot release the unavailable username for you. For more information, see "[Changing your username](#changing-your-username)."{% endif %}
+如果您没有该名称的商标,则可以选择其他用户名或保留当前用户名。 {% data variables.contact.github_support %} 无法为您释放不可用的用户名。 有关详细信息,请参阅“[更改用户名](#changing-your-username)”。{% endif %}
-After changing your username, your old username becomes available for anyone else to claim. Most references to your repositories under the old username automatically change to the new username. However, some links to your profile won't automatically redirect.
+更改用户名后,您的旧用户名即可供其他人申请使用。 对旧用户名下仓库的大多数引用会自动更改为新用户名。 不过,指向您个人资料的某些链接不会自动重定向。
-{% data variables.product.product_name %} cannot set up redirects for:
-- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) using your old username
-- Links to [gists](/articles/creating-gists) that include your old username
+{% data variables.product.product_name %} 无法为以下各项设置重定向:
+- 使用旧用户名的 [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
+- 包含旧用户名的 [gists](/articles/creating-gists) 链接
{% ifversion fpt or ghec %}
-If you're a member of an {% data variables.enterprise.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
+如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员,则无法更改用户名。 {% data reusables.enterprise-accounts.emu-more-info-account %}
{% endif %}
-## Repository references
+## 仓库引用
-After you change your username, {% data variables.product.product_name %} will automatically redirect references to your repositories.
-- Web links to your existing repositories will continue to work. This can take a few minutes to complete after you make the change.
-- Command line pushes from your local repository clones to the old remote tracking URLs will continue to work.
+您更改用户名后,{% data variables.product.product_name %} 自动将引用重定向到您的仓库。
+- 指向现有仓库的 Web 链接仍然有效。 进行更改后,可能需要几分钟时间才能完成。
+- 从本地仓库克隆推送到旧的远程跟踪 URL 的命令行仍然有效。
-If the new owner of your old username creates a repository with the same name as your repository, that will override the redirect entry and your redirect will stop working. Because of this possibility, we recommend you update all existing remote repository URLs after changing your username. For more information, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
+如果旧用户名的新所有者创建与您的仓库同名的仓库,则会覆盖重定向条目,并且您的重定向将停止工作。 由于这种可能性,我们建议您在更改用户名后更新所有现有的远程仓库 URL。 有关详细信息,请参阅“[管理远程存储库](/github/getting-started-with-github/managing-remote-repositories)”。
-## Links to your previous profile page
+## 指向以前的个人资料页面的链接
-After changing your username, links to your previous profile page, such as `https://{% data variables.command_line.backticks %}/previoususername`, will return a 404 error. We recommend updating any links to your account on {% data variables.location.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+更改用户名后,指向以前的配置文件页面的链接(例如 `https://{% data variables.command_line.backticks %}/previoususername`)将返回 404 错误。 我们建议从其他位置更新指向 {% data variables.product.product_location %} 帐户的所有链接{% ifversion fpt or ghec %},例如您的 LinkedIn 或 Twitter 个人资料{% endif %}。
-## Your Git commits
+## 您的 Git 提交
-{% ifversion fpt or ghec %}Git commits that were associated with your {% data variables.product.product_name %}-provided `noreply` email address won't be attributed to your new username and won't appear in your contributions graph.{% endif %} If your Git commits are associated with another email address you've [added to your GitHub account](/articles/adding-an-email-address-to-your-github-account), {% ifversion fpt or ghec %}including the ID-based {% data variables.product.product_name %}-provided `noreply` email address, {% endif %}they'll continue to be attributed to you and appear in your contributions graph after you've changed your username. For more information on setting your email address, see "[Setting your commit email address](/articles/setting-your-commit-email-address)."
+{% ifversion fpt or ghec %}与你的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址关联的 Git 提交不会归于新的用户名,并且不会在你的贡献图中显示。{% endif %}如果你的 Git 提交与你已[添加到 GitHub 帐户](/articles/adding-an-email-address-to-your-github-account)的其他电子邮件地址关联,{% ifversion fpt or ghec %}包括基于 ID 的 {% data variables.product.product_name %} 提供的 `noreply` 电子邮件地址,{% endif %}它们在你更改用户名后将继续归于你并在你的贡献图中显示。 有关设置电子邮件地址的详细信息,请参阅“[设置提交电子邮件地址](/articles/setting-your-commit-email-address)”。
-## Your gists
+## 更改用户名
-After changing your username, the URLs to any public or secret gists will also change and previous links to these will return a 404 error. We recommend updating the links to these gists anywhere you may have shared them.
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %}
+3. 在“更改用户名”部分中,单击“更改用户名”。
+ {% ifversion fpt or ghec %}
+4. 阅读有关更改用户名的警告。 如果你仍要更改用户名,请单击“我了解,让我们更改用户名”。
+ 
+5. 键入新的用户名。
+ 
+6. 如果你选择的用户名可用,请单击“更改用户名”。 如果您选择的用户名不可用,可以尝试其他用户名或您看到的建议之一。
+  {% endif %}
-## Changing your username
+## 延伸阅读
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.account_settings %}
-3. In the "Change username" section, click **Change username**.
- {% ifversion fpt or ghec %}
-4. Read the warnings about changing your username. If you still want to change your username, click **I understand, let's change my username**.
- 
-5. Type a new username.
- 
-6. If the username you've chosen is available, click **Change my username**. If the username you've chosen is unavailable, you can try a different username or one of the suggestions you see.
- 
-{% endif %}
-
-## Further reading
-
-- "[Why are my commits linked to the wrong user?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user)"{% ifversion fpt or ghec %}
-- "[{% data variables.product.prodname_dotcom %} Username Policy](/free-pro-team@latest/github/site-policy/github-username-policy)"{% endif %}
+- [我的提交为什么链接到错误的用户?](/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user){% ifversion fpt or ghec %}
+- [{% data variables.product.prodname_dotcom %} 用户名策略](/free-pro-team@latest/github/site-policy/github-username-policy){% endif %}
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
new file mode 100644
index 0000000000..c16f5cfac8
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization.md
@@ -0,0 +1,75 @@
+---
+title: 将用户转换为组织
+redirect_from:
+- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
+- /articles/explaining-the-account-transformation-warning
+- /articles/converting-a-user-into-an-organization
+- /github/setting-up-and-managing-your-github-user-account/converting-a-user-into-an-organization
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
+- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
+intro: 可以将个人帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: User into an organization
+ms.openlocfilehash: 641172d82581ad83bd7281fed941171ce6c817b7
+ms.sourcegitcommit: 2298858ef68ffb4e79490ddbb9d6a64081dfbc39
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 07/21/2022
+ms.locfileid: "147389391"
+---
+{% warning %}
+
+警告:在将用户转换为组织之前,请记住以下几点。
+
+* 你将无法再登录转换后的个人帐户。
+* 你将无法再创建或修改转换后的个人帐户所拥有的 Gist。
+* 组织无法转换回用户。
+* 不会将 SSH 密钥、OAuth 标记、作业配置文件、反应和关联的用户信息传输到组织。 这只适用于被转换的个人帐户,而不适用于该个人帐户的任何协作者。
+* 使用转换后的个人帐户所做的任何提交将不再链接到该帐户。 提交本身将保持不变。
+* 转换后的个人帐户所做的任何现有注释将不再链接至该帐户。 注释本身将保持不变,但会与 `ghost` 用户关联。
+* 将删除使用转换后的个人帐户创建的任何专用存储库的分支。
+{% endwarning %}
+
+{% ifversion fpt or ghec or ghes %}
+## 保留个人帐户并手动创建新组织
+
+如果希望组织的名称与目前用于个人帐户的名称相同,或者要保留个人帐户的信息不变,则必须创建一个新组织,然后将存储库转让给该组织,而不是将个人帐户转换为组织。
+
+1. 要保留当前个人帐户名称以供个人使用,[请将个人帐户名称更改为](/articles/changing-your-github-username)一个好听的新名称。
+2. 使用个人帐户的原始名称[创建新组织](/articles/creating-a-new-organization-from-scratch)。
+3. [将存储库转移到](/articles/transferring-a-repository)新的组织帐户。{% endif %}
+
+## 自动将个人帐户转换为组织
+
+也可以将个人帐户直接转换为组织。 转换帐户:
+ - 按原样保留仓库,无需手动将其转让给另一个帐户
+ - 自动邀请协作者加入具有与其之前相同权限的团队 {% ifversion fpt or ghec %}- 对于 {% data variables.product.prodname_pro %} 上的个人帐户,自动将计费转换到[付费的 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts),无需重新输入付款信息、调整计费周期或随时双倍付款{% endif %}
+
+1. 创建新的个人帐户,转换后您将用它来登录 GitHub 以及访问组织和仓库。
+2. [退出组织](/articles/removing-yourself-from-an-organization)(你要转换的个人帐户已加入的组织)。
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
+5. 在“转换帐户”下,单击“将 转换为组织”。
+ 
+6. 在 Account Transformation Warning(帐户转换警告)对话框中,查看并确认转换。 请注意,此框中的信息与本文顶部的警告信息相同。
+ 
+7. 在“Transform your user into an organization(将用户转换为组织)”页面的“Choose an organization owner(选择组织所有者)”下,选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。
+ 
+8. 选择新组织的订阅,并在提示时输入帐单信息。
+9. 单击“创建组织”。
+10. 登录在第一步中创建的新个人帐户,然后使用上下文切换器访问新组织。
+
+{% tip %}
+
+提示:将个人帐户转换为组织时,我们会将属于该帐户的存储库中的协作者作为外部协作者添加到新组织。 然后,你可以根据需要邀请外部协作者成为新组织的成员。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。
+
+{% endtip %}
+
+## 延伸阅读
+- [设置团队](/articles/setting-up-teams) {% ifversion fpt or ghec %}- [邀请用户加入组织](/articles/inviting-users-to-join-your-organization){% endif %}
+- [访问组织](/articles/accessing-an-organization)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md
new file mode 100644
index 0000000000..1c6a1012b0
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account.md
@@ -0,0 +1,55 @@
+---
+title: 删除个人帐户
+intro: 可随时删除 {% data variables.product.product_name %} 上的个人帐户。
+redirect_from:
+- /articles/deleting-a-user-account
+- /articles/deleting-your-user-account
+- /github/setting-up-and-managing-your-github-user-account/deleting-your-user-account
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
+- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Delete your personal account
+ms.openlocfilehash: 4c02698cbe312d3f13553e49dd324fde4f3ad7bb
+ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 07/13/2022
+ms.locfileid: "145164757"
+---
+删除个人帐户将删除帐户所拥有的所有存储库、专用存储库的分支、Wiki、问题、拉取请求和页面。 {% ifversion fpt or ghec %} 在其他用户拥有的存储库中创建的问题和拉取请求以及所做的评论不会被删除,而是与我们的 [Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的存储库中创建的问题和拉取请求以及所做的评论不会被删除。{% endif %}
+
+{% ifversion fpt or ghec %} 当您删除帐户时,我们会停止对您计费。 与该帐户关联的电子邮件地址可用于 {% data variables.product.product_location %} 上不同的帐户。 90 天后,该帐户名称也可供其他任何人用于新帐户。 {% endif %}
+
+如果你是组织的唯一所有者,则必须先将所有权转让给其他人或删除该组织,然后才能删除个人帐户。 如果组织中有其他所有者,则必须先从组织中删除自己,然后才能删除个人帐户。
+
+有关详细信息,请参阅:
+- [转让组织所有权](/articles/transferring-organization-ownership)
+- [删除组织帐户](/articles/deleting-an-organization-account)
+- [从组织中删除自己](/articles/removing-yourself-from-an-organization/)
+
+## 备份帐户数据
+
+在删除个人帐户之前,请复制帐户所拥有的所有存储库、专用分支、Wiki、问题和拉取请求。
+
+{% warning %}
+
+警告:删除个人帐户后,GitHub 将无法还原内容。
+
+{% endwarning %}
+
+## 删除个人帐户
+
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.account_settings %}
+3. 在帐户设置页面底部的“删除帐户”下,单击“删除帐户”。 在删除个人帐户之前:
+ - 如果您是组织中的唯一所有者,则必须将所有权转让给其他人或删除您的组织。
+ - 如果组织中有其他组织所有者,则必须将自己从组织中删除。
+ 
+4. 在“确认要执行此操作”对话框中,完成相关步骤以确认你了解删除帐户的后果: {% ifversion fpt or ghec %}- 重新确认帐户拥有的所有存储库、专用存储库分支、wiki、问题、拉取请求和 {% data variables.product.prodname_pages %} 站点都将删除,计费将立即结束,并且 90 天后任何人都可在 {% data variables.product.product_name %} 上使用你的用户名。
+ {% else %}- 重新考虑一下,您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除,并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。
+ {% endif %}- 在第一个字段中,输入您的 {% data variables.product.product_name %} 用户名或电子邮件。
+ - 在第二个字段中,键入提示短语。
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
index 25c69e1a94..ec8bc5e53e 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-the-default-branch-name-for-your-repositories.md
@@ -1,6 +1,6 @@
---
-title: Managing the default branch name for your repositories
-intro: 'You can set the default branch name for new repositories that you create on {% data variables.location.product_location %}.'
+title: 管理仓库的默认分支名称
+intro: '您可以为在 {% data variables.product.product_location %} 上创建的新资料库设置默认分支名称。'
versions:
fpt: '*'
ghes: '*'
@@ -13,24 +13,29 @@ redirect_from:
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories
shortTitle: Manage default branch name
+ms.openlocfilehash: a3943f32860f55becaa840f7ca40c13ba87b5ce2
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '145193760'
---
-## About management of the default branch name
+## About the default branch name
-When you create a new repository on {% data variables.location.product_location %}, the repository contains one branch, which is the default branch. You can change the name that {% data variables.product.product_name %} uses for the default branch in new repositories you create. For more information about the default branch, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)."
+当您在 {% data variables.product.product_location %} 上创建一个新仓库时,仓库将包含一个分支,它就是默认分支。 您可以更改 {% data variables.product.product_name %} 用于您新建仓库中默认分支的名称。 有关默认分支的详细信息,请参阅“[关于分支](/github/collaborating-with-issues-and-pull-requests/about-branches#about-the-default-branch)”。
{% data reusables.branches.change-default-branch %}
-## Setting the default branch name
+## 设置默认分支名称
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.repo-tab %}
-3. Under "Repository default branch", click **Change default branch name now**.
- 
-4. Type the default name that you would like to use for new branches.
- 
-5. Click **Update**.
- 
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.repo-tab %}
+3. 在“存储库默认分支”下,单击“立即更改默认分支名称”。
+ 
+4. 键入要用于新分支的默认名称。
+ 
+5. 单击“更新”。
+ 
-## Further reading
+## 延伸阅读
-- "[Managing the default branch name for repositories in your organization](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)"
+- “[管理组织中存储库的默认分支名称](/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization)”
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md
new file mode 100644
index 0000000000..fbb24c1fcd
--- /dev/null
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/merging-multiple-personal-accounts.md
@@ -0,0 +1,53 @@
+---
+title: 合并多个个人帐户
+intro: 如果工作和个人分别使用不同的帐户,您可以合并这些帐户。
+redirect_from:
+- /articles/can-i-merge-two-accounts
+- /articles/keeping-work-and-personal-repositories-separate
+- /articles/merging-multiple-user-accounts
+- /github/setting-up-and-managing-your-github-user-account/merging-multiple-user-accounts
+- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
+- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts
+versions:
+ fpt: '*'
+ ghec: '*'
+topics:
+- Accounts
+shortTitle: Merge multiple personal accounts
+ms.openlocfilehash: 71e2b280fad682f3ee8e9ac85141aedc3bde3d06
+ms.sourcegitcommit: dc42bb4a4826b414751ffa9eed38962c3e3fea8e
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 07/13/2022
+ms.locfileid: "145164791"
+---
+{% tip %}
+
+{% ifversion ghec %}
+
+提示:{% data variables.product.prodname_emus %} 允许企业通过标识提供者 (IdP) 为其成员预配唯一的个人帐户。 有关详细信息,请参阅“[关于企业托管用户](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users)”。 对于其他用例,我们建议仅使用一个个人帐户来管理个人和专业存储库。
+
+{% else %}
+
+提示:我们建议仅使用一个个人帐户来管理个人和专业存储库。
+
+{% endif %}
+
+{% endtip %}
+
+{% warning %}
+
+**警告:**
+- 组织和存储库访问权限不能在帐户之间转让。 如果要删除的帐户具有现有访问权限,则组织所有者或存储库管理员将需要邀请您要保留的帐户。
+- 无法将使用 GitHub 提供的 `noreply` 电子邮件地址创作的任何提交从一个帐户转移到另一个帐户。 如果要删除的帐户使用了“将我的电子邮件地址设为私有”选项,则无法将要删除的帐户创作的提交转移到要保留的帐户。
+
+{% endwarning %}
+
+1. [将任何存储库从要删除的帐户转移](/articles/how-to-transfer-a-repository)到要保留的帐户。 议题、拉取请求和 wiki 也会转让。 确认要保留的帐户中存在仓库。
+2. [更新已移动存储库的任何本地克隆中的远程 URL](/github/getting-started-with-github/managing-remote-repositories)。
+3. [删除不会再使用的帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/deleting-your-personal-account)。
+4. 要将过去的提交归因于新帐户,请将用于创作提交的电子邮件地址添加到要保留的帐户。 有关详细信息,请参阅“[为什么我的贡献没有在我的个人资料中显示?](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile#your-local-git-commit-email-isnt-connected-to-your-account)”
+
+## 延伸阅读
+
+- [{% data variables.product.prodname_dotcom %} 帐户类型](/articles/types-of-github-accounts)
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
index aedaff2bc8..25ab4d853d 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md
@@ -1,6 +1,6 @@
---
-title: Best practices for leaving your company
-intro: 'If you use your account on {% data variables.product.product_name %} for both personal and work purposes, there are a few things to keep in mind when you leave your company or organization.'
+title: 关于离开公司的最佳实践
+intro: '如果你的 {% data variables.product.product_name %} 帐户同时用于个人和工作用途,那么你在离开公司或组织的时候需要注意一些问题。'
redirect_from:
- /articles/best-practices-for-leaving-your-company
- /github/setting-up-and-managing-your-github-user-account/best-practices-for-leaving-your-company
@@ -13,31 +13,36 @@ versions:
topics:
- Accounts
shortTitle: Leaving your company
+ms.openlocfilehash: c288584891981eab7ffe4204e2028b0e70cf1d08
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147687113'
---
+在离开公司之前,请确保在个人帐户中更新以下信息:
-Before you leave your company, make sure you update the following information in your personal account:
+- 通过[在电子邮件设置中删除公司电子邮件地址](/articles/changing-your-primary-email-address)来取消其验证。 然后,您可以在不验证的情况下重新添加它,以保留与您的帐户相关联的所有相关提交。
+- [将你的主电子邮件地址](/articles/changing-your-primary-email-address)从公司电子邮件地址更改为个人电子邮件地址。
+- [验证新的主电子邮件地址](/articles/verifying-your-email-address)。
+- [更改你的 GitHub 用户名](/articles/changing-your-github-username)以删除对公司或组织的任何引用(如有必要)。
+- 如果为个人帐户启用了双重 (2FA) 身份验证,请确保由自己(而不是你的公司)控制你已配置的 2FA 身份验证方法。 有关详细信息,请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。
-- Unverify your company email address by [deleting it in your Email settings](/articles/changing-your-primary-email-address). You can then re-add it without verifying to keep any associated commits linked to your account.
-- [Change your primary email address](/articles/changing-your-primary-email-address) from your company email to your personal email.
-- [Verify your new primary email address](/articles/verifying-your-email-address).
-- [Change your GitHub username](/articles/changing-your-github-username) to remove any references to your company or organization, if necessary.
-- If you've enabled two-factor (2FA) authentication for your personal account, make sure that you (not your company) control the 2FA authentication method you have configured. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)."
+## 离开组织
-## Leaving organizations
+如果你在使用属于组织的存储库,则应[删除自己的组织成员身份](/articles/removing-yourself-from-an-organization)。 请注意,如果你是组织所有者,应先将[组织的所有权转让](/articles/transferring-organization-ownership)给其他人。
-If you've been working with repositories that belong to an organization, you'll want to [remove yourself as a member of the organization](/articles/removing-yourself-from-an-organization). Note that if you are the organization owner, you should first [transfer ownership of the organization](/articles/transferring-organization-ownership) to another person.
+除非使用的是 {% data variables.product.prodname_managed_user %},否则即使离开组织,你仍然可以访问你的个人帐户。 有关 {% data variables.product.prodname_emus %} 的详细信息,请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[关于 {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}”。{% else %}。{% endif %}
-Unless you're using a {% data variables.enterprise.prodname_managed_user %}, you'll still be able to access your personal account, even after leaving the organization. For more information about {% data variables.product.prodname_emus %}, see "[About {% data variables.product.prodname_emus %}]({% ifversion not ghec%}/enterprise-cloud@latest{% endif %}/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
+## 删除与个人仓库的职业关联
-## Removing professional associations with personal repositories
+如果你在属于其他人的个人帐户的存储库中与其进行了专业协作,则应从这些存储库中[删除自己的协作者身份](/articles/removing-yourself-from-a-collaborator-s-repository)。
-If you've been collaborating professionally with another person on repositories that belong to their personal account, you'll want to [remove yourself as a collaborator](/articles/removing-yourself-from-a-collaborator-s-repository) from those repositories.
-
-- [Stop watching repositories](https://github.com/watching) related to your work. You won't want those notifications anymore!
-- [Transfer repositories you own](/articles/how-to-transfer-a-repository) that others may need to continue working on after you leave.
-- [Delete forks that belong to you](/articles/deleting-a-repository) that are related to the work you were doing. Don't worry, deleting a fork doesn't delete the upstream repository.
-- Delete local copies of your forks that may exist on your computer:
+- [停止关注与工作相关的存储库](https://github.com/watching)。 您不再需要这些通知了!
+- [转让你拥有的存储库](/articles/how-to-transfer-a-repository),在你离开后,其他人可能需要继续使用该存储库处理工作。
+- [删除与你的工作相关且属于你的分支](/articles/deleting-a-repository)。 不用担心,删除复刻不会删除上游仓库。
+- 删除您的计算机上可能存在的复刻本地副本:
```shell
-$ rm -rf WORK_DIRECTORY
+$ rm -rf work_directory
```
diff --git a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
index ddfab588a9..5ee9648c36 100644
--- a/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
+++ b/translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md
@@ -1,5 +1,5 @@
---
-title: Converting a user into an organization
+title: 将用户转换为组织
redirect_from:
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization
- /articles/explaining-the-account-transformation-warning
@@ -8,7 +8,7 @@ redirect_from:
- /github/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
- /account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/converting-a-user-into-an-organization
- /account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/converting-a-user-into-an-organization
-intro: You can convert your personal account into an organization. This allows more granular permissions for repositories that belong to the organization.
+intro: 可以将个人帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。
versions:
fpt: '*'
ghes: '*'
@@ -17,58 +17,60 @@ versions:
topics:
- Accounts
shortTitle: User into an organization
+ms.openlocfilehash: 8b99bd119a9fa061c025a4fcc299d7ace31d23eb
+ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/09/2022
+ms.locfileid: '147687079'
---
{% warning %}
-**Warning**: Before converting a user into an organization, keep these points in mind.
+警告:在将用户转换为组织之前,请记住以下几点。
-* You will **no longer** be able to sign into the converted personal account.
-* You will **no longer** be able to create or modify gists owned by the converted personal account.
-* An organization **cannot** be converted back to a user.
-* The SSH keys, OAuth tokens, job profile, reactions, and associated user information, **will not** be transferred to the organization. This is only true for the personal account that's being converted, not any of the personal account's collaborators.
-* Any {% data variables.product.prodname_github_apps %} installed on the converted personal account will be uninstalled.
-* Any commits made with the converted personal account **will no longer be linked** to that account. The commits themselves **will** remain intact.
-* Any existing comments made by the converted personal account **will no longer be linked** to that account. The comments themselves **will** remain intact, but will be associated with the `ghost` user.
-* Any forks of private repositories made with the converted personal account will be deleted.
+* 你将无法再登录转换后的个人帐户。
+* 你将无法再创建或修改转换后的个人帐户所拥有的 Gist。
+* 组织无法转换回用户。
+* 不会将 SSH 密钥、OAuth 标记、作业配置文件、反应和关联的用户信息传输到组织。 这只适用于被转换的个人帐户,而不适用于该个人帐户的任何协作者。
+* 使用转换后的个人帐户所做的任何提交将不再链接到该帐户。 提交本身将保持不变。
+* 转换后的个人帐户所做的任何现有注释将不再链接至该帐户。 注释本身将保持不变,但会与 `ghost` 用户关联。
+* 将删除使用转换后的个人帐户创建的任何专用存储库的分支。
{% endwarning %}
{% ifversion fpt or ghec or ghes %}
-## Keep your personal account and create a new organization manually
+## 保留个人帐户并手动创建新组织
-If you want your organization to have the same name that you are currently using for your personal account, or if you want to keep your personal account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your personal account into an organization.
+如果希望组织的名称与目前用于个人帐户的名称相同,或者要保留个人帐户的信息不变,则必须创建一个新组织,然后将存储库转让给该组织,而不是将个人帐户转换为组织。
-1. To retain your current personal account name for your personal use, [change the name of your personal account](/articles/changing-your-github-username) to something new and wonderful.
-2. [Create a new organization](/articles/creating-a-new-organization-from-scratch) with the original name of your personal account.
-3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.{% endif %}
+1. 要保留当前个人帐户名称以供个人使用,[请将个人帐户名称更改为](/articles/changing-your-github-username)一个好听的新名称。
+2. 使用个人帐户的原始名称[创建新组织](/articles/creating-a-new-organization-from-scratch)。
+3. [将存储库转移到](/articles/transferring-a-repository)新的组织帐户。{% endif %}
-## Convert your personal account into an organization automatically
+## 自动将个人帐户转换为组织
-You can also convert your personal account directly into an organization. Converting your account:
- - Preserves the repositories as they are without the need to transfer them to another account manually
- - Automatically invites collaborators to teams with permissions equivalent to what they had before
- {% ifversion fpt or ghec %}- For personal accounts on {% data variables.product.prodname_pro %}, automatically transitions billing to [the paid {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts) without the need to re-enter payment information, adjust your billing cycle, or double pay at any time{% endif %}
+也可以将个人帐户直接转换为组织。 转换帐户:
+ - 按原样保留仓库,无需手动将其转让给另一个帐户
+ - 自动邀请协作者加入具有与其之前相同权限的团队 {% ifversion fpt or ghec %}- 对于 {% data variables.product.prodname_pro %} 上的个人帐户,自动将计费转换到[付费的 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts),无需重新输入付款信息、调整计费周期或随时双倍付款{% endif %}
-1. Create a new personal account, which you'll use to sign into GitHub and access the organization and your repositories after you convert.
-2. [Leave any organizations](/articles/removing-yourself-from-an-organization) the personal account you're converting has joined.
-{% data reusables.user-settings.access_settings %}
-{% data reusables.user-settings.organizations %}
-5. Under "Transform account", click **Turn into an organization**.
- 
-6. In the Account Transformation Warning dialog box, review and confirm the conversion. Note that the information in this box is the same as the warning at the top of this article.
- 
-7. On the "Transform your user into an organization" page, under "Choose an organization owner", choose either the secondary personal account you created in the previous section or another user you trust to manage the organization.
- 
-8. Choose your new organization's subscription and enter your billing information if prompted.
-9. Click **Create Organization**.
-10. Sign in to the new personal account you created in step one, then use the context switcher to access your new organization.
+1. 创建新的个人帐户,转换后您将用它来登录 GitHub 以及访问组织和仓库。
+2. [退出组织](/articles/removing-yourself-from-an-organization)(你要转换的个人帐户已加入的组织)。
+{% data reusables.user-settings.access_settings %} {% data reusables.user-settings.organizations %}
+5. 在“转换帐户”下,单击“将 转换为组织”。
+ 
+6. 在 Account Transformation Warning(帐户转换警告)对话框中,查看并确认转换。 请注意,此框中的信息与本文顶部的警告信息相同。
+ 
+7. 在“Transform your user into an organization(将用户转换为组织)”页面的“Choose an organization owner(选择组织所有者)”下,选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。
+ 
+8. 选择新组织的订阅,并在提示时输入帐单信息。
+9. 单击“创建组织”。
+10. 登录在第一步中创建的新个人帐户,然后使用上下文切换器访问新组织。
{% tip %}
-**Tip**: When you convert a personal account into an organization, we'll add collaborators on repositories that belong to the account to the new organization as *outside collaborators*. You can then invite *outside collaborators* to become members of your new organization if you wish. For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
+提示:将个人帐户转换为组织时,我们会将属于该帐户的存储库中的协作者作为外部协作者添加到新组织。 然后,你可以根据需要邀请外部协作者成为新组织的成员。 有关详细信息,请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)”。
{% endtip %}
-## Further reading
-- "[Setting up teams](/articles/setting-up-teams)"
-{% ifversion fpt or ghec %}- "[Inviting users to join your organization](/articles/inviting-users-to-join-your-organization)"{% endif %}
-- "[Accessing an organization](/articles/accessing-an-organization)"
+## 延伸阅读
+- [设置团队](/articles/setting-up-teams) {% ifversion fpt or ghec %}- [邀请用户加入组织](/articles/inviting-users-to-join-your-organization){% endif %}
+- [访问组织](/articles/accessing-an-organization)
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
index eed83fb6ff..c93ac3bc0f 100644
--- a/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md
@@ -1,6 +1,6 @@
---
-title: About continuous integration
-intro: 'You can create custom continuous integration (CI) workflows directly in your {% data variables.product.prodname_dotcom %} repository with {% data variables.product.prodname_actions %}.'
+title: 关于持续集成
+intro: '您可以直接在 {% data variables.product.prodname_dotcom %} 仓库中通过 {% data variables.product.prodname_actions %} 创建自定义持续集成 (CI) 工作流程。'
redirect_from:
- /articles/about-continuous-integration
- /github/automating-your-workflow-with-github-actions/about-continuous-integration
@@ -16,45 +16,48 @@ type: overview
topics:
- CI
shortTitle: Continuous integration
+ms.openlocfilehash: 26b9088133ad561900d06a0c885d6b06b9b55861
+ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/10/2022
+ms.locfileid: '147880659'
---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## 关于持续集成
-## About continuous integration
+持续集成 (CI) 是一种需要频繁提交代码到共享仓库的软件实践。 频繁提交代码能较早检测到错误,减少在查找错误来源时开发者需要调试的代码量。 频繁的代码更新也更便于从软件开发团队的不同成员合并更改。 这对开发者非常有益,他们可以将更多时间用于编写代码,而减少在调试错误或解决合并冲突上所花的时间。
-Continuous integration (CI) is a software practice that requires frequently committing code to a shared repository. Committing code more often detects errors sooner and reduces the amount of code a developer needs to debug when finding the source of an error. Frequent code updates also make it easier to merge changes from different members of a software development team. This is great for developers, who can spend more time writing code and less time debugging errors or resolving merge conflicts.
+提交代码到仓库时,可以持续创建并测试代码,以确保提交未引入错误。 您的测试可以包括代码语法检查(检查样式格式)、安全性检查、代码覆盖率、功能测试及其他自定义检查。
-When you commit code to your repository, you can continuously build and test the code to make sure that the commit doesn't introduce errors. Your tests can include code linters (which check style formatting), security checks, code coverage, functional tests, and other custom checks.
+创建和测试代码需要服务器。 您可以在推送代码到仓库之前在本地创建并测试更新,也可以使用 CI 服务器检查仓库中的新代码提交。
-Building and testing your code requires a server. You can build and test updates locally before pushing code to a repository, or you can use a CI server that checks for new code commits in a repository.
+## 关于使用 {% data variables.product.prodname_actions %} 的持续集成
-## About continuous integration using {% data variables.product.prodname_actions %}
-
-{% ifversion ghae %}CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on runner systems that you host. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
-{% else %} CI using {% data variables.product.prodname_actions %} offers workflows that can build the code in your repository and run your tests. Workflows can run on {% data variables.product.prodname_dotcom %}-hosted virtual machines, or on machines that you host yourself. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners)" and "[About self-hosted runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+{% ifversion ghae %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在存储库中生成代码并运行测试的工作流。 工作流程可以在您托管的运行器系统上运行。 有关详细信息,请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners)。
+{% else %}使用 {% data variables.product.prodname_actions %} 的 CI 提供可以在仓库中构建代码并运行测试的工作流程。 工作流程可在 {% data variables.product.prodname_dotcom %} 托管的虚拟机或您自行托管的机器上运行。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_dotcom %} 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners)”和“[关于自托管运行器](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)”。
{% endif %}
-You can configure your CI workflow to run when a {% data variables.product.prodname_dotcom %} event occurs (for example, when new code is pushed to your repository), on a set schedule, or when an external event occurs using the repository dispatch webhook.
+可以配置 CI 工作流,使其在 {% data variables.product.prodname_dotcom %} 事件发生时(例如,当新代码推送到存储库时)运行、按设定的时间表运行,或在使用存储库分发 Webhook 的外部事件发生时运行。
-{% data variables.product.product_name %} runs your CI tests and provides the results of each test in the pull request, so you can see whether the change in your branch introduces an error. When all CI tests in a workflow pass, the changes you pushed are ready to be reviewed by a team member or merged. When a test fails, one of your changes may have caused the failure.
+{% data variables.product.product_name %} 运行 CI 测试并在拉取请求中提供每次测试的结果,因此您可以查看分支中的更改是否引入错误。 如果工作流程中的所有 CI 测试通过,您推送的更改可供团队成员审查或合并 如果测试失败,则是其中某项更改导致了失败。
-When you set up CI in your repository, {% data variables.product.product_name %} analyzes the code in your repository and recommends CI workflows based on the language and framework in your repository. For example, if you use [Node.js](https://nodejs.org/en/), {% data variables.product.product_name %} will suggest a starter workflow that installs your Node.js packages and runs your tests. You can use the CI starter workflow suggested by {% data variables.product.product_name %}, customize the suggested starter workflow, or create your own custom workflow file to run your CI tests.
+如果在仓库中设置了 CI,{% data variables.product.product_name %} 会分析仓库中的代码,并根据仓库中的语言和框架推荐 CI 工作流程。 例如,如果使用 [Node.js](https://nodejs.org/en/),{% data variables.product.product_name %} 将建议使用入门工作流来安装 Node.js 包并运行测试。 您可以使用 {% data variables.product.product_name %} 建议的 CI 入门工作流程,自定义建议的入门工作流程,或创建自己的自定义工作流程文件来运行 CI 测试。
-
+
-In addition to helping you set up CI workflows for your project, you can use {% data variables.product.prodname_actions %} to create workflows across the full software development life cycle. For example, you can use actions to deploy, package, or release your project. For more information, see "[About {% data variables.product.prodname_actions %}](/articles/about-github-actions)."
+除了帮助设置项目的 CI 工作流程之外,您还可以使用 {% data variables.product.prodname_actions %} 创建跨整个软件开发生命周期的工作流程。 例如,您可以使用操作来部署、封装或发行项目。 有关详细信息,请参阅“[关于 {% data variables.product.prodname_actions %}](/articles/about-github-actions)”。
-For a definition of common terms, see "[Core concepts for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)."
+有关常用术语的定义,请参阅“[{% data variables.product.prodname_actions %} 的核心概念](/github/automating-your-workflow-with-github-actions/core-concepts-for-github-actions)”。
-## Starter workflow
+## 入门工作流程
-{% data variables.product.product_name %} offers CI starter workflow for a variety of languages and frameworks.
+{% data variables.product.product_name %} 为各种语言和框架提供 CI 入门工作流程。
-Browse the complete list of CI starter workflow offered by {% data variables.product.company_short %} in the {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) repository{% else %} `actions/starter-workflows` repository on {% data variables.location.product_location %}{% endif %}.
+在 {% ifversion fpt or ghec %}[actions/starter-workflows](https://github.com/actions/starter-workflows/tree/main/ci) 存储库{% else %} {% data variables.product.product_location %} 上的 `actions/starter-workflows` 存储库{% endif %}中浏览 {% data variables.product.company_short %} 提供的 CI 入门工作流的完整列表。
-## Further reading
+## 延伸阅读
{% ifversion fpt or ghec %}
-- "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)"
-{% endif %}
+- [管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions){% endif %}
diff --git a/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
new file mode 100644
index 0000000000..871dc61d02
--- /dev/null
+++ b/translations/zh-CN/content/actions/automating-builds-and-tests/building-and-testing-nodejs-or-python.md
@@ -0,0 +1,22 @@
+---
+title: 构建并测试 Node.js 或 Python
+shortTitle: Build & test Node.js or Python
+intro: You can create a continuous integration (CI) workflow to build and test your project. Use the language selector to show examples for your language of choice.
+redirect_from:
+- /actions/guides/building-and-testing-nodejs-or-python
+versions:
+ fpt: '*'
+ ghes: '*'
+ ghae: '*'
+ ghec: '*'
+type: tutorial
+topics:
+- CI
+ms.openlocfilehash: aa03416907eb05ac6c31081d51dcb50980a3501f
+ms.sourcegitcommit: 67064b14c9d4d18819db8f6398358b77a1c8002a
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 05/17/2022
+ms.locfileid: "145086739"
+---
+
diff --git a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
index 6ea8fbe52c..0ddda1a6c9 100644
--- a/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
+++ b/translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md
@@ -1,7 +1,6 @@
---
-title: Creating a Docker container action
-shortTitle: Create a Docker container action
-intro: 'This guide shows you the minimal steps required to build a Docker container action. '
+title: 创建 Docker 容器操作
+intro: '本指南向您展示构建 Docker 容器操作所需的最少步骤。 '
redirect_from:
- /articles/creating-a-docker-container-action
- /github/automating-your-workflow-with-github-actions/creating-a-docker-container-action
@@ -16,47 +15,50 @@ type: tutorial
topics:
- Action development
- Docker
+shortTitle: Docker container action
+ms.openlocfilehash: f22b361f25f406dfdb1233f4d9ce62f2b6b919dc
+ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 09/05/2022
+ms.locfileid: '147518782'
---
+{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
-{% data reusables.actions.enterprise-beta %}
-{% data reusables.actions.enterprise-github-hosted-runners %}
+## 简介
-## Introduction
+在本指南中,您将了解创建和使用打包的 Docker 容器操作所需的基本组件。 本指南的重点是打包操作所需的组件,因此很少讲操作代码的功能。 操作将在日志文件中打印“Hello World”或“Hello [who-to-greet]”(如果您提供自定义名称)。
-In this guide, you'll learn about the basic components needed to create and use a packaged Docker container action. To focus this guide on the components needed to package the action, the functionality of the action's code is minimal. The action prints "Hello World" in the logs or "Hello [who-to-greet]" if you provide a custom name.
-
-Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
+完成此项目后,您应了解如何构建自己的 Docker 容器操作和在工作流程测试该操作。
{% data reusables.actions.self-hosted-runner-reqs-docker %}
{% data reusables.actions.context-injection-warning %}
-## Prerequisites
+## 先决条件
-You may find it helpful to have a basic understanding of {% data variables.product.prodname_actions %} environment variables and the Docker container filesystem:
+您可能会发现它有助于基本了解 {% data variables.product.prodname_actions %} 环境变量和 Docker 容器文件系统:
-- "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)"
-{% ifversion ghae %}
-- "[Docker container filesystem](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)."
-{% else %}
-- "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)"
-{% endif %}
+- “[使用环境变量](/actions/automating-your-workflow-with-github-actions/using-environment-variables)”{% ifversion ghae %}
+- “[Docker 容器文件系统](/actions/using-github-hosted-runners/about-ae-hosted-runners#docker-container-filesystem)”
+{% else %}
+- “[关于 {% data variables.product.prodname_dotcom %} 托管的运行器](/actions/using-github-hosted-runners/about-github-hosted-runners#docker-container-filesystem)”{% endif %}
-Before you begin, you'll need to create a {% data variables.product.prodname_dotcom %} repository.
+在开始之前,您需要创建 {% data variables.product.prodname_dotcom %} 仓库。
-1. Create a new repository on {% data variables.location.product_location %}. You can choose any repository name or use "hello-world-docker-action" like this example. For more information, see "[Create a new repository](/articles/creating-a-new-repository)."
+1. 在 {% data variables.product.product_location %} 上新建存储库。 您可以选择任何仓库名称或如本例一样使用“hello-world-docker-action”。 有关详细信息,请参阅“[创建新存储库](/articles/creating-a-new-repository)”。
-1. Clone your repository to your computer. For more information, see "[Cloning a repository](/articles/cloning-a-repository)."
+1. 将仓库克隆到计算机。 有关详细信息,请参阅“[克隆存储库](/articles/cloning-a-repository)”。
-1. From your terminal, change directories into your new repository.
+1. 从您的终端,将目录更改为新仓库。
```shell{:copy}
cd hello-world-docker-action
```
-## Creating a Dockerfile
+## 创建 Dockerfile
-In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[Dockerfile support for {% data variables.product.prodname_actions %}](/actions/creating-actions/dockerfile-support-for-github-actions)."
+在新的 `hello-world-docker-action` 目录中,创建一个新的 `Dockerfile` 文件。 如果你有问题,请确保你的文件名正确大写(使用大写字母 `D` 但不要大写 `f`)。 有关详细信息,请参阅“[{% data variables.product.prodname_actions %} 的 Dockerfile 支持](/actions/creating-actions/dockerfile-support-for-github-actions)”。
**Dockerfile**
```Dockerfile{:copy}
@@ -70,12 +72,11 @@ COPY entrypoint.sh /entrypoint.sh
ENTRYPOINT ["/entrypoint.sh"]
```
-## Creating an action metadata file
+## 创建操作元数据文件
-Create a new `action.yml` file in the `hello-world-docker-action` directory you created above. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/actions/creating-actions/metadata-syntax-for-github-actions)."
+在上面创建的 `hello-world-docker-action` 目录中创建一个新的 `action.yml` 文件。 有关详细信息,请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/actions/creating-actions/metadata-syntax-for-github-actions)”。
-{% raw %}
-**action.yml**
+{% raw %} action.yml
```yaml{:copy}
# action.yml
name: 'Hello World'
@@ -96,63 +97,50 @@ runs:
```
{% endraw %}
-This metadata defines one `who-to-greet` input and one `time` output parameter. To pass inputs to the Docker container, you should declare the input using `inputs` and pass the input in the `args` keyword. Everything you include in `args` is passed to the container, but for better discoverability for users of your action, we recommended using inputs.
+此元数据定义一个 `who-to-greet` 输入和一个 `time` 输出参数。 若要将输入传递给 Docker 容器,应使用 `inputs` 声明输入并在 `args` 关键字中传递输入。 你包含在 `args` 中的所有内容都会传递给容器,但为了让用户更好地发现你的操作,建议使用输入。
-{% data variables.product.prodname_dotcom %} will build an image from your `Dockerfile`, and run commands in a new container using this image.
+{% data variables.product.prodname_dotcom %} 将从 `Dockerfile` 构建映像,然后使用此映像在新容器中运行命令。
-## Writing the action code
+## 编写操作代码
-You can choose any base Docker image and, therefore, any language for your action. The following shell script example uses the `who-to-greet` input variable to print "Hello [who-to-greet]" in the log file.
+您可以选择任何基础 Docker 映像,并因此为您的操作选择任何语言。 以下 shell 脚本示例使用 `who-to-greet` 输入变量在日志文件中打印“Hello [who-to-greet]”。
-Next, the script gets the current time and sets it as an output variable that actions running later in a job can use. In order for {% data variables.product.prodname_dotcom %} to recognize output variables, you must {% ifversion actions-save-state-set-output-envs %}write them to the `$GITHUB_OUTPUT` environment file: `echo "