Octomerger Bot
@@ -1,18 +1,38 @@
|
||||
file,reason
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/index.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/viewing-your-subscriptions.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/about-notifications.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/index.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/managing-notifications-from-your-inbox.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile.md,rendering error
|
||||
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,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-access-to-your-personal-repositories/index.md,rendering error
|
||||
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,rendering error
|
||||
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,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/index.md,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/changing-your-github-username.md,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/deleting-your-user-account.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/index.md,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-accessibility-settings.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-the-default-branch-name-for-your-repositories.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-theme-settings.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/merging-multiple-user-accounts.md,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-your-membership-in-organizations/accessing-an-organization.md,rendering error
|
||||
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,rendering error
|
||||
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,rendering error
|
||||
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,rendering error
|
||||
translations/zh-CN/content/actions/advanced-guides/caching-dependencies-to-speed-up-workflows.md,rendering error
|
||||
translations/zh-CN/content/actions/advanced-guides/storing-workflow-data-as-artifacts.md,rendering error
|
||||
translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
|
||||
@@ -233,17 +253,28 @@ translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your
|
||||
translations/zh-CN/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md,rendering error
|
||||
translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/about-authentication-with-saml-single-sign-on.md,rendering error
|
||||
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md,rendering error
|
||||
translations/zh-CN/content/authentication/index.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-anonymized-urls.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/authorizing-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/connecting-with-third-party-applications.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/creating-a-strong-password.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/index.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-security-log.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-ssh-keys.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/about-commit-signature-verification.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/signing-commits.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/index.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-unknown-key-type.md,rendering error
|
||||
translations/zh-CN/content/billing/index.md,rendering error
|
||||
@@ -305,7 +336,6 @@ translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-de
|
||||
translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-default-region-for-codespaces.md,rendering error
|
||||
translations/zh-CN/content/codespaces/customizing-your-codespace/setting-your-timeout-period-for-codespaces.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/codespaces-lifecycle.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/connecting-to-a-private-network.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,rendering error
|
||||
@@ -368,11 +398,25 @@ translations/zh-CN/content/education/manage-coursework-with-github-classroom/tea
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-autograding.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,rendering error
|
||||
translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/exploring-projects-on-github/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/exploring-projects-on-github/saving-repositories-with-stars.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/caching-your-github-credentials-in-git.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/configuring-git-to-handle-line-endings.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/git-workflows.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/ignoring-files.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/updating-credentials-from-the-macos-keychain.md,rendering error
|
||||
translations/zh-CN/content/get-started/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/be-social.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/communicating-on-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/create-a-repo.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
@@ -382,16 +426,26 @@ translations/zh-CN/content/get-started/quickstart/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/set-up-git.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-ae.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/about-git-rebase.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/about-git-subtree-merges.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/about-git.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/dealing-with-non-fast-forward-errors.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/getting-changes-from-a-remote-repository.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/pushing-commits-to-a-remote-repository.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-git/using-git-rebase-on-the-command-line.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/github-mobile.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/index.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/supported-browsers.md,rendering error
|
||||
translations/zh-CN/content/github-cli/github-cli/creating-github-cli-extensions.md,rendering error
|
||||
translations/zh-CN/content/github/customizing-your-github-workflow/exploring-integrations/about-github-marketplace.md,rendering error
|
||||
translations/zh-CN/content/github/importing-your-projects-to-github/importing-source-code-to-github/adding-an-existing-project-to-github-using-the-command-line.md,rendering error
|
||||
translations/zh-CN/content/github/index.md,rendering error
|
||||
translations/zh-CN/content/github/site-policy/github-terms-for-additional-products-and-features.md,rendering error
|
||||
translations/zh-CN/content/github/site-policy/github-terms-of-service.md,rendering error
|
||||
translations/zh-CN/content/github/understanding-how-github-uses-and-protects-your-data/managing-data-use-settings-for-your-private-repository.md,rendering error
|
||||
@@ -484,6 +538,7 @@ translations/zh-CN/content/rest/guides/basics-of-authentication.md,rendering err
|
||||
translations/zh-CN/content/rest/guides/discovering-resources-for-a-user.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/getting-started-with-the-checks-api.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,rendering error
|
||||
translations/zh-CN/content/rest/guides/traversing-with-pagination.md,rendering error
|
||||
translations/zh-CN/content/rest/index.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/api-previews.md,rendering error
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,Listed in localization-support#489
|
||||
|
||||
|
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 在 GitHub 上管理订阅和通知
|
||||
intro: 您可以指定如何接收通知，您感兴趣的仓库，以及您想要听到的活动类型。
|
||||
title: Managing subscriptions and notifications on GitHub
|
||||
intro: 'You can specify how to receive notifications, the repositories you are interested in, and the types of activity you want to hear about.'
|
||||
redirect_from:
|
||||
- /categories/76/articles/
|
||||
- /categories/notifications/
|
||||
- /categories/76/articles
|
||||
- /categories/notifications
|
||||
- /categories/receiving-notifications-about-activity-on-github
|
||||
- /github/managing-subscriptions-and-notifications-on-github
|
||||
versions:
|
||||
@@ -17,6 +17,6 @@ children:
|
||||
- /setting-up-notifications
|
||||
- /viewing-and-triaging-notifications
|
||||
- /managing-subscriptions-for-activity-on-github
|
||||
shortTitle: 订阅和通知
|
||||
shortTitle: Subscriptions & notifications
|
||||
---
|
||||
|
||||
|
||||
@@ -2,16 +2,16 @@
|
||||
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.'
|
||||
redirect_from:
|
||||
- /articles/subscribing-to-conversations/
|
||||
- /articles/unsubscribing-from-conversations/
|
||||
- /articles/subscribing-to-conversations
|
||||
- /articles/unsubscribing-from-conversations
|
||||
- /articles/subscribing-to-and-unsubscribing-from-notifications
|
||||
- /articles/listing-the-issues-and-pull-requests-youre-subscribed-to
|
||||
- /articles/watching-repositories/
|
||||
- /articles/unwatching-repositories/
|
||||
- /articles/watching-repositories
|
||||
- /articles/unwatching-repositories
|
||||
- /articles/watching-and-unwatching-repositories
|
||||
- /articles/watching-and-unwatching-releases-for-a-repository
|
||||
- /articles/watching-and-unwatching-team-discussions
|
||||
- /articles/listing-watched-repositories/
|
||||
- /articles/listing-watched-repositories
|
||||
- /articles/listing-the-repositories-you-re-watching
|
||||
- /articles/listing-the-repositories-youre-watching
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: About notifications
|
||||
intro: 'Notifications provide updates about the activity on {% data variables.product.product_location %} that you''ve subscribed to. You can use the notifications inbox to customize, triage, and manage your updates.'
|
||||
redirect_from:
|
||||
- /articles/notifications/
|
||||
- /articles/notifications
|
||||
- /articles/about-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications-beta
|
||||
- /github/managing-subscriptions-and-notifications-on-github/about-notifications
|
||||
|
||||
@@ -3,16 +3,16 @@ 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.'
|
||||
redirect_from:
|
||||
- /articles/about-web-notifications
|
||||
- /format-of-notification-emails/
|
||||
- /articles/configuring-notification-emails/
|
||||
- /articles/about-notification-emails/
|
||||
- /format-of-notification-emails
|
||||
- /articles/configuring-notification-emails
|
||||
- /articles/about-notification-emails
|
||||
- /articles/about-email-notifications
|
||||
- /articles/accessing-your-notifications
|
||||
- /articles/configuring-notification-delivery-methods/
|
||||
- /articles/managing-notification-delivery-methods/
|
||||
- /articles/managing-notification-emails-for-organizations/
|
||||
- /articles/configuring-notification-delivery-methods
|
||||
- /articles/managing-notification-delivery-methods
|
||||
- /articles/managing-notification-emails-for-organizations
|
||||
- /articles/choosing-the-delivery-method-for-your-notifications
|
||||
- /articles/choosing-the-types-of-notifications-you-receive/
|
||||
- /articles/choosing-the-types-of-notifications-you-receive
|
||||
- /github/managing-subscriptions-and-notifications-on-github/configuring-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications
|
||||
versions:
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 查看和分类通知
|
||||
intro: 为优化通知工作流程，您可以自定义如何查看通知以及对通知分类。
|
||||
title: Viewing and triaging notifications
|
||||
intro: 'To optimize your notifications workflow, you can customize how you view and triage notifications.'
|
||||
redirect_from:
|
||||
- /articles/managing-notifications/
|
||||
- /articles/managing-notifications
|
||||
- /articles/managing-your-notifications
|
||||
- /github/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications
|
||||
versions:
|
||||
@@ -16,6 +16,6 @@ children:
|
||||
- /managing-notifications-from-your-inbox
|
||||
- /triaging-a-single-notification
|
||||
- /customizing-a-workflow-for-triaging-your-notifications
|
||||
shortTitle: 自定义工作流程
|
||||
shortTitle: Customize a workflow
|
||||
---
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: About your profile
|
||||
intro: 'Your profile page tells people the story of your work through the repositories you''re interested in, the contributions you''ve made, and the conversations you''ve had.'
|
||||
redirect_from:
|
||||
- /articles/viewing-your-feeds/
|
||||
- /articles/profile-pages/
|
||||
- /articles/viewing-your-feeds
|
||||
- /articles/profile-pages
|
||||
- /articles/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/about-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 个性化您的个人资料
|
||||
intro: '您可以在个人资料中设置头像和添加个人简历，与其他 {% data variables.product.product_name %} 用户共享您自己的信息。'
|
||||
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.'
|
||||
redirect_from:
|
||||
- /articles/adding-a-bio-to-your-profile/
|
||||
- /articles/setting-your-profile-picture/
|
||||
- /articles/how-do-i-set-up-my-profile-picture/
|
||||
- /articles/gravatar-problems/
|
||||
- /articles/how-do-i-set-up-my-avatar/
|
||||
- /articles/adding-a-bio-to-your-profile
|
||||
- /articles/setting-your-profile-picture
|
||||
- /articles/how-do-i-set-up-my-profile-picture
|
||||
- /articles/gravatar-problems
|
||||
- /articles/how-do-i-set-up-my-avatar
|
||||
- /articles/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/personalizing-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile
|
||||
@@ -17,200 +17,216 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: 个性化
|
||||
shortTitle: Personalize
|
||||
---
|
||||
## 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 %} 的拉取请求、评论、参与页面及图形中识别您。
|
||||
|
||||
在注册帐户时，{% data variables.product.product_name %} 会提供一个随机生成的“默认肖像”。 [默认肖像](https://github.com/blog/1586-identicons)从用户 ID 的哈希生成，因此无法控制其颜色或图案。 您可以将默认肖像替换为能代表您的图片。
|
||||
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.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：头像应为 1 MB 以下的 PNG、JPG 或 GIF 文件。 为获取质量最佳的渲染，建议图像的像素保持在大约 500 x 500 像素。
|
||||
**Tip**: Your profile picture should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
### 设置头像
|
||||
### Setting a profile picture
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在 **Profile Picture（头像）**下，单击 {% octicon "pencil" aria-label="The edit icon" %} **Edit（编辑）**。 
|
||||
3. 单击 **Upload a photo...（上传图片...）**。 
|
||||
3. 裁剪图片。 完成后，单击 **Set new profile picture（设置新头像）**。 
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. Click **Upload a photo...**.
|
||||
|
||||
3. Crop your picture. When you're done, click **Set new profile picture**.
|
||||
|
||||
|
||||
### 将头像重置为默认肖像
|
||||
### Resetting your profile picture to the identicon
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在 **Profile Picture（头像）**下，单击 {% octicon "pencil" aria-label="The edit icon" %} **Edit（编辑）**。 
|
||||
3. 要还原为默认肖像，请单击 **Remove photo（删除照片）**。 如果您的电子邮件地址与[个人全球统一标识](https://en.gravatar.com/)关联，则无法还原到默认肖像。 此时请单击 **Revert to Gravatar（还原到个人全球统一标识）**。 
|
||||
2. Under **Profile Picture**, click {% octicon "pencil" aria-label="The edit icon" %} **Edit**.
|
||||
|
||||
3. To revert to your identicon, click **Remove photo**. If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Click **Revert to Gravatar** instead.
|
||||
|
||||
|
||||
## 更改个人资料名称
|
||||
## Changing your profile name
|
||||
|
||||
您可以更改显示在个人资料中的名称。 此名称也可能显示在您对于组织拥有的私有仓库所做的注释旁边。 更多信息请参阅“[管理组织中成员名称的显示](/articles/managing-the-display-of-member-names-in-your-organization)”。
|
||||
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)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% note %}
|
||||
|
||||
**注：** 如果您是 {% data variables.product.prodname_emu_enterprise %} 的成员，则必须通过您的身份提供商而不是 {% data variables.product.prodname_dotcom_the_website %} 对您的个人资料名称进行任何更改。 {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
**Note:** If you're a member of an {% data variables.product.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 %}
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在“Name（名称）”下，键入要显示在个人资料中的名称。 
|
||||
2. Under "Name", type the name you want to be displayed on your profile.
|
||||
|
||||
|
||||
## 在个人资料中添加个人简历
|
||||
## Adding a bio to your profile
|
||||
|
||||
在个人资料中添加个人简历，与其他 {% data variables.product.product_name %} 用户共享您自己的信息。 借助 [@提及](/articles/basic-writing-and-formatting-syntax)和表情符号，可以包含您当前或以前的工作经历、工作类型甚至您喜欢的咖啡种类。
|
||||
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.
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
要以更长和更突出的方式显示有关自己的自定义信息，您还可以使用个人资料自述文件。 更多信息请参阅“[管理个人资料自述文件](/github/setting-up-and-managing-your-github-profile/managing-your-profile-readme)”。
|
||||
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)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注：** 如果为个人资料启用了活动概述部分，并且您在个人资料的个人简历中 @提及您所属的组织，则该组织会先出现在活动概述中。 更多信息请参阅“[在您的个人资料中显示活动概述](/articles/showing-an-overview-of-your-activity-on-your-profile)”。
|
||||
**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)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在 **Bio（个人简历）**下，添加您要显示在个人资料中的内容。 个人资料字段限于 160 个字符。 
|
||||
2. Under **Bio**, add the content that you want displayed on your profile. The bio field is limited to 160 characters.
|
||||
|
||||
|
||||
{% 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.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
3. 单击 **Update profile（更新个人资料）**。 
|
||||
3. Click **Update profile**.
|
||||
|
||||
|
||||
## 设置状态
|
||||
## Setting a status
|
||||
|
||||
您可以设置状态以显示您当前在 {% 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 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/)."
|
||||
|
||||
在设置状态时，您也可以让人们知道您在 {% data variables.product.product_name %} 上的可用性有限。
|
||||
When you set your status, you can also let people know that you have limited availability on {% data variables.product.product_name %}.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
如果选择“Busy（忙碌）”选项，当人们 @提及您的用户名、向您分配议题或拉取请求或者申请您进行拉取请求审查时，您的用户名旁边将会出现一条表示您在忙碌的注释。 您还将被排除在分配给您所属的任何团队的拉取请求的自动审核任务之外。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."
|
||||
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 your status** or, if you already have a status set, click your current status. 
|
||||
2. 要添加自定义文本到状态，请单击文本字段，然后输入状态消息。 
|
||||
3. （可选）要设置表情符号状态，请单击笑脸图标并从列表中选择表情符号。 
|
||||
4. （可选）如果想表示您的可用性受限，请选择“Busy（忙碌）”。 
|
||||
5. 使用 **Clear status（清除状态）**下拉菜单，选择状态的到期时间。 如果不选择状态到期时间，您的状态将保持到您清除或编辑状态为止。 
|
||||
6. 使用下拉菜单，单击您要向其显示状态的组织。 如果不选择组织，您的状态将是公共的。 
|
||||
7. 单击 **Set status（设置状态）**。 
|
||||
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 your 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**.
|
||||
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 在个人资料中显示徽章
|
||||
## Displaying badges on your profile
|
||||
|
||||
当您参与某些计划时， {% data variables.product.prodname_dotcom %} 会自动在您的个人资料中显示徽章。
|
||||
When you participate in certain programs, {% data variables.product.prodname_dotcom %} automatically displays a badge on your profile.
|
||||
|
||||
| 徽章 | 计划 | 描述 |
|
||||
| ------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
|  | **Mars 2020 Helicopter 贡献者** | 如果您在提交历史记录中撰写了对 Mars 2020 Helicopter 任务中使用的开放源码库相关标记的任何提交， 您将在个人资料上获得 Mars 2020 Helicopter 贡献者徽章。 悬停在徽章上会显示您参与的任务中使用的几个仓库。 要查看符合您徽章资格的完整仓库列表，请参阅“[Mars 2020 Helicopter 贡献者徽章的合格仓库列表](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)”。 |
|
||||
|  | **{% data variables.product.prodname_arctic_vault %} 贡献者** | 如果您在存档于 2020 Arctic Vault 计划的仓库默认分支上编写了任何提交，您的个人资料上会获得一个 {% data variables.product.prodname_arctic_vault %} 贡献者徽章。 悬停在徽章上显示您参与的属于计划一部分的几个仓库。 有关该计划的更多信息，请参阅 [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com)。 |
|
||||
|  | **{% data variables.product.prodname_dotcom %} 赞助者** | 如果您通过 {% data variables.product.prodname_sponsors %} 赞助了开源贡献者，您的个人资料中将获得一个 {% data variables.product.prodname_dotcom %} 赞助者徽章。 单击徽章将带您到个人资料的 **Sponsoring（赞助）**选项卡。 更多信息请参阅“[赞助开源贡献者](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)”。 |
|
||||
| {% octicon "cpu" aria-label="The Developer Program icon" %} | **开发者计划成员** | 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. 有关 {% 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 %} 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. 有关校园专家计划的更多信息，请参阅 [Campus Experts](https://education.github.com/experts)。 |
|
||||
| Badge | Program | Description |
|
||||
| --- | --- | --- |
|
||||
|  | **Mars 2020 Helicopter Contributor** | If you authored any commit(s) present in the commit history for the relevant tag of an open source library used in the Mars 2020 Helicopter Mission, you'll get a Mars 2020 Helicopter Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were used in the mission. For the full list of repositories that will qualify you for the badge, see "[List of qualifying repositories for Mars 2020 Helicopter Contributor badge](/github/setting-up-and-managing-your-github-profile/personalizing-your-profile#list-of-qualifying-repositories-for-mars-2020-helicopter-contributor-badge)." |
|
||||
|  | **{% data variables.product.prodname_arctic_vault %} Contributor** | If you authored any commit(s) on the default branch of a repository that was archived in the 2020 Arctic Vault program, you'll get an {% data variables.product.prodname_arctic_vault %} Contributor badge on your profile. Hovering over the badge shows you several of the repositories you contributed to that were part of the program. For more information on the program, see [{% data variables.product.prodname_archive %}](https://archiveprogram.github.com). |
|
||||
|  | **{% data variables.product.prodname_dotcom %} Sponsor** | If you sponsored an open source contributor through {% data variables.product.prodname_sponsors %} you'll get a {% data variables.product.prodname_dotcom %} Sponsor badge on your profile. Clicking the badge takes you to the **Sponsoring** tab of your profile. For more information, see "[Sponsoring open source contributors](/github/supporting-the-open-source-community-with-github-sponsors/sponsoring-open-source-contributors)." |
|
||||
| {% 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). |
|
||||
|
||||
## 在个人资料中禁用徽章
|
||||
## Disabling badges on your profile
|
||||
|
||||
您可以对您参与的 {% data variables.product.prodname_dotcom %} 计划禁用某些徽章，包括 PRO、{% data variables.product.prodname_arctic_vault %} 和 Mars 2020 Helicopter 贡献者徽章。
|
||||
You can disable some of the badges for {% data variables.product.prodname_dotcom %} programs you're participating in, including the PRO, {% data variables.product.prodname_arctic_vault %} and Mars 2020 Helicopter Contributor badges.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在“Profile settings（个人资料设置）”下，取消选择您想要禁用的徽章。 
|
||||
3. 单击 **Update preferences（更新首选项）**。
|
||||
2. Under "Profile settings", deselect the badge you want you disable.
|
||||
|
||||
3. Click **Update preferences**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Mars 2020 Helicopter 贡献者徽章的合格仓库列表
|
||||
## List of qualifying repositories for Mars 2020 Helicopter Contributor badge
|
||||
|
||||
如果您为下面一个或多个仓库列出的标记撰写了提交历史记录中的任何提交，您的个人资料中将获得 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)。 将来对经过验证的电子邮件的更改不会对徽章产生影响。 我们根据从美国航天局喷气推进实验室获得的资料编制了清单。
|
||||
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 badge 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.
|
||||
|
||||
| {% 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) |
|
||||
| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
|
||||
| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
|
||||
| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
|
||||
| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
|
||||
| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
|
||||
| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
|
||||
| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
|
||||
| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
|
||||
| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
|
||||
| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
|
||||
| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
|
||||
| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
|
||||
| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
|
||||
| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
|
||||
| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
|
||||
| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
|
||||
| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
|
||||
| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
|
||||
| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
|
||||
| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
|
||||
| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
|
||||
| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
|
||||
| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
|
||||
| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
|
||||
| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
|
||||
| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
|
||||
| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
|
||||
| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
|
||||
| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
|
||||
| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
|
||||
| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
|
||||
| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
|
||||
| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
|
||||
| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
|
||||
| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
|
||||
| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
|
||||
| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
|
||||
| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
|
||||
| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
|
||||
| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
|
||||
| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
|
||||
| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
|
||||
| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
|
||||
| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
|
||||
| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
|
||||
| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
|
||||
| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
|
||||
| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
|
||||
| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
|
||||
| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
|
||||
| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
|
||||
| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
|
||||
| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
|
||||
| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
|
||||
| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
|
||||
| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
|
||||
| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
|
||||
| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
|
||||
| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
|
||||
| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
|
||||
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
|
||||
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
|
||||
| [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) |
|
||||
| {% data variables.product.prodname_dotcom %} Repository | Version | Tag |
|
||||
|---|---|---|
|
||||
| [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) |
|
||||
| [boto/boto3](https://github.com/boto/boto3) | 1.17.17 | [1.17.17](https://github.com/boto/boto3/releases/tag/1.17.17) |
|
||||
| [boto/botocore](https://github.com/boto/botocore) | 1.20.11 | [1.20.11](https://github.com/boto/botocore/releases/tag/1.20.11) |
|
||||
| [certifi/python-certifi](https://github.com/certifi/python-certifi) | 2020.12.5 | [2020.12.05](https://github.com/certifi/python-certifi/releases/tag/2020.12.05) |
|
||||
| [chardet/chardet](https://github.com/chardet/chardet) | 4.0.0 | [4.0.0](https://github.com/chardet/chardet/releases/tag/4.0.0) |
|
||||
| [matplotlib/cycler](https://github.com/matplotlib/cycler) | 0.10.0 | [v0.10.0](https://github.com/matplotlib/cycler/releases/tag/v0.10.0) |
|
||||
| [elastic/elasticsearch-py](https://github.com/elastic/elasticsearch-py) | 6.8.1 | [6.8.1](https://github.com/elastic/elasticsearch-py/releases/tag/6.8.1) |
|
||||
| [ianare/exif-py](https://github.com/ianare/exif-py) | 2.3.2 | [2.3.2](https://github.com/ianare/exif-py/releases/tag/2.3.2) |
|
||||
| [kjd/idna](https://github.com/kjd/idna) | 2.10 | [v2.10](https://github.com/kjd/idna/releases/tag/v2.10) |
|
||||
| [jmespath/jmespath.py](https://github.com/jmespath/jmespath.py) | 0.10.0 | [0.10.0](https://github.com/jmespath/jmespath.py/releases/tag/0.10.0) |
|
||||
| [nucleic/kiwi](https://github.com/nucleic/kiwi) | 1.3.1 | [1.3.1](https://github.com/nucleic/kiwi/releases/tag/1.3.1) |
|
||||
| [matplotlib/matplotlib](https://github.com/matplotlib/matplotlib) | 3.3.4 | [v3.3.4](https://github.com/matplotlib/matplotlib/releases/tag/v3.3.4) |
|
||||
| [numpy/numpy](https://github.com/numpy/numpy) | 1.20.1 | [v1.20.1](https://github.com/numpy/numpy/releases/tag/v1.20.1) |
|
||||
| [opencv/opencv-python](https://github.com/opencv/opencv-python) | 4.5.1.48 | [48](https://github.com/opencv/opencv-python/releases/tag/48) |
|
||||
| [python-pillow/Pillow](https://github.com/python-pillow/Pillow) | 8.1.0 | [8.1.0](https://github.com/python-pillow/Pillow/releases/tag/8.1.0) |
|
||||
| [pycurl/pycurl](https://github.com/pycurl/pycurl) | 7.43.0.6 | [REL_7_43_0_6](https://github.com/pycurl/pycurl/releases/tag/REL_7_43_0_6) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.7 | [pyparsing_2.4.7](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.7) |
|
||||
| [pyserial/pyserial](https://github.com/pyserial/pyserial) | 3.5 | [v3.5](https://github.com/pyserial/pyserial/releases/tag/v3.5) |
|
||||
| [dateutil/dateutil](https://github.com/dateutil/dateutil) | 2.8.1 | [2.8.1](https://github.com/dateutil/dateutil/releases/tag/2.8.1) |
|
||||
| [yaml/pyyaml ](https://github.com/yaml/pyyaml) | 5.4.1 | [5.4.1](https://github.com/yaml/pyyaml/releases/tag/5.4.1) |
|
||||
| [psf/requests](https://github.com/psf/requests) | 2.25.1 | [v2.25.1](https://github.com/psf/requests/releases/tag/v2.25.1) |
|
||||
| [boto/s3transfer](https://github.com/boto/s3transfer) | 0.3.4 | [0.3.4](https://github.com/boto/s3transfer/releases/tag/0.3.4) |
|
||||
| [enthought/scimath](https://github.com/enthought/scimath) | 4.2.0 | [4.2.0](https://github.com/enthought/scimath/releases/tag/4.2.0) |
|
||||
| [scipy/scipy](https://github.com/scipy/scipy) | 1.6.1 | [v1.6.1](https://github.com/scipy/scipy/releases/tag/v1.6.1) |
|
||||
| [benjaminp/six](https://github.com/benjaminp/six) | 1.15.0 | [1.15.0](https://github.com/benjaminp/six/releases/tag/1.15.0) |
|
||||
| [enthought/traits](https://github.com/enthought/traits) | 6.2.0 | [6.2.0](https://github.com/enthought/traits/releases/tag/6.2.0) |
|
||||
| [urllib3/urllib3](https://github.com/urllib3/urllib3) | 1.26.3 | [1.26.3](https://github.com/urllib3/urllib3/releases/tag/1.26.3) |
|
||||
| [python-attrs/attrs](https://github.com/python-attrs/attrs) | 19.3.0 | [19.3.0](https://github.com/python-attrs/attrs/releases/tag/19.3.0) |
|
||||
| [CheetahTemplate3/cheetah3](https://github.com/CheetahTemplate3/cheetah3/) | 3.2.4 | [3.2.4](https://github.com/CheetahTemplate3/cheetah3/releases/tag/3.2.4) |
|
||||
| [pallets/click](https://github.com/pallets/click) | 7.0 | [7.0](https://github.com/pallets/click/releases/tag/7.0) |
|
||||
| [pallets/flask](https://github.com/pallets/flask) | 1.1.1 | [1.1.1](https://github.com/pallets/flask/releases/tag/1.1.1) |
|
||||
| [flask-restful/flask-restful](https://github.com/flask-restful/flask-restful) | 0.3.7 | [0.3.7](https://github.com/flask-restful/flask-restful/releases/tag/0.3.7) |
|
||||
| [pytest-dev/iniconfig](https://github.com/pytest-dev/iniconfig) | 1.0.0 | [v1.0.0](https://github.com/pytest-dev/iniconfig/releases/tag/v1.0.0) |
|
||||
| [pallets/itsdangerous](https://github.com/pallets/itsdangerous) | 1.1.0 | [1.1.0](https://github.com/pallets/itsdangerous/releases/tag/1.1.0) |
|
||||
| [pallets/jinja](https://github.com/pallets/jinja) | 2.10.3 | [2.10.3](https://github.com/pallets/jinja/releases/tag/2.10.3) |
|
||||
| [lxml/lxml](https://github.com/lxml/lxml) | 4.4.1 | [lxml-4.4.1](https://github.com/lxml/lxml/releases/tag/lxml-4.4.1) |
|
||||
| [Python-Markdown/markdown](https://github.com/Python-Markdown/markdown) | 3.1.1 | [3.1.1](https://github.com/Python-Markdown/markdown/releases/tag/3.1.1) |
|
||||
| [pallets/markupsafe](https://github.com/pallets/markupsafe) | 1.1.1 | [1.1.1](https://github.com/pallets/markupsafe/releases/tag/1.1.1) |
|
||||
| [pypa/packaging](https://github.com/pypa/packaging) | 19.2 | [19.2](https://github.com/pypa/packaging/releases/tag/19.2) |
|
||||
| [pexpect/pexpect](https://github.com/pexpect/pexpect) | 4.7.0 | [4.7.0](https://github.com/pexpect/pexpect/releases/tag/4.7.0) |
|
||||
| [pytest-dev/pluggy](https://github.com/pytest-dev/pluggy) | 0.13.0 | [0.13.0](https://github.com/pytest-dev/pluggy/releases/tag/0.13.0) |
|
||||
| [pexpect/ptyprocess](https://github.com/pexpect/ptyprocess) | 0.6.0 | [0.6.0](https://github.com/pexpect/ptyprocess/releases/tag/0.6.0) |
|
||||
| [pytest-dev/py](https://github.com/pytest-dev/py) | 1.8.0 | [1.8.0](https://github.com/pytest-dev/py/releases/tag/1.8.0) |
|
||||
| [pyparsing/pyparsing](https://github.com/pyparsing/pyparsing) | 2.4.5 | [pyparsing_2.4.5](https://github.com/pyparsing/pyparsing/releases/tag/pyparsing_2.4.5) |
|
||||
| [pytest-dev/pytest](https://github.com/pytest-dev/pytest) | 5.3.0 | [5.3.0](https://github.com/pytest-dev/pytest/releases/tag/5.3.0) |
|
||||
| [stub42/pytz](https://github.com/stub42/pytz) | 2019.3 | [release_2019.3](https://github.com/stub42/pytz/releases/tag/release_2019.3) |
|
||||
| [uiri/toml](https://github.com/uiri/toml) | 0.10.0 | [0.10.0](https://github.com/uiri/toml/releases/tag/0.10.0) |
|
||||
| [pallets/werkzeug](https://github.com/pallets/werkzeug) | 0.16.0 | [0.16.0](https://github.com/pallets/werkzeug/releases/tag/0.16.0) |
|
||||
| [dmnfarrell/tkintertable](https://github.com/dmnfarrell/tkintertable) | 1.2 | [v1.2](https://github.com/dmnfarrell/tkintertable/releases/tag/v1.2) |
|
||||
| [wxWidgets/wxPython-Classic](https://github.com/wxWidgets/wxPython-Classic) | 2.9.1.1 | [wxPy-2.9.1.1](https://github.com/wxWidgets/wxPython-Classic/releases/tag/wxPy-2.9.1.1) |
|
||||
| [nasa/fprime](https://github.com/nasa/fprime) | 1.3 | [NASA-v1.3](https://github.com/nasa/fprime/releases/tag/NASA-v1.3) |
|
||||
| [nucleic/cppy](https://github.com/nucleic/cppy) | 1.1.0 | [1.1.0](https://github.com/nucleic/cppy/releases/tag/1.1.0) |
|
||||
| [opencv/opencv](https://github.com/opencv/opencv) | 4.5.1 | [4.5.1](https://github.com/opencv/opencv/releases/tag/4.5.1) |
|
||||
| [curl/curl](https://github.com/curl/curl) | 7.72.0 | [curl-7_72_0](https://github.com/curl/curl/releases/tag/curl-7_72_0) |
|
||||
| [madler/zlib](https://github.com/madler/zlib) | 1.2.11 | [v1.2.11](https://github.com/madler/zlib/releases/tag/v1.2.11) |
|
||||
| [apache/lucene](https://github.com/apache/lucene) | 7.7.3 | [releases/lucene-solr/7.7.3](https://github.com/apache/lucene/releases/tag/releases%2Flucene-solr%2F7.7.3) |
|
||||
| [yaml/libyaml](https://github.com/yaml/libyaml) | 0.2.5 | [0.2.5](https://github.com/yaml/libyaml/releases/tag/0.2.5) |
|
||||
| [elastic/elasticsearch](https://github.com/elastic/elasticsearch) | 6.8.1 | [v6.8.1](https://github.com/elastic/elasticsearch/releases/tag/v6.8.1) |
|
||||
| [twbs/bootstrap](https://github.com/twbs/bootstrap) | 4.3.1 | [v4.3.1](https://github.com/twbs/bootstrap/releases/tag/v4.3.1) |
|
||||
| [vuejs/vue](https://github.com/vuejs/vue) | 2.6.10 | [v2.6.10](https://github.com/vuejs/vue/releases/tag/v2.6.10) |
|
||||
| [carrotsearch/hppc](https://github.com/carrotsearch/hppc) | 0.7.1 | [0.7.1](https://github.com/carrotsearch/hppc/releases/tag/0.7.1) |
|
||||
| [JodaOrg/joda-time](https://github.com/JodaOrg/joda-time) | 2.10.1 | [v2.10.1](https://github.com/JodaOrg/joda-time/releases/tag/v2.10.1) |
|
||||
| [tdunning/t-digest](https://github.com/tdunning/t-digest) | 3.2 | [t-digest-3.2](https://github.com/tdunning/t-digest/releases/tag/t-digest-3.2) |
|
||||
| [HdrHistogram/HdrHistogram](https://github.com/HdrHistogram/HdrHistogram) | 2.1.9 | [HdrHistogram-2.1.9](https://github.com/HdrHistogram/HdrHistogram/releases/tag/HdrHistogram-2.1.9) |
|
||||
| [locationtech/spatial4j](https://github.com/locationtech/spatial4j) | 0.7 | [spatial4j-0.7](https://github.com/locationtech/spatial4j/releases/tag/spatial4j-0.7) |
|
||||
| [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
|
||||
|
||||
- "[关于个人资料](/articles/about-your-profile)"
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 在个人资料中嵌入项目
|
||||
intro: 您可以将 Gist 和仓库置顶在个人资料中，使其他人可以很快看到您的得意之作。
|
||||
title: Pinning items to your profile
|
||||
intro: You can pin gists and repositories to your profile so other people can quickly see your best work.
|
||||
redirect_from:
|
||||
- /articles/pinning-repositories-to-your-profile/
|
||||
- /articles/pinning-repositories-to-your-profile
|
||||
- /articles/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/pinning-items-to-your-profile
|
||||
- /github/setting-up-and-managing-your-github-profile/customizing-your-profile/pinning-items-to-your-profile
|
||||
@@ -12,24 +12,28 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Profiles
|
||||
shortTitle: 固定项目
|
||||
shortTitle: Pin items
|
||||
---
|
||||
You can pin a public repository if you own the repository or you've made contributions to the repository. Commits to forks don't count as contributions, so you can't pin a fork that you don't own. 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)"
|
||||
|
||||
您可以嵌入您拥有的或者对其做出了贡献的公共仓库。 对复刻的提交不计为贡献，因此不能嵌入非自己所有的复刻。 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/articles/why-are-my-contributions-not-showing-up-on-my-profile)”
|
||||
You can pin any public gist you own.
|
||||
|
||||
您可以置顶自己的任何公开 Gist。
|
||||
Pinned items include important information about the item, like the number of stars a repository has received or the first few lines of a gist. Once you pin items to your profile, the "Pinned" section replaces the "Popular repositories" section on your profile.
|
||||
|
||||
固定项包括有关项目的重要信息，例如仓库收到的星标数或 Gist 的前几行。 在将项目嵌入到个人资料后，个人资料中的“Pinned（已嵌入）”部分将替换“Popular repositories（常用仓库）”部分。
|
||||
|
||||
您可以重新排序“Pinned（已嵌入）”部分的项目。 在嵌入的右上角，单击 {% octicon "grabber" aria-label="The grabber symbol" %} 并将该嵌入拖至新位置。
|
||||
You can reorder the items in the "Pinned" section. In the upper-right corner of a pin, click {% octicon "grabber" aria-label="The grabber symbol" %} and drag the pin to a new location.
|
||||
|
||||
{% data reusables.profile.access_profile %}
|
||||
2. 在“Popular repositories（常用仓库）”或“Pinned（已嵌入）”部分，单击 **Customize your pins（自定义嵌入）**。 
|
||||
3. 要显示要固定项目的可搜索列表，请选择“Repositories（仓库）”、"Gists" 或两者。 
|
||||
4. （可选）为便于查找特定项目，在过滤器字段中输入用户、组织、仓库或 gist 的名称。 
|
||||
5. 选择最多六个仓库和/或 gist 的组合以显示。 
|
||||
6. 单击 **Save pins（保存嵌入）**。 
|
||||
2. In the "Popular repositories" or "Pinned" section, click **Customize your pins**.
|
||||
|
||||
3. To display a searchable list of items to pin, select "Repositories", "Gists", or both.
|
||||
|
||||
4. Optionally, to make it easier to find a specific item, in the filter field, type the name of a user, organization, repository, or gist.
|
||||
|
||||
5. Select a combination of up to six repositories and/or gists to display.
|
||||
|
||||
6. Click **Save pins**.
|
||||
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于个人资料](/articles/about-your-profile)"
|
||||
- "[About your profile](/articles/about-your-profile)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Sending enterprise contributions to your GitHub.com profile
|
||||
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-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
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
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 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
|
||||
- /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
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 管理对个人仓库的访问
|
||||
intro: 您可以向协作者授予对个人帐户拥有的仓库的访问。
|
||||
title: Managing access to your personal repositories
|
||||
intro: You can give people collaborator access to repositories owned by your personal account.
|
||||
redirect_from:
|
||||
- /categories/101/articles/
|
||||
- /categories/managing-repository-collaborators/
|
||||
- /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 %}'
|
||||
@@ -20,6 +20,6 @@ children:
|
||||
- /removing-a-collaborator-from-a-personal-repository
|
||||
- /removing-yourself-from-a-collaborators-repository
|
||||
- /maintaining-ownership-continuity-of-your-user-accounts-repositories
|
||||
shortTitle: 访问仓库
|
||||
shortTitle: Access to your repositories
|
||||
---
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 邀请协作者参加个人仓库
|
||||
intro: '您可以{% ifversion fpt or ghec %}邀请用户成为{% else %}添加用户成为{% endif %}个人仓库的协作者。'
|
||||
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.'
|
||||
redirect_from:
|
||||
- /articles/how-do-i-add-a-collaborator/
|
||||
- /articles/adding-collaborators-to-a-personal-repository/
|
||||
- /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
|
||||
@@ -16,10 +16,9 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: 邀请协作者
|
||||
shortTitle: Invite collaborators
|
||||
---
|
||||
|
||||
组织拥有的仓库可授予更细致的访问权限。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 上的访问权限](/articles/access-permissions-on-github)”。
|
||||
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 reusables.organizations.org-invite-expiration %}
|
||||
|
||||
@@ -29,33 +28,39 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
|
||||
|
||||
{% note %}
|
||||
|
||||
**注：** {% data variables.product.company_short %} 会限制在 24 小时内可受邀参加仓库的人数。 如果您超过此限制，请等待 24 小时后再邀请，或者创建一个组织以与更多的人协作。
|
||||
**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.
|
||||
|
||||
{% 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 %}
|
||||
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 %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
1. 单击 **Invite a collaborator（邀请协作者）**。 
|
||||
2. 在搜索字段中，开始键入您想邀请的人员的姓名，然后单击匹配列表中的姓名。 
|
||||
3. 单击 **Add NAME to REPOSITORY（添加姓名到仓库）**。 
|
||||
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. 在左侧边栏中，单击 **Collaborators（协作者）**。 
|
||||
6. 在 "Collaborators"（协作者）下，开始输入协作者的用户名。
|
||||
7. 从下拉菜单中选择协作者的用户名。 
|
||||
8. 单击 **Add collaborator（添加协作者）**。 
|
||||
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. 用户将会收到一封邀请他们参加仓库的电子邮件。 在接受邀请后，他们便对仓库具有协作者访问权限。
|
||||
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.
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-account)”
|
||||
- "[从个人仓库删除协作者](/articles/removing-a-collaborator-from-a-personal-repository)"
|
||||
- "[从协作者的仓库删除您自己](/articles/removing-yourself-from-a-collaborator-s-repository)"
|
||||
- "[将成员组织成团队](/organizations/organizing-members-into-teams)"
|
||||
- "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository/#collaborator-access-for-a-repository-owned-by-a-user-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)"
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 从个人仓库中删除协作者
|
||||
intro: 当您从项目中删除协作者时，他们将失去对您仓库的读取/写入权限。 如果仓库为私有并且该人员已创建复刻，则该复刻也将删除。
|
||||
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.'
|
||||
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/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
|
||||
@@ -19,26 +19,28 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: 删除协作者
|
||||
shortTitle: Remove a collaborator
|
||||
---
|
||||
## 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 %}
|
||||
{% data reusables.repositories.navigate-to-manage-access %}
|
||||
4. 在要要删除的协作者的右侧，单击 {% octicon "trash" aria-label="The trash icon" %}。 
|
||||
4. To the right of the collaborator you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
{% else %}
|
||||
3. 在左侧边栏中，单击 **Collaborators & teams（协作者和团队）**。 
|
||||
4. 在要删除的协作者旁边，单击 **X** 图标。 
|
||||
3. In the left sidebar, click **Collaborators & teams**.
|
||||
|
||||
4. Next to the collaborator you want to remove, click the **X** icon.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[从团队中删除组织成员](/articles/removing-organization-members-from-a-team)”
|
||||
- "[从组织仓库删除外部协作者](/articles/removing-an-outside-collaborator-from-an-organization-repository)"
|
||||
- "[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)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 从协作者的仓库中删除您自己
|
||||
intro: 如果您不再想要成为其他人仓库中的协作者，您可以删除自己。
|
||||
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.'
|
||||
redirect_from:
|
||||
- /leave-a-collaborative-repo/
|
||||
- /leave-a-repo/
|
||||
- /articles/removing-yourself-from-a-collaborator-s-repo/
|
||||
- /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
|
||||
@@ -18,10 +18,12 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
- Repositories
|
||||
shortTitle: 删除自己
|
||||
shortTitle: Remove yourself
|
||||
---
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
2. 在左侧边栏中，单击 **Repositories（仓库）**。 
|
||||
3. 在您要离开的仓库旁边，单击 **Leave（离开）**。 
|
||||
4. 仔细阅读警告，然后单击“I understand, leave this repository（我已了解，离开此仓库）”。 
|
||||
2. In the left sidebar, click **Repositories**.
|
||||
|
||||
3. Next to the repository you want to leave, click **Leave**.
|
||||
|
||||
4. Read the warning carefully, then click "I understand, leave this repository."
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
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 %}. 您也可以管理从 {% data variables.product.product_name %} 收到的电子邮件。'
|
||||
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.product.product_location %}{% endif %}. You can also manage emails you receive from {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /categories/managing-email-preferences/
|
||||
- /categories/managing-email-preferences
|
||||
- /articles/managing-email-preferences
|
||||
- /github/setting-up-and-managing-your-github-user-account/managing-email-preferences
|
||||
versions:
|
||||
@@ -22,6 +22,6 @@ children:
|
||||
- /remembering-your-github-username-or-email
|
||||
- /types-of-emails-github-sends
|
||||
- /managing-marketing-emails-from-github
|
||||
shortTitle: 管理电子邮件首选项
|
||||
shortTitle: Manage email preferences
|
||||
---
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 记住您的 GitHub 用户名或电子邮件
|
||||
intro: '是否距离您第一次登录 {% data variables.product.product_location %} 已经有一段时间？ 如果是这样，欢迎回来！ 如果无法记住您的 {% data variables.product.product_name %} 用户帐户名，您可以尝试以下方法来记住它。'
|
||||
title: Remembering your GitHub username or email
|
||||
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 your {% data variables.product.product_name %} user account 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/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
|
||||
@@ -14,63 +14,62 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: 查找您的用户名或电子邮件
|
||||
shortTitle: Find your username or email
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %} 用户
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
1. 在 **GitHub Desktop** 菜单中，单击 **Preferences（首选项）**。
|
||||
2. 在 Preferences（首选项）窗口中，验证以下内容：
|
||||
- 要查看 {% data variables.product.product_name %} 用户名，请单击 **Accounts（帐户）**。
|
||||
- 要查看您的 Git 电子邮件，请单击 **Git**。 请注意，此电子邮件不一定是[您的主 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
|
||||
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).
|
||||
|
||||
{% endmac %}
|
||||
|
||||
{% windows %}
|
||||
|
||||
## {% data variables.product.prodname_desktop %} 用户
|
||||
|
||||
1. 在 **File（文件）**菜单中，单击 **Options（选项）**。
|
||||
2. 在 Options（选项）窗口中，验证以下内容：
|
||||
- 要查看 {% data variables.product.product_name %} 用户名，请单击 **Accounts（帐户）**。
|
||||
- 要查看您的 Git 电子邮件，请单击 **Git**。 请注意，此电子邮件不一定是[您的主 {% data variables.product.product_name %} 电子邮件](/articles/changing-your-primary-email-address)。
|
||||
## {% data variables.product.prodname_desktop %} users
|
||||
|
||||
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).
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
## 在 `user.name` 配置中查找您的用户名
|
||||
## Finding your username in your `user.name` configuration
|
||||
|
||||
设置期间，您可能已[在 Git 中设置用户名](/github/getting-started-with-github/setting-your-username-in-git)。 如果这样，您可以查看此配置设置的值：
|
||||
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:
|
||||
|
||||
```shell
|
||||
$ git config user.name
|
||||
# 查看设置
|
||||
# View the setting
|
||||
<em>YOUR_USERNAME</em>
|
||||
```
|
||||
|
||||
## 在远程仓库的 URL 中查找您的用户名
|
||||
## 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.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：此方法仅当您拥有原始仓库或其他人存储库中您自己的复刻时才有效。 如果您克隆其他人的仓库，将显示他们的用户名而不是您的用户名。 类似地，组织仓库将显示组织的名称，而不是远程 URL 中的特定用户。
|
||||
**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.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
```shell
|
||||
$ cd <em>YOUR_REPOSITORY</em>
|
||||
# 将目录更改为初始化的 Git 仓库
|
||||
# Change directories to the initialized Git repository
|
||||
$ git remote -v
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (fetch)
|
||||
origin https://{% data variables.command_line.codeblock %}/<em>YOUR_USERNAME</em>/<em>YOUR_REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
您的用户名是紧跟在 `https://{% data variables.command_line.backticks %}/` 之后的内容。
|
||||
Your user name is what immediately follows the `https://{% data variables.command_line.backticks %}/`.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[验证电子邮件地址](/articles/verifying-your-email-address)”
|
||||
- "[Verifying your email address](/articles/verifying-your-email-address)"
|
||||
{% endif %}
|
||||
|
||||
@@ -1,14 +1,14 @@
|
||||
---
|
||||
title: 设置提交电子邮件地址
|
||||
intro: '您可以设置用于在 {% data variables.product.product_location %} 和计算机上创作提交的电子邮件地址。'
|
||||
title: Setting your commit email address
|
||||
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/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
|
||||
@@ -20,32 +20,31 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
- Notifications
|
||||
shortTitle: 设置提交电子邮件地址
|
||||
shortTitle: Set commit email address
|
||||
---
|
||||
## About commit email addresses
|
||||
|
||||
## 关于提交电子邮件地址
|
||||
{% data variables.product.prodname_dotcom %} uses your commit email address to associate commits with your account on {% data variables.product.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 %} uses your commit email address to associate commits with your account on {% 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.product.product_location %}{% endif %}. For commits you push from the command line, you can set your commit email address in Git.
|
||||
|
||||
For web-based Git operations, you can set your commit email address on {% 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 %}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 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注**：{% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
**Note**: {% 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 `no-reply` email address from {% data variables.product.product_name %} as your commit email address. 要将 `noreply` 电子邮件地址用于从命令行推送的提交，请在 Git 中设置提交电子邮件地址时使用该电子邮件地址。 要将 `noreply` 地址用于基于 web 的 Git 操作，请在 GitHub 上设置提交电子邮件地址并选择**对我的电子邮件地址保密**。
|
||||
{% ifversion fpt or ghec %}If you'd like to keep your personal email address private, you can use a `no-reply` 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**.
|
||||
|
||||
您也可以选择阻止从命令行推送的提交显示您的个人电子邮件地址。 更多信息请参阅“[阻止推送的命令行显示您的个人电子邮件地址](/articles/blocking-command-line-pushes-that-expose-your-personal-email-address)”。{% endif %}
|
||||
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 %}
|
||||
|
||||
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.product.product_location %}{% ifversion fpt or ghec %}, or the `noreply` email address provided to you in your email settings{% 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 %}
|
||||
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.product.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 %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
@@ -55,9 +54,9 @@ To ensure that commits are attributed to you and appear in your contributions gr
|
||||
|
||||
{% 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.product.product_location %}. This does not apply if you're using the ID-based `noreply` address from {% data variables.product.product_name %}. 更多信息请参阅“[更改 {% data variables.product.prodname_dotcom %} 用户名](/articles/changing-your-github-username)”。{% endif %}
|
||||
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.product.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.prodname_dotcom %} 上设置提交电子邮件地址
|
||||
## Setting your commit email address on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
{% data reusables.files.commit-author-email-options %}
|
||||
|
||||
@@ -67,11 +66,11 @@ If you use your `noreply` email address for {% data variables.product.product_na
|
||||
{% data reusables.user_settings.select_primary_email %}{% ifversion fpt or ghec %}
|
||||
{% data reusables.user_settings.keeping_your_email_address_private %}{% endif %}
|
||||
|
||||
## 在 Git 中设置您的提交电子邮件地址
|
||||
## Setting your commit email address in Git
|
||||
|
||||
您可以使用 `git config` 命令更改与 Git 提交关联的电子邮件地址。 您设置的新电子邮件地址将在从命令行推送到 {% data variables.product.product_location %} 的任何未来提交中显示。 在您更改提交电子邮件地址之前进行的任何提交仍与之前的电子邮件地址关联。
|
||||
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.product.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.
|
||||
|
||||
### 为计算机上的每个仓库设置电子邮件地址
|
||||
### 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 %}
|
||||
@@ -85,14 +84,14 @@ If you use your `noreply` email address for {% data variables.product.product_na
|
||||
```
|
||||
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.product.product_location %}.
|
||||
|
||||
您可以更改与您在一个仓库中所进行的提交关联的电子邮件地址。 此操作将覆盖这一个仓库中的全局 Git 配置设置，但不会影响任何其他仓库。
|
||||
You can change the email address associated with commits you make in a single repository. This will override your global Git config settings in this one repository, but will not affect any other repositories.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 将当前工作目录更改为您想要在其中配置与 Git 提交关联的电子邮件地址的本地仓库。
|
||||
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.
|
||||
3. {% data reusables.user_settings.set_your_email_address_in_git %}
|
||||
```shell
|
||||
$ git config user.email "<em>email@example.com</em>"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: About your personal dashboard
|
||||
redirect_from:
|
||||
- /hidden/about-improved-navigation-to-commonly-accessed-pages-on-github/
|
||||
- /articles/opting-into-the-public-beta-for-a-new-dashboard/
|
||||
- /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
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: 更改 GitHub 用户名
|
||||
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.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/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
|
||||
@@ -15,7 +15,7 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 更改用户名
|
||||
shortTitle: Change your username
|
||||
---
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
@@ -24,7 +24,7 @@ shortTitle: 更改用户名
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
**Note**: Members of an {% data variables.product.prodname_emu_enterprise %} cannot change usernames. Your enterprise's IdP administrator controls your username for {% data variables.product.product_name %}. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
|
||||
**Note**: Members of an {% data variables.product.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)."
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
@@ -36,53 +36,57 @@ shortTitle: 更改用户名
|
||||
|
||||
{% 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.
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
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 %} 无法为您释放不可用的用户名。 更多信息请参阅“[更改用户名](#changing-your-username)”。{% endif %}
|
||||
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 %}
|
||||
|
||||
更改用户名后，您的旧用户名即可供其他人申请使用。 对旧用户名下仓库的大多数引用会自动更改为新用户名。 不过，指向您个人资料的某些链接不会自动重定向。
|
||||
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 %} 无法为以下各项设置重定向：
|
||||
- 使用旧用户名的[@提及](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams)
|
||||
- 包含旧用户名的 [gists](/articles/creating-gists) 链接
|
||||
{% 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
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot make changes to your username. {% data reusables.enterprise-accounts.emu-more-info-account %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 仓库引用
|
||||
## Repository references
|
||||
|
||||
您更改用户名后，{% data variables.product.product_name %} 自动将引用重定向到您的仓库。
|
||||
- 指向现有仓库的 Web 链接仍然有效。 进行更改后，可能需要几分钟时间才能完成。
|
||||
- 从本地仓库克隆推送到旧的远程跟踪 URL 的命令行仍然有效。
|
||||
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.
|
||||
|
||||
如果旧用户名的新所有者创建与您的仓库同名的仓库，则会覆盖重定向条目，并且您的重定向将停止工作。 由于这种可能性，我们建议您在更改用户名后更新所有现有的远程仓库 URL。 更多信息请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
|
||||
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)."
|
||||
|
||||
## 指向以前的个人资料页面的链接
|
||||
## Links to your previous profile page
|
||||
|
||||
更改用户名后，指向以前的个人资料页面的链接（例如 `https://{% data variables.command_line.backticks %}/previoususername`）将返回 404 错误。 We recommend updating any links to your account on {% data variables.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
|
||||
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.product.product_location %} from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
|
||||
|
||||
## 您的 Git 提交
|
||||
## Your Git commits
|
||||
|
||||
{% 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. 有关设置电子邮件地址的更多详细信息，请参阅“[设置您的提交电子邮件地址](/articles/setting-your-commit-email-address)”。
|
||||
{% 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)."
|
||||
|
||||
## 更改用户名
|
||||
## Changing your username
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.account_settings %}
|
||||
3. 在“Change username（更改用户名）”部分，单击 **Change username（更改用户名）**。 {% ifversion fpt or ghec %}
|
||||
4. 阅读有关更改用户名的警告。 如果您仍要更改用户名，请单击 **I understand, let's change my username（我了解，让我们更改用户名）**。 
|
||||
5. 键入新的用户名。 
|
||||
6. 如果您选择的用户名可用，请单击 **Change my username（更改我的用户名）**。 如果您选择的用户名不可用，可以尝试其他用户名或您看到的建议之一。 
|
||||
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 %}
|
||||
|
||||
@@ -1,67 +1,69 @@
|
||||
---
|
||||
title: 将用户转换为组织
|
||||
title: Converting a user into an organization
|
||||
redirect_from:
|
||||
- /articles/what-is-the-difference-between-create-new-organization-and-turn-account-into-an-organization/
|
||||
- /articles/explaining-the-account-transformation-warning/
|
||||
- /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: 您可以将用户帐户转换为组织。 这样可以对属于组织的仓库设置更细化的权限。
|
||||
intro: You can convert your user account into an organization. This allows more granular permissions for repositories that belong to the organization.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 用户到组织
|
||||
shortTitle: User into an organization
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：在将用户转换为组织之前，请记住以下几点：
|
||||
**Warning**: Before converting a user into an organization, keep these points in mind:
|
||||
|
||||
- 您将**不再**能够登录被转换的用户帐户。
|
||||
- 您将**不再**能够创建或修改被转换的用户帐户所拥有的 Gist。
|
||||
- **无法**将组织转换回用户。
|
||||
- SSH 密钥、OAuth 令牌、作业档案、 反应、及关联的用户信息**不会**传输到组织。 这只适用于被转换的用户帐户，而不适用于该用户帐户的任何协作者。
|
||||
- 使用被转换用户帐户进行的任何提交**将不再链接**到该帐户。 提交本身**将**保持原状。
|
||||
- You will **no longer** be able to sign into the converted user account.
|
||||
- You will **no longer** be able to create or modify gists owned by the converted user 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 user account that's being converted, not any of the user account's collaborators.
|
||||
- Any commits made with the converted user account **will no longer be linked** to that account. The commits themselves **will** remain intact.
|
||||
- Any forks of private repositories made with the converted user account will be deleted.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 保留个人用户帐户并手动创建新组织
|
||||
## Keep your personal user 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 user account's information intact, then you must create a new organization and transfer your repositories to it instead of converting your user account into an organization.
|
||||
|
||||
1. 要保留当前用户帐户的名称供您个人使用，请[将您个人用户帐户的名称更改为](/articles/changing-your-github-username)一个好听的新名称。
|
||||
2. [使用个人用户帐户的原名称创建一个新组织](/articles/creating-a-new-organization-from-scratch)。
|
||||
3. [将您的仓库转让](/articles/transferring-a-repository)给新组织帐户。
|
||||
1. To retain your current user account name for your personal use, [change the name of your personal user 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 user account.
|
||||
3. [Transfer your repositories](/articles/transferring-a-repository) to your new organization account.
|
||||
|
||||
## 自动将个人帐户转换为组织
|
||||
## Convert your personal account into an organization automatically
|
||||
|
||||
也可以将个人用户帐户直接转换为组织。 转换帐户：
|
||||
- 按原样保留仓库，无需手动将其转让给另一个帐户
|
||||
- 自动邀请协作者加入与他们以前的权限相当的团队
|
||||
{% ifversion fpt or ghec %}-对 {% data variables.product.prodname_pro %} 上的用户帐户，自动将帐单转移到[付费 {% data variables.product.prodname_team %}](/articles/about-billing-for-github-accounts)，任何时候都无需重新输入付款信息、调整结算周期或双重付费{% endif %}
|
||||
You can also convert your personal user 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 user 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 %}
|
||||
|
||||
1. 创建新的个人帐户，转换后您将用它来登录 GitHub 以及访问组织和仓库。
|
||||
2. [离开](/articles/removing-yourself-from-an-organization)要转换的用户帐户此前加入的任何组织。
|
||||
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 user account you're converting has joined.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.organizations %}
|
||||
5. 在“Transform account（转换帐户）”下，单击 **Turn <username> into an organization（将 <username> 转换为组织）**。 
|
||||
6. 在 Account Transformation Warning（帐户转换警告）对话框中，查看并确认转换。 请注意，此框中的信息与本文顶部的警告信息相同。 
|
||||
7. 在“Transform your user into an organization（将用户转换为组织）”页面的“Choose an organization owner（选择组织所有者）”下，选择您在前面创建的备用个人帐户或您信任的其他用户来管理组织。 
|
||||
8. 选择新组织的订阅，并在提示时输入帐单信息。
|
||||
9. 单击 **Create Organization（创建组织）**。
|
||||
10. 登录在第一步中创建的新用户帐户，然后使用上下文切换器访问您的新组织。
|
||||
5. Under "Transform account", click **Turn <username> 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 user account you created in step one, then use the context switcher to access your new organization.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：将用户帐户转换为组织时，我们会将属于该帐户的仓库中的协作者作为*外部协作者*添加到新组织。 然后，您可以根据需要邀请*外部协作者*成为新组织的成员。 For more information, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization#outside-collaborators)."
|
||||
**Tip**: When you convert a user 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)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 延伸阅读
|
||||
- "[设置团队](/articles/setting-up-teams)"
|
||||
{% ifversion fpt or ghec %}- "[邀请用户加入您的组织](/articles/inviting-users-to-join-your-organization)"{% endif %}
|
||||
- “[访问组织](/articles/accessing-an-organization)”
|
||||
## 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)"
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 删除用户帐户
|
||||
intro: '可随时删除 {% data variables.product.product_name %} 用户帐户。'
|
||||
title: Deleting your user account
|
||||
intro: 'You can delete your {% data variables.product.product_name %} user account at any time.'
|
||||
redirect_from:
|
||||
- /articles/deleting-a-user-account/
|
||||
- /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
|
||||
@@ -12,39 +12,40 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 删除用户帐户
|
||||
shortTitle: Delete your user account
|
||||
---
|
||||
|
||||
删除用户帐户会移除帐户所拥有的所有仓库、私有仓库分支、wiki、议题、拉取请求和页面。 {% ifversion fpt or ghec %} 在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除，而是与我们的[Ghost 用户](https://github.com/ghost)关联。{% else %}在其他用户拥有的仓库中创建的议题和拉取请求以及所做的评论将不会被删除。{% endif %}
|
||||
Deleting your user account removes all repositories, forks of private repositories, wikis, issues, pull requests, and pages owned by your account. {% ifversion fpt or ghec %} Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted - instead, they'll be associated with our [Ghost user](https://github.com/ghost).{% else %}Issues and pull requests you've created and comments you've made in repositories owned by other users will not be deleted.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec %} When you delete your account we stop billing you. The email address associated with the account becomes available for use with a different account on {% data variables.product.product_location %}. After 90 days, the account name also becomes available to anyone else to use on a new account. {% endif %}
|
||||
|
||||
如果您是组织的唯一所有者，则必须先将所有权转让给其他人或删除该组织，然后才能删除您的用户帐户。 如果组织中有其他所有者，则必须先从组织中删除自己，然后才能删除用户帐户。
|
||||
If you’re the only owner of an organization, you must transfer ownership to another person or delete the organization before you can delete your user account. If there are other owners in the organization, you must remove yourself from the organization before you can delete your user account.
|
||||
|
||||
更多信息请参阅：
|
||||
- “[转让组织所有权](/articles/transferring-organization-ownership)”
|
||||
- “[删除组织帐户](/articles/deleting-an-organization-account)”
|
||||
- “[从组织中删除自己](/articles/removing-yourself-from-an-organization/)”
|
||||
For more information, see:
|
||||
- "[Transferring organization ownership](/articles/transferring-organization-ownership)"
|
||||
- "[Deleting an organization account](/articles/deleting-an-organization-account)"
|
||||
- "[Removing yourself from an organization](/articles/removing-yourself-from-an-organization/)"
|
||||
|
||||
## 备份帐户数据
|
||||
## Back up your account data
|
||||
|
||||
在删除用户帐户之前，请复制帐户拥有的所有仓库、私有分支、wiki、议题和拉取请求。
|
||||
Before you delete your user account, make a copy of all repositories, private forks, wikis, issues, and pull requests owned by your account.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**删除用户帐户后，GitHub 无法恢复您的内容。
|
||||
**Warning:** Once your user account has been deleted, GitHub cannot restore your content.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 删除用户帐户
|
||||
## Delete your user account
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.account_settings %}
|
||||
3. 在帐户设置页面底部，“Delete account（删除帐户）”下，单击 **Delete your account（删除帐户）**。 然后即可删除用户帐户。
|
||||
- 如果您是组织中的唯一所有者，则必须将所有权转让给其他人或删除您的组织。
|
||||
- 如果组织中有其他组织所有者，则必须将自己从组织中删除。 
|
||||
4. 在“Make sure you want to do this（确保要执行此操作）”对话框中，完成以下步骤，以确认您了解删除帐户时会发生什么： 
|
||||
3. At the bottom of the Account Settings page, under "Delete account", click **Delete your account**. Before you can delete your user account:
|
||||
- If you're the only owner in the organization, you must transfer ownership to another person or delete your organization.
|
||||
- If there are other organization owners in the organization, you must remove yourself from the organization.
|
||||
|
||||
4. In the "Make sure you want to do this" dialog box, complete the steps to confirm you understand what happens when your account is deleted:
|
||||
|
||||
{% ifversion fpt or ghec %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and {% data variables.product.prodname_pages %} sites owned by your account will be deleted and your billing will end immediately, and your username will be available to anyone for use on {% data variables.product.product_name %} after 90 days.
|
||||
{% else %}- 重新考虑一下，您帐户拥有的所有仓库、私有仓库分支、wiki、议题、提取请求和网页都将被删除，并且任何人将可在 {% data variables.product.product_name %} 上使用您的用户名。
|
||||
{% endif %}- 在第一个字段中，输入您的 {% data variables.product.product_name %} 用户名或电子邮件。
|
||||
- 在第二个字段中，键入提示短语。
|
||||
{% else %}- Recall that all repositories, forks of private repositories, wikis, issues, pull requests and pages owned by your account will be deleted, and your username will be available for use on {% data variables.product.product_name %}.
|
||||
{% endif %}- In the first field, type your {% data variables.product.product_name %} username or email.
|
||||
- In the second field, type the phrase from the prompt.
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Managing user account settings
|
||||
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/
|
||||
- /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:
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 管理对用户帐户项目板的访问
|
||||
intro: 作为项目板所有者，您可以添加或删除协作者，以及自定义他们对项目板的权限。
|
||||
title: Managing access to your user account's project boards
|
||||
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-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
|
||||
@@ -14,22 +14,23 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 管理访问项目板
|
||||
shortTitle: Manage access project boards
|
||||
---
|
||||
A collaborator is a person who has permissions to a project board you own. A collaborator's permissions will default to read access. For more information, see "[Permission levels for user-owned project boards](/articles/permission-levels-for-user-owned-project-boards)."
|
||||
|
||||
协作者是对您拥有的项目板具有访问权限的个人。 协作者的权限默认为读取权限。 更多信息请参阅“[用户项目板的权限级别](/articles/permission-levels-for-user-owned-project-boards)”。
|
||||
## Inviting collaborators to a user-owned project board
|
||||
|
||||
## 邀请协作者参加用户拥有的项目板
|
||||
|
||||
1. 导航到您要在其中添加协作者的项目板。
|
||||
1. Navigate to the project board where you want to add an collaborator.
|
||||
{% 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 %} 电子邮件地址。 
|
||||
5. Under "Search by username, full name or email address", type the collaborator's name, username, or {% data variables.product.prodname_dotcom %} email.
|
||||
|
||||
{% data reusables.project-management.add-collaborator %}
|
||||
7. 新协作者默认具有读取权限。 在新协作者名称旁边，可以选择使用下拉菜单选择不同的权限级别。 
|
||||
7. The new collaborator has read permissions by default. Optionally, next to the new collaborator's name, use the drop-down menu and choose a different permission level.
|
||||
|
||||
|
||||
## 从用户拥有的项目板删除协作者
|
||||
## Removing a collaborator from a user-owned project board
|
||||
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 合并多个用户帐户
|
||||
intro: 如果工作和个人分别使用不同的帐户，您可以合并这些帐户。
|
||||
title: Merging multiple user accounts
|
||||
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/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
|
||||
@@ -12,20 +12,19 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 合并多个用户帐户
|
||||
shortTitle: Merge multiple user accounts
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**建议只使用一个用户帐户来管理个人和专业仓库。
|
||||
**Tip:** We recommend using only one user account to manage both personal and professional repositories.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
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. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. 更多信息请参阅“[为什么我的贡献没有在我的个人资料中显示？](/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)”
|
||||
1. [Transfer any repositories](/articles/how-to-transfer-a-repository) from the account you want to delete to the account you want to keep. Issues, pull requests, and wikis are transferred as well. Verify the repositories exist on the account you want to keep.
|
||||
2. [Update the remote URLs](/github/getting-started-with-github/managing-remote-repositories) in any local clones of the repositories that were moved.
|
||||
3. [Delete the account](/articles/deleting-your-user-account) you no longer want to use.
|
||||
4. To attribute past commits to the new account, add the email address you used to author the commits to the account you're keeping. For more information, see "[Why are my contributions not showing up on my profile?](/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)"
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[{% data variables.product.prodname_dotcom %} 帐户的类型](/articles/types-of-github-accounts)"
|
||||
- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 访问组织
|
||||
intro: 要访问您是其成员的组织，必须登录您的个人用户帐户。
|
||||
title: Accessing an organization
|
||||
intro: 'To access an organization that you''re a member of, you must sign in to your personal user 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/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
|
||||
@@ -16,10 +16,9 @@ versions:
|
||||
topics:
|
||||
- Accounts
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：**只有组织所有者才可查看和更改组织的帐户设置。
|
||||
**Tip:** Only organization owners can see and change the account settings for an organization.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 公开或隐藏组织成员关系
|
||||
intro: 如果要公开显示您属于哪个组织，可以在个人资料中显示组织的头像。
|
||||
title: Publicizing or hiding organization membership
|
||||
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-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
|
||||
@@ -13,17 +13,18 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 显示或隐藏成员资格
|
||||
shortTitle: Show or hide membership
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
## 更改组织成员关系的可见性
|
||||
## Changing the visibility of your organization membership
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user_settings.access_org %}
|
||||
{% data reusables.organizations.people %}
|
||||
4. 在成员列表中找到您的用户名。 如果列表很长，可在搜索框中搜索您的用户名。 
|
||||
5. 在用户名右边的菜单中，选择新的可见性选项：
|
||||
- 要公开您的成员关系，请选择 **Public（公共）**。
|
||||
- 要隐藏您的成员关系，则选择 **Private（私有）**。 
|
||||
4. Locate your username in the list of members. If the list is large, you can search for your username in the search box.
|
||||
|
||||
5. In the menu to the right of your username, choose a new visibility option:
|
||||
- To publicize your membership, choose **Public**.
|
||||
- To hide your membership, choose **Private**.
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 从组织中删除自己
|
||||
intro: 如果您是外部协作者或组织成员，您可以随时离开组织。
|
||||
title: Removing yourself from an organization
|
||||
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/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
|
||||
@@ -13,16 +13,15 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 离开组织
|
||||
shortTitle: Leave an organization
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**如果您目前在组织中负责为 {% data variables.product.product_name %} 付款，从组织中删除自己**不会**更新组织的存档帐单信息。 如果您目前负责计费，则**必须**让组织的其他所有者或帐单管理员[更新组织的付款方式](/articles/adding-or-editing-a-payment-method)。
|
||||
**Warning:** If you're currently responsible for paying for {% data variables.product.product_name %} in your organization, removing yourself from the organization **does not** update the billing information on file for the organization. If you are currently responsible for billing, **you must** have another owner or billing manager for the organization [update the organization's payment method](/articles/adding-or-editing-a-payment-method).
|
||||
|
||||
更多信息请参阅“[转让组织所有权](/articles/transferring-organization-ownership)”。
|
||||
For more information, see "[Transferring organization ownership](/articles/transferring-organization-ownership)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -30,4 +29,5 @@ shortTitle: 离开组织
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.organizations %}
|
||||
3. 在“Organizations（组织）”下，找到您想要从中删除自己的组织，然后单击 **Leave（离开）**。 
|
||||
3. Under "Organizations", find the organization you'd like to remove yourself from, then click **Leave**.
|
||||
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 请求组织批准 OAuth 应用程序
|
||||
intro: '组织成员可以请求所有者批准对 {% data variables.product.prodname_oauth_app %}组织资源的访问权限。'
|
||||
title: Requesting organization approval for OAuth Apps
|
||||
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-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
|
||||
@@ -12,18 +12,20 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 请求 OAuth 应用程序批准
|
||||
shortTitle: Request OAuth App approval
|
||||
---
|
||||
|
||||
## 请求组织批准您已为个人帐户授权的 {% data variables.product.prodname_oauth_app %}
|
||||
## Requesting organization approval for an {% data variables.product.prodname_oauth_app %} you've already authorized for your personal account
|
||||
|
||||
{% 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 %}访问的组织旁边，单击 **Request access（请求访问权限）**。 
|
||||
5. 审查关于请求 {% data variables.product.prodname_oauth_app %}访问权限的信息后，单击 **Request approval from owners（请求所有者的批准）**。 
|
||||
3. In the list of applications, click the name of the {% data variables.product.prodname_oauth_app %} you'd like to request access for.
|
||||
|
||||
4. Next to the organization you'd like the {% data variables.product.prodname_oauth_app %} to access, click **Request access**.
|
||||
|
||||
5. After you review the information about requesting {% data variables.product.prodname_oauth_app %} access, click **Request approval from owners**.
|
||||
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于 {% data variables.product.prodname_oauth_app %} 访问限制](/articles/about-oauth-app-access-restrictions)"
|
||||
- "[About {% data variables.product.prodname_oauth_app %} access restrictions](/articles/about-oauth-app-access-restrictions)"
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Azure Pipelines to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Azure Pipelines share several configuration similarities, which makes migrating to {% data variables.product.prodname_actions %} relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-azure-pipelines-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-azure-pipelines-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from CircleCI to GitHub Actions
|
||||
intro: 'GitHub Actions and CircleCI share several similarities in configuration, which makes migration to GitHub Actions relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-circleci-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-circleci-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Jenkins to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Jenkins share multiple similarities, which makes migration to {% data variables.product.prodname_actions %} relatively straightforward.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-jenkins-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-jenkins-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -2,7 +2,6 @@
|
||||
title: Migrating from Travis CI to GitHub Actions
|
||||
intro: '{% data variables.product.prodname_actions %} and Travis CI share multiple similarities, which helps make it relatively straightforward to migrate to {% data variables.product.prodname_actions %}.'
|
||||
redirect_from:
|
||||
- /actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions
|
||||
- /actions/learn-github-actions/migrating-from-travis-ci-to-github-actions
|
||||
versions:
|
||||
fpt: '*'
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
---
|
||||
title: 身份验证
|
||||
intro: '通过{% ifversion not ghae %}双重身份验证、{% endif %}SSH{% ifversion not ghae %}、{% endif %}和提交签名验证等功能保持帐户和数据的安全。'
|
||||
title: Authentication
|
||||
intro: 'Keep your account and data secure with features like {% ifversion not ghae %}two-factor authentication, {% endif %}SSH{% ifversion not ghae %},{% endif %} and commit signature verification.'
|
||||
redirect_from:
|
||||
- /categories/56/articles/
|
||||
- /categories/ssh/
|
||||
- /mac-verify-ssh/
|
||||
- /ssh-issues/
|
||||
- /verify-ssh-redirect/
|
||||
- /win-verify-ssh/
|
||||
- /categories/92/articles/
|
||||
- /categories/gpg/
|
||||
- /categories/security/
|
||||
- /categories/56/articles
|
||||
- /categories/ssh
|
||||
- /mac-verify-ssh
|
||||
- /ssh-issues
|
||||
- /verify-ssh-redirect
|
||||
- /win-verify-ssh
|
||||
- /categories/92/articles
|
||||
- /categories/gpg
|
||||
- /categories/security
|
||||
- /categories/authenticating-to-github
|
||||
- /github/authenticating-to-github/
|
||||
- /github/authenticating-to-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 关于匿名化 URL
|
||||
intro: '如果将图像或视频上传到 {% data variables.product.product_name %}，图像或视频 URL 将会修改，这样便无法跟踪您的信息。'
|
||||
title: About anonymized URLs
|
||||
intro: 'If you upload an image or video to {% data variables.product.product_name %}, the URL of the image or video will be modified so your information is not trackable.'
|
||||
redirect_from:
|
||||
- /articles/why-do-my-images-have-strange-urls/
|
||||
- /articles/why-do-my-images-have-strange-urls
|
||||
- /articles/about-anonymized-image-urls
|
||||
- /authenticating-to-github/about-anonymized-image-urls
|
||||
- /github/authenticating-to-github/about-anonymized-urls
|
||||
@@ -14,16 +14,15 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
To host your images, {% data variables.product.product_name %} uses the [open-source project Camo](https://github.com/atmos/camo). Camo generates an anonymous URL proxy for each file which hides your browser details and related information from other users. The URL starts `https://<subdomain>.githubusercontent.com/`, with different subdomains depending on how you uploaded the image.
|
||||
|
||||
为托管您的图像，{% data variables.product.product_name %} 使用 [开源项目 Camo](https://github.com/atmos/camo)。 Camo 为每个文件生成匿名 URL 代理，以隐藏您的浏览器详细信息和来自其他用户的相关信息。 URL 以 `https:///<subdomain>.githubusercontent.com/` 开头，并且根据您如何上传映像而有不同的子域。
|
||||
Videos also get anonymized URLs with the same format as image URLs, but are not processed through Camo. This is because {% data variables.product.prodname_dotcom %} does not support externally hosted videos, so the anonymized URL is a link to the uploaded video hosted by {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
视频还可以使用与图像 URL 相同的格式获得匿名化 URL，但不会通过 Camo 进行处理。 这是因为 {% data variables.product.prodname_dotcom %} 不支持外部托管的视频，所以匿名 URL 是由 {% data variables.product.prodname_dotcom %} 托管的已上传视频的链接。
|
||||
Anyone who receives your anonymized URL, directly or indirectly, may view your image or video. To keep sensitive media files private, restrict them to a private network or a server that requires authentication instead of using Camo.
|
||||
|
||||
直接或间接收到您的匿名化 URL 的任何人都可查看您的图像或视频。 为对敏感图像文件保密，将它们限于私人网络或需要身份验证的服务器，而不使用 Camo。
|
||||
## Troubleshooting issues with Camo
|
||||
|
||||
## Camo 问题故障排除
|
||||
|
||||
在偶尔的情况下，通过 Camo 处理的图像可能不会出现在 {% data variables.product.prodname_dotcom %} 上。 下面是可用于确定问题位置的一些步骤。
|
||||
In rare circumstances, images that are processed through Camo might not appear on {% data variables.product.prodname_dotcom %}. Here are some steps you can take to determine where the problem lies.
|
||||
|
||||
{% windows %}
|
||||
|
||||
@@ -35,12 +34,12 @@ Windows users will either need to use the Git PowerShell (which is installed alo
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
### 图像不显示
|
||||
### An image is not showing up
|
||||
|
||||
如果图像显示于浏览器中，但未显示在 {% data variables.product.prodname_dotcom %} 上，您可以尝试本地请求该图像。
|
||||
If an image is showing up in your browser but not on {% data variables.product.prodname_dotcom %}, you can try requesting it locally.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. 使用 `curl` 请求图像标头。
|
||||
1. Request the image headers using `curl`.
|
||||
```shell
|
||||
$ curl -I https://www.my-server.com/images/some-image.png
|
||||
> HTTP/2 200
|
||||
@@ -50,20 +49,20 @@ Windows users will either need to use the Git PowerShell (which is installed alo
|
||||
> Server: Google Frontend
|
||||
> Content-Length: 6507
|
||||
```
|
||||
3. 检查 `Content-Type` 的值。 本例中为 `image/x-png`。
|
||||
4. 根据 [Camo 支持的类型列表](https://github.com/atmos/camo/blob/master/mime-types.json)检查内容类型。
|
||||
3. Check the value of `Content-Type`. In this case, it's `image/x-png`.
|
||||
4. Check that content type against [the list of types supported by Camo](https://github.com/atmos/camo/blob/master/mime-types.json).
|
||||
|
||||
如果您的内容类型不受 Camo 支持，可尝试以下几项操作：
|
||||
* 如果您拥有托管该图像的服务器，请修改它以让其返回正确内容类型的图像。
|
||||
* 如果使用外部服务托管图像，请联系该服务的支持。
|
||||
* 建立对 Camo 的拉取请求以将内容类型添加到列表。
|
||||
If your content type is not supported by Camo, you can try several actions:
|
||||
* If you own the server that's hosting the image, modify it so that it returns a correct content type for images.
|
||||
* If you're using an external service for hosting images, contact support for that service.
|
||||
* Make a pull request to Camo to add your content type to the list.
|
||||
|
||||
### 最近更改的图像不更新
|
||||
### An image that changed recently is not updating
|
||||
|
||||
如果最近更改了图像并且它显示在浏览器中，但未显示在 {% data variables.product.prodname_dotcom %} 上，可尝试重置图像缓存。
|
||||
If you changed an image recently and it's showing up in your browser but not {% data variables.product.prodname_dotcom %}, you can try resetting the cache of the image.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. 使用 `curl` 请求图像标头。
|
||||
1. Request the image headers using `curl`.
|
||||
```shell
|
||||
$ curl -I https://www.my-server.com/images/some-image.png
|
||||
> HTTP/2 200
|
||||
@@ -73,29 +72,29 @@ Windows users will either need to use the Git PowerShell (which is installed alo
|
||||
> Server: Jetty(8.y.z-SNAPSHOT)
|
||||
```
|
||||
|
||||
检查 `Cache-Control` 的值。 本例中没有 `Cache-Control`。 在这种情况下：
|
||||
* 如果您拥有托管该图像的服务器，请修改它以让其返回图像的 `no-cache` 的 `Cache-Control`。
|
||||
* 如果使用外部服务托管图像，请联系该服务的支持。
|
||||
Check the value of `Cache-Control`. In this example, there's no `Cache-Control`. In that case:
|
||||
* If you own the server that's hosting the image, modify it so that it returns a `Cache-Control` of `no-cache` for images.
|
||||
* If you're using an external service for hosting images, contact support for that service.
|
||||
|
||||
如果 `Cache-Control` *设置*为 `no-cache`，请联系 {% data variables.contact.contact_support %} 或搜索 {% data variables.contact.community_support_forum %}。
|
||||
If `Cache-Control` *is* set to `no-cache`, contact {% data variables.contact.contact_support %} or search the {% data variables.contact.community_support_forum %}.
|
||||
|
||||
### 从 Camo 的缓存中删除图像
|
||||
### Removing an image from Camo's cache
|
||||
|
||||
清除缓存会强制每个 {% data variables.product.prodname_dotcom %} 用户重新请求图像，因此应非常谨慎地使用此操作，仅在上述步骤无效时才使用。
|
||||
Purging the cache forces every {% data variables.product.prodname_dotcom %} user to re-request the image, so you should use it very sparingly and only in the event that the above steps did not work.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
1. 使用 `curl -X PURGE` 在 Camo URL 上清除图像。
|
||||
1. Purge the image using `curl -X PURGE` on the Camo URL.
|
||||
```shell
|
||||
$ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
|
||||
> {"status": "ok", "id": "216-8675309-1008701"}
|
||||
```
|
||||
|
||||
### 在私人网络上查看图像
|
||||
### Viewing images on private networks
|
||||
|
||||
如果图像从私人网络或需要身份验证的服务器提供，则无法通过 {% data variables.product.prodname_dotcom %} 查看。 事实上，未登录服务器的任何用户都无法查看。
|
||||
If an image is being served from a private network or from a server that requires authentication, it can't be viewed by {% data variables.product.prodname_dotcom %}. In fact, it can't be viewed by any user without asking them to log into the server.
|
||||
|
||||
要解决此问题，请将图像移至公共的服务。
|
||||
To fix this, please move the image to a service that is publicly available.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- {% data variables.product.prodname_blog %} 上的"[代理用户图像](https://github.com/blog/1766-proxying-user-images)"
|
||||
- "[Proxying user images](https://github.com/blog/1766-proxying-user-images)" on {% data variables.product.prodname_blog %}
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: 关于 GitHub 的 IP 地址
|
||||
intro: '{% data variables.product.product_name %} 可服务于多个 IP 地址范围的应用程序，使用 API 可获取地址。'
|
||||
title: About GitHub's IP addresses
|
||||
intro: '{% data variables.product.product_name %} serves applications from multiple IP address ranges, which are available using the API.'
|
||||
redirect_from:
|
||||
- /articles/what-ip-addresses-does-github-use-that-i-should-whitelist/
|
||||
- /categories/73/articles/
|
||||
- /categories/administration/
|
||||
- /articles/github-s-ip-addresses/
|
||||
- /articles/what-ip-addresses-does-github-use-that-i-should-whitelist
|
||||
- /categories/73/articles
|
||||
- /categories/administration
|
||||
- /articles/github-s-ip-addresses
|
||||
- /articles/about-github-s-ip-addresses
|
||||
- /articles/about-githubs-ip-addresses
|
||||
- /github/authenticating-to-github/about-githubs-ip-addresses
|
||||
@@ -16,25 +16,25 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: GitHub 的 IP 地址
|
||||
shortTitle: GitHub's IP addresses
|
||||
---
|
||||
|
||||
您可以从 [meta](https://api.github.com/meta) API 端点检索 {% data variables.product.prodname_dotcom %} 的 IP 地址列表。 更多信息请参阅“[元数据](/rest/reference/meta)”。
|
||||
You can retrieve a list of {% data variables.product.prodname_dotcom %}'s IP addresses from the [meta](https://api.github.com/meta) API endpoint. For more information, see "[Meta](/rest/reference/meta)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**注意：** Meta API 返回的 {% data variables.product.prodname_dotcom %} IP 地址列表并非详尽无遗。 例如，某些 {% data variables.product.prodname_dotcom %} 服务的 IP 地址可能不会列出，例如 LFS 或 {% data variables.product.prodname_registry %}。
|
||||
**Note:** The list of {% data variables.product.prodname_dotcom %} IP addresses returned by the Meta API is not intended to be an exhaustive list. For example, IP addresses for some {% data variables.product.prodname_dotcom %} services might not be listed, such as LFS or {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
|
||||
|
||||
这些范围在 [CIDR 表示法](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)中。 您可以使用在线转换工具（例如s这个 [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php)）将 CIDR 表示法转换为 IP 地址范围。
|
||||
These ranges are in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). You can use an online conversion tool such as this [CIDR / VLSM Supernet Calculator](http://www.subnet-calculator.com/cidr.php) to convert from CIDR notation to IP address ranges.
|
||||
|
||||
我们会不时更改我们的 IP 地址。 不建议按 IP 地址来创建允许名单，但如果您使用这些 IP 范围，强烈建议经常监控我们的 API。
|
||||
We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
|
||||
|
||||
为使应用程序运行，您必须通过我们用于 `github.com` 的 IP 范围允许 TCP 端口 22、80、443 和 9418。
|
||||
For applications to function, you must allow TCP ports 22, 80, 443, and 9418 via our IP ranges for `github.com`.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[连接问题故障排除](/articles/troubleshooting-connectivity-problems)"
|
||||
- "[Troubleshooting connectivity problems](/articles/troubleshooting-connectivity-problems)"
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Creating a personal access token
|
||||
intro: You should create a personal access token to use in place of a password with the command line or with the API.
|
||||
redirect_from:
|
||||
- /articles/creating-an-oauth-token-for-command-line-use/
|
||||
- /articles/creating-an-access-token-for-command-line-use/
|
||||
- /articles/creating-an-oauth-token-for-command-line-use
|
||||
- /articles/creating-an-access-token-for-command-line-use
|
||||
- /articles/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line
|
||||
- /github/authenticating-to-github/creating-a-personal-access-token
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 创建强密码
|
||||
title: Creating a strong password
|
||||
intro: 'Secure your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} with a strong and unique password using a password manager.'
|
||||
redirect_from:
|
||||
- /articles/what-is-a-strong-password/
|
||||
- /articles/what-is-a-strong-password
|
||||
- /articles/creating-a-strong-password
|
||||
- /github/authenticating-to-github/creating-a-strong-password
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-strong-password
|
||||
@@ -13,27 +13,26 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: 创建强密码
|
||||
shortTitle: Create a strong password
|
||||
---
|
||||
|
||||
You must choose or generate a password for your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} that is at least:
|
||||
- {% ifversion ghes %}七{% else %}八{% endif %}个字符且包含数字和小写字母，或
|
||||
- 至少 15 个字符，任意字符组合
|
||||
- {% ifversion ghes %}Seven{% else %}Eight{% endif %} characters long, if it includes a number and a lowercase letter, or
|
||||
- 15 characters long with any combination of characters
|
||||
|
||||
为确保您的帐户安全，我们建议您遵循以下最佳实践：
|
||||
- 使用 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/) 等密码管理器生成至少 15 个字符的密码。
|
||||
- 为 {% data variables.product.product_name %} 生成唯一的密码。 If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
|
||||
To keep your account secure, we recommend you follow these best practices:
|
||||
- Use a password manager, such as [LastPass](https://lastpass.com/) or [1Password](https://1password.com/), to generate a password of at least 15 characters.
|
||||
- Generate a unique password for {% data variables.product.product_name %}. If you use your {% data variables.product.product_name %} password elsewhere and that service is compromised, then attackers or other malicious actors could use that information to access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.
|
||||
|
||||
- 为您的帐户配置双重身份验证。 更多信息请参阅“[关于双重身份验证](/articles/about-two-factor-authentication)”。
|
||||
- 不与任何人分享您的密码，即使是潜在协作者。 在 {% data variables.product.product_name %} 上每个人都应使用自己的个人帐户。 有关协作方式的更多信息，请参阅：“[邀请协作者参与个人仓库](/articles/inviting-collaborators-to-a-personal-repository)”、“[关于协作开发模式](/articles/about-collaborative-development-models/)”或“[与组织中的团体协作](/organizations/collaborating-with-groups-in-organizations/)”。
|
||||
- Configure two-factor authentication for your personal account. For more information, see "[About two-factor authentication](/articles/about-two-factor-authentication)."
|
||||
- Never share your password, even with a potential collaborator. Each person should use their own personal account on {% data variables.product.product_name %}. For more information on ways to collaborate, see: "[Inviting collaborators to a personal repository](/articles/inviting-collaborators-to-a-personal-repository)," "[About collaborative development models](/articles/about-collaborative-development-models/)," or "[Collaborating with groups in organizations](/organizations/collaborating-with-groups-in-organizations/)."
|
||||
|
||||
{% data reusables.repositories.blocked-passwords %}
|
||||
|
||||
您只能使用密码通过浏览器登录 {% data variables.product.product_name %}。 使用其他方式（例如命令行或 API）向 {% data variables.product.product_name %} 验证时，应使用其他凭据。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)”。
|
||||
You can only use your password to log on to {% data variables.product.product_name %} using your browser. When you authenticate to {% data variables.product.product_name %} with other means, such as the command line or API, you should use other credentials. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
{% ifversion fpt or ghec %}{% data reusables.user_settings.password-authentication-deprecation %}{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[在 Git 中缓存您的 {% data variables.product.product_name %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git/)”
|
||||
- “[保护帐户和数据安全](/articles/keeping-your-account-and-data-secure/)”
|
||||
- "[Caching your {% data variables.product.product_name %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git/)"
|
||||
- "[Keeping your account and data secure](/articles/keeping-your-account-and-data-secure/)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: GitHub's SSH key fingerprints
|
||||
intro: Public key fingerprints can be used to validate a connection to a remote server.
|
||||
redirect_from:
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints/
|
||||
- /articles/what-are-github-s-ssh-key-fingerprints
|
||||
- /articles/github-s-ssh-key-fingerprints
|
||||
- /articles/githubs-ssh-key-fingerprints
|
||||
- /github/authenticating-to-github/githubs-ssh-key-fingerprints
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 保护帐户和数据安全
|
||||
title: Keeping your account and data secure
|
||||
intro: 'To protect your personal information, you should keep both your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} and any associated data secure.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-account-and-data-secure
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -32,6 +32,6 @@ children:
|
||||
- /githubs-ssh-key-fingerprints
|
||||
- /sudo-mode
|
||||
- /preventing-unauthorized-access
|
||||
shortTitle: 帐户安全
|
||||
shortTitle: Account security
|
||||
---
|
||||
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
title: Removing sensitive data from a repository
|
||||
intro: 'If you commit sensitive data, such as a password or SSH key into a Git repository, you can remove it from the history. To entirely remove unwanted files from a repository''s history you can use either the `git filter-repo` tool or the BFG Repo-Cleaner open source tool.'
|
||||
redirect_from:
|
||||
- /remove-sensitive-data/
|
||||
- /removing-sensitive-data/
|
||||
- /articles/remove-sensitive-data/
|
||||
- /remove-sensitive-data
|
||||
- /removing-sensitive-data
|
||||
- /articles/remove-sensitive-data
|
||||
- /articles/removing-sensitive-data-from-a-repository
|
||||
- /github/authenticating-to-github/removing-sensitive-data-from-a-repository
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 审查 SSH 密钥
|
||||
title: Reviewing your SSH keys
|
||||
intro: 'To keep your credentials secure, you should regularly audit your SSH keys, deploy keys, and review authorized applications that access your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/keeping-your-application-access-tokens-safe/
|
||||
- /articles/keeping-your-ssh-keys-and-application-access-tokens-safe/
|
||||
- /articles/keeping-your-application-access-tokens-safe
|
||||
- /articles/keeping-your-ssh-keys-and-application-access-tokens-safe
|
||||
- /articles/reviewing-your-ssh-keys
|
||||
- /github/authenticating-to-github/reviewing-your-ssh-keys
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/reviewing-your-ssh-keys
|
||||
@@ -16,32 +16,32 @@ topics:
|
||||
- Identity
|
||||
- Access management
|
||||
---
|
||||
|
||||
您可以删除未经授权（或可能已泄密）的 SSH 密钥，以确保攻击者无法再访问您的仓库。 您还可以批准有效的现有 SSH 密钥。
|
||||
You can delete unauthorized (or possibly compromised) SSH keys to ensure that an attacker no longer has access to your repositories. You can also approve existing SSH keys that are valid.
|
||||
|
||||
{% mac %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. 在 SSH Settings（SSH 设置）页面中，记下与您的帐户关联的 SSH 密钥。 对于您无法识别或已过期的密钥，请单击 **Delete（删除）**。 如果有您要保留的有效 SSH 密钥，请单击 **Approve（批准）**。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**注：**如果您由于 Git 操作失败而审核 SSH 密钥，则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未验证密钥将在 SSH 密钥列表中突出显示。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. 打开终端。
|
||||
4. Open Terminal.
|
||||
|
||||
{% data reusables.command_line.start_ssh_agent %}
|
||||
|
||||
6. 找到并记录公钥指纹。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} 上的 SSH 密钥*应*匹配您计算机上的相同密钥。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endmac %}
|
||||
|
||||
@@ -49,27 +49,28 @@ topics:
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. 在 SSH Settings（SSH 设置）页面中，记下与您的帐户关联的 SSH 密钥。 对于您无法识别或已过期的密钥，请单击 **Delete（删除）**。 如果有您要保留的有效 SSH 密钥，请单击 **Approve（批准）**。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**注：**如果您由于 Git 操作失败而审核 SSH 密钥，则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未验证密钥将在 SSH 密钥列表中突出显示。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. 打开 Git Bash。
|
||||
4. Open Git Bash.
|
||||
|
||||
5. {% data reusables.desktop.windows_git_bash_turn_on_ssh_agent %}
|
||||
|
||||
{% data reusables.desktop.windows_git_for_windows_turn_on_ssh_agent %}
|
||||
|
||||
6. 找到并记录公钥指纹。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} 上的 SSH 密钥*应*匹配您计算机上的相同密钥。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endwindows %}
|
||||
|
||||
@@ -77,30 +78,31 @@ topics:
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.ssh %}
|
||||
3. 在 SSH Settings（SSH 设置）页面中，记下与您的帐户关联的 SSH 密钥。 对于您无法识别或已过期的密钥，请单击 **Delete（删除）**。 如果有您要保留的有效 SSH 密钥，请单击 **Approve（批准）**。 
|
||||
3. On the SSH Settings page, take note of the SSH keys associated with your account. For those that you don't recognize, or that are out-of-date, click **Delete**. If there are valid SSH keys you'd like to keep, click **Approve**.
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**注：**如果您由于 Git 操作失败而审核 SSH 密钥，则导致 [SSH 密钥审核错误](/articles/error-we-re-doing-an-ssh-key-audit)的未验证密钥将在 SSH 密钥列表中突出显示。
|
||||
**Note:** If you're auditing your SSH keys due to an unsuccessful Git operation, the unverified key that caused the [SSH key audit error](/articles/error-we-re-doing-an-ssh-key-audit) will be highlighted in the list of SSH keys.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
4. 打开终端。
|
||||
4. Open Terminal.
|
||||
|
||||
{% data reusables.command_line.start_ssh_agent %}
|
||||
|
||||
6. 找到并记录公钥指纹。
|
||||
6. Find and take a note of your public key fingerprint.
|
||||
```shell
|
||||
$ ssh-add -l -E sha256
|
||||
> 2048 <em>SHA256:274ffWxgaxq/tSINAykStUL7XWyRNcRTlcST1Ei7gBQ</em> /Users/<em>USERNAME</em>/.ssh/id_rsa (RSA)
|
||||
```
|
||||
|
||||
7. {% data variables.product.product_name %} 上的 SSH 密钥*应*匹配您计算机上的相同密钥。
|
||||
7. The SSH keys on {% data variables.product.product_name %} *should* match the same keys on your computer.
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：如果在 {% data variables.product.product_name %} 上看到您不熟悉的 SSH 密钥，请立即删除并联系 {% data variables.contact.contact_support %}寻求进一步的帮助。 无法识别的公钥可能表示安全问题。
|
||||
**Warning**: If you see an SSH key you're not familiar with on {% data variables.product.product_name %}, delete it immediately and contact {% data variables.contact.contact_support %} for further help. An unidentified public key may indicate a possible security concern.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 更新 GitHub 访问凭据
|
||||
intro: '{% data variables.product.product_name %} 凭据不仅{% ifversion not ghae %}包括密码，还{% endif %}包括您用于与 {% data variables.product.product_name %} 通信的访问令牌、SSH 密钥和应用程序 API 令牌。 如果您有需要，可以自行重置所有这些访问凭据。'
|
||||
title: Updating your GitHub access credentials
|
||||
intro: '{% data variables.product.product_name %} credentials include{% ifversion not ghae %} not only your password, but also{% endif %} the access tokens, SSH keys, and application API tokens you use to communicate with {% data variables.product.product_name %}. Should you have the need, you can reset all of these access credentials yourself.'
|
||||
redirect_from:
|
||||
- /articles/rolling-your-credentials/
|
||||
- /articles/how-can-i-reset-my-password/
|
||||
- /articles/rolling-your-credentials
|
||||
- /articles/how-can-i-reset-my-password
|
||||
- /articles/updating-your-github-access-credentials
|
||||
- /github/authenticating-to-github/updating-your-github-access-credentials
|
||||
- /github/authenticating-to-github/keeping-your-account-and-data-secure/updating-your-github-access-credentials
|
||||
@@ -15,56 +15,57 @@ versions:
|
||||
topics:
|
||||
- Identity
|
||||
- Access management
|
||||
shortTitle: 更新访问凭据
|
||||
shortTitle: Update access credentials
|
||||
---
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## 请求新密码
|
||||
## Requesting a new password
|
||||
|
||||
1. To request a new password, visit {% ifversion fpt or ghec %}https://{% data variables.product.product_url %}/password_reset{% else %}`https://{% data variables.product.product_url %}/password_reset`{% endif %}.
|
||||
2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured. 
|
||||
3. 我们将向您发送一封电子邮件，其中含有可让您重置密码的链接。 您必须在收到电子邮件后的 3 小时内单击此链接。 如果您没有收到来自我们的电子邮件，请确保检查垃圾邮件文件夹。
|
||||
4. 如果您启用了双重身份验证，将提示您获得 2FA 凭据。 键入您的 2FA 凭据或 2FA 恢复代码之一，然后单击 **Verify（验证）**。 
|
||||
5. 键入新密码，确认新密码，然后单击 **Change password（更改密码）**。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)”
|
||||
2. Enter the email address associated with your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}, then click **Send password reset email.** The email will be sent to the backup email address if you have one configured.
|
||||
|
||||
3. We'll email you a link that will allow you to reset your password. You must click on this link within 3 hours of receiving the email. If you didn't receive an email from us, make sure to check your spam folder.
|
||||
4. If you have enabled two-factor authentication, you will be prompted for your 2FA credentials. Type your 2FA credentials or one of your 2FA recovery codes and click **Verify**.
|
||||
|
||||
5. Type a new password, confirm your new password, and click **Change password**. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)."
|
||||
{% ifversion fpt or ghec %}{% else %}
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
为避免将来丢失您的密码，我们建议使用安全密码管理器，如 [LastPass](https://lastpass.com/) 或 [1Password](https://1password.com/)。
|
||||
To avoid losing your password in the future, we suggest using a secure password manager, like [LastPass](https://lastpass.com/) or [1Password](https://1password.com/).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 更改现有的密码
|
||||
## Changing an existing password
|
||||
|
||||
{% data reusables.repositories.blocked-passwords %}
|
||||
|
||||
1. {% data variables.product.signin_link %}到 {% data variables.product.product_name %}。
|
||||
1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
4. 在“Change password（更改密码）”下，输入旧密码、强新密码并确认新密码。 有关创建强密码的帮助，请参阅“[创建强密码](/articles/creating-a-strong-password)”
|
||||
5. 单击 **Update password（更新密码）**。
|
||||
4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)"
|
||||
5. Click **Update password**.
|
||||
|
||||
{% tip %}
|
||||
|
||||
为实现更高的安全性，除了更改密码以外，还可启用双重身份验证。 有关更多详细信息，请参阅[关于双重身份验证](/articles/about-two-factor-authentication)。
|
||||
For greater security, enable two-factor authentication in addition to changing your password. See [About two-factor authentication](/articles/about-two-factor-authentication) for more details.
|
||||
|
||||
{% endtip %}
|
||||
{% endif %}
|
||||
## 更新访问令牌
|
||||
## Updating your access tokens
|
||||
|
||||
有关审查和删除访问令牌的说明，请参阅“[审查授权的集成](/articles/reviewing-your-authorized-integrations)”。 要生成新的访问令牌，请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
|
||||
See "[Reviewing your authorized integrations](/articles/reviewing-your-authorized-integrations)" for instructions on reviewing and deleting access tokens. To generate new access tokens, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
|
||||
## 更新 SSH 密钥
|
||||
## Updating your SSH keys
|
||||
|
||||
有关审查和删除 SSH 密钥的说明，请参阅“[审查 SSH 密钥](/articles/reviewing-your-ssh-keys)”。 要生成和添加新的 SSH 密钥，请参阅“[生成 SSH 密钥](/articles/generating-an-ssh-key)”。
|
||||
See "[Reviewing your SSH keys](/articles/reviewing-your-ssh-keys)" for instructions on reviewing and deleting SSH keys. To generate and add new SSH keys, see "[Generating an SSH key](/articles/generating-an-ssh-key)."
|
||||
|
||||
## 重置 API 令牌
|
||||
## Resetting API tokens
|
||||
|
||||
如果您向 {% data variables.product.product_name %} 注册了任何应用程序，则需要重置其 OAuth 令牌。 更多信息请参阅“[重置授权](/rest/reference/apps#reset-an-authorization)”端点。
|
||||
If you have any applications registered with {% data variables.product.product_name %}, you'll want to reset their OAuth tokens. For more information, see the "[Reset an authorization](/rest/reference/apps#reset-an-authorization)" endpoint.
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## 防止未授权的访问
|
||||
## Preventing unauthorized access
|
||||
|
||||
有关保护您的帐户和阻止未授权访问的更多提示，请参阅“[阻止未授权的访问](/articles/preventing-unauthorized-access)”。
|
||||
For more tips on securing your account and preventing unauthorized access, see "[Preventing unauthorized access](/articles/preventing-unauthorized-access)."
|
||||
{% endif %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 使用双重身份验证访问 GitHub
|
||||
intro: '启用 2FA 后，在登录到 {% data variables.product.product_name %} 时需要提供 2FA 验证码以及密码。'
|
||||
title: Accessing GitHub using two-factor authentication
|
||||
intro: 'With 2FA enabled, you''ll be asked to provide your 2FA authentication code, as well as your password, when you sign in to {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /articles/providing-your-2fa-security-code/
|
||||
- /articles/providing-your-2fa-authentication-code/
|
||||
- /articles/authenticating-to-github-using-fido-u2f-via-nfc/
|
||||
- /articles/providing-your-2fa-security-code
|
||||
- /articles/providing-your-2fa-authentication-code
|
||||
- /articles/authenticating-to-github-using-fido-u2f-via-nfc
|
||||
- /articles/accessing-github-using-two-factor-authentication
|
||||
- /github/authenticating-to-github/accessing-github-using-two-factor-authentication
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication
|
||||
@@ -14,60 +14,59 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- 2FA
|
||||
shortTitle: 使用 2FA 访问 GitHub
|
||||
shortTitle: Access GitHub with 2FA
|
||||
---
|
||||
With two-factor authentication enabled, you'll need to provide an authentication code when accessing {% data variables.product.product_name %} through your browser. If you access {% data variables.product.product_name %} using other methods, such as the API or the command line, you'll need to use an alternative form of authentication. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/about-authentication-to-github)."
|
||||
|
||||
启用双重身份验证后，您在通过浏览器访问 {% data variables.product.product_name %} 时需要提供验证码。 如果使用其他方法访问 {% data variables.product.product_name %}，如 API 或命令行，则需要使用其他形式的身份验证。 更多信息请参阅“[关于 {% data variables.product.prodname_dotcom %} 向验证身份](/github/authenticating-to-github/about-authentication-to-github)”。
|
||||
## Providing a 2FA code when signing in to the website
|
||||
|
||||
## 登录网站时提供 2FA 码
|
||||
After you sign in to {% data variables.product.product_name %} using your password, you'll be prompted to provide an authentication code from {% ifversion fpt or ghec %}a text message or{% endif %} your TOTP app.
|
||||
|
||||
在使用密码登录 {% data variables.product.product_name %} 后，系统会提示您提供{% ifversion fpt or ghec %}短信或{% endif %} TOTP 应用程序中的验证码。
|
||||
{% data variables.product.product_name %} will only ask you to provide your 2FA authentication code again if you've logged out, are using a new device, or your session expires.
|
||||
|
||||
{% data variables.product.product_name %} 仅在您注销后、使用新设备或会话过期时才会要求您再次提供 2FA 验证码。
|
||||
### Generating a code through a TOTP application
|
||||
|
||||
### 通过 TOTP 应用程序生成代码
|
||||
If you chose to set up two-factor authentication using a TOTP application on your smartphone, you can generate an authentication code for {% data variables.product.product_name %} at any time. In most cases, just launching the application will generate a new code. You should refer to your application's documentation for specific instructions.
|
||||
|
||||
如果选择使用 TOTP 应用程序在智能手机上设置双重身份验证，可随时为 {% data variables.product.product_name %} 生成验证码。 大多数情况下，只有启动应用程序才会生成新代码。 具体说明请参阅应用程序的文档。
|
||||
|
||||
如果在配置双重身份验证后删除移动应用程序，则需要提供恢复代码才可访问您的帐户。 更多信息请参阅“[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”
|
||||
If you delete the mobile application after configuring two-factor authentication, you'll need to provide your recovery code to get access to your account. For more information, see "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
### 接收短信
|
||||
### Receiving a text message
|
||||
|
||||
如果设置通过短信进行双重身份验证，{% data variables.product.product_name %} 将通过短信向您发送验证码。
|
||||
If you set up two-factor authentication via text messages, {% data variables.product.product_name %} will send you a text message with your authentication code.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 通过命令行使用双重身份验证
|
||||
## Using two-factor authentication with the command line
|
||||
|
||||
在启用 2FA 后，您在命令行上访问 {% data variables.product.product_name %} 时必须使用个人访问令牌或 SSH 密钥，而不是密码。
|
||||
After you've enabled 2FA, you must use a personal access token or SSH key instead of your password when accessing {% data variables.product.product_name %} on the command line.
|
||||
|
||||
### 在命令行上使用 HTTPS 验证
|
||||
### Authenticating on the command line using HTTPS
|
||||
|
||||
启用 2FA 后，必须创建个人访问令牌以用作在命令行上使用 HTTPS URL 向 {% data variables.product.product_name %} 验证时的密码。
|
||||
After you've enabled 2FA, you must create a personal access token to use as a password when authenticating to {% data variables.product.product_name %} on the command line using HTTPS URLs.
|
||||
|
||||
当命令行上提供用户名和密码时，使用您的 {% data variables.product.product_name %} 用户名和个人访问令牌。 命令行提示不会指出在要求密码时您应输入个人访问令牌。
|
||||
When prompted for a username and password on the command line, use your {% data variables.product.product_name %} username and personal access token. The command line prompt won't specify that you should enter your personal access token when it asks for your password.
|
||||
|
||||
更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
|
||||
For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
|
||||
### 在命令行上使用 SSH 验证
|
||||
### Authenticating on the command line using SSH
|
||||
|
||||
启用 2FA 不会更改您在命令行上使用 SSH URL 向 {% data variables.product.product_name %} 验证的方式。 有关设置和使用 SSH 密钥的更多信息，请参阅“[通过 SSH 连接 {% data variables.product.prodname_dotcom %}](/articles/connecting-to-github-with-ssh/)”。
|
||||
Enabling 2FA doesn't change how you authenticate to {% data variables.product.product_name %} on the command line using SSH URLs. For more information about setting up and using an SSH key, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/articles/connecting-to-github-with-ssh/)."
|
||||
|
||||
## 使用双重身份验证通过 Subversion 访问仓库
|
||||
## Using two-factor authentication to access a repository using Subversion
|
||||
|
||||
通过 Subversion 访问仓库时，必须提供个人人访问令牌，而不是输入密码。 更多信息请参阅“[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
|
||||
When you access a repository via Subversion, you must provide a personal access token instead of entering your password. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
||||
|
||||
## 疑难解答
|
||||
## Troubleshooting
|
||||
|
||||
如果失去对双重身份验证凭据的访问，您可以使用恢复代码或其他恢复方式（如已设置）重新获取对帐户的访问。 更多信息请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。
|
||||
If you lose access to your two-factor authentication credentials, you can use your recovery codes or another recovery method (if you've set one up) to regain access to your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||
|
||||
如果身份验证失败多次，您可能要与移动提供商同步手机的时钟。 通常，这需要在手机的时钟上选中 "Set automatically"（自动设置）选项，而不是提供自己的时区。
|
||||
If your authentication fails several times, you may wish to synchronize your phone's clock with your mobile provider. Often, this involves checking the "Set automatically" option on your phone's clock, rather than providing your own time zone.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于双重身份验证](/articles/about-two-factor-authentication)"
|
||||
- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
|
||||
- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Changing two-factor authentication delivery methods for your mobile device
|
||||
intro: You can switch between receiving authentication codes through a text message or a mobile application.
|
||||
redirect_from:
|
||||
- /articles/changing-two-factor-authentication-delivery-methods/
|
||||
- /articles/changing-two-factor-authentication-delivery-methods
|
||||
- /articles/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /github/authenticating-to-github/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 配置双重身份验证恢复方法
|
||||
intro: 您可以设置多种恢复方法，以便在丢失双重身份验证凭据的情况下访问您的帐户。
|
||||
title: Configuring two-factor authentication recovery methods
|
||||
intro: You can set up a variety of recovery methods to access your account if you lose your two-factor authentication credentials.
|
||||
redirect_from:
|
||||
- /articles/downloading-your-two-factor-authentication-recovery-codes/
|
||||
- /articles/setting-a-fallback-authentication-number/
|
||||
- /articles/about-recover-accounts-elsewhere/
|
||||
- /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere/
|
||||
- /articles/generating-and-storing-an-account-recovery-token/
|
||||
- /articles/downloading-your-two-factor-authentication-recovery-codes
|
||||
- /articles/setting-a-fallback-authentication-number
|
||||
- /articles/about-recover-accounts-elsewhere
|
||||
- /articles/adding-a-fallback-authentication-method-with-recover-accounts-elsewhere
|
||||
- /articles/generating-and-storing-an-account-recovery-token
|
||||
- /articles/configuring-two-factor-authentication-recovery-methods
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication-recovery-methods
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication-recovery-methods
|
||||
@@ -16,71 +16,75 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- 2FA
|
||||
shortTitle: 配置 2FA 恢复
|
||||
shortTitle: Configure 2FA recovery
|
||||
---
|
||||
In addition to securely storing your two-factor authentication recovery codes, we strongly recommend configuring one or more additional recovery methods.
|
||||
|
||||
除了安全存储双重身份验证恢复代码之外，我们强烈建议您配置一种或多种其他恢复方法。
|
||||
## Downloading your two-factor authentication recovery codes
|
||||
|
||||
## 下载双重身份验证恢复代码
|
||||
{% data reusables.two_fa.about-recovery-codes %} You can also download your recovery codes at any point after enabling two-factor authentication.
|
||||
|
||||
{% data reusables.two_fa.about-recovery-codes %} 也可以在启用双重身份验证后随时下载恢复代码。
|
||||
|
||||
为确保您的帐户安全，请勿分享或分发您的恢复代码。 我们建议使用安全密码管理器保存它们，例如：
|
||||
To keep your account secure, don't share or distribute your recovery codes. We recommend saving them with a secure password manager, such as:
|
||||
- [1Password](https://1password.com/)
|
||||
- [LastPass](https://lastpass.com/)
|
||||
|
||||
如果您生成新的恢复代码或禁用并重新启用 2FA，则安全设置中的恢复代码会自动更新。
|
||||
If you generate new recovery codes or disable and re-enable 2FA, the recovery codes in your security settings automatically update.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.show-recovery-codes %}
|
||||
4. 将恢复代码保存在安全的位置。 在失去访问权限时，恢复代码可帮助您恢复帐户登录。
|
||||
- 要在设备上保存恢复代码，请单击 **Download（下载）**。
|
||||
- 要保存恢复代码的硬拷贝，请单击 **Print（打印）**。
|
||||
- 要复制恢复代码以存储在密码管理器中，请单击**复制**。 
|
||||
4. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
|
||||
- To save your recovery codes on your device, click **Download**.
|
||||
- To save a hard copy of your recovery codes, click **Print**.
|
||||
- To copy your recovery codes for storage in a password manager, click **Copy**.
|
||||
|
||||
|
||||
## 生成一组新的恢复代码
|
||||
## Generating a new set of recovery codes
|
||||
|
||||
使用某个恢复代码恢复帐户访问后，该代码无法再用。 用完全部 16 个恢复代码后，可以生成另一个代码列表。 生成一组新的恢复代码将导致此前生成的任何代码失效。
|
||||
Once you use a recovery code to regain access to your account, it cannot be reused. If you've used all 16 recovery codes, you can generate another list of codes. Generating a new set of recovery codes will invalidate any codes you previously generated.
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.show-recovery-codes %}
|
||||
3. 要创建另一批恢复代码，请单击 **Generate new recovery codes（生成新的恢复代码）**。 
|
||||
3. To create another batch of recovery codes, click **Generate new recovery codes**.
|
||||
|
||||
|
||||
## 将安全密钥配置为附加双重身份验证方法
|
||||
## Configuring a security key as an additional two-factor authentication method
|
||||
|
||||
您可以将安全密钥设置为辅助双重身份验证方法，以便使用安全密钥恢复帐户访问。 更多信息请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)”。
|
||||
You can set up a security key as a secondary two-factor authentication method, and use the security key to regain access to your account. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 设置后备身份验证号码
|
||||
## Setting a fallback authentication number
|
||||
|
||||
您可以提供后备设备的号码作为第二号码。 在无法访问主设备和恢复代码时，可通过备用短信号码恢复帐户登录。
|
||||
You can provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
|
||||
|
||||
无论您配置的身份验证方法是通过短信还是通过 TOTP 移动应用程序，都可以使用后备号码。
|
||||
You can use a fallback number regardless of whether you've configured authentication via text message or TOTP mobile application.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**使用后备号码是最后的选择。 如果您设置了后备身份验证号码，我们建议您配置其他恢复方法。
|
||||
- 不法之徒可能会攻击手机运营商，因此 SMS 身份验证存在风险。
|
||||
- 只有美国以外的某些国家/地区支持短信验证；有关支持列表详情，请参阅“[支持 SMS 身份验证的国家/地区](/articles/countries-where-sms-authentication-is-supported)”。
|
||||
**Warning:** Using a fallback number is a last resort. We recommend configuring additional recovery methods if you set a fallback authentication number.
|
||||
- Bad actors may attack cell phone carriers, so SMS authentication is risky.
|
||||
- SMS messages are only supported for certain countries outside the US; for the list, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
3. 在“Fallback SMS number（后备 SMS 号码）”旁边，单击 **Add（添加）**。 
|
||||
4. 在“Fallback SMS number（后备 SMS 号码）”下，单击 **Add fallback SMS number（添加后备 SMS 号码）**。 
|
||||
5. 选择您的国家/地区代码并键入您的手机号码，包括区号。 确认信息无误后，单击 **Set fallback（设置后备号码）**。 
|
||||
3. Next to "Fallback SMS number", click **Add**.
|
||||
|
||||
4. Under "Fallback SMS number", click **Add fallback SMS number**.
|
||||
|
||||
5. Select your country code and type your mobile phone number, including the area code. When your information is correct, click **Set fallback**.
|
||||
|
||||
|
||||
设置完成后，备用设备将收到确认短信。
|
||||
After setup, the backup device will receive a confirmation SMS.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于双重身份验证](/articles/about-two-factor-authentication)"
|
||||
- "[配置双重身份验证](/articles/configuring-two-factor-authentication)"
|
||||
- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
|
||||
- "[丢失双重身份验证凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
- "[Recovering your account if you lose your two-factor authentication credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 配置双重身份验证
|
||||
intro: 您可以选择多个选项，以向帐户添加第二个身份验证源。
|
||||
title: Configuring two-factor authentication
|
||||
intro: You can choose among multiple options to add a second source of authentication to your account.
|
||||
redirect_from:
|
||||
- /articles/configuring-two-factor-authentication-via-a-totp-mobile-app/
|
||||
- /articles/configuring-two-factor-authentication-via-text-message/
|
||||
- /articles/configuring-two-factor-authentication-via-fido-u2f/
|
||||
- /articles/configuring-two-factor-authentication-via-a-totp-mobile-app
|
||||
- /articles/configuring-two-factor-authentication-via-text-message
|
||||
- /articles/configuring-two-factor-authentication-via-fido-u2f
|
||||
- /articles/configuring-two-factor-authentication
|
||||
- /github/authenticating-to-github/configuring-two-factor-authentication
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication
|
||||
@@ -14,30 +14,29 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- 2FA
|
||||
shortTitle: 配置 2FA
|
||||
shortTitle: Configure 2FA
|
||||
---
|
||||
You can configure two-factor authentication using a mobile app{% ifversion fpt or ghec %} or via text message{% endif %}. You can also add a security key.
|
||||
|
||||
您可以使用移动应用程序{% ifversion fpt or ghec %} 或通过短信{% endif %}配置双重身份验证。 您也可以添加安全密钥。
|
||||
|
||||
我们强力建议使用基于时间的一次性密码 (TOTP) 应用程序来配置 2FA。{% ifversion fpt or ghec %} TOTP 应用程序比 SMS 更可靠，特别是对于美国以外的地区。{% endif %} TOTP 应用程序支持在云中安全备份您的验证码，在无法访问设备的情况下也可以进行恢复。
|
||||
We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA.{% ifversion fpt or ghec %} TOTP applications are more reliable than SMS, especially for locations outside the United States.{% endif %} TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**
|
||||
- 如果您是要求双重身份验证的组织中的成员{% ifversion fpt or ghec %}、帐单管理员{% endif %}或其私有仓库的外部协作者，则必须离开该组织后才能在 {% data variables.product.product_location %} 上禁用 2FA。
|
||||
- 如果禁用 2FA，您将自动失去对该组织以及您在该组织私有仓库中所拥有的任何私有复刻的访问权限。 要恢复对该组织和复刻的访问权限，请重新启用双重身份验证并联系组织所有者。
|
||||
**Warning:**
|
||||
- If you're a member{% ifversion fpt or ghec %}, billing manager,{% endif %} or outside collaborator to a private repository of an organization that requires two-factor authentication, you must leave the organization before you can disable 2FA on {% data variables.product.product_location %}.
|
||||
- If you disable 2FA, you will automatically lose access to the organization and any private forks you have of the organization's private repositories. To regain access to the organization and your forks, re-enable two-factor authentication and contact an organization owner.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
|
||||
If you're a member of an {% data variables.product.prodname_emu_enterprise %}, you cannot configure 2FA for your {% data variables.product.prodname_managed_user %} account. 2FA should be configured through your identity provider.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 使用 TOTP 移动应用程序配置双重身份验证
|
||||
## Configuring two-factor authentication using a TOTP mobile app
|
||||
|
||||
基于时间的一次性密码 (TOTP) 应用程序可自动生成在特定时间后变化的验证码。 我们建议使用基于云的 TOTP 应用程序，例如：
|
||||
A time-based one-time password (TOTP) application automatically generates an authentication code that changes after a certain period of time. We recommend using cloud-based TOTP apps such as:
|
||||
- [1Password](https://support.1password.com/one-time-passwords/)
|
||||
- [Authy](https://authy.com/guides/github/)
|
||||
- [LastPass Authenticator](https://lastpass.com/auth/)
|
||||
@@ -45,88 +44,98 @@ If you're a member of an {% data variables.product.prodname_emu_enterprise %}, y
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：要在多个设备上通过 TOTP 配置身份验证，请在设置过程中，同时使用每个设备扫描 QR 码。 如果已启用 2FA，但您要添加其他设备，则必须从安全设置中重新配置 2FA。
|
||||
**Tip**: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. If 2FA is already enabled and you want to add another device, you must re-configure 2FA from your security settings.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. 下载 TOTP 应用程序。
|
||||
1. Download a TOTP app.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.enable-two-factor-authentication %}
|
||||
{%- ifversion fpt or ghes > 3.1 %}
|
||||
5. 在“Two-factor authentication（双重身份验证）”下选择 **Set up using an app（使用应用程序设置）**并点击 **Continue（继续）**。
|
||||
6. 在“Authentication verification（身份验证）”下，执行以下操作之一：
|
||||
- 使用移动设备的应用程序扫描 QR 码。 扫描完成后，应用程序会显示六位数代码，您可以在 {% data variables.product.product_name %} 输入该代码。
|
||||
- 如果无法扫描 QR 码，请单击 **enter this text code（输入此文本代码）**以查看可复制的代码，然后在 TOTP app 上手动输入。 
|
||||
7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. 在 {% data variables.product.product_name %} 上，请在“Enter the six-digit code from the application（从应用程序输入六位数代码）”下的字段中输入代码。 如果您的恢复代码未自动显示，请单击 **Continue（继续）**。 
|
||||
5. Under "Two-factor authentication", select **Set up using an app** and click **Continue**.
|
||||
6. Under "Authentication verification", do one of the following:
|
||||
- Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
|
||||
- If you can't scan the QR code, click **enter this text code** to see a code that you can manually enter in your TOTP app instead.
|
||||
|
||||
7. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code from the application". If your recovery codes are not automatically displayed, click **Continue**.
|
||||
|
||||
{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
|
||||
{%- else %}
|
||||
5. 在双重身份验证页面上，单击 **Set up using an app（使用应用程序设置）**。
|
||||
6. 将恢复代码保存在安全的位置。 在失去访问权限时，恢复代码可帮助您恢复帐户登录。
|
||||
- 要在设备上保存恢复代码，请单击 **Download（下载）**。
|
||||
- 要保存恢复代码的硬拷贝，请单击 **Print（打印）**。
|
||||
- 要复制恢复代码以存储在密码管理器中，请单击**复制**。 
|
||||
7. 保存双重身份验证恢复代码后，单击 **Next（下一步）**。
|
||||
8. 在双重身份验证页面上，执行以下操作之一：
|
||||
- 使用移动设备的应用程序扫描 QR 码。 扫描完成后，应用程序会显示六位数代码，您可以在 {% data variables.product.product_name %} 输入该代码。
|
||||
- 如果无法扫描 QR 码，请单击 **enter this text code（输入此文本代码）**以查看可复制的代码，然后在 {% data variables.product.product_name %} 上手动输入。 
|
||||
9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. 在 {% data variables.product.product_name %} 中的 2FA 页面上，键入代码并单击 **Enable（启用）**。 
|
||||
5. On the Two-factor authentication page, click **Set up using an app**.
|
||||
6. Save your recovery codes in a safe place. Your recovery codes can help you get back into your account if you lose access.
|
||||
- To save your recovery codes on your device, click **Download**.
|
||||
- To save a hard copy of your recovery codes, click **Print**.
|
||||
- To copy your recovery codes for storage in a password manager, click **Copy**.
|
||||
|
||||
7. After saving your two-factor recovery codes, click **Next**.
|
||||
8. On the Two-factor authentication page, do one of the following:
|
||||
- Scan the QR code with your mobile device's app. After scanning, the app displays a six-digit code that you can enter on {% data variables.product.product_name %}.
|
||||
- If you can't scan the QR code, click **enter this text code** to see a code you can copy and manually enter on {% data variables.product.product_name %} instead.
|
||||
|
||||
9. The TOTP mobile application saves your account on {% data variables.product.product_location %} and generates a new authentication code every few seconds. On {% data variables.product.product_name %}, on the 2FA page, type the code and click **Enable**.
|
||||
|
||||
{%- endif %}
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 使用短信配置双重身份验证
|
||||
## Configuring two-factor authentication using text messages
|
||||
|
||||
如果无法使用 TOTP 移动应用程序进行身份验证，您可以使用短信进行身份验证。 也可以提供后备设备的号码作为第二号码。 在无法访问主设备和恢复代码时，可通过备用短信号码恢复帐户登录。
|
||||
If you're unable to authenticate using a TOTP mobile app, you can authenticate using SMS messages. You can also provide a second number for a fallback device. If you lose access to both your primary device and your recovery codes, a backup SMS number can get you back in to your account.
|
||||
|
||||
在使用此方法之前，请确保您可以接收短信。 运营商可能会收取短信费用。
|
||||
Before using this method, be sure that you can receive text messages. Carrier rates may apply.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告：**我们**强烈建议**使用 TOTP 应用程序进行双重身份验证，而不是使用 SMS。 {% data variables.product.product_name %} 并非支持向每个国家/地区的手机发送短信。 通过短信配置身份验证之前，请查看 {% data variables.product.product_name %} 支持通过 SMS 验证的国家/地区列表。 更多信息请参阅“[支持 SMS 身份验证的国家/地区](/articles/countries-where-sms-authentication-is-supported)”。
|
||||
**Warning:** We **strongly recommend** using a TOTP application for two-factor authentication instead of SMS. {% data variables.product.product_name %} doesn't support sending SMS messages to phones in every country. Before configuring authentication via text message, review the list of countries where {% data variables.product.product_name %} supports authentication via SMS. For more information, see "[Countries where SMS authentication is supported](/articles/countries-where-sms-authentication-is-supported)".
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{% data reusables.two_fa.enable-two-factor-authentication %}
|
||||
4. 在“Two-factor authentication（双重身份验证）”下选择 **Set up using SMS（使用 SMS 设置）**并点击 **Continue（继续）**。
|
||||
5. 在“Authentication verification（身份验证）”下，选择您的国家/地区代码并键入您的手机号码，包括区号。 确认信息无误后，单击 **Send authentication code（发送验证码）**。
|
||||
4. Under "Two-factor authentication", select **Set up using SMS** and click **Continue**.
|
||||
5. Under "Authentication verification", select your country code and type your mobile phone number, including the area code. When your information is correct, click **Send authentication code**.
|
||||
|
||||
|
||||
|
||||
|
||||
6. 您将收到含安全码的短信。 在 {% data variables.product.product_name %} 上，请在“Enter the six-digit code sent to your phone（输入发送到手机的六位数代码）”下的字段中输入代码，然后单击 **Continue（继续）**。
|
||||
6. You'll receive a text message with a security code. On {% data variables.product.product_name %}, type the code into the field under "Enter the six-digit code sent to your phone" and click **Continue**.
|
||||
|
||||
|
||||
|
||||
{% data reusables.two_fa.save_your_recovery_codes_during_2fa_setup %}
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 使用安全密钥配置双重身份验证
|
||||
## Configuring two-factor authentication using a security key
|
||||
|
||||
{% data reusables.two_fa.after-2fa-add-security-key %}
|
||||
|
||||
在大多数设备和浏览器上，您可以通过 USB 或 NFC 使用物理安全密钥。 某些浏览器可以使用设备上的指纹读取器、面部识别或密码/PIN 作为安全密钥。
|
||||
On most devices and browsers, you can use a physical security key over USB or NFC. Some browsers can use the fingerprint reader, facial recognition, or password/PIN on your device as a security key.
|
||||
|
||||
安全密钥验证是 TOTP 应用程序{% ifversion fpt or ghec %} 或短信{% endif %}验证的*备用*选择。 如果您丢失了安全密钥，仍可以使用手机的代码进行登录。
|
||||
Authentication with a security key is *secondary* to authentication with a TOTP application{% ifversion fpt or ghec %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
|
||||
|
||||
1. 必须已通过 TOTP 移动应用程序{% ifversion fpt or ghec %} 或通过 SMS{% endif %} 配置了 2FA。
|
||||
2. 确保您的计算机中已插入 WebAuthn 兼容安全密钥。
|
||||
1. You must have already configured 2FA via a TOTP mobile app{% ifversion fpt or ghec %} or via SMS{% endif %}.
|
||||
2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
5. 在“Security keys（安全密钥）”旁边，单击 **添加**。 
|
||||
6. 在“Security keys（安全密钥）”下，单击 **Register new security key（注册新安全密钥）**。 
|
||||
7. 键入安全密钥的昵称，然后单击 **Add（添加）**。 
|
||||
8. 按照安全密钥的文档激活安全密钥。 
|
||||
9. 确认您已下载并且能够访问恢复代码。 如果尚未下载，或者要生成另一组代码，请下载代码并将其保存在安全位置。 如果无法访问自己的帐户，您可以使用恢复代码来恢复帐户访问。 更多信息请参阅“[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”。 
|
||||
5. Next to "Security keys", click **Add**.
|
||||
|
||||
6. Under "Security keys", click **Register new security key**.
|
||||
|
||||
7. Type a nickname for the security key, then click **Add**.
|
||||
|
||||
8. Activate your security key, following your security key's documentation.
|
||||
|
||||
9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||
|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[关于双重身份验证](/articles/about-two-factor-authentication)"
|
||||
- "[配置双重身份验证恢复方法](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- “[使用双重身份验证访问 {% data variables.product.prodname_dotcom %}](/articles/accessing-github-using-two-factor-authentication)”。
|
||||
- “[丢失 2FA 凭据时恢复帐户](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)”
|
||||
- “[创建个人访问令牌](/github/authenticating-to-github/creating-a-personal-access-token)”。
|
||||
- "[About two-factor authentication](/articles/about-two-factor-authentication)"
|
||||
- "[Configuring two-factor authentication recovery methods](/articles/configuring-two-factor-authentication-recovery-methods)"
|
||||
- "[Accessing {% data variables.product.prodname_dotcom %} using two-factor authentication](/articles/accessing-github-using-two-factor-authentication)"
|
||||
- "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)"
|
||||
- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)"
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: 使用双重身份验证 (2FA) 保护您的帐户
|
||||
title: Securing your account with two-factor authentication (2FA)
|
||||
intro: 'You can set up your account on {% data variables.product.product_location %} to require an authentication code in addition to your password when you sign in.'
|
||||
redirect_from:
|
||||
- /categories/84/articles/
|
||||
- /categories/two-factor-authentication-2fa/
|
||||
- /categories/84/articles
|
||||
- /categories/two-factor-authentication-2fa
|
||||
- /articles/securing-your-account-with-two-factor-authentication-2fa
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -21,6 +21,6 @@ children:
|
||||
- /changing-two-factor-authentication-delivery-methods-for-your-mobile-device
|
||||
- /countries-where-sms-authentication-is-supported
|
||||
- /disabling-two-factor-authentication-for-your-personal-account
|
||||
shortTitle: 使用 2FA 保护您的帐户
|
||||
shortTitle: Secure your account with 2FA
|
||||
---
|
||||
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: Recovering your account if you lose your 2FA credentials
|
||||
intro: 'If you lose access to your two-factor authentication credentials, you can use your recovery codes, or another recovery option, to regain access to your account.'
|
||||
redirect_from:
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials/
|
||||
- /articles/authenticating-with-an-account-recovery-token/
|
||||
- /articles/recovering-your-account-if-you-lost-your-2fa-credentials
|
||||
- /articles/authenticating-with-an-account-recovery-token
|
||||
- /articles/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /github/authenticating-to-github/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
- /github/authenticating-to-github/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 寻找在 GitHub 上参与开源项目的方法
|
||||
intro: '您可以找到在 {% data variables.product.product_location %} 上参加与您相关的开源项目的方法。'
|
||||
title: Finding ways to contribute to open source on GitHub
|
||||
intro: 'You can find ways to contribute to open source projects on {% data variables.product.product_location %} that are relevant to you.'
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
|
||||
redirect_from:
|
||||
- /articles/where-can-i-find-open-source-projects-to-work-on/
|
||||
- /articles/finding-interesting-projects-on-github/
|
||||
- /articles/about-official-github-mirrors/
|
||||
- /articles/about-github-mirrors/
|
||||
- /articles/where-can-i-find-open-source-projects-to-work-on
|
||||
- /articles/finding-interesting-projects-on-github
|
||||
- /articles/about-official-github-mirrors
|
||||
- /articles/about-github-mirrors
|
||||
- /articles/finding-open-source-projects-on-github
|
||||
- /github/getting-started-with-github/finding-open-source-projects-on-github
|
||||
- /github/getting-started-with-github/finding-ways-to-contribute-to-open-source-on-github
|
||||
@@ -16,42 +16,41 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Open Source
|
||||
shortTitle: 为开源做贡献
|
||||
shortTitle: Contribute to open source
|
||||
---
|
||||
## Discovering relevant projects
|
||||
|
||||
## 发现相关项目
|
||||
If there's a particular topic that interests you, visit `github.com/topics/<topic>`. For example, if you are interested in machine learning, you can find relevant projects and good first issues by visiting https://github.com/topics/machine-learning. You can browse popular topics by visiting [Topics](https://github.com/topics). You can also search for repositories that match a topic you're interested in. For more information, see "[Searching for repositories](/search-github/searching-on-github/searching-for-repositories#search-by-topic)."
|
||||
|
||||
如果有您感兴趣的特定主题，请访问 `github.com/topics/<topic>`。 例如，如果您对机器学习感兴趣，可以通过访问 https://github.com/topics/machine-learning 找到相关的项目和合适的第一个议题。 您可以通过访问[主题](https://github.com/topics)来浏览热门主题。 您还可以搜索与您感兴趣的主题相匹配的仓库。 更多信息请参阅“[搜索仓库](/search-github/searching-on-github/searching-for-repositories#search-by-topic)”。
|
||||
If you've been active on {% data variables.product.product_location %}, you can find personalized recommendations for projects and good first issues based on your past contributions, stars, and other activities in [Explore](https://github.com/explore). You can also sign up for the Explore newsletter to receive emails about opportunities to contribute to {% data variables.product.product_name %} based on your interests. To sign up, see [Explore email newsletter](https://github.com/explore/subscribe).
|
||||
|
||||
如果您一直活跃在 {% data variables.product.product_location %} 上，可以根据您过去的参与、标星以及在 [Explore](https://github.com/explore) 中的其他活动，为您的项目找到个性化的建议和合适的第一个议题。 您还可以注册 Explore 通讯以根据您的兴趣接收相关电子邮件，了解参与 {% data variables.product.product_name %} 的机会。 要注册，请参阅 [Explore 电子邮件通讯](https://github.com/explore/subscribe)。
|
||||
|
||||
在个人仪表板的“All activity（所有活动）”部分中，了解您关注的仓库和人员的最新活动。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
|
||||
Keep up with recent activity from repositories you watch and people you follow in the "All activity" section of your personal dashboard. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
## 查找合适的第一个议题
|
||||
## Finding good first issues
|
||||
|
||||
如果您已经知道要参与哪些项目，可通过访问 `github.com/<owner>/<repository>/contribute` 查找该仓库中便于初学者参与的议题。 例如，您可以在 https://github.com/electron/electron/contribute 上找到第一次参与 `electron/electron` 的方法。
|
||||
If you already know what project you want to work on, you can find beginner-friendly issues in that repository by visiting `github.com/<owner>/<repository>/contribute`. For an example, you can find ways to make your first contribution to `electron/electron` at https://github.com/electron/electron/contribute.
|
||||
|
||||
## 打开议题
|
||||
## Opening an issue
|
||||
|
||||
如果在开源项目中遇到漏洞，请检查该漏洞是否已报告。 如果该漏洞尚未报告，您可以根据项目的参与指南开启一个议题来报告该漏洞。
|
||||
If you encounter a bug in an open source project, check if the bug has already been reported. If the bug has not been reported, you can open an issue to report the bug according to the project's contribution guidelines.
|
||||
|
||||
## 验证议题或拉取请求
|
||||
## Validating an issue or pull request
|
||||
|
||||
您可以通过多种方式为开源项目做出贡献。
|
||||
There are a variety of ways that you can contribute to open source projects.
|
||||
|
||||
### 重现报告的漏洞
|
||||
您可以通过验证议题或为现有议题添加额外上下文来为开源项目做出贡献。
|
||||
### Reproducing a reported bug
|
||||
You can contribute to an open source project by validating an issue or adding additional context to an existing issue.
|
||||
|
||||
### 测试拉取请求
|
||||
您可以通过将拉取请求合并到项目的本地副本中并测试更改来为开源项目做出贡献。 在对拉取请求的评论中添加测试结果。
|
||||
### Testing a pull request
|
||||
You can contribute to an open source project by merging a pull request into your local copy of the project and testing the changes. Add the outcome of your testing in a comment on the pull request.
|
||||
|
||||
### 更新议题
|
||||
您可以通过向现有议题添加额外信息来为开源项目做出贡献。
|
||||
### Updating issues
|
||||
You can contribute to an open source project by adding additional information to existing issues.
|
||||
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[使用主题对仓库分类](/articles/classifying-your-repository-with-topics)"
|
||||
- "[关于组织仪表板](/articles/about-your-organization-dashboard)"
|
||||
- "[Classifying your repository with topics](/articles/classifying-your-repository-with-topics)"
|
||||
- "[About your organization dashboard](/articles/about-your-organization-dashboard)"
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 在 GitHub 上探索项目
|
||||
intro: '在 {% data variables.product.product_name %} 上发现有趣的项目，并与其他人合作为开源做贡献。'
|
||||
title: Exploring projects on GitHub
|
||||
intro: 'Discover interesting projects on {% data variables.product.product_name %} and contribute to open source by collaborating with other people.'
|
||||
redirect_from:
|
||||
- /categories/stars/
|
||||
- /categories/87/articles/
|
||||
- /categories/exploring-projects-on-github/
|
||||
- /categories/stars
|
||||
- /categories/87/articles
|
||||
- /categories/exploring-projects-on-github
|
||||
- /articles/exploring-projects-on-github
|
||||
- /github/getting-started-with-github/exploring-projects-on-github/
|
||||
- /github/getting-started-with-github/exploring-projects-on-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -18,6 +18,6 @@ children:
|
||||
- /finding-ways-to-contribute-to-open-source-on-github
|
||||
- /saving-repositories-with-stars
|
||||
- /following-people
|
||||
shortTitle: 探索项目
|
||||
shortTitle: Explore projects
|
||||
---
|
||||
|
||||
|
||||
@@ -2,10 +2,10 @@
|
||||
title: Saving repositories with stars
|
||||
intro: 'You can star repositories and topics to keep track of projects you find interesting{% ifversion fpt or ghec %} and discover related content in your news feed{% endif %}.'
|
||||
redirect_from:
|
||||
- /articles/stars/
|
||||
- /articles/about-stars/
|
||||
- /articles/browsing-friends-stars/
|
||||
- /articles/managing-your-stars/
|
||||
- /articles/stars
|
||||
- /articles/about-stars
|
||||
- /articles/browsing-friends-stars
|
||||
- /articles/managing-your-stars
|
||||
- /articles/saving-repositories-with-stars
|
||||
- /github/getting-started-with-github/saving-repositories-with-stars
|
||||
- /github/getting-started-with-github/exploring-projects-on-github/saving-repositories-with-stars
|
||||
|
||||
@@ -1,98 +1,98 @@
|
||||
---
|
||||
title: 关于远程仓库
|
||||
title: About remote repositories
|
||||
redirect_from:
|
||||
- /articles/working-when-github-goes-down/
|
||||
- /articles/sharing-repositories-without-github/
|
||||
- /articles/working-when-github-goes-down
|
||||
- /articles/sharing-repositories-without-github
|
||||
- /articles/about-remote-repositories
|
||||
- /articles/which-url-should-i-use/
|
||||
- /articles/which-url-should-i-use
|
||||
- /articles/which-remote-url-should-i-use
|
||||
- /github/using-git/which-remote-url-should-i-use
|
||||
- /github/using-git/about-remote-repositories
|
||||
- /github/getting-started-with-github/about-remote-repositories
|
||||
- /github/getting-started-with-github/getting-started-with-git/about-remote-repositories
|
||||
intro: 'GitHub 的协作开发方法取决于从您的本地仓库发布提交到 {% data variables.product.product_name %}，以供其他人查看、提取和更新。'
|
||||
intro: 'GitHub''s collaborative approach to development depends on publishing commits from your local repository to {% data variables.product.product_name %} for other people to view, fetch, and update.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## About remote repositories
|
||||
|
||||
## 关于远程仓库
|
||||
A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
|
||||
|
||||
远程 URL 是 Git 一种指示“您的代码存储位置”的绝佳方式。 该 URL 可能是您在 GitHub 上的仓库，也可以是另一个用户的复刻，甚至在完全不同的服务器上。
|
||||
You can only push to two types of URL addresses:
|
||||
|
||||
您只能推送到两类 URL 地址：
|
||||
* An HTTPS URL like `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
* An SSH URL, like `git@{% data variables.command_line.backticks %}:user/repo.git`
|
||||
|
||||
* HTTPS URL，如 `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
* SSH URL，如 `git@{% data variables.command_line.backticks %}:user/repo.git`
|
||||
Git associates a remote URL with a name, and your default remote is usually called `origin`.
|
||||
|
||||
Git 将远程 URL 与名称相关联，您的默认远程通常名为 `origin`。
|
||||
## Creating remote repositories
|
||||
|
||||
## 创建远程仓库
|
||||
|
||||
您可以使用 `git remote add` 命令将远程 URL 与名称匹配。 例如，在命令行中输入以下命令：
|
||||
You can use the `git remote add` command to match a remote URL with a name.
|
||||
For example, you'd type the following in the command line:
|
||||
|
||||
```shell
|
||||
git remote add origin <em> <REMOTE_URL> </em>
|
||||
```
|
||||
|
||||
这会将名称 `origin` 与 `REMOTE_URL` 关联。
|
||||
This associates the name `origin` with the `REMOTE_URL`.
|
||||
|
||||
您可以使用命令 `git remote set-url` 来[更改远程 URL](/github/getting-started-with-github/managing-remote-repositories)。
|
||||
You can use the command `git remote set-url` to [change a remote's URL](/github/getting-started-with-github/managing-remote-repositories).
|
||||
|
||||
## 选择远程仓库的 URL
|
||||
## Choosing a URL for your remote repository
|
||||
|
||||
克隆 {% data variables.product.product_location %} 上的仓库有几种方法。
|
||||
There are several ways to clone repositories available on {% data variables.product.product_location %}.
|
||||
|
||||
当您登录到帐户查看仓库时，可以用于将项目克隆到计算机上的 URL 在仓库详细信息下方提供。
|
||||
When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details.
|
||||
|
||||
有关设置或更改远程 URL 的信息，请参阅“[管理远程仓库](/github/getting-started-with-github/managing-remote-repositories)”。
|
||||
For information on setting or changing your remote URL, see "[Managing remote repositories](/github/getting-started-with-github/managing-remote-repositories)."
|
||||
|
||||
## 使用 HTTPS URL 克隆
|
||||
## Cloning with HTTPS URLs
|
||||
|
||||
`https://` 克隆 URL 在所有仓库中提供，与可见性无关。 即使您在防火墙或代理后面，`https://` 克隆 URL 也有效。
|
||||
The `https://` clone URLs are available on all repositories, regardless of visibility. `https://` clone URLs work even if you are behind a firewall or proxy.
|
||||
|
||||
当您在命令行中使用 HTTPS URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，Git 将要求您输入 {% data variables.product.product_name %} 用户名和密码。 {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using HTTPS URLs on the command line, Git will ask for your {% data variables.product.product_name %} username and password. {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
|
||||
{% data reusables.command_line.provide-an-access-token %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：
|
||||
- 您可以使用凭据小助手，让 Git 在每次与 {% data variables.product.prodname_dotcom %} 通信时记住您的 {% data variables.product.prodname_dotcom %} 凭据。 更多信息请参阅“[在 Git 中缓存 {% data variables.product.prodname_dotcom %} 凭据](/github/getting-started-with-github/caching-your-github-credentials-in-git)”。
|
||||
- 要克隆仓库而不在命令行中对 {% data variables.product.product_name %} 进行身份验证，您可以使用 {% data variables.product.prodname_desktop %} 进行克隆。 更多信息请参阅“[将仓库从 {% data variables.product.prodname_dotcom %} 克隆到 {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)”。
|
||||
**Tips**:
|
||||
- You can use a credential helper so Git will remember your {% data variables.product.prodname_dotcom %} credentials every time it talks to {% data variables.product.prodname_dotcom %}. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
|
||||
- To clone a repository without authenticating to {% data variables.product.product_name %} on the command line, you can use {% data variables.product.prodname_desktop %} to clone instead. For more information, see "[Cloning a repository from {% data variables.product.prodname_dotcom %} to {% data variables.product.prodname_dotcom %} Desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghec %}如果您希望使用 SSH，但不能通过端口 22 进行连接，则可通过 HTTPS 端口使用 SSH。 更多信息请参阅“[通过 HTTPS 端口使用 SSH](/github/authenticating-to-github/using-ssh-over-the-https-port)”。{% endif %}
|
||||
{% ifversion fpt or ghec %}If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "[Using SSH over the HTTPS port](/github/authenticating-to-github/using-ssh-over-the-https-port)."{% endif %}
|
||||
|
||||
## 使用 SSH URL 克隆
|
||||
## Cloning with SSH URLs
|
||||
|
||||
SSH URL 通过 SSH（一种安全协议）提供 Git 仓库的访问权限。 To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. 更多信息请参阅“[通过 SSH 连接 {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/connecting-to-github-with-ssh)”。
|
||||
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the **public** key to your account on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}. For more information, see "[Connecting to {% data variables.product.prodname_dotcom %} with SSH](/github/authenticating-to-github/connecting-to-github-with-ssh)."
|
||||
|
||||
使用 SSH URL 对远程仓库执行 `git clone`、`git fetch`、`git pull` 或 `git push` 命令时，系统将提示您输入密码，并且必须提供您的 SSH 密钥密码。 更多信息请参阅“[使用 SSH 密钥密码](/github/authenticating-to-github/working-with-ssh-key-passphrases)”。
|
||||
When you `git clone`, `git fetch`, `git pull`, or `git push` to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "[Working with SSH key passphrases](/github/authenticating-to-github/working-with-ssh-key-passphrases)."
|
||||
|
||||
{% ifversion fpt or ghec %}如果要访问使用 SAML 单点登录 (SSO) 的组织，您在进行身份验证之前必须授权 SSH 密钥以访问组织。 更多信息请参阅“[关于使用 SAML 单点登录进行身份验证](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)”和“[授权 SSH 密码以用于 SAML 单点登录](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)”。{% endif %}
|
||||
{% ifversion fpt or ghec %}If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "[About authentication with SAML single sign-on](/github/authenticating-to-github/about-authentication-with-saml-single-sign-on)" and "[Authorizing an SSH key for use with SAML single sign-on](/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)."{% endif %}
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：您可以使用 SSH URL 将仓库克隆到计算机，或作为将代码部署到生产服务器的安全方法。 您还可以将 SSH 代理转发与部署脚本一起使用，以避免管理服务器上的密钥。 更多信息请参阅“[使用 SSH 代理转发](/developers/overview/using-ssh-agent-forwarding)”。
|
||||
**Tip**: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "[Using SSH Agent Forwarding](/developers/overview/using-ssh-agent-forwarding)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% ifversion fpt or ghes or ghae or ghec %}
|
||||
|
||||
## 使用 {% data variables.product.prodname_cli %} 克隆
|
||||
## Cloning with {% data variables.product.prodname_cli %}
|
||||
|
||||
您还可以安装 {% data variables.product.prodname_cli %} 以在终端中使用 {% data variables.product.product_name %} 工作流程。 更多信息请参阅“[关于 {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)”。
|
||||
You can also install {% data variables.product.prodname_cli %} to use {% data variables.product.product_name %} workflows in your terminal. For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion not ghae %}
|
||||
## 使用 Subversion 克隆
|
||||
## Cloning with Subversion
|
||||
|
||||
您还可以使用 [Subversion](https://subversion.apache.org/) 客户端访问 {% data variables.product.prodname_dotcom %} 上的任何仓库。 Subversion 提供不同于 Git 的功能集。 更多信息请参阅“[Subversion 与 Git 之间有何差异？](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)”
|
||||
You can also use a [Subversion](https://subversion.apache.org/) client to access any repository on {% data variables.product.prodname_dotcom %}. Subversion offers a different feature set than Git. For more information, see "[What are the differences between Subversion and Git?](/github/importing-your-projects-to-github/what-are-the-differences-between-subversion-and-git)"
|
||||
|
||||
您也可以从 Subversion 客户端访问 {% data variables.product.prodname_dotcom %} 上的仓库。 更多信息请参阅“[Subversion 客户端的支持](/github/importing-your-projects-to-github/support-for-subversion-clients)”。
|
||||
You can also access repositories on {% data variables.product.prodname_dotcom %} from Subversion clients. For more information, see "[Support for Subversion clients](/github/importing-your-projects-to-github/support-for-subversion-clients)."
|
||||
{% endif %}
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 关联文本编辑器与 Git
|
||||
intro: 使用文本编辑器打开文件并通过 Git 编辑。
|
||||
title: Associating text editors with Git
|
||||
intro: Use a text editor to open and edit your files with Git.
|
||||
redirect_from:
|
||||
- /textmate/
|
||||
- /articles/using-textmate-as-your-default-editor/
|
||||
- /articles/using-sublime-text-2-as-your-default-editor/
|
||||
- /textmate
|
||||
- /articles/using-textmate-as-your-default-editor
|
||||
- /articles/using-sublime-text-2-as-your-default-editor
|
||||
- /articles/associating-text-editors-with-git
|
||||
- /github/using-git/associating-text-editors-with-git
|
||||
- /github/getting-started-with-github/associating-text-editors-with-git
|
||||
@@ -14,44 +14,43 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: 关联文本编辑器
|
||||
shortTitle: Associate text editors
|
||||
---
|
||||
|
||||
{% mac %}
|
||||
|
||||
## 使用 Atom 作为编辑器
|
||||
## Using Atom as your editor
|
||||
|
||||
1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## 使用 Visual Studio Code 作为编辑器
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## 使用 Sublime Text 作为编辑器
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
## 使用 TextMate 作为编辑器
|
||||
## Using TextMate as your editor
|
||||
|
||||
1. 安装 [TextMate](https://macromates.com/)。
|
||||
2. 安装 TextMate 的 `mate` shell 实用程序。 更多信息请参阅 TextMate 文档中的“[mate 和 rmate](https://macromates.com/blog/2011/mate-and-rmate/)”。
|
||||
1. Install [TextMate](https://macromates.com/).
|
||||
2. Install TextMate's `mate` shell utility. For more information, see "[mate and rmate](https://macromates.com/blog/2011/mate-and-rmate/)" in the TextMate documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
4. 输入此命令：
|
||||
4. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "mate -w"
|
||||
```
|
||||
@@ -59,38 +58,38 @@ shortTitle: 关联文本编辑器
|
||||
|
||||
{% windows %}
|
||||
|
||||
## 使用 Atom 作为编辑器
|
||||
## Using Atom as your editor
|
||||
|
||||
1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## 使用 Visual Studio Code 作为编辑器
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## 使用 Sublime Text 作为编辑器
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/sublime text 3/subl.exe' -w"
|
||||
```
|
||||
|
||||
## 使用 Notepad++ 作为编辑器
|
||||
## Using Notepad++ as your editor
|
||||
|
||||
1. 从 https://notepad-plus-plus.org/ 安装 Notepad++。 更多信息请参阅 Notepad++ 文档中的“[入门指南](https://npp-user-manual.org/docs/getting-started/)”。
|
||||
1. Install Notepad++ from https://notepad-plus-plus.org/. For more information, see "[Getting started](https://npp-user-manual.org/docs/getting-started/)" in the Notepad++ documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "'C:/Program Files (x86)/Notepad++/notepad++.exe' -multiInst -notabbar -nosession -noPlugin"
|
||||
```
|
||||
@@ -98,29 +97,29 @@ shortTitle: 关联文本编辑器
|
||||
|
||||
{% linux %}
|
||||
|
||||
## 使用 Atom 作为编辑器
|
||||
## Using Atom as your editor
|
||||
|
||||
1. 安装 [Atom](https://atom.io/)。 更多信息请参阅 Atom 文档中的“[安装 Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)”。
|
||||
1. Install [Atom](https://atom.io/). For more information, see "[Installing Atom](https://flight-manual.atom.io/getting-started/sections/installing-atom/)" in the Atom documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "atom --wait"
|
||||
```
|
||||
|
||||
## 使用 Visual Studio Code 作为编辑器
|
||||
## Using Visual Studio Code as your editor
|
||||
|
||||
1. 安装 [Visual Studio Code](https://code.visualstudio.com/) (VS Code)。 更多信息请参阅 VS Code 文档中的“[设置 Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)”。
|
||||
1. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code). For more information, see "[Setting up Visual Studio Code](https://code.visualstudio.com/Docs/setup/setup-overview)" in the VS Code documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "code --wait"
|
||||
```
|
||||
|
||||
## 使用 Sublime Text 作为编辑器
|
||||
## Using Sublime Text as your editor
|
||||
|
||||
1. 安装 [Sublime Text](https://www.sublimetext.com/)。 更多信息请参阅 Sublime Text 文档中的“[安装](https://docs.sublimetext.io/guide/getting-started/installation.html)”。
|
||||
1. Install [Sublime Text](https://www.sublimetext.com/). For more information, see "[Installation](https://docs.sublimetext.io/guide/getting-started/installation.html)" in the Sublime Text documentation.
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
3. 输入此命令：
|
||||
3. Type this command:
|
||||
```shell
|
||||
$ git config --global core.editor "subl -n -w"
|
||||
```
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Caching your GitHub credentials in Git
|
||||
redirect_from:
|
||||
- /firewalls-and-proxies/
|
||||
- /firewalls-and-proxies
|
||||
- /articles/caching-your-github-password-in-git
|
||||
- /github/using-git/caching-your-github-password-in-git
|
||||
- /github/using-git/caching-your-github-credentials-in-git
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 配置 Git 处理行结束符
|
||||
intro: 为避免差异中出现问题，可配置 Git 正常处理行标题。
|
||||
title: Configuring Git to handle line endings
|
||||
intro: 'To avoid problems in your diffs, you can configure Git to properly handle line endings.'
|
||||
redirect_from:
|
||||
- /dealing-with-lineendings/
|
||||
- /line-endings/
|
||||
- /articles/dealing-with-line-endings/
|
||||
- /dealing-with-lineendings
|
||||
- /line-endings
|
||||
- /articles/dealing-with-line-endings
|
||||
- /articles/configuring-git-to-handle-line-endings
|
||||
- /github/using-git/configuring-git-to-handle-line-endings
|
||||
- /github/getting-started-with-github/configuring-git-to-handle-line-endings
|
||||
@@ -14,23 +14,22 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: 处理行结束
|
||||
shortTitle: Handle line endings
|
||||
---
|
||||
|
||||
## About line endings
|
||||
每次按键盘上的 <kbd>return</kbd> 时，会插入一个称为行结束符的不可见字符。 不同的操作系统处理行结束符的方式不同。
|
||||
Every time you press <kbd>return</kbd> on your keyboard you insert an invisible character called a line ending. Different operating systems handle line endings differently.
|
||||
|
||||
在使用 Git 和 {% data variables.product.product_name %} 协作处理项目时，Git 可能产生意外结果，例如，您在 Windows 计算机上操作，而您的协作者是在 macOS 中做的更改。
|
||||
When you're collaborating on projects with Git and {% data variables.product.product_name %}, Git might produce unexpected results if, for example, you're working on a Windows machine, and your collaborator has made a change in macOS.
|
||||
|
||||
您可以将 Git 配置为自动处理行结束符，以便与使用不同操作系统的人员有效地协作。
|
||||
You can configure Git to handle line endings automatically so you can collaborate effectively with people who use different operating systems.
|
||||
|
||||
## 行结束符的全局设置
|
||||
## Global settings for line endings
|
||||
|
||||
`git config core.autocrlf` 命令用于更改 Git 处理行结束符的方式。 它将采用单一参数。
|
||||
The `git config core.autocrlf` command is used to change how Git handles line endings. It takes a single argument.
|
||||
|
||||
{% mac %}
|
||||
|
||||
在 macOS 上，只需将 `input（输入）`传递给配置。 例如：
|
||||
On macOS, you simply pass `input` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf input
|
||||
@@ -41,7 +40,7 @@ $ git config --global core.autocrlf input
|
||||
|
||||
{% windows %}
|
||||
|
||||
在 Windows 上，只需将 `true（真）`传递给配置。 例如：
|
||||
On Windows, you simply pass `true` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf true
|
||||
@@ -53,7 +52,7 @@ $ git config --global core.autocrlf true
|
||||
|
||||
{% linux %}
|
||||
|
||||
在 Linux 上，只需将 `input（输入）`传递给配置。 例如：
|
||||
On Linux, you simply pass `input` to the configuration. For example:
|
||||
|
||||
```shell
|
||||
$ git config --global core.autocrlf input
|
||||
@@ -62,20 +61,20 @@ $ git config --global core.autocrlf input
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
## 按仓库设置
|
||||
## Per-repository settings
|
||||
|
||||
（可选）您可以配置 *.gitattribute* 文件来管理 Git 如何读取特定仓库中的行结束符。 将此文件提交到仓库时，它将覆盖所有仓库贡献者的 `core.autocrlf` 设置。 这可确保所有用户的行为一致，而不管其 Git 设置和环境如何。
|
||||
Optionally, you can configure a *.gitattributes* file to manage how Git reads line endings in a specific repository. When you commit this file to a repository, it overrides the `core.autocrlf` setting for all repository contributors. This ensures consistent behavior for all users, regardless of their Git settings and environment.
|
||||
|
||||
*.gitattributes* 文件必须在仓库的根目录下创建，且像任何其他文件一样提交。
|
||||
The *.gitattributes* file must be created in the root of the repository and committed like any other file.
|
||||
|
||||
*.gitattributes* 文件看上去像一个两列表格。
|
||||
A *.gitattributes* file looks like a table with two columns:
|
||||
|
||||
* 左侧是 Git 要匹配的文件名。
|
||||
* 右侧是 Git 应对这些文件使用的行结束符配置。
|
||||
* On the left is the file name for Git to match.
|
||||
* On the right is the line ending configuration that Git should use for those files.
|
||||
|
||||
### 示例
|
||||
### Example
|
||||
|
||||
以下是 *.gitattributes* 文件示例。 您可以将其用作仓库的模板：
|
||||
Here's an example *.gitattributes* file. You can use it as a template for your repositories:
|
||||
|
||||
```
|
||||
# Set the default behavior, in case people don't have core.autocrlf set.
|
||||
@@ -94,43 +93,43 @@ $ git config --global core.autocrlf input
|
||||
*.jpg binary
|
||||
```
|
||||
|
||||
您会发现文件是匹配的—`*.c`, `*.sln`, `*.png`—用空格分隔，然后提供设置—`text`, `text eol=crlf`, `binary`。 我们将在下面介绍一些可能的设置。
|
||||
You'll notice that files are matched—`*.c`, `*.sln`, `*.png`—, separated by a space, then given a setting—`text`, `text eol=crlf`, `binary`. We'll go over some possible settings below.
|
||||
|
||||
- `text=auto` Git 将以其认为最佳的方式处理文件。 这是一个合适的默认选项。
|
||||
- `text=auto` Git will handle the files in whatever way it thinks is best. This is a good default option.
|
||||
|
||||
- `text eol=crlf` 在检出时 Git 将始终把行结束符转换为 `CRLF`。 您应将其用于必须保持 `CRLF` 结束符的文件，即使在 OSX 或 Linux 上。
|
||||
- `text eol=crlf` Git will always convert line endings to `CRLF` on checkout. You should use this for files that must keep `CRLF` endings, even on OSX or Linux.
|
||||
|
||||
- `text eol=lf` 在检出时 Git 将始终把行结束符转换为 `LF`。 您应将其用于必须保持 LF 结束符的文件，即使在 Windows 上。
|
||||
- `text eol=lf` Git will always convert line endings to `LF` on checkout. You should use this for files that must keep LF endings, even on Windows.
|
||||
|
||||
- `binary` Git 会理解指定文件不是文本，并且不应尝试更改这些文件。 `binary` 设置也是 `-text -diff` 的一个别名。
|
||||
- `binary` Git will understand that the files specified are not text, and it should not try to change them. The `binary` setting is also an alias for `-text -diff`.
|
||||
|
||||
## 在更改行结束符后刷新仓库
|
||||
## Refreshing a repository after changing line endings
|
||||
|
||||
设置 `core.autocrlf` 选项或提交 *.gitattributes* 文件后，您可能会发现 Git 报告您尚未修改的文件更改。 Git 更改了行结束符，以匹配您的新配置。
|
||||
When you set the `core.autocrlf` option or commit a *.gitattributes* file, you may find that Git reports changes to files that you have not modified. Git has changed line endings to match your new configuration.
|
||||
|
||||
为确保仓库中的所有行结束符与新配置匹配，请使用 Git 备份文件，删除仓库中的所有文件（`.git` 目录除外），然后一次性恢复所有文件。
|
||||
To ensure that all the line endings in your repository match your new configuration, backup your files with Git, delete all files in your repository (except the `.git` directory), then restore the files all at once.
|
||||
|
||||
1. 在 Git 中保存当前文件，以便不会丢失任何工作。
|
||||
1. Save your current files in Git, so that none of your work is lost.
|
||||
```shell
|
||||
$ git add . -u
|
||||
$ git commit -m "Saving files before refreshing line endings"
|
||||
```
|
||||
2. 添加回所有已更改的文件，然后标准化行结束符。
|
||||
2. Add all your changed files back and normalize the line endings.
|
||||
```shell
|
||||
$ git add --renormalize .
|
||||
```
|
||||
3. 显示已重写的标准化文件。
|
||||
3. Show the rewritten, normalized files.
|
||||
```shell
|
||||
$ git status
|
||||
```
|
||||
4. 将更改提交到仓库。
|
||||
4. Commit the changes to your repository.
|
||||
```shell
|
||||
$ git commit -m "Normalize all the line endings"
|
||||
```
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- Pro Git 书籍中的[自定义 Git - Git 属性](https://git-scm.com/book/en/Customizing-Git-Git-Attributes)
|
||||
- Git 手册页面中的 [git-config](https://git-scm.com/docs/git-config)
|
||||
- Pro Git 书籍中的[入门 - 首次 Git 设置](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup)
|
||||
- [Mind the End of Your Line（注意行的结束）](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/)，作者：[Tim Clem](https://github.com/tclem)
|
||||
- [Customizing Git - Git Attributes](https://git-scm.com/book/en/Customizing-Git-Git-Attributes) in the Pro Git book
|
||||
- [git-config](https://git-scm.com/docs/git-config) in the man pages for Git
|
||||
- [Getting Started - First-Time Git Setup](https://git-scm.com/book/en/Getting-Started-First-Time-Git-Setup) in the Pro Git book
|
||||
- [Mind the End of Your Line](http://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/) by [Tim Clem](https://github.com/tclem)
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Git 工作流程
|
||||
intro: '{% data variables.product.prodname_dotcom %} 流是一个基于分支的轻量级工作流程，支持定期部署的团队和项目。'
|
||||
title: Git workflows
|
||||
intro: '{% data variables.product.prodname_dotcom %} flow is a lightweight, branch-based workflow that supports teams and projects that deploy regularly.'
|
||||
redirect_from:
|
||||
- /articles/what-is-a-good-git-workflow/
|
||||
- /articles/what-is-a-good-git-workflow
|
||||
- /articles/git-workflows
|
||||
- /github/using-git/git-workflows
|
||||
- /github/getting-started-with-github/git-workflows
|
||||
@@ -13,5 +13,4 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
|
||||
您可以采用 {% data variables.product.prodname_dotcom %} 流方法标准化 {% data variables.product.prodname_dotcom %} 上团队的运作和协作方式。 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 流程](/github/getting-started-with-github/github-flow)”。
|
||||
You can adopt the {% data variables.product.prodname_dotcom %} flow method to standardize how your team functions and collaborates on {% data variables.product.prodname_dotcom %}. For more information, see "[{% data variables.product.prodname_dotcom %} flow](/github/getting-started-with-github/github-flow)."
|
||||
|
||||
@@ -1,66 +1,66 @@
|
||||
---
|
||||
title: 忽略文件
|
||||
title: Ignoring files
|
||||
redirect_from:
|
||||
- /git-ignore/
|
||||
- /ignore-files/
|
||||
- /git-ignore
|
||||
- /ignore-files
|
||||
- /articles/ignoring-files
|
||||
- /github/using-git/ignoring-files
|
||||
- /github/getting-started-with-github/ignoring-files
|
||||
- /github/getting-started-with-github/getting-started-with-git/ignoring-files
|
||||
intro: '您可以配置 Git 忽略您不想检入 {% data variables.product.product_name %} 的文件。'
|
||||
intro: 'You can configure Git to ignore files you don''t want to check in to {% data variables.product.product_name %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## Configuring ignored files for a single repository
|
||||
|
||||
## 为单个仓库配置忽略的文件
|
||||
You can create a *.gitignore* file in your repository's root directory to tell Git which files and directories to ignore when you make a commit.
|
||||
To share the ignore rules with other users who clone the repository, commit the *.gitignore* file in to your repository.
|
||||
|
||||
您可以在仓库的根目录中创建 *.gitignore* 文件，指示 Git 在您进行提交时要忽略哪些文件和目录。 要与克隆仓库的其他用户共享忽略规则，请提交 *.gitignore* 文件到您的仓库。
|
||||
|
||||
GitHub 在 `github/gitignore` 公共仓库中维护建议用于许多常用操作系统、环境及语言的 *.gitignore* 文件正式列表。 您也可以使用 gitignore.io 创建 *.gitignore* 文件，以用于操作系统、编程语言或 IDE。 更多信息请参阅“[github/gitignore](https://github.com/github/gitignore)”和“[gitignore.io](https://www.gitignore.io/)”网站。
|
||||
GitHub maintains an official list of recommended *.gitignore* files for many popular operating systems, environments, and languages in the `github/gitignore` public repository. You can also use gitignore.io to create a *.gitignore* file for your operating system, programming language, or IDE. For more information, see "[github/gitignore](https://github.com/github/gitignore)" and the "[gitignore.io](https://www.gitignore.io/)" site.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 导航到 Git 仓库的位置。
|
||||
3. 为仓库创建 *.gitignore* 文件。
|
||||
2. Navigate to the location of your Git repository.
|
||||
3. Create a *.gitignore* file for your repository.
|
||||
```shell
|
||||
$ touch .gitignore
|
||||
```
|
||||
|
||||
If the command succeeds, there will be no output.
|
||||
|
||||
For an example *.gitignore* file, see "[Some common .gitignore configurations](https://gist.github.com/octocat/9257657)" in the Octocat repository.
|
||||
|
||||
例如 *.gitignore* 文件，请参阅 Octocat 仓库中的“[一些常见的 .gitignore 配置](https://gist.github.com/octocat/9257657)”。
|
||||
|
||||
如果想要忽略已检入的文件，则必须在添加忽略该文件的规则之前取消跟踪它。 从终端取消跟踪文件。
|
||||
If you want to ignore a file that is already checked in, you must untrack the file before you add a rule to ignore it. From your terminal, untrack the file.
|
||||
|
||||
```shell
|
||||
$ git rm --cached <em>FILENAME</em>
|
||||
```
|
||||
|
||||
## 为计算机上的所有存储库配置忽略的文件
|
||||
## Configuring ignored files for all repositories on your computer
|
||||
|
||||
您也可以创建全局 *.gitignore* 文件，以定义忽略计算机上每个 Git 仓库中文件的规则列表。 例如，在 *~/.gitignore_global* 中创建文件并加入一些规则。
|
||||
You can also create a global *.gitignore* file to define a list of rules for ignoring files in every Git repository on your computer. For example, you might create the file at *~/.gitignore_global* and add some rules to it.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 配置 Git 对所有 Git 仓库使用排除文件 *~/.gitignore_global*。
|
||||
2. Configure Git to use the exclude file *~/.gitignore_global* for all Git repositories.
|
||||
```shell
|
||||
$ git config --global core.excludesfile ~/.gitignore_global
|
||||
```
|
||||
|
||||
## 排除本地文件而不创建 *.gitignore* 文件
|
||||
## Excluding local files without creating a *.gitignore* file
|
||||
|
||||
如果不想创建 *.gitignore* 文件与其他人共享，可以创建不随仓库提交的规则。 您可以对不希望其他用户生成的本地生成文件使用此方法，例如编辑者创建的文件。
|
||||
If you don't want to create a *.gitignore* file to share with others, you can create rules that are not committed with the repository. You can use this technique for locally-generated files that you don't expect other users to generate, such as files created by your editor.
|
||||
|
||||
使用您常用的文本编辑器打开 Git 仓库根目录中的文件 *.git/info/exclude*。 您在此处添加的任何规则都不会检入，并且只会对您的本地仓库忽略文件。
|
||||
Use your favorite text editor to open the file called *.git/info/exclude* within the root of your Git repository. Any rule you add here will not be checked in, and will only ignore files for your local repository.
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 导航到 Git 仓库的位置。
|
||||
3. 使用您常用的文本编辑器打开文件 *.git/info/exclude*。
|
||||
2. Navigate to the location of your Git repository.
|
||||
3. Using your favorite text editor, open the file *.git/info/exclude*.
|
||||
|
||||
## 延伸阅读
|
||||
## Further Reading
|
||||
|
||||
* Pro Git 书籍中的[忽略文件](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring)
|
||||
* Git 手册页面中的 [.gitignore](https://git-scm.com/docs/gitignore)
|
||||
* [github/gitignore 仓库中有用的 *.gitignore* 模板集合](https://github.com/github/gitignore)
|
||||
* [gitignore.io](https://www.gitignore.io/) 网站
|
||||
* [Ignoring files](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring) in the Pro Git book
|
||||
* [.gitignore](https://git-scm.com/docs/gitignore) in the man pages for Git
|
||||
* [A collection of useful *.gitignore* templates](https://github.com/github/gitignore) in the github/gitignore repository
|
||||
* [gitignore.io](https://www.gitignore.io/) site
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
---
|
||||
title: 开始使用 Git
|
||||
intro: '设置 Git（一个分布式版本控制系统）以从计算机管理您的 {% data variables.product.product_name %} 仓库。'
|
||||
title: Getting started with Git
|
||||
intro: 'Set up Git, a distributed version control system, to manage your {% data variables.product.product_name %} repositories from your computer.'
|
||||
redirect_from:
|
||||
- /articles/getting-started-with-git-and-github
|
||||
- /github/using-git/getting-started-with-git-and-github
|
||||
- /github/using-git/learning-about-git
|
||||
- /articles/learning-about-git
|
||||
- /github/getting-started-with-github/getting-started-with-git/
|
||||
- /github/getting-started-with-github/getting-started-with-git
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
---
|
||||
title: 管理远程仓库
|
||||
intro: '了解如何使用计算机上的本地仓库以及 {% data variables.product.product_name %} 上托管的远程仓库。'
|
||||
title: Managing remote repositories
|
||||
intro: 'Learn to work with your local repositories on your computer and remote repositories hosted on {% data variables.product.product_name %}.'
|
||||
redirect_from:
|
||||
- /categories/18/articles/
|
||||
- /remotes/
|
||||
- /categories/managing-remotes/
|
||||
- /categories/18/articles
|
||||
- /remotes
|
||||
- /categories/managing-remotes
|
||||
- /articles/managing-remote-repositories
|
||||
- /articles/adding-a-remote
|
||||
- /github/using-git/adding-a-remote
|
||||
@@ -23,18 +23,17 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: 管理远程仓库
|
||||
shortTitle: Manage remote repositories
|
||||
---
|
||||
## Adding a remote repository
|
||||
|
||||
## 添加远程仓库
|
||||
To add a new remote, use the `git remote add` command on the terminal, in the directory your repository is stored at.
|
||||
|
||||
要新增远程，请在终端上存储仓库的目录中使用 `git remote add` 命令。
|
||||
The `git remote add` command takes two arguments:
|
||||
* A remote name, for example, `origin`
|
||||
* A remote URL, for example, `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
|
||||
`git remote add` 命令使用两个参数：
|
||||
* 远程命令，如 `origin`
|
||||
* 远程 URL，如 `https://{% data variables.command_line.backticks %}/user/repo.git`
|
||||
|
||||
例如：
|
||||
For example:
|
||||
|
||||
```shell
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git
|
||||
@@ -46,60 +45,60 @@ $ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>user</em>/<em>repo</em>.git (push)
|
||||
```
|
||||
|
||||
有关使用哪个 URL 的更多信息，请参阅“[关于远程仓库](/github/getting-started-with-github/about-remote-repositories)”。
|
||||
For more information on which URL to use, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
|
||||
### 故障排除：远程原点已存在
|
||||
### Troubleshooting: Remote origin already exists
|
||||
|
||||
此错误消息表示您尝试添加的远程与本地仓库中的远程名称相同。
|
||||
This error means you've tried to add a remote with a name that already exists in your local repository.
|
||||
|
||||
```shell
|
||||
$ git remote add origin https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife.git
|
||||
> fatal: remote origin already exists.
|
||||
```
|
||||
|
||||
要修复此问题，您可以:
|
||||
* 对新远程使用不同的名称.
|
||||
* 在添加新的远程之前，重命名现有的远程仓库。 更多信息请参阅“[重命名远程仓库](#renaming-a-remote-repository)”。
|
||||
* 在添加新的远程之前，删除现有的远程仓库。 更多信息请参阅下面的“[删除远程仓库](#removing-a-remote-repository)”。
|
||||
To fix this, you can:
|
||||
* Use a different name for the new remote.
|
||||
* Rename the existing remote repository before you add the new remote. For more information, see "[Renaming a remote repository](#renaming-a-remote-repository)" below.
|
||||
* Delete the existing remote repository before you add the new remote. For more information, see "[Removing a remote repository](#removing-a-remote-repository)" below.
|
||||
|
||||
## 更改远程仓库的 URL
|
||||
## Changing a remote repository's URL
|
||||
|
||||
`git remote set-url` 命令可更改现有远程仓库的 URL。
|
||||
The `git remote set-url` command changes an existing remote repository URL.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示：** 有关 HTTPS 与 SSH URL 之间的差异，请参阅“[关于远程仓库](/github/getting-started-with-github/about-remote-repositories)”
|
||||
**Tip:** For information on the difference between HTTPS and SSH URLs, see "[About remote repositories](/github/getting-started-with-github/about-remote-repositories)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
`git remote set-url` 命令使用两个参数：
|
||||
The `git remote set-url` command takes two arguments:
|
||||
|
||||
* 现有远程仓库的名称。 例如，`源仓库`或`上游仓库`是两种常见选择。
|
||||
* 远程仓库的新 URL。 例如：
|
||||
* 如果您要更新为使用 HTTPS，您的 URL 可能如下所示：
|
||||
* An existing remote name. For example, `origin` or `upstream` are two common choices.
|
||||
* A new URL for the remote. For example:
|
||||
* If you're updating to use HTTPS, your URL might look like:
|
||||
```shell
|
||||
https://{% data variables.command_line.backticks %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
* 如果您要更新为使用 SSH，您的 URL 可能如下所示：
|
||||
* If you're updating to use SSH, your URL might look like:
|
||||
```shell
|
||||
git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
|
||||
### 将远程 URL 从 SSH 切换到 HTTPS
|
||||
### Switching remote URLs from SSH to HTTPS
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 将当前工作目录更改为您的本地仓库。
|
||||
3. 列出现有远程仓库以获取要更改的远程仓库的名称。
|
||||
2. Change the current working directory to your local project.
|
||||
3. List your existing remotes in order to get the name of the remote you want to change.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (fetch)
|
||||
> origin git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
4. 使用 `git remote set-url` 命令将远程的 URL 从 SSH 更改为 HTTPS。
|
||||
4. Change your remote's URL from SSH to HTTPS with the `git remote set-url` command.
|
||||
```shell
|
||||
$ git remote set-url origin https://{% data variables.command_line.codeblock %}/<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
5. 验证远程 URL 是否已更改。
|
||||
5. Verify that the remote URL has changed.
|
||||
```shell
|
||||
$ git remote -v
|
||||
# Verify new remote URL
|
||||
@@ -107,25 +106,25 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
下次对远程仓库执行 `git fetch`、`git pull` 或 `git push` 操作时，您需要提供 GitHub 用户名和密码。 {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
The next time you `git fetch`, `git pull`, or `git push` to the remote repository, you'll be asked for your GitHub username and password. {% data reusables.user_settings.password-authentication-deprecation %}
|
||||
|
||||
您可以[使用凭据小助手](/github/getting-started-with-github/caching-your-github-credentials-in-git)让 Git 在每次与 GitHub 会话时记住您的 GitHub 用户名和个人访问令牌。
|
||||
You can [use a credential helper](/github/getting-started-with-github/caching-your-github-credentials-in-git) so Git will remember your GitHub username and personal access token every time it talks to GitHub.
|
||||
|
||||
### 将远程 URL 从 HTTPS 切换到 SSH
|
||||
### Switching remote URLs from HTTPS to SSH
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 将当前工作目录更改为您的本地仓库。
|
||||
3. 列出现有远程仓库以获取要更改的远程仓库的名称。
|
||||
2. Change the current working directory to your local project.
|
||||
3. List your existing remotes in order to get the name of the remote you want to change.
|
||||
```shell
|
||||
$ git remote -v
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
4. 使用 `git remote set-url` 命令将远程的 URL 从 HTTPS 更改为 SSH。
|
||||
4. Change your remote's URL from HTTPS to SSH with the `git remote set-url` command.
|
||||
```shell
|
||||
$ git remote set-url origin git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY</em>.git
|
||||
```
|
||||
5. 验证远程 URL 是否已更改。
|
||||
5. Verify that the remote URL has changed.
|
||||
```shell
|
||||
$ git remote -v
|
||||
# Verify new remote URL
|
||||
@@ -133,105 +132,106 @@ git@{% data variables.command_line.codeblock %}:<em>USERNAME</em>/<em>REPOSITORY
|
||||
> origin git@{% data variables.command_line.codeblock %}:<em>USERNAME/REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
### 故障排除：没有该远程 '[name]'
|
||||
### Troubleshooting: No such remote '[name]'
|
||||
|
||||
此错误表示您尝试更改的远程不存在：
|
||||
This error means that the remote you tried to change doesn't exist:
|
||||
|
||||
```shell
|
||||
$ git remote set-url sofake https://{% data variables.command_line.codeblock %}/octocat/Spoon-Knife
|
||||
> fatal: No such remote 'sofake'
|
||||
```
|
||||
|
||||
检查您是否正确键入了远程仓库的名称。
|
||||
Check that you've correctly typed the remote name.
|
||||
|
||||
## 重命名远程仓库
|
||||
## Renaming a remote repository
|
||||
|
||||
使用 `git remote rename` 命令可重命名现有的远程。
|
||||
Use the `git remote rename` command to rename an existing remote.
|
||||
|
||||
`git remote rename` 命令使用两个参数：
|
||||
* 现有的远程名称，例如 `origin`
|
||||
* 远程的新名称，例如 `destination`
|
||||
The `git remote rename` command takes two arguments:
|
||||
* An existing remote name, for example, `origin`
|
||||
* A new name for the remote, for example, `destination`
|
||||
|
||||
## 示例
|
||||
## Example
|
||||
|
||||
以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 查看现有远程
|
||||
# View existing remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
|
||||
$ git remote rename origin destination
|
||||
# 将远程名称从 'origin' 更改为 'destination'
|
||||
# Change remote name from 'origin' to 'destination'
|
||||
|
||||
$ git remote -v
|
||||
# 验证远程的新名称
|
||||
# Verify remote's new name
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
### 故障排除：无法将配置部分 'remote.[old name]' 重命名为 'remote.[new name]'
|
||||
### Troubleshooting: Could not rename config section 'remote.[old name]' to 'remote.[new name]'
|
||||
|
||||
This error means that the old remote name you typed doesn't exist.
|
||||
|
||||
您可以使用 `git remote -v` 命令检查当前存在哪些远程：
|
||||
You can check which remotes currently exist with the `git remote -v` command:
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 查看现有远程
|
||||
# View existing remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER</em>/<em>REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
### 故障排除：远程 [new name] 已存在
|
||||
### Troubleshooting: Remote [new name] already exists
|
||||
|
||||
此错误表示您要使用的远程名称已经存在。 要解决此问题，使用不同的远程名称，或重命名原始远程。
|
||||
This error means that the remote name you want to use already exists. To solve this, either use a different remote name, or rename the original remote.
|
||||
|
||||
## 删除远程仓库
|
||||
## Removing a remote repository
|
||||
|
||||
使用 `git remote rm` 命令可从仓库中删除远程 URL。
|
||||
Use the `git remote rm` command to remove a remote URL from your repository.
|
||||
|
||||
`git remote rm` 命令使用一个参数：
|
||||
* 远程名称，例如 `destination`
|
||||
The `git remote rm` command takes one argument:
|
||||
* A remote name, for example, `destination`
|
||||
|
||||
## 示例
|
||||
## Example
|
||||
|
||||
以下示例假设您[使用 HTTPS 克隆](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls)，即推荐使用的方法。
|
||||
These examples assume you're [cloning using HTTPS](/github/getting-started-with-github/about-remote-repositories/#cloning-with-https-urls), which is recommended.
|
||||
|
||||
```shell
|
||||
$ git remote -v
|
||||
# 查看当前远程
|
||||
# View current remotes
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (fetch)
|
||||
> destination https://{% data variables.command_line.codeblock %}/<em>FORKER/REPOSITORY</em>.git (push)
|
||||
|
||||
$ git remote rm destination
|
||||
# 删除远程
|
||||
# Remove remote
|
||||
$ git remote -v
|
||||
# 验证其已删除
|
||||
# Verify it's gone
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (fetch)
|
||||
> origin https://{% data variables.command_line.codeblock %}/<em>OWNER/REPOSITORY</em>.git (push)
|
||||
```
|
||||
|
||||
{% warning %}
|
||||
|
||||
**注**：`git remote rm` 不会从服务器中删除远程仓库。 它只是从本地仓库中删除远程及其引用。
|
||||
**Note**: `git remote rm` does not delete the remote repository from the server. It simply
|
||||
removes the remote and its references from your local repository.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
### 故障排除：无法删除配置部分 'remote.[name]'
|
||||
### Troubleshooting: Could not remove config section 'remote.[name]'
|
||||
|
||||
此错误表示您尝试删除的远程不存在：
|
||||
This error means that the remote you tried to delete doesn't exist:
|
||||
|
||||
```shell
|
||||
$ git remote rm sofake
|
||||
> error: Could not remove config section 'remote.sofake'
|
||||
```
|
||||
|
||||
检查您是否正确键入了远程仓库的名称。
|
||||
Check that you've correctly typed the remote name.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- _Pro Git_ 书籍中的“[使用远程”](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
|
||||
- "[Working with Remotes" from the _Pro Git_ book](https://git-scm.com/book/en/Git-Basics-Working-with-Remotes)
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
---
|
||||
title: GitHub 上的访问权限
|
||||
title: Access permissions on GitHub
|
||||
redirect_from:
|
||||
- /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do/
|
||||
- /articles/what-are-the-different-types-of-team-permissions/
|
||||
- /articles/what-are-the-different-access-permissions/
|
||||
- /articles/needs-to-be-written-what-can-the-different-types-of-org-team-permissions-do
|
||||
- /articles/what-are-the-different-types-of-team-permissions
|
||||
- /articles/what-are-the-different-access-permissions
|
||||
- /articles/access-permissions-on-github
|
||||
- /github/getting-started-with-github/access-permissions-on-github
|
||||
- /github/getting-started-with-github/learning-about-github/access-permissions-on-github
|
||||
intro: 您可以授权协作者对个人仓库的读取/写入权限，但组织成员对组织的仓库可有更细致的访问权限。
|
||||
intro: 'While you can grant read/write access to collaborators on a personal repository, members of an organization can have more granular access permissions for the organization''s repositories.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
@@ -16,26 +16,25 @@ versions:
|
||||
topics:
|
||||
- Permissions
|
||||
- Accounts
|
||||
shortTitle: 访问权限
|
||||
shortTitle: Access permissions
|
||||
---
|
||||
## Personal user accounts
|
||||
|
||||
## 个人用户帐户
|
||||
A repository owned by a user account has two permission levels: the *repository owner* and *collaborators*. For more information, see "[Permission levels for a user account repository](/articles/permission-levels-for-a-user-account-repository)."
|
||||
|
||||
用户帐户拥有的仓库有两种权限级别：*仓库所有者*和*协作者*。 更多信息请参阅“[用户帐户仓库的权限级别](/articles/permission-levels-for-a-user-account-repository)”。
|
||||
## Organization accounts
|
||||
|
||||
## 组织帐户
|
||||
|
||||
组织成员可以是*所有者*{% ifversion fpt or ghec %}、*帐单管理员*{% endif %}或*成员*角色。 所有者对组织具有完全管理权限{% ifversion fpt or ghec %}，而帐单管理员负责管理帐单设置{% endif %}。 成员是其他每个人的默认角色。 您可以通过团队一次管理多个成员的访问权限。 更多信息请参阅：
|
||||
Organization members can have *owner*{% ifversion fpt or ghec %}, *billing manager*,{% endif %} or *member* roles. Owners have complete administrative access to your organization{% ifversion fpt or ghec %}, while billing managers can manage billing settings{% endif %}. Member is the default role for everyone else. You can manage access permissions for multiple members at a time with teams. For more information, see:
|
||||
- "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)"
|
||||
- "[组织的项目板权限](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[Project board permissions for an organization](/articles/project-board-permissions-for-an-organization)"
|
||||
- "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)"
|
||||
- "[关于团队](/articles/about-teams)"
|
||||
- "[About teams](/articles/about-teams)"
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 企业帐户
|
||||
## Enterprise accounts
|
||||
|
||||
*企业所有者*对企业帐户拥有最终权力，可在企业帐户中执行任何操作。 *帐单管理员*可以管理企业帐户的帐单设置。 企业帐户拥有的组织的成员和外部协作者自动成为企业帐户的成员，但他们对企业帐户本身或其设置没有访问权限。 更多信息请参阅“[企业中的角色](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
|
||||
*Enterprise owners* have ultimate power over the enterprise account and can take every action in the enterprise account. *Billing managers* can manage your enterprise account's billing settings. Members and outside collaborators of organizations owned by your enterprise account are automatically members of the enterprise account, although they have no access to the enterprise account itself or its settings. For more information, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
|
||||
If an enterprise uses {% data variables.product.prodname_emus %}, members are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and are fully managed by the identity provider. The {% data variables.product.prodname_managed_users %} have read-only access to repositories that are not a part of their enterprise and cannot interact with users that are not also members of the enterprise. Within the organizations owned by the enterprise, the {% data variables.product.prodname_managed_users %} can be granted the same granular access levels available for regular organizations. For more information, see "[About {% data variables.product.prodname_emus %}]({% ifversion fpt %}/enterprise-cloud@latest{% endif %}/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation{% else %}."{% endif %}
|
||||
|
||||
@@ -43,6 +42,6 @@ If an enterprise uses {% data variables.product.prodname_emus %}, members are pr
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[{% data variables.product.prodname_dotcom %} 帐户的类型](/articles/types-of-github-accounts)"
|
||||
- "[Types of {% data variables.product.prodname_dotcom %} accounts](/articles/types-of-github-accounts)"
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 了解 GitHub
|
||||
intro: '了解如何使用 {% data variables.product.company_short %} 产品来改进您的软件管理流程并与其他人合作。'
|
||||
title: Learning about GitHub
|
||||
intro: 'Learn how you can use {% data variables.product.company_short %} products to improve your software management process and collaborate with other people.'
|
||||
redirect_from:
|
||||
- /articles/learning-about-github
|
||||
- /github/getting-started-with-github/learning-about-github/
|
||||
- /github/getting-started-with-github/learning-about-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: GitHub 帐户的类型
|
||||
intro: '您的用户帐户是您在 {% data variables.product.product_location %} 中的身份。 Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}'
|
||||
title: Types of GitHub accounts
|
||||
intro: 'Your user account is your identity on {% data variables.product.product_location %}. Your user account can be a member of any number of organizations.{% ifversion fpt or ghec %} Organizations can belong to enterprise accounts.{% endif %}'
|
||||
redirect_from:
|
||||
- /manage-multiple-clients/
|
||||
- /managing-clients/
|
||||
- /articles/what-s-the-difference-between-user-and-organization-accounts/
|
||||
- /articles/differences-between-user-and-organization-accounts/
|
||||
- /manage-multiple-clients
|
||||
- /managing-clients
|
||||
- /articles/what-s-the-difference-between-user-and-organization-accounts
|
||||
- /articles/differences-between-user-and-organization-accounts
|
||||
- /articles/types-of-github-accounts
|
||||
- /github/getting-started-with-github/types-of-github-accounts
|
||||
- /github/getting-started-with-github/learning-about-github/types-of-github-accounts
|
||||
@@ -21,26 +21,25 @@ topics:
|
||||
- Desktop
|
||||
- Security
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
有关各 {% data variables.product.product_name %} 产品功能的完整列表，请参阅“[{% data variables.product.prodname_dotcom %} 的产品](/github/getting-started-with-github/githubs-products)”。
|
||||
For a full list of features for each {% data variables.product.product_name %} product, see "[{% data variables.product.prodname_dotcom %}'s products](/github/getting-started-with-github/githubs-products)."
|
||||
{% endif %}
|
||||
|
||||
## 个人用户帐户
|
||||
## Personal user accounts
|
||||
|
||||
使用 {% data variables.product.product_location %} 的每个人都有其自己的用户帐户，其中包括：
|
||||
Every person who uses {% data variables.product.product_location %} has their own user account, which includes:
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
- 使用 {% data variables.product.prodname_free_user %} 的无限公共和私有仓库
|
||||
- 使用 {% data variables.product.prodname_free_user %} 的无限协作者
|
||||
- 使用 {% data variables.product.prodname_pro %} 的私有仓库的其他功能
|
||||
- [邀请仓库协作者](/articles/inviting-collaborators-to-a-personal-repository)的功能
|
||||
- Unlimited public and private repositories with {% data variables.product.prodname_free_user %}
|
||||
- Unlimited collaborators with {% data variables.product.prodname_free_user %}
|
||||
- Additional features for private repositories with {% data variables.product.prodname_pro %}
|
||||
- Ability to [invite repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
|
||||
|
||||
{% else %}
|
||||
|
||||
- 无限仓库和[协作者](/articles/permission-levels-for-a-user-account-repository)
|
||||
- [添加无限仓库协作者](/articles/inviting-collaborators-to-a-personal-repository)的功能
|
||||
- Unlimited repositories and [collaborators](/articles/permission-levels-for-a-user-account-repository)
|
||||
- Ability to [add unlimited repository collaborators](/articles/inviting-collaborators-to-a-personal-repository)
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -48,10 +47,10 @@ topics:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：
|
||||
**Tips**:
|
||||
|
||||
- 您可以将一个帐户用于多种用途，例如个人用途和业务用途。 我们不建议创建多个帐户。 更多信息请参阅“[合并多个用户帐户](/articles/merging-multiple-user-accounts)”。
|
||||
- 用户帐户适用于人类，但必要时可将其提供给机器人，例如持续集成自动程序。
|
||||
- You can use one account for multiple purposes, such as for personal use and business use. We do not recommend creating more than one account. For more information, see "[Merging multiple user accounts](/articles/merging-multiple-user-accounts)."
|
||||
- User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -59,7 +58,7 @@ topics:
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：用户帐户适用于人类，但必要时可将其提供给机器人，例如持续集成自动程序。
|
||||
**Tip**: User accounts are intended for humans, but you can give one to a robot, such as a continuous integration bot, if necessary.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
@@ -73,22 +72,22 @@ With {% data variables.product.prodname_emus %}, instead of using your personal
|
||||
{% data variables.product.prodname_managed_users_caps %} can only interact with users, repositories, and organizations that are part of their enterprise. {% data variables.product.prodname_managed_users_caps %} have read-only access to the rest of {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users){% ifversion fpt %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
{% endif %}
|
||||
|
||||
## 组织帐户
|
||||
## Organization accounts
|
||||
|
||||
组织是共享帐户，供多个项目的人员同时协作之用。 所有者和管理员可通过复杂的安全和管理功能管理成员对组织数据和项目的访问。
|
||||
Organizations are shared accounts where groups of people can collaborate across many projects at once. Owners and administrators can manage member access to the organization's data and projects with sophisticated security and administrative features.
|
||||
|
||||
{% data reusables.organizations.organizations_include %}
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
## 企业帐户
|
||||
## Enterprise accounts
|
||||
|
||||
通过企业帐户，您可以集中管理多个 {% data variables.product.prodname_dotcom_the_website %} 组织的策略和帐单。 {% data reusables.gated-features.enterprise-accounts %}
|
||||
With enterprise accounts, you can centrally manage policy and billing for multiple {% data variables.product.prodname_dotcom_the_website %} organizations. {% data reusables.gated-features.enterprise-accounts %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
{% ifversion fpt or ghec %}- "[Signing up for a new {% data variables.product.prodname_dotcom %} account](/articles/signing-up-for-a-new-github-account)"
|
||||
- “[{% data variables.product.prodname_dotcom %} 的产品](/articles/githubs-products)”{% endif %}
|
||||
- “[创建新组织帐户](/articles/creating-a-new-organization-account)”
|
||||
- "[{% data variables.product.prodname_dotcom %}'s products](/articles/githubs-products)"{% endif %}
|
||||
- "[Creating a new organization account](/articles/creating-a-new-organization-account)"
|
||||
|
||||
@@ -40,16 +40,16 @@ Once you choose the account type you would like, you can proceed to setting up y
|
||||
To get started with {% data variables.product.prodname_ghe_cloud %}, you will want to create your organization or enterprise account and set up and view billing settings, subscriptions and usage.
|
||||
### Setting up a single organization account with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
#### 1. 关于组织
|
||||
组织是共享帐户，供多个项目的人员同时协作之用。 With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. 更多信息请参阅“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。
|
||||
#### 1. About organizations
|
||||
Organizations are shared accounts where groups of people can collaborate across many projects at once. With {% data variables.product.prodname_ghe_cloud %}, owners and administrators can manage their organization with sophisticated user authentication and management, as well as escalated support and security options. For more information, see "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)."
|
||||
#### 2. Creating or upgrading an organization account
|
||||
|
||||
To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". 更多信息请参阅“[从头开始创建新组织](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)”。
|
||||
To use an organization account with {% data variables.product.prodname_ghe_cloud %}, you will first need to create an organization. When prompted to choose a plan, select "Enterprise". For more information, see "[Creating a new organization from scratch](/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch)."
|
||||
|
||||
Alternatively, if you have an existing organization account that you would like to upgrade, follow the steps in "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription#upgrading-your-organizations-subscription)."
|
||||
#### 3. Setting up and managing billing
|
||||
|
||||
When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [14-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
When you choose to use an organization account with {% data variables.product.prodname_ghe_cloud %}, you'll first have access to a [30-day trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud). If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_user %} and lose access to any advanced tooling and features that are only included with paid products. For more information, see "[Finishing your trial](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud#finishing-your-trial)."
|
||||
|
||||
Your organization's billing settings page allows you to manage settings like your payment method and billing cycle, view information about your subscription, and upgrade your storage and {% data variables.product.prodname_actions %} minutes. For more information on managing your billing settings, see "[Managing your {% data variables.product.prodname_dotcom %} billing settings](/billing/managing-your-github-billing-settings)."
|
||||
|
||||
@@ -62,21 +62,21 @@ To get an enterprise account created for you, contact [{% data variables.product
|
||||
|
||||
{% endnote %}
|
||||
|
||||
#### 1. 关于企业帐户
|
||||
#### 1. About enterprise accounts
|
||||
|
||||
An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. 更多信息请参阅“[关于企业帐户](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)”。
|
||||
#### 2. 将组织添加到企业帐户
|
||||
An enterprise account allows you to centrally manage policy and settings for multiple {% data variables.product.prodname_dotcom %} organizations, including member access, billing and usage and security. For more information, see "[About enterprise accounts](/enterprise-cloud@latest/admin/overview/about-enterprise-accounts)."
|
||||
#### 2. Adding organizations to your enterprise account
|
||||
|
||||
您可以在企业帐户中创建要管理的新组织。 For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
|
||||
You can create new organizations to manage within your enterprise account. For more information, see "[Adding organizations to your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise)."
|
||||
|
||||
Contact your {% data variables.product.prodname_dotcom %} sales account representative if you want to transfer an existing organization to your enterprise account.
|
||||
#### 3. 查看企业帐户的订阅和使用情况
|
||||
#### 3. Viewing the subscription and usage for your enterprise account
|
||||
You can view your current subscription, license usage, invoices, payment history, and other billing information for your enterprise account at any time. Both enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Viewing the subscription and usage for your enterprise account](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
|
||||
## Part 3: Managing your organization or enterprise members and teams with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
### Managing members and teams in your organization
|
||||
You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
|
||||
You can set permissions and member roles, create and manage teams, and give people access to repositories in your organization.
|
||||
#### 1. Managing members of your organization
|
||||
{% data reusables.getting-started.managing-org-members %}
|
||||
#### 2. Organization permissions and roles
|
||||
@@ -91,18 +91,18 @@ You can set permissions and member roles, create and manage teams, and give peop
|
||||
### Managing members of an enterprise account
|
||||
Managing members of an enterprise is separate from managing members or teams in an organization. It is important to note that enterprise owners or administrators cannot access organization-level settings or manage members for organizations in their enterprise unless they are made an organization owner. For more information, see the above section, "[Managing members and teams in your organization](#managing-members-and-teams-in-your-organization)."
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)”。
|
||||
If your enterprise uses {% data variables.product.prodname_emus %}, your members are fully managed through your identity provider. Adding members, making changes to their membership, and assigning roles is all managed using your IdP. For more information, see "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/authentication/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users)."
|
||||
|
||||
If your enterprise does not use {% data variables.product.prodname_emus %}, follow the steps below.
|
||||
|
||||
#### 1. Assigning roles in an enterprise
|
||||
By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. 更多信息请参阅“[企业中的角色](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)”。
|
||||
#### 2. 邀请人员管理企业
|
||||
By default, everyone in an enterprise is a member of the enterprise. There are also administrative roles, including enterprise owner and billing manager, that have different levels of access to enterprise settings and data. For more information, see "[Roles in an enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)."
|
||||
#### 2. Inviting people to manage your enterprise
|
||||
You can invite people to manage your enterprise as enterprise owners or billing managers, as well as remove those who no longer need access. For more information, see "[Inviting people to manage your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise)."
|
||||
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. 更多信息请参阅“[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
|
||||
#### 3. 查看企业中的人员
|
||||
To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. 更多信息请参阅“[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)”。
|
||||
You can also grant enterprise members the ability to manage support tickets in the support portal. For more information, see "[Managing support entitlements for your enterprise](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)."
|
||||
#### 3. Viewing people in your enterprise
|
||||
To audit access to enterprise-owned resources or user license usage, you can view every enterprise administrator, enterprise member, and outside collaborator in your enterprise. You can see the organizations that a member belongs to and the specific repositories that an outside collaborator has access to. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise)."
|
||||
|
||||
## Part 4: Managing security with {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
@@ -124,12 +124,12 @@ You can help keep your organization secure by requiring two-factor authenticatio
|
||||
If you manage your applications and the identities of your organization members with an identity provider (IdP), you can configure SAML single-sign-on (SSO) to control and secure access to organization resources like repositories, issues and pull requests. When members of your organization access organization resources that use SAML SSO, {% data variables.product.prodname_dotcom %} will redirect them to your IdP to authenticate. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)."
|
||||
|
||||
Organization owners can choose to disable, enable but not enforce, or enable and enforce SAML SSO. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)" and "[Enforcing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enforcing-saml-single-sign-on-for-your-organization)."
|
||||
#### 5. 管理组织的团队同步
|
||||
Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. 更多信息请参阅“[管理组织的团队同步](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)”。
|
||||
#### 5. Managing team synchronization for your organization
|
||||
Organization owners can enable team synchronization between your identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organization owners and team maintainers to connect teams in your organization with IdP groups. For more information, see "[Managing team synchronization for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/managing-team-synchronization-for-your-organization)."
|
||||
|
||||
### Managing security for an {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
|
||||
With {% data variables.product.prodname_emus %}, access and identity is managed centrally through your identity provider. Two-factor authentication and other login requirements should be enabled and enforced on your IdP.
|
||||
|
||||
#### 1. Enabling and SAML single sign-on and provisioning in your {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
@@ -141,23 +141,23 @@ You can connect teams in your organizations to security groups in your identity
|
||||
|
||||
#### 3. Managing allowed IP addresses for organizations in your {% data variables.product.prodname_emu_enterprise %}
|
||||
|
||||
You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. 更多信息请参阅“[在企业中实施安全设置策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)”。
|
||||
You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your {% data variables.product.prodname_emu_enterprise %}. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)."
|
||||
|
||||
#### 4. Enforcing policies for Advanced Security features in your {% data variables.product.prodname_emu_enterprise %}
|
||||
{% data reusables.getting-started.enterprise-advanced-security %}
|
||||
|
||||
### Managing security for an enterprise account without {% data variables.product.prodname_managed_users %}
|
||||
To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
|
||||
To manage security for your enterprise, you can require two-factor authentication, manage allowed IP addresses, enable SAML single sign-on and team synchronization at an enterprise level, and sign up for and enforce GitHub Advanced Security features.
|
||||
|
||||
#### 1. Requiring two-factor authentication and managing allowed IP addresses for organizations in your enterprise account
|
||||
企业所有者可以要求企业帐户拥有的所有组织中的组织成员、帐单管理员和外部协作者使用双重身份验证来保护其个人帐户。 Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
|
||||
Enterprise owners can require that organization members, billing managers, and outside collaborators in all organizations owned by an enterprise account use two-factor authentication to secure their personal accounts. Before doing so, we recommend notifying all who have access to organizations in your enterprise. You can also configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account.
|
||||
|
||||
For more information on enforcing two-factor authentication and allowed IP address lists, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise)."
|
||||
#### 2. Enabling and enforcing SAML single sign-on for organizations in your enterprise account
|
||||
You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. 更多信息请参阅“[关于企业的身份和访问权限管理](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。
|
||||
You can centrally manage access to your enterprise's resources, organization membership and team membership using your IdP and SAM single sign-on (SSO). Enterprise owners can enable SAML SSO across all organizations owned by an enterprise account. For more information, see "[About identity and access management for your enterprise](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
|
||||
|
||||
#### 3. Managing team synchronization
|
||||
You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. 更多信息请参阅“[管理企业帐户中组织的团队同步](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。
|
||||
You can enable and manage team synchronization between an identity provider (IdP) and {% data variables.product.prodname_dotcom %} to allow organizations owned by your enterprise account to manage team membership with IdP groups. For more information, see "[Managing team synchronization for organizations in your enterprise account](/enterprise-cloud@latest/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)."
|
||||
|
||||
#### 4. Enforcing policies for Advanced Security features in your enterprise account
|
||||
{% data reusables.getting-started.enterprise-advanced-security %}
|
||||
@@ -177,11 +177,11 @@ To manage and moderate your organization, you can set organization policies, man
|
||||
To manage and moderate your enterprise, you can set policies for organizations within the enterprise, view audit logs, configure webhooks, and restrict email notifications.
|
||||
#### 1. Managing policies for organizations in your enterprise account
|
||||
|
||||
You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. 更多信息请参阅“[为您的企业设置策略](/enterprise-cloud@latest/admin/policies)”。
|
||||
You can choose to enforce a number of policies for all organizations owned by your enterprise, or choose to allow these policies to be set in each organization. Types of policies you can enforce include repository management, project board, and team policies. For more information, see "[Setting policies for your enterprise](/enterprise-cloud@latest/admin/policies)."
|
||||
#### 2. Viewing audit logs, configuring webhooks, and restricting email notifications for your enterprise
|
||||
You can view actions from all of the organizations owned by your enterprise account in the enterprise audit log. You can also configure webhooks to receive events from organizations owned by your enterprise account. For more information, see "[Viewing the audit logs for organizations in your enterprise](/enterprise-cloud@latest/admin/user-management/managing-organizations-in-your-enterprise/viewing-the-audit-logs-for-organizations-in-your-enterprise)" and "[Managing global webhooks](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-global-webhooks)."
|
||||
|
||||
You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. 更多信息请参阅“[限制企业的电子邮件通知](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)”。
|
||||
You can also restrict email notifications for your enterprise account so that enterprise members can only use an email address in a verified or approved domain to receive notifications. For more information, see "[Restricting email notifications for your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
|
||||
|
||||
## Part 6: Customizing and automating your organization or enterprise's work on {% data variables.product.prodname_dotcom %}
|
||||
Members of your organization or enterprise can use tools from the {% data variables.product.prodname_marketplace %}, the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, and existing {% data variables.product.product_name %} features to customize and automate your work.
|
||||
@@ -192,13 +192,13 @@ Members of your organization or enterprise can use tools from the {% data variab
|
||||
{% data reusables.getting-started.api %}
|
||||
### 3. Building {% data variables.product.prodname_actions %}
|
||||
{% data reusables.getting-started.actions %}
|
||||
### 4. Publishing and managing {% data variables.product.prodname_registry %}
|
||||
### 4. Publishing and managing {% data variables.product.prodname_registry %}
|
||||
{% data reusables.getting-started.packages %}
|
||||
### 5. Using {% data variables.product.prodname_pages %}
|
||||
{% data variables.product.prodname_pages %} is a static site hosting service that takes HTML, CSS, and JavaScript files straight from a repository and publishes a website. You can manage the publication of {% data variables.product.prodname_pages %} sites at the organization level. For more information, see "[Managing the publication of {% data variables.product.prodname_pages %} sites for your organization](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" and "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages)."
|
||||
## Part 7: Participating in {% data variables.product.prodname_dotcom %}'s community
|
||||
|
||||
Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
|
||||
Members of your organization or enterprise can use GitHub's learning and support resources to get the help they need. You can also support the open source community.
|
||||
### 1. Learning with {% data variables.product.prodname_learning %}
|
||||
Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot.
|
||||
|
||||
@@ -206,7 +206,7 @@ For more information, see "[Git and {% data variables.product.prodname_dotcom %}
|
||||
### 2. Supporting the open source community
|
||||
{% data reusables.getting-started.sponsors %}
|
||||
|
||||
### 3. 联系 {% data variables.contact.github_support %}
|
||||
### 3. Contacting {% data variables.contact.github_support %}
|
||||
{% data reusables.getting-started.contact-support %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. 更多信息请参阅“[{% data variables.product.prodname_ghe_cloud %} 支持](/github/working-with-github-support/github-enterprise-cloud-support)”。
|
||||
{% data variables.product.prodname_ghe_cloud %} allows you to submit priority support requests with a target eight-hour response time. For more information, see "[{% data variables.product.prodname_ghe_cloud %} support](/github/working-with-github-support/github-enterprise-cloud-support)."
|
||||
|
||||
@@ -1,11 +1,11 @@
|
||||
---
|
||||
title: 社交化
|
||||
title: Be social
|
||||
redirect_from:
|
||||
- /be-social/
|
||||
- /be-social
|
||||
- /articles/be-social
|
||||
- /github/getting-started-with-github/be-social
|
||||
- /github/getting-started-with-github/quickstart/be-social
|
||||
intro: '您可以在 {% data variables.product.prodname_dotcom %} 上与人员、仓库及组织进行互动。 从您的个人仪表板查看其他人正在做什么，在跟谁联系。'
|
||||
intro: 'You can interact with people, repositories, and organizations on {% data variables.product.prodname_dotcom %}. See what others are working on and who they''re connecting with from your personal dashboard.'
|
||||
permissions: '{% data reusables.enterprise-accounts.emu-permission-interact %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -19,63 +19,63 @@ topics:
|
||||
- Notifications
|
||||
- Accounts
|
||||
---
|
||||
To learn about accessing your personal dashboard, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
要了解有关访问个人仪表板的信息，请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
|
||||
## Following people
|
||||
|
||||
## 关注他人
|
||||
When you follow someone on {% data variables.product.prodname_dotcom %}, you'll get notifications on your personal dashboard about their activity. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard)."
|
||||
|
||||
在 {% data variables.product.prodname_dotcom %} 上关注某人后，您将会在您的个人仪表板中收到有关其活动的通知。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”。
|
||||
Click **Follow** on a person's profile page to follow them.
|
||||
|
||||
在某人的个人资料页面上单击 **Follow（关注）**可关注他们。
|
||||
|
||||
|
||||
|
||||
## Watching a repository
|
||||
|
||||
## 关注仓库
|
||||
You can watch a repository to receive notifications for new pull requests and issues. When the owner updates the repository, you'll see the changes in your personal dashboard. For more information see {% ifversion fpt or ghae or ghes or ghec %}"[Viewing your subscriptions](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}"[Watching and unwatching repositories](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}."
|
||||
|
||||
您可以关注仓库以接收有关新拉取请求和议题的通知。 当所有者更新仓库时，您将在个人仪表板中看到其更改。 更多信息请参阅{% ifversion fpt or ghae or ghes or ghec %}“[查看您的订阅](/github/managing-subscriptions-and-notifications-on-github/viewing-your-subscriptions){% else %}”[关注和取消关注仓库](/github/receiving-notifications-about-activity-on-github/watching-and-unwatching-repositories){% endif %}”。
|
||||
Click **Watch** at the top of a repository to watch it.
|
||||
|
||||
在仓库顶部单击 **Watch（关注）**可关注它。
|
||||
|
||||
|
||||
|
||||
|
||||
## 加入对话
|
||||
## Joining the conversation
|
||||
|
||||
{% data reusables.support.ask-and-answer-forum %}
|
||||
|
||||
## {% data variables.product.product_name %} 上的通信
|
||||
## Communicating on {% data variables.product.product_name %}
|
||||
|
||||
{% data variables.product.product_name %} 提供内置的协作通信工具，如议题和拉取请求，使您在构建出色的软件时能够与社区进行密切互动。 有关这些工具的概述以及每个工具的特异性，请参阅“[{% data variables.product.prodname_dotcom %} 通信快速入门](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)”。
|
||||
{% data variables.product.product_name %} provides built-in collaborative communication tools, such as issues and pull requests, allowing you to interact closely with your community when building great software. For an overview of these tools, and information about the specificity of each, see "[Quickstart for communicating on {% data variables.product.prodname_dotcom %}](/github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github)."
|
||||
|
||||
## 更多功能
|
||||
## Doing even more
|
||||
|
||||
### 创建拉取请求
|
||||
### Creating pull requests
|
||||
|
||||
您可能希望为其他人的项目做出贡献，例如添加功能或修复漏洞。 做出更改后，通过发送拉取请求让原作者知道。 更多信息请参阅“[关于拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)”。
|
||||
You may want to contribute to another person's project, whether to add features or to fix bugs. After making changes, let the original author know by sending a pull request. For more information, see "[About pull requests](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)."
|
||||
|
||||
|
||||
|
||||
|
||||
### 使用议题
|
||||
### Using issues
|
||||
|
||||
在仓库上进行协作时，可使用议题来跟踪想法、增强功能、任务或漏洞。 更多信息请参阅“[关于议题](/articles/about-issues/)”。
|
||||
When collaborating on a repository, use issues to track ideas, enhancements, tasks, or bugs. For more information, see '[About issues](/articles/about-issues/)."
|
||||
|
||||
|
||||
|
||||
|
||||
### 参与组织
|
||||
### Participating in organizations
|
||||
|
||||
组织是共享帐户，其中业务和开源项目可一次协助处理多个项目。 所有者和管理员可建立具有特殊权限的团队、拥有公共组织资料以及跟踪组织内的活动。 更多信息请参阅“[关于组织](/articles/about-organizations/)”。
|
||||
Organizations are shared accounts where businesses and open-source projects can collaborate across many projects at once. Owners and administrators can establish teams with special permissions, have a public organization profile, and keep track of activity within the organization. For more information, see "[About organizations](/articles/about-organizations/)."
|
||||
|
||||
|
||||
|
||||
|
||||
### 在 {% data variables.product.prodname_dotcom %} 上探索其他项目
|
||||
### Exploring other projects on {% data variables.product.prodname_dotcom %}
|
||||
|
||||
使用 {% data variables.explore.explore_github %}、[探索仓库](https://github.com/explore)以及 {% data variables.explore.trending_page %} 来发现感兴趣的项目。 用星号标记感兴趣的项目，以便今后访问。 访问您的 {% data variables.explore.your_stars_page %} 可查看所有加星标的项目。 更多信息请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard/)”。
|
||||
Discover interesting projects using {% data variables.explore.explore_github %}, [Explore repositories](https://github.com/explore), and the {% data variables.explore.trending_page %}. Star interesting projects and come back to them later. Visit your {% data variables.explore.your_stars_page %} to see all your starred projects. For more information, see "[About your personal dashboard](/articles/about-your-personal-dashboard/)."
|
||||
|
||||
## 祝贺
|
||||
## Celebrate
|
||||
|
||||
您现在已连接到 {% data variables.product.product_name %} 社区。 接下来您要做什么？ 
|
||||
You're now connected to the {% data variables.product.product_name %} community. What do you want to do next?
|
||||
|
||||
|
||||
|
||||
- 要将您的 {% data variables.product.product_name %} 项目与计算机同步，您可以设置 Git。 更多信息请参阅“[设置 Git](/articles/set-up-git)”。
|
||||
- 您也可以创建仓库，以放置所有项目和维护工作流程。 更多信息请参阅“[创建仓库](/articles/create-a-repo)”。
|
||||
- 您可以复刻仓库以进行您想要看到的更改，而不影响原始仓库。 更多信息请参阅“[复刻仓库](/articles/fork-a-repo)”。
|
||||
- To synchronize your {% data variables.product.product_name %} projects with your computer, you can set up Git. For more information see "[Set up Git](/articles/set-up-git)."
|
||||
- You can also create a repository, where you can put all your projects and maintain your workflows. For more information see, "[Create a repository](/articles/create-a-repo)."
|
||||
- You can fork a repository to make changes you want to see without affecting the original repository. For more information, see "[Fork a repository](/articles/fork-a-repo)."
|
||||
- {% data reusables.support.connect-in-the-forum-bootcamp %}
|
||||
|
||||
@@ -4,7 +4,7 @@ intro: 'You can discuss specific projects and changes, as well as broader ideas
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/getting-started/quickstart-for-communicating-on-github
|
||||
- /articles/about-discussions-in-issues-and-pull-requests/
|
||||
- /articles/about-discussions-in-issues-and-pull-requests
|
||||
- /github/collaborating-with-issues-and-pull-requests/about-conversations-on-github
|
||||
- /github/collaborating-with-issues-and-pull-requests/quickstart-for-communicating-on-github
|
||||
- /github/getting-started-with-github/quickstart/communicating-on-github
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: Git and GitHub learning resources
|
||||
redirect_from:
|
||||
- /articles/good-resources-for-learning-git-and-github/
|
||||
- /articles/what-are-other-good-resources-for-learning-git-and-github/
|
||||
- /articles/good-resources-for-learning-git-and-github
|
||||
- /articles/what-are-other-good-resources-for-learning-git-and-github
|
||||
- /articles/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/git-and-github-learning-resources
|
||||
- /github/getting-started-with-github/quickstart/git-and-github-learning-resources
|
||||
|
||||
@@ -2,8 +2,8 @@
|
||||
title: GitHub flow
|
||||
intro: 'Follow {% data variables.product.prodname_dotcom %} flow to collaborate on projects.'
|
||||
redirect_from:
|
||||
- /articles/creating-and-editing-files-in-your-repository/
|
||||
- /articles/github-flow-in-the-browser/
|
||||
- /articles/creating-and-editing-files-in-your-repository
|
||||
- /articles/github-flow-in-the-browser
|
||||
- /articles/github-flow
|
||||
- /github/collaborating-with-issues-and-pull-requests/github-flow
|
||||
- /github/getting-started-with-github/github-flow
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Signing up for GitHub
|
||||
intro: 'Start using {% data variables.product.prodname_dotcom %} for yourself or your team.'
|
||||
redirect_from:
|
||||
- /articles/signing-up-for-github
|
||||
- /github/getting-started-with-github/signing-up-for-github/
|
||||
- /github/getting-started-with-github/signing-up-for-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 设置 GitHub Enterprise Cloud 试用版
|
||||
intro: '您可以免费试用 {% data variables.product.prodname_ghe_cloud %}。'
|
||||
title: Setting up a trial of GitHub Enterprise Cloud
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_cloud %} for free.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-cloud
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-cloud
|
||||
@@ -11,55 +11,58 @@ versions:
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Cloud 试用版
|
||||
shortTitle: Enterprise Cloud trial
|
||||
---
|
||||
|
||||
{% data reusables.enterprise.ghec-cta-button %}
|
||||
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_cloud %}
|
||||
## About {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
{% data reusables.organizations.about-organizations %}
|
||||
|
||||
You can use organizations for free with {% data variables.product.prodname_free_team %}, which includes limited features. For additional features, such as SAML single sign-on (SSO), access control for {% data variables.product.prodname_pages %}, and included {% data variables.product.prodname_actions %} minutes, you can upgrade to {% data variables.product.prodname_ghe_cloud %}. For a detailed list of the features available with {% data variables.product.prodname_ghe_cloud %}, see our [Pricing](https://github.com/pricing) page.
|
||||
|
||||
{% data reusables.saml.saml-accounts %}更多信息请参阅“<a href="/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on" class="dotcom-only">关于使用 SAML 单点登录管理身份和访问</a>”。
|
||||
{% data reusables.saml.saml-accounts %} For more information, see "<a href="/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on" class="dotcom-only">About identity and access management with SAML single sign-on</a>."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_cloud %} 试用版
|
||||
## About trials of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
You can set up a 14-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. 在试用期间无需提供付款方式，除非您将 {% data variables.product.prodname_marketplace %} 应用程序添加到需要付款方式的组织。 更多信息请参阅“<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">关于 {% data variables.product.prodname_marketplace %} 的计费</a>”。
|
||||
You can set up a 30-day trial to evaluate {% data variables.product.prodname_ghe_cloud %}. You do not need to provide a payment method during the trial unless you add {% data variables.product.prodname_marketplace %} apps to your organization that require a payment method. For more information, see "<a href="/articles/about-billing-for-github-marketplace/" class="dotcom-only">About billing for {% data variables.product.prodname_marketplace %}</a>."
|
||||
|
||||
试用版包括 50 个席位。 如果需要更多席位来评估 {% data variables.product.prodname_ghe_cloud %}，请联系 {% data variables.contact.contact_enterprise_sales %}。 在试用结束时，您可以选择不同数量的席位。
|
||||
Your trial includes 50 seats. If you need more seats to evaluate {% data variables.product.prodname_ghe_cloud %}, contact {% data variables.contact.contact_enterprise_sales %}. At the end of the trial, you can choose a different number of seats.
|
||||
|
||||
试用版也可用于 {% data variables.product.prodname_ghe_server %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_server %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-server)”。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_server %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_server %}](/articles/setting-up-a-trial-of-github-enterprise-server)."
|
||||
|
||||
## 设置 {% data variables.product.prodname_ghe_cloud %} 的试用版
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. 更多信息请参阅“<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">注册新 {% data variables.product.prodname_dotcom %} 帐户</a>”。
|
||||
Before you can try {% data variables.product.prodname_ghe_cloud %}, you must be signed into a user account. If you don't already have a user account on {% data variables.product.prodname_dotcom_the_website %}, you must create one. For more information, see "<a href="/articles/signing-up-for-a-new-github-account" class="dotcom-only">Signing up for a new {% data variables.product.prodname_dotcom %} account</a>."
|
||||
|
||||
1. Navigate to [{% data variables.product.prodname_dotcom %} for enterprises](https://github.com/enterprise).
|
||||
1. Click **Start a free trial**. 
|
||||
1. Click **Enterprise Cloud**. 
|
||||
1. Click **Start a free trial**.
|
||||
|
||||
1. Click **Enterprise Cloud**.
|
||||
|
||||
1. Follow the prompts to configure your trial.
|
||||
|
||||
## 探索 {% data variables.product.prodname_ghe_cloud %}
|
||||
## Exploring {% data variables.product.prodname_ghe_cloud %}
|
||||
|
||||
设置试用版后，您可以按照 [Enterprise 入门指南](https://resources.github.com/enterprise-onboarding/)来探索 {% data variables.product.prodname_ghe_cloud %}。
|
||||
After setting up your trial, you can explore {% data variables.product.prodname_ghe_cloud %} by following the [Enterprise Onboarding Guide](https://resources.github.com/enterprise-onboarding/).
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## 结束试用
|
||||
## Finishing your trial
|
||||
|
||||
在试用期间，您可以随时购买 {% data variables.product.prodname_enterprise %} 或降级到 {% data variables.product.prodname_team %}。
|
||||
You can buy {% data variables.product.prodname_enterprise %} or downgrade to {% data variables.product.prodname_team %} at any time during your trial.
|
||||
|
||||
如果在试用期结束前没有购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} ， 您的组织将会降级到 {% data variables.product.prodname_free_team %}，不能使用只包含在付费产品中的任何高级工具和功能，包括从那些私有仓库发布的 {% data variables.product.prodname_pages %} 站点。 如果您不打算升级，为避免失去高级功能的使用权限，请在试用结束前将仓库设为公共。 更多信息请参阅“[设置仓库可见性](/articles/setting-repository-visibility)”。
|
||||
If you don't purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %} before your trial ends, your organization will be downgraded to {% data variables.product.prodname_free_team %} and lose access to any advanced tooling and features that are only included with paid products, including {% data variables.product.prodname_pages %} sites published from those private repositories. If you don't plan to upgrade, to avoid losing access to advanced features, make the repositories public before your trial ends. For more information, see "[Setting repository visibility](/articles/setting-repository-visibility)."
|
||||
|
||||
对于组织来说，降级到 {% data variables.product.prodname_free_team %} 还会禁用试用期间配置的任何 SAML 设置。 购买 {% data variables.product.prodname_enterprise %} 或 {% data variables.product.prodname_team %} 后，您的 SAML 设置将再次启用，以便您组织中的用户进行身份验证。
|
||||
Downgrading to {% data variables.product.prodname_free_team %} for organizations also disables any SAML settings configured during the trial period. Once you purchase {% data variables.product.prodname_enterprise %} or {% data variables.product.prodname_team %}, your SAML settings will be enabled again for users in your organization to authenticate.
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.billing_plans %}
|
||||
5. 在“{% data variables.product.prodname_ghe_cloud %} Free Trial（GitHub Enterprise Cloud 免费试用）”下，单击 **Buy Enterprise（购买 Enterprise 版）**或 **Downgrade to Team（降级到 Team 版）**。 
|
||||
6. 按照提示输入付款方式，然后单击 **Submit（提交）**。
|
||||
5. Under "{% data variables.product.prodname_ghe_cloud %} Free Trial", click **Buy Enterprise** or **Downgrade to Team**.
|
||||
|
||||
6. Follow the prompts to enter your payment method, then click **Submit**.
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 设置 GitHub Enterprise Server 试用版
|
||||
intro: '您可以免费试用 {% data variables.product.prodname_ghe_server %}。'
|
||||
title: Setting up a trial of GitHub Enterprise Server
|
||||
intro: 'You can try {% data variables.product.prodname_ghe_server %} for free.'
|
||||
redirect_from:
|
||||
- /articles/requesting-a-trial-of-github-enterprise/
|
||||
- /articles/requesting-a-trial-of-github-enterprise
|
||||
- /articles/setting-up-a-trial-of-github-enterprise-server
|
||||
- /github/getting-started-with-github/setting-up-a-trial-of-github-enterprise-server
|
||||
- /github/getting-started-with-github/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server
|
||||
@@ -12,56 +12,55 @@ versions:
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: Enterprise Server 试用版
|
||||
shortTitle: Enterprise Server trial
|
||||
---
|
||||
## About trials of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
## 关于 {% data variables.product.prodname_ghe_server %} 试用版
|
||||
You can request a 45-day trial to evaluate {% data variables.product.prodname_ghe_server %}. Your trial will be installed as a virtual appliance, with options for on-premises or cloud deployment. For a list of supported visualization platforms, see "[Setting up a GitHub Enterprise Server instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
您可以申请 45 天试用版来试用 {% data variables.product.prodname_ghe_server %}。 您的试用版将作为虚拟设备安装，带有内部或云部署选项。 有关支持的可视化平台列表，请参阅“[设置 GitHub Enterprise Server 实例](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)”。
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Security{% endif %} alerts and {% data variables.product.prodname_github_connect %} are not currently available in trials of {% data variables.product.prodname_ghe_server %}. For a demonstration of these features, contact {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}安全{% endif %}警报和 {% data variables.product.prodname_github_connect %} 目前在 {% data variables.product.prodname_ghe_server %} 试用版中不可用。 要获取这些功能的演示，请联系 {% data variables.contact.contact_enterprise_sales %}。 For more information about these features, see "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)."
|
||||
|
||||
试用版也可用于 {% data variables.product.prodname_ghe_cloud %}。 更多信息请参阅“[设置 {% data variables.product.prodname_ghe_cloud %} 的试用](/articles/setting-up-a-trial-of-github-enterprise-cloud)”。
|
||||
Trials are also available for {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)."
|
||||
|
||||
{% data reusables.products.which-product-to-use %}
|
||||
|
||||
## 设置 {% data variables.product.prodname_ghe_server %} 的试用版
|
||||
## Setting up your trial of {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
{% data variables.product.prodname_ghe_server %} 作为虚拟设备安装。 确定组织中设置虚拟机的最佳人选，并要求该人员提交[试用申请](https://enterprise.github.com/trial)。 您可以在提交申请后立即开始试用。
|
||||
{% data variables.product.prodname_ghe_server %} is installed as a virtual appliance. Determine the best person in your organization to set up a virtual machine, and ask that person to submit a [trial request](https://enterprise.github.com/trial). You can begin your trial immediately after submitting a request.
|
||||
|
||||
要为 {% data variables.product.prodname_enterprise %} Web 门户设置帐户，请单击提交试用申请后您收到的电子邮件中的链接，然后按照提示操作。 然后下载您的许可文件。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
To set up an account for the {% data variables.product.prodname_enterprise %} Web portal, click the link in the email you received after submitting your trial request, and follow the prompts. Then, download your license file. For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/enterprise-server@latest/billing/managing-your-license-for-github-enterprise)."
|
||||
|
||||
要安装 {% data variables.product.prodname_ghe_server %}，请下载必要的组件并上传您的许可证文件。 有关更多信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)”中所选可视化平台的说明。
|
||||
To install {% data variables.product.prodname_ghe_server %}, download the necessary components and upload your license file. For more information, see the instructions for your chosen visualization platform in "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
|
||||
## 后续步骤
|
||||
## Next steps
|
||||
|
||||
要充分利用您的试用版，请按以下步骤操作：
|
||||
To get the most out of your trial, follow these steps:
|
||||
|
||||
1. [创建一个组织](/enterprise-server@latest/admin/user-management/creating-organizations)。
|
||||
2. 要了解使用 {% data variables.product.prodname_dotcom %} 的基础知识，请参阅：
|
||||
- [{% data variables.product.prodname_dotcom %} 快速入门指南](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/)网络直播
|
||||
- {% data variables.product.prodname_dotcom %} 指南中的[了解 {% data variables.product.prodname_dotcom %} 流程](https://guides.github.com/introduction/flow/)
|
||||
- {% data variables.product.prodname_dotcom %} 指南中的 [Hello World](https://guides.github.com/activities/hello-world/)
|
||||
3. 要配置实例以满足组织的需求，请参阅“[配置企业](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)”。
|
||||
4. 要将 {% data variables.product.prodname_ghe_server %} 与您的身份提供程序集成，请参阅“[使用 SAML](/enterprise-server@latest/admin/user-management/using-saml)”和“[使用 LDAP](/enterprise-server@latest/admin/authentication/using-ldap)”。
|
||||
5. 邀请不限数量的人员加入您的试用版。
|
||||
- 使用内置身份验证或配置的身份提供程序将用户添加到 {% data variables.product.prodname_ghe_server %} 实例。 更多信息请参阅“[使用内置身份验证](/enterprise-server@latest/admin/user-management/using-built-in-authentication)”。
|
||||
- 要邀请人员成为帐户管理员，请访问 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)。
|
||||
1. [Create an organization](/enterprise-server@latest/admin/user-management/creating-organizations).
|
||||
2. To learn the basics of using {% data variables.product.prodname_dotcom %}, see:
|
||||
- [Quick start guide to {% data variables.product.prodname_dotcom %}](https://resources.github.com/webcasts/Quick-start-guide-to-GitHub/) webcast
|
||||
- [Understanding the {% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
- [Hello World](https://guides.github.com/activities/hello-world/) in {% data variables.product.prodname_dotcom %} Guides
|
||||
3. To configure your instance to meet your organization's needs, see "[Configuring your enterprise](/enterprise-server@latest/admin/configuration/configuring-your-enterprise)."
|
||||
4. To integrate {% data variables.product.prodname_ghe_server %} with your identity provider, see "[Using SAML](/enterprise-server@latest/admin/user-management/using-saml)" and "[Using LDAP](/enterprise-server@latest/admin/authentication/using-ldap)."
|
||||
5. Invite an unlimited number of people to join your trial.
|
||||
- Add users to your {% data variables.product.prodname_ghe_server %} instance using built-in authentication or your configured identity provider. For more information, see "[Using built in authentication](/enterprise-server@latest/admin/user-management/using-built-in-authentication)."
|
||||
- To invite people to become account administrators, visit the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login).
|
||||
|
||||
{% note %}
|
||||
|
||||
**注：**您邀请成为帐户管理员的人员将收到一封电子邮件，其中包含接受邀请的链接。
|
||||
**Note:** People you invite to become account administrators will receive an email with a link to accept your invitation.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.products.product-roadmap %}
|
||||
|
||||
## 结束试用
|
||||
## Finishing your trial
|
||||
|
||||
您可以在试用期内随时在 [{% data variables.product.prodname_enterprise %} Web 门户](https://enterprise.github.com/login)中升级到完整许可证。
|
||||
You can upgrade to full licenses in the [{% data variables.product.prodname_enterprise %} Web portal](https://enterprise.github.com/login) at any time during the trial period.
|
||||
|
||||
如果您在试用的最后一天仍未升级，将收到一封电子邮件，通知您试用已结束。 如果需要更多时间来评估 {% data variables.product.prodname_enterprise %}，请联系 {% data variables.contact.contact_enterprise_sales %} 申请延期。
|
||||
If you haven't upgraded by the last day of your trial, you'll receive an email notifying you that your trial had ended. If you need more time to evaluate {% data variables.product.prodname_enterprise %}, contact {% data variables.contact.contact_enterprise_sales %} to request an extension.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[设置 {% data variables.product.prodname_ghe_cloud %} 的试用版](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)”
|
||||
- "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)"
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: 验证电子邮件地址
|
||||
intro: '验证主电子邮件地址可确保增强的安全性，以便 {% data variables.product.prodname_dotcom %} 员工在您忘记密码时更好地协助您，并为您提供 {% data variables.product.prodname_dotcom %} 上更多功能的访问权限。'
|
||||
title: Verifying your email address
|
||||
intro: 'Verifying your primary email address ensures strengthened security, allows {% data variables.product.prodname_dotcom %} staff to better assist you if you forget your password, and gives you access to more features on {% data variables.product.prodname_dotcom %}.'
|
||||
redirect_from:
|
||||
- /articles/troubleshooting-email-verification/
|
||||
- /articles/setting-up-email-verification/
|
||||
- /articles/troubleshooting-email-verification
|
||||
- /articles/setting-up-email-verification
|
||||
- /articles/verifying-your-email-address
|
||||
- /github/getting-started-with-github/verifying-your-email-address
|
||||
- /github/getting-started-with-github/signing-up-for-github/verifying-your-email-address
|
||||
@@ -12,59 +12,60 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Accounts
|
||||
shortTitle: 验证您的电子邮件地址
|
||||
shortTitle: Verify your email address
|
||||
---
|
||||
## About email verification
|
||||
|
||||
## 关于电子邮件通知
|
||||
You can verify your email address after signing up for a new account, or when you add a new email address. If an email address is undeliverable or bouncing, it will be unverified.
|
||||
|
||||
您可在注册新帐户后或添加新电子邮件地址时验证您的电子邮件地址。 如果电子邮件地址无法送达或退回，它将无法进行验证。
|
||||
|
||||
如果没有验证电子邮件地址，您将无法：
|
||||
- 创建或复刻仓库
|
||||
- 创建议题或拉取请求
|
||||
- 对议题、拉取请求或提交发表评论
|
||||
- 授权 {% data variables.product.prodname_oauth_app %} 应用程序
|
||||
- 生成个人访问令牌
|
||||
- 接收电子邮件通知
|
||||
- 对仓库加星标
|
||||
- 创建或更新项目板，包括添加卡片
|
||||
- 创建或更新 gist
|
||||
- 创建或使用 {% data variables.product.prodname_actions %}
|
||||
- 通过 {% data variables.product.prodname_sponsors %} 赞助开发者
|
||||
If you do not verify your email address, you will not be able to:
|
||||
- Create or fork repositories
|
||||
- Create issues or pull requests
|
||||
- Comment on issues, pull requests, or commits
|
||||
- Authorize {% data variables.product.prodname_oauth_app %} applications
|
||||
- Generate personal access tokens
|
||||
- Receive email notifications
|
||||
- Star repositories
|
||||
- Create or update project boards, including adding cards
|
||||
- Create or update gists
|
||||
- Create or use {% data variables.product.prodname_actions %}
|
||||
- Sponsor developers with {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：
|
||||
**Warnings**:
|
||||
|
||||
- {% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
- {% data reusables.user_settings.verify-org-approved-email-domain %}
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 验证电子邮件地址
|
||||
## Verifying your email address
|
||||
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.emails %}
|
||||
1. 在电子邮件地址下，单击 **Resend verification email（重新发送验证电子邮件）**。 
|
||||
4. {% data variables.product.prodname_dotcom %} 将向您发送一封含有链接的电子邮件。 单击该链接后，您将转到 {% data variables.product.prodname_dotcom %} 仪表板并看到确认横幅。 
|
||||
1. Under your email address, click **Resend verification email**.
|
||||
|
||||
4. {% data variables.product.prodname_dotcom %} will send you an email with a link in it. After you click that link, you'll be taken to your {% data variables.product.prodname_dotcom %} dashboard and see a confirmation banner.
|
||||
|
||||
|
||||
## 电子邮件验证故障排除
|
||||
## Troubleshooting email verification
|
||||
|
||||
### 无法发送验证电子邮件
|
||||
### Unable to send verification email
|
||||
|
||||
{% data reusables.user_settings.no-verification-disposable-emails %}
|
||||
|
||||
### 单击验证链接后的错误页面
|
||||
### Error page after clicking verification link
|
||||
|
||||
验证链接将在 24 小时后过期。 如果您没有在 24 小时内验证电子邮件，则可以请求其他电子邮件验证链接。 更多信息请参阅“[验证电子邮件地址](/articles/verifying-your-email-address)”。
|
||||
The verification link expires after 24 hours. If you don't verify your email within 24 hours, you can request another email verification link. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
|
||||
|
||||
If you click on the link in the confirmation email within 24 hours and you are directed to an error page, you should ensure that you're signed into the correct account on {% data variables.product.product_location %}.
|
||||
|
||||
1. {% data variables.product.signout_link %} of your personal account on {% data variables.product.product_location %}.
|
||||
2. 退出并重新启动浏览器。
|
||||
2. Quit and restart your browser.
|
||||
3. {% data variables.product.signin_link %} to your personal account on {% data variables.product.product_location %}.
|
||||
4. 单击我们发送给您的电子邮件中的验证链接。
|
||||
4. Click on the verification link in the email we sent you.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- “[更改主电子邮件地址](/articles/changing-your-primary-email-address)”
|
||||
- "[Changing your primary email address](/articles/changing-your-primary-email-address)"
|
||||
|
||||
@@ -1,75 +1,74 @@
|
||||
---
|
||||
title: 关于 Git 变基
|
||||
title: About Git rebase
|
||||
redirect_from:
|
||||
- /rebase/
|
||||
- /rebase
|
||||
- articles/interactive-rebase/
|
||||
- /articles/about-git-rebase
|
||||
- /github/using-git/about-git-rebase
|
||||
- /github/getting-started-with-github/about-git-rebase
|
||||
- /github/getting-started-with-github/using-git/about-git-rebase
|
||||
intro: '`git rebase` 命令用于轻松更改一系列提交，修改仓库的历史记录。 您可以重新排序、编辑提交或将提交压缩到一起。'
|
||||
intro: 'The `git rebase` command allows you to easily change a series of commits, modifying the history of your repository. You can reorder, edit, or squash commits together.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
Typically, you would use `git rebase` to:
|
||||
|
||||
通常，您会使用 `git rebase` 来：
|
||||
|
||||
* 编辑之前的提交消息
|
||||
* 将多个提交合并为一个
|
||||
* 删除或还原不再必要的提交
|
||||
* Edit previous commit messages
|
||||
* Combine multiple commits into one
|
||||
* Delete or revert commits that are no longer necessary
|
||||
|
||||
{% warning %}
|
||||
|
||||
**警告**：由于更改您的提交历史记录可能会给其他人使用仓库造成困难，因此如果提交已经推送到仓库，提交变基被视为一种坏习惯。 要了解如何在 {% data variables.product.product_location %} 上安全地变基，请参阅“[关于拉取请求合并](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)”。
|
||||
**Warning**: Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository. To learn how to safely rebase on {% data variables.product.product_location %}, see "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 对分支变基提交
|
||||
## Rebasing commits against a branch
|
||||
|
||||
要对另一个分支与当前分支状态之间的所有提交变基，可以在 shell（Windows 的命令提示符或者 Mac 和 Linux 的终端）中输入以下命令：
|
||||
To rebase all the commits between another branch and the current branch state, you can enter the following command in your shell (either the command prompt for Windows, or the terminal for Mac and Linux):
|
||||
|
||||
```shell
|
||||
$ git rebase --interactive <em>other_branch_name</em>
|
||||
```
|
||||
|
||||
## 对某一时间点变基提交
|
||||
## Rebasing commits against a point in time
|
||||
|
||||
要变基当前分支中最近的几个提交，可以在 shell 中输入以下命令：
|
||||
To rebase the last few commits in your current branch, you can enter the following command in your shell:
|
||||
|
||||
```shell
|
||||
$ git rebase --interactive HEAD~7
|
||||
```
|
||||
|
||||
## 变基时可用的命令
|
||||
## Commands available while rebasing
|
||||
|
||||
变基时有六个命令可用：
|
||||
There are six commands available while rebasing:
|
||||
|
||||
<dl>
|
||||
<dt><code>pick</code></dt>
|
||||
<dd><code>pick</code> 只表示包含提交。 在变基进行时重新排列 <code>pick</code> 命令的顺序会更改提交的顺序。 如果选择不包含提交，应删除整行。 </dd>
|
||||
<dd><code>pick</code> simply means that the commit is included. Rearranging the order of the <code>pick</code> commands changes the order of the commits when the rebase is underway. If you choose not to include a commit, you should delete the entire line. </dd>
|
||||
|
||||
<dt><code>reword</code></dt>
|
||||
<dd><code>reword</code> 命令类似于 <code>pick</code>，但在使用后，变基过程就会暂停，让您有机会改变提交消息。 提交所做的任何更改都不受影响。 </dd>
|
||||
<dd>The <code>reword</code> command is similar to <code>pick</code>, but after you use it, the rebase process will pause and give you a chance to alter the commit message. Any changes made by the commit are not affected. </dd>
|
||||
|
||||
<dt><code>edit</code></dt>
|
||||
<dd>如果选择 <code>edit</code> 提交，您将有机会修订提交，也就是说，可以完全添加或更改提交。 您也可以创建更多提交后再继续变基。 这样您可以将大提交拆分为小提交，或者删除在提交中执行错误更改。 </dd>
|
||||
<dd>If you choose to <code>edit</code> a commit, you'll be given the chance to amend the commit, meaning that you can add or change the commit entirely. You can also make more commits before you continue the rebase. This allows you to split a large commit into smaller ones, or, remove erroneous changes made in a commit. </dd>
|
||||
|
||||
<dt><code>压缩</code></dt>
|
||||
<dd>此命令可用于将两个或以上的提交合并为一个。 下面的提交压缩到其上面的提交。 Git 让您有机会编写描述两次更改的新提交消息。</dd>
|
||||
<dt><code>squash</code></dt>
|
||||
<dd>This command lets you combine two or more commits into a single commit. A commit is squashed into the commit above it. Git gives you the chance to write a new commit message describing both changes.</dd>
|
||||
|
||||
<dt><code>fixup</code></dt>
|
||||
<dd>这类似于 <code>squash</code>，但要合并的提交丢弃了其消息。 提交只是合并到其上面的提交，之前提交的消息用于描述两次更改。</dd>
|
||||
<dd>This is similar to <code>squash</code>, but the commit to be merged has its message discarded. The commit is simply merged into the commit above it, and the earlier commit's message is used to describe both changes.</dd>
|
||||
|
||||
<dt><code>exec</code></dt>
|
||||
<dd>这可让您对提交运行任意 shell 命令。</dd>
|
||||
<dd>This lets you run arbitrary shell commands against a commit.</dd>
|
||||
</dl>
|
||||
|
||||
## `git rebase` 使用示例
|
||||
## An example of using `git rebase`
|
||||
|
||||
无论使用哪个命令，Git 都将启动[默认文本编辑器](/github/getting-started-with-github/associating-text-editors-with-git)，并且打开详细说明所选范围中提交的文件。 该文件类似于：
|
||||
No matter which command you use, Git will launch [your default text editor](/github/getting-started-with-github/associating-text-editors-with-git) and open a file that details the commits in the range you've chosen. That file looks something like this:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -95,18 +94,18 @@ pick 7b36971 something to move before patch B
|
||||
#
|
||||
```
|
||||
|
||||
从上到下分解此信息，我们可以看出：
|
||||
Breaking this information, from top to bottom, we see that:
|
||||
|
||||
- 列出了七个命令，表示从起点到当前分支状态之间有七处更改。
|
||||
- 您选择要变基的提交按最早更改（顶部）到最新更改（底部）的顺序存储。
|
||||
- 每行列出一个命令（默认为 `pick`）、提交 SHA 和提交消息。 整个 `git rebase` 程序以您对这三列的操作为中心。 您做出的更改将*变基*到仓库。
|
||||
- 在提交后，Git 会告知我们正在处理的提交范围 (`41a72e6..7b36971`)。
|
||||
- 最后，Git 会提供一些帮助，告知在变基提交时可用的命令。
|
||||
- Seven commits are listed, which indicates that there were seven changes between our starting point and our current branch state.
|
||||
- The commits you chose to rebase are sorted in the order of the oldest changes (at the top) to the newest changes (at the bottom).
|
||||
- Each line lists a command (by default, `pick`), the commit SHA, and the commit message. The entire `git rebase` procedure centers around your manipulation of these three columns. The changes you make are *rebased* onto your repository.
|
||||
- After the commits, Git tells you the range of commits we're working with (`41a72e6..7b36971`).
|
||||
- Finally, Git gives some help by telling you the commands that are available to you when rebasing commits.
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- "[使用 Git rebase](/articles/using-git-rebase)"
|
||||
- [_Pro Git_ 书籍中的“Git 分支”一章](https://git-scm.com/book/en/Git-Branching-Rebasing)
|
||||
- [_Pro Git_ 书籍中的“交互式变基”一章](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
|
||||
- "[使用变基压缩提交](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
|
||||
- {% data variables.product.prodname_desktop %} 文档中的“[同步分支](/desktop/contributing-to-projects/syncing-your-branch)”
|
||||
- "[Using Git rebase](/articles/using-git-rebase)"
|
||||
- [The "Git Branching" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Branching-Rebasing)
|
||||
- [The "Interactive Rebasing" chapter from the _Pro Git_ book](https://git-scm.com/book/en/Git-Tools-Rewriting-History#_changing_multiple)
|
||||
- "[Squashing commits with rebase](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)"
|
||||
- "[Syncing your branch](/desktop/contributing-to-projects/syncing-your-branch)" in the {% data variables.product.prodname_desktop %} documentation
|
||||
|
||||
@@ -1,45 +1,44 @@
|
||||
---
|
||||
title: 关于 Git 子树合并
|
||||
title: About Git subtree merges
|
||||
redirect_from:
|
||||
- /articles/working-with-subtree-merge/
|
||||
- /subtree-merge/
|
||||
- /articles/working-with-subtree-merge
|
||||
- /subtree-merge
|
||||
- /articles/about-git-subtree-merges
|
||||
- /github/using-git/about-git-subtree-merges
|
||||
- /github/getting-started-with-github/about-git-subtree-merges
|
||||
- /github/getting-started-with-github/using-git/about-git-subtree-merges
|
||||
intro: 如果需要管理单一仓库中的多个项目，可以使用*子树合并*来处理所有引用。
|
||||
intro: 'If you need to manage multiple projects within a single repository, you can use a *subtree merge* to handle all the references.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
## About subtree merges
|
||||
|
||||
## 关于子树合并
|
||||
Typically, a subtree merge is used to contain a repository within a repository. The "subrepository" is stored in a folder of the main repository.
|
||||
|
||||
通常，子树合并用于在仓库中包含仓库。 “子仓库”存储在主仓库的文件夹中。
|
||||
The best way to explain subtree merges is to show by example. We will:
|
||||
|
||||
解释子树合并的最佳方式是举例说明。 我们将：
|
||||
- Make an empty repository called `test` that represents our project
|
||||
- Merge another repository into it as a subtree called `Spoon-Knife`.
|
||||
- The `test` project will use that subproject as if it were part of the same repository.
|
||||
- Fetch updates from `Spoon-Knife` into our `test` project.
|
||||
|
||||
- 创建一个名为 `test` 的空仓库，表示我们的项目
|
||||
- 将另一个仓库 `Spoon-Knife` 作为子树合并到其中。
|
||||
- 如果该子项目属于同一仓库，`test` 项目会使用它。
|
||||
- 从 `Spoon-Knife` 提取更新到 `test` 项目。
|
||||
|
||||
## 创建用于子树合并的空仓库
|
||||
## Setting up the empty repository for a subtree merge
|
||||
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
2. 创建一个新目录并找到它。
|
||||
2. Create a new directory and navigate to it.
|
||||
```shell
|
||||
$ mkdir test
|
||||
$ cd test
|
||||
```
|
||||
3. 初始化新的 Git 仓库。
|
||||
3. Initialize a new Git repository.
|
||||
```shell
|
||||
$ git init
|
||||
> Initialized empty Git repository in /Users/octocat/tmp/test/.git/
|
||||
```
|
||||
4. 创建并提交新文件。
|
||||
4. Create and commit a new file.
|
||||
```shell
|
||||
$ touch .gitignore
|
||||
$ git add .gitignore
|
||||
@@ -49,9 +48,9 @@ versions:
|
||||
> create mode 100644 .gitignore
|
||||
```
|
||||
|
||||
## 新增一个仓库为子树
|
||||
## Adding a new repository as a subtree
|
||||
|
||||
1. 新增指向我们感兴趣的单独项目的远程 URL。
|
||||
1. Add a new remote URL pointing to the separate project that we're interested in.
|
||||
```shell
|
||||
$ git remote add -f spoon-knife git@github.com:octocat/Spoon-Knife.git
|
||||
> Updating spoon-knife
|
||||
@@ -64,52 +63,52 @@ versions:
|
||||
> From git://github.com/octocat/Spoon-Knife
|
||||
> * [new branch] main -> Spoon-Knife/main
|
||||
```
|
||||
2. 将 `Spon-Knife` 项目合并到当地 Git 项目。 这不会在本地更改任何文件，但会为下一步准备 Git。
|
||||
2. Merge the `Spoon-Knife` project into the local Git project. This doesn't change any of your files locally, but it does prepare Git for the next step.
|
||||
|
||||
如果您使用的是 Git 2.9 或更高版本：
|
||||
If you're using Git 2.9 or above:
|
||||
```shell
|
||||
$ git merge -s ours --no-commit --allow-unrelated-histories spoon-knife/main
|
||||
> Automatic merge went well; stopped before committing as requested
|
||||
```
|
||||
|
||||
如果您使用的是 Git 2.8 或更低版本：
|
||||
If you're using Git 2.8 or below:
|
||||
```shell
|
||||
$ git merge -s ours --no-commit spoon-knife/main
|
||||
> Automatic merge went well; stopped before committing as requested
|
||||
```
|
||||
3. 创建新目录 **spoon-knife** 并将 `Spoon-Knife` 项目的 Git 历史记录复制到其中。
|
||||
3. Create a new directory called **spoon-knife**, and copy the Git history of the `Spoon-Knife` project into it.
|
||||
```shell
|
||||
$ git read-tree --prefix=spoon-knife/ -u spoon-knife/main
|
||||
```
|
||||
4. 提交更改以确保其安全。
|
||||
4. Commit the changes to keep them safe.
|
||||
```shell
|
||||
$ git commit -m "Subtree merged in spoon-knife"
|
||||
> [main fe0ca25] Subtree merged in spoon-knife
|
||||
```
|
||||
|
||||
虽然我们只添加了一个子项目，但是可在 Git 仓库中加入任意数量的子项目。
|
||||
Although we've only added one subproject, any number of subprojects can be incorporated into a Git repository.
|
||||
|
||||
{% tip %}
|
||||
|
||||
**提示**：如果以后创建仓库的全新克隆，不会为您创建您添加的远程 Url。 您需要再次使用 [the `git remote add` 命令添加它们](/github/getting-started-with-github/managing-remote-repositories)。
|
||||
**Tip**: If you create a fresh clone of the repository in the future, the remotes you've added will not be created for you. You will have to add them again using [the `git remote add` command](/github/getting-started-with-github/managing-remote-repositories).
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## 同步更新和更改
|
||||
## Synchronizing with updates and changes
|
||||
|
||||
添加子项目时，它不会自动与上游更改保持同步。 您需要使用以下命令更新子项目：
|
||||
When a subproject is added, it is not automatically kept in sync with the upstream changes. You will need to update the subproject with the following command:
|
||||
|
||||
```shell
|
||||
$ git pull -s subtree <em>remotename</em> <em>branchname</em>
|
||||
```
|
||||
|
||||
对于上述示例，将是：
|
||||
For the example above, this would be:
|
||||
|
||||
```shell
|
||||
$ git pull -s subtree spoon-knife main
|
||||
```
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [_Pro Git_ 书籍中的“高级合并”一章](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
|
||||
- "[如何使用子树合并策略](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
|
||||
- [The "Advanced Merging" chapter from the _Pro Git_ book](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging)
|
||||
- "[How to use the subtree merge strategy](https://www.kernel.org/pub/software/scm/git/docs/howto/using-merge-subtree.html)"
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
title: Getting changes from a remote repository
|
||||
intro: You can use common Git commands to access remote repositories.
|
||||
redirect_from:
|
||||
- /articles/fetching-a-remote/
|
||||
- /articles/fetching-a-remote
|
||||
- /articles/getting-changes-from-a-remote-repository
|
||||
- /github/using-git/getting-changes-from-a-remote-repository
|
||||
- /github/getting-started-with-github/getting-changes-from-a-remote-repository
|
||||
|
||||
@@ -1,15 +1,15 @@
|
||||
---
|
||||
title: 使用 Git
|
||||
intro: '使用 Git 从计算机管理您的 {% data variables.product.product_name %} 仓库。'
|
||||
title: Using Git
|
||||
intro: 'Use Git to manage your {% data variables.product.product_name %} repositories from your computer.'
|
||||
redirect_from:
|
||||
- /articles/using-common-git-commands
|
||||
- /github/using-git/using-common-git-commands
|
||||
- /github/using-git/using-advanced-git-commands
|
||||
- /categories/52/articles/
|
||||
- /categories/advanced-git/
|
||||
- /categories/52/articles
|
||||
- /categories/advanced-git
|
||||
- /articles/using-advanced-git-commands
|
||||
- /github/using-git/changing-author-info
|
||||
- /github/getting-started-with-github/using-git/
|
||||
- /github/getting-started-with-github/using-git
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
---
|
||||
title: 推送提交到远程仓库
|
||||
intro: 使用 `git push` 将本地分支上的提交推送到远程仓库。
|
||||
title: Pushing commits to a remote repository
|
||||
intro: Use `git push` to push commits made on your local branch to a remote repository.
|
||||
redirect_from:
|
||||
- /articles/pushing-to-a-remote/
|
||||
- /articles/pushing-to-a-remote
|
||||
- /articles/pushing-commits-to-a-remote-repository
|
||||
- /github/using-git/pushing-commits-to-a-remote-repository
|
||||
- /github/getting-started-with-github/pushing-commits-to-a-remote-repository
|
||||
@@ -12,76 +12,87 @@ versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: 推送提交到远程
|
||||
shortTitle: Push commits to a remote
|
||||
---
|
||||
|
||||
## About `git push`
|
||||
`git push` 命令使用两个参数：
|
||||
The `git push` command takes two arguments:
|
||||
|
||||
* 远程命令，如 `origin`
|
||||
* 分支名称，如 `main`
|
||||
* A remote name, for example, `origin`
|
||||
* A branch name, for example, `main`
|
||||
|
||||
例如：
|
||||
For example:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <BRANCHNAME> </em>
|
||||
```
|
||||
|
||||
例如，您通常运行 `git push origin main` 来推送本地更改到在线仓库。
|
||||
As an example, you usually run `git push origin main` to push your local changes
|
||||
to your online repository.
|
||||
|
||||
## 重命名分支
|
||||
## Renaming branches
|
||||
|
||||
要重命名分支，同样使用 `git push` 命令，但要加上一个或多个参数：新分支的名称。 例如：
|
||||
To rename a branch, you'd use the same `git push` command, but you would add
|
||||
one more argument: the name of the new branch. For example:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <LOCALBRANCHNAME></em>:<em><REMOTEBRANCHNAME> </em>
|
||||
```
|
||||
|
||||
这会将 `LOCALBRANCHNAME` 推送到 `REMOTENAME`，但其名称将改为 `REMOTEBRANCHNAME`。
|
||||
This pushes the `LOCALBRANCHNAME` to your `REMOTENAME`, but it is renamed to `REMOTEBRANCHNAME`.
|
||||
|
||||
## 处理“非快进”错误
|
||||
## Dealing with "non-fast-forward" errors
|
||||
|
||||
如果仓库的本地副本未同步或“落后于”您推送到的上游分支，您会收到一条消息表示：`non-fast-forward updates were rejected`。 这意味着您必须检索或“提取”上游更改，然后才可推送本地更改。
|
||||
If your local copy of a repository is out of sync with, or "behind," the upstream
|
||||
repository you're pushing to, you'll get a message saying `non-fast-forward updates were rejected`.
|
||||
This means that you must retrieve, or "fetch," the upstream changes, before
|
||||
you are able to push your local changes.
|
||||
|
||||
有关此错误的更多信息，请参阅“[处理非快进错误](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)”。
|
||||
For more information on this error, see "[Dealing with non-fast-forward errors](/github/getting-started-with-github/dealing-with-non-fast-forward-errors)."
|
||||
|
||||
## 推送标记
|
||||
## Pushing tags
|
||||
|
||||
默认情况下，没有其他参数时，`git push` 会发送所有名称与远程分支相同的匹配分支。
|
||||
By default, and without additional parameters, `git push` sends all matching branches
|
||||
that have the same names as remote branches.
|
||||
|
||||
要推送单一标记，可以发出与推送分支相同的命令：
|
||||
To push a single tag, you can issue the same command as pushing a branch:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME> <TAGNAME> </em>
|
||||
```
|
||||
|
||||
要推送所有标记，可以输入命令：
|
||||
To push all your tags, you can type the command:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME></em> --tags
|
||||
```
|
||||
|
||||
## 删除远程分支或标记
|
||||
## Deleting a remote branch or tag
|
||||
|
||||
删除分支的语法初看有点神秘：
|
||||
The syntax to delete a branch is a bit arcane at first glance:
|
||||
|
||||
```shell
|
||||
git push <em> <REMOTENAME></em> :<em><BRANCHNAME> </em>
|
||||
```
|
||||
|
||||
请注意，冒号前有一个空格。 命令与重命名分支的步骤类似。 但这里是告诉 Git _不要_推送任何内容到 `REMOTENAME` 上的 `BRANCHNAME`。 因此，`git push` 会删除远程仓库上的分支。
|
||||
Note that there is a space before the colon. The command resembles the same steps
|
||||
you'd take to rename a branch. However, here, you're telling Git to push _nothing_
|
||||
into `BRANCHNAME` on `REMOTENAME`. Because of this, `git push` deletes the branch
|
||||
on the remote repository.
|
||||
|
||||
## 远程和复刻
|
||||
## Remotes and forks
|
||||
|
||||
您可能已经知道，[您可以对 GitHub 上的仓库“复刻”](https://guides.github.com/overviews/forking/)。
|
||||
You might already know that [you can "fork" repositories](https://guides.github.com/overviews/forking/) on GitHub.
|
||||
|
||||
在克隆您拥有的仓库时，向其提供远程 URL，告知 Git 到何处提取和推送更新。 如果要协作处理原始仓库，可添加新的远程 URL（通常称为 `upstream`）到本地 Git 克隆：
|
||||
When you clone a repository you own, you provide it with a remote URL that tells
|
||||
Git where to fetch and push updates. If you want to collaborate with the original
|
||||
repository, you'd add a new remote URL, typically called `upstream`, to
|
||||
your local Git clone:
|
||||
|
||||
```shell
|
||||
git remote add upstream <em> <THEIR_REMOTE_URL> </em>
|
||||
```
|
||||
|
||||
现在可以从*其*复刻提取更新和分支：
|
||||
Now, you can fetch updates and branches from *their* fork:
|
||||
|
||||
```shell
|
||||
git fetch upstream
|
||||
@@ -94,14 +105,15 @@ git fetch upstream
|
||||
> * [new branch] main -> upstream/main
|
||||
```
|
||||
|
||||
在完成本地更改后，可以推送本地分支到 GitHub 并[发起拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)。
|
||||
When you're done making local changes, you can push your local branch to GitHub
|
||||
and [initiate a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests).
|
||||
|
||||
有关使用复刻的更多信息，请参阅“[同步复刻](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)”。
|
||||
For more information on working with forks, see "[Syncing a fork](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork)".
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- ["Pro Git" 书中的“远程”一章](https://git-scm.com/book/ch5-2.html)
|
||||
- [The "Remotes" chapter from the "Pro Git" book](https://git-scm.com/book/ch5-2.html)
|
||||
- [`git remote` main page](https://git-scm.com/docs/git-remote.html)
|
||||
- "[Git 小抄](/articles/git-cheatsheet)"
|
||||
- "[Git 工作流程](/github/getting-started-with-github/git-workflows)"
|
||||
- "[Git 手册](https://guides.github.com/introduction/git-handbook/)"
|
||||
- "[Git cheatsheet](/articles/git-cheatsheet)"
|
||||
- "[Git workflows](/github/getting-started-with-github/git-workflows)"
|
||||
- "[Git Handbook](https://guides.github.com/introduction/git-handbook/)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Splitting a subfolder out into a new repository
|
||||
redirect_from:
|
||||
- /articles/splitting-a-subpath-out-into-a-new-repository/
|
||||
- /articles/splitting-a-subpath-out-into-a-new-repository
|
||||
- /articles/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/using-git/splitting-a-subfolder-out-into-a-new-repository
|
||||
- /github/getting-started-with-github/splitting-a-subfolder-out-into-a-new-repository
|
||||
|
||||
@@ -1,25 +1,24 @@
|
||||
---
|
||||
title: 在命令行中使用 Git rebase
|
||||
title: Using Git rebase on the command line
|
||||
redirect_from:
|
||||
- /articles/using-git-rebase/
|
||||
- /articles/using-git-rebase
|
||||
- /articles/using-git-rebase-on-the-command-line
|
||||
- /github/using-git/using-git-rebase-on-the-command-line
|
||||
- /github/getting-started-with-github/using-git-rebase-on-the-command-line
|
||||
- /github/getting-started-with-github/using-git/using-git-rebase-on-the-command-line
|
||||
intro: 以下是在命令行中使用 `git rebase` 的简短教程。
|
||||
intro: Here's a short tutorial on using `git rebase` on the command line.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Git 变基
|
||||
shortTitle: Git rebase
|
||||
---
|
||||
## Using Git rebase
|
||||
|
||||
## 使用 Git 变基
|
||||
In this example, we will cover all of the `git rebase` commands available, except for `exec`.
|
||||
|
||||
在本例中，我们将涵盖所有可用的 `git rebase` 命令，`exec` 除外。
|
||||
|
||||
我们将通过在终端上输入 `git rebase --interactive HEAD~7` 开始变基。 首选的文本编辑器将显示以下行：
|
||||
We'll start our rebase by entering `git rebase --interactive HEAD~7` on the terminal. Our favorite text editor will display the following lines:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -31,17 +30,17 @@ pick 4ca2acc i cant' typ goods
|
||||
pick 7b36971 something to move before patch B
|
||||
```
|
||||
|
||||
在本例中，我们将：
|
||||
In this example, we're going to:
|
||||
|
||||
* 使用 `squash` 将第五个提交 (`fa39187`) 压缩到 `"Patch A"` 提交 (`1fc6c95`) 中。
|
||||
* 将最后一个提交 (`7b36971`) 向上移动到 `"Patch B"` 提交 (`6b2481b`) 之前，并将其保留为 `pick`。
|
||||
* 将 `"A fix for Patch B"` 提交 (`c619268`) 合并到 `"Patch B"` 提交 (`6b2481b`) 中，并使用 `fixup` 忽略提交消息。
|
||||
* 使用 `edit` 将第三个提交 (`dd1475d`) 拆分成两个较小的提交。
|
||||
* 使用 `reword` 修复拼写错误的提交 (`4ca2acc`) 的提交消息。
|
||||
* Squash the fifth commit (`fa39187`) into the `"Patch A"` commit (`1fc6c95`), using `squash`.
|
||||
* Move the last commit (`7b36971`) up before the `"Patch B"` commit (`6b2481b`), and keep it as `pick`.
|
||||
* Merge the `"A fix for Patch B"` commit (`c619268`) into the `"Patch B"` commit (`6b2481b`), and disregard the commit message using `fixup`.
|
||||
* Split the third commit (`dd1475d`) into two smaller commits, using `edit`.
|
||||
* Fix the commit message of the misspelled commit (`4ca2acc`), using `reword`.
|
||||
|
||||
唷！ 这听起来像是有好多工作，但一步一步来，我们可以轻松地进行这些更改。
|
||||
Phew! This sounds like a lot of work, but by taking it one step at a time, we can easily make those changes.
|
||||
|
||||
首先，我们需要修改文件中的命令，如下所示：
|
||||
To start, we'll need to modify the commands in the file to look like this:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -53,35 +52,35 @@ edit dd1475d something I want to split
|
||||
reword 4ca2acc i cant' typ goods
|
||||
```
|
||||
|
||||
我们将每行的命令从 `pick` 更改为我们感兴趣的命令。
|
||||
We've changed each line's command from `pick` to the command we're interested in.
|
||||
|
||||
现在，保存并关闭编辑器，这将开始交互式变基。
|
||||
Now, save and close the editor; this will start the interactive rebase.
|
||||
|
||||
Git 跳过第一条变基命令 `pick 1fc6c95`，因为该命令无需任何操作。 它转到下一条命令 `squash fa39187`。 由于此操作需要您的输入，因此 Git 再次打开您的文本编辑器。 其打开的文件类似如下：
|
||||
Git skips the first rebase command, `pick 1fc6c95`, since it doesn't need to do anything. It goes to the next command, `squash fa39187`. Since this operation requires your input, Git opens your text editor once again. The file it opens up looks something like this:
|
||||
|
||||
```
|
||||
# 这是两个提交的组合。
|
||||
# 第一个提交的消息是：
|
||||
# This is a combination of two commits.
|
||||
# The first commit's message is:
|
||||
|
||||
Patch A
|
||||
|
||||
# 这是第二个提交消息：
|
||||
# This is the 2nd commit message:
|
||||
|
||||
something to add to patch A
|
||||
|
||||
# 请输入您的更改的提交消息。 开头
|
||||
# 为 '#' 的行将被忽略，并且空消息会中止提交。
|
||||
# 当前不在任何分支中。
|
||||
# 要进行提交的更改：
|
||||
# （使用 "git reset HEAD <file>..." 取消暂存）
|
||||
# Please enter the commit message for your changes. Lines starting
|
||||
# with '#' will be ignored, and an empty message aborts the commit.
|
||||
# Not currently on any branch.
|
||||
# Changes to be committed:
|
||||
# (use "git reset HEAD <file>..." to unstage)
|
||||
#
|
||||
# 已修改：a
|
||||
# modified: a
|
||||
#
|
||||
```
|
||||
|
||||
此文件是用 Git 的方式表明“嗨，这就是我要使用这条 `squash` 完成的操作”。 它列出了第一个提交的消息 (`"Patch A"`) 和第二个提交的消息 (`"something to add to patch A"`)。 如果对这些提交消息感到满意，您可以保存该文件，然后关闭编辑器。 否则，您可选择更改提交消息，只需更改文本即可。
|
||||
This file is Git's way of saying, "Hey, here's what I'm about to do with this `squash`." It lists the first commit's message (`"Patch A"`), and the second commit's message (`"something to add to patch A"`). If you're happy with these commit messages, you can save the file, and close the editor. Otherwise, you have the option of changing the commit message by simply changing the text.
|
||||
|
||||
编辑器关闭后，变基继续：
|
||||
When the editor is closed, the rebase continues:
|
||||
|
||||
```
|
||||
pick 1fc6c95 Patch A
|
||||
@@ -93,9 +92,9 @@ edit dd1475d something I want to split
|
||||
reword 4ca2acc i cant' typ goods
|
||||
```
|
||||
|
||||
Git 会处理两条 `pick` 命令（针对 `pick 7b36971` 和 `pick 6b2481b`）。 它*还*会处理 `fixup` 命令 (`fixup c619268`)，因为该命令不需要任何交互。 `fixup` 会将来自 `c619268` 的更改合并到其之前的提交 `6b2481b` 中。 这些更改都有相同的提交消息：`"Patch B"`。
|
||||
Git processes the two `pick` commands (for `pick 7b36971` and `pick 6b2481b`). It *also* processes the `fixup` command (`fixup c619268`), since it doesn't require any interaction. `fixup` merges the changes from `c619268` into the commit before it, `6b2481b`. Both changes will have the same commit message: `"Patch B"`.
|
||||
|
||||
Git 开始 `edit dd1475d` 操作，停止，然后将以下消息打印到终端：
|
||||
Git gets to the `edit dd1475d` operation, stops, and prints the following message to the terminal:
|
||||
|
||||
```shell
|
||||
You can amend the commit now, with
|
||||
@@ -107,28 +106,28 @@ Once you are satisfied with your changes, run
|
||||
git rebase --continue
|
||||
```
|
||||
|
||||
此时，您可以编辑项目中的任何文件以进行任何额外的更改。 对于您进行的每个更改，您都需要通过输入 `git commit --amend` 命令执行新提交。 完成所有更改后，您可以运行 `git rebase --continue`。
|
||||
At this point, you can edit any of the files in your project to make any additional changes. For each change you make, you'll need to perform a new commit, and you can do that by entering the `git commit --amend` command. When you're finished making all your changes, you can run `git rebase --continue`.
|
||||
|
||||
Git 随后开始执行 `reword 4ca2acc` 命令。 它会再次打开您的文本编辑器，并显示以下信息：
|
||||
Git then gets to the `reword 4ca2acc` command. It opens up your text editor one more time, and presents the following information:
|
||||
|
||||
```
|
||||
i cant' typ goods
|
||||
|
||||
# 请输入您的更改的提交消息。 开头
|
||||
# 为 '#' 的行将被忽略，并且空消息会中止提交。
|
||||
# 当前不在任何分支中。
|
||||
# 要进行提交的更改：
|
||||
# （使用 "git reset HEAD^1 <file>..." 取消暂存）
|
||||
# Please enter the commit message for your changes. Lines starting
|
||||
# with '#' will be ignored, and an empty message aborts the commit.
|
||||
# Not currently on any branch.
|
||||
# Changes to be committed:
|
||||
# (use "git reset HEAD^1 <file>..." to unstage)
|
||||
#
|
||||
# 已修改：a
|
||||
# modified: a
|
||||
#
|
||||
```
|
||||
|
||||
和以前一样，Git 显示提交消息供您进行编辑。 您可以更改文本 (`"i cant' typ goods"`)，保存该文件，然后关闭编辑器。 Git 将完成变基并将您返回终端。
|
||||
As before, Git is showing the commit message for you to edit. You can change the text (`"i cant' typ goods"`), save the file, and close the editor. Git will finish the rebase and return you to the terminal.
|
||||
|
||||
## 将变基的代码推送到 GitHub
|
||||
## Pushing rebased code to GitHub
|
||||
|
||||
由于您已更改 Git 历史记录，因此通常的 `git push origin` **不起**作用。 您需要通过“强制推送”最新更改来修改命令：
|
||||
Since you've altered Git history, the usual `git push origin` **will not** work. You'll need to modify the command by "force-pushing" your latest changes:
|
||||
|
||||
```shell
|
||||
# Don't override changes
|
||||
@@ -140,10 +139,10 @@ $ git push origin main --force
|
||||
|
||||
{% warning %}
|
||||
|
||||
强制推送具有严重的影响，因为它会更改分支提交的历史顺序。 请谨慎使用，尤其是您的仓库被多人访问时。
|
||||
Force pushing has serious implications because it changes the historical sequence of commits for the branch. Use it with caution, especially if your repository is being accessed by multiple people.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
* “[解决 Git 变基后的合并冲突](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)”
|
||||
* "[Resolving merge conflicts after a Git rebase](/github/getting-started-with-github/resolving-merge-conflicts-after-a-git-rebase)"
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Using GitHub
|
||||
intro: 'Explore {% data variables.product.company_short %}''s products from different platforms and devices.'
|
||||
redirect_from:
|
||||
- /articles/using-github
|
||||
- /github/getting-started-with-github/using-github/
|
||||
- /github/getting-started-with-github/using-github
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
title: Keyboard shortcuts
|
||||
intro: 'Nearly every page on {% data variables.product.prodname_dotcom %} has a keyboard shortcut to perform actions faster.'
|
||||
redirect_from:
|
||||
- /articles/using-keyboard-shortcuts/
|
||||
- /categories/75/articles/
|
||||
- /categories/keyboard-shortcuts/
|
||||
- /articles/using-keyboard-shortcuts
|
||||
- /categories/75/articles
|
||||
- /categories/keyboard-shortcuts
|
||||
- /articles/keyboard-shortcuts
|
||||
- /github/getting-started-with-github/keyboard-shortcuts
|
||||
- /github/getting-started-with-github/using-github/keyboard-shortcuts
|
||||
|
||||
@@ -1,23 +1,22 @@
|
||||
---
|
||||
title: 支持的浏览器
|
||||
title: Supported browsers
|
||||
redirect_from:
|
||||
- /articles/why-doesn-t-graphs-work-with-ie-8/
|
||||
- /articles/why-don-t-graphs-work-with-ie8/
|
||||
- /articles/why-doesn-t-graphs-work-with-ie-8
|
||||
- /articles/why-don-t-graphs-work-with-ie8
|
||||
- /articles/supported-browsers
|
||||
- /github/getting-started-with-github/supported-browsers
|
||||
- /github/getting-started-with-github/using-github/supported-browsers
|
||||
intro: '我们将 {% data variables.product.product_name %} 设计为支持最新的 Web 浏览器。 我们支持最新版本的 [Chrome](https://www.google.com/chrome/)、[Firefox](http://www.mozilla.org/firefox/)、[Safari](http://www.apple.com/safari/) 和 [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge)。'
|
||||
intro: 'We design {% data variables.product.product_name %} to support the latest web browsers. We support the current versions of [Chrome](https://www.google.com/chrome/), [Firefox](http://www.mozilla.org/firefox/), [Safari](http://www.apple.com/safari/), and [Microsoft Edge](https://www.microsoft.com/en-us/windows/microsoft-edge).'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
---
|
||||
|
||||
## Firefox Extended Support Release
|
||||
|
||||
我们尽最大努力支持 Firefox 的最新 [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR)。 较旧版本的 Firefox 可能会禁用 {% data variables.product.product_name %} 上的某些功能，因此需要最新版本的 Firefox。
|
||||
We do our best to support Firefox's latest [Extended Support Release](https://www.mozilla.org/en-US/firefox/organizations/) (ESR). Older versions of Firefox may disable some features on {% data variables.product.product_name %} and require the latest version of Firefox.
|
||||
|
||||
## 测试版和开发者版本
|
||||
## Beta and developer builds
|
||||
|
||||
您可能会在我们支持的浏览器的测试版和开发者版本中遇到意外的漏洞。 如果您在这些未发布版本之一中遇到 {% data variables.product.product_name %} 上的漏洞，请确认同一浏览器的稳定版本中也存在该漏洞。 如果漏洞仅在不稳定版本中存在，请考虑向浏览器开发者报告该漏洞。
|
||||
You may encounter unexpected bugs in beta and developer builds of our supported browsers. If you encounter a bug on {% data variables.product.product_name %} in one of these unreleased builds, please verify that it also exists in the stable version of the same browser. If the bug only exists in the unstable version, consider reporting the bug to the browser developer.
|
||||
|
||||
@@ -4,7 +4,7 @@ redirect_from:
|
||||
- /articles/
|
||||
- /common-issues-and-questions/
|
||||
- /troubleshooting-common-issues/
|
||||
intro: 适用于软件开发者、设计师和项目经理的文档、指南和帮助主题。 涵盖 Git、拉取请求、问题、wiki、gist 和充分使用 GitHub 进行开发所需的一切。
|
||||
intro: 'Documentation, guides, and help topics for software developers, designers, and project managers. Covers using Git, pull requests, issues, wikis, gists, and everything you need to make the most of GitHub for development.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -20,6 +20,4 @@ children:
|
||||
- /understanding-how-github-uses-and-protects-your-data
|
||||
- /site-policy
|
||||
- /site-policy-deprecated
|
||||
- /setting-up-and-managing-your-enterprise
|
||||
---
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 使用分页遍历
|
||||
intro: 通过一些使用搜索 API 的示例，探讨如何使用分页来管理响应。
|
||||
title: Traversing with pagination
|
||||
intro: Explore how to use pagination to manage your responses with some examples using the Search API.
|
||||
redirect_from:
|
||||
- /guides/traversing-with-pagination/
|
||||
- /v3/guides/traversing-with-pagination
|
||||
@@ -11,75 +11,105 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
shortTitle: 使用分页遍历
|
||||
shortTitle: Traverse with pagination
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 为开发人员提供了丰富的信息供他们使用。 在很多时候，您甚至会发现自己请求的信息_太多_，为了满足我们的服务器，API 会自动[对请求的项目进行分页][pagination]。
|
||||
The {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API provides a vast wealth of information for developers to consume.
|
||||
Most of the time, you might even find that you're asking for _too much_ information,
|
||||
and in order to keep our servers happy, the API will automatically [paginate the requested items](/rest/overview/resources-in-the-rest-api#pagination).
|
||||
|
||||
在本指南中，我们将对 搜索 API 进行一些调用，并使用分页遍历结果。 您可以在[平台样本][platform samples]仓库中找到此项目的完整源代码。
|
||||
In this guide, we'll make some calls to the Search API, and iterate over
|
||||
the results using pagination. You can find the complete source code for this project
|
||||
in the [platform-samples][platform samples] repository.
|
||||
|
||||
{% data reusables.rest-api.dotcom-only-guide-note %}
|
||||
|
||||
## 分页基础知识
|
||||
## Basics of Pagination
|
||||
|
||||
首先需要了解有关接收分页条目的一些事实：
|
||||
To start with, it's important to know a few facts about receiving paginated items:
|
||||
|
||||
1. 不同的 API 调用响应具有不同的默认值。 例如，调用[列出公共仓库](/rest/reference/repos#list-public-repositories)将提供以 30 项为单位的分页结果，而调用 GitHub 搜索 API 将提供以 100 项为单位的分页结果
|
||||
2. 您可以指定要接收的条目数（最多 100 个）；但是，
|
||||
3. 出于技术原因，并非每个端点的行为都相同。 例如，[事件](/rest/reference/activity#events)不允许设置要接收的最大条目数量。 请务必阅读关于如何处理特定端点分页结果的文档。
|
||||
1. Different API calls respond with different defaults. For example, a call to
|
||||
[List public repositories](/rest/reference/repos#list-public-repositories)
|
||||
provides paginated items in sets of 30, whereas a call to the GitHub Search API
|
||||
provides items in sets of 100
|
||||
2. You can specify how many items to receive (up to a maximum of 100); but,
|
||||
3. For technical reasons, not every endpoint behaves the same. For example,
|
||||
[events](/rest/reference/activity#events) won't let you set a maximum for items to receive.
|
||||
Be sure to read the documentation on how to handle paginated results for specific endpoints.
|
||||
|
||||
有关分页的信息包含在 API 调用的 [Link 标头](https://datatracker.ietf.org/doc/html/rfc5988)中。 例如，我们向搜索 API 发出一个 curl 请求，以查明 Mozilla 项目使用短语 `addClass` 的次数：
|
||||
Information about pagination is provided in [the Link header](https://datatracker.ietf.org/doc/html/rfc5988)
|
||||
of an API call. For example, let's make a curl request to the search API, to find
|
||||
out how many times Mozilla projects use the phrase `addClass`:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla"
|
||||
```
|
||||
|
||||
`-I` 参数表示我们只关注标头，而不关注实际内容。 在检查结果时，您会注意到 Link 标头中的一些信息，如下所示：
|
||||
The `-I` parameter indicates that we only care about the headers, not the actual
|
||||
content. In examining the result, you'll notice some information in the Link header
|
||||
that looks like this:
|
||||
|
||||
链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=2>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last"
|
||||
|
||||
我们来分解说明。 `rel="next"` 表示下一页是 `page=2`。 这是合理的，因为在默认情况下，所有分页查询都是从第 `1` 页开始。`rel="last"` 提供了更多信息，指示结果的最后一页是第 `34` 页。 因此，我们还有 33 页有关 `addClass` 的信息可用。 不错！
|
||||
Let's break that down. `rel="next"` says that the next page is `page=2`. This makes
|
||||
sense, since by default, all paginated queries start at page `1.` `rel="last"`
|
||||
provides some more information, stating that the last page of results is on page `34`.
|
||||
Thus, we have 33 more pages of information about `addClass` that we can consume.
|
||||
Nice!
|
||||
|
||||
**始终**信赖提供给您的这些链接关系。 不要试图猜测或构建自己的 URL。
|
||||
**Always** rely on these link relations provided to you. Don't try to guess or construct your own URL.
|
||||
|
||||
### 浏览页面
|
||||
### Navigating through the pages
|
||||
|
||||
现在您知道要接收多少页面，可以开始浏览页面以使用结果。 您可以通过传递 `page` 参数进行浏览。 默认情况下，`page` 总是从 `1` 开始。 让我们跳到第 14 页，看看会发生什么：
|
||||
Now that you know how many pages there are to receive, you can start navigating
|
||||
through the pages to consume the results. You do this by passing in a `page`
|
||||
parameter. By default, `page` always starts at `1`. Let's jump ahead to page 14
|
||||
and see what happens:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&page=14"
|
||||
```
|
||||
|
||||
以下是再次出现的 Link 标头：
|
||||
Here's the link header once more:
|
||||
|
||||
链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&page=15>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=34>; rel="last",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=1>; rel="first",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&page=13>; rel="prev"
|
||||
|
||||
果然，`rel="next"` 是 15，而 `rel="last"` 仍是 34。 但是现在我们得到了更多信息：`rel="first"` 表示_第一_页的 URL，更重要的是，`rel="prev"` 让您知道了上一页的页码。 根据这些信息，您可以构造一些 UI，使用户可以在 API 调用结果列表的第一页、上一页、下一页或最后一页之间跳转。
|
||||
As expected, `rel="next"` is at 15, and `rel="last"` is still 34. But now we've
|
||||
got some more information: `rel="first"` indicates the URL for the _first_ page,
|
||||
and more importantly, `rel="prev"` lets you know the page number of the previous
|
||||
page. Using this information, you could construct some UI that lets users jump
|
||||
between the first, previous, next, or last list of results in an API call.
|
||||
|
||||
### 更改接收的条目数量
|
||||
### Changing the number of items received
|
||||
|
||||
通过传递 `per_page` 参数，您可以指定希望每页返回多少个条目，最多 100 个。 我们来尝试请求 50 个关于 `addClass` 的条目：
|
||||
By passing the `per_page` parameter, you can specify how many items you want
|
||||
each page to return, up to 100 items. Let's try asking for 50 items about `addClass`:
|
||||
|
||||
```shell
|
||||
$ curl -I "https://api.github.com/search/code?q=addClass+user:mozilla&per_page=50"
|
||||
```
|
||||
|
||||
请注意它对标头响应的影响：
|
||||
Notice what it does to the header response:
|
||||
|
||||
链接：<https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
|
||||
Link: <https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=2>; rel="next",
|
||||
<https://api.github.com/search/code?q=addClass+user%3Amozilla&per_page=50&page=20>; rel="last"
|
||||
|
||||
您可能已经猜到了，`rel="last"` 信息表明最后一页现在是第 20 页。 这是因为我们要求每页提供更多的结果相关信息。
|
||||
As you might have guessed, the `rel="last"` information says that the last page
|
||||
is now 20. This is because we are asking for more information per page about
|
||||
our results.
|
||||
|
||||
## 使用信息
|
||||
## Consuming the information
|
||||
|
||||
您不希望仅仅为了能够处理分页而进行低级的 curl 调用，所以我们来编写一个 Ruby 小脚本来完成上述所有任务。
|
||||
You don't want to be making low-level curl calls just to be able to work with
|
||||
pagination, so let's write a little Ruby script that does everything we've
|
||||
just described above.
|
||||
|
||||
与往常一样，首选我们需要使用 [GitHub 的 Octokit.rb][octokit.rb] Ruby 库，并传递我们的 [个人访问令牌][personal token]：
|
||||
As always, first we'll require [GitHub's Octokit.rb][octokit.rb] Ruby library, and
|
||||
pass in our [personal access token][personal token]:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -89,16 +119,26 @@ require 'octokit'
|
||||
client = Octokit::Client.new :access_token => ENV['MY_PERSONAL_TOKEN']
|
||||
```
|
||||
|
||||
接下来，我们将使用 Octokit 的 `search_code` 方法执行搜索。 与使用 `curl` 不同的是，我们还可以立即检索结果数量，所以我们输入以下代码：
|
||||
Next, we'll execute the search, using Octokit's `search_code` method. Unlike
|
||||
using `curl`, we can also immediately retrieve the number of results, so let's
|
||||
do that:
|
||||
|
||||
``` ruby
|
||||
results = client.search_code('addClass user:mozilla')
|
||||
total_count = results.total_count
|
||||
```
|
||||
|
||||
现在，我们来获取最后一页的页码 - 类似于链接标头中的 `page=34>; rel="last"` 信息。 Octokit.rb 通过“[超媒体连接关系][hypermedia-relations]”的实现来支持分页信息。 我们不会对这种关系展开详细讨论，只想提醒您，`results` 变量中的每个元素都有一个被称为 `rels` 的哈希，它可能包含有关 `:next`、`:last`、`:first` 和 `:prev` 的信息，具体取决于您所得结果。 这些关系还包含通过调用 `rels[:last].href` 所得 URL 的相关信息。
|
||||
Now, let's grab the number of the last page, similar to `page=34>; rel="last"`
|
||||
information in the link header. Octokit.rb support pagination information through
|
||||
an implementation called "[Hypermedia link relations][hypermedia-relations]."
|
||||
We won't go into detail about what that is, but, suffice to say, each element
|
||||
in the `results` variable has a hash called `rels`, which can contain information
|
||||
about `:next`, `:last`, `:first`, and `:prev`, depending on which result you're
|
||||
on. These relations also contain information about the resulting URL, by calling
|
||||
`rels[:last].href`.
|
||||
|
||||
知道了这一点后，我们来获取最后一个结果的页码，并将所有这些信息呈现给用户：
|
||||
Knowing this, let's grab the page number of the last result, and present all
|
||||
this information to the user:
|
||||
|
||||
``` ruby
|
||||
last_response = client.last_response
|
||||
@@ -107,7 +147,13 @@ number_of_pages = last_response.rels[:last].href.match(/page=(\d+).*$/)[1]
|
||||
puts "There are #{total_count} results, on #{number_of_pages} pages!"
|
||||
```
|
||||
|
||||
最后，我们来遍历结果。 您可以使用 `for i in 1..number_of_pages.to_i` 循环进行浏览，但我们这次将根据 `rels[:next]` 标头来检索每一页的信息。 为简单起见，我们只获取每个页面中第一个结果的文件路径。 为此，我们需要一个循环；在每个循环的最后，我们根据 `rels[:next]` 信息来检索下一页的数据集。 当没有 `rels[:next]` 信息可用时（也就是说，我们到达了 `rels[:last]`），循环将结束。 如下所示：
|
||||
Finally, let's iterate through the results. You could do this with a loop `for i in 1..number_of_pages.to_i`,
|
||||
but instead, let's follow the `rels[:next]` headers to retrieve information from
|
||||
each page. For the sake of simplicity, let's just grab the file path of the first
|
||||
result from each page. To do this, we'll need a loop; and at the end of every loop,
|
||||
we'll retrieve the data set for the next page by following the `rels[:next]` information.
|
||||
The loop will finish when there is no `rels[:next]` information to consume (in other
|
||||
words, we are at `rels[:last]`). It might look something like this:
|
||||
|
||||
``` ruby
|
||||
puts last_response.data.items.first.path
|
||||
@@ -117,7 +163,9 @@ until last_response.rels[:next].nil?
|
||||
end
|
||||
```
|
||||
|
||||
使用 Octokit.rb 更改每页的条目数非常简单。 只需将 `per_page` 选项哈希传递给初始客户端构造函数。 之后，您的代码应保持不变：
|
||||
Changing the number of items per page is extremely simple with Octokit.rb. Simply
|
||||
pass a `per_page` options hash to the initial client construction. After that,
|
||||
your code should remain intact:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -144,15 +192,17 @@ until last_response.rels[:next].nil?
|
||||
end
|
||||
```
|
||||
|
||||
## 构造分页链接
|
||||
## Constructing Pagination Links
|
||||
|
||||
一般来说，使用分页时，您的目标不是要抓住所有可能的结果，而是要产生一组导航，如下所示：
|
||||
Normally, with pagination, your goal isn't to concatenate all of the possible
|
||||
results, but rather, to produce a set of navigation, like this:
|
||||
|
||||
|
||||
|
||||
|
||||
让我们勾勒出一个可能需要做什么的微观版本。
|
||||
Let's sketch out a micro-version of what that might entail.
|
||||
|
||||
根据上面的代码，我们已经知道可以从第一次调用的分页结果中获取 `number_of_pages`。
|
||||
From the code above, we already know we can get the `number_of_pages` in the
|
||||
paginated results from the first call:
|
||||
|
||||
``` ruby
|
||||
require 'octokit'
|
||||
@@ -171,7 +221,7 @@ puts last_response.rels[:last].href
|
||||
puts "There are #{total_count} results, on #{number_of_pages} pages!"
|
||||
```
|
||||
|
||||
我们可以从其中构造美观的数字框 ASCII 表示形式：
|
||||
From there, we can construct a beautiful ASCII representation of the number boxes:
|
||||
``` ruby
|
||||
numbers = ""
|
||||
for i in 1..number_of_pages.to_i
|
||||
@@ -180,7 +230,8 @@ end
|
||||
puts numbers
|
||||
```
|
||||
|
||||
我们通过构造一个随机数来模拟用户单击其中一个框：
|
||||
Let's simulate a user clicking on one of these boxes, by constructing a random
|
||||
number:
|
||||
|
||||
``` ruby
|
||||
random_page = Random.new
|
||||
@@ -189,13 +240,15 @@ random_page = random_page.rand(1..number_of_pages.to_i)
|
||||
puts "A User appeared, and clicked number #{random_page}!"
|
||||
```
|
||||
|
||||
现在我们有了页码，可通过传递 `:page` 选项，使用 Octokit 明确检索各个页面：
|
||||
Now that we have a page number, we can use Octokit to explicitly retrieve that
|
||||
individual page, by passing the `:page` option:
|
||||
|
||||
``` ruby
|
||||
clicked_results = client.search_code('addClass user:mozilla', :page => random_page)
|
||||
```
|
||||
|
||||
如果我们想弄得花哨一些，还可以抓住上下页，以生成后退 (`<<`) 和前进 (`>>`) 元素的链接：
|
||||
If we wanted to get fancy, we could also grab the previous and next pages, in
|
||||
order to generate links for back (`<<`) and forward (`>>`) elements:
|
||||
|
||||
``` ruby
|
||||
prev_page_href = client.last_response.rels[:prev] ? client.last_response.rels[:prev].href : "(none)"
|
||||
@@ -210,3 +263,4 @@ puts "The next page link is #{next_page_href}"
|
||||
[octokit.rb]: https://github.com/octokit/octokit.rb
|
||||
[personal token]: /articles/creating-an-access-token-for-command-line-use
|
||||
[hypermedia-relations]: https://github.com/octokit/octokit.rb#pagination
|
||||
[listing commits]: /rest/reference/repos#list-commits
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
date: '2021-12-07'
|
||||
intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
|
||||
intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."<br><br>**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.
|
||||
sections:
|
||||
features:
|
||||
-
|
||||
@@ -159,6 +159,7 @@ sections:
|
||||
#bugs:
|
||||
#- PLACEHOLDER
|
||||
known_issues:
|
||||
- After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- 自定义防火墙规则在升级过程中被删除。
|
||||
- Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。
|
||||
|
||||
Reference in New Issue
Block a user