From 118fa7ca0b249f43a2b427b2c30cf1da6aaa976c Mon Sep 17 00:00:00 2001 From: M Hickford Date: Sun, 5 Jun 2022 23:08:07 +0100 Subject: [PATCH 1/8] Describe contents of automatically generated release notes --- .../automatically-generated-release-notes.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md index 4cb3addc93..e35226edd8 100644 --- a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md +++ b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -19,6 +19,14 @@ communityRedirect: 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. 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. +### Contents of automatically generated release notes + +The automatically generated release notes include: + +* A list of merged pull requests. +* A list of contributors to the release. +* A link to a full changelog. + ## Creating automatically generated release notes for a new release {% data reusables.repositories.navigate-to-repo %} From 390e364c8334ae58fe0713eaa54779d7ed760b8d Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 6 Jun 2022 18:51:57 -0400 Subject: [PATCH 2/8] New translation batch for cn (#28276) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report --- translations/log/cn-resets.csv | 9 +- .../about-github-hosted-runners.md | 5 +- .../about-using-actions-in-your-enterprise.md | 2 +- ...bout-authentication-for-your-enterprise.md | 73 ++++++-- .../about-enterprise-managed-users.md | 15 +- .../about-saml-for-enterprise-iam.md | 76 ++++---- ...ting-a-listing-description-for-your-app.md | 2 +- .../create-a-group-assignment.md | 2 +- .../getting-started-with-github-ae.md | 2 +- ...ng-started-with-github-enterprise-cloud.md | 2 +- ...g-started-with-github-enterprise-server.md | 2 +- .../getting-started-with-github-team.md | 2 +- ...etting-started-with-your-github-account.md | 4 +- .../quickstart/contributing-to-projects.md | 2 +- .../get-started/quickstart/create-a-repo.md | 2 +- .../get-started/quickstart/fork-a-repo.md | 4 +- .../git-and-github-learning-resources.md | 2 +- .../basic-writing-and-formatting-syntax.md | 2 +- .../closing-an-issue.md | 30 +++ ...-and-searching-issues-and-pull-requests.md | 3 +- .../tracking-your-work-with-issues/index.md | 1 + .../index.md | 1 + .../managing-projects.md | 43 +++++ .../about-ssh-certificate-authorities.md | 6 + .../about-github-pages.md | 2 +- .../about-collaborative-development-models.md | 2 +- .../searching-issues-and-pull-requests.md | 92 +++++---- .../github-privacy-statement.md | 176 +++++++++--------- .../data/features/issue-close-reasons.yml | 8 + .../section-using-jobs-in-a-workflow-name.md | 2 +- ...b-enterprise.md => learning-enterprise.md} | 2 +- .../{learning-lab.md => learning.md} | 2 +- ...earning-lab.md => open-source-learning.md} | 0 .../data/reusables/projects/create-project.md | 7 +- .../reusables/projects/create-user-project.md | 5 +- .../reusables/projects/reopen-a-project.md | 6 + translations/zh-CN/data/variables/product.yml | 6 +- 37 files changed, 377 insertions(+), 225 deletions(-) create mode 100644 translations/zh-CN/content/issues/tracking-your-work-with-issues/closing-an-issue.md create mode 100644 translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-projects.md create mode 100644 translations/zh-CN/data/features/issue-close-reasons.yml rename translations/zh-CN/data/reusables/getting-started/{learning-lab-enterprise.md => learning-enterprise.md} (51%) rename translations/zh-CN/data/reusables/getting-started/{learning-lab.md => learning.md} (53%) rename translations/zh-CN/data/reusables/open-source/{open-source-learning-lab.md => open-source-learning.md} (100%) create mode 100644 translations/zh-CN/data/reusables/projects/reopen-a-project.md diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 9a459ea7ff..ebe4a83535 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -78,7 +78,6 @@ translations/zh-CN/content/admin/identity-and-access-management/using-enterprise translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users-with-okta.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,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md,broken liquid tags -translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-user-provisioning-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/index.md,broken liquid tags @@ -345,14 +344,14 @@ translations/zh-CN/data/reusables/dependabot/dependabot-alerts-dependency-graph- translations/zh-CN/data/reusables/dependabot/enterprise-enable-dependabot.md,broken liquid tags translations/zh-CN/data/reusables/dotcom_billing/downgrade-org-to-free.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-accounts/emu-password-reset-session.md,broken liquid tags -translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,broken liquid tags +translations/zh-CN/data/reusables/enterprise-accounts/emu-short-summary.md,rendering error translations/zh-CN/data/reusables/enterprise-licensing/about-license-sync.md,broken liquid tags translations/zh-CN/data/reusables/enterprise-licensing/you-can-sync-for-a-combined-view.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_installation/hardware-rec-table.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags translations/zh-CN/data/reusables/enterprise_management_console/badge_indicator.md,broken liquid tags -translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,broken liquid tags +translations/zh-CN/data/reusables/gated-features/enterprise-accounts.md,rendering error translations/zh-CN/data/reusables/gated-features/packages.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/secret-scanning.md,broken liquid tags translations/zh-CN/data/reusables/getting-started/actions.md,broken liquid tags @@ -373,9 +372,9 @@ translations/zh-CN/data/reusables/repositories/deleted_forks_from_private_reposi translations/zh-CN/data/reusables/repositories/enable-security-alerts.md,broken liquid tags translations/zh-CN/data/reusables/repositories/github-reviews-security-advisories.md,broken liquid tags translations/zh-CN/data/reusables/repositories/select-marketplace-apps.md,broken liquid tags -translations/zh-CN/data/reusables/saml/saml-session-oauth.md,broken liquid tags +translations/zh-CN/data/reusables/saml/saml-session-oauth.md,rendering error translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,Listed in localization-support#489 -translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,broken liquid tags +translations/zh-CN/data/reusables/saml/you-must-periodically-authenticate.md,rendering error translations/zh-CN/data/reusables/scim/after-you-configure-saml.md,broken liquid tags translations/zh-CN/data/reusables/secret-scanning/enterprise-enable-secret-scanning.md,broken liquid tags translations/zh-CN/data/reusables/security-advisory/link-browsing-advisory-db.md,broken liquid tags diff --git a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index 0b48304482..479516094e 100644 --- a/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/zh-CN/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -187,11 +187,8 @@ API 返回的 {% data variables.product.prodname_actions %} IP 地址列表每 - `/github/workspace` - {% data reusables.repositories.action-root-user-required %} - `/github/workflow` -{% ifversion fpt or ghec %} - ## 延伸阅读 - "[管理 {% data variables.product.prodname_actions %} 的计费](/billing/managing-billing-for-github-actions)" - -{% endif %} +- You can use a matrix strategy to run your jobs on multiple images. 更多信息请参阅“[对作业使用矩阵](/actions/using-jobs/using-a-matrix-for-your-jobs)”。 {% endif %} diff --git a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index b2dca564bc..6610670d48 100644 --- a/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/zh-CN/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos **Notes:** - When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." -- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. +- When {% data variables.product.product_name %} is updated, bundled actions are automatically replaced with default versions in the upgrade package. {% endnote %} diff --git a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 54025d7284..425d007629 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -21,7 +21,9 @@ topics: {% data variables.product.product_name %} 上的企业所有者可以控制身份验证和访问企业资源的要求。 -You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. 如果您允许成员管理自己的帐户，则还可以配置 SAML 身份验证，以提高安全性，并集中团队使用的 Web 应用程序的身份和访问权限。 如果选择管理成员的用户帐户，则必须配置 SAML 身份验证。 +You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. 如果您允许成员管理自己的帐户，则还可以配置 SAML 身份验证，以提高安全性，并集中团队使用的 Web 应用程序的身份和访问权限。 + +After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)." ## {% data variables.product.product_name %} 的身份验证方法 @@ -29,7 +31,7 @@ You can choose to allow members to create and manage user accounts, or your ente - [通过 {% data variables.product.product_location %} 进行身份验证](#authentication-through-githubcom) - [通过具有附加 SAML 访问限制的 {% data variables.product.product_location %} 进行身份验证](#authentication-through-githubcom-with-additional-saml-access-restriction) -- [使用 {% data variables.product.prodname_emus %} 和 SAML SSO 进行身份验证](#authentication-with-enterprise-managed-users-and-saml-sso) +- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation) ### 通过 {% data variables.product.product_location %} 进行身份验证 @@ -41,10 +43,61 @@ You can choose to allow members to create and manage user accounts, or your ente 如果您对 {% data variables.product.product_name %} 使用独立组织，或者您不想对企业中的每个组织使用 SAML 身份验证，则可以为单个组织配置 SAML。 更多信息请参阅“[关于使用 SAML 单点登录管理身份和访问](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)”。 -### 使用 {% data variables.product.prodname_emus %} 和 SAML SSO 进行身份验证 +### Authentication with {% data variables.product.prodname_emus %} and federation 如果您需要增强控制您在 {% data variables.product.product_location %} 上的企业成员的帐户，则可以使用 {% data variables.product.prodname_emus %}。 借助 {% data variables.product.prodname_emus %}，您可以使用 IdP 在 {% data variables.product.product_location %} 上为您的企业成员配置和管理帐户。 每个成员登录到您创建的帐户，您的企业将管理该帐户。 参与 {% data variables.product.prodname_dotcom_the_website %} 的其余部分受到限制。 更多信息请参阅“[关于 {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)”。 +## Identifying the best authentication method for your enterprise + +Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows. + +To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions. + +- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users) +- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use) +- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites) +- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise) +- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators) +- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs) + +### Do you want to control the user accounts for your users? + +{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources. + +With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts. + +If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP. + +### Which identity provider does your enterprise use? + +{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. For the list of supported IdPs for each option, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" and "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)." + +You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you. + +### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites? + +To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.product.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." + +These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise. + +### Do your developers rely on collaboration outside of your enterprise? + +{% data variables.product.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers need to collaborate in repositories outside your enterprise, even private repositories, to complete their work, {% data variables.product.prodname_emus %} may not be right for your enterprise, and SAML SSO may be a better solution. + +### Does your enterprise rely on outside collaborators? + +With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." + +With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.product.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. + +### Can your enterprise tolerate migration costs? + +If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt. + +If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." + +Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you. + {% elsif ghes %} 站点管理员可以决定人员如何进行身份验证以访问 {% data variables.product.product_name %} 实例。 您可以使用 {% data variables.product.product_name %} 的内置身份验证，或者，如果要集中管理团队使用的 Web 应用程序的身份和访问，则可以配置外部身份验证方法。 @@ -76,20 +129,6 @@ You can choose to allow members to create and manage user accounts, or your ente {% endif %} -## 关于访问控制 - -{% ifversion ghec or ghae %}企业成员{% elsif ghes %}有权访问 {% data variables.product.product_location %} 的人员{% endif %}可以使用组织成员身份、团队和角色来管理对实例上的 {% ifversion ghec %}企业资源{% elsif ghae %}企业{% elsif ghes %}资源{% endif %} 的访问权限。 更多信息请参阅以下文章。 - -{%- ifversion ghec %} -- “[邀请用户加入您的组织](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)” -{%- elsif ghes or ghae %} -- “[向组织添加人员](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)” -{%- endif %} -- "[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)" -- "[关于团队](/organizations/organizing-members-into-teams/about-teams)" -- "[组织的仓库角色](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)" -- "[用户帐户仓库的权限级别](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository)" - ## 延伸阅读 - "[{% data variables.product.company_short %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)" diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index f00deb29b5..187a28d564 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -2,7 +2,6 @@ title: About Enterprise Managed Users shortTitle: About managed users intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' -product: '{% data reusables.gated-features.emus %}' redirect_from: - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users @@ -21,11 +20,11 @@ topics: ## About {% data variables.product.prodname_emus %} -With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML{% if oidc-for-emu %} or OIDC{% endif %} single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP. In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." +Organization membership can be managed manually, or you can update membership automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." {% if oidc-for-emu %} @@ -33,7 +32,7 @@ Organization membership can be managed manually or updated automatically as {% d {% endif %} -You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. +You can grant {% data variables.product.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." @@ -43,6 +42,11 @@ Enterprise owners can audit all of the {% data variables.product.prodname_manage To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." +{% note %} + +**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." + +{% endnote %} ## Identity provider support @@ -62,6 +66,8 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. +* {% data variables.product.prodname_managed_users %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. +* Outside collaborators are not supported by {% data variables.product.prodname_emus %}. * {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. @@ -70,6 +76,7 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e * {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. * Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. * {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* {% data reusables.enterprise-accounts.emu-forks %} * Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. * {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. For more information, see "[About {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)." diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index c419d4dd1d..071e18b27f 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -1,7 +1,7 @@ --- -title: About SAML for enterprise IAM -shortTitle: About SAML for IAM -intro: 'You can use SAML single sign-on (SSO) {% ifversion ghec or ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.product.product_location %}{% elsif ghae %}to {% data variables.product.product_location %}{% endif %}.' +title: 关于企业 IAM 的 SAML +shortTitle: 关于 IAM 的 SAML +intro: '您可以使用 SAML 单点登录 (SSO) {% ifversion ghae %}和跨域身份管理系统 (SCIM) {% endif %}集中管理 {% ifversion ghec %}对企业在 {% data variables.product.prodname_dotcom_the_website %} 上拥有的组织{% elsif ghes %}对 {% data variables.product.product_location %}{% elsif ghae %}对 {% data variables.product.product_location %}{% endif %} 的访问。' versions: ghec: '*' ghes: '*' @@ -24,41 +24,37 @@ redirect_from: - /admin/identity-and-access-management/using-saml-for-enterprise-iam/about-identity-and-access-management-for-your-enterprise --- -## About SAML SSO for {% ifversion ghec or ghae %}your enterprise on {% endif %}{% ifversion ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} +## 关于 {% ifversion ghec or ghae %} {% endif %}{% ifversion ghec or ghes %}{% data variables.product.product_location %}{% elsif ghae %}{% data variables.product.product_name %}{% endif %} 上企业的 SAML SSO {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." +If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} -If your enterprise members manage their own personal accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. Alternatively, you can provision and manage the accounts of your enterprise members on {% data variables.product.product_location %} by using an enterprise account with {% data variables.product.prodname_emus %} enabled. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-cloud)." +{% data reusables.saml.about-saml-enterprise-accounts %} 更多信息请参阅“[配置企业的 SAML 单点登录](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)”。 -{% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." +Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." -After you enable SAML SSO, depending on the IdP you use, you may be able to enable additional identity and access management features. +{% data reusables.enterprise-accounts.about-recovery-codes %} 更多信息请参阅“[管理企业的恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)”。 -If you use Azure AD as your IDP, you can use team synchronization to manage team membership within each organization. {% data reusables.identity-and-permissions.about-team-sync %} For more information, see "[Managing team synchronization for organizations in your enterprise account](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)." +启用 SAML SSO 后，根据使用的 IDP，您可能能够启用额外的身份和访问管理功能。 -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." - -## About {% data variables.product.prodname_emus %} - -{% data reusables.enterprise-accounts.emu-short-summary %} +如果使用 Azure AD 作为 IDP，您可以使用团队同步来管理每个组织中的团队成员身份。 {% data reusables.identity-and-permissions.about-team-sync %} 更多信息请参阅“[管理企业帐户中组织的团队同步](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)”。 {% note %} -**Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}. +**注意：** 除非为企业启用了 {% data variables.product.prodname_emus %}，否则无法在企业级别使用 SCIM。 {% endnote %} -Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." +{% data reusables.saml.switching-from-org-to-enterprise %} 更多信息请参阅“[将 SAML 配置从组织切换到企业帐户](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)”。 {% elsif ghes %} -SAML SSO allows people to authenticate and access {% data variables.product.product_location %} through an external system for identity management. +SAML SSO 允许人们通过外部系统验证和访问 {% data variables.product.product_location %} 以进行身份管理。 -SAML is an XML-based standard for authentication and authorization. When you configure SAML for {% data variables.product.product_location %}, the external system for authentication is called an identity provider (IdP). Your instance acts as a SAML service provider (SP). For more information about the SAML standard, see [Security Assertion Markup Language](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language) on Wikipedia. +SAML 是一种基于 XML 的身份验证和授权标准。 为 {% data variables.product.product_location %} 配置 SAML 时，用于身份验证的外部系统称为身份提供程序 (IdP)。 您的实例充当 SAML 服务提供商 (SP)。 有关 SAML 标准的更多信息，请参阅维基百科上的[安全断言标记语言](https://en.wikipedia.org/wiki/Security_Assertion_Markup_Language)。 -For more information about the configuration of SAML SSO on {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)." +有关 {% data variables.product.product_name %} 上 SAML SSO 配置的详细信息，请参阅“[为企业配置 SAML 单点登录](/admin/identity-and-access-management/using-saml-for-enterprise-iam/configuring-saml-single-sign-on-for-your-enterprise)”。 {% data reusables.saml.saml-ghes-account-revocation %} @@ -70,28 +66,28 @@ For more information about the configuration of SAML SSO on {% data variables.pr {% data reusables.saml.ae-uses-saml-sso %} {% data reusables.saml.ae-enable-saml-sso-during-bootstrapping %} -After you configure the application for {% data variables.product.product_name %} on your identity provider (IdP), you can provision access to {% data variables.product.product_location %} by assigning the application to users and groups on your IdP. For more information about SAML SSO for {% data variables.product.product_name %}, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)." +在身份提供程序 (IdP) 上为 {% data variables.product.product_name %} 配置应用程序后，可以通过将应用程序分配到 IdP 上的用户和组来预配其访问 {% data variables.product.product_location %} 的权限。 有关用于 {% data variables.product.product_name %} 的 SAML SSO 的详细信息，请参阅“[为企业配置 SAML 单点登录](/admin/authentication/configuring-saml-single-sign-on-for-your-enterprise)”。 -{% data reusables.scim.after-you-configure-saml %} For more information, see "[Configuring user provisioning for your enterprise](/admin/authentication/configuring-user-provisioning-for-your-enterprise)." +{% data reusables.scim.after-you-configure-saml %} 更多信息请参阅“[配置企业的用户预配](/admin/authentication/configuring-user-provisioning-for-your-enterprise)”。 -To learn how to configure both authentication and user provisioning for {% data variables.product.product_location %} with your specific IdP, see "[Configuring authentication and provisioning with your identity provider](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)." +要了解如何合适特定 IdP 为 {% data variables.product.product_location %} 配置身份验证和用户预配，请参阅“[使用身份提供程序配置身份验证和预配](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider)”。 {% endif %} -## Supported IdPs +## 支持的 IdP {% ifversion ghec %} -We test and officially support the following IdPs. For SAML SSO, we offer limited support for all identity providers that implement the SAML 2.0 standard. For more information, see the [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website. +我们测试并正式支持以下 IdP。 对于 SAML SSO，我们向执行 SAML 2.0 标准的所有身份提供程序提供有限的支持。 更多信息请参阅 OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security)。 -IdP | SAML | Team synchronization | ---- | :--: | :-------: | -Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | -Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} | -Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | | -OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | -PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | -Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | +| IdP | SAML | 团队同步 | +| -------------------------------------------- |:--------------------------------------------------------------:|:-------------------------------------------------------------:| +| Active Directory Federation Services (AD FS) | {% octicon "check-circle-fill" aria-label= "The check icon" %} | | +| Azure Active Directory (Azure AD) | {% octicon "check-circle-fill" aria-label="The check icon" %} | {% octicon "check-circle-fill" aria-label="The check icon" %} +| Okta | {% octicon "check-circle-fill" aria-label="The check icon" %} | | +| OneLogin | {% octicon "check-circle-fill" aria-label="The check icon" %} | | +| PingOne | {% octicon "check-circle-fill" aria-label="The check icon" %} | | +| Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% elsif ghes %} @@ -99,7 +95,7 @@ Shibboleth | {% octicon "check-circle-fill" aria-label="The check icon" %} | | {% ifversion ghes > 3.3 %} -If your IdP supports encrypted assertions, you can configure encrypted assertions on {% data variables.product.product_name %} for increased security during the authentication process. +如果您的 IdP 支持加密断言，您可以在 {% data variables.product.product_name %} 上配置加密断言，以提高身份验证过程中的安全性。 {% endif %} @@ -107,7 +103,7 @@ If your IdP supports encrypted assertions, you can configure encrypted assertion {% elsif ghae %} -The following IdPs are officially supported for integration with {% data variables.product.prodname_ghe_managed %}. +正式支持以下 IdP 与 {% data variables.product.prodname_ghe_managed %} 集成。 {% data reusables.saml.okta-ae-sso-beta %} @@ -117,14 +113,14 @@ The following IdPs are officially supported for integration with {% data variabl {% ifversion ghae %} -## Mapping {% data variables.product.prodname_ghe_managed %} teams to Okta groups +## 将 {% data variables.product.prodname_ghe_managed %} 团队映射到 Okta 组 -If you use Okta as your IdP, you can map your Okta groups to teams on {% data variables.product.product_name %}. For more information, see "[Mapping Okta groups to teams](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)." +如果您使用 Okta 作为您的 IdP，则可以将 Okta 组映射到 {% data variables.product.product_name %} 上的团队。 更多信息请参阅“[将 Okta 组映射到团队](/admin/authentication/configuring-authentication-and-provisioning-with-your-identity-provider/mapping-okta-groups-to-teams)”。 {% endif %} -## Further reading +## 延伸阅读 -- [SAML Wiki](https://wiki.oasis-open.org/security) on the OASIS website -- [System for Cross-domain Identity Management: Protocol (RFC 7644)](https://tools.ietf.org/html/rfc7644) on the IETF website{% ifversion ghae %} -- [Restricting network traffic to your enterprise](/admin/configuration/restricting-network-traffic-to-your-enterprise){% endif %} +- OASIS 网站上的 [SAML Wiki](https://wiki.oasis-open.org/security) +- IETF 网站上的[跨域身份管理系统：协议 (RFC 7644)](https://tools.ietf.org/html/rfc7644){% ifversion ghae %} +- “[限制到企业的网络流量](/admin/configuration/restricting-network-traffic-to-your-enterprise)”{% endif %} diff --git a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 87b9c48809..4e0ac3e351 100644 --- a/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/zh-CN/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -168,7 +168,7 @@ shortTitle: 写入列表说明 ### 学习所需的技能 - GitHub Learning Lab 可以帮助您学习如何使用 GitHub、如何使用 Markdown 更有效地沟通以及如何处理合并冲突等。 + GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. - 仅大写专有名词。 diff --git a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 2e4556f542..542fe27d59 100644 --- a/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/zh-CN/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -143,7 +143,7 @@ redirect_from: ## 后续步骤 -- 在创建作业和学生组成团队后，团队成员可以使用 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://lab.github.com/githubtraining/managing-merge-conflicts)课程。 +- 在创建作业和学生组成团队后，团队成员可以使用 Git 和 {% data variables.product.product_name %} 的功能开始处理作业。 学生可以克隆仓库、推送提交、管理分支、创建和审查拉取请求、解决合并冲突以及讨论议题的更改。 您和团队都可以审查仓库的提交历史记录。 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 %}. - 当团队完成作业时，您可以查看仓库中的文件，或者查看仓库的历史和可视化内容，以更好地了解团队如何协作。 更多信息请参阅“[使用图表可视化仓库](/github/visualizing-repository-data-with-graphs)”。 diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md index ff28a4e2b3..4634a07ea9 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-ae.md @@ -77,7 +77,7 @@ Your enterprise members can learn more about Git and {% data variables.product.p 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)." ### 2. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab-enterprise %} +{% data reusables.getting-started.learning-enterprise %} ### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 7935a24b28..6c03319974 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -206,7 +206,7 @@ Members of your organization or enterprise can use GitHub's learning and support You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." ### 2. Learning with {% data variables.product.prodname_learning %} -Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." ### 3. Supporting the open source community diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 6f0bdccad1..6d3d965498 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -120,7 +120,7 @@ Your enterprise members can learn more about Git and {% data variables.product.p 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)." ### 2. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab-enterprise %} +{% data reusables.getting-started.learning-enterprise %} ### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md index 9a128d919c..d86dfcde06 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-github-team.md @@ -87,7 +87,7 @@ You can help to make your organization more secure by recommending or requiring You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." ### 4. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab %} +{% data reusables.getting-started.learning %} ### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} diff --git a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md index 2e0c446eb0..82e83fdb37 100644 --- a/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/zh-CN/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -81,7 +81,7 @@ For more information about how to authenticate to {% data variables.product.prod ### 4. Writing on {% data variables.product.product_name %} To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/about-writing-and-formatting-on-github)." -You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}. +You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}. ### 5. Searching on {% data variables.product.product_name %} Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." @@ -187,7 +187,7 @@ For more information, see "[Securing your software supply chain](/code-security/ {% data reusables.docs.you-can-read-docs-for-your-product %} ### 4. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab %} +{% data reusables.getting-started.learning %} {% ifversion fpt or ghec %} ### 5. Supporting the open source community diff --git a/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md index 8f3eeaf8ae..729d06ee46 100644 --- a/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md +++ b/translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md @@ -25,7 +25,7 @@ topics: 本教程使用 [Spoon-Knife 项目](https://github.com/octocat/Spoon-Knife)，这是一个托管在 {% data variables.product.prodname_dotcom_the_website %} 上的测试存储库，可让您测试复刻和拉取请求工作流程。 1. 导航到 `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife。 -2. 单击 **Fork（复刻）**。 ![复刻按钮](/assets/images/help/repository/fork_button.jpg) +2. 单击 **Fork（复刻）**。 ![复刻按钮](/assets/images/help/repository/fork_button.png) 1. {% data variables.product.product_name %} 将带您进入 Spoon-Knife 存储库的副本（您的复刻）。 ## 克隆复刻 diff --git a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md index 36c11ca399..f62bf434cc 100644 --- a/translations/zh-CN/content/get-started/quickstart/create-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/create-a-repo.md @@ -34,7 +34,7 @@ topics: {% note %} -**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +**注：**您可以为开源项目创建公共仓库。 创建公共仓库时，请确保包含[许可文件](https://choosealicense.com/)以确定您希望与其他人共享项目。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endnote %} diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md index f7c977ee28..8e5bc8e3d1 100644 --- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md @@ -42,7 +42,7 @@ topics: 从其他人的项目复刻创建公共仓库时，请确保包含许可文件以确定您希望与其他人共享项目。 更多信息请参阅 choosealicense.com 上的“[选择开源许可](https://choosealicense.com/)”。 -{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endif %} @@ -57,7 +57,7 @@ topics: 您可能为了对上游或原始仓库提议更改而复刻项目。 在这种情况下，最好定期将您的复刻与上游仓库同步。 为此，您需要在命令行上使用 Git。 您可以使用刚才复刻的 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 仓库练习设置上游仓库。 1. 在 {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %} 上，导航到 [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) 存储库。 -2. 在页面的右上角，单击 **Fork（复刻）**。 ![复刻按钮](/assets/images/help/repository/fork_button.jpg) +2. 在页面的右上角，单击 **Fork（复刻）**。 ![复刻按钮](/assets/images/help/repository/fork_button.png) {% endwebui %} diff --git a/translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md index 46c2fb3372..7979e5918b 100644 --- a/translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md @@ -44,7 +44,7 @@ Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides ch ### Free courses -{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://lab.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); courses on programming languages and tools such as HTML, Python, and NodeJS; and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. +{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://skills.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github); and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. ### {% data variables.product.prodname_dotcom %}'s web-based educational programs diff --git a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index 4b7a34481c..3706a82633 100644 --- a/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -134,7 +134,7 @@ git commit | ------------------ | ---------------------------------------------------------------------- | | 在同一个分支上的 `.md` 文件中 | `/assets/images/electrocat.png` | | 在另一个分支的 `.md` 文件中 | `/../main/assets/images/electrocat.png` | -| 在仓库的议题、拉取请求和评论中 | `../blob/main/assets/images/electrocat.png` | +| 在仓库的议题、拉取请求和评论中 | `../blob/main/assets/images/electrocat.png?raw=true` | | 在另一个仓库的 `.md` 文件中 | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | | 在另一个仓库的议题、拉取请求和评论中 | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/closing-an-issue.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/closing-an-issue.md new file mode 100644 index 0000000000..dade651f34 --- /dev/null +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/closing-an-issue.md @@ -0,0 +1,30 @@ +--- +title: Closing an issue +intro: 'You can close an issue when bugs are fixed, feedback is acted on, or to show that work is not planned.' +permissions: 'Anyone can close an issue they opened.

