New translation batch for cn (#33317)
This commit is contained in:
docubot
@@ -366,7 +366,6 @@ translations/zh-CN/data/reusables/actions/hardware-requirements-3.6.md,file dele
|
||||
translations/zh-CN/data/reusables/actions/link-to-example-library.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/minio-gateways-removal.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/perform-blob-storage-precheck.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/reusable-workflows-ghes-beta.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/self-hosted-runner-groups-navigate-to-repo-org-enterprise.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/apps/metadata-permissions.md,file deleted because it no longer exists in main
|
||||
@@ -407,6 +406,7 @@ translations/zh-CN/data/reusables/getting-started/learning-lab.md,file deleted b
|
||||
translations/zh-CN/data/reusables/open-source/open-source-learning-lab.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/pages/pages-builds-with-github-actions-public-beta.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/repositories/squash-and-rebase-linear-commit-hisitory.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/rest-reference/apps/oauth-applications.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/rest-reference/branches/branch-protection.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/rest-reference/checks/runs.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/rest-reference/deployments/statuses.md,file deleted because it no longer exists in main
|
||||
@@ -435,20 +435,20 @@ translations/zh-CN/data/reusables/security-center/beta.md,file deleted because i
|
||||
translations/zh-CN/data/reusables/server-statistics/release-phase.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md,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,broken liquid tags
|
||||
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/about-notifications.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md,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-organizations-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/managing-your-profile-readme.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/showing-your-private-contributions-and-achievements-on-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/viewing-contributions-on-your-profile.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/inviting-collaborators-to-a-personal-repository.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-a-collaborator-from-a-personal-repository.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/removing-yourself-from-a-collaborators-repository.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/index.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/remembering-your-github-username-or-email.md,broken liquid tags
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/changing-your-github-username.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-personal-account-settings/managing-security-and-analysis-settings-for-your-personal-account.md,rendering error
|
||||
@@ -457,9 +457,9 @@ translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-pers
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-membership-in-organizations/requesting-organization-approval-for-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/best-practices-for-leaving-your-company.md,rendering error
|
||||
translations/zh-CN/content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/converting-a-user-into-an-organization.md,rendering error
|
||||
translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,rendering error
|
||||
translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,rendering error
|
||||
translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,rendering error
|
||||
translations/zh-CN/content/actions/automating-builds-and-tests/about-continuous-integration.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/creating-actions/creating-a-composite-action.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/creating-actions/creating-a-docker-container-action.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/creating-actions/creating-a-javascript-action.md,rendering error
|
||||
translations/zh-CN/content/actions/creating-actions/metadata-syntax-for-github-actions.md,rendering error
|
||||
translations/zh-CN/content/actions/deployment/about-deployments/about-continuous-deployment.md,rendering error
|
||||
@@ -492,11 +492,11 @@ translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing-
|
||||
translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error
|
||||
translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error
|
||||
translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,rendering error
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,rendering error
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
translations/zh-CN/content/actions/migrating-to-github-actions/automating-migration-with-github-actions-importer.md,rendering error
|
||||
translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,rendering error
|
||||
translations/zh-CN/content/actions/monitoring-and-troubleshooting-workflows/viewing-job-execution-time.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,rendering error
|
||||
translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/quickstart.md,rendering error
|
||||
@@ -516,76 +516,71 @@ translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md,rend
|
||||
translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error
|
||||
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error
|
||||
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error
|
||||
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/command-line-utilities.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-applications.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-email-for-notifications.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-github-pages-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-rate-limits.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-ssh-connections-to-your-instance.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/enabling-private-mode.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,rendering error
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/configuration/configuring-your-enterprise/troubleshooting-tls-errors.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/caching-repositories/about-repository-caching.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/caching-repositories/configuring-a-repository-cache.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/caching-repositories/index.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/configuring-clustering/cluster-network-configuration.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,rendering error
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/accessing-the-monitor-dashboard.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/configuring-collectd.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/generating-a-health-check-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/monitoring-using-snmp.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/monitoring-your-appliance/recommended-alert-thresholds.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/enabling-automatic-update-checks.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-storage.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/advanced-configuration-and-troubleshooting/using-a-staging-environment.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/changing-authentication-methods.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise/downloading-your-enterprise-accounts-single-sign-on-recovery-codes.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/configuring-built-in-authentication.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/disabling-unauthenticated-sign-ups.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,rendering error
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/enabling-encrypted-assertions.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/saml-configuration-reference.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/updating-a-users-saml-nameid.md,broken liquid tags
|
||||
@@ -594,73 +589,71 @@ translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-ser
|
||||
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-google-cloud-platform.md,rendering error
|
||||
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-openstack-kvm.md,rendering error
|
||||
translations/zh-CN/content/admin/installation/setting-up-a-github-enterprise-server-instance/installing-github-enterprise-server-on-vmware.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/exporting-server-statistics.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/managing-global-webhooks.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/searching-the-audit-log-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-data-residency.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-data-residency.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/overview/about-enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/about-github-enterprise-server.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/overview/about-github-for-enterprises.md,rendering error
|
||||
translations/zh-CN/content/admin/overview/system-overview.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-azure-blob-storage.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-aws.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/packages/enabling-github-packages-with-minio.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/packages/getting-started-with-github-packages-for-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/packages/migrating-your-enterprise-to-the-container-registry-from-the-docker-registry.md,rendering error
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,rendering error
|
||||
translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,rendering error
|
||||
translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/adding-people-to-teams.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/continuous-integration-using-jenkins.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/creating-teams.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-organizations-in-your-enterprise/restoring-a-deleted-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/configuring-git-large-file-storage-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-and-managing-a-users-saml-access-to-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,rendering error
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/exporting-migration-data-from-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/index.md,broken liquid tags
|
||||
translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/migrating-data-to-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on.md,rendering error
|
||||
translations/zh-CN/content/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on.md,rendering error
|
||||
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account.md,rendering error
|
||||
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.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/connecting-to-github-with-ssh/testing-your-ssh-connection.md,rendering error
|
||||
translations/zh-CN/content/authentication/connecting-to-github-with-ssh/testing-your-ssh-connection.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/about-authentication-to-github.md,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/preventing-unauthorized-access.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/creating-a-strong-password.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/preventing-unauthorized-access.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/reviewing-your-deploy-keys.md,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/sudo-mode.md,rendering error
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/sudo-mode.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/keeping-your-account-and-data-secure/updating-your-github-access-credentials.md,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/adding-a-gpg-key-to-your-github-account.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/associating-an-email-with-your-gpg-key.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/displaying-verification-statuses-for-all-of-your-commits.md,rendering error
|
||||
translations/zh-CN/content/authentication/managing-commit-signature-verification/index.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,rendering error
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/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/index.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/securing-your-account-with-two-factor-authentication-2fa/recovering-your-account-if-you-lose-your-2fa-credentials.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,rendering error
|
||||
translations/zh-CN/content/authentication/troubleshooting-commit-signature-verification/checking-your-commit-and-tag-signature-verification-status.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-agent-admitted-failure-to-sign.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/error-key-already-in-use.md,broken liquid tags
|
||||
translations/zh-CN/content/authentication/troubleshooting-ssh/recovering-your-ssh-key-passphrase.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/about-billing-for-github-advanced-security.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot.md,broken liquid tags
|
||||
@@ -669,13 +662,13 @@ translations/zh-CN/content/billing/managing-billing-for-github-packages/about-bi
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,rendering error
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server.md,broken liquid tags
|
||||
translations/zh-CN/content/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/adopting-github-advanced-security-at-scale/phase-6-rollout-and-scale-secret-scanning.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error
|
||||
@@ -685,12 +678,12 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/triaging-code-scanning-alerts-in-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,rendering error
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags
|
||||
translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error
|
||||
translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error
|
||||
@@ -719,10 +712,7 @@ translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-
|
||||
translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error
|
||||
translations/zh-CN/content/code-security/secret-scanning/secret-scanning-patterns.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error
|
||||
translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md,rendering error
|
||||
@@ -732,54 +722,45 @@ translations/zh-CN/content/code-security/supply-chain-security/understanding-you
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md,rendering error
|
||||
translations/zh-CN/content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-the-dependency-graph.md,broken liquid tags
|
||||
translations/zh-CN/content/codespaces/codespaces-reference/security-in-github-codespaces.md,broken liquid tags
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository.md,rendering error
|
||||
translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template.md,rendering error
|
||||
translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,rendering error
|
||||
translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge.md,rendering error
|
||||
translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-prebuilds.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,rendering error
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags
|
||||
translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,rendering error
|
||||
translations/zh-CN/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository.md,rendering error
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md,broken liquid tags
|
||||
translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags
|
||||
translations/zh-CN/content/copilot/quickstart.md,broken liquid tags
|
||||
translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,rendering error
|
||||
translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags
|
||||
translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/about-connections-to-github.md,broken liquid tags
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,rendering error
|
||||
translations/zh-CN/content/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/authenticating-with-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/managing-allowed-ip-addresses-for-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/building-github-apps/rate-limits-for-github-apps.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/apps/building-oauth-apps/scopes-for-oauth-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/about-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,rendering error
|
||||
translations/zh-CN/content/developers/apps/getting-started-with-apps/setting-up-your-development-environment-to-create-a-github-app.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/apps/guides/using-the-github-api-in-your-app.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/requirements-for-listing-an-app.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/github-marketplace/creating-apps-for-github-marketplace/security-best-practices-for-apps.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,rendering error
|
||||
translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/github-marketplace/selling-your-app-on-github-marketplace/pricing-plans-for-github-marketplace-apps.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/overview/about-githubs-apis.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/overview/managing-deploy-keys.md,rendering error
|
||||
translations/zh-CN/content/developers/overview/managing-deploy-keys.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/overview/secret-scanning-partner-program.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/webhooks-and-events/events/issue-event-types.md,broken liquid tags
|
||||
translations/zh-CN/content/developers/webhooks-and-events/webhooks/webhook-events-and-payloads.md,rendering error
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,rendering error
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,rendering error
|
||||
translations/zh-CN/content/discussions/guides/finding-your-discussions.md,rendering error
|
||||
translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,rendering error
|
||||
translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md,rendering error
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/collaborating-with-maintainers-using-discussions.md,broken liquid tags
|
||||
translations/zh-CN/content/discussions/collaborating-with-your-community-using-discussions/participating-in-a-discussion.md,broken liquid tags
|
||||
translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags
|
||||
translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags
|
||||
translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/about-using-makecode-arcade-with-github-classroom.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/integrate-github-classroom-with-an-ide.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-an-individual-assignment.md,rendering error
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/learn-with-github-classroom/view-autograding-results.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/manage-classrooms.md,broken liquid tags
|
||||
translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/use-the-git-and-github-starter-assignment.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,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/customizing-your-github-workflow/exploring-integrations/github-extensions-and-integrations.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/exploring-projects-on-github/following-organizations.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/about-remote-repositories.md,rendering error
|
||||
translations/zh-CN/content/get-started/getting-started-with-git/associating-text-editors-with-git.md,broken liquid tags
|
||||
@@ -787,26 +768,24 @@ translations/zh-CN/content/get-started/getting-started-with-git/caching-your-git
|
||||
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/getting-started-with-git/why-is-git-always-asking-for-my-password.md,rendering error
|
||||
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,rendering error
|
||||
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,rendering error
|
||||
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/adding-locally-hosted-code-to-github.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-git-repository-using-the-command-line.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/importing-your-projects-to-github/importing-source-code-to-github/importing-a-repository-with-github-importer.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/access-permissions-on-github.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/learning-about-github/githubs-products.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-ae.md,rendering error
|
||||
translations/zh-CN/content/get-started/learning-about-github/types-of-github-accounts.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,rendering error
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/quickstart/be-social.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/create-a-repo.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error
|
||||
translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.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-rebase.md,broken liquid tags
|
||||
translations/zh-CN/content/get-started/using-github/github-mobile.md,rendering error
|
||||
translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,rendering error
|
||||
translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags
|
||||
@@ -820,7 +799,7 @@ translations/zh-CN/content/graphql/guides/forming-calls-with-graphql.md,renderin
|
||||
translations/zh-CN/content/graphql/guides/introduction-to-graphql.md,broken liquid tags
|
||||
translations/zh-CN/content/graphql/guides/managing-enterprise-accounts.md,rendering error
|
||||
translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
|
||||
translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,rendering error
|
||||
translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
|
||||
translations/zh-CN/content/graphql/reference/enums.md,rendering error
|
||||
translations/zh-CN/content/graphql/reference/input-objects.md,rendering error
|
||||
translations/zh-CN/content/graphql/reference/interfaces.md,rendering error
|
||||
@@ -830,16 +809,15 @@ translations/zh-CN/content/graphql/reference/unions.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/changing-project-board-visibility.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/copying-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/organizing-your-work-with-project-boards/managing-project-boards/creating-a-project-board.md,rendering error
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic.md,rendering error
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,rendering error
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,rendering error
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/managing-organization-settings/deleting-an-organization-account.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-organization-settings/disabling-project-boards-in-your-organization.md,rendering error
|
||||
@@ -850,7 +828,7 @@ translations/zh-CN/content/organizations/managing-organization-settings/managing
|
||||
translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team.md,rendering error
|
||||
@@ -863,7 +841,6 @@ translations/zh-CN/content/packages/learn-github-packages/introduction-to-github
|
||||
translations/zh-CN/content/packages/learn-github-packages/publishing-a-package.md,rendering error
|
||||
translations/zh-CN/content/packages/learn-github-packages/viewing-packages.md,rendering error
|
||||
translations/zh-CN/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
|
||||
translations/zh-CN/content/packages/quickstart.md,rendering error
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md,rendering error
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry.md,rendering error
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,rendering error
|
||||
@@ -874,31 +851,31 @@ translations/zh-CN/content/packages/working-with-a-github-packages-registry/work
|
||||
translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,rendering error
|
||||
translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/about-custom-domains-and-github-pages.md,broken liquid tags
|
||||
translations/zh-CN/content/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
|
||||
translations/zh-CN/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/addressing-merge-conflicts/resolving-a-merge-conflict-using-the-command-line.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/keeping-your-pull-request-in-sync-with-the-base-branch.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,rendering error
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-on-behalf-of-an-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/commit-exists-on-github-but-not-in-my-local-clone.md,broken liquid tags
|
||||
translations/zh-CN/content/pull-requests/committing-changes-to-your-project/troubleshooting-commits/why-are-my-commits-linked-to-the-wrong-user.md,rendering error
|
||||
translations/zh-CN/content/repositories/archiving-a-github-repository/archiving-repositories.md,rendering error
|
||||
translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,rendering error
|
||||
translations/zh-CN/content/repositories/archiving-a-github-repository/backing-up-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/archiving-a-github-repository/referencing-and-citing-content.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-merging-for-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-rebasing-for-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/configuring-commit-squashing-for-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/index.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-auto-merge-for-pull-requests-in-your-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-suggestions-to-update-pull-request-branches.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches.md,rendering error
|
||||
@@ -907,29 +884,25 @@ translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/troubleshooting-required-status-checks.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/changing-the-default-branch.md,rendering error
|
||||
translations/zh-CN/content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/cloning-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/restoring-a-deleted-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/transferring-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,rendering error
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/about-releases.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/comparing-releases.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/linking-to-releases.md,rendering error
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/viewing-activity-and-data-for-your-repository/understanding-connections-between-repositories.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/viewing-a-file.md,rendering error
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-files/adding-a-file-to-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/working-with-files/managing-large-files/about-large-files-on-github.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/getting-permanent-links-to-files.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/apps/oauth-applications.md,rendering error
|
||||
translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags
|
||||
@@ -955,14 +928,15 @@ translations/zh-CN/content/rest/overview/other-authentication-methods.md,renderi
|
||||
translations/zh-CN/content/rest/overview/permissions-required-for-github-apps.md,rendering error
|
||||
translations/zh-CN/content/rest/packages.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/projects/projects.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/scim.md,rendering error
|
||||
translations/zh-CN/content/rest/teams/team-sync.md,rendering error
|
||||
translations/zh-CN/content/rest/scim.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/teams/team-sync.md,broken liquid tags
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-for-repositories.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/managing-your-sponsorship-tiers.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,rendering error
|
||||
translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,rendering error
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
|
||||
translations/zh-CN/content/support/contacting-github-support/providing-data-to-github-support.md,broken liquid tags
|
||||
translations/zh-CN/content/support/contacting-github-support/viewing-and-updating-support-tickets.md,broken liquid tags
|
||||
translations/zh-CN/content/support/learning-about-github-support/about-github-premium-support.md,rendering error
|
||||
translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,rendering error
|
||||
translations/zh-CN/data/glossaries/external.yml,broken liquid tags
|
||||
@@ -984,19 +958,21 @@ translations/zh-CN/data/release-notes/enterprise-server/3-4/7.yml,rendering erro
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-4/8.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-5/5.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/cache-default-size.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/cache-default-size.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/changing-the-access-policy-of-a-runner-group.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/changing-the-name-of-a-runner-group.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/create-runner-group.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/creating-a-runner-group-for-an-organization.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/disabling-github-actions.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/enterprise-common-prereqs.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/enterprise-marketplace-actions.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/github-connect-resolution.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/enterprise-postinstall-nextsteps.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/github-connect-resolution.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/jobs/section-using-conditions-to-control-job-execution.md,broken liquid tags
|
||||
@@ -1004,6 +980,7 @@ translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,rendering e
|
||||
translations/zh-CN/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/reusable-workflows-enterprise-beta.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/reusable-workflows.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/runner-groups-add-to-enterprise-first-steps.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/self-hosted-runner-add-to-enterprise.md,rendering error
|
||||
@@ -1016,11 +993,11 @@ translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-pages-cus
|
||||
translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runner-groups.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/sidebar-secret.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/upgrade-runners-before-upgrade-ghes.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/workflow-template-overview.md,rendering error
|
||||
translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,rendering error
|
||||
translations/zh-CN/data/reusables/advanced-security/about-committer-numbers-ghec-ghes.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/advanced-security/about-ghas-organization-policy.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
|
||||
translations/zh-CN/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
|
||||
@@ -1028,9 +1005,9 @@ translations/zh-CN/data/reusables/advanced-security/secret-scanning-push-protect
|
||||
translations/zh-CN/data/reusables/apps/user-to-server-rate-limits.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_org_admins.md,rendering error
|
||||
translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md,rendering error
|
||||
translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,rendering error
|
||||
translations/zh-CN/data/reusables/classroom/about-autograding.md,rendering error
|
||||
translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,rendering error
|
||||
translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error
|
||||
translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error
|
||||
translations/zh-CN/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error
|
||||
@@ -1038,7 +1015,7 @@ translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-
|
||||
translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/run-additional-queries.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,rendering error
|
||||
translations/zh-CN/data/reusables/code-scanning/what-is-codeql-cli.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/codespaces/customize-vcpus-and-ram.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/codespaces/next-steps-adding-devcontainer.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/codespaces/prebuilds-crossreference.md,broken liquid tags
|
||||
@@ -1051,15 +1028,15 @@ translations/zh-CN/data/reusables/dependabot/dependabot-alerts-filters.md,render
|
||||
translations/zh-CN/data/reusables/dependabot/enabling-disabling-dependency-graph-private-repo.md,rendering error
|
||||
translations/zh-CN/data/reusables/dependabot/sidebar-secret.md,rendering error
|
||||
translations/zh-CN/data/reusables/dependabot/supported-package-managers.md,rendering error
|
||||
translations/zh-CN/data/reusables/desktop/get-an-account.md,rendering error
|
||||
translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,rendering error
|
||||
translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,rendering error
|
||||
translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,rendering error
|
||||
translations/zh-CN/data/reusables/desktop/get-an-account.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/discussions/enabling-or-disabling-github-discussions-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/discussions/navigate-to-repo-or-org.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/discussions/starting-a-discussion.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dotcom_billing/actions-packages-report-download-org-account.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,rendering error
|
||||
translations/zh-CN/data/reusables/dotcom_billing/view-all-subscriptions.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/actions-packages-report-download-enterprise-accounts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/billing-microsoft-ea-overview.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/dormant-user-activity.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-cap-validates.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-follow.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-fork.md,broken liquid tags
|
||||
@@ -1068,48 +1045,48 @@ translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-interact.md
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-propose.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-permission-repo.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/oidc-gei-warning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/repo-creation-policy.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise-accounts/security-tab.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise/apply-configuration.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise/apply-configuration.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise/rate_limit.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise/repository-caching-release-phase.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise/test-in-staging.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_installation/download-package.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise/test-in-staging.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_installation/download-package.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_installation/hotpatching-explanation.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_installation/ssh-into-instance.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/dormancy-threshold.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/sign-in.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_site_admin_settings/tls-downtime.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/alternatively-enable-external-authentication.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication-new-accounts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/built-in-authentication.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames-for-external-authentication.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,rendering error
|
||||
translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error
|
||||
translations/zh-CN/data/reusables/gated-features/secret-scanning.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/actions.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/actions.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/adding-members-to-organizations.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/configuring-security-features.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/creating-organizations.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/creating-organizations.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/enforcing-repo-management-policies.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/enterprise-advanced-security.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,rendering error
|
||||
translations/zh-CN/data/reusables/git/git-push.md,rendering error
|
||||
translations/zh-CN/data/reusables/getting-started/managing-enterprise-members.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/git/git-push.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/identity-and-permissions/vigilant-mode-beta-note.md,rendering error
|
||||
translations/zh-CN/data/reusables/large_files/storage_assets_location.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,rendering error
|
||||
translations/zh-CN/data/reusables/large_files/use_lfs_tip.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/notifications/outbound_email_tip.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/notifications/shared_state.md,rendering error
|
||||
translations/zh-CN/data/reusables/notifications/vulnerable-dependency-notification-options.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/billing_plans.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/github-apps-settings-sidebar.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/member-privileges.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/navigate-to-org.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/navigate-to-org.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/organizations/repository-defaults.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/security-and-analysis.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/security.md,rendering error
|
||||
@@ -1117,28 +1094,28 @@ translations/zh-CN/data/reusables/organizations/teams_sidebar.md,rendering error
|
||||
translations/zh-CN/data/reusables/organizations/verified-domains.md,rendering error
|
||||
translations/zh-CN/data/reusables/package_registry/authenticate-packages.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/package_registry/authenticate-to-container-registry-steps.md,rendering error
|
||||
translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,rendering error
|
||||
translations/zh-CN/data/reusables/package_registry/next-steps-for-packages-enterprise-setup.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/package_registry/package-registry-with-github-tokens.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/package_registry/packages-billing.md,rendering error
|
||||
translations/zh-CN/data/reusables/package_registry/packages-billing.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/package_registry/required-scopes.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pages/build-failure-email-server.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pages/emu-org-only.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pages/sidebar-pages.md,rendering error
|
||||
translations/zh-CN/data/reusables/projects/enable-basic-workflow.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/projects/graphql-ghes.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/configure_pull_request_merges_intro.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pull_requests/default_merge_option.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pull_requests/pull_request_merges_and_contributions.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pull_requests/rebase_and_merge_summary.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pull_requests/resolving-conversations.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,rendering error
|
||||
translations/zh-CN/data/reusables/pull_requests/squash_and_merge_summary.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/release-notes/ghas-3.4-secret-scanning-known-issue.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/changed-files.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/deploy-keys.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/deploy-keys.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/navigate-to-code-security-and-analysis.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/navigate-to-commit-page.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/navigate-to-repo.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/repositories/repository-branches.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/sidebar-notifications.md,rendering error
|
||||
translations/zh-CN/data/reusables/repositories/suggest-changes.md,broken liquid tags
|
||||
@@ -1146,24 +1123,24 @@ translations/zh-CN/data/reusables/repositories/tracks-vulnerabilities.md,broken
|
||||
translations/zh-CN/data/reusables/repositories/you-can-fork.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/rest-api/dotcom-only-guide-note.md,rendering error
|
||||
translations/zh-CN/data/reusables/saml/about-authorized-credentials.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/about-linked-identities.md,rendering error
|
||||
translations/zh-CN/data/reusables/saml/about-linked-identities.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/about-saml-access-enterprise-account.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/authorized-creds-info.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/must-authorize-linked-identity.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error
|
||||
translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,rendering error
|
||||
translations/zh-CN/data/reusables/scim/supported-idps.md,rendering error
|
||||
translations/zh-CN/data/reusables/scim/enterprise-account-scim.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/scim/supported-idps.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/search/syntax_tips.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/secret-scanning/partner-secret-list-private-repo.md,rendering error
|
||||
translations/zh-CN/data/reusables/secret-scanning/secret-list-private-push-protection.md,rendering error
|
||||
translations/zh-CN/data/reusables/security-overview/permissions.md,rendering error
|
||||
translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,rendering error
|
||||
translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,rendering error
|
||||
translations/zh-CN/data/reusables/shortdesc/rate_limits_github_apps.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/sponsors/select-sponsorship-billing.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/ssh/about-ssh.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/ssh/key-type-support.md,rendering error
|
||||
translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,rendering error
|
||||
translations/zh-CN/data/reusables/support/help_resources.md,rendering error
|
||||
translations/zh-CN/data/reusables/ssh/rsa-sha-1-connection-failure-criteria.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/support/help_resources.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/support/submit-a-ticket.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/user-settings/access_applications.md,rendering error
|
||||
translations/zh-CN/data/reusables/user-settings/account_settings.md,rendering error
|
||||
|
||||
|
@@ -16,12 +16,12 @@ type: overview
|
||||
topics:
|
||||
- Action development
|
||||
- Fundamentals
|
||||
ms.openlocfilehash: ac933a5014750f75373fafa7f8dd52333b79a469
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.openlocfilehash: 1e81bea551ceff1980b0bbe96202f60db0d0e7f2
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147154571'
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191944'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
@@ -35,7 +35,7 @@ ms.locfileid: '147154571'
|
||||
|
||||
## 操作的类型
|
||||
|
||||
您可以创建 Docker 容器和 JavaScript 操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须为 `action.yml` 或 `action.yaml`。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
|
||||
可以构建 Docker 容器、JavaScript 和复合操作。 操作需要元数据文件来定义操作的输入、输出和主要进入点。 元数据文件名必须为 `action.yml` 或 `action.yaml`。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions)”。
|
||||
|
||||
| 类型 | 操作系统 |
|
||||
| ---- | ------------------- |
|
||||
|
||||
@@ -271,3 +271,10 @@ jobs:
|
||||
From your repository, click the **Actions** tab, and select the latest workflow run. Under **Jobs** or in the visualization graph, click **A job to say hello**. You should see "Hello Mona the Octocat" or the name you used for the `who-to-greet` input and the timestamp printed in the log.
|
||||
|
||||
|
||||
|
||||
## Template repositories for creating JavaScript actions
|
||||
|
||||
{% data variables.product.prodname_dotcom %} provides template repositories for creating JavaScript and TypeScript actions. You can use these templates to quickly get started with creating a new action that includes tests, linting, and other recommended practices.
|
||||
|
||||
* [`javascript-action` template repository](https://github.com/actions/javascript-action)
|
||||
* [`typescript-action` template repository](https://github.com/actions/typescript-action)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling Server Statistics for your enterprise
|
||||
intro: 'You can analyze your own aggregate data from {% data variables.product.prodname_ghe_server %} and help us improve {% data variables.product.company_short %} products by enabling {% data variables.product.prodname_server_statistics %}.'
|
||||
title: 为企业启用服务器统计信息
|
||||
intro: '可以从 {% data variables.product.prodname_ghe_server %} 分析自己的聚合数据，并通过启用 {% data variables.product.prodname_server_statistics %} 帮助改进 {% data variables.product.company_short %} 产品。'
|
||||
versions:
|
||||
feature: server-statistics
|
||||
redirect_from:
|
||||
@@ -8,23 +8,27 @@ redirect_from:
|
||||
topics:
|
||||
- Enterprise
|
||||
shortTitle: Server Statistics
|
||||
ms.openlocfilehash: 125651de793a45240008de34845762e6de637040
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191868'
|
||||
---
|
||||
## 关于 {% data variables.product.prodname_server_statistics %}
|
||||
|
||||
## About {% data variables.product.prodname_server_statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} 从 {% data variables.location.product_location %} 中收集聚合使用情况数据，你可以使用这些数据更好地预测组织的需求、了解团队的工作方式并显示你从 {% data variables.product.prodname_ghe_server %} 获取的值。
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} collects aggregate usage data from {% data variables.location.product_location %}, which you can use to better anticipate the needs of your organization, understand how your team works, and show the value you get from {% data variables.product.prodname_ghe_server %}.
|
||||
{% data variables.product.prodname_server_statistics %} 仅在存储库、问题、拉取请求和其他功能上收集某些聚合指标。 不会收集 {% data variables.product.prodname_dotcom %} 内容，例如代码、问题、评论或拉取请求内容。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)”。
|
||||
|
||||
{% data variables.product.prodname_server_statistics %} only collects certain aggregate metrics on repositories, issues, pull requests, and other features. {% data variables.product.prodname_dotcom %} content, such as code, issues, comments, or pull request content, is not collected. For more information, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics)."
|
||||
通过启用 {% data variables.product.prodname_server_statistics %}，还可帮助提高 {% data variables.product.company_short %}。 你将提供的聚合数据有助于我们了解我们的客户使用 {% data variables.product.prodname_dotcom %} 的方式，并做出更好、更明智的产品决策，最终使你受益。
|
||||
|
||||
By enabling {% data variables.product.prodname_server_statistics %}, you are also helping to improve {% data variables.product.company_short %}. The aggregated data you will provide helps us understand how our customers are using {% data variables.product.prodname_dotcom %}, and make better and more informed product decisions, ultimately benefiting you.
|
||||
## 启用 {% data variables.product.prodname_server_statistics %}
|
||||
|
||||
## Enabling {% data variables.product.prodname_server_statistics %}
|
||||
启用 {% data variables.product.prodname_server_statistics %} 之前，必须首先通过 {% data variables.product.prodname_github_connect %} 将 {% data variables.product.prodname_ghe_server %} 实例连接到 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息，请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
|
||||
|
||||
Before you can enable {% data variables.product.prodname_server_statistics %}, you must first connect your {% data variables.product.prodname_ghe_server %} instance to {% data variables.product.prodname_dotcom_the_website %} through {% data variables.product.prodname_github_connect %}. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@3.1/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
|
||||
可随时从 {% data variables.product.prodname_ghe_server %} 禁用 {% data variables.product.prodname_server_statistics %}。
|
||||
|
||||
You can disable {% data variables.product.prodname_server_statistics %} from {% data variables.product.prodname_ghe_server %} at any time.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.github-connect-tab %}
|
||||
4. Under "Share server statistics with GitHub.com", select the dropdown menu and click **Enabled** or **Disabled**.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}
|
||||
4. 在“与 GitHub.com 共享服务器统计信息”下，选择下拉菜单并单击“启用”或“禁用” 。
|
||||
|
||||
|
||||
@@ -23,29 +23,36 @@ Subdomain isolation mitigates cross-site scripting and other related vulnerabili
|
||||
|
||||
When subdomain isolation is enabled, {% data variables.product.prodname_ghe_server %} replaces several paths with subdomains. After enabling subdomain isolation, attempts to access the previous paths for some user-supplied content, such as `http(s)://HOSTNAME/raw/`, may return `404` errors.
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.3-7-new-subdomains %}
|
||||
|
||||
| Path without subdomain isolation | Path with subdomain isolation |
|
||||
| --- | --- |
|
||||
| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/` | `http(s)://docker.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/assets/` | `http(s)://assets.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/avatars/` | `http(s)://avatars.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/codeload/` | `http(s)://codeload.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/gist/` | `http(s)://gist.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/media/` | `http(s)://media.HOSTNAME/` |
|
||||
{%- ifversion viewscreen-and-notebooks %}
|
||||
| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
|
||||
{%- else %}
|
||||
| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/notebooks/` | `http(s)://notebooks.HOSTNAME/` |
|
||||
{%- endif %}
|
||||
| `http(s)://HOSTNAME/pages/` | `http(s)://pages.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/raw/` | `http(s)://raw.HOSTNAME/` |
|
||||
{%- ifversion ghes < 3.7 %}
|
||||
| `http(s)://HOSTNAME/render/` | `http(s)://render.HOSTNAME/` |
|
||||
{%- endif %}
|
||||
| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` |
|
||||
{%- ifversion viewscreen-and-notebooks %}
|
||||
| `http(s)://HOSTNAME/viewscreen/` | `http(s)://viewscreen.HOSTNAME/` |
|
||||
{%- endif %}
|
||||
{%- ifversion ghes > 3.4 %}
|
||||
| Not supported | `https://containers.HOSTNAME/` |
|
||||
{%- endif %}
|
||||
| `http(s)://HOSTNAME/reply/` | `http(s)://reply.HOSTNAME/` |
|
||||
| `http(s)://HOSTNAME/uploads/` | `http(s)://uploads.HOSTNAME/` | {% ifversion ghes %}
|
||||
| `https://HOSTNAME/` | `http(s)://docker.HOSTNAME/`{% endif %}{% ifversion ghes %}
|
||||
| `https://HOSTNAME/_registry/npm/` | `https://npm.HOSTNAME/`
|
||||
| `https://HOSTNAME/_registry/rubygems/` | `https://rubygems.HOSTNAME/`
|
||||
| `https://HOSTNAME/_registry/maven/` | `https://maven.HOSTNAME/`
|
||||
| `https://HOSTNAME/_registry/nuget/` | `https://nuget.HOSTNAME/`{% endif %}{% ifversion ghes > 3.4 %}
|
||||
| Not supported | `https://containers.HOSTNAME/` |{% endif %}
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Restricting network traffic to your enterprise with an IP allow list
|
||||
title: 使用 IP 允许列表限制到企业的网络流量
|
||||
shortTitle: Restricting network traffic
|
||||
intro: You can restrict access to your enterprise and only allow access to your resources from specified IP addresses by using an IP allow list.
|
||||
intro: 可以使用 IP 允许列表限制对企业的访问，仅允许从指定的 IP 地址访问资源。
|
||||
permissions: Enterprise owners can configure IP allow lists.
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
@@ -17,192 +17,154 @@ topics:
|
||||
redirect_from:
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise
|
||||
ms.openlocfilehash: 8511499e723fdeb4a2d24c2fce627bce56ad9777
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191892'
|
||||
---
|
||||
## 关于网络流量限制
|
||||
|
||||
## About network traffic restrictions
|
||||
|
||||
By default, authorized users can access your enterprise from any IP address. You can restrict access to resources {% ifversion ghec %}owned by organizations in an enterprise account {% endif %}by configuring an allow list for specific IP addresses. {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
默认情况下，授权用户可以从任何 IP 地址访问您的企业。 可以通过为特定 IP 地址配置允许列表来限制对{% ifversion ghec %}企业帐户中组织拥有的{% endif %}资源的访问。 {% data reusables.identity-and-permissions.ip-allow-lists-example-and-restrictions %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your enterprise uses {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can choose whether to use {% data variables.product.company_short %}'s IP allow list feature or to use the allow list restrictions for your identity provider (IdP). If your enterprise does not use {% data variables.product.prodname_emus %} with Azure and OIDC, you can use {% data variables.product.company_short %}'s allow list feature.
|
||||
如果你的企业将 {% data variables.product.prodname_emus %} 与 Azure AD 和 OIDC 配合使用，你则可以选择是使用 {% data variables.product.company_short %} 的 IP 允许列表功能，还是为标识提供者 (IdP) 使用允许列表限制。 如果你的企业未将 {% data variables.product.prodname_emus %} 与 Azure 和 OIDC 配合使用，你则可以使用 {% data variables.product.company_short %} 的允许列表功能。
|
||||
|
||||
{% elsif ghae %}
|
||||
|
||||
By default, Azure network security group (NSG) rules leave all inbound traffic open on ports 22, 80, 443, and 25. You can contact {% data variables.contact.github_support %} to configure access restrictions for {% data variables.product.product_name %}.
|
||||
默认情况下，Azure 网络安全组 (NSG) 规则允许所有入站流量在端口 22、80、443 和 25 打开。 可以联系 {% data variables.contact.github_support %} 为 {% data variables.product.product_name %} 配置访问限制。
|
||||
|
||||
For restrictions using Azure NSGs, contact {% data variables.contact.github_support %} with the IP addresses that should be allowed to access {% data variables.product.product_name %}. Specify address ranges using the standard CIDR (Classless Inter-Domain Routing) format. {% data variables.contact.github_support %} will configure the appropriate firewall rules to restrict network access over HTTP, SSH, HTTPS, and SMTP. For more information, see "[Receiving help from {% data variables.contact.github_support %}](/admin/enterprise-support/receiving-help-from-github-support)."
|
||||
对于使用 Azure NSG 的限制，请联系 {% data variables.contact.github_support %} 以获取应允许访问 {% data variables.product.product_name %} 的 IP 地址。 使用标准 CIDR（无类域间路由）格式指定地址范围。 {% data variables.contact.github_support %} 将配置合适的防火墙规则，以限制通过 HTTP、SSH、HTTPS 和 SMTP 的网络访问。 有关详细信息，请参阅“[从 {% data variables.contact.github_support %} 获取帮助](/admin/enterprise-support/receiving-help-from-github-support)”。
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## About {% data variables.product.company_short %}'s IP allow list
|
||||
## 关于 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
|
||||
You can use {% data variables.product.company_short %}'s IP allow list to control access to your enterprise and assets owned by organizations in your enterprise.
|
||||
可以使用 {% data variables.product.company_short %} 的 IP 允许列表来控制对企业和企业中组织拥有的资产的访问。
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-cidr-notation %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-enable %} {% data reusables.identity-and-permissions.ip-allow-lists-enterprise %}
|
||||
|
||||
## About your IdP's allow list
|
||||
## 关于 IdP 的允许列表
|
||||
|
||||
If you are using {% data variables.product.prodname_emus %} with Azure AD and OIDC, you can use your IdP's allow list.
|
||||
如果将 {% data variables.product.prodname_emus %} 与 Azure AD 和 OIDC 配合使用，则可以使用 IdP 的允许列表。
|
||||
|
||||
Using your IdP's allow list deactivates the {% data variables.product.company_short %} IP allow list configurations for all organizations in your enterprise and deactivates the GraphQL APIs for enabling and managing IP allow lists.
|
||||
使用 IdP 的允许列表会停用企业中所有组织的 {% data variables.product.company_short %} IP 允许列表配置，并停用 GraphQL API 以启用和管理 IP 允许列表。
|
||||
|
||||
By default, your IdP runs the CAP on the initial interactive SAML or OIDC sign-in to {% data variables.product.company_short %} for any IP allow list configuration you choose.
|
||||
默认情况下，你的 IdP 会在初始交互式 SAML 或 OIDC 登录到 {% data variables.product.company_short %} 时为你所选择的任何 IP 允许列表配置运行 CAP。
|
||||
|
||||
The OIDC CAP only applies for requests to the API using a user-to-server token, such as a token for an {% data variables.product.prodname_oauth_app %} or a {% data variables.product.prodname_github_app %} acting on behalf of a user. The OIDC CAP does not apply when a {% data variables.product.prodname_github_app %} uses a server-to-server token. For more information, see "[Authenticating with {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)" and "[About support for your IdPs Conditional Access Policy](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)."
|
||||
OIDC CAP 仅适用于使用用户到服务器令牌对 API 的请求，例如 {% data variables.product.prodname_oauth_app %} 或代表用户操作的 {% data variables.product.prodname_github_app %} 的令牌。 当 {% data variables.product.prodname_github_app %} 使用服务器到服务器令牌时，OIDC CAP 不适用。 有关详细信息，请参阅“[使用 {% data variables.product.prodname_github_apps %} 进行身份验证](/developers/apps/building-github-apps/authenticating-with-github-apps#authenticating-as-an-installation)”和“[关于对 IdP 条件访问策略的支持](/enterprise-cloud@latest/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy#github-apps-and-oauth-apps)”。
|
||||
|
||||
To ensure seamless use of the OIDC CAP while still applying the policy to user-to-server tokens, you must copy all of the IP ranges from each {% data variables.product.prodname_github_app %} that your enterprise uses to your IdP policy.
|
||||
为了确保在将策略应用到用户到服务器令牌的同时无缝使用 OIDC CAP，必须将企业使用的每个 {% data variables.product.prodname_github_app %} 中的所有 IP 范围复制到 IdP 策略。
|
||||
|
||||
## Using {% data variables.product.company_short %}'s IP allow list
|
||||
## 使用 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
|
||||
### Enabling {% data variables.product.company_short %}'s IP allow list
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", enable the IP allow list.
|
||||
- If you are using {% data variables.product.prodname_emus %} with OIDC, select the dropdown menu and click **GitHub**.
|
||||
|
||||
### 启用 {% data variables.product.company_short %} 的 IP 允许列表
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. 在“IP 允许列表”下，启用 IP 允许列表。
|
||||
- 如果将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择下拉菜单并单击“GitHub”。
|
||||
|
||||
|
||||
Select **Enable IP allow list**.
|
||||
|
||||
选择“启用 IP 允许列表”。
|
||||
|
||||
|
||||
- If you are not using {% data variables.product.prodname_emus %} with OIDC, select **Enable IP allow list**.
|
||||
|
||||
1. Click **Save**.
|
||||
- 如果未将 {% data variables.product.prodname_emus %} 与 OIDC 配合使用，请选择“启用 IP 允许列表”。
|
||||
|
||||
1. 单击“ **保存**”。
|
||||
|
||||
### Adding an allowed IP address
|
||||
### 添加允许的 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.identity-and-permissions.ipv6-allow-lists %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
### 允许 {% data variables.product.prodname_github_apps %} 访问
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
### Editing an allowed IP address
|
||||
### 编辑允许的 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Click **Update**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. 单击“更新”。
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
### Checking if an IP address is permitted
|
||||
### 检查是否允许使用 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
### Deleting an allowed IP address
|
||||
### 删除允许的 IP 地址
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
## Using your identity provider's allow list
|
||||
## 使用标识提供者的允许列表
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Using your IdP's allow list is only supported for {% data variables.product.prodname_emus %} with Azure AD and OIDC.
|
||||
注意：仅 {% data variables.product.prodname_emus %} 和 Azure AD 和 OIDC 支持使用 IdP 的允许列表。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security %}
|
||||
1. Under "IP allow list", select the dropdown and click **Identity Provider**.
|
||||
{% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} {% data reusables.organizations.security %}
|
||||
1. 在“IP 允许列表”下，选择下拉列表并单击“标识提供者”。
|
||||
|
||||
|
||||
1. Optionally, to allow installed {% data variables.product.company_short %} and {% data variables.product.prodname_oauth_apps %} to access your enterprise from any IP address, select **Skip IdP check for applications**.
|
||||
|
||||
1. （可选）若要允许已安装的 {% data variables.product.company_short %} 和 {% data variables.product.prodname_oauth_apps %} 从任意 IP 地址访问你的企业，请选择“为应用程序跳过 IdP 检查”。
|
||||
|
||||
|
||||
1. Click **Save**.
|
||||
|
||||
1. 单击“ **保存**”。
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghae %}
|
||||
|
||||
## Enabling allowed IP addresses
|
||||
## 启用允许的 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-enabling-allowed-ip-addresses %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Under "IP allow list", select **Enable IP allow list**.
|
||||
|
||||
4. Click **Save**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. 在“IP 允许列表”下，选择“启用 IP 允许列表”。
|
||||
|
||||
4. 单击“ **保存**”。
|
||||
|
||||
## Adding an allowed IP address
|
||||
## 添加允许的 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-description %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-add-entry %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
{% data reusables.identity-and-permissions.about-adding-ip-allow-list-entries %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-add-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-add-description %} {% data reusables.identity-and-permissions.ip-allow-lists-add-entry %} {% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Allowing access by {% data variables.product.prodname_github_apps %}
|
||||
## 允许 {% data variables.product.prodname_github_apps %} 访问
|
||||
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-githubapps-enterprise %}
|
||||
|
||||
## Editing an allowed IP address
|
||||
## 编辑允许的 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-editing-ip-allow-list-entries %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. Click **Update**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-ip %} {% data reusables.identity-and-permissions.ip-allow-lists-edit-description %}
|
||||
8. 单击“更新”。
|
||||
{% data reusables.identity-and-permissions.check-ip-address %}
|
||||
|
||||
## Checking if an IP address is permitted
|
||||
## 检查是否允许使用 IP 地址
|
||||
|
||||
{% data reusables.identity-and-permissions.about-checking-ip-address %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.check-ip-address-step %}
|
||||
|
||||
## Deleting an allowed IP address
|
||||
## 删除允许的 IP 地址
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %}
|
||||
{% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %} {% data reusables.identity-and-permissions.ip-allow-lists-delete-entry %} {% data reusables.identity-and-permissions.ip-allow-lists-confirm-deletion %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Using {% data variables.product.prodname_actions %} with an IP allow list
|
||||
## 对 {% data variables.product.prodname_actions %} 使用 IP 允许列表
|
||||
|
||||
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling GitHub Actions with MinIO storage
|
||||
intro: 'You can enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %} and use MinIO storage to store data generated by workflow runs.'
|
||||
title: 使用 MinIO 存储启用 GitHub Actions
|
||||
intro: '可以在 {% data variables.product.prodname_ghe_server %} 上启用 {% data variables.product.prodname_actions %}，并使用 MinIO 存储来存储工作流运行生成的数据。'
|
||||
permissions: 'Site administrators can enable {% data variables.product.prodname_actions %} and configure enterprise settings.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
@@ -14,36 +14,35 @@ redirect_from:
|
||||
- /admin/github-actions/enabling-github-actions-with-minio-gateway-for-nas-storage
|
||||
- /admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-minio-gateway-for-nas-storage
|
||||
shortTitle: MinIO storage
|
||||
ms.openlocfilehash: 3d9c6cfca6b81a66185515c8757cef22290ead30
|
||||
ms.sourcegitcommit: 8f1801040a84ca9353899a2d1e6782c702aaed0d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/16/2022
|
||||
ms.locfileid: '148166567'
|
||||
---
|
||||
## 先决条件
|
||||
|
||||
## Prerequisites
|
||||
在启用 {% data variables.product.prodname_actions %} 之前，请确保您已完成以下步骤：
|
||||
|
||||
Before enabling {% data variables.product.prodname_actions %}, make sure you have completed the following steps:
|
||||
* 创建 MinIO 存储桶，用于存储工作流运行生成的数据。 有关安装和配置 MinIO 的详细信息，请参阅 MinIO 文档中的“[MinIO 高性能对象存储](https://min.io/docs/minio/container/index.html)”和“[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)”。
|
||||
|
||||
* Create your MinIO bucket for storing data generated by workflow runs. For more information about installing and configuring MinIO, see "[MinIO High Performance Object Storage](https://min.io/docs/minio/container/index.html)" and "[mc mb](https://min.io/docs/minio/linux/reference/minio-mc/mc-mb.html)" in the MinIO documentation.
|
||||
为避免设备上的资源争用，我们建议将 MinIO 与 {% data variables.location.product_location %} 分开托管。
|
||||
|
||||
To avoid resource contention on the appliance, we recommend that MinIO be hosted separately from {% data variables.location.product_location %}.
|
||||
{% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %} {% data reusables.actions.enterprise-common-prereqs %}
|
||||
|
||||
{% indented_data_reference reusables.actions.enterprise-s3-permission spaces=2 %}
|
||||
{% data reusables.actions.enterprise-common-prereqs %}
|
||||
## 使用 MinIO 存储启用 {% data variables.product.prodname_actions %}
|
||||
|
||||
## Enabling {% data variables.product.prodname_actions %} with MinIO storage
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_management_console.actions %} {% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. 在“项目和日志存储”下，选择“Amazon S3”，然后输入存储桶的详细信息：
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_management_console.actions %}
|
||||
{% data reusables.actions.enterprise-enable-checkbox %}
|
||||
1. Under "Artifact & Log Storage", select **Amazon S3**, and enter your storage bucket's details:
|
||||
* AWS 服务 URL：MinIO 服务的 URL。 例如 `https://my-minio.example:9000`。
|
||||
* AWS S3 存储桶：S3 存储桶的名称。
|
||||
* AWS S3 访问密钥和 AWS S3 密钥：用于 MinIO 实例的 `MINIO_ACCESS_KEY` 和 `MINIO_SECRET_KEY` 。
|
||||
|
||||
* **AWS Service URL**: The URL to your MinIO service. For example, `https://my-minio.example:9000`.
|
||||
* **AWS S3 Bucket**: The name of your S3 bucket.
|
||||
* **AWS S3 Access Key** and **AWS S3 Secret Key**: The `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` used for your MinIO instance.
|
||||
|
||||
1. 在“项目和日志存储”下，选择“强制路径样式”。
|
||||
|
||||
|
||||
1. Under "Artifact & Log Storage", select **Force path style**.
|
||||
|
||||
|
||||
{% data reusables.enterprise_management_console.test-storage-button %}
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
 {% data reusables.enterprise_management_console.test-storage-button %} {% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
{% data reusables.actions.enterprise-postinstall-nextsteps %}
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About support for your IdP's Conditional Access Policy
|
||||
title: 关于对 IdP 的条件访问策略的支持
|
||||
shortTitle: Conditional access policy
|
||||
intro: 'When your enterprise uses OIDC SSO, {% data variables.product.prodname_dotcom %} can validate access to your enterprise and its resources using your IdP''s Conditional Access Policy (CAP).'
|
||||
intro: '企业使用 OIDC SSO 时，{% data variables.product.prodname_dotcom %} 可以使用 IdP 的条件访问策略 (CAP) 验证对企业及其资源的访问。'
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
versions:
|
||||
feature: oidc-for-emu
|
||||
@@ -10,35 +10,40 @@ topics:
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- SSO
|
||||
ms.openlocfilehash: aed7008bd008ccfd6303ccbb36f4d6f3bd7002ca
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148179995'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
|
||||
|
||||
## About support for Conditional Access Policies
|
||||
## 关于对条件访问策略的支持
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %}
|
||||
|
||||
{% data variables.product.product_name %} supports CAP for any {% data variables.enterprise.prodname_emu_enterprise %} where OIDC SSO is enabled. {% data variables.product.product_name %} enforces your IdP's IP conditions but cannot enforce your device compliance conditions. Enterprise owners can choose to use this IP allow list configuration instead of {% data variables.product.product_name %}'s IP allow list, and can do so once OIDC SSO is configured. For more information about IP allow lists, see "[Restricting network traffic with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)" and "[Managing allowed IP addresses for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)."
|
||||
{% data variables.product.product_name %} 支持对启用了 OIDC SSO 的任何 {% data variables.enterprise.prodname_emu_enterprise %} 使用 CAP。 {% data variables.product.product_name %} 强制实施你的 IdP 的 IP 条件，但不能强制实施你设备的合规性条件。 企业所有者可以选择使用此 IP 允许列表配置，而不是 {% data variables.product.product_name %} 的 IP 允许列表，并且可以在配置 OIDC SSO 后执行此操作。 有关 IP 允许列表的详细信息，请参阅“[使用 IP 允许列表限制网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)”和“[管理组织的允许 IP 地址](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)”。
|
||||
|
||||
|
||||
For more information about using OIDC with {% data variables.product.prodname_emus %}, see "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)" and "[Migrating from SAML to OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)."
|
||||
有关将 OIDC 与 {% data variables.product.prodname_emus %} 结合使用的详细信息，请参阅“[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)”和“[从 SAML 迁移到 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc)”。
|
||||
|
||||
## Considerations for integrations and automations
|
||||
## 集成和自动化的注意事项
|
||||
|
||||
{% data variables.product.prodname_dotcom %} sends the originating IP address to your IdP for validation against your CAP. To make sure actions and apps are not blocked by your IdP's CAP, you will need to make changes to your configuration.
|
||||
{% data variables.product.prodname_dotcom %} 将发起的 IP 地址发送到你的 IdP 以针对你的 CAP 进行验证。 若要确保 IdP 的 CAP 未阻止操作和应用，需要对配置进行更改。
|
||||
|
||||
{% data reusables.enterprise-accounts.oidc-gei-warning %}
|
||||
|
||||
### {% data variables.product.prodname_actions %}
|
||||
|
||||
Actions that use a {% data variables.product.pat_generic %} will likely be blocked by your IdP's CAP. We recommend that {% data variables.product.pat_generic %}s are created by a service account which is then exempted from IP controls in your IdP's CAP.
|
||||
使用 {% data variables.product.pat_generic %} 的操作可能将被你的 IdP 的 CAP 阻止。 我们建议由服务帐户创建 {% data variables.product.pat_generic %}，该服务帐户随后会从 IdP 的 CAP 中的 IP 控制中豁免。
|
||||
|
||||
If you're unable to use a service account, another option for unblocking actions that use {% data variables.product.pat_generic %}s is to allow the IP ranges used by {% data variables.product.prodname_actions %}. For more information, see "[About GitHub's IP addresses](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)."
|
||||
如果无法使用服务帐户，则取消阻止使用 {% data variables.product.pat_generic %} 的操作的另一个选项是允许 {% data variables.product.prodname_actions %} 使用的 IP 范围。 有关详细信息，请参阅“[关于 GitHub 的 IP 地址](/authentication/keeping-your-account-and-data-secure/about-githubs-ip-addresses)”。
|
||||
|
||||
### {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
|
||||
### {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %}
|
||||
|
||||
When {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %} make requests on a member's behalf, {% data variables.product.prodname_dotcom %} will send the IP address of the app's server to your IdP for validation. If the IP address of the app's server is not validated by your IdP's CAP, the request will fail.
|
||||
当 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %} 代表成员发出请求时，{% data variables.product.prodname_dotcom %} 会将应用的服务器的 IP 地址发送到 IdP 进行验证。 如果 IdP 的 CAP 未验证应用的服务器的 IP 地址，请求将失败。
|
||||
|
||||
You can contact the owners of the apps you want to use, ask for their IP ranges, and configure your IdP's CAP to allow access from those IP ranges. If you're unable to contact the owners, you can review your IdP sign-in logs to review the IP addresses seen in the requests, then allow-list those addresses.
|
||||
可以联系要使用的应用的所有者，询问其 IP 范围，并配置 IdP 的 CAP，以允许从这些 IP 范围进行访问。 如果无法联系所有者，可以查看 IdP 登录日志，查看请求中显示的 IP 地址，然后允许列出这些地址。
|
||||
|
||||
If you do not wish to allow all of the IP ranges for all of your enterprise's apps, you can also exempt installed {% data variables.product.prodname_github_apps %} and authorized {% data variables.product.prodname_oauth_apps %} from the IdP allow list. If you do so, these apps will continue working regardless of the originating IP address. For more information, see "[Enforcing policies for security settings in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)."
|
||||
如果不希望允许所有企业应用的所有 IP 范围，还可以从 IdP 允许列表中免除已安装的 {% data variables.product.prodname_github_apps %} 以及授权的 {% data variables.product.prodname_oauth_apps %}。 如果这样做，无论起始 IP 地址如何，这些应用都将继续工作。 有关详细信息，请参阅“[为企业中的安全设置强制实施策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#allowing-access-by-github-apps)”。
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring OIDC for Enterprise Managed Users
|
||||
title: 为企业托管用户配置 OIDC
|
||||
shortTitle: OIDC for managed users
|
||||
intro: 'You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring OpenID Connect (OIDC) single sign-on (SSO) and enable support for your IdP''s Conditional Access Policy (CAP).'
|
||||
intro: '可以通过配置 OpenID Connect (OIDC) 单一登录 (SSO) 自动管理对 {% data variables.product.prodname_dotcom %} 上的企业帐户的访问，并启用对 IdP 的条件访问策略 (CAP) 的支持。'
|
||||
product: '{% data reusables.gated-features.emus %}'
|
||||
versions:
|
||||
feature: oidc-for-emu
|
||||
@@ -10,40 +10,42 @@ topics:
|
||||
- Authentication
|
||||
- Enterprise
|
||||
- SSO
|
||||
ms.openlocfilehash: caa557cb976fb60a59572e1623db6be87efeee54
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148179987'
|
||||
---
|
||||
|
||||
{% data reusables.enterprise-accounts.azure-emu-support-oidc %}
|
||||
|
||||
## About OIDC for Enterprise Managed Users
|
||||
## 关于适用于企业托管用户的 OIDC
|
||||
|
||||
With {% data variables.product.prodname_emus %}, your enterprise uses your identity provider (IdP) to authenticate all members. You can use OpenID Connect (OIDC) to manage authentication for your {% data variables.enterprise.prodname_emu_enterprise %}. Enabling OIDC SSO is a one-click setup process with certificates managed by {% data variables.product.prodname_dotcom %} and your IdP.
|
||||
通过 {% data variables.product.prodname_emus %}，企业使用标识提供者 (IdP) 对所有成员进行身份验证。 可以使用 OpenID Connect (OIDC) 管理 {% data variables.enterprise.prodname_emu_enterprise %} 的身份验证。 启用 OIDC SSO 是一个一键式设置过程，证书由 {% data variables.product.prodname_dotcom %} 和你的 IdP 管理。
|
||||
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)."
|
||||
{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息，请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。
|
||||
|
||||
You can adjust the lifetime of a session, and how often a {% data variables.enterprise.prodname_managed_user %} needs to reauthenticate with your IdP, by changing the lifetime policy property of the ID tokens issued for {% data variables.product.prodname_dotcom %} from your IdP. The default lifetime is one hour. For more information, see "[Configurable token lifetimes in the Microsoft identity platform](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)" in the Azure AD documentation.
|
||||
可以通过从 IdP 更改为 {% data variables.product.prodname_dotcom %} 颁发的 ID 令牌的生存期属性，调整会话的生存期，以及 {% data variables.enterprise.prodname_managed_user %} 需要对 IdP 重新进行身份验证的频率。 默认生存期为 1 小时。 有关详细信息，请参阅 Azure AD 文档中的“[Microsoft 标识平台中的可配置令牌生存期](https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-configurable-token-lifetimes)”。
|
||||
|
||||
{% data reusables.enterprise_user_management.SAML-to-OIDC-migration-for-EMU %}
|
||||
|
||||
{% data reusables.enterprise-accounts.oidc-gei-warning %}
|
||||
|
||||
## Identity provider support
|
||||
## 标识提供者支持
|
||||
|
||||
Support for OIDC is available for customers using Azure Active Directory (Azure AD).
|
||||
对 OIDC 的支持可供使用 Azure Active Directory (Azure AD) 的客户使用。
|
||||
|
||||
Each Azure AD tenant can support only one OIDC integration with {% data variables.product.prodname_emus %}. If you want to connect Azure AD to more than one enterprise on {% data variables.product.prodname_dotcom %}, use SAML instead. For more information, see "[Configuring SAML single sign-on for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)."
|
||||
每个 Azure AD 租户只能支持一个与 {% data variables.product.prodname_emus %} 的 OIDC 集成。 如果要将 Azure AD 连接到 {% data variables.product.prodname_dotcom %} 上的多个企业，请改用 SAML。 有关详细信息，请参阅“[为 {% data variables.product.prodname_emus %} 配置 SAML 单一登录](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users)”。
|
||||
|
||||
## Configuring OIDC for Enterprise Managed Users
|
||||
## 为企业托管用户配置 OIDC
|
||||
|
||||
1. Sign into {% data variables.product.prodname_dotcom_the_website %} as the setup user for your new enterprise with the username **@<em>SHORT-CODE</em>_admin**.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.security-tab %}
|
||||
1. Select **Require OIDC single sign-on**.
|
||||
|
||||
1. To continue setup and be redirected to Azure AD, click **Save**.
|
||||
{% data reusables.enterprise-accounts.emu-azure-admin-consent %}
|
||||
{% data reusables.enterprise-accounts.download-recovery-codes %}
|
||||
1. 使用用户名“@<em>SHORT-CODE</em>_admin”以新企业的安装用户身份登录到 {% data variables.product.prodname_dotcom_the_website %}。
|
||||
{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
|
||||
1. 选择“要求 OIDC 单一登录”。
|
||||
|
||||
1. 若要继续设置并重定向到 Azure AD，请单击“保存”。
|
||||
{% data reusables.enterprise-accounts.emu-azure-admin-consent %} {% data reusables.enterprise-accounts.download-recovery-codes %}
|
||||
|
||||
## Enabling provisioning
|
||||
## 启用设置
|
||||
|
||||
After you enable OIDC SSO, enable provisioning. For more information, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)."
|
||||
启用 OIDC SSO 后，启用预配。 有关详细信息，请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Enabling GitHub Packages with Azure Blob Storage
|
||||
intro: 'Set up {% data variables.product.prodname_registry %} with Azure Blob Storage as your external storage.'
|
||||
title: 使用 Azure Blob 存储启用 GitHub Packages
|
||||
intro: '以 Azure Blob 存储作为外部存储设置 {% data variables.product.prodname_registry %} 。'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: tutorial
|
||||
@@ -9,42 +9,44 @@ topics:
|
||||
- Packages
|
||||
- Storage
|
||||
shortTitle: Enable Packages with Azure
|
||||
ms.openlocfilehash: b851f698baba60323cbaaa69122cacdc92ec83c2
|
||||
ms.sourcegitcommit: 3ece72cf2d90987575d369c44101d19d3bb06f76
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190385'
|
||||
---
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warnings:**
|
||||
- It is critical that you set the restrictive access policies you need for your storage bucket, because {% data variables.product.company_short %} does not apply specific object permissions or additional access control lists (ACLs) to your storage bucket configuration. For example, if you make your bucket public, data in the bucket will be accessible on the public internet.
|
||||
- We recommend using a dedicated bucket for {% data variables.product.prodname_registry %}, separate from the bucket you use for {% data variables.product.prodname_actions %} storage.
|
||||
- Make sure to configure the bucket you'll want to use in the future. We do not recommend changing your storage after you start using {% data variables.product.prodname_registry %}.
|
||||
警告：
|
||||
- 为存储桶设置所需的限制性访问策略至关重要，因为 {% data variables.product.company_short %} 不会将特定对象权限或其他访问控制列表 (ACL) 应用于存储桶配置。 例如，如果将存储桶设为公共，则在公共互联网上可以访问存储桶中的数据。
|
||||
- 我们建议对 {% data variables.product.prodname_registry %} 使用专用存储桶，与用于 {% data variables.product.prodname_actions %} 存储的存储桶分开。
|
||||
- 请确保配置将来要使用的存储桶。 在开始使用 {% data variables.product.prodname_registry %} 后，我们不建议更改存储系统。
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Prerequisites
|
||||
## 先决条件
|
||||
|
||||
Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your Azure Blob storage bucket. To prepare your Azure Blob storage bucket, we recommend consulting the official Azure Blob storage docs at the official [Azure Blob Storage documentation site](https://docs.microsoft.com/en-us/azure/storage/blobs/).
|
||||
在 {% data variables.location.product_location_enterprise %} 上启用和配置 {% data variables.product.prodname_registry %} 之前，需要准备 Azure Blob 存储 Bucket。 若要准备 Azure Blob 存储 Bucket，建议查阅官方 [Azure Blob 存储文档站点](https://docs.microsoft.com/en-us/azure/storage/blobs/)上的官方 Azure Blob 存储文档。
|
||||
|
||||
## Enabling {% data variables.product.prodname_registry %} with Azure Blob Storage
|
||||
## 使用 Azure Blob 存储启用 {% data variables.product.prodname_registry %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
{% data reusables.enterprise_site_admin_settings.packages-tab %}
|
||||
{% data reusables.package_registry.enable-enterprise-github-packages %}
|
||||
1. Under "Packages Storage", select **Azure Blob Storage** and enter your Azure container name for your packages storage bucket and connection string.
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.management-console %} {% data reusables.enterprise_site_admin_settings.packages-tab %} {% data reusables.package_registry.enable-enterprise-github-packages %}
|
||||
1. 在“包存储”下，选择“Azure Blob 存储”，然后为包存储 Bucket 和连接字符串输入 Azure 容器名称。
|
||||
|
||||
- You must create a storage container prior to setting the container name and connection string.
|
||||
- 在设置容器名称和连接字符串之前，必须创建存储容器。
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** You can find your Azure Connection String by navigating to the Access Key menu in your Azure storage account.
|
||||
Usage of a SAS Token or SAS URL as connection string is not currently supported.
|
||||
注意：可以通过导航到 Azure 存储帐户中的“访问密钥”菜单来查找 Azure 连接字符串。
|
||||
目前不支持使用 SAS 令牌或 SAS URL 作为连接字符串。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise_management_console.save-settings %}
|
||||
|
||||
## Next steps
|
||||
## 后续步骤
|
||||
|
||||
{% data reusables.package_registry.next-steps-for-packages-enterprise-setup %}
|
||||
|
||||
@@ -56,7 +56,7 @@ You can enforce policies to control how members of your enterprise on {% data va
|
||||
|
||||
Each time someone creates a new repository within your enterprise, that person must choose a visibility for the repository. When you configure a default visibility setting for the enterprise, you choose which visibility is selected by default. For more information on repository visibility, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)."
|
||||
|
||||
If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
|
||||
If an enterprise owner disallows members from creating certain types of repositories, members will not be able to create that type of repository even if the visibility setting defaults to that type. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% ifversion ghes or ghae %}
|
||||
@@ -166,7 +166,7 @@ Across all organizations owned by your enterprise, you can set the default branc
|
||||
|
||||
Across all organizations owned by your enterprise, you can allow members with admin access to change a repository's visibility, restrict repository visibility changes to organization owners, or allow owners to administer the setting on the organization level. When you prevent members from changing repository visibility, only enterprise owners can change the visibility of a repository.
|
||||
|
||||
If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Setting a policy for repository creation](#setting-a-policy-for-repository-creation)."
|
||||
If an enterprise owner has restricted repository creation to organization owners only, then members will not be able to change repository visibility. If an enterprise owner has restricted member repository creation to private repositories only, then members will only be able to change the visibility of a repository to private. For more information, see "[Enforcing a policy for repository creation](#enforcing-a-policy-for-repository-creation)."
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About billing for GitHub Actions
|
||||
intro: 'If you want to use {% data variables.product.prodname_actions %} beyond the storage or minutes included in your account, you will be billed for additional usage.'
|
||||
title: 关于 GitHub Actions 的计费
|
||||
intro: '如果要对 {% data variables.product.prodname_actions %} 的使用超出帐户所含存储容量或分钟数，您需要支付额外的使用费。'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-actions
|
||||
@@ -13,105 +13,104 @@ topics:
|
||||
- Actions
|
||||
- Spending limits
|
||||
shortTitle: Billing for GitHub Actions
|
||||
ms.openlocfilehash: fcc8f84b8a11b214ca66e8a3851a1afc9df6213a
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191884'
|
||||
---
|
||||
## About billing for {% data variables.product.prodname_actions %}
|
||||
## 关于 {% data variables.product.prodname_actions %} 的计费
|
||||
|
||||
{% data reusables.actions.actions-billing %}
|
||||
|
||||
{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
|
||||
{% data reusables.actions.actions-spending-limit-brief %} 有关详细信息，请参阅“[关于支出限制](#about-spending-limits)”。
|
||||
|
||||
{% ifversion ghec %}
|
||||
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
{% ifversion ghec %} 如果通过 Microsoft 企业协议购买了 {% data variables.product.prodname_enterprise %}，则可以将 Azure 订阅 ID 连接到企业帐户，以启用和支付超出额度的 {% data variables.product.prodname_actions %} 使用量，包括帐户。 有关详细信息，请参阅“[将 Azure 订阅连接到企业](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)”。
|
||||
{% endif %}
|
||||
|
||||
Minutes reset every month, while storage usage does not.
|
||||
分钟数每月重置一次，而存储空间使用量不会重置。
|
||||
|
||||
### Included storage and minutes
|
||||
### 包括存储和分钟数
|
||||
|
||||
{% ifversion actions-hosted-runners %}
|
||||
{% note %}
|
||||
{% ifversion actions-hosted-runners %} {% note %}
|
||||
|
||||
**Note**: Entitlement minutes cannot be used for Windows and Ubuntu runners over 2-cores. These runners will always be charged for, including in public repos. For more information, see "[Per-minute rates for runners](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)."
|
||||
注意：权利分钟数不能用于超过 2 核的 Windows 和 Ubuntu 运行器。 这些运行器将始终收取费用，包括在公共存储库中。 有关详细信息，请参阅“[运行器的每分钟费率](/billing/managing-billing-for-github-actions/about-billing-for-github-actions#per-minute-rates)”。
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% endnote %} {% endif %}
|
||||
|
||||
|Product | Storage | Minutes (per month)|
|
||||
|产品 | 存储 | 分钟数（每月）|
|
||||
|------- | ------- | ---------|
|
||||
| {% data variables.product.prodname_free_user %} | 500 MB | 2,000 |
|
||||
| {% data variables.product.prodname_pro %} | 1 GB | 3,000 |
|
||||
| {% data variables.product.prodname_free_team %} for organizations | 500 MB | 2,000 |
|
||||
| {% data variables.product.prodname_pro %} | 1GB | 3,000 |
|
||||
| 组织的 {% data variables.product.prodname_free_team %} | 500 MB | 2,000 |
|
||||
| {% data variables.product.prodname_team %} | 2 GB | 3,000 |
|
||||
| {% data variables.product.prodname_ghe_cloud %} | 50 GB | 50,000 |
|
||||
|
||||
Jobs that run on Windows and macOS runners that {% data variables.product.prodname_dotcom %} hosts consume minutes at 2 and 10 times the rate that jobs on Linux runners consume. For example, using 1,000 Windows minutes would consume 2,000 of the minutes included in your account. Using 1,000 macOS minutes, would consume 10,000 minutes included in your account.
|
||||
在 {% data variables.product.prodname_dotcom %} 主机的 Windows 和 macOS 运行器上运行的作业，其消耗分钟数是在 Linux 运行器上运行的作业的 2 倍和 10 倍。 例如，1,000 分钟的 Windows 使用时间将占用帐户中包含的 2,000 分钟。 1,000 分钟的 macOS 使用时间将占用帐户中包含的 10,000 分钟。
|
||||
|
||||
### Minute multipliers
|
||||
### 分钟乘数
|
||||
|
||||
| Operating system | Minute multiplier |
|
||||
| 操作系统 | 分钟乘数 |
|
||||
|------- | ---------|
|
||||
| Linux | 1 |
|
||||
| macOS| 10 |
|
||||
| Windows | 2 |
|
||||
|
||||
The storage used by a repository is the total storage used by {% data variables.product.prodname_actions %} artifacts and {% data variables.product.prodname_registry %}. Your storage cost is the total usage for all repositories owned by your account. For more information about pricing for {% data variables.product.prodname_registry %}, see "[About billing for {% data variables.product.prodname_registry %}](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)."
|
||||
仓库使用的存储空间是 {% data variables.product.prodname_actions %} 构件和 {% data variables.product.prodname_registry %} 使用的存储空间总计。 存储成本是帐户拥有的所有存储库的总使用量。 有关 {% data variables.product.prodname_registry %} 计费的详细信息，请参阅“[关于 {% data variables.product.prodname_registry %} 的计费](/billing/managing-billing-for-github-packages/about-billing-for-github-packages)”。
|
||||
|
||||
If your account's usage surpasses these limits and you have set a spending limit above $0 USD, you will pay $0.008 USD per GB of storage per day and per-minute usage depending on the operating system used by the {% data variables.product.prodname_dotcom %}-hosted runner. {% data variables.product.prodname_dotcom %} rounds the minutes and partial minutes each job uses up to the nearest whole minute.
|
||||
如果你的帐户使用量超出了这些限额，并且你设置的支出限额高于 0 美元，则每天的每 GB 存储用量和每分钟用量需要支付 0.008 美元，具体取决于 {% data variables.product.prodname_dotcom %} 托管运行器使用的操作系统。 {% data variables.product.prodname_dotcom %} 将每个作业使用的分钟数和部分分钟数舍入到最接近的分钟整数。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Minute multipliers do not apply to the per-minute rates shown below.
|
||||
注意：分钟数乘数不适用于如下所示的每分钟费率。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
### Per-minute rates
|
||||
### 每分钟费率
|
||||
|
||||
{% data reusables.billing.billing-standard-runners %}
|
||||
{%- ifversion actions-hosted-runners %}
|
||||
{% data reusables.billing.billing-hosted-runners %}
|
||||
{%- endif %}
|
||||
{% data reusables.billing.billing-standard-runners %} {%- ifversion actions-hosted-runners %} {% data reusables.billing.billing-hosted-runners %} {%- endif %}
|
||||
|
||||
- The number of jobs you can run concurrently across all repositories in your user or organization account depends on your GitHub plan. For more information, see "[Usage limits and billing](/actions/reference/usage-limits-billing-and-administration)" for {% data variables.product.prodname_dotcom %}-hosted runners and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)" for self-hosted runner usage limits.
|
||||
- {% data reusables.user-settings.context_switcher %}
|
||||
{% ifversion actions-hosted-runners %}
|
||||
- For {% data variables.actions.hosted_runner %}s, there is no additional cost for configurations that assign public static IP addresses to a {% data variables.actions.hosted_runner %}. For more information on {% data variables.actions.hosted_runner %}s, see "[Using {% data variables.actions.hosted_runner %}s](/actions/using-github-hosted-runners/using-larger-runners)."
|
||||
- Entitlement minutes cannot be used for {% data variables.actions.hosted_runner %}s.
|
||||
- The {% data variables.actions.hosted_runner %}s are not free for public repositories.
|
||||
- 可在用户或组织帐户的所有仓库中同时运行的作业数量取决于您的 GitHub 计划。 有关详细信息，请参阅 {% data variables.product.prodname_dotcom %} 托管运行器的“[使用限制和计费](/actions/reference/usage-limits-billing-and-administration)”和自托管运行器使用限制的“[关于自托管运行器](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)”。
|
||||
- {% data reusables.user-settings.context_switcher %} {% ifversion actions-hosted-runners %}
|
||||
- 对于 {% data variables.actions.hosted_runner %}，将公共静态 IP 地址分配给 {% data variables.actions.hosted_runner %} 的配置没有额外成本。 有关 {% data variables.actions.hosted_runner %} 的详细信息，请参阅“[使用 {% data variables.actions.hosted_runner %}](/actions/using-github-hosted-runners/using-larger-runners)”。
|
||||
- 权利分钟数不能用于 {% data variables.actions.hosted_runner %}。
|
||||
- {% data variables.actions.hosted_runner %} 针对公共存储库不是免费的。
|
||||
{% endif %}
|
||||
|
||||
## Calculating minute and storage spending
|
||||
## 计算分钟和存储支出
|
||||
|
||||
{% data reusables.dotcom_billing.pricing_calculator.pricing_cal_actions %}
|
||||
|
||||
At the end of the month, {% data variables.product.prodname_dotcom %} calculates the cost of minutes and storage used over the amount included in your account.
|
||||
在月末，{% data variables.product.prodname_dotcom %} 会计算您使用的超过帐户自带限额的分钟数和存储空间费用。
|
||||
|
||||
### Sample minutes cost calculation
|
||||
### 样品分钟数成本计算
|
||||
|
||||
For example, if your organization uses {% data variables.product.prodname_team %} and allows unlimited spending, using 5,000 minutes could have a total storage and minute overage cost of $56 USD, depending on the operating systems used to run jobs.
|
||||
例如，如果您的组织使用 {% data variables.product.prodname_team %} 并允许无限制支出，则使用 5,000 分钟可能会产生 56 美元的总存储空间和分钟数超额费用，具体取决于用于运行作业的操作系统。
|
||||
|
||||
- 5,000 (3,000 Linux and 2,000 Windows) minutes = $56 USD ($24 USD + $32 USD).
|
||||
- 3,000 Linux minutes at $0.008 USD per minute = $24 USD.
|
||||
- 2,000 Windows minutes at $0.016 USD per minute = $32 USD.
|
||||
- 5,000（3,000 Linux 加 2,000 Windows）分钟 = $56 ($24 + $32)。
|
||||
- 3,000 Linux 分钟（每分钟 $0.008）= $24。
|
||||
- 2,000 Windows 分钟（每分钟 $0.016）= $32。
|
||||
|
||||
{% data variables.product.prodname_dotcom %} calculates your storage usage for each month based on hourly usage during that month.
|
||||
{% data variables.product.prodname_dotcom %} 根据每个月的小时用量计算该月的存储使用量。
|
||||
|
||||
### Sample storage cost calculation
|
||||
### 样品存储成本计算
|
||||
|
||||
For example, if you use 3 GB of storage for 10 days of March and 12 GB for 21 days of March, your storage usage would be:
|
||||
例如，如果在三月的 10 天内使用 3 GB 的存储，在三月的 21 天使用 12 GB 的存储，则存储使用量为：
|
||||
|
||||
- 3 GB x 10 days x (24 hours per day) = 720 GB-Hours
|
||||
- 12 GB x 21 days x (24 hours per day) = 6,048 GB-Hours
|
||||
- 720 GB-Hours + 6,048 GB-Hours = 6,768 GB-Hours
|
||||
- 6,768 GB-Hours / (744 hours per month) = 9.0967 GB-Months
|
||||
- 3 GB x 10 天 x（每天 24 小时）= 720 GB-小时
|
||||
- 12 GB x 21 天 x（每天 24 小时）= 6,048 GB-小时
|
||||
- 720 GB-小时 + 6,048 GB-小时 = 6,768 GB-小时
|
||||
- 6,768 GB-小时 / (每月 744 小时) = 9.0967 GB-月
|
||||
|
||||
At the end of the month, {% data variables.product.prodname_dotcom %} rounds your storage to the nearest MB. Therefore, your storage usage for March would be 9.097 GB.
|
||||
到月底，{% data variables.product.prodname_dotcom %} 会将您的存储量舍入到最接近的 MB。 因此，三月的存储使用量为 9.097 GB。
|
||||
|
||||
Your {% data variables.product.prodname_actions %} usage shares your account's existing billing date, payment method, and receipt. {% data reusables.dotcom_billing.view-all-subscriptions %}
|
||||
{% data variables.product.prodname_actions %} 使用将共用帐户的现有计费日期、付款方式和收据。 {% data reusables.dotcom_billing.view-all-subscriptions %}
|
||||
|
||||
## About spending limits
|
||||
## 关于支出限制
|
||||
|
||||
{% data reusables.actions.actions-spending-limit-detailed %}
|
||||
|
||||
For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
|
||||
有关管理和更改帐户支出限制的信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”。
|
||||
|
||||
{% data reusables.dotcom_billing.actions-packages-unpaid-account %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Managing privately reported security vulnerabilities
|
||||
intro: Repository maintainers can manage security vulnerabilities that have been privately reported to them by security reseachers for repositories where private vulnerability reporting is enabled.
|
||||
title: 管理私下报告的安全漏洞
|
||||
intro: 存储库维护人员可以管理由存储库安全研究人员向其私下报告的安全漏洞，这些存储库已启用了非公开漏洞报告。
|
||||
permissions: 'Anyone with admin permissions to a repository can see, review, and manage privately-reported vulnerabilities for the repository.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -11,35 +11,38 @@ topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Manage vulnerability reports
|
||||
ms.openlocfilehash: 942533788dc6ad9280ddc023f583462c7a0ff7f8
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159786'
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
## 关于私下报告安全漏洞
|
||||
|
||||
Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to you using a simple form.
|
||||
通过非公开漏洞报告，安全研究人员可以轻松使用简单的表单直接向你报告漏洞。
|
||||
|
||||
When a security researcher reports a vulnerability privately, you are notified and can choose to either accept it, ask more questions, or reject it. If you accept the report, you're ready to collaborate on a fix for the vulnerability in private with the security researcher.
|
||||
当安全研究人员私下报告漏洞时，你会收到通知并且可以选择接受报告、提出更多问题或拒绝报告。 如果接受报告，则可以与安全研究人员私下协作修复漏洞。
|
||||
|
||||
## Managing security vulnerabilities that are privately reported
|
||||
## 管理私下报告的安全漏洞
|
||||
|
||||
{% data variables.product.prodname_dotcom %} notifies repository maintainers when security researchers privately report vulnerabilities in their repository, and sends notifications if maintainers watch the repository or if they have notifications enabled for the repository. For more information, see "[Configuring notifications](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)."
|
||||
当安全研究人员私下报告存储库中的漏洞时，{% data variables.product.prodname_dotcom %} 会通知存储库维护人员，并在维护人员监视存储库或为存储库启用通知的情况下发送通知。 有关详细信息，请参阅“[配置通知](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications)”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click the advisory you want to review. An advisory that is privately reported will have a status of `Needs triage`.
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
1. 单击要查看的通告。 私下报告的通告的状态为 `Needs triage`。
|
||||
|
||||
|
||||
|
||||
|
||||
2. Carefully review the report. You can:
|
||||
- Collaborate with the security researcher on a patch in private, by clicking **Start a temporary private fork**. This gives you a place for further discussions with the contributor without changing the status of the proposed advisory from `Needs triage`.
|
||||
- Accept the vulnerability report as a draft advisory on {% data variables.product.prodname_dotcom %}, by clicking **Accept and open as draft**. If you choose this option:
|
||||
- This doesn't make the report public.
|
||||
- The report becomes a draft repository security advisory and you can work on it in the same way as any draft advisory that you create.
|
||||
For more information on security advisories, see "[About repository security advisories](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)."
|
||||
- Reject the report by clicking **Close security advisory**. Where possible, you should add a comment explaining why you don't consider the report a security risk before you close the advisory.
|
||||
2. 仔细查看报告。 可以：
|
||||
- 单击“启动临时专用分叉”，与安全研究人员私下协作生成修补程序。 这为你提供了一个与参与者进一步讨论的空间，而无需从 `Needs triage` 更改建议的通告状态。
|
||||
- 单击“接受并作为草稿打开”，在 {% data variables.product.prodname_dotcom %} 上将漏洞报告作为草稿通告接受。 如果你选择此选项：
|
||||
- 该选项不会公开报表。
|
||||
- 报表将成为存储库安全通告草稿，可以采用与创建的任何草稿通告相同的方式使用它。
|
||||
有关安全通告的详细信息，请参阅“[关于存储库安全通告](/code-security/security-advisories/repository-security-advisories/about-repository-security-advisories)”。
|
||||
- 单击“关闭安全通告”可拒绝报告。 在可能的情况下，在关闭通告之前应添加注释，解释为什么不将报告内容视为安全风险。
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Privately reporting a security vulnerability
|
||||
intro: Some public repositories configure security advisories so that anyone can report security vulnerabilities directly and privately to the maintainers.
|
||||
title: 私下报告安全漏洞
|
||||
intro: 某些公共存储库配置安全公告，以便任何人都可以直接并私下向维护人员报告安全漏洞。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,61 +10,64 @@ topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Privately reporting
|
||||
ms.openlocfilehash: 7f4f208bd2724608cf9955efd82a256c3479e884
|
||||
ms.sourcegitcommit: 2ff4a43f0b14939da79d56c54402cfee8d90ae23
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/17/2022
|
||||
ms.locfileid: '148169555'
|
||||
---
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-beta %}
|
||||
|
||||
{% data reusables.security-advisory.private-vulnerability-reporting-enable %}
|
||||
|
||||
## About privately reporting a security vulnerability
|
||||
## 关于私人报告安全漏洞
|
||||
|
||||
Security researchers often feel responsible for alerting users to a vulnerability that could be exploited. If there are no clear instuctions about contacting maintainers of the repository containing the vulnerability, security researchers may have no other choice but to post about the vulnerability on social media, send direct messages to the maintainer, or even create public issues. This situation can potentially lead to a public disclosure of the vulnerability details.
|
||||
安全研究人员通常有责任提醒用户注意可能被利用的漏洞。 如果没有关于联系包含该漏洞的存储库的维护人员的明确说明，安全研究人员可能别无选择，只好在社交媒体上发布该漏洞，直接向维护人员发送消息，甚至提出公共问题。 这种情况可能会导致公开披露漏洞详细信息。
|
||||
|
||||
Private vulnerability reporting makes it easy for security researchers to report vulnerabilities directly to repository maintainer using a simple form.
|
||||
通过私下漏洞报告，安全研究人员可以轻松地使用简单的表单直接向存储库维护人员报告漏洞。
|
||||
|
||||
For security researchers, the benefits of using private vulnerability reporting are:
|
||||
- Less frustration, and less time spent trying to figure out how to contact the maintainer.
|
||||
- A smoother process for disclosing and discussing vulnerability details.
|
||||
- The opportunity to discuss vulnerability details privately with repository maintainer.
|
||||
对于安全研究人员来说，使用私下漏洞报告的好处是：
|
||||
- 减少挫折感，减少花费在尝试如何联系维护人员的时间。
|
||||
- 披露和讨论漏洞详细信息的过程更顺畅。
|
||||
- 有机会与存储库维护人员私下讨论漏洞详细信息。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If the repository doesn't have private vulnerabiliy reporting enabled, you need to initiate the reporting process by following the instructions in the security policy for the repository, or create an issue asking the maintainers for a preferred security contact. For more information, see "[About coordinated disclosure of security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)."
|
||||
注意：如果存储库未启用私下漏洞报告，则需要按照存储库的安全策略中的说明启动报告过程，或者创建问题，让维护人员提供首选的安全联系人。 有关详细信息，请参阅“[关于协调披露安全漏洞](/code-security/security-advisories/guidance-on-reporting-and-writing/about-coordinated-disclosure-of-security-vulnerabilities#about-reporting-and-disclosing-vulnerabilities-in-projects-on-github)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Privately reporting a security vulnerability
|
||||
## 私下报告安全漏洞
|
||||
|
||||
Security researchers can privately report a security vulnerability to repository maintainers.
|
||||
安全研究人员可以私下向存储库维护人员报告安全漏洞。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click **Report a vulnerability** to open the advisory form.
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
1. 单击“报告漏洞”可打开咨询表单。
|
||||
|
||||
|
||||
|
||||
|
||||
2. Fill in the advisory details form.
|
||||
2. 填写咨询详细信息表单。
|
||||
{% tip %}
|
||||
|
||||
**Tip:** In this form, only the title and description are mandatory. (In the general draft security advisory form, which the repository maintainer initiates, specifying the ecosystem is also required.) However, we recommend security researchers provide as much information as possible on the form so that the maintainers can make an informed decision about the submitted report. You can adopt the template used by our security researchers from the {% data variables.product.prodname_security %}, which is available on the [`github/securitylab` repository](https://github.com/github/securitylab/blob/main/docs/report-template.md)."
|
||||
提示：在此表单中，只有标题和说明是必填的。 （在存储库维护人员启动的一般安全咨询表单草稿中，还需要指定生态系统。）但是，建议安全研究人员在表单上提供尽可能多的信息，以便维护人员可以就提交的报告做出明智的决定。 可以采用我们的安全研究人员从 {% data variables.product.prodname_security %} 使用的模板，该模板可在 [`github/securitylab` 存储库](https://github.com/github/securitylab/blob/main/docs/report-template.md)中获取。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
For more information about the fields available and guidance on filling in the form, see "[Creating a repository security advisory](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)" and "[Best practices for writing repository security advisories](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)."
|
||||
有关可用字段和填写表单的指导的详细信息，请参阅“[创建存储库安全公告](/code-security/security-advisories/repository-security-advisories/creating-a-repository-security-advisory)”和“[编写存储库安全公告的最佳做法](/code-security/security-advisories/guidance-on-reporting-and-writing/best-practices-for-writing-repository-security-advisories)”。
|
||||
|
||||
1. At the bottom of the form, click **Submit report**. {% data variables.product.prodname_dotcom %} will display a message letting you know that maintainers have been notified and that you have a pending credit for this security advisory.
|
||||
1. 在表单底部，单击“提交报告”。 {% data variables.product.prodname_dotcom %} 将显示一条消息，告知你已通知维护人员，并且你拥有此安全公告的待处理额度。
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** When the report is submitted, {% data variables.product.prodname_dotcom %} automatically adds the reporter of the vulnerability as a collaborator and as a credited user on the proposed advisory.
|
||||
提示：提交报告后，{% data variables.product.prodname_dotcom %} 会自动将漏洞报告者添加为协作者，并在建议的公告中作为信用用户添加。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
1. Optionally, click **Start a temporary private fork** if you want to start to fix the issue. Note that only the repository maintainer can merge that private fork.
|
||||
1. （可选）如果要开始修复问题，单击“启动临时专用分支”。 请注意，只有存储库维护人员才能合并该专用分支。
|
||||
|
||||
|
||||
|
||||
|
||||
The next steps depend on the action taken by the repository maintainer. For more information, see "[Managing privately reported security vulnerabilities](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)."
|
||||
后续步骤取决于存储库维护人员执行的操作。 有关详细信息，请参阅“[管理私下报告的安全漏洞](/code-security/security-advisories/guidance-on-reporting-and-writing/managing-privately-reported-security-vulnerabilities)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a repository security advisory
|
||||
intro: You can create a draft security advisory to privately discuss and fix a security vulnerability in your open source project.
|
||||
title: 创建存储库安全公告
|
||||
intro: 您可以创建安全通告草稿，以私下讨论和修复开源项目中的安全漏洞。
|
||||
redirect_from:
|
||||
- /articles/creating-a-maintainer-security-advisory
|
||||
- /github/managing-security-vulnerabilities/creating-a-maintainer-security-advisory
|
||||
@@ -15,31 +15,31 @@ topics:
|
||||
- Security advisories
|
||||
- Vulnerabilities
|
||||
shortTitle: Create repository advisories
|
||||
ms.openlocfilehash: 5c78a8b0c0a2d5085a876de2b0788ef093c4c6b1
|
||||
ms.sourcegitcommit: 74c60a4564bcc17e47b5a67941ac6d9fe13b6a5c
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/30/2022
|
||||
ms.locfileid: '148186153'
|
||||
---
|
||||
|
||||
Anyone with admin permissions to a repository can create a security advisory.
|
||||
任何对仓库有管理员权限的人都可以创建安全通告。
|
||||
|
||||
{% data reusables.security-advisory.security-researcher-cannot-create-advisory %}
|
||||
|
||||
## Creating a security advisory
|
||||
## 创建安全通知
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-security %}
|
||||
{% data reusables.repositories.sidebar-advisories %}
|
||||
1. Click **New draft security advisory** to open the draft advisory form. The fields marked with an asterisk are required.
|
||||
|
||||
1. Type a title for your security advisory.
|
||||
{% data reusables.repositories.security-advisory-edit-details %}
|
||||
{% data reusables.repositories.security-advisory-edit-severity %}
|
||||
{% data reusables.repositories.security-advisory-edit-cwe-cve %}
|
||||
{% data reusables.repositories.security-advisory-edit-description %}
|
||||
1. Click **Create draft security advisory**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-security %} {% data reusables.repositories.sidebar-advisories %}
|
||||
1. 单击“新建安全公告草稿”，打开草稿公告表单。 带有星号的所有字段为必填项。
|
||||
|
||||
1. 键入安全通告的标题。
|
||||
{% data reusables.repositories.security-advisory-edit-details %} {% data reusables.repositories.security-advisory-edit-severity %} {% data reusables.repositories.security-advisory-edit-cwe-cve %} {% data reusables.repositories.security-advisory-edit-description %}
|
||||
1. 单击“创建安全公告草稿”。
|
||||
|
||||
|
||||
## Next steps
|
||||
## 后续步骤
|
||||
|
||||
- Comment on the draft security advisory to discuss the vulnerability with your team.
|
||||
- Add collaborators to the security advisory. For more information, see "[Adding a collaborator to a repository security advisory](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)."
|
||||
- Privately collaborate to fix the vulnerability in a temporary private fork. For more information, see "[Collaborating in a temporary private fork to resolve a repository security vulnerability](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)."
|
||||
- Add individuals who should receive credit for contributing to the security advisory. For more information, see "[Editing a repository security advisory](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)."
|
||||
- Publish the security advisory to notify your community of the security vulnerability. For more information, see "[Publishing a repository security advisory](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)."
|
||||
- 评论安全通告草稿，与团队讨论漏洞。
|
||||
- 添加协作者到安全通告。 有关详细信息，请参阅“[将协作者添加到存储库安全公告](/code-security/repository-security-advisories/adding-a-collaborator-to-a-repository-security-advisory)”。
|
||||
- 在临时私有复刻中私下协作以修复漏洞。 有关详细信息，请参阅“[在临时专用分支中协作以解决存储库安全漏洞](/code-security/repository-security-advisories/collaborating-in-a-temporary-private-fork-to-resolve-a-repository-security-vulnerability)”。
|
||||
- 添加因对安全通告做出贡献而应获得积分的个人。 有关详细信息，请参阅“[编辑存储库安全公告](/code-security/repository-security-advisories/editing-a-repository-security-advisory#about-credits-for-security-advisories)”。
|
||||
- 发布安全通告以向社区提醒安全漏洞。 有关详细信息，请参阅“[发布存储库安全公告](/code-security/repository-security-advisories/publishing-a-repository-security-advisory)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a codespace for a repository
|
||||
intro: You can create a codespace for a branch in a repository to develop online.
|
||||
title: 为存储库创建 codespace
|
||||
intro: 您可以为仓库中的分支创建代码空间以便在线开发。
|
||||
redirect_from:
|
||||
- /github/developing-online-with-github-codespaces/creating-a-codespace
|
||||
- /github/developing-online-with-codespaces/creating-a-codespace
|
||||
@@ -14,95 +14,100 @@ topics:
|
||||
- Fundamentals
|
||||
- Developer
|
||||
shortTitle: Create a codespace for a repo
|
||||
ms.openlocfilehash: 409c946feda4ffbd3d9ab615b6ea07fabee3f530
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188318'
|
||||
---
|
||||
## 关于为存储库创建 codespace
|
||||
|
||||
## About creating a codespace for a repository
|
||||
{% data reusables.codespaces.ways-to-create-a-codespace %}使用本文中的选项卡显示有关创建 codespace 的每种方法的说明。
|
||||
|
||||
{% data reusables.codespaces.ways-to-create-a-codespace %} Use the tabs in this article to display instructions for each of these ways of creating a codespace.
|
||||
|
||||
{% data reusables.codespaces.starting-new-project-template %} For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
{% data reusables.codespaces.starting-new-project-template %}有关详细信息，请参阅“[通过模板创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)”。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: If you use a JetBrains IDE, you can use {% data variables.product.prodname_cli %} to create a codespace. You can then use the JetBrains Gateway application to open the codespace in a JetBrains IDE. For more information, see "[Using Codespaces in your JetBrains IDE](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)."
|
||||
注意：如果使用 JetBrains IDE，则可以使用 {% data variables.product.prodname_cli %} 创建 codespace。 然后，你就可以使用 JetBrains Gateway 应用程序在 JetBrains IDE 中打开 codespace。 有关详细信息，请参阅“[在 JetBrains IDE 中使用 Codespaces](/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can use {% data variables.product.prodname_github_codespaces %} on your personal {% data variables.product.prodname_dotcom_the_website %} account, with the quota of free use included each month for accounts on the Free and Pro plans. {% data reusables.codespaces.codespaces-continue-by-paying %}
|
||||
可以在个人 {% data variables.product.prodname_dotcom_the_website %} 帐户上使用 {% data variables.product.prodname_github_codespaces %}，其中免费版和专业版计划中的帐户包含每月免费使用配额。 {% data reusables.codespaces.codespaces-continue-by-paying %}
|
||||
|
||||
Organizations can enable members and outside collaborators to create and use codespaces at the organization's expense. For more information, see "[Enabling {% data variables.product.prodname_github_codespaces %} for your organization](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)."
|
||||
组织可以让成员和外部协作者能够创建和使用 codespace，费用由组织承担。 有关详细信息，请参阅“[为组织启用 {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-codespaces-for-your-organization/enabling-github-codespaces-for-your-organization)”。
|
||||
|
||||
{% data reusables.codespaces.codespaces-are-personal %}
|
||||
|
||||
If you create a codespace from a repository, the codespace will be associated with a specific branch, which cannot be empty. You can create more than one codespace per repository or even per branch.
|
||||
如果从存储库创建 codespace，该 codespace 将与不能为空的特定分支相关联。 每个仓库甚至每个分支可创建多个代码空间。
|
||||
|
||||
{% data reusables.codespaces.you-can-see-all-your-codespaces %}
|
||||
|
||||
### The codespace creation process
|
||||
### codespace 创建过程
|
||||
|
||||
When you create a codespace, a number of steps happen to create and connect you to your development environment:
|
||||
创建代码空间时，需要执行一些步骤并将您连接到开发环境。
|
||||
|
||||
- Step 1: VM and storage are assigned to your codespace.
|
||||
- Step 2: Container is created and your repository is cloned.
|
||||
- Step 3: You can connect to the codespace.
|
||||
- Step 4: Codespace continues with post-creation setup.
|
||||
- 第 1 步：虚拟机和存储被分配到您的代码空间。
|
||||
- 第 2 步：创建容器并克隆仓库。
|
||||
- 第 3 步：您可以连接到代码空间。
|
||||
- 第 4 步：代码空间继续创建后设置。
|
||||
|
||||
For more information on what happens when you create a codespace, see "[Deep Dive](/codespaces/getting-started/deep-dive)."
|
||||
有关创建 codespace 时发生的情况的详细信息，请参阅“[深入探讨](/codespaces/getting-started/deep-dive)。”
|
||||
|
||||
For more information on the lifecycle of a codespace, see "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)."
|
||||
有关 codespace 生命周期的详细信息，请参阅“[codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)”。
|
||||
|
||||
If you want to use Git hooks for your codespace, then you should set up hooks using the [`devcontainer.json` lifecycle scripts](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts), such as `postCreateCommand`, during step 4. Since your codespace container is created after the repository is cloned, any [git template directory](https://git-scm.com/docs/git-init#_template_directory) configured in the container image will not apply to your codespace. Hooks must instead be installed after the codespace is created. For more information on using `postCreateCommand`, see the [`devcontainer.json` reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties) in the {% data variables.product.prodname_vscode_shortname %} documentation.
|
||||
如果要对 codespace 使用 Git 挂钩，则应在步骤 4 中使用 [`devcontainer.json` 生命周期脚本](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)（如 `postCreateCommand`）设置挂钩。 由于在克隆存储库之后创建了 codespace 容器，因此在容器映像中配置的任何[ git 模板目录](https://git-scm.com/docs/git-init#_template_directory)将不适用于你的 codespace。 在创建代码空间后，必须改为安装挂钩。 有关使用 `postCreateCommand` 的详细信息，请参阅 {% data variables.product.prodname_vscode_shortname %} 文档中的 [`devcontainer.json` 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_devcontainerjson-properties)。
|
||||
|
||||
{% data reusables.codespaces.use-visual-studio-features %}
|
||||
|
||||
{% data reusables.codespaces.prebuilds-crossreference %}
|
||||
|
||||
## Creating a codespace for a repository
|
||||
## 为存储库创建 codespace
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create a codespace for.
|
||||
1. 在存储库名称下，使用“分支”下拉菜单，然后选择要为其创建 codespace 的分支。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
1. 单击“{% octicon "code" aria-label="The code icon" %} 代码”按钮，然后单击“codespace”选项卡。
|
||||
|
||||
|
||||
|
||||
|
||||
If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed below the **Create codespace on BRANCH** button telling you who will pay for the codespace.
|
||||
如果此存储库的 codespace 的计费对象为组织或其父企业，则会在“在 BRANCH 上创建 codespace”按钮下方显示一条消息，告知谁将为 codespace 付费。
|
||||
|
||||
1. Create your codespace, either using the default options, or after configuring advanced options:
|
||||
1. 使用默认选项或在配置高级选项之后创建 codespace：
|
||||
|
||||
* **Use the default options**
|
||||
* 使用默认选项
|
||||
|
||||
To create a codespace using the default options, click the plus sign ({% octicon "plus" aria-label="The plus icon" %}). Alternatively, if you don't currently have any codespaces for this repository, you can click **Create codespace on BRANCH**.
|
||||
要使用默认选项创建 codespace，请单击“加号 ({% octicon "plus" aria-label="The plus icon" %})”。 如果当前没有此存储库的任何 codespace，也可以单击“在 BRANCH 上创建 codespace”。
|
||||
|
||||
* **Configure options**
|
||||
* **配置选项**
|
||||
|
||||
To configure advanced options for your codespace, such as a different machine type or a particular `devcontainer.json` file:
|
||||
若要配置 codespace 高级选项（例如其他计算机类型或特定 `devcontainer.json` 文件），请执行以下操作：
|
||||
|
||||
1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab and select **New with options**.
|
||||
1. 单击“Codespaces”选项卡右上角的省略号 (…)，然后单击“使用选项新建” 。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the options page for your codespace, choose your preferred options from the dropdown menus.
|
||||
1. 在 codespace 选项页上，从下拉菜单中选择首选选项。
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**
|
||||
**说明**
|
||||
|
||||
* You can bookmark the options page to give you a quick way to create a codespace for this repository and branch.
|
||||
* The [https://github.com/codespaces/new](https://github.com/codespaces/new) page provides a quick way to create a codespace for any repository and branch. You can get to this page quickly by typing `codespace.new` into your browser's address bar.
|
||||
* For more information about the `devcontainer.json` file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
|
||||
* For more information about machine types, see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)."
|
||||
* 可以为选项页添加书签，以便快速创建此存储库和分支的 codespace。
|
||||
* [https://github.com/codespaces/new](https://github.com/codespaces/new) 页提供了为任何存储库和分支创建 codespace 的快速方法。 可以通过在浏览器的地址栏中输入 `codespace.new` 来快速访问此页面。
|
||||
* 有关 `devcontainer.json` 文件的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
|
||||
* 有关计算机类型的详细信息，请参阅“[更改 codespace 的计算机类型](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace#about-machine-types)”。
|
||||
* {% data reusables.codespaces.codespaces-machine-type-availability %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Click **Create codespace**.
|
||||
1. 单击“创建 codespace”。
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -116,30 +121,30 @@ If you want to use Git hooks for your codespace, then you should set up hooks us
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
To create a new codespace, use the `gh codespace create` subcommand.
|
||||
若要创建新的 codespace，请使用 `gh codespace create` 子命令。
|
||||
|
||||
```shell
|
||||
gh codespace create
|
||||
```
|
||||
|
||||
You are prompted to choose a repository. If codespaces for this repository are billable to an organization, or its parent enterprise, a message is displayed telling you who will pay for the codespace. You are then prompted to choose a branch, a dev container configuration file (if more than one is available), and a machine type (if more than one is available).
|
||||
系统会提示你选择存储库。 如果此存储库的 codespace 的计费对象为组织或其父企业，则会显示一条消息，告知谁将为 codespace 付费。 系统将提示你选择分支、开发容器配置文件（如果有多个可用）和计算机类型（如果有多个可用）。
|
||||
|
||||
Alternatively, you can use flags to specify some or all of the options:
|
||||
或者，您可以使用标志来指定部分或全部选项：
|
||||
|
||||
```shell
|
||||
gh codespace create -r OWNER/REPO -b BRANCH --devcontainer-path PATH -m MACHINE-TYPE
|
||||
```
|
||||
|
||||
In this example, replace `owner/repo` with the repository identifier. Replace `branch` with the name of the branch, or the full SHA hash of the commit, that you want to be initially checked out in the codespace. If you use the `-r` flag without the `b` flag, the codespace is created from the default branch.
|
||||
在此示例中，将 `owner/repo` 替换为存储库标识符。 将 `branch` 替换为你希望最初在 codespace 中签出的分支的名称或提交的完整 SHA 哈希。 如果使用 `-r` 标志而不使用 `b` 标志，则从默认分支创建 codespace。
|
||||
|
||||
Replace `path` with the path to the dev container configuration file you want to use for the new codespace. If you omit this flag and more than one dev container file is available you will be prompted to choose one from a list. For more information about the dev container configuration file, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
将 `path` 替换为要用于新的 codespace 的开发容器配置文件的路径。 如果省略此标志，并且有多个开发容器文件可用，系统将提示你从列表中选择一个文件。 有关开发容器配置文件的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
|
||||
Replace `machine-type` with a valid identifier for an available machine type. Identifiers are strings such as: `basicLinux32gb` and `standardLinux32gb`. The type of machines that are available depends on the repository, your personal account, and your location. If you enter an invalid or unavailable machine type, the available types are shown in the error message. If you omit this flag and more than one machine type is available you will be prompted to choose one from a list.
|
||||
将 `machine-type` 替换为可用计算机类型的有效标识符。 标识符是字符串，例如：`basicLinux32gb` 和 `standardLinux32gb`。 可用的计算机类型取决于存储库、个人帐户以及你的位置。 如果输入无效或不可用的计算机类型，则错误消息中将显示可用类型。 如果省略此标志，并且有多个计算机类型可用，系统将提示您从列表中选择一个计算机类型。
|
||||
|
||||
For full details of the options for this command, see [the {% data variables.product.prodname_cli %} manual](https://cli.github.com/manual/gh_codespace_create).
|
||||
有关此命令的选项的完整详细信息，请参阅 [{% data variables.product.prodname_cli %} 手册](https://cli.github.com/manual/gh_codespace_create)。
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Further reading
|
||||
- "[Opening an existing codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)"
|
||||
- "[Adding an 'Open in {% data variables.product.prodname_github_codespaces %}' badge](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)"
|
||||
## 延伸阅读
|
||||
- “[打开现有 codespace](/codespaces/developing-in-codespaces/opening-an-existing-codespace)”
|
||||
- [添加“在 {% data variables.product.prodname_github_codespaces %} 中打开”徽章](/codespaces/setting-up-your-project-for-codespaces/adding-a-codespaces-badge)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a codespace from a template
|
||||
intro: If you're starting a new project, you can create a codespace from a blank template or choose a template specially designed for the type of work you want to do.
|
||||
title: 通过模板创建 codespace
|
||||
intro: 如果要启动新项目，可以通过空白模板创建 codespace，或者选择专为你要执行的工作类型设计的模板。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -11,92 +11,95 @@ topics:
|
||||
- Developer
|
||||
shortTitle: Create a codespace from a template
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: 9e7ee0d110e962fa755f5f57cc70bc3cab341808
|
||||
ms.sourcegitcommit: 1f3bd126ca000982c538f1621d47722737740943
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148188310'
|
||||
---
|
||||
## 关于适用于 {% data variables.product.prodname_github_codespaces %} 的模板
|
||||
|
||||
## About templates for {% data variables.product.prodname_github_codespaces %}
|
||||
|
||||
If you're starting a new project, you can get started with development work quickly by creating a codespace from a template. You'll be able to work on your project in a cloud-based development environment, save your files in the cloud, and publish your work to a new remote repository that you can share with others or clone to your local machine.
|
||||
如果要启动新项目，可以通过从模板创建 codespace 来快速开始开发工作。 你将能够在基于云的开发环境中处理项目、将文件保存在云中，以及将工作发布到可与他人共享或克隆到本地计算机的新远程存储库中。
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Codespaces created from a template, rather than from a repository, are always billed to your personal account. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)."
|
||||
注意：通过模板（而不是存储库）创建的 codespace 将始终向个人帐户计费。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
You can start from a blank template, choose from templates maintained by {% data variables.product.company_short %} for popular technologies such as React or Jupyter Notebook, or launch a codespace from any template repository on {% data variables.product.prodname_dotcom %}. With a blank template, you'll start with an empty directory, with access to cloud-based compute resources and the tools, languages, and runtime environments that come preinstalled with the default codespace image. With other templates, you'll get starter files for the technology you're working with, plus typically some extra files such as a README file, a `.gitignore` file, and dev container configuration files containing some custom environment configuration. For more information on dev containers and the default image, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
可以从空白模板开始着手，从 {% data variables.product.company_short %} 维护的模板中选择 React 或 Jupyter Notebook 等常用技术，或者从 {% data variables.product.prodname_dotcom %} 上的任何模板存储库中启动 codespace。 使用空白模板时，你将从空目录开始创建，并且可以访问基于云的计算资源，以及预安装了默认 codespace 映像的工具、语言和运行时环境。 使用其他模板时，你将获得当前所用技术的入门文件，通常还有一些额外文件，例如自述文件、`.gitignore` 文件和包含一些自定义环境配置的开发容器配置文件。 有关开发容器和默认映像的详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
|
||||
As an example, if you create a codespace from {% data variables.product.company_short %}'s React template, you'll arrive in a workspace containing template files for a simple application, such as `index.js`, `app.js`, and `package.json`. Shortly after the codespace opens, a development server will start up automatically, and you will be able to view the running application in a simple browser tab within the {% data variables.product.prodname_vscode_shortname %} web client.
|
||||
例如，如果通过 {% data variables.product.company_short %} 的React 模板创建 codespace，则将到达包含简单应用程序的模板文件的工作区中，例如 `index.js`、`app.js` 和 `package.json`。 在 codespace 打开后不久，开发服务器将自动启动，并且你将能够在 {% data variables.product.prodname_vscode_shortname %} Web 客户端内的简单浏览器选项卡中查看正在运行的应用程序。
|
||||
|
||||
|
||||
|
||||
|
||||
The files and configuration included in templates are defined in template repositories. The template repository is cloned into your codespace when you create the codespace. After that, the link is severed, and your codespace won't be linked to a remote repository until you publish to one.
|
||||
模板中包含的文件和配置在模板存储库中定义。 创建 codespace 时，模板存储库将克隆到 codespace 中。 之后，链接将被切断，并且 codespace 将不会链接到远程存储库，直到你发布到远程存储库为止。
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** To help people get started with your framework, library, or other project, you can set up a template repository for use with {% data variables.product.prodname_github_codespaces %}. For more information, see "[Setting up a template repository for {% data variables.product.prodname_github_codespaces %}](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)."
|
||||
提示：为了帮助用户开始使用你的框架、库或其他项目，你可以设置模板存储库，以便与 {% data variables.product.prodname_github_codespaces %} 配合使用。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_github_codespaces %} 的模板存储库](/codespaces/setting-up-your-project-for-codespaces/setting-up-a-template-repository-for-github-codespaces)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Creating a codespace from a {% data variables.product.company_short %} template
|
||||
## 通过 {% data variables.product.company_short %} 模板创建 codespace
|
||||
|
||||
Templates maintained by {% data variables.product.company_short %}, including the blank template, are available from the "Your codespaces" page.
|
||||
{% data variables.product.company_short %} 维护的模板（包括空白模板）在“你的 codespace”页中提供。
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
{% data reusables.codespaces.view-all-templates-step %}
|
||||
1. Optionally, to view the template repository containing the files for a template, click the name of the template.
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %} {% data reusables.codespaces.view-all-templates-step %}
|
||||
1. （可选）若要查看包含模板文件的模板存储库，请单击模板的名称。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Under the template you want to launch, click **Use this template**.
|
||||
1. 在要启动的模板下，单击“**使用此模板**”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% data reusables.codespaces.template-codespaces-default-editor %}
|
||||
|
||||
## Creating a codespace from a template repository
|
||||
## 通过模板存储库创建 codespace
|
||||
|
||||
You can create a codespace from any template repository, then publish your work to a new repository when you are ready. For more information on template repositories, see "[Creating a repository from a template](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)."
|
||||
可以通过任何模板存储库创建 codespace，然后在准备就绪后将工作发布到新存储库。 有关模板存储库的详细信息，请参阅“[通过模板创建存储库](/repositories/creating-and-managing-repositories/creating-a-repository-from-a-template#about-repository-templates)”。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.codespaces.open-template-in-codespace-step %}
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.codespaces.open-template-in-codespace-step %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you're a maintainer of the template repository, and want to commit changes to the template repository itself, you should create a codespace from the **{% octicon "code" aria-label="The code icon" %} Code** dropdown. For more information, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
备注：如果你是模板存储库的维护者，并且要将更改提交到模板存储库本身，则应通过“{% octicon "code" aria-label="The code icon" %} 代码”下拉列表创建 codespace 。 有关详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.codespaces.template-codespaces-default-editor %}
|
||||
|
||||
## Publishing to a repository on {% data variables.product.product_name %}
|
||||
## 发布到 {% data variables.product.product_name %} 上的存储库
|
||||
|
||||
{% data reusables.codespaces.about-publishing-templates %}
|
||||
|
||||
### Publishing from {% data variables.product.prodname_vscode_shortname %}
|
||||
### 从 {% data variables.product.prodname_vscode_shortname %} 发布
|
||||
|
||||
{% data reusables.codespaces.publishing-template-codespaces %}
|
||||
|
||||
When a codespace is published, you have access to a greater range of options to customize your {% data variables.product.prodname_github_codespaces %} experience. For example, you can:
|
||||
发布 codespace 后，你可以使用更多选项来自定义 {% data variables.product.prodname_github_codespaces %} 体验。 例如，你能够：
|
||||
|
||||
- Change the machine type of your codespace to make sure you're using resources appropriate for the work you're doing (see "[Changing the machine type for your codespace](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)").
|
||||
- Allow {% data variables.product.prodname_dotcom %} to automatically use GPG to sign commits you make in your codespace (see "[Managing GPG verification for {% data variables.product.prodname_github_codespaces %}](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)").
|
||||
- Share encrypted secrets with your codespace (see "[Managing encrypted secrets for your codespaces](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)").
|
||||
- 更改 codespace 的计算机类型，以确保使用适合你当前所执行工作的资源（请参阅“[更改 codespace 的计算机类型](/codespaces/customizing-your-codespace/changing-the-machine-type-for-your-codespace)”）。
|
||||
- 允许 {% data variables.product.prodname_dotcom %} 自动使用 GPG 对 codespace 中的提交进行签名（请参阅“[管理 {% data variables.product.prodname_github_codespaces %} 的 GPG 验证](/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces)”）。
|
||||
- 与 codespace 共享加密机密（请参阅“[管理 codespace 的加密机密](/codespaces/managing-your-codespaces/managing-encrypted-secrets-for-your-codespaces)”）。
|
||||
|
||||
### Publishing from {% data variables.product.prodname_dotcom_the_website %}
|
||||
### 从 {% data variables.product.prodname_dotcom_the_website %} 发布
|
||||
|
||||
You can publish an unpublished codespace from the "Your codespaces" page on {% data variables.product.prodname_dotcom_the_website %}. This is useful if you want to publish a codespace that you don't currently have open in your browser. If you do this, your work will be preserved in a repository, but there won't be a link between your existing codespace and the new repository. However, you can navigate to the new repository and create a codespace from there, and this codespace will be connected to the repository.
|
||||
可以从 {% data variables.product.prodname_dotcom_the_website %} 上“你的 codespaces”页面中发布未发布的 codespace。 如果要发布当前未在浏览器中打开的 codespace，此做法非常有用。 如果执行此操作，你的工作将保留在存储库中，但现有 codespace 和新存储库之间不会有链接。 但是，你可以导航到新存储库并从那里创建 codespace，并且此 codespace 将连接到存储库。
|
||||
|
||||
{% data reusables.codespaces.your-codespaces-procedure-step %}
|
||||
1. Next to the unpublished codespace, click the ellipsis (**...**), then select **Publish to a new repository**.
|
||||
1. 在未发布的 codespace 旁边，单击省略号 (...) ，然后选择“发布到新存储库” 。
|
||||
|
||||
|
||||
1. Choose a name for your new repository, set it as **Public** or **Private**, and click **Create repository**.
|
||||
|
||||
1. 为新存储库选择一个名称，将其设置为“公共”或“专用”，然后单击“创建存储库” 。
|
||||
|
||||
|
||||
1. Optionally, to view the new repository, click **See repository**.
|
||||
|
||||
1. （可选）若要查看新存储库，请单击“查看存储库”。
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)"
|
||||
- "[The codespace lifecycle](/codespaces/getting-started/the-codespace-lifecycle)"
|
||||
- "[Using source control in your codespace](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)"
|
||||
- [为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository)
|
||||
- [codespace 生命周期](/codespaces/getting-started/the-codespace-lifecycle)
|
||||
- [在 codespace 中使用源代码管理](/codespaces/developing-in-codespaces/using-source-control-in-your-codespace)
|
||||
|
||||
@@ -9,12 +9,12 @@ topics:
|
||||
- Codespaces
|
||||
redirect_from:
|
||||
- /codespaces/prebuilding-your-codespaces/about-codespaces-prebuilds
|
||||
ms.openlocfilehash: e0962e410f2227a23ff98c8a3e7995ea8ec8a914
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.openlocfilehash: eecb77b541cc735fcf788fbc5da6960cabad899d
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158795'
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191916'
|
||||
---
|
||||
## 概述
|
||||
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Configuring prebuilds
|
||||
title: 配置预生成
|
||||
shortTitle: Configure prebuilds
|
||||
intro: You can configure your project to prebuild a codespace automatically each time you push a change to your repository.
|
||||
intro: 可以配置项目，使其在你每次将更改推送到存储库时自动预生成 codespace。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -10,106 +10,111 @@ topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
permissions: People with admin access to a repository can configure prebuilds for the repository.
|
||||
ms.openlocfilehash: dbb355e150695f27d1d6a7fa51eccc33a0ebde4f
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159115'
|
||||
---
|
||||
可以为存储库的特定分支与特定开发容器配置文件的组合设置预生成配置。
|
||||
|
||||
You can set up a prebuild configuration for the combination of a specific branch of your repository with a specific dev container configuration file.
|
||||
从启用预生成的父分支创建的所有分支通常也会获得同一开发容器配置的预生成。 这是因为使用父分支所用开发容器配置的子分支的预生成在大多数情况下是相同的，因此可以帮助开发人员从这些分支更快地创建 codespace。 有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)”。
|
||||
|
||||
Any branches created from a prebuild-enabled parent branch will typically also get prebuilds for the same dev container configuration. This is because prebuilds for child branches that use the same dev container configuration as the parent branch are, for the most part, identical, so developers can benefit from faster codespace creation times on those branches also. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers)."
|
||||
通常，如果为分支配置预生成，预生成可用于多种计算机类型。 但是，如果存储库大于 32 GB，预生成就不适用于 2 核和 4 核计算机类型，因为这些计算机类型提供的存储限制为 32 GB。
|
||||
|
||||
Typically, when you configure prebuilds for a branch, prebuilds will be available for multiple machine types. However, if your repository is greater than 32 GB, prebuilds won't be available for 2-core and 4-core machine types, since the storage these provide is limited to 32 GB.
|
||||
## 先决条件
|
||||
|
||||
## Prerequisites
|
||||
预生成是使用 {% data variables.product.prodname_actions %} 创建的。 因此，必须在要为其配置预生成的存储库中启用 {% data variables.product.prodname_actions %}。 有关详细信息，请参阅“[管理存储库的 {% data variables.product.prodname_actions %} 设置](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)”。
|
||||
|
||||
Prebuilds are created using {% data variables.product.prodname_actions %}. As a result, {% data variables.product.prodname_actions %} must be enabled for the repository for which you are configuring prebuilds. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)."
|
||||
|
||||
## Configuring prebuilds
|
||||
## 配置预生成
|
||||
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. In the "Prebuild configuration" section of the page, click **Set up prebuild**.
|
||||
1. 在页面的“预生成配置”部分，单击“设置预生成”。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Choose the branch for which you want to set up prebuilds.
|
||||
1. 选择要为其设置预生成的分支。
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Any branches created from a prebuild-enabled base branch will typically also get prebuilds for the same dev container configuration. For example, if you enable prebuilds for a dev container configuration file on the default branch of the repository, branches based on the default branch will, in most cases, also get prebuilds for the same dev container configuration.
|
||||
**注意**：从启用预生成的基础映像分支创建的所有分支通常也会获得同一开发容器配置的预生成。 例如，如果在存储库的默认分支上为开发容器配置文件启用预生成，则大多数情况下，基于默认分支的分支也会获得同一开发容器配置的预生成。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Optionally, in the **Configuration file** dropdown menu that's displayed, choose the `devcontainer.json` configuration file that you want to use for your prebuilds. For more information, see "[Introduction to dev containers](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)."
|
||||
1. 根据需要，可以在显示的“配置文件”下拉菜单中选择要用于预生成的 `devcontainer.json` 配置文件。 有关详细信息，请参阅“[开发容器简介](/codespaces/setting-up-your-project-for-codespaces/introduction-to-dev-containers#devcontainerjson)”。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Choose how you want to automatically trigger prebuild updates.
|
||||
1. 选择要如何自动触发预生成更新。
|
||||
|
||||
* **Every push** (the default setting) - With this setting, prebuilds will be updated on every push made to the given branch. This will ensure that codespaces generated from a prebuild always contain the latest codespace configuration, including any recently added or updated dependencies.
|
||||
* **On configuration change** - With this setting, prebuilds will be updated every time associated configuration files for a given repo and branch are updated. This ensures that changes to the dev container configuration files for the repository are used when a codespace is generated from a prebuild. The {% data variables.product.prodname_actions %} workflow that updates the prebuilds will run less often, so this option will use fewer {% data variables.product.prodname_actions %} minutes. However, this option will not guarantee that codespaces always include recently added or updated dependencies, so these may have to be added or updated manually after a codespace has been created.
|
||||
* **Scheduled** - With this setting, you can have your prebuilds updated on a custom schedule that's defined by you. This can reduce consumption of {% data variables.product.prodname_actions %} minutes, however, with this option, codespaces may be created that do not use the latest dev container configuration changes.
|
||||
* 每次推送（默认设置）- 通过此设置，预生成将在每次对给定分支进行推送时更新。 这可确保从预生成生成的 codespace 始终包含最新的 codespace 配置，包括任何最近添加或更新的依赖项。
|
||||
* 配置更改时 - 使用此设置时，每次更新给定存储库和分支的相关配置文件时，都会更新预生成。 这可确保在从预生成生成 codespace 时使用对存储库的开发容器配置文件进行的更改。 更新预生成的 {% data variables.product.prodname_actions %} 工作流的运行频率较低，因此此选项使用的 {% data variables.product.prodname_actions %} 分钟数较少。 但是，此选项不保证 codespace 始终包含最近添加或更新的依赖项，因此在创建 codespace 后可能需要手动添加或更新这些依赖项。
|
||||
* 计划 - 使用此设置，可以根据你定义的自定义计划更新预生成。 这可以减少 {% data variables.product.prodname_actions %} 分钟数消耗，但是，使用此选项，可以创建 codespace，而不使用最新的开发容器配置更改。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, select **Reduce prebuild available to only specific regions** to create prebuilds only in specified regions. Select the regions in which you want prebuilds to be available.
|
||||
1. 根据需要，可以选择“减少仅对特定区域可用的预生成”，以便仅在指定区域中创建预生成。 选择要在其中提供预生成的区域。
|
||||
|
||||
By default, prebuilds are created in all of the available regions, incurring storage charges per prebuild.
|
||||
默认情况下，预生成在所有可用区域中创建，每个预生成都会产生存储费用。
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes**:
|
||||
* The prebuild in each region incurs individual storage charges. You should, therefore, only enable prebuilds for regions in which you know they'll be used. For more information, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)."
|
||||
* Developers can set their default region for {% data variables.product.prodname_github_codespaces %}, which can allow you to enable prebuilds for fewer regions. For more information, see "[Setting your default region for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)."
|
||||
**注释**：
|
||||
* 每个区域的预生成会产生单独的存储费用。 因此，应只为已知将使用的区域启用预生成。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#billing-for-codespaces-prebuilds)”。
|
||||
* 开发人员可以为 {% data variables.product.prodname_github_codespaces %} 设置其默认区域，这样就可以减少要启用预生成的区域。 有关详细信息，请参阅“[为 {% data variables.product.prodname_github_codespaces %} 设置默认区域](/codespaces/customizing-your-codespace/setting-your-default-region-for-github-codespaces)”。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
1. Optionally, under **Template history**, set the number of prebuild versions to be retained. You can input any number between 1 and 5. The default number of saved versions is 2, which means that only the latest prebuild and the previous version are saved.
|
||||
1. 根据需要，可以在“模板历史记录”下设置要保留的预生成模板版本数。 可以输入介于 1 和 5 之间的任意数字。 默认保存的版本数为 2，这意味着只保存最新版本的和上一个版本的预生成。
|
||||
|
||||
|
||||
|
||||
|
||||
Depending on your prebuild trigger settings, your prebuild could change with each push or on each dev container configuration change. Retaining older versions of prebuilds enables you to create a prebuild from an older commit with a different dev container configuration than the current prebuild. This setting allows you to set the number of retained versions to a level that is appropriate for your needs.
|
||||
根据预生成触发器设置，预生成可能会随每个推送或每个开发容器配置的更改而更改。 保留较旧版本的预生成使你能够使用与当前预生成不同的开发容器配置从较旧的提交创建预生成。 通过此设置可将保留的版本数设置为所需的级别。
|
||||
|
||||
If you set the number of prebuild versions to save to 1, {% data variables.product.prodname_github_codespaces %} will only save the latest version of the prebuild and will delete the older version each time the template is updated. This means you will not get a prebuilt codespace if you go back to an older dev container configuration.
|
||||
如果将保存的预生成版本数设置为 1，{% data variables.product.prodname_github_codespaces %} 将仅保存最新版本的预生成，并在每次模板更新时删除旧版本。 这意味着，如果返回到较旧的开发容器配置，则不会获取预生成的 codespace。
|
||||
|
||||
There is a storage cost associated with each prebuild version that's retained. For example, if you are generating prebuilds in 4 regions and retaining 2 versions, you will be charged for storage of up to 8 prebuilds. For more information on billing, see "[About billing for {% data variables.product.prodname_github_codespaces %}](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)."
|
||||
保留的每个预生成版本都需支付存储费用。 例如，如果要在 4 个区域中生成预生成并保留 2 个版本，则最多需要支付 8 个预生成的存储费用。 有关计费的详细信息，请参阅“[关于 {% data variables.product.prodname_github_codespaces %} 的计费](/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#codespaces-pricing)”。
|
||||
|
||||
1. Optionally, add users or teams to notify when the prebuild workflow run fails for this configuration. You can begin typing a username, team name, or full name, then click the name once it appears to add them to the list. The users or teams you add will receive an email when prebuild failures occur, containing a link to the workflow run logs to help with further investigation.
|
||||
1. 根据需要，可以添加用户或团队，以便在此配置的预生成工作流运行失败时发出通知。 可以开始键入用户名、团队名称或全名，然后在显示名称后单击该名称以将其添加到列表中。 发生预生成失败时，添加的用户或团队将收到电子邮件，其中包含工作流运行日志链接，以帮助进一步调查。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Optionally, at the bottom of the page, click **Show advanced options**.
|
||||
1. 根据需要，单击页面底部的“显示高级选项”。
|
||||
|
||||
|
||||
|
||||
|
||||
In the "Advanced options" section, if you select **Disable prebuild optimization**, codespaces will be created without a prebuild if the latest prebuild workflow has failed or is currently running. For more information, see "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)."
|
||||
在“高级选项”部分中，如果选择“禁用预生成优化”，则当最新的预生成工作流失败或当前正在运行时，将在没有预生成的情况下创建 codespace。 有关详细信息，请参阅“[预生成故障排除](/codespaces/troubleshooting/troubleshooting-prebuilds#preventing-out-of-date-prebuilds-being-used)”。
|
||||
|
||||
1. Click **Create**.
|
||||
1. 单击“创建”。
|
||||
|
||||
{% data reusables.codespaces.prebuilds-permission-authorization %}
|
||||
|
||||
After you create a prebuild configuration it is listed on the {% data variables.product.prodname_github_codespaces %} page of your repository settings. A {% data variables.product.prodname_actions %} workflow is queued and then run to create prebuilds in the regions you specified, based on the branch and dev container configuration file you selected.
|
||||
创建预生成配置后，它会列在存储库设置的 {% data variables.product.prodname_github_codespaces %} 页面中。 {% data variables.product.prodname_actions %} 工作流已排队，然后会运行，从而根据所选分支和开发容器配置文件在指定的区域中创建预生成。
|
||||
|
||||
|
||||
|
||||
|
||||
For information about editing and deleting prebuild configurations, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)."
|
||||
有关编辑和删除预生成配置的信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds)”。
|
||||
|
||||
## Configuring environment variables
|
||||
## 配置环境变量
|
||||
|
||||
To allow the prebuild process to access environment variables required to create your development environment, you can set these either as {% data variables.product.prodname_codespaces %} repository secrets or as {% data variables.product.prodname_codespaces %} organization secrets. For more information, see "[Adding secrets for a repository](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)" and "[Adding secrets for an organization](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)."
|
||||
若要让预生成过程能够访问创建开发环境所需的环境变量，可将这些变量设置为 {% data variables.product.prodname_codespaces %} 存储库机密或为 {% data variables.product.prodname_codespaces %} 组织机密。 有关详细信息，请参阅“[为存储库添加机密](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-a-repository)”和“[为组织添加机密](/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-github-codespaces#adding-secrets-for-an-organization)”。
|
||||
|
||||
Secrets that you create in this way will be accessible by anyone who creates a codespace from this repository. If you do not want this, you can alternatively set the `CODESPACES_PREBUILD_TOKEN` secret. The `CODESPACES_PREBUILD_TOKEN` secret is only used for prebuilding and its value is not accessible in users' codespaces.
|
||||
以这种方式创建的机密将由从该存储库创建 codespace 的任何人访问。 如果不希望这样，也可以设置 `CODESPACES_PREBUILD_TOKEN` 机密。 `CODESPACES_PREBUILD_TOKEN` 机密仅用于预生成，并且无法在用户的 codespace 中访问其值。
|
||||
|
||||
Prebuilds cannot use any user-level secrets while building your environment, because these are not available until after the codespace has been created.
|
||||
预生成在生成环境时不会使用任何用户级机密，因为这些机密在创建 codespace 后才会可用。
|
||||
|
||||
## Configuring time-consuming tasks to be included in the prebuild
|
||||
## 配置预生成中包含的耗时任务
|
||||
|
||||
You can use the `onCreateCommand` and `updateContentCommand` commands in your `devcontainer.json` to include time-consuming processes as part of the prebuild creation. For more information, see the {% data variables.product.prodname_vscode %} documentation, "[devcontainer.json reference](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)."
|
||||
可以在 `devcontainer.json` 中使用 `onCreateCommand` 和 `updateContentCommand` 命令，以将耗时过程作为预生成创建的一部分。 有关详细信息，请参阅 {% data variables.product.prodname_vscode %} 文档“[devcontainer.json 参考](https://code.visualstudio.com/docs/remote/devcontainerjson-reference#_lifecycle-scripts)”。
|
||||
|
||||
`onCreateCommand` is run only once, when the prebuild is created, whereas `updateContentCommand` is run at creation of the prebuild and at subsequent updates to it. Incremental builds should be included in `updateContentCommand` since they represent the source of your project and need to be included for every prebuild update.
|
||||
`onCreateCommand` 只在创建预生成时运行一次，而 `updateContentCommand` 在预生成创建和预生成后续更新时运行。 增量生成应包含在 `updateContentCommand` 中，因为它们代表项目的源，并且需要包含在每次预生成更新中。
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[Allowing a prebuild to access other repositories](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)"
|
||||
- "[Troubleshooting prebuilds](/codespaces/troubleshooting/troubleshooting-prebuilds)"
|
||||
- “[允许预生成访问其他存储库](/codespaces/prebuilding-your-codespaces/allowing-a-prebuild-to-access-other-repositories)”
|
||||
- [对预生成进行故障排除](/codespaces/troubleshooting/troubleshooting-prebuilds)
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Adding an "Open in GitHub Codespaces" badge
|
||||
title: 添加“在 GitHub Codespaces 中打开”锁屏提醒
|
||||
shortTitle: Add a Codespaces badge
|
||||
intro: You can add a badge to a Markdown file in your repository which people can click to create a codespace.
|
||||
intro: 可以将锁屏提醒添加到存储库中的 Markdown 文件，用户可以单击该文件来创建 codespace。
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -10,50 +10,55 @@ type: how_to
|
||||
topics:
|
||||
- Codespaces
|
||||
- Set up
|
||||
ms.openlocfilehash: c69a815501f5943a56d32af3e58cd7850a69588b
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158779'
|
||||
---
|
||||
## 概述
|
||||
|
||||
## Overview
|
||||
向 Markdown 文件添加“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒可让用户轻松地为存储库创建 codespace。
|
||||
|
||||
Adding an "Open in {% data variables.product.prodname_github_codespaces %}" badge to a Markdown file gives people an easy way to create a codespace for your repository.
|
||||
|
||||
|
||||
|
||||
创建锁屏提醒时，可以为锁屏提醒将创建的 codespace 选择特定配置选项。
|
||||
|
||||
When you create a badge you can choose specific configuration options for the codespace that the badge will create.
|
||||
当人们单击锁屏提醒时，他们会进入用于创建 codespace 的高级选项页，其中包含你预先选择的选项。 有关高级选项页的详细信息，请参阅“[为存储库创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)”。
|
||||
|
||||
When people click the badge they'll be taken to the advanced options page for codespace creation, with the options you chose preselected. For more information about the advanced options page, see "[Creating a codespace for a repository](/codespaces/developing-in-codespaces/creating-a-codespace-for-a-repository#creating-a-codespace-for-a-repository)."
|
||||
在高级选项页中，用户可以根据需要更改预先选择的设置，然后单击“创建 codespace”。
|
||||
|
||||
From the advanced options page, users can change the preselected settings if required, then click **Create codespace**.
|
||||
|
||||
## Creating an "Open in {% data variables.product.prodname_github_codespaces %}" badge
|
||||
## 创建“在 {% data variables.product.prodname_github_codespaces %} 中打开”锁屏提醒
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under the repository name, use the "Branch" dropdown menu, and select the branch you want to create the badge for.
|
||||
1. 在存储库名称下，使用“分支”下拉菜单选择要为其创建徽章的分支。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click the **{% octicon "code" aria-label="The code icon" %} Code** button, then click the **Codespaces** tab.
|
||||
1. 单击“{% octicon "code" aria-label="The code icon" %} 代码”按钮，然后单击“codespace”选项卡。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click the ellipsis (**...**) at the top right of the **Codespaces** tab, then click **New with options**.
|
||||
1. 单击“Codespace”选项卡右上角的省略号 (…)，然后单击“新建选项” 。
|
||||
|
||||
|
||||
|
||||
|
||||
1. On the advanced options page for codespace creation, select the values you want to be preselected in each field.
|
||||
1. 在用于创建 codespace 的高级选项页上，选择要在每个字段中预先选择的值。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Copy the URL from the browser's address bar.
|
||||
1. Add the following Markdown to, for example, the `README.md` file of your repository:
|
||||
1. 复制浏览器地址栏中的 URL。
|
||||
1. 例如，将以下 Markdown 添加到存储库的 `README.md` 文件：
|
||||
|
||||
```Markdown{:copy}
|
||||
[](COPIED-URL)
|
||||
```
|
||||
|
||||
For example:
|
||||
例如：
|
||||
|
||||
```Markdown
|
||||
[](https://github.com/codespaces/new?hide_repo_select=true&ref=main&repo=0000000&machine=premiumLinux&devcontainer_path=.devcontainer%2Fdevcontainer.json&location=WestUs2)
|
||||
```
|
||||
|
||||
In the above example, `0000000` will be the reference number of your repository. The other details in the URL are determined by the values you selected in the fields on the advanced options page.
|
||||
在上面的示例中，`0000000` 会是存储库的引用编号。 URL 中的其他详细信息由在高级选项页上的字段中选择的值确定。
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Troubleshooting prebuilds
|
||||
title: 对预生成进行故障排除
|
||||
shortTitle: Codespaces prebuilds
|
||||
intro: You can use prebuilds to speed up the creation of codespaces. This article provides troubleshooting steps for common issues with prebuilds.
|
||||
intro: 可以使用预生成来加快 codespace 的创建速度。 本文提供有关预生成的常见问题的故障排除步骤。
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -9,86 +9,91 @@ type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
miniTocMaxHeadingLevel: 3
|
||||
ms.openlocfilehash: b8c45f9eae6094b78026d055ebea27c3748a8681
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148158883'
|
||||
---
|
||||
有关 {% data variables.product.prodname_github_codespaces %} 预生成的详细信息，请参阅“[预生成 codespace](/codespaces/prebuilding-your-codespaces)”。
|
||||
|
||||
For more information about {% data variables.product.prodname_github_codespaces %} prebuilds, see "[Prebuilding your codespaces](/codespaces/prebuilding-your-codespaces)."
|
||||
## 检查是否从预生成创建 codespace？
|
||||
|
||||
## Checking whether a codespace was created from a prebuild?
|
||||
创建 codespace 时，可选择要使用的虚拟机类型。 如果预生成可用于该类型的虚拟机，其旁边会显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”。
|
||||
|
||||
When you create a codespace, you can choose the type of the virtual machine you want to use. If a prebuild is available for the type of virtual machine, "{% octicon "zap" aria-label="The zap icon" %} Prebuild ready" is shown next to it.
|
||||
|
||||
|
||||
|
||||
如果将 {% data variables.product.prodname_github_codespaces %} 编辑器首选项设置为“{% data variables.product.prodname_vscode %} for Web”，则“设置 codespace”页面将显示“找到预生成 codespace”消息（如果正在使用预生成）。
|
||||
|
||||
If you have your {% data variables.product.prodname_github_codespaces %} editor preference set to "{% data variables.product.prodname_vscode %} for Web" then the "Setting up your codespace" page will show the message "Prebuilt codespace found" if a prebuild is being used.
|
||||
|
||||
|
||||
|
||||
同样，如果编辑器首选项为“{% data variables.product.prodname_vscode_shortname %}”，则在创建新 codespace 时，集成终端将包含“你位于存储库预生成配置定义的预生成 codespace 上”消息。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_github_codespaces %} 的默认编辑器](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)”。
|
||||
|
||||
Similarly, if your editor preference is "{% data variables.product.prodname_vscode_shortname %}" then the integrated terminal will contain the message "You are on a prebuilt codespace defined by the prebuild configuration for your repository" when you create a new codespace. For more information, see "[Setting your default editor for {% data variables.product.prodname_github_codespaces %}](/codespaces/customizing-your-codespace/setting-your-default-editor-for-github-codespaces)."
|
||||
|
||||
After you have created a codespace you can check whether it was created from a prebuild by running the following {% data variables.product.prodname_cli %} command in the terminal:
|
||||
创建 codespace 后，可以通过在终端中运行以下 {% data variables.product.prodname_cli %} 命令来检查它是否是从预生成创建的：
|
||||
|
||||
```shell{:copy}
|
||||
gh api /user/codespaces/$CODESPACE_NAME --jq .prebuild
|
||||
```
|
||||
|
||||
This returns `true` if the codespace was created using a prebuild.
|
||||
如果 codespace 是使用预生成创建的，则返回 `true`。
|
||||
|
||||
Alternatively, if {% data variables.product.prodname_cli %} (`gh`) is not installed, you can use the following command, which returns `createFromPrebuild` if the codespace was created from a prebuild:
|
||||
或者，如果未安装 {% data variables.product.prodname_cli %} (`gh`)，则可以使用以下命令，该命令返回 `createFromPrebuild`（如果从预生成创建 codespace）：
|
||||
|
||||
```shell{:copy}
|
||||
cat /workspaces/.codespaces/shared/environment-variables.json | jq '.ACTION_NAME'
|
||||
```
|
||||
|
||||
## The "Prebuild Ready" label is sometimes missing
|
||||
## 有时缺少“预生成就绪”标签
|
||||
|
||||
You may notice that sometimes, when you create a new codespace from a prebuild-enabled branch, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed in the dialog box for choosing a machine type. This means that prebuilds are not currently available.
|
||||
你可能会注意到，有时，当从启用预生成的分支创建新 codespace 时，选择计算机类型的对话框中不会显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签。 这意味着预生成当前不可用。
|
||||
|
||||
By default, each time you push to a prebuild-enabled branch, the prebuild is updated. If the push involves a change to the dev container configuration then, while the update is in progress, the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is removed from the list of machine types. During this time you can still create codespaces without a prebuild. If required, you can reduce the occasions on which prebuilds are unavailable for a repository by setting the prebuild to be updated only when you make a change to your dev container configuration files, or only on a custom schedule. For more information, see "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)."
|
||||
默认情况下，每次推送到启用预生成的分支时，预生成都会更新。 如果推送涉及对开发容器配置的更改，则在进行更新时，将从计算机类型列表中删除“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签。 在此期间，仍然可以在没有预生成的情况下创建 codespace。 如果需要，可将预生成设置为仅在对开发容器配置文件进行更改时更新，或仅按自定义计划更新，从而减少预生成不可用于存储库的情况。 有关详细信息，请参阅“[配置预生成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds#configuring-prebuilds)”。
|
||||
|
||||
If your branch is not specifically enabled for prebuilds it may still benefit from prebuilds if it was branched from a prebuild-enabled branch. However, if the dev container configuration is changed on your branch, so that it's not the same as the configuration on the base branch, prebuilds will no longer be available on your branch.
|
||||
如果你的分支没有专门为预生成启用，如果它是从启用预生成的分支分出来的，它仍然可以从预生成中受益。 但是，如果分支上的开发容器配置已更改，变得与基础分支上的配置不同，则分支上将不再提供预生成。
|
||||
|
||||
Here are things to check if the "{% octicon "zap" aria-label="The zap icon" %} Prebuild Ready" label is not displayed for a particular branch:
|
||||
检查特定分支是否未显示“{% octicon "zap" aria-label="The zap icon" %} 预生成就绪”标签需要完成以下事项：
|
||||
|
||||
* Confirm that a prebuild configuration exists for this branch. If you’re not a repository administrator, you'll need to reach out to one to confirm this.
|
||||
* Confirm that the prebuild configuration includes your region.
|
||||
* Check whether a change to the dev container configuration was pushed to the prebuild-enabled branch recently. If so, you will typically have to wait until the prebuild workflow run for this push completes before prebuilds are available again.
|
||||
* If no configuration changes were recently made, go to the **Actions** tab of your repository, click **{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} Prebuilds** in the workflows list, and check that prebuild workflow runs for the branch are succeeding. If latest runs of a workflow failed, and one or more of these failed runs contained changes to the dev container configuration, then there will be no available prebuilds for the associated branch.
|
||||
* 确认此分支存在预生成配置。 如果你不是存储库管理员，则需要联系其中一个管理员来确认这一点。
|
||||
* 确认预生成配置包括你的区域。
|
||||
* 检查开发容器配置的更改最近是否已推送到启用预生成的分支。 如果是这样，则通常必须等到此推送的预生成工作流运行完成，才能再次使用预生成。
|
||||
* 如果最近未进行任何配置更改，请转到存储库的“操作”选项卡，单击工作流列表中的“{% octicon "codespaces" aria-label="The Codespaces icon" %} {% data variables.product.prodname_codespaces %} 预生成”，并检查分支的预生成工作流运行是否成功 。 如果工作流的最新运行失败，并且其中一个或多个失败的运行包含对开发容器配置的更改，则关联的分支将没有可用的预生成。
|
||||
|
||||
## Some resources cannot be accessed in codespaces created using a prebuild
|
||||
## 在使用预生成创建的 codespace 中无法访问某些资源
|
||||
|
||||
If the `devcontainer.json` configuration file for a prebuild configuration specifies that permissions for access to other repositories are required, then the repository administrator is prompted to authorize these permissions when they create or update the prebuild configuration. If the administrator does not grant all of the requested permissions there's a chance that problems may occur in the prebuild, and in codespaces created from this prebuild. This is true even if the user who creates a codespace based on this prebuild _does_ grant all of the permissions when they are prompted to do so.
|
||||
如果预生成配置的 `devcontainer.json` 配置文件指定需要其他存储库的访问权限，则系统会提示存储库管理员在创建或更新预生成配置时授权这些权限。 如果管理员未授予所有请求的权限，则预生成及其创建的 codespace 中可能会出现问题。 即使基于此预生成创建 codespace 的用户在收到提示时授予了所有权限，也是如此。
|
||||
|
||||
## Troubleshooting failed workflow runs for prebuilds
|
||||
## 失败的预生成工作流运行故障排除
|
||||
|
||||
### Increasing the {% data variables.product.prodname_actions %} spending limit
|
||||
### 提高 {% data variables.product.prodname_actions %} 支出限制
|
||||
|
||||
Prebuilds are created and updated using {% data variables.product.prodname_actions %}. Your prebuild workflows will fail if you have used all of your {% data variables.product.prodname_actions %} minutes and have reached your spending limit. If this occurs you can increase your {% data variables.product.prodname_actions %} spending limit to allow the workflows to run. For more information, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."
|
||||
预生成是使用 {% data variables.product.prodname_actions %} 创建和更新的。 如果用完了所有 {% data variables.product.prodname_actions %} 分钟数并达到了支出限制，你的预生成工作流将会失败。 如果发生这种情况，可以增加 {% data variables.product.prodname_actions %} 支出限制，以允许工作流运行。 有关详细信息，请参阅“[管理 {% data variables.product.prodname_actions %} 的支出限制](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)”。
|
||||
|
||||
### Authorizing access permissions
|
||||
### 授予访问权限
|
||||
|
||||
If the `devcontainer.json` configuration file for a prebuild configuration is updated to specify that permissions for access to other repositories are required, and a repository administrator has not been prompted to authorize these permissions for the prebuild configuration, then the prebuild workflow may fail. Try updating the prebuild configuration, without making any changes. If, when you click **Update**, the authorization page is displayed, check that the requested permissions are appropriate and, if so, authorize the request. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)" and "[Managing access to other repositories within your codespace](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)."
|
||||
如果更新了预生成配置的 `devcontainer.json` 配置文件以指定需要其他存储库的访问权限，并且系统未提示存储库管理员为预生成配置授权这些权限，则预生成工作流可能会失败。 尝试在不进行任何更改的情况下更新预生成配置。 如果单击“更新”显示了授权页面，请检查请求的权限是否合适，如果合适，请授权该请求。 有关详细信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds#editing-a-prebuild-configuration)”和“[管理对 codespace 中其他存储库的访问](/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces#setting-additional-repository-permissions)”。
|
||||
|
||||
If the workflow runs for a prebuild configuration are failing, you can temporarily disable the prebuild configuration while you investigate. For more information, see "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)."
|
||||
如果预生成配置的工作流运行失败，则可以在调查时暂时禁用预生成配置。 有关详细信息，请参阅“[管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds#disabling-a-prebuild-configuration)”。
|
||||
|
||||
### Preventing out-of-date prebuilds being used
|
||||
### 防止使用过时预生成
|
||||
|
||||
By default, if the latest prebuild workflow has failed, then a previous prebuild for the same combination of repository, branch, and `devcontainer.json` configuration file will be used to create new codespaces. This behavior is called prebuild optimization.
|
||||
默认情况下，如果最新的预生成工作流失败，将通过先前使用相同组合的存储库、分支和 `devcontainer.json` 配置文件的预生成来创建新的 codespace。 此行为称为预生成优化。
|
||||
|
||||
We recommend keeping prebuild optimization enabled, because it helps ensure that codespaces can still be created quickly if an up-to-date prebuild is not available. However, as a repository administrator, you can disable prebuild optimization if you run into problems with prebuilt codespaces being behind the current state of the branch. If you disable prebuild optimization, codespaces for the relevant combination of repository, branch, and `devcontainer.json` file will be created without a prebuild if the latest prebuild workflow has failed or is currently running.
|
||||
建议启用预生成优化，因为它有助于确保在最新预生成不可用时仍可快速创建 codespace。 但如果遇到预生成 codespace 落后于分支当前状态的问题，存储库管理员可以禁用预生成优化。 如果禁用预生成优化，则当最新的预生成工作流失败或当前正在运行时，将在没有预生成的情况下创建存储库、分支和 `devcontainer.json` 文件相关组合的 codespace。
|
||||
|
||||
{% data reusables.codespaces.accessing-prebuild-configuration %}
|
||||
1. To the right of the affected prebuild configuration, select the ellipsis (**...**), then click **Edit**.
|
||||
1. 在受影响的预生成配置右侧，选择省略号 (…)，然后单击“编辑” 。
|
||||
|
||||
|
||||
1. Scroll to the bottom of the "Edit configuration" page and click **Show advanced options**.
|
||||
|
||||
1. 滚动到“编辑配置”页底部，然后单击“显示高级选项”。
|
||||
|
||||
|
||||
1. If you're sure you want to disable the default setting, select **Disable prebuild optimization**.
|
||||
|
||||
1. 如果确定要禁用默认设置，请选择“禁用预生成优化”。
|
||||
|
||||
|
||||
1. To save your change, click **Update**.
|
||||
|
||||
1. 若要保存更改，请单击“更新”。
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[Configuring prebuilds](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)"
|
||||
- "[Managing prebuilds](/codespaces/prebuilding-your-codespaces/managing-prebuilds)"
|
||||
- [配置预生成](/codespaces/prebuilding-your-codespaces/configuring-prebuilds)
|
||||
- [管理预生成](/codespaces/prebuilding-your-codespaces/managing-prebuilds)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 创建默认的社区运行状况文件
|
||||
intro: 您可以创建默认社区健康文件，例如 CONTRIBUTING 和 CODE_OF_CONDUCT。 默认文件将用于不包含该类型自有文件的帐户所拥有的任何仓库。
|
||||
title: Creating a default community health file
|
||||
intro: 'You can create default community health files, such as CONTRIBUTING and CODE_OF_CONDUCT. Default files will be used for any repository owned by the account that does not contain its own file of that type.'
|
||||
redirect_from:
|
||||
- /articles/creating-a-default-community-health-file-for-your-organization
|
||||
- /github/building-a-strong-community/creating-a-default-community-health-file-for-your-organization
|
||||
@@ -12,41 +12,46 @@ versions:
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Community health file
|
||||
ms.openlocfilehash: 762af2fcbbc16e0bfc671df2409fede9ea6e2c67
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145099301'
|
||||
---
|
||||
## 关于默认社区健康文件
|
||||
|
||||
可以将默认社区运行状况文件添加到存储库根目录下或者 `docs` 或 `.github` 文件夹中名为 `.github` 的公共存储库中。
|
||||
## About default community health files
|
||||
|
||||
对于在以下任何位置不含该类型自有文件的帐户所拥有的任何仓库，{% data variables.product.product_name %} 将使用并显示默认文件：
|
||||
- 仓库的根目录
|
||||
- `.github` 文件夹
|
||||
- `docs` 文件夹
|
||||
You can add default community health files to a public repository called `.github`, in the root of the repository or in the `docs` or `.github` folders.
|
||||
|
||||
例如，在不含自有 CONTRIBUTING 文件的仓库中创建议题或拉取请求的人将会看到指向默认 CONTRIBUTING 文件的链接。 如果存储库在其自己的 `.github/ISSUE_TEMPLATE` 文件夹{% ifversion fpt or ghes or ghec %}中含有任何文件，包括议题模板或 config.yml 文件，{% endif %}则不会使用默认 `.github/ISSUE_TEMPLATE` 文件夹的内容。
|
||||
{% data variables.product.product_name %} will use and display default files for any repository owned by the account that does not have its own file of that type in any of the following places:
|
||||
- the root of the repository
|
||||
- the `.github` folder
|
||||
- the `docs` folder
|
||||
|
||||
默认文件不包含在各个存储库的克隆、包或下载中，因为它们只存储在 `.github` 存储库中。
|
||||
For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
|
||||
|
||||
## 支持的文件类型
|
||||
Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
|
||||
|
||||
可以在组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}中为以下社区运行状况文件创建默认内容：
|
||||
## Supported file types
|
||||
|
||||
社区运行状况文件 | 说明 --- | ---{% ifversion fpt or ghec %} CODE_OF_CONDUCT.md | CODE_OF_CONDUCT 文件定义有关如何参与社区的标准。 有关详细信息，请参阅“[为项目添加行为准则](/articles/adding-a-code-of-conduct-to-your-project/)”。{% endif %} CONTRIBUTING.md | CONTRIBUTING 文件指示应如何参与你的项目。 有关详细信息，请参阅“[设置存储库贡献者指南](/articles/setting-guidelines-for-repository-contributors/)”。{% ifversion fpt or ghec %} FUNDING.yml | FUNDING 文件在存储库中显示发起人按钮，以提高开源项目资助选项的可见性。 有关详细信息，请参阅“[在存储库中显示发起人按钮](/articles/displaying-a-sponsor-button-in-your-repository)。”{% endif %} 问题和拉取请求模板 {% ifversion fpt or ghes or ghec %} 和 config.yml{% endif %} | 问题和拉取请求模板可自定义和标准化你希望参与者在存储库中打开问题或拉取请求时包含的信息。 有关详细信息，请参阅“[关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates/)。”{% ifversion fpt or ghes or ghec %} SECURITY.md | SECURITY 文件阐述了如何报告项目中的安全漏洞。 有关详细信息，请参阅“[向存储库添加安全策略](/code-security/getting-started/adding-a-security-policy-to-your-repository)。”{% endif %} SUPPORT.md | SUPPORT 文件介绍在项目中获取帮助的途径。 有关详细信息，请参阅“[向项目添加支持资源](/articles/adding-support-resources-to-your-project/)”。
|
||||
You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} for the following community health files:
|
||||
|
||||
您不能创建默认许可文件。 必须将许可文件添加到各个仓库中，以便在克隆、打包或下载项目时包含该文件。
|
||||
Community health file | Description
|
||||
--- | ---{% ifversion fpt or ghec %}
|
||||
*CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
|
||||
*CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion discussion-category-forms %}
|
||||
Discussion category forms | Discussion category forms customize the templates that are available for community members to use when they open new discussions in your repository. For more information, see "[Creating discussion category forms](/discussions/managing-discussions-for-your-community/creating-discussion-category-forms)."{% endif %}{% ifversion fpt or ghec %}
|
||||
*FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
|
||||
Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes or ghec %}
|
||||
*SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
|
||||
*SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
|
||||
|
||||
## 创建用于默认文件的仓库
|
||||
You cannot create a default license file. License files must be added to individual repositories so the file will be included when a project is cloned, packaged, or downloaded.
|
||||
|
||||
## Creating a repository for default files
|
||||
|
||||
{% data reusables.repositories.create_new %}
|
||||
2. 使用“所有者”下拉菜单，选择要为其创建默认文件的组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}。
|
||||
|
||||
3. 输入“.github”作为存储库的名称和描述（可选）。
|
||||
|
||||
4. 确保存储库状态设置为“公共”（默认文件的存储库不能是私有的）。
|
||||
 {% data reusables.repositories.initialize-with-readme %} {% data reusables.repositories.create-repo %}
|
||||
7. 在仓库中，创建一个受支持的社区健康文件。 议题模板 {% ifversion fpt or ghes or ghec %} 及其配置文件 {% endif %} 必须位于名为 `.github/ISSUE_TEMPLATE` 的文件夹中。 所有其他支持的文件可能位于存储库根目录、`.github` 文件夹或 `docs` 文件夹中。 有关详细信息，请参阅“[新建文件](/articles/creating-new-files/)”。
|
||||
2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %} you want to create default files for.
|
||||
|
||||
3. Type **.github** as the name for your repository, and an optional description.
|
||||
|
||||
4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
|
||||
|
||||
{% data reusables.repositories.initialize-with-readme %}
|
||||
{% data reusables.repositories.create-repo %}
|
||||
7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a pull request template for your repository
|
||||
intro: 'When you add a pull request template to your repository, project contributors will automatically see the template''s contents in the pull request body.'
|
||||
title: 为仓库创建拉取请求模板
|
||||
intro: 将拉取请求模板添加到仓库后，项目贡献者会自动在拉取请求正文中看到模板的内容。
|
||||
redirect_from:
|
||||
- /articles/creating-a-pull-request-template-for-your-repository
|
||||
- /github/building-a-strong-community/creating-a-pull-request-template-for-your-repository
|
||||
@@ -12,41 +12,44 @@ versions:
|
||||
topics:
|
||||
- Community
|
||||
shortTitle: Create a PR template
|
||||
ms.openlocfilehash: fa4d3cf78b63af147c85b8f6d77d7cca74e3853a
|
||||
ms.sourcegitcommit: 4daa156856e651cb3854ead40e35bd918e481ad6
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/02/2022
|
||||
ms.locfileid: '148190406'
|
||||
---
|
||||
有关详细信息，请参阅“[关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates)”。
|
||||
|
||||
For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)."
|
||||
|
||||
You can create a *PULL_REQUEST_TEMPLATE/* subdirectory in any of the supported folders to contain multiple pull request templates, and use the `template` query parameter to specify the template that will fill the pull request body. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
|
||||
可以在任何支持的文件夹中创建 PULL_REQUEST_TEMPLATE/ 子目录，以包含多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板。 有关详细信息，请参阅“[使用查询参数创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”。
|
||||
|
||||
{% ifversion fpt or ghes or ghec %}
|
||||
|
||||
You can create default pull request templates for your organization{% ifversion fpt or ghes or ghec %} or personal account{% endif %}. For more information, see "[Creating a default community health file](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)."
|
||||
可以为组织{% ifversion fpt or ghes or ghec %}或个人帐户{% endif %}创建默认的拉取请求模板。 有关详细信息，请参阅[创建默认社区运行状况文件](/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file)。
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Adding a pull request template
|
||||
## 添加拉取请求模板
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. In the file name field:
|
||||
- To make your pull request template visible in the repository's root directory, name the pull request template `pull_request_template.md`.
|
||||
|
||||
- To make your pull request template visible in the repository's `docs` directory, name the pull request template `docs/pull_request_template.md`.
|
||||
|
||||
- To store your file in a hidden directory, name the pull request template `.github/pull_request_template.md`.
|
||||
|
||||
- To create multiple pull request templates and use the `template` query parameter to specify a template to fill the pull request body, type *.github/PULL_REQUEST_TEMPLATE/*, then the name of your pull request template. For example, `.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`. You can also store multiple pull request templates in a `PULL_REQUEST_TEMPLATE` subdirectory within the root or `docs/` directories. For more information, see "[Using query parameters to create a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)."
|
||||
|
||||
4. In the body of the new file, add your pull request template. This could include:
|
||||
- A [reference to a related issue](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests) in your repository.
|
||||
- A description of the changes proposed in the pull request.
|
||||
- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) of the person or team responsible for reviewing proposed changes.
|
||||
{% data reusables.files.write_commit_message %}
|
||||
{% data reusables.files.choose_commit_branch %} Templates are available to collaborators when they are merged into the repository's default branch.
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
|
||||
3. 在文件名字段中：
|
||||
- 若要使拉取请求模板显示在存储库根目录中，请将拉取请求模板命名为 `pull_request_template.md`。
|
||||
|
||||
- 若要使拉取请求模板显示在存储库的 `docs` 目录中，请将拉取请求模板命名为 `docs/pull_request_template.md`。
|
||||
|
||||
- 若要将文件存储在隐藏目录中，请将拉取请求模板命名为 `.github/pull_request_template.md`。
|
||||
|
||||
- 若要创建多个拉取请求模板，并使用 `template` 查询参数指定填充拉取请求正文的模板，请键入“.github/PULL_REQUEST_TEMPLATE/”，后跟拉取请求模板的名称。 例如，`.github/PULL_REQUEST_TEMPLATE/pull_request_template.md`。 也可以在根目录或 `docs/` 目录的 `PULL_REQUEST_TEMPLATE` 子目录中存储多个拉取请求模板。 有关详细信息，请参阅“[使用查询参数创建拉取请求](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request)”。
|
||||
|
||||
4. 在新文件的正文中，添加您的拉取请求模板。 这可能包括：
|
||||
- 存储库中[对相关问题的引用](/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests)。
|
||||
- 对拉取请求中所提议更改的说明。
|
||||
- [@mentions](/articles/basic-writing-and-formatting-syntax/#mentioning-people-and-teams) 负责审查提议更改的人员或团队。
|
||||
{% data reusables.files.write_commit_message %} {% data reusables.files.choose_commit_branch %} 模板可供协作者用来合并到存储库的默认分支。
|
||||
{% data reusables.files.propose_new_file %}
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates)"
|
||||
- "[About automation for issues and pull requests with query parameters](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)"
|
||||
- "[Creating a pull request](/articles/creating-a-pull-request)"
|
||||
- [关于问题和拉取请求模板](/articles/about-issue-and-pull-request-templates)
|
||||
- [关于使用查询参数自动处理问题和拉取请求](/articles/about-automation-for-issues-and-pull-requests-with-query-parameters)
|
||||
- [创建拉取请求](/articles/creating-a-pull-request)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About apps
|
||||
intro: 'You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs to add flexibility and reduce friction in your own workflow.{% ifversion fpt or ghec %} You can also share integrations with others on [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace).{% endif %}'
|
||||
title: 关于应用程序
|
||||
intro: '你可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成来增加灵活性并减少自己工作流程中的摩擦。{% ifversion fpt or ghec %} 你也可以与 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 上的其他 API 集成。{% endif %}'
|
||||
redirect_from:
|
||||
- /apps/building-integrationssetting-up-a-new-integration
|
||||
- /apps/building-integrations
|
||||
@@ -14,93 +14,99 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- GitHub Apps
|
||||
ms.openlocfilehash: a66af14f6047b2aff435ac4ac8dc83d7a1181e92
|
||||
ms.sourcegitcommit: f638d569cd4f0dd6d0fb967818267992c0499110
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 10/25/2022
|
||||
ms.locfileid: '148107355'
|
||||
---
|
||||
Apps on {% data variables.product.prodname_dotcom %} allow you to automate and improve your workflow. You can build apps to improve your workflow.{% ifversion fpt or ghec %} You can also share or sell apps in [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace). To learn how to list an app on {% data variables.product.prodname_marketplace %}, see "[Getting started with GitHub Marketplace](/marketplace/getting-started/)."{% endif %}
|
||||
{% data variables.product.prodname_dotcom %} 上的应用程序允许您自动化并改进工作流程。 可以生成应用来改进工作流。{% ifversion fpt or ghec %}也可以在 [{% data variables.product.prodname_marketplace %}](https://github.com/marketplace) 中分享或销售应用。 若要了解如何在 {% data variables.product.prodname_marketplace %} 中上架应用，请参阅“[GitHub 市场入门](/marketplace/getting-started/)”。{% endif %}
|
||||
|
||||
{% data reusables.marketplace.github_apps_preferred %}, but GitHub supports both {% data variables.product.prodname_oauth_apps %} and {% data variables.product.prodname_github_apps %}. For information on choosing a type of app, see "[Differences between GitHub Apps and OAuth Apps](/developers/apps/differences-between-github-apps-and-oauth-apps)."
|
||||
{% data reusables.marketplace.github_apps_preferred %}，但 GitHub 支持 {% data variables.product.prodname_oauth_apps %} 和 {% data variables.product.prodname_github_apps %}。 有关选择应用类型的信息，请参阅“[GitHub 应用与 OAuth 应用的区别](/developers/apps/differences-between-github-apps-and-oauth-apps)”。
|
||||
|
||||
{% data reusables.apps.general-apps-restrictions %}
|
||||
|
||||
For a walkthrough of the process of building a {% data variables.product.prodname_github_app %}, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
|
||||
有关生成 {% data variables.product.prodname_github_app %} 的过程演练，请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。
|
||||
|
||||
## About {% data variables.product.prodname_github_apps %}
|
||||
## 关于 {% data variables.product.prodname_github_apps %}
|
||||
|
||||
{% data variables.product.prodname_github_apps %} are first-class actors within GitHub. A {% data variables.product.prodname_github_app %} acts on its own behalf, taking actions via the API directly using its own identity, which means you don't need to maintain a bot or service account as a separate user.
|
||||
{% data variables.product.prodname_github_apps %} 是 GitHub 中的一流产品。 {% data variables.product.prodname_github_app %} 应用程序以自己的名义运行，通过 API 直接使用自己的身份进行操作，这意味着您无需作为独立用户维护自动程序或服务帐户。
|
||||
|
||||
{% data variables.product.prodname_github_apps %} can be installed directly on organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions. When you set up your {% data variables.product.prodname_github_app %}, you can select the repositories you want it to access. For example, you can set up an app called `MyGitHub` that writes issues in the `octocat` repository and _only_ the `octocat` repository. To install a {% data variables.product.prodname_github_app %}, you must be an organization owner or have admin permissions in a repository.
|
||||
{% data variables.product.prodname_github_apps %} 可以直接安装在组织和个人帐户上，并获得对特定仓库的访问权限。 它们拥有内置 web 挂钩和狭窄的特定权限。 设置 {% data variables.product.prodname_github_app %}时，可以选择希望它访问的仓库。 例如，可以设置一个名为在存储库中`MyGitHub`写入问题且`octocat`仅 _写入_ 存储库的应用`octocat`。 要安装 {% data variables.product.prodname_github_app %}，您必须是组织所有者或在仓库中具有管理员权限。
|
||||
|
||||
{% data reusables.apps.app_manager_role %}
|
||||
|
||||
{% data variables.product.prodname_github_apps %} are applications that need to be hosted somewhere. For step-by-step instructions that cover servers and hosting, see "[Building Your First {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)."
|
||||
{% data variables.product.prodname_github_apps %} 是需要托管在某处的应用程序。 有关涵盖服务器和托管的分步说明，请参阅“[生成第一个 {% data variables.product.prodname_github_app %}](/apps/building-your-first-github-app)”。
|
||||
|
||||
To improve your workflow, you can create a {% data variables.product.prodname_github_app %} that contains multiple scripts or an entire application, and then connect that app to many other tools. For example, you can connect {% data variables.product.prodname_github_apps %} to GitHub, Slack, other in-house apps you may have, email programs, or other APIs.
|
||||
要改进自己的工作流程，可以创建一个包含多个脚本或整个应用程序的 {% data variables.product.prodname_github_app %}，然后将此应用程序连接至许多其他工具。 例如，您可以将 {% data variables.product.prodname_github_apps %} 连接至 GitHub、Slack、自己可能拥有的其他内部应用程序、电子邮件程序或其他 API。
|
||||
|
||||
Keep these ideas in mind when creating {% data variables.product.prodname_github_apps %}:
|
||||
创建 {% data variables.product.prodname_github_apps %} 时，请记住以下方法：
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
* {% data reusables.apps.maximum-github-apps-allowed %} {% endif %}
|
||||
* A {% data variables.product.prodname_github_app %} should take actions independent of a user (unless the app is using a [user-to-server](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests) token). {% data reusables.apps.expiring_user_authorization_tokens %}
|
||||
* {% data variables.product.prodname_github_app %} 的操作应独立于用户（除非此应用使用[用户到服务器](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps#user-to-server-requests)令牌）。 {% data reusables.apps.expiring_user_authorization_tokens %}
|
||||
|
||||
* Make sure the {% data variables.product.prodname_github_app %} integrates with specific repositories.
|
||||
* The {% data variables.product.prodname_github_app %} should connect to a personal account or an organization.
|
||||
* Don't expect the {% data variables.product.prodname_github_app %} to know and do everything a user can.
|
||||
* Don't use a {% data variables.product.prodname_github_app %} if you just need a "Login with GitHub" service. But a {% data variables.product.prodname_github_app %} can use a [user identification flow](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/) to log users in _and_ do other things.
|
||||
* Don't build a {% data variables.product.prodname_github_app %} if you _only_ want to act as a GitHub user and do everything that user can do.{% ifversion fpt or ghec %}
|
||||
* 请确保 {% data variables.product.prodname_github_app %} 与特定仓库集成。
|
||||
* {% data variables.product.prodname_github_app %} 应该连接到个人帐户或组织。
|
||||
* 不要指望 {% data variables.product.prodname_github_app %} 知道并尽其所能。
|
||||
* 如果您只需要“使用GitHub登录”服务，请不要使用 {% data variables.product.prodname_github_app %}。 但是 {% data variables.product.prodname_github_app %} 可以使用[用户标识流](/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps/)让用户登录和执行其他操作。
|
||||
* 如果只想充当 GitHub 用户并执行用户所能执行的所有操作，请不要生成 {% data variables.product.prodname_github_app %}。{% ifversion fpt or ghec %}
|
||||
* {% data reusables.apps.general-apps-restrictions %}{% endif %}
|
||||
|
||||
To begin developing {% data variables.product.prodname_github_apps %}, start with "[Creating a {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)."{% ifversion fpt or ghec %} To learn how to use {% data variables.product.prodname_github_app %} Manifests, which allow people to create preconfigured {% data variables.product.prodname_github_apps %}, see "[Creating {% data variables.product.prodname_github_apps %} from a manifest](/apps/building-github-apps/creating-github-apps-from-a-manifest/)."{% endif %}
|
||||
若要开始开发 {% data variables.product.prodname_github_apps %}，请从“[创建 {% data variables.product.prodname_github_app %}](/apps/building-github-apps/creating-a-github-app/)”开始。{% ifversion fpt or ghec %}若要了解如何使用 {% data variables.product.prodname_github_app %} 清单创建预配置的 {% data variables.product.prodname_github_apps %}，请参阅“[从清单创建 {% data variables.product.prodname_github_apps %}](/apps/building-github-apps/creating-github-apps-from-a-manifest/)”。{% endif %}
|
||||
|
||||
## About {% data variables.product.prodname_oauth_apps %}
|
||||
## 关于 {% data variables.product.prodname_oauth_apps %}
|
||||
|
||||
OAuth2 is a protocol that lets external applications request authorization to private details in a user's {% data variables.product.prodname_dotcom %} account without accessing their password. This is preferred over Basic Authentication because tokens can be limited to specific types of data and can be revoked by users at any time.
|
||||
OAuth2 是一种协议，它允许外部应用程序请求授权在不使用密码的情况下访问用户 {% data variables.product.prodname_dotcom %} 帐户中的私有信息。 此协议优先于基本验证，因为令牌可能仅限于特定类型的数据，用户可以随时撤销。
|
||||
|
||||
{% data reusables.apps.deletes_ssh_keys %}
|
||||
|
||||
An {% data variables.product.prodname_oauth_app %} uses {% data variables.product.prodname_dotcom %} as an identity provider to authenticate as the user who grants access to the app. This means when a user grants an {% data variables.product.prodname_oauth_app %} access, they grant permissions to _all_ repositories they have access to in their account, and also to any organizations they belong to that haven't blocked third-party access.
|
||||
{% data variables.product.prodname_oauth_app %} 使用 {% data variables.product.prodname_dotcom %} 作为身份提供程序以验证为授予应用程序访问权限的用户。 这意味着，当用户授予 {% data variables.product.prodname_oauth_app %} 访问权限时，将授权访问其帐户有权访问的所有存储库，以及他们所属的、未阻止第三方访问的任何组织。
|
||||
|
||||
Building an {% data variables.product.prodname_oauth_app %} is a good option if you are creating more complex processes than a simple script can handle. Note that {% data variables.product.prodname_oauth_apps %} are applications that need to be hosted somewhere.
|
||||
如果要创建比简单脚本的处理范围更复杂的流程，构建 {% data variables.product.prodname_oauth_app %} 是一个很好的选择。 请注意，{% data variables.product.prodname_oauth_apps %} 是需要托管在某处的应用程序。
|
||||
|
||||
Keep these ideas in mind when creating {% data variables.product.prodname_oauth_apps %}:
|
||||
创建 {% data variables.product.prodname_oauth_apps %} 时，请记住以下几点：
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
* {% data reusables.apps.maximum-oauth-apps-allowed %} {% endif %}
|
||||
* An {% data variables.product.prodname_oauth_app %} should always act as the authenticated {% data variables.product.prodname_dotcom %} user across all of {% data variables.product.prodname_dotcom %} (for example, when providing user notifications).
|
||||
* An {% data variables.product.prodname_oauth_app %} can be used as an identity provider by enabling a "Login with {% data variables.product.prodname_dotcom %}" for the authenticated user.
|
||||
* Don't build an {% data variables.product.prodname_oauth_app %} if you want your application to act on a single repository. With the `repo` OAuth scope, {% data variables.product.prodname_oauth_apps %} can act on _all_ of the authenticated user's repositories.
|
||||
* Don't build an {% data variables.product.prodname_oauth_app %} to act as an application for your team or company. {% data variables.product.prodname_oauth_apps %} authenticate as a single user, so if one person creates an {% data variables.product.prodname_oauth_app %} for a company to use, and then they leave the company, no one else will have access to it.{% ifversion fpt or ghec %}
|
||||
* {% data variables.product.prodname_oauth_app %} 在所有 {% data variables.product.prodname_dotcom %} 中（例如，在提供用户通知时）应始终代表经身份验证的 {% data variables.product.prodname_dotcom %} 用户。
|
||||
* 通过为经身份验证的用户启用“使用 {% data variables.product.prodname_dotcom %} 进行登录”，{% data variables.product.prodname_oauth_app %} 可用作身份提供程序。
|
||||
* 如果您希望应用程序作用于单个仓库，请不要构建 {% data variables.product.prodname_oauth_app %}。 使用 `repo` OAuth 作用域，{% data variables.product.prodname_oauth_apps %} 可以作用于经身份验证用户的所有存储库。
|
||||
* 不要构建 {% data variables.product.prodname_oauth_app %} 作为团队或公司的应用程序。 {% data variables.product.prodname_oauth_apps %} 将验证为单个用户，因此，如果有人创建了 {% data variables.product.prodname_oauth_app %} 供公司使用，那么一旦他们离开公司，其他人将无法访问它。{% ifversion fpt or ghec %}
|
||||
* {% data reusables.apps.oauth-apps-restrictions %}{% endif %}
|
||||
|
||||
For more on {% data variables.product.prodname_oauth_apps %}, see "[Creating an {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)" and "[Registering your app](/rest/guides/basics-of-authentication#registering-your-app)."
|
||||
有关 {% data variables.product.prodname_oauth_apps %} 的详细信息，请参阅“[创建 {% data variables.product.prodname_oauth_app %}](/apps/building-oauth-apps/creating-an-oauth-app/)”和“[注册应用](/rest/guides/basics-of-authentication#registering-your-app)”。
|
||||
|
||||
## {% data variables.product.pat_generic_caps %}s
|
||||
|
||||
A [{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) is a string of characters that functions similarly to an [OAuth token](/apps/building-oauth-apps/authorizing-oauth-apps/) in that you can specify its permissions via [scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/). A {% data variables.product.pat_generic %} is also similar to a password, but you can have many of them and you can revoke access to each one at any time.
|
||||
[{% data variables.product.pat_generic %}](/articles/creating-a-personal-access-token-for-the-command-line/) 是一个字符串，其功能类似于 [OAuth 令牌](/apps/building-oauth-apps/authorizing-oauth-apps/)，可以通过[作用域](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/)指定其权限。 {% data variables.product.pat_generic %} 还与密码类似，但你能拥有很多令牌，而且可以随时撤销对每个令牌的访问权限。
|
||||
|
||||
As an example, you can enable a {% data variables.product.pat_generic %} to write to your repositories. If then you run a cURL command or write a script that [creates an issue](/rest/reference/issues#create-an-issue) in your repository, you would pass the {% data variables.product.pat_generic %} to authenticate. You can store the {% data variables.product.pat_generic %} as an environment variable to avoid typing it every time you use it.
|
||||
例如，可以启用 {% data variables.product.pat_generic %} 以写入存储库。 如果随后运行 cURL 命令或编写在存储库中[创建问题](/rest/reference/issues#create-an-issue)的脚本，则需要传递 {% data variables.product.pat_generic %} 以进行身份验证。 可以将 {% data variables.product.pat_generic %} 存储为环境变量，以免每次使用时都要输入。
|
||||
|
||||
Keep these ideas in mind when using {% data variables.product.pat_generic %}s:
|
||||
使用 {% data variables.product.pat_generic %}s 时，请记住以下想法：
|
||||
|
||||
* Remember to use this token to represent yourself only.
|
||||
* You can perform one-off cURL requests.
|
||||
* You can run personal scripts.
|
||||
* Don't set up a script for your whole team or company to use.
|
||||
* Don't set up a shared personal account to act as a bot user.
|
||||
* Grant your token the minimal privileges it needs.
|
||||
* Set an expiration for your {% data variables.product.pat_generic %}s, to help keep your information secure.
|
||||
* 记得只能用此令牌代表您自己。
|
||||
* 您可以执行一次性 cURL 请求。
|
||||
* 您可以运行个人脚本。
|
||||
* 不要为整个团队或公司设置脚本。
|
||||
* 不要设置共享个人账户以用作自动程序用户。
|
||||
* 为令牌授予所需的最低特权。
|
||||
* 为 {% data variables.product.pat_generic %}s 设置过期时间，以帮助确保信息安全。
|
||||
|
||||
## Determining which integration to build
|
||||
## 确定要构建的集成
|
||||
|
||||
Before you get started creating integrations, you need to determine the best way to access, authenticate, and interact with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} APIs. The following image offers some questions to ask yourself when deciding whether to use {% data variables.product.pat_generic %}s, {% data variables.product.prodname_github_apps %}, or {% data variables.product.prodname_oauth_apps %} for your integration.
|
||||
在开始创建集成之前，您需要确定使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 访问、验证和交互的最佳方式。 下图提供了一些问题，你在决定是否对集成使用 {% data variables.product.pat_generic %}s、{% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %} 时可以考虑这些问题。
|
||||
|
||||
|
||||
|
||||
|
||||
Consider these questions about how your integration needs to behave and what it needs to access:
|
||||
请考虑关于您的集成需要如何操作及它需要访问什么等问题：
|
||||
|
||||
* Will my integration act only as me, or will it act more like an application?
|
||||
* Do I want it to act independently of me as its own entity?
|
||||
* Will it access everything that I can access, or do I want to limit its access?
|
||||
* Is it simple or complex? For example, {% data variables.product.pat_generic %}s are good for simple scripts and cURLs, whereas an {% data variables.product.prodname_oauth_app %} can handle more complex scripting.
|
||||
* 我的集成是只像我一样，还是更像一个应用程序？
|
||||
* 我是否希望它作为单独的实体独立于我运行？
|
||||
* 它是否能访问我可以访问的一切，或者说我想限制它的访问权限？
|
||||
* 它是简单还是复杂？ 例如，{% data variables.product.pat_generic %}s 对简单的脚本和 cURL 有益，而 {% data variables.product.prodname_oauth_app %} 可以处理更复杂的脚本。
|
||||
|
||||
## Requesting support
|
||||
## 请求支持
|
||||
|
||||
{% data reusables.support.help_resources %}
|
||||
|
||||
@@ -9,6 +9,8 @@ children:
|
||||
- /managing-categories-for-discussions
|
||||
- /moderating-discussions
|
||||
- /viewing-insights-for-your-discussions
|
||||
- /creating-discussion-category-forms
|
||||
- /syntax-for-discussion-category-forms
|
||||
ms.openlocfilehash: 156460ecfbb27820f11ccad388ceaff069f835b1
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
|
||||
@@ -1,215 +1,201 @@
|
||||
---
|
||||
title: Managing discussions
|
||||
intro: 'You can categorize, spotlight, transfer, or delete the discussions.'
|
||||
title: 管理讨论
|
||||
intro: 可以分类、聚焦、转让或删除讨论。
|
||||
permissions: Repository administrators and people with write or greater access to a repository can manage discussions in the repository. Repository administrators and people with write or greater access to the source repository for organization discussions can manage discussions in the organization.
|
||||
versions:
|
||||
feature: discussions
|
||||
shortTitle: Manage discussions
|
||||
redirect_from:
|
||||
- /discussions/managing-discussions-for-your-community/managing-discussions-in-your-repository
|
||||
ms.openlocfilehash: e5e1474648973c90d16e8998db18518331233aa3
|
||||
ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148164337'
|
||||
---
|
||||
## 关于讨论的管理
|
||||
|
||||
{% data reusables.discussions.about-discussions %} 有关讨论的详细信息，请参阅“[关于讨论](/discussions/collaborating-with-your-community-using-discussions/about-discussions)”。
|
||||
|
||||
## About management of discussions
|
||||
组织所有者可以选择在组织拥有的存储库中创建讨论所需的权限。 同样，若要选择创建组织讨论所需的权限，组织所有者可以更改源存储库中所需的权限。 有关详细信息，请参阅“[管理组织中存储库的讨论创建](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)”。
|
||||
|
||||
{% data reusables.discussions.about-discussions %} For more information about discussions, see "[About discussions](/discussions/collaborating-with-your-community-using-discussions/about-discussions)."
|
||||
作为讨论维护者，您可以创建社区资源，以鼓励与总体项目目标一致的讨论，并为协作者维护一个友好、开放的论坛。 为协作者制定{% ifversion fpt or ghec %}行为守则或{% endif %}参与指南将有助于促进协作和富有成效的论坛。 有关如何创建社区资源的详细信息，请参阅{% ifversion fpt or ghec %}“[向项目添加行为准则](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)”和{% endif %}“[设置适用于存储库参与者的指南](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)”。
|
||||
|
||||
Organization owners can choose the permissions required to create a discussion in repositories owned by the organization. Similarly, to choose the permissions required to create an organization discussion, organization owners can change the permissions required in the source repository. For more information, see "[Managing discussion creation for repositories in your organization](/organizations/managing-organization-settings/managing-discussion-creation-for-repositories-in-your-organization)."
|
||||
当讨论产生可以解决的想法或漏洞时，您可以从讨论创建新议题。 有关详细信息，请参阅“[创建问题](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)”。
|
||||
|
||||
As a discussions maintainer, you can create community resources to encourage discussions that are aligned with the overall project goal and maintain a friendly open forum for collaborators. Creating{% ifversion fpt or ghec %} a code of conduct or{% endif %} contribution guidelines for collaborators to follow will help facilitate a collaborative and productive forum. For more information on creating community resources, see{% ifversion fpt or ghec %} "[Adding a code of conduct to your project](/communities/setting-up-your-project-for-healthy-contributions/adding-a-code-of-conduct-to-your-project)," and{% endif %} "[Setting guidelines for repository contributors](/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors)."
|
||||
可以将讨论固定到存储库或组织的讨论列表顶部。 {% ifversion discussions-category-specific-pins %}还可以将讨论固定到特定类别。{% endif %}有关详细信息，请参阅“[固定讨论](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)”。
|
||||
|
||||
When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)."
|
||||
|
||||
You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)."
|
||||
|
||||
For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)."
|
||||
有关如何促进健康讨论的详细信息，请参阅“[缓和评论和对话](/communities/moderating-comments-and-conversations)”。
|
||||
|
||||
{% data reusables.discussions.you-can-label-discussions %}
|
||||
|
||||
## Prerequisites
|
||||
## 必备知识
|
||||
|
||||
To manage discussions in a repository, {% data variables.product.prodname_discussions %} must be enabled for the repository. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for a repository](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)."
|
||||
要管理仓库中的讨论，必须为仓库启用 {% data variables.product.prodname_discussions %}。 有关详细信息，请参阅“[启用或禁用存储库的 {% data variables.product.prodname_discussions %}](/github/administering-a-repository/enabling-or-disabling-github-discussions-for-a-repository)”。
|
||||
|
||||
To manage discussions in an organization, {% data variables.product.prodname_discussions %} must be enabled for the organization. For more information, see "[Enabling or disabling {% data variables.product.prodname_discussions %} for an organization](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)."
|
||||
若要管理组织中的讨论，必须为组织启用 {% data variables.product.prodname_discussions %}。 有关详细信息，请参阅“[启用或禁用组织的 {% data variables.product.prodname_discussions %}](/organizations/managing-organization-settings/enabling-or-disabling-github-discussions-for-an-organization)”。
|
||||
|
||||
## Changing the category for a discussion
|
||||
## 更改讨论类别
|
||||
|
||||
You can categorize discussions to help community members find related discussions. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
|
||||
您可以对讨论进行分类，以帮助社区成员查找相关的讨论。 有关详细信息，请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
|
||||
|
||||
You can also move a discussion to a different category. It's not possible to move a discussion to or from the polls category.
|
||||
您也可以将讨论移动到另一个类别。 无法将讨论移动到投票类别或从投票类别移出。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}.
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧边栏中“Category（类别）”的右侧，单击 {% octicon "gear" aria-label="The gear icon" %}。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click a category.
|
||||
1. 单击一个类别。
|
||||
|
||||
|
||||
|
||||
|
||||
## Pinning a discussion
|
||||
## 固定讨论
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category.
|
||||
{% ifversion discussions-category-specific-pins %} 可以将讨论固定在存储库或组织的讨论列表上方。 还可以将讨论固定到特定类别。 除了固定到特定类别的讨论外，还将显示全局固定讨论。
|
||||
|
||||
This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category.
|
||||
这是当你有一个全局固定讨论和固定到“想法”类别的讨论时的外观。
|
||||
|
||||
|
||||
|
||||
|
||||
### Pinning a discussion globally
|
||||
### 全局固定讨论
|
||||
{% endif %}
|
||||
|
||||
You can pin up to four important discussions above the list of discussions for the repository or organization.
|
||||
可以在存储库或组织讨论列表上固定多达四个重要的讨论。
|
||||
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“固定讨论”。
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% else %}
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
1. Optionally, customize the look of the pinned discussion.
|
||||
1. （可选）自定义固定讨论的外观。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Pin discussion**.
|
||||
1. 单击“固定讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
### Pinning a discussion to a category
|
||||
### 将讨论固定到类别
|
||||
|
||||
You can pin up to four important discussions above the list of discussions in a specific category.
|
||||
可以在特定类别的讨论列表上固定四个重要讨论。
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“将讨论固定到类别”。
|
||||
|
||||
|
||||
|
||||
|
||||
2. To confirm, click **Pin to CATEGORY**.
|
||||
2. 若要确认，请单击“固定到类别”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Editing a pinned discussion
|
||||
## 编辑固定的讨论
|
||||
|
||||
Editing a pinned discussion will not change the discussion's category. For more information, see "[Managing categories for discussions](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)."
|
||||
编辑固定的讨论不会更改讨论的类别。 有关详细信息，请参阅“[管理讨论的类别](/discussions/managing-discussions-for-your-community/managing-categories-for-discussions)”。
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧栏中，单击 {% octicon "pencil" aria-label="The pencil icon" %}“编辑固定讨论”。
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
 {% else %}
|
||||
 {% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
1. Customize the look of the pinned discussion.
|
||||
1. 自定义固定的讨论的外观。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Pin discussion**.
|
||||
1. 单击“固定讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
## Unpinning a discussion
|
||||
## 取消固定讨论
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category.
|
||||
可以从存储库或组织的讨论列表中取消固定讨论，也可以从特定类别的讨论列表中取消固定讨论。
|
||||
|
||||
### Unpinning a globally pinned discussion
|
||||
### 取消固定全局固定讨论
|
||||
|
||||
You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions.
|
||||
可以取消固定全局固定讨论。 这不会删除讨论，但讨论将不再显示在讨论列表上方。
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“取消固定讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Read the warning, then click **Unpin discussion**.
|
||||
1. 阅读警告，然后单击“取消固定讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
### Unpinning a discussion from a category
|
||||
### 从类别中取消固定讨论
|
||||
|
||||
You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category.
|
||||
可以取消固定到特定类别的讨论。 这不会删除讨论，但讨论将不再显示在类别上方。
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧边栏中，单击 {% octicon "pin" aria-label="The pin icon" %}“从该类别中取消固定讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Read the warning, then click **Unpin from this category**.
|
||||
1. 阅读警告，然后单击“从该类别取消固定”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Transferring a discussion
|
||||
## 转让讨论
|
||||
|
||||
To transfer a discussion, you must have permissions to create discussions in the repository where you want to transfer the discussion. If you want to transfer a discussion to an organization, you must have permissions to create discussions in the source repository for the organization's discussions. You can only transfer discussions between repositories owned by the same user or organization account. You can't transfer a discussion from a private{% ifversion ghec or ghes %} or internal{% endif %} repository to a public repository.
|
||||
要转让讨论，您必须具有在要转让讨论的仓库中创建讨论的权限。 如果要将讨论转让给组织，必须具有在组织的讨论的源存储库中创建讨论的权限。 您只能在同一用户或组织帐户拥有的仓库之间转让讨论。 不能将讨论从专用{% ifversion ghec or ghes %}或内部{% endif %}存储库转移到公共存储库。
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧边栏中，单击{% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}Transfer this discussion{% else %}“转移讨论”{% endif %} 。
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
 {% else %}
|
||||
 {% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions.
|
||||
1. 选择“选择存储库”下拉列表，并单击要将讨论转让到的存储库。 如果要将讨论转让给组织，请选择组织的讨论的源存储库。
|
||||
|
||||
|
||||
|
||||
|
||||
1. Click **Transfer discussion**.
|
||||
1. 单击“转让讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
## Deleting a discussion
|
||||
## 删除讨论
|
||||
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %}
|
||||
{% data reusables.discussions.discussions-tab %}
|
||||
{% data reusables.discussions.click-discussion-in-list %}
|
||||
1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**.
|
||||
{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %}
|
||||
1. 在右侧栏中，单击 {% octicon "trash" aria-label="The trash arrow icon" %}“删除讨论”。
|
||||
{% ifversion discussions-category-specific-pins %}
|
||||
|
||||
{% else %}
|
||||
{% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
{% endif %}
|
||||
|
||||
1. Read the warning, then click **Delete this discussion**.
|
||||
1. 阅读警告，然后单击“删除此讨论”。
|
||||
|
||||
|
||||
|
||||
|
||||
## Converting issues based on labels
|
||||
## 基于标签转换议题
|
||||
|
||||
You can convert all issues with the same label to discussions in bulk. Future issues with this label will also automatically convert to the discussion and category you configure.
|
||||
您可以将具有相同标签的所有议题批量转换为讨论。 具有此标签的未来议题也将自动转换为您配置的讨论和类别。
|
||||
|
||||
1. On {% data variables.location.product_location %}, navigate to the main page of the repository or, for organization discussions, the source repository.
|
||||
{% data reusables.repositories.sidebar-issues %}
|
||||
{% data reusables.project-management.labels %}
|
||||
1. Next to the label you want to convert to issues, click **Convert issues**.
|
||||
1. Select the **Choose a category** drop-down menu, and click a category for your discussion.
|
||||
1. Click **I understand, convert this issue to a discussion**.
|
||||
1. 在 {% data variables.location.product_location %} 上，导航到存储库主页；对于组织讨论，导航到源存储库主页。
|
||||
{% data reusables.repositories.sidebar-issues %} {% data reusables.project-management.labels %}
|
||||
1. 在要转换为问题的标签旁边，单击“转换问题”。
|
||||
1. 选择“选择类别”下拉菜单，然后单击某个类别进行讨论。
|
||||
1. 单击“我明白，将此问题转化为讨论”。
|
||||
|
||||
@@ -1,78 +1,84 @@
|
||||
---
|
||||
title: Create a group assignment
|
||||
intro: You can create a collaborative assignment for teams of students who participate in your course.
|
||||
title: 创建组分配
|
||||
intro: 您可以为参加您课程的学生团队创建协作作业。
|
||||
versions:
|
||||
fpt: '*'
|
||||
permissions: 'Organization owners who are admins for a classroom can create and manage group assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
|
||||
redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/create-group-assignments
|
||||
- /education/manage-coursework-with-github-classroom/create-a-group-assignment
|
||||
ms.openlocfilehash: 71c5f5eaf97ba58e25921c1e2be6fc638550dfa8
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179758'
|
||||
---
|
||||
## About group assignments
|
||||
## 关于组分配
|
||||
|
||||
{% data reusables.classroom.assignments-group-definition %} Students can work together on a group assignment in a shared repository, like a team of professional developers.
|
||||
{% data reusables.classroom.assignments-group-definition %} 学生可以像专业开发人员团队一样，在共享仓库中共同完成小组作业。
|
||||
|
||||
When a student accepts a group assignment, the student can create a new team or join an existing team. {% data variables.product.prodname_classroom %} saves the teams for an assignment as a set. You can name the set of teams for a specific assignment when you create the assignment, and you can reuse that set of teams for a later assignment.
|
||||
当学生接受小组作业时，该学生可以创建新团队或加入现有团队。 {% data variables.product.prodname_classroom %} 将任务团队保存为集合。 您可以在创建作业时为特定作业指定一组团队，并且在后面的作业中可以重复使用该组团队。
|
||||
|
||||
{% data reusables.classroom.classroom-creates-group-repositories %}
|
||||
|
||||
{% data reusables.classroom.about-assignments %}
|
||||
|
||||
You can decide how many teams one assignment can have, and how many members each team can have. Each team that a student creates for an assignment is a team within your organization on {% data variables.product.product_name %}. The visibility of the team is secret. Teams that you create on {% data variables.product.product_name %} will not appear in {% data variables.product.prodname_classroom %}. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
您可以决定一个任务可以拥有多少个团队，以及每个团队可以拥有多少成员。 学生为作业创建的每个团队都是 {% data variables.product.product_name %} 上组织内的团队。 团队的可见性是秘密。 您在 {% data variables.product.product_name %} 上创建的团队不会出现在 {% data variables.product.prodname_classroom %} 中。 有关详细信息，请参阅“[关于团队](/organizations/organizing-members-into-teams/about-teams)”。
|
||||
|
||||
For a video demonstration of the creation of a group assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
|
||||
有关创建小组作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本信息](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
|
||||
|
||||
{% data reusables.classroom.reuse-assignment-link %}
|
||||
|
||||
## Prerequisites
|
||||
## 先决条件
|
||||
|
||||
{% data reusables.classroom.assignments-classroom-prerequisite %}
|
||||
|
||||
## Creating an assignment
|
||||
## 创建作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-create-the-assignment %}
|
||||
|
||||
## Setting up the basics for an assignment
|
||||
## 设置作业的基本信息
|
||||
|
||||
Name your assignment, decide whether to assign a deadline, define teams, and choose the visibility of assignment repositories.
|
||||
指定作业的名称，决定是否分配截止时间，确定团队，并选择作业仓库的可见性。
|
||||
|
||||
- [Naming an assignment](#naming-an-assignment)
|
||||
- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
|
||||
- [Choosing an assignment type](#choosing-an-assignment-type)
|
||||
- [Defining teams for an assignment](#defining-teams-for-an-assignment)
|
||||
- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
|
||||
- [指定作业名称](#naming-an-assignment)
|
||||
- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
|
||||
- [选择作业类型](#choosing-an-assignment-type)
|
||||
- [确定作业的团队](#defining-teams-for-an-assignment)
|
||||
- [选择作业存储库的可见性](#choosing-a-visibility-for-assignment-repositories)
|
||||
|
||||
### Naming an assignment
|
||||
### 指定作业名称
|
||||
|
||||
For a group assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the name of the team. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the team's name on {% data variables.product.product_name %} is "student-team", the name of the assignment repository for members of the team will be `assignment-1-student-team`.
|
||||
对于小组作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和团队名称对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果将作业命名为“assignment-1”，而团队在 {% data variables.product.product_name %} 上的名称是“student-team”，则团队成员的作业存储库的名称将是 `assignment-1-student-team`。
|
||||
|
||||
{% data reusables.classroom.assignments-type-a-title %}
|
||||
|
||||
### Assigning a deadline for an assignment
|
||||
### 分配作业的截止时间
|
||||
|
||||
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
|
||||
|
||||
### Choosing an assignment type
|
||||
### 选择作业类型
|
||||
|
||||
Under "Individual or group assignment", select the drop-down menu, then click **Group assignment**. You can't change the assignment type after you create the assignment. If you'd rather create an individual assignment, see "[Create an individual assignment](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)."
|
||||
在“个人或小组作业”下，选择下拉菜单，然后单击“小组作业”。 创建作业后不可更改作业类型。 如果希望创建个人作业，请参阅“[创建个人作业](/education/manage-coursework-with-github-classroom/create-an-individual-assignment)”。
|
||||
|
||||
### Defining teams for an assignment
|
||||
### 确定作业的团队
|
||||
|
||||
If you've already created a group assignment for the classroom, you can reuse a set of teams for the new assignment. To create a new set with the teams that your students create for the assignment, type the name for the set. Optionally, type the maximum number of team members and total teams.
|
||||
如果已为教室创建了小组作业，可以对新作业重复使用一组团队。 要使用学生为作业创建的团队创建一个新组，请输入组的名称。 （可选）键入团队成员和团队总数的最大数量。
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tips**:
|
||||
**提示**：
|
||||
|
||||
- We recommend including details about the set of teams in the name for the set. For example, if you want to use the set of teams for one assignment, name the set after the assignment. If you want to reuse the set throughout a semester or course, name the set after the semester or course.
|
||||
- 我们建议在组的名称中包含有关该组团队的详细信息。 例如，如果要对某个作业使用团队组，请以作业命名该组。 如果要在整个学期或课程中重复使用该组，请以学期或课程命名该组。
|
||||
|
||||
- If you'd like to assign students to a specific team, give your students a name for the team and provide a list of members.
|
||||
- 如果想将学生分配到特定团队，请为学生指定团队的名称并提供成员列表。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
|
||||
|
||||
### Choosing a visibility for assignment repositories
|
||||
### 选择作业仓库的可见性
|
||||
|
||||
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
|
||||
|
||||
@@ -80,22 +86,22 @@ If you've already created a group assignment for the classroom, you can reuse a
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
|
||||
|
||||
## Adding starter code and configuring a development environment
|
||||
## 添加起始代码并配置开发环境
|
||||
|
||||
{% data reusables.classroom.assignments-guide-intro-for-environment %}
|
||||
|
||||
- [Choosing a template repository](#choosing-a-template-repository)
|
||||
- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
- [选择模板存储库](#choosing-a-template-repository)
|
||||
- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
|
||||
### Choosing a template repository
|
||||
### 选择模板仓库
|
||||
|
||||
By default, a new assignment will create an empty repository for each team that a student creates. {% data reusables.classroom.you-can-choose-a-template-repository %}
|
||||
默认情况下，新作业将为学生创建的每个团队创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-template-repository %}
|
||||
|
||||
### Choosing an integrated development environment (IDE)
|
||||
### 选择集成开发环境 (IDE)
|
||||
|
||||
{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
|
||||
{% data reusables.classroom.about-online-ides %} 有关详细信息，请参阅“[将 {% data variables.product.prodname_classroom %} 与 IDE 集成](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
|
||||
|
||||
{% data reusables.classroom.classroom-codespaces-link %}
|
||||
|
||||
@@ -103,18 +109,18 @@ By default, a new assignment will create an empty repository for each team that
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
|
||||
|
||||
## Providing feedback
|
||||
## 提供反馈
|
||||
|
||||
Optionally, you can automatically grade assignments and create a space for discussing each submission with the team.
|
||||
（可选）您可以自动对作业进行分级，并创建一个空间，用于与团队讨论每个提交。
|
||||
|
||||
- [Testing assignments automatically](#testing-assignments-automatically)
|
||||
- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
|
||||
- [自动测试作业](#testing-assignments-automatically)
|
||||
- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
|
||||
|
||||
### Testing assignments automatically
|
||||
### 自动测试作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-using-autograding %}
|
||||
|
||||
### Creating a pull request for feedback
|
||||
### 为反馈创建拉取请求
|
||||
|
||||
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
|
||||
|
||||
@@ -122,36 +128,36 @@ Optionally, you can automatically grade assignments and create a space for discu
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
|
||||
|
||||
## Inviting students to an assignment
|
||||
## 邀请学生参加作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
|
||||
|
||||
You can see the teams that are working on or have submitted an assignment in the **Teams** tab for the assignment. {% data reusables.classroom.assignments-to-prevent-submission %}
|
||||
可以在作业的“团队”选项卡中查看正在处理作业或已提交作业的团队。 {% data reusables.classroom.assignments-to-prevent-submission %}
|
||||
|
||||
<div class="procedural-image-wrapper">
|
||||
<img alt="Group assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-group-hero.png">
|
||||
</div>
|
||||
|
||||
## Monitoring students' progress
|
||||
The assignment overview page displays information about your assignment acceptances and team progress. You may have different summary information based on the configurations of your assignments.
|
||||
## 监控学生的进度
|
||||
作业概述页显示有关作业接受和团队进度的信息。 根据作业的配置，您可能有不同的摘要信息。
|
||||
|
||||
- **Total teams**: The number of teams that have been created.
|
||||
- **Rostered students**: The number of students on the Classroom's roster.
|
||||
- **Students not on a team**: The number of students on the Classroom roster who have not yet joined a team.
|
||||
- **Accepted teams**: The number of teams who have accepted this assignment.
|
||||
- **Assignment submissions**: The number of teams that have submitted the assignment. Submission is triggered at the assignment deadline.
|
||||
- **Passing teams**: The number of teams that are currently passing the autograding tests for this assignment.
|
||||
- 团队总数：已创建的团队数。
|
||||
- 名册内学生：课堂名册上的学生人数。
|
||||
- 不在团队的学生：课堂名册上尚未加入团队的学生人数。
|
||||
- 接受的团队：已接受此作业的团队数。
|
||||
- 作业提交：已提交作业的团队数。 在作业截止日期触发提交。
|
||||
- 通过团队：当前通过此作业的自动评分测试的团队数。
|
||||
|
||||
## Next steps
|
||||
## 后续步骤
|
||||
|
||||
- After you create the assignment and your students form teams, team members can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and the team can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," "[Using Git](/github/getting-started-with-github/using-git)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)," and the free course on [resolving merge conflicts](https://github.com/skills/resolve-merge-conflicts) from {% data variables.product.prodname_learning %}.
|
||||
- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 有关详细信息，请参阅“[开始使用 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)”、“[存储库](/repositories)”、“[使用 Git](/github/getting-started-with-github/using-git)”和“[协作处理问题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”，以及 {% data variables.product.prodname_learning %} 关于[解决合并冲突](https://github.com/skills/resolve-merge-conflicts)的免费课程。
|
||||
|
||||
- When a team finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand how the team collaborated. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
|
||||
- 当团队完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解团队如何协作。 有关详细信息，请参阅“[使用图表可视化存储库数据](/github/visualizing-repository-data-with-graphs)”。
|
||||
|
||||
- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
|
||||
- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 有关详细信息，请参阅“[对拉取请求添加注释](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码中打开问题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以提供常见错误反馈的详细信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- [{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
|
||||
- "[Connect a learning management system course to a classroom](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
|
||||
- [Using Existing Teams in Group Assignments?](https://education.github.community/t/using-existing-teams-in-group-assignments/6999) in the {% data variables.product.prodname_education %} Community
|
||||
- [教师版 {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
|
||||
- “[将学习管理系统课程连接到教室](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)”
|
||||
- {% data variables.product.prodname_education %} 社区中的[在小组作业中使用现有团队？](https://education.github.community/t/using-existing-teams-in-group-assignments/6999)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Create an individual assignment
|
||||
intro: You can create an assignment for students in your course to complete individually.
|
||||
title: 创建个人作业
|
||||
intro: 您可以为课程中的学生创建需单独完成的作业。
|
||||
versions:
|
||||
fpt: '*'
|
||||
permissions: 'Organization owners who are admins for a classroom can create and manage individual assignments for a classroom. {% data reusables.classroom.classroom-admins-link %}'
|
||||
@@ -8,8 +8,14 @@ redirect_from:
|
||||
- /education/manage-coursework-with-github-classroom/creating-an-individual-assignment
|
||||
- /education/manage-coursework-with-github-classroom/create-an-individual-assignment
|
||||
shortTitle: Individual assignment
|
||||
ms.openlocfilehash: 1ffa725be4e42695b297545f65c998b14ed8e000
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179743'
|
||||
---
|
||||
## About individual assignments
|
||||
## 关于个人作业
|
||||
|
||||
{% data reusables.classroom.assignments-individual-definition %}
|
||||
|
||||
@@ -17,42 +23,42 @@ shortTitle: Individual assignment
|
||||
|
||||
{% data reusables.classroom.about-assignments %}
|
||||
|
||||
For a video demonstration of the creation of an individual assignment, see "[Basics of setting up {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)."
|
||||
有关创建个人作业的视频演示，请参阅“[设置 {% data variables.product.prodname_classroom %} 的基本信息](/education/manage-coursework-with-github-classroom/basics-of-setting-up-github-classroom)”。
|
||||
|
||||
{% data reusables.classroom.reuse-assignment-link %}
|
||||
|
||||
## Prerequisites
|
||||
## 先决条件
|
||||
|
||||
{% data reusables.classroom.assignments-classroom-prerequisite %}
|
||||
|
||||
## Creating an assignment
|
||||
## 创建作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-create-the-assignment %}
|
||||
|
||||
## Setting up the basics for an assignment
|
||||
## 设置作业的基本信息
|
||||
|
||||
Name your assignment, decide whether to assign a deadline, and choose the visibility of assignment repositories.
|
||||
指定作业的名称，决定是否分配截止时间，并选择作业仓库的可见性。
|
||||
|
||||
- [Naming an assignment](#naming-an-assignment)
|
||||
- [Assigning a deadline for an assignment](#assigning-a-deadline-for-an-assignment)
|
||||
- [Choosing an assignment type](#choosing-an-assignment-type)
|
||||
- [Choosing a visibility for assignment repositories](#choosing-a-visibility-for-assignment-repositories)
|
||||
- [指定作业名称](#naming-an-assignment)
|
||||
- [分配作业的截止时间](#assigning-a-deadline-for-an-assignment)
|
||||
- [选择作业类型](#choosing-an-assignment-type)
|
||||
- [选择作业存储库的可见性](#choosing-a-visibility-for-assignment-repositories)
|
||||
|
||||
### Naming an assignment
|
||||
### 指定作业名称
|
||||
|
||||
For an individual assignment, {% data variables.product.prodname_classroom %} names repositories by the repository prefix and the student's {% data variables.product.product_name %} username. By default, the repository prefix is the assignment title. For example, if you name an assignment "assignment-1" and the student's username on {% data variables.product.product_name %} is @octocat, the name of the assignment repository for @octocat will be `assignment-1-octocat`.
|
||||
对于个人作业，{% data variables.product.prodname_classroom %} 使用仓库前缀和学生的 {% data variables.product.product_name %} 用户名对仓库命名。 默认情况下，仓库前缀是作业标题。 例如，如果你对作业 "assignment-1" 命名，学生在 {% data variables.product.product_name %} 上的用户名是 @octocat，则 @octocat 的作业存储库的名称将是 `assignment-1-octocat`。
|
||||
|
||||
{% data reusables.classroom.assignments-type-a-title %}
|
||||
|
||||
### Assigning a deadline for an assignment
|
||||
### 分配作业的截止时间
|
||||
|
||||
{% data reusables.classroom.assignments-guide-assign-a-deadline %}
|
||||
|
||||
### Choosing an assignment type
|
||||
### 选择作业类型
|
||||
|
||||
Under "Individual or group assignment", select the drop-down menu, and click **Individual assignment**. You can't change the assignment type after you create the assignment. If you'd rather create a group assignment, see "[Create a group assignment](/education/manage-coursework-with-github-classroom/create-a-group-assignment)."
|
||||
在“个人或小组作业”下，选择下拉菜单，并单击“个人作业”。 创建作业后不可更改作业类型。 如果想要创建小组作业，请参阅“[创建小组作业](/education/manage-coursework-with-github-classroom/create-a-group-assignment)”。
|
||||
|
||||
### Choosing a visibility for assignment repositories
|
||||
### 选择作业仓库的可见性
|
||||
|
||||
{% data reusables.classroom.assignments-repository-visibility-and-permissions %}
|
||||
|
||||
@@ -60,41 +66,41 @@ Under "Individual or group assignment", select the drop-down menu, and click **I
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-basics %}
|
||||
|
||||
## Adding starter code and configuring a development environment
|
||||
## 添加起始代码并配置开发环境
|
||||
|
||||
{% data reusables.classroom.assignments-guide-intro-for-environment %}
|
||||
|
||||
- [Choosing a template repository](#choosing-a-template-repository)
|
||||
- [Choosing an integrated development environment (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
- [选择模板存储库](#choosing-a-template-repository)
|
||||
- [选择集成开发环境 (IDE)](#choosing-an-integrated-development-environment-ide)
|
||||
|
||||
### Choosing a template repository
|
||||
### 选择模板仓库
|
||||
|
||||
By default, a new assignment will create an empty repository for each student on the roster for the classroom. {% data reusables.classroom.you-can-choose-a-template-repository %}
|
||||
默认情况下，新作业将为教室名册上的每个学生创建一个空仓库。 {% data reusables.classroom.you-can-choose-a-template-repository %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-template-repository %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-continue-after-starter-code-and-feedback %}
|
||||
|
||||
### Choosing an integrated development environment (IDE)
|
||||
### 选择集成开发环境 (IDE)
|
||||
|
||||
{% data reusables.classroom.about-online-ides %} For more information, see "[Integrate {% data variables.product.prodname_classroom %} with an IDE](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)."
|
||||
{% data reusables.classroom.about-online-ides %} 有关详细信息，请参阅“[将 {% data variables.product.prodname_classroom %} 与 IDE 集成](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide)”。
|
||||
|
||||
{% data reusables.classroom.classroom-codespaces-link %}
|
||||
|
||||
{% data reusables.classroom.assignments-guide-choose-an-online-ide %}
|
||||
|
||||
## Providing feedback for an assignment
|
||||
## 为作业提供反馈
|
||||
|
||||
Optionally, you can automatically grade assignments and create a space for discussing each submission with the student.
|
||||
（可选）您可以自动对作业进行分级，并创建一个空间，用于与学生讨论每个提交。
|
||||
|
||||
- [Testing assignments automatically](#testing-assignments-automatically)
|
||||
- [Creating a pull request for feedback](#creating-a-pull-request-for-feedback)
|
||||
- [自动测试作业](#testing-assignments-automatically)
|
||||
- [为反馈创建拉取请求](#creating-a-pull-request-for-feedback)
|
||||
|
||||
### Testing assignments automatically
|
||||
### 自动测试作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-using-autograding %}
|
||||
|
||||
### Creating a pull request for feedback
|
||||
### 为反馈创建拉取请求
|
||||
|
||||
{% data reusables.classroom.you-can-create-a-pull-request-for-feedback %}
|
||||
|
||||
@@ -102,34 +108,34 @@ Optionally, you can automatically grade assignments and create a space for discu
|
||||
|
||||
{% data reusables.classroom.assignments-guide-click-create-assignment-button %}
|
||||
|
||||
## Inviting students to an assignment
|
||||
## 邀请学生参加作业
|
||||
|
||||
{% data reusables.classroom.assignments-guide-invite-students-to-assignment %}
|
||||
|
||||
You can see whether a student has joined the classroom and accepted or submitted an assignment in the **Classroom roster** tab for the assignment. You can also link students' {% data variables.product.prodname_dotcom %} aliases to their associated roster identifier and vice versa in this tab. {% data reusables.classroom.assignments-to-prevent-submission %}
|
||||
你可以在作业的“课堂名册”选项卡中查看学生是否已进入教室以及是否接受或提交作业。 你还可以在此选项卡中将学生的 {% data variables.product.prodname_dotcom %} 别名链接到其关联的名册标识符，反之亦然。{% data reusables.classroom.assignments-to-prevent-submission %}
|
||||
|
||||
<div class="procedural-image-wrapper">
|
||||
<img alt="Individual assignment" class="procedural-image-wrapper" src="/assets/images/help/classroom/assignment-individual-hero.png">
|
||||
</div>
|
||||
|
||||
## Monitoring students' progress
|
||||
The assignment overview page provides an overview of your assignment acceptances and student progress. You may have different summary information based on the configurations of your assignments.
|
||||
## 监控学生的进度
|
||||
作业概述页面提供了作业接受情况和学生进度的概述。 根据作业的配置，您可能有不同的摘要信息。
|
||||
|
||||
- **Rostered students**: The number of students on the Classroom's roster.
|
||||
- **Added students**: The number of {% data variables.product.prodname_dotcom %} accounts that have accepted the assignment and are not associated with a roster identifier.
|
||||
- **Accepted students**: The number of accounts have accepted this assignment.
|
||||
- **Assignment submissions**: The number of students that have submitted the assignment. Submission is triggered at the assignment deadline.
|
||||
- **Passing students**: The number of students currently passing the autograding tests for this assignment.
|
||||
- **名册内学生**：课堂名册上的学生人数。
|
||||
- **已添加的学生**：已接受作业且未与名册标识符关联的 {% data variables.product.prodname_dotcom %} 帐户数。
|
||||
- **已接受的学生**：已接受此作业的帐户数。
|
||||
- **作业提交**：已提交作业的学生人数。 在作业截止日期触发提交。
|
||||
- **及格学生**：当前通过此作业的自动评分测试的学生人数。
|
||||
|
||||
## Next steps
|
||||
## 后续步骤
|
||||
|
||||
- Once you create the assignment, students can start work on the assignment using Git and {% data variables.product.product_name %}'s features. Students can clone the repository, push commits, manage branches, create and review pull requests, address merge conflicts, and discuss changes with issues. Both you and student can review the commit history for the repository. For more information, see "[Getting started with {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)," "[Repositories](/repositories)," and "[Collaborating with issues and pull requests](/github/collaborating-with-issues-and-pull-requests)."
|
||||
- 在创建作业后，学生可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和学生都可以审查仓库的提交历史记录。 有关详细信息，请参阅“[开始使用 {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github)”、“[存储库](/repositories)”和“[协作处理问题和拉取请求](/github/collaborating-with-issues-and-pull-requests)”。
|
||||
|
||||
- When a student finishes an assignment, you can review the files in the repository, or you can review the history and visualizations for the repository to better understand the student's work. For more information, see "[Visualizing repository data with graphs](/github/visualizing-repository-data-with-graphs)."
|
||||
- 当学生完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解学生的工作。 有关详细信息，请参阅“[使用图表可视化存储库数据](/github/visualizing-repository-data-with-graphs)”。
|
||||
|
||||
- You can provide feedback for an assignment by commenting on individual commits or lines in a pull request. For more information, see "[Commenting on a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)" and "[Opening an issue from code](/github/managing-your-work-on-github/opening-an-issue-from-code)." For more information about creating saved replies to provide feedback for common errors, see "[About saved replies](/github/writing-on-github/about-saved-replies)."
|
||||
- 您可以通过在拉取请求中评论个别提交或行来提供作业反馈。 有关详细信息，请参阅“[对拉取请求添加注释](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/commenting-on-a-pull-request)”和“[从代码中打开问题](/github/managing-your-work-on-github/opening-an-issue-from-code)”。 有关创建已保存回复以提供常见错误反馈的详细信息，请参阅“[关于已保存回复](/github/writing-on-github/about-saved-replies)”。
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[{% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)"
|
||||
- "[Connect a learning management system to {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)"
|
||||
- [教师版 {% data variables.product.prodname_global_campus %}](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers)
|
||||
- [将学习管理系统连接到 {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom)
|
||||
|
||||
@@ -1,83 +1,88 @@
|
||||
---
|
||||
title: Getting started with GitHub AE
|
||||
intro: 'Get started with setting up and configuring {% data variables.product.product_name %} for {% data variables.location.product_location %}.'
|
||||
title: 开始使用 GitHub AE
|
||||
intro: '开始为 {% data variables.location.product_location %} 设置和配置 {% data variables.product.product_name %}。'
|
||||
versions:
|
||||
ghae: '*'
|
||||
ms.openlocfilehash: 957a922a2493abd8f625cdb9e9d6650283820222
|
||||
ms.sourcegitcommit: c562c85cc75ffe1eb4e9595d8adc09ec71697ab1
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/22/2022
|
||||
ms.locfileid: '148180059'
|
||||
---
|
||||
本指南将引导你作为企业所有者完成在 {% data variables.product.product_name %} 上设置、配置 {% data variables.location.product_location %} 并管理设置。 若要了解 {% data variables.product.product_name %} 相关详细信息，请参阅“[关于 {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)。”
|
||||
|
||||
This guide will walk you through setting up, configuring, and managing settings for {% data variables.location.product_location %} on {% data variables.product.product_name %} as an enterprise owner. For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_managed %}](/admin/overview/about-github-ae)."
|
||||
## 第 1 部分：设置 {% data variables.product.product_name %}
|
||||
若要开始使用 {% data variables.product.product_name %}，可以创建企业帐户、初始化 {% data variables.product.product_name %}、配置 IP 允许列表、配置用户身份验证和预配以及管理 {% data variables.location.product_location %} 的计费。
|
||||
|
||||
## Part 1: Setting up {% data variables.product.product_name %}
|
||||
To get started with {% data variables.product.product_name %}, you can create your enterprise account, initialize {% data variables.product.product_name %}, configure an IP allow list, configure user authentication and provisioning, and manage billing for {% data variables.location.product_location %}.
|
||||
|
||||
### 1. Creating your {% data variables.product.product_name %} enterprise account
|
||||
You will first need to purchase {% data variables.product.product_name %}. For more information, contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact).
|
||||
### 1. 创建你的 {% data variables.product.product_name %} 企业帐户
|
||||
您首先需要购买 {% data variables.product.product_name %}。 有关详细信息，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。
|
||||
|
||||
{% data reusables.github-ae.initialize-enterprise %}
|
||||
|
||||
### 2. Initializing {% data variables.product.product_name %}
|
||||
After {% data variables.product.company_short %} creates the owner account for {% data variables.location.product_location %} on {% data variables.product.product_name %}, you will receive an email to sign in and complete the initialization. During initialization, you, as the enterprise owner, will name {% data variables.location.product_location %}, configure SAML SSO, create policies for all organizations in {% data variables.location.product_location %}, and configure a support contact for your enterprise members. For more information, see "[Initializing {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)."
|
||||
### 2. 初始化 {% data variables.product.product_name %}
|
||||
当 {% data variables.product.company_short %} 在 {% data variables.product.product_name %} 上为 {% data variables.location.product_location %} 创建所有者帐户后，你将收到一封电子邮件，要求你登录并完成初始化。 在初始化期间，作为企业所有者，你将命名 {% data variables.location.product_location %}、配置 SAML SSO、为 {% data variables.location.product_location %} 中的所有组织创建策略，并为企业成员配置支持联系人。 有关详细信息，请参阅“[初始化 {% data variables.product.prodname_ghe_managed %}](/admin/configuration/configuring-your-enterprise/initializing-github-ae)”。
|
||||
|
||||
### 3. Restricting network traffic
|
||||
You can configure an allow list for specific IP addresses to restrict access to assets owned by organizations in your enterprise account. For more information, see "[Restricting network traffic to your enterprise with an IP allow list](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)."
|
||||
### 3. 限制网络流量
|
||||
您可以为特定 IP 地址配置允许列表，以限制对企业帐户中组织拥有的资产的访问。 有关详细信息，请参阅“[使用 IP 允许列表限制到企业的网络流量](/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list)”。
|
||||
|
||||
### 4. Managing identity and access for {% data variables.location.product_location %}
|
||||
You can centrally manage access to {% data variables.location.product_location %} on {% data variables.product.product_name %} from an identity provider (IdP) using SAML single sign-on (SSO) for user authentication and System for Cross-domain Identity Management (SCIM) for user provisioning. Once you configure provisioning, you can assign or unassign users to the application from the IdP, creating or disabling user accounts in the enterprise. For more information, see "[About identity and access management for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)."
|
||||
### 4. 管理 {% data variables.location.product_location %} 的标识和访问
|
||||
你可以使用 SAML 单一登录 (SSO) 进行用户身份验证和跨域身份管理系统 (SCIM) 进行用户预配，从标识提供者 (IdP) 集中管理对 {% data variables.product.product_name %} 上 {% data variables.location.product_location %} 的访问。 在配置预配后，您可以从 IdP 分配用户给应用程序或取消分配，从而在企业中创建或禁用用户帐户。 有关详细信息，请参阅“[关于企业标识和访问管理](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-identity-and-access-management-for-your-enterprise)”。
|
||||
|
||||
### 5. Managing billing for {% data variables.location.product_location %}
|
||||
Owners of the subscription for {% data variables.location.product_location %} on {% data variables.product.product_name %} can view billing details for {% data variables.product.product_name %} in the Azure portal. For more information, see "[Managing billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
### 5. 管理 {% data variables.location.product_location %} 的计费
|
||||
{% data variables.product.product_name %} 上 {% data variables.location.product_location %} 的订阅所有者可以在 Azure 门户中查看 {% data variables.product.product_name %} 的计费详细信息。 有关详细信息，请参阅“[管理企业的计费](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)”。
|
||||
|
||||
## Part 2: Organizing and managing enterprise members
|
||||
As an enterprise owner for {% data variables.product.product_name %}, you can manage settings on user, repository, team, and organization levels. You can manage members of {% data variables.location.product_location %}, create and manage organizations, set policies for repository management, and create and manage teams.
|
||||
## 第 2 部分：组织和管理企业成员
|
||||
作为 {% data variables.product.product_name %} 的企业所有者，您可以管理用户、存储库、团队和组织级别的设置。 你可以管理 {% data variables.location.product_location %} 的成员、创建和管理组织、设置存储库管理策略，以及创建和管理团队。
|
||||
|
||||
### 1. Managing members of {% data variables.location.product_location %}
|
||||
### 1. 管理 {% data variables.location.product_location %} 的成员
|
||||
{% data reusables.getting-started.managing-enterprise-members %}
|
||||
|
||||
### 2. Creating organizations
|
||||
### 2. 创建组织
|
||||
{% data reusables.getting-started.creating-organizations %}
|
||||
|
||||
### 3. Adding members to organizations
|
||||
### 3. 向组织添加成员
|
||||
{% data reusables.getting-started.adding-members-to-organizations %}
|
||||
|
||||
### 4. Creating teams
|
||||
### 4. 创建团队
|
||||
{% data reusables.getting-started.creating-teams %}
|
||||
|
||||
### 5. Setting organization and repository permission levels
|
||||
### 5. 设置组织和存储库权限级别
|
||||
{% data reusables.getting-started.setting-org-and-repo-permissions %}
|
||||
|
||||
### 6. Enforcing repository management policies
|
||||
### 6. 实施存储库管理策略
|
||||
{% data reusables.getting-started.enforcing-repo-management-policies %}
|
||||
|
||||
## Part 3: Building securely
|
||||
To increase the security of {% data variables.location.product_location %}, you can monitor {% data variables.location.product_location %} and configure security and analysis features for your organizations.
|
||||
## 第 3 部分：安全构建
|
||||
若要提高 {% data variables.location.product_location %} 的安全性，你可以监视 {% data variables.location.product_location %}，并为组织配置安全性和分析功能。
|
||||
|
||||
### 1. Monitoring {% data variables.location.product_location %}
|
||||
You can monitor {% data variables.location.product_location %} with your activity dashboard and audit logging. For more information, see "[Monitoring activity in your enterprise](/admin/monitoring-activity-in-your-enterprise)."
|
||||
### 1. 监视 {% data variables.location.product_location %}
|
||||
你可以使用活动仪表板和审核日志记录来监视 {% data variables.location.product_location %}。 有关详细信息，请参阅“[监视企业中的活动](/admin/monitoring-activity-in-your-enterprise)”。
|
||||
|
||||
### 2. Configuring security features for your organizations
|
||||
### 2. 为组织配置安全功能
|
||||
{% data reusables.getting-started.configuring-security-features %}
|
||||
|
||||
## Part 4: Customizing and automating work on {% data variables.location.product_location %}
|
||||
You can customize and automate work in organizations in {% data variables.location.product_location %} with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, and {% data variables.product.prodname_pages %}.
|
||||
## 第 4 部分：自定义和自动化 {% data variables.location.product_location %} 上的工作
|
||||
你可以使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %} 和 {% data variables.product.prodname_pages %} 在 {% data variables.location.product_location %} 中自定义和自动化组织中的工作。
|
||||
|
||||
### 1. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
|
||||
### 1. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
|
||||
{% data reusables.getting-started.api %}
|
||||
|
||||
### 2. Building {% data variables.product.prodname_actions %}
|
||||
### 2. 生成 {% data variables.product.prodname_actions %}
|
||||
{% data reusables.getting-started.actions %}
|
||||
|
||||
For more information on enabling and configuring {% data variables.product.prodname_actions %} for {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)."
|
||||
有关为 {% data variables.product.product_name %} 启用和配置 {% data variables.product.prodname_actions %} 的详细信息，请参阅“[{% data variables.product.prodname_ghe_managed %} 的 {% data variables.product.prodname_actions %} 入门](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-ae)”。
|
||||
|
||||
### 3. Using {% data variables.product.prodname_pages %}
|
||||
### 3. 使用 {% data variables.product.prodname_pages %}
|
||||
{% data reusables.getting-started.github-pages-enterprise %}
|
||||
## Part 5: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
|
||||
Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need with {% data variables.product.prodname_dotcom %} Enterprise Support.
|
||||
## 第 5 部分：使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源
|
||||
您的企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息，您也可以通过 {% data variables.product.prodname_dotcom %} Enterprise 支持获得所需的支持。
|
||||
|
||||
### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_managed %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %}
|
||||
您可以阅读反映 {% data variables.product.prodname_ghe_managed %} 可用功能的文档。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)”。
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
### 2. 通过 {% data variables.product.prodname_learning %} 学习
|
||||
{% data reusables.getting-started.learning-enterprise %}
|
||||
|
||||
### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
|
||||
### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持
|
||||
{% data reusables.getting-started.contact-support-enterprise %}
|
||||
|
||||
@@ -1,128 +1,132 @@
|
||||
---
|
||||
title: Getting started with GitHub Enterprise Server
|
||||
intro: 'Get started with setting up and managing {% data variables.location.product_location %}.'
|
||||
title: 开始使用 GitHub Enterprise Server
|
||||
intro: '开始设置和管理 {% data variables.location.product_location %}。'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ms.openlocfilehash: 68cd462c42ef63863750d9edc5e122dc3c325115
|
||||
ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/14/2022
|
||||
ms.locfileid: '148163414'
|
||||
---
|
||||
本指南将引导你以企业管理员身份设置、配置和管理 {% data variables.location.product_location %}。
|
||||
|
||||
This guide will walk you through setting up, configuring and managing {% data variables.location.product_location %} as an enterprise administrator.
|
||||
{% data variables.product.company_short %} 提供了两种部署 {% data variables.product.prodname_enterprise %} 的方法。
|
||||
|
||||
{% data variables.product.company_short %} provides two ways to deploy {% data variables.product.prodname_enterprise %}.
|
||||
- {% data variables.product.prodname_ghe_cloud %}
|
||||
- {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
- **{% data variables.product.prodname_ghe_cloud %}**
|
||||
- **{% data variables.product.prodname_ghe_server %}**
|
||||
{% data variables.product.company_short %} 托管 {% data variables.product.prodname_ghe_cloud %}。 可以在自己的数据中心或受支持的云提供商中部署和托管 {% data variables.product.prodname_ghe_server %} 。
|
||||
|
||||
{% data variables.product.company_short %} hosts {% data variables.product.prodname_ghe_cloud %}. You can deploy and host {% data variables.product.prodname_ghe_server %} in your own datacenter or a supported cloud provider.
|
||||
有关 {% data variables.product.product_name %} 的详细信息，请参阅“[关于 {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)”。
|
||||
|
||||
For more information about {% data variables.product.product_name %}, see "[About {% data variables.product.prodname_ghe_server %}](/admin/overview/about-github-enterprise-server)."
|
||||
## 第 1 部分：安装 {% data variables.product.product_name %}
|
||||
要开始使用 {% data variables.product.product_name %}，您需要创建企业帐户、安装实例、使用管理控制台进行初始设置、配置实例和管理帐单。
|
||||
### 1. 创建企业帐户
|
||||
在安装 {% data variables.product.product_name %} 之前，可以通过联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)在 {% data variables.product.prodname_dotcom_the_website %} 上创建一个企业帐户。 {% data variables.product.prodname_dotcom_the_website %} 上的企业帐户可用于计费以及通过 {% data variables.product.prodname_github_connect %} 与 {% data variables.product.prodname_dotcom_the_website %} 共享功能。 有关详细信息，请参阅[关于企业帐户](/admin/overview/about-enterprise-accounts)。
|
||||
### 2. 安装 {% data variables.product.product_name %}
|
||||
要开始使用 {% data variables.product.product_name %}，您需要在所选的虚拟化平台上安装设备。 有关详细信息，请参阅“[设置 {% data variables.product.prodname_ghe_server %} 实例](/admin/installation/setting-up-a-github-enterprise-server-instance)”。
|
||||
|
||||
## Part 1: Installing {% data variables.product.product_name %}
|
||||
To get started with {% data variables.product.product_name %}, you will need to create your enterprise account, install the instance, use the Management Console for initial setup, configure your instance, and manage billing.
|
||||
### 1. Creating your enterprise account
|
||||
Before you install {% data variables.product.product_name %}, you can create an enterprise account on {% data variables.product.prodname_dotcom_the_website %} by contacting [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). An enterprise account on {% data variables.product.prodname_dotcom_the_website %} is useful for billing and for shared features with {% data variables.product.prodname_dotcom_the_website %} via {% data variables.product.prodname_github_connect %}. For more information, see "[About enterprise accounts](/admin/overview/about-enterprise-accounts)."
|
||||
### 2. Installing {% data variables.product.product_name %}
|
||||
To get started with {% data variables.product.product_name %}, you will need to install the appliance on a virtualization platform of your choice. For more information, see "[Setting up a {% data variables.product.prodname_ghe_server %} instance](/admin/installation/setting-up-a-github-enterprise-server-instance)."
|
||||
### 3. 使用管理控制台
|
||||
你将使用管理控制台在首次启动 {% data variables.location.product_location %} 时完成初始设置过程。 您还可以使用管理控制台管理实例设置，例如许可证、域、身份验证和 TLS。 有关详细信息，请参阅“[访问管理控制台](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)”。
|
||||
|
||||
### 3. Using the Management Console
|
||||
You will use the Management Console to walk through the initial setup process when first launching {% data variables.location.product_location %}. You can also use the Management Console to manage instance settings such as the license, domain, authentication, and TLS. For more information, see "[Accessing the management console](/admin/configuration/configuring-your-enterprise/accessing-the-management-console)."
|
||||
### 4. 配置 {% data variables.location.product_location %}
|
||||
除了管理控制台之外，还可以使用站点管理仪表板和管理 shell (SSH) 来管理 {% data variables.location.product_location %}。 例如，您可以配置应用程序和速率限制、查看报告、使用命令行实用程序。 有关详细信息，请参阅“[配置你的企业](/admin/configuration/configuring-your-enterprise)”。
|
||||
|
||||
### 4. Configuring {% data variables.location.product_location %}
|
||||
In addition to the Management Console, you can use the site admin dashboard and the administrative shell (SSH) to manage {% data variables.location.product_location %}. For example, you can configure applications and rate limits, view reports, use command-line utilities. For more information, see "[Configuring your enterprise](/admin/configuration/configuring-your-enterprise)."
|
||||
您可以使用 {% data variables.product.product_name %} 通过动态主机配置协议 (DHCP) 使用的默认网络设置，也可以使用虚拟机控制台配置网络设置。 您还可以配置代理服务器或防火墙规则。 有关详细信息，请参阅“[配置网络设置](/admin/configuration/configuring-network-settings)”。
|
||||
|
||||
You can use the default network settings used by {% data variables.product.product_name %} via the dynamic host configuration protocol (DHCP), or you can also configure the network settings using the virtual machine console. You can also configure a proxy server or firewall rules. For more information, see "[Configuring network settings](/admin/configuration/configuring-network-settings)."
|
||||
### 5. 配置高可用性
|
||||
可以配置 {% data variables.location.product_location %} 来实现高可用性，以最大程度地减少硬件故障和网络中断的影响。 有关详细信息，请参阅“[配置高可用性](/admin/enterprise-management/configuring-high-availability)”。
|
||||
|
||||
### 5. Configuring high availability
|
||||
You can configure {% data variables.location.product_location %} for high availability to minimize the impact of hardware failures and network outages. For more information, see "[Configuring high availability](/admin/enterprise-management/configuring-high-availability)."
|
||||
### 6. 设置暂存实例
|
||||
可以设置暂存实例来测试修改、规划灾难恢复，并在将更新应用于 {% data variables.location.product_location %} 之前试用更新。 有关详细信息，请参阅“[设置暂存实例](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)”。
|
||||
|
||||
### 6. Setting up a staging instance
|
||||
You can set up a staging instance to test modifications, plan for disaster recovery, and try out updates before applying them to {% data variables.location.product_location %}. For more information, see "[Setting up a staging instance](/admin/installation/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance)."
|
||||
### 7. 指定备份和灾难恢复
|
||||
要保护生产数据，可以使用 {% data variables.product.prodname_enterprise_backup_utilities %} 配置 {% data variables.location.product_location %} 的自动备份。 有关详细信息，请参阅“[在设备上配置备份](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)”。
|
||||
|
||||
### 7. Designating backups and disaster recovery
|
||||
To protect your production data, you can configure automated backups of {% data variables.location.product_location %} with {% data variables.product.prodname_enterprise_backup_utilities %}. For more information, see "[Configuring backups on your appliance](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)."
|
||||
### 8. 管理企业的账单
|
||||
对于连接到您的企业帐户的所有组织和 {% data variables.product.product_name %} 实例，帐单将汇总到所有付费 {% data variables.product.prodname_dotcom %}.com 服务的单个帐单费用中。 企业所有者和帐单管理员均可访问和管理企业帐户的帐单设置。 有关详细信息，请参阅“[管理企业的计费](/admin/overview/managing-billing-for-your-enterprise)”。
|
||||
|
||||
### 8. Managing billing for your enterprise
|
||||
Billing for all the organizations and {% data variables.product.product_name %} instances connected to your enterprise account is aggregated into a single bill charge for all of your paid {% data variables.product.prodname_dotcom %}.com services. Enterprise owners and billing managers can access and manage billing settings for enterprise accounts. For more information, see "[Managing billing for your enterprise](/admin/overview/managing-billing-for-your-enterprise)."
|
||||
## 第 2 部分：组织和管理团队
|
||||
作为企业所有者或管理员，您可以管理用户、存储库、团队和组织级别的设置。 您可以管理企业成员、创建和管理组织、设置存储库管理策略以及创建和管理团队。
|
||||
|
||||
## Part 2: Organizing and managing your team
|
||||
As an enterprise owner or administrator, you can manage settings on user, repository, team and organization levels. You can manage members of your enterprise, create and manage organizations, set policies for repository management, and create and manage teams.
|
||||
|
||||
### 1. Managing members of {% data variables.location.product_location %}
|
||||
### 1. 管理 {% data variables.location.product_location %} 的成员
|
||||
{% data reusables.getting-started.managing-enterprise-members %}
|
||||
|
||||
### 2. Creating organizations
|
||||
### 2. 创建组织
|
||||
{% data reusables.getting-started.creating-organizations %}
|
||||
|
||||
### 3. Adding members to organizations
|
||||
### 3. 向组织添加成员
|
||||
{% data reusables.getting-started.adding-members-to-organizations %}
|
||||
|
||||
### 4. Creating teams
|
||||
### 4. 创建团队
|
||||
{% data reusables.getting-started.creating-teams %}
|
||||
|
||||
### 5. Setting organization and repository permission levels
|
||||
### 5. 设置组织和存储库权限级别
|
||||
{% data reusables.getting-started.setting-org-and-repo-permissions %}
|
||||
|
||||
### 6. Enforcing repository management policies
|
||||
### 6. 实施存储库管理策略
|
||||
{% data reusables.getting-started.enforcing-repo-management-policies %}
|
||||
|
||||
## Part 3: Building securely
|
||||
To increase the security of {% data variables.location.product_location %}, you can configure authentication for enterprise members, use tools and audit logging to stay in compliance, configure security and analysis features for your organizations, and optionally enable {% data variables.product.prodname_GH_advanced_security %}.
|
||||
### 1. Authenticating enterprise members
|
||||
You can use {% data variables.product.product_name %}'s built-in authentication method, or you can choose between an external authentication provider, such as CAS, LDAP, or SAML, to integrate your existing accounts and centrally manage user access to {% data variables.location.product_location %}. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)."
|
||||
## 第 3 部分：安全构建
|
||||
要提高 {% data variables.location.product_location %} 的安全性，可以为企业成员配置身份验证，使用工具和审核日志记录以保持合规性，为组织配置安全性和分析功能，以及选择性地启用 {% data variables.product.prodname_GH_advanced_security %}。
|
||||
### 1. 对企业成员进行身份验证
|
||||
可以使用 {% data variables.product.product_name %} 的内置身份验证方法，也可以在外部身份验证提供程序（如 CAS、LDAP 或 SAML）之间进行选择，以集成现有帐户并集中管理用户对 {% data variables.location.product_location %} 的访问。 有关详细信息，请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)”。
|
||||
|
||||
You can also require two-factor authentication for each of your organizations. For more information, see "[Requiring two factor authentication for an organization](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)."
|
||||
您还可以要求对每个组织进行双重身份验证。 有关详细信息，请参阅“[要求对组织进行双因素身份验证](/admin/user-management/managing-organizations-in-your-enterprise/requiring-two-factor-authentication-for-an-organization)”。
|
||||
|
||||
### 2. Staying in compliance
|
||||
You can implement required status checks and commit verifications to enforce your organization's compliance standards and automate compliance workflows. You can also use the audit log for your organization to review actions performed by your team. For more information, see "[Enforcing policy with pre-receive hooks](/admin/policies/enforcing-policy-with-pre-receive-hooks)" and "[About the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)."
|
||||
### 2. 保持合规性
|
||||
您可以实施所需的状态检查和提交验证，以强制实施组织的合规性标准并自动执行合规性工作流。 您还可以使用组织的审核日志来查看团队执行的操作。 有关详细信息，请参阅“[使用预接收挂钩强制实施策略](/admin/policies/enforcing-policy-with-pre-receive-hooks)”和“[关于企业审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/about-the-audit-log-for-your-enterprise)”。
|
||||
|
||||
{% ifversion ghes %}
|
||||
### 3. Configuring security features for your organizations
|
||||
{% data reusables.getting-started.configuring-security-features %}
|
||||
{% endif %}
|
||||
### 3. 为组织配置安全功能
|
||||
{% data reusables.getting-started.configuring-security-features %} {% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
### 4. Enabling {% data variables.product.prodname_GH_advanced_security %} features
|
||||
You can upgrade your {% data variables.product.product_name %} license to include {% data variables.product.prodname_GH_advanced_security %}. This provides extra features that help users find and fix security problems in their code, such as code and secret scanning. For more information, see "[{% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
|
||||
### 4. 启用 {% data variables.product.prodname_GH_advanced_security %} 功能
|
||||
您可以升级 {% data variables.product.product_name %} 许可证以包含 {% data variables.product.prodname_GH_advanced_security %}。 这将提供额外的功能，帮助用户发现和修复其代码中的安全问题，例如代码和机密扫描。 有关详细信息，请参阅“[企业的 {% data variables.product.prodname_GH_advanced_security %}](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)”。
|
||||
{% endif %}
|
||||
|
||||
## Part 4: Customizing and automating your enterprise's work on {% data variables.product.prodname_dotcom %}
|
||||
You can customize and automate work in organizations in your enterprise with {% data variables.product.prodname_dotcom %} and {% data variables.product.prodname_oauth_apps %}, {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_registry %} , and {% data variables.product.prodname_pages %}.
|
||||
## 第 4 部分：自定义和自动化企业在 {% data variables.product.prodname_dotcom %} 上的工作
|
||||
您可以使用 {% data variables.product.prodname_dotcom %} 和 {% data variables.product.prodname_oauth_apps %}、{% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API、{% data variables.product.prodname_actions %}、{% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_pages %} 自定义和自动化企业中组织中的工作。
|
||||
|
||||
### 1. Building {% data variables.product.prodname_github_apps %} and {% data variables.product.prodname_oauth_apps %}
|
||||
You can build integrations with the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API, such as {% data variables.product.prodname_github_apps %} or {% data variables.product.prodname_oauth_apps %}, for use in organizations in your enterprise to complement and extend your workflows. For more information, see "[About apps](/developers/apps/getting-started-with-apps/about-apps)."
|
||||
### 2. Using the {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
|
||||
### 1. 构建 {% data variables.product.prodname_github_apps %} 和 {% data variables.product.prodname_oauth_apps %}
|
||||
您可以构建与 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API 的集成，如 {% data variables.product.prodname_github_apps %} 或 {% data variables.product.prodname_oauth_apps %}，以便在企业中的组织中使用，以补充和扩展您的工作流程。 有关详细信息，请参阅“[关于应用](/developers/apps/getting-started-with-apps/about-apps)”。
|
||||
### 2. 使用 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.product.product_name %}{% endif %} API
|
||||
{% data reusables.getting-started.api %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
### 3. Building {% data variables.product.prodname_actions %}
|
||||
### 3. 生成 {% data variables.product.prodname_actions %}
|
||||
{% data reusables.getting-started.actions %}
|
||||
|
||||
For more information on enabling and configuring {% data variables.product.prodname_actions %} on {% data variables.product.product_name %}, see "[Getting started with {% data variables.product.prodname_actions %} for {% data variables.product.prodname_ghe_server %}](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
有关在 {% data variables.product.product_name %} 上启用和配置 {% data variables.product.prodname_actions %} 的详细信息，请参阅“[{% data variables.product.prodname_ghe_server %} 的 {% data variables.product.prodname_actions %} 使用入门](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)”。
|
||||
|
||||
### 4. Publishing and managing {% data variables.product.prodname_registry %}
|
||||
### 4. 发布和管理 {% data variables.product.prodname_registry %}
|
||||
{% data reusables.getting-started.packages %}
|
||||
|
||||
For more information on enabling and configuring {% data variables.product.prodname_registry %} for {% data variables.location.product_location %}, see "[Getting started with {% data variables.product.prodname_registry %} for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)."
|
||||
有关启用和配置 {% data variables.location.product_location %} 的 {% data variables.product.prodname_registry %} 的详细信息，请参阅“[企业 {% data variables.product.prodname_registry %} 入门](/admin/packages/getting-started-with-github-packages-for-your-enterprise)”。
|
||||
{% endif %}
|
||||
|
||||
### 5. Using {% data variables.product.prodname_pages %}
|
||||
### 5. 使用 {% data variables.product.prodname_pages %}
|
||||
{% data reusables.getting-started.github-pages-enterprise %}
|
||||
|
||||
## Part 5: Connecting with other {% data variables.product.prodname_dotcom %} resources
|
||||
You can use {% data variables.product.prodname_github_connect %} to share resources.
|
||||
## 第 5 部分：与其他 {% data variables.product.prodname_dotcom %} 资源连接
|
||||
您可以使用 {% data variables.product.prodname_github_connect %} 共享资源。
|
||||
|
||||
If you are the owner of both a {% data variables.product.product_name %} instance and a {% data variables.product.prodname_ghe_cloud %} organization or enterprise account, you can enable {% data variables.product.prodname_github_connect %}. {% data variables.product.prodname_github_connect %} allows you to share specific workflows and features between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, such as unified search and contributions. For more information, see "[Connecting {% data variables.product.prodname_ghe_server %} to {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)."
|
||||
如果您既是 {% data variables.product.product_name %} 实例的所有者，又是 {% data variables.product.prodname_ghe_cloud %} 组织或企业帐户的所有者，则可以启用 {% data variables.product.prodname_github_connect %}。 {% data variables.product.prodname_github_connect %} 允许你在 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间共享特定的工作流和功能，例如统一搜索和贡献。 有关详细信息，请参阅“[将 {% data variables.product.prodname_ghe_server %} 连接到 {% data variables.product.prodname_ghe_cloud %}](/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud)”。
|
||||
|
||||
## Part 6: Using {% data variables.product.prodname_dotcom %}'s learning and support resources
|
||||
Your enterprise members can learn more about Git and {% data variables.product.prodname_dotcom %} with our learning resources, and you can get the support you need when setting up and managing {% data variables.location.product_location %} with {% data variables.product.prodname_dotcom %} Enterprise Support.
|
||||
## 第 6 部分：使用 {% data variables.product.prodname_dotcom %} 的学习和支持资源
|
||||
企业成员可以通过我们的学习资源了解有关 Git 和 {% data variables.product.prodname_dotcom %} 的更多信息，并且你可以在设置和管理 {% data variables.location.product_location %} 时向 {% data variables.product.prodname_dotcom %} Enterprise 支持获得所需的支持。
|
||||
|
||||
### 1. Reading about {% data variables.product.product_name %} on {% data variables.product.prodname_docs %}
|
||||
### 1. 在 {% data variables.product.prodname_docs %} 上阅读 {% data variables.product.product_name %}
|
||||
|
||||
You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_server %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)."
|
||||
您可以阅读反映 {% data variables.product.prodname_ghe_server %} 可用功能的文档。 有关详细信息，请参阅[关于 {% data variables.product.prodname_docs %} 的版本](/get-started/learning-about-github/about-versions-of-github-docs)。
|
||||
|
||||
{% data reusables.enterprise.best-practices %}
|
||||
|
||||
### 2. Learning with {% data variables.product.prodname_learning %}
|
||||
### 2. 通过 {% data variables.product.prodname_learning %} 学习
|
||||
{% data reusables.getting-started.learning-enterprise %}
|
||||
|
||||
### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support
|
||||
### 3. 使用 {% data variables.product.prodname_dotcom %} Enterprise 支持
|
||||
{% data reusables.getting-started.contact-support-enterprise %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Migrating from {% data variables.product.prodname_projects_v1 %}'
|
||||
intro: 'You can migrate your {% data variables.projects.projects_v1_board %} to the new {% data variables.product.prodname_projects_v2 %} experience.'
|
||||
title: '从 {% data variables.product.prodname_projects_v1 %} 中迁移'
|
||||
intro: '可以将 {% data variables.projects.projects_v1_board %} 迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验。'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
@@ -10,57 +10,53 @@ type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: e6db4fd8c6587f413ee0e6832dbae93bbf281573
|
||||
ms.sourcegitcommit: 9bf175b190674416ad4e11b5c567409f74c00ad2
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/23/2022
|
||||
ms.locfileid: '148181219'
|
||||
---
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Notes:**
|
||||
**注意：**
|
||||
|
||||
- If the project you are migrating contains more than {% data variables.projects.item_limit %} items, open issues will be prioritized followed by open pull requests and then notes. Remaining space will be used for closed issues, merged pull requested, and closed pull requests. Items that cannot be migrated due to this limit will be moved to the archive. If the archive limit of {% data variables.projects.archived_item_limit %} items is reached, additional items will not be migrated.
|
||||
- Note cards are converted to draft issues, and the contents are saved to the body of the draft issue. If information appears to be missing, make any hidden fields visible. For more information, see "[Showing and hiding fields](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)."
|
||||
- Automation will not be migrated.
|
||||
- Triage, archive, and activity will not be migrated.
|
||||
- After migration, the new migrated project and old project will not be kept in sync.
|
||||
- 如果你要迁移的项目包含超过 {% data variables.projects.item_limit %} 个项，则将优先处理未结的问题，接着是未解决的拉取请求，然后是注释。 剩余的空间将用于已解决的问题、已合并的请求拉取和已解决的拉取请求。 由于此限制而无法迁移的项将被移动到存档。 如果达到 {% data variables.projects.archived_item_limit %} 个项的存档限制，则不会迁移其他项。
|
||||
- 注释卡被转换为草稿问题，内容被保存到草稿问题的正文中。 如果信息出现缺失，请使任何隐藏的字段可见。 有关详细信息，请参阅“[显示和隐藏字段](/issues/planning-and-tracking-with-projects/customizing-views-in-your-project/customizing-a-view#showing-and-hiding-fields)”。
|
||||
- 不会迁移自动化。
|
||||
- 不会迁移会审、存档和活动。
|
||||
- 迁移后，新迁移的项目和旧项目不会保持同步。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About project migration
|
||||
## 关于项目迁移
|
||||
|
||||
You can migrate your project boards to the new {% data variables.product.prodname_projects_v2 %} experience and try out tables, multiple views, new automation options, and powerful field types. For more information, see "[About projects](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)."
|
||||
可以将项目板迁移到新的 {% data variables.product.prodname_projects_v2 %} 体验，并试用表格、多个视图、新的自动化选项和强大的字段类型。 有关详细信息，请参阅“[关于项目](/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects)”。
|
||||
|
||||
## Migrating an organization project board
|
||||
## 迁移组织项目板
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}
|
||||
1. On the left, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}
|
||||
1. 在左侧，单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a user project board
|
||||
## 迁移用户项目板
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.profile.access_profile %}
|
||||
1. On the top of your profile page, in the main navigation, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Above the list of projects, click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.profile.access_profile %}
|
||||
1. 在个人资料页面顶部的主导航栏中，单击 {% octicon "table" aria-label="The project board icon" %}“项目”。
|
||||
|
||||
1. 在项目列表上方，单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
## Migrating a repository project board
|
||||
## 迁移存储库项目板
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data variables.projects.projects_v2_caps %} does not support repository level projects. When you migrate a repository project board, it will migrate to either the organization or personal account that owns the repository project, and the migrated project will be pinned to the original repository.
|
||||
注意：{% data variables.projects.projects_v2_caps %} 不支持存储库级别的项目。 当你迁移存储库项目板时，它将迁移到拥有存储库项目的组织或个人帐户，并且迁移的项目将被固定到原始存储库。
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.enable-migration %}
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Under your repository name, click {% octicon "table" aria-label="The project board icon" %} **Projects**.
|
||||
|
||||
1. Click **Projects (classic)**.
|
||||
|
||||
{% data reusables.projects.migrate-project-steps %}
|
||||
{% data reusables.projects.enable-migration %} {% data reusables.repositories.navigate-to-repo %}
|
||||
1. 在存储库名称下，单击 {% octicon "table" aria-label="The project board icon" %}“项目”。
|
||||
|
||||
1. 单击“Projects (经典)”。
|
||||
 {% data reusables.projects.migrate-project-steps %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Quickstart for GitHub Packages
|
||||
intro: 'Publish to {% data variables.product.prodname_registry %} with {% data variables.product.prodname_actions %}.'
|
||||
title: GitHub Packages 快速入门
|
||||
intro: '通过 {% data variables.product.prodname_actions %} 发布到 {% data variables.product.prodname_registry %}。'
|
||||
allowTitleToDifferFromFilename: true
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -8,29 +8,34 @@ versions:
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Quickstart
|
||||
ms.openlocfilehash: 887c4ee6c5e6b3e2c391c2d5754cfcb2787e4b86
|
||||
ms.sourcegitcommit: cfe91073c844cb762131b2de9fb41f7f9db792fc
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/24/2022
|
||||
ms.locfileid: '148181251'
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Introduction
|
||||
## 简介
|
||||
|
||||
In this guide, you'll create a {% data variables.product.prodname_actions %} workflow to test your code and then publish it to {% data variables.product.prodname_registry %}.
|
||||
在本指南中，您将创建 {% data variables.product.prodname_actions %} 工作流程来测试代码，然后将其发布到 {% data variables.product.prodname_registry %}。
|
||||
|
||||
## Publishing your package
|
||||
## 发布包
|
||||
|
||||
1. Create a new repository on {% data variables.product.prodname_dotcom %}, adding the `.gitignore` for Node. For more information, see "[Creating a new repository](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)."
|
||||
2. Clone the repository to your local machine.
|
||||
1. 在 {% data variables.product.prodname_dotcom %} 上创建新存储库，为节点添加 `.gitignore`。 有关详细信息，请参阅“[创建新存储库](/github/creating-cloning-and-archiving-repositories/creating-a-new-repository)”。
|
||||
2. 将存储库克隆到本地计算机。
|
||||
```shell
|
||||
$ git clone https://{% ifversion ghes or ghae %}YOUR-HOSTNAME{% else %}github.com{% endif %}/YOUR-USERNAME/YOUR-REPOSITORY.git
|
||||
$ cd YOUR-REPOSITORY
|
||||
```
|
||||
3. Create an `index.js` file and add a basic alert to say "Hello world!"
|
||||
3. 创建 `index.js` 文件，并添加指示“Hello world!”的基本警报
|
||||
{% raw %}
|
||||
```javascript{:copy}
|
||||
console.log("Hello, World!");
|
||||
```
|
||||
{% endraw %}
|
||||
4. Initialize an npm package with `npm init`. In the package initialization wizard, enter your package with the name: _`@YOUR-USERNAME/YOUR-REPOSITORY`_, and set the test script to `exit 0`. This will generate a `package.json` file with information about your package.
|
||||
4. 使用 `npm init` 初始化 npm 包。 在包初始化向导中，输入名称为 _`@YOUR-USERNAME/YOUR-REPOSITORY`_ 的包，并将测试脚本设置为 `exit 0`。 这将生成一个 `package.json` 文件，其中包含有关包的信息。
|
||||
{% raw %}
|
||||
```shell
|
||||
$ npm init
|
||||
@@ -41,15 +46,15 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
|
||||
...
|
||||
```
|
||||
{% endraw %}
|
||||
5. Run `npm install` to generate the `package-lock.json` file, then commit and push your changes to {% data variables.product.prodname_dotcom %}.
|
||||
5. 运行 `npm install` 以生成 `package-lock.json` 文件，然后提交更改并将其推送到 {% data variables.product.prodname_dotcom %}。
|
||||
```shell
|
||||
$ npm install
|
||||
$ git add index.js package.json package-lock.json
|
||||
$ git commit -m "initialize npm package"
|
||||
$ git push
|
||||
```
|
||||
6. Create a `.github/workflows` directory. In that directory, create a file named `release-package.yml`.
|
||||
7. Copy the following YAML content into the `release-package.yml` file{% ifversion ghes or ghae %}, replacing `YOUR-HOSTNAME` with the name of your enterprise{% endif %}.
|
||||
6. 创建 `.github/workflows` 目录。 在此目录中，创建名为 `release-package.yml` 的文件。
|
||||
7. 将以下 YAML 内容复制到 `release-package.yml` 文件{% ifversion ghes or ghae %} 中，将 `YOUR-HOSTNAME` 替换为企业名称{% endif %}。
|
||||
```yaml{:copy}
|
||||
name: Node.js Package
|
||||
|
||||
@@ -85,22 +90,20 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
|
||||
env:
|
||||
NODE_AUTH_TOKEN: ${% raw %}{{secrets.GITHUB_TOKEN}}{% endraw %}
|
||||
```
|
||||
8. Tell NPM which scope and registry to publish packages to using one of the following methods:
|
||||
- Add an NPM configuration file for the repository by creating a `.npmrc` file in the root directory with the contents:
|
||||
{% raw %}
|
||||
8. 告诉 NPM 使用以下方法之一发布包的范围和注册表：
|
||||
- 在根目录中创建包含以下内容的 `.npmrc` 文件，为存储库添加 NPM 配置文件：{% raw %}
|
||||
```shell
|
||||
@YOUR-USERNAME:registry=https://npm.pkg.github.com
|
||||
```
|
||||
{% endraw %}
|
||||
- Edit the `package.json` file and specify the `publishConfig` key:
|
||||
{% raw %}
|
||||
- 编辑 `package.json` 文件并指定 `publishConfig` 密钥：{% raw %}
|
||||
```shell
|
||||
"publishConfig": {
|
||||
"@<em>YOUR-USERNAME</em>:registry": "https://npm.pkg.github.com"
|
||||
}
|
||||
```
|
||||
{% endraw %}
|
||||
9. Commit and push your changes to {% data variables.product.prodname_dotcom %}.
|
||||
9. 提交并推送更改到 {% data variables.product.prodname_dotcom %}。
|
||||
```shell
|
||||
$ git add .github/workflows/release-package.yml
|
||||
# Also add the file you created or edited in the previous step.
|
||||
@@ -108,28 +111,26 @@ In this guide, you'll create a {% data variables.product.prodname_actions %} wor
|
||||
$ git commit -m "workflow to publish package"
|
||||
$ git push
|
||||
```
|
||||
10. The workflow that you created will run whenever a new release is created in your repository. If the tests pass, then the package will be published to {% data variables.product.prodname_registry %}.
|
||||
10. 只要您的仓库中创建新版本，您创建的工作流程就会运行。 如果测试通过，则包将发布到 {% data variables.product.prodname_registry %}。
|
||||
|
||||
To test this out, navigate to the **Code** tab in your repository and create a new release. For more information, see "[Managing releases in a repository](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)."
|
||||
要测试这一点，请导航到存储库中的“代码”选项卡，并创建新版本。 有关详细信息，请参阅“[管理存储库中的发行版](/github/administering-a-repository/managing-releases-in-a-repository#creating-a-release)”。
|
||||
|
||||
## Viewing your published package
|
||||
## 查看已发布的包
|
||||
|
||||
You can view all of the packages you have published.
|
||||
您可以查看您发布的所有软件包。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.package_registry.packages-from-code-tab %}
|
||||
{% data reusables.package_registry.navigate-to-packages %}
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %}
|
||||
|
||||
## Installing a published package
|
||||
## 安装已发布的包
|
||||
|
||||
Now that you've published the package, you'll want to use it as a dependency across your projects. For more information, see "[Working with the npm registry](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)."
|
||||
现在，您已发布包，您需要使用它作为项目之间的依赖项。 有关详细信息，请参阅“[使用 npm 注册表](/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package)”。
|
||||
|
||||
## Next steps
|
||||
## 后续步骤
|
||||
|
||||
The basic workflow you just added runs any time a new release is created in your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_registry %}. You can publish your package to multiple registries with a single workflow, trigger the workflow to run on different events such as a merged pull request, manage containers, and more.
|
||||
您刚刚添加的基本工作流程在仓库中创建新版本时运行。 但是，这只是您可以对 {% data variables.product.prodname_registry %} 执行操作的开始。 您可以使用单个工作流和将包发布到多个注册表，触发工作流程以在发生不同事件（如合并拉取请求、管理容器等）时运行。
|
||||
|
||||
Combining {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_registry %} and {% data variables.product.prodname_actions %}:
|
||||
合并 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 可以帮助您实现应用程序开发过程几乎每个方面的自动化。 准备好开始了吗？ 以下是一些有用的资源，可用于执行 {% data variables.product.prodname_registry %} 和 {% data variables.product.prodname_actions %} 的后续步骤：
|
||||
|
||||
- "[Learn {% data variables.product.prodname_registry %}](/packages/learn-github-packages)" for an in-depth tutorial on GitHub Packages
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial on GitHub Actions
|
||||
- "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)" for specific uses cases and examples
|
||||
- 有关 GitHub 包的深入教程，请“[了解 {% data variables.product.prodname_registry %}](/packages/learn-github-packages)”。
|
||||
- 有关 GitHub Actions 的深入教程，请“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”
|
||||
- 有关特定用例和示例，请“[使用 {% data variables.product.prodname_registry %} 注册表](/packages/working-with-a-github-packages-registry)”
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Creating a repository from a template
|
||||
intro: You can generate a new repository with the same directory structure and files as an existing repository.
|
||||
title: 从模板创建仓库
|
||||
intro: 您可以生成具有与现有仓库相同的目录结构和文件的新仓库。
|
||||
redirect_from:
|
||||
- /articles/creating-a-repository-from-a-template
|
||||
- /github/creating-cloning-and-archiving-repositories/creating-a-repository-from-a-template
|
||||
@@ -13,45 +13,46 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Create from a template
|
||||
ms.openlocfilehash: 16d124431426e19cf95c768e8a4cdaa5f4da2e17
|
||||
ms.sourcegitcommit: e8c012864f13f9146e53fcb0699e2928c949ffa8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/09/2022
|
||||
ms.locfileid: '148159762'
|
||||
---
|
||||
## About repository templates
|
||||
## 关于仓库模板
|
||||
|
||||
Anyone with read permissions to a template repository can create a repository from that template. For more information, see "[Creating a template repository](/articles/creating-a-template-repository)."
|
||||
任何对模板仓库具有读取权限的人都可以从该模板创建仓库。 有关详细信息，请参阅“[创建模板存储库](/articles/creating-a-template-repository)”。
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: You can also create a repository from a template using the {% data variables.product.prodname_cli %}. For more information, see "[`gh repo create`](https://cli.github.com/manual/gh_repo_create)" in the {% data variables.product.prodname_cli %} documentation.
|
||||
提示：你也可以使用 {% data variables.product.prodname_cli %} 从模板创建存储库。 有关详细信息，请参阅 {% data variables.product.prodname_cli %} 文档中的“[`gh repo create`](https://cli.github.com/manual/gh_repo_create)”。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
You can choose to include the directory structure and files from only the default branch of the template repository or to include all branches. Branches created from a template have unrelated histories, which means you cannot create pull requests or merge between the branches.
|
||||
您可以选择仅包括模板仓库的默认分支中的目录结构和文件，或者包括所有分支。 从模板创建的分支具有不相关的历史记录，这意味着您无法创建拉取请求或在分支之间合并。
|
||||
|
||||
Creating a repository from a template is similar to forking a repository, but there are important differences:
|
||||
- A new fork includes the entire commit history of the parent repository, while a repository created from a template starts with a single commit.
|
||||
- Commits to a fork don't appear in your contributions graph, while commits to a repository created from a template do appear in your contribution graph.
|
||||
- A fork can be a temporary way to contribute code to an existing project, while creating a repository from a template starts a new project quickly.
|
||||
从模板创建仓库类似于创建仓库的复刻，但存在一些重要差异：
|
||||
- 新的复刻包含父仓库的整个提交历史记录，而从模板创建的仓库从一个提交开始记录。
|
||||
- 对复刻的提交不会显示在您的贡献图中，而对从模板创建的仓库的提交会显示在您的贡献图中。
|
||||
- 复刻可能是向现有项目贡献代码的临时方式，而从模板创建的仓库可以快速启动新项目。
|
||||
|
||||
For more information about forks, see "[About forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
|
||||
有关分支的详细信息，请参阅“[关于分支](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)”。
|
||||
|
||||
## Creating a repository from a template
|
||||
## 从模板创建仓库
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Above the file list, click **Use this template**.
|
||||
1. 在文件列表上方，单击“使用此模板”。
|
||||
{% ifversion fpt or ghec %}
|
||||
1. Select **Create a new repository**.
|
||||
1. 选择“创建新存储库”。
|
||||
|
||||
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Alternatively, you can open the template in a codespace and publish your work to a new repository later. For more information, see "[Creating a codespace from a template](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)."
|
||||
注意：此外，你也可以在 codespace 中打开模板，稍后将工作发布到新存储库。 有关详细信息，请参阅“[通过模板创建 codespace](/codespaces/developing-in-codespaces/creating-a-codespace-from-a-template)”。
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
{% data reusables.repositories.owner-drop-down %}
|
||||
{% data reusables.repositories.repo-name %}
|
||||
{% data reusables.repositories.choose-repo-visibility %}
|
||||
1. Optionally, to include the directory structure and files from all branches in the template, and not just the default branch, select **Include all branches**.
|
||||
|
||||
{% data reusables.repositories.select-marketplace-apps %}
|
||||
8. Click **Create repository from template**.
|
||||
{% endnote %} {% endif %} {% data reusables.repositories.owner-drop-down %} {% data reusables.repositories.repo-name %} {% data reusables.repositories.choose-repo-visibility %}
|
||||
1. （可选）要在模板中包含来自所有分支的目录结构和文件，而不仅仅是默认分支，请选择“包含所有分支”。
|
||||
 {% data reusables.repositories.select-marketplace-apps %}
|
||||
8. 单击“从模板创建存储库”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Automatically generated release notes
|
||||
intro: You can automatically generate release notes for your GitHub releases
|
||||
title: 自动生成的发行说明
|
||||
intro: 您可以为 GitHub 版本自动生成发行说明
|
||||
permissions: Repository collaborators and people with write access to a repository can generate and customize automated release notes for a release.
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -13,71 +13,63 @@ shortTitle: Automated release notes
|
||||
communityRedirect:
|
||||
name: Provide GitHub Feedback
|
||||
href: 'https://github.com/orgs/community/discussions/categories/general'
|
||||
ms.openlocfilehash: aee951e6f57492240b5baf8870578409945aefdc
|
||||
ms.sourcegitcommit: 1a77ceb9e20c002173dda983db9405bcd5be254a
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/29/2022
|
||||
ms.locfileid: '148185192'
|
||||
---
|
||||
## 关于自动生成的发行说明
|
||||
|
||||
## About automatically generated release notes
|
||||
自动生成的发行说明为 {% data variables.product.prodname_dotcom %} 发行版手动编写发行说明提供了一种自动替代方法。 使用自动生成的发行说明，您可以快速生成发行版内容的概览。 自动生成的发行说明包括合并的拉取请求列表、发布参与者列表和完整更改日志的链接。
|
||||
|
||||
Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. Automatically generated release notes include a list of merged pull requests, a list of contributors to the release, and a link to a full changelog.
|
||||
您还可以自定义自动发行说明，使用标签创建自定义类别来组织要包含的拉取请求，并排除某些标签和用户不出现在输出中。
|
||||
|
||||
You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
|
||||
## 为新版本创建自动生成的发行说明
|
||||
|
||||
## Creating automatically generated release notes for a new release
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Click **Draft a new release**.
|
||||
|
||||
4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
5. If you are creating a new tag, click **Create new tag**.
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
6. If you have created a new tag, use the drop-down menu to select the branch that contains the project you want to release.
|
||||
{% ifversion fpt or ghec %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
{%- data reusables.releases.previous-release-tag %}
|
||||
7. To the top right of the description text box, click {% ifversion previous-release-tag %}**Generate release notes**{% else %}**Auto-generate release notes**{% endif %}.{% ifversion previous-release-tag %}
|
||||
{% else %}
|
||||
{% endif %}
|
||||
8. Check the generated notes to ensure they include all (and only) the information you want to include.
|
||||
9. Optionally, to include binary files such as compiled programs in your release, drag and drop or manually select files in the binaries box.
|
||||
|
||||
10. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
|
||||
|
||||
{%- ifversion fpt or ghec %}
|
||||
11. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
|
||||
|
||||
{%- endif %}
|
||||
12. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.releases %}
|
||||
3. 单击“草拟新发行版”。
|
||||
|
||||
4. {% ifversion fpt or ghec %}单击“选择标记”，然后键入{% else %}键入{% endif %}发行版的版本号。 或者，选择现有标记。
|
||||
{% ifversion fpt or ghec %} 
|
||||
5. 如果要创建新标记，请单击“创建新标记”。
|
||||
 {% else %}  {% endif %}
|
||||
6. 如果已创建新标记，请使用下拉菜单选择包含要发布的项目的分支。
|
||||
{% ifversion fpt or ghec %}{% else %} {% endif %} {%- data reusables.releases.previous-release-tag %}
|
||||
7. 在说明文本框右上角，单击{% ifversion previous-release-tag %}“生成发行说明”{% else %}“自动生成发行说明”{% endif %}。{% ifversion previous-release-tag %}{% else %}{% endif %}
|
||||
8. 检查生成的注释，确保它们包含所有（且仅有）您要包含的信息。
|
||||
9. （可选）要在发行版中包含二进制文件（例如已编译的程序），请在二进制文件框中拖放或手动选择文件。
|
||||
|
||||
10. 若要通知用户发行版尚未准备投入生产，并且可能不稳定，请选择“这是预发行版”。
|
||||
 {%- ifversion fpt or ghec %}
|
||||
11. （可选）选择“为此版本创建讨论”，然后选择“类别”下拉菜单，然后单击类别进行版本讨论 。
|
||||
 {%- endif %}
|
||||
12. 如果已准备好公开发行版，请单击“发布发行版”。 若要稍后处理发行版，请单击“保存草稿”。
|
||||
|
||||
|
||||
|
||||
## Configuring automatically generated release notes
|
||||
## 配置自动生成的发行说明
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.files.add-file %}
|
||||
3. In the file name field, type `.github/release.yml` to create the `release.yml` file in the `.github` directory.
|
||||
|
||||
4. In the file, using the configuration options below, specify in YAML the pull request labels and authors you want to exclude from this release. You can also create new categories and list the pull request labels to be included in each of them.
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.files.add-file %}
|
||||
3. 在文件名字段中，键入 `.github/release.yml` 以在 `.github` 目录中创建 `release.yml` 文件。
|
||||
|
||||
4. 在文件中，使用下面的配置选项，在 YAML 中指定要从此版本中排除的拉取请求标签和作者。 您还可以创建新类别并列出要包含在每个类别中的拉取请求标签。
|
||||
|
||||
### Configuration options
|
||||
### 配置选项
|
||||
|
||||
| Parameter | Description |
|
||||
| 参数 | 说明 |
|
||||
| :- | :- |
|
||||
| `changelog.exclude.labels` | A list of labels that exclude a pull request from appearing in release notes. |
|
||||
| `changelog.exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from release notes. |
|
||||
| `changelog.categories[*].title` | **Required.** The title of a category of changes in release notes. |
|
||||
| `changelog.categories[*].labels`| **Required.** Labels that qualify a pull request for this category. Use `*` as a catch-all for pull requests that didn't match any of the previous categories. |
|
||||
| `changelog.categories[*].exclude.labels` | A list of labels that exclude a pull request from appearing in this category. |
|
||||
| `changelog.categories[*].exclude.authors` | A list of user or bot login handles whose pull requests are to be excluded from this category. |
|
||||
| `changelog.exclude.labels` | 不在发行说明中显示拉取请求的标签列表。 |
|
||||
| `changelog.exclude.authors` | 要从发行说明中排除其拉取请求的用户或自动程序登录句柄的列表。 |
|
||||
| `changelog.categories[*].title` | **必填。** 发行说明中更改类别的标题。 |
|
||||
| `changelog.categories[*].labels`| **必填。** 符合此类别的拉取请求条件的标签。 使用 `*` 作为与上述任何类别都不匹配的拉取请求的统称。 |
|
||||
| `changelog.categories[*].exclude.labels` | 不在此类别中显示拉取请求的标签列表。 |
|
||||
| `changelog.categories[*].exclude.authors` | 要从此类别中排除其拉取请求的用户或自动程序登录句柄的列表。 |
|
||||
|
||||
### Example configurations
|
||||
### 示例配置
|
||||
|
||||
A configuration for a repository that labels semver releases
|
||||
标记 SemVer 版本的存储库配置
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -104,7 +96,7 @@ changelog:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
A configuration for a repository that doesn't tag pull requests but where we want to separate out {% data variables.product.prodname_dependabot %} automated pull requests in release notes (`labels: '*'` is required to display a catchall category)
|
||||
不标记拉取请求但我们希望在发行说明中分离 {% data variables.product.prodname_dependabot %} 自动拉取请求的存储库的配置（`labels: '*'` 需要显示 catchall 类别）
|
||||
|
||||
{% raw %}
|
||||
```yaml{:copy}
|
||||
@@ -124,6 +116,6 @@ changelog:
|
||||
```
|
||||
{% endraw %}
|
||||
|
||||
## Further reading
|
||||
## 延伸阅读
|
||||
|
||||
- "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)"
|
||||
- [管理标签](/issues/using-labels-and-milestones-to-track-work/managing-labels)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Understanding connections between repositories
|
||||
intro: Use the network graph and forks list to understand fork networks.
|
||||
title: 了解仓库之间的连接
|
||||
intro: 使用网络图和分支列表了解分支网络。
|
||||
product: '{% data reusables.gated-features.repository-insights %}'
|
||||
redirect_from:
|
||||
- /articles/viewing-a-repository-s-network
|
||||
@@ -22,57 +22,60 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: Connections between repositories
|
||||
ms.openlocfilehash: 46cc440093c3ca8dc0952933847a6f04b0446661
|
||||
ms.sourcegitcommit: 468a0323fa636517985a3e08e2772dbb0545cab8
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/03/2022
|
||||
ms.locfileid: '148191353'
|
||||
---
|
||||
## 查看仓库的网络
|
||||
|
||||
## Viewing a repository's network
|
||||
|
||||
The network graph displays the branch history of the entire repository network, including fork branches. This graph is a timeline of the most recent commits, and shows up to 100 of the most recently pushed-to branches. The first row references the date and the first column references the branch owner. Use arrow keys or other keyboard shortcuts to more easily navigate the graph. They are provided in the “Keyboard shortcuts available” pop up under the graph.
|
||||
网络图显示了整个存储库网络的分支历史记录，包括创建分支。 此图是最近提交的时间线，最多显示 100 个最近已推送的分支。 第一行引用日期，第一列引用分支所有者。 使用箭头键或其他键盘快捷方式可以更轻松地在图中浏览。 图下面的“可用的键盘快捷方式”弹出窗口中提供了这些选项。
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** To see older branches, click and drag within the graph.
|
||||
提示：若要查看较旧的分支，请在图中单击并拖动。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
## Accessing the network graph
|
||||
## 访问网络图
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Network**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 在左侧边栏中，单击“网络”。
|
||||
|
||||
|
||||
## Listing the forks of a repository
|
||||
## 列出仓库的复刻
|
||||
|
||||
The Members graph displays all the forks of a repository.
|
||||
成员图显示仓库的所有复刻。
|
||||
|
||||
Forks are listed alphabetically by the organization or username of the person who forked the repository. You can click on the organization or username to be redirected to the organization or user's {% data variables.product.product_name %} profile page or click on the fork name to be redirected to the specific fork of the repository.
|
||||
分支按存储库分支创建组织或创建者用户名的字母顺序列出。 可以单击要重定向到组织或用户 {% data variables.product.product_name %} 个人资料页面的组织或用户名，或者单击要重定向到存储库特定分支的分支名称。
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Accessing the Members graph
|
||||
### 访问成员图
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. In the left sidebar, click **Forks**.
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %}
|
||||
3. 在左侧边栏中，单击“分支”。
|
||||
|
||||
|
||||
## Viewing the dependencies of a repository
|
||||
## 查看仓库的依赖项
|
||||
|
||||
You can use the dependency graph to explore the code your repository depends on.
|
||||
您可以使用依赖关系图来浏览仓库所依赖的代码。
|
||||
|
||||
Almost all software relies on code developed and maintained by other developers, often known as a supply chain. For example, utilities, libraries, and frameworks. These dependencies are an integral part of your code and any bugs or vulnerabilities in them may affect your code. It's important to review and maintain these dependencies.
|
||||
几乎所有软件都依赖于其他开发者开发和维护的代码，常常被称为供应链。 例如，实用程序、库和框架。 这些依赖项是代码不可分割的一部分，其中的任何错误或漏洞都可能影响您的代码。 审查和维护这些依赖项非常重要。
|
||||
|
||||
The dependency graph provides a great way to visualize and explore the dependencies for a repository. For more information, see "[About the dependency graph](/code-security/supply-chain-security/about-the-dependency-graph)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)."
|
||||
依赖关系图提供了可视化和探索仓库依赖关系的好方法。 有关详细信息，请参阅“[关于依赖项关系图](/code-security/supply-chain-security/about-the-dependency-graph)”和“[探索存储库的依赖项](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository)”。
|
||||
|
||||
You can also set up your repository so that {% data variables.product.company_short %} alerts you automatically whenever a security vulnerability is found in one of your dependencies. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
|
||||
您也可以设置仓库，以便在您的一个依赖项中发现安全漏洞时，{% data variables.product.company_short %} 会自动提醒您。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)”。
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Viewing a file
|
||||
intro: You can view raw file content or trace changes to lines in a file and discover how parts of the file evolved over time.
|
||||
title: 查看文件
|
||||
intro: 可以查看原始文件内容或跟踪对文件中各行的更改，了解文件的各个部分如何随时间演变。
|
||||
redirect_from:
|
||||
- /articles/using-git-blame-to-trace-changes-in-a-file
|
||||
- /articles/tracing-changes-in-a-file
|
||||
@@ -16,48 +16,54 @@ versions:
|
||||
topics:
|
||||
- Repositories
|
||||
shortTitle: View files and track file changes
|
||||
ms.openlocfilehash: 7d34e776cb1747ee749531e49abf6f0e3d052b3b
|
||||
ms.sourcegitcommit: 82b1242de02ecc4bdec02a5b6d11568fb2deb1aa
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 11/21/2022
|
||||
ms.locfileid: '148179847'
|
||||
---
|
||||
## Viewing or copying the raw file content
|
||||
## 查看或复制原始文件内容
|
||||
|
||||
With the raw view, you can view or copy the raw content of a file without any styling.
|
||||
使用原始视图，可以查看或复制不带任何样式的文件原始内容。
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
1. Click the file that you want to view.
|
||||
2. In the upper-right corner of the file view, click **Raw**.
|
||||
|
||||
3. Optionally, to copy the raw file content, in the upper-right corner of the file view, click **{% octicon "copy" aria-label="The copy icon" %}**.
|
||||
1. 单击要查看的文件。
|
||||
2. 在文件视图的右上角，单击“原始”。
|
||||
|
||||
3. （可选）若要复制原始文件内容，请在文件视图右上角单击“{% octicon "copy" aria-label="The copy icon" %}”。
|
||||
|
||||
## Viewing the line-by-line revision history for a file
|
||||
## 查看文件的逐行修订历史记录
|
||||
|
||||
With the blame view, you can view the line-by-line revision history for an entire file, or view the revision history of a single line within a file by clicking {% octicon "versions" aria-label="The prior blame icon" %}. Each time you click {% octicon "versions" aria-label="The prior blame icon" %}, you'll see the previous revision information for that line, including who committed the change and when.
|
||||
使用追溯视图时，可以查看整个文件的逐行修订历史记录，也可以单击 {% octicon "versions" aria-label="The prior blame icon" %} 查看文件中某一行的修订历史记录。 每次单击 {% octicon "versions" aria-label="The prior blame icon" %} 后，将看到该行以前的修订信息，包括提交更改的人员和时间。
|
||||
|
||||
|
||||
|
||||
|
||||
In a file or pull request, you can also use the {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} menu to view Git blame for a selected line or range of lines.
|
||||
在文件或拉取请求中，还可以使用 {% octicon "kebab-horizontal" aria-label="The horizontal kebab octicon" %} 菜单查看所选行或行范围的 Git 追溯。
|
||||
|
||||
|
||||
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip:** On the command line, you can also use `git blame` to view the revision history of lines within a file. For more information, see [Git's `git blame` documentation](https://git-scm.com/docs/git-blame).
|
||||
提示：在命令行上，还可以使用 `git blame` 查看文件内各行的修订历史记录。 有关详细信息，请参阅 [Git 的 `git blame` 文档](https://git-scm.com/docs/git-blame)。
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
2. Click to open the file whose line history you want to view.
|
||||
3. In the upper-right corner of the file view, click **Blame** to open the blame view.
|
||||
|
||||
4. To see earlier revisions of a specific line, or reblame, click {% octicon "versions" aria-label="The prior blame icon" %} until you've found the changes you're interested in viewing.
|
||||
|
||||
2. 单击以打开您想要查看其行历史记录的文件。
|
||||
3. 在文件视图的右上角，单击“追溯”以打开追溯视图。
|
||||
|
||||
4. 若要查看特定行的早期修订，或重新追溯，请单击 {% octicon "versions" aria-label="The prior blame icon" %}，直至找到你想查看的更改。
|
||||
|
||||
|
||||
{% ifversion blame-ignore-revs %}
|
||||
|
||||
## Ignore commits in the blame view
|
||||
## 忽略追溯视图中的提交
|
||||
|
||||
All revisions specified in the `.git-blame-ignore-revs` file, which must be in the root directory of your repository, are hidden from the blame view using Git's `git blame --ignore-revs-file` configuration setting. For more information, see [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt) in the Git documentation.
|
||||
`.git-blame-ignore-revs` 文件中指定的所有修订（必须位于存储库的根目录中）利用 Git 的 `git blame --ignore-revs-file` 配置设置从追溯视图中隐藏。 有关详细信息，请参阅 Git 文档中的 [`git blame --ignore-revs-file`](https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt)。
|
||||
|
||||
1. In the root directory of your repository, create a file named `.git-blame-ignore-revs`.
|
||||
2. Add the commit hashes you want to exclude from the blame view to that file. We recommend the file to be structured as follows, including comments:
|
||||
1. 在存储库的根目录中，创建一个名为 `.git-blame-ignore-revs` 的文件。
|
||||
2. 在该文件中添加要从追溯视图中排除的提交哈希。 建议按如下所示构建文件（包括评论）：
|
||||
|
||||
```ini
|
||||
# .git-blame-ignore-revs
|
||||
@@ -67,19 +73,19 @@ All revisions specified in the `.git-blame-ignore-revs` file, which must be in t
|
||||
69d029cec8337c616552756310748c4a507bd75a
|
||||
```
|
||||
|
||||
3. Commit and push the changes.
|
||||
3. 提交并推送更改。
|
||||
|
||||
Now when you visit the blame view, the listed revisions will not be included in the blame. You'll see an **Ignoring revisions in .git-blame-ignore-revs** banner indicating that some commits may be hidden:
|
||||
现在，访问追溯视图时，追溯中将不会包含列出的修订。 你会看到“忽略 .git-blame-ignore-revs 中的修订”横幅，表明某些提交可能已隐藏：
|
||||
|
||||
|
||||
|
||||
|
||||
This can be useful when a few commits make extensive changes to your code. You can use the file when running `git blame` locally as well:
|
||||
当一些提交对代码进行大量更改时，这非常有用。 也可以在本地运行 `git blame` 时使用该文件：
|
||||
|
||||
```shell
|
||||
git blame --ignore-revs-file .git-blame-ignore-revs
|
||||
```
|
||||
|
||||
You can also configure your local git so it always ignores the revs in that file:
|
||||
还可以配置本地 git，使其始终忽略该文件中的修订：
|
||||
|
||||
```shell
|
||||
git config blame.ignoreRevsFile .git-blame-ignore-revs
|
||||
@@ -87,6 +93,6 @@ git config blame.ignoreRevsFile .git-blame-ignore-revs
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Bypassing `.git-blame-ignore-revs` in the blame view
|
||||
## 绕过追溯视图中的 `.git-blame-ignore-revs`
|
||||
|
||||
If the blame view for a file shows **Ignoring revisions in .git-blame-ignore-revs**, you can still bypass `.git-blame-ignore-revs` and see the normal blame view. In the URL, append a `~` to the SHA and the **Ignoring revisions in .git-blame-ignore-revs** will disappear.
|
||||
如果文件的追溯视图显示“忽略 .git-blame-ignore-revs 中的修订”，仍可以绕过 `.git-blame-ignore-revs` 并查看正常的追溯视图。 在 URL 中，将 `~` 追加到 SHA，“忽略 .git-blame-ignore-revs 中的修订”将消失。
|
||||
|
||||
@@ -11,12 +11,12 @@ versions:
|
||||
ghec: '*'
|
||||
topics:
|
||||
- API
|
||||
ms.openlocfilehash: ab880cef09b936bb573d783373f048395d0a2f58
|
||||
ms.sourcegitcommit: 16548aa24259e37cc0ac4900ca8fefc46dc84cdb
|
||||
ms.openlocfilehash: 5f633132edddb17ae129a3feba791ab8ec780366
|
||||
ms.sourcegitcommit: 9af8891fea10039b3374c76818634e05410e349d
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 12/01/2022
|
||||
ms.locfileid: '148190059'
|
||||
ms.lasthandoff: 12/06/2022
|
||||
ms.locfileid: '148191876'
|
||||
---
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ ms.locfileid: '148190059'
|
||||
|
||||
- Ruby → [octokit.rb](https://github.com/octokit/octokit.rb)
|
||||
- .NET → [octokit.net](https://github.com/octokit/octokit.net)
|
||||
- JavaScript → [octokit/octokit.js](https://github.com/octokit/octokit.js)
|
||||
- JavaScript → [octokit.js](https://github.com/octokit/octokit.js)
|
||||
|
||||
## 第三方库
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 查看和更新支持工单
|
||||
intro: '可以查看支持票证{% ifversion ghes or ghec %}，与同事协作处理票证，{% endif %}并使用 {% data variables.contact.support_portal %} 响应 {% data variables.contact.github_support %}。'
|
||||
title: Viewing and updating support tickets
|
||||
intro: 'You can view your support tickets{% ifversion ghes or ghec %}, collaborate with colleagues on tickets,{% endif %} and respond to {% data variables.contact.github_support %} using the {% data variables.contact.support_portal %}.'
|
||||
shortTitle: Managing your tickets
|
||||
versions:
|
||||
fpt: '*'
|
||||
@@ -8,62 +8,64 @@ versions:
|
||||
ghes: '*'
|
||||
topics:
|
||||
- Support
|
||||
ms.openlocfilehash: 35c7b28232c0d11170ea9585480b2cfb1785ebd0
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147051978'
|
||||
---
|
||||
## 关于工单管理
|
||||
|
||||
## About ticket management
|
||||
|
||||
{% data reusables.support.zendesk-old-tickets %}
|
||||
|
||||
可以使用 [GitHub 支持门户](https://support.github.com/)查看当前和过去的支持工单并回复 {% data variables.contact.github_support %}。 120 天后，已解决的票证将会存档{% ifversion ghec or ghes or ghae %}，并且只能查看企业帐户的已存档票证{% endif %}。
|
||||
You can use the [GitHub Support Portal](https://support.github.com/) to view current and past support tickets and respond to {% data variables.contact.github_support %}. After 120 days, resolved tickets are archived{% ifversion ghec or ghes or ghae %}, and archived tickets can only be viewed for enterprise accounts{% endif %}.
|
||||
|
||||
{% ifversion ghes or ghec %} {% data reusables.enterprise-accounts.support-entitlements %} {% endif %}
|
||||
{% ifversion ghes or ghec %}
|
||||
{% data reusables.enterprise-accounts.support-entitlements %}
|
||||
{% endif %}
|
||||
|
||||
## 查看最近的支持票证
|
||||
## Viewing your recent support tickets
|
||||
|
||||
{% data reusables.support.view-open-tickets %}
|
||||
1. 在文本框下，可以阅读评论历史记录。 最近的回复位于顶部。
|
||||
|
||||
1. Under the text box, you can read the comment history. The most recent response is at the top.
|
||||
|
||||
|
||||
|
||||
1. Optionally, to translate the ticket comment, click {% octicon "globe" aria-label="The globe icon" %} and choose your preferred language from the dropdown menu. You can translate your support ticket into Chinese (Simplified), French, German, Japanese, Portuguese (Brazil), or Spanish.
|
||||
|
||||
|
||||
|
||||
{% ifversion ghec or ghes or ghae %}
|
||||
|
||||
## 查看已存档的支持票证
|
||||
## Viewing your archived support tickets
|
||||
|
||||
只能查看企业帐户的已存档票证。
|
||||
You can only view archived tickets for an enterprise account.
|
||||
|
||||
{% data reusables.support.navigate-to-my-tickets %}
|
||||
1. 选择“我的票证”下拉菜单，然后单击企业帐户的名称。
|
||||
1. Select the **My Tickets** drop-down menu and click the name of the enterprise account.
|
||||
|
||||
{% indented_data_reference reusables.support.entitlements-note spaces=3 %}
|
||||
|
||||
|
||||
1. 在“我的票证”表下，单击“查看已存档的票证”。
|
||||
|
||||
1. Under the "My tickets" table, click **View archived tickets**.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 更新支持工单
|
||||
## Updating support tickets
|
||||
|
||||
{% data reusables.support.view-open-tickets %}
|
||||
1. （可选）如果问题得到解决，请在文本框下单击“关闭工单”。
|
||||
|
||||
1. 若要回复 GitHub 支持并向工单添加新评论，请在文本框中输入你的回复。
|
||||
|
||||
1. 若要将评论添加到工单，请单击“评论”。
|
||||
|
||||
1. Optionally, if the issue is resolved, under the text box, click **Close ticket**.
|
||||
|
||||
1. To respond to GitHub Support and add a new comment to the ticket, type your response in the text box.
|
||||
|
||||
1. To add your comment to the ticket, click **Comment**.
|
||||
|
||||
|
||||
{% ifversion ghec or ghes %}
|
||||
## 协作处理支持工单
|
||||
## Collaborating on support tickets
|
||||
|
||||
你可以使用支持门户与你的同事协作处理支持工单。 拥有支持权利的所有者、计费管理员和其他企业成员可以查看与企业帐户或由企业帐户管理的组织关联的工单。 有关详细信息，请参阅“[管理企业的支持权利](/enterprise-cloud@latest/admin/user-management/managing-users-in-your-enterprise/managing-support-entitlements-for-your-enterprise)”。
|
||||
You can collaborate with your colleagues on support tickets using the support portal. Owners, billing managers, and other enterprise members with support entitlements can view tickets associated with an enterprise account or an organization managed by an enterprise account. 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)."
|
||||
|
||||
除了查看票据外，如果电子邮件地址复制到了工单上，或者工单创建者使用的电子邮件地址的域名被验证为企业帐户或企业帐户管理的组织，则还可以向支持工单添加评论。 有关验证域的详细信息，请参阅“[为企业验证或批准域](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)”和“[为组织验证或批准域](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)”。
|
||||
In addition to viewing tickets, you can also add comments to support tickets if your email address is copied on the ticket or if the person who opened the ticket used an email address with a domain that is verified for the enterprise account or organization managed by an enterprise account. For more information about verifying a domain, see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[Verifying or approving a domain for your organization](/enterprise-cloud@latest/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [关于 GitHub 支持](/support/learning-about-github-support/about-github-support)
|
||||
- "[About GitHub Support](/support/learning-about-github-support/about-github-support)"
|
||||
|
||||
@@ -83,6 +83,10 @@ If you have any paid product or are a member of an organization with a paid prod
|
||||
With {% data variables.product.product_name %}, you have access to support in English and Japanese.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes %}
|
||||
{% data reusables.support.support-ticket-translation-option %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes or ghec %}
|
||||
|
||||
To contact {% data variables.contact.github_support %}, visit the {% data variables.contact.contact_support_portal %}. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)."
|
||||
|
||||
@@ -29,4 +29,5 @@ sections:
|
||||
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
|
||||
- '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
|
||||
- |
|
||||
GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
|
||||
GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
|
||||
- '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
|
||||
@@ -1,27 +1,30 @@
|
||||
date: '2022-08-30'
|
||||
sections:
|
||||
bugs:
|
||||
- 解锁存储库以进行临时访问后，站点管理员无法管理存储库中安全产品的设置。
|
||||
- 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。
|
||||
- "<code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> 的个人用户的站点管理员页面包含不适用于 GitHub Enterprise Server 的功能。"
|
||||
- 在某些情况下，运行 `ghe-cluster-config-apply` 可以将空配置复制到群集中的现有节点。
|
||||
- 在某些情况下，以 `ghe-config-apply` 开始的配置运行未完成，或返回了 `Container count mismatch` 错误。
|
||||
- 在 GitHub Enterprise Server 实例上更新自签名 TLS 证书后，Web 界面中某些页面上的 UI 元素没有显示。
|
||||
- Web 界面顶部的站点管理员栏包含指向当前正在运行的应用程序版本的 SHA 的断开链接。
|
||||
- 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。
|
||||
- 如果站点管理员没有直接升级到 GitHub Enterprise Server 3.4，则 Web UI 和 REST API 中缺少来自 GitHub Advanced Security 客户的机密扫描的警报。警报现在可见。
|
||||
- 当用户将存储库分叉到组织中时，一长串组织将无法正确呈现。
|
||||
- After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
|
||||
- Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
|
||||
- The site admin page for individual users at <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> contained functionality not intended for GitHub Enterprise Server.
|
||||
- In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
|
||||
- In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
|
||||
- After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
|
||||
- The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
|
||||
- In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
|
||||
- Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
|
||||
- When a user forked a repository into an organization, a long list of organizations would not render properly.
|
||||
changes:
|
||||
- "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。"
|
||||
- "包含 `organization` 或 `org` 路由的 API 现在接受组织的 slug 或 ID。以前，API 只接受 slug，这导致 GitHub Advanced Security 终结点的 `Link` 标头无法访问。有关详细信息，请参阅 REST API 文档中的“[组织](https://docs.github.com/rest/orgs/orgs)”。"
|
||||
- "企业审核日志现在包含更多用户生成的事件，例如 `project.create`。REST API 还返回其他用户生成的事件，例如 `repo.create`。有关详细信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise)”和“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api)”。"
|
||||
- "在某些情况下，缓存副本可能会拒绝对最近更新的存储库的某些 Git 操作。有关存储库缓存的详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。"
|
||||
- Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
|
||||
- APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
|
||||
- The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
|
||||
- In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
|
||||
known_issues:
|
||||
- "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。"
|
||||
- 自定义防火墙规则在升级过程中被删除。
|
||||
- "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。"
|
||||
- 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。
|
||||
- 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
|
||||
- "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。"
|
||||
- 特定于处理预接收挂钩的资源限制可能会导致某些预接收挂钩失败。
|
||||
- 从不同主机上的备份恢复设备后，需要重新启动操作服务。
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- Actions services need to be restarted after restoring an appliance from a backup taken on a different host.
|
||||
- |
|
||||
GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
|
||||
- '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
|
||||
@@ -1,33 +1,38 @@
|
||||
date: '2022-08-30'
|
||||
sections:
|
||||
bugs:
|
||||
- 解锁存储库以进行临时访问后，站点管理员无法管理存储库中安全产品的设置。
|
||||
- 管理控制台和 `/home/admin/.ssh/authorized_keys` 文件中可能会出现重复的管理 SSH 密钥。
|
||||
- "<code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> 的个人用户的站点管理员页面包含不适用于 GitHub Enterprise Server 的功能。"
|
||||
- 在某些情况下，运行 `ghe-cluster-config-apply` 可以将空配置复制到群集中的现有节点。
|
||||
- 在某些情况下，以 `ghe-config-apply` 开始的配置运行未完成，或返回了 `Container count mismatch` 错误。
|
||||
- 在 GitHub Enterprise Server 实例上更新自签名 TLS 证书后，Web 界面中某些页面上的 UI 元素没有显示。
|
||||
- 在某些情况下，尽管不是线程安全的，但由于同时使用的库，可能会导致后台任务停止。
|
||||
- Web 界面顶部的站点管理员栏包含指向当前正在运行的应用程序版本的 SHA 的断开链接。
|
||||
- 组织所有者无法设置创建讨论所需的访问级别。
|
||||
- 讨论用户被错误地引导至 GitHub.com 的社区指南。
|
||||
- 在某些情况下，系统错误地指示用户在创建讨论之前验证其电子邮件。
|
||||
- 如果站点管理员没有直接升级到 GitHub Enterprise Server 3.4，则 Web UI 和 REST API 中缺少来自 GitHub Advanced Security 客户的机密扫描的警报。警报现在可见。
|
||||
- After unlocking a repository for temporary access, a site administrator was unable to manage settings for security products in the repository.
|
||||
- Duplicate administrative SSH keys could appear in both the Management Console and the `/home/admin/.ssh/authorized_keys` file.
|
||||
- The site admin page for individual users at <code>http(s)://<em>HOSTNAME</em>/stafftools/users/<em>USERNAME</em>/admin</code> contained functionality not intended for GitHub Enterprise Server.
|
||||
- In some cases, running `ghe-cluster-config-apply` could replicate an empty configuration to existing nodes in a cluster.
|
||||
- In some cases, configuration runs started with `ghe-config-apply` did not complete, or returned a `Container count mismatch` error.
|
||||
- After updating a self-signed TLS certificate on a GitHub Enterprise Server instance, UI elements on some pages in the web interface did not appear.
|
||||
- In some cases, background tasks could stall due to a library that was used concurrently despite not being thread-safe.
|
||||
- The site admin bar at the top of the web interface contained a broken link to the SHA for the currently running version of the application.
|
||||
- Organization owners were unable to set the level of access required to create discussions.
|
||||
- Discussions users were incorrectly directed to the community guidelines for GitHub.com.
|
||||
- In some cases, users were incorrectly instructed to verify their email before creating a discussion.
|
||||
- Alerts from secret scanning for GitHub Advanced Security customers were missing in the web UI and REST API if a site administrator did not upgrade directly to GitHub Enterprise Server 3.4. The alerts are now visible.
|
||||
changes:
|
||||
- "由于并行日志清理，支持包的生成速度更快。有关支持包的详细信息，请参阅“[将数据提供给 GitHub 支持](/support/contacting-github-support/providing-data-to-github-support)”。"
|
||||
- "包含 `organization` 或 `org` 路由的 API 现在接受组织的 slug 或 ID。以前，API 只接受 slug，这导致 GitHub Advanced Security 终结点的 `Link` 标头无法访问。有关详细信息，请参阅 REST API 文档中的“[组织](https://docs.github.com/rest/orgs/orgs)”。"
|
||||
- "企业审核日志现在包含更多用户生成的事件，例如 `project.create`。REST API 还返回其他用户生成的事件，例如 `repo.create`。有关详细信息，请参阅“[访问企业的审核日志](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for -your-enterprise)”和“[使用企业的审核日志 API](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit- log-api-for-your-enterprise#querying-the-audit-log-rest-api)”。"
|
||||
- "在某些情况下，缓存副本可能会拒绝对最近更新的存储库的某些 Git 操作。有关存储库缓存的详细信息，请参阅“[关于存储库缓存](/admin/enterprise-management/caching-repositories/about-repository-caching)”。"
|
||||
- "你现在可以使用 REST API 将全局公告横幅配置为可关闭。有关详细信息，请参阅“[为企业自定义用户消息](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)”。"
|
||||
- Generation of support bundles is faster as a result of parallelized log sanitization. For more information about support bundles, see "[Providing data to GitHub Support](/support/contacting-github-support/providing-data-to-github-support)."
|
||||
- APIs that contain the `organization` or `org` route now accept either the organization's slug or ID. Previously, the APIs only accepted slugs, which caused `Link` headers for GitHub Advanced Security endpoints to be inaccessible. For more information, see "[Organizations](https://docs.github.com/rest/orgs/orgs)" in the REST API documentation.
|
||||
- The enterprise audit log now includes more user-generated events, such as `project.create`. The REST API also returns additional user-generated events, such as `repo.create`. For more information, see "[Accessing the audit log for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/accessing-the-audit-log-for-your-enterprise)" and "[Using the audit log API for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise#querying-the-audit-log-rest-api)."
|
||||
- In some cases, cache replicas could reject some Git operations on recently updated repositories. For more information about repository caching, see "[About repository caching](/admin/enterprise-management/caching-repositories/about-repository-caching)."
|
||||
- You can now configure the global announcement banner to be dismissable using the REST API. For more information, see "[Customizing user messages for your enterprise](/admin/user-management/managing-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-global-announcement-banner)."
|
||||
known_issues:
|
||||
- "在新建的没有任何用户的 {% data variables.product.prodname_ghe_server %} 实例上，攻击者可以创建第一个管理员用户。"
|
||||
- 自定义防火墙规则在升级过程中被删除。
|
||||
- "[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。"
|
||||
- 如果问题包含指向同一存储库中 Blob 的永久链接，且 Blob 的文件路径长度超过 255 个字符，则无法关闭问题。
|
||||
- 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
|
||||
- "{% data variables.product.prodname_registry %} npm 注册表不再在元数据响应中返回时间值。这样可以大幅改善性能。作为元数据响应的一部分，我们继续拥有返回时间值所需的所有数据，并将在我们解决现有性能问题后恢复返回这个值。"
|
||||
- 特定于处理预接收挂钩的资源限制可能导致部分预接收挂钩失败。
|
||||
- 从不同主机上的备份恢复实例后，需要重新启动操作服务。
|
||||
- 在存储库的设置中，启用允许具有读取访问权限的用户创建讨论的选项不会启用此功能。
|
||||
- 在某些情况下，用户无法将现有问题转换为讨论。
|
||||
- 机密扫描的自定义模式将 `.*` 作为结束分隔符，特别是在“机密之后”字段中。此分隔符会导致跨存储库的机密扫描不一致，并且你可能会注意到存储库历史记录中没有完成扫描的间隙。增量扫描也可能受到影响。为防止出现扫描问题，请修改模式的结尾以删除 `.*` 分隔符。
|
||||
- On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
|
||||
- Custom firewall rules are removed during the upgrade process.
|
||||
- Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.
|
||||
- Issues cannot be closed if they contain a permalink to a blob in the same repository, where the blob's file path is longer than 255 characters.
|
||||
- When "Users can search GitHub.com" is enabled with GitHub Connect, issues in private and internal repositories are not included in GitHub.com search results.
|
||||
- The {% data variables.product.prodname_registry %} npm registry no longer returns a time value in metadata responses. This was done to allow for substantial performance improvements. We continue to have all the data necessary to return a time value as part of the metadata response and will resume returning this value in the future once we have solved the existing performance issues.
|
||||
- Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
|
||||
- Actions services need to be restarted after restoring an instance from a backup taken on a different host.
|
||||
- In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality.
|
||||
- In some cases, users cannot convert existing issues to discussions.
|
||||
- Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
|
||||
- |
|
||||
After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
|
||||
- |
|
||||
GitHub Pages builds may time out on instances in AWS that are configured for high availability. [Updated: 2022-11-28]
|
||||
- '{% data reusables.release-notes.babeld-max-threads-performance-issue %}'
|
||||
@@ -0,0 +1,17 @@
|
||||
{% ifversion ghes = 3.4 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Reusable workflows are currently in beta and subject to change.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% elsif ghae > 3.3 %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note**: Reusable workflows are currently unavailable in {% data variables.product.product_name %}, but will be available in a future update.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
@@ -21,3 +21,8 @@ A user is considered active if the user has performed any of the following activ
|
||||
- Starring a repository
|
||||
- Deleting a repository
|
||||
- Accessing resources by using a {% data variables.product.pat_generic %} or SSH key
|
||||
- Joining an organization
|
||||
|
||||
{% ifversion ghes %}
|
||||
A user will also be considered active if their account has been updated by LDAP.
|
||||
{% endif %}
|
||||
|
||||
@@ -127,7 +127,7 @@ products:
|
||||
rest:
|
||||
banner:
|
||||
api_versioned: The REST API is now versioned.
|
||||
api_version_info: For more information, see "<a href="{{ versionWithApiVersion }}/rest/overview/api-versions">About API versioning</a>".
|
||||
api_version_info: For more information, see "<a href="{{ versionWithApiVersion }}/rest/overview/api-versions">About API versioning</a>."
|
||||
ghes_api_versioned: After a site administrator upgrades your Enterprise Server instance to {{ firstGhesReleaseWithApiVersions.versionTitle }} or later, the REST API will be versioned. To learn how to find your instance's version, see "<a href="/{{ currentVersion }}/get-started/learning-about-github/about-versions-of-github-docs#github-enterprise-server">About versions of GitHub Docs</a>".
|
||||
versioning:
|
||||
about_versions: About REST API versions
|
||||
|
||||
Reference in New Issue
Block a user