-
- - Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | +| Engenheiro de segurança | Capaz de contribuir com código e manter o pipeline de segurança | **Manter** | Excluir resultados da varredura de código | +| Prestador de serviço | Capaz de desenvolver integrações de webhooks | **Gravar** | Gerenciar webhooks | +| Gerente de comunidade | Capaz de lidar com todas as interações da comunidade sem ser capaz de contribuir com código | **Leitura** | – Marcar um problema como duplicado
– Gerenciar as configurações de página do GitHub
– Gerenciar as configurações do wiki
– Definir a visualização social
– Editar os metadados do repositório
– Discussões sobre triagem | -## Additional permissions for custom roles +## Permissões adicionais para funções personalizadas -After choosing an inherited role, you can select additional permissions for your custom role. +Depois de escolher uma função herdada, você poderá selecionar as permissões adicionais para a sua função personalizada. -You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role. +Você só pode escolher uma permissão adicional se já não estiver incluída na função herdada. Por exemplo, se a função herdada oferecer acesso de **Gravação** em um repositório, a permissão "Fechar uma solicitação de pull" já estará incluída na função herdada. {% ifversion discussions %} -### Discussions +### Discussões -- Create a discussion category -- Edit a discussion category -- Delete a discussion category -- Mark or unmark discussion answers -- Hide or unhide discussion comments -- Convert issues to discussions +- Criar uma categoria de discussão +- Editar uma categoria de discussão +- Excluir uma categoria de discussão +- Marcar ou desmarcar respostas de discussão +- Ocultar ou mostrar comentários da discussão +- Converter problemas em discussões -For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)." +Para obter mais informações, confira "[{% data variables.product.prodname_discussions %}](/discussions)". {% endif %} -### Issue and Pull Requests +### Problemas e Pull Requests -- Assign or remove a user -- Add or remove a label +- Atribuir ou remover um usuário +- Adicionar ou remover um rótulo -### Issue +### Problema -- Close an issue -- Reopen a closed issue -- Delete an issue -- Mark an issue as a duplicate +- Fechar um problema +- Reabrir um problema fechado +- Excluir um problema +- Marcar um problema como duplicado ### Pull Request -- Close a pull request -- Reopen a closed pull request -- Request a pull request review +- Fechar uma solicitação de pull +- Reabrir uma solicitação de pull fechada +- Solicitar uma revisão de solicitação de pull -### Repository +### Repositório -- Set milestones -- Manage wiki settings -- Manage project settings -- Manage pull request merging settings -- Manage {% data variables.product.prodname_pages %} settings (see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)") -- Manage webhooks -- Manage deploy keys -- Edit repository metadata -{%- ifversion ghec %} -- Set interaction limits -{%- endif %} -- Set the social preview -- Push commits to protected branches (branch protection rules will still apply) -- Create protected tags -- Delete protected tags -{%- ifversion bypass-branch-protections %} -- Bypass branch protections -{%- endif %} +- Definir os marcos +- Gerenciar as configurações do wiki +- Gerenciar as configurações do projeto +- Gerenciar as configurações de mesclagem de solicitação de pull +- Gerenciar as configurações do {% data variables.product.prodname_pages %} (confira "[Como configurar uma fonte de publicação para seu site do {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)") +- Gerenciar webhooks +- Gerenciar as chaves de implantação +- Editar os metadados do repositório {%- ifversion ghec %} +- Definir os limites de interação {%- endif %} +- Definir a visualização social +- Efetuar push de commits para branches protegidos (as regras de proteção de branch ainda serão aplicadas) +- Criar marcas protegidas +- Excluir marcas protegidas {%- ifversion bypass-branch-protections %} +- Ignorar as proteções de branch {%- endif %} -### Security +### Segurança -- View {% data variables.product.prodname_code_scanning %} results -- Dismiss or reopen {% data variables.product.prodname_code_scanning %} results -- Delete {% data variables.product.prodname_code_scanning %} results -- View {% data variables.product.prodname_dependabot_alerts %} -- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %} -- View {% data variables.product.prodname_secret_scanning %} results -- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results +- Exibir os resultados da {% data variables.product.prodname_code_scanning %} +- Ignorar ou reabrir os resultados da {% data variables.product.prodname_code_scanning %} +- Excluir os resultados da {% data variables.product.prodname_code_scanning %} +- Exibir os {% data variables.product.prodname_dependabot_alerts %} +- Ignorar ou reabrir os {% data variables.product.prodname_dependabot_alerts %} +- Exibir os resultados da {% data variables.product.prodname_secret_scanning %} +- Ignorar ou reabrir os resultados da {% data variables.product.prodname_secret_scanning %} -## Precedence for different levels of access +## Precedência para diferentes níveis de acesso -If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. +Se uma pessoa receber diferentes níveis de acesso por meio de caminhos diferentes como, por exemplo, a associação a uma equipe e as permissões básicas para uma organização, o maior acesso substitui os outros. Por exemplo, se um proprietário da organização dá a um integrante da organização uma função personalizada que use a função de "ler" herdada e, em seguida, o proprietário da organização definir a permissão de base da organização para "gravar", essa função personalizada terá acesso de gravação, junto com quaisquer permissões adicionais incluídas na função personalizada. {% data reusables.organizations.mixed-roles-warning %} -To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: - - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - - "[Editing a repository role](#editing-a-repository-role)" \ No newline at end of file +Para resolver o acesso conflitante, você pode ajustar as permissões básicas da sua organização ou o acesso da equipe ou editar a função personalizada. Para obter mais informações, consulte: + - "[Como definir as permissões base de uma organização](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" + - "[Como gerenciar o acesso da equipe a um repositório da organização](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" + - "[Como editar uma função do repositório](#editing-a-repository-role)" diff --git a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index e687fd7b2b..b90b8ff549 100644 --- a/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -183,18 +183,18 @@ By default, you can only use npm packages hosted on your enterprise, and you wil {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. +1. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. Replace `
- 
-
+
-# Bibliotecas de terceiros
+## O Octokit tem muitos sabores
+
+Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.
+
+- **Python** → [octokit.py](https://github.com/khornberg/octokit.py)
+- **Ruby** → [octokit.rb](https://github.com/octokit/octokit.rb)
+- **.NET** → [octokit.net](https://github.com/octokit/octokit.net)
+- **JavaScript** → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+
+## Bibliotecas de terceiros
### Clojure
@@ -130,6 +130,7 @@ ms.locfileid: '146769154'
|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
|**github-flask**|[github-flask (site oficial)](http://github-flask.readthedocs.org)|
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
+|**githubkit**|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
### Ruby
diff --git a/translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md
index bc0bce5698..7ff3731a54 100644
--- a/translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md
+++ b/translations/pt-BR/data/reusables/actions/private-repository-forks-configure.md
@@ -1,10 +1,7 @@
----
-ms.openlocfilehash: 3def1c7efad50b8bfda097251abf28dd4a5f46df
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145083859"
----
-1. Em **Criar fork de fluxos de trabalho de solicitação de pull**, selecione suas opções. Por exemplo: 
-1. Clique em **Salvar** para aplicar as configurações.
+1. Under **Fork pull request workflows**, select your options. For example:
+ {% ifversion actions-private-fork-workflow-approvals %}
+ {% else %}
+
+ {% endif %}
+
+1. Click **Save** to apply the settings.
diff --git a/translations/pt-BR/data/reusables/actions/private-repository-forks-options.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-options.md
index b4980f8da0..7e7219bd70 100644
--- a/translations/pt-BR/data/reusables/actions/private-repository-forks-options.md
+++ b/translations/pt-BR/data/reusables/actions/private-repository-forks-options.md
@@ -1,11 +1,4 @@
----
-ms.openlocfilehash: 6c1dd36680cbcbf04fda2d18f14a828249715ff7
-ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d
-ms.translationtype: HT
-ms.contentlocale: pt-BR
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145065400"
----
-- **Executar fluxos de trabalho por meio de solicitações de pull com fork** – Permite que os usuários executem fluxos de trabalho por meio de solicitações de pull com fork usando um `GITHUB_TOKEN` com permissão somente leitura e sem acesso aos segredos.
-- **Enviar tokens de gravação para fluxos de trabalho por meio de solicitações de pull** – Permite que as solicitações de pull de forks usem um `GITHUB_TOKEN` com permissão de gravação.
-- **Enviar segredos para fluxos de trabalho por meio de solicitações de pull** – Disponibiliza todos os segredos para a solicitação de pull.
+- **Run workflows from fork pull requests** - Allows users to run workflows from fork pull requests, using a `GITHUB_TOKEN` with read-only permission, and with no access to secrets.
+- **Send write tokens to workflows from pull requests** - Allows pull requests from forks to use a `GITHUB_TOKEN` with write permission.
+- **Send secrets to workflows from pull requests** - Makes all secrets available to the pull request.{% ifversion actions-private-fork-workflow-approvals %}
+- **Require approval for fork pull request workflows** - Workflow runs on pull requests from collaborators without write permission will require approval from someone with write permission before they will run.{% endif %}
diff --git a/translations/pt-BR/data/reusables/actions/workflows/approve-workflow-runs.md b/translations/pt-BR/data/reusables/actions/workflows/approve-workflow-runs.md
new file mode 100644
index 0000000000..63c0773889
--- /dev/null
+++ b/translations/pt-BR/data/reusables/actions/workflows/approve-workflow-runs.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: fec57b88af5ef5b7227d88a8c70e5a4b4bb9c769
+ms.sourcegitcommit: fdc4466e89467a7b13239e26c6042dc1428946b6
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163808"
+---
+Os mantenedores com acesso de gravação a um repositório podem usar o seguinte procedimento para revisar e executar fluxos de trabalho em pull requests de colaboradores que exigem aprovação.
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
+1. Inspecione as alterações propostas no pull request e certifique-se de que você esteja confortável em executar seus fluxos de trabalho no branch do pull request. Você deve ficar especialmente atento para todas as alterações propostas no diretório `.github/workflows/` que afetem arquivos de fluxo de trabalho.
+1. Se você estiver familiarizado com a execução de fluxos de trabalho no branch de solicitação de pull, volte à guia {% octicon "comment-discussion" aria-label="The discussion icon" %} **Conversa** e, em "Fluxos de trabalho que aguardam aprovação", clique em **Aprovar e executar**.
+
+ 
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md
index cce6e5778b..633f3b007a 100644
--- a/translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md
+++ b/translations/pt-BR/data/reusables/code-scanning/autobuild-compiled-languages.md
@@ -1 +1,9 @@
-For the supported compiled languages, you can use the `autobuild` action in the {% data variables.code-scanning.codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
\ No newline at end of file
+---
+ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161059"
+---
+Para as linguagens compiladas compatíveis, use a ação `autobuild` no {% data variables.code-scanning.codeql_workflow %} para compilar o código. Isso evita que você precise especificar comandos de build explícitos para C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} e Java.
\ No newline at end of file
diff --git a/translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md b/translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md
index 1400f1f34b..d4acbcc66b 100644
--- a/translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md
+++ b/translations/pt-BR/data/reusables/code-scanning/codeql-runner-analyze-example.md
@@ -1,4 +1,12 @@
-1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. The results will appear in the **Security** tab for your repository.
+---
+ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: pt-BR
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161225"
+---
+1. Preencha os bancos de dados do {% data variables.product.prodname_codeql %}, analise-os e carregue os resultados no {% data variables.product.product_name %}. Os resultados serão exibidos na guia **Segurança** do repositório.
```shell
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
@@ -9,7 +17,7 @@
> POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
> Successfully uploaded results
```
-2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the
- O Octokit tem muitos sabores
-Use a biblioteca oficial do Octokit ou escolha entre qualquer uma das bibliotecas de terceiros disponíveis.
- -+--- +ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160753" +--- +{% data variables.product.prodname_copilot %} está disponível para clientes {% data variables.product.company_short %} com uma conta pessoal em {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.copilot.emus-cannot-use-copilot %}
-{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." +O {% data variables.product.prodname_copilot %} é gratuito para uso de alunos, professores e mantenedores verificados de projetos populares de software livre. Se você não for aluno, professor nem mantenedor de um projeto popular de software livre, experimente o {% data variables.product.prodname_copilot %} gratuitamente com uma avaliação única de 60 dias. Após a avaliação gratuita, você precisará de uma assinatura paga para uso contínuo. Para ver mais informações, confira "[Sobre a cobrança do {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)". diff --git a/translations/pt-BR/data/reusables/github-connect/connection-port-protocol.md b/translations/pt-BR/data/reusables/github-connect/connection-port-protocol.md new file mode 100644 index 0000000000..1710cf193e --- /dev/null +++ b/translations/pt-BR/data/reusables/github-connect/connection-port-protocol.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160752" +--- +A conexão usa HTTPS nas portas 443 ou 80 e é protegida pelo TLS. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/gpg/paste-ssh-public-key.md b/translations/pt-BR/data/reusables/gpg/paste-ssh-public-key.md index fcfe12de64..24d9305a3d 100644 --- a/translations/pt-BR/data/reusables/gpg/paste-ssh-public-key.md +++ b/translations/pt-BR/data/reusables/gpg/paste-ssh-public-key.md @@ -1,12 +1,11 @@ --- -ms.openlocfilehash: dc6bad5b656bb5d755196146b017213b66d1730e -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 +ms.openlocfilehash: 6dfaad4dc9dc813104183b2c9db41e480c9b27fb +ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884717" +ms.lasthandoff: 11/14/2022 +ms.locfileid: "148163574" --- -1. Para definir sua chave de assinatura SSH no Git, cole o texto abaixo, substituindo o conteúdo da sua área de transferência pela chave que gostaria de usar. Como a chave contém espaços, você deve colocá-la entre aspas: +1. Para definir a chave de assinatura SSH no Git, cole o texto abaixo, substituindo **/PATH/TO/KEY.PUB** pela chave pública que deseja usar. ```bash - $ git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com' - ``` \ No newline at end of file + $ git config --global user.signingkey /PATH/TO/.SSH/KEY.PUB diff --git a/translations/pt-BR/data/reusables/organizations/blocking-a-user.md b/translations/pt-BR/data/reusables/organizations/blocking-a-user.md new file mode 100644 index 0000000000..2defe39cf1 --- /dev/null +++ b/translations/pt-BR/data/reusables/organizations/blocking-a-user.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 44fb7593fc71c38604cb0e7b96ea0439c7028a1f +ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2 +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/14/2022 +ms.locfileid: "148164219" +--- +Ao bloquear um usuário, você pode optar por bloqueá-lo indefinidamente ou por um período específico. Se você bloquear alguém por um período específico, ele será automaticamente desbloqueado após o término desse período. Se você bloquear alguém indefinidamente, será possível desbloqueá-lo manualmente a qualquer momento. Para obter mais informações, consulte "[Como bloquear um usuário da sua organização](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)". \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/about-READMEs.md b/translations/pt-BR/data/reusables/repositories/about-READMEs.md new file mode 100644 index 0000000000..b2d6c42c19 --- /dev/null +++ b/translations/pt-BR/data/reusables/repositories/about-READMEs.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: a4b1ca4e0548ebc2be12a34e0bb1687e9e650038 +ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e +ms.translationtype: HT +ms.contentlocale: pt-BR +ms.lasthandoff: 11/14/2022 +ms.locfileid: "148163421" +--- +É possível adicionar um arquivo README a um repositório para comunicar informações importantes sobre o seu projeto. Um LEIAME, junto com uma licença de repositório, um arquivo de citação{% ifversion fpt or ghec %}, diretrizes de contribuição e um código de conduta{% elsif ghes %} e diretrizes de contribuição{% endif %}, comunica as expectativas do projeto e ajuda você a gerenciar contribuições. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md b/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md index 4c949c04b5..46c2632f77 100644 --- a/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md +++ b/translations/pt-BR/data/reusables/repositories/anyone-can-view-anonymized-url.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 85c7f83e66e8519c6d62346fe69b6e3f0b413ff1 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 ms.translationtype: HT ms.contentlocale: pt-BR -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147419886" +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160750" --- {% warning %} -**Aviso:** se você anexar um arquivo a uma solicitação de pull, a um comentário de problema, a um tíquete no {% data variables.contact.support_portal %}, qualquer pessoa poderá exibir a URL anônima sem autenticação, mesmo que a solicitação de pull esteja em um repositório privado{% ifversion ghes %} ou um modo privado esteja habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para obter mais informações sobre as URLs anônimas, confira "[Sobre as URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} +**Aviso:** quando você carregar uma imagem ou um vídeo em uma solicitação de pull ou em um comentário de problema ou carregar um arquivo no {% data variables.contact.support_portal %}, qualquer pessoa poderá visualizar a URL anônima sem autenticação, mesmo que a solicitação de pull ou o problema esteja em um repositório privado{% ifversion ghes %} ou que o modo privado esteja habilitado{% endif %}. Para manter arquivos de mídia confidenciais privados, forneça-os a partir de uma rede privada ou servidor que exige autenticação. {% ifversion fpt or ghec %}Para obter mais informações sobre as URLs anônimas, confira "[Sobre as URLs anônimas](/github/authenticating-to-github/about-anonymized-urls)".{% endif %} {% endwarning %} From b72f9f2df7bbf416900b74db4505cedbff9aac3d Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Tue, 15 Nov 2022 09:12:59 -0800 Subject: [PATCH 2/5] New translation batch for cn (#32630) --- translations/log/msft-cn-resets.csv | 30 +--- ...proving-workflow-runs-from-public-forks.md | 27 +-- .../actions/managing-workflow-runs/index.md | 11 +- ...hing-dependencies-to-speed-up-workflows.md | 50 +++--- .../about-github-connect.md | 90 +++++----- .../managing-github-connect.md | 100 +++++------ .../network-ports.md | 70 ++++---- .../about-enterprise-managed-users.md | 140 +++++++-------- ...-for-enterprise-managed-users-with-okta.md | 103 +++++------ ...mberships-with-identity-provider-groups.md | 85 +++++---- ...g-the-audit-log-api-for-your-enterprise.md | 2 +- .../zh-CN/content/admin/overview/index.md | 8 +- ...-codeql-workflow-for-compiled-languages.md | 119 +++++++------ .../uploading-a-sarif-file-to-github.md | 75 ++++---- ...running-codeql-runner-in-your-ci-system.md | 126 +++++++------- ...tomating-dependabot-with-github-actions.md | 8 +- ...ulnerability-reporting-for-a-repository.md | 44 +++++ .../zh-CN/content/codespaces/overview.md | 53 +++--- .../the-githubdev-web-based-editor.md | 114 +++++++------ .../blocking-a-user-from-your-organization.md | 103 ++++++----- .../about-github-copilot.md | 41 +++-- .../scopes-for-oauth-apps.md | 3 +- .../receiving-webhooks-with-the-github-cli.md | 8 +- .../managing-discussions.md | 131 ++++++++++++-- .../moderating-discussions.md | 58 ++++--- ...about-github-global-campus-for-students.md | 7 +- .../managing-remote-repositories.md | 4 +- .../zh-CN/content/get-started/index.md | 2 +- .../quickstart/contributing-to-projects.md | 4 +- .../get-started/quickstart/github-glossary.md | 18 +- .../attaching-files.md | 59 ++++--- .../index.md | 8 +- ...ing-the-audit-log-for-your-organization.md | 2 +- .../about-custom-repository-roles.md | 161 +++++++++--------- .../working-with-the-npm-registry.md | 6 +- .../index.md | 8 +- .../using-files/navigating-code-on-github.md | 1 + .../dependency-graph/dependency-review.md | 15 +- .../zh-CN/content/rest/overview/libraries.md | 31 ++-- .../private-repository-forks-configure.md | 17 +- .../private-repository-forks-options.md | 15 +- .../workflows/approve-workflow-runs.md | 15 ++ .../autobuild-compiled-languages.md | 10 +- .../codeql-runner-analyze-example.md | 14 +- .../reusables/code-scanning/edit-workflow.md | 10 +- .../copilot/emus-cannot-use-copilot.md | 9 + .../enterprise-accounts/emu-scim-note.md | 10 +- .../enterprise/ghec-authentication-options.md | 9 + .../data/reusables/gated-features/copilot.md | 12 +- .../connection-port-protocol.md | 9 + .../reusables/gpg/paste-ssh-public-key.md | 13 +- .../organizations/blocking-a-user.md | 9 + .../reusables/repositories/about-READMEs.md | 9 + .../anyone-can-view-anonymized-url.md | 10 +- 54 files changed, 1171 insertions(+), 925 deletions(-) create mode 100644 translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md create mode 100644 translations/zh-CN/data/reusables/actions/workflows/approve-workflow-runs.md create mode 100644 translations/zh-CN/data/reusables/copilot/emus-cannot-use-copilot.md create mode 100644 translations/zh-CN/data/reusables/enterprise/ghec-authentication-options.md create mode 100644 translations/zh-CN/data/reusables/github-connect/connection-port-protocol.md create mode 100644 translations/zh-CN/data/reusables/organizations/blocking-a-user.md create mode 100644 translations/zh-CN/data/reusables/repositories/about-READMEs.md diff --git a/translations/log/msft-cn-resets.csv b/translations/log/msft-cn-resets.csv index 334fb1731c..1f514bbecf 100644 --- a/translations/log/msft-cn-resets.csv +++ b/translations/log/msft-cn-resets.csv @@ -484,6 +484,7 @@ translations/zh-CN/content/actions/learn-github-actions/finding-and-customizing- translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,rendering error translations/zh-CN/content/actions/learn-github-actions/usage-limits-billing-and-administration.md,rendering error translations/zh-CN/content/actions/managing-issues-and-pull-requests/moving-assigned-issues-on-project-boards.md,broken liquid tags +translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/disabling-and-enabling-a-workflow.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/manually-running-a-workflow.md,broken liquid tags translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error @@ -506,24 +507,21 @@ translations/zh-CN/content/actions/using-workflows/sharing-workflows-secrets-and translations/zh-CN/content/actions/using-workflows/storing-workflow-data-as-artifacts.md,rendering error translations/zh-CN/content/actions/using-workflows/triggering-a-workflow.md,rendering error translations/zh-CN/content/actions/using-workflows/workflow-syntax-for-github-actions.md,rendering error -translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,broken liquid tags +translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-code-scanning-for-your-appliance.md,rendering error translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-secret-scanning-for-your-appliance.md,rendering error translations/zh-CN/content/admin/code-security/managing-github-advanced-security-for-your-enterprise/enabling-github-advanced-security-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/code-security/managing-supply-chain-security-for-your-enterprise/viewing-the-vulnerability-data-for-your-enterprise.md,broken liquid tags -translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md,rendering error translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md,rendering error translations/zh-CN/content/admin/configuration/configuring-github-connect/index.md,broken liquid tags -translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-an-outbound-web-proxy-server.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-built-in-firewall-rules.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-dns-nameservers.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-tls.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/enabling-subdomain-isolation.md,rendering error -translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/using-github-enterprise-server-with-a-load-balancer.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-network-settings/validating-your-domain-settings.md,broken liquid tags translations/zh-CN/content/admin/configuration/configuring-your-enterprise/accessing-the-administrative-shell-ssh.md,broken liquid tags @@ -578,13 +576,10 @@ translations/zh-CN/content/admin/identity-and-access-management/using-built-in-a translations/zh-CN/content/admin/identity-and-access-management/using-built-in-authentication/inviting-people-to-use-your-instance.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/index.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-cas-for-enterprise-iam/using-cas.md,broken liquid tags -translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-enterprise-managed-users.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-saml-single-sign-on-for-enterprise-managed-users.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-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,rendering error -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-enterprise-managed-users-for-iam/migrating-from-saml-to-oidc.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-ldap-for-enterprise-iam/index.md,broken liquid tags translations/zh-CN/content/admin/identity-and-access-management/using-saml-for-enterprise-iam/about-saml-for-enterprise-iam.md,rendering error @@ -694,7 +689,6 @@ translations/zh-CN/content/code-security/adopting-github-advanced-security-at-sc translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning.md,rendering error -translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error @@ -704,13 +698,11 @@ translations/zh-CN/content/code-security/code-scanning/automatically-scanning-yo translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/viewing-code-scanning-logs.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning.md,rendering error translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning.md,broken liquid tags -translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system.md,rendering error translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system.md,rendering error translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,rendering error translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/migrating-from-the-codeql-runner-to-codeql-cli.md,broken liquid tags -translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md,broken liquid tags translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/troubleshooting-codeql-runner-in-your-ci-system.md,rendering error translations/zh-CN/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md,rendering error translations/zh-CN/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md,rendering error @@ -738,6 +730,7 @@ translations/zh-CN/content/code-security/secret-scanning/managing-alerts-from-se translations/zh-CN/content/code-security/secret-scanning/protecting-pushes-with-secret-scanning.md,rendering error translations/zh-CN/content/code-security/secret-scanning/pushing-a-branch-blocked-by-push-protection.md,rendering error translations/zh-CN/content/code-security/security-advisories/global-security-advisories/about-the-github-advisory-database.md,rendering error +translations/zh-CN/content/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository.md,rendering error translations/zh-CN/content/code-security/security-overview/about-the-security-overview.md,rendering error translations/zh-CN/content/code-security/security-overview/filtering-alerts-in-the-security-overview.md,rendering error translations/zh-CN/content/code-security/security-overview/viewing-the-security-overview.md,rendering error @@ -782,7 +775,6 @@ translations/zh-CN/content/codespaces/managing-your-codespaces/managing-encrypte translations/zh-CN/content/codespaces/managing-your-codespaces/managing-gpg-verification-for-github-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/managing-your-codespaces/reviewing-your-security-logs-for-github-codespaces.md,broken liquid tags -translations/zh-CN/content/codespaces/overview.md,broken liquid tags translations/zh-CN/content/codespaces/prebuilding-your-codespaces/about-github-codespaces-prebuilds.md,broken liquid tags translations/zh-CN/content/codespaces/prebuilding-your-codespaces/configuring-prebuilds.md,broken liquid tags translations/zh-CN/content/codespaces/prebuilding-your-codespaces/managing-prebuilds.md,broken liquid tags @@ -794,7 +786,6 @@ translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/set translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-java-project-for-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-nodejs-project-for-codespaces.md,broken liquid tags translations/zh-CN/content/codespaces/setting-up-your-project-for-codespaces/setting-up-your-python-project-for-codespaces.md,broken liquid tags -translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/exporting-changes-to-a-branch.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/github-codespaces-logs.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/index.md,broken liquid tags @@ -806,12 +797,12 @@ translations/zh-CN/content/codespaces/troubleshooting/working-with-support-for-g translations/zh-CN/content/communities/documenting-your-project-with-wikis/about-wikis.md,broken liquid tags translations/zh-CN/content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md,broken liquid tags translations/zh-CN/content/communities/documenting-your-project-with-wikis/editing-wiki-content.md,rendering error +translations/zh-CN/content/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization.md,broken liquid tags translations/zh-CN/content/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags translations/zh-CN/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio.md,broken liquid tags -translations/zh-CN/content/copilot/overview-of-github-copilot/about-github-copilot.md,broken liquid tags translations/zh-CN/content/copilot/quickstart.md,broken liquid tags translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/adding-and-cloning-repositories/cloning-a-repository-from-github-to-github-desktop.md,broken liquid tags translations/zh-CN/content/desktop/contributing-and-collaborating-using-github-desktop/making-changes-in-a-branch/index.md,broken liquid tags @@ -840,6 +831,7 @@ translations/zh-CN/content/discussions/collaborating-with-your-community-using-d translations/zh-CN/content/discussions/guides/finding-your-discussions.md,broken liquid tags translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-categories-for-discussions.md,broken liquid tags translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md,broken liquid tags +translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md,broken liquid tags translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md,broken liquid tags translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers.md,broken liquid tags translations/zh-CN/content/education/manage-coursework-with-github-classroom/get-started-with-github-classroom/glossary.md,broken liquid tags @@ -876,8 +868,7 @@ translations/zh-CN/content/get-started/quickstart/contributing-to-projects.md,re translations/zh-CN/content/get-started/quickstart/create-a-repo.md,broken liquid tags translations/zh-CN/content/get-started/quickstart/fork-a-repo.md,rendering error translations/zh-CN/content/get-started/quickstart/git-and-github-learning-resources.md,broken liquid tags -translations/zh-CN/content/get-started/quickstart/github-glossary.md,rendering error -translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags +translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,rendering error translations/zh-CN/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md,broken liquid tags translations/zh-CN/content/get-started/signing-up-for-github/verifying-your-email-address.md,rendering error translations/zh-CN/content/get-started/using-git/about-git-rebase.md,broken liquid tags @@ -888,7 +879,6 @@ translations/zh-CN/content/get-started/using-github/keyboard-shortcuts.md,render translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/about-writing-and-formatting-on-github.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md,rendering error translations/zh-CN/content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/quickstart-for-writing-on-github.md,rendering error -translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/attaching-files.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls.md,broken liquid tags translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-formatting/writing-mathematical-expressions.md,rendering error translations/zh-CN/content/github-cli/github-cli/quickstart.md,rendering error @@ -924,7 +914,6 @@ translations/zh-CN/content/organizations/managing-organization-settings/managing translations/zh-CN/content/organizations/managing-organization-settings/managing-the-default-branch-name-for-repositories-in-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-organization-settings/managing-the-forking-policy-for-your-organization.md,broken liquid tags translations/zh-CN/content/organizations/managing-organization-settings/setting-permissions-for-adding-outside-collaborators.md,rendering error -translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/about-custom-repository-roles.md,broken liquid tags translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-security-managers-in-your-organization.md,rendering error translations/zh-CN/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md,broken liquid tags translations/zh-CN/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags @@ -1006,7 +995,6 @@ translations/zh-CN/content/rest/activity/notifications.md,broken liquid tags translations/zh-CN/content/rest/apps/oauth-applications.md,broken liquid tags translations/zh-CN/content/rest/codespaces/codespaces.md,broken liquid tags translations/zh-CN/content/rest/dependabot/index.md,broken liquid tags -translations/zh-CN/content/rest/dependency-graph/dependency-review.md,broken liquid tags translations/zh-CN/content/rest/enterprise-admin/admin-stats.md,broken liquid tags translations/zh-CN/content/rest/enterprise-admin/announcement.md,broken liquid tags translations/zh-CN/content/rest/enterprise-admin/billing.md,broken liquid tags @@ -1083,6 +1071,8 @@ translations/zh-CN/data/reusables/actions/jobs/section-defining-outputs-for-jobs translations/zh-CN/data/reusables/actions/jobs/section-running-jobs-in-a-container.md,broken liquid tags translations/zh-CN/data/reusables/actions/more-resources-for-ghes.md,rendering error translations/zh-CN/data/reusables/actions/moving-a-runner-to-a-group.md,rendering error +translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md,broken liquid tags +translations/zh-CN/data/reusables/actions/private-repository-forks-options.md,broken liquid tags translations/zh-CN/data/reusables/actions/ref_name-description.md,broken liquid tags translations/zh-CN/data/reusables/actions/reusable-workflow-artifacts.md,rendering error translations/zh-CN/data/reusables/actions/reusable-workflow-calling-syntax.md,rendering error @@ -1113,13 +1103,10 @@ translations/zh-CN/data/reusables/audit_log/audit_log_sidebar_for_site_admins.md translations/zh-CN/data/reusables/branches/new-repo-default-branch.md,broken liquid tags translations/zh-CN/data/reusables/classroom/about-autograding.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/autobuild-add-build-steps.md,broken liquid tags -translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/codeql-context-for-actions-and-third-party-tools.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/codeql-languages-bullets.md,rendering error translations/zh-CN/data/reusables/code-scanning/codeql-languages-keywords.md,rendering error -translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/deprecation-codeql-runner.md,rendering error -translations/zh-CN/data/reusables/code-scanning/edit-workflow.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning-actions.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/enterprise-enable-code-scanning.md,broken liquid tags translations/zh-CN/data/reusables/code-scanning/licensing-note.md,broken liquid tags @@ -1181,7 +1168,6 @@ translations/zh-CN/data/reusables/enterprise_user_management/consider-usernames- translations/zh-CN/data/reusables/enterprise_user_management/disclaimer-for-git-read-access.md,broken liquid tags translations/zh-CN/data/reusables/files/choose-commit-email.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/codespaces-classroom-articles.md,broken liquid tags -translations/zh-CN/data/reusables/gated-features/copilot.md,broken liquid tags translations/zh-CN/data/reusables/gated-features/dependency-vulnerable-calls.md,rendering error translations/zh-CN/data/reusables/gated-features/secret-scanning-partner.md,rendering error translations/zh-CN/data/reusables/gated-features/secret-scanning.md,rendering error diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md index 723ca8c8a7..a706c1c012 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks.md @@ -1,31 +1,20 @@ --- -title: 批准复刻中的工作流程运行 -intro: 当外部贡献者第一次向公共仓库提交拉取请求时，拥有写入权限的维护者可能必须批准任何工作流程运行。 +title: Approving workflow runs from public forks +intro: 'When an outside contributor submits a pull request to a public repository, a maintainer with write access may need to approve any workflow runs.' versions: fpt: '*' ghec: '*' shortTitle: Approve public fork runs -ms.openlocfilehash: b995362f67d97a3e2ee6d1029cbe24227867f58a -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '145084656' --- -## 关于公共复刻中的工作流程运行 + +## About workflow runs from public forks {% data reusables.actions.workflow-run-approve-public-fork %} -可以为[存储库](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks)、[组织](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks)或[企业](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise)配置工作流审批要求。 +You can configure workflow approval requirements for a [repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#configuring-required-approval-for-workflows-from-public-forks), [organization](/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#configuring-required-approval-for-workflows-from-public-forks), or [enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise#enforcing-a-policy-for-fork-pull-requests-in-your-enterprise). -已等待批准超过 30 天的工作流程运行将自动删除。 +Workflow runs that have been awaiting approval for more than 30 days are automatically deleted. -## 批准公共复刻中拉取请求的工作流程运行 +## Approving workflow runs on a pull request from a public fork -能够写入仓库的维护者可按照以下步骤来审查和运行来自贡献者、需要审批的拉取请求上的工作流程。 - -{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %} -1. 检查拉取请求中的拟议更改，确保您在拉取请求分支上自由运行您的工作流程。 应特别注意 `.github/workflows/` 目录中影响工作流文件的任何拟议更改。 -1. 如果能自由在拉取请求分支上运行工作流，请返回到 {% octicon "comment-discussion" aria-label="The discussion icon" %}“转换”选项卡，在“等待审批的工作流”下，单击“批准并运行” 。 - -  +{% data reusables.actions.workflows.approve-workflow-runs %} diff --git a/translations/zh-CN/content/actions/managing-workflow-runs/index.md b/translations/zh-CN/content/actions/managing-workflow-runs/index.md index 9a38559ec0..8241a52902 100644 --- a/translations/zh-CN/content/actions/managing-workflow-runs/index.md +++ b/translations/zh-CN/content/actions/managing-workflow-runs/index.md @@ -1,6 +1,6 @@ --- title: 管理工作流程运行 -shortTitle: Managing workflow runs +shortTitle: Manage workflow runs intro: '可以重新运行或取消工作流程、{% ifversion fpt or ghes or ghae %}审核部署、{% endif %}查看可计费作业执行分钟数和下载项目。' redirect_from: - /actions/configuring-and-managing-workflows/managing-a-workflow-run @@ -18,17 +18,18 @@ children: - /re-running-workflows-and-jobs - /canceling-a-workflow - /approving-workflow-runs-from-public-forks + - /approving-workflow-runs-from-private-forks - /reviewing-deployments - /disabling-and-enabling-a-workflow - /skipping-workflow-runs - /deleting-a-workflow-run - /downloading-workflow-artifacts - /removing-workflow-artifacts -ms.openlocfilehash: fe5f7c461fc03392bcc93713887b1cc1d4293207 -ms.sourcegitcommit: fcf3546b7cc208155fb8acdf68b81be28afc3d2d +ms.openlocfilehash: 9e7d6f9c29fdfb2a387b84373c1140dbb3ef6713 +ms.sourcegitcommit: 73b91dd4cdf592eadec4252319379d6fbe92858e ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/10/2022 -ms.locfileid: '145099188' +ms.lasthandoff: 11/14/2022 +ms.locfileid: '148164088' --- {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} diff --git a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md index e743a41842..a2a833a1a3 100644 --- a/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md +++ b/translations/zh-CN/content/actions/using-workflows/caching-dependencies-to-speed-up-workflows.md @@ -49,19 +49,24 @@ For more information on workflow run artifacts, see "[Persisting workflow data u ## Restrictions for accessing a cache -A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually `main`). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch `feature-b` has the base branch `feature-a`, a workflow triggered on `feature-b` would have access to caches created in the default branch (`main`), `feature-a`, and `feature-b`. +Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. +Workflow runs can restore caches created in either the current branch or the default branch (usually `main`). If a workflow run is triggered for a pull request, it can also restore caches created in the base branch, including base branches of forked repositories. For example, if the branch `feature-b` has the base branch `feature-a`, a workflow run triggered on a pull request would have access to caches created in the default `main` branch, the base `feature-a` branch, and the current `feature-b` branch. -Access restrictions provide cache isolation and security by creating a logical boundary between different branches or tags. For example, a cache created for the branch `feature-a` (with the base `main`) would not be accessible to a pull request for the branch `feature-c` (with the base `main`). On similar lines, a cache created for the tag `release-a` (from the base `main`) would not be accessible to a workflow triggered for the tag `release-b` (with the base `main`). +Workflow runs cannot restore caches created for child branches or sibling branches. For example, a cache created for the child `feature-b` branch would not be accessible to a workflow run triggered on the parent `main` branch. Similarly, a cache created for the `feature-a` branch with the base `main` would not be accessible to its sibling `feature-c` branch with the base `main`. Workflow runs also cannot restore caches created for different tag names. For example, a cache created for the tag `release-a` with the base `main` would not be accessible to a workflow run triggered for the tag `release-b` with the base `main`. -Multiple workflows within a repository share cache entries. A cache created for a branch within a workflow can be accessed and restored from another workflow for the same repository and branch. +When a cache is created by a workflow run triggered on a pull request, the cache is created for the merge ref (`refs/pull/.../merge`). Because of this, the cache will have a limited scope and can only be restored by re-runs of the pull request. It cannot be restored by the base branch or other pull requests targeting that base branch. + +Multiple workflow runs in a repository can share caches. A cache created for a branch in a workflow run can be accessed and restored from another workflow run for the same repository and branch. ## Using the `cache` action -The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache, the action restores the cached files to the `path` you configure. +The [`cache` action](https://github.com/actions/cache) will attempt to restore a cache based on the `key` you provide. When the action finds a cache that _exactly_ matches the key, the action restores the cached files to the `path` you configure. +You can optionally provide a list of `restore-keys` to use in case the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can _partially_ match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)." -If there is no exact match, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. +If there is an exact match to the provided `key`, this is considered a cache hit. If no cache exactly matches the provided `key`, this is considered a cache miss. On a cache miss, the action automatically creates a new cache if the job completes successfully. The new cache will use the `key` you provided and contains the files you specify in `path`. For more information about how this is handled, see "[Cache hits and misses](#cache-hits-and-misses)." + +You cannot change the contents of an existing cache. Instead, you can create a new cache with a new key. -You can optionally provide a list of `restore-keys` to use when the `key` doesn't match an existing cache. A list of `restore-keys` is useful when you are restoring a cache from another branch because `restore-keys` can partially match cache keys. For more information about matching `restore-keys`, see "[Matching a cache key](#matching-a-cache-key)." ### Input parameters for the `cache` action @@ -94,6 +99,21 @@ You can optionally provide a list of `restore-keys` to use when the `key` doesn' - `cache-hit`: A boolean value to indicate an exact match was found for the key. +### Cache hits and misses +When `key` exactly matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory. + +When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully. + +When a cache miss occurs, the action also searches your specified `restore-keys` for any matches: + +1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`. + - When there is an exact match, the action restores the files in the cache to the `path` directory. + - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory. +1. The `cache` action completes and the next step in the job runs. +1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory. + +For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." + ### Example using the `cache` action This example creates a new cache when the packages in `package-lock.json` file change, or when the runner's operating system changes. The cache key uses contexts and expressions to generate a key that includes the runner's operating system and a SHA-256 hash of the `package-lock.json` file. @@ -136,20 +156,6 @@ jobs: run: npm test ``` -When `key` matches an existing cache, it's called a _cache hit_, and the action restores the cached files to the `path` directory. - -When `key` doesn't match an existing cache, it's called a _cache miss_, and a new cache is automatically created if the job completes successfully. - -When a cache miss occurs, the action also searches your specified `restore-keys` for any matches: - -1. If you provide `restore-keys`, the `cache` action sequentially searches for any caches that match the list of `restore-keys`. - - When there is an exact match, the action restores the files in the cache to the `path` directory. - - If there are no exact matches, the action searches for partial matches of the restore keys. When the action finds a partial match, the most recent cache is restored to the `path` directory. -1. The `cache` action completes and the next step in the job runs. -1. If the job completes successfully, the action automatically creates a new cache with the contents of the `path` directory. - -For a more detailed explanation of the cache matching process, see "[Matching a cache key](#matching-a-cache-key)." Once you create a cache, you cannot change the contents of an existing cache but you can create a new cache with a new key. - ### Using contexts to create cache keys A cache key can include any of the contexts, functions, literals, and operators supported by {% data variables.product.prodname_actions %}. For more information, see "[Contexts](/actions/learn-github-actions/contexts)" and "[Expressions](/actions/learn-github-actions/expressions)." @@ -185,7 +191,9 @@ In the example workflow above, there is a step that lists the state of the Node ## Matching a cache key -The `cache` action first searches for cache hits for `key` and `restore-keys` in the branch containing the workflow run. If there are no hits in the current branch, the `cache` action searches for `key` and `restore-keys` in the parent branch and upstream branches. +The `cache` action first searches for cache hits for `key` and the cache _version_ in the branch containing the workflow run. If there is no hit, it searches for `restore-keys` and the _version_. If there are still no hits in the current branch, the `cache` action retries same steps on the default branch. Please note that the scope restrictions apply during the search. For more information, see "[Restrictions for accessing a cache](#restrictions-for-accessing-a-cache)." + +Cache version is a way to stamp a cache with metadata of the `path` and the compression tool used while creating the cache. This ensures that the consuming workflow run uniquely matches a cache it can actually decompress and use. For more information, see [Cache Version](https://github.com/actions/cache#cache-version) in the Actions Cache documentation. `restore-keys` allows you to specify a list of alternate restore keys to use when there is a cache miss on `key`. You can create multiple restore keys ordered from the most specific to least specific. The `cache` action searches the `restore-keys` in sequential order. When a key doesn't match directly, the action searches for keys prefixed with the restore key. If there are multiple partial matches for a restore key, the action returns the most recently created cache. diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md index 07cb787914..f3635d4b30 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/about-github-connect.md @@ -1,6 +1,6 @@ --- -title: About GitHub Connect -intro: '{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by giving you access to additional features and workflows that rely on the power of {% data variables.product.prodname_dotcom_the_website %}.' +title: 关于 GitHub Connect +intro: '{% data variables.product.prodname_github_connect %} 通过允许你访问依赖于 {% data variables.product.prodname_dotcom_the_website %} 的力量的其他功能和工作流来增强 {% data variables.product.product_name %}。' versions: ghes: '*' ghae: '*' @@ -9,76 +9,66 @@ topics: - Enterprise - GitHub Connect miniTocMaxHeadingLevel: 3 +ms.openlocfilehash: ac4ec1d8b619e56c38013f5ae38d5782b6faec88 +ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160814' --- +## 关于 {% data variables.product.prodname_github_connect %} -## About {% data variables.product.prodname_github_connect %} +{% data variables.product.prodname_github_connect %} 通过允许 {% data variables.location.product_location %} 以有限的方式从 {% data variables.product.prodname_dotcom_the_website %} 的强大功能中获益，从而增强了 {% data variables.product.product_name %}。 启用 {% data variables.product.prodname_github_connect %} 后，可以启用依赖于 {% data variables.product.prodname_dotcom_the_website %} 的其他功能和工作流，例如 {% data variables.product.prodname_advisory_database %} 中跟踪的安全漏洞的 {% data variables.product.prodname_dependabot_alerts %}。 -{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.location.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}. +{% data variables.product.prodname_github_connect %} 不会将 {% data variables.location.product_location %} 打开到公共 Internet。 企业的任何私有数据都不会公开给 {% data variables.product.prodname_dotcom_the_website %} 用户。 相反，{% data variables.product.prodname_github_connect %} 仅传输你选择启用的各个功能所需的有限数据。 除非启用许可证同步，否则 {% data variables.product.prodname_github_connect %} 不会传输任何个人数据。 有关 {% data variables.product.prodname_github_connect %} 传输哪些数据的详细信息，请参阅“[{% data variables.product.prodname_github_connect %} 的数据传输](#data-transmission-for-github-connect)”。 -{% data variables.product.prodname_github_connect %} does not open {% data variables.location.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)." +启用 {% data variables.product.prodname_github_connect %} 将不允许 {% data variables.product.prodname_dotcom_the_website %} 用户对 {% data variables.product.product_name %} 进行更改。 -Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}. +若要启用 {% data variables.product.prodname_github_connect %}，需在 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %} 上使用 {% data variables.product.prodname_ghe_cloud %} 的组织或企业帐户之间配置连接。 {% data reusables.github-connect.connection-port-protocol %}有关详细信息，请参阅“[管理 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)”。 -To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)." +启用 {% data variables.product.prodname_github_connect %} 后，你将能够启用{% ifversion ghes %}用户许可证自动同步和 {% endif %}{% data variables.product.prodname_dependabot_alerts %} 等功能。 有关所有可用功能的详细信息，请参阅“[{% data variables.product.prodname_github_connect %} 功能](#github-connect-features)”。 -After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)." +## {% data variables.product.prodname_github_connect %} 功能 -## {% data variables.product.prodname_github_connect %} features +配置 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的连接后，便可为企业启用 {% data variables.product.prodname_github_connect %} 的各个功能。 -After you configure the connection between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise. +功能 | 说明 | 详细信息 | ------- | ----------- | ---------------- |{% ifversion ghes %} 用户许可证自动同步 | 通过自动将用户许可证从 {% data variables.location.product_location %} 同步到 {% data variables.product.prodname_ghe_cloud %} 来管理 {% data variables.product.prodname_enterprise %} 部署中的许可证使用情况。 |“[为企业启用用户许可证自动同步](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)”{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot %} | 允许用户查找和修复代码依赖项中的漏洞。 |“[为企业启用 {% data variables.product.prodname_dependabot %}](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)”{% endif %} {% data variables.product.prodname_dotcom_the_website %} 操作 | 允许用户在工作流文件中使用来自 {% data variables.product.prodname_dotcom_the_website %} 的操作。 |“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)”{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | 从 GitHub Enterprise Server 分析自己的聚合数据，并帮助我们改进 GitHub 产品。 | [为企业启用 {% data variables.product.prodname_server_statistics %}](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise){% endif %} 统一搜索 | 从 {% data variables.location.product_location %} 搜索时，允许用户在搜索结果中包含 {% data variables.product.prodname_dotcom_the_website %} 上的存储库。 | [为企业启用 {% data variables.enterprise.prodname_unified_search %}](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)统一参与 | 允许用户将他们在 {% data variables.location.product_location %} 上的工作的匿名参与计数包含在 {% data variables.product.prodname_dotcom_the_website %} 上的参与图中。 | [为企业启用 {% data variables.enterprise.prodname_unified_contributions %}](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise) -Feature | Description | More information | -------- | ----------- | ---------------- |{% ifversion ghes %} -Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %} -{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %} -{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %} -{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[Enabling {% data variables.product.prodname_server_statistics %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %} -Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[Enabling {% data variables.enterprise.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" -Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[Enabling {% data variables.enterprise.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)" +## {% data variables.product.prodname_github_connect %} 的数据传输 -## Data transmission for {% data variables.product.prodname_github_connect %} - -When {% data variables.product.prodname_github_connect %} is enabled, a record on {% data variables.product.prodname_ghe_cloud %} stores information about the connection. If you enable individual features of {% data variables.product.prodname_github_connect %}, additional data is transmitted. +启用 {% data variables.product.prodname_github_connect %} 时，{% data variables.product.prodname_ghe_cloud %} 上的记录会存储有关连接的信息。 如果启用 {% data variables.product.prodname_github_connect %} 的各个功能，则会传输其他数据。 {% note %} -**Note:** No repositories, issues, or pull requests are ever transmitted from {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} by {% data variables.product.prodname_github_connect %}. +注意：{% data variables.product.prodname_github_connect %} 从未将存储库、问题或拉取请求从 {% data variables.product.product_name %} 传输到 {% data variables.product.prodname_dotcom_the_website %}。 {% endnote %} -### Data transmitted when {% data variables.product.prodname_github_connect %} is enabled +### 启用 {% data variables.product.prodname_github_connect %} 时传输的数据 -When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection. +当你启用 {% data variables.product.prodname_github_connect %} 或特定的 {% data variables.product.prodname_github_connect %} 功能时，{% data variables.product.prodname_ghe_cloud %} 上的记录将存储有关连接的以下信息。 {% ifversion ghes %} -- The public key portion of your {% data variables.product.prodname_ghe_server %} license -- A hash of your {% data variables.product.prodname_ghe_server %} license -- The customer name on your {% data variables.product.prodname_ghe_server %} license -- The version of {% data variables.location.product_location_enterprise %}{% endif %} -- The hostname of {% data variables.location.product_location %} -- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.location.product_location %} -- The authentication token that's used by {% data variables.location.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %} -- If Transport Layer Security (TLS) is enabled and configured on {% data variables.location.product_location %}{% ifversion ghes %} -- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.location.product_location %}, and the date and time of enablement{% endif %} -- The dormancy threshold for your enterprise -- The number of dormant users for your enterprise -- A count of license-consuming seats, which does not include suspended users +- {% data variables.product.prodname_ghe_server %} 许可的公钥部分 +- {% data variables.product.prodname_ghe_server %} 许可的哈希 +- {% data variables.product.prodname_ghe_server %} 许可上的客户名称 +- {% data variables.location.product_location_enterprise %}{% endif %} 的版本 +- {% data variables.location.product_location %} 的主机名 +- {% data variables.product.prodname_ghe_cloud %} 上连接到 {% data variables.location.product_location %} 的组织或企业帐户 +- {% data variables.location.product_location %} 用于向 {% data variables.product.prodname_ghe_cloud %} 发出请求的身份验证令牌 +- 是否在 {% data variables.location.product_location %}{% ifversion ghes %} 上启用并配置了传输层安全性 (TLS) +- 在 {% data variables.location.product_location %} 上启用的 {% data variables.product.prodname_github_connect %} 功能，以及启用日期和时间{% endif %} +- 企业休眠阈值 +- 企业休眠用户数 +- 许可证消耗的席位计数，其中不包括暂停的用户 -{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.location.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled. +{% data variables.product.prodname_github_connect %} 从启用 {% data variables.product.prodname_github_connect %} 的日期和大致时间开始每周同步 {% data variables.location.product_location %} 和 {% data variables.product.prodname_ghe_cloud %} 之间的上述连接数据。 -### Data transmitted by individual features of {% data variables.product.prodname_github_connect %} +### {% data variables.product.prodname_github_connect %} 的各个功能传输的数据 -Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}. +如果启用 {% data variables.product.prodname_github_connect %} 的各个功能，则会传输其他数据。 -Feature | Data | Which way does the data flow? | Where is the data used? | -------- | ---- | --------- | ------ |{% ifversion ghes %} -Automatic user license sync | Each {% data variables.product.product_name %} user's user ID and email addresses | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} -{% data variables.product.prodname_dependabot_alerts %} | Vulnerability alerts | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} -{% data variables.product.prodname_dependabot_updates %} | Dependencies and the metadata for each dependency's repository
If a dependency is stored in a private repository on {% data variables.product.prodname_dotcom_the_website %}, data will only be transmitted if {% data variables.product.prodname_dependabot %} is configured and authorized to access that repository. | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} -{% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}
From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %} -{% data variables.product.prodname_server_statistics %} | Aggregate metrics about your usage of {% data variables.product.prodname_ghe_server %}. For the complete list of metrics, see "[About {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)." | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} -Unified search | Search terms, search results | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}
From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | -Unified contributions | Contribution counts | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} | +功能 | 数据 | 数据流向何方？ | 在哪里使用了数据？ | ------- | ---- | --------- | ------ |{% ifversion ghes %} 用户许可证自动同步 | 每个 {% data variables.product.product_name %} 用户的用户 ID 和电子邮件地址 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae %} {% data variables.product.prodname_dependabot_alerts %} | 漏洞警报 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %} | {% data variables.product.product_name %} |{% endif %}{% ifversion dependabot-updates-github-connect %} {% data variables.product.prodname_dependabot_updates %} | 依赖项和每个依赖项存储库的元数据
如果依赖项存储在 {% data variables.product.prodname_dotcom_the_website %} 上的专用存储库中，则只有在 {% data variables.product.prodname_dependabot %} 配置并授权访问该存储库时才会传输数据。 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %} | {% data variables.product.product_name %} {% endif %} {% data variables.product.prodname_dotcom_the_website %} 操作 | 操作名称、操作（来自 {% data variables.product.prodname_marketplace %} 的 YAML 文件）| 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %}
从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}{% ifversion server-statistics %} {% data variables.product.prodname_server_statistics %} | 聚合有关 {% data variables.product.prodname_ghe_server %} 使用情况的指标。 有关指标的完整列表，请参阅“[关于 {% data variables.product.prodname_server_statistics %}](/admin/monitoring-activity-in-your-enterprise/analyzing-how-your-team-works-with-server-statistics/about-server-statistics#server-statistics-data-collected)”。 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_ghe_cloud %} | {% data variables.product.prodname_ghe_cloud %}{% endif %} 统一搜索 | 搜索词、搜索结果 | 从 {% data variables.product.prodname_dotcom_the_website %} 到 {% data variables.product.product_name %}
从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %} | 统一参与 | 参与计数 | 从 {% data variables.product.product_name %} 到 {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.prodname_dotcom_the_website %} | -## Further reading +## 延伸阅读 -- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation +- GraphQL API 文档中的“[企业帐户](/graphql/guides/managing-enterprise-accounts)” diff --git a/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md index d693ab2f7b..838c838941 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md +++ b/translations/zh-CN/content/admin/configuration/configuring-github-connect/managing-github-connect.md @@ -1,7 +1,7 @@ --- -title: Managing GitHub Connect +title: 管理 GitHub Connect shortTitle: Manage GitHub Connect -intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.location.product_location %}.' +intro: '可启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.location.product_location %} 的其他功能和工作流。' redirect_from: - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com @@ -20,71 +20,65 @@ topics: - GitHub Connect - Infrastructure - Networking +ms.openlocfilehash: 30a170543b63c390aa8975b1ca57c265bc7fa8fa +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160646' --- - {% data reusables.github-connect.beta %} -## About {% data variables.product.prodname_github_connect %} +## 关于 {% data variables.product.prodname_github_connect %} -You can access additional features and workflows on {% data variables.location.product_location %} by enabling {% data variables.product.prodname_github_connect %}. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." +可以通过启用 {% data variables.product.prodname_github_connect %} 来访问 {% data variables.location.product_location %} 上的其他功能和工作流。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。 -When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.location.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data reusables.github-connect.connection-port-protocol %} +启用 {% data variables.product.prodname_github_connect %} 时，需要在 {% data variables.location.product_location %} 与 {% data variables.product.prodname_ghe_cloud %} 上的组织或企业帐户之间配置连接。 {% data reusables.github-connect.connection-port-protocol %} -Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} uses the {% data variables.product.prodname_github_app %}'s credentials to make requests to {% data variables.product.prodname_ghe_cloud %}. +启用 {% data variables.product.prodname_github_connect %} 可以在 {% data variables.product.prodname_ghe_cloud %} 上创建组织或企业帐户所拥有的 {% data variables.product.prodname_github_app %}。 {% data variables.product.product_name %} 使用 {% data variables.product.prodname_github_app %} 的凭据向 {% data variables.product.prodname_ghe_cloud %} 发出请求。 -{% ifversion ghes %} -{% data variables.product.prodname_ghe_server %} stores credentials from the {% data variables.product.prodname_github_app %}. The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}. -- An authentication token, which is valid for one hour -- A private key, which is used to generate a new authentication token +{% ifversion ghes %} {% data variables.product.prodname_ghe_server %} 会存储来自 {% data variables.product.prodname_github_app %} 的凭据。 这些凭据将复制到任何高可用性或集群环境中的所有节点，并存储在任何备份中，包括由 {% data variables.product.prodname_enterprise_backup_utilities %} 创建的快照。 +- 有效期为一小时的身份验证令牌 +- 用于生成新的身份验证令牌的私钥 {% endif %} + +## 先决条件 + +若要使用 {% data variables.product.prodname_github_connect %}，必须在使用 {% data variables.product.prodname_ghe_cloud %} 的 {% data variables.product.prodname_dotcom_the_website %} 上拥有组织或企业帐户。 你可能已将 {% data variables.product.prodname_ghe_cloud %} 包含在计划中。 {% data reusables.enterprise.link-to-ghec-trial %} + +{% ifversion ghes %}如果 {% data variables.product.prodname_dotcom_the_website %} 上的组织或企业帐户使用 IP 允许列表，则必须将 {% data variables.location.product_location %} 的 IP 地址或网络添加到 {% data variables.product.prodname_dotcom_the_website %} 上的 IP 允许列表。 有关详细信息，请参阅 {% data variables.product.prodname_ghe_cloud %} 文档中的“[管理组织的允许 IP 地址](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)”或“[为企业中的安全设置实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)”。 + +若要配置连接，代理配置必须允许连接到 `github.com`、`api.github.com` 和 `uploads.github.com`。 有关详细信息，请参阅“[配置出站代理服务器](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)”。 {% endif %} -## Prerequisites +## 启用 {% data variables.product.prodname_github_connect %} -To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %} +如果企业所有者同时也是使用 {% data variables.product.prodname_ghe_cloud %} 的组织或企业帐户的所有者，可以启用 {% data variables.product.prodname_github_connect %}。 + +如果要将 {% data variables.location.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 上不属于企业帐户的组织，则必须以组织所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 + +如果要将 {% data variables.location.product_location %} 连接到 {% data variables.product.prodname_ghe_cloud %} 上企业帐户拥有的组织或者连接到企业帐户本身，则必须以企业所有者身份登录到 {% data variables.product.prodname_dotcom_the_website %}。 {% ifversion ghes %} -If your organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} uses IP allow lists, you must add the IP address or network for {% data variables.location.product_location %} to your IP allow list on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing allowed IP addresses for your organization](/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization)" and "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-allowed-ip-addresses-for-organizations-in-your-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation. - -To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. For more information, see "[Configuring an outbound web proxy server](/enterprise/admin/guides/installation/configuring-an-outbound-web-proxy-server)." -{% endif %} - -## Enabling {% data variables.product.prodname_github_connect %} - -Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}. - -If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner. - -If you're connecting {% data variables.location.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner. - -{% ifversion ghes %} -1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.github-connect-tab %}{% else %} -1. Sign in to {% data variables.location.product_location %} and {% data variables.product.prodname_dotcom_the_website %}. +1. 登录到 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %}{% else %} +1. 登录到 {% data variables.location.product_location %} 和 {% data variables.product.prodname_dotcom_the_website %}。 {% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %} -1. Under "{% data variables.product.prodname_github_connect %} is not enabled yet", click **Enable {% data variables.product.prodname_github_connect %}**. By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features." -{% ifversion ghes %} - {% else %} -  -{% endif %} -1. Next to the enterprise account or organization you'd like to connect, click **Connect**. -  +1. 在“{% data variables.product.prodname_github_connect %} 尚未启用”下，单击“启用 {% data variables.product.prodname_github_connect %}”。 单击“启用 {% data variables.product.prodname_github_connect %}”，表示你同意“{% data variables.product.prodname_dotcom %} 其他产品和功能的条款”。 +{% ifversion ghes %} {% else %}  {% endif %} +1. 在要连接的企业帐户或组织旁，单击“连接”。 +  -## Disabling {% data variables.product.prodname_github_connect %} +## 禁用 {% data variables.product.prodname_github_connect %} -Enterprise owners can disable {% data variables.product.prodname_github_connect %}. +企业所有者可以禁用 {% data variables.product.prodname_github_connect %}。 -When you disconnect from {% data variables.product.prodname_ghe_cloud %}, the {% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} is deleted from your enterprise account or organization and credentials stored on {% data variables.location.product_location %} are deleted. +与 {% data variables.product.prodname_ghe_cloud %} 断开连接后，{% data variables.product.prodname_github_connect %} {% data variables.product.prodname_github_app %} 会从企业帐户或组织中删除，{% data variables.location.product_location %} 上存储的凭据也会删除。 -{% data reusables.enterprise-accounts.access-enterprise %} -{% data reusables.enterprise-accounts.github-connect-tab %} -1. Next to the enterprise account or organization you'd like to disconnect, click **Disable {% data variables.product.prodname_github_connect %}**. -{% ifversion ghes %} -  -1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. -  -{% else %} -  -1. Read the information about disconnecting and click **Disable {% data variables.product.prodname_github_connect %}**. -  -{% endif %} +{% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.github-connect-tab %} +1. 在要断开连接的企业帐户或组织旁，单击“禁用 {% data variables.product.prodname_github_connect %}”。 +{% ifversion ghes %}  +1. 阅读有关断开连接的信息，并单击“禁用 {% data variables.product.prodname_github_connect %}”。 +  +{% else %}  +1. 阅读有关断开连接的信息，并单击“禁用 {% data variables.product.prodname_github_connect %}”。 +  {% endif %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md index da2928d54d..2004173a21 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/network-ports.md @@ -1,5 +1,5 @@ --- -title: Network ports +title: 网络端口 redirect_from: - /enterprise/admin/articles/configuring-firewalls - /enterprise/admin/articles/firewall @@ -8,7 +8,7 @@ redirect_from: - /enterprise/admin/installation/network-ports - /enterprise/admin/configuration/network-ports - /admin/configuration/network-ports -intro: 'Open network ports selectively based on the network services you need to expose for administrators, end users, and email support.' +intro: 根据您需要为管理员、最终用户和电子邮件支持显示的网络服务有选择地打开网络端口。 versions: ghes: '*' type: reference @@ -17,56 +17,62 @@ topics: - Infrastructure - Networking - Security +ms.openlocfilehash: 048b27ed44cea11057c781ae3043078a825f8d1a +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160652' --- -## Administrative ports +## 管理端口 -Some administrative ports are required to configure {% data variables.location.product_location %} and run certain features. Administrative ports are not required for basic application use by end users. +配置 {% data variables.location.product_location %} 并运行某些功能需要一些管理端口。 最终用户在使用基本应用程序时不需要管理端口。 -| Port | Service | Description | +| 端口 | 服务 | 说明 | |---|---|---| -| 8443 | HTTPS | Secure web-based {% data variables.enterprise.management_console %}. Required for basic installation and configuration. | -| 8080 | HTTP | Plain-text web-based {% data variables.enterprise.management_console %}. Not required unless TLS is disabled manually. | -| 122 | SSH | Shell access for {% data variables.location.product_location %}. Required to be open to incoming connections between all nodes in a high availability configuration. The default SSH port (22) is dedicated to Git and SSH application network traffic. | -| 1194/UDP | VPN | Secure replication network tunnel in high availability configuration. Required to be open for communication between all nodes in the configuration.| -| 123/UDP| NTP | Required for time protocol operation. | -| 161/UDP | SNMP | Required for network monitoring protocol operation. | +| 8443 | HTTPS | 基于安全 Web 的 {% data variables.enterprise.management_console %}。 进行基本安装和配置时需要。 | +| 8080 | HTTP | 基于纯文本 Web 的 {% data variables.enterprise.management_console %}。 除非手动禁用 TLS，否则不需要。 | +| 122 | SSH | {% data variables.location.product_location %} 的 shell 访问权限。 需要对高可用性配置中所有节点之间的传入连接开放。 默认 SSH 端口 (22) 专用于 Git 和 SSH 应用程序网络流量。 | +| 1194/UDP | VPN | 采用高可用性配置的安全复制网络隧道。 需要对配置中所有节点之间的通信开放。| +| 123/UDP| NTP | 为时间协议操作所需。 | +| 161/UDP | SNMP | 为网络监视协议操作所需。 | -## Application ports for end users +## 最终用户的应用程序端口 -Application ports provide web application and Git access for end users. +应用程序端口为最终用户提供 Web 应用程序和 Git 访问。 -| Port | Service | Description | +| 端口 | 服务 | 说明 | |---|---|---| -| 443 | HTTPS | Access to the web application and Git over HTTPS. | -| 80 | HTTP | Access to the web application. All requests are redirected to the HTTPS port if TLS is configured. | -| 22 | SSH | Access to Git over SSH. Supports clone, fetch, and push operations to public and private repositories. | -| 9418 | Git | Git protocol port supports clone and fetch operations to public repositories with unencrypted network communication. {% data reusables.enterprise_installation.when-9418-necessary %} | +| 443 | HTTPS | 通过 HTTPS 访问 Web 应用程序和 Git。 | +| 80 | HTTP | 访问 Web 应用程序。 如果配置了 TLS，则所有请求都将重定向到 HTTPS 端口。 | +| 22 | SSH | 通过 SSH 访问 Git。 支持对公共和私有仓库执行克隆、提取和推送操作。 | +| 9418 | Git | Git 协议端口支持通过未加密网络通信对公共仓库执行克隆和提取操作。 {% data reusables.enterprise_installation.when-9418-necessary %} | {% data reusables.enterprise_installation.terminating-tls %} -## Email ports +## 电子邮件端口 -Email ports must be accessible directly or via relay for inbound email support for end users. +电子邮件端口必须可直接访问或通过中继访问，以便为最终用户提供入站电子邮件支持。 -| Port | Service | Description | +| 端口 | 服务 | 说明 | |---|---|---| -| 25 | SMTP | Support for SMTP with encryption (STARTTLS). | +| 25 | SMTP | 支持采用加密的 SMTP (STARTTLS)。 | -## {% data variables.product.prodname_actions %} ports +## {% data variables.product.prodname_actions %} 端口 -{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.location.product_location %}. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)." +{% data variables.product.prodname_actions %} 端口必须可供自托管运行器访问才能连接到 {% data variables.location.product_location %}。 有关详细信息，请参阅[关于自承载运行器](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)。 -| Port | Service | Description | +| 端口 | 服务 | 说明 | |---|---|---| -| 443 | HTTPS | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is configured. -| 80 | HTTP | Self-hosted runners connect to {% data variables.location.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured. +| 443 | HTTPS | 自托管运行器连接到 {% data variables.location.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果配置了 TLS 则必填。 +| 80 | HTTP | 自托管运行器连接到 {% data variables.location.product_location %} 以接收作业分配并下载新版本的运行器应用程序。 如果未配置 TLS 则必填。 -If you enable automatic access to {% data variables.product.prodname_dotcom_the_website %} actions, {% data variables.product.prodname_actions %} will always search for an action on {% data variables.location.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)." +如果启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问，{% data variables.product.prodname_actions %} 将始终先通过这些端口搜索 {% data variables.location.product_location %} 上的操作，然后再检查 {% data variables.product.prodname_dotcom_the_website %}。 有关详细信息，请参阅“[使用 {% data variables.product.prodname_github_connect %} 启用对 {% data variables.product.prodname_dotcom_the_website %} 操作的自动访问](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect#about-resolution-for-actions-using-github-connect)。” -## {% data variables.product.prodname_github_connect %} ports +## {% data variables.product.prodname_github_connect %} 端口 -If you enable {% data variables.product.prodname_github_connect %}, the connection between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %} uses HTTPS over ports 443 or 80, and TLS is required. For more information, see "[About {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)." +如果启用 {% data variables.product.prodname_github_connect %}，则 {% data variables.product.product_name %} 和 {% data variables.product.prodname_dotcom_the_website %} 之间的连接使用 HTTPS 通过端口 443 或 80，并且需要 TLS。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/about-github-connect)”。 -## Further reading +## 延伸阅读 -- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)" +- “[配置 TLS](/admin/configuration/configuring-network-settings/configuring-tls)” 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 28132548ca..ff7a0ab59b 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 @@ -1,7 +1,7 @@ --- -title: About {% data variables.product.prodname_emus %} +title: '关于 {% data variables.product.prodname_emus %}' 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.' +intro: '可以从标识提供者的 {% data variables.product.prodname_dotcom %} 上集中管理企业成员的标识和访问。' 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 @@ -17,50 +17,55 @@ topics: - Enterprise - SSO allowTitleToDifferFromFilename: true +ms.openlocfilehash: 82a8b8c29ea38d57f0481146f2a857c2dcba8413 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160726' --- +## 关于 {% data variables.product.prodname_emus %} -## About {% data variables.product.prodname_emus %} +使用 {% data variables.product.prodname_emus %}，可以通过标识提供者 (IdP) 控制企业成员的用户帐户。 IdP 中分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将会预配为 {% data variables.product.prodname_dotcom %} 上的新用户帐户，并添加到企业中。 可以通过 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.enterprise.prodname_managed_user %} the role of user, enterprise owner, or billing manager. {% data variables.enterprise.prodname_managed_users_caps %} can own organizations within your enterprise and can add other {% data variables.enterprise.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)." +在 IdP 中，你可以为每个 {% data variables.enterprise.prodname_managed_user %} 提供用户、企业所有者或计费管理员的角色。 {% data variables.enterprise.prodname_managed_users_caps %} 可以拥有企业内的组织，并且可以将其他 {% data variables.enterprise.prodname_managed_users %} 添加到组织和其中的团队。 有关详细信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”和“[关于组织](/organizations/collaborating-with-groups-in-organizations/about-organizations)”。 {% ifversion oidc-for-emu %} -{% data reusables.enterprise-accounts.emu-cap-validates %} For more information, see "[About support for your IdP's Conditional Access Policy](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)." +{% data reusables.enterprise-accounts.emu-cap-validates %} 有关详细信息，请参阅“[关于对 IdP 的条件访问策略的支持](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/about-support-for-your-idps-conditional-access-policy)”。 {% endif %} -You can grant {% data variables.enterprise.prodname_managed_users %} access to and the ability to contribute to repositories within your enterprise, but {% data variables.enterprise.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.enterprise.prodname_managed_users %}](#abilities-and-restrictions-of-enterprise-managed-users)." +可以授予 {% data variables.enterprise.prodname_managed_users %} 访问权限以及参与企业内部存储库的能力，但 {% data variables.enterprise.prodname_managed_users %} 无法创建公共内容，也不能与其他用户、组织和企业协作处理 {% data variables.product.prodname_dotcom %} 的其余部分。 有关详细信息，请参阅“[{% data variables.enterprise.prodname_managed_users %} 的功能和限制](#abilities-and-restrictions-of-enterprise-managed-users)”。 -The usernames of your enterprise's {% data variables.enterprise.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)." +企业的 {% data variables.enterprise.prodname_managed_users %} 的用户名及其个人资料信息（例如显示名称和电子邮件地址）通过 IdP 设置，用户无法自行更改。 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。 -Enterprise owners can audit all of the {% data variables.enterprise.prodname_managed_users %}' actions on {% data variables.product.prodname_dotcom %}. For more information, see "[Audit log events for your enterprise](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)." +企业所有者可以在 {% data variables.product.prodname_dotcom %} 上审核所有 {% data variables.enterprise.prodname_managed_users %} 的操作。 有关详细信息，请参阅“[企业的审核日志事件](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise#about-audit-log-events-for-your-enterprise)”。 -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)." +若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 有关创建此帐户的详细信息，请参阅“[关于具有托管用户的企业](#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)." +注意：使用 {% data variables.product.prodname_ghe_cloud %} 进行标识和访问管理有多个选项，而 {% data variables.product.prodname_emus %} 并不是每个客户的最佳解决方案。 如需详细了解 {% data variables.product.prodname_emus %} 是否适合你的企业，请参阅“[关于企业身份验证](/admin/identity-and-access-management/managing-iam-for-your-enterprise/about-authentication-for-your-enterprise#identifying-the-best-authentication-method-for-your-enterprise)”。 {% endnote %} -## About organization membership management +## 关于组织成员身份管理 -Organization memberships can be managed manually, or you can update memberships automatically using IdP groups. To manage organization memberships through your IdP, the members must be added to an IdP group, and the IdP group must be connected to a team within the organization. For more information about managing organization and team memberships 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)." +可手动管理组织成员身份，也可使用 IdP 组自动更新成员身份。 要通过 IdP 管理组织成员身份，必须将成员添加到 IdP 组，并且 IdP 组必须连接到组织内的团队。 有关自动管理组织和团队成员身份的详细信息，请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。 -The way a member is added to an organization owned by your enterprise (through IdP groups or manually) determines how they must be removed from an organization. +将成员添加到企业拥有的组织的方式（通过 IdP 组或手动）决定了必须如何从组织中删除他们。 -- If a member was added to an organization manually, you must remove them manually. 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. -- If a user became a member of an organization because they were added to IdP groups mapped to one or more teams in the organization, removing them from _all_ of the mapped IdP groups associated with the organization will remove them from the organization. +- 如果将成员手动添加到组织，则必须手动将其删除。 从 IdP 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配他们，将暂停用户，但不会将其从组织中删除。 +- 如果用户由于被添加到映射到组织中的一个或多个团队的 IdP 组而成为该组织的成员，则从与组织关联的所有映射的 IdP 组中删除这些用户会将其从组织中删除。 -To discover how a member was added to an organization, you can filter the member list by type. For more information, see "[Viewing people in your enterprise](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)." +要了解成员是如何添加到组织中的，可以按类型筛选成员列表。 有关详细信息，请参阅[查看企业中的人员](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#filtering-by-member-type-in-an-enterprise-with-managed-users)。 -## Identity provider support +## 标识提供者支持 -{% data variables.product.prodname_emus %} supports the following IdPs{% ifversion oidc-for-emu %} and authentication methods: +{% data variables.product.prodname_emus %} 支持以下 IdP{% ifversion oidc-for-emu %} 和身份验证方法： -| | SAML | OIDC (beta) | +| | SAML | OIDC（beta 版本） | |----------------------------------|-----------------------------------------------|-----------------------------------------------| | Azure Active Directory | {% octicon "check" aria-label="Check icon" %} | {% octicon "check" aria-label="Check icon" %} | | Okta | {% octicon "check" aria-label="Check icon" %} | | @@ -70,36 +75,36 @@ To discover how a member was added to an organization, you can filter the member {% endif %} -## Abilities and restrictions of {% data variables.enterprise.prodname_managed_users %} +## {% data variables.enterprise.prodname_managed_users %} 的功能和限制 -{% data variables.enterprise.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.enterprise.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.enterprise.prodname_managed_users_caps %} 只能参与企业中的专用和内部存储库及其用户帐户拥有的专用存储库。 {% data variables.enterprise.prodname_managed_users_caps %} 对更广泛的 {% data variables.product.prodname_dotcom %} 社区具有只读访问权限。 这些针对用户和内容的可见性和访问限制适用于所有请求，包括 API 请求。 -* {% data variables.enterprise.prodname_managed_users_caps %} cannot be invited to organizations or repositories outside of the enterprise, nor can the {% data variables.enterprise.prodname_managed_users %} be invited to other enterprises. -* Outside collaborators are not supported by {% data variables.product.prodname_emus %}. -* {% data variables.enterprise.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.enterprise.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.enterprise.prodname_managed_users_caps %} and the content they create is only visible to other members of the enterprise. -* {% data variables.enterprise.prodname_managed_users_caps %} cannot follow users outside of the enterprise. -* {% data variables.enterprise.prodname_managed_users_caps %} cannot create gists or comment on gists. -* {% data variables.enterprise.prodname_managed_users_caps %} cannot create starter workflows for {% data variables.product.prodname_actions %}. -* {% data variables.enterprise.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.enterprise.prodname_managed_user %} to collaborate. -* You can choose whether {% data variables.enterprise.prodname_managed_users %} are able to create repositories owned by their user accounts. For more information, see "[Enforcing repository management policies in your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)." -* If you allow {% data variables.enterprise.prodname_managed_users %} to create repositories owned by their user accounts, they can only own private repositories and can only invite other enterprise members to collaborate on their user-owned repositories. +* 不能邀请 {% data variables.enterprise.prodname_managed_users_caps %} 加入企业外部的组织或存储库，也不能邀请 {% data variables.enterprise.prodname_managed_users %} 加入其他企业。 +* {% data variables.product.prodname_emus %} 不支持外部协作者。 +* {% data variables.enterprise.prodname_managed_users_caps %} 无法在企业外部的存储库中创建问题或拉取请求、添加评论或添加反应，也不能加注星标、监视或创建分支。 +* {% data variables.enterprise.prodname_managed_users_caps %} 可以查看 {% data variables.product.prodname_dotcom_the_website %} 上的所有公共存储库，但无法将代码推送到企业外部的存储库。 +* {% data variables.enterprise.prodname_managed_users_caps %} 和创建的内容只对企业的其他成员可见。 +* {% data variables.enterprise.prodname_managed_users_caps %} 无法关注企业外部的用户。 +* {% data variables.enterprise.prodname_managed_users_caps %} 无法创建 Gist 或对 Gist 添加评论。 +* {% data variables.enterprise.prodname_managed_users_caps %} 无法为 {% data variables.product.prodname_actions %} 创建入门工作流。 +* {% data variables.enterprise.prodname_managed_users_caps %} 无法在其用户帐户上安装 {% data variables.product.prodname_github_apps %}。 +* 其他 {% data variables.product.prodname_dotcom %} 用户无法查看、提及或邀请 {% data variables.enterprise.prodname_managed_user %} 进行协作。 +* 可以选择 {% data variables.enterprise.prodname_managed_users %} 是否能够创建其用户帐户拥有的存储库。 有关详细信息，请参阅“[在企业中实施存储库管理策略](/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-repository-creation)”。 +* 如果允许 {% data variables.enterprise.prodname_managed_users %} 创建其用户帐户拥有的存储库，则他们只能拥有专用存储库，并且只能邀请其他企业成员协作处理其用户拥有的存储库。 * {% data reusables.enterprise-accounts.emu-forks %} -* Only private and internal repositories can be created in organizations owned by an {% data variables.enterprise.prodname_emu_enterprise %}, depending on organization and enterprise repository visibility settings. -* {% data variables.enterprise.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)." +* 只能在 {% data variables.enterprise.prodname_emu_enterprise %} 拥有的组织中创建专用和内部存储库，具体取决于组织和企业存储库可见性设置。 +* {% data variables.enterprise.prodname_managed_users_caps %} 在使用 {% data variables.product.prodname_pages %} 方面受到限制。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_pages %}](/pages/getting-started-with-github-pages/about-github-pages#limitations-for-enterprise-managed-users)”。 * {% data reusables.copilot.emus-cannot-use-copilot %} -## Getting started with {% data variables.product.prodname_emus %} +## {% data variables.product.prodname_emus %} 入门 -Before your developers can use {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_emus %}, you must follow a series of configuration steps. +必须先执行一系列配置步骤，开发人员才能将 {% data variables.product.prodname_ghe_cloud %} 与 {% data variables.product.prodname_emus %} 一起使用。 -1. To use {% data variables.product.prodname_emus %}, you need a separate type of enterprise account with {% data variables.product.prodname_emus %} enabled. To try out {% data variables.product.prodname_emus %} or to discuss options for migrating from your existing enterprise, please contact [{% data variables.product.prodname_dotcom %}'s Sales team](https://enterprise.github.com/contact). +1. 若要使用 {% data variables.product.prodname_emus %}，需要启用了 {% data variables.product.prodname_emus %} 的单独企业帐户类型。 若要试用 {% data variables.product.prodname_emus %} 或讨论从现有企业迁移的选项，请联系 [{% data variables.product.prodname_dotcom %} 的销售团队](https://enterprise.github.com/contact)。 - Your contact on the GitHub Sales team will work with you to create your new {% data variables.enterprise.prodname_emu_enterprise %}. You'll need to provide the email address for the user who will set up your enterprise and a short code that will be used as the suffix for your enterprise members' usernames. {% data reusables.enterprise-accounts.emu-shortcode %} For more information, see "[Usernames and profile information](#usernames-and-profile-information)." + GitHub 销售团队的联系人将与你合作创建新的 {% data variables.enterprise.prodname_emu_enterprise %}。 你需要为将设置企业的用户提供电子邮件地址，以及一个短代码，该代码将用作企业成员用户名的后缀。 {% data reusables.enterprise-accounts.emu-shortcode %} 有关详细信息，请参阅“[用户名和个人资料信息](#usernames-and-profile-information)”。 -2. After we create your enterprise, you will receive an email from {% data variables.product.prodname_dotcom %} inviting you to choose a password for your enterprise's setup user, which will be the first owner in the enterprise. Use an incognito or private browsing window when setting the password. The setup user is only used to configure single sign-on and SCIM provisioning integration for the enterprise. It will no longer have access to administer the enterprise account once SSO is successfully enabled. The setup user's username is your enterprise's shortcode suffixed with `_admin`. +2. 创建企业后，你将收到来自 {% data variables.product.prodname_dotcom %} 的电子邮件，邀请你为企业的设置用户选择密码，该用户将是企业的第一个所有者。 设置密码时，请使用隐身或专用浏览窗口。 设置用户仅用于为企业配置单一登录和 SCIM 预配集成。 成功启用 SSO 后，设置用户将不再有权管理企业帐户。 设置用户的用户名是企业的短代码，后缀为 `_admin`。 {% note %} @@ -107,54 +112,53 @@ Before your developers can use {% data variables.product.prodname_ghe_cloud %} w {% endnote %} -3. After you log in as the setup user, we recommend enabling two-factor authentication. For more information, see "[Configuring two-factor authentication](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)." +3. 你以设置用户身份登录后，我们建议你启用双因素身份验证。 有关详细信息，请参阅“[配置双因素身份验证](/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)”。 -1. To get started, configure {% ifversion oidc-for-emu %}how your members will authenticate. If you are using Azure Active Directory as your identity provider, you can choose between OpenID Connect (OIDC) and Security Assertion Markup Language (SAML). Both options provide a seamless sign-in experience for your members, but only OIDC includes support for Conditional Access Policies (CAP). If you are using Okta as your identity provider, you can use SAML to authenticate your members.{% else %}SAML SSO for your enterprise. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)."{% endif %} +1. 首先，请配置 {% ifversion oidc-for-emu %} 成员如何进行身份验证。 如果使用 Azure Active Directory 作为标识提供者，可以在 OpenID Connect (OIDC) 和安全断言标记语言 (SAML) 之间进行选择。 这两个选项都为成员提供无缝登录体验，但只有 OIDC 包括对条件访问策略 (CAP) 的支持。 如果使用 Okta 作为标识提供者，则可以使用 SAML 对成员进行身份验证。{% else %}SAML SSO 适用于企业。 有关详细信息，请参阅“[为 Enterprise 托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。{% endif %} {% ifversion oidc-for-emu %} - To get started, read the guide for your chosen authentication method. + 首先，请阅读所选身份验证方法的指南。 - - "[Configuring OIDC for Enterprise Managed Users](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)." - - "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." + - “[为企业托管用户配置 OIDC](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-oidc-for-enterprise-managed-users)”。 + - “[为企业托管用户配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。 {% endif %} -4. Once you have configured SSO, you can configure SCIM provisioning. SCIM is how your identity provider will create {% data variables.enterprise.prodname_managed_users %} on {% data variables.product.prodname_dotcom_the_website %}. For more information on configuring SCIM provisioning, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." +4. 配置 SSO 后，可以配置 SCIM 预配。 SCIM 是标识提供者在 {% data variables.product.prodname_dotcom_the_website %} 上创建 {% data variables.enterprise.prodname_managed_users %} 的方式。 有关配置 SCIM 预配的详细信息，请参阅“[为企业托管用户配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 -5. Once authentication and provisioning are configured, you can start managing organization membership for your {% data variables.enterprise.prodname_managed_users %} by synchronizing IdP groups with teams. For more information, see "[Managing team memberships with identity provider groups](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)." +5. 配置身份验证和预配后，可以通过将 IdP 组与团队同步来开始管理 {% data variables.enterprise.prodname_managed_users %} 的组织成员身份。 有关详细信息，请参阅[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups)。 -If members of your enterprise must use one workstation to contribute to repositories on {% data variables.location.product_location %} from both a {% data variables.enterprise.prodname_managed_user %} and a personal account, you can provide support. For more information, see "[Supporting developers with multiple user accounts on {% data variables.product.prodname_dotcom_the_website %}](#supporting-developers-with-multiple-user-accounts-on-githubcom)." +如果企业成员必须使用一个工作站同时从 {% data variables.enterprise.prodname_managed_user %} 和个人帐户参与 {% data variables.location.product_location %} 上的存储库，则可以提供支持。 有关详细信息，请参阅“[支持在 {% data variables.product.prodname_dotcom_the_website %} 上具有多个用户帐户的开发人员](#supporting-developers-with-multiple-user-accounts-on-githubcom)”。 -## Authenticating as a {% data variables.enterprise.prodname_managed_user %} +## 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证 -{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their identity provider. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}. +{% data variables.enterprise.prodname_managed_users_caps %} 必须通过其标识提供者进行身份验证。 若要进行身份验证，{% data variables.enterprise.prodname_managed_user %} 可以访问其 IdP 应用程序门户或使用 {% data variables.product.prodname_dotcom_the_website %} 上的登录页。 -By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[Enforcing policies for security settings in your enterprise](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)." +默认情况下，当未经身份验证的用户尝试访问使用 {% data variables.product.prodname_emus %} 的企业时，{% data variables.product.company_short %} 会显示 404 错误。 企业所有者可以选择性地启用自动重定向到单一登录 (SSO)，而不会显示 404。 有关详细信息，请参阅“[为企业中的安全设置强制实施策略](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)”。 -{% 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)." +{% data reusables.enterprise-accounts.about-recovery-codes %} 有关详细信息，请参阅“[管理企业的恢复代码](/admin/identity-and-access-management/managing-recovery-codes-for-your-enterprise)”。 -### Authenticating as a {% data variables.enterprise.prodname_managed_user %} via {% data variables.product.prodname_dotcom_the_website %} +### 通过 {% data variables.product.prodname_dotcom_the_website %} 作为 {% data variables.enterprise.prodname_managed_user %} 进行身份验证 -1. Navigate to [https://github.com/login](https://github.com/login). -1. In the "Username or email address" text box, enter your username including the underscore and short code. -  - When the form recognizes your username, the form will update. You do not need to enter your password on this form. -1. To continue to your identity provider, click **Sign in with your identity provider**. -  +1. 导航到 [https://github.com/login](https://github.com/login)。 +1. 在“用户名或电子邮件地址”文本框中，输入用户名，包括下划线和短代码。 +  表单识别用户名后将更新。 无需在此表单中输入密码。 +1. 若要继续访问标识提供者，请单击“使用标识提供者登录”。 +  -## Usernames and profile information +## 用户名和个人资料信息 -{% data variables.product.product_name %} automatically creates a username for each person by normalizing an identifier provided by your IdP. For more information, see "[Username considerations for external authentication](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)." +{% data variables.product.product_name %} 通过规范 IdP 提供的标识符自动为每个用户创建用户名。 有关详细信息，请参阅“[外部身份验证的用户名注意事项](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication)”。 -A conflict may occur when provisioning users if the unique parts of the identifier provided by your IdP are removed during normalization. If you're unable to provision a user due to a username conflict, you should modify the username provided by your IdP. For more information, see "[Resolving username problems](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)." +如果在规范化期间删除 IdP 提供的标识符的唯一部分，则预配用户时可能会发生冲突。 如果由于用户名冲突而无法预配用户，则应修改 IdP 提供的用户名。 有关详细信息，请参阅“[解决用户名问题](/admin/identity-and-access-management/managing-iam-for-your-enterprise/username-considerations-for-external-authentication#resolving-username-problems)”。 {% data reusables.enterprise-accounts.emu-only-emails-within-the-enterprise-can-conflict %} -The profile name and email address of a {% data variables.enterprise.prodname_managed_user %} is also provided by the IdP. {% data variables.enterprise.prodname_managed_users_caps %} cannot change their profile name or email address on {% data variables.product.prodname_dotcom %}, and the IdP can only provide a single email address. +IdP 还提供了 {% data variables.enterprise.prodname_managed_user %} 的个人资料名称和电子邮件地址。 {% data variables.enterprise.prodname_managed_users_caps %} 无法更改 {% data variables.product.prodname_dotcom %} 上的个人资料名称或电子邮件地址，并且 IdP 仅可提供单个电子邮件地址。 -## Supporting developers with multiple user accounts on {% data variables.location.product_location %} +## 支持在 {% data variables.location.product_location %} 上具有多个用户帐户的开发人员 -People on your team may need to contribute to resources on {% data variables.location.product_location %} that are outside of your {% data variables.enterprise.prodname_emu_enterprise %}. For example, you may wish to maintain a separate enterprise for your company's open source projects. Because a {% data variables.enterprise.prodname_managed_user %} cannot contribute to public resources, users will need to maintain a separate, personal account for this work. +团队中的人员可能需要在 {% data variables.location.product_location %} 上参与 {% data variables.enterprise.prodname_emu_enterprise %} 外部的资源。 例如，你可能希望为公司的开放源代码项目维护单独的企业。 由于 {% data variables.enterprise.prodname_managed_user %} 无法参与公共资源，因此用户需要为此工作维护单独的个人帐户。 -People who must contribute from two user accounts on {% data variables.location.product_location %} using one workstation can configure Git to simplify the process. For more information, see "[Managing multiple accounts](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)." +必须使用一个工作站在 {% data variables.location.product_location %} 上从两个用户帐户进行参与的人员可以配置 Git 以简化该过程。 有关详细信息，请参阅“[管理多个帐户](/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts)”。 diff --git a/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 b/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 index 7e7b0137be..45afb909ee 100644 --- a/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 +++ b/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 @@ -1,7 +1,7 @@ --- -title: Configuring SCIM provisioning for Enterprise Managed Users with Okta +title: 使用 Okta 为企业托管用户配置 SCIM 预配 shortTitle: Set up provisioning with Okta -intro: You can provision new users and manage their membership of your enterprise and teams using Okta as your identity provider. +intro: 您可以使用 Okta 作为身份提供商来预配新用户并管理其企业和团队的成员身份。 product: '{% data reusables.gated-features.emus %}' versions: ghec: '*' @@ -17,81 +17,86 @@ topics: - Authentication - Enterprise - SSO +ms.openlocfilehash: b8c086d1d91c1248fa5a0349bb6f8ef32c3bbdf0 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160710' --- +## 关于使用 Okta 进行预配 -## About provisioning with Okta +您可以使用 {% data variables.product.prodname_emus %} Okta 作为您的身份提供商来预配新帐户、管理企业成员身份以及管理企业中组织的团队成员身份。 有关预配 {% data variables.product.prodname_emus %} 的详细信息，请参阅“[为 Enterprise Managed User 配置 SCIM 预配](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)”。 -You can use {% data variables.product.prodname_emus %} with Okta as your identity provider to provision new accounts, manage enterprise membership, and manage team memberships for organizations in your enterprise. For more information about provisioning for {% data variables.product.prodname_emus %}, see "[Configuring SCIM provisioning for enterprise managed users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users)." +在使用 Okta 配置预配之前，必须配置 SAML 单点登录。 有关详细信息，请参阅“[为 Enterprise Managed User 配置 SAML 单一登录](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)”。 -Before you can configure provisioning with Okta, you must configure SAML single-sign on. For more information, see "[Configuring SAML single sign-on for Enterprise Managed Users](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-saml-single-sign-on-for-enterprise-managed-users)." +要使用 Okta 配置预配，必须在 {% data variables.product.prodname_emu_idp_application %} 应用程序中设置企业名称，并输入安装用户的 {% data variables.product.pat_generic %}。 然后，您可以在 Okta 中开始预配用户。 -To configure provisioning with Okta, you must set your enterprise's name in the {% data variables.product.prodname_emu_idp_application %} application and enter your setup user's {% data variables.product.pat_generic %}. You can then start provisioning users in Okta. +## 支持的功能 -## Supported features +{% data variables.product.prodname_emus %} 支持 Okta 中的许多预配功能。 -{% data variables.product.prodname_emus %} supports many provisioning features in Okta. - -| Feature | Description | +| 功能 | 说明 | | --- | --- | -| Push New Users | Users that are assigned to the {% data variables.product.prodname_emu_idp_application %} application in Okta are automatically created in the enterprise on {% data variables.product.product_name %}. | -| Push Profile Update | Updates made to the user's profile in Okta will be pushed to {% data variables.product.product_name %}. | -| Push Groups | Groups in Okta that are assigned to the {% data variables.product.prodname_emu_idp_application %} application as Push Groups are automatically created in the enterprise on {% data variables.product.product_name %}. | -| Push User Deactivation | Unassigning the user from the {% data variables.product.prodname_emu_idp_application %} application in Okta will disable the user on {% data variables.product.product_name %}. The user will not be able to sign in, but the user's information is maintained. | -| Reactivate Users | Users in Okta whose Okta accounts are reactivated and who are assigned back to the {% data variables.product.prodname_emu_idp_application %} application will be enabled. | +| 推送新用户 | 分配给 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户将在 {% data variables.product.product_name %} 上自动创建。 | +| 推送配置文件更新 | 对 Okta 中的用户配置文件所做的更新将被推送到 {% data variables.product.product_name %}。 | +| 推送组 | Okta 中作为推送组分配给 {% data variables.product.prodname_emu_idp_application %} 应用程序的组将在 {% data variables.product.product_name %} 上自动创建。 | +| 推送用户停用 | 从 Okta 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序中取消分配用户将在 {% data variables.product.product_name %} 上禁用该用户。 用户将无法登录，但会保留用户的信息。 | +| 重新激活用户 | 将启用 Okta 中已重新激活其 Okta 帐户并将其分配回 {% data variables.product.prodname_emu_idp_application %} 应用程序的用户。 | {% note %} -**Note:** {% data variables.product.prodname_emus %} does not support modifications to usernames. +**注意：** {% data variables.product.prodname_emus %} 不支持修改用户名。 {% endnote %} -## Setting your enterprise name +## 设置企业名称 -After your {% data variables.enterprise.prodname_emu_enterprise %} has been created, you can begin to configure provisioning by setting your enterprise name in Okta. +创建 {% data variables.enterprise.prodname_emu_enterprise %} 后，可以通过在 Okta 中设置企业名称来开始配置预配。 -1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. -1. Click the **Sign On** tab. -1. To make changes, click **Edit**. -1. Under "Advanced Sign-on Settings", in the "Enterprise Name" text box, type your enterprise name. For example, if you access your enterprise at `https://github.com/enterprises/octoinc`, your enterprise name would be "octoinc". - -1. To save your enterprise name, click **Save**. +1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 +1. 单击“登录”选项卡。 +1. 若要进行更改，请单击“编辑”。 +1. 在“Advanced Sign-on Settings（高级登录设置）”下的“Enterprise Name（企业名称）”文本框中，键入您的企业名称。 例如，如果你在 `https://github.com/enterprises/octoinc` 访问你的企业，则你的企业名称将为“octoinc”。 + +1. 若要保存企业名称，请单击“保存”。 -## Configuring provisioning +## 配置预配 -After setting your enterprise name, you can proceed to configure provisioning settings. +设置企业名称后，可以继续配置预配设置。 -To configure provisioning, the setup user with the **@SHORT-CODE_admin** username will need to provide a {% data variables.product.pat_v1 %} with the **admin:enterprise** scope. For more information on creating a new token, see "[Creating a {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)." +若要配置预配，具有 @SHORT-CODE_admin 用户名的安装用户将需要提供作用域为 admin:enterprise 的 {% data variables.product.pat_v1 %}。 有关创建新令牌的详细信息，请参阅“[创建 {% data variables.product.pat_generic %}](/github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/configuring-scim-provisioning-for-enterprise-managed-users#creating-a-personal-access-token)”。 -1. Navigate to your {% data variables.product.prodname_emu_idp_application %} application on Okta. -1. Click the **Provisioning** tab. -1. In the settings menu, click **Integration**. -1. To make changes, click **Edit**. -1. Select **Enable API integration**. -1. In the "API Token" field, enter the {% data variables.product.pat_v1 %} with the **admin:enterprise** scope belonging to the setup user. - -1. Click **Test API Credentials**. If the test is successful, a verification message will appear at the top of the screen. -1. To save the token, click **Save**. -1. In the settings menu, click **To App**. - -1. To the right of "Provisioning to App", to allow changes to be made, click **Edit**. -1. Select **Enable** for **Create Users**, **Update User Attributes**, and **Deactivate Users**. - -1. To finish configuring provisioning, click **Save**. +1. 导航到 Okta 上的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 +1. 单击 **资源调配** 选项卡。 +1. 在“设置”菜单中，单击“集成”。 +1. 若要进行更改，请单击“编辑”。 +1. 选择“启用 API 集成”。 +1. 在“API 令牌”字段中，输入属于安装用户的作用域为 admin:enterprise 的 {% data variables.product.pat_v1 %}。 + +1. 单击“测试 API 凭据”。 如果测试成功，屏幕顶部将显示一条验证消息。 +1. 若要保存令牌，请单击“保存”。 +1. 在“设置”菜单中，单击“转到应用”。 + +1. 在“预配到应用”的右侧，要允许进行更改，请单击“编辑”。 +1. 对于“创建用户”、“更新用户属性”和“停用用户”，选择“启用” 。 + +1. 若要完成配置预配，请单击“保存”。 -## Assigning users and groups +## 分配用户和组 -After you have configured SAML SSO and provisioning, you will be able to provision new users on {% data variables.product.prodname_dotcom_the_website %} by assigning users or groups to the {% data variables.product.prodname_emu_idp_application %} application. +配置 SAML SSO 和预配后，可以通过将用户或组分配到 {% data variables.product.prodname_emu_idp_application %} 应用程序在 {% data variables.product.prodname_dotcom_the_website %} 上预配新用户。 {% data reusables.scim.emu-scim-rate-limit %} -You can also automatically manage organization membership by adding groups to the "Push Groups" tab in Okta. When the group is provisioned successfully, it will be available to connect to teams in the enterprise's organizations. For more information about managing teams, 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)." +还可以通过将组添加到 Okta 中的“推送组”选项卡来自动管理组织成员身份。 成功预配组后，该组将可用于连接到企业组织中的团队。 有关管理团队的详细信息，请参阅“[使用标识提供者组管理团队成员身份](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/managing-team-memberships-with-identity-provider-groups)”。 -When assigning users, you can use the "Roles" attribute in the {% data variables.product.prodname_emu_idp_application %} application to set a user's role in your enterprise on {% data variables.product.product_name %}. For more information on roles, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)." +分配用户时，可以使用 {% data variables.product.prodname_emu_idp_application %} 应用程序中的“角色”属性在 {% data variables.product.product_name %} 上设置用户在企业中的角色。 有关角色的详细信息，请参阅“[企业中的角色](/github/setting-up-and-managing-your-enterprise/managing-users-in-your-enterprise/roles-in-an-enterprise)”。 - + -## Deprovisioning users and groups +## 取消预配用户和组 -To remove a user or group from {% data variables.product.product_name %}, remove the user or group from both the "Assignments" tab and the "Push groups" tab in Okta. For users, make sure the user is removed from all groups in the "Push Groups" tab. +若要从 {% data variables.product.product_name %} 中删除用户或组，请从 Okta 的“分配”选项卡和“推送组”选项卡中删除用户或组。 对于用户，请确保从“推送组”选项卡中的所有组中删除该用户。 diff --git a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md index d1d7db49c3..fc940b0940 100644 --- a/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md +++ b/translations/zh-CN/content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md @@ -1,7 +1,7 @@ --- -title: Managing team memberships with identity provider groups +title: 使用标识提供者组管理团队成员身份 shortTitle: Manage teams with your IdP -intro: 'You can manage team and organization membership on {% data variables.product.product_name %} through your identity provider (IdP) by connecting IdP groups with teams within your {% data variables.enterprise.prodname_emu_enterprise %}.' +intro: '将 IdP 组与 {% data variables.enterprise.prodname_emu_enterprise %} 中的团队连接，可以通过标识提供者 (IdP) 管理 {% data variables.product.product_name %} 上的团队和组织成员身份。' product: '{% data reusables.gated-features.emus %}' redirect_from: - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-users-with-your-identity-provider/managing-team-memberships-with-identity-provider-groups @@ -16,77 +16,74 @@ topics: - Enterprise - SSO - Teams +ms.openlocfilehash: 179835d6642cd5718a565869337b5420b29407a5 +ms.sourcegitcommit: 2e1852bcdd690cb66b9b5d69cb056a2bb2b9a6b4 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160822' --- +## 关于使用 {% data variables.product.prodname_emus %} 的团队管理 -## About team management with {% data variables.product.prodname_emus %} +使用 {% data variables.product.prodname_emus %}，可以通过将 {% data variables.product.prodname_dotcom %} 团队与 IdP 组连接起来，通过 IdP 管理企业内的团队和组织成员身份。 将某个企业组织中的团队连接到 IdP 组时，IdP 组对成员身份的更改会自动反映在企业中，从而减少手动更新和自定义脚本的需要。 -With {% data variables.product.prodname_emus %}, you can manage team and organization membership within your enterprise through your IdP by connecting {% data variables.product.prodname_dotcom %} teams with IdP groups. When you connect a team in one of your enterprise's organizations to an IdP group, changes to membership from the IdP group are reflected in your enterprise automatically, reducing the need for manual updates and custom scripts. - -When a change to an IdP group or a new team connection results in a {% data variables.enterprise.prodname_managed_user %} joining a team in an organization they were not already a member of, the {% data variables.enterprise.prodname_managed_user %} will automatically be added to the organization. When you disconnect a group from a team, users who became members of the organization via team membership are removed from the organization if they are not assigned membership in the organization by any other means. +当 IdP 组的更改或新的团队连接导致 {% data variables.enterprise.prodname_managed_user %} 加入他们尚未加入的组织中的团队时，{% data variables.enterprise.prodname_managed_user %} 将自动添加到组织中。 当你断开组与团队的连接时，如果未通过任何其他方式为其分配组织成员身份，则通过团队成员身份成为组织成员的用户将从组织中删除。 {% note %} -**Note:** Organization owners can also add {% data variables.enterprise.prodname_managed_users %} to organizations manually, as long as the accounts have already been provisioned via SCIM. +注意：组织所有者也可以手动将 {% data variables.enterprise.prodname_managed_users %} 添加到组织，只要帐户已通过 SCIM 进行预配。 {% endnote %} -When group membership changes on your IdP, your IdP sends a SCIM request with the changes to {% data variables.product.prodname_dotcom_the_website %} according to the schedule determined by your IdP, so change may not be immediate. Any requests that change team or organization membership will register in the audit log as changes made by the account used to configure user provisioning. +当 Idp 上的组成员身份发生变化时，你的 IdP 会根据 IdP 确定的时间表发送 SCIM 请求，其中包含对 {% data variables.product.prodname_dotcom_the_website %} 的更改，因此更改可能不会立即发生。 任何更改团队或组织成员身份的请求都将在审核日志中注册为用于配置用户预配的帐户所做的更改。 -Teams connected to IdP groups cannot be parents of other teams nor a child of another team. If the team you want to connect to an IdP group is a parent or child team, we recommend creating a new team or removing the nested relationships that make your team a parent team. +连接到 IdP 组的团队不能是其他团队的父级，也不能是另一个团队的子级。 如果要连接到 IdP 组的团队是父团队或子团队，建议创建一个新团队或删除使你的团队成为父团队的嵌套关系。 -To manage repository access for any team in your enterprise, including teams connected to an IdP group, you must make changes on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)". +若要管理企业中任何团队（包括连接到 IdP 组的团队）的存储库访问权限，必须对 {% data variables.product.prodname_dotcom_the_website %} 进行更改。 有关详细信息，请参阅“[管理团队对组织存储库的访问权限](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)”。 -## Requirements for connecting IdP groups with teams +## 将 IdP 组与团队连接的要求 -Before you can connect an IdP group with a team on {% data variables.product.prodname_dotcom %}, you must assign the group to the {% data variables.product.prodname_emu_idp_application %} application in your IdP. For more information, see "[About SCIM provisioning for {% data variables.product.prodname_emus %}](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)." +在将 IdP 组与 {% data variables.product.prodname_dotcom %} 上的团队连接之前，必须将该组分配给 IdP 中的 {% data variables.product.prodname_emu_idp_application %} 应用程序。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_emus %} 的 SCIM 预配](/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users)”。 -You can connect a team in your enterprise to one IdP group. You can assign the same IdP group to multiple teams in your enterprise. +可以将企业中的团队连接到一个 IdP 组。 可以将同一 IdP 组分配给企业中的多个团队。 -If you are connecting an existing team to an IdP group, you must first remove any members that were added manually. After you connect a team in your enterprise to an IdP group, your IdP administrator must make team membership changes through the identity provider. You cannot manage team membership on {% data variables.product.prodname_dotcom_the_website %}. +如果要将现有团队连接到 IdP 组，必须先删除手动添加的任何成员。 将企业中的团队连接到 IdP 组后，IdP 管理员必须通过标识提供者更改团队成员身份。 无法在 {% data variables.product.prodname_dotcom_the_website %} 上管理团队成员身份。 -## Creating a new team connected to an IdP group +## 创建连接到 IdP 组的新团队 -Any member of an organization can create a new team and connect the team to an IdP group. +组织的任何成员都可以创建新团队并将团队连接到 IdP 组。 -{% data reusables.profile.access_org %} -{% data reusables.user-settings.access_org %} -{% data reusables.organizations.new_team %} -{% data reusables.organizations.team_name %} -{% data reusables.organizations.team_description %} -1. To connect a team, select the "Identity Provider Groups" drop-down menu and click the team you want to connect. -  -{% data reusables.organizations.team_visibility %} -{% data reusables.organizations.create_team %} +{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.new_team %} {% data reusables.organizations.team_name %} {% data reusables.organizations.team_description %} +1. 若要连接团队，请选择“标识提供者组”下拉菜单，然后单击要连接的团队。 +  {% data reusables.organizations.team_visibility %} {% data reusables.organizations.create_team %} -## Managing the connection between an existing team and an IdP group +## 管理现有团队和 IdP 组之间的连接 -Organization owners and team maintainers can manage the existing connection between an IdP group and a team. +组织所有者和团队维护者可以管理 IdP 组和团队之间的现有连接。 {% note %} -**Note**: Before you connect an existing team on {% data variables.product.prodname_dotcom_the_website %} to an IdP group for the first time, all members of the team on {% data variables.product.prodname_dotcom_the_website %} must first be removed. For more information, see "[Removing organization members from a team](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)." +注意：在首次将 {% data variables.product.prodname_dotcom_the_website %} 上的现有团队连接到 IdP 组之前，必须先删除 {% data variables.product.prodname_dotcom_the_website %} 上的所有团队成员。 有关详细信息，请参阅“[从团队中删除组织成员](/github/setting-up-and-managing-organizations-and-teams/removing-organization-members-from-a-team)”。 {% endnote %} {% data reusables.profile.access_profile %} -{% data reusables.profile.access_org %} -{% data reusables.organizations.specific_team %} -{% data reusables.organizations.team_settings %} -1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}. -  -1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list. -  -1. Click **Save changes**. +{% data reusables.profile.access_org %} {% data reusables.organizations.specific_team %} {% data reusables.organizations.team_settings %} +1. （可选）在“标识提供者组”下，单击要断开连接的 IdP 组右侧的 {% octicon "x" aria-label="X symbol" %}。 +  +1. 若要连接 IdP 组，请在“标识提供者组”下选择下拉菜单，然后从列表中单击标识提供者组。 +  +1. 单击“保存更改”。 -## Viewing IdP groups, group membership, and connected teams +## 查看 IdP 组、组成员身份和连接的团队 -You can review a list of IdP groups, see any teams connected to an IdP group, and see the membership of each IdP group on {% data variables.product.product_name %}. You must edit the membership for a group on your IdP. +可以查看 IdP 组列表，查看连接到 IdP 组的任何团队，并在 {% data variables.product.product_name %} 上查看每个 IdP 组的成员身份。 必须在 IdP 上编辑组的成员身份。 {% data reusables.enterprise-accounts.access-enterprise %} -1. To review a list of IdP groups, in the left sidebar, click {% octicon "key" aria-label="The key icon" %} **Identity provider**. -  -2. To see the members and teams connected to an IdP group, click the group's name. -  -4. To view the teams connected to the IdP group, click **Teams**. -  +1. 若要查看 IdP 组列表，请在左侧边栏中单击 {% octicon "key" aria-label="The key icon" %}“标识提供者”。 +  +2. 若要查看连接到 IdP 组的成员和团队，请单击该组的名称。 +  +4. 若要查看连接到 IdP 组的团队，请单击“团队”。 +  diff --git a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md index 2d570ef443..bf86d9d4a8 100644 --- a/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md +++ b/translations/zh-CN/content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md @@ -18,7 +18,7 @@ topics: ## Using the audit log API -You can interact with the audit log using the GraphQL API or the REST API. +You can interact with the audit log using the GraphQL API or the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the APIs.{% endif %} Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](http://en.wikipedia.org/wiki/Unix_time). diff --git a/translations/zh-CN/content/admin/overview/index.md b/translations/zh-CN/content/admin/overview/index.md index 2be6a906ee..e38470daba 100644 --- a/translations/zh-CN/content/admin/overview/index.md +++ b/translations/zh-CN/content/admin/overview/index.md @@ -19,11 +19,11 @@ children: - /best-practices-for-enterprises - /creating-an-enterprise-account - /accessing-compliance-reports-for-your-enterprise -ms.openlocfilehash: d936542993310333e314efcc9d5bb5689be00701 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: f0322eef087f09b029051fc08ac61bc4e529d6dc +ms.sourcegitcommit: 0a6e3eee6eea9b1e445aea1e4461d64cf6b63218 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147389841' +ms.lasthandoff: 11/14/2022 +ms.locfileid: '148163554' --- 如需更多信息或购买 {% data variables.product.prodname_enterprise %}，请参阅 [{% data variables.product.prodname_enterprise %}](https://github.com/enterprise)。 diff --git a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md index 1572cddf4f..66beebcd70 100644 --- a/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md +++ b/translations/zh-CN/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md @@ -1,7 +1,7 @@ --- -title: Configuring the CodeQL workflow for compiled languages +title: 为编译的语言配置 CodeQL 工作流 shortTitle: Configure compiled languages -intro: 'You can configure how {% data variables.product.prodname_dotcom %} uses the {% data variables.code-scanning.codeql_workflow %} to scan code written in compiled languages for vulnerabilities and errors.' +intro: '可以配置 {% data variables.product.prodname_dotcom %} 如何使用 {% data variables.code-scanning.codeql_workflow %} 扫描用编译语言编写的代码以查找漏洞和错误。' product: '{% data reusables.gated-features.code-scanning %}' permissions: 'If you have write permissions to a repository, you can configure {% data variables.product.prodname_code_scanning %} for that repository.' redirect_from: @@ -25,107 +25,106 @@ topics: - C/C++ - C# - Java +ms.openlocfilehash: 91983e79a6381b4a38cbb1de4f6d7f228637b192 +ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/11/2022 +ms.locfileid: '148161197' --- +{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} +## 关于 {% data variables.code-scanning.codeql_workflow %} 和编译语言 -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning-actions %} +通过添加 {% data variables.product.prodname_actions %} 工作流程到仓库，设置 {% data variables.product.prodname_dotcom %} 对仓库运行 {% data variables.product.prodname_code_scanning %}。 对于 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}，可以添加 {% data variables.code-scanning.codeql_workflow %}。 有关详细信息，请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。 -## About the {% data variables.code-scanning.codeql_workflow %} and compiled languages +{% data reusables.code-scanning.edit-workflow %} 有关配置 {% data variables.product.prodname_code_scanning %} 和编辑工作流文件的一般信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %} ](/code-security/secure-coding/configuring-code-scanning)”和“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -You set up {% data variables.product.prodname_dotcom %} to run {% data variables.product.prodname_code_scanning %} for your repository by adding a {% data variables.product.prodname_actions %} workflow to the repository. For {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}, you add the {% data variables.code-scanning.codeql_workflow %}. For more information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." +## 关于 {% data variables.product.prodname_codeql %} 的自动构建 -{% data reusables.code-scanning.edit-workflow %} -For general information about configuring {% data variables.product.prodname_code_scanning %} and editing workflow files, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning)" and "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." - -## About autobuild for {% data variables.product.prodname_codeql %} - -{% data variables.product.prodname_code_scanning_capc %} works by running queries against one or more databases. Each database contains a representation of all of the code in a single language in your repository. -For the compiled languages C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java, the process of populating this database involves building the code and extracting data. {% data reusables.code-scanning.analyze-go %} +{% data variables.product.prodname_code_scanning_capc %} 的工作原理是针对一个或多个数据库运行查询。 每个数据库都包含仓库中所有代码的单一语言表示形式。 +对于编译语言 C/C++、C#、{% ifversion codeql-go-autobuild %} Go、{% endif %} 和 Java，填充此数据库的过程涉及构建代码和提取数据。 {% data reusables.code-scanning.analyze-go %} {% data reusables.code-scanning.autobuild-compiled-languages %} -If your workflow uses a `language` matrix, `autobuild` attempts to build each of the compiled languages listed in the matrix. Without a matrix `autobuild` attempts to build the supported compiled language that has the most source files in the repository. With the exception of Go, analysis of other compiled languages in your repository will fail unless you supply explicit build commands. +如果你的工作流使用 `language` 矩阵，`autobuild` 会尝试生成矩阵中列出的每种编译语言。 如果不使用矩阵，则 `autobuild` 会尝试生成在存储库中具有最多源文件的受支持编译语言。 除 Go 以外，除非您提供明确的构建命令，否则您仓库中其他编译语言的分析将失败。 {% note %} -{% ifversion ghae %} -**Note**: {% data reusables.actions.self-hosted-runners-software %} -{% else %} -**Note**: If you use self-hosted runners for {% data variables.product.prodname_actions %}, you may need to install additional software to use the `autobuild` process. Additionally, if your repository requires a specific version of a build tool, you may need to install it manually. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +{% ifversion ghae %} **注意**：{% data reusables.actions.self-hosted-runners-software %} {% else %} **注意**：如果使用 {% data variables.product.prodname_actions %} 的自承载运行器，则可能需要安装其他软件才能使用 `autobuild` 进程。 此外，如果您的仓库需要特定版本的构建工具，您可能需要手动安装它。 有关详细信息，请参阅“[{% data variables.product.prodname_dotcom %} 托管的运行器的规范](/actions/reference/specifications-for-github-hosted-runners/#supported-software)”。 {% endif %} {% endnote %} ### C/C++ -| Supported system type | System name | +| 支持的系统类型 | 系统名称 | |----|----| -| Operating system | Windows, macOS, and Linux | -| Build system | Windows: MSbuild and build scripts
Linux and macOS: Autoconf, Make, CMake, qmake, Meson, Waf, SCons, Linux Kbuild, and build scripts | +| 操作系统 | Windows、macOS 和 Linux | +| 构建系统 | Windows：MSbuild 和生成脚本
Linux 和 macOS：Autoconf、Make、CMake、qmake、Meson、Waf、SCons、Linux Kbuild 和生成脚本 | -The behavior of the `autobuild` step varies according to the operating system that the extraction runs on. On Windows, the `autobuild` step attempts to autodetect a suitable build method for C/C++ using the following approach: +`autobuild` 步骤的行为因运行提取的操作系统而异。 在 Windows 上，`autobuild` 步骤尝试使用以下方法自动检测适合 C/C++ 的生成方法： -1. Invoke `MSBuild.exe` on the solution (`.sln`) or project (`.vcxproj`) file closest to the root. -If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them. -2. Invoke a script that looks like a build script—_build.bat_, _build.cmd_, _and build.exe_ (in that order). +1. 对离根最近的解决方案 (`.sln`) 或项目 (`.vcxproj`) 文件调用 `MSBuild.exe`。 +如果 `autobuild` 在顶层目录下的相同（最短）深度检测到多个解决方案或项目文件，它将尝试生成所有这些文件。 +2. 调用看起来像生成脚本的脚本：build.bat、build.cmd 和 build.exe（按此顺序） 。 -On Linux and macOS, the `autobuild` step reviews the files present in the repository to determine the build system used: +在 Linux 和 macOS 上，`autobuild` 步骤检查存储库中存在的文件，以确定使用的生成系统： -1. Look for a build system in the root directory. -2. If none are found, search subdirectories for a unique directory with a build system for C/C++. -3. Run an appropriate command to configure the system. +1. 在根目录中查找构建系统。 +2. 如果未找到，则搜索子目录以查找含有 C/C++ 构建系统的唯一目录。 +3. 运行适当的命令来配置系统。 ### C# -| Supported system type | System name | +| 支持的系统类型 | 系统名称 | |----|----| -| Operating system | Windows and Linux | -| Build system | .NET and MSbuild, as well as build scripts | +| 操作系统 | Windows 和 Linux | +| 构建系统 | .NET 和 MSbuild，以及构建脚本 | -The `autobuild` process attempts to autodetect a suitable build method for C# using the following approach: +`autobuild` 进程尝试使用以下方法自动检测适合 C# 的构建方法： -1. Invoke `dotnet build` on the solution (`.sln`) or project (`.csproj`) file closest to the root. -2. Invoke `MSbuild` (Linux) or `MSBuild.exe` (Windows) on the solution or project file closest to the root. -If `autobuild` detects multiple solution or project files at the same (shortest) depth from the top level directory, it will attempt to build all of them. -3. Invoke a script that looks like a build script—_build_ and _build.sh_ (in that order, for Linux) or _build.bat_, _build.cmd_, _and build.exe_ (in that order, for Windows). +1. 对离根最近的解决方案 (`.sln`) 或项目 (`.csproj`) 文件调用 `dotnet build`。 +2. 对离根最近的解决方案或项目文件调用 `MSbuild` (Linux) 或 `MSBuild.exe` (Windows)。 +如果 `autobuild` 在顶层目录下的相同（最短）深度检测到多个解决方案或项目文件，它将尝试生成所有这些文件。 +3. 调用看起来像生成脚本的脚本：build 和 build.sh（对于 Linux，按此顺序）或 build.bat、build.cmd 和 build.exe（对于 Windows，按此顺序） 。 {% ifversion codeql-go-autobuild %} ### Go -| Supported system type | System name | +| 支持的系统类型 | 系统名称 | |----|----| -| Operating system | Windows, macOS, and Linux | -| Build system | Go modules, `dep` and Glide, as well as build scripts including Makefiles and Ninja scripts | +| 操作系统 | Windows、macOS 和 Linux | +| 构建系统 | Go 模块、`dep` 和 Glide，以及生成脚本，包括 Makefiles 和 Ninja 脚本 | -The `autobuild` process attempts to autodetect a suitable way to install the dependencies needed by a Go repository before extracting all `.go` files: +`autobuild` 过程尝试在提取所有 `.go` 文件之前自动检测安装 Go 存储库所需的依赖项的合适方法： -1. Invoke `make`, `ninja`, `./build` or `./build.sh` (in that order) until one of these commands succeeds and a subsequent `go list ./...` also succeeds, indicating that the needed dependencies have been installed. -2. If none of those commands succeeded, look for `go.mod`, `Gopkg.toml` or `glide.yaml`, and run `go get` (unless vendoring is in use), `dep ensure -v` or `glide install` respectively to try to install dependencies. -3. Finally, if configurations files for these dependency managers are not found, rearrange the repository directory structure suitable for addition to `GOPATH`, and use `go get` to install dependencies. The directory structure reverts to normal after extraction completes. -4. Extract all Go code in the repository, similar to running `go build ./...`. +1. 调用 `make`、`ninja`、`./build` 或 `./build.sh`（按该顺序），直到其中一个命令成功，后续 `go list ./...` 也成功，这表示已安装所需的依赖项。 +2. 如果这些命令都没有成功，请查找 `go.mod`、`Gopkg.toml` 或 `glide.yaml`，并分别运行 `go get`（除非正在使用供应商）、`dep ensure -v` 或 `glide install` 以尝试安装依赖项。 +3. 最后，如果未找到这些依赖项管理器的配置文件，请重新排列适合添加到 `GOPATH` 的存储库目录结构，并使用 `go get` 安装依赖项。 提取完成后，目录结构恢复为正常。 +4. 提取存储库中的所有 Go 代码，类似于运行 `go build ./...`。 {% endif %} ### Java -| Supported system type | System name | +| 支持的系统类型 | 系统名称 | |----|----| -| Operating system | Windows, macOS, and Linux (no restriction) | -| Build system | Gradle, Maven and Ant | +| 操作系统 | Windows、macOS 和 Linux（无限制） | +| 构建系统 | Gradle、Maven 和 Ant | -The `autobuild` process tries to determine the build system for Java codebases by applying this strategy: +`autobuild` 进程尝试通过应用此策略来确定 Java 代码库的生成系统： -1. Search for a build file in the root directory. Check for Gradle then Maven then Ant build files. -2. Run the first build file found. If both Gradle and Maven files are present, the Gradle file is used. -3. Otherwise, search for build files in direct subdirectories of the root directory. If only one subdirectory contains build files, run the first file identified in that subdirectory (using the same preference as for 1). If more than one subdirectory contains build files, report an error. +1. 在根目录中搜索构建文件。 先后检查 Gradle、Maven 和 Ant 构建文件。 +2. 运行找到的第一个构建文件。 如果 Gradle 和 Maven 文件都存在，则使用 Gradle 文件。 +3. 否则，在根目录的直接子目录中搜索构建文件。 如果只有一个子目录包含构建文件，则运行该子目录中标识的第一个文件（使用与 1 相同的首选项）。 如果多个子目录包含构建文件，则报告错误。 -## Adding build steps for a compiled language +## 添加编译语言的构建步骤 -{% data reusables.code-scanning.autobuild-add-build-steps %} For information on how to edit the workflow file, see "[Configuring {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)." +{% data reusables.code-scanning.autobuild-add-build-steps %} 有关如何编辑工作流文件的信息，请参阅“[配置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/configuring-code-scanning#editing-a-code-scanning-workflow)”。 -After removing the `autobuild` step, uncomment the `run` step and add build commands that are suitable for your repository. The workflow `run` step runs command-line programs using the operating system's shell. You can modify these commands and add more commands to customize the build process. +删除 `autobuild` 步骤后，取消注释 `run` 步骤并添加适合存储库的生成命令。 工作流 `run` 步骤会使用操作系统的 shell 来运行命令行程序。 可以修改这些命令并添加更多命令以自定义生成过程。 ``` yaml - run: | @@ -133,9 +132,9 @@ After removing the `autobuild` step, uncomment the `run` step and add build comm make release ``` -For more information about the `run` keyword, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)." +有关 `run` 关键字的详细信息，请参阅“[{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun)”。 -If your repository contains multiple compiled languages, you can specify language-specific build commands. For example, if your repository contains C/C++, C# and Java, and `autobuild` correctly builds C/C++ and C# but fails to build Java, you could use the following configuration in your workflow, after the `init` step. This specifies build steps for Java while still using `autobuild` for C/C++ and C#: +如果存储库包含多个编译语言，可以指定特定于语言的生成命令。 例如，如果存储库包含 C/C++、C# 和 Java，而 `autobuild` 正确生成了 C/C++ 和 C#，但未能生成 Java，那么在 `init` 步骤之后，可以在工作流中使用以下配置。 这指定了 Java 的生成步骤，同时仍然为 C/C++ 和 C# 使用 `autobuild`： ```yaml - if: matrix.language == 'cpp' || matrix.language == 'csharp' @@ -149,8 +148,8 @@ If your repository contains multiple compiled languages, you can specify languag make release ``` -For more information about the `if` conditional, see "[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)." +有关 `if` 条件的详细信息，请参阅“[GitHub Actions 的工作流语法](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsif)”。 -For more tips and tricks about why `autobuild` won't build your code, see "[Troubleshooting the {% data variables.product.prodname_codeql %} workflow](/code-security/secure-coding/troubleshooting-the-codeql-workflow)." +有关为什么 `autobuild` 无法生成代码的更多提示和技巧，请参阅“[{% data variables.product.prodname_codeql %} 工作流故障排除](/code-security/secure-coding/troubleshooting-the-codeql-workflow)”。 -If you added manual build steps for compiled languages and {% data variables.product.prodname_code_scanning %} is still not working on your repository, contact {% data variables.contact.contact_support %}. +如果您为编译语言添加了手动构建步骤，但 {% data variables.product.prodname_code_scanning %} 仍然无法处理您的仓库，请联系 {% data variables.contact.contact_support %}。 diff --git a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md index bbd4e2ad7e..a6b11b3974 100644 --- a/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md +++ b/translations/zh-CN/content/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github.md @@ -1,5 +1,5 @@ --- -title: Uploading a SARIF file to GitHub +title: 将 SARIF 文件上传到 GitHub shortTitle: Upload a SARIF file intro: '{% data reusables.code-scanning.you-can-upload-third-party-analysis %}' permissions: 'People with write permissions to a repository can upload {% data variables.product.prodname_code_scanning %} data generated outside {% data variables.product.prodname_dotcom %}.' @@ -23,54 +23,57 @@ topics: - Repositories - CI - SARIF +ms.openlocfilehash: 3def104e487f54e2c48d462d1dcfe8bab63c6fa3 +ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/11/2022 +ms.locfileid: '148161157' --- +{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} +## 关于 {% data variables.product.prodname_code_scanning %} 的 SARIF 文件上传 -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} +{% data variables.product.prodname_dotcom %} 使用静态分析结果交换格式 (SARIF) 文件中的信息创建 {% data variables.product.prodname_code_scanning %} 警报。 SARIF 文件可通过在用于上传文件的 {% data variables.product.prodname_actions %} 工作流程中运行的 SARIF 兼容分析工具生成。 或者，当文件生成为仓库外部的构件时， 您可以直接将 SARIF 文件推送到仓库，并使用工作流程上传 SARIF 文件。 有关详细信息，请参阅“[管理存储库的 {% data variables.product.prodname_code_scanning %} 警报](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)”。 -## About SARIF file uploads for {% data variables.product.prodname_code_scanning %} +您可以使用许多静态分析安全测试工具来生成 SARIF 文件，包括 {% data variables.product.prodname_codeql %}。 结果必须使用 SARIF 版本 2.1.0。 有关详细信息，请参阅“[{% data variables.product.prodname_code_scanning %} 的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning)”。 -{% data variables.product.prodname_dotcom %} creates {% data variables.product.prodname_code_scanning %} alerts in a repository using information from Static Analysis Results Interchange Format (SARIF) files. SARIF files can be uploaded to a repository using the API or {% data variables.product.prodname_actions %}. For more information, see "[Managing {% data variables.product.prodname_code_scanning %} alerts for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)." +可以使用 {% data variables.product.prodname_actions %}、{% data variables.product.prodname_code_scanning %} API{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} 或 {% data variables.product.prodname_codeql_cli %} 上传结果。 最佳上传方法将取决于您如何生成 SARIF 文件，例如，如果您使用： -You can generate SARIF files using many static analysis security testing tools, including {% data variables.product.prodname_codeql %}. The results must use SARIF version 2.1.0. For more information, see "[SARIF support for {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/sarif-support-for-code-scanning)." - -You can upload the results using {% data variables.product.prodname_actions %}, the {% data variables.product.prodname_code_scanning %} API,{% ifversion codeql-runner-supported %} the {% data variables.code-scanning.codeql_runner %},{% endif %} or the {% data variables.product.prodname_codeql_cli %}. The best upload method will depend on how you generate the SARIF file, for example, if you use: - -- {% data variables.product.prodname_actions %} to run the {% data variables.product.prodname_codeql %} action, there is no further action required. The {% data variables.product.prodname_codeql %} action uploads the SARIF file automatically when it completes analysis. -- {% data variables.product.prodname_actions %} to run a SARIF-compatible analysis tool, you could update the workflow to include a final step that uploads the results (see below). - - The {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} in your CI system, you can use the CLI to upload results to {% data variables.product.prodname_dotcom %} (for more information, see "[Installing {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)").{% ifversion codeql-runner-supported %} -- The {% data variables.code-scanning.codeql_runner %}, to run {% data variables.product.prodname_code_scanning %} in your CI system, by default the runner automatically uploads results to {% data variables.product.prodname_dotcom %} on completion. If you block the automatic upload, when you are ready to upload results you can use the `upload` command (for more information, see "[Running {% data variables.code-scanning.codeql_runner %} in your CI system](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)").{% endif %} -- A tool that generates results as an artifact outside of your repository, you can use the {% data variables.product.prodname_code_scanning %} API to upload the file (for more information, see "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)"). +- {% data variables.product.prodname_actions %} 来运行 {% data variables.product.prodname_codeql %} 操作，则无需进一步操作。 {% data variables.product.prodname_codeql %} 操作在完成分析后自动上传 SARIF 文件。 +- {% data variables.product.prodname_actions %} 运行与 SARIF 兼容的分析工具，您可以更新工作流程以包括上传结果的最后一步（见下文）。 + - {% data variables.product.prodname_codeql_cli %} 在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}，你可以使用 CLI 将结果上传到 {% data variables.product.prodname_dotcom %}（有关详细信息，请参阅“[在 CI 系统中安装 {% data variables.product.prodname_codeql_cli %}](/code-security/secure-coding/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system)”）。{% ifversion codeql-runner-supported %} +- {% data variables.code-scanning.codeql_runner %}，要在 CI 系统中运行 {% data variables.product.prodname_code_scanning %}，默认情况下运行器会在完成后自动将结果上传到 {% data variables.product.prodname_dotcom %}。 如果阻止自动上传，当准备好上传结果时，可以使用 `upload` 命令（有关详细信息，请参阅“[在 CI 系统中运行 {% data variables.code-scanning.codeql_runner %}](/code-security/secure-coding/running-codeql-runner-in-your-ci-system)”）。{% endif %} +- 作为存储库外部工件生成结果的工具，你可以使用 {% data variables.product.prodname_code_scanning %} API 上传文件（有关详细信息，请参阅“[将分析作为 SARIF 数据上传](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)”）。 {% data reusables.code-scanning.not-available %} -## Uploading a {% data variables.product.prodname_code_scanning %} analysis with {% data variables.product.prodname_actions %} +## 通过 {% data variables.product.prodname_actions %} 上传 {% data variables.product.prodname_code_scanning %} 分析 -To use {% data variables.product.prodname_actions %} to upload a third-party SARIF file to a repository, you'll need a workflow. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +要使用 {% data variables.product.prodname_actions %} 将第三方 SARIF 文件上传到存储库，需要工作流程。 有关详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -Your workflow will need to use the `upload-sarif` action, which is part of the `github/codeql-action` repository. It has input parameters that you can use to configure the upload. The main input parameters you'll use are: +工作流将需要使用 `upload-sarif` 操作，该操作是 `github/codeql-action` 存储库的一部分。 它包含可用于配置上传的输入参数。 您将使用的主要输入参数是： -- `sarif-file`, which configures the file or directory of SARIF files to be uploaded. The directory or file path is relative to the root of the repository. -- `category` (optional), which assigns a category for results in the SARIF file. This enables you to analyze the same commit in multiple ways and review the results using the {% data variables.product.prodname_code_scanning %} views in {% data variables.product.prodname_dotcom %}. For example, you can analyze using multiple tools, and in mono-repos, you can analyze different slices of the repository based on the subset of changed files. +- `sarif-file`，用于配置要上传的 SARIF 文件的文件或目录。 目录或文件路径相对于存储库的根目录。 +- `category`（可选），用于为 SARIF 文件中的结果分配类别。 这使您能够以多种方式分析同一提交，并使用 {% data variables.product.prodname_dotcom %} 中的 {% data variables.product.prodname_code_scanning %} 视图查看结果。 例如，您可以使用多个工具进行分析，在单存储库中，您可以根据已更改文件的子集分析存储库的不同片段。 -For more information see the [`upload-sarif` action](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif). +有关详细信息，请参阅 [`upload-sarif` 操作](https://github.com/github/codeql-action/tree/{% ifversion actions-node16-action %}v2{% else %}v1{% endif %}/upload-sarif)。 -The `upload-sarif` action can be configured to run when the `push` and `scheduled` event occur. For more information about {% data variables.product.prodname_actions %} events, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." +`upload-sarif` 操作可以配置为在 `push` 和 `scheduled` 事件发生时运行。 有关 {% data variables.product.prodname_actions %} 事件的详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。 -If your SARIF file doesn't include `partialFingerprints`, the `upload-sarif` action will calculate the `partialFingerprints` field for you and attempt to prevent duplicate alerts. {% data variables.product.prodname_dotcom %} can only create `partialFingerprints` when the repository contains both the SARIF file and the source code used in the static analysis. For more information about preventing duplicate alerts, see "[About SARIF support for code scanning](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)." +如果你的 SARIF 文件不包含 `partialFingerprints`，则 `upload-sarif` 操作将为你计算 `partialFingerprints` 字段并尝试防止重复警报。 仅当存储库同时包含 SARIF 文件和静态分析中使用的源代码时，{% data variables.product.prodname_dotcom %} 才能创建 `partialFingerprints`。 有关防止重复警报的详细信息，请参阅“[关于代码扫描的 SARIF 支持](/code-security/secure-coding/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs)”。 {% data reusables.code-scanning.upload-sarif-alert-limit %} -### Example workflow for SARIF files generated outside of a repository +### 在存储库外部生成的 SARIF 文件的工作流程示例 -You can create a new workflow that uploads SARIF files after you commit them to your repository. This is useful when the SARIF file is generated as an artifact outside of your repository. +您可以创建一个新的工作流程，以在将 SARIF 文件提交到仓库后上传它们。 当 SARIF 文件作为存储库外部的工件生成时，这很有用。 -This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." +只要提交被推送到仓库，此示例工作流程就会运行。 操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了在推送提交时运行，工作流计划为每周运行一次。 有关详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。 -This workflow uploads the `results.sarif` file located in the root of the repository. For more information about creating a workflow file, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)." +此工作流上传位于存储库根目录中的 `results.sarif` 文件。 有关创建工作流文件的详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)”。 -Alternatively, you could modify this workflow to upload a directory of SARIF files. For example, you could place all SARIF files in a directory in the root of your repository called `sarif-output` and set the action's input parameter `sarif_file` to `sarif-output`. Note that if you upload a directory, each SARIF file must include a unique `runAutomationDetails.id` to define the category for the results. For more information, see "[`runAutomationDetails` object](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)." +或者，您也可以修改此工作流程以上传 SARIF 文件的目录。 例如，您可以将所有 SARIF 文件放在存储库根目录中名为 `sarif-output` 的目录中，并将操作的输入参数 `sarif_file` 设置为 `sarif-output`。 请注意，如果上传目录，则每个 SARIF 文件都必须包含唯一的 `runAutomationDetails.id` 才能定义结果的类别。 有关详细信息，请参阅“[`runAutomationDetails` 对象](/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#runautomationdetails-object)”。 ```yaml name: "Upload SARIF" @@ -105,13 +108,13 @@ jobs: category: my-analysis-tool ``` -### Example workflow that runs the ESLint analysis tool +### 运行 ESLint 分析工具的示例工作流程 -If you generate your third-party SARIF file as part of a continuous integration (CI) workflow, you can add the `upload-sarif` action as a step after running your CI tests. If you don't already have a CI workflow, you can create one using a {% data variables.product.prodname_actions %} template. For more information, see the "[{% data variables.product.prodname_actions %} quickstart](/actions/quickstart)." +如果在持续集成 (CI) 工作流中生成第三方 SARIF 文件，则可以在运行 CI 测试后将 `upload-sarif` 操作添加为一个步骤。 如果您还没有 CI 工作流程，可以使用 {% data variables.product.prodname_actions %} 模板创建一个。 有关详细信息，请参阅“[{% data variables.product.prodname_actions %} 快速入门](/actions/quickstart)”。 -This example workflow runs anytime commits are pushed to the repository. The action uses the `partialFingerprints` property to determine if changes have occurred. In addition to running when commits are pushed, the workflow is scheduled to run once per week. For more information, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows)." +只要提交被推送到仓库，此示例工作流程就会运行。 操作使用 `partialFingerprints` 属性来确定是否发生了更改。 除了在推送提交时运行，工作流计划为每周运行一次。 有关详细信息，请参阅“[触发工作流的事件](/actions/reference/events-that-trigger-workflows)”。 -The workflow shows an example of running the ESLint static analysis tool as a step in a workflow. The `Run ESLint` step runs the ESLint tool and outputs the `results.sarif` file. The workflow then uploads the `results.sarif` file to {% data variables.product.prodname_dotcom %} using the `upload-sarif` action. For more information about creating a workflow file, see "[Introduction to GitHub Actions](/actions/learn-github-actions/introduction-to-github-actions)." +工作流程显示了将 ESLint 静态分析工具作为工作流程中一个步骤运行的示例。 `Run ESLint` 步骤运行 ESLint 工具并输出 `results.sarif` 文件。 然后，工作流使用 `upload-sarif` 操作将 `results.sarif` 文件上传到 {% data variables.product.prodname_dotcom %}。 有关创建工作流文件的详细信息，请参阅“[GitHub Actions 简介](/actions/learn-github-actions/introduction-to-github-actions)”。 ```yaml name: "ESLint analysis" @@ -147,9 +150,9 @@ jobs: sarif_file: results.sarif ``` -## Further reading +## 延伸阅读 -- "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions)" -- "[Viewing your workflow history](/actions/managing-workflow-runs/viewing-workflow-run-history)" -- "[About {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in your CI system](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)" -- "[Upload an analysis as SARIF data](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data)" +- [{% data variables.product.prodname_actions %} 的工作流语法](/actions/reference/workflow-syntax-for-github-actions) +- [查看工作流历史记录](/actions/managing-workflow-runs/viewing-workflow-run-history) +- [关于 CI 系统中的 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system) +- [上传分析作为 SARIF 数据](/rest/reference/code-scanning#upload-an-analysis-as-sarif-data) diff --git a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md index 24b916c11a..12e9ce948b 100644 --- a/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md +++ b/translations/zh-CN/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/running-codeql-runner-in-your-ci-system.md @@ -1,7 +1,7 @@ --- -title: Running CodeQL runner in your CI system +title: 在 CI 系统中运行 CodeQL 运行器 shortTitle: Run CodeQL runner -intro: 'You can use the {% data variables.code-scanning.codeql_runner %} to perform {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} in a third-party continuous integration system.' +intro: '可以使用 {% data variables.code-scanning.codeql_runner %} 在第三方持续集成系统中执行 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %}。' product: '{% data reusables.gated-features.code-scanning %}' redirect_from: - /github/finding-security-vulnerabilities-and-errors-in-your-code/running-code-scanning-in-your-ci-system @@ -24,102 +24,102 @@ topics: - Integration - CI - SARIF +ms.openlocfilehash: 7e60376ed165a3af2da7f000c37d326cb33ade99 +ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/11/2022 +ms.locfileid: '148161092' --- - {% ifversion codeql-runner-supported %} -{% data reusables.code-scanning.deprecation-codeql-runner %} -{% data reusables.code-scanning.beta %} -{% data reusables.code-scanning.enterprise-enable-code-scanning %} +{% data reusables.code-scanning.deprecation-codeql-runner %} {% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning %} -## About the {% data variables.code-scanning.codeql_runner %} +## 关于 {% data variables.code-scanning.codeql_runner %} -The {% data variables.code-scanning.codeql_runner %} is a tool you can use to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." +{% data variables.code-scanning.codeql_runner %} 是可以用来在第三方持续集成 (CI) 系统中处理的代码上运行 {% data variables.product.prodname_code_scanning %} 的工具。 {% data reusables.code-scanning.about-code-scanning %} 有关信息，请参阅“[关于使用 {% data variables.product.prodname_codeql %} 进行 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)”。 -In many cases it is easier to set up {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} using the {% data variables.product.prodname_codeql_cli %} directly in your CI system. +在许多情况下，在 CI 系统中直接使用 {% data variables.product.prodname_codeql_cli %} 设置 {% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} 更简单。 -Alternatively, you can use {% data variables.product.prodname_actions %} to run {% data variables.product.prodname_code_scanning %} within {% data variables.product.product_name %}. For information, see "[Setting up {% data variables.product.prodname_code_scanning %} for a repository](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)." +您也可以使用 {% data variables.product.prodname_actions %} 在 {% data variables.product.product_name %} 中运行 {% data variables.product.prodname_code_scanning %}。 有关信息，请参阅“[为存储库设置 {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/setting-up-code-scanning-for-a-repository)”。 -The {% data variables.code-scanning.codeql_runner %} is a command-line tool that runs {% data variables.product.prodname_codeql %} analysis on a checkout of a {% data variables.product.prodname_dotcom %} repository. You add the runner to your third-party system, then call the runner to analyze code and upload the results to {% data variables.product.product_name %}. These results are displayed as {% data variables.product.prodname_code_scanning %} alerts in the repository. +{% data variables.code-scanning.codeql_runner %} 是在 {% data variables.product.prodname_dotcom %} 存储库的签出上运行 {% data variables.product.prodname_codeql %} 分析的命令行工具。 你可以将运行器添加到第三方系统，然后调用运行器以分析代码并将结果上传到 {% data variables.product.product_name %}。 这些结果在仓库中显示为 {% data variables.product.prodname_code_scanning %} 警报。 {% note %} -**Note:** -{% ifversion fpt or ghec %} -* The {% data variables.code-scanning.codeql_runner %} uses the {% data variables.product.prodname_codeql %} CLI to analyze code and therefore has the same license conditions. It's free to use on public repositories that are maintained on {% data variables.product.prodname_dotcom_the_website %}, and available to use on private repositories that are owned by customers with an {% data variables.product.prodname_advanced_security %} license. For information, see "[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} Terms and Conditions](https://securitylab.github.com/tools/codeql/license)" and "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +注意：{% ifversion fpt or ghec %} +* {% data variables.code-scanning.codeql_runner %} 使用 {% data variables.product.prodname_codeql %} CLI 来分析代码，因此具有相同的许可条件。 它可自由用于 {% data variables.product.prodname_dotcom_the_website %} 上维护的公共仓库，并且可用于具有 {% data variables.product.prodname_advanced_security %} 许可证的客户所拥有的私有仓库。 有关信息，请参阅“[{% data variables.product.product_name %} {% data variables.product.prodname_codeql %} 条款和条件](https://securitylab.github.com/tools/codeql/license)”以及“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 {% else %} -* The {% data variables.code-scanning.codeql_runner %} is available to customers with an {% data variables.product.prodname_advanced_security %} license. -{% endif %} -{% ifversion ghae %} -* The {% data variables.code-scanning.codeql_runner %} shouldn't be confused with the {% data variables.product.prodname_codeql %} CLI. The {% data variables.product.prodname_codeql %} CLI is a command-line interface that lets you create {% data variables.product.prodname_codeql %} databases for security research and run {% data variables.product.prodname_codeql %} queries. -For more information, see "[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)." -{% endif %} -{% endnote %} +* {% data variables.code-scanning.codeql_runner %} 可供拥有 {% data variables.product.prodname_advanced_security %} 许可证的客户使用。 +{% endif %} {% ifversion ghae %} +* 请勿将 {% data variables.code-scanning.codeql_runner %} 与 {% data variables.product.prodname_codeql %} CLI 混淆。 {% data variables.product.prodname_codeql %} CLI 是一个命令行接口，允许您创建用于安全研究的 {% data variables.product.prodname_codeql %} 数据库并运行 {% data variables.product.prodname_codeql %} 查询。 +有关详细信息，请参阅“[{% data variables.product.prodname_codeql_cli %}](https://codeql.github.com/docs/codeql-cli/)”。 +{% endif %} {% endnote %} -## Downloading the {% data variables.code-scanning.codeql_runner %} +## 下载 {% data variables.code-scanning.codeql_runner %} -You can download the {% data variables.code-scanning.codeql_runner %} from https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases. On some operating systems, you may need to change permissions for the downloaded file before you can run it. +可以从 https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases 下载 {% data variables.code-scanning.codeql_runner %}。 在某些操作系统上，您可能需要更改下载文件的权限才能运行它。 -On Linux: +在 Linux 上： ```shell chmod +x codeql-runner-linux ``` -On macOS: +在 macOS 上： ```shell chmod +x codeql-runner-macos sudo xattr -d com.apple.quarantine codeql-runner-macos ``` -On Windows, the `codeql-runner-win.exe` file usually requires no change to permissions. +在 Windows 中，`codeql-runner-win.exe` 文件通常无需更改权限。 -## Adding the {% data variables.code-scanning.codeql_runner %} to your CI system +## 将 {% data variables.code-scanning.codeql_runner %} 添加到 CI 系统 -Once you download the {% data variables.code-scanning.codeql_runner %} and verify that it can be executed, you should make the runner available to each CI server that you intend to use for {% data variables.product.prodname_code_scanning %}. For example, you might configure each server to copy the runner from a central, internal location. Alternatively, you could use the REST API to get the runner directly from {% data variables.product.prodname_dotcom %}, for example: +下载 {% data variables.code-scanning.codeql_runner %} 并确认它可执行后，应将该运行器提供给打算用于 {% data variables.product.prodname_code_scanning %} 的每个 CI 服务器。 例如，您可以配置每台服务器从中央内部位置复制运行器。 或者，您也可以使用 REST API 直接从 {% data variables.product.prodname_dotcom %} 获取运行器，例如： ```shell wget https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action/releases/latest/download/codeql-runner-linux chmod +x codeql-runner-linux ``` -In addition to this, each CI server also needs: +除此之外，每个 CI 服务器还需要： -- A {% data variables.product.prodname_github_app %} or {% data variables.product.pat_generic %} for the {% data variables.code-scanning.codeql_runner %} to use. You must use an access token with the `repo` scope, or a {% data variables.product.prodname_github_app %} with the `security_events` write permission, and `metadata` and `contents` read permissions. For information, see "[Building {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)" and "[Creating a {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)." -- Access to the {% data variables.product.prodname_codeql %} bundle associated with this release of the {% data variables.code-scanning.codeql_runner %}. This package contains queries and libraries needed for {% data variables.product.prodname_codeql %} analysis, plus the {% data variables.product.prodname_codeql %} CLI, which is used internally by the runner. For information, see "[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)." +- 供 {% data variables.code-scanning.codeql_runner %} 使用的 {% data variables.product.prodname_github_app %} 或 {% data variables.product.pat_generic %}。 必须使用具有 `repo` 范围的访问令牌，或具有 `security_events` 写入权限和 `metadata` 与 `contents` 读取权限的 {% data variables.product.prodname_github_app %}。 有关信息，请参阅“[生成 {% data variables.product.prodname_github_apps %}](/developers/apps/building-github-apps)”和“[创建 {% data variables.product.pat_generic %}](/github/authenticating-to-github/creating-a-personal-access-token)”。 +- 访问与此版本的 {% data variables.code-scanning.codeql_runner %} 关联的 {% data variables.product.prodname_codeql %} 捆绑包。 此包包含 {% data variables.product.prodname_codeql %} 分析所需的查询和库，以及供运行器内部使用的 {% data variables.product.prodname_codeql %} CLI。 有关信息，请参阅“[{% data variables.product.prodname_codeql %} CLI](https://codeql.github.com/docs/codeql-cli/)”。 -The options for providing access to the {% data variables.product.prodname_codeql %} bundle are: +提供 {% data variables.product.prodname_codeql %} 包访问权限的选项： -1. Allow the CI servers access to https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/github/codeql-action so that the {% data variables.code-scanning.codeql_runner %} can download the bundle automatically. -1. Manually download/extract the bundle, store it with other central resources, and use the
Includes `manage_runners:enterprise`{% ifversion ghec or ghes > 3.3 %}, `manage_billing:enterprise`,{% endif %} and `read:enterprise`. `manage_runners:enterprise` | Gives full control over self-hosted runners within the enterprise. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)." {% ifversion ghec or ghes > 3.3 %} `manage_billing:enterprise` | Read and write enterprise billing data. For more information, see "[Billing](/rest/billing)" in the REST API documentation. {% endif %} - `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %} + `read:enterprise` | Read all data on an enterprise profile. Does not include profile data of enterprise members or organizations.{% endif %}{% ifversion read-audit-scope %} +**`read:audit_log`** | Read audit log data.{% endif %} {% note %} **Note:** Your OAuth App can request the scopes in the initial redirection. You diff --git a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md index 200f7cda3c..957a6931b5 100644 --- a/translations/zh-CN/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md +++ b/translations/zh-CN/content/developers/webhooks-and-events/webhooks/receiving-webhooks-with-the-github-cli.md @@ -6,12 +6,12 @@ versions: topics: - Webhooks shortTitle: Receiving webhooks with the GitHub CLI -ms.openlocfilehash: 2772a9d4208d0afe77871255ad6510b7f39de8d5 -ms.sourcegitcommit: 6b1c6174d0df40c90edfd7526496baabb1dd159d +ms.openlocfilehash: 11bc5b476a191a61594cb73f1e6ce1be5bb6cf9b +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 11/04/2022 -ms.locfileid: '148132961' +ms.lasthandoff: 11/10/2022 +ms.locfileid: '148160662' --- ## 关于使用 {% data variables.product.prodname_cli %} 接收 Webhook diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md index 2c45e9104d..302f14adae 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/managing-discussions.md @@ -20,6 +20,8 @@ As a discussions maintainer, you can create community resources to encourage dis When a discussion yields an idea or bug that is ready to be worked on, you can create a new issue from a discussion. For more information, see "[Creating an issue](/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-discussion)." +You can pin a discussion to the top of the list of discussions for the repository or organization. {% ifversion discussions-category-specific-pins %}You can also pin a discussion to a specific category.{% endif %} For more information, see "[Pinning a discussion](/discussions/managing-discussions-for-your-community/managing-discussions#pinning-a-discussion)." + For more information on facilitating a healthy discussion, see "[Moderating comments and conversations](/communities/moderating-comments-and-conversations)." {% data reusables.discussions.you-can-label-discussions %} @@ -40,23 +42,63 @@ You can also move a discussion to a different category. It's not possible to mov {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} 1. In the right sidebar, to the right of "Category", click {% octicon "gear" aria-label="The gear icon" %}. -  + +  + 1. Click a category. -  + +  ## Pinning a discussion -You can pin up to four important discussions above the list of discussions for the repository or organization. +{% ifversion discussions-category-specific-pins %} +You can pin a discussion above the list of discussions for the repository or organization. You can also pin a discussion to a specific category. The globally pinned discussions will be shown in addition to the discussions pinned to a specific category. + +This is what it looks like when you have a globally pinned discussion and a discussion pinned to the Ideas category. + + + +### Pinning a discussion globally +{% endif %} + +You can pin up to four important discussions above the list of discussions for the repository or organization. + {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion**. -  +{% ifversion discussions-category-specific-pins %} + + {% else %} + + {% endif %} + 1. Optionally, customize the look of the pinned discussion. -  + +  + 1. Click **Pin discussion**. -  + +  + +{% ifversion discussions-category-specific-pins %} +### Pinning a discussion to a category + +You can pin up to four important discussions above the list of discussions in a specific category. + +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Pin discussion to CATEGORY**. + +  + +2. To confirm, click **Pin to CATEGORY**. + +  + +{% endif %} ## Editing a pinned discussion @@ -66,21 +108,60 @@ Editing a pinned discussion will not change the discussion's category. For more {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} 1. In the right sidebar, click {% octicon "pencil" aria-label="The pencil icon" %} **Edit pinned discussion**. -  + {% ifversion discussions-category-specific-pins %} + +  {% else %} + + + {% endif %} + 1. Customize the look of the pinned discussion. -  + +  + 1. Click **Pin discussion**. -  + +  ## Unpinning a discussion +{% ifversion discussions-category-specific-pins %} + +You can unpin a discussion from the list of discussions for the repository or organization, or from the list of discussions in a specific category. + +### Unpinning a globally pinned discussion + +You can unpin a globally pinned discussion. This will not delete the discussion, but the discussion will no longer be displayed above the list of discussions. +{% endif %} + {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} 1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion**. -  + +  + 1. Read the warning, then click **Unpin discussion**. -  + +  + +{% ifversion discussions-category-specific-pins %} +### Unpinning a discussion from a category + +You can unpin a discussion pinned to a specific category. This will not delete the discussion, but the discussion will no longer be displayed at the top of the category. + +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +{% data reusables.discussions.click-discussion-in-list %} +1. In the right sidebar, click {% octicon "pin" aria-label="The pin icon" %} **Unpin discussion from this category**. + +  + +1. Read the warning, then click **Unpin from this category**. + +  + +{% endif %} ## Transferring a discussion @@ -89,12 +170,21 @@ To transfer a discussion, you must have permissions to create discussions in the {% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} -1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} **Transfer discussion**. -  +1. In the right sidebar, click {% octicon "arrow-right" aria-label="The right arrow icon" %} {% ifversion discussions-category-specific-pins %}**Transfer this discussion**{% else %}**Transfer discussion**{% endif %}. +{% ifversion discussions-category-specific-pins %} + +  {% else %} + + + {% endif %} + 1. Select the **Choose a repository** drop-down, and click the repository you want to transfer the discussion to. If you want to transfer a discussion to an organization, choose the source repository for the organization's discussions. -  + +  + 1. Click **Transfer discussion**. -  + +  ## Deleting a discussion @@ -102,9 +192,16 @@ To transfer a discussion, you must have permissions to create discussions in the {% data reusables.discussions.discussions-tab %} {% data reusables.discussions.click-discussion-in-list %} 1. In the right sidebar, click {% octicon "trash" aria-label="The trash arrow icon" %} **Delete discussion**. -  +{% ifversion discussions-category-specific-pins %} + + {% else %} + + + {% endif %} + 1. Read the warning, then click **Delete this discussion**. -  + +  ## Converting issues based on labels diff --git a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md index 6a6cc36656..9f154541c3 100644 --- a/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md +++ b/translations/zh-CN/content/discussions/managing-discussions-for-your-community/moderating-discussions.md @@ -1,41 +1,47 @@ --- -title: 主持讨论 -intro: '可以通过将评论标记为答案、锁定或解锁讨论、将问题转换为讨论，以及编辑或删除不符合{% ifversion fpt or ghec %}社区行为准则{% elsif ghes > 3.5 %}和组织的参与指南{% endif %}的评论、讨论和类别，来促进正常的协作。' +title: Moderating discussions +intro: 'You can promote healthy collaboration by marking comments as answers, locking or unlocking discussions, converting issues to discussions, and editing or deleting comments, discussions, and categories that don''t align with your{% ifversion fpt or ghec %} community''s code of conduct{% elsif ghes > 3.5 %} organization''s contribution guidelines{% endif %}.' permissions: People with triage access to a repository can moderate discussions in the repository. People with triage access to the source repository for organization discussions can moderate discussions in the organization. versions: feature: discussions -ms.openlocfilehash: 7d128c9beadb190f9c22c345cf0c3124b1dfcfcb -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 -ms.translationtype: HT -ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: '147410113' --- -## 关于主持讨论 -{% data reusables.discussions.about-discussions %}如果你对存储库具有会审权限，便可通过将评论标记为答案、锁定不再有用或对社区造成损害的讨论，以及在想法仍处于开发早期阶段时将问题转换为讨论，从而帮助主持存储库的讨论。 同样，对于组织讨论，如果你对源存储库具有会审权限，则可以为该组织主持讨论。 -## 将评论标记为答案 +## About moderating discussions + +{% data reusables.discussions.about-discussions %} If you have triage permissions for a repository, you can help moderate that repository's discussions by marking comments as answers, locking discussions that are no longer useful or are damaging to the community, and converting issues to discussions when an idea is still in the early stages of development. Similarly, if you have triage permission for the source repository for organization discussions, you can moderate discussions for that organization. + +## Marking a comment as an answer {% data reusables.discussions.marking-a-comment-as-an-answer %} -## 锁定讨论 +## Locking discussions -如果整个对话没有建设性或者违反了社区的行为准则或 {% data variables.product.prodname_dotcom %} 的[社区准则](/free-pro-team@latest/github/site-policy/github-community-guidelines)，锁定对话是明智之举。 您还可以锁定对话，以防止对要用作社区公告的讨论发表评论。 锁定对话后，对存储库或组织讨论的源存储库具有写入访问权限的人员仍能够对讨论发表评论。 +It's appropriate to lock a conversation when the entire conversation is not constructive or violates your community's code of conduct or {% data variables.product.prodname_dotcom %}'s [Community Guidelines](/free-pro-team@latest/github/site-policy/github-community-guidelines). You can also lock a conversation to prevent comments on a discussion you want to use as an announcement to the community. When you lock a conversation, people with write access to the repository, or source repository for organization discussions, will still be able to comment on the discussion. -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.discussions.discussions-tab %} -1. 在讨论列表中，单击要锁定的讨论。 -  -1. 单击讨论右侧的“锁定对话”。 -1. 阅读有关锁定对话的信息，然后单击“锁定此讨论的对话”。 -1. 准备好解锁对话时，请单击“解锁对话”，然后单击“解锁此讨论的对话” 。 +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.discussions.discussions-tab %} +1. In the list of discussions, click the discussion you want to lock. +  +1. In the right margin of a discussion, click **Lock conversation**. +1. Read the information about locking conversations and click **Lock conversation on this discussion**. +1. When you're ready to unlock the conversation, click **Unlock conversation**, then click **Unlock conversation on this discussion**. -## 将议题转换为讨论 +## Converting an issue to a discussion -在将议题转换为讨论时，会使用议题中的内容自动创建讨论。 对存储库或组织讨论的源存储库具有写入访问权限的人员可以根据标签批量转换问题。 有关详细信息，请参阅“[管理讨论](/discussions/managing-discussions-for-your-community/managing-discussions)”。 +When you convert an issue to a discussion, the discussion is automatically created using the content from the issue. People with write access to a repository, or source repository for organization discussions, can bulk convert issues based on labels. For more information, see "[Managing discussions](/discussions/managing-discussions-for-your-community/managing-discussions)." -{% data reusables.discussions.navigate-to-repo-or-org %} {% data reusables.repositories.sidebar-issues %} -1. 在议题列表中，单击您想要转换的议题。 -1. 单击问题右侧的“转换为讨论”。 -1. 选择“选择类别”下拉菜单，然后单击某个类别进行讨论。 -1. 单击“我明白，将此问题转化为讨论”。 +{% data reusables.discussions.navigate-to-repo-or-org %} +{% data reusables.repositories.sidebar-issues %} +1. In the list of issues, click the issue you'd like to convert. +1. In the right margin of an issue, click **Convert to discussion**. +1. Select the **Choose a category** drop-down menu, and click a category for your discussion. +1. Click **I understand, convert this issue to a discussion**. + +{% ifversion discussions-hide-comments-on-block %} +## Blocking a user from your organization + +Organization owners and moderators can block a user from the organization if their comments don't align with the community's code of conduct. When you block a user, they will no longer be able to comment on discussions. You can also hide all of the comments a user has made in the organization. For more information, see "[Blocking a user from your organization](/communities/maintaining-your-safety-on-github/blocking-a-user-from-your-organization)." + +{% data reusables.organizations.blocking-a-user %} +{% endif %} diff --git a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md index acf04c777a..d7164d372a 100644 --- a/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md +++ b/translations/zh-CN/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-global-campus-for-students.md @@ -33,15 +33,16 @@ Once you are a verified {% data variables.product.prodname_global_campus %} stud - Stay in the know on what the community is interested in by rewatching recent [Campus TV](https://www.twitch.tv/githubeducation) episodes. Campus TV is created by {% data variables.product.prodname_dotcom %} and student community leaders and can be watched live or on demand. - Discover student-created repositories from GitHub Community Exchange. For more information, see "[About GitHub Community Exchange](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-students/about-github-community-exchange)." -A free subscription for {% data variables.product.prodname_copilot %} is available to verified students with {% data variables.product.prodname_education %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)." - -{% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." +{% data variables.product.prodname_global_campus %} students also receive the following {% data variables.product.prodname_dotcom %} benefits. +- **{% data variables.product.prodname_copilot %}**: Verified students receive a free subscription for {% data variables.product.prodname_copilot %}. You will be automatically notified about the free subscription when you visit the {% data variables.product.prodname_copilot %} subscription page in your account settings. For more information about subscribing to and using {% data variables.product.prodname_copilot %}, see "[Managing your {% data variables.product.prodname_copilot %} subscription](/billing/managing-billing-for-github-copilot/managing-your-github-copilot-subscription#setting-up-a-trial-of-github-copilot)" and "[About {% data variables.product.prodname_copilot %}](/copilot/overview-of-github-copilot/about-github-copilot)." +- **{% data variables.product.prodname_github_codespaces %}**: {% data reusables.education.student-codespaces-benefit %} For more information on getting started with {% data variables.product.prodname_github_codespaces %}, see "[{% data variables.product.prodname_github_codespaces %} overview](/codespaces/overview)." {% note %} **Note:** {% data reusables.education.note-on-student-codespaces-usage %} For more information, see "[Using {% data variables.product.prodname_github_codespaces %} with {% data variables.product.prodname_classroom %}](/education/manage-coursework-with-github-classroom/integrate-github-classroom-with-an-ide/using-github-codespaces-with-github-classroom)." {% endnote %} + ## Further reading - "[About {% data variables.product.prodname_global_campus %} for teachers](/education/explore-the-benefits-of-teaching-and-learning-with-github-education/github-global-campus-for-teachers/about-github-global-campus-for-teachers)" diff --git a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md index b10cb2025a..d543ff4837 100644 --- a/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md +++ b/translations/zh-CN/content/get-started/getting-started-with-git/managing-remote-repositories.md @@ -212,8 +212,8 @@ $ git remote rm destination # Remove remote $ git remote -v # Verify it's gone -> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (fetch) -> origin https://{% data variables.command_line.codeblock %}/ OWNER/REPOSITORY.git (push) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (fetch) +> origin https://{% data variables.command_line.codeblock %}/OWNER/REPOSITORY.git (push) ``` {% warning %} diff --git a/translations/zh-CN/content/get-started/index.md b/translations/zh-CN/content/get-started/index.md index 2e358789f0..2c1d0e7ab7 100644 --- a/translations/zh-CN/content/get-started/index.md +++ b/translations/zh-CN/content/get-started/index.md @@ -23,7 +23,7 @@ versions: ghec: '*' layout: product-landing introLinks: - quickstart: /github/getting-started-with-github/quickstart + quickstart: /get-started/quickstart featuredLinks: guides: - /github/getting-started-with-github/githubs-products 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 4bd5001966..a725011596 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 @@ -29,7 +29,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn {% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %} 3. Select an owner for the forked repository.  -4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further. +4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.  5. Optionally, add a description of your fork.  @@ -184,7 +184,7 @@ For more information about how to push changes in {% data variables.product.prod At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back. -To do so, head on over to the repository on {% data variables.product.product_name %} where your project lives. For this example, it would be at `https://www.github.com/
- Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | +| 安全工程师 | 能够贡献代码并维护安全管道 | **维护** | 删除代码扫描结果 | +| 承办商 | 能够开发 web 挂钩集成 | **写入** | 管理 web 挂钩 | +| 社区经理 | 能够处理所有社区互动，而无需贡献代码 | **读取** | - 将问题标记为重复问题
- 管理 GitHub 页面设置
- 管理 Wiki 设置
- 设置社交预览
- 编辑存储库元数据
- 会审讨论 | -## Additional permissions for custom roles +## 自定义角色的其他权限 -After choosing an inherited role, you can select additional permissions for your custom role. +选择继承角色后，您可以为自定义角色选择其他权限。 -You can only choose an additional permission if it's not already included in the inherited role. For example, if the inherited role offers **Write** access to a repository, then the "Close a pull request" permission will already be included in the inherited role. +仅当继承的角色中尚未包含其他权限时，才能选择该权限。 例如，如果继承的角色提供对存储库的写入访问权限，则“关闭拉取请求”权限将已包含在继承的角色中。 {% ifversion discussions %} -### Discussions +### 讨论 -- Create a discussion category -- Edit a discussion category -- Delete a discussion category -- Mark or unmark discussion answers -- Hide or unhide discussion comments -- Convert issues to discussions +- 创建讨论类别 +- 编辑讨论类别 +- 删除讨论类别 +- 标记或取消标记讨论答案 +- 隐藏或取消隐藏讨论评论 +- 将问题转化为讨论 -For more information, see "[{% data variables.product.prodname_discussions %}](/discussions)." +有关详细信息，请参阅“[{% data variables.product.prodname_discussions %}](/discussions)”。 {% endif %} -### Issue and Pull Requests +### 议题和拉取请求 -- Assign or remove a user -- Add or remove a label +- 分配或删除用户 +- 添加或删除标签 -### Issue +### 问题 -- Close an issue -- Reopen a closed issue -- Delete an issue -- Mark an issue as a duplicate +- 关闭问题 +- 重新打开已关闭的问题 +- 删除问题 +- 将问题标记为重复问题 -### Pull Request +### 拉取请求 -- Close a pull request -- Reopen a closed pull request -- Request a pull request review +- 关闭拉取请求 +- 重新打开已关闭的拉取请求 +- 请求拉取请求审查 -### Repository +### 存储库 -- Set milestones -- Manage wiki settings -- Manage project settings -- Manage pull request merging settings -- Manage {% data variables.product.prodname_pages %} settings (see "[Configuring a publishing source for your {% data variables.product.prodname_pages %} site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)") -- Manage webhooks -- Manage deploy keys -- Edit repository metadata -{%- ifversion ghec %} -- Set interaction limits -{%- endif %} -- Set the social preview -- Push commits to protected branches (branch protection rules will still apply) -- Create protected tags -- Delete protected tags -{%- ifversion bypass-branch-protections %} -- Bypass branch protections -{%- endif %} +- 设置里程碑 +- 管理 Wiki 设置 +- 获取项目设置 +- 管理拉取请求合并设置 +- 管理 {% data variables.product.prodname_pages %} 设置（请参阅“[为 {% data variables.product.prodname_pages %} 站点配置发布源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”） +- 管理 web 挂钩 +- 管理部署密钥 +- 编辑存储库元数据{%- ifversion ghec %} +- 设置交互限制{%- endif %} +- 设置社交预览 +- 将提交推送到受保护分支（分支保护规则仍然适用） +- 创建受保护的标记 +- 删除受保护标记{%- ifversion bypass-branch-protections %} +- 绕过分支保护{%- endif %} -### Security +### 安全性 -- View {% data variables.product.prodname_code_scanning %} results -- Dismiss or reopen {% data variables.product.prodname_code_scanning %} results -- Delete {% data variables.product.prodname_code_scanning %} results -- View {% data variables.product.prodname_dependabot_alerts %} -- Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %} -- View {% data variables.product.prodname_secret_scanning %} results -- Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results +- 查看 {% data variables.product.prodname_code_scanning %} 结果 +- 关闭或重新打开 {% data variables.product.prodname_code_scanning %} 结果 +- 删除 {% data variables.product.prodname_code_scanning %} 结果 +- 查看 {% data variables.product.prodname_dependabot_alerts %} +- 关闭或重新打开 {% data variables.product.prodname_dependabot_alerts %} +- 查看 {% data variables.product.prodname_secret_scanning %} results +- 关闭或重新打开 {% data variables.product.prodname_secret_scanning %} 结果 -## Precedence for different levels of access +## 不同级别访问的优先级 -If a person is given different levels of access through different avenues, such as team membership and the base permissions for an organization, the highest access overrides the others. For example, if an organization owner gives an organization member a custom role that uses the "Read" inherited role, and then an organization owner sets the organization's base permission to "Write", then this custom role will have write access, along with any additional permissions included in the custom role. +如果通过不同的途径（如团队成员身份和组织的基本权限）为某人授予不同级别的访问权限，则最高访问权限将覆盖其他访问权限。 例如，如果组织所有者向组织成员提供使用“读取”继承角色的自定义角色，然后组织所有者将组织的基本权限设置为“写入”，则此自定义角色将具有写入权限以及自定义角色中包含的任何其他权限。 {% data reusables.organizations.mixed-roles-warning %} -To resolve conflicting access, you can adjust your organization's base permissions or the team's access, or edit the custom role. For more information, see: - - "[Setting base permissions for an organization](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization)" - - "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" - - "[Editing a repository role](#editing-a-repository-role)" \ No newline at end of file +要解决冲突的访问权限，您可以调整组织的基本权限或团队的访问权限，或编辑自定义角色。 有关详细信息，请参阅： + - [为组织设置基本权限](/github/setting-up-and-managing-organizations-and-teams/setting-base-permissions-for-an-organization) + - “[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)” + - [编辑存储库角色](#editing-a-repository-role) diff --git a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md index e687fd7b2b..b90b8ff549 100644 --- a/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md +++ b/translations/zh-CN/content/packages/working-with-a-github-packages-registry/working-with-the-npm-registry.md @@ -183,18 +183,18 @@ By default, you can only use npm packages hosted on your enterprise, and you wil {% data reusables.package_registry.authenticate-step %} {% data reusables.package_registry.create-npmrc-owner-step %} {% data reusables.package_registry.add-npmrc-to-repo-step %} -4. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. For example, this following *package.json* uses the `@octo-org/octo-app` package as a dependency. +1. Configure *package.json* in your project to use the package you are installing. To add your package dependencies to the *package.json* file for {% data variables.product.prodname_registry %}, specify the full-scoped package name, such as `@my-org/server`. For packages from *npmjs.com*, specify the full name, such as `@babel/core` or `@lodash`. Replace `
-
-
+
-# 第三方库
+## Octokit 风格多样
+
+使用官方的 Octokit 库，或者使用任何适用的第三方库。
+
+- Python → [octokit.py](https://github.com/khornberg/octokit.py)
+- Ruby → [octokit.rb](https://github.com/octokit/octokit.rb)
+- .NET → [octokit.net](https://github.com/octokit/octokit.net)
+- JavaScript → [octokit/octokit.js](https://github.com/octokit/octokit.js)
+
+## 第三方库
### Clojure
@@ -130,6 +130,7 @@ ms.locfileid: '146769155'
|**octohub**|[turnkeylinux/octohub](https://github.com/turnkeylinux/octohub)|
|**github-flask**|[github-flask（官方网站）](http://github-flask.readthedocs.org)|
|**torngithub**|[jkeylu/torngithub](https://github.com/jkeylu/torngithub)|
+|githubkit|[yanyongyu/githubkit](https://github.com/yanyongyu/githubkit)|
### Ruby
diff --git a/translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md b/translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md
index ef5e6b4a21..7ff3731a54 100644
--- a/translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md
+++ b/translations/zh-CN/data/reusables/actions/private-repository-forks-configure.md
@@ -1,10 +1,7 @@
----
-ms.openlocfilehash: 3def1c7efad50b8bfda097251abf28dd4a5f46df
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145084881"
----
-1. 在“复刻拉取请求工作流”下，选择选项。 例如：
-1. 单击“保存”以应用设置。
+1. Under **Fork pull request workflows**, select your options. For example:
+ {% ifversion actions-private-fork-workflow-approvals %}
+ {% else %}
+
+ {% endif %}
+
+1. Click **Save** to apply the settings.
diff --git a/translations/zh-CN/data/reusables/actions/private-repository-forks-options.md b/translations/zh-CN/data/reusables/actions/private-repository-forks-options.md
index ece0d1b83c..7e7219bd70 100644
--- a/translations/zh-CN/data/reusables/actions/private-repository-forks-options.md
+++ b/translations/zh-CN/data/reusables/actions/private-repository-forks-options.md
@@ -1,11 +1,4 @@
----
-ms.openlocfilehash: 6c1dd36680cbcbf04fda2d18f14a828249715ff7
-ms.sourcegitcommit: fb047f9450b41b24afc43d9512a5db2a2b750a2a
-ms.translationtype: HT
-ms.contentlocale: zh-CN
-ms.lasthandoff: 09/11/2022
-ms.locfileid: "145065910"
----
-- **从分支拉取请求运行工作流** - 允许用户使用具有只读权限、没有密码访问权限的 `GITHUB_TOKEN`，从分支拉取请求运行工作流。
-- **从拉取请求向工作流发送写入令牌** - 允许来自分支的拉取请求使用具有写入权限的 `GITHUB_TOKEN`。
-- **从拉取请求向工作流发送机密** - 使所有机密都可用于拉取请求。
+- **Run workflows from fork pull requests** - Allows users to run workflows from fork pull requests, using a `GITHUB_TOKEN` with read-only permission, and with no access to secrets.
+- **Send write tokens to workflows from pull requests** - Allows pull requests from forks to use a `GITHUB_TOKEN` with write permission.
+- **Send secrets to workflows from pull requests** - Makes all secrets available to the pull request.{% ifversion actions-private-fork-workflow-approvals %}
+- **Require approval for fork pull request workflows** - Workflow runs on pull requests from collaborators without write permission will require approval from someone with write permission before they will run.{% endif %}
diff --git a/translations/zh-CN/data/reusables/actions/workflows/approve-workflow-runs.md b/translations/zh-CN/data/reusables/actions/workflows/approve-workflow-runs.md
new file mode 100644
index 0000000000..4eda119c15
--- /dev/null
+++ b/translations/zh-CN/data/reusables/actions/workflows/approve-workflow-runs.md
@@ -0,0 +1,15 @@
+---
+ms.openlocfilehash: fec57b88af5ef5b7227d88a8c70e5a4b4bb9c769
+ms.sourcegitcommit: fdc4466e89467a7b13239e26c6042dc1428946b6
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/14/2022
+ms.locfileid: "148163814"
+---
+能够写入仓库的维护者可按照以下步骤来审查和运行来自贡献者、需要审批的拉取请求上的工作流程。
+
+{% data reusables.repositories.sidebar-pr %} {% data reusables.repositories.choose-pr-review %} {% data reusables.repositories.changed-files %}
+1. 检查拉取请求中的拟议更改，确保您在拉取请求分支上自由运行您的工作流程。 应特别注意 `.github/workflows/` 目录中影响工作流文件的任何拟议更改。
+1. 如果能自由在拉取请求分支上运行工作流，请返回到 {% octicon "comment-discussion" aria-label="The discussion icon" %}“转换”选项卡，在“等待审批的工作流”下，单击“批准并运行” 。
+
+ 
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md b/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
index cce6e5778b..11a4132fc1 100644
--- a/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
+++ b/translations/zh-CN/data/reusables/code-scanning/autobuild-compiled-languages.md
@@ -1 +1,9 @@
-For the supported compiled languages, you can use the `autobuild` action in the {% data variables.code-scanning.codeql_workflow %} to build your code. This avoids you having to specify explicit build commands for C/C++, C#,{% ifversion codeql-go-autobuild %} Go,{% endif %} and Java.
\ No newline at end of file
+---
+ms.openlocfilehash: 982b04961e4f780a5f1e284dad5620157f68569b
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161060"
+---
+对于受支持的编译语言，你可使用 {% data variables.code-scanning.codeql_workflow %} 中的 `autobuild` 操作来生成代码。 这样就无需为 C/C++、C#、{% ifversion codeql-go-autobuild %}Go{% endif %} 和 Java 指定显式生成命令。
\ No newline at end of file
diff --git a/translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md b/translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md
index 1400f1f34b..4373ce68a1 100644
--- a/translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md
+++ b/translations/zh-CN/data/reusables/code-scanning/codeql-runner-analyze-example.md
@@ -1,4 +1,12 @@
-1. Populate the {% data variables.product.prodname_codeql %} databases, analyze them, and upload the results to {% data variables.product.product_name %}. The results will appear in the **Security** tab for your repository.
+---
+ms.openlocfilehash: e6d7a33506174bf50d70ae9b5d4ac9857cd880ae
+ms.sourcegitcommit: b617c4a7a1e4bf2de3987a86e0eb217d7031490f
+ms.translationtype: HT
+ms.contentlocale: zh-CN
+ms.lasthandoff: 11/11/2022
+ms.locfileid: "148161224"
+---
+1. 填充 {% data variables.product.prodname_codeql %} 数据库、进行分析并将结果上传到 {% data variables.product.product_name %}。 结果将显示在存储库的“安全”选项卡中。
```shell
$ echo "$TOKEN" | /path/to-runner/codeql-runner-linux analyze --repository octo-org/example-repo
@@ -9,7 +17,7 @@
> POST /repos/octo-org/example-repo/code-scanning/sarifs - 202 in 786ms
> Successfully uploaded results
```
-2. To upload {% data variables.product.prodname_code_scanning %} results as pull request checks, specify the pull request using the
- Octokit 风格多样
-使用官方的 Octokit 库，或者使用任何适用的第三方库。
- -+--- +ms.openlocfilehash: c408676063e80cca29eb7392181c00c4ecf7f76d +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160761" +--- +{% data variables.product.prodname_copilot %} 可用于个人帐户位于 {% data variables.product.prodname_dotcom_the_website %} 上的 {% data variables.product.company_short %} 客户。 {% data reusables.copilot.emus-cannot-use-copilot %}
-{% data variables.product.prodname_copilot %} is free to use for verified students, teachers, and maintainers of popular open source projects. If you are not a student, teacher, or maintainer of a popular open source project, you can try {% data variables.product.prodname_copilot %} for free with a one-time 60 day trial. After the free trial, you will need a paid subscription for continued use. For more information, see "[About billing for {% data variables.product.prodname_copilot %}](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)." +{% data variables.product.prodname_copilot %} 供经过验证的学生、教师和热门开源项目的维护人员免费使用。 如果你不是学生、教师或热门开源项目的维护人员，可以在一次性 60 天试用版中免费试用 {% data variables.product.prodname_copilot %}。 免费试用后，需要付费订阅才能继续使用。 有关详细信息，请参阅“[关于 {% data variables.product.prodname_copilot %} 的计费](/billing/managing-billing-for-github-copilot/about-billing-for-github-copilot)”。 diff --git a/translations/zh-CN/data/reusables/github-connect/connection-port-protocol.md b/translations/zh-CN/data/reusables/github-connect/connection-port-protocol.md new file mode 100644 index 0000000000..659f2caf8f --- /dev/null +++ b/translations/zh-CN/data/reusables/github-connect/connection-port-protocol.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 3492d399c754d53fea2091a08c95b212455a8e18 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160758" +--- +连接通过端口 443 或 80 使用 HTTPS，并受 TLS 保护。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/gpg/paste-ssh-public-key.md b/translations/zh-CN/data/reusables/gpg/paste-ssh-public-key.md index f5f448cb30..eda475d710 100644 --- a/translations/zh-CN/data/reusables/gpg/paste-ssh-public-key.md +++ b/translations/zh-CN/data/reusables/gpg/paste-ssh-public-key.md @@ -1,12 +1,11 @@ --- -ms.openlocfilehash: dc6bad5b656bb5d755196146b017213b66d1730e -ms.sourcegitcommit: 80842b4e4c500daa051eff0ccd7cde91c2d4bb36 +ms.openlocfilehash: adefefb787099214cf17f7b2276a8f44f3fe8e56 +ms.sourcegitcommit: f54d01e643f994ce48f0774dbc680ad77dd6193f ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/11/2022 -ms.locfileid: "147884718" +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160570" --- -1. 若要在 Git 中设置 SSH 签名密钥，请粘贴下面的文本，替换要使用的密钥的剪贴板内容。 由于密钥包含空格，因此必须用引号将它括起： +1. 若要在 Git 中设置 SSH 签名密钥，请粘贴下面的文本，将 /PATH/TO/KEY.PUB 替换为要使用的公钥路径。 ```bash - $ git config --global user.signingkey 'ssh-ed25519 AAAAC3(...) user@example.com' - ``` \ No newline at end of file + $ git config --global user.signingkey=/PATH/TO/.SSH/KEY.PUB \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/organizations/blocking-a-user.md b/translations/zh-CN/data/reusables/organizations/blocking-a-user.md new file mode 100644 index 0000000000..b60cc8c641 --- /dev/null +++ b/translations/zh-CN/data/reusables/organizations/blocking-a-user.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: 44fb7593fc71c38604cb0e7b96ea0439c7028a1f +ms.sourcegitcommit: 1529de77bfcbe45519131b5f5fb3ab319758c2d2 +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/14/2022 +ms.locfileid: "148164221" +--- +阻止用户时，您可以选择无限期或在特定时间段内阻止他们。 如果在特定时间段内阻止某人，则所选时间结束后会自动解除对他们的阻止。 如果无限期阻止某人，您可以随时手动解除阻止。 有关详细信息，请参阅“[取消阻止用户对组织的访问](/communities/maintaining-your-safety-on-github/unblocking-a-user-from-your-organization)”。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/about-READMEs.md b/translations/zh-CN/data/reusables/repositories/about-READMEs.md new file mode 100644 index 0000000000..2b960461e2 --- /dev/null +++ b/translations/zh-CN/data/reusables/repositories/about-READMEs.md @@ -0,0 +1,9 @@ +--- +ms.openlocfilehash: a4b1ca4e0548ebc2be12a34e0bb1687e9e650038 +ms.sourcegitcommit: c2aa10a61db44ee111c09565b6114dd5c97b6e2e +ms.translationtype: HT +ms.contentlocale: zh-CN +ms.lasthandoff: 11/14/2022 +ms.locfileid: "148163427" +--- +您可以将 README 文件添加到仓库来交流有关您项目的重要信息。 自述文件以及存储库许可证、引文文件{% ifversion fpt or ghec %}、贡献指南、行为准则{% elsif ghes %}以及贡献指南{% endif %}传达了对项目的期望，并有助于管理贡献。 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/repositories/anyone-can-view-anonymized-url.md b/translations/zh-CN/data/reusables/repositories/anyone-can-view-anonymized-url.md index b077d8b56d..19e3feeea2 100644 --- a/translations/zh-CN/data/reusables/repositories/anyone-can-view-anonymized-url.md +++ b/translations/zh-CN/data/reusables/repositories/anyone-can-view-anonymized-url.md @@ -1,13 +1,13 @@ --- -ms.openlocfilehash: 85c7f83e66e8519c6d62346fe69b6e3f0b413ff1 -ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5 +ms.openlocfilehash: 478008cfe79ec4fe3c32c154af38692879f5c807 +ms.sourcegitcommit: d82f268a6f0236d1f4d2bf3d049974ada0170402 ms.translationtype: HT ms.contentlocale: zh-CN -ms.lasthandoff: 09/05/2022 -ms.locfileid: "147419888" +ms.lasthandoff: 11/10/2022 +ms.locfileid: "148160757" --- {% warning %} -警告：如果在拉取请求、问题评论或 {% data variables.contact.support_portal %} 票证中附加了文件，则任何人都可以查看匿名 URL，无需身份验证，即使该拉取请求位于专用存储库中{% ifversion ghes %}，或者启用了专用模式{% endif %}。 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt or ghec %}有关匿名 URL 的详细信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %} +警告：当将映像或视频上传到拉取请求或发布评论，或将文件上传到 {% data variables.contact.support_portal %} 中的工单时，任何人都可以查看匿名 URL，而无需身份验证，即使该拉取请求或问题位于专用存储库中{% ifversion ghes %}或者启用了专用模式{% endif %}。 要对敏感媒体文件保密，请从需要身份验证的私有网络或服务器提供它们。 {% ifversion fpt or ghec %}有关匿名 URL 的详细信息，请参阅“[关于匿名 URL](/github/authenticating-to-github/about-anonymized-urls)”。{% endif %} {% endwarning %} From 377bcd30d0c77d7c956aaabde0b5df6bd85409ac Mon Sep 17 00:00:00 2001 From: Matt Pollard