Repository owners, collaborators on repositories owned by a personal account, and people with triage permissions or greater on repositories owned by an organization can close issues opened by others. {% data reusables.enterprise-accounts.emu-permission-repo %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Issues + - Project management +shortTitle: 关闭议题 +--- + +{% note %} + +**Note:** You can also close issues automatically with keywords in pull requests and commit messages. 更多信息请参阅“[将拉取请求链接到议题](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword)”。 + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to close. +{%- if issue-close-reasons %} +1. Optionally, to change the reason for closing the issue, select {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to "Close issue" and click a reason. ![Screenshot showing dropdown menu containing issue close reasons](/assets/images/help/issues/close-issue-select-reason.png) +2. Click **Close issue**. ![Screenshot showing "close issue" button](/assets/images/help/issues/close-issue-with-reason.png) +{%- else %} +1. At the bottom of the page, click **Close issue**. ![Screenshot showing "close issue" button](/assets/images/help/issues/close-issue.png) +{% endif %} diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index 06a51f32d5..eeaeaa564e 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -175,7 +175,8 @@ gh pr list --search "team:octo-org/octo-team" 对于议题，您还可以使用搜索来： -- 通过关闭引用过滤链接到拉取请求的议题：`linked:pr` +- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`{% if issue-close-reasons %} +- Filter issues by the reason they were closed: `is:closed reason:complete` or `is:closed reason:"not planned"`{% endif %} 对于拉取请求，您还可以使用搜索来： - 过滤[草稿](/articles/about-pull-requests#draft-pull-requests)拉取请求：`is:draft` diff --git a/translations/zh-CN/content/issues/tracking-your-work-with-issues/index.md b/translations/zh-CN/content/issues/tracking-your-work-with-issues/index.md index fd651e710b..b5eb32fdd1 100644 --- a/translations/zh-CN/content/issues/tracking-your-work-with-issues/index.md +++ b/translations/zh-CN/content/issues/tracking-your-work-with-issues/index.md @@ -22,6 +22,7 @@ children: - /marking-issues-or-pull-requests-as-a-duplicate - /pinning-an-issue-to-your-repository - /transferring-an-issue-to-another-repository + - /closing-an-issue - /deleting-an-issue - /planning-and-tracking-work-for-your-team-or-project redirect_from: diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/index.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/index.md index 10c16d1c9d..c372b5c83e 100644 --- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/index.md +++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/index.md @@ -17,6 +17,7 @@ children: - /filtering-projects - /using-the-api-to-manage-projects - /automating-projects + - /managing-projects - /managing-the-visibility-of-your-projects - /managing-access-to-projects - /using-insights-with-projects diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-projects.md new file mode 100644 index 0000000000..131afe51b7 --- /dev/null +++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-projects.md @@ -0,0 +1,43 @@ +--- +title: Managing projects (beta) +intro: 'You can close and re-open projects, or you can permanently delete projects.' +allowTitleToDifferFromFilename: true +miniTocMaxHeadingLevel: 2 +versions: + fpt: '*' + ghec: '*' +topics: + - Projects + - Organizations +--- + +## Deleting a project + +You can delete a project to permanently remove it. + +{% data reusables.projects.project-settings %} +1. At the bottom of the page, click **Delete this project**. ![Screenshot showing project delete button](/assets/images/help/issues/delete-project-button.png) +1. Read the warnings, then type the name of your project into the text box. ![Screenshot showing project delete confirmation](/assets/images/help/issues/project-delete-confirm.png) +1. Click **I understand the consequences, delete this project**. + +## Closing a project + +You can close a project to remove it from the list of projects but retain the contents and ability to re-open the project later. + +{% data reusables.projects.project-settings %} +1. At the bottom of the page, click **Close this project**. ![Screenshot showing project close button](/assets/images/help/issues/close-project-button.png) + +## Re-opening an organization project + +You can reopen a previously closed project. + +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.projects.reopen-a-project %} + +## Re-opening a user project + +You can reopen a previously closed project. + +{% data reusables.profile.access_profile %} +{% data reusables.projects.reopen-a-project %} diff --git a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index f3ab05dbfa..0971b23086 100644 --- a/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/zh-CN/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -42,6 +42,12 @@ SSH 证书是一种机制：一个 SSH 密钥对另一个 SSH 密钥签名。 在颁发每个证书时，必须包含扩展，以指定证书用于哪个 {% data variables.product.product_name %} 用户。 例如，您可以使用 OpenSSH 的 `ssh-keygen` 命令，将 _KEY-IDENTITY_ 替换为密钥标识，_USERNAME_ 替换为 {% data variables.product.product_name %} 用户名： 您生成的证书将授权代表该用户使用您组织的任何资源。 在签发证书之前，请确保验证用户的身份。 +{% note %} + +**Note:** You must update to OpenSSH 7.6 or later to use these commands. + +{% endnote %} + ```shell $ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub ``` diff --git a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md index f5b9453f58..5d0a1ff8c7 100644 --- a/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/zh-CN/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -137,5 +137,5 @@ When a {% data variables.product.prodname_pages %} site is visited, the visitor' ## Further reading -- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} +- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md index e54bc6bf8d..9c44f4e187 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md @@ -23,7 +23,7 @@ shortTitle: 协作开发 {% tip %} -**提示：** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %} +**提示：** {% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning %} {% endtip %} diff --git a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 6ddd17e18a..0c1e55af1f 100644 --- a/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -72,6 +72,18 @@ shortTitle: 搜索议题和 PR | `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) 匹配含有 "performance" 字样的开放议题。 | | `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) 匹配含有 "android" 字样的已关闭议题和拉取请求。 | +{% if issue-close-reasons %} +## Search by the reason an issue was closed + +You can filter issues based on the reason given when the issue was closed, using the `reason` qualifier. + +| 限定符 | 示例 | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `reason:complete` | [**libraries is:closed reason:complete**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) matches issues with the word "libraries" that were closed as "completed." | +| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) matches issues with the word "libraries" that were closed as "not planned." | + +{% endif %} + ## 按仓库可见性过滤 您可以使用 `is` 限定符，按包含议题和拉取请求的仓库的可见性进行过滤。 更多信息请参阅“[关于仓库](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)”。 @@ -144,10 +156,10 @@ shortTitle: 搜索议题和 PR 您可以使用 `label` 限定符按标签缩小结果范围。 由于议题可有多个标签，因此您可为每个议题列出单独的限定符。 -| 限定符 | 示例 | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) 匹配标签为 "help wanted"、位于 Ruby 仓库中的议题。 | -| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) 匹配正文中含有 "broken" 字样、没有 "bug" 标签但*有* "priority" 标签的议题。 | +| 限定符 | 示例 | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." | | | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) 匹配含有 "bug" 和 "resolved" 标签的议题。{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | | [**label:bug label:resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) 匹配含有 "bug" 或 "resolved" 标签的议题。{% endif %} @@ -155,82 +167,82 @@ shortTitle: 搜索议题和 PR `milestone` 限定符查找作为仓库内[里程碑](/articles/about-milestones)组成部分的议题或拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) 匹配位于名为 "overhaul" 的里程碑中的议题。 | -| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) 匹配位于名为 "bug fix" 的里程碑中的议题。 | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." | ## 按项目板搜索 您可以使用 `project` 限定符查找与仓库或组织中特定[项目板](/articles/about-project-boards/)关联的议题。 必须按项目板编号搜索项目板。 您可在项目板 URL 的末尾找到项目板编号。 -| 限定符 | 示例 | -| -------------------------- | --------------------------------------------------------------------- | -| project:PROJECT_BOARD | **project:github/57** 匹配 GitHub 拥有的、与组织项目板 57 关联的议题。 | -| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** 匹配与 @github 的 linguist 仓库中的项目板 1 关联的议题。 | +| 限定符 | 示例 | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. | ## 按提交状态搜索 您可以基于提交的状态过滤拉取请求。 这在使用 [Status API](/rest/reference/commits#commit-statuses) 或 CI 服务时特别有用。 -| 限定符 | 示例 | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) 匹配在状态为待定的 Go 仓库中打开的拉取请求。 | -| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) 匹配正文中含有 "finally" 字样、具有成功状态的打开拉取请求。 | -| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) 匹配在 2015 年 5 月打开、具有失败状态的拉取请求。 | +| 限定符 | 示例 | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. | ## 按提交 SHA 搜索 如果您知道提交的特定 SHA 哈希，您可以使用它来搜索包含该 SHA 的拉取请求。 SHA 语法必须至少 7 个字符。 -| 限定符 | 示例 | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) 匹配具有开头为 `e1109ab` 的提交 SHA 的拉取请求。 | -| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) 匹配具有开头为 `0eff326d6213c` 的提交 SHA 的合并拉取请求。 | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. | ## 按分支名称搜索 您可以基于拉取请求来自的分支（"head" 分支）或其合并到的分支（"base" 分支）来过滤拉取请求。 -| 限定符 | 示例 | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) 匹配从名称以 "change" 字样开头的已关闭分支打开的拉取请求。 | -| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) 匹配合并到 `gh-pages` 分支中的拉取请求。 | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. | ## 按语言搜索 通过 `language` 限定符，您可以搜索以特定语言编写的仓库内的议题和拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) 匹配 Ruby 仓库中的开放议题。 | +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. | ## 按评论数量搜索 您可以使用 `comments` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)以按评论数量搜索。 -| 限定符 | 示例 | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) 匹配具有超过 100 条评论的已关闭议题。 | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) 匹配具有 500 到 1,000 条评论的议题。 | +| 限定符 | 示例 | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | ## 按交互数量搜索 您可以使用 `interactions` 限定符以及[大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按交互数量过滤议题和拉取请求。 交互数量是对议题或拉取请求的反应和评论数量。 -| 限定符 | 示例 | -| -------------------------- | ----------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) 匹配 500 至 1,000 个交互的拉取请求或议题。 | +| 限定符 | 示例 | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) 匹配超过 2000 个交互的拉取请求或议题。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. | ## 按反应数量搜索 您可以使用 `reactions` 限定符以及 [大于、小于和范围限定符](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax)按反应数量过滤议题和拉取请求。 -| 限定符 | 示例 | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------ | -| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) 匹配 500 至 1000 个反应的议题。 | +| 限定符 | 示例 | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | +| reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) 匹配超过 1000 个反应的议题。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. | ## 搜索草稿拉取请求 您可以过滤草稿拉取请求。 更多信息请参阅“[关于拉取请求](/articles/about-pull-requests#draft-pull-requests)”。 diff --git a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md index b3717caa63..2d31dfa64c 100644 --- a/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md +++ b/translations/zh-CN/content/site-policy/privacy-policies/github-privacy-statement.md @@ -86,157 +86,157 @@ topics: 如果您在我们这里拥有付费帐户，或者使用我们的服务进行购买或销售，我们会自动收集有关您在服务上的交易的某些信息，例如您的全名、地址、地区、州、国家、邮政编码、日期、时间和收费金额。 #### 使用信息 -If you're accessing or using our Service, we may automatically collect information about how you use the Service, such as the pages you view, the referring site, your IP address and information about your device, session information, the date and time of each request, information contained in or relating to your contributions to individual repositories, and telemetry data (i.e., information about how a specific feature or service is performing) regarding your use of other features and functionality of the Service. +如果您访问或使用我们的服务，我们可能会自动收集有关您如何使用服务的信息，例如您查看的页面、进站前链接点、您的 IP 地址和有关您设备的信息、会话信息、每个请求的日期和时间、包含在您对各个存储库的贡献中或与之相关的信息，以及有关您使用服务的其他特性和功能的遥测数据（即有关特定功能或服务如何执行的信息）。 #### Cookie -As further described below, we automatically collect information from cookies (such as cookie ID and settings) in connection with our Service. +如下所述，我们会自动从与我们的服务相关的 Cookie 中收集信息（例如 Cookie ID 和设置）。 #### 设备信息 -We may collect information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. +我们可能会收集有关您设备的信息，例如其 IP 地址、浏览器或客户端应用程序信息、语言首选项、操作系统和应用程序版本、设备类型和 ID 以及设备型号和制造商。 -#### Geolocation information -In connection with certain features and depending on the functionality of the Service, we collect geolocation information such as through IP addresses or the location information you choose to provide in your Account profile. +#### 地理位置信息 +对于某些功能，并根据服务的功能，我们收集地理位置信息，例如通过 IP 地址或您选择在您的帐户配置文件中提供的位置信息。 -### Information we create or generate -We infer new information from other data we collect, including using automated means to generate information about your likely preferences or other characteristics (“inferences”). For example, we infer your general geographic location (such as city, state, and country) based on your IP address. +### 我们创建或生成的信息 +我们从收集的其他数据中推断出新信息，包括使用自动方式生成有关您可能的偏好或其他特征的信息（“推断”）。 例如，我们会根据您的 IP 地址推断您的一般地理位置（例如城市、州和国家/地区）。 ### 从第三方收集信息 -Other companies with whom you choose to engage. GitHub may collect Personal Data about you from third parties. 例如，如果您报名参加培训或从我们的供应商、合作伙伴或附属公司获取有关 GitHub 的信息，就可能会发生这种情况。 GitHub does not purchase Personal Data from third-party data brokers. +您选择与之合作的其他公司。 GitHub 可能会从第三方收集有关您的个人数据。 例如，如果您报名参加培训或从我们的供应商、合作伙伴或附属公司获取有关 GitHub 的信息，就可能会发生这种情况。 GitHub 不从第三方数据中间商购买个人数据。 -Service Providers. We may also receive information from processors or service providers who process the data on our behalf, such as our payment processor who process payment and billing information in connection with our Service. +服务提供商。 我们还可能从代表我们处理数据的处理者或服务提供商接收信息，例如处理与我们服务相关的付款和账单信息的支付处理者。 -Content you post on our Service. Information you store in, or contribute to, a public repository, provide for use in connection with a Community Feature or make otherwise publicly available through the Service will be collected by GitHub as described in this Privacy Statement. Such information may also be available to the GitHub user community as well as the general public. For more information, please review details regarding public repositories and community features [here](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile). +您在我们的服务上发布的内容。 GitHub 将按照本隐私声明中所述收集您存储在公共存储库中或向公共存储库提供的信息、提供用于与社区功能相关的信息或以其他方式通过服务公开提供的信息。 此类信息也可能提供给 GitHub 用户社区以及公众。 有关更多信息，请查看[此处](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile)有关公共存储库和社区功能的详细信息。 -Co-branding/marketing partners. We may receive information from partners with which we offer co-branded services or engage in joint marketing activities. +联合品牌/营销合作伙伴。 我们可能会从与我们合作提供联合品牌服务或参与联合营销活动的合作伙伴收到信息。 -Publicly available sources. We may also obtain information from publicly available sources as GitHub repositories. +公开可用的来源。 我们还可能从公开可用的来源获取信息，作为 GitHub 存储库。 -When you are asked to provide Personal Data, you may decline. And you may use web browser or operating system controls to prevent certain types of automatic data collection. But if you choose not to provide or allow information that is necessary for certain services or features, those services or features may not be available or fully functional. +当您被要求提供个人数据时，您可以拒绝。 您可以使用 Web 浏览器或操作系统控件来防止某些类型的自动数据收集。 但是，如果您选择不提供或允许某些服务或功能所需的信息，则这些服务或功能可能不可用或功能不完全可用。 ## GitHub 如何使用您的信息 -We may use your information to provide, administer, analyze, manage, and operate our Service. For example, we use your information for the following purposes: -- Provide our products and deliver our services including troubleshooting, improving, and personalizing the features on the Service. -- Business operations such as billing, accounting, improving our internal operations, securing our systems, detecting fraudulent or illegal activity, and meeting our legal obligations. -- Improve and develop our products and services including to develop new services or features, and conduct research. -- Personalization of our Service by understanding you and your preferences to enhance your experience and enjoyment using our Service. -- Provide customer support and respond to your questions. -- Deliver promotional communications with you about new services, features, offers, promotions, and other information about our Service. -- Send you information, including confirmations, invoices, technical notices, updates, security alerts, support and administrative messages. +我们可能会使用您的信息来提供、管理、分析、管理和运营我们的服务。 例如，我们将您的信息用于以下目的： +- 提供我们的产品和服务，包括故障排除、改进和个性化服务功能。 +- 业务运营，例如计费、会计、改善我们的内部运营、保护我们的系统、检测欺诈或非法活动以及履行我们的法律义务。 +- 改进和开发我们的产品和服务，包括开发新服务或功能，以及进行研究。 +- 通过了解您和您的偏好来个性化我们的服务，以增强您对我们服务的体验和享受。 +- 提供客户支持并回答您的问题。 +- 向您提供新服务、功能、优惠、促销以及有关服务的其他信息。 +- 向您发送信息，包括确认、发票、技术通知、更新、安全警报、支持和管理消息。 -We combine data we collect from different sources for these purposes and to give you a more seamless, consistent, and personalized experience. +出于这些目的，我们将从不同来源收集的数据结合起来，为您提供更加无缝、一致和个性化的体验。 ## 我们如何分享所收集的信息 -We share Personal Data with your consent or as necessary to complete your transactions or provide the services you have requested or authorized. In addition, we may share each of the categories of your Personal Data described above with the types of third parties described below for the following business purposes: +我们会在您同意的情况下或在必要时共享个人数据，以完成您的交易或提供您请求或授权的服务。 此外，出于以下商业目的，我们可能会与下述类型的第三方共享上述每个类别的个人数据： -### Public information -You may select options available through our Service to publicly display and share your name and/or username and certain other information, such as your profile, demographic data, content and files, or geolocation data. For example, if you would like your email address to remain private, even when you’re commenting on public repositories, [you can adjust your setting for your email address to be private in your user profile](https://github.com/settings/emails). You can also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). 有关提交消息中电子邮件地址的更多信息，请参阅[此处](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)。 +### 公开信息 +您可以选择通过我们的服务提供的选项，以公开显示和共享您的姓名和/或用户名以及某些其他信息，例如您的个人资料、人口统计数据、内容和文件或地理位置数据。 例如，如果您希望自己的电子邮件地址保持私密，即使您正在评论公共存储库，[也可以在用户配置文件中将电子邮件地址的设置调整为为私密](https://github.com/settings/emails)。 您还可以[更新本地 Git 配置以使用您的私密电子邮件地址](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)。 有关提交消息中电子邮件地址的更多信息，请参阅[此处](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address)。 -Please note that if you would like to compile GitHub data, you must comply with our [Terms of Service](/site-policy/github-terms/github-terms-of-service) regarding information usage and privacy, and you may only use any public-facing information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users. +请注意，如果您想编译 GitHub 数据，则必须遵守我们关于信息使用和隐私 [服务条款](/site-policy/github-terms/github-terms-of-service) ，并且您只能将您收集的任何面向公众的信息用于我们用户授权的目的。 例如，如果 GitHub 用户出于识别和归因的目的而公开电子邮件地址，请不要将该电子邮件地址用于向用户发送未经请求的电子邮件或出售个人信息（例如向招聘人员、猎头和职介所出售）或用于商业广告。 我们希望您合理地保护从 GitHub 收集的任何信息，并且必须及时回应 GitHub 或 GitHub 用户的投诉以及删除和“别碰”要求。 ### 第三方应用程序 -We share your Personal Data with third parties when you tell us to do so. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your Personal Data. 例如，如果您加入组织，则表明您愿意向组织所有者提供在组织访问日志中查看您的活动的权限。 +当您要求时，我们会与第三方共享您的个人数据。 例如，如果您购买我们 Marketplace 上列出的应用程序，我们将分享您的用户名以便该应用程序开发者为您提供服务。 此外，您可以通过在 GitHub 上的操作来指示我们分享您的个人信息。 例如，如果您加入组织，则表明您愿意向组织所有者提供在组织访问日志中查看您的活动的权限。 -You can enable or add third-party applications, known as "Developer Products" to your Account. 这些开发者产品并非使用 GitHub 的必要条件。 We will share your Personal Data with such third-party applications when you ask us to; however, you are responsible for your use of the third-party Developer Product and for the amount of Personal Data you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile. +您可以启用或添加第三方应用程序（称为“开发人员产品”）到您的帐户。 这些开发者产品并非使用 GitHub 的必要条件。 当您要求我们时，我们将与此类第三方应用程序共享您的个人数据；但是，您应对您对第三方开发者产品的使用以及您选择与其共享的个人数据量负责。 您可以查看我们的 [API 文档](/rest/reference/users)，以了解您使用自己的 GitHub 个人资料向开发者产品验证时会提供哪些信息。 -### Organizations with which you engage -You may indicate, through your actions on GitHub, that you are willing to share your Personal Data. If you collaborate on or become a member of an organization, then its Account owners may receive your Personal Data. When you accept an invitation to an organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Please contact the Account owners for more information about how they might process your Personal Data in their Organization and the ways for you to access, update, alter, or delete your Personal Data stored in the Account. +### 您参与的组织 +您可以通过在 GitHub 上的操作来表明您愿意分享自己的个人数据。 如果您与组织协作或成为组织成员，则其帐户所有者可能会收到您的个人数据。 当您接受组织邀请时，您将被告知所有者可以看到的信息类型（更多信息请参阅[关于组织成员](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)）。 请联系帐户所有者，详细了解他们在组织中如何处理您的个人数据，以及您访问、更新、更改或删除存储在该帐户中的个人数据的方式。 ### 服务提供商 -We share your Personal Data with service providers who process the information on our behalf to provide or improve our Service. For example, our service providers may perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all Personal Data in the United States, our service providers may process data outside of the United States or the European Union. Such processing by service providers will be in compliance with applicable law including any relevant transfer mechanism. +我们与代表我们处理信息的服务提供商共享您的个人数据，以提供或改进我们的服务。 例如，我们的服务提供商履行付款处理、客户支持事件单、网络数据传输、安全及其他类似服务。 虽然 GitHub 在美国处理所有个人数据，但我们的服务提供商可能在美国或欧盟外部处理数据。 服务提供商的此类处理将遵守适用法律，包括任何相关的传输机制。 - ### Affiliates We enable access to Personal Data across our subsidiaries, affiliates, and related companies, for example, where we share common data systems or where access is needed to operate and provide the Service. + ### 关联公司 我们允许跨子公司、关联公司和相关公司访问个人数据，例如，我们共享通用数据系统或需要访问权限来运营和提供服务。 ### 出于安全目的 -We will disclose Personal Data if we believe it is necessary to: -- protect our customers and others, for example to prevent spam or attempts to commit fraud, or to help prevent the loss of life or serious injury of anyone; -- operate and maintain the security of the Service, including to prevent or stop an attack on our systems or networks; or -- protect the rights or property or ourselves or others, including enforcing our agreements, terms, and policies. +如果我们认为是实现以下目的所必需，将公布个人数据： +- 保护我们的客户和其他人，例如防止垃圾邮件或欺诈企图，或帮助防止任何人的生命损失或严重伤害； +- 运营和维护服务的安全性，包括防止或阻止对我们系统或网络的攻击；或 +- 保护权利或财产或我们自己或他人，包括执行我们的协议、条款和政策。 ### 法律要求披露 -GitHub may disclose Personal Data or other information we collect about you to law enforcement or other governmental agencies if required in response to a valid legal process. For more information about our disclosure in response to legal requests, see our [Guidelines for Legal Requests of User Data](/github/site-policy/guidelines-for-legal-requests-of-user-data). +GitHub 可能会向执法部门或其他政府机构披露我们收集的有关您的个人数据或其他信息，以响应有效的法律程序。 有关我们为响应法律要求而披露的更多信息，请参阅我们的[用户数据法律要求指南](/github/site-policy/guidelines-for-legal-requests-of-user-data)。 ### 控制权变更或出售 -We may share your Personal Data if we are involved in a merger, sale, or acquisition of corporate entities or business units as described in this Privacy Statement. +如果我们参与本隐私声明中所述的公司实体或业务部门的合并、出售或收购，我们可能会共享您的个人数据。 -Please note that some of the features on our Service include integrations, references, or links to services provided by third parties whose privacy practices differ from ours. If you provide Personal Data to any of those third parties, or allow us to share Personal Data with them, that data is governed by their privacy statements. +请注意，我们服务的某些功能包括集成、引用或指向隐私惯例与我们不同的第三方提供的服务的链接。 如果您向任何这些第三方提供个人数据，或允许我们与他们共享个人数据，则该数据受其隐私声明的约束。 -Finally, we may share de-identified information in accordance with applicable law. +最后，我们可能会根据适用法律共享去识别化的信息。 -### No Selling of Personal Data -We *do not* sell your Personal Data for monetary or other consideration as defined under California and Nevada state laws. You can learn more about the CCPA and how we comply with it [here](#githubs-notice-to-california-residents). +### 不出售个人数据 +我们*不会*出于加利福尼亚州和内华达州法律定义的金钱或其他考虑而出售您的个人数据。 您可以在[此处](#githubs-notice-to-california-residents)了解有关 CCPA 以及我们如何遵守它的更多信息。 ## 您对我们处理您的个人数据的选择 -We provide choices about the Personal Data we collect about you. The choices you make will not apply to any Personal Data associated with an Organization under your Account. +我们提供有关我们收集的有关您的个人数据的选择。 您所做的选择将不适用于与您帐户下的组织相关的任何个人数据。 -Access, correction, and deletion. If you're a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). 您可以在个人资料中限制信息、保持更新个人信息或者联系 [GitHub 支持](https://support.github.com/contact)或 [GitHub 高级支持](https://enterprise.githubsupport.com/hc/en-us)，以控制我们收集的信息。 +访问、更正和删除。 如果您是 GitHub 用户，则可以通过[编辑用户个人资料](https://github.com/settings/profile)或联系 [GitHub 支持](https://support.github.com/contact)或 [GitHub 高级支持](https://enterprise.githubsupport.com/hc/en-us)，访问、更新、更改或删除您的基本用户个人资料信息。 您可以在个人资料中限制信息、保持更新个人信息或者联系 [GitHub 支持](https://support.github.com/contact)或 [GitHub 高级支持](https://enterprise.githubsupport.com/hc/en-us)，以控制我们收集的信息。 -We retain and use your information as described in this Privacy Statement, but barring legal requirements, we will delete your full profile within 90 days of your request. 删除帐户后，某些数据，例如对其他用户仓库的贡献和对其他议题的评论，仍然保留。 However, we will delete or de-identify your Personal Data, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a ghost user. That said, the email address you have provided via your Git commit settings will always be associated with your commits in the Git system. 如果您已选择将自己的电子邮件地址设为私密，则还应更新您的 Git 提交设置。 我们无法更改或删除 Git 提交历史记录中的数据 — 虽然 Git 软件设计用于维护记录，但我们让您来控制在该记录中放入哪些信息。 +我们按照本隐私声明中所述保留和使用您的信息，但除非法律要求，否则我们将在您提出请求后的 90 天内删除您的完整个人资料。 删除帐户后，某些数据，例如对其他用户仓库的贡献和对其他议题的评论，仍然保留。 但是，我们通过将其与空用户相关联，从议题、拉取请求和评论的作者字段中删除或去识别化您的个人数据，包括您的用户名和电子邮件地址。 也就是说，您通过 Git 提交设置提供的电子邮件地址将始终与 Git 系统中的提交相关联。 如果您已选择将自己的电子邮件地址设为私密，则还应更新您的 Git 提交设置。 我们无法更改或删除 Git 提交历史记录中的数据 — 虽然 Git 软件设计用于维护记录，但我们让您来控制在该记录中放入哪些信息。 -If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). +如果 GitHub 处理除您的个人资料信息以外的个人数据，例如 GitHub 从[第三方](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties)收到的有关您的信息，则根据适用法律，您可以联系 [GitHub 支持](https://support.github.com/contact) 或 [GitHub 高级支持](https://enterprise.githubsupport.com/hc/en-us)访问、更新、更改、删除、反对或限制处理您的个人数据。 -You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as the GitHub Feed, the GitHub Globe, GitHub Explore, the GitHub Discussion Leaderboard) through [profile settings](https://github.com/settings/profile). +您可以通过[个人资料设置](https://github.com/settings/profile)来调整帐户上的设置，包括将您的个人数据显示在私人或公共存储库中，或与社区功能（例如 GitHub Feed、GitHub Globe、GitHub Explore、GitHub 讨论排行榜）相关的个人数据。 -Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement. +此外，如果您无法通过上述方式访问我们拥有的某些个人数据，您可以按照本隐私声明底部所述与我们联系以请求访问。 ### 数据可移植性 作为 GitHub 用户，您可以随时带走您的数据。 例如，您可以[将您的仓库克隆到桌面](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop)，也可以使用我们的[数据移植工具](https://developer.github.com/changes/2018-05-24-user-migration-api/)下载我们拥有的与您相关的信息。 ### 沟通偏好 -We use your email address to communicate with you, if you've said that's okay, and only for the reasons you’ve said that’s okay. 例如，如果您向我们的支持团队提出请求，我们将通过电子邮件答复您。 You have control over how your email address is used and shared on and through our Service. You may manage your communication preferences in your [profile](https://github.com/settings/emails). +我们使用您的电子邮件地址与您通信，但需要征得您的同意，并且以您的同意为前提。 例如，如果您向我们的支持团队提出请求，我们将通过电子邮件答复您。 您可以控制如何在我们的服务上和通过我们的服务使用和共享您的电子邮件地址。 您可以在[个人资料](https://github.com/settings/emails)中管理您的通信首选项。 -根据设计，Git 版本控制系统将许多操作与用户的电子邮件地址相关联，例如提交消息。 See more details regarding [setting your commit email address](https://github.com/settings/emails). +根据设计，Git 版本控制系统将许多操作与用户的电子邮件地址相关联，例如提交消息。 请参阅有关[设置提交电子邮件地址](https://github.com/settings/emails)的更多详细信息。 -Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails, for example, about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We may also send marketing emails, based on your choices and in accordance with applicable laws and regulations. 在我们发送的每封营销电子邮件的底部，都有一个“退订”链接。 +根据您的[电子邮件设置](https://github.com/settings/emails)，GitHub 有时可能会发送有关新动态的通知电子邮件，例如，您关注的仓库中有变动、出现新功能、有反馈请求、有重要政策变动或需要提供客户支持。 根据您的选择和适用的法律法规，我们还可能会发送营销电子邮件。 在我们发送的每封营销电子邮件的底部，都有一个“退订”链接。 请注意，您不能选择不接收我们的重要通讯，例如来自我们支持团队的电子邮件或系统电子邮件，但是您可以在个人资料中配置通知设置以选择不接收其他通讯。 -### European Data Protection Rights +### 欧洲数据保护权利 -If the processing of Personal Data about you is subject to European Union data protection law, you have certain rights with respect to that data: +如果有关您的个人数据的处理受欧盟数据保护法的约束，则您对该数据拥有某些权利： -You can request access to, and rectification or erasure of, Personal Data; If any automated processing of Personal Data is based on your consent or a contract with you, you have a right to transfer or receive a copy of the Personal Data in a usable and portable format; If the processing of Personal Data is based on your consent, you can withdraw consent at any time for future processing; You can to object to, or obtain a restriction of, the processing of Personal Data under certain circumstances; and For residents of France, you can send us specific instructions regarding the use of your data after your death. +您可以要求访问、更正或删除个人数据； 如果个人数据的任何自动处理是基于您的同意或与您的合同，您有权以可用和可移植的格式传输或接收个人数据的副本； 如果个人数据的处理是基于您的同意，您可以随时撤回同意以供将来处理； 在某些情况下，您可以反对或限制个人数据的处理； 对于法国居民，您可以在去世后向我们发送有关使用您的数据的具体说明。 -To make such requests, please use the contact information at the bottom of this statement. When we are processing data on behalf of another party (i.e., where GitHub is acting as a data processor) you should direct your request to that party. You also have the right to lodge a complaint with a supervisory authority, but we encourage you to first contact us with any questions or concerns. +要提出此类请求，请使用本声明底部的联系信息。 当我们代表另一方（即 GitHub 充当数据处理者）处理数据时，您应将您的请求定向到该方。 您也有权向监管机构提出投诉，但我们鼓励您首先与我们联系，提出任何问题或疑虑。 -We rely on different lawful bases for collecting and processing Personal Data about you, for example, with your consent and/or as necessary to provide the services you use, operate our business, meet our contractual and legal obligations, protect the security of our systems and our customers, or fulfill other legitimate interests. +我们依靠不同的法律依据来收集和处理您的个人数据，例如，在您同意和/或在必要时提供您使用的服务，运营我们的业务，履行我们的合同和法律义务，保护我们的系统和客户的安全，或履行其他合法利益。 -## Our use of cookies and tracking technologies +## 我们对 Cookie 和跟踪技术的使用 -### Cookies and tracking technologies +### Cookie 和跟踪技术 -GitHub uses cookies to provide, secure and improve our Service or to develop new features and functionality of our Service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, compile statistical reports, and provide information for future development of GitHub. We use our own cookies and do not use any third-party service providers in this context. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our Service. We provide more information about [cookies on GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) on our [GitHub Subprocessors and Cookies](/github/site-policy/github-subprocessors-and-cookies) page that describes the cookies we set, the needs we have for those cookies, and the expiration of such cookies. +GitHub 使用 Cookie 来提供、保护和改进我们的服务，或开发我们服务的新特性和功能。 例如，我们使用它们来保持您的登录状态、记住您的偏好、出于安全目的识别您的设备、编译统计报告以及为 GitHub 的未来发展提供信息。 我们使用自己的 Cookie，在这种情况下不使用任何第三方服务提供商。 如果您禁止浏览器或设备接受这些 cookie，则将无法登录或使用我们的服务。 我们在 [GitHub 子处理器和 Cookie](/github/site-policy/github-subprocessors-and-cookies) 页面上提供有关 [GitHub 上 Cookie](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) 的更多信息，其中描述了我们设置的 Cookie、我们对这些 Cookie 的需求以及此类 Cookie 的过期时间。 -Our emails to users may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email communications more effective and to make sure we are not sending you unwanted email. +我们给用户的电子邮件可能包含一个像素标签，它是一个很小的清晰图像，可以告诉我们您是否打开了电子邮件以及您的 IP 地址是什么。 我们使用此像素标签使我们的电子邮件通信对您更有效，并确保我们不会发送您不需要的电子邮件。 ### DNT “[别跟踪](https://www.eff.org/issues/do-not-track)”(DNT) 是有一种隐私首选项，如果您不希望在线服务（特别是广告网络）通过第三方跟踪服务收集和分享有关您在线活动的某类信息，您可以在浏览器中设置该选项。 GitHub 响应浏览器的 DNT 信号，并遵循[关于响应 DNT 信号的 W3C 标准](https://www.w3.org/TR/tracking-dnt/)。 如果您要设置浏览器以传达不希望被跟踪的信号，请查看浏览器的文档以了解如何启用该信号。 还有一些很适合阻止在线跟踪的应用程序，例如 [Privacy Badger](https://privacybadger.org/)。 -## Retention of Personal Data -We retain Personal Data for as long as necessary to provide the services and fulfill the transactions you have requested, comply with our legal obligations, resolve disputes, enforce our agreements, and other legitimate and lawful business purposes. Because these needs can vary for different data types in the context of different services, actual retention periods can vary significantly based on criteria such as user expectations or consent, the sensitivity of the data, the availability of automated controls that enable users to delete data, and our legal or contractual obligations. For example, we may retain your Personal Data for longer periods, where necessary, subject to applicable law, for security purposes. +## 个人数据的保留 +只要有必要，我们就会保留个人数据，以提供服务并完成您请求的交易，遵守我们的法律义务，解决争议，执行我们的协议以及其他合法和合法的商业目的。 由于在不同服务环境中，不同数据类型的这些需求可能会有所不同，因此实际保留期可能会根据用户期望或同意、数据的敏感性、使用户能够删除数据的自动控制的可用性以及我们的法律或合同义务等标准而有很大差异。 例如，出于安全目的，我们可能会在必要时根据适用法律将您的个人数据保留更长时间。 ## GitHub 如何保护您的信息 -GitHub takes reasonable measures necessary to protect your Personal Data from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of your Personal Data. To help us protect personal data, we request that you use a strong password and never share your password with anyone or use the same password with other sites or accounts. +GitHub 采取必要的合理措施来保护您的个人数据免遭未经授权的访问、更改或破坏；保持数据准确性；并帮助确保正确使用您的个人数据。 为了帮助我们保护个人数据，我们要求您使用强密码，切勿与任何人共享密码或与其他网站或帐户使用相同的密码。 -In addition, if your account has private repositories, you control the access to that Content. GitHub personnel does not access private repository content except for -- security purposes, -- automated scanning for known vulnerabilities, active malware, or other content known to violate our Terms of Service +此外，如果您的帐户具有私有仓库，则可以控制对该内容的访问。 GitHub 人员不能访问私有仓库内容，除非 +- 出于安全目的， +- 自动扫描已知漏洞、活动恶意软件或已知违反我们服务条款的其他内容 - 协助仓库所有者处理支持事项 - 保持服务的完整性 -- to comply with our legal obligations if we have reason to believe the contents are in violation of the law, -- or with your consent. +- 在我们有理由相信内容违反法律时遵守我们的法律义务， +- 或经您同意。 -Github will provide notice regarding private repository access where not prohibited by law or if in response to a security threat or other risk to security. +Github 将在法律不禁止的情况下，或者在响应安全威胁或其他安全风险的情况下，提供有关私有仓库访问的通知。 ### 跨境数据传输 -GitHub processes Personal Data both inside and outside of the United States and relies on legal mechanisms such as Standard Contractual Clauses to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. You may request a copy of the Standard Contractual Clauses using the contact details provided in the section entitled “Contacting GitHub” below. +GitHub 处理美国境内外的个人数据，并依靠标准合同条款等法律机制将数据从欧洲经济区、英国和瑞士合法传输到美国。 您可以使用下面标题为“联系 GitHub”的部分中提供的联系方式索取标准合同条款的副本。 ### 解决投诉 -If you have concerns about the way GitHub is handling your Personal Data, please let us know immediately. 我们乐于提供帮助。 您可以通过填写[隐私问题联系表](https://support.github.com/contact/privacy)联系我们。 You may also email us directly at **(privacy [at] github [dot] com)** with the subject line "Privacy Concerns." 我们将尽快回复 — 最迟不超过 45 天。 +如果您对 GitHub 处理您的个人数据的方式有疑问，请立即告诉我们。 我们乐于提供帮助。 您可以通过填写[隐私问题联系表](https://support.github.com/contact/privacy)联系我们。 您也可以直接通过 **(privacy [at] github [dot] com)** 给我们发送主题行为“隐私问题”的电子邮件。 我们将尽快回复 — 最迟不超过 45 天。 您还可以直接联系我们的数据保护官。 @@ -274,36 +274,36 @@ Cliquez ici pour obtenir la version française: [Déclaration de confidentialit 有关本声明翻译成其他语言的版本，请访问 [https://docs.github.com/](/)，然后从“English（英文）”下的下拉菜单中选择语言。 -## GitHub's notice to California residents +## GitHub 对加州居民的声明 2018 年[加州消费者隐私法案](https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375)（加州 民事 法典第 1798.100 及其后各段，修正案，“CCPA”）赋予加州居民对其个人信息的权利和控制。 GitHub, Inc. （"GitHub"、“我们”）根据 CCPA 的要求向加州居民（“您”）提供本声明，概述如何收集和处理其个人信息。 这是 GitHub 专门向加州居民介绍的在 CCPA 下的消费者隐私权。 至于我们如何将 CCPA 关于控制个人信息的核心权利扩展到美国所有用户，请参阅我们的[隐私声明](/github/site-policy/github-privacy-statement)。 -### Our handling of personal information -While the table below contains information about the categories of personal information we collect, process, and share, please see the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement) for full details. +### 我们对个人信息的处理 +虽然下表包含有关我们收集、处理和分享的个人信息类别的信息，但要了解更详细的信息还请参阅 [GitHub 隐私声明](/github/site-policy/github-privacy-statement)。 -| 过去 12 个月内收集的个人信息类别 | 个人信息收集来源的类别 | -| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 标识符（例如，真实姓名、别名、邮政地址、唯一的个人标识符、在线标识符、互联网协议地址、电子邮件地址、帐户名或其他类似的标识符） | Information consumer provides directly or automatically through their interaction with our Service and/or Website or GitHub’s vendors, partners, or affiliates | -| Personal information described in Cal. 民事 Code §1798.80 (e) such as name, address, credit card or debit card number) | Information consumer may choose to provide directly, through service providers | -| Characteristics of protected classifications under California or federal law (such as gender) | 消费者可选择直接提供的信息 | -| 商业信息（例如有关购买、获取或考虑的产品或服务的信息，或其他购买或消费历史记录或趋势的信息） | 消费者直接提供的信息，或者在与我们服务交互的过程中自动提供的信息 | -| Geolocation data (such as any information collected after giving users the opportunity to opt-in to location-based services, which rely upon a device’s precise location services. ) | Information consumer provides automatically through their interaction with our Services | -| Audio, electronic, visual, or similar information such as content and files uploaded to the Service. | 消费者可选择直接提供的信息 | -| Professional or employment information | 消费者可选择直接提供的信息 | -| Inferences drawn from any of the information identified in this table to create a profile about a consumer reflecting the consumer’s preferences | 消费者直接提供的信息，或者在与我们服务交互的过程中自动提供的信息 | +| 过去 12 个月内收集的个人信息类别 | 个人信息收集来源的类别 | +| --------------------------------------------------------------- | ---------------------------------------------------- | +| 标识符（例如，真实姓名、别名、邮政地址、唯一的个人标识符、在线标识符、互联网协议地址、电子邮件地址、帐户名或其他类似的标识符） | 消费者通过与我们的服务和/或网站或 GitHub 的供应商、合作伙伴或附属公司的互动直接或自动提供的信息 | +| 加州规范 民事 §1798.80 (e) 中描述的个人信息，例如姓名、地址、信用卡或贷记卡号 | 消费者可以选择通过服务提供商直接提供的信息 | +| 加州或联邦法律下受保护的分类特征（例如性别） | 消费者可选择直接提供的信息 | +| 商业信息（例如有关购买、获取或考虑的产品或服务的信息，或其他购买或消费历史记录或趋势的信息） | 消费者直接提供的信息，或者在与我们服务交互的过程中自动提供的信息 | +| 地理位置数据（例如，在让用户有机会选择加入基于位置的服务后收集的任何信息，这些服务依赖于设备的精确位置服务。 ) | 消费者在与我们服务交互的过程中自动提供的信息 | +| 上传到服务的音频、电子、视频或类似信息，例如内容和文件。 | 消费者可选择直接提供的信息 | +| 专业或就业信息 | 消费者可选择直接提供的信息 | +| 从此表中标识的任何信息中得出推论，以创建反映消费者偏好的消费者档案 | 消费者直接提供的信息，或者在与我们服务交互的过程中自动提供的信息 | -We use the categories of personal information described above for the purposes listed in the [“How GitHub uses your information”](/github/site-policy/github-privacy-statement#how-github-uses-your-information) section of our Privacy Statement. We also disclose the categories of personal information listed above for business purposes. Please see the [“How we share the information we collect”](/github/site-policy/github-privacy-statement#how-we-share-the-information-we-collect) section of our Privacy Statement for additional details. +我们将上述个人信息类别用于隐私声明的[“GitHub 如何使用您的信息”](/github/site-policy/github-privacy-statement#how-github-uses-your-information)一节中列出的目的。 我们还出于商业目的披露上面列出的个人信息类别。 有关其他详细信息，请参阅隐私声明[“我们如何共享收集的信息”](/github/site-policy/github-privacy-statement#how-we-share-the-information-we-collect)一节。 ### 我们不会出售您的个人信息 -根据 CCPA，企业要向他人出售加州居民的个人信息：1) 必须事先通知相关的加州居民；以及 2) 必须提供否决权。 GitHub does not sell personal information, including personal information of anyone under 16 years old. +根据 CCPA，企业要向他人出售加州居民的个人信息：1) 必须事先通知相关的加州居民；以及 2) 必须提供否决权。 GitHub 不出售个人信息，包括 16 岁以下任何人的个人信息。 ### 您在 CCPA 下的权利 CCPA 为加州居民提供关于其个人信息的某些权利。 要提交基于这些权利的申请，请通过我们的[联系表](https://support.github.com/contact?tags=docs-policy)联系我们。 -我们收到请求后，将核实提出请求的个人是否为其个人信息适用于此类请求的居民。 California residents may exercise their rights themselves or may use an authorized agent, designated in writing or through a power of attorney, to make requests on their behalf. If you use an authorized agent to submit a request, we may require that you provide us additional information demonstrating that the agent is acting on your behalf, and we may need you to verify your identity directly with us. With respect to your personal information, California residents may exercise the rights described below. -#### Right to Know. +我们收到请求后，将核实提出请求的个人是否为其个人信息适用于此类请求的居民。 加州居民可以自己行使自己的权利，也可以使用书面或授权书指定的授权代理人代表他们提出请求。 如果您通过授权代理人提交请求，我们可能要求您提供额外信息，以证明该代理人在代表您行事，并且我们可能需要您直接向我们验证您的身份。。 对于自己的个人信息，加州居民可行使下述权利。 +#### 知情权。 You have a right to request that we disclose to you the personal information we have collected about you. You also have a right to request additional information about our collection, use, disclosure, or sale of such personal information. Note that we have provided much of this information in this privacy statement. You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to know” by contacting us here. #### Right to Request Deletion. You also have a right to request that we delete personal information under certain circumstances, subject to a number of exceptions. To make a request to delete, You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to delete” by contacting us here. diff --git a/translations/zh-CN/data/features/issue-close-reasons.yml b/translations/zh-CN/data/features/issue-close-reasons.yml new file mode 100644 index 0000000000..b11b389fe7 --- /dev/null +++ b/translations/zh-CN/data/features/issue-close-reasons.yml @@ -0,0 +1,8 @@ +--- +#Issues 6363 +#Closed issue states +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6363' diff --git a/translations/zh-CN/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md b/translations/zh-CN/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md index 98456bea22..ac788fb978 100644 --- a/translations/zh-CN/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md +++ b/translations/zh-CN/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md @@ -1 +1 @@ -Use `jobs..name` to a name for the job, which is displayed on {% data variables.product.prodname_dotcom %}. +Use `jobs..name` to set a name for the job, which is displayed in the {% data variables.product.prodname_dotcom %} UI. diff --git a/translations/zh-CN/data/reusables/getting-started/learning-lab-enterprise.md b/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md similarity index 51% rename from translations/zh-CN/data/reusables/getting-started/learning-lab-enterprise.md rename to translations/zh-CN/data/reusables/getting-started/learning-enterprise.md index 6564a08836..2647286168 100644 --- a/translations/zh-CN/data/reusables/getting-started/learning-lab-enterprise.md +++ b/translations/zh-CN/data/reusables/getting-started/learning-enterprise.md @@ -1,3 +1,3 @@ -您的企业成员可以通过 [{% data variables.product.prodname_learning %}](https://lab.github.com/) 在自己的 GitHub 存储库中完成有趣、逼真的项目来学习新技能。 每门课程都是由 GitHub 社区创建的实践课程，由友好的学习实验室机器人授课。 +您的企业成员可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣、逼真的项目来学习新技能。 Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. 更多信息请参阅“[Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)”。 diff --git a/translations/zh-CN/data/reusables/getting-started/learning-lab.md b/translations/zh-CN/data/reusables/getting-started/learning.md similarity index 53% rename from translations/zh-CN/data/reusables/getting-started/learning-lab.md rename to translations/zh-CN/data/reusables/getting-started/learning.md index 7982ff5b97..5e3cdd2b84 100644 --- a/translations/zh-CN/data/reusables/getting-started/learning-lab.md +++ b/translations/zh-CN/data/reusables/getting-started/learning.md @@ -1,3 +1,3 @@ -您可以通过 [{% data variables.product.prodname_learning %}](https://lab.github.com/) 在自己的 GitHub 存储库中完成有趣，逼真的项目来学习新技能。 每门课程都是由 GitHub 社区创建的实践课程，由友好的学习实验室机器人授课。 +您可以通过 [{% data variables.product.prodname_learning %}](https://skills.github.com/) 在自己的 GitHub 存储库中完成有趣，逼真的项目来学习新技能。 Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. 更多信息请参阅“[Git 和 {% data variables.product.prodname_dotcom %} 学习资源](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)”。 diff --git a/translations/zh-CN/data/reusables/open-source/open-source-learning-lab.md b/translations/zh-CN/data/reusables/open-source/open-source-learning.md similarity index 100% rename from translations/zh-CN/data/reusables/open-source/open-source-learning-lab.md rename to translations/zh-CN/data/reusables/open-source/open-source-learning.md diff --git a/translations/zh-CN/data/reusables/projects/create-project.md b/translations/zh-CN/data/reusables/projects/create-project.md index 338f228e85..3f7ae138e2 100644 --- a/translations/zh-CN/data/reusables/projects/create-project.md +++ b/translations/zh-CN/data/reusables/projects/create-project.md @@ -1,5 +1,8 @@ 1. 在 {% data variables.product.prodname_dotcom %} 上，导航到组织的主页面。 -2. 单击 {% octicon "table" aria-label="The project icon" %} **Projects（项目）**。 -3. 选择 **New project（新项目）**下拉菜单并点击 **New project (Beta)（新项目 [测试版]）**。 +1. 单击 {% octicon "table" aria-label="The project icon" %} **Projects（项目）**。 +1. 选择 **New project（新项目）**下拉菜单并点击 **New project (Beta)（新项目 [测试版]）**。 ![新项目](/assets/images/help/issues/new_project_beta.png) +1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. + + ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/projects/create-user-project.md b/translations/zh-CN/data/reusables/projects/create-user-project.md index 80a8feeb41..5e303bc69d 100644 --- a/translations/zh-CN/data/reusables/projects/create-user-project.md +++ b/translations/zh-CN/data/reusables/projects/create-user-project.md @@ -1,4 +1,7 @@ 1. 在任何 {% data variables.product.product_name %} 页面上，单击您的头像，然后选择 **Your projects（您的项目）**。 -2. 选择 **New project（新项目）**下拉菜单并点击 **New project (Beta)（新项目 [测试版]）**。 +1. 选择 **New project（新项目）**下拉菜单并点击 **New project (Beta)（新项目 [测试版]）**。 ![新项目](/assets/images/help/issues/new_project_beta.png) +1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. + + ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/projects/reopen-a-project.md b/translations/zh-CN/data/reusables/projects/reopen-a-project.md new file mode 100644 index 0000000000..8f0cbdec82 --- /dev/null +++ b/translations/zh-CN/data/reusables/projects/reopen-a-project.md @@ -0,0 +1,6 @@ +1. Click the **Projects** tab. ![Screenshot showing project close button](/assets/images/help/issues/projects-profile-tab.png) +1. To show closed projects, click **Closed**. ![Screenshot showing project close button](/assets/images/help/issues/closed-projects-tab.png) +1. Click the project you want to reopen. +1. 在右上角，单击 {% octicon "kebab-horizontal" aria-label="The menu icon" %} 以打开菜单。 +1. In the menu, to access the project settings, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png) \ No newline at end of file diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 1f0e227403..3841753480 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -105,12 +105,12 @@ prodname_advanced_security: 'Advanced Security' prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' prodname_serverless: '基于 Web 的编辑器' -#GitHub resources: blog, jobs, Learning Lab +#GitHub resources: blog, jobs, skills prodname_gcf: 'GitHub Community Support' prodname_blog: 'GitHub 博客' prodname_jobs: 'GitHub Jobs' -prodname_learning: 'GitHub Learning Lab' -prodname_learning_link: 'https://lab.github.com/' +prodname_learning: 'GitHub Skills' +prodname_learning_link: 'https://skills.github.com/' prodname_roadmap: 'GitHub 公共路线图' prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap' #GitHub support From 29f03e7c543edb4c7855b06d8d0a436bf0893d60 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 6 Jun 2022 18:58:09 -0400 Subject: [PATCH 3/8] New translation batch for ja (#28278) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report --- .../about-github-hosted-runners.md | 5 +- .../configuring-web-commit-signing.md | 2 +- .../about-using-actions-in-your-enterprise.md | 2 +- ...bout-authentication-for-your-enterprise.md | 73 ++++++++++---- .../about-enterprise-managed-users.md | 15 ++- .../about-saml-for-enterprise-iam.md | 16 ++-- ...es-in-the-audit-log-for-your-enterprise.md | 2 +- ...ting-a-listing-description-for-your-app.md | 2 +- .../create-a-group-assignment.md | 2 +- .../getting-started-with-github-ae.md | 2 +- ...ng-started-with-github-enterprise-cloud.md | 2 +- ...g-started-with-github-enterprise-server.md | 4 +- .../getting-started-with-github-team.md | 2 +- ...etting-started-with-your-github-account.md | 4 +- .../quickstart/contributing-to-projects.md | 2 +- .../get-started/quickstart/create-a-repo.md | 2 +- .../get-started/quickstart/fork-a-repo.md | 4 +- .../git-and-github-learning-resources.md | 45 ++++----- .../basic-writing-and-formatting-syntax.md | 2 +- .../closing-an-issue.md | 30 ++++++ ...-and-searching-issues-and-pull-requests.md | 3 +- .../tracking-your-work-with-issues/index.md | 1 + .../index.md | 1 + .../managing-projects.md | 43 +++++++++ .../about-ssh-certificate-authorities.md | 6 ++ .../about-github-pages.md | 2 +- .../about-collaborative-development-models.md | 2 +- .../searching-issues-and-pull-requests.md | 94 +++++++++++-------- .../data/features/issue-close-reasons.yml | 8 ++ .../enterprise-server/3-2/11.yml | 40 ++++---- .../enterprise-server/3-2/12.yml | 14 +-- .../enterprise-server/3-2/13.yml | 2 +- .../release-notes/enterprise-server/3-3/6.yml | 50 +++++----- .../release-notes/enterprise-server/3-3/7.yml | 24 ++--- .../release-notes/enterprise-server/3-3/8.yml | 10 +- .../release-notes/enterprise-server/3-4/1.yml | 58 ++++++------ .../release-notes/enterprise-server/3-4/2.yml | 32 +++---- .../release-notes/enterprise-server/3-4/3.yml | 20 ++-- .../enterprise-server/3-5/0-rc1.yml | 18 ++-- .../release-notes/enterprise-server/3-5/0.yml | 18 ++-- .../section-using-jobs-in-a-workflow-name.md | 2 +- ...b-enterprise.md => learning-enterprise.md} | 2 +- .../{learning-lab.md => learning.md} | 2 +- ...earning-lab.md => open-source-learning.md} | 0 .../data/reusables/projects/create-project.md | 7 +- .../reusables/projects/create-user-project.md | 5 +- .../reusables/projects/reopen-a-project.md | 6 ++ translations/ja-JP/data/variables/product.yml | 6 +- translations/log/ja-resets.csv | 5 +- 49 files changed, 426 insertions(+), 273 deletions(-) create mode 100644 translations/ja-JP/content/issues/tracking-your-work-with-issues/closing-an-issue.md create mode 100644 translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-projects.md create mode 100644 translations/ja-JP/data/features/issue-close-reasons.yml rename translations/ja-JP/data/reusables/getting-started/{learning-lab-enterprise.md => learning-enterprise.md} (63%) rename translations/ja-JP/data/reusables/getting-started/{learning-lab.md => learning.md} (66%) rename translations/ja-JP/data/reusables/open-source/{open-source-learning-lab.md => open-source-learning.md} (100%) create mode 100644 translations/ja-JP/data/reusables/projects/reopen-a-project.md diff --git a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md index ed92e0882f..3470a958b4 100644 --- a/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md +++ b/translations/ja-JP/content/actions/using-github-hosted-runners/about-github-hosted-runners.md @@ -187,11 +187,8 @@ Dockerコンテナで実行されるアクションには、 `/github`パスの - `/github/workspace` - {% data reusables.repositories.action-root-user-required %} - `/github/workflow` -{% ifversion fpt or ghec %} - ## 参考リンク - 「[{% data variables.product.prodname_actions %} の支払いを管理する](/billing/managing-billing-for-github-actions)」 - -{% endif %} +- You can use a matrix strategy to run your jobs on multiple images. For more information, see "[Using a matrix for your jobs](/actions/using-jobs/using-a-matrix-for-your-jobs)." {% endif %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md index 67bb383325..1e7b640177 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md +++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-web-commit-signing.md @@ -37,7 +37,7 @@ You can enable web commit signing, rotate the private key used for web commit si ```bash{:copy} ghe-config-apply ``` -1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)." +1. Create a new user on {% data variables.product.product_location %} via built-in authentication or external authentication. 詳しい情報については「[Enterpriseでの認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)」を参照してください。 - The user's username must be `web-flow`. - The user's email address must be the same address you used for the PGP key. {% data reusables.enterprise_site_admin_settings.add-key-to-web-flow-user %} diff --git a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index b2dca564bc..6610670d48 100644 --- a/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/ja-JP/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -48,7 +48,7 @@ Each action is a repository in the `actions` organization, and each action repos **Notes:** - When using setup actions (such as `actions/setup-LANGUAGE`) on {% data variables.product.product_name %} with self-hosted runners, you might need to set up the tools cache on runners that do not have internet access. For more information, see "[Setting up the tool cache on self-hosted runners without internet access](/enterprise/admin/github-actions/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access)." -- Bundled actions are automatically updated when {% data variables.product.product_name %} is updated. +- When {% data variables.product.product_name %} is updated, bundled actions are automatically replaced with default versions in the upgrade package. {% endnote %} diff --git a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md index 416130cfad..0165c30adb 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise.md @@ -21,7 +21,9 @@ topics: Enterprise owners on {% data variables.product.product_name %} can control the requirements for authentication and access to the enterprise's resources. -You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. If you choose to manage your members' user accounts, you must configure SAML authentication. +You can choose to allow members to create and manage user accounts, or your enterprise can create and manage accounts for members with {% data variables.product.prodname_emus %}. If you allow members to manage their own accounts, you can also configure SAML authentication to both increase security and centralize identity and access for the web applications that your team uses. + +After learning more about these options, to determine which method is best for your enterprise, see "[Identifying the best authentication method for your enterprise](#identifying-the-best-authentication-method-for-your-enterprise)." ## Authentication methods for {% data variables.product.product_name %} @@ -29,7 +31,7 @@ The following options are available for account management and authentication on - [Authentication through {% data variables.product.product_location %}](#authentication-through-githubcom) - [Authentication through {% data variables.product.product_location %} with additional SAML access restriction](#authentication-through-githubcom-with-additional-saml-access-restriction) -- [Authentication with {% data variables.product.prodname_emus %} and SAML SSO](#authentication-with-enterprise-managed-users-and-saml-sso) +- [Authentication with {% data variables.product.prodname_emus %} and federation](#authentication-with-enterprise-managed-users-and-federation) ### Authentication through {% data variables.product.product_location %} @@ -41,10 +43,61 @@ If you configure additional SAML access restriction, each member must create and If you use a standalone organization with {% data variables.product.product_name %}, or if you don't want to use SAML authentication for every organization in your enterprise, you can configure SAML for an individual organization. For more information, see "[About identity and access management with SAML single sign-on](/organizations/managing-saml-single-sign-on-for-your-organization/about-identity-and-access-management-with-saml-single-sign-on)." -### Authentication with {% data variables.product.prodname_emus %} and SAML SSO +### Authentication with {% data variables.product.prodname_emus %} and federation If you need more control of the accounts for your enterprise members on {% data variables.product.product_location %}, you can use {% data variables.product.prodname_emus %}. With {% data variables.product.prodname_emus %}, you provision and manage accounts for your enterprise members on {% data variables.product.product_location %} using your IdP. Each member signs into an account that you create, and your enterprise manages the account. Contributions to the rest of {% data variables.product.prodname_dotcom_the_website %} are restricted. For more information, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users)." +## Identifying the best authentication method for your enterprise + +Both SAML SSO and {% data variables.product.prodname_emus %} increase security for your enterprise's resources. {% data variables.product.prodname_emus %} additionally allows you to control the user accounts for your enterprise members and restricts what the accounts are able to do. However, those restrictions may be unacceptable for your enterprise if they obstruct your developers' workflows. + +To determine whether your enterprise would benefit more from SAML SSO or {% data variables.product.prodname_emus %}, ask yourself these questions. + +- [Do you want to control the user accounts for your users?](#do-you-want-to-control-the-user-accounts-for-your-users) +- [Which identity provider does your enterprise use?](#which-identity-provider-does-your-enterprise-use) +- [Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites?](#do-your-developers-work-in-public-repositories-gists-or-github-pages-sites) +- [Do your developers rely on collaboration outside of your enterprise?](#do-your-developers-rely-on-collaboration-outside-of-your-enterprise) +- [Does your enterprise rely on outside collaborators?](#does-your-enterprise-rely-on-outside-collaborators) +- [Can your enterprise tolerate migration costs?](#can-your-enterprise-tolerate-migration-costs) + +### Do you want to control the user accounts for your users? + +{% data variables.product.prodname_emus %} may be right for your enterprise if you don't want enterprise members to use their own personal accounts on {% data variables.product.prodname_dotcom_the_website %} to access your enterprise's resources. + +With SAML SSO, developers create and manage their own personal accounts, and each account is linked to a SAML identity in your IdP. {% data variables.product.prodname_emus %} functions more like other familiar SSO solutions, as you will provision the accounts for your users. You can also ensure user accounts conform with your company identity, by controlling usernames and the email addresses associated with the accounts. + +If you currently require your users to create a new account on {% data variables.product.prodname_dotcom_the_website %} to use with your enterprise only, {% data variables.product.prodname_emus %} might be right for you. However, SAML SSO may be a better option if using your IdP as the source of truth for your user and access management would add too much complexity. For example, perhaps your enterprise does not have an established process for onboarding new users in your IdP. + +### Which identity provider does your enterprise use? + +{% data variables.product.prodname_emus %} is supported for a limited number of IdPs, while SAML SSO offers full support for a larger number of IdPs, plus limited support for all IdPs that implement the SAML 2.0 standard. For the list of supported IdPs for each option, see "[About {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#identity-provider-support)" and "[About SAML for enterprise IAM](/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam#supported-idps)." + +You can use {% data variables.product.prodname_emus %} with an unsupported IdP only if you federate the unsupported IdP to a supported IdP to use as an integration point. If you wish to avoid this extra complexity, SAML SSO may be a better solution for you. + +### Do your developers work in public repositories, gists, or {% data variables.product.prodname_pages %} sites? + +To prevent enterprise members from accidentally leaking corporate-owned content to the public on {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_emus %} imposes strong restrictions on what users can do. For example, {% data variables.product.prodname_managed_users %} cannot create public repositories, gists of any visibility, or {% data variables.product.prodname_pages %} sites that are visible outside the enterprise. For a full list of restrictions, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#abilities-and-restrictions-of-managed-users)." + +These restrictions are unacceptable for some enterprises. To determine whether {% data variables.product.prodname_emus %} will work for you, review the restrictions with your developers, and confirm whether any of the restrictions will hinder your existing workflows. If so, SAML SSO may be a better choice for your enterprise. + +### Do your developers rely on collaboration outside of your enterprise? + +{% data variables.product.prodname_managed_users_caps %} can only contribute to repositories within your enterprise. If your developers need to collaborate in repositories outside your enterprise, even private repositories, to complete their work, {% data variables.product.prodname_emus %} may not be right for your enterprise, and SAML SSO may be a better solution. + +### Does your enterprise rely on outside collaborators? + +With SAML SSO, you can give access to specific repositories to people who are not members of your IdP's directory, by using the outside collaborator role. This can be especially useful for collaborators that are external to your business, such as contractors. For more information, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)." + +With {% data variables.product.prodname_emus %}, the outside collaborator role does not exist. Your enterprise's resources can only be accessed by {% data variables.product.prodname_managed_users %}, which are always provisioned by your IdP. To give external collaborators access to your enterprise, you would have to use guest accounts in your IdP. If you're interested in {% data variables.product.prodname_emus %}, confirm with your developers whether this will hinder any of their existing workflows. If so, SAML SSO may be a better solution. + +### Can your enterprise tolerate migration costs? + +If your enterprise is new to {% data variables.product.prodname_dotcom_the_website %}, SAML SSO and {% data variables.product.prodname_emus %} are equally easy to adopt. + +If you're already using {% data variables.product.prodname_dotcom_the_website %} with developers managing their own user accounts, adopting {% data variables.product.prodname_emus %} requires migrating to a new enterprise account. For more information, see "[About enterprises with {% data variables.product.prodname_managed_users %}](/admin/identity-and-access-management/using-enterprise-managed-users-and-saml-for-iam/about-enterprise-managed-users#about-enterprises-with-managed-users)." + +Although {% data variables.product.prodname_emus %} is free, the migration process may require time or cost from your team. Confirm that this migration process is acceptable to your business and your developers. If not, SAML SSO may be the better choice for you. + {% elsif ghes %} Site administrators can decide how people authenticate to access a {% data variables.product.product_name %} instance. You can use {% data variables.product.product_name %}'s built-in authentication, or, if you want to centralize identity and access management for the web applications that your team uses, you can configure an external authentication method. @@ -76,20 +129,6 @@ If you choose to use external authentication, you can also configure fallback au {% endif %} -## About access control - -{% ifversion ghec or ghae %}Members of your enterprise{% elsif ghes %}People with access to {% data variables.product.product_location %}{% endif %} can manage access to {% ifversion ghec %}your enterprise's resources{% elsif ghae %}your enterprise{% elsif ghes %}resources on your instance{% endif %} by using organization membership, teams, and roles. 詳しい情報については、以下を参照してください。 - -{%- ifversion ghec %} -- [Organization に参加するようユーザを招待する](/organizations/managing-membership-in-your-organization/inviting-users-to-join-your-organization)" -{%- elsif ghes or ghae %} -- "[Adding people to your organization](/organizations/managing-membership-in-your-organization/adding-people-to-your-organization)" -{%- endif %} -- 「[Organizationのロール](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)」 -- [Team について](/organizations/organizing-members-into-teams/about-teams) -- 「[Organizationのリポジトリロール](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)」 -- [ユーザアカウントのリポジトリの権限レベル](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository) - ## 参考リンク - 「[{% data variables.product.company_short %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」 diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md index 546395b6ea..d429b9998a 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md @@ -2,7 +2,6 @@ title: About Enterprise Managed Users shortTitle: About managed users intro: 'You can centrally manage identity and access for your enterprise members on {% data variables.product.prodname_dotcom %} from your identity provider.' -product: '{% data reusables.gated-features.emus %}' redirect_from: - /early-access/github/articles/get-started-with-managed-users-for-your-enterprise - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/about-enterprise-managed-users @@ -21,11 +20,11 @@ topics: ## {% data variables.product.prodname_emus %}について -With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). You can simplify authentication with SAML{% if oidc-for-emu %} or OIDC{% endif %} single sign-on (SSO) and provision, update, and deprovision user accounts for your enterprise members. Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access from your IdP. +With {% data variables.product.prodname_emus %}, you can control the user accounts of your enterprise members through your identity provider (IdP). Users assigned to the {% data variables.product.prodname_emu_idp_application %} application in your IdP are provisioned as new user accounts on {% data variables.product.prodname_dotcom %} and added to your enterprise. You control usernames, profile data, team membership, and repository access for the user accounts from your IdP. In your IdP, you can give each {% data variables.product.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.product.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.product.prodname_managed_users %} to the organizations and teams within. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)" and "[About organizations](/organizations/collaborating-with-groups-in-organizations/about-organizations)." -Organization membership can be managed manually or updated automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." +Organization membership can be managed manually, or you can update membership automatically as {% data variables.product.prodname_managed_users %} are added to IdP groups that are connected to teams within the organization. When a {% data variables.product.prodname_managed_user %} is manually added to an organization, unassigning them from the {% data variables.product.prodname_emu_idp_application %} application on your IdP will suspend the user but not remove them from the organization. For more information about managing organization and team membership automatically, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)." {% if oidc-for-emu %} @@ -33,7 +32,7 @@ Organization membership can be managed manually or updated automatically as {% d {% endif %} -You can grant {% data variables.product.prodname_managed_users %} access and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. The {% data variables.product.prodname_managed_users %} provisioned for your enterprise cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. Outside collaborators are not supported by {% data variables.product.prodname_emus %}. +You can grant {% data variables.product.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.product.prodname_managed_users %} cannot create public content or collaborate with other users, organizations, and enterprises on the rest of {% data variables.product.prodname_dotcom %}. For more information, see "[Abilities and restrictions of {% data variables.product.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." The usernames of your enterprise's {% data variables.product.prodname_managed_users %} and their profile information, such as display names and email addresses, are set by through your IdP and cannot be changed by the users themselves. For more information, see "[Usernames and profile information](#usernames-and-profile-information)." @@ -43,6 +42,11 @@ Enterprise owners can audit all of the {% data variables.product.prodname_manage To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. For more information about creating this account, see "[About enterprises with managed users](#about-enterprises-with-managed-users)." +{% note %} + +**Note:** There are multiple options for identity and access management with {% data variables.product.prodname_ghe_cloud %}, and {% data variables.product.prodname_emus %} is not the best solution for every customer. For more information about whether {% data variables.product.prodname_emus %} is right for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." + +{% endnote %} ## Identity provider support @@ -62,6 +66,8 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e {% data variables.product.prodname_managed_users_caps %} can only contribute to private and internal repositories within their enterprise and private repositories owned by their user account. {% data variables.product.prodname_managed_users_caps %} have read-only access to the wider {% data variables.product.prodname_dotcom %} community. These visibility and access restrictions for users and content apply to all requests, including API requests. +* {% data variables.product.prodname_managed_users %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.product.prodname_managed_users %} be invited to other enterprises. +* Outside collaborators are not supported by {% data variables.product.prodname_emus %}. * {% data variables.product.prodname_managed_users_caps %} cannot create issues or pull requests in, comment or add reactions to, nor star, watch, or fork repositories outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} can view all public repositories on {% data variables.product.prodname_dotcom_the_website %}, but cannot push code to repositories outside of the enterprise. * {% data variables.product.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. @@ -70,6 +76,7 @@ To use {% data variables.product.prodname_emus %}, you need a separate type of e * {% data variables.product.prodname_managed_users_caps %} cannot install {% data variables.product.prodname_github_apps %} on their user accounts. * Other {% data variables.product.prodname_dotcom %} users cannot see, mention, or invite a {% data variables.product.prodname_managed_user %} to collaborate. * {% data variables.product.prodname_managed_users_caps %} can only own private repositories and {% data variables.product.prodname_managed_users %} can only invite other enterprise members to collaborate on their owned repositories. +* {% data reusables.enterprise-accounts.emu-forks %} * Only private and internal repositories can be created in organizations owned by an {% data variables.product.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. * {% data variables.product.prodname_managed_users_caps %} are limited in their use of {% data variables.product.prodname_pages %}. 詳しい情報については、「[{% data variables.product.prodname_pages %} について](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)」を参照してください。 diff --git a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md index ece07f9ae0..042ecc2b2b 100644 --- a/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md +++ b/translations/ja-JP/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md @@ -1,7 +1,7 @@ --- title: About SAML for enterprise IAM shortTitle: About SAML for IAM -intro: 'You can use SAML single sign-on (SSO) {% ifversion ghec or ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.product.product_location %}{% elsif ghae %}to {% data variables.product.product_location %}{% endif %}.' +intro: 'You can use SAML single sign-on (SSO) {% ifversion ghae %}and System for Cross-domain Identity Management (SCIM) {% endif %}to centrally manage access {% ifversion ghec %}to organizations owned by your enterprise on {% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}to {% data variables.product.product_location %}{% elsif ghae %}to {% data variables.product.product_location %}{% endif %}.' versions: ghec: '*' ghes: '*' @@ -28,9 +28,11 @@ redirect_from: {% ifversion ghec %} -{% data reusables.saml.dotcom-saml-explanation %} {% data reusables.saml.about-saml-enterprise-accounts %} For more information, see "[Configuring SAML single sign-on for your enterprise](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)." +If your enterprise members manage their own user accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. {% data reusables.saml.dotcom-saml-explanation %} -If your enterprise members manage their own personal accounts on {% data variables.product.product_location %}, you can configure SAML authentication as an additional access restriction for your enterprise or organization. Alternatively, you can provision and manage the accounts of your enterprise members on {% data variables.product.product_location %} by using an enterprise account with {% data variables.product.prodname_emus %} enabled. For more information, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#authentication-methods-for-github-enterprise-cloud)." +{% data reusables.saml.about-saml-enterprise-accounts %}詳しい情報については、「[Enterprise 向けの SAML シングルサインオンを設定する](/admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise)」を参照してください。 + +Alternatively, you can provision and manage the accounts of your enterprise members with {% data variables.product.prodname_emus %}. To help you determine whether SAML SSO or {% data variables.product.prodname_emus %} is better for your enterprise, see "[About authentication for your enterprise](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)." {% data reusables.enterprise-accounts.about-recovery-codes %} For more information, see "[Managing recovery codes for your enterprise](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)." @@ -38,19 +40,13 @@ SAML SSO を有効にした後、使用する IdP によっては、追加のア IdP として Azure AD を使用している場合は、Team 同期を使用して、各 Organization 内の Team メンバーシップを管理できます。 {% data reusables.identity-and-permissions.about-team-sync %} 詳しい情報については、「[Enterprise アカウントで Organization の Team 同期を管理する](/admin/authentication/managing-identity-and-access-for-your-enterprise/managing-team-synchronization-for-organizations-in-your-enterprise)」を参照してください。 -{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." - -## {% data variables.product.prodname_emus %}について - -{% data reusables.enterprise-accounts.emu-short-summary %} - {% note %} **Note:** You cannot use SCIM at the enterprise level unless your enterprise is enabled for {% data variables.product.prodname_emus %}. {% endnote %} -Configuring {% data variables.product.prodname_emus %} for SAML single-sign on and user provisioning involves following a different process than you would for an enterprise that isn't using {% data variables.product.prodname_managed_users %}. If your enterprise uses {% data variables.product.prodname_emus %}, see "[Configuring SAML single sign-on for Enterprise Managed Users](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-saml-single-sign-on-for-enterprise-managed-users)." +{% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)." {% elsif ghes %} diff --git a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md index 3f75a5a2d2..d5240df0e0 100644 --- a/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md +++ b/translations/ja-JP/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/displaying-ip-addresses-in-the-audit-log-for-your-enterprise.md @@ -28,7 +28,7 @@ You are responsible for meeting any legal obligations that accompany the viewing If you choose to display IP addresses, the IP addresses only appear in your enterprise's audit log. IP addresses will not appear for events in the audit logs for individual organizations owned by your enterprise. For more information about organization audit logs, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization)." -You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.product.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)." +You can display IP addresses in the audit log regardless of which authentication method you use for your enterprise on {% data variables.product.product_location %}. 詳しい情報については「[Enterpriseでの認証について](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise)」を参照してください。 When anyone creates an account on {% data variables.product.product_location %}, the person agrees to {% data variables.product.company_short %}'s collection of basic information about connections to {% data variables.product.company_short %}'s services, including source IP address. For more information, see "[GitHub Privacy Statement](/free-pro-team@latest/site-policy/privacy-policies/github-privacy-statement#usage-information)." diff --git a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md index 25d7ba332c..aa7d4a3509 100644 --- a/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md +++ b/translations/ja-JP/content/developers/github-marketplace/listing-an-app-on-github-marketplace/writing-a-listing-description-for-your-app.md @@ -168,7 +168,7 @@ shortTitle: リストの説明を書く ### 必要なスキルを学ぶ - GitHub Learning Labでは、GitHubの使い方を学習、Markdownによる効果的な連絡、マージコンフリクトの処理などが可能です。 + GitHub Skills can help you learn how to use GitHub, communicate more effectively with Markdown, handle merge conflicts, and more. - 大文字で始めて英文字表記するのは固有名詞だけです。 diff --git a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md index 587e68725d..dad07815aa 100644 --- a/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md +++ b/translations/ja-JP/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/create-a-group-assignment.md @@ -143,7 +143,7 @@ The assignment overview page displays information about your assignment acceptan ## 次のステップ -- 課題を作成し、学生がTeamを編成した後、TeamメンバーはGitと{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたもTeamも、リポジトリのコミット履歴をレビューできます。 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 [managing merge conflicts](https://lab.github.com/githubtraining/managing-merge-conflicts) from {% data variables.product.prodname_learning %}. +- 課題を作成し、学生がTeamを編成した後、TeamメンバーはGitと{% data variables.product.product_name %}の機能を使用して課題を開始できます。 学生はリポジトリのクローン、コミットのプッシュ、ブランチの管理、プルリクエストの作成およびレビュー、マージコンフリクトへの対処、およびIssueの変更に関するディスカッションが可能です。 あなたもTeamも、リポジトリのコミット履歴をレビューできます。 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 %}. - 課題を完了したチームがある場合は、そのリポジトリにあるファイルをレビューできます。また、チームがどのように協力したかをより深く理解するため、リポジトリの履歴や視覚化されたデータを確認できます。 詳しい情報については、「[リポジトリデータをグラフで可視化する](/github/visualizing-repository-data-with-graphs)」を参照してください。 diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md index 9c7d4e222b..2e528a4699 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-ae.md @@ -77,7 +77,7 @@ Your enterprise members can learn more about Git and {% data variables.product.p 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)." ### 2. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab-enterprise %} +{% data reusables.getting-started.learning-enterprise %} ### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md index 68a2d83b78..4b1d54360d 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-cloud.md @@ -206,7 +206,7 @@ Members of your organization or enterprise can use GitHub's learning and support You can read documentation that reflects the features available with {% data variables.product.prodname_ghe_cloud %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." ### 2. Learning with {% data variables.product.prodname_learning %} -Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Members of your organization or enterprise can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." ### 3. Supporting the open source community diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md index 06ae077d79..08e04985ae 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-enterprise-server.md @@ -67,7 +67,7 @@ As an enterprise owner or administrator, you can manage settings on user, reposi ## Part 3: Building securely To increase the security of {% data variables.product.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.product.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)." +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.product.product_location %}. 詳しい情報については「[Enterpriseでの認証について](/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)." @@ -120,7 +120,7 @@ Your enterprise members can learn more about Git and {% data variables.product.p 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)." ### 2. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab-enterprise %} +{% data reusables.getting-started.learning-enterprise %} ### 3. Working with {% data variables.product.prodname_dotcom %} Enterprise Support {% data reusables.getting-started.contact-support-enterprise %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md index 0dee78bca6..5e37000424 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-github-team.md @@ -87,7 +87,7 @@ You can help to make your organization more secure by recommending or requiring You can read documentation that reflects the features available with {% data variables.product.prodname_team %}. For more information, see "[About versions of {% data variables.product.prodname_docs %}](/get-started/learning-about-github/about-versions-of-github-docs)." ### 4. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab %} +{% data reusables.getting-started.learning %} ### 5. Supporting the open source community {% data reusables.getting-started.sponsors %} diff --git a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md index 32343e3474..e741ab09ae 100644 --- a/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md +++ b/translations/ja-JP/content/get-started/onboarding/getting-started-with-your-github-account.md @@ -81,7 +81,7 @@ For more information about how to authenticate to {% data variables.product.prod ### 4. Writing on {% data variables.product.product_name %} To make your communication clear and organized in issues and pull requests, you can use {% data variables.product.prodname_dotcom %} Flavored Markdown for formatting, which combines an easy-to-read, easy-to-write syntax with some custom functionality. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/github/writing-on-github/about-writing-and-formatting-on-github)」を参照してください。 -You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicating using Markdown](https://lab.github.com/githubtraining/communicating-using-markdown)" course on {% data variables.product.prodname_learning %}. +You can learn {% data variables.product.prodname_dotcom %} Flavored Markdown with the "[Communicate using Markdown](https://github.com/skills/communicate-using-markdown)" course on {% data variables.product.prodname_learning %}. ### 5. Searching on {% data variables.product.product_name %} Our integrated search allows you to find what you are looking for among the many repositories, users and lines of code on {% data variables.product.product_name %}. You can search globally across all of {% data variables.product.product_name %} or limit your search to a particular repository or organization. For more information about the types of searches you can do on {% data variables.product.product_name %}, see "[About searching on {% data variables.product.prodname_dotcom %}](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github)." @@ -187,7 +187,7 @@ For more information, see "[Securing your software supply chain](/code-security/ {% data reusables.docs.you-can-read-docs-for-your-product %} ### 4. Learning with {% data variables.product.prodname_learning %} -{% data reusables.getting-started.learning-lab %} +{% data reusables.getting-started.learning %} {% ifversion fpt or ghec %} ### 5. Supporting the open source community diff --git a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md index da9abcce7b..1f4ea8f999 100644 --- a/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md +++ b/translations/ja-JP/content/get-started/quickstart/contributing-to-projects.md @@ -25,7 +25,7 @@ Creating a "fork" is producing a personal copy of someone else's project. Forks This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow. 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife. -2. Click **Fork**. ![[Fork] ボタン](/assets/images/help/repository/fork_button.jpg) +2. Click **Fork**. ![[Fork] ボタン](/assets/images/help/repository/fork_button.png) 1. {% data variables.product.product_name %} will take you to your copy (your fork) of the Spoon-Knife repository. ## Cloning a fork diff --git a/translations/ja-JP/content/get-started/quickstart/create-a-repo.md b/translations/ja-JP/content/get-started/quickstart/create-a-repo.md index 03ccb262cb..3bf4736c79 100644 --- a/translations/ja-JP/content/get-started/quickstart/create-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/create-a-repo.md @@ -34,7 +34,7 @@ topics: {% note %} -**メモ:** オープンソースプロジェクトのパブリックリポジトリを作成できます。 パブリックリポジトリを作成する際は、他のユーザにどのようにプロジェクトを共有してほしいのかを定義する[ライセンスファイル](https://choosealicense.com/)を含めるようにしてください。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +**メモ:** オープンソースプロジェクトのパブリックリポジトリを作成できます。 パブリックリポジトリを作成する際は、他のユーザにどのようにプロジェクトを共有してほしいのかを定義する[ライセンスファイル](https://choosealicense.com/)を含めるようにしてください。 {% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endnote %} diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md index 5612c62f5d..70903d5f60 100644 --- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md @@ -42,7 +42,7 @@ Most commonly, forks are used to either propose changes to someone else's projec 他のユーザのプロジェクトのフォークからパブリックリポジトリを作成する際は、プロジェクトの他者との共有方法を定義するライセンスファイルを必ず含めてください。 詳しい情報については、choosealicense.com の「[オープンソースのライセンスを選択する](https://choosealicense.com/)」を参照してください。 -{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning-lab %} +{% data reusables.open-source.open-source-guide-repositories %} {% data reusables.open-source.open-source-learning %} {% endif %} @@ -57,7 +57,7 @@ If you have not yet, you should first [set up Git](/articles/set-up-git). [Git 上流または元のリポジトリへの変更を提案するために、プロジェクトをフォークする場合があります。 この場合、自分のフォークを上流のリポジトリと定期的に同期させるとよいでしょう。 これには、コマンドラインで Git を使用する必要があります。 先程フォークした同じ [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) リポジトリを使用して、上流リポジトリの設定を練習できます。 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.product.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. -2. ページの右上にある [**Fork**] をクリックします。 ![[Fork] ボタン](/assets/images/help/repository/fork_button.jpg) +2. ページの右上にある [**Fork**] をクリックします。 ![[Fork] ボタン](/assets/images/help/repository/fork_button.png) {% endwebui %} diff --git a/translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md b/translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md index 46c2fb3372..483f9783f1 100644 --- a/translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md +++ b/translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md @@ -1,12 +1,12 @@ --- -title: Git and GitHub learning resources +title: Git と GitHub の学習リソース redirect_from: - /articles/good-resources-for-learning-git-and-github - /articles/what-are-other-good-resources-for-learning-git-and-github - /articles/git-and-github-learning-resources - /github/getting-started-with-github/git-and-github-learning-resources - /github/getting-started-with-github/quickstart/git-and-github-learning-resources -intro: 'There are a lot of helpful Git and {% data variables.product.product_name %} resources on the web. This is a short list of our favorites!' +intro: 'ウェブ上には数多くの役に立つ Git と {% data variables.product.product_name %} のリソースが存在します。 おすすめのものをまとめました。' versions: fpt: '*' ghes: '*' @@ -16,48 +16,49 @@ authors: - GitHub shortTitle: Learning resources --- -## Using Git -Familiarize yourself with Git by visiting the [official Git project site](https://git-scm.com) and reading the [ProGit book](http://git-scm.com/book). You can also review the [Git command list](https://git-scm.com/docs). +## Git を使用する -## Using {% data variables.product.product_name %} +[公式 Git プロジェクトサイト](https://git-scm.com)にアクセスして [ProGit book](http://git-scm.com/book) を読み、Git に慣れましょう。 You can also review the [Git command list](https://git-scm.com/docs). + +## {% data variables.product.product_name %}を使用する {% ifversion fpt or ghec %} -{% data variables.product.prodname_learning %} offers free interactive courses that are built into {% data variables.product.prodname_dotcom %} with instant automated feedback and help. Learn to open your first pull request, make your first open source contribution, create a {% data variables.product.prodname_pages %} site, and more. For more information about course offerings, see [{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}). +{% data variables.product.prodname_learning %} では、即座に自動化されたフィードバックやヘルプとともに、{% data variables.product.prodname_dotcom %} に組み込まれた無料のインタラクティブなコースを提供しています。 最初のプルリクエストをオープンしたり、最初のオープンソースへのコントリビューションを行ったり、{% data variables.product.prodname_pages %} のサイトを作成したりできます。 コースについての詳細は、[{% data variables.product.prodname_learning %}]({% data variables.product.prodname_learning_link %}) をご覧ください。 {% endif %} -Become better acquainted with {% data variables.product.product_name %} through our [getting started](/categories/getting-started-with-github/) articles. See our [{% data variables.product.prodname_dotcom %} flow](https://guides.github.com/introduction/flow) for a process introduction. Refer to our [overview guides](https://guides.github.com) to walk through basic concepts. +[使ってみる](/categories/getting-started-with-github/)という記事を通して、{% data variables.product.product_name %} について理解を深めましょう。 [{% data variables.product.prodname_dotcom %} のフロー](https://guides.github.com/introduction/flow)でプロセスの紹介をご確認ください。 [概要ガイド](https://guides.github.com)を参照して基本的な概念をご覧ください。 {% data reusables.support.ask-and-answer-forum %} -### Branches, forks, and pull requests +### ブランチ、フォーク、プルリクエスト -Learn about [Git branching](http://learngitbranching.js.org/) using an interactive tool. Read about [forks](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) and [pull requests](/articles/using-pull-requests) as well as [how we use pull requests](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github) at {% data variables.product.prodname_dotcom %}. Access references about using {% data variables.product.prodname_dotcom %} from the [command line](https://cli.github.com/). +インタラクティブなツールを使用して、[Git のブランチ](http://learngitbranching.js.org/)について学びましょう。 [フォーク](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)や[プルリクエスト](/articles/using-pull-requests)、および {% data variables.product.prodname_dotcom %} で[プルリクエストがどのように使用されているのか](https://github.com/blog/1124-how-we-use-pull-requests-to-build-github)をお読みください。 [コマンドライン](https://cli.github.com/)から {% data variables.product.prodname_dotcom %} の使用に関するリファレンスにアクセスしてください。 -### Tune in +### 動画 -Our {% data variables.product.prodname_dotcom %} [YouTube Training and Guides channel](https://youtube.com/githubguides) offers tutorials about [pull requests](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19), [forking](https://www.youtube.com/watch?v=5oJHRbqEofs), [rebase](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22), and [reset](https://www.youtube.com/watch?v=BKPjPMVB81g) functions. Each topic is covered in 5 minutes or less. +{% data variables.product.prodname_dotcom %}[YouTube のトレーニングおよびガイドチャンネル](https://youtube.com/githubguides)では、[プルリクエスト](https://www.youtube.com/watch?v=d5wpJ5VimSU&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=19)、[フォーキング](https://www.youtube.com/watch?v=5oJHRbqEofs)、[リベース](https://www.youtube.com/watch?v=SxzjZtJwOgo&list=PLg7s6cbtAD15G8lNyoaYDuKZSKyJrgwB-&index=22)、および[リセット](https://www.youtube.com/watch?v=BKPjPMVB81g)機能についてのチュートリアルを提供しています。 各トピックの所要時間は 5 分以内です。 -## Training +## トレーニング -### Free courses +### 無料コース -{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://lab.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://lab.github.com/githubtraining/introduction-to-github); courses on programming languages and tools such as HTML, Python, and NodeJS; and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. +{% data variables.product.product_name %} offers a series of interactive, [on-demand training courses](https://skills.github.com/) including [Introduction to {% data variables.product.prodname_dotcom %}](https://github.com/skills/introduction-to-github); and courses on {% data variables.product.product_name %} specific tools such as {% data variables.product.prodname_actions %}. -### {% data variables.product.prodname_dotcom %}'s web-based educational programs +### {% data variables.product.prodname_dotcom %}のウェブベース教育プログラム -{% data variables.product.prodname_dotcom %} offers live [trainings](https://services.github.com/#upcoming-events) with a hands-on, project-based approach for those who love the command line and those who don't. +{% data variables.product.prodname_dotcom %} では、生中継の[トレーニング](https://services.github.com/#upcoming-events)を提供しています。コマンドラインの好き嫌いにかかわらず、すべてのユーザに向けたハンズオン、プロジェクトベースのアプローチを紹介しています。 -### Training for your company +### 企業向けトレーニング -{% data variables.product.prodname_dotcom %} offers [in-person classes](https://services.github.com/#offerings) taught by our highly-experienced educators. [Contact us](https://services.github.com/#contact) to ask your training-related questions. +{% data variables.product.prodname_dotcom %} では、経験豊富な教育者による[対面式のクラス](https://services.github.com/#offerings)を提供しています。 トレーニングに関するお問い合わせについては、[こちら](https://services.github.com/#contact)までどうぞ。 -## Extras +## その他 -An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. Feel free to adapt our [.gitignore templates](https://github.com/github/gitignore) to meet your needs. +An interactive [online Git course](https://www.pluralsight.com/courses/code-school-git-real) from [Pluralsight](https://www.pluralsight.com/codeschool) has seven levels with dozens of exercises in a fun game format. [.gitignore テンプレート](https://github.com/github/gitignore)では、お客様のニーズに合わせることができます。 -Extend your {% data variables.product.prodname_dotcom %} reach through {% ifversion fpt or ghec %}[integrations](/articles/about-integrations){% else %}integrations{% endif %}, or by installing [{% data variables.product.prodname_desktop %}](https://desktop.github.com) and the robust [Atom](https://atom.io) text editor. +{% data variables.product.prodname_dotcom %} のリーチを、{% ifversion fpt or ghec %}[インテグレーション](/articles/about-integrations){% else %}インテグレーション{% endif %}、または[{% data variables.product.prodname_desktop %}](https://desktop.github.com) と堅牢な [Atom](https://atom.io) テキストエディタで拡張しましょう。 -Learn how to launch and grow your open source project with the [Open Source Guides](https://opensource.guide/). +[オープンソースのガイド](https://opensource.guide/)で、オープンソースのプロジェクトを立ち上げ成長させる方法をご確認ください。 diff --git a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md index ab9ef1757e..bfda7e2b21 100644 --- a/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md +++ b/translations/ja-JP/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md @@ -134,7 +134,7 @@ Here are some examples for using relative links to display an image. | ----------------------------------------------------------- | ---------------------------------------------------------------------- | | In a `.md` file on the same branch | `/assets/images/electrocat.png` | | In a `.md` file on another branch | `/../main/assets/images/electrocat.png` | -| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png` | +| In issues, pull requests and comments of the repository | `../blob/main/assets/images/electrocat.png?raw=true` | | In a `.md` file in another repository | `/../../../../github/docs/blob/main/assets/images/electrocat.png` | | In issues, pull requests and comments of another repository | `../../../github/docs/blob/main/assets/images/electrocat.png?raw=true` | diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/closing-an-issue.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/closing-an-issue.md new file mode 100644 index 0000000000..971c8b4a82 --- /dev/null +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/closing-an-issue.md @@ -0,0 +1,30 @@ +--- +title: Closing an issue +intro: 'You can close an issue when bugs are fixed, feedback is acted on, or to show that work is not planned.' +permissions: 'Anyone can close an issue they opened.

Repository owners, collaborators on repositories owned by a personal account, and people with triage permissions or greater on repositories owned by an organization can close issues opened by others. {% data reusables.enterprise-accounts.emu-permission-repo %}' +versions: + fpt: '*' + ghes: '*' + ghae: '*' + ghec: '*' +topics: + - Issues + - Project management +shortTitle: Close an issue（Issueのクローズ） +--- + +{% note %} + +**Note:** You can also close issues automatically with keywords in pull requests and commit messages. 詳しい情報については「[プルリクエストのIssueへのリンク](/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword#linking-a-pull-request-to-an-issue-using-a-keyword)」を参照してください。 + +{% endnote %} + +{% data reusables.repositories.navigate-to-repo %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to close. +{%- if issue-close-reasons %} +1. Optionally, to change the reason for closing the issue, select {% octicon "triangle-down" aria-label="The down triangle octicon" %} next to "Close issue" and click a reason. ![Screenshot showing dropdown menu containing issue close reasons](/assets/images/help/issues/close-issue-select-reason.png) +2. Click **Close issue**. ![Screenshot showing "close issue" button](/assets/images/help/issues/close-issue-with-reason.png) +{%- else %} +1. At the bottom of the page, click **Close issue**. ![Screenshot showing "close issue" button](/assets/images/help/issues/close-issue.png) +{% endif %} diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md index d196d10033..d0f86a89a0 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md @@ -175,7 +175,8 @@ Issue およびPull Requestの検索用語により、次のことができま Issueについては、以下も検索に利用できます。 -- クローズしているリファレンス`linked:pr`によってプルリクエストにリンクされているIssueのフィルタリング +- Filter for issues that are linked to a pull request by a closing reference: `linked:pr`{% if issue-close-reasons %} +- Filter issues by the reason they were closed: `is:closed reason:complete` or `is:closed reason:"not planned"`{% endif %} プルリクエストについては、検索を利用して以下の操作もできます。 - [ドラフト](/articles/about-pull-requests#draft-pull-requests)Pull Requestのフィルタリング: `is:draft` diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/index.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/index.md index 17396c36a8..d6d94bbbe4 100644 --- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/index.md +++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/index.md @@ -22,6 +22,7 @@ children: - /marking-issues-or-pull-requests-as-a-duplicate - /pinning-an-issue-to-your-repository - /transferring-an-issue-to-another-repository + - /closing-an-issue - /deleting-an-issue - /planning-and-tracking-work-for-your-team-or-project redirect_from: diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/index.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/index.md index 5de8e43533..44498de820 100644 --- a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/index.md +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/index.md @@ -17,6 +17,7 @@ children: - /filtering-projects - /using-the-api-to-manage-projects - /automating-projects + - /managing-projects - /managing-the-visibility-of-your-projects - /managing-access-to-projects - /using-insights-with-projects diff --git a/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-projects.md b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-projects.md new file mode 100644 index 0000000000..131afe51b7 --- /dev/null +++ b/translations/ja-JP/content/issues/trying-out-the-new-projects-experience/managing-projects.md @@ -0,0 +1,43 @@ +--- +title: Managing projects (beta) +intro: 'You can close and re-open projects, or you can permanently delete projects.' +allowTitleToDifferFromFilename: true +miniTocMaxHeadingLevel: 2 +versions: + fpt: '*' + ghec: '*' +topics: + - Projects + - Organizations +--- + +## Deleting a project + +You can delete a project to permanently remove it. + +{% data reusables.projects.project-settings %} +1. At the bottom of the page, click **Delete this project**. ![Screenshot showing project delete button](/assets/images/help/issues/delete-project-button.png) +1. Read the warnings, then type the name of your project into the text box. ![Screenshot showing project delete confirmation](/assets/images/help/issues/project-delete-confirm.png) +1. Click **I understand the consequences, delete this project**. + +## Closing a project + +You can close a project to remove it from the list of projects but retain the contents and ability to re-open the project later. + +{% data reusables.projects.project-settings %} +1. At the bottom of the page, click **Close this project**. ![Screenshot showing project close button](/assets/images/help/issues/close-project-button.png) + +## Re-opening an organization project + +You can reopen a previously closed project. + +{% data reusables.profile.access_org %} +{% data reusables.user-settings.access_org %} +{% data reusables.projects.reopen-a-project %} + +## Re-opening a user project + +You can reopen a previously closed project. + +{% data reusables.profile.access_profile %} +{% data reusables.projects.reopen-a-project %} diff --git a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md index 07daffb882..5026304d9d 100644 --- a/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md +++ b/translations/ja-JP/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md @@ -42,6 +42,12 @@ OrganizationがSSH証明書を必要としない場合は、メンバーは自 各証明書を発行する際には、その証明書がどの{% data variables.product.product_name %}ユーザー用かを示すエクステンションを指定する必要があります。 たとえば、OpenSSH の`ssh-keygen` コマンドを以下のように使用することができます。_KEY-IDENTITY_ は特定のキー IDに、_USERNAME_ は {% data variables.product.product_name %} ユーザ名に置き換えます。 あなたが生成する証明書は、あなたのOrganizationのリソースに対してそのユーザの代わりに振る舞うことを認可されるようになります。 証明書を発行する前に、そのユーザのアイデンティティを必ず検証してください。 +{% note %} + +**Note:** You must update to OpenSSH 7.6 or later to use these commands. + +{% endnote %} + ```shell $ ssh-keygen -s ./ca-key -V '+1d' -I KEY-IDENTITY -O extension:login@{% data variables.product.product_url %}=USERNAME ./user-key.pub ``` diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md index f5b9453f58..5d0a1ff8c7 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md @@ -137,5 +137,5 @@ When a {% data variables.product.prodname_pages %} site is visited, the visitor' ## Further reading -- [{% data variables.product.prodname_pages %}](https://lab.github.com/githubtraining/github-pages) on {% data variables.product.prodname_learning %} +- [{% data variables.product.prodname_pages %}](https://github.com/skills/github-pages) on {% data variables.product.prodname_learning %} - "[{% data variables.product.prodname_pages %}](/rest/reference/repos#pages)" diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md index 2313a3f966..a1f5af783d 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models.md @@ -23,7 +23,7 @@ In the fork and pull model, anyone can fork an existing repository and push chan {% tip %} -**ヒント：**{% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning-lab %} +**ヒント：**{% data reusables.open-source.open-source-guide-general %} {% data reusables.open-source.open-source-learning %} {% endtip %} diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md index 970bb55b17..9ea57eeba8 100644 --- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md +++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md @@ -72,6 +72,18 @@ shortTitle: Search issues & PRs | `is:open` | [**performance is:open is:issue**](https://github.com/search?q=performance+is%3Aopen+is%3Aissue&type=Issues) は、「performance」という単語があるオープン Issue にマッチします。 | | `is:closed` | [**android is:closed**](https://github.com/search?utf8=%E2%9C%93&q=android+is%3Aclosed&type=) は、「android」という単語があるクローズされた Issue とプルリクエストにマッチします。 | +{% if issue-close-reasons %} +## Search by the reason an issue was closed + +You can filter issues based on the reason given when the issue was closed, using the `reason` qualifier. + +| 修飾子 | サンプル | +| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `reason:complete` | [**libraries is:closed reason:complete**](https://github.com/search?q=libraries+is%3Aclosed+reason%3Acompleted&type=Issues) matches issues with the word "libraries" that were closed as "completed." | +| `reason:"not planned"` | [**libraries is:closed reason:"not planned"**](https://github.com/search?q=libraries+is%3Aclosed+reason%3A%22not+planned%22&type=Issues) matches issues with the word "libraries" that were closed as "not planned." | + +{% endif %} + ## リポジトリの可視性によるフィルタ `is` 修飾子を使用して、Issue とプルリクエストを含むリポジトリの可視性でフィルタできます。 For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)." @@ -125,10 +137,10 @@ shortTitle: Search issues & PRs `involves` 修飾子は、特定のユーザが何らかの方法で関与する Issue を表示します。 `involves` 修飾子は、単一ユーザについて、`author`、`assignee`、`mentions`、および `commenter` を論理 OR でつなげます。 言い換えれば、この修飾子は、特定のユーザが作成した、当該ユーザにアサインされた、当該ユーザをメンションした、または、当該ユーザがコメントした、Issue およびプルリクエストを表示します。 -| 修飾子 | サンプル | -| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** は、@defunkt または @jlord が関与している Issue にマッチします。 | -| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues)は、本文に「bootstrap」という単語を含まず、@mdo が関与している Issue にマッチします。 | +| 修飾子 | サンプル | +| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| involves:USERNAME | **[involves:defunkt involves:jlord](https://github.com/search?q=involves%3Adefunkt+involves%3Ajlord&type=Issues)** は、@defunkt または @jlord が関与している Issue にマッチします。 | +| | [**NOT bootstrap in:body involves:mdo**](https://github.com/search?q=NOT+bootstrap+in%3Abody+involves%3Amdo&type=Issues) matches issues @mdo is involved in that do not contain the word "bootstrap" in the body. | ## リンクされた Issue とプルリクエストを検索する 結果を絞り込んで、クローズしているリファレンスによってプルリクエストにリンクされている、またはプルリクエストによってクローズされる可能性がある Issue にリンクされている Issue のみを表示することができます。 @@ -144,10 +156,10 @@ shortTitle: Search issues & PRs `label` 修飾子を使って、ラベルで検索結果を絞り込むことができます。 Issue は複数のラベルがある可能性があることから、各 Issue について異なる修飾子を記載できます。 -| 修飾子 | サンプル | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) は、Ruby のリポジトリにある「help wanted」のラベルがある Issue にマッチします。 | -| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues)は、「bug」ラベルはないが「priority」ラベルがある、本文に「broken」という単語がある Issue にマッチします。** | +| 修飾子 | サンプル | +| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| label:LABEL | [**label:"help wanted" language:ruby**](https://github.com/search?utf8=%E2%9C%93&q=label%3A%22help+wanted%22+language%3Aruby&type=Issues) matches issues with the label "help wanted" that are in Ruby repositories. | +| | [**broken in:body -label:bug label:priority**](https://github.com/search?q=broken+in%3Abody+-label%3Abug+label%3Apriority&type=Issues) matches issues with the word "broken" in the body, that lack the label "bug", but *do* have the label "priority." | | | [**label:bug label:resolved**](https://github.com/search?l=&q=label%3Abug+label%3Aresolved&type=Issues) matches issues with the labels "bug" and "resolved."{% ifversion fpt or ghes > 3.2 or ghae or ghec %} | | [**label:bug,resolved**](https://github.com/search?q=label%3Abug%2Cresolved&type=Issues) matches issues with the label "bug" or the label "resolved."{% endif %} @@ -155,73 +167,73 @@ shortTitle: Search issues & PRs `milestone` 修飾子は、リポジトリ内の[マイルストーン](/articles/about-milestones)の一部である Issue またはプルリクエストを表示します。 -| 修飾子 | サンプル | -| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues)は、「overhaul」という名前のマイルストーンにある Issue にマッチします。 | -| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues)は、「bug fix」という名前のマイルストーンにある Issue にマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| milestone:MILESTONE | [**milestone:"overhaul"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22overhaul%22&type=Issues) matches issues that are in a milestone named "overhaul." | +| | [**milestone:"bug fix"**](https://github.com/search?utf8=%E2%9C%93&q=milestone%3A%22bug+fix%22&type=Issues) matches issues that are in a milestone named "bug fix." | ## プロジェクトボードで検索 リポジトリまたは Organization にある特定の[プロジェクトボード](/articles/about-project-boards/)と関連する Issue を表示するには、`project` 修飾子を使います。 プロジェクトボードはプロジェクトボード番号で検索する必要があります。 プロジェクトボードの URL の末尾に、プロジェクトボード番号が表示されています。 -| 修飾子 | サンプル | -| -------------------------- | ---------------------------------------------------------------------------------------------- | -| project:PROJECT_BOARD | **project:github/57** は、Organization のプロジェクトボード 57 に関連付けられている、GitHub が所有する Issue にマッチします。 | -| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** は、@github の Linguist リポジトリのプロジェクトボード 1 に関連付けられている Issue にマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ----------------------------------------------------------------------------------------------------------------------- | +| project:PROJECT_BOARD | **project:github/57** matches issues owned by GitHub that are associated with the organization's project board 57. | +| project:REPOSITORY/PROJECT_BOARD | **project:github/linguist/1** matches issues that are associated with project board 1 in @github's linguist repository. | ## コミットステータスで検索 コミットのステータスでプルリクエストをフィルタリングできます。 This is especially useful if you are using [the Status API](/rest/reference/commits#commit-statuses) or a CI service. -| 修飾子 | サンプル | -| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) は、ステータスが pending になっている Go リポジトリにオープンしたプルリクエストにマッチします。 | -| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) は、ステータスが successful になっている body に「finally」という単語があるオープンなプルリクエストにマッチします。 | -| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) は、ステータスが failed になっている 2015 年 5 月にオープンしたプルリクエストにマッチします。 | +| 修飾子 | サンプル | +| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `status:pending` | [**language:go status:pending**](https://github.com/search?utf8=%E2%9C%93&q=language%3Ago+status%3Apending) matches pull requests opened into Go repositories where the status is pending. | +| `status:success` | [**is:open status:success finally in:body**](https://github.com/search?utf8=%E2%9C%93&q=is%3Aopen+status%3Asuccess+finally+in%3Abody&type=Issues) matches open pull requests with the word "finally" in the body with a successful status. | +| `status:failure` | [**created:2015-05-01..2015-05-30 status:failure**](https://github.com/search?utf8=%E2%9C%93&q=created%3A2015-05-01..2015-05-30+status%3Afailure&type=Issues) matches pull requests opened on May 2015 with a failed status. | ## コミット SHA で検索 コミットの特定の SHA ハッシュを知っている場合、その SHA を含むプルリクエストを検索するために使えます。 SHA の構文は、7 字以上であることが必要です。 -| 修飾子 | サンプル | -| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | -| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) は、`e1109ab` で始まるコミット SHA のプルリクエストにマッチします。 | -| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) は、`0eff326d6213c`で始まるコミット SHA のマージされたプルリクエストにマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| SHA | [**e1109ab**](https://github.com/search?q=e1109ab&type=Issues) matches pull requests with a commit SHA that starts with `e1109ab`. | +| | [**0eff326d6213c is:merged**](https://github.com/search?q=0eff326d+is%3Amerged&type=Issues) matches merged pull requests with a commit SHA that starts with `0eff326d6213c`. | ## ブランチ名で検索 元のブランチ (「head」ブランチ) またはマージされるブランチ (「base」ブランチ) でプルリクエストをフィルタリングできます。 -| 修飾子 | サンプル | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) は、クローズされた「change」という単語から始まる名前のブランチから開かれたプルリクエストに一致します。 | -| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) は、`gh-pages` ブランチにマージされるプルリクエストにマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| head:HEAD_BRANCH | [**head:change is:closed is:unmerged**](https://github.com/search?utf8=%E2%9C%93&q=head%3Achange+is%3Aclosed+is%3Aunmerged) matches pull requests opened from branch names beginning with the word "change" that are closed. | +| base:BASE_BRANCH | [**base:gh-pages**](https://github.com/search?utf8=%E2%9C%93&q=base%3Agh-pages) matches pull requests that are being merged into the `gh-pages` branch. | ## 言語で検索 `language` 修飾子により、特定の言語で記述されたリポジトリ内の Issue およびプルリクエストを検索できます。 -| 修飾子 | サンプル | -| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) は、Ruby のリポジトリにあるオープン Issue にマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | +| language:LANGUAGE | [**language:ruby state:open**](https://github.com/search?q=language%3Aruby+state%3Aopen&type=Issues) matches open issues that are in Ruby repositories. | ## コメントの数で検索 You can use the `comments` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax) to search by the number of comments. -| 修飾子 | サンプル | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues)は、コメント数が 100 を超えるクローズした Issue にマッチします。 | -| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues)は、500 から 1,000 までの範囲のコメント数の Issue にマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| comments:n | [**state:closed comments:>100**](https://github.com/search?q=state%3Aclosed+comments%3A%3E100&type=Issues) matches closed issues with more than 100 comments. | +| | [**comments:500..1000**](https://github.com/search?q=comments%3A500..1000&type=Issues) matches issues with comments ranging from 500 to 1,000. | ## インタラクションの数で検索 You can filter issues and pull requests by the number of interactions with the `interactions` qualifier along with [greater than, less than, and range qualifiers](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax). インタラクションの数とは、1 つの Issue またはプルリクエストにあるリアクションおよびコメントの数のことです。 -| 修飾子 | サンプル | -| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | -| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 を超えるプルリクエストまたは Issue にマッチします。 | -| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) は、インタラクションの数が 500 から 1,000 までの範囲のプルリクエストまたは Issue にマッチします。 | +| 修飾子 | サンプル | +| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| interactions:n | [** interactions:>2000**](https://github.com/search?q=interactions%3A%3E2000) は、インタラクションの数が 2,000 を超えるプルリクエストまたは Issue にマッチします。 | +| | [**interactions:500..1000**](https://github.com/search?q=interactions%3A500..1000) matches pull requests or issues with interactions ranging from 500 to 1,000. | ## リアクションの数で検索 @@ -230,7 +242,7 @@ You can filter issues and pull requests by the number of reactions using the `re | 修飾子 | サンプル | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | reactions:n | [** reactions:>1000**](https://github.com/search?q=reactions%3A%3E1000&type=Issues) は、リアクションの数が 1,000 を超える Issue にマッチします。 | -| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) は、リアクションの数が 500 から 1,000 までの範囲の Issue にマッチします。 | +| | [**reactions:500..1000**](https://github.com/search?q=reactions%3A500..1000) matches issues with reactions ranging from 500 to 1,000. | ## ドラフトプルリクエストを検索 ドラフトプルリクエストをフィルタリングすることができます。 For more information, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)." diff --git a/translations/ja-JP/data/features/issue-close-reasons.yml b/translations/ja-JP/data/features/issue-close-reasons.yml new file mode 100644 index 0000000000..b11b389fe7 --- /dev/null +++ b/translations/ja-JP/data/features/issue-close-reasons.yml @@ -0,0 +1,8 @@ +--- +#Issues 6363 +#Closed issue states +versions: + fpt: '*' + ghec: '*' + ghes: '>=3.6' + ghae: 'issue-6363' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml index f4e14e5f74..edac64c05d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/11.yml @@ -8,37 +8,37 @@ sections: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - '{% data variables.product.prodname_ghe_server %}のアップグレード後に、古い設定オプションが残っている場合、MinioのプロセスのCPU使用率が高くなります。' - - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release. - - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time. - - A subset of internal configuration files are more reliably updated after a hotpatch. - - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. + - Management Consolemのプライバシー設定で`TLS 1.0`と`TLS 1.1`の有効化のオプションが表示されていましたが、これらのプロトコルバージョンは以前のリリースで削除されていました。 + - HA環境において、MSSQLのレプリケーション設定には初回の{% data variables.product.prodname_actions %}の有効化のあとに、手作業の追加ステップが必要になることがあります。 + - 内部設定ファイルの一部は、ホットパッチ後にさらに確実に更新されます。 + - '`ghe-run-migrations`スクリプトは、一時的な証明書名を正しく生成するのに失敗することがあります。' - クラスタ環境において、複数のWebノードをまたぐ内部APIの失敗によって、Git LFSの操作が失敗することがありました。 - - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - - In some cluster topologies, webhook delivery information was not available. + - '`gpg --import`を使うpre-receiveフックが、不十分な`syscall`権限のためにタイムアウトしました。' + - 一部のクラスタトポロジーにおいて、webhookの配信情報が利用できませんでした。 - HA設定では、{% data variables.product.prodname_actions %}が以前に有効化されていた場合、レプリカの破棄が失敗します。 - - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. + - 移行の実行中に、Elasticsearchのヘルスチェックが黄色のクラスタのステータスを許しません。 + - ユーザが自分のアカウントをOrganizationに変換した結果作成されたOrganizationが、グローバルなEnterpriseアカウントに追加されませんでした。 - '`ghe-migrator`を使う場合、もしくは{% data variables.product.prodname_dotcom_the_website %}からエクスポートする場合、データがエクスポート中に削除されると実行に長時間かかるエクスポートが失敗します。' - - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - - Links to inaccessible pages were removed. + - '{% data variables.product.prodname_actions %}デプロイメントグラフで、保留中のジョブの連打リンクの際にエラーが表示されます。' + - アクセスできないページへのリンクが削除されました。 - Web UIで2つのコミットの比較から別のところに移動すると、他のページにdiffが保持されます。 - - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. + - TeamをPull Requestのレビュー担当者として追加すると、そのTeamのメンバー数が正しく表示されないことがあります。 - '外部でSCIMグループにょって管理されているメンバーを削除しようとすると、[Remove team membership for a user](/rest/reference/teams#remove-team-membership-for-a-user) API エンドポイントがエラーを返します。' - - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - - The "Site admin mode" link in the site footer did not change state when clicked. + - 大量の休眠ユーザによって{% data variables.product.prodname_github_connect %}の設定が失敗することがあります。 + - サイトアドミンのWeb UIの"Feature & beta enrollments（機能とベータ登録）"ページが誤って利用可能でした。 + - サイトのフッタの"Site admin mode（サイトアドミンモード）"リンクが、クリックされても状態が変化しませんでした。 - '`spokesctl cache-policy rm`コマンドは、`error: failed to delete cache policy`というメッセージで失敗することがなくなりました。' changes: - - Memcached connection limits were increased to better accommodate large cluster topologies. - - The Dependency Graph API previously ran with a statically defined port. - - The default shard counts for cluster-related Elasticsearch shard settings have been updated. - - The “Triage” and “Maintain” team roles are preserved during repository migrations. - - Performance has been improved for web requests made by enterprise owners. + - 大規模なクラスタトポロジーへの対応を改善するため、Memcachedの接続制限が引き上げられました。 + - Dependency Graph APIは、以前は静的に定義されたポートで実行されていました。 + - クラスタ関連のElasticsearchのシャード設定のデフォルトのシャード数が更新されました。 + - Teamロールの“Triage”及び“Maintain”は、リポジトリの移行中に保持されます。 + - Enterpriseのオーナーによって発行されたWebリクエストのパフォーマンスが改善されました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml index 5e3bfa935e..2200503f8f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/12.yml @@ -4,21 +4,21 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. - - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. - - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. + - アップグレードパッケージで高可用性ペアのノードをアップグレードすると、Elasticsearchが不整合な状態になることがあります。 + - 一部のクラスタトポロジでは、コマンドラインユーティリティの`ghe-spokesctl`及び`ghe-btop`の実行が失敗します。 + - パッケージのアップグレードの間に、`elasticsearch-upgrade`サービスが複数回並列に実行されることから、Elasticsearchのインデックスが複製されることがあります。 + - ユーザアカウントをOrganizationに変換する際に、そのユーザアカウントが{% data variables.product.prodname_ghe_server %} Enterpriseアカウントのオーナーだった場合、変換されたOrganizationは誤ってEntepriseオーナーのリストに表示されます。 - OAuth Application IDがマッチするインテグレーションが既に存在する場合、Enterprise Administration REST APIを使った偽装OAuthトークンの作成が正しく動作しませんでした。 changes: - - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. + - 設定の適用の実行を停止させる設定エラーは、設定ログに加えてターミナルにも出力されるようになりました。 - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - '{% data variables.product.prodname_codeql %}スターターワークフローは、{% data variables.product.prodname_actions %}のためのデフォルトのトークンの権限が使われていない場合でも、エラーになりません。' - - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. + - インスタンスで{% data variables.product.prodname_GH_advanced_security %}の機能が有効化されている場合、リポジトリのコントリビューションに対するバッチを処理している際のバックグラウンドジョブのパフォーマンスが改善されました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml index 0b4a2ae5fa..9496bcb5a5 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-2/13.yml @@ -22,6 +22,6 @@ sections: - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/6.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/6.yml index 86348e31c9..60a665e77c 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/6.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/6.yml @@ -9,41 +9,41 @@ sections: bugs: - '{% data variables.product.prodname_dependabot %}を有効にするとき、エラーによって一部のセキュリティアドバイザリが一時的に適用不能になったものとして読まれました。' - '{% data variables.product.prodname_ghe_server %}のアップグレード後に、古い設定オプションが残っている場合、MinioのプロセスのCPU使用率が高くなります。' - - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release. - - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time. - - A subset of internal configuration files are more reliably updated after a hotpatch. - - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. + - Management Consolemのプライバシー設定で`TLS 1.0`と`TLS 1.1`の有効化のオプションが表示されていましたが、これらのプロトコルバージョンは以前のリリースで削除されていました。 + - HA環境において、MSSQLのレプリケーション設定には初回の{% data variables.product.prodname_actions %}の有効化のあとに、手作業の追加ステップが必要になることがあります。 + - 内部設定ファイルの一部は、ホットパッチ後にさらに確実に更新されます。 + - '`ghe-run-migrations`スクリプトは、一時的な証明書名を正しく生成するのに失敗することがあります。' - クラスタ環境において、複数のWebノードをまたぐ内部APIの失敗によって、Git LFSの操作が失敗することがありました。 - - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - - In some cluster topologies, webhook delivery information was not available. - - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - - Repositories would display a non-functional Discussions tab in the web UI. - - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - Links to inaccessible pages were removed. - - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - - Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued. - - LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously. + - '`gpg --import`を使うpre-receiveフックが、不十分な`syscall`権限のためにタイムアウトしました。' + - 一部のクラスタトポロジーにおいて、webhookの配信情報が利用できませんでした。 + - 移行の実行中に、Elasticsearchのヘルスチェックが黄色のクラスタのステータスを許しません。 + - リポジトリは、機能しないディスカッションタブをWeb UIに表示します。 + - ユーザが自分のアカウントをOrganizationに変換した結果作成されたOrganizationが、グローバルなEnterpriseアカウントに追加されませんでした。 + - アクセスできないページへのリンクが削除されました。 + - '{% data variables.product.prodname_actions %}デプロイメントグラフで、保留中のジョブの連打リンクの際にエラーが表示されます。' + - 大量の不要なバックグラウンドジョブがキューイングされたために、一部のインスタンスでCPU使用率が高くなりました。 + - 以前に同期されていなかったGPGキーを同期しようとした際に、LDAPユーザの同期ジョブが失敗します。 - ユーザのPull RequestダッシュボードからPull Requestへのリンクをたどると、リポジトリヘッダがロードされません。 - - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. - - The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group. - - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - - The "Site admin mode" link in the site footer did not change state when clicked. + - TeamをPull Requestのレビュー担当者として追加すると、そのTeamのメンバー数が正しく表示されないことがあります。 + - SCIMグループを通じて外部で管理されているメンバーを削除しようとすると、Teamメンバーシップの削除のAPIエンドポイントがエラーを返します。 + - 大量の休眠ユーザによって{% data variables.product.prodname_github_connect %}の設定が失敗することがあります。 + - サイトアドミンのWeb UIの"Feature & beta enrollments（機能とベータ登録）"ページが誤って利用可能でした。 + - サイトのフッタの"Site admin mode（サイトアドミンモード）"リンクが、クリックされても状態が変化しませんでした。 - '`spokesctl cache-policy rm`コマンドは、`error: failed to delete cache policy`というメッセージで失敗することがなくなりました。' changes: - - Memcached connection limits were increased to better accommodate large cluster topologies. - - The Dependency Graph API previously ran with a statically defined port. - - The default shard counts for cluster-related Elasticsearch shard settings have been updated. - - When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved. - - The “Triage” and “Maintain” team roles are preserved during repository migrations. - - Performance has been improved for web requests made by enterprise owners. + - 大規模なクラスタトポロジーへの対応を改善するため、Memcachedの接続制限が引き上げられました。 + - Dependency Graph APIは、以前は静的に定義されたポートで実行されていました。 + - クラスタ関連のElasticsearchのシャード設定のデフォルトのシャード数が更新されました。 + - '"People"ページでOrganizationのロールによってEnterpriseメンバーをフィルタリングする場合のドロップダウンメニューアイテムのテキストが改善されました。' + - Teamロールの“Triage”及び“Maintain”は、リポジトリの移行中に保持されます。 + - Enterpriseのオーナーによって発行されたWebリクエストのパフォーマンスが改善されました。 known_issues: - '{% data variables.product.prodname_ghe_server %} 3.3にアップグレード後、{% data variables.product.prodname_actions %}が自動起動に失敗することがあります。この問題を解決するためには、アプライアンスにSSHで接続し、`ghe-actions-start`コマンドを実行してください。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - '{% data variables.product.prodname_actions %}のストレージ設定は、"Force Path Style（パススタイルの強制）"が選択されている場合、検証できず{% data variables.enterprise.management_console %}に保存できません。その代わりに、`ghe-actions-precheck`コマンドラインユーティリティで設定しなければなりません。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml index 4d1a28482c..24942ab54b 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/7.yml @@ -4,28 +4,28 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - When a manifest file was deleted from a repository, the manifest would not be removed from the repository's "Dependency graph" page. - - Resolved a regression that could lead to consistent failures to retrieve artifacts and download log archives for {% data variables.product.prodname_actions %}. In some circumstances we stopped resolving URLs for internal communications that used `localhost`, and instead incorrectly used the instance hostname. - - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. - - Rotated log files with the extension `.backup` would accumulate in directories containing system logs. - - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. + - マニフェストファイルがリポジトリから削除されたとき、その目にフェストがリポジトリの"Dependency graph（依存関係グラフ）"ページから削除されません。 + - '{% data variables.product.prodname_actions %}の成果物の取得とログアーカイブのダウンロードの一貫した失敗につながりうるリグレッションが解決されました。環境によっては`localhost`を使った内部的な通信のURLの解決を停止し、その代わりにインスタンスのホスト名を誤って使用していました。' + - アップグレードパッケージで高可用性ペアのノードをアップグレードすると、Elasticsearchが不整合な状態になることがあります。 + - '`.backup`という拡張子を持つローテートされたログファイルが、システムログを含むディレクトリに蓄積されます。' + - 一部のクラスタトポロジでは、コマンドラインユーティリティの`ghe-spokesctl`及び`ghe-btop`の実行が失敗します。 + - パッケージのアップグレードの間に、`elasticsearch-upgrade`サービスが複数回並列に実行されることから、Elasticsearchのインデックスが複製されることがあります。 - Pull Requestとコメントのビューで、リッチdiffがGit LFSによって追跡されている一部のファイルのロードに失敗します。 - - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - - Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed. + - ユーザアカウントをOrganizationに変換する際に、そのユーザアカウントが{% data variables.product.prodname_ghe_server %} Enterpriseアカウントのオーナーだった場合、変換されたOrganizationは誤ってEntepriseオーナーのリストに表示されます。 + - OAuth Application IDがマッチするインテグレーションが既に存在する場合、Enterprise Administration REST APIを使った偽装OAuthトークンの作成はエラーになりました。 - 検出されたシークレットにUTF8文字がある場合、Secret Scanning REST APIがレスポンスコード`500`を返します。 - - Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location. + - データがローカルキャッシュの場所から利用できる場合であっても、リポジトリキャッシュサーバーが非キャッシュの場所からデータを提供することがあります。 changes: - - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. + - 設定の適用の実行を停止させる設定エラーは、設定ログに加えてターミナルにも出力されるようになりました。 - Memcachedで許されている最大よりも長い値をキャッシュしようとするとエラーが生じますが、キーは報告されませんでした。 - - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. + - インスタンスで{% data variables.product.prodname_GH_advanced_security %}の機能が有効化されている場合、リポジトリのコントリビューションに対するバッチを処理している際のバックグラウンドジョブのパフォーマンスが改善されました。 known_issues: - '{% data variables.product.prodname_ghe_server %} 3.3にアップグレード後、{% data variables.product.prodname_actions %}が自動起動に失敗することがあります。この問題を解決するためには、アプライアンスにSSHで接続し、`ghe-actions-start`コマンドを実行してください。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - '{% data variables.product.prodname_actions %}のストレージ設定は、"Force Path Style（パススタイルの強制）"が選択されている場合、検証できず{% data variables.enterprise.management_console %}に保存できません。その代わりに、`ghe-actions-precheck`コマンドラインユーティリティで設定しなければなりません。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml index 7890da2da7..c1502987ca 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-3/8.yml @@ -9,25 +9,25 @@ sections: - 一部のクラスタトポロジーで、`ghe-cluster-status`コマンドが`/tmp`に空のディレクトリを残しました。 - SNMPが誤って大量の`Cannot statfs`エラーメッセージをsyslogに記録しました。 - SAML認証が設定され、ビルトインのフォールバックが有効化されたインスタンスで、ビルトインのユーザがログアウト語に生成されたページからサインインしようとすると、“login”ループに捕まってしまいます。 - - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - '`/stafftools/repositories/:owner/:repo/disk`ページから`git fsck`の出力を見ようとすると、`500 Internal Server Error`で失敗します。' - SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。 - Issueコメントにアップロードされたビデオが適切にレンダリングされません。 - リポジトリページでファイルファインダーを使おうとしたとき、検索フィールド内でバックスペースキーを入力すると、検索結果が複数回リストされ、レンダリングの問題が生じます。 - - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - GitHub Enterprise Importerを使ってリポジトリをインポートしようとすると、プロジェクトのタイムラインイベントが正しく設定されていないことから、一部のIssueのインポートに失敗します。 - '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。' changes: - 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。 - '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。' - Support BundleにはMySQLに保存されたテーブルの行数が含まれるようになりました。 - - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. - - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + - どのリポジトリネットワークでスケジュールされたメンテナンスをオンにするかを判断する際に、到達不能なオブジェクトのサイズはカウントされなくなりました。 + - '[Workflow runs API](/rest/actions/workflow-runs)及び`workflow_run`イベントwebhookのペイロードに、`run_started_at`レスポンスフィールドが含まれるようになりました。' known_issues: - '{% data variables.product.prodname_ghe_server %} 3.3にアップグレード後、{% data variables.product.prodname_actions %}が自動起動に失敗することがあります。この問題を解決するためには、アプライアンスにSSHで接続し、`ghe-actions-start`コマンドを実行してください。' - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - '{% data variables.product.prodname_actions %}のストレージ設定は、"Force Path Style（パススタイルの強制）"が選択されている場合、検証できず{% data variables.enterprise.management_console %}に保存できません。その代わりに、`ghe-actions-precheck`コマンドラインユーティリティで設定しなければなりません。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml index 8235e576bc..14b6ef5c67 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/1.yml @@ -10,41 +10,41 @@ sections: - 複合アクションを使っている場合、ワークフローの実行が完了しないことがあります。 - '{% data variables.product.prodname_dependabot %}を有効にするとき、エラーによって一部のセキュリティアドバイザリが一時的に適用不能になったものとして読まれました。' - '{% data variables.product.prodname_ghe_server %}のアップグレード後に、古い設定オプションが残っている場合、MinioのプロセスのCPU使用率が高くなります。' - - The options to enable `TLS 1.0` and `TLS 1.1` in the Privacy settings of the Management Console were shown, although removal of those protocol versions occurred in an earlier release. - - In a HA environment, configuring MSSQL replication could require additional manual steps after enabling {% data variables.product.prodname_actions %} for the first time. - - A subset of internal configuration files are more reliably updated after a hotpatch. - - The `ghe-run-migrations` script would sometimes fail to generate temporary certificate names correctly. - - Pre-receive hooks that used `gpg --import` timed out due to insufficient `syscall` privileges. - - In some cluster topologies, webhook delivery information was not available. - - The {% data variables.product.prodname_actions %} deployment graph would display an error when rendering a pending job. - - Elasticsearch health checks would not allow a yellow cluster status when running migrations. - - When using the [Migrations API](/rest/reference/migrations), queued export jobs were not processed. - - Repositories would display a non-functional Discussions tab in the web UI. - - Organizations created as a result of a user transforming their user account into an organization were not added to the global enterprise account. - - LDAP user sync jobs would fail when trying to sync GPG keys that had been synced previously. - - Links to inaccessible pages were removed. - - Some instances experienced high CPU usage due to large amounts unnecessary background jobs being queued. - - Empty repositories didnt sync correctly to cache servers. - - Adding a team as a reviewer to a pull request would sometimes show the incorrect number of members on that team. - - The remove team membership API endpoint would respond with an error when attempting to remove member externally managed via a SCIM Group. - - A large number of dormant users could cause a {% data variables.product.prodname_github_connect %} configuration to fail. - - The "Feature & beta enrollments" page in the Site admin web UI was incorrectly available. - - The "Site admin mode" link in the site footer did not change state when clicked. + - Management Consolemのプライバシー設定で`TLS 1.0`と`TLS 1.1`の有効化のオプションが表示されていましたが、これらのプロトコルバージョンは以前のリリースで削除されていました。 + - HA環境において、MSSQLのレプリケーション設定には初回の{% data variables.product.prodname_actions %}の有効化のあとに、手作業の追加ステップが必要になることがあります。 + - 内部設定ファイルの一部は、ホットパッチ後にさらに確実に更新されます。 + - '`ghe-run-migrations`スクリプトは、一時的な証明書名を正しく生成するのに失敗することがあります。' + - '`gpg --import`を使うpre-receiveフックが、不十分な`syscall`権限のためにタイムアウトしました。' + - 一部のクラスタトポロジーにおいて、webhookの配信情報が利用できませんでした。 + - '{% data variables.product.prodname_actions %}デプロイメントグラフで、保留中のジョブの連打リンクの際にエラーが表示されます。' + - 移行の実行中に、Elasticsearchのヘルスチェックが黄色のクラスタのステータスを許しません。 + - '[Migrations API](/rest/reference/migrations)を使う場合、キューイングされたエクスポートジョブが処理されませんでした。' + - リポジトリは、機能しないディスカッションタブをWeb UIに表示します。 + - ユーザが自分のアカウントをOrganizationに変換した結果作成されたOrganizationが、グローバルなEnterpriseアカウントに追加されませんでした。 + - 以前に同期されていなかったGPGキーを同期しようとした際に、LDAPユーザの同期ジョブが失敗します。 + - アクセスできないページへのリンクが削除されました。 + - 大量の不要なバックグラウンドジョブがキューイングされたために、一部のインスタンスでCPU使用率が高くなりました。 + - 空のリポジトリは、キャッシュサーバーに正しく同期されませんでした。 + - TeamをPull Requestのレビュー担当者として追加すると、そのTeamのメンバー数が正しく表示されないことがあります。 + - SCIMグループを通じて外部で管理されているメンバーを削除しようとすると、Teamメンバーシップの削除のAPIエンドポイントがエラーを返します。 + - 大量の休眠ユーザによって{% data variables.product.prodname_github_connect %}の設定が失敗することがあります。 + - サイトアドミンのWeb UIの"Feature & beta enrollments（機能とベータ登録）"ページが誤って利用可能でした。 + - サイトのフッタの"Site admin mode（サイトアドミンモード）"リンクが、クリックされても状態が変化しませんでした。 changes: - - Memcached connection limits were increased to better accommodate large cluster topologies. - - The Dependency Graph API previously ran with a statically defined port. - - The default shard counts for cluster-related Elasticsearch shard settings have been updated. - - The [Migrations API](/rest/reference/migrations) now generates exports of repositories. - - When filtering enterprise members by organization role on the "People" page, the text for the dropdown menu items has been improved. - - The “Triage” and “Maintain” team roles are preserved during repository migrations. - - Using ghe-migrator or exporting from GitHub.com, an export would not include Pull Request attachments. - - Performance has been improved for web requests made by enterprise owners. + - 大規模なクラスタトポロジーへの対応を改善するため、Memcachedの接続制限が引き上げられました。 + - Dependency Graph APIは、以前は静的に定義されたポートで実行されていました。 + - クラスタ関連のElasticsearchのシャード設定のデフォルトのシャード数が更新されました。 + - '[Migrations API](/rest/reference/migrations)がリポジトリのエクスポートを生成するようになりました。' + - '"People"ページでOrganizationのロールによってEnterpriseメンバーをフィルタリングする場合のドロップダウンメニューアイテムのテキストが改善されました。' + - Teamロールの“Triage”及び“Maintain”は、リポジトリの移行中に保持されます。 + - GitHub.comからのエクスポートにghe-migratorを使うと、エクスポートにはPull Requestの添付ファイルが含まれません。 + - Enterpriseのオーナーによって発行されたWebリクエストのパフォーマンスが改善されました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - | diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml index 25c6f1178f..0e4271ac9d 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/2.yml @@ -4,26 +4,26 @@ sections: security_fixes: - パッケージは最新のセキュリティバージョンにアップデートされました。 bugs: - - Resolved a regression that could lead to consistent failures to retrieve artifacts and download log archives for {% data variables.product.prodname_actions %}. In some circumstances we stopped resolving URLs for internal communications that used `localhost`, and instead incorrectly used the instance hostname. - - When a manifest file was deleted from a repository, the manifest would not be removed from the repository's "Dependency graph" page. - - Upgrading the nodes in a high availability pair with an upgrade package could cause Elasticsearch to enter an inconsistent state in some cases. - - Rotated log files with the extension `.backup` would accumulate in directories containing system logs. - - In some cluster topologies, the command line utilities `ghe-spokesctl` and `ghe-btop` failed to run. - - Elasticsearch indices could be duplicated during a package upgrade, due to an `elasticsearch-upgrade` service running multiple times in parallel. - - Repository cache servers could serve data from non-cache locations even when the data was available in the local cache location. - - When converting a user account to an organization, if the user account was an owner of the {% data variables.product.prodname_ghe_server %} enterprise account, the converted organization would incorrectly appear in the enterprise owner list. - - The `/stafftools/users/ip_addresses/:address` page responded with a `500 Internal Server Error` when attempting to display the page for an IPv6 address. - - Creating an impersonation OAuth token using the Enterprise Administration REST API resulted in an error when an integration matching the OAuth Application ID already existed. + - '{% data variables.product.prodname_actions %}の成果物の取得とログアーカイブのダウンロードの一貫した失敗につながりうるリグレッションが解決されました。環境によっては`localhost`を使った内部的な通信のURLの解決を停止し、その代わりにインスタンスのホスト名を誤って使用していました。' + - マニフェストファイルがリポジトリから削除されたとき、その目にフェストがリポジトリの"Dependency graph（依存関係グラフ）"ページから削除されません。 + - アップグレードパッケージで高可用性ペアのノードをアップグレードすると、Elasticsearchが不整合な状態になることがあります。 + - '`.backup`という拡張子を持つローテートされたログファイルが、システムログを含むディレクトリに蓄積されます。' + - 一部のクラスタトポロジでは、コマンドラインユーティリティの`ghe-spokesctl`及び`ghe-btop`の実行が失敗します。 + - パッケージのアップグレードの間に、`elasticsearch-upgrade`サービスが複数回並列に実行されることから、Elasticsearchのインデックスが複製されることがあります。 + - データがローカルキャッシュの場所から利用できる場合であっても、リポジトリキャッシュサーバーが非キャッシュの場所からデータを提供することがあります。 + - ユーザアカウントをOrganizationに変換する際に、そのユーザアカウントが{% data variables.product.prodname_ghe_server %} Enterpriseアカウントのオーナーだった場合、変換されたOrganizationは誤ってEntepriseオーナーのリストに表示されます。 + - IPv6のアドレスのページを表示しようとした場合、`/stafftools/users/ip_addresses/:address`ページは`500 Internal Server Error`を返しました。 + - OAuth Application IDがマッチするインテグレーションが既に存在する場合、Enterprise Administration REST APIを使った偽装OAuthトークンの作成はエラーになりました。 changes: - - Added support for replica domain names that are more than 63 characters. - - Configuration errors that halt a config apply run are now output to the terminal in addition to the configuration log. - - If {% data variables.product.prodname_GH_advanced_security %} features are enabled on your instance, the performance of background jobs has improved when processing batches for repository contributions. + - 63文字以上のレプリカのドメイン名のサポートが追加されました。 + - 設定の適用の実行を停止させる設定エラーは、設定ログに加えてターミナルにも出力されるようになりました。 + - インスタンスで{% data variables.product.prodname_GH_advanced_security %}の機能が有効化されている場合、リポジトリのコントリビューションに対するバッチを処理している際のバックグラウンドジョブのパフォーマンスが改善されました。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - | @@ -74,9 +74,9 @@ sections: 手動でリポジトリメンテナンスタスクを開始するには、影響される各リポジトリについて`https:///stafftools/repositories///network`にアクセスし、Scheduleボタンをクリックしてください。 - - heading: Theme picker for GitHub Pages has been removed + heading: GitHub Pagesのテーマピッカーの削除 notes: - | - The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." + GitHub Pagesのテーマピッカーは、Pagesの設定から削除されました。GitHub Pagesのテーマ設定に関する詳しい情報については「[Jekyllを使ったGitHub Pagesサイトへのテーマの追加(/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)を参照してください。 backups: - '{% data variables.product.prodname_ghe_server %} 3.4は、[バックアップとディザスタリカバリ](/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance)のために、最低でも[GitHub Enterprise Backup Utilities 3.4.0](https://github.com/github/backup-utils)を必要とします。' diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml index a1eb5454e7..b2659090f0 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/3.yml @@ -8,29 +8,29 @@ sections: bugs: - 一部のクラスタトポロジーで、`ghe-cluster-status`コマンドが`/tmp`に空のディレクトリを残しました。 - SNMPがsyslogに大量の`Cannot statfs`エラーメッセージを誤って記録しました。 - - When adding custom patterns and providing non-UTF8 test strings, match highlighting was incorrect. - - LDAP users with an underscore character (`_`) in their user names can now login successfully. + - カスタムパターンを追加し、非UTF8のテスト文字列を提供すると、マッチのハイライトが正しくありませんでした。 + - ユーザ名にアンダースコア（`_`）を持つLDAPユーザは、正常にログインできるようになりました。 - SAML認証が設定され、ビルトインのフォールバックが有効化されたインスタンスで、ビルトインのユーザがログアウト語に生成されたページからサインインしようとすると、“login”ループに捕まってしまいます。 - - After enabling SAML encrypted assertions with Azure as identity provider, the sign in page would fail with a `500` error. - - Character key shortcut preferences weren't respected. - - Attempts to view the `git fsck` output from the `/stafftools/repositories/:owner/:repo/disk` page would fail with a `500 Internal Server Error`. + - アイデンティティプロバイダとしてAzureを使ってSAML暗号化アサーションを有効化したあと、サインインページが`500`エラーで失敗します。 + - キャラクタキーのショートカット設定が用いられませんでした。 + - '`/stafftools/repositories/:owner/:repo/disk`ページから`git fsck`の出力を見ようとすると、`500 Internal Server Error`で失敗します。' - SAML暗号化されたアサーションを利用する場合、一部のアサーションは正しくSSHキーを検証済みとしてマークしませんでした。 - Issueコメントにアップロードされたビデオが適切にレンダリングされません。 - - When using GitHub Enterprise Importer to import a repository, some issues would fail to import due to incorrectly configured project timeline events. + - GitHub Enterprise Importerを使ってリポジトリをインポートしようとすると、プロジェクトのタイムラインイベントが正しく設定されていないことから、一部のIssueのインポートに失敗します。 - '`ghe-migrator`を使う場合、移行はIssueやPull Request内のビデオの添付ファイルのインポートに失敗します。' changes: - 高可用性構成では、Management Consoleのレプリケーションの概要ページが現在のレプリケーションのステータスではなく、現在のレプリケーション設定だけを表示することを明確にしてください。 - - The Nomad allocation timeout for Dependency Graph has been increased to ensure post-upgrade migrations can complete. + - アップグレード後の移行が確実に完了するようにするため、依存関係グラフのためのNomadの割り当てのタイムアウトは長くなりました。 - '{% data variables.product.prodname_registry %}を有効化する場合、接続文字列としてのShared Access Signature (SAS)トークンの利用は現在サポートされていないことを明確にしてください。' - Support BundleにはMySQLに保存されたテーブルの行数が含まれるようになりました。 - - When determining which repository networks to schedule maintenance on, we no longer count the size of unreachable objects. - - The `run_started_at` response field is now included in the [Workflow runs API](/rest/actions/workflow-runs) and the `workflow_run` event webhook payload. + - どのリポジトリネットワークでスケジュールされたメンテナンスをオンにするかを判断する際に、到達不能なオブジェクトのサイズはカウントされなくなりました。 + - '[Workflow runs API](/rest/actions/workflow-runs)及び`workflow_run`イベントwebhookのペイロードに、`run_started_at`レスポンスフィールドが含まれるようになりました。' known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 - Git LFSが追跡するファイル[Webインターフェースからアップロードされたもの](https://github.com/blog/2105-upload-files-to-your-repositories)が、不正にリポジトリに直接追加されてしまいます。 - 同じリポジトリ内のファイルパスが255文字を超えるblobへのパーマリンクを含むIssueをクローズできませんでした。 - - When "Users can search GitHub.com" is enabled with {% data variables.product.prodname_github_connect %}, issues in private and internal repositories are not included in {% data variables.product.prodname_dotcom_the_website %} search results. + - '{% data variables.product.prodname_github_connect %}で"Users can search GitHub.com（ユーザはGitHub.comの検索が可能）" が有効化されたとき、プライベート及びインターナルリポジトリのIssueが{% data variables.product.prodname_dotcom_the_website %}の検索結果に含まれません。' - '{% data variables.product.prodname_registry %}のnpmレジストリは、メタデータのレスポンス中で時間の値を返さなくなります。これは、大きなパフォーマンス改善のために行われました。メタデータレスポンスの一部として時間の値を返すために必要なすべてのデータは保持し続け、既存のパフォーマンスの問題を解決した将来に、この値を返すことを再開します。' - pre-receive フックの処理に固有のリソース制限によって、pre-receive フックに失敗するものが生じることがあります。 - | diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml index 1693194491..022712884f 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0-rc1.yml @@ -13,21 +13,21 @@ intro: | sections: features: - - heading: IP exception list for validation testing after maintenance + heading: メンテナンス後の検証テストのためのIP例外リスト notes: - | - You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." + メンテナンスモードが有効化されている間に、GitHub Enterprise Serverインスタンス上のアプリケーションサービスにアクセスできるIPアドレスの許可リストを設定できるようになりました。許可されたIPアドレスからインスタンスのWebインターフェースにアクセスする管理者は、メンテナンス後及びメンテナンスモードを無効化する前にインスタンスの機能を検証できます。詳しい情報については「[メンテナンスモードの有効化とスケジューリング](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)」を参照してください。 - - heading: Custom repository roles are generally available + heading: カスタムリポジトリロールの一般提供 notes: - | - With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + Organizationは、カスタムリポジトリロールを使用してユーザに付与するリポジトリへのアクセス権限をより細かく制御できるようになりました。詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 - A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository. + カスタムリポジトリロールはOrganizationのオーナーによって作成され、そのOrganization内のすべてのリポジトリに渡って利用できます。それぞれのロールにはカスタムの名前と説明が与えられます。ロールは、40以上の細かな権限のセットから設定できます。いったん作成されると、リポジトリの管理者は自分のリポジトリでカスタムロールを任意のユーザ、Team、外部のコラボレータに割り当てることができます。 - Custom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization. + カスタムリポジトリロールは、Organizationの設定の新しい**Repository roles（リポジトリロール）**タブから作成、表示、編集、削除できます。 - Custom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation. + カスタムリポジトリロールは、GitHub Enterprise ServerのREST APIでも完全にサポートされています。Organization APIを使ってOrganization内のすべてのカスタムリポジトリロールをリストでき、個人やTeamにリポジトリへのアクセスを付与するための既存のAPIは、カスタムリポジトリロールをサポートするために拡張されました。詳しい情報については、REST APIドキュメンテーションの「[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)」を参照してください。 - heading: GitHub Container registry in public beta notes: @@ -336,10 +336,10 @@ sections: - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." - - heading: Theme picker for GitHub Pages has been removed + heading: GitHub Pagesのテーマピッカーの削除 notes: - | - The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." + GitHub Pagesのテーマピッカーは、Pagesの設定から削除されました。GitHub Pagesのテーマ設定に関する詳しい情報については「[Jekyllを使ったGitHub Pagesサイトへのテーマの追加(/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)を参照してください。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml index bd247ccbab..a3b9e039aa 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-5/0.yml @@ -6,21 +6,21 @@ intro: | sections: features: - - heading: IP exception list for validation testing after maintenance + heading: メンテナンス後の検証テストのためのIP例外リスト notes: - | - You can now configure an allow list of IP addresses that can access application services on your GitHub Enterprise Server instance while maintenance mode is enabled. Administrators who visit the instance's web interface from an allowed IP address can validate the instance's functionality post-maintenance and before disabling maintenance mode. For more information, see "[Enabling and scheduling maintenance mode](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)." + メンテナンスモードが有効化されている間に、GitHub Enterprise Serverインスタンス上のアプリケーションサービスにアクセスできるIPアドレスの許可リストを設定できるようになりました。許可されたIPアドレスからインスタンスのWebインターフェースにアクセスする管理者は、メンテナンス後及びメンテナンスモードを無効化する前にインスタンスの機能を検証できます。詳しい情報については「[メンテナンスモードの有効化とスケジューリング](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)」を参照してください。 - - heading: Custom repository roles are generally available + heading: カスタムリポジトリロールの一般提供 notes: - | - With custom repository roles, organizations now have more granular control over the repository access permissions they can grant to users. For more information, see "[Managing custom repository roles for an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)." + Organizationは、カスタムリポジトリロールを使用してユーザに付与するリポジトリへのアクセス権限をより細かく制御できるようになりました。詳しい情報については「[Organizationのカスタムリポジトリロールの管理](/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization)」を参照してください。 - A custom repository role is created by an organization owner, and is available across all repositories in that organization. Each role can be given a custom name, and a description. It can be configured from a set of over 40 fine grained permissions. Once created, repository admins can assign a custom role to any user, team or outside collaborator in their repository. + カスタムリポジトリロールはOrganizationのオーナーによって作成され、そのOrganization内のすべてのリポジトリに渡って利用できます。それぞれのロールにはカスタムの名前と説明が与えられます。ロールは、40以上の細かな権限のセットから設定できます。いったん作成されると、リポジトリの管理者は自分のリポジトリでカスタムロールを任意のユーザ、Team、外部のコラボレータに割り当てることができます。 - Custom repository roles can be created, viewed, edited and deleted via the new **Repository roles** tab in an organization's settings. A maximum of 3 custom roles can be created within an organization. + カスタムリポジトリロールは、Organizationの設定の新しい**Repository roles（リポジトリロール）**タブから作成、表示、編集、削除できます。 - Custom repository roles are also fully supported in the GitHub Enterprise Server REST APIs. The Organizations API can be used to list all custom repository roles in an organization, and the existing APIs for granting repository access to individuals and teams have been extended to support custom repository roles. For more information, see "[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)" in the REST API documentation. + カスタムリポジトリロールは、GitHub Enterprise ServerのREST APIでも完全にサポートされています。Organization APIを使ってOrganization内のすべてのカスタムリポジトリロールをリストでき、個人やTeamにリポジトリへのアクセスを付与するための既存のAPIは、カスタムリポジトリロールをサポートするために拡張されました。詳しい情報については、REST APIドキュメンテーションの「[Organizations](/rest/reference/orgs#list-custom-repository-roles-in-an-organization)」を参照してください。 - heading: GitHub Container registry in public beta notes: @@ -329,10 +329,10 @@ sections: - | The CodeQL runner is deprecated in favor of the CodeQL CLI. GitHub Enterprise Server 3.4 and later no longer include the CodeQL runner. This deprecation only affects users who use CodeQL code scanning in 3rd party CI/CD systems. GitHub Actions users are not affected. GitHub strongly recommends that customers migrate to the CodeQL CLI, which is a feature-complete replacement for the CodeQL runner and has many additional features. For more information, see "[Migrating from the CodeQL runner to CodeQL CLI](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli)." - - heading: Theme picker for GitHub Pages has been removed + heading: GitHub Pagesのテーマピッカーの削除 notes: - | - The theme picker for GitHub Pages has been removed from the Pages settings. For more information about configuration of themes for GitHub Pages, see "[Adding a theme to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)." + GitHub Pagesのテーマピッカーは、Pagesの設定から削除されました。GitHub Pagesのテーマ設定に関する詳しい情報については「[Jekyllを使ったGitHub Pagesサイトへのテーマの追加(/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll)を参照してください。 known_issues: - 新しくセットアップされたユーザを持たない{% data variables.product.prodname_ghe_server %}インスタンスで、攻撃者が最初の管理ユーザを作成できました。 - アップグレードの過程で、カスタムのファイアウォールのルールが削除されます。 diff --git a/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md b/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md index 98456bea22..ac788fb978 100644 --- a/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md +++ b/translations/ja-JP/data/reusables/actions/jobs/section-using-jobs-in-a-workflow-name.md @@ -1 +1 @@ -Use `jobs..name` to a name for the job, which is displayed on {% data variables.product.prodname_dotcom %}. +Use `jobs..name` to set a name for the job, which is displayed in the {% data variables.product.prodname_dotcom %} UI. diff --git a/translations/ja-JP/data/reusables/getting-started/learning-lab-enterprise.md b/translations/ja-JP/data/reusables/getting-started/learning-enterprise.md similarity index 63% rename from translations/ja-JP/data/reusables/getting-started/learning-lab-enterprise.md rename to translations/ja-JP/data/reusables/getting-started/learning-enterprise.md index dfd8d34d5c..dde4115e6e 100644 --- a/translations/ja-JP/data/reusables/getting-started/learning-lab-enterprise.md +++ b/translations/ja-JP/data/reusables/getting-started/learning-enterprise.md @@ -1,3 +1,3 @@ -Your enterprise members can learn new skills by completing fun, realistic projects in their very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +Your enterprise members can learn new skills by completing fun, realistic projects in their very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." diff --git a/translations/ja-JP/data/reusables/getting-started/learning-lab.md b/translations/ja-JP/data/reusables/getting-started/learning.md similarity index 66% rename from translations/ja-JP/data/reusables/getting-started/learning-lab.md rename to translations/ja-JP/data/reusables/getting-started/learning.md index 569109de48..ac8bd20546 100644 --- a/translations/ja-JP/data/reusables/getting-started/learning-lab.md +++ b/translations/ja-JP/data/reusables/getting-started/learning.md @@ -1,3 +1,3 @@ -You can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://lab.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by the friendly Learning Lab bot. +You can learn new skills by completing fun, realistic projects in your very own GitHub repository with [{% data variables.product.prodname_learning %}](https://skills.github.com/). Each course is a hands-on lesson created by the GitHub community and taught by a friendly bot. For more information, see "[Git and {% data variables.product.prodname_dotcom %} learning resources](/github/getting-started-with-github/quickstart/git-and-github-learning-resources)." diff --git a/translations/ja-JP/data/reusables/open-source/open-source-learning-lab.md b/translations/ja-JP/data/reusables/open-source/open-source-learning.md similarity index 100% rename from translations/ja-JP/data/reusables/open-source/open-source-learning-lab.md rename to translations/ja-JP/data/reusables/open-source/open-source-learning.md diff --git a/translations/ja-JP/data/reusables/projects/create-project.md b/translations/ja-JP/data/reusables/projects/create-project.md index 599aac8e74..9225865198 100644 --- a/translations/ja-JP/data/reusables/projects/create-project.md +++ b/translations/ja-JP/data/reusables/projects/create-project.md @@ -1,5 +1,8 @@ 1. {% data variables.product.prodname_dotcom %}で、Organizationのメインページにアクセスしてください。 -2. {% octicon "table" aria-label="The project icon" %} **Projects（プロジェクト）**をクリックしてください。 -3. **New project（新規プロジェクト）**ドロップダウンメニューを選択して、**New project (Beta)（新規プロジェクト ベータ）**をクリックしてください。 +1. {% octicon "table" aria-label="The project icon" %} **Projects（プロジェクト）**をクリックしてください。 +1. **New project（新規プロジェクト）**ドロップダウンメニューを選択して、**New project (Beta)（新規プロジェクト ベータ）**をクリックしてください。 ![新規プロジェクト](/assets/images/help/issues/new_project_beta.png) +1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. + + ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/create-user-project.md b/translations/ja-JP/data/reusables/projects/create-user-project.md index 47aff4eb6e..0d8d8c9bcd 100644 --- a/translations/ja-JP/data/reusables/projects/create-user-project.md +++ b/translations/ja-JP/data/reusables/projects/create-user-project.md @@ -1,4 +1,7 @@ 1. On any {% data variables.product.product_name %} page, click on your avatar, then select **Your projects**. -2. **New project（新規プロジェクト）**ドロップダウンメニューを選択して、**New project (Beta)（新規プロジェクト ベータ）**をクリックしてください。 +1. **New project（新規プロジェクト）**ドロップダウンメニューを選択して、**New project (Beta)（新規プロジェクト ベータ）**をクリックしてください。 ![新規プロジェクト](/assets/images/help/issues/new_project_beta.png) +1. When prompted to select a template, click a template or, to start with an empty project, click "Table" or "Board". Then, click **Create**. + + ![Screenshot showing template selection modal](/assets/images/help/issues/projects-select-template.png) \ No newline at end of file diff --git a/translations/ja-JP/data/reusables/projects/reopen-a-project.md b/translations/ja-JP/data/reusables/projects/reopen-a-project.md new file mode 100644 index 0000000000..e2ab9ab140 --- /dev/null +++ b/translations/ja-JP/data/reusables/projects/reopen-a-project.md @@ -0,0 +1,6 @@ +1. Click the **Projects** tab. ![Screenshot showing project close button](/assets/images/help/issues/projects-profile-tab.png) +1. To show closed projects, click **Closed**. ![Screenshot showing project close button](/assets/images/help/issues/closed-projects-tab.png) +1. Click the project you want to reopen. +1. In the top-right, click {% octicon "kebab-horizontal" aria-label="The menu icon" %} to open the menu. +1. In the menu, to access the project settings, click {% octicon "gear" aria-label="The gear icon" %} **Settings**. +1. At the bottom of the page, click **Re-open project**. ![Screenshot showing project re-open button](/assets/images/help/issues/reopen-project-button.png) \ No newline at end of file diff --git a/translations/ja-JP/data/variables/product.yml b/translations/ja-JP/data/variables/product.yml index 7047df9b68..3698f89ef9 100644 --- a/translations/ja-JP/data/variables/product.yml +++ b/translations/ja-JP/data/variables/product.yml @@ -105,12 +105,12 @@ prodname_advanced_security: 'Advanced Security' prodname_codespaces: 'Codespaces' prodname_github_codespaces: 'GitHub Codespaces' prodname_serverless: 'web-based editor' -#GitHub resources: blog, jobs, Learning Lab +#GitHub resources: blog, jobs, skills prodname_gcf: 'GitHub Community Support' prodname_blog: 'GitHub ブログ' prodname_jobs: 'GitHub Jobs' -prodname_learning: 'GitHub Learning Lab' -prodname_learning_link: 'https://lab.github.com/' +prodname_learning: 'GitHub Skills' +prodname_learning_link: 'https://skills.github.com/' prodname_roadmap: 'GitHubパブリックロードマップ' prodname_roadmap_link: 'https://github.com/github/roadmap#github-public-roadmap' #GitHub support diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index ba973b1a09..2104e8a8fe 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -166,7 +166,6 @@ translations/ja-JP/content/get-started/getting-started-with-git/updating-credent translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,Listed in localization-support#489 translations/ja-JP/content/get-started/learning-about-github/about-github-advanced-security.md,rendering error translations/ja-JP/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md,broken liquid tags -translations/ja-JP/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags translations/ja-JP/content/get-started/using-github/github-mobile.md,broken liquid tags translations/ja-JP/content/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists.md,broken liquid tags translations/ja-JP/content/issues/tracking-your-work-with-issues/planning-and-tracking-work-for-your-team-or-project.md,broken liquid tags @@ -273,9 +272,9 @@ translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liqui translations/ja-JP/data/reusables/education/apply-for-team.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/actions-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,Listed in localization-support#489 -translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,broken liquid tags +translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,rendering error translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,Listed in localization-support#489 -translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,broken liquid tags +translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,rendering error translations/ja-JP/data/reusables/enterprise-accounts/pages-tab.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags From 8ed5b4fa4646f818e9e0f395fa041c4e5ebe2f3b Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Tue, 7 Jun 2022 02:31:32 +0000 Subject: [PATCH 4/8] update search indexes --- lib/search/indexes/github-docs-3.1-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.5-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 80 files changed, 160 insertions(+), 160 deletions(-) diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index a75a3f8f97..5645b3f8a4 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5b2efdfd07eb13b06304ad4cfd7ad5bf0123e80af3e121a9b89aacb0aefb0af5 -size 740907 +oid sha256:20ffb85e5201436f80959ca72d60298fe1241d6f5697151a8db31f740d8d924b +size 740692 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index 9a0f90fa85..1208b21812 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a22a53a4485fd3001a33770af909deaeae56ebefcedd89231c654ea550e1c0c6 -size 1563760 +oid sha256:fc899b90a30dfd824e987c9676e3eb66faf13763712faa7925c82d4aba6890ba +size 1564083 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 2949310ebf..cf285cacee 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d8135bdbd3e0a9527d6f754c2642b3f45e9792b7e7e6c4ff7d00ff55d6adbbf4 -size 997459 +oid sha256:ee25c7e6452a6bb9a5a05008e81dd0f05565c8d58b7b31078fdd4ded11455be3 +size 997655 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index 519f2d7e73..ad5e99a97f 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3835b7b241041284a4309e8ba6b4d417a70d8a7c45dea79dbff1db73d0d32e4e -size 3997252 +oid sha256:e214d64ce459d2118d422ee097441ee48c55ff2d476083fe205e88bbd640ac4b +size 3997932 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index e2d9f3dae5..7a4c1ca1be 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6165a84d6b4e5c93763477e7fc95e60e630ede887ed308767dcee3e23042d305 -size 683787 +oid sha256:f3ee885ff2104791c88613957604603b45290f0226488f9689f11600258b3c42 +size 683866 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index 1e13923a9e..fdeed102c7 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6a2e7374d671a8122817a84b736f0a16f3aed5e333e874a7bf8bcec463b12809 -size 2974393 +oid sha256:a2de372f5833cd9276d023a69c4b384fceab6f05e116b927480925864f079f6b +size 2975436 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 576802d6d4..1027bb2174 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1cfeaa0609b714a9fa014dac3ffc21f2040e92b5dd189c6b9106d5b7208d4f69 -size 750221 +oid sha256:ed22f99112dc02d3bf8a0b0374a5d8b4fe71c87e82f31085309564845c8db868 +size 750334 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index cd67e379ed..aa5600eee3 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:35f685b2df8bfc1076b61aecbbee117db0554bec89396b7d0356ededeaa5ec5d -size 4130683 +oid sha256:df7323066cee0a2390fc2228ab28218f8b1ffee56fc93127071f46729713f26f +size 4131949 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index 1032e064fc..bd30349814 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:196353bdd0ff1053d2765aeecff4f50dc01bf6aedc4b28af3868fae6d2c14c86 -size 674502 +oid sha256:e66c2d43b46ca74ce7dd32aab6354f32b898e39026821a3c6ca3418ebd7fc936 +size 674451 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 79b719ef98..f0f9d8ff10 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0d3166a85c7864b7e153cfe33ffc492116a37535d8edabfe7c3b76354571251a -size 2879153 +oid sha256:08c893c345ac8aa599bd1e00268f405a9d216d18ecd9a1dd0f6f2f543a879dd8 +size 2877089 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index b7a12f8f1c..df669ea745 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:38c48d93cc91bbb7d3a98779458b50bb09782f3d1805c25822fd37fe0277ffa1 -size 762402 +oid sha256:be24306dafa25cf4f50e19e795ec00fb479f9c1a8358cc0084ad2a57b6969ab8 +size 762263 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 81a7ead30e..349e529f05 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e8e8fabe100797dd3e6144de35a0fe483db73061f9823598377c520b7fc16b07 -size 1603082 +oid sha256:a1d9b9ef0ab9cd88e14980c9a96fe090aec189cfb27de1027793307e22b25a3e +size 1602936 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 279cba6c58..9cd2c838fd 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:09c62c71f67598c0a5d80c076c8df748073a373104417c19b001c5f111ff152d -size 1034022 +oid sha256:2d847b3caac3d1656ba426736ed6fbcf714bba82f6fe29cee5e7eae3fcd52e27 +size 1034124 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 7e2b573dda..28549e0362 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d3646fb41352518ccf7e72bebd5fe1b2c84a890005b33cadee355573ea34f108 -size 4151019 +oid sha256:0ab3bcb9f0989aa61387438f9eabeba2eb272cb709a052ed0681a6078b32d633 +size 4151034 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index 48e82f2a8f..07814ae4c4 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:87c5ed287d461686309299e89a0e53ef1568076838013788d862ce909999733c -size 703533 +oid sha256:be5dd6b9007422b06723d550d9b1f7d60e3b838a947c546828ff381967bf009c +size 703832 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 9833c59d95..9e83f2e32f 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1c02a7ef5d175bac097ccf9318e5c731d5eaa53bbcc5ad3764b648c6034b2e30 -size 3060977 +oid sha256:88f27b61e99b4e410a4a27f994e0e684ba4a09be867dea8b862b65cf9542e117 +size 3062656 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index be06da5666..a683bda8d4 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bc93d0b9acbd66d66b79fa76e4227c07e128b8a4ac5d36cdad29a09dab432b16 -size 771108 +oid sha256:fd07d7c77a1cc91c80be982e25953dcbdfe2d2f51967f41cd08e49db27d960c2 +size 771191 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index a255b6eca5..42ae39ac20 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5b52389966b9a6b944e686f4accc5076078bc0e9f18b9154fc1f8c7f468676d2 -size 4248049 +oid sha256:5dfff17e8aa3732b28d230033d90d02f80d0a04b31107c3f467b12fc82206762 +size 4249327 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 1cf212724b..f0a1237c63 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:cb335a6e08bd857ea8248a86331ef4f1c95f6fad29dafc024d30f902fc1bbb9f -size 694077 +oid sha256:6bb35e1313d1dc193b2c8b5a3ed21abc7dbdeabda3a52637185e20ba15c34bd9 +size 693892 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index a74542c9e3..43d5e50c42 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:15692fc33c49d612137b74ac013298636f85189861bc4ac73bd1def860c7e559 -size 2960645 +oid sha256:3bb43c17a88beb262d51a2c340514c7258d400e62c41d5a48baf6b735eaf9516 +size 2957848 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 43a8c6a54b..cd4ebb8967 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:088d9f54d6588700cf0ac1eae542275ac3faca3b141e490d07d6608e4a6f47de -size 785850 +oid sha256:f57a5b2bbb14a02b8bc8ac936aeee123bb5b0ed9e5b923d7f7c72b0373bfb4df +size 785657 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 8a16407556..f6b5173958 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f5ab3bda5b662ae7241836de9d0fbcfd61f3ab1f200987f46b76737d98155161 -size 1645236 +oid sha256:5e5634753acc889018f1f153330fc959253cc855e3759595342a7fcd425c8a9b +size 1644883 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index 1daab6fd0a..d98b57df44 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a7f6471e689346ab5aa4ae2d4597956e3be614527fe870cc94381953bc633fde -size 1068920 +oid sha256:10dc4e0185f821d9673b21cdd00dca1ae9089cffb73edd9ac45803964e777f5e +size 1068966 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 2f266df4f9..f6b6c10b96 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:66f48c86b33fd148a5dbdc43cc02a7c4153d2e27fe57e0a8fc15623e96377778 -size 4246305 +oid sha256:dc591c222932880adb7e758dbf2c4b3bd80bc9b41341e68a8ec3faf1f4d3605e +size 4246281 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 03c8218598..07317a2931 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0845f55592ad8b2481a10d863f25b567dcb98caeed9e3652747e31803e54bf51 -size 723296 +oid sha256:57f559f88a2988813136f203ad96e96f5388652fcddf4090279cca6744b599e0 +size 723340 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index 5c9cc3d7d2..5eed91edf2 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f9bb627fa9aae4cafbc5f3fd3eabe6834394c0abe9f8407acc427d31af9cd482 -size 3141694 +oid sha256:a649b7b2db6de94e994b6970646fce3f4d5fbe9407fbee46b3f75075e625b9ac +size 3142267 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 92bf9229d6..f9641d53ae 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:35b32152cd891077394028f98f7151858e884f0779677fa388b5dc90abcc16f1 -size 794726 +oid sha256:5b4b8b57352cc92bf0637f6e9264fca270584da37998cbb84ec42c6066dbcb77 +size 794654 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index b39e939024..3099aa56b1 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:110adc7641fa206be3955012640ca4d6777634b51a17fd70cfae8420ba03dd8d -size 4367816 +oid sha256:84ebfb4f4dd19b9f9cfcf29fa47a46086c79b7331caf613ec9764df4cbb4a31c +size 4367880 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index 517a517ea4..b6a0761db8 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bb0a11a9d883e94ef048306263e6e93d19b4e5afda005397678197aa06917064 -size 713510 +oid sha256:96a39820e15ce4020d689b8b14caedb9bd2bfbac943dd39e20b9c306988eeeee +size 713280 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 716f11f01f..737b551b3d 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7f03ba2893b637e5161f99f30e97dce03993c4508e174c6056c3925c0ca1e252 -size 3039168 +oid sha256:b47d05c61c3255428466bb57da9540d72824a4acf7a035074080eb714b10df0d +size 3036012 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 2599ff7922..7e96d9da49 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:97f14986aaf351750e8c90995dd14d5a4c54dcc900ff56668df25e8ffd3ce6d3 -size 787582 +oid sha256:33d384d6c0af91d36cec95b317b070a5bd02662374cd12b3beeb44877daa0dcb +size 787498 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index 16629af20b..f3d5b74dae 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:23488ec40a300baab8776c6d1324fcc18ea04c8c200d57946e356ef4f020f775 -size 1655806 +oid sha256:99e0012e67165215fe29f416873257a1fddca6fbb982fbd18fa876cb60ce4f2c +size 1655876 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index df6b936674..60e6891021 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:de5d08b54682c90bd397a2486b3f730ce4e3ebb375e5b03ddc828241782b0a59 -size 1077148 +oid sha256:7b985cb45ec396c18e34e86fa7ca02bf05d77b276f80e408950b107d89b26fe6 +size 1076926 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index 9e32d40f51..68a8b1e4b2 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8d42fb52400d0beb73f9f41a23950789aab160306ff535eee009bb9ec17500cd -size 4287172 +oid sha256:6c0f473167d120201bde16322b10cbf8d95da07fc0ef21df8456d7b8ab9709fe +size 4286047 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index 8d4c169e85..4d89a479ae 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:89ad439587cb523e114eca2f41dd64cd3099c5b7859a5f04af8cab48e046b8c1 -size 726670 +oid sha256:60d5808e2f0f25b92fcb7c01df60b4c56ada32dbcd15bb19ee9a3b9720ef41bb +size 726661 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index 9bdc10422c..dd01407fa3 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0ecb4a8dfad767a6623401504462c73ba7addc82c20c9bb94c2e7aba4c062156 -size 3160326 +oid sha256:fbbf979ed24913281ebf41e3e6b459e1d700306218941a855c4c99652321216c +size 3160846 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index 7780b37d47..b5123fbf26 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f857093a69b57c3ce16a65c78d93caf52a6b6156dbe9da76444a8c6050c2d6ea -size 797206 +oid sha256:f17fff52a1d36b2368d33981e876140ecb2ba911a620b2e9482d4d593113a829 +size 797203 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 1b14d5582a..23d03f42fd 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:224e7656116c71b5fb56e89046993be803f4a43d846dc82195d9028cd76a8b98 -size 4390191 +oid sha256:198994e99278bc67a2c185a4068ef09ae376ac95b3fdb3711ae68ff3e2273dc7 +size 4391404 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index ae241b83ea..89a1d74484 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7c9d2560b1670ba22963abcf828fcc8398b25d628bee62e2a71a25aaf1961958 -size 716853 +oid sha256:99c2cacd9c84affb41616e1880459f7e42eb11610f7c1e81b9cf8df3f56b04c2 +size 716671 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index ecaf3f6e71..44a8a4408b 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d6d51ee560187354609dc1b04135d315262ba97fe2f874abc2da641008116572 -size 3058571 +oid sha256:1454b4a43bb7c9a69816f3ed1730e0e69e55dcff79d2d85545ea58ea5a154d00 +size 3055472 diff --git a/lib/search/indexes/github-docs-3.5-cn-records.json.br b/lib/search/indexes/github-docs-3.5-cn-records.json.br index e9796cfa95..00fa6942ca 100644 --- a/lib/search/indexes/github-docs-3.5-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.5-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1efc4e8c4529b5d432fe3edb15fcd8b3d645bd6a57ef262be9f73ef8451a8088 -size 815722 +oid sha256:3092d225806b9594ea23e798e58d29e7de168d736877e69cc48650ab6bd1d48f +size 815571 diff --git a/lib/search/indexes/github-docs-3.5-cn.json.br b/lib/search/indexes/github-docs-3.5-cn.json.br index bff30d97cc..93441e4f3a 100644 --- a/lib/search/indexes/github-docs-3.5-cn.json.br +++ b/lib/search/indexes/github-docs-3.5-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4537a6968d23a207e7d03e35250d1e6736e3172b032a3afd52c1d031ffce40a3 -size 1723883 +oid sha256:2f89bf2a1fd4e6bd05dd3e1942b7a51ac05d71b0f84430f0bc99ca22dc640c45 +size 1723450 diff --git a/lib/search/indexes/github-docs-3.5-en-records.json.br b/lib/search/indexes/github-docs-3.5-en-records.json.br index c849db446d..ba887c5c38 100644 --- a/lib/search/indexes/github-docs-3.5-en-records.json.br +++ b/lib/search/indexes/github-docs-3.5-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d65c947789b3e0eaa711f063a9e024fb889532139e170b7372721937f4e89604 -size 1116299 +oid sha256:d14fad9b4cfd275cc5e7aa2a2e1e61147916eaaed4327bbbc921cc9d83c31aa9 +size 1116354 diff --git a/lib/search/indexes/github-docs-3.5-en.json.br b/lib/search/indexes/github-docs-3.5-en.json.br index 94a6b2416b..7a8ecd868b 100644 --- a/lib/search/indexes/github-docs-3.5-en.json.br +++ b/lib/search/indexes/github-docs-3.5-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:818fc88d79e422fb2805578e6148b6717e09e675f3252ac4ba41c4cf55edcfdc -size 4444428 +oid sha256:68f0096709f6d664e0b85ecfce794e2b04b568ca7e83e86c2232d8cd4b454daf +size 4444042 diff --git a/lib/search/indexes/github-docs-3.5-es-records.json.br b/lib/search/indexes/github-docs-3.5-es-records.json.br index bb31c13a1d..71cf511f2e 100644 --- a/lib/search/indexes/github-docs-3.5-es-records.json.br +++ b/lib/search/indexes/github-docs-3.5-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3efa32caf1d1028b0df56c873b12e60f5525cca9520954238be28c6102ca104b -size 749304 +oid sha256:eeb9a33d9bdb1203e9cedb0bebcd15b57e102686c6813fd58898addc64c23042 +size 749613 diff --git a/lib/search/indexes/github-docs-3.5-es.json.br b/lib/search/indexes/github-docs-3.5-es.json.br index a127b65597..d2861710dd 100644 --- a/lib/search/indexes/github-docs-3.5-es.json.br +++ b/lib/search/indexes/github-docs-3.5-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0e95c72a54d2eae9fd4f61f225cc65d0e36214db005ee29c3eddc5655d7b4662 -size 3273807 +oid sha256:5201426ef5184868298f23daabc584558c911d48dd7e5336dcf34c0ff28e0f47 +size 3274870 diff --git a/lib/search/indexes/github-docs-3.5-ja-records.json.br b/lib/search/indexes/github-docs-3.5-ja-records.json.br index 117705728f..858f4b9380 100644 --- a/lib/search/indexes/github-docs-3.5-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.5-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:68d5baef17a8dc385969f593690feab0316be4b24c75043ba1d49a572018cf51 -size 822470 +oid sha256:466127cdbbb9fa704523b234327f67e15dc3f1b6eaba2a5189a5de88c07b07b2 +size 822476 diff --git a/lib/search/indexes/github-docs-3.5-ja.json.br b/lib/search/indexes/github-docs-3.5-ja.json.br index 3a730cde1a..27b922035a 100644 --- a/lib/search/indexes/github-docs-3.5-ja.json.br +++ b/lib/search/indexes/github-docs-3.5-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:613952f59f34b552f9a06e23145fcbddb17d8f36b0e55596780b7966f5ccdfec -size 4549241 +oid sha256:e828a7a1653a5dccac8b62f918b499cf57ecd30091569fe901162b231bdfbdbd +size 4549166 diff --git a/lib/search/indexes/github-docs-3.5-pt-records.json.br b/lib/search/indexes/github-docs-3.5-pt-records.json.br index 2de036a1af..8fa2688b66 100644 --- a/lib/search/indexes/github-docs-3.5-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.5-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:975282e4ca84a7c9a95854718ba26a35ebce45f8ab42a6f4b4f89bd97ad103d8 -size 739050 +oid sha256:da029acaa9bfe1d686f5f6244b3522aead83d7fcf04a8b0bd7c032494a8adf6f +size 738584 diff --git a/lib/search/indexes/github-docs-3.5-pt.json.br b/lib/search/indexes/github-docs-3.5-pt.json.br index 4da941b1a7..c604eaa2b1 100644 --- a/lib/search/indexes/github-docs-3.5-pt.json.br +++ b/lib/search/indexes/github-docs-3.5-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:98e6720d49ca5c737409abc4bd5dfc732a4f4f2429bab3948a34c3c815c681a6 -size 3165182 +oid sha256:9910e4e6413c9505c5bc1f9a62bef2c7a60efa22e41a9818c9fcfaad8e109a02 +size 3162226 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 3d138b7e19..4b7ee6499e 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:01da91a31954468565c16578bff8e8cbe8c76fe6d8cd0e7af4930c2e80a56f29 -size 980544 +oid sha256:c8a2cc13ae594761bab0a7210875477faa4d67fd4fd305813ec301d52f1a2905 +size 981958 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index 6331a89b5b..4dc0cf0936 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1dcf939f841f3c680f12b306cbee628dcaaa0680ea3067b7a5b4f38795ad5c80 -size 1714356 +oid sha256:68170fd7ae484299ba626ae607ba6cdf7dfa70637318a854c9c529a8c585a92f +size 1714481 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index e6075242f7..933de17aaf 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c921b3bf0b9381b18da914b4120bcb74550f1b118f7e3117d883a4f3ae20f83c -size 1343780 +oid sha256:6a10337b52a390a41bcfd7ff8e40e7b622117dc750d5e552c1e12d27bf54189f +size 1344431 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 763e7aa858..d33e6a0162 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3ec8363907d7efa2f97b49baa72e82d3015ac38a066fcbb41bd495ce9e0765fe -size 5073196 +oid sha256:9b1de8898450876c173f613cb4c046733390f468edef56c65fe09496b7788b78 +size 5075467 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index ef4571f704..a5f02c52a1 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:84d0d89572be6585f032a5f9936b2b0a566a0aae5256192d1368d18e95bbb52d -size 885668 +oid sha256:5a2c2b75101870350dadc010e3463f08233b0bf5d58ab85c45466fce48c52454 +size 886041 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 1d80ad8f98..b4dbf98017 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e462f411f9f3c4b67a2a721a893727039dc830c809fdc1652826eff8c443c6df -size 3674914 +oid sha256:c90a2bef78b89d09ecf6ef6d6a39441d75b9138d4a3960102bbbed92ee6e5fe8 +size 3678048 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index 5b3209623c..91abeaa389 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8cbfc9594d5fe45b4100fb3f95eb0564eecbc4e655b5691dceda0d329271daf3 -size 984441 +oid sha256:d351051d73a6f03ba0229d4eff2445d8ec2ebec87a5555aaf8a11c206e128d77 +size 984687 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 3698f47234..8aa315e3c6 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ecc832c9d1f1c383d9f25a87f46a6cbfd16dd4927f121671a04106461f494677 -size 5217489 +oid sha256:97f4ba10b67cd18c72d99974b48cc2d6a1dd5ed62255bfdbf93bfe4a1cc05f17 +size 5219949 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index ce6360531a..b0d1918c22 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c47bdba106f2050894d525948d8821119626f17bbdba3934e66edd7b5adfd50d -size 873867 +oid sha256:5b27582bde57c7819c95c9b5d5b00b810e1f726049acca3ab7b25a219012b1f7 +size 873585 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index bae577c8f9..acd0af9ea6 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2516528455c3ff1145c5e8e84ab088ff6a73771b7b827fba51fc8dfbd533437a -size 3573086 +oid sha256:fc67bf434f946c641dd10a700766cf96f712709960aa000584d7f5b85318c24c +size 3570705 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 89e2586c89..c217646c03 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1ba1d9a9e971dc3d81f3fc50adf83b830751fbdee689b1a77f22c376c4bfa329 -size 625643 +oid sha256:62586359c45cf924fb2b632ea24a46aa0a92ec79046c8c41fb4b1082df44f576 +size 625261 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index 808ed20ae8..27117d10b7 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:168b689ca74489d0eb8eeb244a8797d0fd5d3dda9a7b50ff06a11ac72be39b32 -size 1267880 +oid sha256:acbff59a39c1178197b6eae8eb14442f671578fa8b64412b8d529c6f5ecb186d +size 1267047 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 86057a6235..ca67ac864c 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ba54559545fce6946c358806cf3655e0fc9c5fa675135ac8c2bb041363a374df -size 867118 +oid sha256:34eb3e4a5afde4bf07aa58c0915077e74ab11b3a5e4df597758d3b6b762137d1 +size 866550 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index b603660fc4..6b7ee2539d 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d252126d6c2b26319dd5ffc3647a491702488d7f0d38d0ed54cfbd800fb0421c -size 3403854 +oid sha256:84e44dd8399948aea70a73e47ef4d8b2b6608a5ca106ca0367ac723a3c0b9b08 +size 3405721 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 656c00354c..0785234558 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:59ea9439641b382f07287dc9e94b5510c3ef4815b312e3648896194b2fc53224 -size 582502 +oid sha256:0f52853382310cd0561f9ddfd11d381aff88e60872511be018df1fbe6065bb45 +size 582523 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 7481a78c2a..686f7f0692 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8e67f36a1a3247b3f9075c2d51fca1343f1dba093fdfed042365749ba41bc443 -size 2460039 +oid sha256:213b76c230fa3f0fef0834f99edb46234d813d4544eaf743712f9d80cb97eb8a +size 2460860 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index c9cd561717..61bb866738 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:72a4ad782fab7cefc389b1262481f065ede16e8eb842dcae5dbb1dba57a04b53 -size 635067 +oid sha256:19d916621fe22d369afdf5dda3c3142cfdc6f35c38d9b23b556c5b1e830112b8 +size 635112 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index 64f2a09214..a5ca16f108 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a26128814f484f6c933a73c205d9b0af2d6eed668705d535b922021d60c3e2b5 -size 3373934 +oid sha256:bcda26e89cbb7852542ca55bc584e48afdce991ce49a0be3d199505fdcd07a5c +size 3375714 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 4d3f3a2e99..3cbd520054 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:600075ef75fb96dae357aec18bb238671ac87097cb94983ea109547dde8ef549 -size 574867 +oid sha256:cdb6af7e0435c13bb8fbe21201974bda74bb00203cdc6d2c083405a304ea0340 +size 574903 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index f2a08516fe..ed898f3c53 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:942523395fc7646b7541728692350118e4b7a4780904217d57f9cf61612c99cc -size 2358486 +oid sha256:169f28320ad5e8c9308b0eb0c693b4d84e569adeb9821cbd2eb66fe622a6d673 +size 2358477 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index 59f43068e7..a7afb475b5 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fcc6196f2008c8cdb719126aa32bbc66cf18864ec9641c960bb8529ae1731c94 -size 945573 +oid sha256:538054b58f5d58e9efe616e0d8fdaf4e543412330b5223c71ff4e6093e644bfd +size 946502 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 323e820ffd..ec97bb688b 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9251e157adb281b08946f6a3bfd153a95e07ff6f803a6f67a1d7257273992595 -size 1837840 +oid sha256:6205207444ddc8c8cb99c03943b2ae3dd853c24251c7228a111a6eeaaa61ad9b +size 1841730 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index f7fb2c5536..8175c49046 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4babcdec1951135713b94499f8bd3839d2dc9af2aab5d7fc9350e7ac71e68853 -size 1273353 +oid sha256:44f4c362624739dd948a9a10f8da0efa202219b7e5db0b91dcdb728b78d866fc +size 1273571 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index bf02812faa..e57eb04d2b 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a549df2c3e5d1f904c42162ff5ecef0ad1097b87be14ae51edf604a63a3d139a -size 5048747 +oid sha256:edf2dd7e2de86fd4ff950d5e647b0d4cef8fed5bb1376ed53314a8577d75f6f0 +size 5051957 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index 2a29034309..cfec4f60d0 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ddf24263011f4062b00290f8613c706cd0527f51e43bc41a692012da4fd8f46f -size 873464 +oid sha256:beba4d2e42376cd3ce8c70ec3e106dbe9adbd68e44ee257d525ea1b2b84092ca +size 874071 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index a5d8a477db..4e0134478c 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1cfe3ceeab47625ef7df0c56646ff4e1c09da7c6fb04539bd1ed59a2c4a2a8cd -size 3770406 +oid sha256:a83c1af48ef552602cd060926571a05c20dbb945183c3625cdc0742396dc0e4c +size 3775521 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index 99028bc390..152d392c2d 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f85282fb7a5d278edef1dec0266670a710838b3215b3d7bec1533e07478e9399 -size 952619 +oid sha256:9a0584db2fab77f2f939571e60b6310e1fffcfb0d975e1b245e9171feb1ca4a9 +size 952992 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 4d3d3e6dce..91d062eb5c 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1090c6b43400a9163468bc98a7da3eb71bab2ec26b67d9213c86e808aebb4720 -size 5260509 +oid sha256:0a8786dc736ed6fd23f99cb9068f30dc0711c2f78ec5c1d2807c580aa6601955 +size 5264111 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 34b976cb71..b454bd2efa 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8dc0195293f1ac08202dc8b75cc90f04b6b0c93d38fe3ca04996e777786935b4 -size 862180 +oid sha256:af4ee0563161edb913eb37d54b2d12289420b9ad13dc5a368648c901135589a7 +size 862237 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index da38abcb7d..bb45ef8b9d 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bdf3caff605f997c0bdfb017e10fa5af6ad71728a52a61c60107b55872968524 -size 3669671 +oid sha256:fdcfac598c4ac696604bf936a6a58dea0cea310a61d86570627e9af6f3d94e70 +size 3668915 From 443f9cc8e03bcf6d12c9ca74feb60f034a47f7b3 Mon Sep 17 00:00:00 2001 From: Martin Lopes Date: Tue, 7 Jun 2022 13:54:21 +1000 Subject: [PATCH 5/8] Adds links to the example library (#28254) --- .../understanding-github-actions.md | 10 +++++----- content/actions/quickstart.md | 3 +++ data/reusables/actions/link-to-example-library.md | 1 + 3 files changed, 9 insertions(+), 5 deletions(-) create mode 100644 data/reusables/actions/link-to-example-library.md diff --git a/content/actions/learn-github-actions/understanding-github-actions.md b/content/actions/learn-github-actions/understanding-github-actions.md index e13d3d5c13..a92f932538 100644 --- a/content/actions/learn-github-actions/understanding-github-actions.md +++ b/content/actions/learn-github-actions/understanding-github-actions.md @@ -86,14 +86,14 @@ For more information, see "[Creating actions](/actions/creating-actions)." {% data reusables.actions.workflow-basic-example-and-explanation %} +## More complex examples +{% data reusables.actions.link-to-example-library %} + ## Next steps -To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." - +- To continue learning about {% data variables.product.prodname_actions %}, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)." {% ifversion fpt or ghec or ghes %} - -To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". - +- To understand how billing works for {% data variables.product.prodname_actions %}, see "[About billing for {% data variables.product.prodname_actions %}](/actions/reference/usage-limits-billing-and-administration#about-billing-for-github-actions)". {% endif %} ## Contacting support diff --git a/content/actions/quickstart.md b/content/actions/quickstart.md index 610d840918..fc6d84a103 100644 --- a/content/actions/quickstart.md +++ b/content/actions/quickstart.md @@ -80,6 +80,9 @@ Committing the workflow file to a branch in your repository triggers the `push` {% data reusables.actions.workflow-template-overview %} +## More complex examples +{% data reusables.actions.link-to-example-library %} + ## Next steps The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}: diff --git a/data/reusables/actions/link-to-example-library.md b/data/reusables/actions/link-to-example-library.md new file mode 100644 index 0000000000..b1391dacb2 --- /dev/null +++ b/data/reusables/actions/link-to-example-library.md @@ -0,0 +1 @@ +For examples that demonstrate more complex features of {% data variables.product.prodname_actions %}, see "[Examples](/actions/examples)." You can see detailed examples that explain how to test your code on a runner, access the {% data variables.product.prodname_dotcom %} CLI, and use advanced features such as concurrency and test matrices. From d9655fa4b3400fe468ce4ba5d2167f0df5042b1b Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Tue, 7 Jun 2022 11:25:01 +0200 Subject: [PATCH 6/8] Combine list and existing conceptual content --- .../automatically-generated-release-notes.md | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md index e35226edd8..3c94bbe950 100644 --- a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md +++ b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -17,16 +17,9 @@ communityRedirect: ## About automatically generated release notes -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. 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. - -### Contents of automatically generated release notes - -The automatically generated release notes include: - -* A list of merged pull requests. -* A list of contributors to the release. -* A link to a full changelog. +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 %} From 356cfecea34be776dbee408fe9e53df947826aaf Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Tue, 7 Jun 2022 11:26:04 +0200 Subject: [PATCH 7/8] Trivial spacing adjustment --- .../automatically-generated-release-notes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md index 3c94bbe950..397fc4b7f0 100644 --- a/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md +++ b/content/repositories/releasing-projects-on-github/automatically-generated-release-notes.md @@ -20,6 +20,7 @@ communityRedirect: 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 %} From 3a3e36a52518bf1c703b58a1f306216efa359f76 Mon Sep 17 00:00:00 2001 From: Jesse Seales <103135467+sealesj@users.noreply.github.com> Date: Tue, 7 Jun 2022 05:57:38 -0400 Subject: [PATCH 8/8] Additional closing curly brace (#18382) Adding additional closing curly brace to the minimal SARIF file example so that code can be copy/pasted for a user and work without additional formatting. --- .../sarif-support-for-code-scanning.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md index 637c78f8c7..29f610cec3 100644 --- a/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md +++ b/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md @@ -211,11 +211,12 @@ This SARIF output file has example values to show the minimum required propertie "id": "R01" ... "properties" : { - "id" : "java/unsafe-deserialization", - "kind" : "path-problem", - "name" : "...", - "problem.severity" : "error", - "security-severity" : "9.8", + "id" : "java/unsafe-deserialization", + "kind" : "path-problem", + "name" : "...", + "problem.severity" : "error", + "security-severity" : "9.8", + } } ] }