From 3c6a586a38891164a6969933328d6ea3a4726cc3 Mon Sep 17 00:00:00 2001 From: Riaan du Plessis Date: Sun, 20 Mar 2022 22:43:24 +0200 Subject: [PATCH 01/18] Added missing whitespace --- .../acceptable-use-policies/github-acceptable-use-policies.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md b/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md index 587d5ac59f..1e4adc1f7a 100644 --- a/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md +++ b/content/site-policy/acceptable-use-policies/github-acceptable-use-policies.md @@ -98,7 +98,7 @@ The Service's bandwidth limitations vary based on the features you use. If we de While we understand that you may want to promote your Content by posting supporters' names or logos in your Account, the primary focus of the Content posted in or through your Account to the Service should not be advertising or promotional marketing. This includes Content posted in or through Pages, Packages, repositories, and all other parts of the Service. You may include static images, links, and promotional text in the README documents or project description sections associated with your Account, but they must be related to the project you are hosting on GitHub. You may not advertise in other Users' Accounts, such as by posting monetized or excessive bulk content in issues. -You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/)or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion. +You may not promote or distribute content or activity that is illegal or otherwise prohibited by our [Terms of Service](/github/site-policy/github-terms-of-service/) or [Acceptable Use Policies](/github/site-policy/github-acceptable-use-policies/), including excessive automated bulk activity (for example, spamming), get-rich-quick schemes, and misrepresentation or deception related to your promotion. If you decide to post any promotional materials in your Account, you are solely responsible for complying with all applicable laws and regulations, including without limitation the U.S. Federal Trade Commission's Guidelines on Endorsements and Testimonials. We reserve the right to remove any promotional materials or advertisements that, in our sole discretion, violate any GitHub terms or policies. From d6eb5327ce6ffd85b8b75ceb59853c98cec56332 Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Mon, 21 Mar 2022 16:32:14 +0100 Subject: [PATCH 02/18] Update code owners to reflect restructuring (#26368) --- .github/CODEOWNERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index f54c51ee4e..d9e4842478 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -24,7 +24,7 @@ package.json @github/docs-engineering /translations/log/ @github/docs-localization @Octomerger # Site Policy -/content/github/site-policy/ @github/site-policy-admins +/content/site-policy/ @github/site-policy-admins # Content strategy /contributing/content-markup-reference.md @github/docs-content-strategy From d747df7c49f7c2c5eec3c16d0f2271190072f951 Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Mon, 21 Mar 2022 17:39:04 +0100 Subject: [PATCH 03/18] Fix two lightweight feature flags for GitHub AE (#26371) --- .../customizing-your-repository/about-code-owners.md | 2 +- .../searching-a-repositorys-releases.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 647063b1ee..a4bef4079e 100644 --- a/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -37,7 +37,7 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %} ## CODEOWNERS file size CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. diff --git a/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index fb70e9fcec..d13265d50b 100644 --- a/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -7,7 +7,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae-issue-4974: '*' + ghae: 'issue-4974' topics: - Repositories --- From 021b15a722e82d53078fe088b6c87e76efbec9ab Mon Sep 17 00:00:00 2001 From: Matt Pollard Date: Mon, 21 Mar 2022 17:42:59 +0100 Subject: [PATCH 04/18] Add conditions to remove beta note for code and secret scanning in GitHub AE (#26373) --- data/reusables/code-scanning/beta.md | 6 +++++- data/reusables/secret-scanning/beta.md | 7 ++++++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/data/reusables/code-scanning/beta.md b/data/reusables/code-scanning/beta.md index d8c203c722..ecb5dc9480 100644 --- a/data/reusables/code-scanning/beta.md +++ b/data/reusables/code-scanning/beta.md @@ -1,4 +1,8 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} {% note %} diff --git a/data/reusables/secret-scanning/beta.md b/data/reusables/secret-scanning/beta.md index b42386fada..30ec5c2ce6 100644 --- a/data/reusables/secret-scanning/beta.md +++ b/data/reusables/secret-scanning/beta.md @@ -1,4 +1,9 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} + {% note %} **Note:** {% data variables.product.prodname_secret_scanning_caps %} for organization-owned repositories is currently in beta and subject to change. From 2c2bd1deb7eef3680c94755456a522541701e569 Mon Sep 17 00:00:00 2001 From: djdefi Date: Mon, 21 Mar 2022 09:56:45 -0700 Subject: [PATCH 05/18] Add worker scaling note 3.1 (#26319) --- data/release-notes/enterprise-server/3-1/0.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/data/release-notes/enterprise-server/3-1/0.yml b/data/release-notes/enterprise-server/3-1/0.yml index f4db0c2cc8..ccd0725cf4 100644 --- a/data/release-notes/enterprise-server/3-1/0.yml +++ b/data/release-notes/enterprise-server/3-1/0.yml @@ -76,6 +76,7 @@ sections: - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - Check annotations older than four months will be archived. + - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - heading: Security Changes notes: From a246803262a8e0e349a4cc17bef0d866dc7b41ad Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 21 Mar 2022 11:11:12 -0700 Subject: [PATCH 06/18] New translation batch for pt (#26381) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt * run script/i18n/reset-known-broken-translation-files.js --- ...on-levels-for-a-user-account-repository.md | 2 +- .../environment-variables.md | 2 +- .../security-guides/encrypted-secrets.md | 4 +- .../workflow-commands-for-github-actions.md | 466 +++++++++++++++--- .../workflow-syntax-for-github-actions.md | 8 +- ...enabling-dependabot-for-your-enterprise.md | 2 +- .../configuring-a-hostname.md | 8 +- .../network-ports.md | 20 +- ...ng-a-failover-to-your-replica-appliance.md | 39 +- .../about-github-actions-for-enterprises.md | 2 +- .../about-using-actions-in-your-enterprise.md | 16 +- ...-githubcom-actions-using-github-connect.md | 4 +- .../about-migrations.md | 2 +- .../checking-for-existing-ssh-keys.md | 2 +- .../using-ssh-over-the-https-port.md | 2 +- ...ode-scanning-alerts-for-your-repository.md | 4 +- .../about-dependabot-alerts.md | 6 +- ...ilities-in-the-github-advisory-database.md | 2 +- ...ing-notifications-for-dependabot-alerts.md | 6 +- .../dependabot/dependabot-alerts/index.md | 4 +- .../viewing-and-updating-dependabot-alerts.md | 8 +- ...configuring-dependabot-security-updates.md | 4 +- .../dependabot-security-updates/index.md | 4 +- .../about-dependabot-version-updates.md | 4 +- ...ion-options-for-the-dependabot.yml-file.md | 6 +- .../configuring-dependabot-version-updates.md | 8 +- .../customizing-dependency-updates.md | 4 +- .../dependabot-version-updates/index.md | 4 +- ...ndencies-configured-for-version-updates.md | 2 +- .../content/code-security/dependabot/index.md | 4 +- .../working-with-dependabot/index.md | 6 +- ...your-actions-up-to-date-with-dependabot.md | 4 +- ...naging-encrypted-secrets-for-dependabot.md | 2 +- ...ng-pull-requests-for-dependency-updates.md | 4 +- .../troubleshooting-dependabot-errors.md | 8 +- ...he-detection-of-vulnerable-dependencies.md | 12 +- .../github-security-features.md | 2 +- .../securing-your-organization.md | 6 +- .../securing-your-repository.md | 6 +- .../secret-scanning/about-secret-scanning.md | 4 +- .../about-the-security-overview.md | 16 +- .../about-supply-chain-security.md | 128 ++--- .../about-the-dependency-graph.md | 10 +- ...loring-the-dependencies-of-a-repository.md | 12 +- .../troubleshooting-the-dependency-graph.md | 6 +- ...ating-a-github-app-using-url-parameters.md | 38 +- .../creating-a-github-app.md | 2 +- ...g-and-authorizing-users-for-github-apps.md | 2 +- ...se-settings-for-your-private-repository.md | 4 +- .../get-started/quickstart/fork-a-repo.md | 2 +- ...-up-a-trial-of-github-enterprise-server.md | 2 +- .../creating-and-highlighting-code-blocks.md | 2 +- .../creating-diagrams.md | 34 +- ...analysis-settings-for-your-organization.md | 6 +- ...om-repository-roles-for-an-organization.md | 28 +- ...r-github-pages-site-locally-with-jekyll.md | 2 +- .../requesting-a-pull-request-review.md | 6 +- .../about-code-owners.md | 2 +- .../searching-a-repositorys-releases.md | 2 +- .../working-with-non-code-files.md | 36 +- .../content/rest/reference/deploy_keys.md | 6 +- .../content/rest/reference/deployments.md | 2 +- .../github-community-guidelines.md | 2 +- .../release-notes/enterprise-server/3-1/0.yml | 1 + .../enterprise-server/3-2/0-rc1.yml | 2 +- .../release-notes/enterprise-server/3-2/0.yml | 2 +- .../release-notes/enterprise-server/3-4/0.yml | 5 + .../actions/github-connect-resolution.md | 2 +- .../private-repository-forks-overview.md | 2 +- .../reusables/actions/ref_name-description.md | 2 +- .../actions/ref_protected-description.md | 2 +- .../reusables/actions/ref_type-description.md | 2 +- .../reusables/actions/registry-credentials.md | 2 +- .../actions/restrict-runner-workflow-beta.md | 2 +- .../reusable-workflow-calling-syntax.md | 6 +- .../actions/reusable-workflows-ghes-beta.md | 2 +- .../reusables/actions/reusable-workflows.md | 2 +- .../reusables/actions/run_id_description.md | 2 +- .../actions/runner-arch-description.md | 2 +- .../actions/runner-tool-cache-description.md | 2 +- ...osted-runner-check-installation-success.md | 4 +- ...ed-runner-configure-runner-group-access.md | 2 +- ...-runner-navigate-to-repo-org-enterprise.md | 6 +- ...self-hosted-runner-networking-to-dotcom.md | 2 +- .../self-hosted-runner-ports-protocols.md | 2 +- .../data/reusables/code-scanning/beta.md | 6 +- .../dependabot/private-dependencies-note.md | 2 +- .../data/reusables/secret-scanning/beta.md | 7 +- 88 files changed, 728 insertions(+), 396 deletions(-) diff --git a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md index 2ffb6eda9d..b1bc170fad 100644 --- a/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md +++ b/translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/permission-levels-for-a-user-account-repository.md @@ -48,7 +48,7 @@ O proprietário do repositório tem controle total do repositório. Além das a | Personalizar a visualização das mídias sociais do repositório | "[Personalizar a visualização das mídias sociais do seu repositório](/github/administering-a-repository/customizing-your-repositorys-social-media-preview)" | | Criar um modelo a partir do repositório | "[Criando um repositório de modelo](/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)"{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} | Controle o acesso a {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis | "[Gerenciar as configurações de segurança e análise do repositório](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)" |{% endif %}{% ifversion fpt or ghec %} -| Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório | "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | +| Ignorar {% data variables.product.prodname_dependabot_alerts %} no repositório | "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" | | Gerenciar o uso de dados para um repositório privado | "[Gerenciar as configurações de uso de dados para o seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)" {% endif %} | Definir os proprietários do código do repositório | "[Sobre proprietários do código](/github/creating-cloning-and-archiving-repositories/about-code-owners)" | diff --git a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md index 3d09ced703..e0fa6a26af 100644 --- a/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md +++ b/translations/pt-BR/content/actions/learn-github-actions/environment-variables.md @@ -147,7 +147,7 @@ As variáveis de ambiente padrão que os conjuntos de {% data variables.product. {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %} | `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} For example, `feature-branch-1`.| | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} | | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} {%- endif %} -| `GITHUB_REPOSITORY` | O nome do proprietário e do repositório. Por exemplo, `octocat/Hello-World`. | | `GITHUB_REPOSITORY_OWNER` | O nome do proprietário do repositório. Por exemplo, `octocat`. | | `GITHUB_RETENTION_DAYS` | O número de dias que os registros da execução do fluxo de trabalho e os artefatos são mantidos. Por exemplo, `90`. | | `GITHUB_RUN_ATTEMPT` | Um número único para cada tentativa da execução de um fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. Por exemplo, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} Por exemplo, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} Por exemplo, `3`. | | `GITHUB_SERVER_URL`| A URL do servidor de {% data variables.product.product_name %} server. Por exemplo: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | O SHA do commit que acionou o fluxo de trabalho. The value of this commit SHA depends on the event that triggered the workflow. For more information, see [Events that trigger workflows](/actions/using-workflows/events-that-trigger-workflows). Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | | `GITHUB_WORKFLOW` | O nome do fluxo de trabalho. Por exemplo, `My test workflow`. Se o fluxo de trabalho não determinar um `nome`, o valor desta variável será o caminho completo do arquivo do fluxo de trabalho no repositório. | | `GITHUB_WORKSPACE` | O diretório de trabalho padrão no executor para as etapas e para a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. | +| `GITHUB_REPOSITORY` | O nome do proprietário e do repositório. Por exemplo, `octocat/Hello-World`. | | `GITHUB_REPOSITORY_OWNER` | O nome do proprietário do repositório. Por exemplo, `octocat`. | | `GITHUB_RETENTION_DAYS` | O número de dias que os registros da execução do fluxo de trabalho e os artefatos são mantidos. Por exemplo, `90`. | | `GITHUB_RUN_ATTEMPT` | Um número único para cada tentativa da execução de um fluxo de trabalho particular em um repositório. Este número começa em 1 para a primeira tentativa de execução do fluxo de trabalho e aumenta a cada nova execução. Por exemplo, `3`. | | `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} Por exemplo, `1658821493`. | | `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} Por exemplo, `3`. | | `GITHUB_SERVER_URL`| A URL do servidor de {% data variables.product.product_name %} server. Por exemplo: `https://{% data variables.product.product_url %}`. | `GITHUB_SHA` | O SHA do commit que acionou o fluxo de trabalho. O valor do commit deste SHA depende do evento que acionou o fluxo de trabalho. Para obter mais informações, consulte [Eventos que acionam fluxos de trabalho](/actions/using-workflows/events-that-trigger-workflows). Por exemplo, `ffac537e6cbbf934b08745a378932722df287a53`. | | `GITHUB_WORKFLOW` | O nome do fluxo de trabalho. Por exemplo, `My test workflow`. Se o fluxo de trabalho não determinar um `nome`, o valor desta variável será o caminho completo do arquivo do fluxo de trabalho no repositório. | | `GITHUB_WORKSPACE` | O diretório de trabalho padrão no executor para as etapas e para a localidade padrão do seu repositório ao usar a ação [`checkout`](https://github.com/actions/checkout). Por exemplo, `/home/runner/work/my-repo-name/my-repo-name`. | {%- if actions-runner-arch-envvars %} | `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %} {%- endif %} diff --git a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md index b9e44ac4cb..8d25a5c220 100644 --- a/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md +++ b/translations/pt-BR/content/actions/security-guides/encrypted-secrets.md @@ -226,9 +226,9 @@ steps: ``` {% endraw %} -Secrets cannot be directly referenced in `if:` conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job. For more information, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)" and [`jobs..steps[*].if`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsif). +Não é possível fazer referência a segredos nas condicionais `if:`. Em vez disso, considere definir segredos como variáveis de ambiente no nível de trabalho e, em seguida, fazer referência às variáveis de ambiente para executar etapas condicionalmente no trabalho. Para obter mais informações, consulte "[Disponibilidade de contexto](/actions/learn-github-actions/contexts#context-availability)" e [`trabalhos..steps[*].if`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsif). -If a secret has not been set, the return value of an expression referencing the secret (such as {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} in the example) will be an empty string. +Se um segredo não tiver sido definido, o valor de retorno de uma expressão referente ao segredo (como {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} no exemplo) será uma string vazia. Evite a transmissão de segredos entre processos da linha de comando sempre que possível. Os processos da linha de comando podem ser visíveis para outros usuários (usando o comando `ps`) ou capturado por [eventos de auditoria de segurança](https://docs.microsoft.com/windows-server/identity/ad-ds/manage/component-updates/command-line-process-auditing). Para ajudar a proteger os segredos, considere o uso de variáveis de ambiente, `STDIN`, ou outros mecanismos compatíveis com o processo de destino. diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md index eb591ed4c1..9e184886de 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -2,6 +2,7 @@ title: Comandos do fluxo de trabalho para o GitHub Actions shortTitle: Comandos do fluxo de trabalho intro: Você pode usar comandos do fluxo de trabalho ao executar comandos do shell em um fluxo de trabalho ou no código de uma ação. +defaultTool: bash redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -26,10 +27,24 @@ As ações podem comunicar-se com a máquina do executor para definir as variáv A maioria dos comandos de fluxo de trabalho usa o comando `echo` em um formato específico, enquanto outros são chamados escrevendo um arquivo. Para obter mais informações, consulte ["Arquivos de ambiente".](#environment-files) -``` bash +### Exemplo + +{% bash %} + +```bash{:copy} echo "::workflow-command parameter1={data},parameter2={data}::{command value}" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}" +``` + +{% endpowershell %} + {% note %} **Observação:** Os nomes do comando do fluxo de trabalho e do parâmetro não diferenciam maiúsculas e minúsculas. @@ -46,14 +61,18 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}" O [actions/toolkit](https://github.com/actions/toolkit) inclui uma quantidade de funções que podem ser executadas como comandos do fluxo de trabalho. Use a sintaxe `::` para executar os comandos do fluxo de trabalho no arquivo YAML. Em seguida, esses comandos serão enviados para a o executor por meio do `stdout`. Por exemplo, em vez de usar o código para definir uma saída, como abaixo: -```javascript +```javascript{:copy} core.setOutput('SELECTED_COLOR', 'green'); ``` +### Example: Setting a value + Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o mesmo valor: +{% bash %} + {% raw %} -``` yaml +```yaml{:copy} - name: Set selected color run: echo '::set-output name=SELECTED_COLOR::green' id: random-color-generator @@ -62,6 +81,22 @@ Você pode usar o comando `set-output` no seu fluxo de trabalho para definir o m ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} + - name: Set selected color + run: Write-Output "::set-output name=SELECTED_COLOR::green" + id: random-color-generator + - name: Get color + run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}" +``` +{% endraw %} + +{% endpowershell %} + A tabela a seguir mostra quais funções do conjunto de ferramentas estão disponíveis dentro de um fluxo de trabalho: | Função do kit de ferramentas | Comando equivalente do fluxo de trabalho | @@ -86,186 +121,336 @@ A tabela a seguir mostra quais funções do conjunto de ferramentas estão dispo ## Definir um parâmetro de saída -``` +Configura um parâmetro de saída da ação. + +```{:copy} ::set-output name={name}::{value} ``` -Configura um parâmetro de saída da ação. - Opcionalmente, você também pode declarar os parâmetros de saída no arquivo de metadados de uma ação. Para obter mais informações, consulte "[Sintaxe de metadados para o {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)". -### Exemplo +### Example: Setting an output parameter -``` bash +{% bash %} + +```bash{:copy} echo "::set-output name=action_fruit::strawberry" ``` -## Configurar uma mensagem de depuração +{% endbash %} +{% powershell %} + +```pwsh{:copy} +Write-Output "::set-output name=action_fruit::strawberry" ``` -::debug::{message} -``` + +{% endpowershell %} + +## Configurar uma mensagem de depuração Imprime uma mensagem de erro no log. Você deve criar um segredo nomeado `ACTIONS_STEP_DEBUG` com o valor `true` para ver as mensagens de erro configuradas por esse comando no log. Para obter mais informações, consulte "[Habilitar o registro de depuração](/actions/managing-workflow-runs/enabling-debug-logging)". -### Exemplo +```{:copy} +::debug::{message} +``` -``` bash +### Example: Setting a debug message + +{% bash %} + +```bash{:copy} echo "::debug::Set the Octocat variable" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::debug::Set the Octocat variable" +``` + +{% endpowershell %} + {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} ## Configurando uma mensagem de aviso -``` +Cria uma mensagem de aviso e a imprime no registro. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de aviso e a imprime no registro. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Exemplo +### Example: Setting a notice message -``` bash +{% bash %} + +```bash{:copy} echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} {% endif %} ## Configurar uma mensagem de aviso -``` +Cria uma mensagem de aviso e a imprime no log. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de aviso e a imprime no log. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Exemplo +### Example: Setting a warning message -``` bash +{% bash %} + +```bash{:copy} echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## Configurar uma mensagem de erro -``` +Cria uma mensagem de erro e a imprime no log. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -Cria uma mensagem de erro e a imprime no log. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Exemplo +### Example: Setting an error message -``` bash +{% bash %} + +```bash{:copy} echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## Agrupar linhas dos registros -``` +Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo` e especifique um `título`. Qualquer coisa que você imprimir no registro entre os comandos `grupo` e `endgroup` estará aninhada dentro de uma entrada expansível no registro. + +```{:copy} ::group::{title} ::endgroup:: ``` -Cria um grupo expansível no registro. Para criar um grupo, use o comando `grupo` e especifique um `título`. Qualquer coisa que você imprimir no registro entre os comandos `grupo` e `endgroup` estará aninhada dentro de uma entrada expansível no registro. +### Example: Grouping log lines -### Exemplo +{% bash %} -```bash -echo "::group::My title" -echo "Inside group" -echo "::endgroup::" +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + steps: + - name: Group of log lines + run: | + echo "::group::My title" + echo "Inside group" + echo "::endgroup::" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + steps: + - name: Group of log lines + run: | + Write-Output "::group::My title" + Write-Output "Inside group" + Write-Output "::endgroup::" +``` + +{% endpowershell %} + ![Grupo dobrável no registro da execução do fluxo de trabalho](/assets/images/actions-log-group.png) ## Mascarar um valor no registro -``` +```{:copy} ::add-mask::{value} ``` Mascarar um valor evita que uma string ou variável seja impressa no log. Cada palavra mascarada separada por espaço em branco é substituída pelo caractere `*`. Você pode usar uma variável de ambiente ou string para o `value` da máscara. -### Exemplo de máscara de string +### Example: Masking a string Quando você imprime `"Mona The Octocat"` no log, você verá `"***"`. -```bash +{% bash %} + +```bash{:copy} echo "::add-mask::Mona The Octocat" ``` -### Exemplo de máscara de uma variável de ambiente +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::add-mask::Mona The Octocat" +``` + +{% endpowershell %} + +### Example: Masking an environment variable Ao imprimir a variável `MY_NAME` ou o valor `"Mona The Octocat"` no log, você verá `"***"` em vez de `"Mona The Octocat"`. -```bash -MY_NAME="Mona The Octocat" -echo "::add-mask::$MY_NAME" +{% bash %} + +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: bash-version + run: echo "::add-mask::$MY_NAME" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: powershell-version + run: Write-Output "::add-mask::$env:MY_NAME" +``` + +{% endpowershell %} + ## Parar e iniciar os comandos no fluxo de trabalho -`::stop-commands::{endtoken}` - Para de processar quaisquer comandos de fluxo de trabalho. Esse comando especial permite fazer o registro do que você desejar sem executar um comando do fluxo de trabalho acidentalmente. Por exemplo, é possível parar o log para gerar um script inteiro que tenha comentários. +```{:copy} +::stop-commands::{endtoken} +``` + Para parar o processamento de comandos de fluxo de trabalho, passe um token único para `stop-commands`. Para retomar os comandos do fluxo de trabalho, passe o mesmo token que você usou para parar os comandos do fluxo de trabalho. {% warning %} -**Aviso:** Certifique-se de que o token que você está usando é gerado aleatoriamente e exclusivo para cada execução. Como demonstrado no exemplo abaixo, você pode gerar um hash exclusivo do seu `github.token` para cada execução. +**Aviso:** Certifique-se de que o token que você está usando é gerado aleatoriamente e exclusivo para cada execução. {% endwarning %} -``` +```{:copy} ::{endtoken}:: ``` -### Exemplo de parar e iniciar comandos de workflow +### Example: Stopping and starting workflow commands + +{% bash %} {% raw %} -```yaml +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest steps: - - name: disable workflow commands + - name: Disable workflow commands run: | - echo '::warning:: this is a warning' - echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`" - echo '::warning:: this will NOT be a warning' - echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::" - echo '::warning:: this is a warning again' + echo '::warning:: This is a warning message, to demonstrate that commands are being processed.' + stopMarker=$(uuidgen) + echo "::stop-commands::$stopMarker" + echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + echo "::$stopMarker::" + echo '::warning:: This is a warning again, because stop-commands has been turned off.' +``` +{% endraw %} + +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: Disable workflow commands + run: | + Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.' + $stopMarker = New-Guid + Write-Output "::stop-commands::$stopMarker" + Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + Write-Output "::$stopMarker::" + Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.' ``` {% endraw %} +{% endpowershell %} + ## Eco de saídas de comando -``` +Habilita ou desabilita o eco de comandos de fluxo de trabalho. Por exemplo, se você usar o comando `set-output` em um fluxo de trabalho, ele definirá um parâmetro de saída, mas o registro da execução do fluxo de trabalho não irá mostrar o comando em si. Se você habilitar o comando de eco, o registro mostrará o comando, como `::set-output name={name}::{value}`. + +```{:copy} ::echo::on ::echo::off ``` -Habilita ou desabilita o eco de comandos de fluxo de trabalho. Por exemplo, se você usar o comando `set-output` em um fluxo de trabalho, ele definirá um parâmetro de saída, mas o registro da execução do fluxo de trabalho não irá mostrar o comando em si. Se você habilitar o comando de eco, o registro mostrará o comando, como `::set-output name={name}::{value}`. - O eco de comandos encontra-se desabilitado por padrão. No entanto, um comando de fluxo de trabalho será refletido se houver algum erro que processa o comando. Os comandos `add-mask`, `depurar`, `aviso` e `erro` não são compatíveis com o eco, porque suas saídas já estão ecoadas no registros. Você também pode habilitar o comando de eco globalmente ativando o registrode depuração da etapa usando o segredo `ACTIONS_STEP_DEBUG`. Para obter mais informações, consulte[Habilitando o log de depuração](/actions/managing-workflow-runs/enabling-debug-logging)". Em contraste, o comando do fluxo de trabalho `echo` permite que você habilite o comando de eco em um nível mais granular em vez de habilitá-lo para cada fluxo de trabalho em um repositório. -### Exemplo de alternar o comando do eco +### Example: Toggling command echoing -```yaml +{% bash %} + +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest @@ -279,9 +464,29 @@ jobs: echo '::set-output name=action_echo::disabled' ``` -A etapa acima imprime as seguintes linhas no registro: +{% endbash %} +{% powershell %} + +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: toggle workflow command echoing + run: | + write-output "::set-output name=action_echo::disabled" + write-output "::echo::on" + write-output "::set-output name=action_echo::enabled" + write-output "::echo::off" + write-output "::set-output name=action_echo::disabled" ``` + +{% endpowershell %} + +The example above prints the following lines to the log: + +```{:copy} ::set-output name=action_echo::enabled ::echo::off ``` @@ -298,13 +503,13 @@ O comando `save-state` pode ser executado apenas em uma ação e não está disp Este exemplo usa o JavaScript para executar o comando `save-state`. A variável de ambiente resultante é denominada `STATE_processID` com o valor de `12345`: -``` javascript +```javascript{:copy} console.log('::save-state name=processID::12345') ``` A variável `STATE_processID` está exclusivamente disponível para o script de limpeza executado na ação `principal`. Este exemplo é executado em `principal` e usa o JavaScript para exibir o valor atribuído à variável de ambiente `STATE_processID`: -``` javascript +```javascript{:copy} console.log("O PID em execução a partir da ação principal é: " + process.env.STATE_processID); ``` @@ -312,37 +517,70 @@ console.log("O PID em execução a partir da ação principal é: " + process.e Durante a execução de um fluxo de trabalho, o executor gera arquivos temporários que podem ser usados para executar certas ações. O caminho para esses arquivos são expostos através de variáveis de ambiente. Você precisará usar a codificação UTF-8 ao escrever para esses arquivos para garantir o processamento adequado dos comandos. Vários comandos podem ser escritos no mesmo arquivo, separados por novas linhas. -{% warning %} +{% powershell %} -**Aviso:** no Windows, o PowerShell de legado (`shell: powershell`) não usa UTF-8 por padrão. +{% note %} -Ao usar `shell: powershell`, você deverá especificar a codificação UTF-8. Por exemplo: +**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. Por exemplo: -```yaml +```yaml{:copy} jobs: legacy-powershell-example: - uses: windows-2019 + runs-on: windows-latest steps: - shell: powershell - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append + run: | + "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Como alternativa, você pode usar PowerShell Core (`shell: pwsh`), cujo padrão é UTF-8. +PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. Por exemplo: -{% endwarning %} +```yaml{:copy} +jobs: + powershell-core-example: + runs-on: windows-latest + steps: + - shell: pwsh + run: | + "mypath" >> $env:GITHUB_PATH +``` + +{% endnote %} + +{% endpowershell %} ## Definir uma variável de ambiente -``` bash +{% bash %} + +```bash{:copy} echo "{environment_variable_name}={value}" >> $GITHUB_ENV ``` +{% endbash %} + +{% powershell %} + +- Using PowerShell version 6 and higher: +```pwsh{:copy} +"{environment_variable_name}={value}" >> $env:GITHUB_ENV +``` + +- Using PowerShell version 5.1 and below: +```powershell{:copy} +"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append +``` + +{% endpowershell %} + Você pode tornar uma variável de ambiente disponível para quaisquer etapas subsequentes em um trabalho de fluxo de trabalho definindo ou atualizando a variável de ambiente e gravando isso no arquivo de ambiente `GITHUB_ENV`. A etapa que cria ou atualiza a variável de ambiente não tem acesso ao novo valor, mas todos os passos subsequentes em um trabalho terão acesso. Os nomes das variáveis de ambiente são diferenciam maiúsculas e minúsculas e você pode incluir a pontuação. Para obter mais informações, consulte "[Variáveis de ambiente](/actions/learn-github-actions/environment-variables)". ### Exemplo +{% bash %} + {% raw %} -``` +```yaml{:copy} steps: - name: Set the value id: step_one @@ -355,11 +593,31 @@ steps: ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +steps: + - name: Set the value + id: step_one + run: | + "action_state=yellow" >> $env:GITHUB_ENV + - name: Use the value + id: step_two + run: | + Write-Output "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} + +{% endpowershell %} + ### Strings de linha múltipla Para strings linha múltipla, você pode usar um delimitador com a seguinte sintaxe. -``` +```{:copy} {name}<<{delimiter} {value} {delimiter} @@ -367,29 +625,75 @@ Para strings linha múltipla, você pode usar um delimitador com a seguinte sint #### Exemplo -Neste exemplo, usamos `EOF` como um delimitador e definimos a variável de ambiente `JSON_RESPONSE` como o valor da resposta de curl. -```yaml +This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response. + +{% bash %} + +```yaml{:copy} steps: - - name: Set the value + - name: Set the value in bash id: step_one run: | echo 'JSON_RESPONSE<> $GITHUB_ENV - curl https://httpbin.org/json >> $GITHUB_ENV + curl https://example.lab >> $GITHUB_ENV echo 'EOF' >> $GITHUB_ENV ``` -## Adicionar um caminho do sistema +{% endbash %} -``` bash -echo "{path}" >> $GITHUB_PATH +{% powershell %} + +```yaml{:copy} +steps: + - name: Set the value in pwsh + id: step_one + run: | + "JSON_RESPONSE<> $env:GITHUB_ENV + (Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV + "EOF" >> $env:GITHUB_ENV + shell: pwsh ``` +{% endpowershell %} + +## Adicionar um caminho do sistema + Prepara um diretório para a variável `PATH` do sistema e disponibiliza automaticamente para todas as ações subsequentes no trabalho atual; a ação atualmente em execução não pode acessar a variável de caminho atualizada. Para ver os caminhos atualmente definidos para o seu trabalho, você pode usar o `echo "$PATH"` em uma etapa ou ação. +{% bash %} + +```bash{:copy} +echo "{path}" >> $GITHUB_PATH +``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +"{path}" >> $env:GITHUB_PATH +``` + +{% endpowershell %} + ### Exemplo Este exemplo demonstra como adicionar o diretório `$HOME/.local/bin` ao `PATH`: -``` bash +{% bash %} + +```bash{:copy} echo "$HOME/.local/bin" >> $GITHUB_PATH ``` + +{% endbash %} + + +This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`: + +{% powershell %} + +```pwsh{:copy} +"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH +``` + +{% endpowershell %} diff --git a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md index 59f2df6e10..560cdf1737 100644 --- a/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md +++ b/translations/pt-BR/content/actions/using-workflows/workflow-syntax-for-github-actions.md @@ -342,11 +342,11 @@ steps: uses: actions/heroku@1.0.0 ``` -#### Example: Using secrets +#### Exemplo: Usando segredos -Secrets cannot be directly referenced in `if:` conditionals. Instead, consider setting secrets as job-level environment variables, then referencing the environment variables to conditionally run steps in the job. +Não é possível fazer referência a segredos nas condicionais `if:`. Em vez disso, considere definir segredos como variáveis de ambiente no nível de trabalho e, em seguida, fazer referência às variáveis de ambiente para executar etapas condicionalmente no trabalho. -If a secret has not been set, the return value of an expression referencing the secret (such as {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} in the example) will be an empty string. +Se um segredo não tiver sido definido, o valor de retorno de uma expressão referente ao segredo (como {% raw %}`${{ secrets.SuperSecret }}`{% endraw %} no exemplo) será uma string vazia. {% raw %} ```yaml @@ -365,7 +365,7 @@ jobs: ``` {% endraw %} -For more information, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)" and "[Encrypted secrets](/actions/security-guides/encrypted-secrets)." +Para obter mais informações, consulte "[Disponibilidade de contexto](/actions/learn-github-actions/contexts#context-availability)" e "[Segredos criptografados](/actions/security-guides/encrypted-secrets)". ### `jobs..steps[*].name` diff --git a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md index 2c14eff6db..6b90321137 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md +++ b/translations/pt-BR/content/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise.md @@ -67,7 +67,7 @@ Após habilitar {% data variables.product.prodname_dependabot_alerts %}, você p Com {% data variables.product.prodname_dependabot_updates %}, {% data variables.product.company_short %} cria automaticamente pull requests para atualizar dependências de duas maneiras. - **{% data variables.product.prodname_dependabot_version_updates %}**: Os usuários adicionam um arquivo de configuração de {% data variables.product.prodname_dependabot %} ao repositório para habilitar {% data variables.product.prodname_dependabot %} e criar pull requests quando uma nova versão de uma dependência monitorada for lançada. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". -- **{% data variables.product.prodname_dependabot_security_updates %}**: Os usuários alternam uma configuração de repositório para habilitar {% data variables.product.prodname_dependabot %} para criar pull requests quando {% data variables.product.prodname_dotcom %} detecta uma vulnerabilidade em uma das dependências do gráfico de dependências para o repositório. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." +- **{% data variables.product.prodname_dependabot_security_updates %}**: Os usuários alternam uma configuração de repositório para habilitar {% data variables.product.prodname_dependabot %} para criar pull requests quando {% data variables.product.prodname_dotcom %} detecta uma vulnerabilidade em uma das dependências do gráfico de dependências para o repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)" e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)". {% endif %} ## Habilitando {% data variables.product.prodname_dependabot_alerts %} diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 509097a1fd..10f71e3518 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -17,7 +17,11 @@ topics: Se configurar um nome de host em vez de um endereço IP codificado, você poderá alterar o hardware físico em que a {% data variables.product.product_location %} é executada sem afetar os usuários ou o software cliente. -A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. Por exemplo, a configuração do nome de host pode ser `github.nomedaempresa.com.` Também recomendamos habilitar o isolamento de subdomínio para o nome do host escolhido a fim de mitigar várias vulnerabilidades no estilo de script entre sites. Para obter mais informações sobre as configurações de nome de host, consulte a [Seção 2.1 em HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). +A configuração do nome de host no {% data variables.enterprise.management_console %} deve ser definida como um nome de domínio totalmente qualificado (FQDN) que seja resolvido na internet ou dentro da sua rede interna. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. + +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} @@ -29,4 +33,4 @@ A configuração do nome de host no {% data variables.enterprise.management_cons {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -Depois de configurar um nome de host, recomendamos que você habilite o isolamento de subdomínio para a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. Para obter mais informações, consulte "[Habilitar isolamento de subdomínio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)". diff --git a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md index 04e7395bf2..7868daccfd 100644 --- a/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md +++ b/translations/pt-BR/content/admin/configuration/configuring-network-settings/network-ports.md @@ -26,7 +26,7 @@ Certas portas administrativas são obrigatórias para configurar a {% data varia | Porta | Serviço | Descrição | | -------- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 8443 | HTTPS | {% data variables.enterprise.management_console %} seguro na web. Obrigatória para instalação e configuração básicas. | -| 8080 | HTTP | {% data variables.enterprise.management_console %} de texto simples na web. Not required unless TLS is disabled manually. | +| 8080 | HTTP | {% data variables.enterprise.management_console %} de texto simples na web. Não é obrigatória, a menos que o TSL seja desabilitado manualmente. | | 122 | SSH | Acesso de shell à {% data variables.product.product_location %}. Obrigatório para estar aberto a conexões de entrada entre todos os nós em uma configuração de alta disponibilidade. A porta SSH padrão (22) é dedicada ao tráfego de rede de aplicativos Git e SSH. | | 1194/UDP | VPN | Túnel de rede de réplica segura na configuração de alta disponibilidade. Obrigatório estar aberto para a comunicação entre todos os nós da configuração. | | 123/UDP | NTP | Obrigatória para operações de protocolo de tempo. | @@ -39,7 +39,7 @@ As portas de aplicativo fornecem aplicativos da web e acesso dos usuários finai | Porta | Serviço | Descrição | | ----- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 443 | HTTPS | Acesso ao aplicativo da web e ao Git por HTTPS. | -| 80 | HTTP | Acesso ao aplicativo da web. All requests are redirected to the HTTPS port if TLS is configured. | +| 80 | HTTP | Acesso ao aplicativo da web. Todas as solicitações são redirecionadas para a porta HTTPS se o TLS estiver configurado. | | 22 | SSH | Acesso ao Git por SSH. Compatível com operações de clonagem, fetch e push em repositórios públicos e privados. | | 9418 | Git | A porta do protocolo Git é compatível com operações de clonagem e fetch em repositórios públicos com comunicação de rede não criptografada. {% data reusables.enterprise_installation.when-9418-necessary %} @@ -53,17 +53,17 @@ As portas de e-mail devem estar acessíveis diretamente ou via retransmissão pa | ----- | ------- | ------------------------------------------- | | 25 | SMTP | Suporte a SMTP com criptografia (STARTTLS). | -## {% data variables.product.prodname_actions %} ports +## Portas de {% data variables.product.prodname_actions %} -{% data variables.product.prodname_actions %} ports must be accessible for self-hosted runners to connect to {% data variables.product.product_location %}. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)." +As portas de {% data variables.product.prodname_actions %} devem poder ser acessadas por executores auto-hospedados para se conectar a {% data variables.product.product_location %}. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github-enterprise-server)." -| Porta | Serviço | Descrição | -| ----- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| 443 | HTTPS | Self-hosted runners connect to {% data variables.product.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.product.product_location %} to receive job assignments and to download new versions of the runner application. Required if TLS is not configured. | +| Porta | Serviço | Descrição | +| ----- | ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| 443 | HTTPS | Os executores auto-hospedados conectam a {% data variables.product.product_location %} para receber atividades de trabalho e fazer o download das novas versões do aplicativo do executor. Obrigatório se TLS estiver configurado. | +| 80 | HTTP | Os executores auto-hospedados conectam a {% data variables.product.product_location %} para receber atividades de trabalho e fazer o download das novas versões do aplicativo do executor. Obrigatório se TLS não estiver configurado. | -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.product.product_location %} first, via these ports, before checking {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% 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)". +Se você habilitar o acesso automático a ações de {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_actions %} sempre irá pesquisar uma ação em {% data variables.product.product_location %} primeiro, por meio dessas portas, antes de verificar {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Habilitar o acesso automático às ações de {% data variables.product.prodname_dotcom_the_website %} usando o {% 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)". ## Leia mais -- "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)" +- "[Configurando TLS](/admin/configuration/configuring-network-settings/configuring-tls)" diff --git a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index 8fbdf432b2..54c752c8a2 100644 --- a/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/pt-BR/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -19,25 +19,32 @@ O tempo do failover dependerá do tempo necessário para promover manualmente a {% data reusables.enterprise_installation.promoting-a-replica %} -1. Para permitir que a replicação termine antes de você alternar os appliances, coloque o appliance principal no modo de manutenção: - - Para usar o console de gerenciamento, consulte "[Habilitar e programar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"; - - Você também pode usar o comando `ghe-maintenance -s`. +1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode. + + - Put the appliance into maintenance mode. + + - Para usar o console de gerenciamento, consulte "[Habilitar e programar o modo de manutenção](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)"; + + - Você também pode usar o comando `ghe-maintenance -s`. + ```shell + $ ghe-maintenance -s + ``` + + - Quando o número de operações ativas do Git, consultas MySQL e tarefas do Resque alcançam zero, aguarde 30 segundos. + + {% note %} + + **Observação:** O Nomad sempre terá trabalhos em execução, mesmo no modo de manutenção. Portanto, você pode ignorar esses trabalhos com segurança. + + {% endnote %} + + - Para verificar todos os canais de replicação que reportarem `OK`, use o comando `ghe-repl-status -vv`. + ```shell - $ ghe-maintenance -s + $ ghe-repl-status -vv ``` -2. Quando o número de operações ativas do Git, consultas MySQL e tarefas do Resque alcançam zero, aguarde 30 segundos. - {% note %} - - **Observação:** O Nomad sempre terá trabalhos em execução, mesmo no modo de manutenção. Portanto, você pode ignorar esses trabalhos com segurança. - - {% endnote %} - -3. Para verificar todos os canais de replicação que reportarem `OK`, use o comando `ghe-repl-status -vv`. - ```shell - $ ghe-repl-status -vv - ``` -4. Para parar a replicação e promover o appliance réplica ao status de primário, use o comando `ghe-repl-promote`. A ação também colocará automaticamente o nó primário no nó de manutenção, se ele for acessível. +4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. A ação também colocará automaticamente o nó primário no nó de manutenção, se ele for acessível. ```shell $ ghe-repl-promote ``` diff --git a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md index 7107f53840..5df8a8e937 100644 --- a/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md +++ b/translations/pt-BR/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises.md @@ -33,7 +33,7 @@ topics: {% data variables.product.prodname_actions %} ajuda a sua equipe a trabalhar mais rápido e em escala. Quando grandes repositórios começam a usar o {% data variables.product.prodname_actions %}, as equipes fazem merge de um número significativamente maior de pull requests por dia, e os pull requests são mesclados muito mais rapidamente. Para obter mais informações, consulte "[Gravação e envio mais rápido de código](https://octoverse.github.com/writing-code-faster/#scale-through-automation)" no estado do Octoverse. -Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. {% ifversion ghec %}For more information, see "[Finding and customizing actions](/actions/learn-github-actions/finding-and-customizing-actions)."{% else %}You can restrict your developers to using actions that exist on {% data variables.product.product_location %}, or you can allow your developers to access actions on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[About using actions in your enterprise](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)."{% endif %} +Você pode criar suas próprias automações exclusivas ou você pode usar e adaptar os fluxos de trabalho do nosso ecossistema de mais de 10, 00 ações construídas por líderes do setor e pela comunidade de código aberto. {% ifversion ghec %}Para obter mais informações, consulte "[Encontrando e personalizando ações](/actions/learn-github-actions/finding-and-customizing-actions).{% else %}Você pode restringir seus desenvolvedores a usar ações que existem no {% data variables.product.product_location %} ou você pode permitir que seus desenvolvedores acessem ações em {% data variables.product.prodname_dotcom_the_website %}. Para obter mais informações, consulte "[Sobre o uso de ações na sua empresa](/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise)".{% endif %} {% data variables.product.prodname_actions %} é intuitivo para o desenvolvedor, pois está integrado diretamente à experiência familiar de {% data variables.product.product_name %}. diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md index 5deb482159..1c1b8d6783 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/about-using-actions-in-your-enterprise.md @@ -13,7 +13,7 @@ type: overview topics: - Actions - Enterprise -shortTitle: About actions in your enterprise +shortTitle: Sobre ações na sua empresa --- {% data reusables.actions.enterprise-beta %} @@ -23,24 +23,24 @@ shortTitle: About actions in your enterprise Os fluxos de trabalho de {% data variables.product.prodname_actions %} podem usar _ações_, que são tarefas individuais que você pode combinar para criar tarefas e personalizar seu fluxo de trabalho. Você pode criar suas próprias ações ou usar e personalizar ações compartilhadas pela comunidade {% data variables.product.prodname_dotcom %}. -{% data reusables.actions.enterprise-no-internet-actions %} You can restrict your developers to using actions that are stored on {% data variables.product.product_location %}, which includes most official {% data variables.product.company_short %}-authored actions, as well as any actions your developers create. Alternatively, to allow your developers to benefit from the full ecosystem of actions built by industry leaders and the open source community, you can configure access to other actions from {% data variables.product.prodname_dotcom_the_website %}. +{% data reusables.actions.enterprise-no-internet-actions %} Você pode restringir seus desenvolvedores a usar ações que são armazenadas em {% data variables.product.product_location %}, o que inclui a maioria das ações oficiais de criadas por {% data variables.product.company_short %}, bem como quaisquer ações que seus desenvolvedores criarem. Como alternativa, para permitir que seus desenvolvedores se beneficiem de todo o ecossistema de ações criadas pelos líderes do setor e pela comunidade de código aberto você pode configurar o acesso a outras ações a partir de {% data variables.product.prodname_dotcom_the_website %}. -We recommend allowing automatic access to all actions from {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}However, this does require {% data variables.product.product_name %} to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. If you don't want to allow these connections, or{% else %}If{% endif %} you want to have greater control over which actions are used on your enterprise, you can manually sync specific actions from {% data variables.product.prodname_dotcom_the_website %}. +Recomendamos permitir acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes %}No entanto, isso exige que {% data variables.product.product_name %} faça conexões de saída para {% data variables.product.prodname_dotcom_the_website %}. Se você não quiser permitir essas conexões ou{% else %}Se{% endif %} se você quiser ter maior controle sobre quais ações são usadas em sua empresa, você pode sincronizar manualmente ações específicas de {% data variables.product.prodname_dotcom_the_website %}. ## Ações oficiais agrupadas com a sua instância corporativa {% data reusables.actions.actions-bundled-with-ghes %} -The bundled official actions include the following, among others. +As acções oficiais agrupadas incluem, entre outras, as listadas a seguir. - `actions/checkout` - `actions/upload-artifact` - `actions/download-artifact` - `actions/labeler` -- Various `actions/setup-` actions +- Diversas ações de `actions/setup-` Para ver todas as ações oficiais incluídas na instância da sua empresa, acesse a organização das `ações` na sua instância: https://HOSTNAME/actions. -There is no connection required between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %} to use these actions. +Não há conexão necessária entre {% data variables.product.product_location %} e {% data variables.product.prodname_dotcom_the_website %} para usar essas ações. Cada ação é um repositório na organização de `ações`, e cada repositório de ação inclui as tags necessárias, branches e commit de SHAs que seus fluxos de trabalho podem usar para fazer referência à ação. Para obter informações sobre como atualizar as ações oficiais empacotadas, consulte "[Usar a versão mais recente das ações oficiais empacotadas](/admin/github-actions/using-the-latest-version-of-the-official-bundled-actions)". @@ -61,7 +61,7 @@ A abordagem recomendada é habilitar o acesso automático para todas as ações {% ifversion ghes %} {% note %} -**Note:** Before you can configure access to actions on {% data variables.product.prodname_dotcom_the_website %}, you must configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." +**Oservação:** Antes que você possa configurar o acesso a ações em {% data variables.product.prodname_dotcom_the_website %}, você deve configurar {% data variables.product.product_location %} para usar {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Primeiros passos com {% data variables.product.prodname_actions %} para o GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)." {% endnote %} @@ -71,4 +71,4 @@ A abordagem recomendada é habilitar o acesso automático para todas as ações {% data reusables.actions.enterprise-limit-actions-use %} -Alternatively, if you want stricter control over which actions are allowed in your enterprise, or you do not want to allow outbound connections to {% data variables.product.prodname_dotcom_the_website %}, you can manually download and sync actions onto your enterprise instance using the `actions-sync` tool. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". +Como alternativa, se você quiser um controle mais rigoroso sobre quais as ações são permitidas na sua empresa, ou você não deseja permitir conexões de saída para {% data variables.product.prodname_dotcom_the_website %}, você pode fazer o download e sincronizar manualmente ações para a instância corporativa usando a ferramenta `actions-sync`. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". diff --git a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md index 9ce209f06d..b75787043a 100644 --- a/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md +++ b/translations/pt-BR/content/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect.md @@ -27,11 +27,11 @@ Por padrão, os fluxos de trabalho {% data variables.product.prodname_actions %} Como alternativa, se você quiser ter um controle mais rigoroso sobre quais as ações que são permitidas na sua empresa, você pode fazer o download e sincronizar manualmente as ações na instância da sua empresa usando a ferramenta de `actions-sync`. Para obter mais informações, consulte "[Sincronizando ações manualmente com o {% data variables.product.prodname_dotcom_the_website %}](/enterprise/admin/github-actions/manually-syncing-actions-from-githubcom)". -## About resolution for actions using {% data variables.product.prodname_github_connect %} +## Sobre resolução para ações usando {% data variables.product.prodname_github_connect %} {% data reusables.actions.github-connect-resolution %} -If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghes < 3.3 or ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)." +Se um usuário tiver criado uma organização e um repositório em sua empresa, que corresponde a uma organização e nome do repositório em {% data variables.product.prodname_dotcom_the_website %}, o repositório da sua empresa será usado em vez do repositório de {% data variables.product.prodname_dotcom_the_website %}. {% ifversion ghes < 3.3 or ghae %}Um usuário malicioso poderia aproveitar esse comportamento para executar o código como parte de um fluxo de trabalho{% else %}Para obter mais informações, consulte "[Desativação automática de namespaces para ações acessadas em {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)". {% endif %} ## Habilitar o acesso automático a todas as ações de {% data variables.product.prodname_dotcom_the_website %} diff --git a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index d58f1fd37e..a285a8c6df 100644 --- a/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/pt-BR/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -25,7 +25,7 @@ Você pode fazer três tipos de migração: Durante uma migração, tudo gira em torno do repositório. A maioria dos dados associados ao repositório pode ser migrada. Por exemplo, um repositório dentro de uma organização migrará o repositório *e* a organização, além dos usuários, equipes, problemas e pull requests associados ao repositório. -Os itens na tabela abaixo podem ser migrados com um repositório. Não é possível migrar os itens que não constam na lista. +Os itens na tabela abaixo podem ser migrados com um repositório. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} diff --git a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index 1f221de627..b13485f5c3 100644 --- a/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/pt-BR/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -25,7 +25,7 @@ shortTitle: Verificar se há chave SSH existente # Lists the files in your .ssh directory, if they exist ``` -3. Verifique a listagem do diretório para verificar se você já tem uma chave SSH pública. Por padrão, o nome de arquivo {% ifversion ghae %} de uma chave pública compatível com {% data variables.product.product_name %} é *id_rsa.pub*.{% elsif fpt or ghes %}nomes de arquivos de chaves públicas compatíveis com {% data variables.product.product_name %} são um dos listados a seguir. +3. Verifique a listagem do diretório para verificar se você já tem uma chave SSH pública. Por padrão, o nome de arquivo {% ifversion ghae %} de uma chave pública compatível com {% data variables.product.product_name %} é *id_rsa.pub*.{% else %}nomes de arquivos de chaves públicas compatíveis com {% data variables.product.product_name %} são um dos listados a seguir. - *id_rsa.pub* - *id_ecdsa.pub* - *id_ed25519.pub*{% endif %} diff --git a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 492e72e225..4c75b7f042 100644 --- a/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/pt-BR/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -33,7 +33,7 @@ Se deu certo, ótimo! Caso contrário, [siga nosso guia para solução de proble Se você conseguir fazer SSH para `git@ssh.{% data variables.command_line.backticks %}` por meio da porta 443, você poderá substituir as configurações SSH para forçar qualquer conexão ao {% data variables.product.product_location %} a ser executada nesse servidor e nessa porta. -Para definir isso no seu arquivo de configuração do SSH, edite o arquivo em `~/.ssh/config` e adicione esta seção: +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} diff --git a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md index 0e85203a99..e7c8cf69d3 100644 --- a/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md +++ b/translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md @@ -121,7 +121,7 @@ Você pode pesquisar na lista de alertas. Isso é útil se houver um grande núm **Dicas:** - A busca múltipla de palavras é equivalente a uma busca OU. -- The AND search will return results where the search terms are found _anywhere_, in any order in the alert name or details. +- A pesquisa E retornará resultados em que os termos da pesquisa são encontrados _em qualquer lugar_, em qualquer ordem no nome ou informações do alerta. {% endtip %} @@ -150,7 +150,7 @@ Se você tem permissão de escrita em um repositório, você pode visualizar ale Você pode usar{% ifversion fpt or ghes > 3.1 or ghae or ghec %} a pesquisa de texto livre ou{% endif %} os filtros para exibir um subconjunto de alertas e, em seguida, marcar, por sua vez, todos os alertas correspondentes como fechados. -Alertas podem ser corrigidos em um branch, mas não em outro. You can use the "Branch" filter, on the summary of alerts, to check whether an alert is fixed in a particular branch. +Alertas podem ser corrigidos em um branch, mas não em outro. Você pode usar o filtro "Branch", no resumo dos alertas, para verificar se um alerta é corrigido em um branch específico. {% ifversion fpt or ghes > 3.1 or ghae or ghec %} ![Filtrar alertas por branch](/assets/images/help/repository/code-scanning-branch-filter.png) diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md index 95506700a3..23b4e8f7f1 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/about-dependabot-alerts.md @@ -1,5 +1,5 @@ --- -title: About Dependabot alerts +title: Sobre alertas do Dependabot intro: 'O {% data variables.product.product_name %} envia {% data variables.product.prodname_dependabot_alerts %} quando detectamos vulnerabilidades que afetam o seu repositório.' redirect_from: - /articles/about-security-alerts-for-vulnerable-dependencies @@ -83,7 +83,7 @@ Para repositórios em que {% data variables.product.prodname_dependabot_security ## Acesso a {% data variables.product.prodname_dependabot_alerts %} -É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." +É possível ver todos os alertas que afetam um determinado projeto{% ifversion fpt or ghec %} na aba Segurança do repositório ou{% endif %} no gráfico de dependências do repositório. Para obter mais informações, consulte "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." Por padrão, notificamos as pessoas com permissões de administrador nos repositórios afetados sobre os novos {% data variables.product.prodname_dependabot_alerts %}. {% ifversion fpt or ghec %}{% data variables.product.product_name %} nunca divulga publicamente vulnerabilidades identificadas para qualquer repositório. Você também pode tornar o {% data variables.product.prodname_dependabot_alerts %} visível para pessoas ou repositórios de trabalho de equipes adicionais que você possui ou para os quais tem permissões de administrador. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise do repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)". {% endif %} @@ -97,5 +97,5 @@ Você também pode ver todos os {% data variables.product.prodname_dependabot_al ## Leia mais - "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %} +- "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% endif %} {% ifversion fpt or ghec %}- "[Privacidade em {% data variables.product.prodname_dotcom %}](/get-started/privacy-on-github)"{% endif %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md index 3937bb774d..f00c6a0e32 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/browsing-security-vulnerabilities-in-the-github-advisory-database.md @@ -37,7 +37,7 @@ As consultorias revisadas por {% data variables.product.company_short %} são vu Analisamos cuidadosamente cada consultoria com relação à sua validade. Cada consultoria revisada por {% data variables.product.company_short %} tem uma descrição completa e contém informações de pacote e ecossistema. -Se você habilitar {% data variables.product.prodname_dependabot_alerts %} para os seus repositórios, você será notificado automaticamente quando uma nova consultoria revisada por {% data variables.product.company_short %} afetar pacotes dos quais você depende. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +Se você habilitar {% data variables.product.prodname_dependabot_alerts %} para os seus repositórios, você será notificado automaticamente quando uma nova consultoria revisada por {% data variables.product.company_short %} afetar pacotes dos quais você depende. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". ### Sobre consultorias não revisadas diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md index 3e24decd97..f2b4d4e400 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/configuring-notifications-for-dependabot-alerts.md @@ -1,6 +1,6 @@ --- -title: Configuring notifications for Dependabot alerts -shortTitle: Configure notifications +title: Configurando notificações para alertas do Dependabot +shortTitle: Configurar notificações intro: 'Otimize a forma como você recebe notificações sobre {% data variables.product.prodname_dependabot_alerts %}.' redirect_from: - /github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies @@ -60,7 +60,7 @@ Você pode definir as configurações de notificação para si mesmo ou para sua ## Como reduzir o ruído das notificações para dependências vulneráveis -Se você estiver preocupado em receber muitas notificações para {% data variables.product.prodname_dependabot_alerts %}, recomendamos que você opte pelo resumo semanal de e-mail ou desabilite as notificações enquanto mantém {% data variables.product.prodname_dependabot_alerts %} habilitado. Você ainda pode navegar para ver seu {% data variables.product.prodname_dependabot_alerts %} na aba Segurança do seu repositório. For more information, see "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." +Se você estiver preocupado em receber muitas notificações para {% data variables.product.prodname_dependabot_alerts %}, recomendamos que você opte pelo resumo semanal de e-mail ou desabilite as notificações enquanto mantém {% data variables.product.prodname_dependabot_alerts %} habilitado. Você ainda pode navegar para ver seu {% data variables.product.prodname_dependabot_alerts %} na aba Segurança do seu repositório. Para obter mais informações, consulte "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)." ## Leia mais diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md index 6cf2febdbf..2f23241ca5 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/index.md @@ -1,7 +1,7 @@ --- -title: Identifying vulnerabilities in your project's dependencies with Dependabot alerts +title: Identificando vulnerabilidades nas dependências do seu projeto com alertas do Dependabot shortTitle: Alertas do Dependabot -intro: '{% data variables.product.prodname_dependabot %} generates {% data variables.product.prodname_dependabot_alerts %} when known vulnerabilites are detected in dependencies that your project uses.' +intro: '{% data variables.product.prodname_dependabot %} gera {% data variables.product.prodname_dependabot_alerts %} quando as vulnerabilidades conhecidas são detectadas em dependências que o seu projeto usa.' allowTitleToDifferFromFilename: true versions: fpt: '*' diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md index ed46ed10ed..73864b1320 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-alerts/viewing-and-updating-dependabot-alerts.md @@ -1,5 +1,5 @@ --- -title: Viewing and updating Dependabot alerts +title: Visualizando e atualizando alertas do Dependabot intro: 'Se o {% data variables.product.product_name %} descobrir dependências vulneráveis no seu projeto, você poderá visualizá-las na aba de alertas do Dependabot no seu repositório. Em seguida, você pode atualizar seu projeto para resolver ou descartar a vulnerabilidade.' redirect_from: - /articles/viewing-and-updating-vulnerable-dependencies-in-your-repository @@ -7,7 +7,7 @@ redirect_from: - /code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository - /code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/viewing-and-updating-vulnerable-dependencies-in-your-repository permissions: Repository administrators and organization owners can view and update dependencies. -shortTitle: View Dependabot alerts +shortTitle: Ver alertas do Dependabot versions: fpt: '*' ghes: '*' @@ -26,7 +26,7 @@ topics: {% data reusables.dependabot.beta-security-and-version-updates %} {% data reusables.dependabot.enterprise-enable-dependabot %} -A aba de {% data variables.product.prodname_dependabot_alerts %} do seu repositório lista todos os {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} abertos e fechados correspondentes a {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Você pode{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filtrar alertas por pacote, ecossistema ou manifesto. Você também pode{% endif %} ordernar a lista de alertas, além de poder clicar em alertas específicos para mais detalhes. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +A aba de {% data variables.product.prodname_dependabot_alerts %} do seu repositório lista todos os {% data variables.product.prodname_dependabot_alerts %}{% ifversion fpt or ghec or ghes > 3.2 %} abertos e fechados correspondentes a {% data variables.product.prodname_dependabot_security_updates %}{% endif %}. Você pode{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-5638 %} filtrar alertas por pacote, ecossistema ou manifesto. Você também pode{% endif %} ordernar a lista de alertas, além de poder clicar em alertas específicos para mais detalhes. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". {% ifversion fpt or ghec or ghes > 3.2 %} É possível habilitar atualizações de segurança automáticas para qualquer repositório que usa o {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)." @@ -99,7 +99,7 @@ Cada alerta de {% data variables.product.prodname_dependabot %} tem um identific ## Leia mais -- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)"{% endif %} - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" - "[Solução de problemas na detecção de dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/troubleshooting-the-detection-of-vulnerable-dependencies)"{% ifversion fpt or ghec or ghes > 3.2 %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md index 3c0fb8b5df..965fd7c827 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates.md @@ -71,12 +71,12 @@ O {% data variables.product.prodname_dependabot_security_updates %} exige config {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.repositories.navigate-to-security-and-analysis %} -1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %} +1. Em "Segurança e análise de código", à direita de "atualizações de segurança de {% data variables.product.prodname_dependabot %}", clique em **Habilitar** para habilitar o recurso ou **Desabilitar** para desabilitá-lo. {% ifversion fpt or ghec %}Para repositórios públicos, o botão fica desabilitado se o recurso estiver sempre habilitado.{% endif %} {% ifversion fpt or ghec %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/help/repository/enable-dependabot-security-updates-button.png){% else %}!["Code security and analysis" section with button to enable {% data variables.product.prodname_dependabot_security_updates %}](/assets/images/enterprise/3.3/repository/security-and-analysis-disable-or-enable-ghes.png){% endif %} ## Leia mais -- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec %} +- "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"{% ifversion fpt or ghec %} - "[Gerenciando configurações de uso de dados para o seu repositório privado](/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository)"{% endif %} - "[Ecossistemas de pacotes compatíveis](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems)" diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/index.md index 059029a0d5..357aa2ce8c 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/index.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-security-updates/index.md @@ -1,6 +1,6 @@ --- -title: Automatically updating dependencies with known vulnerabilities with Dependabot security updates -intro: '{% data variables.product.prodname_dependabot %} can help you fix vulnerable dependencies by automatically raising pull requests to update dependencies to secure versions.' +title: Atualizar dependências automaticamente com vulnerabilidades conhecidas com atualizações de segurança do Dependabot +intro: '{% data variables.product.prodname_dependabot %} pode ajudar você a corrigir dependências vulneráveis criando automaticamente pull requests para atualizar dependências para versões seguras.' allowTitleToDifferFromFilename: true versions: fpt: '*' diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md index 1dc65fa444..d02ca901ba 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates.md @@ -32,7 +32,7 @@ O {% data variables.product.prodname_dependabot %} facilita a manutenção de su Você habilita o {% data variables.product.prodname_dependabot_version_updates %} verificando um arquivo de configuração no seu repositório. O arquivo de configuração especifica a localização do manifesto ou de outros arquivos de definição de pacote, armazenados no seu repositório. O {% data variables.product.prodname_dependabot %} usa essas informações para verificar pacotes e aplicativos desatualizados. {% data variables.product.prodname_dependabot %} determina se há uma nova versão de uma dependência observando a versão semântica ([semver](https://semver.org/)) da dependência para decidir se deve atualizar para essa versão. Para certos gerentes de pacote, {% data variables.product.prodname_dependabot_version_updates %} também é compatível com armazenamento. Dependências de vendor (ou armazenadas) são dependências registradas em um diretório específico em um repositório, em vez de referenciadas em um manifesto. Dependências de vendor estão disponíveis no tempo de criação, ainda que os servidores de pacote estejam indisponíveis. {% data variables.product.prodname_dependabot_version_updates %} pode ser configurado para verificar as dependências de vendor para novas versões e atualizá-las, se necessário. -Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +Quando {% data variables.product.prodname_dependabot %} identifica uma dependência desatualizada, ele cria uma pull request para atualizar o manifesto para a última versão da dependência. Para dependências de vendor, {% data variables.product.prodname_dependabot %} levanta um pull request para substituir diretamente a dependência desatualizada pela nova versão. Você verifica se os seus testes passam, revisa o changelog e lança observações incluídas no resumo do pull request e, em seguida, faz a mesclagem. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". Se você habilitar _Atualizações de segurança_, {% data variables.product.prodname_dependabot %} também eleva pull requests para atualizar dependências vulneráveis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." @@ -51,7 +51,7 @@ Se tiver habilitado atualizações de segurança, às vezes você verá atualiza ## Repositórios e ecossistemas suportados -É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados. Para alguns gerenciadores de pacotes, você também pode configurar o armazenamento para dependências. For more information, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#vendor)." +É possível configurar atualizações de versão para repositórios que contenham um manifesto de dependência ou arquivo de bloqueio para um dos gerentes de pacotes suportados. Para alguns gerenciadores de pacotes, você também pode configurar o armazenamento para dependências. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#vendor)". {% note %} {% data reusables.dependabot.private-dependencies-note %} diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index 0f93f44637..a561859e55 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -1,5 +1,5 @@ --- -title: Configuration options for the dependabot.yml file +title: Opções de configuração para o arquivo dependabot.yml intro: 'Informações detalhadas para todas as opções que você pode usar para personalizar como o {% data variables.product.prodname_dependabot %} mantém seus repositórios.' permissions: 'People with write permissions to a repository can configure {% data variables.product.prodname_dependabot %} for the repository.' allowTitleToDifferFromFilename: true @@ -19,7 +19,7 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Configure dependabot.yml +shortTitle: Configurar dependabot.yml --- {% data reusables.dependabot.beta-security-and-version-updates %} @@ -29,7 +29,7 @@ shortTitle: Configure dependabot.yml O arquivo de configuração do {% data variables.product.prodname_dependabot %} , *dependabot.yml*, usa a sintaxe YAML. Se você não souber o que é YAMLe quiser saber mais, consulte "[Aprender a usar YAML em cinco minutos](https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes)". -Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. For more information and an example, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)." +Você deve armazenar este arquivo no diretório `.github` do seu repositório. Ao adicionar ou atualizar o arquivo *dependabot.yml* , isso aciona uma verificação imediata de atualizações de versão. Para obter mais informações e um exemplo, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-dependabot-version-updates)". Quaisquer opções que também afetem as atualizações de segurança são usadas na próxima vez que um alerta de segurança acionar um pull request para uma atualização de segurança. Para obter mais informações, consulte "[Configurando {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)." diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md index 4700dec98a..6f58c413eb 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates.md @@ -1,5 +1,5 @@ --- -title: Configuring Dependabot version updates +title: Configurando a versão das atualizações do Dependabot intro: 'Você pode configurar seu repositório para que o {% data variables.product.prodname_dependabot %} atualize automaticamente os pacotes que você usa.' permissions: 'People with write permissions to a repository can enable or disable {% data variables.product.prodname_dependabot_version_updates %} for the repository.' redirect_from: @@ -18,7 +18,7 @@ topics: - Repositories - Dependencies - Pull requests -shortTitle: Configure version updates +shortTitle: Configurar atualizações da versão --- @@ -35,7 +35,7 @@ Você habilita {% data variables.product.prodname_dependabot_version_updates %}, ## Habilitar {% data variables.product.prodname_dependabot_version_updates %} -{% data reusables.dependabot.create-dependabot-yml %} For information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)." +{% data reusables.dependabot.create-dependabot-yml %} Para obter informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates)". 1. Adicione uma `versão`. 1. Opcionalmente, se você tiver dependências em um registro privado, adicione uma seção de `registros` que contém detalhes de autenticação. 1. Adicione uma seção de `atualizações` com uma entrada para cada gerenciador de pacotes que você deseja que {% data variables.product.prodname_dependabot %} monitore. @@ -139,4 +139,4 @@ updates: update-types: ["version-update:semver-patch"] ``` -For more information about checking for existing ignore preferences, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)." +Para obter mais informações sobre a verificação de preferências de ignorados existentes, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md index 833ac4f45d..085fc10df9 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/customizing-dependency-updates.md @@ -35,7 +35,7 @@ Depois que você habilitou as atualizações de versão, você pode personalizar - Alterar o número máximo de pull requests abertos para atualizações de versão a partir do padrão de 5: `open-pull-requests-limit` - Abrir pull requests para atualizações de versão para atingir um branch específico, em vez do branch padrão: `target-branch` -For more information about the configuration options, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." +Para obter mais informações sobre as opções de configuração, consulte "[Opções de configuração para o arquivo dependabot.yml](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)". Ao atualizar o arquivo *dependabot.yml* no seu repositório, o {% data variables.product.prodname_dependabot %} executa uma verificação imediata com a nova configuração. Dentro de minutos você verá uma lista atualizada de dependências na aba **{% data variables.product.prodname_dependabot %}**. Isso pode demorar mais se o repositório tiver muitas dependências. Você também pode ver novas pull requests para atualizações de versão. Para obter mais informações, consulte "[Listando dependências configuradas para atualizações da versão](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/listing-dependencies-configured-for-version-updates)". @@ -141,4 +141,4 @@ updates: ## Mais exemplos -For more examples, see "[Configuration options for the dependabot.yml file](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates)." +Para obter mais exemplos, consulte "[Opções de configuração para o arquivo dependabot.yml](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates). ". diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/index.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/index.md index d6014060b7..054c2a79d0 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/index.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/index.md @@ -1,6 +1,6 @@ --- -title: Keeping your dependencies updated automatically with Dependabot version updates -intro: 'You can use {% data variables.product.prodname_dependabot %} to automatically keep the dependencies and packages used in your repository updated to the latest version, even when they don’t have any known vulnerabilities.' +title: Manter suas dependências atualizadas automaticamente com as atualizações da versão do Dependabot +intro: 'Você pode usar o {% data variables.product.prodname_dependabot %} para manter automaticamente as dependências e pacotes usados no repositório atualizados para a última versão mesmo quando não eles têm nenhuma vulnerabilidade conhecida.' allowTitleToDifferFromFilename: true redirect_from: - /github/administering-a-repository/keeping-your-dependencies-updated-automatically diff --git a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md index bfd5f66530..9c66ed3ed3 100644 --- a/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/dependabot-version-updates/listing-dependencies-configured-for-version-updates.md @@ -23,7 +23,7 @@ shortTitle: Listar dependências configuradas ## Visualizando dependências monitoradas por {% data variables.product.prodname_dependabot %} -Depois de habilitar as atualizações de versão, você pode confirmar que a sua configuração está correta usando a aba **{% data variables.product.prodname_dependabot %}** no gráfico de dependências para o repositório. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +Depois de habilitar as atualizações de versão, você pode confirmar que a sua configuração está correta usando a aba **{% data variables.product.prodname_dependabot %}** no gráfico de dependências para o repositório. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". {% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.accessing-repository-graphs %} diff --git a/translations/pt-BR/content/code-security/dependabot/index.md b/translations/pt-BR/content/code-security/dependabot/index.md index cb1f4984f9..e080f0eaef 100644 --- a/translations/pt-BR/content/code-security/dependabot/index.md +++ b/translations/pt-BR/content/code-security/dependabot/index.md @@ -1,7 +1,7 @@ --- -title: Keeping your supply chain secure with Dependabot +title: Mantendo sua cadeia de suprimentos em segurança com o Dependabot shortTitle: Dependabot -intro: 'Monitor vulnerabilities in dependencies used in your project{% ifversion fpt or ghec or ghes > 3.2 %} and keep your dependencies up-to-date{% endif %} with {% data variables.product.prodname_dependabot %}.' +intro: 'Monitore as vulnerabilidades em dependências usadas no seu projeto{% ifversion fpt or ghec or ghes > 3.2 %} e mantenha suas dependências atualizadas{% endif %} com {% data variables.product.prodname_dependabot %}.' allowTitleToDifferFromFilename: true versions: fpt: '*' diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/index.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/index.md index 2ff0dbc0da..2a58fe8eec 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/index.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/index.md @@ -1,7 +1,7 @@ --- -title: Working with Dependabot -shortTitle: Work with Dependabot -intro: 'Guidance and recommendations for working with {% data variables.product.prodname_dependabot %}, such as managing pull requests raised by {% data variables.product.prodname_dependabot %}, using {% data variables.product.prodname_actions %} with {% data variables.product.prodname_dependabot %}, and troubleshooting {% data variables.product.prodname_dependabot %} errors.' +title: Trabalhando com Dependabot +shortTitle: Trabalhe com Dependabot +intro: 'Orientação e recomendações para trabalhar com {% data variables.product.prodname_dependabot %}, como gerenciar pull requests levantados por {% data variables.product.prodname_dependabot %}, usando {% data variables.product.prodname_actions %} com {% data variables.product.prodname_dependabot %} e solucionando erros de {% data variables.product.prodname_dependabot %}.' versions: fpt: '*' ghec: '*' diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md index f4bda796b6..62ee9f59f4 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot.md @@ -37,7 +37,7 @@ Ações são frequentemente atualizadas com correções de bugs e novos recursos 1. Defina um `schedule.interval` para especificar quantas vezes procurar por novas versões. {% data reusables.dependabot.check-in-dependabot-yml %} Se você tiver editado um arquivo existente, salve suas alterações. -Você também pode habilitar o {% data variables.product.prodname_dependabot_version_updates %} em bifurcações. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)." +Você também pode habilitar o {% data variables.product.prodname_dependabot_version_updates %} em bifurcações. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates#enabling-version-updates-on-forks)". ### Exemplo de arquivo *dependabot.yml* para {% data variables.product.prodname_actions %} @@ -58,7 +58,7 @@ updates: ## Configurando o {% data variables.product.prodname_dependabot_version_updates %} para ações -Ao habilitar {% data variables.product.prodname_dependabot_version_updates %} para ações, você deve especificar valores para `package-ecosystem`, `directory` e `schedule.interval`. Há muitas propriedades opcionais adicionais que você pode definir para personalizar ainda mais suas atualizações de versão. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates)." +Ao habilitar {% data variables.product.prodname_dependabot_version_updates %} para ações, você deve especificar valores para `package-ecosystem`, `directory` e `schedule.interval`. Há muitas propriedades opcionais adicionais que você pode definir para personalizar ainda mais suas atualizações de versão. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates)". ## Leia mais diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md index f3765ffd50..fb6d696ef6 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-encrypted-secrets-for-dependabot.md @@ -34,7 +34,7 @@ password: ${{secrets.MY_ARTIFACTORY_PASSWORD}} ``` {% endraw %} -For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". ### Nomear os seus segredos diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md index dab90a241a..304da6b022 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/managing-pull-requests-for-dependency-updates.md @@ -42,7 +42,7 @@ Se você tem muitas dependências para gerenciar, você pode querer personalizar ## Alterando a estratégia de rebase para pull requests {% data variables.product.prodname_dependabot %} -Por padrão, o {% data variables.product.prodname_dependabot %} faz o rebasamento automaticamente das pull requests para resolver quaisquer conflitos. Se você preferir lidar com conflitos de merge manualmente, pode desativar isso usando a opção `rebase-strategy`. For details, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy)." +Por padrão, o {% data variables.product.prodname_dependabot %} faz o rebasamento automaticamente das pull requests para resolver quaisquer conflitos. Se você preferir lidar com conflitos de merge manualmente, pode desativar isso usando a opção `rebase-strategy`. Para obter detalhes, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#rebase-strategy). ". ## Gerenciando pull requests {% data variables.product.prodname_dependabot %} com comandos de comentário @@ -63,4 +63,4 @@ Você pode usar qualquer um dos seguintes comandos em um pull request de {% data {% data variables.product.prodname_dependabot %} reagirá com um emoji "positivo" para reconhecer o comando e pode responder com um comentário no pull request. Embora {% data variables.product.prodname_dependabot %} normalmente responda rapidamente, alguns comandos podem levar vários minutos para serem concluídos se {% data variables.product.prodname_dependabot %} estiver ocupado processando outras atualizações ou comandos. -Se você executar algum comando para ignorar dependências ou versões, o {% data variables.product.prodname_dependabot %} armazena centralmente as preferências para o repositório. Embora esta seja uma solução rápida, para repositórios com mais de um colaborador é melhor definir explicitamente as dependências e versões para ignorar no arquivo de configuração. Isso facilita que todos os colaboradores vejam por que uma determinada dependência não está sendo atualizada automaticamente. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)." +Se você executar algum comando para ignorar dependências ou versões, o {% data variables.product.prodname_dependabot %} armazena centralmente as preferências para o repositório. Embora esta seja uma solução rápida, para repositórios com mais de um colaborador é melhor definir explicitamente as dependências e versões para ignorar no arquivo de configuração. Isso facilita que todos os colaboradores vejam por que uma determinada dependência não está sendo atualizada automaticamente. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#ignore)". diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md index 93305cd5ad..20b20c325c 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-dependabot-errors.md @@ -77,7 +77,7 @@ Pull requests para atualizações de segurança atuam para atualizar uma depend Cada aplicativo com dependências tem um gráfico de dependências, ou seja, um gráfico direcionado acíclico de cada versão de pacote da qual o aplicativo depende direta ou indiretamente. Toda vez que uma dependência é atualizada, este gráfico deve ser resolvido. Caso contrário, o aplicativo não será criado. Quando um ecossistema tem um gráfico de dependência profundo e complexo, por exemplo, npm e RubyGems, geralmente é impossível atualizar uma única dependência sem atualizar todo o ecossistema. -A melhor maneira de evitar esse problema é manter-se atualizado com as versões mais recentes, habilitando, por exemplo, as atualizações de versões. Isso aumenta a probabilidade de que uma vulnerabilidade em uma dependência possa ser resolvida por meio de uma atualização simples que não afete o gráfico de dependência. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +A melhor maneira de evitar esse problema é manter-se atualizado com as versões mais recentes, habilitando, por exemplo, as atualizações de versões. Isso aumenta a probabilidade de que uma vulnerabilidade em uma dependência possa ser resolvida por meio de uma atualização simples que não afete o gráfico de dependência. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". ### {% data variables.product.prodname_dependabot %} não consegue atualizar para a versão necessária, pois já existe um pull request aberto para a última versão @@ -91,13 +91,13 @@ Existem duas opções: você pode revisar o pull request aberto e fazer o merge Este erro é difícil de ser corrigido. Se a atualização de uma versão expirar, você poderá especificar as dependências mais importantes para atualizar usando o parâmetro `permitir` ou, como alternativa, você pode usar o parâmetro `ignorar` para excluir algumas dependências de atualizações. Atualizar sua configuração pode permitir que {% data variables.product.prodname_dependabot %} revise a atualização da versão e gere o pull request no tempo disponível. -Se uma atualização de segurança expirar, você pode reduzir as chances de isso acontecer mantendo as dependências atualizadas, por exemplo, habilitando atualizações de versão. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +Se uma atualização de segurança expirar, você pode reduzir as chances de isso acontecer mantendo as dependências atualizadas, por exemplo, habilitando atualizações de versão. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". ### {% data variables.product.prodname_dependabot %} não consegue abrir mais nenhum pull request Há um limite no número de pull requests abertos que {% data variables.product.prodname_dependabot %} irá gerar. Quando este limite é atingido, nenhum pull request novo será aberto e este erro será relatado. A melhor maneira de resolver este erro é revisar e fazer merge alguns dos pull requests abertos. -Existem limites separados para solicitações de atualização de versões e segurança, para que os pull requests de atualização de versão aberta não possam bloquear a criação de uma solicitação de atualização de segurança. O limite para pull requests de atualização de segurança é 10. Por padrão, o limite para atualizações de versão é 5, mas você pode alterá-lo usando o parâmetro `open-pull-requests-limit` no arquivo de configuração. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)." +Existem limites separados para solicitações de atualização de versões e segurança, para que os pull requests de atualização de versão aberta não possam bloquear a criação de uma solicitação de atualização de segurança. O limite para pull requests de atualização de segurança é 10. Por padrão, o limite para atualizações de versão é 5, mas você pode alterá-lo usando o parâmetro `open-pull-requests-limit` no arquivo de configuração. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#open-pull-requests-limit)". A melhor maneira de resolver este erro é fazer o merge ou fechar alguns dos pull requests existentes e acionar um novo pull request manualmente. Para obter mais informações, consulte "[Acionar um pull request de {% data variables.product.prodname_dependabot %} manualmente](#triggering-a-dependabot-pull-request-manually)". @@ -125,5 +125,5 @@ Se você desbloquear {% data variables.product.prodname_dependabot %}, você pod ## Leia mais -- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)" +- "[Solucionando problemas do gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)" - "[Solução de problemas na detecção de dependências vulneráveis](/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md index af332a25e3..d9dc0f05af 100644 --- a/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md +++ b/translations/pt-BR/content/code-security/dependabot/working-with-dependabot/troubleshooting-the-detection-of-vulnerable-dependencies.md @@ -1,7 +1,7 @@ --- title: Solução de problemas de detecção de dependências vulneráveis intro: 'Se as informações sobre dependências relatadas por {% data variables.product.product_name %} não são o que você esperava, há uma série de pontos a considerar, e várias coisas que você pode verificar.' -shortTitle: Troubleshoot vulnerability detection +shortTitle: Solução de problemas de vulnerabilidade redirect_from: - /github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies - /code-security/supply-chain-security/troubleshooting-the-detection-of-vulnerable-dependencies @@ -32,13 +32,13 @@ topics: O {% data variables.product.prodname_dotcom %} gera e exibe dados de dependência de maneira diferente de outras ferramentas. Consequentemente, se você usou outra ferramenta para identificar dependências, quase certamente verá resultados diferentes. Considere o seguinte: * {% data variables.product.prodname_advisory_database %} é uma das fontes de dados que {% data variables.product.prodname_dotcom %} usa para identificar dependências vulneráveis. É um banco de dados gratuito e curado com informações sobre vulnerabilidade para ecossistemas de pacote comum em {% data variables.product.prodname_dotcom %}. Inclui tanto dados relatados diretamente para {% data variables.product.prodname_dotcom %} de {% data variables.product.prodname_security_advisories %} quanto os feeds oficiais e as fontes comunitárias. Estes dados são revisados e curados por {% data variables.product.prodname_dotcom %} para garantir que informações falsas ou não acionáveis não sejam compartilhadas com a comunidade de desenvolvimento. {% data reusables.security-advisory.link-browsing-advisory-db %} -* O gráfico de dependências analisa todos os arquivos conhecidos de manifesto de pacote no repositório de um usuário. Por exemplo, para o npm, ele irá analisar o arquivo _package-lock.json_. Ele constrói um gráfico de todas as dependências do repositório e dependências públicas. Isso acontece quando você habilita o gráfico de dependências e quando alguém faz push para o branch-padrão, e inclui commits que fazem alterações em um formato de manifesto compatível. For more information, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)." -* {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} são agregados ao nível do repositório, em vez de criar um alerta por vulnerabilidade. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." +* O gráfico de dependências analisa todos os arquivos conhecidos de manifesto de pacote no repositório de um usuário. Por exemplo, para o npm, ele irá analisar o arquivo _package-lock.json_. Ele constrói um gráfico de todas as dependências do repositório e dependências públicas. Isso acontece quando você habilita o gráfico de dependências e quando alguém faz push para o branch-padrão, e inclui commits que fazem alterações em um formato de manifesto compatível. Para obter mais informações, consulte "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" e "[Solucionando problemas no gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)". +* {% data variables.product.prodname_dependabot %} verifica qualquer push, para o branch-padrão, que contém um arquivo de manifesto. Quando um novo registro de vulnerabilidade é adicionado, ele verifica todos os repositórios existentes e gera um alerta para cada repositório vulnerável. {% data variables.product.prodname_dependabot_alerts %} são agregados ao nível do repositório, em vez de criar um alerta por vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". * {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} são acionados quando você recebe um alerta sobre uma dependência vulnerável no repositório. Sempre que possível, {% data variables.product.prodname_dependabot %} cria um pull request no repositório para atualizar a dependência vulnerável à versão mínima segura necessária para evitar a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)" e "[Solução de problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)". {% endif %}{% data variables.product.prodname_dependabot %} não pesquisa repositórios com relação a dependências vulneráveis de uma programação, mas o faz quando algo muda. Por exemplo, aciona-se uma varredura quando uma nova dependência é adicionada ({% data variables.product.prodname_dotcom %} verifica isso em cada push), ou quando uma nova vulnerabilidade é adicionada ao banco de dados da consultoria{% ifversion ghes or ghae-issue-4864 %} e sincronizado com {% data variables.product.product_location %}{% endif %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)". -## Do {% data variables.product.prodname_dependabot_alerts %} only relate to vulnerable dependencies in manifests and lockfiles? +## {% data variables.product.prodname_dependabot_alerts %} só está relacionado a dependências vulneráveis nos manifestos e arquivos de bloqueio? Os {% data variables.product.prodname_dependabot_alerts %} aconselham você com relação a dependências que você deve atualizar, incluindo dependências transitivas, em que a versão pode ser determinada a partir de um manifesto ou de um arquivo de bloqueio. {% ifversion fpt or ghec or ghes > 3.2 %}{% data variables.product.prodname_dependabot_security_updates %} sugere apenas uma mudança em que {% data variables.product.prodname_dependabot %} pode "corrigir" diretamente a dependência, ou seja, quando são: * Dependências diretas, que são definidas explicitamente em um manifesto ou arquivo de bloqueio @@ -87,7 +87,7 @@ A contagem de {% data variables.product.prodname_dependabot_alerts %} em {% data ## Leia mais - "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" -- "[Troubleshooting the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} +- "[Solucionando problemas do gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph)"{% ifversion fpt or ghec or ghes > 3.2 %} - "[Solucionar problemas de {% data variables.product.prodname_dependabot %}](/github/managing-security-vulnerabilities/troubleshooting-dependabot-errors)"{% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/github-security-features.md b/translations/pt-BR/content/code-security/getting-started/github-security-features.md index 2d4b87fd94..6c4d6c538f 100644 --- a/translations/pt-BR/content/code-security/getting-started/github-security-features.md +++ b/translations/pt-BR/content/code-security/getting-started/github-security-features.md @@ -37,7 +37,7 @@ Discute em particular e corrige vulnerabilidades de segurança no código do seu ### {% data variables.product.prodname_dependabot_alerts %} e atualizações de segurança -Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[About {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +Ver alertas sobre dependências conhecidas por conter vulnerabilidades de segurança e escolher se deseja gerar pull requests para atualizar essas dependências automaticamente. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)". {% endif %} {% ifversion ghes < 3.3 or ghae-issue-4864 %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md index bec4ce8a43..9938941aa8 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-organization.md @@ -48,7 +48,7 @@ Você pode criar uma política de segurança padrão que será exibida em qualqu {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)," "[Exploring the dependencies of a repository](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)," and "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)." +Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)" "[Explorando as dependências de um repositório](/code-security/supply-chain-security/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)" e "[Gerenciando as configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)". {% endif %} {% ifversion fpt or ghes > 3.1 or ghae-issue-4864 or ghec %} @@ -79,7 +79,7 @@ Para obter mais informações, consulte "[Sobre {% data variables.product.prodna Você pode habilitar {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests para manter suas dependências atualizadas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)". -Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". {% endif %} @@ -135,7 +135,7 @@ Para obter mais informações, consulte "[Gerenciar configurações de seguranç ## Próximas etapas {% ifversion fpt or ghes > 3.1 or ghec %}Você pode visualizar, filtrar e organizar alertas de segurança em repositórios pertencentes à sua organização na visão geral de segurança. Para obter mais informações, consulte "[Sobre a visão geral de segurança](/code-security/security-overview/about-the-security-overview)".{% endif %} -Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes or ghec %} "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciando pull requests para atualizações de dependências](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates), {% endif %}"[Gerenciando {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)" e "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} diff --git a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md index 0cb11f2ed8..dfe6eed7c5 100644 --- a/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md +++ b/translations/pt-BR/content/code-security/getting-started/securing-your-repository.md @@ -75,7 +75,7 @@ Para obter mais informações, consulte "[Explorar as dependências de um reposi {% data reusables.dependabot.dependabot-alerts-beta %} {% data reusables.dependabot.dependabot-alerts-dependency-graph-enterprise %} -For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" and "[Managing security and analysis settings for your user account](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}." +Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies){% ifversion fpt or ghec %}" e "[Gerenciando configurações de segurança e análise da sua conta de usuário](/github/setting-up-and-managing-your-github-user-account/managing-security-and-analysis-settings-for-your-user-account){% endif %}". {% endif %} @@ -111,7 +111,7 @@ Para obter mais informações, consulte "[Sobre {% data variables.product.prodna Você pode habilitar {% data variables.product.prodname_dependabot %} para aumentar automaticamente os pull requests para manter suas dependências atualizadas. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/about-dependabot-version-updates)". -Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. For more information, see "[Configuring {% data variables.product.prodname_dependabot %} version updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)." +Para habilitar {% data variables.product.prodname_dependabot_version_updates %}, você deve criar um arquivo de configuração *dependabot.yml*. Para obter mais informações, consulte "[Configurando as atualizações da versão de {% data variables.product.prodname_dependabot %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/enabling-and-disabling-dependabot-version-updates)". {% endif %} @@ -132,7 +132,7 @@ Você pode configurar {% data variables.product.prodname_code_scanning %} para i {% endif %} ## Próximas etapas -Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. For more information, see {% ifversion fpt or ghes or ghec %} "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),"{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Managing pull requests for dependency updates](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates)," {% endif %}"[Managing {% data variables.product.prodname_code_scanning %} for your repository](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)," and "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." +Você pode visualizar e gerenciar alertas de funcionalidades de segurança para resolver dependências e vulnerabilidades no seu código. Para obter mais informações, consulte {% ifversion fpt or ghes or ghec %} "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/code-security/supply-chain-security/viewing-and-updating-vulnerable-dependencies-in-your-repository),{% endif %} {% ifversion fpt or ghec or ghes > 3.2 %}"[Gerenciando pull requests para atualizações de dependências](/code-security/supply-chain-security/managing-pull-requests-for-dependency-updates), {% endif %}"[Gerenciando {% data variables.product.prodname_code_scanning %} para o seu repositório](/code-security/secure-coding/managing-code-scanning-alerts-for-your-repository)" e "[Gerenciando alertas de {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)." {% ifversion fpt or ghec %}Se você tiver uma vulnerabilidade de segurança, você poderá criar uma consultoria de segurança para discutir em privado e corrigir a vulnerabilidade. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)" e " "[Criar uma consultoria de segurança](/code-security/security-advisories/creating-a-security-advisory)". {% endif %} diff --git a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md index f49db4795c..9549eaaae2 100644 --- a/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md @@ -31,9 +31,9 @@ If your project communicates with an external service, you might use a token or {% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is available on {% data variables.product.prodname_dotcom_the_website %} in two forms: -1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relvant partner. +1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relevant partner. -2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scannng partners, by other service providers, or defined by your organization are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. +2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scanning partners, by other service providers, or defined by your organization, are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. {% endif %} Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %} diff --git a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md index 47fef99fe6..3eb4d98fb4 100644 --- a/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md +++ b/translations/pt-BR/content/code-security/security-overview/about-the-security-overview.md @@ -28,7 +28,7 @@ shortTitle: Sobre a visão geral de segurança Você pode usar a visão geral de segurança para uma visão de alto nível do status de segurança da sua organização ou para identificar repositórios problemáticos que exigem intervenção. É possível visualizar as informações de segurança de tipo agregado ou específico do repositório na visão geral de segurança. Você também pode usar a visão geral de segurança para ver quais funcionalidades de segurança são habilitadas para os repositórios e para configurar quaisquer funcionalidades de segurança disponíveis que não estão em uso atualmente. -The security overview indicates whether {% ifversion fpt or ghes > 3.1 or ghec %}security{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} features are enabled for repositories owned by your organization and consolidates alerts for each feature.{% ifversion fpt or ghes > 3.1 or ghec %} Security features include {% data variables.product.prodname_GH_advanced_security %} features, such as {% data variables.product.prodname_code_scanning %} and {% data variables.product.prodname_secret_scanning %}, as well as {% data variables.product.prodname_dependabot_alerts %}.{% endif %} For more information about {% data variables.product.prodname_GH_advanced_security %} features, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} +A visão geral de segurança indica se {% ifversion fpt or ghes > 3.1 or ghec %}os recursos de segurança{% endif %}{% ifversion ghae %}{% data variables.product.prodname_GH_advanced_security %}{% endif %} estão habilitados para os repositórios pertencentes à sua organização e consolida os alertas para cada recurso.{% ifversion fpt or ghes > 3.1 or ghec %} As funcionalidades de segurança incluem funcionalidaes de {% data variables.product.prodname_GH_advanced_security %} como, por exemplo, {% data variables.product.prodname_code_scanning %} e {% data variables.product.prodname_secret_scanning %}, bem como {% data variables.product.prodname_dependabot_alerts %}.{% endif %} Para obter mais informações sobre as funcionalidades de {% data variables.product.prodname_GH_advanced_security %} conuslte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)."{% ifversion fpt or ghes > 3.1 or ghec %} Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)."{% endif %} Para obter mais informações sobre como proteger seu código nos níveis do repositório e da organização, consulte "[Protegendo seu repositório](/code-security/getting-started/securing-your-repository)" e "[Protegendo sua organização](/code-security/getting-started/securing-your-organization)". @@ -50,13 +50,13 @@ Para cada repositório na visão de segurança, você verá ícones para cada ti ![Ícones na visão geral de segurança](/assets/images/help/organizations/security-overview-icons.png) -| Ícone | Significado | -| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning) | -| {% octicon "key" aria-label="Secret scanning alerts" %} | Alertas de {% data variables.product.prodname_secret_scanning_caps %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning) | -| {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)." | -| {% octicon "check" aria-label="Check" %} | O recurso de segurança está habilitado, mas não envia alertas neste repositório. | -| {% octicon "x" aria-label="x" %} | O recurso de segurança não é compatível com este repositório. | +| Ícone | Significado | +| ------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| {% octicon "code-square" aria-label="Code scanning alerts" %} | Alertas de {% data variables.product.prodname_code_scanning_capc %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_code_scanning %}](/code-security/secure-coding/about-code-scanning) | +| {% octicon "key" aria-label="Secret scanning alerts" %} | Alertas de {% data variables.product.prodname_secret_scanning_caps %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning) | +| {% octicon "hubot" aria-label="Dependabot alerts" %} | {% data variables.product.prodname_dependabot_alerts %}. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)". | +| {% octicon "check" aria-label="Check" %} | O recurso de segurança está habilitado, mas não envia alertas neste repositório. | +| {% octicon "x" aria-label="x" %} | O recurso de segurança não é compatível com este repositório. | A visão geral de segurança exibe alertas ativos criados por funcionalidades de segurança. Se não houver alertas na visão geral de segurança de um repositório, as vulnerabilidades de segurança não detectadas ou erros de código ainda poderão existir. diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md index 330130e1ac..a15d93bf29 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security.md @@ -1,6 +1,6 @@ --- title: Sobre a segurança da cadeia de suprimento -intro: '{% data variables.product.product_name %} helps you secure your supply chain, from understanding the dependencies in your environment, to knowing about vulnerabilities in those dependencies{% ifversion fpt or ghec or ghes > 3.2 %}, and patching them{% endif %}.' +intro: '{% data variables.product.product_name %} ajuda você a proteger sua cadeia de suprimentos, de entender as dependências do seu ambiente, conhecer as vulnerabilidades nessas dependências{% ifversion fpt or ghec or ghes > 3.2 %} e corrigi-las{% endif %}.' miniTocMaxHeadingLevel: 3 shortTitle: Segurança da cadeia de suprimento redirect_from: @@ -21,134 +21,134 @@ topics: - Repositories --- -## About supply chain security at GitHub +## Sobre a segurança da cadeia de suprimentos no GitHub -With the accelerated use of open source, most projects depend on hundreds of open-source dependencies. This poses a security problem: what if the dependencies you're using are vulnerable? You could be putting your users at risk of a supply chain attack. One of the most important things you can do to protect your supply chain is to patch your vulnerabilities. +Com o uso acelerado de código aberto, a maioria dos projetos depende de centenas de dependências de código aberto. Isso coloca um problema de segurança: e se as dependências que você estiver usando forem vulneráveis? Você poderia colocar os seus usuários em risco de ataque da cadeia de suprimentos. Uma das coisas mais importantes que você pode fazer para proteger sua cadeia de suprimentos é corrigir suas vulnerabilidades. -You add dependencies directly to your supply chain when you specify them in a manifest file or a lockfile. Dependencies can also be included transitively, that is, even if you don’t specify a particular dependency, but a dependency of yours uses it, then you’re also dependent on that dependency. +Você adiciona dependências diretamente à sua cadeia de suprimentos ao especificá-las em um arquivo de manifesto ou um arquivo de bloqueio. As dependências também podem ser incluídas transitoriamente, ou seja, até mesmo se você não especificar uma dependência em particular, mas a sua dependência a usa, portanto, você também depende dessa dependência. -{% data variables.product.product_name %} offers a range of features to help you understand the dependencies in your environment{% ifversion ghes < 3.3 or ghae %} and know about vulnerabilities in those dependencies{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %}, know about vulnerabilities in those dependencies, and patch them{% endif %}. +{% data variables.product.product_name %} oferece uma variedade de recursos para ajudar você a entender as dependências do seu ambiente{% ifversion ghes < 3.3 or ghae %} e conhecer as vulnerabilidades dessas dependências{% endif %}{% ifversion fpt or ghec or ghes > 3.2 %},conhecer as vulnerabilidades nessas dependências e corrigi-las{% endif %}. -The supply chain features on {% data variables.product.product_name %} are: +As funcionalidades da cadeia de suprimentos em {% data variables.product.product_name %} são: - **Gráfico de dependências** -{% ifversion fpt or ghec or ghes > 3.1 or ghae %}- **Dependency review**{% endif %} +{% ifversion fpt or ghec or ghes > 3.1 or ghae %}- **Revisão de Dependência**{% endif %} - **{% data variables.product.prodname_dependabot_alerts %} ** {% ifversion fpt or ghec or ghes > 3.2 %}- **{% data variables.product.prodname_dependabot_updates %}** - **{% data variables.product.prodname_dependabot_security_updates %}** - **{% data variables.product.prodname_dependabot_version_updates %}**{% endif %} -The dependency graph is central to supply chain security. The dependency graph identifies all upstream dependencies and public downstream dependents of a repository or package. You can see your repository’s dependencies and some of their properties, like vulnerability information, on the dependency graph for the repository. +O gráfico de dependências é fundamental para fornecer segurança da cadeia de suprimentos. O gráfico de dependências identifica todas as dependências a montante e as dependências públicas a jusante de um repositório ou pacote. É possível ver as dependências e algumas de suas propriedades, como informações de vulnerabilidade, no gráfico de dependências do repositório. {% ifversion fpt or ghec or ghes > 3.1 or ghae %} -Other supply chain features on {% data variables.product.prodname_dotcom %} rely on the information provided by the dependency graph. +As outras funcionalidades da cadeia de suprimentos em {% data variables.product.prodname_dotcom %} dependem das informações fornecidas pelo gráfico de dependências. -- Dependency review uses the dependency graph to identify dependency changes and help you understand the security impact of these changes when you review pull requests. -- {% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of known vulnerabilities published in the {% data variables.product.prodname_advisory_database %}, scans your dependecies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability is detected. -{% ifversion fpt or ghec or ghes > 3.2 %}- {% data variables.product.prodname_dependabot_security_updates %} use the dependency graph and {% data variables.product.prodname_dependabot_alerts %} to help you update dependencies with known vulnerabilities in your repository. +- A revisão de dependências usa o gráfico de dependências para identificar mudanças de dependências e ajuda você a entender o impacto de segurança dessas alterações ao revisar pull requests. +- Os dados de dependência de referência cruzada de {% data variables.product.prodname_dependabot %} fornecidos pelo gráfico de dependências com a lista de vulnerabilidades conhecidas publicadas no {% data variables.product.prodname_advisory_database %}, verifica suas dependências e gera {% data variables.product.prodname_dependabot_alerts %} quando uma potencial vulnerabilidade é detectada. +{% ifversion fpt or ghec or ghes > 3.2 %}- {% data variables.product.prodname_dependabot_security_updates %} usa o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para ajudar você a atualizar dependências com vulnerabilidades conhecidas no seu repositório. -{% data variables.product.prodname_dependabot_version_updates %} don't use the dependency graph and rely on the semantic versioning of dependencies instead. {% data variables.product.prodname_dependabot_version_updates %} help you keep your dependencies updated, even when they don’t have any vulnerabilities. +{% data variables.product.prodname_dependabot_version_updates %} não usa o gráfico de dependências e confia na versão semântica das dependências. {% data variables.product.prodname_dependabot_version_updates %} ajuda você a manter suas dependências atualizadas, mesmo quando elas não têm nenhuma vulnerabilidade. {% endif %} {% endif %} {% ifversion ghes < 3.2 %} -{% data variables.product.prodname_dependabot %} cross-references dependency data provided by the dependency graph with the list of known vulnerabilities published in the {% data variables.product.prodname_advisory_database %}, scans your dependencies and generates {% data variables.product.prodname_dependabot_alerts %} when a potential vulnerability is detected. +Os dados de dependência de referência cruzada de {% data variables.product.prodname_dependabot %} fornecidos pelo gráfico de dependências com a lista de vulnerabilidades conhecidas publicadas no {% data variables.product.prodname_advisory_database %}, verifica suas dependências e gera {% data variables.product.prodname_dependabot_alerts %} quando uma potencial vulnerabilidade é detectada. {% endif %} -## Feature overview +## Visão geral de recursos -### What is the dependency graph +### Qual é o gráfico de dependências -To generate the dependency graph, {% data variables.product.company_short %} looks at a repository’s explicit dependencies declared in the manifest and lockfiles. When enabled, the dependency graph automatically parses all known package manifest files in the repository, and uses this to construct a graph with known dependency names and versions. +Para gerar o gráfico de dependência, {% data variables.product.company_short %} analisa as dependências explícitas de um repositório declaradas no manifesto e no arquivo de bloqueio. Quando habilitado, o gráfico de dependências analisa automaticamente todos os arquivos de manifesto de pacote conhecidos no repositório, e usa isto para construir um gráfico com nomes e versões conhecidas das dependências. -- The dependency graph includes information on your _direct_ dependencies and _transitive_ dependencies. -- The dependency graph is automatically updated when you push a commit to {% data variables.product.company_short %} that changes or adds a supported manifest or lock file to the default branch, and when anyone pushes a change to the repository of one of your dependencies. -- You can see the dependency graph by opening the repository's main page on {% data variables.product.product_name %}, and navigating to the **Insights** tab. +- O gráfico de dependências inclui informações sobre suas dependências _diretas_ e dependências _transitivas_. +- O gráfico de dependência é atualizado automaticamente quando você faz push de um commit para {% data variables.product.company_short %} que altera ou adiciona um manifesto compatível ou um arquivo de bloqueio para o branch padrão, e quando alguém fizer uma alteração no repositório de uma de suas dependências. +- É possível ver o gráfico de dependências abrindo a página principal do repositório no {% data variables.product.product_name %} e acessando a aba **Insights**. -For more information about the dependency graph, see "[About the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)." +Para obter mais informações sobre o gráfico de dependências, consulte "[Sobre o gráfico de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph)". {% ifversion fpt or ghec or ghes > 3.1 or ghae %} -### What is dependency review +### O que é revisão de dependências -Dependency review helps reviewers and contributors understand dependency changes and their security impact in every pull request. +A revisão de dependências ajuda os revisores e colaboradores a entenderem as mudanças de dependência e seu impacto de segurança em cada pull request. -- Dependency review tells you which dependencies were added, removed, or updated, in a pull request. You can use the release dates, popularity of dependencies, and vulnerability information to help you decide whether to accept the change. -- You can see the dependency review for a pull request by showing the rich diff on the **Files Changed** tab. +- A revisão de dependências informa quais dependências foram adicionadas, removidas ou atualizadas em um pull request. Você pode usar as datas de versão, a popularidade das dependências e informações de vulnerabilidade para ajudar você a decidir se deseja aceitar a alteração. +- Você pode ver a revisão de dependências para um pull request mostrando o diff avançado na aba**Arquivos alterados**. -For more information about dependency review, see "[About dependency review](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)." +Para obter mais informações sobre a análise de dependências, consulte "[Sobre a revisão de dependências](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review)". {% endif %} -### What is Dependabot +### O que é o Dependabot -{% data variables.product.prodname_dependabot %} keeps your dependencies up to date by informing you of any security vulnerabilities in your dependencies{% ifversion fpt or ghec or ghes > 3.2 or ghae %}, and automatically opens pull requests to upgrade your dependencies to the next available secure version when a {% data variables.product.prodname_dependabot %} alert is triggered, or to the latest version when a release is published{% else %} so that you can update that dependency{% endif %}. +{% data variables.product.prodname_dependabot %} mantém suas dependências atualizadas informando você de qualquer vulnerabilidade de segurança em suas dependências{% ifversion fpt or ghec or ghes > 3.2 or ghae %} e abre automaticamente os pull requests para atualizar suas dependências para a próxima versão segura disponível quando um alerta der {% data variables.product.prodname_dependabot %} é acionado ou, na última versão, quando uma versão é publicada{% else %} para que você possa atualizar essa dependência{% endif %}. {% ifversion fpt or ghec or ghes > 3.2 %} -The term "{% data variables.product.prodname_dependabot %}" encompasses the following features: -- {% data variables.product.prodname_dependabot_alerts %}—Displayed notification on the **Security** tab for the repository, and in the repository's dependency graph. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. +O termo "{% data variables.product.prodname_dependabot %}" engloba as seguintes funcionalidades: +- {% data variables.product.prodname_dependabot_alerts %}—Notificação exibida na aba **Segurança** do repositório e no gráfico de dependências do repositório. O alerta inclui um link para o arquivo afetado no projeto, e informações sobre uma versão corrigida. - {% data variables.product.prodname_dependabot_updates %}: - - {% data variables.product.prodname_dependabot_security_updates %}—Triggered updates to upgrade your dependencies to a secure version when an alert is triggered. - - {% data variables.product.prodname_dependabot_version_updates %}—Scheduled updates to keep your dependencies up to date with the latest version. + - {% data variables.product.prodname_dependabot_security_updates %}—Atualizações acionadas para atualizar suas dependências para uma versão segura quando um alerta é acionado. + - {% data variables.product.prodname_dependabot_version_updates %}— Atualizações agendadas para manter suas dependências atualizadas com a versão mais recente. {% endif %} -#### What are Dependabot alerts +#### Quais são os alertas do Dependabot -{% data variables.product.prodname_dependabot_alerts %} highlight repositories affected by a newly discovered vulnerability based on the dependency graph and the {% data variables.product.prodname_advisory_database %}, which contains the versions on known vulnerability lists. +{% data variables.product.prodname_dependabot_alerts %} destaca repositórios afetados por uma vulnerabilidade recém-descoberta baseada no gráfico de dependências e no {% data variables.product.prodname_advisory_database %}, que contém as versões em listas de vulnerabilidades conhecidas. - {% data variables.product.prodname_dependabot %} faz a digitalização para detectar dependências vulneráveis e envia {% data variables.product.prodname_dependabot_alerts %} quando: {% ifversion fpt or ghec %} - - A new vulnerability is added to the {% data variables.product.prodname_advisory_database %}.{% else %} + - Uma nova vulnerabilidade é adicionada ao {% data variables.product.prodname_advisory_database %}.{% else %} - São sincronizados novos dados de consultoria com {% data variables.product.product_location %} a cada hora a partir de {% data variables.product.prodname_dotcom_the_website %}. {% data reusables.security-advisory.link-browsing-advisory-db %}{% endif %} - - The dependency graph for the repository changes. -- {% data variables.product.prodname_dependabot_alerts %} are displayed {% ifversion fpt or ghec or ghes > 3.0 %} on the **Security** tab for the repository and{% endif %} in the repository's dependency graph. O alerta inclui {% ifversion fpt or ghec or ghes > 3.0 %} um link para o arquivo afetado no projeto, e {% endif %}informações sobre uma versão fixa. + - O gráfico de dependências para as alterações no repositório. +- {% data variables.product.prodname_dependabot_alerts %} são exibidos {% ifversion fpt or ghec or ghes > 3.0 %} na aba **Segurança** do repositório e{% endif %} no gráfico de dependências do repositório. O alerta inclui {% ifversion fpt or ghec or ghes > 3.0 %} um link para o arquivo afetado no projeto, e {% endif %}informações sobre uma versão fixa. -For more information about {% data variables.product.prodname_dependabot_alerts %}, see "[About alerts for vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)." +Para obter mais informações sobre {% data variables.product.prodname_dependabot_alerts %}, consulte "[Sobre alertas para dependências vulneráveis](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies)". {% ifversion fpt or ghec or ghes > 3.2 %} -#### What are Dependabot updates +#### Quais são as atualizações do Dependabot -There are two types of {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} _security_ updates and _version_ updates. {% data variables.product.prodname_dependabot %} generates automatic pull requests to update your dependencies in both cases, but there are several differences. +Há dois tipos de {% data variables.product.prodname_dependabot_updates %}: {% data variables.product.prodname_dependabot %} atualizações de _segurança_ e atualizações de _versão_. {% data variables.product.prodname_dependabot %} gera pull requests automáticos para atualizar suas dependências em ambos os casos, mas existem várias diferenças. {% data variables.product.prodname_dependabot_security_updates %}: - - Triggered by a {% data variables.product.prodname_dependabot %} alert - - Update dependencies to the minimum version that resolves a known vulnerability - - Supported for ecosystems the dependency graph supports + - Acionado por um alerta de {% data variables.product.prodname_dependabot %} + - Atualizar dependências para a versão mínima que resolve uma vulnerabilidade conhecida + - Compatível para os ecossistemas que o gráfico de dependências suporta {% data variables.product.prodname_dependabot_version_updates %}: - - Run on a schedule you configure - - Update dependencies to the latest version that matches the configuration - - Supported for a different group of ecosystems + - Executar em um calendário que você configura + - Atualizar dependências para a última versão que corresponde à configuração + - Compatível para um grupo diferente de ecossistemas -For more information about {% data variables.product.prodname_dependabot_updates %}, see "[About {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" and "[About {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)." +Para obter mais informações sobre {% data variables.product.prodname_dependabot_updates %}, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-dependabot-security-updates)" e "[Sobre {% data variables.product.prodname_dependabot_version_updates %}](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/about-dependabot-version-updates)". {% endif %} -## Feature availability +## Disponibilidade de recursos {% ifversion fpt or ghec %} -Public repositories: -- **Dependency graph**—enabled by default and cannot be disabled. -- **Dependency review**—enabled by default and cannot be disabled. -- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. {% data variables.product.prodname_dotcom %} detects vulnerable dependencies and displays information in the dependency graph, but does not generate {% data variables.product.prodname_dependabot_alerts %} by default. Repository owners or people with admin access can enable {% data variables.product.prodname_dependabot_alerts %}. You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." +Repositórios públicos: +- **Gráfico de dependência**—habilitado por padrão e não pode ser desabilitado. +- **Revisão de dependência**—habilitado por padrão e não pode ser desabilitado. +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. {% data variables.product.prodname_dotcom %} detecta dependências vulneráveis e exibe informações no gráfico de dependência, mas não gera {% data variables.product.prodname_dependabot_alerts %} por padrão. Os proprietários do repositório ou pessoas com acesso de administrador podem habilitar {% data variables.product.prodname_dependabot_alerts %}. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciando configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". -Private repositories: -- **Dependency graph**—not enabled by default. The feature can be enabled by repository administrators. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". +Repositórios privados: +- **Gráfico de dependência**—não habilitado por padrão. O recurso pode ser habilitado pelos administradores do repositório. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". {% ifversion fpt %} -- **Dependency review**—available in private repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review). +- **Revisão de dependência**— disponível em repositórios privados pertencentes a organizações que usam {% data variables.product.prodname_ghe_cloud %} e têm uma licença para {% data variables.product.prodname_GH_advanced_security %}. Para obter mais informações, consulte a [documentação de {% data variables.product.prodname_ghe_cloud %}](/enterprise-cloud@latest/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review). {% elsif ghec %} -- **Dependency review**—available in private repositories owned by organizations provided you have a license for {% data variables.product.prodname_GH_advanced_security %} and the dependency graph enabled. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" and "[Exploring the dependencies of a repository](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)." +- **Revisão de dependência**— disponível em repositórios privados pertencentes a organizações, desde que você tenha uma licença para {% data variables.product.prodname_GH_advanced_security %} e o gráfico de dependências habilitado. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)" e "[Explorando as dependências de um repositório](/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository#enabling-and-disabling-the-dependency-graph-for-a-private-repository)". {% endif %} -- **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. You can also enable or disable Dependabot alerts for all repositories owned by your user account or organization. For more information, see "[Managing security and analysis settings for your user account](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" or "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)." +- **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. Os proprietários de repositórios privados ou pessoas com acesso de administrador, podem habilitar o {% data variables.product.prodname_dependabot_alerts %} ativando o gráfico de dependências e {% data variables.product.prodname_dependabot_alerts %} para seus repositórios. Você também pode habilitar ou desabilitar alertas do Dependabot para todos os repositórios pertencentes à sua conta de usuário ou organização. Para obter mais informações, consulte "[Gerenciando configurações de segurança e análise da sua conta de usuário](/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-security-and-analysis-settings-for-your-user-account)" ou "[Gerenciando configurações de segurança e análise da sua organização](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization)". -Any repository type: -- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." -- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +Qualquer tipo de repositório: +- **{% data variables.product.prodname_dependabot_security_updates %}**—não habilitado por padrão. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +- **{% data variables.product.prodname_dependabot_version_updates %}**—não habilitado por padrão. As pessoas com permissões de gravação em um repositório podem habilitar {% data variables.product.prodname_dependabot_version_updates %}. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." {% endif %} {% ifversion ghes or ghae %} -- **Dependency graph** and **{% data variables.product.prodname_dependabot_alerts %}**—not enabled by default. Both features are configured at an enterprise level by the enterprise owner. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." -- **Dependency review**—available when dependency graph is enabled for {% data variables.product.product_location %} and {% data variables.product.prodname_advanced_security %} is enabled for the organization or repository. For more information, see "[About {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." +- **Gráfico de dependência** e **{% data variables.product.prodname_dependabot_alerts %}**—não habilitado por padrão. Ambas as funcionalidades são configuradas a nível empresarial pelo proprietário da empresa. For more information, see {% ifversion ghes %}"[Enabling the dependency graph for your enterprise](/admin/code-security/managing-supply-chain-security-for-your-enterprise/enabling-the-dependency-graph-for-your-enterprise)" and {% endif %}"[Enabling {% data variables.product.prodname_dependabot %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)." +- **Revisão de dependência**—disponível quando o gráfico de dependências está habilitado para {% data variables.product.product_location %} e {% data variables.product.prodname_advanced_security %} está habilitado para a organização ou repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_GH_advanced_security %}](/get-started/learning-about-github/about-github-advanced-security)." {% endif %} {% ifversion ghes > 3.2 %} -- **{% data variables.product.prodname_dependabot_security_updates %}**—not enabled by default. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." -- **{% data variables.product.prodname_dependabot_version_updates %}**—not enabled by default. People with write permissions to a repository can enable {% data variables.product.prodname_dependabot_version_updates %}. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." +- **{% data variables.product.prodname_dependabot_security_updates %}**—não habilitado por padrão. É possível habilitar o {% data variables.product.prodname_dependabot_security_updates %} para qualquer repositório que use {% data variables.product.prodname_dependabot_alerts %} e o gráfico de dependências. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/about-dependabot-security-updates)." +- **{% data variables.product.prodname_dependabot_version_updates %}**—não habilitado por padrão. As pessoas com permissões de gravação em um repositório podem habilitar {% data variables.product.prodname_dependabot_version_updates %}. Para obter mais informações sobre habilitar atualizações de segurança, consulte "[Configurar {% data variables.product.prodname_dependabot_security_updates %}](/github/managing-security-vulnerabilities/configuring-dependabot-security-updates)." {% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md index 28a634fca7..e02389b368 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md @@ -56,7 +56,7 @@ Você pode usar o gráfico de dependências para: - Explorar os repositórios dos quais o seu código depende{% ifversion fpt or ghec %} e aqueles que dependem dele{% endif %}. Para obter mais informações, consulte "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)". {% ifversion fpt or ghec %} - Visualizar um resumo das dependências usadas nos repositórios da sua organização em um único painel. Para obter mais informações, consulte "[Visualizar informações na organização](/articles/viewing-insights-for-your-organization#viewing-organization-dependency-insights)".{% endif %} -- Ver e atualizar dependências vulneráveis no seu repositório. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} +- Ver e atualizar dependências vulneráveis no seu repositório. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)."{% ifversion fpt or ghes > 3.1 or ghec %} - Veja as informações sobre dependências vulneráveis em pull requests. Para obter mais informações, consulte "[Revisar as alterações de dependências em um pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-dependency-changes-in-a-pull-request)".{% endif %} ## Habilitar o gráfico de dependências @@ -77,14 +77,14 @@ Os formatos recomendados definem explicitamente quais versões são usadas para | `dotnet` CLI | .NET languages (C#, C++, F#, VB) | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj` | `.csproj`, `.vbproj`, `.nuspec`, `.vcxproj`, `.fsproj`, `packages.config` | {%- if github-actions-in-dependency-graph %} -| {% data variables.product.prodname_actions %} workflows +| Fluxos de trabalho de {% data variables.product.prodname_actions %} [1] | YAML | `.yml`, `.yaml` | `.yml`, `.yaml` | {%- endif %} {%- ifversion fpt or ghes > 3.2 or ghae %} -| Go modules | Go | `go.sum` | `go.mod`, `go.sum` | +| Módulos do Go | Go | `go.sum` | `go.mod`, `go.sum` | {%- elsif ghes = 3.2 %} -| Go modules | Go | `go.mod` | `go.mod` | +| Módulos do Go | Go | `go.mod` | `go.mod` | {%- endif %} | Maven | Java, Scala | `pom.xml` | `pom.xml` | | npm | JavaScript | `package-lock.json` | `package-lock.json`, `package.json`| | pip | Python | `requirements.txt`, `pipfile.lock` | `requirements.txt`, `pipfile`, `pipfile.lock`, `setup.py`{% if github-actions-in-dependency-graph %}[2]{% else %}[1]{% endif %} {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4752 %} @@ -111,5 +111,5 @@ Os formatos recomendados definem explicitamente quais versões são usadas para - "[Gráfico de dependências](https://en.wikipedia.org/wiki/Dependency_graph)" na Wikipedia - "[Explorar as dependências de um repositório](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)"{% ifversion fpt or ghec %} - "[Visualizar informações da sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)"{% endif %} -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Solução de problemas na detecção de dependências vulneráveis](/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies)" diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md index 4f5f873dbb..490aabe6c5 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md @@ -40,7 +40,7 @@ Os proprietários das empresas podem configurar o gráfico de dependências a n ### Vista de dependências {% ifversion fpt or ghec %} -As dependências são agrupadas por ecossistema. Você pode expandir sua dependência para visualizar suas dependências. Dependências de repositórios privados, pacotes privados ou arquivos não reconhecidos são exibidos em texto sem formatação. If the package manager for the dependency is in a public repository, {% data variables.product.product_name %} will display a link to that repository. +As dependências são agrupadas por ecossistema. Você pode expandir sua dependência para visualizar suas dependências. Dependências de repositórios privados, pacotes privados ou arquivos não reconhecidos são exibidos em texto sem formatação. Se o gerenciador de pacotes para a dependência estiver em um repositório público, {% data variables.product.product_name %} irá exibir um link para o repositório. Se foram detectadas vulnerabilidades no repositório, estas são exibidas na parte superior da visualização para usuários com acesso ao {% data variables.product.prodname_dependabot_alerts %}. @@ -83,10 +83,10 @@ Você pode desabilitar o gráfico de dependências a qualquer momento clicando e ## Alterar o pacote "Usado por" -You may notice some repositories have a "Used by" section in the sidebar of the **Code** tab. Your repository will have a "Used by" section if: - * The dependency graph is enabled for the repository (see the above section for more details). - * Your repository contains a package that is published on a [supported package ecosystem](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems). - * Within the ecosystem, your package has a link to a _public_ repository where the source is stored. +Você pode notar que alguns repositórios têm uma seção "Usado por" na barra lateral da aba**Código**. Seu repositório terá uma seção "Usado por", se: + * O gráfico de dependências está habilitado para o repositório (consulte a seção acima para mais detalhes). + * Seu repositório contém um pacote que é publicado em um [ecossistema de pacote compatível](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph#supported-package-ecosystems). + * Dentro do ecossistema, seu pacote tem um link para um repositório _público_ onde a fonte é armazenada. A seção "Usado por" mostra o número de referências públicas ao pacote que foi encontrado, e exibe os avatares de alguns dos proprietários dos projetos dependentes. @@ -115,7 +115,7 @@ Se um arquivo de manifesto ou de bloqueio não for processado, suas dependência ## Leia mais - "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% ifversion fpt or ghec %} +- "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)"{% ifversion fpt or ghec %} - "[Visualizar informações da sua organização](/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-your-organization)" - "[Entender como o {% data variables.product.prodname_dotcom %} usa e protege seus dados](/get-started/privacy-on-github)" {% endif %} diff --git a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md index a8755cefb6..a20d9100f4 100644 --- a/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md +++ b/translations/pt-BR/content/code-security/supply-chain-security/understanding-your-software-supply-chain/troubleshooting-the-dependency-graph.md @@ -1,7 +1,7 @@ --- title: Solução de problemas para o gráfico de dependências -intro: 'If the dependency information reported by the dependency graph is not what you expected, there are a number of points to consider, and various things you can check.' -shortTitle: Troubleshoot dependency graph +intro: 'Se as informações de dependências relatadas pelo gráfico de dependências não é o que você esperava, há uma série de pontos a considerar e várias coisas que você pode verificar.' +shortTitle: Solucionar problemas do gráfico de dependências versions: fpt: '*' ghes: '*' @@ -26,7 +26,7 @@ O gráfico de dependências inclui informações sobre dependências explicitame O gráfico de dependências não inclui dependências de "soltas". Dependências "soltas" são arquivos individuais copiados de outra fonte e verificados no repositório diretamente ou dentro de um arquivo (como um arquivo ZIP ou JAR), em vez de ser referenciadas pelo manifesto ou arquivo de bloqueio do gerenciador de pacotes. -**Check**: Is the missing dependency for a component that's not specified in the repository's manifest or lockfile? +**Verificação**: A dependência ausente para um componente que não está especificado no manifesto ou arquivo de bloqueio do repositório? ## O gráfico de dependências detecta dependências especificadas usando variáveis? diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md index 8eaf17a767..1c7a015cf4 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app-using-url-parameters.md @@ -59,39 +59,39 @@ Lista completa de parâmetros de consulta, permissões e eventos disponíveis en Você pode selecionar permissões em uma string de consultas usando o nome da permissão na tabela a seguir como o nome do parâmetro de consulta e o tipo de permissão como valor da consulta. Por exemplo, para selecionar permissões de `Leitura & gravação` na interface de usuário para `conteúdo`, sua string de consulta incluiria `&contents=write`. Para selecionar as permissões `Somente leitura` na interface de usuário para `bloquear`, sua string de consulta incluiria `&blocking=read`. Para selecionar `sem acesso` na interface do usuário para `verificações`, sua string de consulta não incluiria a permissão `verificações`. -| Permissão | Descrição | -| -------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Permissão | Descrição | +| -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`administração`](/rest/reference/permissions-required-for-github-apps/#permission-on-administration) | Concede acesso a vários pontos finais para administração de organização e repositório. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %} | [`bloqueio`](/rest/reference/permissions-required-for-github-apps/#permission-on-blocking) | Concede acesso à [API de usuários de bloqueio](/rest/reference/users#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} | [`Verificações`](/rest/reference/permissions-required-for-github-apps/#permission-on-checks) | Concede acesso à [API de verificação](/rest/reference/checks). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion ghes < 3.4 %} | `content_references` | Concede acesso ao ponto final "[Criar um anexo de conteúdo](/rest/reference/apps#create-a-content-attachment). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`Conteúdo`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Concede acesso a vários pontos finais que permitem modificar o conteúdo do repositório. Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Conteúdo`](/rest/reference/permissions-required-for-github-apps/#permission-on-contents) | Concede acesso a vários pontos finais que permitem modificar o conteúdo do repositório. Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`Implantações`](/rest/reference/permissions-required-for-github-apps/#permission-on-deployments) | Concede acesso à [API de implementação](/rest/reference/repos#deployments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghec %} | [`emails`](/rest/reference/permissions-required-for-github-apps/#permission-on-emails) | Concede acesso à [API de e-mails](/rest/reference/users#emails). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`seguidores`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Concede acesso à [API de seguidores](/rest/reference/users#followers). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Concede acesso à [API de chaves de GPG](/rest/reference/users#gpg-keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Problemas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Concede acesso à [API de problemas](/rest/reference/issues). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`chaves`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Concede acesso à [API de chaves públicas](/rest/reference/users#keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`seguidores`](/rest/reference/permissions-required-for-github-apps/#permission-on-followers) | Concede acesso à [API de seguidores](/rest/reference/users#followers). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`gpg_keys`](/rest/reference/permissions-required-for-github-apps/#permission-on-gpg-keys) | Concede acesso à [API de chaves de GPG](/rest/reference/users#gpg-keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Problemas`](/rest/reference/permissions-required-for-github-apps/#permission-on-issues) | Concede acesso à [API de problemas](/rest/reference/issues). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`chaves`](/rest/reference/permissions-required-for-github-apps/#permission-on-keys) | Concede acesso à [API de chaves públicas](/rest/reference/users#keys). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`members`](/rest/reference/permissions-required-for-github-apps/#permission-on-members) | Concede acesso para gerenciar os membros de uma organização. Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghec %} -| [`metadados`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Concede acesso a pontos finais somente leitura que não vazam dados confidenciais. Pode ser `leitura ` ou `nenhum`. O padrão é `leitura`, ao definir qualquer permissão, ou `nenhum` quando você não especificar nenhuma permissão para o {% data variables.product.prodname_github_app %}. | +| [`metadados`](/rest/reference/permissions-required-for-github-apps/#metadata-permissions) | Concede acesso a pontos finais somente leitura que não vazam dados confidenciais. Pode ser `leitura ` ou `nenhum`. O padrão é `leitura`, ao definir qualquer permissão, ou `nenhum` quando você não especificar nenhuma permissão para o {% data variables.product.prodname_github_app %}. | | [`organization_administration`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-administration) | Concede acesso ao ponto final "[Atualizar uma organização](/rest/reference/orgs#update-an-organization)" ponto final e Pa [API de restrições de interação da organização](/rest/reference/interactions#set-interaction-restrictions-for-an-organization). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Concede acesso à [API de webhooks da organização](/rest/reference/orgs#webhooks/). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| `organization_plan` | Concede acesso para obter informações sobre o plano de uma organização usando o ponto final "[Obter uma organização](/rest/reference/orgs#get-an-organization)". Pode ser: `nenhum` ou `leitura`. | +| [`organization_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-hooks) | Concede acesso à [API de webhooks da organização](/rest/reference/orgs#webhooks/). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `organization_plan` | Concede acesso para obter informações sobre o plano de uma organização usando o ponto final "[Obter uma organização](/rest/reference/orgs#get-an-organization)". Pode ser: `nenhum` ou `leitura`. | | [`organization_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghec %} | [`organization_user_blocking`](/rest/reference/permissions-required-for-github-apps/#permission-on-organization-projects) | Concede acesso à [API de usuários de bloqueio da organização](/rest/reference/orgs#blocking). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`Páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Concede acesso à [API de páginas](/rest/reference/repos#pages). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| `plano` | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`. | -| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Páginas`](/rest/reference/permissions-required-for-github-apps/#permission-on-pages) | Concede acesso à [API de páginas](/rest/reference/repos#pages). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `plano` | Concede acesso para obter informações sobre o plano de um usuário do GitHub que usa o ponto final "[Obter um usuário](/rest/reference/users#get-a-user)". Pode ser: `nenhum` ou `leitura`. | +| [`pull_requests`](/rest/reference/permissions-required-for-github-apps/#permission-on-pull-requests) | Concede acesso a vários pontos finais do pull request. Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`repository_hooks`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-hooks) | Concede acesso à [API de webhooks do repositório](/rest/reference/repos#hooks). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`repository_projects`](/rest/reference/permissions-required-for-github-apps/#permission-on-repository-projects) | Concede acesso à [API de Projetos](/rest/reference/projects). Pode ser: `nenhum`, `leitura`, `gravação` ou `administrador`.{% ifversion fpt or ghes or ghec %} | [`secret_scanning_alerts`](/rest/reference/permissions-required-for-github-apps/#permission-on-secret-scanning-alerts) | Concede acesso à [API de varredura de segredo](/rest/reference/secret-scanning). Pode ser: `none`, `read` ou `write`.{% endif %}{% ifversion fpt or ghes or ghec %} | [`security_events`](/rest/reference/permissions-required-for-github-apps/#permission-on-security-events) | Concede acesso à [API de varredura de código](/rest/reference/code-scanning/). Pode ser: `nenhum`, `leitura` ou `gravação`.{% endif %} -| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | -| [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/commits#commit-statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`single_file`](/rest/reference/permissions-required-for-github-apps/#permission-on-single-file) | Concede acesso à [API de conteúdo](/rest/reference/repos#contents). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`estrela`](/rest/reference/permissions-required-for-github-apps/#permission-on-starring) | Concede acesso à [API estrelada](/rest/reference/activity#starring). Pode ser: `nenhum`, `leitura` ou `gravação`. | +| [`Status`](/rest/reference/permissions-required-for-github-apps/#permission-on-statuses) | Concede acesso à [API de status](/rest/reference/commits#commit-statuses). Pode ser: `nenhum`, `leitura` ou `gravação`. | | [`team_discussions`](/rest/reference/permissions-required-for-github-apps/#permission-on-team-discussions) | Concede acesso à [API de discussões de equipe](/rest/reference/teams#discussions) e à [API de comentários de discussão de equipe](/rest/reference/teams#discussion-comments). Pode ser: `nenhum`, `leitura` ou `gravação`.{% ifversion fpt or ghes or ghae-issue-4864 or ghec %} -| `vulnerability_alerts` | Grants access to receive {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies in a repository. See "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" to learn more. Pode ser: `none` ou `read`.{% endif %} -| `inspecionando` | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`. | +| `vulnerability_alerts` | Concede acesso para receber {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis em um repositório. Consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies/)" para saber mais. Pode ser: `none` ou `read`.{% endif %} +| `inspecionando` | Concede acesso à lista e alterações de repositórios que um usuário assinou. Pode ser: `nenhum`, `leitura` ou `gravação`. | ## Eventos webhook do {% data variables.product.prodname_github_app %} diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md index eb7f4722a3..ad9e22082c 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/creating-a-github-app.md @@ -47,7 +47,7 @@ topics: {% endif %} 1. Por padrão, para melhorar a segurança de seus aplicativos, seus aplicativos usarão os tokens de autorização do usuário. Para optar por não usar tokens do usuário expirados, você deverá desmarcar "Expirar tokens de autorização do usuário". Para saber mais sobre como configurar o fluxo de atualização do token e os benefícios de expirar os tokens do usuário, consulte "[Atualizando tokens de acesso do usuário para o servidor](/apps/building-github-apps/refreshing-user-to-server-access-tokens/)." ![Opção para expirar os tokens dos usuários durante a configuração dos aplicativos GitHub](/assets/images/github-apps/expire-user-tokens-selection.png) 1. Se seu aplicativo autoriza usuários a usar o fluxo OAuth, você pode selecionar **Solicitar autorização de usuário (OAuth) durante a instalação** para permitir que pessoas autorizem o aplicativo ao instalá-lo, economizando uma etapa. Se você selecionar esta opção, a "URL de configuração" irá tornar-se indisponível e os usuários serão redirecionados para a "URL de retorno de chamada de autorização do usuário" após a instalação do aplicativo. Consulte "[Autorizando usuários durante a instalação](/apps/installing-github-apps/#authorizing-users-during-installation)" para obter mais informações. ![Request user authorization during installation](/assets/images/github-apps/github_apps_request_auth_upon_install.png){% if device-flow-is-opt-in %} -1. If your GitHub App will use the device flow to identify and authorize users, click **Enable Device Flow**. Para obter mais informações sobre o fluxo do dispositivo, consulte "[Autorizando aplicativos OAuth](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)". ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %} +1. Se o seu aplicativo GitHub usar o fluxo do dispositivo para identificar e autorizar usuários, clique em **Habilitar fluxo de dispositivo**. Para obter mais informações sobre o fluxo do dispositivo, consulte "[Autorizando aplicativos OAuth](/developers/apps/building-oauth-apps/authorizing-oauth-apps#device-flow)". ![Screenshot showing field for enabling device flow](/assets/images/oauth-apps/enable-device-flow.png){% endif %} 1. Se for necessária uma configuração adicional após a instalação, adicione um "Configurar URL" para redirecionar os usuários após a instalação do seu aplicativo. ![Campo para a URL de configuração do seu aplicativo GitHub ](/assets/images/github-apps/github_apps_setup_url.png) {% note %} diff --git a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md index 579e42e4bd..7decc5fba7 100644 --- a/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md +++ b/translations/pt-BR/content/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps.md @@ -127,7 +127,7 @@ curl -H "Authorization: token OAUTH-TOKEN" {% data variables.product.api_url_pre O fluxo de dispositivos permite que você autorize usuários para um aplicativo sem cabeçalho, como uma ferramenta de CLI ou um gerenciador de credenciais do Git. -{% if device-flow-is-opt-in %}Before you can use the device flow to identify and authorize users, you must first enable it in your app's settings. For more information on enabling device flow, see "[Modifying a GitHub App](/developers/apps/managing-github-apps/modifying-a-github-app)." {% endif %}For more information about authorizing users using the device flow, see "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps#device-flow)." +{% if device-flow-is-opt-in %}Antes de poder usar usar o fluxo do dispositivo para identificar e autorizar usuários, primeiro você deve habilitá-lo nas configurações do aplicativo. Para obter mais informações sobre como habilitar o fluxo do dispositivo, consulte "[Modificando um aplicativo GitHub](/developers/apps/managing-github-apps/modifying-a-github-app)". {% endif %}Para obter mais informações sobre autorização de usuários que usam o fluxo do dispositivo, consulte "[Autorizar aplicativos OAuth](/developers/apps/authorizing-oauth-apps#device-flow)." ## Verifique quais recursos de instalação um usuário pode acessar diff --git a/translations/pt-BR/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md b/translations/pt-BR/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md index 17197d6896..16c7423f9b 100644 --- a/translations/pt-BR/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md +++ b/translations/pt-BR/content/get-started/privacy-on-github/managing-data-use-settings-for-your-private-repository.md @@ -16,7 +16,7 @@ shortTitle: Gerenciar o uso de dados para repositório privado ## Sobre o uso de dados para seu repositório privado -Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gráfico de dependências, em que você pode acompanhar as dependências do repositório e receber {% data variables.product.prodname_dependabot_alerts %} quando o {% data variables.product.product_name %} detectar dependências vulneráveis. For more information, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)." +Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gráfico de dependências, em que você pode acompanhar as dependências do repositório e receber {% data variables.product.prodname_dependabot_alerts %} quando o {% data variables.product.product_name %} detectar dependências vulneráveis. Para obter mais informações, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)". ## Habilitar ou desabilitar os recursos de uso de dados @@ -31,5 +31,5 @@ Ao habilitar o uso de dados para seu repositório privado, poderá acessar o gr ## Leia mais - "[Sobre o uso de seus dados pelo {% data variables.product.prodname_dotcom %}](/articles/about-github-s-use-of-your-data)" -- "[Viewing {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" +- "[Visualizando {% data variables.product.prodname_dependabot_alerts %} para dependências vulneráveis](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)" - "[Gerenciar as configurações de segurança e análise para o seu repositório](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository)" diff --git a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md index 2118f2f7ac..93ff618687 100644 --- a/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md +++ b/translations/pt-BR/content/get-started/quickstart/fork-a-repo.md @@ -22,7 +22,7 @@ topics: ## Sobre bifurcações -O uso mais comum das bifurcações são propostas de mudanças no projeto de alguma outra pessoa ou o uso do projeto de outra pessoa como ponto de partida para sua própria ideia. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". +Most commonly, forks are used to either propose changes to someone else's project to which you don't have write access, or to use someone else's project as a starting point for your own idea. Você pode bifurcar um repositório para criar uma cópia do repositório e fazer alterações sem afetar o repositório upstream. Para obter mais informações, consulte "[Trabalhando com as bifurcações](/github/collaborating-with-issues-and-pull-requests/working-with-forks)". ### Proponha mudanças no projeto de outra pessoa diff --git a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md index 63a70e2fe5..c770b9af3d 100644 --- a/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md +++ b/translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-server.md @@ -19,7 +19,7 @@ shortTitle: Teste do servidor corporativo Você pode solicitar uma versão de avaliação por 45 dias do {% data variables.product.prodname_ghe_server %}. A versão de avaliação será instalada como um appliance virtual, com opções para implementação local ou na nuvem. Consulte a lista de plataformas de visualização compatíveis em "[Configurar uma instância do GitHub Enterprise Server](/enterprise-server@latest/admin/installation/setting-up-a-github-enterprise-server-instance)". -{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Alertas de Segurança{% endif %} e {% data variables.product.prodname_github_connect %} não estão disponíveis atualmente nos testes de {% data variables.product.prodname_ghe_server %}. Para uma demonstração desses recursos, entre em contato com {% data variables.contact.contact_enterprise_sales %}. For more information about these features, see "[About {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" and "[Connecting your enterprise account to {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)." +{% ifversion ghes %}{% data variables.product.prodname_dependabot %}{% else %}Alertas de Segurança{% endif %} e {% data variables.product.prodname_github_connect %} não estão disponíveis atualmente nos testes de {% data variables.product.prodname_ghe_server %}. Para uma demonstração desses recursos, entre em contato com {% data variables.contact.contact_enterprise_sales %}. Para obter mais informações sobre essas funcionalidades, consulte "[Sobre {% data variables.product.prodname_dependabot_alerts %}](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)" e "[Conectando sua conta corporativa a {% data variables.product.prodname_ghe_cloud %}](/enterprise-server@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud)". As versões de avaliação também estão disponíveis para {% data variables.product.prodname_ghe_cloud %}. Para obter mais informações, consulte "[Configurar uma versão de avaliação do {% data variables.product.prodname_ghe_cloud %}](/articles/setting-up-a-trial-of-github-enterprise-cloud)". diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md index c8e6d27bac..57693d2503 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks.md @@ -70,7 +70,7 @@ Usamos [Linguist](https://github.com/github/linguist) para executar a detecção {% if mermaid %} ## Criando diagramas -You can also use code blocks to create diagrams in Markdown. GitHub supports Mermaid, geoJSON, topoJSON, and ASCII STL syntax. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)". +Você também pode usar blocos de código para criar diagramas em Markdown. O GitHub é compatível com a sintaxe do Mermaid, geoJSON, topoJSON e ASCII STL. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams)". {% endif %} ## Leia mais diff --git a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md index f2007ab548..4fd49d27e1 100644 --- a/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md +++ b/translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams.md @@ -6,11 +6,11 @@ versions: shortTitle: Crie diagramas --- -## About creating diagrams +## Sobre a criação de diagramas -You can create diagrams in Markdown using three different syntaxes: mermaid, geoJSON and topoJSON, and ASCII STL. +Você pode criar diagramas em Markdown usando três sintaxes diferentes: mermaid, geoJSON e topoJSON e ASCII STL. -## Creating Mermaid diagrams +## Criando diagramas do mermaid O Mermeid é uma ferramenta inspirada em Markdown que transforma texto em diagramas. Por exemplo, o Mermeid pode interpretar gráficos de fluxo, diagramas de sequência, gráficos de pizza e muito mais. Para obter mais informações, consulte a documentação do [Mermaid](https://mermaid-js.github.io/mermaid/#/). @@ -38,13 +38,13 @@ graph TD; {% endnote %} -## Creating geoJSON and topoJSON maps +## Criando mapas do geoJSON e topoJSON -You can use geo/topoJSON syntax to create interactive maps. To create a map, add geoJSON or topoJSON inside a fenced code block with the `geojson` or `topojson` syntax identifier. Para obter mais informações, consulte "[Criar e destacar blocos de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)". +Você pode usar a sintaxe geo/topoJSON para criar mapas interativos. Para criar um mapa, adicione geoJSON ou topoJSON dentro de um bloco de código cercado com o identificador de sintaxe de `geojson` ou `topojson`. Para obter mais informações, consulte "[Criar e destacar blocos de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)". -### Using geoJSON +### Usando geoJSON -For example, you can create a simple map: +Por exemplo, você pode criar um mapa simples: 
 ```geojson
@@ -63,11 +63,11 @@ For example, you can create a simple map:
 ```
-![Rendered map](/assets/images/help/writing/fenced-geojson-rendered-map.png) +![Mapa interpretado](/assets/images/help/writing/fenced-geojson-rendered-map.png) -### Using topoJSON +### Usando topoJSON -For example, you can create a simple topoJSON map: +Por exemplo, você pode criar um mapa topoJSON simples: 
 ```topojson
@@ -106,16 +106,16 @@ For example, you can create a simple topoJSON map:
 ```
-![Rendered topojson map](/assets/images/help/writing/fenced-topojson-rendered-map.png) +![Mapa do topojson interpretado](/assets/images/help/writing/fenced-topojson-rendered-map.png) -For more information on working with `.geojson` and `.topojson` files, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)." +Para obter mais informações sobre como trabalhar com arquivos `.geojson` e `.topojson`, consulte[Trabalhando com arquivos que não são de código](/repositories/working-with-files/using-files/working-with-non-code-files#mapping-geojson-files-on-github)". -## Creating STL 3D models +## Criando modelos de STL 3D -You can use ASCII STL syntax directly in markdown to create interactive 3D models. To display a model, add ASCII STL syntax inside a fenced code block with the `stl` syntax identifier. Para obter mais informações, consulte "[Criar e destacar blocos de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)". +Você pode usar a sintaxe do ASCII STL diretamente no markdown para criar modelos 3D interativos. Para exibir um modelo, adicione a sintaxe ASCII STL dentro de um bloco de código isolado com o identificador de sintaxe `stl`. Para obter mais informações, consulte "[Criar e destacar blocos de código](/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks)". -For example, you can create a simple 3D model: +Por exemplo, você pode criar um modelo 3D simples: 
 ```stl
@@ -152,7 +152,7 @@ endsolid
 ```
-![Rendered 3D model](/assets/images/help/writing/fenced-stl-rendered-object.png) +![Modelo 3D interpretado](/assets/images/help/writing/fenced-stl-rendered-object.png) -For more information on working with `.stl` files, see "[Working with non-code files](/repositories/working-with-files/using-files/working-with-non-code-files#3d-file-viewer)." +Para mais informações sobre como trabalhar com arquivos `.stl`, consulte[Trabalhando com arquivos que não são de código](/repositories/working-with-files/using-files/working-with-non-code-files#3d-file-viewer)". diff --git a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md index 3059e94b4d..f259df5ec1 100644 --- a/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md +++ b/translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md @@ -122,7 +122,7 @@ Você pode habilitar ou desabilitar funcionalidades para todos os repositórios. Por padrão, {% data variables.product.prodname_dependabot %} não pode atualizar as dependências que estão localizadas em repositórios privados ou registros de pacotes privados. Entretanto, se uma dependência estiver em um repositório privado de {% data variables.product.prodname_dotcom %} dentro da mesma organização que o projeto que usa essa dependência, você pode permitir que {% data variables.product.prodname_dependabot %} atualize a versão com sucesso, dando-lhe acesso à hospedagem do repositório. -Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +Se seu código depende de pacotes em um registro privado, você pode permitir que {% data variables.product.prodname_dependabot %} atualize as versões dessas dependências configurando isso no nível do repositório. Você faz isso adicionando detalhes de autenticação ao arquivo _dependabot.yml_ do repositório. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". Para permitir que {% data variables.product.prodname_dependabot %} acesse um repositório privado de {% data variables.product.prodname_dotcom %}: @@ -157,5 +157,5 @@ Você pode gerenciar o acesso a funcionalidades de {% data variables.product.pro - "[Protegendo o seu repositório](/code-security/getting-started/securing-your-repository)"{% ifversion not fpt %} - "[Sobre a verificação de segredo](/github/administering-a-repository/about-secret-scanning)"{% endif %}{% ifversion not ghae %} -- "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} -- "[About supply chain security](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} +- "[Sobre o gráfico de dependências](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)"{% endif %}{% ifversion fpt or ghec or ghes or ghae-issue-4864 %} +- "[Sobre a segurança da cadeia de suprimentos](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-supply-chain-security)"{% endif %} diff --git a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index a1d8431e37..e9c4bd2c00 100644 --- a/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/pt-BR/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -108,40 +108,40 @@ Para resolver o acesso conflitante, você pode ajustar as permissões básicas d - "[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)" - "[Editando uma função do repositório](#editing-a-repository-role)" -## Creating a repository role +## Criando a função de um repositório -To create a new repository role, you add permissions to an inherited role and give the custom role a name. +Para criar uma nova função do repositório, você deve adicionar permissões a uma função herdada e dar um nome à função personalizada. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) -4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) -5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) -6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) -7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) -7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) +5. Clique **Criar uma função**. ![Captura de tela do botão "Criar uma função"](/assets/images/help/organizations/repository-role-create-role.png) +4. Em "Nome", digite o nome da função do seu repositório. ![Campo para digitar um nome para a função de um repositório](/assets/images/help/organizations/repository-role-name.png) +5. Em "Descrição", digite uma descrição da função do repositório. ![Campo para digitar uma descrição para o papel do repositório](/assets/images/help/organizations/repository-role-description.png) +6. Em "Escolha uma função para herdar", selecione a função que deseja herdar. ![Selecionando a opção da função de base do repositório](/assets/images/help/organizations/repository-role-base-role-option.png) +7. Em "Adicionar permissões", use o menu suspenso para selecionar as permissões que você deseja que a sua função personalizada inclua. ![Selecionando níveis de permissão da função a partir do menu suspenso da função do repositório](/assets/images/help/organizations/repository-role-drop-down.png) +7. Clique em **Criar função**. ![Confirmar a criação de função de repositório](/assets/images/help/organizations/repository-role-creation-confirm.png) -## Editing a repository role +## Editando a função de um repositório {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) -4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) +3. À direita da função que você deseja editar, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Editar**. ![Editar opção no menu suspenso para funções de repositório](/assets/images/help/organizations/repository-role-edit-setting.png) +4. Edite e, em seguida, clique em **Atualizar função**. ![Editar campos e atualizar funções do repositório](/assets/images/help/organizations/repository-role-update.png) -## Deleting a repository role +## Excluindo a função de um repositório -If you delete an existing repository role, all pending invitations, teams, and users with the custom role will be reassigned to the organization's base permissions. +Se você excluir a função de um repositório existente, todos os convites pendentes, equipes e usuários com a função personalizada serão reatribuidos às permissões básicas da organização. {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) +3. À direita da função que você deseja excluir, clique em {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %} e, em seguida, clique em **Excluir**. ![Editar opção no menu suspenso para funções de repositório](/assets/images/help/organizations/repository-role-delete-setting.png) 4. Revise as alterações para a função que você deseja remover e, em seguida, clique em **Excluir função**. ![Confirme a exclusão de uma função do repositório](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md index e17c67b115..1852cc5437 100644 --- a/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md +++ b/translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -52,7 +52,7 @@ Antes de usar o Jekyll para testar um site, você deve: {% note %} -**Note:** If you are using Ruby 3.0 and Jekyll 4.2.x or older, you will need to add the `webrick` gem to your project's Gemfile prior to running `bundle install`. +**Observação:** Se você estiver usando o Ruby 3.0 e Jekyll 4.2 ou versão anterior, você deverá adicionar o gem do `webrick` ao arquivo do seu projeto antes de executar `bundle install`. {% endnote %} diff --git a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index f80dd0d34d..f40e97b670 100644 --- a/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -17,9 +17,11 @@ topics: shortTitle: Solicitar revisão de PR --- -Proprietários e colaboradores de um repositório pertencente a uma conta de usuário podem atribuir revisões de pull requests. Os integrantes da organização com permissões de triagem em um repositório podem atribuir uma revisão de pull request. +Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). Para obter mais informações, consulte "[Tipos de contas de {% data variables.product.prodname_dotcom %}](/get-started/learning-about-github/types-of-github-accounts)". Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request. -Os proprietários e colaboradores podem atribuir uma revisão de pull request a qualquer pessoa que recebeu explicitamente [acesso de leitura](/articles/access-permissions-on-github) em um repositório pertencente a um usuário. Os integrantes da organização podem atribuir uma revisão de pull request para qualquer pessoa ou equipe com acesso de leitura em um repositório. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% ifversion fpt or ghae or ghes or ghec %}Se você solicitar uma revisão de uma equipe e a atribuição de revisão de código estiver ativada, integrantes específicos serão solicitados e a equipe será removida como revisora. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %} +To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. + +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. O revisor ou a equipe receberão uma notificação informando que você solicitou a revisão de uma pull request. {% ifversion fpt or ghae or ghes or ghec %}Se você solicitar uma revisão de uma equipe e a atribuição de revisão de código estiver ativada, integrantes específicos serão solicitados e a equipe será removida como revisora. Para obter mais informações, consulte "[Gerenciando configurações de revisão de código para sua equipe](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)".{% endif %} {% note %} diff --git a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 61f927b13a..d172f0cbf3 100644 --- a/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/pt-BR/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -38,7 +38,7 @@ Cada arquivo CODEOWNERS atribui os proprietários do código para um único bran Para que os proprietários do código recebam solicitações de revisão, o arquivo CODEOWNERS deve estar no branch base da pull request. Por exemplo, se você atribuir `@octocat` como o proprietário do código para arquivos *.js* no branch `gh-pages` do seu repositório, `@octocat` receberá solicitações de revisão quando uma pull request com alterações nos arquivos *.js* for aberta entre o branch head e `gh-pages`. -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %} ## Tamanho do arquivo CODEOWNERS Os arquivos CODEOWNERS devem ter menos de 3 MB. Um arquivo CODEOWNERS acima deste limite não será carregado, o que significa que as informações do proprietário do código não serão mostradas e não será solicitado que os proprietários do código apropriado revise as alterações em um pull request. diff --git a/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index 8ff77db4bd..9c84b433b3 100644 --- a/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/translations/pt-BR/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -7,7 +7,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae-issue-4974: '*' + ghae: issue-4974 topics: - Repositories --- diff --git a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md index 5d7b8505e4..206dae6014 100644 --- a/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md +++ b/translations/pt-BR/content/repositories/working-with-files/using-files/working-with-non-code-files.md @@ -131,9 +131,9 @@ Por padrão, o renderizador incorporado tem 420 pixels de largura por 620 pixels {% endtip %} {% if mermaid %} -### Rendering in Markdown +### Interpretação em Markdown -You can embed ASCII STL syntax directly in Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-stl-3d-models)". +Você pode incorporar a sintaxe do ASCII STL diretamente ao Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-stl-3d-models)". {% endif %} ## Renderizar dados CSV e TSV @@ -239,7 +239,7 @@ Quando você clicar no ícone de folha de papel à direita, também verá as alt ![Captura de tela seletor Source Render (Renderizar fonte)](/assets/images/help/repository/source-render-toggle-geojson.png) -### Geometry types +### Tipos de geometria Os mapas no {% data variables.product.product_name %} usam [Leaflet.js](http://leafletjs.com) e são compatíveis com todos os tipos geométricos descritos nas [especificações geoJSON](http://www.geojson.org/geojson-spec.html) (Ponto, LineString, Polígono, Múltiplos Pontos, MultiLineString, MultiPolygon e GeometryCollection). Os arquivos TopoJSON devem ser do tipo "Topology" (Topologia) e estar de acordo com as [especificações topoJSON](https://github.com/mbostock/topojson/wiki/Specification). @@ -281,9 +281,9 @@ Por padrão, o mapa incorporado tem 420px x 620px, mas é possível personalizar {% endtip %} {% if mermaid %} -### Mapping in Markdown +### Mapeamento em Markdown -You can embed geoJSON and topoJSON directly in Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)". +Você pode incorporar geoJSON e topoJSON diretamente ao Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-geojson-and-topojson-maps)". {% endif %} ### Clustering @@ -334,11 +334,11 @@ $ jupyter nbconvert --to html NOTEBOOK-NAME.ipynb - [Galeria de Jupyter Notebooks](https://github.com/jupyter/jupyter/wiki/A-gallery-of-interesting-Jupyter-Notebooks) {% if mermaid %} -## Displaying Mermaid files on {% data variables.product.prodname_dotcom %} +## Exibindo arquivos do Mermaid em {% data variables.product.prodname_dotcom %} -{% data variables.product.product_name %} supports rendering Mermaid files within repositories. Commit the file as you would normally using a `.mermaid` or `.mmd` extension. Then, navigate to the path of the Mermaid file on {% data variables.product.prodname_dotcom %}. +{% data variables.product.product_name %} é compatível com os arquivos de interpretação do Mermaid dentro dos repositórios. Faça o commit do arquivo como você faria normalmente, usando a extensão `.mermaid` ou `.mmd`. Em seguida, acesse o caminho do arquivo do Mermaid em {% data variables.product.prodname_dotcom %}. -For example, if you add a `.mmd` file with the following content to your repository: +Por exemplo, se você adicionar um arquivo `.mmd` com o seguinte conteúdo para o repositório: ``` graph TD @@ -349,27 +349,27 @@ graph TD C -->|Three| F[fa:fa-car Car] ``` -When you view the file in the repository, it is rendered as a flow chart. ![Rendered mermaid file diagram](/assets/images/help/repository/mermaid-file-diagram.png) +Ao visualizar o arquivo no repositório, ele é interpretado como um gráfico de fluxo. ![Diagrama de arquivo do mermaid interpretado](/assets/images/help/repository/mermaid-file-diagram.png) ### Solução de Problemas -If your chart does not render at all, verify that it contains valid Mermaid Markdown syntax by checking your chart with the [Mermaid live editor](https://mermaid.live/edit). +Se o seu gráfico não faz nenhuma interpretação, verifique se ele contém uma sintaxe válida do Markdown do Mermaid, verificando sua carta com [editor ativo do Mermaid](https://mermaid.live/edit). -If the chart displays, but does not appear as you'd expect, you can create a new [feedback discussion](https://github.com/github/feedback/discussions/categories/general-feedback), and add the `mermaid` tag. +Se o gráfico é exibido, mas não aparece como você esperava, você pode criar uma nova discussão de feedback [](https://github.com/github/feedback/discussions/categories/general-feedback) e adicionar a tag `mermaid`. #### Problemas conhecidos -* Sequence diagram charts frequently render with additional padding below the chart, with more padding added as the chart size increases. This is a known issue with the Mermaid library. -* Actor nodes with popover menus do not work as expected within sequence diagram charts. This is due to a discrepancy in how JavaScript events are added to a chart when the Mermaid library's API is used to render a chart. -* Not all charts are a11y compliant. This may affect users who rely on a screen reader. +* O gráfico do diagrama de sequência é frequentemente interpretado com preenchimento adicional abaixo do gráfico, com preenchimento adicional acrescentado à medida que o tamanho do gráfico aumenta. Este é um problema conhecido com a biblioteca do Mermaid. +* Os nós do ator com menus popover não funcionam como esperado dentro de gráficos de diagrama de sequência. Isto se deve uma discrepância na forma como eventos do JavaScript são adicionados a um gráfico quando a API da biblioteca do Mermaid é usada para interpretar um gráfico. +* Nem todos os gráficos são conformes com a11y. Isso pode afetar os usuários que dependem de um leitor de tela. -### Mermaid in Markdown +### Mermaid no Markdown -You can embed Mermaid syntax directly in Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams)". +Você pode incorporar a sintaxe do Mermaid diretamente no Markdown. Para obter mais informações, consulte "[Criando diagramas](/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams)". ### Leia mais -* [Mermaid.js documentation](https://mermaid-js.github.io/mermaid/#/) -* [Mermaid.js live editor](https://mermaid.live/edit) +* [Documentação do Mermaid.js](https://mermaid-js.github.io/mermaid/#/) +* [Editor ativo do Mermaid.js](https://mermaid.live/edit) {% endif %} diff --git a/translations/pt-BR/content/rest/reference/deploy_keys.md b/translations/pt-BR/content/rest/reference/deploy_keys.md index 2a49dbdf47..03aca4d663 100644 --- a/translations/pt-BR/content/rest/reference/deploy_keys.md +++ b/translations/pt-BR/content/rest/reference/deploy_keys.md @@ -1,6 +1,6 @@ --- -title: Deploy Keys -intro: 'The Deploy Keys API allows to create an SSH key that is stored on your server and grants access to a GitHub repository.' +title: Chave de implantação +intro: A API das chaves de implantação permite criar uma chave de SSH que é armazenada no seu servidor e permite acesso a um repositório do GitHub. allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -14,4 +14,4 @@ miniTocMaxHeadingLevel: 3 \ No newline at end of file +--> diff --git a/translations/pt-BR/content/rest/reference/deployments.md b/translations/pt-BR/content/rest/reference/deployments.md index 02a45f7f5e..4a1aaf921c 100644 --- a/translations/pt-BR/content/rest/reference/deployments.md +++ b/translations/pt-BR/content/rest/reference/deployments.md @@ -1,6 +1,6 @@ --- title: Implantações -intro: The deployments API allows you to create and delete deployments and deployment environments. +intro: A API de implantações permite que você crie e exclua implantações e ambientes de implantação. allowTitleToDifferFromFilename: true versions: fpt: '*' diff --git a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md index ff0f9a249d..90dea21aac 100644 --- a/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md +++ b/translations/pt-BR/content/site-policy/github-terms/github-community-guidelines.md @@ -45,7 +45,7 @@ Embora alguns desacordos possam ser resolvidos com comunicação direta e respei * **Bloquear Usuários** - Se você encontrar um usuário específico com quem você prefere não se relacionar, você pode [bloquear o usuário na sua conta pessoal](/articles/blocking-a-user-from-your-personal-account/) ou [na sua organização](/articles/blocking-a-user-from-your-organization/). -* **Limit Interactions** - If your public project is getting unwanted attention, being trolled, spammed, or otherwise, you have the option of setting [temporary interaction limits](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) to keep certain users from interacting with your repository. Você pode até mesmo definir [limites de revisão de código](https://github.blog/2021-11-01-github-keeps-getting-better-for-open-source-maintainers/#preventing-drive-by-pull-request-approvals-and-requested-changes) para garantir contribuições de qualidade nos seus projetos. +* **Limite de interações** - Se seu projeto público estiver recebendo atenção indesejada, sendo ridicularizado, recebendo spam ou se você não tiver a opção de configurar [limites temporários de interação](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository) para impedir que certos usuários interajam com seu repositório. Você pode até mesmo definir [limites de revisão de código](https://github.blog/2021-11-01-github-keeps-getting-better-for-open-source-maintainers/#preventing-drive-by-pull-request-approvals-and-requested-changes) para garantir contribuições de qualidade nos seus projetos. Embora sejamos apaixonados por capacitar os mantenedores a moderar os seus próprios projetos, entre em contato conosco por {% data variables.contact.report_abuse %} se precisar de apoio adicional para lidar com uma situação. diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml index e239d7dff7..9a68bab074 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml @@ -78,6 +78,7 @@ sections: - A versão mais recente do CLI do CodeQL é compatível com o upload dos resultados da análise para o GitHub. Isso facilita a execução da análise de código para clientes que desejem usar sistemas de CI/CD diferentes de {% data variables.product.prodname_actions %}. Anteriormente, esses usuários tinham de usar o executor do CodeQL separado, que continuará disponível. Para obter mais informações, consulte "[Sobre o escaneamento de código CodeQL no seu sistema de CI](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - '{% data variables.product.prodname_actions %} agora é compatível com a ação de ignorar os fluxos de trabalho `push` e `pull_request`, ao procurar algumas palavras-chave comuns na sua mensagem de commit.' - Serão arquivadas as anotações com mais de quatro meses de anotações de verificação. + - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - heading: Alterações de segurança notes: diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml index 5974ae027a..78b6c13d56 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml @@ -60,7 +60,7 @@ sections: - heading: Alterações na administração notes: - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - Uma definição da 'Política de Indicação de Agente de Usuário' foi adicionada às configurações da empresa. Isso permite que um administrador defina uma `Política de Indicação-` mais rigorosa para ocultar o nome do host de uma instalação de {% data variables.product.prodname_ghe_server %} a partir de sites externos. A configuração está desabilitada por padrão e é rastreada pelos eventos de log de auditoria para funcionários e proprietários da empresa quando habilitado ou desabilitado. Para obter mais informações, consulte "[Configurar a Política de Indicação para a sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - A verificação de integridade do MySQL foi alterada para usar `mysqladmin ping` em vez de verificações TCP, o que remove algum ruído desnecessário no registro de erros do MySQL. Além disso, as verificações de falha do Orchestrator foram aprimoradas para evitar falhas desnecessárias do MySQL ao aplicar alterações de configuração de cluster. - 'O serviço do Resque, que é compatível com o processamento de trabalhos em segundo plano, foi substituído pelo Aqueduct Lite. Esta alteração facilita o gerenciamento do sistema de trabalho e não deve afetar a experiência do usuário. Para os novos comandos de administração e depuração para Aqueduct, consulte "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' - diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml index adabd988a2..d582fc578c 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml @@ -58,7 +58,7 @@ sections: - heading: Alterações na administração notes: - - A 'User Agent Referrer Policy' setting has been added to the enterprise settings. This allows an admin to set a stricter `Referrer-Policy` to hide the hostname of a {% data variables.product.prodname_ghe_server %} installation from external sites. The setting is disabled by default and is tracked by audit log events for staff and enterprise owners when enabled or disabled. For more information, see "[Configuring Referrer Policy for your enterprise](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." + - Uma definição da 'Política de Indicação de Agente de Usuário' foi adicionada às configurações da empresa. Isso permite que um administrador defina uma `Política de Indicação-` mais rigorosa para ocultar o nome do host de uma instalação de {% data variables.product.prodname_ghe_server %} a partir de sites externos. A configuração está desabilitada por padrão e é rastreada pelos eventos de log de auditoria para funcionários e proprietários da empresa quando habilitado ou desabilitado. Para obter mais informações, consulte "[Configurar a Política de Indicação para a sua empresa](/admin/configuration/configuring-your-enterprise/configuring-the-referrer-policy-for-your-enterprise)." - A verificação de integridade do MySQL foi alterada para usar `mysqladmin ping` em vez de verificações TCP, o que remove algum ruído desnecessário no registro de erros do MySQL. Além disso, as verificações de falha do Orchestrator foram aprimoradas para evitar falhas desnecessárias do MySQL ao aplicar alterações de configuração de cluster. - 'O serviço do Resque, que é compatível com o processamento de trabalhos em segundo plano, foi substituído pelo Aqueduct Lite. Esta alteração facilita o gerenciamento do sistema de trabalho e não deve afetar a experiência do usuário. Para os novos comandos de administração e depuração para Aqueduct, consulte "[Utilitários de linha de comando](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-aqueduct)."' - diff --git a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml index 3c5ccb44e3..0f21e64cc9 100644 --- a/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml @@ -29,6 +29,11 @@ sections: notes: - | {% data variables.product.prodname_dependabot %} agora está disponível em {% data variables.product.prodname_ghe_server %} 3.4 como beta público, oferecendo atualizações de versão e segurança para vários ecossistemas populares. {% data variables.product.prodname_dependabot %} em {% data variables.product.prodname_ghe_server %} exige {% data variables.product.prodname_actions %} e um grupo de executores auto-hospedados configurado para uso de {% data variables.product.prodname_dependabot %}. {% data variables.product.prodname_dependabot %} em {% data variables.product.prodname_ghe_server %} também exige {% data variables.product.prodname_github_connect %} e {% data variables.product.prodname_dependabot %} para ser habilitado por um administrador. Feedback de beta e sugestões podem ser compartilhados na [discussão de feedback do GitHub{% data variables.product.prodname_dependabot %}](https://github.com/github/feedback/discussions/categories/dependabot-feedback). Para obter mais informações e testar a versão beta, consulte "[Configurar {% data variables.product.prodname_dependabot %} de segurança e versão de atualizações](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + - + heading: SAML authentication supports encrypted assertions + notes: + - | + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." changes: - heading: Alterações na administração diff --git a/translations/pt-BR/data/reusables/actions/github-connect-resolution.md b/translations/pt-BR/data/reusables/actions/github-connect-resolution.md index 816e314a30..b313096713 100644 --- a/translations/pt-BR/data/reusables/actions/github-connect-resolution.md +++ b/translations/pt-BR/data/reusables/actions/github-connect-resolution.md @@ -1 +1 @@ -When a workflow uses an action by referencing the repository where the action is stored, {% data variables.product.prodname_actions %} will first try to find the repository on {% data variables.product.product_location %}. If the repository does not exist on {% data variables.product.product_location %}, and if you have automatic access to {% data variables.product.prodname_dotcom_the_website %} enabled, {% data variables.product.prodname_actions %} will try to find the repository on {% data variables.product.prodname_dotcom_the_website %}. \ No newline at end of file +Quando um fluxo de trabalho usa uma ação, fazendo referência ao repositório onde a ação é armazenada, {% data variables.product.prodname_actions %} primeiro tentará encontrar o repositório em {% data variables.product.product_location %}. Se o repositório não existir em {% data variables.product.product_location %} e se você tiver acesso automático para {% data variables.product.prodname_dotcom_the_website %} habilitado, {% data variables.product.prodname_actions %} tentará encontrar o repositório em {% data variables.product.prodname_dotcom_the_website %}. \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md b/translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md index 41c69fec07..e49adc1642 100644 --- a/translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md +++ b/translations/pt-BR/data/reusables/actions/private-repository-forks-overview.md @@ -1 +1 @@ -Se você depende do uso das bifurcações dos seus repositórios privados, você pode configurar políticas que controlam como os usuários podem executar fluxos de trabalho em eventos `pull_request`. Available to private {% ifversion ghec or ghes or ghae %}and internal{% endif %} repositories only, you can configure these policy settings for {% ifversion ghec %}enterprises, {% elsif ghes or ghae %}your enterprise, {% endif %}organizations, or repositories. +Se você depende do uso das bifurcações dos seus repositórios privados, você pode configurar políticas que controlam como os usuários podem executar fluxos de trabalho em eventos `pull_request`. Disponível apenas para {% ifversion ghec or ghes or ghae %}e repositórios internos de{% endif %}, você pode configurar essas configurações de política para {% ifversion ghec %}empresas, {% elsif ghes or ghae %}sua empresa, {% endif %}organizações ou repositórios. diff --git a/translations/pt-BR/data/reusables/actions/ref_name-description.md b/translations/pt-BR/data/reusables/actions/ref_name-description.md index 4a39dc1922..a57beeadee 100644 --- a/translations/pt-BR/data/reusables/actions/ref_name-description.md +++ b/translations/pt-BR/data/reusables/actions/ref_name-description.md @@ -1 +1 @@ -The branch or tag name that triggered the workflow run. +O nome da branch ou tag que acionou a execução do fluxo de trabalho. diff --git a/translations/pt-BR/data/reusables/actions/ref_protected-description.md b/translations/pt-BR/data/reusables/actions/ref_protected-description.md index 9975dc406a..04b9cfdbfa 100644 --- a/translations/pt-BR/data/reusables/actions/ref_protected-description.md +++ b/translations/pt-BR/data/reusables/actions/ref_protected-description.md @@ -1 +1 @@ -`true` if branch protections are configured for the ref that triggered the workflow run. +`verdadeiro` se as proteções dos branches estiverem configuradas para o ref, que acionou a execução do fluxo de trabalho. diff --git a/translations/pt-BR/data/reusables/actions/ref_type-description.md b/translations/pt-BR/data/reusables/actions/ref_type-description.md index 74888dee73..8ad52dfbc9 100644 --- a/translations/pt-BR/data/reusables/actions/ref_type-description.md +++ b/translations/pt-BR/data/reusables/actions/ref_type-description.md @@ -1 +1 @@ -The type of ref that triggered the workflow run. Valid values are `branch` or `tag`. +O tipo de ref que acionou a execução do fluxo de trabalho. Os valores válidos são `branch` ou `tag`. diff --git a/translations/pt-BR/data/reusables/actions/registry-credentials.md b/translations/pt-BR/data/reusables/actions/registry-credentials.md index 52c09696d7..ebeadd3b98 100644 --- a/translations/pt-BR/data/reusables/actions/registry-credentials.md +++ b/translations/pt-BR/data/reusables/actions/registry-credentials.md @@ -1 +1 @@ -If the image's container registry requires authentication to pull the image, you can use `jobs..container.credentials` to set a `map` of the `username` and `password`. As credenciais são os mesmos valores que você forneceria para o comando [`login do docker`](https://docs.docker.com/engine/reference/commandline/login/). +Se o registro de contêiner da imagem exigir autenticação para extrair a imagem, você pode usar as funções de `..container.credentials` para definir um `mapa` do `nome de usuário` e `senha`. As credenciais são os mesmos valores que você forneceria para o comando [`login do docker`](https://docs.docker.com/engine/reference/commandline/login/). diff --git a/translations/pt-BR/data/reusables/actions/restrict-runner-workflow-beta.md b/translations/pt-BR/data/reusables/actions/restrict-runner-workflow-beta.md index 77949eb08b..c81dc5a793 100644 --- a/translations/pt-BR/data/reusables/actions/restrict-runner-workflow-beta.md +++ b/translations/pt-BR/data/reusables/actions/restrict-runner-workflow-beta.md @@ -1,7 +1,7 @@ {% if restrict-groups-to-workflows %} {% note %} -**Note:** Configuring the workflows that can access a runner group is currently in beta and subject to change. +**Nota:** A configuração dos fluxos de trabalho que podem acessar um grupo de executores está atualmente na versão beta e sujeita a alterações. {% endnote %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md b/translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md index e842a2b090..dc5018fc5b 100644 --- a/translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md +++ b/translations/pt-BR/data/reusables/actions/reusable-workflow-calling-syntax.md @@ -1,4 +1,4 @@ -* `{owner}/{repo}/{path}/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %} for reusable workflows in public {% ifversion ghes or ghec or ghae %}or internal{% endif %} repositories. -* `./{path}/{filename}` for reusable workflows in the same repository.{% endif %} +* `{owner}/{repo}/{path}/{filename}@{ref}`{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %} para fluxos de trabalho nos repositórios públicos {% ifversion ghes or ghec or ghae %}or internos{% endif %}. +* `./{path}/{filename}` para fluxos de trabalho reutilizáveis no mesmo repositório.{% endif %} -`{ref}` pode ser um SHA, uma tag de de versão ou um nome de branch. Usar o commit SHA é o mais seguro para a estabilidade e segurança. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %}If you use the second syntax option (without `{owner}/{repo}` and `@{ref}`) the called workflow is from the same commit as the caller workflow.{% endif %} +`{ref}` pode ser um SHA, uma tag de de versão ou um nome de branch. Usar o commit SHA é o mais seguro para a estabilidade e segurança. Para obter mais informações, consulte "[Enrijecimento de segurança para o GitHub Actions](/actions/learn-github-actions/security-hardening-for-github-actions#reusing-third-party-workflows)". {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6000 %}se você usar a segunda opção de sintaxe (sem `{owner}/{repo}` e `@{ref}`), o fluxo de trabalho chamado é do mesmo commit que o fluxo de trabalho de chamada.{% endif %} diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md b/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md index 6fb3ef2e4f..ab0cad1bf7 100644 --- a/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md +++ b/translations/pt-BR/data/reusables/actions/reusable-workflows-ghes-beta.md @@ -2,7 +2,7 @@ {% note %} -**Note**: Reusable workflows are currently in beta and subject to change. +**Observação**: Os fluxos de trabalho reutilizáveis estão atualmente na versão beta e sujeitos a alterações. {% endnote %} diff --git a/translations/pt-BR/data/reusables/actions/reusable-workflows.md b/translations/pt-BR/data/reusables/actions/reusable-workflows.md index 958dad192c..d0bdd01da3 100644 --- a/translations/pt-BR/data/reusables/actions/reusable-workflows.md +++ b/translations/pt-BR/data/reusables/actions/reusable-workflows.md @@ -1,4 +1,4 @@ {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %} -{% ifversion ghes or ghec or ghae %}You can share workflows with your organization, publicly or privately, by calling{% else %} You can call{% endif %} one workflow from within another workflow. Isso permite a reutilização de fluxos de trabalho, evitando duplicação e tornando seus fluxos de trabalho mais fáceis de manter. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". +{% ifversion ghes or ghec or ghae %}Você pode compartilhar fluxos de trabalho com sua organização, pública ou privadamente, chamando{% else %} Você pode chamar{% endif %} um fluxo de trabalho de dentro de outro fluxo de trabalho. Isso permite a reutilização de fluxos de trabalho, evitando duplicação e tornando seus fluxos de trabalho mais fáceis de manter. Para obter mais informações, consulte "[Reutilizando fluxos de trabalho](/actions/learn-github-actions/reusing-workflows)". {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/run_id_description.md b/translations/pt-BR/data/reusables/actions/run_id_description.md index 0d222af4ae..179bb1229e 100644 --- a/translations/pt-BR/data/reusables/actions/run_id_description.md +++ b/translations/pt-BR/data/reusables/actions/run_id_description.md @@ -1 +1 @@ -A unique number for each workflow run within a repository. Este número não muda se você executar novamente o fluxo de trabalho. +Um número exclusivo para cada fluxo de trabalho executado em um repositório. Este número não muda se você executar novamente o fluxo de trabalho. diff --git a/translations/pt-BR/data/reusables/actions/runner-arch-description.md b/translations/pt-BR/data/reusables/actions/runner-arch-description.md index 60a9d02739..09c886d08b 100644 --- a/translations/pt-BR/data/reusables/actions/runner-arch-description.md +++ b/translations/pt-BR/data/reusables/actions/runner-arch-description.md @@ -1 +1 @@ -The architecture of the runner executing the job. Possible values are `X86`, `X64`, `ARM`, or `ARM64`. +A arquitetura do executor que está executando o trabalho. Os valores poss[iveis são `X86`, `X64`, `ARM` ou `ARM64`. diff --git a/translations/pt-BR/data/reusables/actions/runner-tool-cache-description.md b/translations/pt-BR/data/reusables/actions/runner-tool-cache-description.md index 956500fdcb..1afa28cebb 100644 --- a/translations/pt-BR/data/reusables/actions/runner-tool-cache-description.md +++ b/translations/pt-BR/data/reusables/actions/runner-tool-cache-description.md @@ -1 +1 @@ -O caminho para o diretório que contém ferramentas pré-instaladas para executores hospedados em {% data variables.product.prodname_dotcom %}. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". +O caminho para o diretório que contém ferramentas pré-instaladas para executores hospedados em {% data variables.product.prodname_dotcom %}. Para obter mais informações, consulte "[Sobre executores hospedados em {% data variables.product.prodname_dotcom %}](/actions/reference/specifications-for-github-hosted-runners/#supported-software)". diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md index e8dafca686..3233cf5b48 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-check-installation-success.md @@ -1,8 +1,8 @@ ### Verificando se o seu executor auto-hospedado foi adicionado com sucesso -After completing the steps to add a self-hosted runner, the runner and its status are now listed under {% ifversion fpt or ghec %}"Runners"{% elsif ghae or ghes %}"Self-hosted runners"{% endif %}. +Depois de completar as etapas para adicionar um executor auto-hospedado, o executor e seu status serão listados em {% ifversion fpt or ghec %}"Runners"{% elsif ghae or ghes %}"Executores auto-hospedados"{% endif %}. -A aplicação dos executores auto-hospedados deve estar activa para que o executor aceite os trabalhos. When the runner application is connected to {% data variables.product.product_name %} and ready to receive jobs, you will see the following message on the machine's terminal. +A aplicação dos executores auto-hospedados deve estar activa para que o executor aceite os trabalhos. Quando o aplicativo do executor estiver conectado a {% data variables.product.product_name %} e pronto para receber trabalhos, você verá a seguinte mensagem no terminal da máquina. {% data reusables.actions.self-hosted-runner-connected-output %} diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md index c84ca8a027..5c0b2a2e09 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md @@ -1,5 +1,5 @@ {% data reusables.actions.self-hosted-runner-configure-runner-group %} -1. Modify your policy options. +1. Modifique suas opções de política. {% ifversion not ghae %} {% warning %} diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md index 450f4fd390..029c537cf1 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-navigate-to-repo-org-enterprise.md @@ -1,5 +1,5 @@ {% ifversion fpt %} -1. Navigate to the main page of the organization or repository where your self-hosted runner group is registered. +1. Acesse a página principal da organização ou repositório onde o grupo de executor auto-hospedado está registrado. 2. Clique em {% octicon "gear" aria-label="The Settings gear" %} **Configurações**. 3. Na barra lateral esquerda, clique em **Actions** (Ações). 4. Click **Runners**. @@ -12,6 +12,6 @@ 2. Na barra lateral esquerda, clique em **Visão geral da empresa**. 3. In the enterprise sidebar, click {% octicon "law" aria-label="The law icon" %} **Policies**.{% endif %} 2. Navegue até as configurações {% data variables.product.prodname_actions %}: - * **In an organization or repository**: Click **Actions** in the left sidebar{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, then click **Runners**{% endif %}.{% ifversion ghec or ghae or ghes %} - * {% ifversion ghec %}**If using an enterprise account**:{% elsif ghes or ghae %}**If using an enterprise-level runner**:{% endif %} Click **Actions** under "{% octicon "law" aria-label="The law icon" %} Policies"{% ifversion ghes > 3.1 or ghae or ghec %}, then click the **Runners** tab{% endif %}.{% endif %} + * **Em uma organização ou repositório**: Clique em **Ações** na barra lateral esquerda{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, depois clique em **Executores**{% endif %}.{% ifversion ghec or ghae or ghes %} + * {% ifversion ghec %}**Se estiver usando uma conta corporativa**:{% elsif ghes or ghae %}**Se estiver usando um executor de nível empresarial**:{% endif %} Clique em **Ações** em "Políticas de {% octicon "law" aria-label="The law icon" %} "{% ifversion ghes > 3.1 or ghae or ghec %} e, em seguida, clique na aba **Executores**{% endif %}.{% endif %} {% endif %} diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md index 42dada4867..7c20610c66 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-networking-to-dotcom.md @@ -1 +1 @@ -To use actions from {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %} both {% data variables.product.product_location %} and{% endif %} your self-hosted runners must be able to make outbound connections to {% data variables.product.prodname_dotcom_the_website %}. No inbound connections from {% data variables.product.prodname_dotcom_the_website %} are required. For more information. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)." \ No newline at end of file +Para usar ações de {% data variables.product.prodname_dotcom_the_website %},{% ifversion ghes %}, {% data variables.product.product_location %} e {% endif %} seus executores auto-hospedados devem poder fazer conexões de saída para {% data variables.product.prodname_dotcom_the_website %}. Nenhuma conexão de entrada de {% data variables.product.prodname_dotcom_the_website %} é necessária. For more information. Para obter mais informações, consulte "[Sobre executores auto-hospedados](/actions/hosting-your-own-runners/about-self-hosted-runners#communication-betweens-self-hosted-runners-and-githubcom)." \ No newline at end of file diff --git a/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md index a24c445d1b..e622d937db 100644 --- a/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md +++ b/translations/pt-BR/data/reusables/actions/self-hosted-runner-ports-protocols.md @@ -1,3 +1,3 @@ {% ifversion ghes or ghae %} -The connection between self-hosted runners and {% data variables.product.product_name %} is over {% ifversion ghes %}HTTP (port 80) or {% endif %}HTTPS (port 443). {% ifversion ghes %}To ensure connectivity over HTTPS, configure TLS for {% data variables.product.product_location %}. For more information, see "[Configuring TLS](/admin/configuration/configuring-network-settings/configuring-tls)."{% endif %} +A conexão entre runners auto-hospedados e {% data variables.product.product_name %} é por meio de {% ifversion ghes %}HTTP (porta 80) ou {% endif %}HTTPS (porta 443). {% ifversion ghes %}Para garantir conectividade por meio de HTTPS, configure TLS para {% data variables.product.product_location %}. Para obter mais informações, consulte "[Configurando TLS](/admin/configuration/configuring-network-settings/configuring-tls)".{% endif %} {% endif %} diff --git a/translations/pt-BR/data/reusables/code-scanning/beta.md b/translations/pt-BR/data/reusables/code-scanning/beta.md index 004594d702..f8dd643a8d 100644 --- a/translations/pt-BR/data/reusables/code-scanning/beta.md +++ b/translations/pt-BR/data/reusables/code-scanning/beta.md @@ -1,4 +1,8 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} {% note %} diff --git a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md index 45eaef2384..cacadee6b9 100644 --- a/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md +++ b/translations/pt-BR/data/reusables/dependabot/private-dependencies-note.md @@ -1 +1 @@ -Ao executar atualizações de segurança ou versão, alguns ecossistemas devem ser capazes de resolver todas as dependências de sua fonte para verificar se as atualizações foram bem-sucedidas. Se o seu manifesto ou arquivos de bloqueio contiverem dependências privadas, {% data variables.product.prodname_dependabot %} deverá ser capaz de acessar o local em que essas dependências estão hospedadas. Os proprietários da organização podem conceder a {% data variables.product.prodname_dependabot %} acesso a repositórios privados que contêm dependências para um projeto dentro da mesma organização. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". É possível configurar o acesso a registros privados no arquivo de configuração de _dependabot.yml_ de um repositório. For more information, see "[Configuration options for the dependabot.yml file](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)." +Ao executar atualizações de segurança ou versão, alguns ecossistemas devem ser capazes de resolver todas as dependências de sua fonte para verificar se as atualizações foram bem-sucedidas. Se o seu manifesto ou arquivos de bloqueio contiverem dependências privadas, {% data variables.product.prodname_dependabot %} deverá ser capaz de acessar o local em que essas dependências estão hospedadas. Os proprietários da organização podem conceder a {% data variables.product.prodname_dependabot %} acesso a repositórios privados que contêm dependências para um projeto dentro da mesma organização. Para obter mais informações, consulte "[Gerenciar configurações de segurança e análise para sua organização](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization#allowing-dependabot-to-access-private-dependencies)". É possível configurar o acesso a registros privados no arquivo de configuração de _dependabot.yml_ de um repositório. Para obter mais informações, consulte "[Opções de configuração para o arquivo dependabot.yml](/github/administering-a-repository/configuration-options-for-dependency-updates#configuration-options-for-private-registries)". diff --git a/translations/pt-BR/data/reusables/secret-scanning/beta.md b/translations/pt-BR/data/reusables/secret-scanning/beta.md index bdb7348272..3d3c9fd759 100644 --- a/translations/pt-BR/data/reusables/secret-scanning/beta.md +++ b/translations/pt-BR/data/reusables/secret-scanning/beta.md @@ -1,4 +1,9 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} + {% note %} **Observação:** {% data variables.product.prodname_secret_scanning_caps %} para repositórios pertencentes à organização, está atualmente na versão beta e sujeita a alterações. From dd45ea940754fbba6d5fca51df35a4b3d04bd5d6 Mon Sep 17 00:00:00 2001 From: GitHub Actions Date: Mon, 21 Mar 2022 18:36:52 +0000 Subject: [PATCH 07/18] update search indexes --- lib/search/indexes/github-docs-3.1-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.1-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.2-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.3-pt.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-cn.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-en.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-es.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-ja.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-3.4-pt.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-cn.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-en.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-es.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-ja.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-dotcom-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghae-pt.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-cn.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-en.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-es.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-ja.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt-records.json.br | 4 ++-- lib/search/indexes/github-docs-ghec-pt.json.br | 4 ++-- 70 files changed, 140 insertions(+), 140 deletions(-) diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br index f7d6ca55b6..af549b366d 100644 --- a/lib/search/indexes/github-docs-3.1-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ff0c9edba0a40aa9c746a319a6dc8f3299e134f666177dfa4342f4a9910b4b20 -size 659833 +oid sha256:c7ebcbefd93d8a2a0fa172a36835cfa979ec869b287e22cc0fef1a648a1053d6 +size 660091 diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br index b0df8e7cba..31a8d995e7 100644 --- a/lib/search/indexes/github-docs-3.1-cn.json.br +++ b/lib/search/indexes/github-docs-3.1-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fb1c0e71459563b832c0f0f8a4f860c0c9cf14139c4a7217f8138fd4d473a990 -size 1338146 +oid sha256:cedb646594b35c17dbb14c93c1d0c35d1af191276a72f482bd4e23513f1c1e03 +size 1338039 diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br index 09a8b29290..36f7481edf 100644 --- a/lib/search/indexes/github-docs-3.1-en-records.json.br +++ b/lib/search/indexes/github-docs-3.1-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f3c33c3eb6cb2c5a4a44176435637decf31ec38db7eae5338acff0638190a2bc -size 881318 +oid sha256:b15fc2d5e8fb601847a784fb57851ae894a53a2fa7804dfe147cacfb0b49dce6 +size 881394 diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br index 0364dca6d3..63556a7c94 100644 --- a/lib/search/indexes/github-docs-3.1-en.json.br +++ b/lib/search/indexes/github-docs-3.1-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:387a312051b8f97cba29386cdd20480b325f4ead2bbddbf2b181d776e7c00ac9 -size 3385989 +oid sha256:2c4086ed9a5099499162f8df73a0b34342872660115b381de0046e902c237e5a +size 3387617 diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br index 18f698ddad..27efff3d12 100644 --- a/lib/search/indexes/github-docs-3.1-es-records.json.br +++ b/lib/search/indexes/github-docs-3.1-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:608e9731086822e5fb454c66182b739b4f20d3a8bea69488851fa6b5e70b9fb4 -size 609376 +oid sha256:5bbae6e18ddd5745c36dc61cf32eca8e3e14584c0a77f64c89590b6d10b056c1 +size 608773 diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br index 0340f3962d..e7ec40d1f2 100644 --- a/lib/search/indexes/github-docs-3.1-es.json.br +++ b/lib/search/indexes/github-docs-3.1-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a7a35b7e842eec9acd6cb9ebcda4e9ddd034704bba49f4f8971523ff31e9a9af -size 2567986 +oid sha256:fc49e2bd15b8b0c96849f5a717cc5dd5e538fc784d1bbba72137b353583e0722 +size 2567282 diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br index 2642cda10b..45639b1b3d 100644 --- a/lib/search/indexes/github-docs-3.1-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ede763d4f0bf7c5cf89d6fc9d52c520c27c6cc58e030fdb22e06185bc34b86db -size 673659 +oid sha256:32e78f439b189631db26b41ba879db32e571b2f26b1740b7018fba8e883d9938 +size 674054 diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br index 9568d27ec6..706ed5ecc0 100644 --- a/lib/search/indexes/github-docs-3.1-ja.json.br +++ b/lib/search/indexes/github-docs-3.1-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:129c5e67cd3396fa2a031cd0da721f4b648741baf2405bdf36af4b15cee32b18 -size 3573898 +oid sha256:328f624fde4c2f47135a6f38743c16b5c619b1115654a2d520c5e8c14eb6c097 +size 3573997 diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br index 5357ba0f01..eb84c4e5d3 100644 --- a/lib/search/indexes/github-docs-3.1-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2b5e686d992c66adbc2fab0e932fc4326929f74e75f98dacbf2c117c1790c6e3 -size 598782 +oid sha256:3db85e6b024445b7d525a9a32d2bab8f0119852527e6207728775bafa8b3d610 +size 600049 diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br index 9265bb1d21..a37c395d52 100644 --- a/lib/search/indexes/github-docs-3.1-pt.json.br +++ b/lib/search/indexes/github-docs-3.1-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ba41b694feb8728f96e2c642ba43f4a02aa9f5e41a6cbc05ad475827afc9cd01 -size 2447574 +oid sha256:f96d21dd420753b813762c2667e5c48adb34ed20d91e779f0399796e267cf684 +size 2447784 diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br index c1130e6988..59d384cfc1 100644 --- a/lib/search/indexes/github-docs-3.2-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dff4a49d8bacff2bc137fc2154e1e84a50a7de6f8f01d8c78ed67f0b322573bc -size 676895 +oid sha256:7690f3082a73b79251d6cd07fd470c7306dd513f5c079e3caec1bac21b7f6ea4 +size 677088 diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br index 20bc61c3d0..514b9b237d 100644 --- a/lib/search/indexes/github-docs-3.2-cn.json.br +++ b/lib/search/indexes/github-docs-3.2-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:68dea3ca72e413e961d681afd4757a26f5ee0b655fccc75bee6683b735282394 -size 1368047 +oid sha256:36b2de51db56aa775837c71e2ec09b37edb3d475d561dc26976a1997b19dacb0 +size 1368075 diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br index 817f928477..5f8effe297 100644 --- a/lib/search/indexes/github-docs-3.2-en-records.json.br +++ b/lib/search/indexes/github-docs-3.2-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:610fab4aba6d0b9c98d8173b9f5e88e3d802eaa5bd43e4a3a05b394c661f5b30 -size 910047 +oid sha256:23a0f769a5b0982fb8de5a3ba4a7459651aa1d0ebfc23311ec1efb3af06e8b97 +size 910216 diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br index 689ce1c4b3..960b26f119 100644 --- a/lib/search/indexes/github-docs-3.2-en.json.br +++ b/lib/search/indexes/github-docs-3.2-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:edf33e468746f8bd45499d172890ecf6c6e182f24aa102ba0892addd2d6d6380 -size 3503719 +oid sha256:0b544bebf6c78d3bfcf3889cd9cec72aa587b8b2a7f6f0c7d43bc76e2c26e899 +size 3503828 diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br index d0b0734ad0..ac7091ebdd 100644 --- a/lib/search/indexes/github-docs-3.2-es-records.json.br +++ b/lib/search/indexes/github-docs-3.2-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0a77aa5c29c8dcbb1af735a4c869bafb86a5a6bd62e90bab075b3ca086cec4f6 -size 625131 +oid sha256:55ab34ba5a128ad2569f032da3bd3597ce06ce6c82676757759a2a336886bebf +size 625248 diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br index 96fb684a40..9607a88606 100644 --- a/lib/search/indexes/github-docs-3.2-es.json.br +++ b/lib/search/indexes/github-docs-3.2-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3ac0b47fa94d4753c7a3f1386fccabc1f77fb7b0275a7b8fbb494f0324e0f893 -size 2636202 +oid sha256:7186e9c508312737a491909c608425ce376caa934ac5efc1231c15f49bdccc4b +size 2636233 diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br index b82c1e76fa..49cd15c20d 100644 --- a/lib/search/indexes/github-docs-3.2-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f46ea20fa6047c33289c1424c6758045d1f06570f17ef14d2938ceb46b089939 -size 689971 +oid sha256:2d9d3dc800c2a5c0c60f67abfe38aec284379186aa52b2a77b3cbaf16f189191 +size 690617 diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br index b1ef45af51..1aef9dcd72 100644 --- a/lib/search/indexes/github-docs-3.2-ja.json.br +++ b/lib/search/indexes/github-docs-3.2-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:165d82b212796a1e2a2d5df4cbdb672e3ebe93694b22f4b1c72adc214184957a -size 3664525 +oid sha256:0768c302b3c7625da74f9c61f5905f0e8a4e17e9770cfc8f18ddd93681ac8dea +size 3668034 diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br index 1ffec1813a..3b98dd1291 100644 --- a/lib/search/indexes/github-docs-3.2-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:84f1896f872fc51d04b2dab0e6e5d4fc0de8f2009ebea7e1c51bddc7f0342e02 -size 614693 +oid sha256:32a1f411274c6c1f5920bd0bf2f4caef72bae7ce7f649bd538d8910c9638a8d7 +size 614495 diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br index f76898babf..fd9ecf27ff 100644 --- a/lib/search/indexes/github-docs-3.2-pt.json.br +++ b/lib/search/indexes/github-docs-3.2-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d58c056208af6d3694c42c7c18d52a4204884e7055ba2cd8f64050237278f00f -size 2506649 +oid sha256:5c9dc0a0276a8455356a14e1f1caab5a85f4f096bd44298fe51ed914d34dcead +size 2507577 diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br index 8c956a2ef9..964b2e7614 100644 --- a/lib/search/indexes/github-docs-3.3-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dc2d88716d79e2235e10b15a6686685954859e773a528e09be38e9cda26a8d58 -size 700103 +oid sha256:1ebae1c432164fab2125626c0438b5aff75c7e8d65f632aa7c31ce8f195732d5 +size 699371 diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br index 640727ad94..8b9a2e44b8 100644 --- a/lib/search/indexes/github-docs-3.3-cn.json.br +++ b/lib/search/indexes/github-docs-3.3-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:3c468ed53b7252495f02bec2eaa4a004475897a66a1c09357145564d3c134cab -size 1421656 +oid sha256:4acf995c65898c409a5cd188f20fa6a294384d91c5f13f3bf05a81d96800aa05 +size 1421849 diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br index be96481f8b..b914003d8a 100644 --- a/lib/search/indexes/github-docs-3.3-en-records.json.br +++ b/lib/search/indexes/github-docs-3.3-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d4f63c512b449c588541e2bebf1f556eb5d23c28772d9b2ec26a17e06720e996 -size 945173 +oid sha256:f58c3b4577f9c8eee42a40fbdecd83ed429efda5dadf8580f438e0b3c9116691 +size 944891 diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br index 2df876fbca..c5d4700b99 100644 --- a/lib/search/indexes/github-docs-3.3-en.json.br +++ b/lib/search/indexes/github-docs-3.3-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:429b7ecde229d2c04020d8c7e3fe4725a4ead459eabb95ef9e2e975a4f79fcb3 -size 3619628 +oid sha256:0a10d1eb1bd745fc3572eb724cb12a637add2555662d5b2375374bc3b9c5f8c1 +size 3619296 diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br index 9c964c1ce7..33c374e304 100644 --- a/lib/search/indexes/github-docs-3.3-es-records.json.br +++ b/lib/search/indexes/github-docs-3.3-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:6c03f6c7f6a65dde6193ec93231bf088c9641c8d8172cffc1a40444a16834308 -size 644205 +oid sha256:36ec86b80706dbc058b050dd07e49d17629c848b136a486e0f4838df7174da4e +size 643913 diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br index a30eb9301b..eec48e7297 100644 --- a/lib/search/indexes/github-docs-3.3-es.json.br +++ b/lib/search/indexes/github-docs-3.3-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c0a023f678ad0d413b0967e0fbc2123a7a29fc30267ed5e18bd2da3a9cf3ef43 -size 2723709 +oid sha256:4c1a7315e1e6cc9bf4a5ab99a685c7c3862b804b46fe4d2d0de3f1fcf565637e +size 2721760 diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br index 7d0e1dc949..c33147ab50 100644 --- a/lib/search/indexes/github-docs-3.3-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:bd5f89d09df52de206c52b281b0c486efd5b5674e6d092d919d920b4ae86502d -size 713927 +oid sha256:b8e3d64ba350dd9c058dceb4726fc5a782b57cb4975beb68e77abee489ef2916 +size 713548 diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br index 772a18d978..d9361717a5 100644 --- a/lib/search/indexes/github-docs-3.3-ja.json.br +++ b/lib/search/indexes/github-docs-3.3-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:af4b2c840334ca9ee053dee394bb97033675ad08d935790e7f9b7bbfe61f8f65 -size 3789047 +oid sha256:ebdaa2d6702271600ab40b3819c82a7fb4b6b5952753c44f8accd0fbedf59de4 +size 3787667 diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br index a5dac4a162..65abcab80b 100644 --- a/lib/search/indexes/github-docs-3.3-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c77cc9ea44a3ce88f75adfb4b0e462a70f0d0f9618c39d5d9e88fd22e377de34 -size 634481 +oid sha256:d8483d4979467f772b2b693667eb36ac27e84cbb3faf97138f32ab1b5ab4cfe4 +size 634774 diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br index 3351034c33..c84aa95791 100644 --- a/lib/search/indexes/github-docs-3.3-pt.json.br +++ b/lib/search/indexes/github-docs-3.3-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:d06af2d3a363a8dea90a4b0856d418cc2d2f25db815ddae6fee5aec70300f703 -size 2591441 +oid sha256:68a0f20f2bc00e7fec61b1fd7b616298dbc96ceb742ff8b34ba65d285e0139df +size 2592303 diff --git a/lib/search/indexes/github-docs-3.4-cn-records.json.br b/lib/search/indexes/github-docs-3.4-cn-records.json.br index 746f68ac6c..50a98b265a 100644 --- a/lib/search/indexes/github-docs-3.4-cn-records.json.br +++ b/lib/search/indexes/github-docs-3.4-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e87321fc6811d0ab0c4d7c6e76742319c3b89f3320d4758edd99041be50a4693 -size 703568 +oid sha256:0e66346dea058636aa000103171795548bd2742ec14ad21a3eb983e141be3436 +size 702741 diff --git a/lib/search/indexes/github-docs-3.4-cn.json.br b/lib/search/indexes/github-docs-3.4-cn.json.br index 226200d9bf..6b619a0edc 100644 --- a/lib/search/indexes/github-docs-3.4-cn.json.br +++ b/lib/search/indexes/github-docs-3.4-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:e484abf831ace5bcfd5077ada3fd2532037ef56cf8c7dd82f90b7d856206e38a -size 1433916 +oid sha256:1d37761149634ca646ec089a747875a1f075f92c738cd8fe476b0c2ccfdec9d1 +size 1431502 diff --git a/lib/search/indexes/github-docs-3.4-en-records.json.br b/lib/search/indexes/github-docs-3.4-en-records.json.br index cc948754c8..b1c49cf48b 100644 --- a/lib/search/indexes/github-docs-3.4-en-records.json.br +++ b/lib/search/indexes/github-docs-3.4-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a09b40a0071c4cf66372f9c8e938679242602dd254cc9994118e5082462a4dcf -size 954957 +oid sha256:58d05c6f5e488ae6db66abedd0fc23b3d2f31ef2089066542e8b6d4664f27ee9 +size 955017 diff --git a/lib/search/indexes/github-docs-3.4-en.json.br b/lib/search/indexes/github-docs-3.4-en.json.br index 159039f9b5..21aad90aec 100644 --- a/lib/search/indexes/github-docs-3.4-en.json.br +++ b/lib/search/indexes/github-docs-3.4-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:eca4bee01dddc9117f8da5e0cdd2cdf8ca442dcd720623baa2fe0f132d7ed10a -size 3656711 +oid sha256:9994a95cec0b2687b9730c5bd3d78375750b5476674e36396aa3f0de642a7abb +size 3655956 diff --git a/lib/search/indexes/github-docs-3.4-es-records.json.br b/lib/search/indexes/github-docs-3.4-es-records.json.br index a78c5469b9..fa4277d31d 100644 --- a/lib/search/indexes/github-docs-3.4-es-records.json.br +++ b/lib/search/indexes/github-docs-3.4-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:fdf064c160dad6188799d750596cbf069a579fe5cfb63be7f8eb92941dec4e7f -size 647751 +oid sha256:c96db6e9c6be7a79fd10eeed16e964555721d630d1f6fa197de28c047ebef70b +size 648883 diff --git a/lib/search/indexes/github-docs-3.4-es.json.br b/lib/search/indexes/github-docs-3.4-es.json.br index a26836f780..a39f1a0009 100644 --- a/lib/search/indexes/github-docs-3.4-es.json.br +++ b/lib/search/indexes/github-docs-3.4-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c415d96320c7df570b3f9fbc9cfe0c790c473e605d2cae3469528bdbfb05ef9f -size 2740330 +oid sha256:d8f51ddc7ca8e456df3a73204936d13daf57587ba8d42e764cbb353f72f62d6b +size 2738801 diff --git a/lib/search/indexes/github-docs-3.4-ja-records.json.br b/lib/search/indexes/github-docs-3.4-ja-records.json.br index 54567f11ae..f596aa5096 100644 --- a/lib/search/indexes/github-docs-3.4-ja-records.json.br +++ b/lib/search/indexes/github-docs-3.4-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8c1ec0d82010c17fae8a0f7d5661625322bb681785d37a3e41ce9f75a3fb3b29 -size 716766 +oid sha256:947fa0a52b09b47117851a526f03445118820480b917df77371ee6ebbd7f4e0f +size 716535 diff --git a/lib/search/indexes/github-docs-3.4-ja.json.br b/lib/search/indexes/github-docs-3.4-ja.json.br index 0d67c33a4f..4eefa7d5a7 100644 --- a/lib/search/indexes/github-docs-3.4-ja.json.br +++ b/lib/search/indexes/github-docs-3.4-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:79c021a9d91e909bf28fd0999e5d13341709339288e72562d929e098ac969f40 -size 3808893 +oid sha256:a882ccf1869fd4efc7ae1c12899513966ebec736de157b41216cb39e30be37f4 +size 3810341 diff --git a/lib/search/indexes/github-docs-3.4-pt-records.json.br b/lib/search/indexes/github-docs-3.4-pt-records.json.br index 0aa3b7d023..085fadde67 100644 --- a/lib/search/indexes/github-docs-3.4-pt-records.json.br +++ b/lib/search/indexes/github-docs-3.4-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0ac0ad8430595d6af58c42535fb4bca94c4094568ec0020898ee49921fc72721 -size 638379 +oid sha256:2622231476be3959cad42a35af14c2b1c9379420ddf2b2c49c8c8fe17b25130b +size 638108 diff --git a/lib/search/indexes/github-docs-3.4-pt.json.br b/lib/search/indexes/github-docs-3.4-pt.json.br index 406924df64..e4afbbd9fd 100644 --- a/lib/search/indexes/github-docs-3.4-pt.json.br +++ b/lib/search/indexes/github-docs-3.4-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:dbd786a796b5e6b66e6804e0a09888dd27f65342ba55b8d05f9a08dc12a74544 -size 2603947 +oid sha256:018682b1be10372d14b22edace423bb85a9778165fc0b9d44739ac0c90c93d40 +size 2603273 diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br index 15de032526..74ec9d9e36 100644 --- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:c3d517f33169585250b7beee52f77d9adb7d233f57ee2f4fd87c0fcacc7bc048 -size 906271 +oid sha256:dc544b549dcf0cb6302524c1ec926301b5097b1458af015c77b171ed5724ebe5 +size 907395 diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br index fc3723479d..105b116e1c 100644 --- a/lib/search/indexes/github-docs-dotcom-cn.json.br +++ b/lib/search/indexes/github-docs-dotcom-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9d6f7620bbe42386a876e3c4ca994890a506a0e3b6292697286d4430c166ee29 -size 1571734 +oid sha256:323ebeadfddeee813f824ccedf45ebcd41c971bd5d1dfe6c4ec1e4002c2a1290 +size 1571811 diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br index c37be6981c..101127d0da 100644 --- a/lib/search/indexes/github-docs-dotcom-en-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:2f3b22e4234d9f43568bd9a35f93f3fdfe95835cd98b5a0541d3730a15f6e274 -size 1224998 +oid sha256:d9fc9f41fd337566e1c195dc9a8ad08a7caaf3bd7ac0fb995d1a2146b6b9d131 +size 1224453 diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br index 9c0ed09956..3e745d8ad7 100644 --- a/lib/search/indexes/github-docs-dotcom-en.json.br +++ b/lib/search/indexes/github-docs-dotcom-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b393b09dcc655963ada2502dd32e783d1ab324e7a3e86aa210be53eca4b564ea -size 4416589 +oid sha256:26a334563c6e6a26e73f2d154b6959d6e18b61a8233e3ac51bd3b8166acdb8ae +size 4417870 diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br index 2c020857ff..5d5f6c19a0 100644 --- a/lib/search/indexes/github-docs-dotcom-es-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:09f4115509a1a7fd55ed6b14f0ed9fb37b95a1652d8d656d51c419b9f3ee11d6 -size 817647 +oid sha256:a060b6cddaa10c75d5259ea5a46eea1ef9fb297f2c5e1b5cd42afb02aff55148 +size 819319 diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br index 8db837a5ae..5f1c787a4b 100644 --- a/lib/search/indexes/github-docs-dotcom-es.json.br +++ b/lib/search/indexes/github-docs-dotcom-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:68f335114bb375ee27cd86bc27a13fd527eedb7783d5a245a6b6c926cf8d841e -size 3273885 +oid sha256:08189d7bb2a6765341a51b8c7e56f9386c44ddc6506d07fec85e6d41cdedc789 +size 3273901 diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br index d4ee1caedc..93fe517824 100644 --- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:0a930f822118744a5dc6e8527b5fbacac1a457a0d7ebb07b9c9e8974171d8057 -size 918214 +oid sha256:dc009ecabbb56310a244210e521a468884bcc61243b5cd3120ad0b21a2d7533e +size 919674 diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br index 8ffd5e7f50..af3a26dc03 100644 --- a/lib/search/indexes/github-docs-dotcom-ja.json.br +++ b/lib/search/indexes/github-docs-dotcom-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:047e4222775d8abd65d89a65e80935289d92c93f4f8d9424e14cc24c40e3ecd8 -size 4662824 +oid sha256:c1d24b88f9d01e9100cfd6d5327f7b23262c1221d408ef93aefd5fd867e2fe03 +size 4662214 diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br index e251232997..28a4c197b5 100644 --- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:469f9e58d726244061ba3a41353d2c3a997937b1b29b17f802d1a6df9db1cfe0 -size 806035 +oid sha256:e82405d94265218a62b24f96461f7c42ab12c6d4a276380e4b908546f3f8ea88 +size 806263 diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br index f150fe8732..5250747fe9 100644 --- a/lib/search/indexes/github-docs-dotcom-pt.json.br +++ b/lib/search/indexes/github-docs-dotcom-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7e3061027a390da4bfcc012ef6b93cf462be38208222dd63b1be6693016e50f6 -size 3121112 +oid sha256:f9bc0c287dc17cdb09db34463b3a90c0345d43e28c1e6022ee4414b1b66f6a7a +size 3120326 diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br index 78c584df0f..7483295b5b 100644 --- a/lib/search/indexes/github-docs-ghae-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b3ad79ab0cdf875fe3eab4c52359e06704300761139bca80784b8fad99569e91 -size 537759 +oid sha256:acb882ba567d3c92c57abc5b3cccfa00972abf2b7950a07c00fe486732544eee +size 538314 diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br index d9ec628472..6f264853ec 100644 --- a/lib/search/indexes/github-docs-ghae-cn.json.br +++ b/lib/search/indexes/github-docs-ghae-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:50b21d0df833195261f324a2abb957dee5c5f358424e435fa85e70f61947fdd0 -size 1012611 +oid sha256:69076567f195c087309e02db75ece772b5f45cde5c3d088d83cde0f1846fd8d5 +size 1012977 diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br index 5ecbef719f..837f4c3aa6 100644 --- a/lib/search/indexes/github-docs-ghae-en-records.json.br +++ b/lib/search/indexes/github-docs-ghae-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7ca5b06c1c64a450bc0ae733fe3ee55f2ab8ed50fdd328b0f6790807a1289a45 -size 737935 +oid sha256:11d05e7936af22563d01ec742d39fc38680e995541f8dd1fb51e71035a1153fd +size 739434 diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br index b063f13c20..7ac1c6a107 100644 --- a/lib/search/indexes/github-docs-ghae-en.json.br +++ b/lib/search/indexes/github-docs-ghae-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:7179b371c23578853cc8948c11c832031f1e8de133e3194a9e73a72214e03c4c -size 2789117 +oid sha256:583226863f99bd763652f7251c044addda225a3745294b4e63e42c34538ac933 +size 2790804 diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br index 6d65f7d910..8e621d09b0 100644 --- a/lib/search/indexes/github-docs-ghae-es-records.json.br +++ b/lib/search/indexes/github-docs-ghae-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:9e59b2a9afb4c1d1323cc65f76084c266921679cd34774a252ad5e2ad2c7c9ca -size 496691 +oid sha256:9b7b531d089684b1e9e9c1fce2a7662df62d15017768178e7b78ab045a5570c1 +size 496694 diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br index 008f2deb25..5f132f3b14 100644 --- a/lib/search/indexes/github-docs-ghae-es.json.br +++ b/lib/search/indexes/github-docs-ghae-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:80a98440594318b0529e97107a9ba47532f3fb6a07f7d1b1930d99c2c01a40c9 -size 2018469 +oid sha256:52ae211d3ba8bf0b240d39f89a5862887a0adc7c4f150e07a31ffb45ead97aab +size 2018759 diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br index d47436ac29..fcca954fef 100644 --- a/lib/search/indexes/github-docs-ghae-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ad77bb2b897c3c93b6cca590749a2aa4a5cb86fa12ef995205c70451b7d3b2be -size 548022 +oid sha256:1564b76f7a8dacd010f04ca670c62d4932a64922869d910aa289dbb9c362dd9c +size 548088 diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br index c6d66f220f..14130861d8 100644 --- a/lib/search/indexes/github-docs-ghae-ja.json.br +++ b/lib/search/indexes/github-docs-ghae-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:771fdd7285cb93a223ef4b2e08c722bbb29e9ef78efcc60c79bd5ef29cb89f4e -size 2783872 +oid sha256:4e9cc5d76be8526f162d2651309936a647b6dc6ac8c62db092b8ef3166013664 +size 2781451 diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br index 58b945350f..665bbc0e25 100644 --- a/lib/search/indexes/github-docs-ghae-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:704990ffeea9abaf7d7b3e1729e8a2961fd6362ecc72bc67d4c47a5de1387dde -size 487985 +oid sha256:66e2400fed52f4faa08aeedeaede7db696a7027f787abf302abd90b175decd5d +size 488463 diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br index 082edb958b..d913fd557a 100644 --- a/lib/search/indexes/github-docs-ghae-pt.json.br +++ b/lib/search/indexes/github-docs-ghae-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b8200466d52d5e8f61cbf712c46d8f8c001a8f8a09ba2a3d0bdb70cd0cbaa37a -size 1896954 +oid sha256:cb87dc3b6f149602b5496c7d583adbcb92cc92616a5d95db8445a58b4d33f98e +size 1897002 diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br index c13eb93c19..3d6bbce480 100644 --- a/lib/search/indexes/github-docs-ghec-cn-records.json.br +++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1bfb279bc778e2e614d9dc1d3a5b0b06ddba0eee34cfdb120e172cfbe39ed158 -size 837995 +oid sha256:e720545c594288b2d42f23c84055e91b91e2baa4888c8e1b071ec82adee186b4 +size 838775 diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br index 83b2680fc3..f218d5b4b8 100644 --- a/lib/search/indexes/github-docs-ghec-cn.json.br +++ b/lib/search/indexes/github-docs-ghec-cn.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:b2db7c4687e9a43b75e7422f47769a4a12f055300ea7e3841258008170dbee69 -size 1635377 +oid sha256:7fc2e3eb79ff18806254844a14f91d3d836bd6599d2ae29c4de3e549915f33ee +size 1634448 diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br index 91e8809e27..05083123a9 100644 --- a/lib/search/indexes/github-docs-ghec-en-records.json.br +++ b/lib/search/indexes/github-docs-ghec-en-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:a6a7d034e0f48caee97e1fba8502adf49147bcddcec0d7e14c2264b9cc4d8bc1 -size 1105228 +oid sha256:745b556987142abccaadfd137938ef68efa27aca8f407187c1307dcb867eb2dc +size 1105003 diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br index c366344645..28d4df178e 100644 --- a/lib/search/indexes/github-docs-ghec-en.json.br +++ b/lib/search/indexes/github-docs-ghec-en.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5ad4a6feb5233f01764880315c4ce6705c0c0cf7ae0211907ffcf1f1f8bf614b -size 4207635 +oid sha256:d5a24fa318425dc79ed01e2560a80689ea29ba222f49509a35a74cdab3187746 +size 4206993 diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br index ff87bae6e2..203a891a79 100644 --- a/lib/search/indexes/github-docs-ghec-es-records.json.br +++ b/lib/search/indexes/github-docs-ghec-es-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:1f275f3c75ded67755f324cc00996e0953eda2a48dd0e99806d5e69c651d1e61 -size 776421 +oid sha256:31825cf0d42cb76d194b3d139b9447899864a82615e2d3581ae3216329161186 +size 776284 diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br index f05df35e03..37eb3505bd 100644 --- a/lib/search/indexes/github-docs-ghec-es.json.br +++ b/lib/search/indexes/github-docs-ghec-es.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:4acf4944ab0c36dd9d94b162fb18ca2a4920a62506da4ddac3f71f2abf325595 -size 3266771 +oid sha256:fc88f781e277234e425fa41497cd8a953b809189990e262375c61efe220f2ff2 +size 3266955 diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br index e0c192da4f..f3ca68d82c 100644 --- a/lib/search/indexes/github-docs-ghec-ja-records.json.br +++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:ea56582b707485106c97b95e2f23d99ff69996a97ca5258b76a5cf8c1bff18b7 -size 852908 +oid sha256:f994577167e57831a068aba953a3c4253048b060ec1a8cd641ab69914e70566c +size 854392 diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br index 0e0609059c..090b410fd7 100644 --- a/lib/search/indexes/github-docs-ghec-ja.json.br +++ b/lib/search/indexes/github-docs-ghec-ja.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f70cc3fe84262427cc8a5cf949565f6eaae988092db5db56e132e3e269e58226 -size 4550464 +oid sha256:b81836667a86ccf1a6f082a22dec7f8ae4c5ddbdbf02c4eb7f9a3adacfb7a524 +size 4553982 diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br index 7b1bfe7114..3f8ec29f86 100644 --- a/lib/search/indexes/github-docs-ghec-pt-records.json.br +++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:5fefb22f038f49bb9e2206b26771bfb74939202e7d2f8fe2ca8962900ef1f841 -size 765117 +oid sha256:9ae58c209d322d75e81c7efc5068141bd468a5f7f448e12ca0715a95fe59a034 +size 765411 diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br index 840cf3d069..1f43b6a159 100644 --- a/lib/search/indexes/github-docs-ghec-pt.json.br +++ b/lib/search/indexes/github-docs-ghec-pt.json.br @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:f97312508215bf8493c399fa264ecd1d053ffdf559fa220f40523df46b0ce203 -size 3103523 +oid sha256:fa9559d53b55f9c454538799be28addf091f5c09475176b0dd8592fce96323b8 +size 3104241 From 94561cbe6f05d9e508904c559eb66da3e7301794 Mon Sep 17 00:00:00 2001 From: Robert Sese Date: Mon, 21 Mar 2022 14:00:10 -0500 Subject: [PATCH 08/18] Use a PAT so workflows trigger (#26375) --- .github/workflows/optimize-images.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/optimize-images.yml b/.github/workflows/optimize-images.yml index 4679d6aaf8..88e05bffb7 100644 --- a/.github/workflows/optimize-images.yml +++ b/.github/workflows/optimize-images.yml @@ -23,6 +23,10 @@ jobs: uses: actions/checkout@ec3a7ce113134d7a93b817d10a8272cb61118579 with: ref: ${{ github.head_ref }} + # Need to specify a PAT here because otherwise GITHUB_TOKEN is used + # by default. Workflows won't trigger in that case because actions + # performed with GITHUB_TOKEN don't trigger other workflows. + token: ${{ secrets.DOCUBOT_REPO_PAT }} - name: Check out base ref run: git fetch --no-tags --depth=1 origin $GITHUB_BASE_REF From ca407d067beafbd0ab2b65fac09fb4588b588fa6 Mon Sep 17 00:00:00 2001 From: Rogan Ferguson <40493721+roferg@users.noreply.github.com> Date: Mon, 21 Mar 2022 14:04:26 -0500 Subject: [PATCH 09/18] Empty commit for GEI PAT scope updating (#26376) From 0bc34b18f4c70dec5fcd134000da67ed598133ed Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Mon, 21 Mar 2022 16:02:21 -0400 Subject: [PATCH 10/18] reference docs-engineering for rest/reference (#26372) * reference docs-engineering for rest/reference * cut it --- .github/CODEOWNERS | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index d9e4842478..0c69274411 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -32,7 +32,3 @@ package.json @github/docs-engineering /contributing/content-model.md @github/docs-content-strategy /contributing/content-style-guide.md @github/docs-content-strategy /contributing/content-templates.md @github/docs-content-strategy - -# Make sure that Octokit maintainers get notified about changes -# relevant to the Octokit libraries (https://github.com/octokit) -/content/rest/reference @github/octokit-maintainers From f544ae57d85c576fe765bbedb71ab8055b2f74bc Mon Sep 17 00:00:00 2001 From: Courtney Wilson <77312589+cmwilson21@users.noreply.github.com> Date: Mon, 21 Mar 2022 15:10:42 -0500 Subject: [PATCH 11/18] Update configuration-options-for-the-dependabot.yml-file.md (#16434) --- .../configuration-options-for-the-dependabot.yml-file.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md b/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md index fa69a7d01b..d96f63c8ba 100644 --- a/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md +++ b/content/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file.md @@ -256,6 +256,12 @@ By default, {% data variables.product.prodname_dependabot %} attempts to detect Supported options +{% note %} + +**Note:** The `prefix` and the `prefix-development` options have a 15 character limit. + +{% endnote %} + - `prefix` specifies a prefix for all commit messages. - `prefix-development` specifies a separate prefix for all commit messages that update dependencies in the Development dependency group. When you specify a value for this option, the `prefix` is used only for updates to dependencies in the Production dependency group. This is supported by: `bundler`, `composer`, `mix`, `maven`, `npm`, and `pip`. - `include: "scope"` specifies that any prefix is followed by a list of the dependencies updated in the commit. From c76963ddab79f9d9db127820a917d911d1ef526f Mon Sep 17 00:00:00 2001 From: Felicity Chapman Date: Mon, 21 Mar 2022 20:29:29 +0000 Subject: [PATCH 12/18] [March 21, 2022] Updates for new feed and new option to follow organizations (#26095) --- .../organization-profile-following.png | Bin 0 -> 17413 bytes .../organization-profile-unfollowing.png | Bin 0 -> 17655 bytes .../about-your-personal-dashboard.md | 37 ++++++++++++- ...-to-contribute-to-open-source-on-github.md | 2 +- .../following-organizations.md | 50 ++++++++++++++++++ .../following-people.md | 2 +- .../exploring-projects-on-github/index.md | 1 + .../saving-repositories-with-stars.md | 2 +- data/features/for-you-feed.yml | 5 ++ 9 files changed, 94 insertions(+), 5 deletions(-) create mode 100644 assets/images/help/profile/organization-profile-following.png create mode 100644 assets/images/help/profile/organization-profile-unfollowing.png create mode 100644 content/get-started/exploring-projects-on-github/following-organizations.md create mode 100644 data/features/for-you-feed.yml diff --git a/assets/images/help/profile/organization-profile-following.png b/assets/images/help/profile/organization-profile-following.png new file mode 100644 index 0000000000000000000000000000000000000000..b7675091afebb1698fead65d331a40241dd9e534 GIT binary patch literal 17413 zcmZsDby$=^`?W40-AacD2!eog!vfL`(k0#9&C=b{vC>F)gLK0Z(j{F>cYdqBzq+pP z58~OKd8Y1}x$kq%Oqhb4I64Xu%8M5-&?O~4E4_FDfWZEbM0y4LtrD2U4f}&^C!yi^ z;sq-1pP!d6(lQ8OAHH-{5*L0^K1Q+!dw@3;k`;RKqACXUK_B783z0O*&q80^7ND6S z3EGRQ*|(p_pW^`}#Os^bHM@zteuY{M7eKq?47=3a(H7T1ri=`E=RyTX`34 zVI12eyzChFPKJjA20y=sx%;!r_0hcdol{EDUY4GkH}&YAfO*A~cYDp)!u`Ws$*gT4 zmM{`UAQld}V4v9Ae-8lJKc5IAA*B8L4u$RSBgJd8ze$B@A%D}+#6#68ByoVC_kSM0 zb0u8Ao&1+1maE6z^8StFR}7`R5C0Nl_sru}j+Q|`ad0#YF!wO1P8g;AE2moC-38Z_ z()55hJ+1CC%5G-H_#4RwGsgz?6fW+3o_GmmF!G=BuRe^+nFl8d&3TnrroCCUz&Z|( zA%QzgN#QDc1;6-V>ORiwUqxxhllT@1O(l}!OelwjSKer7UJXr7R)3_!!%O~%XY2za zp*C~meHDsq5I{hoDpndLLmXGnI@$8=|K_J0!>a0~uE1lHSX_GW9~m1R968L886O$C zxQLVyHA*9)J%UCOyv6(bo?8S@$$kuGws+R1dDrhI{&ho!8z`D;d_Y&Y{jEWb?SR@S4&j&bH-V4$p=tR;6q5xS?Ck)4_Pt5+d;zF!sY?hs!;PA-bCAewphyr=@o zU=jBqRSAz^@%CU6|K!9xHIy`Sa%P3G%sPCA!<<4KWr4&x=D*rXp&CkP5JK=SDfEMZrRo2?c5~At zy9}FCCPc`0zRy7+tG}<$cy1%^3G{OBXm29^mA$2vMbcfcSaC^7a@qn1nFaATlnNq8kLNQ<#L38icC9D+pyUXnnn_-njVjB8GGmgyeZ$R))~OOc@er zVOV=9#5bJz$HajlCfUpuaAFQXakd!K&&e;R=?NG2XeDsajk2&sdT^LUt*|$OfFH!w z@$M=Sh)_eOznfBWe6`lGet}Xw_#MO{rj^UH+EDI)b%K6*i)zjDnk*G)*jYs0DYe?}P47htMg7}Nv=gv7F>r*ipwSM} zA5$QYpn!Y|hvUil9zcY^!wpaLchGz0^iZMb^c!4XKz+EnvFKX|kL_4+J^q5Bu*?z< z0BEUi{V=BjO~eE-PfN2iI>Z0Y%D7=y5+Gm)5=$eV?3+Dxqkx&Z?`zmxj9o^(kb68g zsPuv}L@|6F(tP&{#VH<%4Q8_M>I)*_m^qyxA&ihB{COq%wF9?S*oX!ShX1K9BLWWu zq%bSU^l?AL=Ihc|K5%YbnQY8H5G02I68ng)+=Is~R*LP|ql;Rbi*ff8fr#F4`TX=p zh?vYxu7s7HXcReUqnf{nxf>JLPz1@nzB`TY$%Up%)@rtCmdGYHvZzMG|Qqj=R1`cK`V(NN4_{fTjiXe+< z_4W19R*#{BLeB$Vy?Ua@Y+#m}P<!r(uYCeUo%-9`07tDv zjo%>fNdEUg;q5L*_Slyq5OqCtlRte5WHlWd$Q6&d@a*4W=iqohp2eRKBlyH+<+-@H zh^qu{qc4fSWzj;7A?8%Fk<{|s0U1jw_F!VPM7Ok8NtWx%+bMUI9 ze+D&_*&r%~@=B5tvbVRVFKpp>y539q<_l+MhtH$Ow6)j6jeQsL#o>~FeC8td)_g%; zt=H1PO||33LLu)pSrNUWURU;8mg)z5V8hW8Z*_!!q4{2?%jbTy zdw!#P=Et;VzfMR5Ul^`%bPX^ao2wRBvdZ+QCbi+z1{PxL5>lY2?R49mq2k{|-{_m2 z-mTyd0aex1jP30ex3{;Ae0+41l9P=M4MmcpdOSu)Mh42X8rB!;YfQ(9{;hQC9%`HB><5zYi`zatxH_;vB z_vo__fi?pquLPzOnO)dzBWGa6(*kr>A+*L@Td#Miu+2!N-%RDbF`LH7=5eNDltj3( z($q{#`l=igIT^mcZ;?3|eB$$XIjd=A$gq|expnuB`vi=a88Jd%Pb*h)~hoi zGU!DC*X9cmYt=*aB^PXoFSus8xi;f?oFRtpb7OA2vhVK0QD4?X=d3Huj$d9}g-Ec? zn67juqb+U`lA=C9$#>1vPxFGao~n}@M^x|hV~ z#RsIo*nro&lPoAs)kw9`#w@58Jv}|;RKM(=9^54*B`4}8JyQjVJatTbeSN!-Y8h(s zx4tQgD>pts>()%8KBh5u!8Y7w%R<`~44?W2+qVXUqWX%GcJ4QP7UjzVA=Q!Uq?;$y z%-Q1RQnhHi(j_C5oE2~9_C9evm+{6Y>k&NgUYcuG@{-!F_sjexnoV_ zP8XKn2SIyY9BA4$WB_MEAeSbNv^(a^(0HMzFY z`=~t4Cc0_iE;w{JU~_|YFO?}^s#3cK1C99N9p!Kv=@-w9{?Vfs79Am|7(0B8;F=h5 zVWjywAR>9rWWG@e2$1OnSOy!GAZYgT6vHUHq^1L`US!-4q8@HI78tvAmNvo?WVS7GtfW`^wBZw`@c zH4-BLei#VbHM8GpdGkkQW2FS;$AZ)I0*&6z+B)y+zHYBo0v5wm#CO|XEkDFkh za&$Nk5HxTR!`Cps|LT3i^=qh7V0K=Lvbo;K*;%~2+b1ilsm6;MI&poCDvpkbFT@dz%tw9`_oTIV4 z+^Q`rt=^nJfa&CL#P`B|M|PoSiC;(E#8fNU0QX+Y&6HnRdeoD=5#gwbT|O?uHy7u# ze@>L0A%&j&9I8%Fb29xHOWN-NSy|@yrs#(sQlUlpvrX1s5**7>LoTs)VU|3J zbD79?qEcw0fUd>#0Y=!n1qB6xSi5_vO|gp`RRXK}-^75?UDcB+>=fA{o4}Lu)y86J zd;{lq8R>dxg9g0)=Jms`CcmwTF34&1DCCkHi2uT4^GeN_G)aE#=bsb5=1Kd~KAPJ) zq7>Uqf-VV8fs(XZPgTQzaAg4y6%igwWP54c&^s~xz6H5<5iSl=FZLBWiBj7zFXs5$ z;3uhnW<=IgBM){na&2alt+}-;T37=~d>kjHew87}kYiFO?kbuw96%8Wkd;dU#zaO^ zMFDe3sIlRRx(rY)OUF6ckBu-L0he7@NMwc^3HL-naPyX|j~WXRmA3_nflbD`xxbt@ zUeZm}Bj}N6K~AWv^U3$ZU*ehvT)bPGY65$4AhFA8DGG-O3cVLA^Z6*4rW+J{16K z*P|YS$uZ}}{;AzLw-I$P<#%`Tei~5_mN4i&jTCrxb~Zr_Tv%9$D-5RiQqRZ3nk#qs zF>lY#Y;_@q-S;D?4~fjg0~F8EFu{Jf_#BsHo2>Y@h1gn4!O?p5ZHu$E*u+K3i$uJjO>mJ}Qk)2r6JQa+QmQ(c6GR9Tn%xFL^J zTqPe|dOR~GSj<8-0q>6ejJ90bU zmhFn{vOn&Oc4FtK`}{zH!Kjrqst&2I{m$Vm2w0w)C07bKa6wzh_5AF42fig4;?A*_ zF8;>Qr#^9thT0d$Ny0XhNe#0^<~ajTb-?o65{?(9hHe9f z>wwcDDGBof`H+d7{`ttz{xJ<4^y5URi@kpwJ1qQ*HNx5bbt!uq87*DGa~&ls_rX1b z_f)3HvHxTs;YSF9Ru8^&TW*n_RoEH@ppq^=rkU zjdt8H>qLn2-U0i*Jxd_BU0S+b8d(~P4G!qeiXEw9fLw*rH2w^uhPaHf)Xzp>W(>e2$t9kZ3|qOn9It6RxYsrzS;FycXApS5P{FMFCI$n3gQr% z;I?#BG6>9%MS*%U^PF@c@&}Xd^6eE{BY`v=VCPnu$E@JLg*e(js9i>h(cx2nzql- zC$?Q_$F0Ud(~^K;5L6Ms+-<^nl_5tfyEtYR0ZCBwP7tZgdv}hts8hyD<$74MyfPlFt6s!;w@EIaKU!yqMyCr&bn6~r_tzGY_ovh#?^A{_oekW zW?r3dv#vyx->wggxjMPDU>JrtVD8+-d5eV%cH@|7sZz$_??>+5+eNr=+EDb=qQCC$(u``w_4fAYI zx-nsnEHefC!T<`{CWy$`2=-M4MKi$dxuSF_zv>Fm0}R+vm`ShB_xoQ57(losxl4K8}VE%7V>0%F2URuWNKT zdT-KJbm<}|vLnRGfb%$`;EQGJ)HO27G+ovCw2@;z$BOgtaJVF_URpUGO1Vu)M0UC= ztH8{DUJ5V8e&}JUZT2;5BzfLL{j-z$=i)IN0}wCq_G8$fIc!JSR7a^LvlbQ-ijFB? z@j-Da#jma%q#X~gt*s5jHp3xrn@M<3m^2V{f`?%&-uH%)A~2L{(+KH;3Ly>Pt-v&m zL}Ph1Z+CZLzAO|E$mAha>m^6zHe$(Q`ZRPlsWd*%3IyUI_yTHaC$jIFs9d z0UoZOCtNqlpL*mGZ=+TpV(dq=%X$dUO%2sGFR#g;_w)v0o~K3jY1Pm#?X9fCHu59>AZPA<3J5spZ>-tn1N zTu0u!dwbviYZy_T?9GFGHtRYMw5E>r+C4-%o_Bn2)s$2sDOMG($S7#;|RDpND@roZbpP*!uo>eyVtW9KT$p-cq?c zECy zXh%2T^=(1vYoe{)w=&W1(WIoxb(??UVEh3R0p3)A$6hu3+7qH?kB2T~(Bl*Nll=f6 zc?Ngk&K{IJk`97p*s8V&A<1xc@sX6jkLY;NyE|UJ8C{JRyvY@e`;q3s-1{2;)KO;!(-mzVEP9GmuRcozx{)a+_Gp&>43AWz}5Ws++WzM8H;rVxiubTXQo!+zS+2D@eUgX7&)Zqt6$VW&? zNeOe!xJ^EB`c%N#5tO(sax0AabXsNbvv^6X`=yk;$c$UZSt~bxUd@;rL$pVavKF;+ zruEs?rR6ivc7NBlyWPFm^kXLi++S4vJCHmHC=z<=qi7!V)MEQp!sl$Kou=asme>T{ z$x=Mo=hziy-RoM5iI=0+w=K%17i>mNr-aig8^^~!$K=C>dR}FPk0;$VXO0~w!<{m0 z2zRjvcgroV4tE!OpQgN8E~OT$&bqlK|!t;-mu@hI-3|;c?jni+_HY&cRgxKm?4<10R&Bxt{>M@MkzKIU^ zO#=t`R^rM-H$;3-IuXyVpo@kykSFql6F7va3`B+606H=SPj=p&_O=aNm`%z&0dc8uoeGW%vd&)F~N^k{0>cuU19ve_vtF+?6go1{vcOKeifWW z{=9ySpE|FZ2EEnW-W-0uUyFQzVhScA#$*RNNx);0@lOl`lZbqo+`aFP`{lFGh3Leo zA=k&^WSsy^F8c&6_iI%zM^=3URE4qMOjQKSA;9Z{JB#D#zylt!^!7ALqmOc|OoGuAVnf);L@y&q3SHerR4& zkMSpx%N`P6^|P|n?-+ml$auiySZa>gS-CKFI=Dy4Uo|o^CjGp20;*3X9`NHEANW0( z@o)cnY?YFddWYg9s%rw@bU91iGH7k9SnlKNX>UM&IUe9acrF50en3FW6t0dKMRC1! zwY5E(-me6vki*J1zs%>D;%V``tnG>qj~y4b)8cK$6a{lmgIa!++r^XsMHs6h)u%B0 z*C(Zl%WMTEaZwrbSZdBOb-?Lbyckg7u)mw*E-ocxV`Bpwp_!I`lpn54S9&A2++k5q zv+_AQP#LbAeI~ebXfhNQBM@Gv9hH`r8h(IqN$47F)0!VGVmDSx4Gw*n1_TA5Ol{*Q zU#uof)%g5gUYd-#4cw(D;d+yTq3TuQ@$>RFh_s)^atltT_-)`U` zV*h9G+%NXp-7}1PzrMSwQFTFAqe9=yO?O z$8`7ehO)M5es9ZIIO=A-YSWvz>S64%$o z%1mb|snf=3bttL4=bBzmU1gqj|GmbYH1(8qr;LY?VrmxoK~L|9T>93*me2^Zyt$~e zomMWi#MWBpIm&xb4Ii$Nw$n+XE^`mYU81mYD*~b@cKiDJru&?v#Kl8u>*^#O9c$Rw z*vvHG85kHQmzT@P-}*Dhp5BIqA)~X5=jP_Ju(46eXYtuHc{X~?tJvsOFx+MvsjI%G zYhY3`HguO9KK2p+?bg)DOH(qAM12!OjLX zewUjcU^B9s(d5iSYuKik6MG%!?nM9l=R+)WXqx-DEErnKRIOS`+h>I(YLXj34)kz@BPB}}CY zyQIyq4sjhNu1pCZ!zGh_MNj)ojNv!1<&cEt>9JQ-wbYv(5H(WQW@~1vO>k-?_ZQ@& zhQzKfENC)#4$v7&G(5J)ruNdlkvrwPpCHsAK1TKp9a;+Q2sE%(X+GC`)$3vd(IbbA zz||vs*DbSelE$EenvKaw)Z+teU0qSBcw!^eXxnnR<4TejQ1T4pfK#2`37;%@+^EM00o9-`c?gEFMQSRls80 z2&x(~qgi(rn!pS;P?l=P_uPHXI0q8q3R_u^J4AUKHMK$z)1{|u_7p_P%WmQMWCq1S;ztUG4nougKeR$}zM zkh$PtW-n{~bs}rxxP^TCJ0s@-LASTC# zBxZ?>Zv$?W2BWZLjm%|>{W8k}ornf8qL;8^>7At5azfJ#3W1ads0t`w$-y=N>+y=3 zY$4DQa!D>b`@#hLLXwc5rrDGt&b-M0ztJzh(v}b0Vd7wZ%8k3@>Y;_oEg5n1WOV@P z9}DVVdN8O|E^=&q!}#wo*sposHf|$S zEoTr$)Ah1K>v+#{z9RyrP|p#Iguc?hmUAr|RH-f1_7h$I-9FUO=%9t`{Lr zn?#3AwVO`}M3_2LB=(&=>u+||?};Q~@zZ7=3LDvHmR-VM9TAC}17An>1e|>` z)ppYIaLp32ot&NbKGLz2#PTKTA6_HqI}NXKByEY4IoQllE)KJT6glqnQ+qg(oL zueyKGDPBa%!t>&18TI{YLZSAdweNh+lo#0Kg4nm8ou79bT_l|E^h~L?Fintt9Q}5A zy0W%L!+14JKs~q<>GpVfz z7N4FgyYN675UN#PGZA@aGq;6tT>JDDv^}eem)8C-gqfrFQ&fw=-fGOWe zF=ce;SMe9Pbx{Sz8h(Uqo^V$Itg}qiH8l2kg!>D3#s_OcTx(^R(CWx7GFkJQ%6>>> zEw$wL7rNL;TUhLaobvMihEn1TkaHFr_-1KjCph@#3_vCuK&RX=eC}P}h9-CiR}Jh6 zV-d>A7?zRnnRFv>8V|<>`75$@k&63@2viU>G|O8KhK#^XQhe6zEDMS>xtY9RG(&=X z(*4J*I~In)x?XOj#BT-U)IOYBX=84G$Y(2W)3J<+Eh2)BTkp32peAVhqtcB5m=X#BdnyPq@DfMEye4!7e78V^#crgsBUXxIKCJCtM9@9 zf@$8v0hY^*O5*;~kwyRLND2fZOoS%8-~JhoH-_#RS6?1IRgVe<;_IWY_>HUj`}>`t z%)vifT#vIXmoH#Y%lY`97$ZI|j^fv^Uz4k=O!V~h4okZK5U(|a=2BSyd<2vkrlJ9$ zzGrJ`Ny-EJ#h3!I@o7>`9vgS<{c>WeH?TPH9?$IK2A5IFUwPTU1d5Z0VM1cEngTfC zGZ41f@-orayp_crf))nsRqFHNtKf{gznSFxM; zyWjO=oSYHin{!~`A*=#_wJf3bT__jvwkpj#GycBG-@e@*MEG9hYd1P6&Wd}st>`c{ zP+lRh7A_`0k0*Lm219yQC0j;m0nkgMq*p`kW|Ujg0ggc zsWZ=sJ#t46X3DfQ)sOiaY4~$R&UR08b@(IUbDe;#n3~`!nUCpzVGXKkUDQ~VQk$Se@saWI18nw_i%zDF zyEw12`NH_C2lpkMWeCL1jMDb&{NFyOI<0|-fjQqoEDtnuw(;?d9V|5YD03$lXPL^Z zt(BCOr9pBy|67{F0NE#)vqN&q+t`^Ckk}ebpwU#Pm|Ug|@Cb~C32BCxmb5S8WAmw- zT%Zfzk=e-NVMr-9+w}8 z$c+TZeIm(p^nm&8ecYt-yiQs(`O?XMjb9=j`C{Qt3JwwB@urjrY5t3|?Pdo0T>OYW6oCJYxHe*Eb;TW(N(i z?ZT~drVhI|W^8H2W%V%K)+ATqMon*T@9!A2=L_Y3ra(oCYz@*qEgM>o_oa&dO6p{r zU0YwL{2yDGo))B>fyumVQJrcr0{eAg%e%lIk!Fw2<>>6$iTRHwL9%9t-)H$n#`ptN z6%`dNC{C`f4Slj;=DQHbyC%n-e+|Ql>0z!ID=dgK{A#Drd;)xf;-vIf_>^`Qb;}?5 z)BX^Fh{-7A`aaZ#FA74o++9#uD8BI?;`ZBq`QPy0B6t*HEa>%tnEm;)u=ftgA!i7C z@4^P><{G2_Xb|7kyWGAq$o>L|n*I6H&+BZE#uLvh(f>1!*|cJS1dMTug8}L=N!aFV zvzAE153xa6Sy>a#)dWn9ZEYggO~UBbA|kod9|%jz%BFI8zNpPgs5sYsQBjekE^<ql1H~f5j%yKo+HvmZ~8U(!~-3y{PyH8I(vQ(g8ufJN=*o1^2 zG5*q|-QIlg=NOo}(msIM18(RA1RGtx=3w`5GJa-erJT2@j?Ucj|F5llwZ*N_3{pSl zxX*|MkdC9q6ITFp`QZPx88)Gi%;ld@-|1Ki6W( zlnHWXW>+i7Awtn)|D$)zJIGe~FF~kmzfjLY*;Oh)_V4r@V62AJf4(2)ZoM;i9?%x< zitX*eGTRM(#Z62~+`v;BwQohk%>&skc*Op{@=R&o^TRF$*uSySZIm zY~*4#UkHg5))t4#B*68yWfsC!N2a{x2*oxCN}+HW24MtLZKeW9Ve23|x;ZW6yG$|M z$u_j*>@rAN6D&PM$0ncM2AMh`+p@i0^M{9;2AEqB!#o6C9GHi|lS&vTc7^kL&o8j(L_CeRJNvU6B}`;k zLZ50m3)5wYL{c~vIo4Z#r*OMsep#Go^~b+y9d)AL4rLYKYnQb}DK=i&Zp`JRPCplN5zx`@1z{W8}@Th#LMg~bCV z9a*vbRG#fuJGK7Tj8>WX!l!-_ts4s+FH`fg+I@;kf5a`^y;_zu<2)CX^8T^o%=@Id zut0roJXYR-jA`U{Li=q!wFie(GS50PBW@!|tMpyixy=^$9=wOArxsqT0JrCrRp^C} z_pR1m#%gTDY!^avUYXuTM)bHrRz-z2dg@c0=GDVO{l~J>p>$5$csVd{bMs}GlZ6Kd z7efX3lbe4X>)3nGaQAo4!hvSXo+lETFllgEn=)Au?nN2zb>ioK0ZGGw)CfA4um_RI z2n>m^INTjkiBcR4quU7#o8vd%5-p;0+OqiNlVN(7N8jm0okk~7=>gqj#FtXzUhW?a zXBIi%x*iKIT{~dVkztYxPAtAY-mzyku{dyryW=96ZK055D2sPEuTM-;+g(lXE5P&C zf7!afvjD|D$_f$62y{G+M)4(<5GxZ0vBb&Lo?k8zoCeYN33`=r=v!m3)c;AB>!0lM!l z#f^C~?M-eP`^4$f?F{>S>UeVC0Sm+3G%#Bc?tXQ%8;h^u4UtiaQ-O=2a;D#6UUjn= zroEv6Yso@MOQAedVQV!Vm!FTLWy^|71_|^rH8pdV@Z<9?;Y#D;q*E7LCd+6m?M~>g zFf2e6uHY4>wb8=M#Rsm-;#bE_b@(hUW!9uD9hFonZl%TXue3OFpe31^-75Fg&JG&y6!Me7NR^c`7y`}W0U?vMydro`?E`hgFH++nMO2(aKEGrQ?U66K*y|Qh( zIa3ds#!YjuSZbygQXC6f>h#oN#dVFZ9qs;U#HGQr-9vO_&=pfkYWj7*WG|sLENYLt z?72q7M7A5oJDy&^@6*wW*-Ak*-Z?dkrd&eqbaB1B*iXQiiSZ`8itHmzkgP+~4%HVh zeGYGb65=QA&m&D<@o^S%JQg~+ZzH7b{mJnhSGe5Y`g#RJwDZ1DY@A!90x6At6O3aJcwg@&!uPaY&stg#sVm&w=jx)Pw%upp~ zv*b(izO{Hh=&p^ay&daH7rK@>jUgK(+i%K@xs6VLtZ-nb#TnSFhJ2ZU$@0kaofT65 zcA+7_J{~=K`n#OW1Pi3GE)3UZ4p}!-J1&adz(Gf6&B&;2ni`;1t~*OZlc62?b^Y_p z?_H9Y(L8YiQ^K0%!^9(l0#MOlJj@!5jJKBi`#?}HJZqSx(z8~UvuW3E%gQmP&%y{W@ws1h+nh&YW4W4J z{i8N$YYhGQ_S8(zFQHt^^Lr0qJ>rr614Hr`Y9h0aOFt6v1+`ktZB`olP$UDR`eJYq zm)lF2S(#$<)}pSPZo*bM^$s&MI}7pWmDXpl!vwQoHei%c`p#{rhoO`kiWfz3Yz6=p{fMW1L?Tbf;KvxqQi87rRiR(LX#cpzSK1j@9lyEO8|2;Y zb_fRC+oG}^t$$r~;!`1BZZB^2HowkbTx2GITIOf+iak-2}}>qWzbQy{>u_c(w(Gr$1<+I~F#v^OTONT

nH$PGpGCHnvwQhc@Q3Xf@elSRs~L10Em^7?f7m+GsG`@-UQ&h2AXdM3 z=|i2$`9{7LIK4>jb3k~Rp;nQ<`z*r4QmR!5w;u>Yt;e+1uy`{XNAX|G%a)Sogp}^W zBqISDHbzgeAG*$LR+@47zEgAu;#M+1#9lLJCxHfwziI)CPJ9P&ia3j z3uGw(9<)DyB1rOe&+6aXt+NZRa3;p0VYsi;{r1b4yAR;_iA)f~9aUcuN@F1$a5=s& zOhv;anD;b4z+m*fs)_oBtOtouo00=vc9bF?K@2{#0aBy8y<5-hyFuXhR*c77pJ#ne z@Y8FD33zPQYLi(jL+?hvPv_CmvW+OUTF8h!v|2hZQaTj-ZTF2SAh8tZWSav$%Y>NP zH)|<%(sp+C*h|lonH$Lcj_KhE%3ymwH1rtwnxt4@!X?IWdL_vS-Nu|_5~dIp^gEp_ ze|tL6u(^1r4Hk3 z_00G(z||lH=9H||DSTR!=TqW{RXN8H^kGistH{W`4%uKb$$$+_6j6z4M_5n;;Nd!s zpeu3io^sgQCdGFbUvk8wZI)mJXmO*;23#XX3on+%Ub zFe22Y4g{u0I+jxGk0`hl{f@dI%vef?qhU(lp5frHC@)hv2>;@^_Zlk{nT74j)NZ|# zK||t`Tox^^pBtaFG-lSJeHU{og;DqkXLUH%?sVa}aFVG_i%7kl14};IoNmUzsKbe` zQP?|Y6sLOWQq5g606%jRrB0(xRCR(I0uj`Z2{sYAXrJP)ej!s0AhFAxr6A_KnE&|< zbwEuV1qv*$M5w|=U6ED}NyNr+EMinSMWk1&{*w|e920p+Veq!KY*v|?Es5`H_@EM^Ie(u4;H|TsMCyCaCi$WE)VvW|XVYneS zCZ8CpJW4pbfTv80=nv3xxWnPs{&qHKNgtBl<&Aa$=F z)Iz0>F$DUwoQSILqns3U9D{8Z%3iP`*PS~}qhEJ_ic-rkIPkO~%uEIfc3V8?(ZMv8 zaal0wzAPsOz+H4?o;FJ9748Y*P&Pi`}(`Sm<2V z?QZFk&zbOkaDjjJt=Ql<*83&4dMq#UXIGQ&%<>A8zp5)`J}y3?&5&B&*Gi1v^)xhP zVgam!iz3((Gx_D5*am%46H08)c?u1QY}_}V=bPM{Ip&kl5*S=ikmTxbXFl1*nmmWO zaMR9l?X?aJBwme`f1SZirFw20URk>t#^U1yain$~W$Aji%vsUM*|AHpK#kuj;}yfr z3Pl|p9)51r0$rKzHi)paZO=I6c{@i-fKYLjuOl?|5>nv?PAJkXR|_~uW#dF^wnm)R z?QjV`)=beM2nQ24Jj-q`ktHGdimZ(W#ik;@ix@Fd057`26A7R5@l)p6@als4>?21C zN$E5#|FcdP)eEvTsw*mw|e&{E;&90B(*b z32{2;TnzA-<2{$lX=a}*nK60({xj_IB1$1>WBa-;y3LAsBaq^wPKC(jnu`LsE? zq}XM@uG)nyPa~`aR!p##reis*2X5T!uj2XqNB}T=r`(2LFzLM0`9zv#$Cu(=+p$wH z_UF_lf`?kgVDGoap4ZbcjFKMi=|-x~Qi_YAY?1eQ-ZuO5J!E-+oCMDfO1*5z?3$*+b6)?LZh%Bc!H= z10GCau%f2lVFvaqQ_s|^kRITBzFb4i-M6h1S8wu3Xcs@>Ai;z${q3lJ3$htM?WGBo z!VW2T77437&OVMluY}8^B8w@1VhK|xgb^a_d2a}9ykL+yZ{LWEfBjEWEK3qWESH3N z*CC=SWmB(nlv=*jmX~5+-o)0lG(+WCD7yAriu>pdG*`|G=F+PQJ_R^3S#aj*&z)GP zcFOk;p_S{XE_>-!2Xj@Dn z0QH&LHvkO6uSC5ff%pCLzInXbIXZUOdAx2MYs+4_`_r%%jK-V8y)S8pcJ~ z6b#&WHp6U<@&06NSuie~d54jz`1J^Zr^0}{5sQ8G+i$69&;}@cbgL&g#3EDsoO$;CB5hV@}b=P>eySK*sf}gSj{>u+6i@R?KVMdXdwW zyPfTdUUl3e(&6Pid;bfTNG#{6_crIe4d~hP!}dGc81)pBR|dDIhl2IIO6g>^z~en3 zZu=f1&Q*pbA>lrP%jsAfqw>s03W!UiI$Q3~H3K;OkukJK-E296vQf(3u`+a3!=7vd z*kO5(@rsqfTmCTf`@`lh80C#7xgwjcZlb<3);_KH*1D{t)=zG!i*A{)V+vFr6=z;b z%nd`2hGI+|$<}r&9;?H#vR9Q(1R8G@vzvp*26h!*nRB>)ULYadH`1@bRAOHD)+VRN zbnmq#k>dAr9I^NP5ZN*HiRbFKUZg{peLRdLgwckr#GXl01%q{;ewPuS28A&{)w53A zbS#?gYgdn}_vw)r_S0kqKKWT1Y zh8?I6RsN)#vZ@6}Pc08IYnslm+ZdC>^3sZ?s-F#}H`wBCO9sN|2P6tA5W<2_UIX49 zmqo5CHDu}_EdX!#XkI1tqMUq?vh_dL6ujOIt(aABuoby8Ny?}1>Q-Gz28tYoY^ypw zUgoX4Tp+gijlS{X%^^WJoV~=XPn7j zI^eH)Fd==+O5$j%ecxSUIeC{Hut=lfjBhBhLxv+EzpXfx0? zlvZkMMbh&4PfiXi6H~iVug!;{Vx{#Pbk^2by6SN|(`5MJ@h;Qn`7)goxxx1@r2m(! zJV%WZ-J+m`bk_(0gA$PL8Vv%{FhWpCm69BSgmiZ+AP5`XEi&ou zc;@%}{r#T*^M78iZLqk{ea>~RbMEWuog^P3vB4yQ`edeKiW?=I*b~_*zqnpRm!Fr%*mFC}P2LhcI?tXCx2MeAB3Juw;JZ#?cBF&! zsURaj0CgE!FLNNccHFy}Ze(x!>S45Pp%|B46TGP-qWqo{(F_;zxT_lfPZt9I-$*$H zJr%pEjwQPo8k{9zBDG={K19z>tYQq9MlL{ zvFALbW2Q^Y&bFXqr2h~i{}dcHtnt0ZoPCl=G;GUU5j()w&K6da^rDelL-@i76v~N|!W$+|@aTlIXXOaf8xHvTx~d5MO|C_`dxm<{D5zG!HPxzHq;XgIHh_9V4vM2UsRq^Y9tH14!=y=JTx z7|uv?yREU6S(QbB>3y-JvI)y^^Y&lQ^BQhO(Mm_0>eVeAki@TV>?D&BmmBh;9b8=A zcjs}~!{NJ%LhaAMMlm{yV|ib(lh;L^n($h5RHf$<6{ zxk(;wZf$A*V{tS!nj^`{6oVbX?bt(B@zWx`vhb{xE99WoNjZq^@8YvORdzeYUpC&0 z{^saU!l5Y5WBR9yo3MU*Hb_0g&Dm(nvNP0nlCf5W0cHeCgU!GgrZi}KLI8UC$=!(k z16#RrkW)w6{l7~UK}NRFJ~M65c0w1{M@|!^cY%xfg#-WJgV95jOP%7exJY+a7=zs2 zUI?!_<-F?OwT*N5Lh}^=B@X*F)h9asdXl}0|L>9fUE;B%NC7|h8ATSM199x0HY<6KFu(iG zbp3g@(L-Z=g|#`q@~d(NswRP*-pyg~$;8OFZ_u|IdJR7^}xb z)$hWu1yyxFXLRr3g?d^X`Nr|tn7WUm~IZ+s_tEv)W15Gzoa!jFKQtgWW z@#|CjgV~f7=6m25g4XJB$8L(fiH;9qCp@p0ZGQ0aypa2>6r8e%Z*Dr1;*}#FyYld% zFSxeaKULdhmMk4AX%m3azU`F@Y@u#8!5Bi3F(KQcu5gB4x@QP=K}4++*-Q>8k{79l zbVkM$7YP64BtQxY2`M5*M_&`u#8PQy05{V$jufc9p&S)L2-*b|iYHaq*;!Rsx!(t7 zDJw6yt2y7kxch$2*yH7aRb$?a_fCJMx5yI9eFKSBGW5WVcU+0~?p+xn&A8qw`_iyF zmi{tBCfdW(Gj#s__4^=04P>Z4g}JY}n=0v@uA+cv&GHEKhlqc7ylT8j7H36`f|s9x z^C-U7Hw5{H$$VxnvMDQq$nh&{YdNB#qL%l3tb>9~laiBdJUp~t$0%L=92od9kS1m& zStn#S$Y@l2Y5@q-54J$!aL7IP_NfX>OOg%hRPd&uq;Y*YJ@)eLZxNS15O{cI%3AvS zPbJDr%c*%KEaZ|nzt0b&dAeaNg0Kx*_$>0Y9oyqc&~#P^SX<8OSQ5vx666_E*@6Qv z;!W2_C~xi-YUf*q>JZH2<>zw~jPLallpy+GG=&gghr=(@-&x-vcne#E%J@*?8Lir z=+|NNyPne0y@`=txauj`a>$FW-et6B5ncXHt*1iS#EMOnHY&SaE6> zVbYj^b;i935m5@<-^5Y<4hvEz%(&}igwN;-oBkU3oxa0&NP~FA&&FQ9jmqlYQ|eWrve$C|Hq0aLdF=Q zIdPErd3ndUg@$W`86Oi8Zc}l$WL>e_x7m=9k#Uf~()f)`4VVPdI=}Fh;n$9p7kGrP z{ic!ZQD3O1nyd{rzwbo*$o;VaQraml#W8=2Jc+^?!KggDzD1FG>j(J!C&584-+dwy zNs`UrgWB7-sUfZTvX7yoJvluZ3WLxM(Cc&mN4j2UB_*hKmbfX+ASHYFQSDZSNr=}M z8>;<93x{4=jbXvi_R(+yrcU<>eQI^gH;f=TOGG?%{?@jBzgJq3s}qqCGb_uCwXGa6 zk7C0)ZN0sX^{V(pnC^nAh&34?GLhY7u>fI`tde??>AaTQMGiwhn=F>RK|esmGdy?o9|(OVRV@J$ zjCF=O3fN?p;loFdm>7QIT=K^c&1!^|5u$AaCvB!X2$4H;!L(FJ$IJGpz<7Z!<48$? zxHuA)`XHZMc-|}(-(VD{*{cAVcW9@i8hh!ESUT#>o2) zPIc>p6hSG$-w4I{NA+#160B61#V+^mM+fN@g6P7V*#X%Q~=_Kyh=nHdMTEzEJX zfyor~AaSC-CljN1&T$ch?M<()B8W`hh`vD!wbB0iUb|*5+J!I3+fMAA$?=9wSz=mk z5?2_O!!-Rf9;cunm#3VJjrBNvgrnC1fuH-Ckw9)1xgpqjtNLUd7w*XwYS~;e_?9qM zQgn(CnZco?Fz0{}QRLQKIA`?gc|`0=@JdQ1On~%`Ck}kXV_|&W{^{E~#$WFzK9;A{ z!qP}jUgTC4MViZN;lejeg&9cx*C9P?Dg*gps7z@DGXsN^01)Grpaj5yD8k~QT37qI zBj(>{E3XGgm?=MwK>9jCJ2j@6NtqOt3(X{R&?sF-yd&3Rw+AcWsh=Fj?Z-Fzx zIvPTi(b0FoY&LhCzCFM<^lyelDvu(RzNOP7CgA%by)NA}Nj!ZY^$L(zA}2P)F>oM; z;dO(Wou2ok&&m8XsIagodH)^P1D=PvnGP*1&3hMka1S@mm#Q;y&b6F(TjFeqN$!qr z49OBwV?B`rMv44LgcK7MRVRU=4Dp}fB9yxXmWH}}oDqy(vF1kO8 z2ky~VYSDTP)oZ0w2JN`yddUB*p$pp-b{l9#v0Jes=cKlXwF#J%3YH@n(%8F&BEfLj z=PTMbkLI~yX-A(G-8SbBD&O@L>~&*%)g(6c$2ReRhwuI+M=GzT88(o<17i_`xjJq2 zb`HP$S-)oEH>k)2D^MK0x1IpBpiuc)L8-gD(Lb5^%vztN@GyGs>?r7YJT?0Er(8{c zyaA~OS9DsJ2O3??`S0UT6q2S+$=n%`EvQozSIPBwAlCf7mx_rPW@o!&8;{u}BW2+C zc;<)@J$T;r(NN#`b2FO2iofHy0BCHe;VmaKHO&Wk?|P7{EFj*F8NAD7mqHXmF zUvj0bCMG1ZJb1QK@5l)6yTnB_QwS(Z$2+D1 zYFawdAmQdOVO=@PCMMd*+8RZs2+d^Lg|Nm)Oq9rz-Kpv64+m?gtT*Ij&wjpS{8-3{ z4+EbrIty0`MmKhcS-#@_>JU1TIW`U%_x5}R@qMkf+i6YXXOa|*&L+YWz+W007sJhn zBh1njX?idnAJQ4!74wT%uW&Q^84GzQr!f3nP>Td&B8Jdei;Bf}-mOlxVejhwH5yG{ z{)U7>-9SA4deFX;`scehvHe;gVV7IK)51EkcZK9k+bWvo((S~)EbSI>_j)+tRDasT zWlDzw&fPpK0bY5~$#0vg?N6Dbc>gB%2-$~-lDsaT{jLvHE z-pNd%g=0Ej6FU&?VZ)=0cZ1AnQT$+_Lgt!kO86OyALt<0&O2|r0@36}ogdFnq3YG2~mapPk7m=+#IAsSZ% znr760BiZ+3K>NtruRRV2sfMcS!|d^kDESa)FUQ3^w&5=j7AtGVxv7q?wZN$+Y^kTt z%^Cr7X8`nKJd~qDgKn{6E^}m(_`}q<{`w#%f;lZc>FoQx&}|CG@hvScHAL*v$mFEY z=S2hJkx)(?*v8b&=12JC>*hiA#dmsJ-km>vAgFtJOR>L>YEep)qr>#ajPa03%9Vuq zQ}-0+=RJhtE^~xWR;jsRE0OrS!klWLH(gQ-V{;oR-DFG5$17bI(V&mmM1`X`LOUcF zwp8goHWXXH9=tvSLBf`vdgG!54JySo zF}%7HxS0D{0|ROj{>PhdaWQoZK}OUxG?X|Yc_lEqtG;7bD-r&fwMprf zdTFk#x^@`e`+m9y+v!34`Vk(HpXKRF87AJar9^|QU!wNb{@r-X&r$)c-{dW&d$!Z!Vbeu zP<>U^k;8_%cXPIC1V<+BY=4}oekG1uo7*2(6KmS{&%WDy^5Vm7W#_EjsZZ;^d!Kmxl_}1l7S16C zgUJLATZDF=gyDVL_;^(*A+xJ2GB;BU^W$5S6BbtbSK9mAfh)7N6P119wnOgyWVuWK z8piY0o$H8b4fUr_{q@X0y)bx`IK8vwjl$!->Dsxez?str8jI@8T93BO$Tlyu%`SX> z<5Tm-ujb?~KVEJGU+7Y~#_S}Qu0KBJ8*rJ@v)!3& z%_-7j&bRw|!(H;S;)>-4)uy>{bBMYz4D69u_E&cSfzI!P=$WVV+Ye@^POS6V?zJvX zkt--zHpE_E2mOx+Tj9ff0=#JP6oi8=x#jK!?}xP!ZH8?HpPt-E?OsW>?QiT4n4Nw> zmcNrboe$Pq<>B#V$En8um0;uzzIZV$YcFRqpiN6Q!J=+dZ#V$Cb(BG z_%{RB=1P}_tX|KM1t%_c)xeYcsi-6=9A{_rmk3H{4k-5>?4Fvo1>Gw%lTKda&Qy$C z*?Rrh_sE#VN+r{Oj%|iD_gCNd1CphG#AqB(C*X>qjj8hTxFwPexZ2tY5QC?c1s>3> z#$Eq{Sb*q(iz~V7DrDfi-&*l>X|S949T+&eqO`S8q@1sLTK`xq_@r(0WZ^txLAR%@ z&{3yLwES-Q&SLpf-iw|a|0jXLC!3M`V_9bs z5*Hnu`&mId(9ue>tD}Xa6S?zezPWPeo6?|jY%iUidB2`aJ@B-0e5G&N=2zIKpP5Ro zrx^3htERty4K*g{69Xke8C9|OZA7D%>z^7Qi3pC&v6Y!N?=o2h-LcNPs4G=zX7;50 zw;+H`(XVdi{Z!=tG}+0;9}PIy6qn=}wH|x4Az5!vJv=5x1C~784^Bw$Gt$z(&$^rz zTa{`%XV9`j&NTUrHZEWnQIQ+Pv!DBX`2lP1cFCN=>Ky`Z8oiiV0xla2k8|o!1s)Tb zaGXO5@ZrWp+3Mk+5sQ$6_3sC5N~!l=nXdD+m=-& zb*f`QC`ZJ)Ui5>7*>k}HeFM%J0yayh%ga<|$1!C$%>gS$HxD&iGgr|~jcjITKguqo zS4m|xBox$lnUJL;n-s`6a^&9Gaui=Dj@{r#NUR$%EP}J1n^T6sCHs4YmhQvmQ3wd5 zhpJosJ{aq1D?=!O-#kzKsQ>p*O|i?kuQ!=QriFdHK)zcuRZZ z_u-S=bv%hN(tUp|!rJ;wGh2wmeEnq}ILY1qwk6lwXJ@={KR9tl;bS%_ki_!y|S6^MT+l z2bRn4C()b6cmuz$QTs%R$(LEdhqbf8hvIP99nYI3E8U1esg_?Rx(h5azI|_XVu`US zKXFzE4rRJ{M@e(gy`szp^77Z@gGRix@f1zN*NoED zE~s2|e_?Zz-}yZmAu$4n*%zNQGJhA~uK%vpts#A`W7x1`W%K)25lh8LV_&M@hDv(y zT`>b=hSDAp(TW{GYU<>%IEm@XE_8uc=Esq$o^#ez4^;o+E+%{Y)5k@SZ)##sq}(H| z$I!nQZdg`jWo0>Fq8rbI?-J<#L)~r0>_gf34v#t$>$R_bqJW&>FQ4e_z7OT@Xw`-_ zPhK&X**8xS_~M`h+coJBo4J-N2LpElU34uldt5rt4#EsQ1WkzPYTmeSC7EMd`S1SgH|6Iq%wMk&vfj6 z4ujrJr+XP)F-~9l5K4^RXN8hIy-GYW>@qTVv;4U0+W*NnuLgsdx>t+Yisv(;;&O7y%-PbmrAK-vU$Qc?=y(j z6|Oon$$U5~MnHrAjkF|Z*Uk>sDqCA0nwIHdgWvBfdv9j8k{TK$j=cY>yh%yFW*a*jpcc?38oe}i_7Q&C_jR<_QVIs{(`?1pc=p(E6AB%=052Cg(C0SR zY6ZGhv}-L0_j5Upotc}w#S3mYyXU}g*B1&wPc=OHV5E7c=4jx9jl8j`ygf3kys@^l z{m3AwVpP;TFuSpo*U>DUy%cN%;A)Af_iK_}Tha}dRW_Pl#W}|4@Ewyw(isM;IzpfS z6s9U^wJL;OzBa)Ie2Fb1f?0+7Qd^JtxC%8dR#GrOH^&XKxuE8;fqg{|;5GU`hI%Dw zw^~;WiAn|m$$R=_1)?%@f8$m-S0Ot-k=xW{)Y#aVo0FqxXk_%Iu<&um9ju(l z(bCf5fJ5;M)_tt4t^H(IIxa4*zqj{|bkOCb#O6}pJ(c>viq>CgKgvJfrF9W{ZsXzm zxMN4Y%B^`)Uki+P@sv0;cIf>lE~6su{k~A23t6iS(%6Z;;~Cc?`(}6Sq!>4qLPiPK z@x8(u6`0n~6-}0<)~UU)iS%{BMHepI#~Y*p7Y7s(y!1K^cw@T{Eg29D%LyXSz}>Um z6(AcQ5or53k^q&XO#nHDM1w{TB{{LBxaAn$EzoYK1edt*ayTe+2xvryDlu(fcQ7qx zJ*G7i?TNd-ufKqx+|qRgAFn&!rzna8D+N*`RnZ&YMG3SB_4tMq#6ORDSDzzHK$Rjd zdOD)3y3fDgbNxn6HrnqZwP(U7X)si(3l^51_+69TIwY{%m4z*v2`B0Rr1wk9%Jj-1 zWrEKenGV4yo=Tm`j)R{~JH6-DW|+HNnF3}6-_KJIsbz@~C3cfEEHSq|A(ltCqg-uo&LGdqTJd?P|PlA-^gZQ$`4pAN!HlHmYT zNo&p+BsSlCl1n8^&rTzYPpNB10_)p~?4@%)zNpZf%NDINU2yf(3(TxQKR}ad2C4uFV$CIhfBIZ)6Ooxx~}f&)2C6wVq#CNtaA2i=bL>; zC}d~8Ms@jQCkJYtttS@q4fY?Ds4bk(pcIGuKTW5sCx05JH^4Z?5)JV!y&mt;Pf4bk zF=0m6cV9 zCK>FGbS|J2{(!YsEXjay!Jkh!?EBc$wXVEW|0Rg=6=>3BAVxWSxna<6Rc*U3=+=mN zXL4Fmt(B8O4=v%;tEsUqam4QaYQI1T|2hG7_=FmXb%2#FczHCu6qUjOwN(M1mY>5&4jXEeNuQGf%NOZTB`-`}CO@SS6T(@ArUK zrZ?yf74UysAaV%%e~Zi{+iTY3BNgkxK?(jK_&19l!-b)Bt3WI5D_2xi%)ziky9Es+ z`wK+utCA%Eo3?Yk2l>r6-V6~3Rx8Yr>7(>UkKTge;S`65hxhroq>B*J;TDXCU~|v? zMNz%m5gHO}uYL^fr^{`0o9o;+t$}%$3+r*v_gO*LcB9W?1z2ROROEkK_59EV+9D~I zLnR|14A=sFBq`9uvdfIksGQ?IGfmbt+ z^e2BjxUkzdJ8T%3X%H^GpTP{M&fYm$jA)}mgd_zX2miO2Jbk{s7g z&!R=(H(T(}_9yej-Q_ismk&|oIcyRfn)6w#|D7{z?fS8Kh5w$fme$bwQHphDQ3Nj; zF;c7;-`cj3;3qlegc@ADDNz5WY0Uhc&oXaYq~}9?#0&5e4}eRH)B6mONeo6y;?v{k zTe>kx_ulvT!Lr6ch=vetobC$|2(kgIZFX}Gv_3-&Y(wb{9tW zc4E5TbrL@n?e=rcKeIHDZ{l6$)&y2NN>l|%OAJn=#VLW{-6TtCLNCDJKZzUakd=!E z4dY>A)~ z;~FO&$k0FVy)GC`LE&eik=%WrvII{0OMFm(g{iWzsML5B-DjM1LC*lU?c!XS`Vw3>i!d4i_ z@8KTEk8k9KtE+1f&uyBA#spF($0{u8+Ep|-U*A*ZD*ALhNaSt6y+;f)T%L;2dyQjgy zZJV2$y=m9v|1f7bp2CPyb{HowY$AgZ(VfeR)!UMVc3L>&hO_j8QN1mrk;6k{4SamZ zzkcPulTjvW#wz5J-D*3!EP;pbXY1V+v57|R_<9Qo8ChRn-@9)!k^k6*0_hF%>wu!I z@L>};NJj$nV+cBFz>yTed;mUFxD)ACTvEas_RzfJSoOk^qGbBNwP4}@NRIYvB4mkZXltozh%P^!JHv{%Ypfofri2b5rfm zHVJI$>xLoJMG>XCwR(Va&FgRo=F6DKpQB<3_S&X%x*R2Ur8H>Pj9kuXG2O}R=jG;> zI!v)kc>Ir^R&WZzP|3kigAFzTmJ0Zh5xF^4PqC1ft~kg4pZ|G*jSJ=&P+$Cmv|miT zVmtpmkVd5My3ocQxWc}_JJcnkrX0${1nhL-!xP?C68=LYQmp|kjT})=`>|E;1T5qB zXMH^>qMHM22khiwaj5@Ato{N<=oh!hkYXj28AdZ?L~$uuS$cFL{1=OyS%F+T!KWd) za)IVyj(lq$Yn?`azb}Oi1}%M@Fisj+*Y9$fY2Y6s zOt}-svmUk56Gv5!lk49Tp&JqFI8pkxXXP#9t;*`VdS#|Ef{5G}6D zqzh?VUu??$;)4<*yjW20&(=nA(zqxVNn?d^(*2(&z@H|VCYmOhR__E04-b7>JfEMc zdOoGknOqk1pw4ySh0v`#H~YK0<=D8XsM^bWd)__$my(8OsHf-gYDr1SljGHtEp%aV z6b;{h^P36s^XP}5=c$gI(le(r1{uP7>C;lN{)mq*mvAccfaUzd0NqE_PXBxhzynIn z+L!^oaF1DEAG5(sDNeEN*$eoy#icTZxo- z=v{>@*+5BLOSy|>58vIpx>s?J^#;uvX$3ZMGJnOykg6cIx3+X&;=rwM%K7B{k9q#p z)0SzG8OzAMzM#?757!|eduL~?C;YE1L$xmt-h$u(i%hbZ+jA)~=%3pbU(3ogeh?z} zIy~q8o1b7rE%dH%m$>bvDV&6L1A|G(oHxZA8vQ{%Ja%+^{NO*<%=R>51n3Nhzyl&8 zB7R++EG&p&tBQ9SVeGN=L=dzsE#ZG%VnJ?MF!mm8yz;kp@KgTYc5HwO1gM%n_|(Lm z>XQg6=Hcf`DGr)HYYv&(;K%dysws3>kLfFaZIed-#n9&erXHD{0cUv)$?=U2NEf{zCANuR*G;gGbV(jsr?#b4Dep6RuH*Z8?(@fl+5(Ij<9m(Z%8vO=C!HxzmB{&bdT_rCPb*u^tMt+1fr zXC(yLc=Q;7>ue)?R#qFfI$!+x$)CrD5rz?7;cYF%Ot(g}9`IPrVQFqAsFI_rusPAZ zD(MK;^VaBbU2S00;RD+44<@^-6Kh$V3bW}%#}`RvSn#DOk-Ranv0N0$FqvGy8txPz zxasGUOE}~oxfc5QR?&Qb*!pI=aZU7*DweSI%x0wjyv6F=S&i>-kGQ#6N5TF(w4Xjj z4PF~oMTu?egaG|8`RQArg&Srf3>6v&A(t|K4@io#UE=LB8poO9p$XQ^nY2cS2%%5L z755c9#pB2MOMXFkn*a-)%f27B3_<4OXhzcX6C%`OFj|iXp?uFw<1rya;~(s zF?u~MDS7Y0U_KK?$bPjW_v~IV$9>f_e&s&=+> zAvSoAzK1}H|G1COYj0Azkl%rAY+pqV&rjWB%9wk(;0If14x9+ZV4(KV$QJXdhwoiy zF`mE^;q*x7DSIYWTSsEx)VTCus6)ZX4PIf0?>FEl&nnrbwy(}S~b zc(SbDN9z@XxBdS3c*4@;AZVI>*oH~jC_9$rbB1}UWCM}iO;~kdI6nMPP}%OCSFDetoB!wzBbE8d<2dgi7B^kjRemqBmJZ~K>bg9RA zSOc!5m#`6S;(*O7zQjP2dU-cpks7YsxbCWXD)jwdzdCx$&*D^`M{wv4)-M!=)8-9V z5}hq~-m`adsVH^U;#D#5L39?y+!h7F%b5%MU#vY2Rv}{WDN4wH<0(KLq_?k+gMnd^uVe4Xr;|}J-+3R~)Fi8(>-l?4HDAMAAX)&vo{6LEg*_mqz z+!x=nH90@%JX?7lCa2NHD>)6C2n?vt3_+3RvikX;|(>3ps zstqh3^We(U4RahFLBDP=GBUrN401O%W|`iZRN6fal|VJ4)RQu_^0AzZsm5iHACHu{ zZc=AwufkqL{@%W7-|_Efc^BewpSLVtC2k~izHjkTlWY)d<6wu_xsm8O&Ii$-KsIMa zW>|dcEny-rf2N*r&wUyNV*C{oy<8E_*tGhNU$KSM<%^$<9bjf>$O+BpNZy`pVPS)= z&27y#fuaFRrfJ4OO6LnCIV?W!gI45F(%&esuFl5xJI=(E4PM17leUxlxIWq*QDcp9 za&jz{r9nQ*>ngSiNmfRiVS$RBQpHx{OboC&S5S=|75~+pY#B5MYie28UOcJwdO7p6 z_tI#enzs;_UhuqMeJ4Xv$FJ0}jvsx#c?!4>%^LEU)qU#W?cc(1V6P+Boj2rD^AOd~ zUyETP1O1efaG-%C(ySZw^kZRv-s1WD1QNe#NqVU$6JAcr`~lFB2KHFH!wBbJrV|fd zoX4cCcYG~78cx>xf|ks0zEo&<$@{3|1rHei==%49{-Oa^d_1n7-?VF3ug55vzq&Wd z7am!v9mw_#XEADno4YJQhgeuMm?21<%)6w3Wiy{;8K9U{&C=F-Y>xzoAGFt&Gp*wt zkL-#GOMe}wN=*1s)r_MXTs7_sN@tdPtT*x61Ml$Jz|XHoShVA7z$QdIMn}w<8g5dt z4nY!~hD6@VDfRM)nXLZ$jWZY8n4oawbyzzr*E`Ix&ww^qB!@+q!1>0=t-_wky= zS+x9!S4g9;ZAn;6IT^5K4dqe1`ek^e^W3nslty#y;05ZebRpDxGxDYK<%BDa@ci=P zY=TUQMyP)D;5)$A*av_~p#dM?5MFJ-+ib z(=twBgF>}kXUG_-8aW=7d_pEg&ph|cdX2N@1*Q-06Dh@6lE<(r&sGtL{wOcje$MRB z^=1Fk7K!9-v-1u7B`0yQYQl7}XL0dv&+7DR-fXNThjLU!IDIHmQE8h+7G7kb3uWqM`c;OcO}f+O!H9eRn& zN&6g;-ZbLf?P4!YQ4j|>e;*;qc7g59^;n;ha!yMH@E+=g%H1*~|NU!&E?)EOe^^3u zTxcnNT3*sP5{*L|daQ?$K<(?yVRqnP;F}v%k|&Z0OL>M$ssRF|jEuc;&TgF@eRV7$> zx~mtX-|k3AFlxGkt|06Ol?hH~$^;Ow+UI>8-8)qWVpb(H8JI+cwrM8Hf~&NgpI16k zPMY=H%_*%`p`Q0=bTwFYnj`R>H`nm=)P;<$!?UFWq4IBN=f#2TBL=?kw;=v4fazg4 z`}al-IQ)A;JI1pI2Q97_xbtZ3Hg@++@fwZU=9gdR4YvuKl89SJVm5kYs87_dB1l&q z8JfB|M!mPPBS%#5rP_C~|pYc-#ATrP%;O|MZ+M1tW!<9Mfq^& zAqrySn_c)fTDT{H`yjmQ+<2GCg5`Z@IX-X72$BS;%=z4Vd9#qK3silEk7EIq=tf9+ zmRi;jN{@yNzOeUg=kRd^p$^$^jBX`_xv}z0EGbNyMcOQ#_;)?Xjwm35Z79ELm7qfyD(=#Op37O8c7bxZJLVKX(32Q z7sR#nEY%Py{F-JUTu3IRi_l!twvK`b7b<3YCSZcSwyuy81qpTKJk-UP@+Pc|zTtr%9x>djrpzag#a3HVftVC0%I8ZKVj%i9=)u@7%ZZ^x{t|?dVp1;7}Iz5y-oCzS}zI6Zio7>)} zWe+jr-a1K>`Aj-@x4e^E$LC`}7%~(@54C8H9miHJXOA|{`qmAJt)G8)low(~?=Gh< z5oQBe;hx;hwcCpsAI4q{%uA4x9G?##LEnI$)pv8=MuU9VO}G^#$ZNCN$la_I;?Agn ziZma@N}?e0*1RG~?TGo2IPYAYi;XUbu<`*sCA>uVk}Z!OO#~II?Fo8an?Cg_`(Zh$ zQ_L~gd?GVYs(48%pz^47`Na8}hlbmuCtr;+;rlPw zh4_b1!e(a7?jn@!$ebb0lt;0Wb&+n1%#kbXqc{r`N!buU{VcdmobS?9XHNgb!Bci` z9F(CyJAoc_yCU#cOk$A1B>m$NDRMrEvodWILMfseC6CAA#Zi9!Rp7iTRb)+ zhh%=~!wNfP>Hp~rg!&+s<(Ceq`5@B5J{WTe>8$gm7)TshKfll&;2p(IarQToEY$|z zr(0nC3HLX$2z4moQoHXm8y<2*BE|io&nc)_=O^4S!s?tyD7;J0ZaxJP-vtdnQYR{Yb>R>h= zB>C)-_mj~EI)HTN;WVODyS+LvG+q^8Qd8gZe983+F(0LN8>XiVStoTSn8<~2I3ScG zp=}%bf>lUfY)PL?YmMMF0S-JEGB|%-K8p*72}uf1i_+@9a~_hl;3S;@;Fodd?S95# zWJV)a)bzy*@q;)X6LLOOt4Q{*!Q44P<`WhoKHS#R)-=dDEGC%nch2EgbY{~G2@1|t z8_$I*Z{gG*SrvUSnd7Bfb$&iB!>#twad?%`jBMP3!6_=RoUgAuIm&7&#a~7PZV|}M z227I;`MP?yBBnfv9Ql&urasiW&U`m9wWvr7`fz zivbZyfh^tlW*>afV3BrJE#)sE9_h9gwQtoBle24I95G3PAQipQTJ;Mnlia`~!Tc+$M7x7Woj`R2=Bm@9@<|)l$!fG|5c`^W@KI}) zu!gOnq&2nbsKEq3EgiTI7&wnnjT}%6d|tiqR!7*UXQO%_p*Ooiz7Cr5h`ms-2ndT1 zD2E2WUk&&D@ZjAOdPL^F%Ql0$QQm|iqRzre1UGtb?oeqZINzC`u^A=a9fX1!8qcWS zN95ho24WM(j=+f)5ryqwntqZGdpzGN?l@WTW%ejhO3zAm`*}QdiPO)ua3(mg( z?g(J~zkhJgml^Zr zh!-y-5`-rDprXh|SMgJmz&P$4c2*8FqFNj}4u;h86#m7K-#vMW=!OWLT0GgzR0QDp zZqdgLr1$d65=YbmTRZ$~ig(%w)8o?KV+wVmPSpJWGrJ9}IfvZ9(~%;g%Nh1=+^On)I&M<- zoSFpg8!f$%b1k&|7^RrDtj*7v5O@CrJ8+8p26zIjYtbW_1?BVhPdK_Xb?VQij~DXQ z-bt47OCJ!+fgXcV$ag_%5o4jmfoHLiq4zHI_WHi!Xa$}-uo$=`rzIU6F)LVrYeSX@ zHt*iGZ{31EE2p*VSMO4@fSiY+Y5?^OFkT=o0cwE-rz_HV8W8t`R%SsW8<-&>CeTl# dSH$0XkGE>#UWySyi literal 0 HcmV?d00001 diff --git a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md index 8ed0bcd91e..3a8b6f2226 100644 --- a/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md +++ b/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/about-your-personal-dashboard.md @@ -40,9 +40,23 @@ You can also find a list of your recently visited repositories, teams, and proje ## Staying updated with activity from the community -In the "All activity" section of your news feed, you can view updates from repositories you're subscribed to and people you follow. The "All activity" section shows updates from repositories you watch or have starred, and from users you follow. +{% if for-you-feed %} +The main section of your dashboard has two activity feeds: + +- Following: Activity by people you follow and from repositories you watch. +- For you: Activity and recommendations based on your {% data variables.product.product_name %} network. + +### Following feed + +This feed shows activity from repositories and users you have shown a direct interest in, by following a user or watching a repository. For example, you'll see updates when a user you follow: + +{% else %} +In the "All activity" section of your news feed, you can view updates from repositories you watch and users you follow. You'll see updates in your news feed when a user you follow: +{% endif %} + + - Stars a repository. - Follows another user.{% ifversion fpt or ghes or ghec %} - Creates a public repository.{% endif %} @@ -51,7 +65,26 @@ You'll see updates in your news feed when a user you follow: - Forks a public repository.{% endif %} - Publishes a new release. -For more information about starring repositories and following people, see "[Saving repositories with stars](/articles/saving-repositories-with-stars/)" and "[Following people](/articles/following-people)." +For more information about starring repositories and following people, see "[Following people](/articles/following-people)" and "[Be social](/get-started/quickstart/be-social)." + +{% if for-you-feed %} +### For you feed + +{% note %} + +**Note:** This new tab is currently in public beta and subject to change. + +{% endnote %} + +This feed shows activity and recommendations based on your network on {% data variables.product.product_name %}. It's designed to provide updates that inspire you, keep you up-to-date, and help you find new communities you want to participate in. Your network includes: + +- Repositories you have starred +- Repositories you've contributed to +- Users you follow or sponsor +- Users you've collaborated with +- Organizations you follow + +{% endif %} ## Exploring recommended repositories diff --git a/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md b/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md index 671697cc51..8858b9e749 100644 --- a/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md +++ b/content/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github.md @@ -24,7 +24,7 @@ If there's a particular topic that interests you, visit `github.com/topics/ Date: Mon, 21 Mar 2022 13:33:46 -0700 Subject: [PATCH 13/18] New translation batch for cn (#26386) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=cn * run script/i18n/reset-known-broken-translation-files.js * Check in cn CSV report Co-authored-by: Peter Bengtsson --- translations/log/cn-resets.csv | 1 + ...-security-hardening-with-openid-connect.md | 204 ++++---- ...g-openid-connect-in-amazon-web-services.md | 36 +- .../configuring-openid-connect-in-azure.md | 36 +- ...openid-connect-in-google-cloud-platform.md | 44 +- ...uring-openid-connect-in-hashicorp-vault.md | 48 +- .../targeting-different-environments/index.md | 4 +- .../using-environments-for-deployment.md | 20 +- .../workflow-commands-for-github-actions.md | 466 +++++++++++++++--- .../configuring-a-hostname.md | 8 +- ...ng-a-failover-to-your-replica-appliance.md | 39 +- .../restoring-a-deleted-repository.md | 16 +- .../about-migrations.md | 2 +- .../checking-for-existing-ssh-keys.md | 2 +- .../using-ssh-over-the-https-port.md | 2 +- .../secret-scanning/about-secret-scanning.md | 4 +- ...e-vs-code-command-palette-in-codespaces.md | 28 +- .../creating-a-codespace.md | 2 +- .../deleting-a-codespace.md | 2 +- .../using-codespaces-with-github-cli.md | 32 +- .../get-started/quickstart/fork-a-repo.md | 2 +- .../managing-access-to-projects.md | 2 +- ...anaging-the-visibility-of-your-projects.md | 22 +- ...om-repository-roles-for-an-organization.md | 150 +++--- .../requesting-a-pull-request-review.md | 6 +- .../about-code-owners.md | 2 +- .../searching-a-repositorys-releases.md | 2 +- .../content/rest/reference/codespaces.md | 4 +- .../release-notes/enterprise-server/3-1/0.yml | 1 + .../release-notes/enterprise-server/3-4/0.yml | 5 + .../data/reusables/code-scanning/beta.md | 6 +- .../rest-reference/orgs/custom_roles.md | 2 +- .../data/reusables/secret-scanning/beta.md | 7 +- translations/zh-CN/data/variables/product.yml | 2 +- 34 files changed, 773 insertions(+), 436 deletions(-) diff --git a/translations/log/cn-resets.csv b/translations/log/cn-resets.csv index 76e01604a5..f29b21ffe3 100644 --- a/translations/log/cn-resets.csv +++ b/translations/log/cn-resets.csv @@ -138,6 +138,7 @@ translations/zh-CN/content/codespaces/customizing-your-codespace/personalizing-c translations/zh-CN/content/codespaces/developing-in-codespaces/developing-in-a-codespace.md,broken liquid tags translations/zh-CN/content/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace.md,broken liquid tags translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-in-visual-studio-code.md,broken liquid tags +translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md,broken liquid tags translations/zh-CN/content/codespaces/managing-codespaces-for-your-organization/enabling-codespaces-for-your-organization.md,broken liquid tags translations/zh-CN/content/codespaces/the-githubdev-web-based-editor.md,broken liquid tags translations/zh-CN/content/codespaces/troubleshooting/troubleshooting-your-connection-to-codespaces.md,broken liquid tags diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md index 6b23804431..f90b8b9df1 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect.md @@ -1,7 +1,7 @@ --- -title: About security hardening with OpenID Connect -shortTitle: About security hardening with OpenID Connect -intro: OpenID Connect allows your workflows to exchange short-lived tokens directly from your cloud provider. +title: 关于使用 OpenID Connect 进行安全强化 +shortTitle: 关于使用 OpenID Connect 进行安全强化 +intro: OpenID Connect 允许您的工作流程直接从云提供商交换短期令牌。 miniTocMaxHeadingLevel: 4 versions: fpt: '*' @@ -15,45 +15,45 @@ topics: {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -## Overview of OpenID Connect +## OpenID Connect 概述 -{% data variables.product.prodname_actions %} workflows are often designed to access a cloud provider (such as AWS, Azure, GCP, or HashiCorp Vault) in order to deploy software or use the cloud's services. Before the workflow can access these resources, it will supply credentials, such as a password or token, to the cloud provider. These credentials are usually stored as a secret in {% data variables.product.prodname_dotcom %}, and the workflow presents this secret to the cloud provider every time it runs. +{% data variables.product.prodname_actions %} 工作流程通常设计为访问云提供商（如 AWS、Azure、GCP 或 HashiCorp Vault），以便部署软件或使用云的服务。 在工作流程可以访问这些资源之前，它将向云提供商提供凭据（如密码或令牌）。 这些凭据通常作为机密存储在 {% data variables.product.prodname_dotcom %} 中，工作流程在每次运行时都会将此机密呈现给云提供商。 -However, using hardcoded secrets requires you to create credentials in the cloud provider and then duplicate them in {% data variables.product.prodname_dotcom %} as a secret. +但是，使用硬编码的机密需要在云提供商中创建凭据，然后在 {% data variables.product.prodname_dotcom %} 中将其复制为机密。 -With OpenID Connect (OIDC), you can take a different approach by configuring your workflow to request a short-lived access token directly from the cloud provider. Your cloud provider also needs to support OIDC on their end, and you must configure a trust relationship that controls which workflows are able to request the access tokens. Providers that currently support OIDC include Amazon Web Services, Azure, Google Cloud Platform, and HashiCorp Vault, among others. +借助 OpenID Connect (OIDC)，您可以采用不同的方法，将工作流程配置为直接从云提供商请求短期访问令牌。 您的云提供商还需要在其终端上支持 OIDC，并且您必须配置信任关系，以控制哪些工作流程能够请求访问令牌。 目前支持 OIDC 的提供商包括 Amazon Web Services、Azure、Google Cloud Platform 和 HashiCorp Vault 等。 -### Benefits of using OIDC +### 使用 OIDC 的好处 -By updating your workflows to use OIDC tokens, you can adopt the following good security practices: +通过更新工作流程以使用 OIDC 令牌，您可以采用以下良好的安全实践： -- **No cloud secrets**: You won't need to duplicate your cloud credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. Instead, you can configure the OIDC trust on your cloud provider, and then update your workflows to request a short-lived access token from the cloud provider through OIDC. -- **Authentication and authorization management**: You have more granular control over how workflows can use credentials, using your cloud provider's authentication (authN) and authorization (authZ) tools to control access to cloud resources. -- **Rotating credentials**: With OIDC, your cloud provider issues a short-lived access token that is only valid for a single job, and then automatically expires. +- **无云机密**：无需将云凭据复制为长期 {% data variables.product.prodname_dotcom %} 机密。 相反，您可以在云提供商上配置 OIDC 信任，然后更新您的工作流程，通过 OIDC 向云提供商请求短期访问令牌。 +- **身份验证和授权管理**：您可以更细致地控制工作流程如何使用凭据，使用云提供商的身份验证 (authN) 和授权 (authZ) 工具来控制对云资源的访问。 +- **轮换凭证**：借助 OIDC，您的云提供商会颁发仅对单个作业有效的短期访问令牌，然后自动过期。 -### Getting started with OIDC +### 开始使用 OIDC -The following diagram gives an overview of how {% data variables.product.prodname_dotcom %}'s OIDC provider integrates with your workflows and cloud provider: +下图概述了 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商如何与您的工作流程和云提供商集成： -![OIDC diagram](/assets/images/help/images/oidc-architecture.png) +![OIDC 图](/assets/images/help/images/oidc-architecture.png) -1. In your cloud provider, create an OIDC trust between your cloud role and your {% data variables.product.prodname_dotcom %} workflow(s) that need access to the cloud. -2. Every time your job runs, {% data variables.product.prodname_dotcom %}'s OIDC Provider auto-generates an OIDC token. This token contains multiple claims to establish a security-hardened and verifiable identity about the specific workflow that is trying to authenticate. -3. You could include a step or action in your job to request this token from {% data variables.product.prodname_dotcom %}'s OIDC provider, and present it to the cloud provider. -4. Once the cloud provider successfully validates the claims presented in the token, it then provides a short-lived cloud access token that is available only for the duration of the job. +1. 在云提供商中，在您的云角色和需要访问云的 {% data variables.product.prodname_dotcom %} 工作流程之间创建 OIDC 信任。 +2. 每次作业运行时，{% data variables.product.prodname_dotcom %}的 OIDC 提供商都会自动生成一个 OIDC 令牌。 此令牌包含多个声明，用于建立有关尝试进行身份验证的特定工作流程的经安全强化且可验证的身份。 +3. 您可以在作业中包含一个步骤或操作，以从 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商请求此令牌，并将其提供给云提供商。 +4. 云提供商成功验证令牌中提供的声明后，将提供仅在作业期间可用的短期云访问令牌。 -## Configuring the OIDC trust with the cloud +## 通过云配置 OIDC 信任 -When you configure your cloud to trust {% data variables.product.prodname_dotcom %}'s OIDC provider, you **must** add conditions that filter incoming requests, so that untrusted repositories or workflows can’t request access tokens for your cloud resources: +将云配置为信任 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商时，**必须**添加过滤传入请求的条件，使不受信任的存储库或工作流程无法为您的云资源请求访问令牌： -- Before granting an access token, your cloud provider checks that the [`subject`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) and other claims used to set conditions in its trust settings match those in the request's JSON Web Token (JWT). As a result, you must take care to correctly define the _subject_ and other conditions in your cloud provider. -- The OIDC trust configuration steps and the syntax to set conditions for cloud roles (using _Subject_ and other claims) will vary depending on which cloud provider you're using. For some examples, see "[Example subject claims](#example-subject-claims)." +- 在授予访问令牌之前，云提供商会检查[`主题`](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims)以及用于在其信任设置中设置条件的其他声明是否与请求的 JSON Web 令牌 (JWT) 中的声明匹配。 因此，您必须注意正确定义云提供商中的_主题_和其他条件。 +- OIDC 信任配置步骤和为云角色设置条件的语法（使用_主题_和其他声明）将因您使用的云提供商而异。 有关一些示例，请参阅“[示例主题声明](#example-subject-claims)”。 -### Understanding the OIDC token +### 了解 OIDC 令牌 -Each job requests an OIDC token from {% data variables.product.prodname_dotcom %}'s OIDC provider, which responds with an automatically generated JSON web token (JWT) that is unique for each workflow job where it is generated. When the job runs, the OIDC token is presented to the cloud provider. To validate the token, the cloud provider checks if the OIDC token's subject and other claims are a match for the conditions that were preconfigured on the cloud role's OIDC trust definition. +每个作业都从 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商请求一个 OIDC 令牌，提供商使用自动生成的 JSON Web 令牌 (JWT) 进行响应，该令牌对于生成它的每个工作流程作业都是唯一的。 当作业运行时，OIDC 令牌将呈现给云提供商。 要验证令牌，云提供商会检查 OIDC 令牌的主题和其他声明是否与云角色的 OIDC 信任定义上预配置的条件匹配。 -The following example OIDC token uses a subject (`sub`) that references a job environment named `prod` in the `octo-org/octo-repo` repository. +以下示例 OIDC 令牌使用引用 `octo-org/octo-repo` 存储库中名为 `prod` 的作业环境的主题 (`sub`)。 ```yaml { @@ -88,116 +88,116 @@ The following example OIDC token uses a subject (`sub`) that references a job en } ``` -To see all the claims supported by {% data variables.product.prodname_dotcom %}'s OIDC provider, review the `claims_supported` entries at https://token.actions.githubusercontent.com/.well-known/openid-configuration. +要查看 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商支持的所有声明，请查看 https://token.actions.githubusercontent.com/.well-known/openid-configuration 中的 `claims_supported` 条目。 -The token includes the standard audience, issuer, and subject claims: +令牌包括标准受众、颁发者和主题声明： -| Claim | 描述 | -| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `aud` | _(Audience)_ By default, this is the URL of the repository owner, such as the organization that owns the repository. This is the only claim that can be customized. You can set a custom audience with a toolkit command: [`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | -| `iss` | _(Issuer)_ The issuer of the OIDC token: `https://token.actions.githubusercontent.com` | -| `sub` | _(Subject)_ Defines the subject claim that is to be validated by the cloud provider. This setting is essential for making sure that access tokens are only allocated in a predictable way. | +| 声明 | 描述 | +| ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `aud` | _（受众）_ 默认情况下，这是存储库所有者（如拥有存储库的组织）的 URL。 这是唯一可以自定义的声明。 您可以使用工具包命令设置自定义受众：[`core.getIDToken(audience)`](https://www.npmjs.com/package/@actions/core/v/1.6.0) | +| `iss` | _（发行人）_ OIDC 令牌的发行人：`https://token.actions.githubusercontent.com` | +| `sub` | _（主题）_ 定义要由云提供商验证的主题声明。 此设置对于确保仅以可预测的方式分配访问令牌至关重要。 | -The OIDC token also includes additional standard claims: +OIDC 令牌还包括其他标准声明： -| Claim | 描述 | -| ----- | --------------------------------------------------------------------- | -| `alg` | _(Algorithm)_ The algorithm used by the OIDC provider. | -| `exp` | _(Expires at)_ Identifies the expiry time of the JWT. | -| `iat` | _(Issued at)_ The time when the JWT was issued. | -| `jti` | _(JWT token identifier)_ Unique identifier for the OIDC token. | -| `kid` | _(Key identifier)_ Unique key for the OIDC token. | -| `nbf` | _(Not before)_ JWT is not valid for use before this time. | -| `typ` | _(Type)_ Describes the type of token. This is a JSON Web Token (JWT). | +| 声明 | 描述 | +| ----- | ------------------------------------- | +| `alg` | _（算法）_OIDC 提供商使用的算法。 | +| `exp` | _（到期时间）_ 标识 JWT 的到期时间。 | +| `iat` | _（发行时间）_ JWT 的发行时间。 | +| `jti` | _（JWT 令牌标识符）_ OIDC 令牌的唯一标识符。 | +| `kid` | _（密钥标识符）_ OIDC 令牌的唯一密钥。 | +| `nbf` | _（在此之前无效）_ JWT 在此时间之前无效。 | +| `typ` | _（类型）_ 描述令牌的类型。 这是 JSON Web 令牌 (JWT)。 | -The token also includes custom claims provided by {% data variables.product.prodname_dotcom %}: +令牌还包括 {% data variables.product.prodname_dotcom %} 提供的自定义声明： -| Claim | 描述 | -| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `actor` | The user account that initiated the workflow run. | -| `base_ref` | The target branch of the pull request in a workflow run. | -| `environment` | The name of the environment used by the job. | -| `event_name` | 触发工作流程运行的事件的名称。 | -| `head_ref` | The source branch of the pull request in a workflow run. | -| `job_workflow_ref` | This is the ref path to the reusable workflow used by this job. For more information, see "["Using OpenID Connect with reusable workflows"](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)." | -| `ref` | _(Reference)_ The git ref that triggered the workflow run. | -| `ref_type` | The type of `ref`, for example: "branch". | -| `仓库` | The repository from where the workflow is running. | -| `repository_owner` | The name of the organization in which the `repository` is stored. | -| `run_id` | The ID of the workflow run that triggered the workflow. | -| `run_number` | The number of times this workflow has been run. | -| `run_attempt` | The number of times this workflow run has been retried. | -| `工作流程` | 工作流程的名称。 | +| 声明 | 描述 | +| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| `actor` | 发起工作流程运行的用户帐户。 | +| `base_ref` | 工作流程运行中拉取请求的目标分支。 | +| `environment` | 作业使用的环境的名称。 | +| `event_name` | 触发工作流程运行的事件的名称。 | +| `head_ref` | 工作流程运行中拉取请求的来源分支。 | +| `job_workflow_ref` | 这是此作业使用的可重用工作流程的引用路径。 更多信息请参阅“[使用 OpenID 连接和可重用工作流程](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)”。 | +| `ref` | _（引用）_ 触发工作流程运行的 git 引用。 | +| `ref_type` | `ref` 的类型，例如："branch"。 | +| `仓库` | 运行工作流程的存储库。 | +| `repository_owner` | 存储 `repository` 的组织的名称。 | +| `run_id` | 触发工作流程的工作流程运行的 ID。 | +| `run_number` | 此工作流程已运行的次数。 | +| `run_attempt` | 此工作流程运行的重试次数。 | +| `工作流程` | 工作流程的名称。 | -### Defining trust conditions on cloud roles using OIDC claims +### 使用 OIDC 声明定义云角色的信任条件 -With OIDC, a {% data variables.product.prodname_actions %} workflow requires a token in order to access resources in your cloud provider. The workflow requests an access token from your cloud provider, which checks the details presented by the JWT. If the trust configuration in the JWT is a match, your cloud provider responds by issuing a temporary token to the workflow, which can then be used to access resources in your cloud provider. You can configure your cloud provider to only respond to requests that originate from a specific organization's repository; you can also specify additional conditions, described below. +借助 OIDC，{% data variables.product.prodname_actions %} 工作流程需要令牌才能访问云提供商中的资源。 工作流程从云提供商请求访问令牌，以检查 JWT 提供的详细信息。 如果 JWT 中的信任配置匹配，则云提供商将通过向工作流程颁发临时令牌来做出响应，然后可以使用该令牌访问云提供商中的资源。 您可以将云提供商配置为仅响应来自特定组织的存储库的请求；您还可以指定其他条件，如下所述。 -Audience and Subject claims are typically used in combination while setting conditions on the cloud role/resources to scope its access to the GitHub workflows. -- **Audience**: By default, this value uses the URL of the organization or repository owner. This can be used to set a condition that only the workflows in the specific organization can access the cloud role. -- **Subject**: Has a predefined format and is a concatenation of some of the key metadata about the workflow, such as the {% data variables.product.prodname_dotcom %} organization, repository, branch, or associated [`job`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment) environment. See "[Example subject claims](#example-subject-claims)" to see how the subject claim is assembled from concatenated metadata. +在云角色/资源上设置条件以限定其对 GitHub 工作流程的访问范围时，受众和主题声明通常结合使用。 +- **受众**：默认情况下，此值使用组织或存储库所有者的 URL。 这可用于设置只有特定组织中的工作流程才能访问云角色的条件。 +- **主题**：具有预定义的格式，并且是有关工作流程的某些关键元数据的串联，如 {% data variables.product.prodname_dotcom %} 组织、存储库、分支或关联的[`作业`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idenvironment)环境。 请参阅“[示例主题声明](#example-subject-claims)”，了解如何从串联的元数据汇编主题声明。 -There are also many additional claims supported in the OIDC token that can also be used for setting these conditions. +OIDC 令牌中还支持许多其他声明，这些声明也可用于设置这些条件。 -In addition, your cloud provider could allow you to assign a role to the access tokens, letting you specify even more granular permissions. +此外，云提供商可以允许你为访问令牌分配角色，从而允许你指定更精细的权限。 {% note %} -**Note**: To control how your cloud provider issues access tokens, you **must** define at least one condition, so that untrusted repositories can’t request access tokens for your cloud resources. +**注意**：要控制云提供商颁发访问令牌的方式，**必须**至少定义一个条件，使不受信任的存储库无法为云资源请求访问令牌。 {% endnote %} -### Example subject claims +### 示例主题声明 -The following examples demonstrate how to use "Subject" as a condition, and explain how the "Subject" is assembled from concatenated metadata. The [subject](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims) uses information from the [`job` context](/actions/learn-github-actions/contexts#job-context), and instructs your cloud provider that access token requests may only be granted for requests from workflows running in specific branches, environments. The following sections describe some common subjects you can use. +以下示例演示如何使用“主题”作为条件，并说明如何从串联的元数据汇编“主题”。 [主题](https://openid.net/specs/openid-connect-core-1_0.html#StandardClaims)使用 [`作业`上下文](/actions/learn-github-actions/contexts#job-context)中的信息，并指示云提供商只能为来自特定分支、环境中运行的工作流程的请求授予访问令牌请求。 以下各节介绍了您可以使用的一些常见主题。 -#### Filtering for a specific environment +#### 筛选特定环境 -The subject claim includes the environment name when the job references an environment. +当作业引用环境时，主题声明包括环境名称。 -You can configure a subject that filters for a specific [environment](/actions/deployment/using-environments-for-deployment) name. In this example, the workflow run must have originated from a job that has an environment named `Production`, in a repository named `octo-repo` that is owned by the `octo-org` organization: +您可以配置针对特定[环境](/actions/deployment/using-environments-for-deployment)进行筛选的主题名称。 在此示例中，工作流程运行必须源自具有环境 `Production`、位于 `octo-org` 组织拥有的存储库 `octo-repo` 中的作业： | | | | --- | ------------------------------------------------------------------- | | 语法: | `repo::environment:` | | 示例： | `repo:octo-org/octo-repo:environment:Production` | -#### Filtering for `pull_request` events +#### 筛选 `pull_request` 事件 -The subject claim includes the `pull_request` string when the workflow is triggered by a pull request event, but only if the job doesn't reference an environment. +当工作流程由拉取请求事件触发时，主题声明包括 `pull_request` 字符串，但前提是作业未引用环境。 -You can configure a subject that filters for the [`pull_request`](/actions/learn-github-actions/events-that-trigger-workflows#pull_request) event. In this example, the workflow run must have been triggered by a `pull_request` event in a repository named `octo-repo` that is owned by the `octo-org` organization: +您可以配置筛选 [`pull_request`](/actions/learn-github-actions/events-that-trigger-workflows#pull_request) 事件的主题。 在此示例中，工作流程运行必须由 `octo-org` 组织拥有的存储库 `octo-repo` 中的 `pull_request` 事件触发： | | | | --- | -------------------------------------------- | | 语法: | `repo::pull_request` | | 示例： | `repo:octo-org/octo-repo:pull_request` | -#### Filtering for a specific branch +#### 筛选特定分支 -The subject claim includes the branch name of the workflow, but only if the job doesn't reference an environment, and if the workflow is not triggered by a pull request event. +主题声明包括工作流程的分支名称，但前提是作业未引用环境，并且工作流程不是由拉取请求事件触发的。 -You can configure a subject that filters for a specific branch name. In this example, the workflow run must have originated from a branch named `demo-branch`, in a repository named `octo-repo` that is owned by the `octo-org` organization: +您可以配置筛选特定分支名称的主题。 在此示例中，工作流程运行必须源自 `octo-org` 组织拥有的存储库 `octo-repo` 中的 `demo-branch` 分支： | | | | --- | --------------------------------------------------------- | | 语法: | `repo::ref:refs/heads/branchName` | | 示例： | `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` | -#### Filtering for a specific tag +#### 筛选特定标记 -The subject claim includes the tag name of the workflow, but only if the job doesn't reference an environment, and if the workflow is not triggered by a pull request event. +主题声明包括工作流程的标记名称，但前提是作业未引用环境，并且工作流程不是由拉取请求事件触发的。 -You can create a subject that filters for specific tag. In this example, the workflow run must have originated with a tag named `demo-tag`, in a repository named `octo-repo` that is owned by the `octo-org` organization: +您可以创建筛选特定标记的主题。 在此示例中，工作流程运行必须源自 `octo-org` 组织拥有的存储库 `octo-repo` 中的 `demo-tag` 标记： | | | | --- | ------------------------------------------------------------- | | 语法: | `repo::ref:refs/tags/` | | 示例： | `repo:octo-org/octo-repo:ref:refs/tags/demo-tag` | -### Configuring the subject in your cloud provider +### 在云提供商中配置主题 -To configure the subject in your cloud provider's trust relationship, you must add the subject string to its trust configuration. The following examples demonstrate how various cloud providers can accept the same `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` subject in different ways: +要在云提供商的信任关系中配置主题，必须将主题字符串添加到其信任配置中。 以下示例演示了各种云提供商如何以不同的方式接受相同的 `repo:octo-org/octo-repo:ref:refs/heads/demo-branch` 主题： | | | | ------------------- | ------------------------------------------------------------------------------------------------- | @@ -206,18 +206,18 @@ To configure the subject in your cloud provider's trust relationship, you must a | Google Cloud 平台 | `(assertion.sub=='repo:octo-org/octo-repo:ref:refs/heads/demo-branch')` | | HashiCorp Vault | `bound_subject="repo:octo-org/octo-repo:ref:refs/heads/demo-branch"` | -For more information, see the guides listed in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)." +更多信息请参阅“[为云提供商启用 OpenID Connect](#enabling-openid-connect-for-your-cloud-provider)”中列出的指南。 -## Updating your actions for OIDC +## 更新用于 OIDC 的操作 -To update your custom actions to authenticate using OIDC, you can use `getIDToken()` from the Actions toolkit to request a JWT from {% data variables.product.prodname_dotcom %}'s OIDC provider. For more information, see "OIDC Token" in the [npm package documentation](https://www.npmjs.com/package/@actions/core/v/1.6.0). +要更新您的自定义操作以使用 OIDC 进行身份验证，您可以使用 Actions 工具包中的 `getIDToken()` 从 {% data variables.product.prodname_dotcom %} 的 OIDC 提供商请求 JWT。 更多信息请参阅 [npm 包文档](https://www.npmjs.com/package/@actions/core/v/1.6.0)中的“OIDC 令牌”。 -You could also use a `curl` command to request the JWT, using the following environment variables: +您还可以使用 `curl` 命令来请求 JWT，方法是使用以下环境变量： -| | | -| -------------------------------- | ------------------------------------------------------------------------- | -| `ACTIONS_ID_TOKEN_REQUEST_URL` | The URL for {% data variables.product.prodname_dotcom %}'s OIDC provider. | -| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | Bearer token for the request to the OIDC provider. | +| | | +| -------------------------------- | ------------------------------------------------------------- | +| `ACTIONS_ID_TOKEN_REQUEST_URL` | {% data variables.product.prodname_dotcom %} 的 OIDC 提供商的 URL。 | +| `ACTIONS_ID_TOKEN_REQUEST_TOKEN` | 向 OIDC 提供商发出请求的持有者令牌。 | 例如： @@ -230,20 +230,20 @@ curl -H "Authorization: bearer $ACTIONS_ID_TOKEN_REQUEST_TOKEN" "$ACTIONS_ID_TOK {% data reusables.actions.oidc-permissions-token %} -## Updating your workflows for OIDC +## 更新 OIDC 的工作流程 -You can now update your YAML workflows to use OIDC access tokens instead of secrets. Popular cloud providers have published their official login actions that make it easy for you to get started with OIDC. For more information about updating your workflows, see the cloud-specific guides listed below in "[Enabling OpenID Connect for your cloud provider](#enabling-openid-connect-for-your-cloud-provider)." +现在，您可以更新 YAML 工作流程，以使用 OIDC 访问令牌而不是机密。 常用的云提供商已发布其官方登录操作，使您可以轻松开始使用 OIDC。 有关更新工作流程的详细信息，请参阅下面“[为云提供商启用 OpenID Connect ](#enabling-openid-connect-for-your-cloud-provider)”中列出的云特定指南。 -## Enabling OpenID Connect for your cloud provider +## 为云提供商启用 OpenID Connect -To enable and configure OIDC for your specific cloud provider, see the following guides: +要为您的特定云提供商启用和配置 OIDC，请参阅以下指南： -- ["Configuring OpenID Connect in Amazon Web Services"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services) -- ["Configuring OpenID Connect in Azure"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure) -- ["Configuring OpenID Connect in Google Cloud Platform"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform) -- ["Configuring OpenID Connect in Hashicorp Vault"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault) +- ["在 Amazon Web Services 中配置 OpenID Connect"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services) +- ["在 Azure 中配置 OpenID Connect"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure) +- ["在 Google Cloud Platform 中配置 OpenID Connect"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform) +- ["在 Hashicorp Vault 中配置 OpenID Connect"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault) -To enable and configure OIDC for another cloud provider, see the following guide: +要为其他云提供商启用和配置 OIDC，请参阅以下指南： -- ["Configuring OpenID Connect in cloud providers"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers) +- ["在云提供商中配置 OpenID Connect"](/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-cloud-providers) diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md index dc17f0ec52..8f9715ed11 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md @@ -1,7 +1,7 @@ --- -title: Configuring OpenID Connect in Amazon Web Services -shortTitle: Configuring OpenID Connect in Amazon Web Services -intro: Use OpenID Connect within your workflows to authenticate with Amazon Web Services. +title: 在 Amazon Web Services 中配置 OpenID Connect +shortTitle: 在 Amazon Web Services 中配置 OpenID Connect +intro: 在工作流程中使用 OpenID Connect 向 Amazon Web Services 进行身份验证。 miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -17,9 +17,9 @@ topics: ## 概览 -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Amazon Web Services (AWS), without needing to store the AWS credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. +OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} 工作流程访问 Amazon Web Services (AWS) 中的资源，而无需将任何 AWS 凭据存储为长期 {% data variables.product.prodname_dotcom %} 机密。 -This guide explains how to configure AWS to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) that uses tokens to authenticate to AWS and access resources. +本指南介绍如何配置 AWS 信任 {% data variables.product.prodname_dotcom %} 的 OIDC 作为联合标识，并包括使用令牌向 AWS 验证并访问资源的 [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) 工作流程示例。 ## 基本要求 @@ -27,18 +27,18 @@ This guide explains how to configure AWS to trust {% data variables.product.prod {% data reusables.actions.oidc-security-notice %} -## Adding the identity provider to AWS +## 将身份提供商添加到 AWS -To add the {% data variables.product.prodname_dotcom %} OIDC provider to IAM, see the [AWS documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html). +要将 {% data variables.product.prodname_dotcom %} OIDC 提供商添加到 IAM，请参阅 [AWS 文档](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html)。 -- For the provider URL: Use `https://token.actions.githubusercontent.com` -- For the "Audience": Use `sts.amazonaws.com` if you are using the [official action](https://github.com/aws-actions/configure-aws-credentials). +- 对于提供商 URL：使用 `https://token.actions.githubusercontent.com` +- 对于“受众”：如果您使用的是[官方操作](https://github.com/aws-actions/configure-aws-credentials)，请使用 `sts.amazonaws.com`。 -### Configuring the role and trust policy +### 配置角色和信任策略 -To configure the role and trust in IAM, see the AWS documentation for ["Assuming a Role"](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role) and ["Creating a role for web identity or OpenID connect federation"](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html). +要在 IAM 中配置角色和信任，请参阅 AWS 文档中的[“假定角色”](https://github.com/aws-actions/configure-aws-credentials#assuming-a-role)和[“为 Web 身份或 OpenID Connect Federation 创建角色”](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-idp_oidc.html)。 -Edit the trust relationship to add the `sub` field to the validation conditions. 例如： +编辑信任关系以将 `sub` 字段添加到验证条件。 例如： ```json{:copy} "Condition": { @@ -53,19 +53,19 @@ Edit the trust relationship to add the `sub` field to the validation conditions. 要更新 OIDC 的工作流程，您需要对 YAML 进行两项更改： 1. 为令牌添加权限设置。 -2. Use the [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) action to exchange the OIDC token (JWT) for a cloud access token. +2. 使用 [`aws-actions/configure-aws-credentials`](https://github.com/aws-actions/configure-aws-credentials) 操作将 OIDC 令牌 (JWT) 交换为云访问令牌。 ### 添加权限设置  {% data reusables.actions.oidc-permissions-token %} -### Requesting the access token +### 请求访问令牌 -The `aws-actions/configure-aws-credentials` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from AWS. For more information, see the AWS [documentation](https://github.com/aws-actions/configure-aws-credentials). +`aws-actions/configure-aws-credentials` 操作从 {% data variables.product.prodname_dotcom %} OIDC 提供商接收 JWT，然后从 AWS 请求访问令牌。 更多信息请参阅 AWS [文档](https://github.com/aws-actions/configure-aws-credentials)。 -- ``: Add the name of your S3 bucket here. -- ``: Replace the example with your AWS role. -- ``: Add the name of your AWS region here. +- ``：在此处添加 S3 存储桶的名称。 +- ``：将示例替换为您的 AWS 角色。 +- ``：在此处添加您的 AWS 区域的名称。 ```yaml{:copy} # Sample workflow to access AWS resources when workflow is tied to branch diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md index 7bef1cd354..0d0f10e75d 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure.md @@ -1,7 +1,7 @@ --- -title: Configuring OpenID Connect in Azure -shortTitle: Configuring OpenID Connect in Azure -intro: Use OpenID Connect within your workflows to authenticate with Azure. +title: 在 Azure 中配置 OpenID Connect +shortTitle: 在 Azure 中配置 OpenID Connect +intro: 在工作流程中使用 OpenID Connect 向 Azure 进行身份验证。 miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -17,9 +17,9 @@ topics: ## 概览 -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Azure, without needing to store the Azure credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. +OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} 工作流程访问 Azure 中的资源，而无需将任何 Azure 凭据存储为长期 {% data variables.product.prodname_dotcom %} 机密。 -This guide gives an overview of how to configure Azure to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`azure/login`](https://github.com/Azure/login) action that uses tokens to authenticate to Azure and access resources. +本指南概述了如何配置 Azure 信任 {% data variables.product.prodname_dotcom %} 的 OIDC 作为联合标识，并包括 [`azure/login`](https://github.com/Azure/login) 操作的工作流程示例，该操作使用令牌向 Azure 进行身份验证和访问资源。 ## 基本要求 @@ -27,36 +27,36 @@ This guide gives an overview of how to configure Azure to trust {% data variable {% data reusables.actions.oidc-security-notice %} -## Adding the Federated Credentials to Azure +## 将联合凭据添加到 Azure -{% data variables.product.prodname_dotcom %}'s OIDC provider works with Azure's workload identity federation. For an overview, see Microsoft's documentation at "[Workload identity federation](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)." +{% data variables.product.prodname_dotcom %} 的 OIDC 提供商与 Azure 的工作负载联合身份验证配合使用。 有关概述，请参阅 Microsoft 的文档“[工作负载联合身份验证](https://docs.microsoft.com/en-us/azure/active-directory/develop/workload-identity-federation)”。 -To configure the OIDC identity provider in Azure, you will need to perform the following configuration. For instructions on making these changes, refer to [the Azure documentation](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure). +要在 Azure 中配置 OIDC 身份提供商，您需要执行以下配置。 有关进行这些更改的说明，请参阅 [Azure 文档](https://docs.microsoft.com/en-us/azure/developer/github/connect-from-azure)。 -1. Create an Azure Active Directory application and a service principal. -2. Add federated credentials for the Azure Active Directory application. -3. Create {% data variables.product.prodname_dotcom %} secrets for storing Azure configuration. +1. 创建 Azure Active Directory 应用程序和服务主体。 +2. 为 Azure Active Directory 应用程序添加联合凭据。 +3. 创建用于存储 Azure 配置的 {% data variables.product.prodname_dotcom %} 机密。 -Additional guidance for configuring the identity provider: +配置身份提供商的附加指导： -- For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). -- For the `audience` setting, `api://AzureADTokenExchange` is the recommended value, but you can also specify other values here. +- 为强化安全，请确保您已查看[“使用云配置 OIDC 信任”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)。 有关示例，请参阅[“在云提供商中配置主题”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider)。 +- 对于`受众`设置，建议的值为 `api://AzureADTokenExchange`，但您也可以在此处指定其他值。 ## 更新 {% data variables.product.prodname_actions %} 工作流程 要更新 OIDC 的工作流程，您需要对 YAML 进行两项更改： 1. 为令牌添加权限设置。 -2. Use the [`azure/login`](https://github.com/Azure/login) action to exchange the OIDC token (JWT) for a cloud access token. +2. 使用 [`azure/login`](https://github.com/Azure/login) 操作将 OIDC 令牌 (JWT) 交换为云访问令牌。 ### 添加权限设置  {% data reusables.actions.oidc-permissions-token %} -### Requesting the access token +### 请求访问令牌 -The [`azure/login`](https://github.com/Azure/login) action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from Azure. For more information, see the [`azure/login`](https://github.com/Azure/login) documentation. +[`azure/login`](https://github.com/Azure/login) 操作从 {% data variables.product.prodname_dotcom %} OIDC 提供商接收 JWT，然后从 Azure 请求访问令牌。 更多信息请参阅 [`azure/login`](https://github.com/Azure/login) 文档。 -The following example exchanges an OIDC ID token with Azure to receive an access token, which can then be used to access cloud resources. +以下示例将 OIDC ID 令牌与 Azure 交换以接收访问令牌，然后可以使用该令牌访问云资源。 {% raw %} ```yaml{:copy} diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md index c5319bd950..b36b348e7e 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-google-cloud-platform.md @@ -1,7 +1,7 @@ --- -title: Configuring OpenID Connect in Google Cloud Platform -shortTitle: Configuring OpenID Connect in Google Cloud Platform -intro: Use OpenID Connect within your workflows to authenticate with Google Cloud Platform. +title: 在 Google Cloud Platform 中配置 OpenID Connect +shortTitle: 在 Google Cloud Platform 中配置 OpenID Connect +intro: 在工作流程中使用 OpenID Connect 向 Google Cloud 平台进行身份验证。 miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -17,9 +17,9 @@ topics: ## 概览 -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to access resources in Google Cloud Platform (GCP), without needing to store the GCP credentials as long-lived {% data variables.product.prodname_dotcom %} secrets. +OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} 工作流程访问 Google Cloud 平台中的资源，而无需将任何 GCP 凭据存储为长期 {% data variables.product.prodname_dotcom %} 机密。 -This guide gives an overview of how to configure GCP to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and includes a workflow example for the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action that uses tokens to authenticate to GCP and access resources. +本指南概述了如何配置 GCP 信任 {% data variables.product.prodname_dotcom %} 的 OIDC 作为联合标识，并包括 [`google-github-actions/auth`](https://github.com/google-github-actions/auth) 操作的工作流程示例，该操作使用令牌向 GCP 进行身份验证和访问资源。 ## 基本要求 @@ -27,41 +27,41 @@ This guide gives an overview of how to configure GCP to trust {% data variables. {% data reusables.actions.oidc-security-notice %} -## Adding a Google Cloud Workload Identity Provider +## 添加 Google Cloud 工作负载身份提供商 -To configure the OIDC identity provider in GCP, you will need to perform the following configuration. For instructions on making these changes, refer to [the GCP documentation](https://github.com/google-github-actions/auth). +要在 GCP 中配置 OIDC 身份提供商，您需要执行以下配置。 有关进行这些更改的说明，请参阅 [GCP 文档](https://github.com/google-github-actions/auth)。 -1. Create a new identity pool. -2. Configure the mapping and add conditions. -3. Connect the new pool to a service account. +1. 创建新的身份池。 +2. 配置映射并添加条件。 +3. 将新池连接到服务帐户。 -Additional guidance for configuring the identity provider: +配置身份提供商的附加指导： -- For security hardening, make sure you've reviewed ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud). For an example, see ["Configuring the subject in your cloud provider"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider). -- For the service account to be available for configuration, it needs to be assigned to the `roles/iam.workloadIdentityUser` role. For more information, see [the GCP documentation](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions). -- The Issuer URL to use: `https://token.actions.githubusercontent.com` +- 为强化安全，请确保您已查看[“使用云配置 OIDC 信任”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)。 有关示例，请参阅[“在云提供商中配置主题”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-subject-in-your-cloud-provider)。 +- 要使服务帐户可用于配置，需要将其分配给 `roles/iam.workloadIdentityUser` 角色。 更多信息请参阅 [GCP 文档](https://cloud.google.com/iam/docs/workload-identity-federation?_ga=2.114275588.-285296507.1634918453#conditions)。 +- 要使用的颁发者 URL：`https://token.actions.githubusercontent.com` ## 更新 {% data variables.product.prodname_actions %} 工作流程 要更新 OIDC 的工作流程，您需要对 YAML 进行两项更改： 1. 为令牌添加权限设置。 -2. Use the [`google-github-actions/auth`](https://github.com/google-github-actions/auth) action to exchange the OIDC token (JWT) for a cloud access token. +2. 使用 [`google-github-actions/auth`](https://github.com/google-github-actions/auth) 操作将 OIDC 令牌 (JWT) 交换为云访问令牌。 ### 添加权限设置  {% data reusables.actions.oidc-permissions-token %} -### Requesting the access token +### 请求访问令牌 -The `google-github-actions/auth` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from GCP. For more information, see the GCP [documentation](https://github.com/google-github-actions/auth). +`google-github-actions/auth` 操作从 {% data variables.product.prodname_dotcom %} OIDC 提供商接收 JWT，然后从 GCP 请求访问令牌。 更多信息请参阅 GCP [文档](https://github.com/google-github-actions/auth)。 -This example has a job called `Get_OIDC_ID_token` that uses actions to request a list of services from GCP. +此示例有一个名为 `Get_OIDC_ID_token` 的作业，该作业使用操作从 GCP 请求服务列表。 -- ``: Replace this with the path to your identity provider in GCP. For example, `projects//locations/global/workloadIdentityPools/` -- ``: Replace this with the name of your service account in GCP. -- ``: Replace this with the ID of your GCP project. +- ``：将此值替换为指向 GCP 中身份提供商的路径。 例如 `projects//locations/global/workloadIdentityPools/` +- ``：将此值替换为您在 GCP 中的服务帐户的名称。 +- ``：将此值替换为 GCP 项目的 ID。 -This action exchanges a {% data variables.product.prodname_dotcom %} OIDC token for a Google Cloud access token, using [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation). +此操作使用[工作负载联合身份验证](https://cloud.google.com/iam/docs/workload-identity-federation)将 {% data variables.product.prodname_dotcom %} OIDC 令牌交换为 Google Cloud 访问令牌。 {% raw %} ```yaml{:copy} diff --git a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md index 284fb6eaa4..ce7e5e6f93 100644 --- a/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md +++ b/translations/zh-CN/content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-hashicorp-vault.md @@ -1,7 +1,7 @@ --- -title: Configuring OpenID Connect in HashiCorp Vault -shortTitle: Configuring OpenID Connect in HashiCorp Vault -intro: Use OpenID Connect within your workflows to authenticate with HashiCorp Vault. +title: 在 HashiCorp Vault 中配置 OpenID Connect +shortTitle: 在 HashiCorp Vault 中配置 OpenID Connect +intro: 在工作流程中使用 OpenID Connect 通过 HashiCorp Vault 进行身份验证。 miniTocMaxHeadingLevel: 3 versions: fpt: '*' @@ -17,9 +17,9 @@ topics: ## 概览 -OpenID Connect (OIDC) allows your {% data variables.product.prodname_actions %} workflows to authenticate with a HashiCorp Vault to retrieve secrets. +OpenID Connect (OIDC) 允许您的 {% data variables.product.prodname_actions %} 工作流程使用 HashiCorp Vault 进行身份验证以检索机密。 -This guide gives an overview of how to configure HashiCorp Vault to trust {% data variables.product.prodname_dotcom %}'s OIDC as a federated identity, and demonstrates how to use this configuration in the [hashicorp/vault-action](https://github.com/hashicorp/vault-action) action to retrieve secrets from HashiCorp Vault. +本指南概述如何配置 HashiCorp Vault 信任 {% data variables.product.prodname_dotcom %} 的 OIDC 作为联合身份，并演示如何在 [hashicorp/vault-action](https://github.com/hashicorp/vault-action) 操作中使用此配置从 HashiCorp Vault 检索机密。 ## 基本要求 @@ -27,45 +27,45 @@ This guide gives an overview of how to configure HashiCorp Vault to trust {% dat {% data reusables.actions.oidc-security-notice %} -## Adding the identity provider to HashiCorp Vault +## 将身份提供商添加到 HashiCorp Vault -To use OIDC with HashiCorp Vault, you will need to add a trust configuration for the {% data variables.product.prodname_dotcom %} OIDC provider. For more information, see the HashiCorp Vault [documentation](https://www.vaultproject.io/docs/auth/jwt). +要将 OIDC 与 HashiCorp Vault 配合使用，您需要为 {% data variables.product.prodname_dotcom %} OIDC 提供商添加信任配置。 更多信息请参阅 HashiCorp Vault [文档](https://www.vaultproject.io/docs/auth/jwt)。 -Configure the vault to accept JSON Web Tokens (JWT) for authentication: -- For the `oidc_discovery_url`, use `https://token.actions.githubusercontent.com` -- For `bound_issuer`, use `https://token.actions.githubusercontent.com` -- Ensure that `bound_subject` is correctly defined for your security requirements. For more information, see ["Configuring the OIDC trust with the cloud"](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud) and [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action). +配置 Vault 接受 JSON Web 令牌 (JWT) 进行身份验证： +- 对于 `oidc_discovery_url`，请使用 `https://token.actions.githubusercontent.com` +- 对于 `bound_issuer`，请使用 `https://token.actions.githubusercontent.com` +- 确保针对您的安全要求正确定义了 `bound_subject`。 更多信息请参阅[“使用云配置 OIDC 信任”](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#configuring-the-oidc-trust-with-the-cloud)和 [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action)。 ## 更新 {% data variables.product.prodname_actions %} 工作流程 要更新 OIDC 的工作流程，您需要对 YAML 进行两项更改： 1. 为令牌添加权限设置。 -2. Use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to exchange the OIDC token (JWT) for a cloud access token. +2. 使用 [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) 操作将 OIDC 令牌 (JWT) 交换为云访问令牌。 -To add OIDC integration to your workflows that allow them to access secrets in Vault, you will need to add the following code changes: +要将 OIDC 集成添加到您的工作流程中，以允许他们访问 Vault 中的密钥，您需要添加以下代码更改： - Grant permission to fetch the token from the {% data variables.product.prodname_dotcom %} OIDC provider: - - The workflow needs `permissions:` settings with the `id-token` value set to `write`. This lets you fetch the OIDC token from every job in the workflow. -- Request the JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and present it to HashiCorp Vault to receive an access token: - - You could use the [Actions toolkit](https://github.com/actions/toolkit/) to fetch the tokens for your job, or you can use the [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) action to fetch the JWT and receive the access token from the Vault. + - 工作流需要 `permissions:` 设置将 `id-token` 值设为 `write`。 This lets you fetch the OIDC token from every job in the workflow. +- 向 {% data variables.product.prodname_dotcom %} OIDC 提供商请求 JWT，并将其提供给 HashiCorp Vault 以接收访问令牌： + - 您可以使用[操作工具包](https://github.com/actions/toolkit/)来获取作业的令牌，也可以使用 [`hashicorp/vault-action`](https://github.com/hashicorp/vault-action) 操作来获取 JWT 并从 Vault 接收访问令牌。 -This example demonstrates how to use OIDC with the official action to request a secret from HashiCorp Vault. +此示例演示如何将 OIDC 与官方操作结合使用，以向 HashiCorp Vault 请求机密。 ### 添加权限设置  {% data reusables.actions.oidc-permissions-token %} -### Requesting the access token +### 请求访问令牌 -The `hashicorp/vault-action` action receives a JWT from the {% data variables.product.prodname_dotcom %} OIDC provider, and then requests an access token from your HashiCorp Vault instance to retrieve secrets. For more information, see the HashiCorp Vault [documentation](https://github.com/hashicorp/vault-action). +`hashicorp/vault-action` 操作从 {% data variables.product.prodname_dotcom %} OIDC 提供商接收 JWT，然后从 HashiCorp Vault 实例请求访问令牌以检索机密。 更多信息请参阅 HashiCorp Vault [文档](https://github.com/hashicorp/vault-action)。 -This example demonstrates how to create a job that requests a secret from HashiCorp Vault. +此示例演示如何创建从 HashiCorp Vault请求机密的作业。 -- ``: Replace this with the URL of your HashiCorp Vault. -- ``: Replace this with the role you've set in the HashiCorp Vault trust relationship. -- ``: Replace this with the audience you've defined in the HashiCorp Vault trust relationship. -- ``: Replace this with the path to the secret you're retrieving from HashiCorp Vault. For example: `secret/data/ci npmToken`. +- ``：将此值替换为您的 HashiCorp Vault 的URL。 +- ``：将此值替换为您在 HashiCorp Vault 信任关系中设置的角色。 +- ``：将此值替换为您在 HashiCorp Vault 信任关系中定义的受众。 +- ``：将此值替换为您从 HashiCorp Vault 检索的机密的路径。 例如：`secret/data/ci npmToken`。 ```yaml{:copy} jobs: diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/index.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/index.md index 2cf3b18a76..48d573190c 100644 --- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/index.md +++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/index.md @@ -1,6 +1,6 @@ --- -title: Targeting different environments -shortTitle: Targeting different environments +title: 针对不同的环境 +shortTitle: 针对不同的环境 intro: 您可以使用保护规则和机密配置环境。 引用环境的工作流程作业在运行或访问环境的机密之前，必须遵循环境的任何保护规则。 versions: fpt: '*' diff --git a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md index 84805257d2..b836c1139b 100644 --- a/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md +++ b/translations/zh-CN/content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md @@ -86,20 +86,20 @@ Environments are used to describe a general deployment target like `production`, 1. 单击 **Save protection rules（保存保护规则）**。 3. （可选）指定哪些分支可以部署到此环境。 有关可能值的详细信息，请参阅“[部署分支](#deployment-branches)”。 1. 在 **Deployment branches（部署分支）**下拉列表中选择所需的选项。 - 1. If you chose **Selected branches**, enter the branch name patterns that you want to allow. -4. Optionally, add environment secrets. These secrets are only available to workflow jobs that use the environment. Additionally, workflow jobs that use this environment can only access these secrets after any configured rules (for example, required reviewers) pass. 有关机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。 - 1. Under **Environment secrets**, click **Add Secret**. - 1. Enter the secret name. - 1. Enter the secret value. + 1. 如果选择 **Selected branches（选定分支）**，请输入要允许的分支名称模式。 +4. （可选）添加环境机密。 这些机密仅可用于使用环境的工作流程作业。 此外，使用此环境的工作流程作业只能在任何配置的规则（例如，必需的审查者）通过后才能访问这些机密。 有关机密的更多信息，请参阅“[加密密码](/actions/reference/encrypted-secrets)”。 + 1. 在 **Environment secrets（环境机密）**下，单击 **Add Secret（添加机密）**。 + 1. 输入机密名称。 + 1. 输入机密值。 1. 单击 **Add secret（添加密码）**。 {% ifversion fpt or ghae or ghes > 3.1 or ghec %}您也可以通过 REST API 创建和配置环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”和“[密码](/rest/reference/actions#secrets)”。{% endif %} 运行引用不存在的环境的工作流程将使用引用的名称创建环境。 新创建的环境将不配置任何保护规则或机密。 可在仓库中编辑工作流程的任何人都可以通过工作流程文件创建环境，但只有仓库管理员才能配置环境。 -## Using an environment +## 使用环境 -工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 The job can access the environment's secrets only after the job is sent to a runner. +工作流程中的每个作业都可以引用单个环境。 在将引用环境的作业发送到运行器之前，必须通过为环境配置的任何保护规则。 只有在将作业发送给运行器后，作业才能访问环境的机密。 当工作流程引用环境时，环境将显示在仓库的部署中。 有关查看当前和以前的部署的详细信息，请参阅“[查看部署历史记录](/developers/overview/viewing-deployment-history)”。 @@ -119,12 +119,12 @@ Environments are used to describe a general deployment target like `production`, {% ifversion fpt or ghae or ghes > 3.1 or ghec %}您也可以通过 REST API 删除环境。 更多信息请参阅“[环境](/rest/reference/repos#environments)”。{% endif %} -## How environments relate to deployments +## 环境与部署的关系 {% data reusables.actions.environment-deployment-event %} -You can access these objects through the REST API or GraphQL API. You can also subscribe to these webhook events. For more information, see "[Repositories](/rest/reference/repos#deployments)" (REST API), "[Objects]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)" (GraphQL API), or "[Webhook events and payloads](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)." +您可以通过 REST API 或 GraphQL API 访问这些对象。 您还可以订阅这些 web 挂钩事件。 更多信息请参阅“[存储库](/rest/reference/repos#deployments)”（REST API）、“[对象]({% ifversion ghec %}/free-pro-team@latest{% endif %}/graphql/reference/objects#deployment)”（GraphQL API）或“[web 挂钩事件和有效负载](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#deployment)”。 ## 后续步骤 -{% data variables.product.prodname_actions %} provides several features for managing your deployments. For more information, see "[Deploying with GitHub Actions](/actions/deployment/deploying-with-github-actions)." +{% data variables.product.prodname_actions %} 具有多个用于管理部署的功能。 更多信息请参阅“[使用 GitHub Actions 进行部署](/actions/deployment/deploying-with-github-actions)”。 diff --git a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md index 573e25e030..f0e38daacf 100644 --- a/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/zh-CN/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -2,6 +2,7 @@ title: GitHub Actions 的工作流程命令 shortTitle: 工作流程命令 intro: 您可以在工作流程或操作代码中运行 shell 命令时使用工作流程命令。 +defaultTool: bash redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -26,10 +27,24 @@ versions: 大多数工作流程命令使用特定格式的 `echo` 命令，而其他工作流程则通过写入文件被调用。 更多信息请参阅“[环境文件](#environment-files)”。 -``` bash +### 示例 + +{% bash %} + +```bash{:copy} echo "::workflow-command parameter1={data},parameter2={data}::{command value}" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}" +``` + +{% endpowershell %} + {% note %} **注意：**工作流程命令和参数名称不区分大小写。 @@ -46,14 +61,18 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}" [actions/toolkit](https://github.com/actions/toolkit) 包括一些可以作为工作流程命令执行的功能。 使用 `::` 语法来运行您的 YAML 文件中的工作流程命令；然后，通过 `stdout` 将这些命令发送给运行器。 例如，不使用代码来设置环境变量，如下所示： -```javascript +```javascript{:copy} core.setOutput('SELECTED_COLOR', 'green'); ``` +### Example: Setting a value + 您可以在工作流程中使用 `set-output` 命令来设置相同的值： +{% bash %} + {% raw %} -``` yaml +```yaml{:copy} - name: Set selected color run: echo '::set-output name=SELECTED_COLOR::green' id: random-color-generator @@ -62,6 +81,22 @@ core.setOutput('SELECTED_COLOR', 'green'); ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} + - name: Set selected color + run: Write-Output "::set-output name=SELECTED_COLOR::green" + id: random-color-generator + - name: Get color + run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}" +``` +{% endraw %} + +{% endpowershell %} + 下表显示了在工作流程中可用的工具包功能： | 工具包函数 | 等效工作流程命令 | @@ -86,186 +121,336 @@ core.setOutput('SELECTED_COLOR', 'green'); ## 设置输出参数 -``` +设置操作的输出参数。 + +```{:copy} ::set-output name={name}::{value} ``` -设置操作的输出参数。 - （可选）您也可以在操作的元数据文件中声明输出参数。 更多信息请参阅“[{% data variables.product.prodname_actions %} 的元数据语法](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)”。 -### 示例 +### Example: Setting an output parameter -``` bash +{% bash %} + +```bash{:copy} echo "::set-output name=action_fruit::strawberry" ``` -## 设置调试消息 +{% endbash %} +{% powershell %} + +```pwsh{:copy} +Write-Output "::set-output name=action_fruit::strawberry" ``` -::debug::{message} -``` + +{% endpowershell %} + +## 设置调试消息 将调试消息打印到日志。 您可以创建名为 `ACTIONS_STEP_DEBUG`、值为 `true` 的密码，才能在日志中查看通过此命令设置的调试消息。 更多信息请参阅“[启用调试日志记录](/actions/managing-workflow-runs/enabling-debug-logging)”。 -### 示例 +```{:copy} +::debug::{message} +``` -``` bash +### Example: Setting a debug message + +{% bash %} + +```bash{:copy} echo "::debug::Set the Octocat variable" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::debug::Set the Octocat variable" +``` + +{% endpowershell %} + {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} ## 设置通知消息 -``` +创建通知消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -创建通知消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### 示例 +### Example: Setting a notice message -``` bash +{% bash %} + +```bash{:copy} echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} {% endif %} ## 设置警告消息 -``` +创建警告消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -创建警告消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### 示例 +### Example: Setting a warning message -``` bash +{% bash %} + +```bash{:copy} echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## 设置错误消息 -``` +创建错误消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -创建错误消息并将该消息打印到日志。 {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### 示例 +### Example: Setting an error message -``` bash +{% bash %} + +```bash{:copy} echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## 对日志行分组 -``` +在日志中创建一个可扩展的组。 要创建组，请使用 `group` 命令并指定 `title`。 打印到 `group` 与 `endgroup` 命令之间日志的任何内容都会嵌套在日志中可扩展的条目内。 + +```{:copy} ::group::{title} ::endgroup:: ``` -在日志中创建一个可扩展的组。 要创建组，请使用 `group` 命令并指定 `title`。 打印到 `group` 与 `endgroup` 命令之间日志的任何内容都会嵌套在日志中可扩展的条目内。 +### Example: Grouping log lines -### 示例 +{% bash %} -```bash -echo "::group::My title" -echo "Inside group" -echo "::endgroup::" +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + steps: + - name: Group of log lines + run: | + echo "::group::My title" + echo "Inside group" + echo "::endgroup::" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + steps: + - name: Group of log lines + run: | + Write-Output "::group::My title" + Write-Output "Inside group" + Write-Output "::endgroup::" +``` + +{% endpowershell %} + ![工作流运行日志中的可折叠组](/assets/images/actions-log-group.png) ## 在日志中屏蔽值 -``` +```{:copy} ::add-mask::{value} ``` 屏蔽值可阻止在日志中打印字符串或变量。 用空格分隔的每个屏蔽的词均替换为 `*` 字符。 您可以使用环境变量或字符串作为屏蔽的 `value`。 -### 屏蔽字符串的示例 +### Example: Masking a string 当您在日志中打印 `"Mona The Octocat"` 时，您将看到 `"***"`。 -```bash +{% bash %} + +```bash{:copy} echo "::add-mask::Mona The Octocat" ``` -### 屏蔽环境变量的示例 +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::add-mask::Mona The Octocat" +``` + +{% endpowershell %} + +### Example: Masking an environment variable 当您在日志中打印变量 `MY_NAME` 或值 `"Mona The Octocat"` 时，您将看到 `"***"` 而不是 `"Mona The Octocat"`。 -```bash -MY_NAME="Mona The Octocat" -echo "::add-mask::$MY_NAME" +{% bash %} + +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: bash-version + run: echo "::add-mask::$MY_NAME" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: powershell-version + run: Write-Output "::add-mask::$env:MY_NAME" +``` + +{% endpowershell %} + ## 停止和启动工作流程命令 -`::stop-commands::{endtoken}` - 停止处理任何工作流程命令。 此特殊命令可让您记录任何内容而不会意外运行工作流程命令。 例如，您可以停止记录以输出带有注释的整个脚本。 +```{:copy} +::stop-commands::{endtoken} +``` + 要停止处理工作流程命令，请将唯一的令牌传递给 `stop-commands`。 要继续处理工作流程命令，请传递用于停止工作流程命令的同一令牌。 {% warning %} -**警告：** 请确保您使用的令牌是随机生成的，且对每次运行唯一。 如下面的示例所示，您可以为每次运行生成 `github.token` 的唯一哈希值。 +**警告：** 请确保您使用的令牌是随机生成的，且对每次运行唯一。 {% endwarning %} -``` +```{:copy} ::{endtoken}:: ``` -### 停止和启动工作流程命令的示例 +### Example: Stopping and starting workflow commands + +{% bash %} {% raw %} -```yaml +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest steps: - - name: disable workflow commands + - name: Disable workflow commands run: | - echo '::warning:: this is a warning' - echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`" - echo '::warning:: this will NOT be a warning' - echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::" - echo '::warning:: this is a warning again' + echo '::warning:: This is a warning message, to demonstrate that commands are being processed.' + stopMarker=$(uuidgen) + echo "::stop-commands::$stopMarker" + echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + echo "::$stopMarker::" + echo '::warning:: This is a warning again, because stop-commands has been turned off.' +``` +{% endraw %} + +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: Disable workflow commands + run: | + Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.' + $stopMarker = New-Guid + Write-Output "::stop-commands::$stopMarker" + Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + Write-Output "::$stopMarker::" + Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.' ``` {% endraw %} +{% endpowershell %} + ## Echoing command outputs -``` +Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. + +```{:copy} ::echo::on ::echo::off ``` -Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. - Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command. The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log. You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository. -### Example toggling command echoing +### Example: Toggling command echoing -```yaml +{% bash %} + +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest @@ -279,9 +464,29 @@ jobs: echo '::set-output name=action_echo::disabled' ``` -The step above prints the following lines to the log: +{% endbash %} +{% powershell %} + +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: toggle workflow command echoing + run: | + write-output "::set-output name=action_echo::disabled" + write-output "::echo::on" + write-output "::set-output name=action_echo::enabled" + write-output "::echo::off" + write-output "::set-output name=action_echo::disabled" ``` + +{% endpowershell %} + +The example above prints the following lines to the log: + +```{:copy} ::set-output name=action_echo::enabled ::echo::off ``` @@ -298,13 +503,13 @@ Only the second `set-output` and `echo` workflow commands are included in the lo 此示例使用 JavaScript 运行 `save-state` 命令。 由此生成的环境变量被命名为 `STATE_processID`，带 `12345` 的值： -``` javascript +```javascript{:copy} console.log('::save-state name=processID::12345') ``` 然后，`STATE_processID` 变量将仅可被用于 `main` 操作下运行的清理脚本。 此示例在 `main` 中运行，并使用 JavaScript 显示分配给 `STATE_processID` 环境变量的值： -``` javascript +```javascript{:copy} console.log("The running PID from the main action is: " + process.env.STATE_processID); ``` @@ -312,37 +517,70 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro 在工作流程执行期间，运行器生成可用于执行某些操作的临时文件。 这些文件的路径通过环境变量显示。 写入这些文件时，您需要使用 UTF-8 编码，以确保正确处理命令。 多个命令可以写入同一个文件，用换行符分隔。 -{% warning %} +{% powershell %} -**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. +{% note %} -When using `shell: powershell`, you must specify UTF-8 encoding. 例如： +**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. 例如： -```yaml +```yaml{:copy} jobs: legacy-powershell-example: - uses: windows-2019 + runs-on: windows-latest steps: - shell: powershell - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append + run: | + "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. +PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. 例如： -{% endwarning %} +```yaml{:copy} +jobs: + powershell-core-example: + runs-on: windows-latest + steps: + - shell: pwsh + run: | + "mypath" >> $env:GITHUB_PATH +``` + +{% endnote %} + +{% endpowershell %} ## 设置环境变量 -``` bash +{% bash %} + +```bash{:copy} echo "{environment_variable_name}={value}" >> $GITHUB_ENV ``` +{% endbash %} + +{% powershell %} + +- Using PowerShell version 6 and higher: +```pwsh{:copy} +"{environment_variable_name}={value}" >> $env:GITHUB_ENV +``` + +- Using PowerShell version 5.1 and below: +```powershell{:copy} +"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append +``` + +{% endpowershell %} + You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. 创建或更新环境变量的步骤无法访问新值，但在作业中的所有后续步骤均可访问。 The names of environment variables are case-sensitive, and you can include punctuation. 更多信息请参阅“[环境变量](/actions/learn-github-actions/environment-variables)”。 ### 示例 +{% bash %} + {% raw %} -``` +```yaml{:copy} steps: - name: Set the value id: step_one @@ -355,11 +593,31 @@ steps: ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +steps: + - name: Set the value + id: step_one + run: | + "action_state=yellow" >> $env:GITHUB_ENV + - name: Use the value + id: step_two + run: | + Write-Output "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} + +{% endpowershell %} + ### 多行字符串 对于多行字符串，您可以使用具有以下语法的分隔符。 -``` +```{:copy} {name}<<{delimiter} {value} {delimiter} @@ -367,29 +625,75 @@ steps: #### 示例 -在此示例中， 我们使用 `EOF` 作为分隔符，并将 `JSON_RESPONSE` 环境变量设置为 cURL 响应的值。 -```yaml +This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response. + +{% bash %} + +```yaml{:copy} steps: - - name: Set the value + - name: Set the value in bash id: step_one run: | echo 'JSON_RESPONSE<> $GITHUB_ENV - curl https://httpbin.org/json >> $GITHUB_ENV + curl https://example.lab >> $GITHUB_ENV echo 'EOF' >> $GITHUB_ENV ``` -## 添加系统路径 +{% endbash %} -``` bash -echo "{path}" >> $GITHUB_PATH +{% powershell %} + +```yaml{:copy} +steps: + - name: Set the value in pwsh + id: step_one + run: | + "JSON_RESPONSE<> $env:GITHUB_ENV + (Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV + "EOF" >> $env:GITHUB_ENV + shell: pwsh ``` +{% endpowershell %} + +## 添加系统路径 + Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. 要查看作业的当前定义路径，您可以在步骤或操作中使用 `echo "$PATH"`。 +{% bash %} + +```bash{:copy} +echo "{path}" >> $GITHUB_PATH +``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +"{path}" >> $env:GITHUB_PATH +``` + +{% endpowershell %} + ### 示例 此示例演示如何将用户 `$HOME/.local/bin` 目录添加到 `PATH`： -``` bash +{% bash %} + +```bash{:copy} echo "$HOME/.local/bin" >> $GITHUB_PATH ``` + +{% endbash %} + + +This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`: + +{% powershell %} + +```pwsh{:copy} +"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH +``` + +{% endpowershell %} diff --git a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index b656a9eda2..a20bc90c54 100644 --- a/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/zh-CN/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -17,7 +17,11 @@ topics: 如果配置的是主机名，而不是硬编码 IP 地址，您将能够更改运行 {% data variables.product.product_location %} 的物理硬件，而不会影响用户或客户端软件。 -{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN)，此域名可在互联网上或您的内部网络内解析。 例如，您的主机名设置可以是 `github.companyname.com`。我们还建议为选定的主机名启用子域隔离，以缓解多种跨站点脚本样式漏洞。 更多关于主机名设置的信息，请参阅 [HTTP RFC 的第 2.1 节](https://tools.ietf.org/html/rfc1123#section-2)。 +{% data variables.enterprise.management_console %} 中的主机名设置应设置为合适的完全限定域名 (FQDN)，此域名可在互联网上或您的内部网络内解析。 For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. + +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。 + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} @@ -29,4 +33,4 @@ topics: {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -配置完主机名后，建议为 {% data variables.product.product_location %} 启用子域隔离。 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。 +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. 更多信息请参阅“[启用子域隔离](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)”。 diff --git a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index 43a90b0edc..22657f5de3 100644 --- a/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/zh-CN/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -19,25 +19,32 @@ shortTitle: 启动故障转移到设备 {% data reusables.enterprise_installation.promoting-a-replica %} -1. 要允许复制在切换设备之前完成，请将主设备置于维护模式： - - 要使用 Management Console，请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。 - - 您也可以使用 `ghe-maintenance -s` 命令。 +1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode. + + - Put the appliance into maintenance mode. + + - 要使用 Management Console，请参阅“[启用和排定维护模式](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)”。 + + - 您也可以使用 `ghe-maintenance -s` 命令。 + ```shell + $ ghe-maintenance -s + ``` + + - 当活动 Git 操作、MySQL 查询和 Resque 作业数量达到零时，等待 30 秒。 + + {% note %} + + **注意：** Nomad 将始终有作业在运行，即使是在维护模式下，因此您可以安全地忽略这些作业。 + + {% endnote %} + + - 要验证所有复制通道均报告 `OK`，请使用 `ghe-repl-status -vv` 命令。 + ```shell - $ ghe-maintenance -s + $ ghe-repl-status -vv ``` -2. 当活动 Git 操作、MySQL 查询和 Resque 作业数量达到零时，等待 30 秒。 - {% note %} - - **注意：** Nomad 将始终有作业在运行，即使是在维护模式下，因此您可以安全地忽略这些作业。 - - {% endnote %} - -3. 要验证所有复制通道均报告 `OK`，请使用 `ghe-repl-status -vv` 命令。 - ```shell - $ ghe-repl-status -vv - ``` -4. 要停止复制并将副本设备升级为主设备，请使用 `ghe-repl-promote` 命令。 此操作还会自动将主节点（若可到达）置于维护模式。 +4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. 此操作还会自动将主节点（若可到达）置于维护模式。 ```shell $ ghe-repl-promote ``` diff --git a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md index 8e0e3bddfe..4000353c26 100644 --- a/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md +++ b/translations/zh-CN/content/admin/user-management/managing-repositories-in-your-enterprise/restoring-a-deleted-repository.md @@ -1,6 +1,6 @@ --- title: 恢复已删除的仓库 -intro: Site administrators can restore deleted repositories to recover their contents. +intro: 站点管理员可以恢复已删除的仓库来恢复其内容。 versions: ghes: '*' ghae: '*' @@ -8,14 +8,14 @@ topics: - Enterprise - Privacy - Repositories -shortTitle: Restore a deleted repository +shortTitle: 恢复已删除的仓库 --- -通常情况下，如果有人删除仓库，它将在磁盘上保留 90 天并且可以通过站点管理员仪表板进行恢复。 Unless a legal hold is in effect on a user or organization, after 90 days the repository is purged and deleted forever. +通常情况下，如果有人删除仓库，它将在磁盘上保留 90 天并且可以通过站点管理员仪表板进行恢复。 除非法定保留对用户或组织有效，否则 90 天后，存储库将被清除并永久删除。 ## 关于仓库恢复 -If a repository was part of a fork network when it was deleted, the restored repository will be detached from the original fork network. +如果存储库在被删除时是复刻网络的一部分，则还原的存储库将与原始复刻网络分离。 仓库被删除后，可能需要一个小时才能恢复。 @@ -26,10 +26,10 @@ If a repository was part of a fork network when it was deleted, the restored rep {% data reusables.enterprise_site_admin_settings.access-settings %} {% data reusables.enterprise_site_admin_settings.search-user-or-org %} {% data reusables.enterprise_site_admin_settings.click-user-or-org %} -1. In the {% octicon "repo" aria-label="The repo icon" %} **Repositories** section, click the {% octicon "trash" aria-label="The trash icon" %} **Deleted repositories** link. -1. Find the repository you want to restore in the deleted repositories list, then to the right of the repository name click **Restore**. -1. To confirm you would like to restore the named repository, click **Restore**. +1. 在 {% octicon "repo" aria-label="The repo icon" %} **存储库**部分，单击 {% octicon "trash" aria-label="The trash icon" %} **已删除的存储库**链接。 +1. 在已删除的存储库列表中找到要还原的存储库，然后在存储库名称右侧单击 **Restore（还原）**。 +1. 要确认是否要还原指定的存储库，请单击 **Restore（还原）**。 ## 延伸阅读 -- "[Placing a legal hold on a user or organization](/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization)" +- "[对用户或组织合法保留](/admin/user-management/managing-users-in-your-enterprise/placing-a-legal-hold-on-a-user-or-organization)" diff --git a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index b04d237d3a..b65b8cf7d9 100644 --- a/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/zh-CN/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -25,7 +25,7 @@ topics: 在迁移中，一切都围绕仓库进行。 与仓库关联的大多数数据都可以迁移。 例如，组织内的仓库将迁移仓库*和*组织，以及与该仓库关联的任何用户、团队、问题和拉取请求。 -下表中的项可随仓库一起迁移。 迁移的数据列表中未显示的任何项都无法迁移。 +下表中的项可随仓库一起迁移。 Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} diff --git a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index 291407dc29..edd4ada50f 100644 --- a/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/zh-CN/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -25,7 +25,7 @@ shortTitle: Check for existing SSH key # Lists the files in your .ssh directory, if they exist ``` -3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% elsif fpt or ghes %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. +3. Check the directory listing to see if you already have a public SSH key. By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% else %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. - *id_rsa.pub* - *id_ecdsa.pub* - *id_ed25519.pub*{% endif %} diff --git a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index 3b0faba806..7ffedc539e 100644 --- a/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/zh-CN/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -33,7 +33,7 @@ $ ssh -T -p 443 git@ssh.github.com 如果您能在端口 443 上通过 SSH 连接到 `git@ssh.{% data variables.command_line.backticks %}`，则可以覆盖您的 SSH 设置以强制与 {% data variables.product.product_location %} 的任何连接均通过该服务器和端口运行。 -要在 SSH 配置文件中设置此设置，请在 `~/.ssh/config` 编辑该文件，并添加以下部分： +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} diff --git a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md index f49db4795c..9549eaaae2 100644 --- a/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/zh-CN/content/code-security/secret-scanning/about-secret-scanning.md @@ -31,9 +31,9 @@ If your project communicates with an external service, you might use a token or {% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is available on {% data variables.product.prodname_dotcom_the_website %} in two forms: -1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relvant partner. +1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relevant partner. -2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scannng partners, by other service providers, or defined by your organization are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. +2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scanning partners, by other service providers, or defined by your organization, are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. {% endif %} Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %} diff --git a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md index becd84f143..00c48172fc 100644 --- a/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md +++ b/translations/zh-CN/content/codespaces/codespaces-reference/using-the-vs-code-command-palette-in-codespaces.md @@ -1,5 +1,5 @@ --- -title: Using the Visual Studio Code Command Palette in Codespaces +title: 在 Codespaces 中使用 Visual Studio 代码命令面板 intro: '您可以使用 {% data variables.product.prodname_vscode %} 的命令调色板功能访问代码空间中的许多命令。' versions: fpt: '*' @@ -9,21 +9,21 @@ topics: - Codespaces - Visual Studio Code product: '{% data reusables.gated-features.codespaces %}' -shortTitle: VS Code Command Palette +shortTitle: VS 代码命令面板 allowTitleToDifferFromFilename: true redirect_from: - /codespaces/codespaces-reference/using-the-command-palette-in-codespaces --- -## About the {% data variables.product.prodname_vscode %} Command Palette +## 关于 {% data variables.product.prodname_vscode %} 命令面板 -命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 The {% data variables.product.prodname_vscode_command_palette %} allows you to access many commands for {% data variables.product.prodname_codespaces %} and {% data variables.product.prodname_vscode %}. For more information on using the {% data variables.product.prodname_vscode_command_palette %}, see "[User Interface](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)" in the Visual Studio Code documentation. +命令调色板是 {% data variables.product.prodname_vscode %} 的重点功能之一，可用于代码空间。 {% data variables.product.prodname_vscode_command_palette %} 允许您访问 {% data variables.product.prodname_codespaces %} 和 {% data variables.product.prodname_vscode %} 的许多命令。 有关使用 {% data variables.product.prodname_vscode_command_palette %} 的更多信息，请参阅 visual Studio Code 文档中的 “[用户界面](https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette)”。 -## Accessing the {% data variables.product.prodname_vscode_command_palette %} +## 访问 {% data variables.product.prodname_vscode_command_palette %} -You can access the {% data variables.product.prodname_vscode_command_palette %} in a number of ways. +您可以通过多种方式访问 {% data variables.product.prodname_vscode_command_palette %}。 -- Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux). +- Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux)。 请注意，此命令是 Firefox 中保留的键盘快捷键。 - F1 @@ -33,21 +33,21 @@ You can access the {% data variables.product.prodname_vscode_command_palette %} ## {% data variables.product.prodname_github_codespaces %} 命令 -To see all commands related to {% data variables.product.prodname_github_codespaces %}, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "Codespaces". +要查看与 {% data variables.product.prodname_github_codespaces %} 相关的所有命令， [访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "Codespaces"。 ![与代码空间相关的所有命令列表](/assets/images/help/codespaces/codespaces-command-palette.png) ### 挂起或停止代码空间 -If you add a new secret or change the machine type, you'll have to stop and restart the codespace for it to apply your changes. +如果添加新密钥或更换机器类型，则必须停止并重新启动代码空间才能应用更改。 -To suspend or stop your codespace's container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "stop". 选择 **Codespaces: Stop Current Codespace（Codespace：停止当前 Codespace）**。 +要暂停或停止代码空间的容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入"stop"。 选择 **Codespaces: Stop Current Codespace（Codespace：停止当前 Codespace）**。 ![停止代码空间的命令](/assets/images/help/codespaces/codespaces-stop.png) ### 从模板添加开发容器 -To add a dev container from a template, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "dev container". 选择 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** +要从模板添加开发容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "dev container"。 选择 **Codespaces: Add Development Container Configuration Files...（Codespaces：添加开发容器配置文件...）** ![添加开发容器的命令](/assets/images/help/codespaces/add-prebuilt-container-command.png) @@ -55,14 +55,14 @@ To add a dev container from a template, [access the {% data variables.product.pr 如果您添加 dev 容器或编辑任何配置文件（`devcontainer.json` 和 `Dockerfile`），则需要重建代码空间才可应用更改。 -To rebuild your container, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "rebuild". 选择 **Codespaces: Rebuild Container（代码空间：重建容器）**。 +要重建容器，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "rebuild"。 选择 **Codespaces: Rebuild Container（代码空间：重建容器）**。 ![重建代码空间的命令](/assets/images/help/codespaces/codespaces-rebuild.png) ### Codespaces 日志 -You can use the {% data variables.product.prodname_vscode_command_palette %} to access the codespace creation logs, or you can use it export all logs. +可以使用 {% data variables.product.prodname_vscode_command_palette %} 访问代码空间创建日志，也可以使用它导出所有日志。 -To retrieve the logs for Codespaces, [access the {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette), then start typing "log". 选择 **Codespaces: Export Logs（Codespaces：导出日志）**以导出所有与 Codespaces 相关的日志，或选择 **Codespaces: View Creation Logs（Codespaces：查看创建日志）**以查看与设置相关的日志。 +要检索 Codespaces 的日志，[访问 {% data variables.product.prodname_vscode_command_palette %}](#accessing-the-command-palette)，然后开始键入 "log"。 选择 **Codespaces: Export Logs（Codespaces：导出日志）**以导出所有与 Codespaces 相关的日志，或选择 **Codespaces: View Creation Logs（Codespaces：查看创建日志）**以查看与设置相关的日志。 ![访问日志的命令](/assets/images/help/codespaces/codespaces-logs.png) diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md index 9ee02aab12..f13d002eb3 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/creating-a-codespace.md @@ -14,7 +14,7 @@ topics: - Codespaces - Fundamentals - Developer -shortTitle: Create a codespace +shortTitle: 创建代码空间 --- ## 关于代码空间的创建 diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md index 3199aa5282..2e7a09d0b7 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/deleting-a-codespace.md @@ -13,7 +13,7 @@ topics: - Codespaces - Fundamentals - Developer -shortTitle: Delete a codespace +shortTitle: 删除代码空间 --- diff --git a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md index 4476c38f0b..089a99a913 100644 --- a/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md +++ b/translations/zh-CN/content/codespaces/developing-in-codespaces/using-codespaces-with-github-cli.md @@ -13,7 +13,7 @@ topics: - Developer --- -## 关于 {% data variables.product.prodname_cli %} +## About {% data variables.product.prodname_cli %} {% data reusables.cli.about-cli %} For more information, see "[About {% data variables.product.prodname_cli %}](/github-cli/github-cli/about-github-cli)." @@ -28,22 +28,26 @@ You can work with {% data variables.product.prodname_codespaces %} in the {% da - [Modify ports in a codespace](#modify-ports-in-a-codespace) - [Access codespace logs](#access-codespace-logs) -## 安装 {% data variables.product.prodname_cli %} +## Installing {% data variables.product.prodname_cli %} {% data reusables.cli.cli-installation %} + +## Using {% data variables.product.prodname_cli %} -## 使用 {% data variables.product.prodname_cli %} - -If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account. +If you have not already done so, run `gh auth login` to authenticate with your {% data variables.product.prodname_dotcom %} account. To use `gh` to work with {% data variables.product.prodname_codespaces %}, type `gh codespace ` or its alias `gh cs `. -As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could: +As an example of a series of commands you might use to work with {% data variables.product.prodname_github_codespaces %}, you could: -* List your current codespaces, to check whether you have a codespace for a particular repository:
`gh codespace list` -* Create a new codespace for the required repository branch:
`gh codespace create -r github/docs -b main` -* SSH into the new codespace:
`gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w` -* Forward a port to your local machine:
`gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w` +* List your current codespaces, to check whether you have a codespace for a particular repository:
+ `gh codespace list` +* Create a new codespace for the required repository branch:
+ `gh codespace create -r github/docs -b main` +* SSH into the new codespace:
+ `gh codespace ssh -c mona-github-docs-v4qxrv7rfwv9w` +* Forward a port to your local machine:
+ `gh codespace ports forward 8000:8000 -c mona-github-docs-v4qxrv7rfwv9w` ## `gh` commands for {% data variables.product.prodname_github_codespaces %} @@ -71,7 +75,7 @@ The list includes the unique name of each codespace, which you can use in other gh codespace create -r owner/repository [-b branch] ``` -更多信息请参阅“[创建代码空间](/codespaces/developing-in-codespaces/creating-a-codespace)”。 +For more information, see "[Creating a codespace](/codespaces/developing-in-codespaces/creating-a-codespace)." ### Stop a codespace @@ -119,7 +123,7 @@ Use the prefix `remote:` on a file or directory name to indicate that it's on th The location of files and directories on the codespace is relative to the home directory of the remote user. -#### 示例 +#### Examples * Copy a file from the local machine to the `$HOME` directory of a codespace: @@ -167,13 +171,13 @@ You can set the visibility of a forwarded port. {% data reusables.codespaces.por gh codespace ports visibility codespace-port:private|org|public -c codespace-name ``` -You can set the visibility for multiple ports with one command. 例如： +You can set the visibility for multiple ports with one command. For example: ```shell gh codespace ports visibility 80:private 3000:public 3306:org -c codespace-name ``` -更多信息请参阅“[在代码空间中转发端口](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)”。 +For more information, see "[Forwarding ports in your codespace](/codespaces/developing-in-codespaces/forwarding-ports-in-your-codespace)." ### Access codespace logs diff --git a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md index 6ef8d49d2a..d572564bde 100644 --- a/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md +++ b/translations/zh-CN/content/get-started/quickstart/fork-a-repo.md @@ -22,7 +22,7 @@ topics: ## 关于复刻 -复刻最常见的用法是对其他人的项目提出更改或将其他人的项目用作自己创意的起点。 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。 +Most commonly, forks are used to either propose changes to someone else's project to which you don't have write access, or to use someone else's project as a starting point for your own idea. 您可以复刻仓库以创建仓库的副本，并在不影响上游仓库的情况下进行更改。 更多信息请参阅“[使用复刻](/github/collaborating-with-issues-and-pull-requests/working-with-forks)”。 ### 对其他人的项目提出更改 diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md index ea1937b0dc..02af612463 100644 --- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md +++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-access-to-projects.md @@ -66,7 +66,7 @@ You can only invite an individual user to collaborate on your organization-level {% note %} -This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." +This only affects collaborators for your project, not for repositories in your project. To view an item on the project, someone must have the required permissions for the repository that the item belongs to. 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。 For more information, see "[Setting repository visibility](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" and "[Managing teams and people with access to your repository](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-teams-and-people-with-access-to-your-repository)." {% endnote %} diff --git a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md index 147f39eb56..89185c749e 100644 --- a/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md +++ b/translations/zh-CN/content/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects.md @@ -1,6 +1,6 @@ --- -title: Managing the visibility of your projects (beta) -intro: You can control who can view your projects. +title: 管理项目的可见性（测试版） +intro: 您可以控制谁可以查看您的项目。 allowTitleToDifferFromFilename: true miniTocMaxHeadingLevel: 3 versions: @@ -13,21 +13,21 @@ topics: {% data reusables.projects.projects-beta %} -## About project visibility +## 关于项目可见性 -Projects (beta) can be public or private. For public projects, everyone on the internet can view the project. For private projects, only users granted at least read access can see the project. +项目（测试版）可以是公共的，也可以是私有的。 对于公共项目，互联网上的每个人都可以查看。 对于私有项目，只有被授予至少读取访问权限的用户才能查看。 -Only the project visibility is affected; to view an item on the project, someone must have the required permissions for the repository that the item belongs to. If your project includes items from a private repository, people who are not collaborators in the repository will not be able to view items from that repository. +只有项目可见性会受影响；要查看项目上的项，必须有人具有该项所属存储库所需的权限。 如果项目包含私有存储库中的项目，则不是存储库协作者的用户将无法查看该存储库中的项。 -![Project with hidden item](/assets/images/help/projects/hidden-items.png) +![包含隐藏项的项目](/assets/images/help/projects/hidden-items.png) -Only project admins can control project visibility. +只有项目管理员才能控制项目可见性。 -In private, organization-owned projects, the avatars of users who are current making updates to the project are displayed in the project UI. +在组织拥有的私有项目中，当前对项目进行更新的用户的头像将显示在项目 UI 中。 -Project admins can also manage write and admin access to their project and control read access for individual users. For more information, see "[Managing access to projects](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)." +项目管理员还可以管理对其项目的写入和管理员访问权限，并控制单个用户的读取访问权限。 更多信息请参阅“[管理对项目的访问](/issues/trying-out-the-new-projects-experience/managing-access-to-projects)”。 -## Changing project visibility +## 更改项目可见性 {% data reusables.projects.project-settings %} -1. Under **Visibility**, select **Private** or **Public**. +1. 在 **Visibility（可见性）**下，选择 **Private（私有）**或 **Public（公共）**。 diff --git a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md index f58eecfe2f..85c4c5901c 100644 --- a/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md +++ b/translations/zh-CN/content/organizations/managing-peoples-access-to-your-organization-with-roles/managing-custom-repository-roles-for-an-organization.md @@ -1,147 +1,147 @@ --- -title: Managing custom repository roles for an organization -intro: You can more granularly control access to your organization's repositories by creating custom repository roles. +title: 管理组织的自定义存储库角色 +intro: 通过创建自定义存储库角色，可以更精细地控制对组织存储库的访问。 permissions: Organization owners can manage custom repository roles. versions: ghec: '*' topics: - Organizations - Teams -shortTitle: Custom repository roles +shortTitle: 自定义存储库角色 redirect_from: - /early-access/github/articles/managing-custom-repository-roles-for-an-organization --- {% data reusables.pre-release-program.custom-roles-public-beta %} -## About custom repository roles +## 关于自定义存储库角色 -To perform any actions on {% data variables.product.product_name %}, such as creating a pull request in a repository or changing an organization's billing settings, a person must have sufficient access to the relevant account or resource. This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. +要对 {% data variables.product.product_name %} 执行任何操作，例如在存储库中创建拉取请求或更改组织的计费设置，人员必须具有对相关帐户或资源的足够访问权限。 This access is controlled by permissions. A permission is the ability to perform a specific action. For example, the ability to delete an issue is a permission. A role is a set of permissions you can assign to individuals or teams. -Within an organization, you can assign roles at the organization, team, and repository level. For more information about the different levels of roles, see "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)." +在组织内，您可以在组织、团队和存储库级别分配角色。 有关不同级别角色的更多信息，请参阅“[组织中的角色](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)”。 -If your organization uses {% data variables.product.prodname_ghe_cloud %}, you can have more granular control over the permissions you grant at the repository level by creating up to three custom repository roles. A custom repository role is a configurable set of permissions with a custom name you choose. After you create a custom role, anyone with admin access to a repository can assign the role to an individual or team. For more information, see "[Managing an individual's access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)" and "[Managing team access to an organization repository](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)" +如果您的组织使用 {% data variables.product.prodname_ghe_cloud %}，则通过创建最多三个自定义存储库角色，可以更精细地控制在存储库级别授予的权限。 自定义存储库角色是一组可配置的权限，具有您选择的自定义名称。 创建自定义角色后，对存储库具有管理员访问权限的任何人都可以将该角色分配给个人或团队。 更多信息请参阅“[管理个人对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository)”和“[管理团队对组织存储库的访问](/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository)” {% data reusables.enterprise.link-to-ghec-trial %} -## About the inherited role +## 关于继承的角色 -When you create a custom repository role, you start by choosing an inherited role from a set of pre-defined options. The inherited role determines the initial set of permissions included in the custom role. Then, you can further customize the role by choosing additional permissions to give the role. For the full list of available permissions, see "[Additional permissions for custom roles](#additional-permissions-for-custom-roles)." +创建自定义存储库角色时，首先从一组预定义选项中选择继承的角色。 继承的角色确定自定义角色中包含的初始权限集。 然后，您可以通过选择其他权限来授予角色，从而进一步自定义角色。 有关可用权限的完整列表，请参阅“[自定义角色的其他权限](#additional-permissions-for-custom-roles)”。 -Your options for the inherited role are standardized for different types of contributors in your repository. +继承角色的选项已针对存储库中不同类型的参与者进行了标准化。 -| Inherited role | Designed for | -| -------------- | ------------------------------------------------------------------------------------------------------ | -| **读取** | Non-code contributors who want to view or discuss your project. | -| **分类** | Contributors who need to proactively manage issues and pull requests without write access. | -| **写入** | Organization members and collaborators who actively push to your project. | -| **维护** | Project managers who need to manage the repository without access to sensitive or destructive actions. | +| 继承的角色 | 适用于 | +| ------ | ------------------------------- | +| **读取** | 想要查看或讨论项目的非代码参与者。 | +| **分类** | 需要主动管理问题和在没有写入访问权限的情况下拉取请求的参与者。 | +| **写入** | 积极推动项目的组织成员和协作者。 | +| **维护** | 需要管理存储库而无法访问敏感或破坏性操作的项目经理。 | -## Custom role examples +## 自定义角色示例 -Here are some examples of custom repository roles you can configure. +以下是您可以配置的自定义存储库角色的一些示例。 -| Custom repository role | 摘要 | Inherited role | Additional permissions | -| ---------------------- | ----------------------------------------------------------------------------------- | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Security engineer | Able to contribute code and maintain the security pipeline | **维护** | Delete code scanning results | -| Contractor | Able to develop webhooks integrations | **写入** | Manage webhooks | -| Community manager | Able to handle all the community interactions without being able to contribute code | **读取** | - Mark an issue as duplicate
- Manage GitHub Page settings
- Manage wiki settings
- Set the social preview
- Edit repository metadata
- Triage discussions | +| 自定义存储库角色 | 摘要 | 继承的角色 | 其他权限 | +| -------- | ------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------ | +| 安全工程师 | 能够贡献代码并维护安全管道 | **维护** | 删除代码扫描结果 | +| 承包商 | 能够开发 web 挂钩集成 | **写入** | 管理 web 挂钩 | +| 社区经理 | 能够处理所有社区互动，而无需贡献代码 | **读取** | - 将问题标记为重复
- 管理 GitHub Pages 设置 -
管理 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. +仅当继承的角色中尚未包含其他权限时，才能选择该权限。 例如，如果继承的角色提供对存储库**写入**访问权限，则“关闭拉取请求”权限将已包含在继承的角色中。 -### Issue and Pull Requests +### 议题和拉取请求 -- **Assign or remove a user**: Assign a user to an issue or pull request, or remove a user from an issue or pull request. -- **Add or remove a label**: Add a label to an issue or a pull request, or remove a label from an issue or pull request. +- **分配或删除用户**：将用户分配给问题或拉取请求，或从问题或拉取请求中删除用户。 +- **添加或删除标签**：向议题或拉取请求添加标签，或者从议题或拉取请求中删除标签。 ### 议题 -- **Close an issue** -- **Reopen a closed issue** -- **Delete an issue** -- **Mark an issue as a duplicate** +- **关闭议题** +- **重新打开已关闭的议题** +- **删除议题** +- **将议题标记为重复** ### 拉取请求 -- **Close a pull request** -- **Reopen a closed pull request** -- **Request a pull request review**: Request a review from a user or team. +- **关闭拉取请求** +- **重新打开已关闭的拉取请求** +- **请求拉取请求审核**：请求用户或团队审核。 ### 仓库 -- **Set milestones**: Add milestones to an issue or pull request. -- **Manage wiki settings**: Turn on wikis for a repository. -- **Manage project settings**: Turning on projects for a repository. -- **Manage pull request merging settings**: Choose the type of merge commits that are allowed in your repository, such as merge, squash, or rebase. -- **Manage {% data variables.product.prodname_pages %} settings**: Enable {% data variables.product.prodname_pages %} for the repository, and select the branch you want to publish. 更多信息请参阅“[配置 {% data variables.product.prodname_pages %} 站点的发布来源](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site)”。 -- **Manage webhooks**: Add webhooks to the repository. -- **Manage deploy keys**: Add deploy keys to the repository. -- **Edit repository metadata**: Update the repository description as well as the repository topics. -- **Set interaction limits**: Temporarily restrict certain users from commenting, opening issues, or creating pull requests in your public repository to enforce a period of limited activity. For more information, see "[Limiting interactions in your repository](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)." -- **Set the social preview**: Add an identifying image to your repository that appears on social media platforms when your repository is linked. 更多信息请参阅“[自定义仓库的社交媒体审查](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)”。 -- **Push commits to protected branches**: Push to a branch that is marked as a protected branch. -- **Create protected tags**: Create tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." -- **Delete protected tags**: Delete tags that match a tag protection rule. For more information, see "[Configuring tag protection rules](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)." +- **设置里程碑**：将里程碑添加到议题或拉取请求。 +- **管理 wiki 设置**：打开存储库的 wiki。 +- **管理项目设置**：打开存储库的项目。 +- **管理拉取请求合并设置**：选择存储库中允许的合并提交类型，例如合并、压缩或变基。 +- **管理 {% data variables.product.prodname_pages %} 设置**：为存储库启用 {% 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 挂钩**：将 web 挂钩添加到存储库。 +- **管理部署密钥**：将部署密钥添加到存储库。 +- **编辑存储库元数据**：更新存储库描述以及存储库主题。 +- **设置交互限制**：暂时限制某些用户在公共存储库中发表评论、打开议题或创建拉取请求，以强制执行一段有限的活动。 更多信息请参阅“[限制存储库中的交互](/communities/moderating-comments-and-conversations/limiting-interactions-in-your-repository)”。 +- **设置社交预览**：将识别图像添加到存储库，该图像在链接存储库时显示在社交媒体平台上。 更多信息请参阅“[自定义仓库的社交媒体审查](/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/customizing-your-repositorys-social-media-preview)”。 +- **推送提交到受保护分支**：推送到标记为受保护分支的分支。 +- **创建受保护的标记**：创建与标记保护规则匹配的标记。 更多信息请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。 +- **删除受保护的标记**：删除与标记保护规则匹配的标记。 更多信息请参阅“[配置标记保护规则](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-tag-protection-rules)”。 ### 安全 -- **View {% data variables.product.prodname_code_scanning %} results**: Ability to view {% data variables.product.prodname_code_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_code_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_code_scanning %} alerts. -- **Delete {% data variables.product.prodname_code_scanning %} results**: Ability to delete {% data variables.product.prodname_code_scanning %} alerts. -- **View {% data variables.product.prodname_dependabot_alerts %}**: Ability to view {% data variables.product.prodname_dependabot_alerts %}. -- **Dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}**: Ability to dismiss or reopen {% data variables.product.prodname_dependabot_alerts %}. -- **View {% data variables.product.prodname_secret_scanning %} results**: Ability to view {% data variables.product.prodname_secret_scanning %} alerts. -- **Dismiss or reopen {% data variables.product.prodname_secret_scanning %} results**: Ability to dismiss or reopen {% data variables.product.prodname_secret_scanning %} alerts. +- **查看 {% data variables.product.prodname_code_scanning %} 结果**：能够查看 {% data variables.product.prodname_code_scanning %} 警报。 +- **忽略或重新打开 {% data variables.product.prodname_code_scanning %} 结果**：能够忽略或重新打开 {% 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_dependabot_alerts %}**：能够忽略或重新打开 {% data variables.product.prodname_dependabot_alerts %}。 +- **查看 {% data variables.product.prodname_secret_scanning %} 结果**：能够查看 {% data variables.product.prodname_secret_scanning %} 警报。 +- **忽略或重新打开 {% data variables.product.prodname_secret_scanning %} 结果**：能够忽略或重新打开 {% 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. 更多信息请参阅： +要解决冲突的访问权限，您可以调整组织的基本权限或团队的访问权限，或编辑自定义角色。 更多信息请参阅： - “[设置组织的基本权限](/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](#editing-a-repository-role)" + - "[编辑存储库角色](#editing-a-repository-role)" -## Creating a repository role +## 创建存储库角色 -To create a new repository role, you add permissions to an inherited role and give the custom role a name. +要创建新的存储库角色，请向继承的角色添加权限并为自定义角色命名。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -5. Click **Create a Role**. ![Screenshot of "Create a Role" button](/assets/images/help/organizations/repository-role-create-role.png) -4. Under "Name", type the name of your repository role. ![Field to type a name for the repository role](/assets/images/help/organizations/repository-role-name.png) -5. Under "Description", type a description of your repository role. ![Field to type a description for the repository role](/assets/images/help/organizations/repository-role-description.png) -6. Under "Choose a role to inherit", select the role you want to inherit. ![Selecting repository role base role option](/assets/images/help/organizations/repository-role-base-role-option.png) -7. Under "Add Permissions", use the drop-down menu to select the permissions you want your custom role to include. ![Selecting permission levels from repository role drop-down](/assets/images/help/organizations/repository-role-drop-down.png) -7. Click **Create role**. ![Confirm creating a repository role](/assets/images/help/organizations/repository-role-creation-confirm.png) +5. 单击 **Create a Role（创建角色）**。 ![" "创建角色" "按钮的屏幕截图](/assets/images/help/organizations/repository-role-create-role.png) +4. 在“Name（名称）”下，键入存储库角色的名称。 ![用于键入存储库角色名称的字段](/assets/images/help/organizations/repository-role-name.png) +5. 在“Description（描述）”下，键入存储库角色的描述。 ![用于键入存储库角色描述的字段](/assets/images/help/organizations/repository-role-description.png) +6. 在“Choose a role to inherit（选择要继承的角色）”下，选择要继承的角色。 ![选择存储库角色基本角色选项](/assets/images/help/organizations/repository-role-base-role-option.png) +7. 在“Add Permissions（添加权限）”下，使用下拉菜单选择您希望自定义角色包含的权限。 ![从存储库角色下拉列表中选择权限级别](/assets/images/help/organizations/repository-role-drop-down.png) +7. 单击 **Create a role（创建角色）**。 ![确认创建存储库角色](/assets/images/help/organizations/repository-role-creation-confirm.png) -## Editing a repository role +## 编辑存储库角色 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to edit, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Edit**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-edit-setting.png) -4. Edit, then click **Update role**. ![Edit fields and update repository roles](/assets/images/help/organizations/repository-role-update.png) +3. 在要删除的角色的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Edit（编辑）**。 ![存储库角色下拉菜单中的编辑选项](/assets/images/help/organizations/repository-role-edit-setting.png) +4. 编辑，然后单击 **Update role（更新角色）**。 ![编辑字段和更新存储库角色](/assets/images/help/organizations/repository-role-update.png) -## Deleting a repository role +## 删除存储库角色 -If you delete an existing repository role, all pending invitations, teams, and users with the custom role will be reassigned to the organization's base permissions. +如果您删除现有存储库角色，则所有具有自定义角色的待处理邀请、团队和用户都将被重新分配给组织的基本权限。 {% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.org-list %} {% data reusables.organizations.org-settings-repository-roles %} -3. To the right of the role you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}, then click **Delete**. ![Edit option in drop-down menu for repository roles](/assets/images/help/organizations/repository-role-delete-setting.png) -4. Review changes for the role you want to remove, then click **Delete role**. ![Confirm deleting a repository role](/assets/images/help/organizations/repository-role-delete-confirm.png) +3. 在要删除的角色的右侧，单击 {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}，然后单击 **Delete（删除）**。 ![存储库角色下拉菜单中的编辑选项](/assets/images/help/organizations/repository-role-delete-setting.png) +4. 查看要删除的角色的更改，然后单击 **Delete role（删除角色）**。 ![确认删除存储库角色](/assets/images/help/organizations/repository-role-delete-confirm.png) diff --git a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index 7afd4c566b..a8ef7ddf56 100644 --- a/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/zh-CN/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -17,9 +17,11 @@ topics: shortTitle: 请求 PR 审查 --- -用户帐户拥有的仓库的所有者和协作者可以分配拉取请求审查。 拥有仓库查验漏洞权限的组织成员可以分配拉取请求审查。 +Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). 更多信息请参阅“[{% data variables.product.prodname_dotcom %} 帐户的类型](/get-started/learning-about-github/types-of-github-accounts)”。 Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request. -所有者或协作者可以将拉取请求审核分配给被明确授予用户拥有仓库[读取权限](/articles/access-permissions-on-github)的任何人。 组织成员也可将拉取请求审查分配给拥有仓库读取权限的任何个人或团队。 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% ifversion fpt or ghae or ghes or ghec %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. + +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. 被请求的审查者或团队将收到您请求他们审查拉取请求的通知。 {% ifversion fpt or ghae or ghes or ghec %}如果您请求团队审查，并且启用了代码审查分配，则会向特定成员发出申请，并且取消团队作为审查者。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} {% note %} diff --git a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 38250866d5..7732e3c8ac 100644 --- a/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -38,7 +38,7 @@ topics: 为使代码所有者接收审查请求，CODEOWNERS 文件必须在拉取请求的基本分支上。 例如，如果您将 `@octocat` 分配为仓库 `gh-pages` 分支上 *.js* 文件的代码所有者，则在头部分支与 `gh-pages` 之间打开更改 *.js* 文件的拉取请求时，`@octocat` 将会收到审查请求。 -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %} ## CODEOWNERS 文件大小 CODEOWNERS 文件大小必须低于 3MB。 将不会加载超过此限制的 CODEOWNERS 文件，这意味着不会显示代码所有者信息，并且不会要求相应的代码所有者查看拉取请求中的更改。 diff --git a/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index c81c08a9de..2fb1bc4bd3 100644 --- a/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/translations/zh-CN/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -7,7 +7,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae-issue-4974: '*' + ghae: issue-4974 topics: - Repositories --- diff --git a/translations/zh-CN/content/rest/reference/codespaces.md b/translations/zh-CN/content/rest/reference/codespaces.md index 11f28ca643..3a07a37eb0 100644 --- a/translations/zh-CN/content/rest/reference/codespaces.md +++ b/translations/zh-CN/content/rest/reference/codespaces.md @@ -1,6 +1,6 @@ --- title: Codespaces -intro: 'The {% data variables.product.prodname_codespaces %} API enables you to manage your codespaces using the REST API.' +intro: '{% data variables.product.prodname_codespaces %} API 允许您使用 REST API 管理代码空间。' product: '{% data reusables.gated-features.codespaces %}' versions: fpt: '*' @@ -12,4 +12,4 @@ miniTocMaxHeadingLevel: 3 \ No newline at end of file +--> diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml index f4db0c2cc8..ccd0725cf4 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-1/0.yml @@ -76,6 +76,7 @@ sections: - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - Check annotations older than four months will be archived. + - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - heading: Security Changes notes: diff --git a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml index f93f958df2..ae450a768d 100644 --- a/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/zh-CN/data/release-notes/enterprise-server/3-4/0.yml @@ -29,6 +29,11 @@ sections: notes: - | {% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/github/feedback/discussions/categories/dependabot-feedback). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + - + heading: SAML authentication supports encrypted assertions + notes: + - | + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." changes: - heading: 管理更改 diff --git a/translations/zh-CN/data/reusables/code-scanning/beta.md b/translations/zh-CN/data/reusables/code-scanning/beta.md index 2737a4e73b..42bf4638be 100644 --- a/translations/zh-CN/data/reusables/code-scanning/beta.md +++ b/translations/zh-CN/data/reusables/code-scanning/beta.md @@ -1,4 +1,8 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} {% note %} diff --git a/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md b/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md index 310339895f..337d796c17 100644 --- a/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md +++ b/translations/zh-CN/data/reusables/rest-reference/orgs/custom_roles.md @@ -1 +1 @@ -## Custom repository roles \ No newline at end of file +## 自定义存储库角色 \ No newline at end of file diff --git a/translations/zh-CN/data/reusables/secret-scanning/beta.md b/translations/zh-CN/data/reusables/secret-scanning/beta.md index b7064d4a0a..4676aecb28 100644 --- a/translations/zh-CN/data/reusables/secret-scanning/beta.md +++ b/translations/zh-CN/data/reusables/secret-scanning/beta.md @@ -1,4 +1,9 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} + {% note %} **注意：**组织拥有的仓库的 {% data variables.product.prodname_secret_scanning_caps %} 目前处于公测阶段，可能会有变动。 diff --git a/translations/zh-CN/data/variables/product.yml b/translations/zh-CN/data/variables/product.yml index 8daf51cd32..df050c6dde 100644 --- a/translations/zh-CN/data/variables/product.yml +++ b/translations/zh-CN/data/variables/product.yml @@ -142,7 +142,7 @@ prodname_vs: 'Visual Studio' prodname_vscode: 'Visual Studio Code' prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise' prodname_vss_admin_portal_with_url: '[Visual Studio 订阅的管理员门户](https://visualstudio.microsoft.com/subscriptions-administration/)' -prodname_vscode_command_palette: 'VS Code Command Palette' +prodname_vscode_command_palette: 'VS 代码命令面板' #GitHub Dependabot prodname_dependabot: 'Dependabot' prodname_dependabot_alerts: 'Dependabot 警报' From fba1a1bd81620890da5ab1f7100b17705eeb47f4 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 21 Mar 2022 14:19:06 -0700 Subject: [PATCH 14/18] New translation batch for ja (#26387) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=ja * run script/i18n/reset-known-broken-translation-files.js * Check in ja CSV report Co-authored-by: Peter Bengtsson --- .../workflow-commands-for-github-actions.md | 466 +++++++++++++++--- .../configuring-a-hostname.md | 8 +- ...ng-a-failover-to-your-replica-appliance.md | 39 +- .../about-migrations.md | 2 +- .../checking-for-existing-ssh-keys.md | 2 +- .../using-ssh-over-the-https-port.md | 2 +- .../secret-scanning/about-secret-scanning.md | 4 +- .../get-started/quickstart/fork-a-repo.md | 2 +- .../get-started/quickstart/hello-world.md | 2 +- ...hooting-custom-domains-and-github-pages.md | 8 +- ...ing-your-custom-domain-for-github-pages.md | 30 +- ...ithub-pages-site-with-the-theme-chooser.md | 2 +- ...shing-source-for-your-github-pages-site.md | 27 +- .../creating-a-github-pages-site.md | 2 +- ...uring-your-github-pages-site-with-https.md | 8 +- translations/ja-JP/content/pages/index.md | 2 +- .../ja-JP/content/pages/quickstart.md | 40 +- ...reating-a-github-pages-site-with-jekyll.md | 8 +- ...for-your-github-pages-site-using-jekyll.md | 21 +- ...r-github-pages-site-locally-with-jekyll.md | 2 +- .../requesting-a-pull-request-review.md | 6 +- .../about-code-owners.md | 2 +- .../searching-a-repositorys-releases.md | 2 +- .../release-notes/enterprise-server/3-1/0.yml | 1 + .../release-notes/enterprise-server/3-4/0.yml | 5 + .../data/reusables/code-scanning/beta.md | 6 +- .../data/reusables/secret-scanning/beta.md | 7 +- translations/log/ja-resets.csv | 2 + 28 files changed, 523 insertions(+), 185 deletions(-) diff --git a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md index 05248380fa..b366202437 100644 --- a/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/ja-JP/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -2,6 +2,7 @@ title: GitHub Actionsのワークフローコマンド shortTitle: ワークフロー コマンド intro: ワークフロー内あるいはアクションのコード内でシェルコマンドを実行する際には、ワークフローコマンドを利用できます。 +defaultTool: bash redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -26,10 +27,24 @@ versions: ほとんどのワークフローコマンドは特定の形式で `echo` コマンドを使用しますが、他のワークフローコマンドはファイルへの書き込みによって呼び出されます。 詳しい情報については、「[環境ファイル](#environment-files)」を参照してください。 -``` bash +### サンプル + +{% bash %} + +```bash{:copy} echo "::workflow-command parameter1={data},parameter2={data}::{command value}" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}" +``` + +{% endpowershell %} + {% note %} **ノート:** ワークフローコマンドおよびパラメータ名では、大文字と小文字は区別されません。 @@ -46,14 +61,18 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}" [actions/toolkit](https://github.com/actions/toolkit)には、ワークフローコマンドとして実行できる多くの関数があります。 `::`構文を使って、YAMLファイル内でワークフローコマンドを実行してください。それらのコマンドは`stdout`を通じてランナーに送信されます。 たとえば、コードを使用して出力を設定する代わりに、以下のようにします。 -```javascript +```javascript{:copy} core.setOutput('SELECTED_COLOR', 'green'); ``` +### Example: Setting a value + ワークフローで `set-output` コマンドを使用して、同じ値を設定できます。 +{% bash %} + {% raw %} -``` yaml +```yaml{:copy} - name: Set selected color run: echo '::set-output name=SELECTED_COLOR::green' id: random-color-generator @@ -62,6 +81,22 @@ core.setOutput('SELECTED_COLOR', 'green'); ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} + - name: Set selected color + run: Write-Output "::set-output name=SELECTED_COLOR::green" + id: random-color-generator + - name: Get color + run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}" +``` +{% endraw %} + +{% endpowershell %} + 以下の表は、ワークフロー内で使えるツールキット関数を示しています。 | ツールキット関数 | 等価なワークフローのコマンド | @@ -86,186 +121,336 @@ core.setOutput('SELECTED_COLOR', 'green'); ## 出力パラメータの設定 -``` +アクションの出力パラメータを設定します。 + +```{:copy} ::set-output name={name}::{value} ``` -アクションの出力パラメータを設定します。 - あるいは、出力パラメータをアクションのメタデータファイル中で宣言することもできます。 For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)." -### サンプル +### Example: Setting an output parameter -``` bash +{% bash %} + +```bash{:copy} echo "::set-output name=action_fruit::strawberry" ``` -## デバッグメッセージの設定 +{% endbash %} +{% powershell %} + +```pwsh{:copy} +Write-Output "::set-output name=action_fruit::strawberry" ``` -::debug::{message} -``` + +{% endpowershell %} + +## デバッグメッセージの設定 デバッグメッセージをログに出力します。 ログでこのコマンドにより設定されたデバッグメッセージを表示するには、`ACTIONS_STEP_DEBUG` という名前のシークレットを作成し、値を `true` に設定する必要があります。 詳しい情報については、「[デバッグログの有効化](/actions/managing-workflow-runs/enabling-debug-logging)」を参照してください。 -### サンプル +```{:copy} +::debug::{message} +``` -``` bash +### Example: Setting a debug message + +{% bash %} + +```bash{:copy} echo "::debug::Set the Octocat variable" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::debug::Set the Octocat variable" +``` + +{% endpowershell %} + {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} ## Setting a notice message -``` +Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Creates a notice message and prints the message to the log. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### サンプル +### Example: Setting a notice message -``` bash +{% bash %} + +```bash{:copy} echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} {% endif %} ## 警告メッセージの設定 -``` +警告メッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -警告メッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### サンプル +### Example: Setting a warning message -``` bash +{% bash %} + +```bash{:copy} echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## エラーメッセージの設定 -``` +エラーメッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -エラーメッセージを作成し、ログにそのメッセージを出力します。 {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### サンプル +### Example: Setting an error message -``` bash +{% bash %} + +```bash{:copy} echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## ログの行のグループ化 -``` +展開可能なグループをログ中に作成します。 グループを作成するには、`group`コマンドを使って`title`を指定してください。 `group`と`endgroup`コマンド間でログに出力したすべての内容は、ログ中の展開可能なエントリ内にネストされます。 + +```{:copy} ::group::{title} ::endgroup:: ``` -展開可能なグループをログ中に作成します。 グループを作成するには、`group`コマンドを使って`title`を指定してください。 `group`と`endgroup`コマンド間でログに出力したすべての内容は、ログ中の展開可能なエントリ内にネストされます。 +### Example: Grouping log lines -### サンプル +{% bash %} -```bash -echo "::group::My title" -echo "Inside group" -echo "::endgroup::" +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + steps: + - name: Group of log lines + run: | + echo "::group::My title" + echo "Inside group" + echo "::endgroup::" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + steps: + - name: Group of log lines + run: | + Write-Output "::group::My title" + Write-Output "Inside group" + Write-Output "::endgroup::" +``` + +{% endpowershell %} + ![ワークフローの実行ログ中の折りたたみ可能なグループ](/assets/images/actions-log-group.png) ## ログ中での値のマスク -``` +```{:copy} ::add-mask::{value} ``` 値をマスクすることにより、文字列または値がログに出力されることを防ぎます。 空白で分離された、マスクされた各語は "`*`" という文字で置き換えられます。 マスクの `value` には、環境変数または文字列を用いることができます。 -### 文字列をマスクするサンプル +### Example: Masking a string ログに `"Mona The Octocat"` を出力すると、`"***"` が表示されます。 -```bash +{% bash %} + +```bash{:copy} echo "::add-mask::Mona The Octocat" ``` -### 環境変数をマスクするサンプル +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::add-mask::Mona The Octocat" +``` + +{% endpowershell %} + +### Example: Masking an environment variable 変数 `MY_NAME` または値 `"Mona The Octocat"` をログに出力すると、`"Mona The Octocat"` の代わりに `"***"` が表示されます。 -```bash -MY_NAME="Mona The Octocat" -echo "::add-mask::$MY_NAME" +{% bash %} + +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: bash-version + run: echo "::add-mask::$MY_NAME" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: powershell-version + run: Write-Output "::add-mask::$env:MY_NAME" +``` + +{% endpowershell %} + ## ワークフローコマンドの停止と開始 -`::stop-commands::{endtoken}` - ワークフローコマンドの処理を停止します。 この特殊コマンドを使うと、意図せずワークフローコマンドを実行することなくいかなるログも取れます。 たとえば、コメントがあるスクリプト全体を出力するためにログ取得を停止できます。 +```{:copy} +::stop-commands::{endtoken} +``` + To stop the processing of workflow commands, pass a unique token to `stop-commands`. To resume processing workflow commands, pass the same token that you used to stop workflow commands. {% warning %} -**Warning:** Make sure the token you're using is randomly generated and unique for each run. As demonstrated in the example below, you can generate a unique hash of your `github.token` for each run. +**Warning:** Make sure the token you're using is randomly generated and unique for each run. {% endwarning %} -``` +```{:copy} ::{endtoken}:: ``` -### Example stopping and starting workflow commands +### Example: Stopping and starting workflow commands + +{% bash %} {% raw %} -```yaml +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest steps: - - name: disable workflow commands + - name: Disable workflow commands run: | - echo '::warning:: this is a warning' - echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`" - echo '::warning:: this will NOT be a warning' - echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::" - echo '::warning:: this is a warning again' + echo '::warning:: This is a warning message, to demonstrate that commands are being processed.' + stopMarker=$(uuidgen) + echo "::stop-commands::$stopMarker" + echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + echo "::$stopMarker::" + echo '::warning:: This is a warning again, because stop-commands has been turned off.' +``` +{% endraw %} + +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: Disable workflow commands + run: | + Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.' + $stopMarker = New-Guid + Write-Output "::stop-commands::$stopMarker" + Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + Write-Output "::$stopMarker::" + Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.' ``` {% endraw %} +{% endpowershell %} + ## Echoing command outputs -``` +Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. + +```{:copy} ::echo::on ::echo::off ``` -Enables or disables echoing of workflow commands. For example, if you use the `set-output` command in a workflow, it sets an output parameter but the workflow run's log does not show the command itself. If you enable command echoing, then the log shows the command, such as `::set-output name={name}::{value}`. - Command echoing is disabled by default. However, a workflow command is echoed if there are any errors processing the command. The `add-mask`, `debug`, `warning`, and `error` commands do not support echoing because their outputs are already echoed to the log. You can also enable command echoing globally by turning on step debug logging using the `ACTIONS_STEP_DEBUG` secret. For more information, see "[Enabling debug logging](/actions/managing-workflow-runs/enabling-debug-logging)". In contrast, the `echo` workflow command lets you enable command echoing at a more granular level, rather than enabling it for every workflow in a repository. -### Example toggling command echoing +### Example: Toggling command echoing -```yaml +{% bash %} + +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest @@ -279,9 +464,29 @@ jobs: echo '::set-output name=action_echo::disabled' ``` -The step above prints the following lines to the log: +{% endbash %} +{% powershell %} + +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: toggle workflow command echoing + run: | + write-output "::set-output name=action_echo::disabled" + write-output "::echo::on" + write-output "::set-output name=action_echo::enabled" + write-output "::echo::off" + write-output "::set-output name=action_echo::disabled" ``` + +{% endpowershell %} + +The example above prints the following lines to the log: + +```{:copy} ::set-output name=action_echo::enabled ::echo::off ``` @@ -298,13 +503,13 @@ Only the second `set-output` and `echo` workflow commands are included in the lo 以下の例はJavaScriptを使って`save-state`コマンドを実行します。 結果の環境変数は`STATE_processID`という名前になり、`12345`という値を持ちます。 -``` javascript +```javascript{:copy} console.log('::save-state name=processID::12345') ``` そして、`STATE_processID`変数は`main`アクションの下で実行されるクリーンアップスクリプトからのみ利用できます。 以下の例は`main`を実行し、JavaScriptを使って環境変数`STATE_processID`に割り当てられた値を表示します。 -``` javascript +```javascript{:copy} console.log("The running PID from the main action is: " + process.env.STATE_processID); ``` @@ -312,37 +517,70 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro ワークフローの実行中に、ランナーは特定のアクションを実行する際に使用できる一時ファイルを生成します。 これらのファイルへのパスは、環境変数を介して公開されます。 コマンドを適切に処理するには、これらのファイルに書き込むときに UTF-8 エンコーディングを使用する必要があります。 複数のコマンドを、改行で区切って同じファイルに書き込むことができます。 -{% warning %} +{% powershell %} -**Warning:** On Windows, legacy PowerShell (`shell: powershell`) does not use UTF-8 by default. +{% note %} -When using `shell: powershell`, you must specify UTF-8 encoding. 例: +**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. 例: -```yaml +```yaml{:copy} jobs: legacy-powershell-example: - uses: windows-2019 + runs-on: windows-latest steps: - shell: powershell - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append + run: | + "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. +PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. 例: -{% endwarning %} +```yaml{:copy} +jobs: + powershell-core-example: + runs-on: windows-latest + steps: + - shell: pwsh + run: | + "mypath" >> $env:GITHUB_PATH +``` + +{% endnote %} + +{% endpowershell %} ## 環境変数の設定 -``` bash +{% bash %} + +```bash{:copy} echo "{environment_variable_name}={value}" >> $GITHUB_ENV ``` +{% endbash %} + +{% powershell %} + +- Using PowerShell version 6 and higher: +```pwsh{:copy} +"{environment_variable_name}={value}" >> $env:GITHUB_ENV +``` + +- Using PowerShell version 5.1 and below: +```powershell{:copy} +"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append +``` + +{% endpowershell %} + You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. The names of environment variables are case-sensitive, and you can include punctuation. 詳しい情報については、「[環境変数](/actions/learn-github-actions/environment-variables)」を参照してください。 ### サンプル +{% bash %} + {% raw %} -``` +```yaml{:copy} steps: - name: Set the value id: step_one @@ -355,11 +593,31 @@ steps: ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +steps: + - name: Set the value + id: step_one + run: | + "action_state=yellow" >> $env:GITHUB_ENV + - name: Use the value + id: step_two + run: | + Write-Output "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} + +{% endpowershell %} + ### 複数行の文字列 複数行の文字列の場合、次の構文で区切り文字を使用できます。 -``` +```{:copy} {name}<<{delimiter} {value} {delimiter} @@ -367,29 +625,75 @@ steps: #### サンプル -この例では、区切り文字として `EOF` を使用し、`JSON_RESPONSE` 環境変数を cURL レスポンスの値に設定します。 -```yaml +This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response. + +{% bash %} + +```yaml{:copy} steps: - - name: Set the value + - name: Set the value in bash id: step_one run: | echo 'JSON_RESPONSE<> $GITHUB_ENV - curl https://httpbin.org/json >> $GITHUB_ENV + curl https://example.lab >> $GITHUB_ENV echo 'EOF' >> $GITHUB_ENV ``` -## システムパスの追加 +{% endbash %} -``` bash -echo "{path}" >> $GITHUB_PATH +{% powershell %} + +```yaml{:copy} +steps: + - name: Set the value in pwsh + id: step_one + run: | + "JSON_RESPONSE<> $env:GITHUB_ENV + (Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV + "EOF" >> $env:GITHUB_ENV + shell: pwsh ``` +{% endpowershell %} + +## システムパスの追加 + Prepends a directory to the system `PATH` variable and automatically makes it available to all subsequent actions in the current job; the currently running action cannot access the updated path variable. ジョブに現在定義されているパスを見るには、ステップもしくはアクション中で`echo "$PATH"`を使うことができます。 +{% bash %} + +```bash{:copy} +echo "{path}" >> $GITHUB_PATH +``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +"{path}" >> $env:GITHUB_PATH +``` + +{% endpowershell %} + ### サンプル この例は、ユーザの`$HOME/.local/bin`ディレクトリを`PATH`に追加する方法を示しています。 -``` bash +{% bash %} + +```bash{:copy} echo "$HOME/.local/bin" >> $GITHUB_PATH ``` + +{% endbash %} + + +This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`: + +{% powershell %} + +```pwsh{:copy} +"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH +``` + +{% endpowershell %} diff --git a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index 3823b294b3..232b2ac264 100644 --- a/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/ja-JP/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -17,7 +17,11 @@ topics: ハードコードされたIPアドレスの代わりにホスト名を設定すれば、ユーザやクライアントソフトウェアに影響を与えることなく{% data variables.product.product_location %}を動作させる物理ハードウェアを変更できるようになります。 -{% data variables.enterprise.management_console %} のホスト名の設定は、適切な完全修飾ドメイン名 (FQDN) に設定して、インターネット上または内部ネットワーク内で解決できるようにしてください。 たとえば、ホスト名の設定は `github.companyname.com` であるかもしれません。 また、選択したホスト名に対して Subdomain Isolation を有効にして、いくつかのクロスサイトスクリプティングスタイルの脆弱性を軽減することもおすすめします。 ホスト名の設定に関する詳しい情報については、[HTTP RFC の Section 2.1](https://tools.ietf.org/html/rfc1123#section-2) を参照してください。 +{% data variables.enterprise.management_console %} のホスト名の設定は、適切な完全修飾ドメイン名 (FQDN) に設定して、インターネット上または内部ネットワーク内で解決できるようにしてください。 For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. + +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. 詳しい情報については"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)"を参照してください。 + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} @@ -29,4 +33,4 @@ topics: {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -ホスト名を設定したら、{% data variables.product.product_location %}のSubdomain Isolationを有効化することをお勧めします。 詳しい情報については"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)"を参照してください。 +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. 詳しい情報については"[Subdomain Isolationの有効化](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)"を参照してください。 diff --git a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index 0e5fbe4540..e773ad9a19 100644 --- a/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/ja-JP/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -19,25 +19,32 @@ shortTitle: Initiate failover to appliance {% data reusables.enterprise_installation.promoting-a-replica %} -1. アプライアンスを切り替える前にレプリケーションを終了できるようにするには、プライマリアプライアンスをメンテナンスモードにします。 - - Management Console を使用するには、「[メンテナンスモードの有効化とスケジュール設定](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)」を参照してください。 - - `ghe-maintenance -s` コマンドも使用できます。 +1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode. + + - Put the appliance into maintenance mode. + + - Management Console を使用するには、「[メンテナンスモードの有効化とスケジュール設定](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)」を参照してください。 + + - `ghe-maintenance -s` コマンドも使用できます。 + ```shell + $ ghe-maintenance -s + ``` + + - When the number of active Git operations, MySQL queries, and Resque jobs reaches zero, wait 30 seconds. + + {% note %} + + **Note:** Nomad will always have jobs running, even in maintenance mode, so you can safely ignore these jobs. + + {% endnote %} + + - すべてのレプリケーションチャネルが `OK` を報告することを確認するには、`ghe-repl-status -vv` コマンドを使用します。 + ```shell - $ ghe-maintenance -s + $ ghe-repl-status -vv ``` -2. When the number of active Git operations, MySQL queries, and Resque jobs reaches zero, wait 30 seconds. - {% note %} - - **Note:** Nomad will always have jobs running, even in maintenance mode, so you can safely ignore these jobs. - - {% endnote %} - -3. すべてのレプリケーションチャネルが `OK` を報告することを確認するには、`ghe-repl-status -vv` コマンドを使用します。 - ```shell - $ ghe-repl-status -vv - ``` -4. レプリケーションを停止してレプリカアプライアンスをプライマリステータスに昇格するには、`ghe-repl-encourage` コマンドを使用します。 到達可能であれば、これによりプライマリノードも自動的にメンテナンスノードになります。 +4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. 到達可能であれば、これによりプライマリノードも自動的にメンテナンスノードになります。 ```shell $ ghe-repl-promote ``` diff --git a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index 7200ff6386..8ac17e95e2 100644 --- a/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/ja-JP/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -25,7 +25,7 @@ topics: 移行においては、すべての事項についてリポジトリが中心になります。 リポジトリに関係するほとんどのデータは移行できます。 たとえば Organization 内のリポジトリは、リポジトリ*および*その Organization、またそのリポジトリに関連付けられているユーザ、Team、Issue、プルリクエストのすべてを移行します。 -以下の表の項目はレポジトリと共に移行できます。 このデータの移行リストに記載されていない項目はどれも移行できません。 +以下の表の項目はレポジトリと共に移行できます。 Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} diff --git a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index bbdaa9119f..4a430ae839 100644 --- a/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/ja-JP/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -25,7 +25,7 @@ shortTitle: Check for existing SSH key # .ssh ディレクトリ内のファイルを一覧表示する（存在する場合） ``` -3. ディレクトリの一覧から、公開 SSH キーをすでに持っているか確認します。 By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% elsif fpt or ghes %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. +3. ディレクトリの一覧から、公開 SSH キーをすでに持っているか確認します。 By default, the {% ifversion ghae %}filename of a supported public key for {% data variables.product.product_name %} is *id_rsa.pub*.{% else %}filenames of supported public keys for {% data variables.product.product_name %} are one of the following. - *id_rsa.pub* - *id_ecdsa.pub* - *id_ed25519.pub*{% endif %} diff --git a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index e27c854f3e..dfa64c1eb1 100644 --- a/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/ja-JP/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -33,7 +33,7 @@ $ ssh -T -p 443 git@ssh.github.com If you are able to SSH into `git@ssh.{% data variables.command_line.backticks %}` over port 443, you can override your SSH settings to force any connection to {% data variables.product.product_location %} to run through that server and port. -To set this in your SSH confifguration file, edit the file at `~/.ssh/config`, and add this section: +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} diff --git a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md index f49db4795c..9549eaaae2 100644 --- a/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/ja-JP/content/code-security/secret-scanning/about-secret-scanning.md @@ -31,9 +31,9 @@ If your project communicates with an external service, you might use a token or {% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is available on {% data variables.product.prodname_dotcom_the_website %} in two forms: -1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relvant partner. +1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relevant partner. -2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scannng partners, by other service providers, or defined by your organization are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. +2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scanning partners, by other service providers, or defined by your organization, are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. {% endif %} Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %} diff --git a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md index 4f546dfef5..4300129c0d 100644 --- a/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md +++ b/translations/ja-JP/content/get-started/quickstart/fork-a-repo.md @@ -22,7 +22,7 @@ topics: ## フォークについて -一般的にフォークは、他のユーザのプロジェクトへの変更を提案するため、あるいは他のユーザのプロジェクトを自分のアイディアの出発点として活用するために使用します。 You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." +Most commonly, forks are used to either propose changes to someone else's project to which you don't have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." ### 他のユーザのプロジェクトへの変更を提案する diff --git a/translations/ja-JP/content/get-started/quickstart/hello-world.md b/translations/ja-JP/content/get-started/quickstart/hello-world.md index 9cf7699063..ce26597435 100644 --- a/translations/ja-JP/content/get-started/quickstart/hello-world.md +++ b/translations/ja-JP/content/get-started/quickstart/hello-world.md @@ -87,7 +87,7 @@ When you created a new branch in the previous step, {% data variables.product.pr You can make and save changes to the files in your repository. On {% data variables.product.product_name %}, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes so that other contributors can understand what you’ve done and why. 1. Under the `readme-edits` branch you created, click the _README.md_ file. -2. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file. +2. {% octicon "pencil" aria-label="The edit icon" %}をクリックしてファイルを編集してください。 3. In the editor, write a bit about yourself. Try using different Markdown elements. 4. In the **Commit changes** box, write a commit message that describes your changes. 5. **[Commit changes]** をクリックしてください。 diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md index 8356b987bd..817790d578 100644 --- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages.md @@ -31,12 +31,12 @@ shortTitle: カスタムドメインのトラブルシューティング ## DNS の設定ミス -デフォルトドメインをカスタムドメインにポイントすることに問題がある場合は、DNS プロバイダに連絡してください。 +サイトのデフォルトドメインをカスタムドメインを指すようにすることに問題がある場合は、DNS プロバイダに連絡してください。 -You can also use one of the following methods to test whether your custom domain's DNS records are configured correctly: +カスタムドメインのDNSレコードが正しく設定されているかをテストするには、以下の方法のいずれかを使うこともできます。 -- A CLI tool such as `dig`. For more information, see "[Managing a custom domain for your {% data variables.product.prodname_pages %} site](/articles/managing-a-custom-domain-for-your-github-pages-site)". -- An online DNS lookup tool. +- `dig`のようなCLIツール。 詳しい情報については「[{% data variables.product.prodname_pages %}サイトのカスタムドメインの管理](/articles/managing-a-custom-domain-for-your-github-pages-site)」を参照してください。 +- オンラインのDNSルックアップツール。 ## サポートされていないカスタムドメイン名 diff --git a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md index d8e5302de3..b61509fd71 100644 --- a/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md +++ b/translations/ja-JP/content/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages.md @@ -1,45 +1,45 @@ --- -title: Verifying your custom domain for GitHub Pages -intro: You can increase the security of your custom domain and avoid takeover attacks by verifying your domain. +title: GitHub Pagesのカスタムドメインの検証 +intro: ドメインを検証することで、カスタムドメインのセキュリティを高め、乗っ取り攻撃を回避できます。 product: '{% data reusables.gated-features.pages %}' versions: fpt: '*' ghec: '*' topics: - Pages -shortTitle: Verify a custom domain +shortTitle: カスタムドメインの検証 --- -## About domain verification for GitHub Pages +## GitHub Pagesのドメイン検証について -When you verify your custom domain for your user account or organization, only repositories owned by your user account or organization may be used to publish a {% data variables.product.prodname_pages %} site to the verified custom domain or the domain's immediate subdomains. +自分のユーザアカウントあるいはOrganizationのカスタムドメインを検証すると、その検証されたカスタムドメインもしくはその直接のサブドメインに{% data variables.product.prodname_pages %}サイトを公開できるのは、自分のユーザアカウントあるいはOrganizationが所有するリポジトリだけになります。 -Verifying your domain stops other GitHub users from taking over your custom domain and using it to publish their own {% data variables.product.prodname_pages %} site. Domain takeovers can happen when you delete your repository, when your billing plan is downgraded, or after any other change which unlinks the custom domain or disables {% data variables.product.prodname_pages %} while the domain remains configured for {% data variables.product.prodname_pages %} and is not verified. +ドメインを検証すると、他のGitHubユーザがそのカスタムドメインを乗っ取り、そのユーザ自身の{% data variables.product.prodname_pages %}サイトの公開に使うことを止められます。 ドメインの乗っ取りは、{% data variables.product.prodname_pages %}用にドメインを残したままで検証せず、あなたが自分のリポジトリを削除したとき、支払いプランをダウングレードしたとき、あるいはカスタムドメインのリンクを解除するその他の変更や{% data variables.product.prodname_pages %}を無効化した後に生じます。 -When you verify a domain, any immediate subdomains are also included in the verification. For example, if the `github.com` custom domain is verified, `docs.github.com`, `support.github.com`, and any other immediate subdomains will also be protected from takeovers. +ドメインを検証すると、直接のサブドメインもその検証に含まれます。 たとえば、`github.com`というカスタムドメインが検証されると、`docs.github.com`、`support.github.com`あるいはその他の直接のサブドメインも、乗っ取りから保護されることになります。 -It's also possible to verify a domain for your organization{% ifversion ghec %} or enterprise{% endif %}, which displays a "Verified" badge on the organization {% ifversion ghec %}or enterprise{% endif %} profile{% ifversion ghec %} and, on {% data variables.product.prodname_ghe_cloud %}, allows you to restrict notifications to email addresses using the verified domain{% endif %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization){% ifversion ghec %}" and "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise){% endif %}." +Organization{% ifversion ghec %}あるいはEnterprise{% endif %}のドメインを検証することもできます。そうすると、「検証済み」バッジがOrganization{% ifversion ghec %}もしくはEnterprise{% endif %}のプロフィールに表示され{% ifversion ghec %}、{% data variables.product.prodname_ghe_cloud %}では検証済みドメインを使ってメールアドレスへの通知を制限できるようになり{% endif %}ます。 詳しい情報については「[Organizationのドメインの検証あるいは承認](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)」{% ifversion ghec %}及び「[Enterpriseのドメインの検証あるいは承認](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)」{% endif %}を参照してください。 -## Verifying a domain for your user site +## ユーザサイトのドメインの検証 {% data reusables.user-settings.access_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The pages icon" %} Pages**. +1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "browser" aria-label="The pages icon" %} Pages**をクリックしてください。 {% data reusables.pages.settings-verify-domain-setup %} -1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `USERNAME` with your username and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. +1. DNS設定が変更されるまで待ちます。これはすぐに行われることも、最大で24時間かかることもあります。 DNS設定への変更は、コマンドラインで`dig`コマンドを実行して確認できます。 以下のコマンドで、`USERNAME`を自分のユーザ名に、`example.com`を検証しているドメインに置き換えてください。 DNS設定が更新されていれば、出力中に新しいTXTレコードが表示されます。 ``` dig _github-pages-challenge-USERNAME.example.com +nostats +nocomments +nocmd TXT ``` {% data reusables.pages.settings-verify-domain-confirm %} -## Verifying a domain for your organization site +## Organizationのサイトのドメインの検証 -Organization owners can verify custom domains for their organization. +Organizationのオーナーは、自分のOrganizatinのカスタムドメインを検証できます。 {% data reusables.profile.access_org %} {% data reusables.profile.org_settings %} -1. In the "Code, planning, and automation" section of the sidebar, click **{% octicon "browser" aria-label="The browser icon" %} Pages**. +1. サイドバーの"Code, planning, and automation（コード、計画、自動化）"のセクションで、**{% octicon "browser" aria-label="The browser icon" %} Pages**をクリックしてください。 {% data reusables.pages.settings-verify-domain-setup %} -1. Wait for your DNS configuration to change, this may be immediate or take up to 24 hours. You can confirm the change to your DNS configuration by running the `dig` command on the command line. In the command below, replace `ORGANIZATION` with the name of your organization and `example.com` with the domain you're verifying. If your DNS configuration has updated, you should see your new TXT record in the output. +1. DNS設定が変更されるまで待ちます。これはすぐに行われることも、最大で24時間かかることもあります。 DNS設定への変更は、コマンドラインで`dig`コマンドを実行して確認できます。 以下のコマンドで、`ORGANIZATION`を自分のOrganization名に、`example.com`を検証しているドメインに置き換えてください。 DNS設定が更新されていれば、出力中に新しいTXTレコードが表示されます。 ``` dig _github-pages-challenge-ORGANIZATION.example.com +nostats +nocomments +nocmd TXT ``` diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md index 47027309e8..e6d3affdbb 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser.md @@ -39,7 +39,7 @@ Jekyll テーマをリポジトリに手動で追加したことがある場合 4. ページ上部の、選択したいテーマをクリックし、[**Select theme**] をクリックします。 ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png) 5. サイトの *README.md* ファイルを編集するようプロンプトが表示される場合があります。 - ファイルを後で編集する場合、[**Cancel**] をクリックします。 ![ファイルを編集する際の [Cancel] リンク](/assets/images/help/pages/cancel-edit.png) - - To edit the file now, see "[Editing files](/repositories/working-with-files/managing-files/editing-files)." + - すぐにファイルを編集するには、「[Editing files（ファイルの編集）](/repositories/working-with-files/managing-files/editing-files)」を参照してください。 選択したテーマは、リポジトリの Markdown ファイルに自動的に適用されます。 テーマをリポジトリの HTML ファイルに適用するには、各ファイルのレイアウトを指定する YAML front matter を追加する必要があります。 詳しい情報については、Jekyll サイトの「[Front Matter](https://jekyllrb.com/docs/front-matter/)」を参照してください。 diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md index a7f9575a98..5e931e4862 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md @@ -1,6 +1,6 @@ --- -title: GitHub Pages サイトの公開元を設定する -intro: '{% data variables.product.prodname_pages %} サイトでデフォルトの公開元を使用している場合、サイトは自動的に公開されます。 You can also choose to publish your site from a different branch or folder.' +title: Configuring a publishing source for your GitHub Pages site +intro: 'If you use the default publishing source for your {% data variables.product.prodname_pages %} site, your site will publish automatically. You can also choose to publish your site from a different branch or folder.' redirect_from: - /articles/configuring-a-publishing-source-for-github-pages - /articles/configuring-a-publishing-source-for-your-github-pages-site @@ -14,33 +14,36 @@ versions: ghec: '*' topics: - Pages -shortTitle: 公開ソースの設定 +shortTitle: Configure publishing source --- -公開元に関する詳しい情報については、「[{% data variables.product.prodname_pages %} について](/articles/about-github-pages#publishing-sources-for-github-pages-sites)」を参照してください。 +For more information about publishing sources, see "[About {% data variables.product.prodname_pages %}](/articles/about-github-pages#publishing-sources-for-github-pages-sites)." -## 公開元を選択する +## Choosing a publishing source Before you configure a publishing source, make sure the branch you want to use as your publishing source already exists in your repository. {% data reusables.pages.navigate-site-repo %} {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -3. [{% data variables.product.prodname_pages %}] で、[**None**] または [**Branch**] ドロップダウンメニューから公開元を選択します。 ![公開元を選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-drop-down.png) -4. 必要に応じて、ドロップダウンメニューで発行元のフォルダを選択します。 ![公開元のフォルダを選択するドロップダウンメニュー](/assets/images/help/pages/publishing-source-folder-drop-down.png) -5. [**Save**] をクリックします。 ![公開元の設定への変更を保存するボタン](/assets/images/help/pages/publishing-source-save.png) +3. Under "{% data variables.product.prodname_pages %}", use the **None** or **Branch** drop-down menu and select a publishing source. + ![Drop-down menu to select a publishing source](/assets/images/help/pages/publishing-source-drop-down.png) +4. Optionally, use the drop-down menu to select a folder for your publishing source. + ![Drop-down menu to select a folder for publishing source](/assets/images/help/pages/publishing-source-folder-drop-down.png) +5. Click **Save**. + ![Button to save changes to publishing source settings](/assets/images/help/pages/publishing-source-save.png) -## {% data variables.product.prodname_pages %} サイトの公開に関するトラブルシューティング +## Troubleshooting publishing problems with your {% data variables.product.prodname_pages %} site {% data reusables.pages.admin-must-push %} -If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. 詳細については、「[{% data variables.product.prodname_pages %} サイトの Jekyll ビルドエラーに関するトラブルシューティング](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)」を参照してください。 +If you choose the `docs` folder on any branch as your publishing source, then later remove the `/docs` folder from that branch in your repository, your site won't build and you'll get a page build error message for a missing `/docs` folder. For more information, see "[Troubleshooting Jekyll build errors for {% data variables.product.prodname_pages %} sites](/articles/troubleshooting-jekyll-build-errors-for-github-pages-sites#missing-docs-folder)." -{% ifversion fpt %} +{% ifversion fpt %} Your {% data variables.product.prodname_pages %} site will always be deployed with a {% data variables.product.prodname_actions %} workflow run, even if you've configured your {% data variables.product.prodname_pages %} site to be built using a different CI tool. Most external CI workflows "deploy" to GitHub Pages by committing the build output to the `gh-pages` branch of the repository, and typically include a `.nojekyll` file. When this happens, the {% data variables.product.prodname_actions %} worfklow will detect the state that the branch does not need a build step, and will execute only the steps necessary to deploy the site to {% data variables.product.prodname_pages %} servers. -To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. 詳しい情報については、「[ワークフロー実行の履歴を表示する](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)」を参照してください。 For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." +To find potential errors with either the build or deployment, you can check the workflow run for your {% data variables.product.prodname_pages %} site by reviewing your repository's workflow runs. For more information, see "[Viewing workflow run history](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)." For more information about how to re-run the workflow in case of an error, see "[Re-running workflows and jobs](/actions/managing-workflow-runs/re-running-workflows-and-jobs)." {% note %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md index f70d1267c2..b311a78103 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md @@ -45,7 +45,7 @@ shortTitle: GitHub Pagesのサイトの作成 {% tip %} - **Tip:** If `index.html` is present, this will be used instead of `index.md`. If neither `index.html` nor `index.md` are present, `README.md` will be used. + **参考:** `index.html`があるなら、`index.md`の代わりに利用されます。 `index.html`も`index.md`もないなら、`README.md`が使われます。 {% endtip %} {% data reusables.pages.configure-publishing-source %} diff --git a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md index 38a7076147..3da106918d 100644 --- a/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md +++ b/translations/ja-JP/content/pages/getting-started-with-github-pages/securing-your-github-pages-site-with-https.md @@ -25,7 +25,7 @@ shortTitle: HTTPSでのサイトの保護 {% note %} -**Note:** RFC3280 states that the maximum length of the common name should be 64 characters. Therefore, the entire domain name of your {% data variables.product.prodname_pages %} site must be less than 64 characters long for a certificate to be successfully created. +**ノート:** RFC3280は、コモンネームの最大長は64文字でなければならないとしています。 したがって、証明書が正常に作成されるようにするには、{% data variables.product.prodname_pages %}サイトのドメイン名全体の長さは64文字未満でなければなりません。 {% endnote %} @@ -36,11 +36,11 @@ shortTitle: HTTPSでのサイトの保護 {% data reusables.pages.sidebar-pages %} 3. [{% data variables.product.prodname_pages %}] で、[**Enforce HTTPS**] を選択します。 ![[Enforce HTTPS] チェックボックス](/assets/images/help/pages/enforce-https-checkbox.png) -## Troubleshooting certificate provisioning ("Certificate not yet created" error") +## 証明書プロビジョニングのトラブルシューティング（"Certificate not yet created" error"） -When you set or change your custom domain in the Pages settings, an automatic DNS check begins. This check determines if your DNS settings are configured to allow {% data variables.product.prodname_dotcom %} to obtain a certificate automatically. If the check is successful, {% data variables.product.prodname_dotcom %} queues a job to request a TLS certificate from [Let's Encrypt](https://letsencrypt.org/). On receiving a valid certificate, {% data variables.product.prodname_dotcom %} automatically uploads it to the servers that handle TLS termination for Pages. When this process completes successfully, a check mark is displayed beside your custom domain name. +Pagesの設定でカスタムドメインを設定もしくは変更した場合、自動DNSチェックが開始されます。 このチェックは、DNS設定が{% data variables.product.prodname_dotcom %}による自動的な証明書の取得を許可するように設定されているかを判断します。 このチェックに成功すると、{% data variables.product.prodname_dotcom %}は[Let's Encrypt](https://letsencrypt.org/)にTLS証明書をリクエストするジョブをキューイングします。 有効な証明書を受信すると、{% data variables.product.prodname_dotcom %}は自動的にそれをPagesのTLSターミネーションを処理するサーバーにアップロードします。 このプロセスが正常に終了すると、カスタムドメイン名の横にチェックマークが表示されます。 -The process may take some time. If the process has not completed several minutes after you clicked **Save**, try clicking **Remove** next to your custom domain name. Retype the domain name and click **Save** again. This will cancel and restart the provisioning process. +このプロセスには多少の時間がかかることがあります。 **Save（保存）**をクリックしてから数分経ってもこのプロセスが終了しないなら、カスタムドメイン名の隣にある**Remove（削除）**をクリックしてみてください。 ドメイン名を再入力し、**Save（保存）**をもう一度クリックしてください。 これでプロビジョニングのプロセスがキャンセルされ、再起動されます。 ## 混在したコンテンツの問題を解決する diff --git a/translations/ja-JP/content/pages/index.md b/translations/ja-JP/content/pages/index.md index 4c6930bb35..44ce4c4065 100644 --- a/translations/ja-JP/content/pages/index.md +++ b/translations/ja-JP/content/pages/index.md @@ -1,7 +1,7 @@ --- title: GitHub Pagesのドキュメンテーション shortTitle: GitHub Pages -intro: 'You can create a website directly from a repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}.' +intro: '{% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}上のリポジトリから直接Webサイトを作成できます。' redirect_from: - /categories/20/articles - /categories/95/articles diff --git a/translations/ja-JP/content/pages/quickstart.md b/translations/ja-JP/content/pages/quickstart.md index 5fd2d42e5c..34ebe0cad1 100644 --- a/translations/ja-JP/content/pages/quickstart.md +++ b/translations/ja-JP/content/pages/quickstart.md @@ -1,6 +1,6 @@ --- -title: Quickstart for GitHub Pages -intro: 'You can use {% data variables.product.prodname_pages %} to showcase some open source projects, host a blog, or even share your résumé. This guide will help get you started on creating your next website.' +title: GitHub Pagesのクイックスタート +intro: '{% data variables.product.prodname_pages %}を使って、オープンソースプロジェクトを紹介したり、ブログをホストしたり、履歴書を共有することさえもできます。 このガイドは、次のWebサイトを作成し始めるための役に立ちます。' allowTitleToDifferFromFilename: true versions: fpt: '*' @@ -16,30 +16,30 @@ product: '{% data reusables.gated-features.pages %}' ## はじめに -{% data variables.product.prodname_pages %} are public webpages hosted and published through {% data variables.product.product_name %}. The quickest way to get up and running is by using the Jekyll Theme Chooser to load a pre-made theme. You can then modify your {% data variables.product.prodname_pages %}' content and style. +{% data variables.product.prodname_pages %}は、{% data variables.product.product_name %}を通じてホストされ、公開されるパブリックなWebページです。 立ち上げて実行するための最速の方法は、Jekyll テーマ選択画面を使って事前作成されたテーマをロードすることです。 その後、{% data variables.product.prodname_pages %}のコンテンツやスタイルを変更できます。 -This guide will lead you through creating a user site at `username.github.io`. +このガイドは、`username.github.io`でのユーザサイトの作成をご案内します。 -## Creating your website +## Webサイトの作成 {% data reusables.repositories.create_new %} -1. Enter `username.github.io` as the repository name. Replace `username` with your {% data variables.product.prodname_dotcom %} username. For example, if your username is `octocat`, the repository name should be `octocat.github.io`. ![Repository name field](/assets/images/help/pages/create-repository-name-pages.png) +1. リポジトリ名として`username.github.io`を入力してください。 `username`を自分の{% data variables.product.prodname_dotcom %}ユーザ名で置き換えてください。 たとえば、ユーザ名が`octocat`なら、リポジトリ名は`octocat.github.io`となります。 ![リポジトリ名フィールド](/assets/images/help/pages/create-repository-name-pages.png) {% data reusables.repositories.sidebar-settings %} {% data reusables.pages.sidebar-pages %} -1. Click **Choose a theme**. ![[Choose a theme] ボタン](/assets/images/help/pages/choose-theme.png) -2. The Theme Chooser will open. Browse the available themes, then click **Select theme** to select a theme. It's easy to change your theme later, so if you're not sure, just choose one for now. ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png) -3. After you select a theme, your repository's `README.md` file will open in the file editor. The `README.md` file is where you will write the content for your site. You can edit the file or keep the default content for now. -4. When you are done editing the file, click **Commit changes**. -5. Visit `username.github.io` to view your new website. **メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。 +1. **Choose a theme（テーマの選択）**をクリックしてください。 ![[Choose a theme] ボタン](/assets/images/help/pages/choose-theme.png) +2. テーマ選択画面が開きます。 利用可能なテーマをブラウズし、**Select theme（テーマの選択）**をクリックしてテーマを選択してください。 後でテーマを変更することも容易なので、はっきりしない場合はとりあえずどれか1つを選択しておいてください。 ![テーマのオプションおよび [Select theme] ボタン](/assets/images/help/pages/select-theme.png) +3. テーマとを選択すると、ファイルエディタで`README.md`ファイルが開かれます。 `README.md`ファイルは、サイトの内容を書くところです。 このファイルを編集することも、あるいはとりあえずデフォルトの内容をそのままにしておくこともできます。 +4. ファイルの編集が終わったら、**Commit changes（変更をコミット）**をクリックしてください。 +5. `username.github.io`にアクセスして、新しいWebサイトを見てみてください。 **メモ:** サイトに対する変更は、その変更を{% data variables.product.product_name %}にプッシュしてから公開されるまでに、最大20分かかることがあります。 -## Changing the title and description +## タイトルと説明の変更 -By default, the title of your site is `username.github.io`. You can change the title by editing the `_config.yml` file in your repository. You can also add a description for your site. +デフォルトでは、サイトのタイトルは`username.github.io`です。 リポジトリ内の`_config.yml`ファイルを編集すれば、タイトルを変更できます。 サイトの説明を追加することもできます。 -1. Click the **Code** tab of your repository. -1. In the file list, click `_config.yml` to open the file. -1. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file. -1. The `_config.yml` file already contains a line that specifies the theme for your site. Add a new line with `title:` followed by the title you want. Add a new line with `description:` followed by the description you want. 例: +1. リポジトリの**Code（コード）**タブをクリックしてください。 +1. ファイルリスト中で`_config.yml`をクリックしてオープンしてください。 +1. {% octicon "pencil" aria-label="The edit icon" %}をクリックしてファイルを編集してください。 +1. `_config.yml`には、既にサイトのテーマを指定する行が含まれています。 新しい行として`title:`の後に指定したいタイトルを続けてください。 新しい行を追加して`description:`の後に指定したい説明を続けてください。 例: ```yaml theme: jekyll-theme-minimal @@ -47,10 +47,10 @@ By default, the title of your site is `username.github.io`. You can change the t description: Bookmark this to keep an eye on my project updates! ``` -1. When you are done editing the file, click **Commit changes**. +1. ファイルの編集を終えたら、**Commit changes（変更をコミット）**をクリックしてください。 ## 次のステップ -For more information about how to add additional pages to your site, see "[Adding content to your GitHub Pages site using Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites)." +サイトへのページの追加方法に関する詳しい情報については「[Jekyllを使ったGitHub Pagesサイトへのコンテンツの追加](/pages/setting-up-a-github-pages-site-with-jekyll/adding-content-to-your-github-pages-site-using-jekyll#about-content-in-jekyll-sites)」を参照してください。 -For more information about setting up a {% data variables.product.prodname_pages %} site with Jekyll, see "[About GitHub Pages and Jekyll](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)." +Jekyllと合わせて{% data variables.product.prodname_pages %}をセットアップすることに関する詳しい情報については「[GitHub PagesとJekyllについて](/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll)」を参照してください。 diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md index a30b8d437d..5137b5456f 100644 --- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md @@ -68,9 +68,9 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを サイトを `gh-pages` ブランチから公開する場合には、`gh-pages` ブランチを作成してチェックアウトします。 ```shell $ git checkout --orphan gh-pages - # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch + # 履歴やコンテンツなしでgh-pagesという新しいブランチを作成、gh-pagesブランチに切り替え $ git rm -rf - # Removes the contents from your default branch from the working directory + # ワーキングディレクトリでデフォルトブランチからコンテンツを削除 ``` 1. 新しい Jekyll サイトを作成するには、`jekyll new` コマンドを使用します。 ```shell @@ -89,7 +89,7 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを 正しいバージョンの Jekyll は、`github-pages` gem の依存関係としてインストールされます。 1. Gemfile を保存して閉じます。 -1. From the command line, run `bundle install`. +1. コマンドラインから`bundle install`を実行 1. あるいは、`_config.yml`ファイルに必要な編集を加えてください。 これは、リポジトリがサブディレクトリでホストされている場合に相対パスに対して必要です。 詳しい情報については「[サブフォルダを分割して新しいリポジトリにする](/github/getting-started-with-github/using-git/splitting-a-subfolder-out-into-a-new-repository)」を参照してください。 ```yml domain: my-site.github.io # HTTPSを強制したいなら、ドメインの先頭でhttpを指定しない。例: example.com @@ -102,7 +102,7 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを git add . git commit -m 'Initial GitHub pages site with Jekyll' ``` -1. Add your repository on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} as a remote, replacing {% ifversion ghes or ghae %}_HOSTNAME_ with your enterprise's hostname,{% endif %} _USER_ with the account that owns the repository{% ifversion ghes or ghae %},{% endif %} and _REPOSITORY_ with the name of the repository. +1. {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %}でリモートとしてリポジトリを追加してください。{% ifversion ghes or ghae %}_HOSTNAME_をEnterpriseのホスト名で、{% endif %}_USER_をリポジトリを所有するアカウントで、{% ifversion ghes or ghae %}{% endif %}_REPOSITORY_をリポジトリ名で置き換えてください。 ```shell {% ifversion fpt or ghec %} $ git remote add origin https://github.com/USER/REPOSITORY.git diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md index 682c5a984d..baf0068f4c 100644 --- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md @@ -1,6 +1,6 @@ --- -title: Jekyll を使用して、GitHub Pages サイトの Markdown プロセッサを設定する -intro: 'Markdown プロセッサを選択して、{% data variables.product.prodname_pages %} サイトで Markdown をどのようにレンダリングするかを決めることができます。' +title: Setting a Markdown processor for your GitHub Pages site using Jekyll +intro: 'You can choose a Markdown processor to determine how Markdown is rendered on your {% data variables.product.prodname_pages %} site.' redirect_from: - /articles/migrating-your-pages-site-from-maruku - /articles/updating-your-markdown-processor-to-kramdown @@ -14,25 +14,26 @@ versions: ghec: '*' topics: - Pages -shortTitle: Markdownプロセッサの設定 +shortTitle: Set Markdown processor --- -リポジトリへの書き込み権限があるユーザは、{% data variables.product.prodname_pages %} サイトに対して Markdown プロセッサを設定できます。 +People with write permissions for a repository can set the Markdown processor for a {% data variables.product.prodname_pages %} site. -{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. 詳しい情報については、「[{% data variables.product.prodname_dotcom %}での執筆とフォーマットについて](/articles/about-writing-and-formatting-on-github)」を参照してください。 +{% data variables.product.prodname_pages %} supports two Markdown processors: [kramdown](http://kramdown.gettalong.org/) and {% data variables.product.prodname_dotcom %}'s own Markdown processor, which is used to render [{% data variables.product.prodname_dotcom %} Flavored Markdown (GFM)](https://github.github.com/gfm/) throughout {% data variables.product.product_name %}. For more information, see "[About writing and formatting on {% data variables.product.prodname_dotcom %}](/articles/about-writing-and-formatting-on-github)." You can use {% data variables.product.prodname_dotcom %} Flavored Markdown with either processor, but only our GFM processor will always match the results you see on {% data variables.product.product_name %}. {% data reusables.pages.navigate-site-repo %} -2. リポジトリの *_config.yml* ファイルを開きます。 +2. In your repository, browse to the *_config.yml* file. {% data reusables.repositories.edit-file %} -4. `markdown` で始まる行を見つけ、値を `kramdown` または `GFM`に変更します。 ![config.yml での Markdown 設定](/assets/images/help/pages/config-markdown-value.png) +4. Find the line that starts with `markdown:` and change the value to `kramdown` or `GFM`. + ![Markdown setting in config.yml](/assets/images/help/pages/config-markdown-value.png) {% data reusables.files.write_commit_message %} {% data reusables.files.choose-commit-email %} {% data reusables.files.choose_commit_branch %} {% data reusables.files.propose_new_file %} -## 参考リンク +## Further reading -- [kramdown のドキュメント](https://kramdown.gettalong.org/documentation.html) -- [{% data variables.product.prodname_dotcom %} Flavored Markdown の仕様](https://github.github.com/gfm/) +- [kramdown Documentation](https://kramdown.gettalong.org/documentation.html) +- [{% data variables.product.prodname_dotcom %} Flavored Markdown Spec](https://github.github.com/gfm/) diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md index 6f1fa114b1..a641eb99dc 100644 --- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md +++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/testing-your-github-pages-site-locally-with-jekyll.md @@ -52,7 +52,7 @@ Jekyll を使用してサイトをテストする前に、以下の操作が必 {% note %} -**Note:** If you are using Ruby 3.0 and Jekyll 4.2.x or older, you will need to add the `webrick` gem to your project's Gemfile prior to running `bundle install`. +**ノート:** Ruby 3.0及びJekyll 4.2.xあるいはそれより古いものを使っているなら、`bundle install`を実行する前にプロジェクトのGemfileに`webrick` gemを追加する必要があります。 {% endnote %} diff --git a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index e4760ebf16..a35b477866 100644 --- a/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -17,9 +17,11 @@ topics: shortTitle: Request a PR review --- -ユーザアカウントが所有しているリポジトリのオーナーとコラボレータは、プルリクエストのレビューを割り当てることができます。 リポジトリに対するトリアージ権限を持つ Organization メンバーは、プルリクエストのレビューを割り当てることができます。 +Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). 詳しい情報については、「[{% data variables.product.prodname_dotcom %}アカウントの種類](/get-started/learning-about-github/types-of-github-accounts)」を参照してください。" Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request. -オーナーまたはコラボレータは、ユーザ所有のリポジトリに明示的に[読み取りアクセス](/articles/access-permissions-on-github)を付与された人にプルリクエストのレビューを割り当てることができます。 Organization メンバーは、リポジトリの読み取りアクセス権を持つ人や Team にプルリクエストのレビューを割り当てることができます。 リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% ifversion fpt or ghae or ghes or ghec %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. + +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. リクエストされたレビュー担当者または Team は、Pull Request レビューをするようあなたが依頼したという通知を受け取ります。 {% ifversion fpt or ghae or ghes or ghec %}Team にレビューをリクエストし、コードレビューの割り当てが有効になっている場合、特定のメンバーがリクエストされ、Team はレビュー担当者として削除されます。 For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} {% note %} diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index a57c184903..2b5b2c67e0 100644 --- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -38,7 +38,7 @@ CODEOWNERS ファイルを使うためには、コードオーナーを追加し コードオーナーがレビューのリクエストを受け取るためには、CODEOWNERS ファイルがプルリクエストの base ブランチになければなりません。 たとえばリポジトリ中の`gh-pages`ブランチの、*.js*ファイルのコードオーナーとして`@octocat`を割り当てたなら、*.js*に変更を加えるプルリクエストがheadブランチと`gh-pages`の間でオープンされると、`@octocat`はレビューのリクエストを受けることになります。 -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %} ## CODEOWNERS file size CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. diff --git a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index d4359ecd5c..fe49b3658a 100644 --- a/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/translations/ja-JP/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -7,7 +7,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae-issue-4974: '*' + ghae: issue-4974 topics: - Repositories --- diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml index f4db0c2cc8..ccd0725cf4 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-1/0.yml @@ -76,6 +76,7 @@ sections: - The latest release of the CodeQL CLI supports uploading analysis results to GitHub. This makes it easier to run code analysis for customers who wish to use CI/CD systems other than {% data variables.product.prodname_actions %}. Previously, such users had to use the separate CodeQL runner, which will continue to be available. For more information, see "[About CodeQL code scanning in your CI system](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)." - '{% data variables.product.prodname_actions %} now supports skipping `push` and `pull_request` workflows by looking for some common keywords in your commit message.' - Check annotations older than four months will be archived. + - Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18] - heading: Security Changes notes: diff --git a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml index e96c854969..54c5d38568 100644 --- a/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/ja-JP/data/release-notes/enterprise-server/3-4/0.yml @@ -29,6 +29,11 @@ sections: notes: - | {% data variables.product.prodname_dependabot %} is now available in {% data variables.product.prodname_ghe_server %} 3.4 as a public beta, offering both version updates and security updates for several popular ecosystems. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} requires {% data variables.product.prodname_actions %} and a pool of self-hosted runners configured for {% data variables.product.prodname_dependabot %} use. {% data variables.product.prodname_dependabot %} on {% data variables.product.prodname_ghe_server %} also requires {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_dependabot %} to be enabled by an administrator. Beta feedback and suggestions can be shared in the [{% data variables.product.prodname_dependabot %} Feedback GitHub discussion](https://github.com/github/feedback/discussions/categories/dependabot-feedback). For more information and to try the beta, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)." + - + heading: SAML authentication supports encrypted assertions + notes: + - | + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." changes: - heading: 管理に関する変更 diff --git a/translations/ja-JP/data/reusables/code-scanning/beta.md b/translations/ja-JP/data/reusables/code-scanning/beta.md index a18be28cd0..bb9cf0d33c 100644 --- a/translations/ja-JP/data/reusables/code-scanning/beta.md +++ b/translations/ja-JP/data/reusables/code-scanning/beta.md @@ -1,4 +1,8 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} {% note %} diff --git a/translations/ja-JP/data/reusables/secret-scanning/beta.md b/translations/ja-JP/data/reusables/secret-scanning/beta.md index c81d69def2..4dd22083b1 100644 --- a/translations/ja-JP/data/reusables/secret-scanning/beta.md +++ b/translations/ja-JP/data/reusables/secret-scanning/beta.md @@ -1,4 +1,9 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} + {% note %} **ノート:** Organizationが所有するリポジトリのための{% data variables.product.prodname_secret_scanning_caps %}は現在ベータで、変更されることがあります。 diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv index e3e23a3916..d2bfcd0828 100644 --- a/translations/log/ja-resets.csv +++ b/translations/log/ja-resets.csv @@ -171,8 +171,10 @@ translations/ja-JP/content/packages/working-with-a-github-packages-registry/work translations/ja-JP/content/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry.md,broken liquid tags translations/ja-JP/content/pages/getting-started-with-github-pages/about-github-pages.md,broken liquid tags translations/ja-JP/content/pages/getting-started-with-github-pages/changing-the-visibility-of-your-github-pages-site.md,broken liquid tags +translations/ja-JP/content/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site.md,broken liquid tags translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,broken liquid tags translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags +translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/setting-a-markdown-processor-for-your-github-pages-site-using-jekyll.md,broken liquid tags translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/troubleshooting-jekyll-build-errors-for-github-pages-sites.md,broken liquid tags translations/ja-JP/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,broken liquid tags translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository.md,broken liquid tags From 416e8a3f59c1567e37083440ba7674cfd2940607 Mon Sep 17 00:00:00 2001 From: docubot <67483024+docubot@users.noreply.github.com> Date: Mon, 21 Mar 2022 14:45:51 -0700 Subject: [PATCH 15/18] New translation batch for es (#26383) * Add crowdin translations * Run script/i18n/homogenize-frontmatter.js * Run script/i18n/fix-translation-errors.js * Run script/i18n/lint-translation-files.js --check rendering * run script/i18n/reset-files-with-broken-liquid-tags.js --language=es * run script/i18n/reset-known-broken-translation-files.js Co-authored-by: Peter Bengtsson --- .../workflow-commands-for-github-actions.md | 466 +++++++++++++++--- .../configuring-a-hostname.md | 8 +- ...ng-a-failover-to-your-replica-appliance.md | 39 +- .../about-migrations.md | 2 +- .../checking-for-existing-ssh-keys.md | 2 +- .../using-ssh-over-the-https-port.md | 2 +- .../secret-scanning/about-secret-scanning.md | 4 +- .../get-started/quickstart/fork-a-repo.md | 2 +- .../requesting-a-pull-request-review.md | 6 +- .../about-code-owners.md | 2 +- .../searching-a-repositorys-releases.md | 2 +- .../release-notes/enterprise-server/3-1/0.yml | 1 + .../release-notes/enterprise-server/3-4/0.yml | 5 + .../data/reusables/code-scanning/beta.md | 6 +- .../data/reusables/secret-scanning/beta.md | 7 +- 15 files changed, 443 insertions(+), 111 deletions(-) diff --git a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md index 075ac683c5..f7d5b68915 100644 --- a/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md +++ b/translations/es-ES/content/actions/using-workflows/workflow-commands-for-github-actions.md @@ -2,6 +2,7 @@ title: Comandos de flujo de trabajo para Acciones de GitHub shortTitle: Comandos de flujo de trabajo intro: Puedes usar comandos de flujo de trabajo cuando ejecutas comandos de Shell en un flujo de trabajo o en el código de una acción. +defaultTool: bash redirect_from: - /articles/development-tools-for-github-actions - /github/automating-your-workflow-with-github-actions/development-tools-for-github-actions @@ -26,10 +27,24 @@ Las acciones pueden comunicarse con la máquina del ejecutor para establecer var La mayoría de los comandos de los flujos de trabajo utilizan el comando `echo` en un formato específico, mientras que otras se invocan si escribes a un archivo. Para obtener más información, consulta la sección ["Archivos de ambiente".](#environment-files) -``` bash +### Ejemplo + +{% bash %} + +```bash{:copy} echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value}" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}" +``` + +{% endpowershell %} + {% note %} **Nota:** los nombres de comandos y parámetros de flujo de trabajo no distinguen mayúsculas de minúsculas. @@ -46,14 +61,18 @@ echo ":: Workflow-Command Parameter1 ={data}, parameter2 ={data}::{command value El [actions/toolkit](https://github.com/actions/toolkit) incluye varias funciones que se pueden ejecutar como comandos de flujo de trabajo. Utiliza la sintaxis `::` para ejecutar los comandos de flujo de trabajo dentro de tu archivo YAML; estos comandos se envían entonces a través de `stdout`. Por ejemplo, en vez de utilizar código para configurar una salida, como se muestra aquí: -```javascript +```javascript{:copy} core.setOutput('SELECTED_COLOR', 'green'); ``` +### Example: Setting a value + Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar el mismo valor: +{% bash %} + {% raw %} -``` yaml +```yaml{:copy} - name: Set selected color run: echo '::set-output name=SELECTED_COLOR::green' id: random-color-generator @@ -62,6 +81,22 @@ Puedes utilizar el comando `set-output` en tu flujo de trabajo para configurar e ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} + - name: Set selected color + run: Write-Output "::set-output name=SELECTED_COLOR::green" + id: random-color-generator + - name: Get color + run: Write-Output "The selected color is ${{ steps.random-color-generator.outputs.SELECTED_COLOR }}" +``` +{% endraw %} + +{% endpowershell %} + La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles dentro de un flujo de trabajo: | Funcion del Toolkit | Comando equivalente del flujo de trabajo | @@ -86,186 +121,336 @@ La siguiente tabla muestra qué funciones del toolkit se encuentran disponibles ## Configurar un parámetro de salida -``` +Establece un parámetro de salida de la acción. + +```{:copy} ::set-output name={name}::{value} ``` -Establece un parámetro de salida de la acción. - Opcionalmente, también puedes declarar parámetros de salida en el archivo de metadatos de una acción. Para obtener más información, consulta la sección "[Sintaxis de metadatos para {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs-for-docker-container-and-javascript-actions)". -### Ejemplo +### Example: Setting an output parameter -``` bash +{% bash %} + +```bash{:copy} echo "::set-output name=action_fruit::strawberry" ``` -## Agregar un mensaje de depuración +{% endbash %} +{% powershell %} + +```pwsh{:copy} +Write-Output "::set-output name=action_fruit::strawberry" ``` -::debug::{message} -``` + +{% endpowershell %} + +## Agregar un mensaje de depuración Imprime un mensaje de depuración para el registro. Debes crear un archivo `ACTIONS_STEP_DEBUG` designado secretamente con el valor `true` para ver los mensajes de depuración establecidos por este comando en el registro. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)." -### Ejemplo +```{:copy} +::debug::{message} +``` -``` bash +### Example: Setting a debug message + +{% bash %} + +```bash{:copy} echo "::debug::Set the Octocat variable" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::debug::Set the Octocat variable" +``` + +{% endpowershell %} + {% ifversion fpt or ghes > 3.2 or ghae-issue-4929 or ghec %} ## Configurar un mensaje de aviso -``` +Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::notice file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de aviso e imprime el mensaje en la bitácora. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Ejemplo +### Example: Setting a notice message -``` bash +{% bash %} + +```bash{:copy} echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} {% endif %} ## Configurar un mensaje de advertencia -``` +Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::warning file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de advertencia e imprime el mensaje en el registro. {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Ejemplo +### Example: Setting a warning message -``` bash +{% bash %} + +```bash{:copy} echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## Configurar un mensaje de error -``` +Crea un mensaje de error e imprime el mensaje en el registro {% data reusables.actions.message-annotation-explanation %} + +```{:copy} ::error file={name},line={line},endLine={endLine},title={title}::{message} ``` -Crea un mensaje de error e imprime el mensaje en el registro {% data reusables.actions.message-annotation-explanation %} - {% data reusables.actions.message-parameters %} -### Ejemplo +### Example: Setting an error message -``` bash +{% bash %} + +```bash{:copy} echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" ``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon" +``` + +{% endpowershell %} ## Agrupar líneas de las bitácoras -``` +Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma. + +```{:copy} ::group::{title} ::endgroup:: ``` -Crea un grupo expansible en la bitácora. Para crear un grupo, utiliza el comando `group` y especifica un `title`. Todo lo que imprimas en la bitácora entre los comandos `group` y `endgroup` se anidará dentro de una entrada expansible en la misma. +### Example: Grouping log lines -### Ejemplo +{% bash %} -```bash -echo "::group::My title" -echo "Inside group" -echo "::endgroup::" +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + steps: + - name: Group of log lines + run: | + echo "::group::My title" + echo "Inside group" + echo "::endgroup::" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + steps: + - name: Group of log lines + run: | + Write-Output "::group::My title" + Write-Output "Inside group" + Write-Output "::endgroup::" +``` + +{% endpowershell %} + ![Grupo plegable en la bitácora de una ejecución de flujo de trabajo](/assets/images/actions-log-group.png) ## Enmascarar un valor en el registro -``` +```{:copy} ::add-mask::{value} ``` El enmascaramiento de un valor impide que una cadena o variable se imprima en el registro. Cada palabra enmascarada separada por un espacio en blanco se reemplaza con el carácter `*`. Puedes usar una variable de entorno o cadena para el `valor` de la máscara. -### Ejemplo de enmascaramiento de una cadena +### Example: Masking a string Cuando imprimas `"Mona The Octocat"` en el registro, verás `"***"`. -```bash +{% bash %} + +```bash{:copy} echo "::add-mask::Mona The Octocat" ``` -### Ejemplo de enmascaramiento de una variable de entorno +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +Write-Output "::add-mask::Mona The Octocat" +``` + +{% endpowershell %} + +### Example: Masking an environment variable Cuando imprimes la variable `MY_NAME` o el valor `"Mona The Octocat"` en el registro, verás `"***"` en lugar de `"Mona The Octocat"`. -```bash -MY_NAME="Mona The Octocat" -echo "::add-mask::$MY_NAME" +{% bash %} + +```yaml{:copy} +jobs: + bash-example: + runs-on: ubuntu-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: bash-version + run: echo "::add-mask::$MY_NAME" ``` +{% endbash %} + +{% powershell %} + +```yaml{:copy} +jobs: + powershell-example: + runs-on: windows-latest + env: + MY_NAME: "Mona The Octocat" + steps: + - name: powershell-version + run: Write-Output "::add-mask::$env:MY_NAME" +``` + +{% endpowershell %} + ## Detener e iniciar comandos de flujo de trabajo -`::stop-commands::{endtoken}` - Deja de procesar cualquier comando de flujo de trabajo. Este comando especial te permite registrar lo que sea sin ejecutar accidentalmente un comando de flujo de trabajo. Por ejemplo, podrías dejar de registrar para producir un script completo que tenga comentarios. +```{:copy} +::stop-commands::{endtoken} +``` + Para parar el procesamiento de los comandos de flujo de trabajo, pasa un token único a `stop-commands`. Para resumir los comandos de flujo de trabajo de procesamiento, pasa el mismo token que utilizaste para detener los comandos de flujo de trabajo. {% warning %} -**Advertencia:** Asegúrate de que el token que estás utilizando se genere aleatoriamente y sea único para cada ejecución. Tal como se demuestra en el siguiente ejemplo, puedes generar un hash único de tu `github.token` para cada ejecución. +**Advertencia:** Asegúrate de que el token que estás utilizando se genere aleatoriamente y sea único para cada ejecución. {% endwarning %} -``` +```{:copy} ::{endtoken}:: ``` -### Ejemplo deteniendo e iniciando los comandos de un flujo de trabajo +### Example: Stopping and starting workflow commands + +{% bash %} {% raw %} -```yaml +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest steps: - - name: disable workflow commands + - name: Disable workflow commands run: | - echo '::warning:: this is a warning' - echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`" - echo '::warning:: this will NOT be a warning' - echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::" - echo '::warning:: this is a warning again' + echo '::warning:: This is a warning message, to demonstrate that commands are being processed.' + stopMarker=$(uuidgen) + echo "::stop-commands::$stopMarker" + echo '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + echo "::$stopMarker::" + echo '::warning:: This is a warning again, because stop-commands has been turned off.' +``` +{% endraw %} + +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: Disable workflow commands + run: | + Write-Output '::warning:: This is a warning message, to demonstrate that commands are being processed.' + $stopMarker = New-Guid + Write-Output "::stop-commands::$stopMarker" + Write-Output '::warning:: This will NOT be rendered as a warning, because stop-commands has been invoked.' + Write-Output "::$stopMarker::" + Write-Output '::warning:: This is a warning again, because stop-commands has been turned off.' ``` {% endraw %} +{% endpowershell %} + ## Hacer eco en las salidas de comando -``` +Habilita o inhabilita el hacer eco en los comandos de los flujos de trabajo. Por ejemplo, si utilizas el comando `set-output` en un flujo de trabajo, este configura un parámetro de salida pero la bitácora de la ejecución del flujo de trabajo no muestra al comando mismo. Si habilitas el eco del comando, entonces la bitácora lo mostrará, tal como en `::set-output name={name}::{value}`. + +```{:copy} ::echo::on ::echo::off ``` -Habilita o inhabilita el hacer eco en los comandos de los flujos de trabajo. Por ejemplo, si utilizas el comando `set-output` en un flujo de trabajo, este configura un parámetro de salida pero la bitácora de la ejecución del flujo de trabajo no muestra al comando mismo. Si habilitas el eco del comando, entonces la bitácora lo mostrará, tal como en `::set-output name={name}::{value}`. - El eco de comando se encuentra inhabilitado predeterminadamente. Sin embargo, los comandos de flujo de trabajo hacen eco si existen errores para procesarlos. Los comandos `add-mask`, `debug`, `warning` y `error` no son compatibles con el eco porque sus salidas ya hicieron eco en la bitácora. También puedes habilitar el eco de comandos globalmente si activas la generación de bitácoras de depuración de pasos utilizando el secreto `ACTIONS_STEP_DEBUG`. Para obtener más información, consulta la sección "[Habilitar el registro de depuración](/actions/managing-workflow-runs/enabling-debug-logging)". Como contraste, el comando de flujo de trabajo `echo` te permite habilitar el eco de comandos en un nivel más granular en vez de habilitarlo para cada flujo de trabajo en un repositorio. -### Ejemplo de cómo alternar el eco de comandos +### Example: Toggling command echoing -```yaml +{% bash %} + +```yaml{:copy} jobs: workflow-command-job: runs-on: ubuntu-latest @@ -279,9 +464,29 @@ jobs: echo '::set-output name=action_echo::disabled' ``` -El paso anterior imprime las siguientes líneas en la bitácora: +{% endbash %} +{% powershell %} + +```yaml{:copy} +jobs: + workflow-command-job: + runs-on: windows-latest + steps: + - name: toggle workflow command echoing + run: | + write-output "::set-output name=action_echo::disabled" + write-output "::echo::on" + write-output "::set-output name=action_echo::enabled" + write-output "::echo::off" + write-output "::set-output name=action_echo::disabled" ``` + +{% endpowershell %} + +The example above prints the following lines to the log: + +```{:copy} ::set-output name=action_echo::enabled ::echo::off ``` @@ -298,13 +503,13 @@ El comando `save-state` solo puede ejecutarse dentro de una acción y no está d Este ejemplo utiliza JavaScript para ejecutar el comando `save-state`. La variable de ambiente resultante se nombra `STATE_processID` con el valor de `12345`: -``` javascript +```javascript{:copy} console.log('::save-state name=processID::12345') ``` La variable `STATE_processID` se encontrará entonces exclusivamente disponible para el script de limpieza que se ejecuta bajo la acción `main`. Este ejemplo se ejecuta en `main` y utiliza JavaScript para mostrar el valor asignado a la variable de ambiente `STATE_processID`: -``` javascript +```javascript{:copy} console.log("The running PID from the main action is: " + process.env.STATE_processID); ``` @@ -312,37 +517,70 @@ console.log("The running PID from the main action is: " + process.env.STATE_pro Durante la ejecución de un flujo de trabajo, el ejecutor genera archivos temporales que pueden utilizarse para llevar a cabo ciertas acciones. La ruta a estos archivos se expone a través de variables de ambiente. Necesitarás utilizar codificación UTF-8 cuando escribas en estos archivos para garantizar el procesamiento adecuado de los comandos. Se pueden escribir varios comandos en el mismo archivo, separados por líneas nuevas. -{% warning %} +{% powershell %} -**Advertencia:** en Windows, el PowerShell tradicional (`shell: powershell`) no utiliza el cifrado UTF-8 predeterminado. +{% note %} -When using `shell: powershell`, you must specify UTF-8 encoding. Por ejemplo: +**Note:** PowerShell versions 5.1 and below (`shell: powershell`) do not use UTF-8 by default, so you must specify the UTF-8 encoding. Por ejemplo: -```yaml +```yaml{:copy} jobs: legacy-powershell-example: - uses: windows-2019 + runs-on: windows-latest steps: - shell: powershell - run: echo "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append + run: | + "mypath" | Out-File -FilePath $env:GITHUB_PATH -Encoding utf8 -Append ``` -Alternatively, you can use PowerShell Core (`shell: pwsh`), which defaults to UTF-8. +PowerShell Core versions 6 and higher (`shell: pwsh`) use UTF-8 by default. Por ejemplo: -{% endwarning %} +```yaml{:copy} +jobs: + powershell-core-example: + runs-on: windows-latest + steps: + - shell: pwsh + run: | + "mypath" >> $env:GITHUB_PATH +``` + +{% endnote %} + +{% endpowershell %} ## Configurar una variable de ambiente -``` bash +{% bash %} + +```bash{:copy} echo "{environment_variable_name}={value}" >> $GITHUB_ENV ``` +{% endbash %} + +{% powershell %} + +- Using PowerShell version 6 and higher: +```pwsh{:copy} +"{environment_variable_name}={value}" >> $env:GITHUB_ENV +``` + +- Using PowerShell version 5.1 and below: +```powershell{:copy} +"{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Encoding utf8 -Append +``` + +{% endpowershell %} + You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. El paso que crea o actualiza la variable de ambiente no tiene acceso al valor nuevo, pero todos los pasos subsecuentes en un job tendrán acceso. The names of environment variables are case-sensitive, and you can include punctuation. Para obtener más información, consulta "[Variables del entorno](/actions/learn-github-actions/environment-variables)". ### Ejemplo +{% bash %} + {% raw %} -``` +```yaml{:copy} steps: - name: Set the value id: step_one @@ -355,11 +593,31 @@ steps: ``` {% endraw %} +{% endbash %} + +{% powershell %} + +{% raw %} +```yaml{:copy} +steps: + - name: Set the value + id: step_one + run: | + "action_state=yellow" >> $env:GITHUB_ENV + - name: Use the value + id: step_two + run: | + Write-Output "${{ env.action_state }}" # This will output 'yellow' +``` +{% endraw %} + +{% endpowershell %} + ### Secuencias de línea múltiple Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la siguiente sintaxis. -``` +```{:copy} {name}<<{delimiter} {value} {delimiter} @@ -367,29 +625,75 @@ Para las secuencias de lìnea mùltiple, puedes utilizar un delimitador con la s #### Ejemplo -En este ejemplo, utilizamos `EOF` como delimitador y configuramos la variable de ambiente `JSON_RESPONSE` para el valor de la respuesta de curl. -```yaml +This example uses `EOF` as a delimiter, and sets the `JSON_RESPONSE` environment variable to the value of the `curl` response. + +{% bash %} + +```yaml{:copy} steps: - - name: Set the value + - name: Set the value in bash id: step_one run: | echo 'JSON_RESPONSE<> $GITHUB_ENV - curl https://httpbin.org/json >> $GITHUB_ENV + curl https://example.lab >> $GITHUB_ENV echo 'EOF' >> $GITHUB_ENV ``` -## Agregar una ruta de sistema +{% endbash %} -``` bash -echo "{path}" >> $GITHUB_PATH +{% powershell %} + +```yaml{:copy} +steps: + - name: Set the value in pwsh + id: step_one + run: | + "JSON_RESPONSE<> $env:GITHUB_ENV + (Invoke-WebRequest -Uri "https://example.lab").Content >> $env:GITHUB_ENV + "EOF" >> $env:GITHUB_ENV + shell: pwsh ``` +{% endpowershell %} + +## Agregar una ruta de sistema + Antepone un directorio a la variable de sistema `PATH` y la hace disponible automáticamente para todas las acciones subsecuentes en el job actual; la acción que se está ejecutando actualmente no puede acceder a la variable de ruta actualizada. Para ver las rutas definidas actualmente para tu job, puedes utilizar `echo "$PATH"` en un paso o en una acción. +{% bash %} + +```bash{:copy} +echo "{path}" >> $GITHUB_PATH +``` +{% endbash %} + +{% powershell %} + +```pwsh{:copy} +"{path}" >> $env:GITHUB_PATH +``` + +{% endpowershell %} + ### Ejemplo Este ejemplo demuestra cómo agregar el directorio `$HOME/.local/bin` del usuario al `PATH`: -``` bash +{% bash %} + +```bash{:copy} echo "$HOME/.local/bin" >> $GITHUB_PATH ``` + +{% endbash %} + + +This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`: + +{% powershell %} + +```pwsh{:copy} +"$env:HOMEPATH/.local/bin" >> $env:GITHUB_PATH +``` + +{% endpowershell %} diff --git a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md index b61937585b..8e82a3e45f 100644 --- a/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md +++ b/translations/es-ES/content/admin/configuration/configuring-network-settings/configuring-a-hostname.md @@ -17,7 +17,11 @@ topics: Si configuras un nombre del host en lugar de una dirección IP codificada de forma rígida, podrás cambiar el hardware físico que ejecuta {% data variables.product.product_location %} sin afectar a los usuarios o al software del cliente. -La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. Por ejemplo, tu configuración de nombre del host podría ser `github.companyname.com.` También recomendamos habilitar el aislamiento de subdominio para el nombre del host elegido a fin de mitigar varias vulnerabilidades del estilo cross-site scripting. Para obtener más información, consulta [Sección 2.1 del HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). +La configuración del nombre de host en la {% data variables.enterprise.management_console %} debe ajustarse a un nombre de dominio adecuado y que cumpla con todos los requisitos (FQDN) el cual se pueda resolver en la internet o dentro de tu red interna. For example, your hostname setting could be `github.companyname.com.` Web and API requests will automatically redirect to the hostname configured in the {% data variables.enterprise.management_console %}. + +After you configure a hostname, you can enable subdomain isolation to further increase the security of {% data variables.product.product_location %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." + +For more information on the supported hostname types, see [Section 2.1 of the HTTP RFC](https://tools.ietf.org/html/rfc1123#section-2). {% data reusables.enterprise_installation.changing-hostname-not-supported %} @@ -29,4 +33,4 @@ La configuración del nombre de host en la {% data variables.enterprise.manageme {% data reusables.enterprise_management_console.test-domain-settings-failure %} {% data reusables.enterprise_management_console.save-settings %} -Después de configurar un nombre del host, recomendamos que habilites el aislamiento de subdominio para {% data variables.product.product_location %}. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." +To help mitigate various cross-site scripting vulnerabilities, we recommend that you enable subdomain isolation for {% data variables.product.product_location %} after you configure a hostname. Para obtener más información, consulta "[Habilitar el aislamiento de subdominio](/enterprise/{{ currentVersion }}/admin/guides/installation/enabling-subdomain-isolation/)." diff --git a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md index 21ea21a4f7..a407bf95c8 100644 --- a/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md +++ b/translations/es-ES/content/admin/enterprise-management/configuring-high-availability/initiating-a-failover-to-your-replica-appliance.md @@ -19,25 +19,32 @@ El tiempo requerido para la tolerancia de fallos depende de cuánto le tome para {% data reusables.enterprise_installation.promoting-a-replica %} -1. Para permitir que la replicación finalice antes de cambiar aparatos, pon el aparato principal en modo mantenimiento: - - Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)" - - También puedes usar el comando `ghe-maintenance -s`. +1. If the primary appliance is available, to allow replication to finish before you switch appliances, on the primary appliance, put the primary appliance into maintenance mode. + + - Put the appliance into maintenance mode. + + - Para usar el administrador de consola, consulta "[Habilitar y programar el modo mantenimiento](/enterprise/admin/guides/installation/enabling-and-scheduling-maintenance-mode/)" + + - También puedes usar el comando `ghe-maintenance -s`. + ```shell + $ ghe-maintenance -s + ``` + + - Cuando la cantidad de operaciones activas de Git, consultas de MySQL y jobs de Resque lleguen a cero, espera 30 segundos. + + {% note %} + + **Nota:** Nomad siempre tendrá jobs en ejecución, incluso si está en modo de mantenimiento, así que puedes ignorar estos jobs de forma segura. + + {% endnote %} + + - Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`. + ```shell - $ ghe-maintenance -s + $ ghe-repl-status -vv ``` -2. Cuando la cantidad de operaciones activas de Git, consultas de MySQL y jobs de Resque lleguen a cero, espera 30 segundos. - {% note %} - - **Nota:** Nomad siempre tendrá jobs en ejecución, incluso si está en modo de mantenimiento, así que puedes ignorar estos jobs de forma segura. - - {% endnote %} - -3. Para verificar que todos los canales de replicación informan `OK`, utiliza el comando `ghe-repl-status -vv`. - ```shell - $ ghe-repl-status -vv - ``` -4. Para frenar la replicación e impulsar el aparato de réplica a un estado primario, utiliza el comando `ghe-repl-promote`. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible. +4. On the replica appliance, to stop replication and promote the replica appliance to primary status, use the `ghe-repl-promote` command. Esto también pondrá de forma automática al nodo primario en nodo mantenimiento si es accesible. ```shell $ ghe-repl-promote ``` diff --git a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md index 330df79754..7dafac5db6 100644 --- a/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md +++ b/translations/es-ES/content/admin/user-management/migrating-data-to-and-from-your-enterprise/about-migrations.md @@ -25,7 +25,7 @@ Existen tres tipos de migraciones que se pueden realizar: En una migración, todo gira en torno a un repositorio. La mayoría de los datos asociados con un repositorio se pueden migrar. Por ejemplo, un repositorio dentro de una organización migrará el repositorio *y* la organización, así como los usuarios, equipos, propuestas y solicitudes de extracción asociados con el repositorio. -Los elementos de la tabla a continuación se pueden migrar con un repositorio. Los elementos que no se muestren en la lista de datos migrados no se pueden migrar. +Los elementos de la tabla a continuación se pueden migrar con un repositorio. Any items not shown in the list of migrated data can not be migrated, including {% data variables.large_files.product_name_short %} assets. {% data reusables.enterprise_migrations.fork-persistence %} diff --git a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md index bca81ac3c4..759d070755 100644 --- a/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md +++ b/translations/es-ES/content/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys.md @@ -25,7 +25,7 @@ shortTitle: Verificar la llave SSH existente # Lists the files in your .ssh directory, if they exist ``` -3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Predeterminadamente, {% ifversion ghae %}el nombre de archivo de una llave pública para {% data variables.product.product_name %} es *id_rsa.pub*.{% elsif fpt or ghes %}los nombres de archivo de las llaves públicas compatibles para {% data variables.product.product_name %} son una de las siguientes. +3. Comprueba la lista de directorio para ver si ya tiene una clave SSH pública. Predeterminadamente, {% ifversion ghae %}el nombre de archivo de una llave pública para {% data variables.product.product_name %} es *id_rsa.pub*.{% else %}los nombres de archivo de las llaves públicas compatibles para {% data variables.product.product_name %} son una de las siguientes. - *id_rsa.pub* - *id_ecdsa.pub* - *id_ed25519.pub*{% endif %} diff --git a/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md index a810fd6fe6..c011c393f2 100644 --- a/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md +++ b/translations/es-ES/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md @@ -33,7 +33,7 @@ Si eso funcionó, ¡fantástico! De lo contrario, puede que debas [seguir nuestr Si puedes ingresar a `git@ssh.{% data variables.command_line.backticks %}` por SSH a través del puerto 443, podrás reemplazar los parámetros SSH para forzar que cualquier conexión a {% data variables.product.product_location %} se ejecute a través de ese servidor y puerto. -Para configurar esto en tu archivo de configuración SSH, edita el archivo en `~/.ssh/config` y agrega esta sección: +To set this in your SSH configuration file, edit the file at `~/.ssh/config`, and add this section: ``` Host {% data variables.command_line.codeblock %} diff --git a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md index f49db4795c..9549eaaae2 100644 --- a/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md +++ b/translations/es-ES/content/code-security/secret-scanning/about-secret-scanning.md @@ -31,9 +31,9 @@ If your project communicates with an external service, you might use a token or {% ifversion fpt or ghec %} {% data variables.product.prodname_secret_scanning_caps %} is available on {% data variables.product.prodname_dotcom_the_website %} in two forms: -1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relvant partner. +1. **{% data variables.product.prodname_secret_scanning_partner_caps %}.** Runs automatically on all public repositories. Any strings that match patterns that were provided by secret scanning partners are reported directly to the relevant partner. -2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scannng partners, by other service providers, or defined by your organization are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. +2. **{% data variables.product.prodname_secret_scanning_GHAS_caps %}.** You can enable and configure additional scanning for repositories owned by organizations that use {% data variables.product.prodname_ghe_cloud %} and have a license for {% data variables.product.prodname_GH_advanced_security %}. Any strings that match patterns provided by secret scanning partners, by other service providers, or defined by your organization, are reported as alerts in the "Security" tab of repositories. If a string in a public repository matches a partner pattern, it is also reported to the partner. {% endif %} Service providers can partner with {% data variables.product.company_short %} to provide their secret formats for scanning. {% data reusables.secret-scanning.partner-program-link %} diff --git a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md index 145314eb1f..bce507d4c9 100644 --- a/translations/es-ES/content/get-started/quickstart/fork-a-repo.md +++ b/translations/es-ES/content/get-started/quickstart/fork-a-repo.md @@ -21,7 +21,7 @@ topics: --- ## About forks -Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." +Most commonly, forks are used to either propose changes to someone else's project to which you don't have write access, or to use someone else's project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository. For more information, see "[Working with forks](/github/collaborating-with-issues-and-pull-requests/working-with-forks)." ### Propose changes to someone else's project diff --git a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md index 0d8f54b35a..2e1c7f916a 100644 --- a/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md +++ b/translations/es-ES/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review.md @@ -16,9 +16,11 @@ topics: - Pull requests shortTitle: Request a PR review --- -Owners and collaborators on a repository owned by a user account can assign pull request reviews. Organization members with triage permissions to a repository can assign a pull request review. +Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). For more information, see "[Types of {% data variables.product.prodname_dotcom %} accounts](/get-started/learning-about-github/types-of-github-accounts)." Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request. -Owners or collaborators can assign a pull request review to any person that has been explicitly granted [read access](/articles/access-permissions-on-github) to a user-owned repository. Organization members can assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% ifversion fpt or ghae or ghes or ghec %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} +To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see "[Repository roles for an organization](/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization)." If you have write access, you can assign anyone who has read access to the repository as a reviewer. + +Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. {% ifversion fpt or ghae or ghes or ghec %}If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see "[Managing code review settings for your team](/organizations/organizing-members-into-teams/managing-code-review-settings-for-your-team)."{% endif %} {% note %} diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md index 647063b1ee..a4bef4079e 100644 --- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md +++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners.md @@ -37,7 +37,7 @@ Each CODEOWNERS file assigns the code owners for a single branch in the reposito For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign `@octocat` as the code owner for *.js* files on the `gh-pages` branch of your repository, `@octocat` will receive review requests when a pull request with changes to *.js* files is opened between the head branch and `gh-pages`. -{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-9273 %} +{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4675 %} ## CODEOWNERS file size CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request. diff --git a/translations/es-ES/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md b/translations/es-ES/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md index c9dc9ab4fd..ab03d6def8 100644 --- a/translations/es-ES/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md +++ b/translations/es-ES/content/repositories/releasing-projects-on-github/searching-a-repositorys-releases.md @@ -7,7 +7,7 @@ versions: fpt: '*' ghec: '*' ghes: '>3.2' - ghae-issue-4974: '*' + ghae: issue-4974 topics: - Repositories --- diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml index f37b8ac998..cc3dcfbd19 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/0.yml @@ -33,6 +33,7 @@ sections: - 'El último lanzamiento del CLI de CodeQL es compatible con subir los resultados del análisis a GitHub. esto facilita ejecutar el análisis de código para los clientes que quieran utilizar sistemas de IC/DC diferentes a los de {% data variables.product.prodname_actions %}. Anteriormente, estos usuarios tenían que utilizar un ejecutor de CodeQL por separado, el cual aún estará disponible. Para obtener más información, consulta la sección [Acerca del escaneo de código de CodeQL en tu sistema de IC](/enterprise-server@3.1/code-security/secure-coding/about-codeql-code-scanning-in-your-ci-system)".' - '{% data variables.product.prodname_actions %} es ahora compatible con saltar los flujos de trabajo de tipo `push` y `pull_request` si se buscan las palabras clave en común dentro de tu mensaje de confirmación.' - 'Se archivará las anotaciones de verificación más antiguas a cuatro meses.' + - 'Scaling of worker allocation for background tasks has been revised. We recommend validating that the new defaults are appropriate for your workload. Custom background worker overrides should be unset in most cases. [Updated 2022-03-18]' - heading: 'Cambios de seguridad' notes: - 'Siguiendo la retroalimentación, seguirá habiendo compatibilidad para mostrar los resultados del escaneo de código en una solicitud de cambios sin emitirlos con una ID de esta. Para obtener más información, consulta las secciones "[Configurar el escaneo de código](/enterprise-server@3.1/code-security/secure-coding/configuring-code-scanning#scanning-pull-requests)" y "[Configurar el escaneo de código de CodeQL en tu sistema de IC](/enterprise-server@3.1/code-security/secure-coding/configuring-codeql-code-scanning-in-your-ci-system#scanning-pull-requests).' diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml b/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml index f0e9b739b4..e2c97f8bec 100644 --- a/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml +++ b/translations/es-ES/data/release-notes/enterprise-server/3-4/0.yml @@ -29,6 +29,11 @@ sections: notes: - | El {% data variables.product.prodname_dependabot %} ahora está disponible en {% data variables.product.prodname_ghe_server %} 3.4 como un beta público y ofrece tanto actualziaciones de versión como de seguridad para varios ecosistemas populares. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} requiere {% data variables.product.prodname_actions %} y un conjunto de ejecutores auto-hospedados configurado para que el mismo {% data variables.product.prodname_dependabot %} los utilice. El {% data variables.product.prodname_dependabot %} en {% data variables.product.prodname_ghe_server %} también requiere que un administrador habilite tanto {% data variables.product.prodname_github_connect %} como el mismo {% data variables.product.prodname_dependabot %}. Puedes compartir tu retroalimentación y sugerencias en el [Debate de GitHub sobre la retroalimentación para el {% data variables.product.prodname_dependabot %}](https://github.com/github/feedback/discussions/categories/dependabot-feedback). Para obtener más información y probar el beta, consulta la sección "[Configurar la seguridad y las actualizaciones de versión del {% data variables.product.prodname_dependabot %} en tu empresa](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)". + - + heading: SAML authentication supports encrypted assertions + notes: + - | + If you use SAML authentication for {% data variables.product.prodname_ghe_server %}, you can now configure encrypted assertions from your IdP to improve security. Encrypted assertions add an additional layer of encryption when your IdP transmits information to {% data variables.product.product_location %}. For more information, see "[Using SAML](/admin/identity-and-access-management/authenticating-users-for-your-github-enterprise-server-instance/using-saml#enabling-encrypted-assertions)." changes: - heading: Cambios en la administración diff --git a/translations/es-ES/data/reusables/code-scanning/beta.md b/translations/es-ES/data/reusables/code-scanning/beta.md index bc41c01a1c..1e7fb13e55 100644 --- a/translations/es-ES/data/reusables/code-scanning/beta.md +++ b/translations/es-ES/data/reusables/code-scanning/beta.md @@ -1,4 +1,8 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} {% note %} diff --git a/translations/es-ES/data/reusables/secret-scanning/beta.md b/translations/es-ES/data/reusables/secret-scanning/beta.md index 9436c83fea..c997ecba8b 100644 --- a/translations/es-ES/data/reusables/secret-scanning/beta.md +++ b/translations/es-ES/data/reusables/secret-scanning/beta.md @@ -1,4 +1,9 @@ -{% ifversion ghae %} +{% ifversion ghae-issue-5752 %} + + + +{% elsif ghae %} + {% note %} **Nota:** Las {% data variables.product.prodname_secret_scanning_caps %} para los repositorios que pertenecen a organizaciones se encuentra actualmente en beta y está sujeta a cambios. From 6e039efe703beb0d4e2630861a3683182f0fe83f Mon Sep 17 00:00:00 2001 From: Siddharth Kshetrapal Date: Mon, 21 Mar 2022 23:10:06 +0100 Subject: [PATCH 16/18] Fix flash of incorrect theme for @primer/components (#24123) * Pass color mode from server to ThemeProvider * Add preventSSRMismatch * Fix bad merge, my bad. * use release candidate for csrf safe approach * upgrade primer/react to 34.7.1 Co-authored-by: Mike Surowiec --- package-lock.json | 58 +++++++++++++++++++++++++++++++++++++++++------ package.json | 2 +- pages/_app.tsx | 23 +++++++------------ 3 files changed, 60 insertions(+), 23 deletions(-) diff --git a/package-lock.json b/package-lock.json index 4f2a50a441..30b32046b8 100644 --- a/package-lock.json +++ b/package-lock.json @@ -11,7 +11,7 @@ "@primer/css": "^19.4.0", "@primer/octicons": "17.0.0", "@primer/octicons-react": "17.0.0", - "@primer/react": "^34.6.0", + "@primer/react": "^34.7.1", "@react-aria/ssr": "^3.1.0", "accept-language-parser": "^1.5.0", "ajv": "^8.9.0", @@ -3603,9 +3603,9 @@ "integrity": "sha512-+Gwo89YK1OFi6oubTlah/zPxxzMNaMLy+inECAYI646KIFdzzhAsKWb3z5tSOu5Ff7no4isRV64rWfMSKLZclw==" }, "node_modules/@primer/react": { - "version": "34.6.0", - "resolved": "https://registry.npmjs.org/@primer/react/-/react-34.6.0.tgz", - "integrity": "sha512-a0Mh6YmpEyQF6ad0mnfOJoC+y1heDM4uuvBcQQKJQ28DVeif5mn+slCD2C9ZQvnhkl4qnh3iqXOTxmKN5fCHNQ==", + "version": "34.7.1", + "resolved": "https://registry.npmjs.org/@primer/react/-/react-34.7.1.tgz", + "integrity": "sha512-9OLRo3N1/B/jqb7aJPY7xmtyKM8afZlmWLnEOmT8LOCmuwPiRXI+4GsJjaV9RPx3h8rUXBQwpaYZGDDj9+/OjA==", "dependencies": { "@primer/behaviors": "1.1.0", "@primer/octicons-react": "16.1.1", @@ -4772,6 +4772,17 @@ "string-width": "^4.1.0" } }, + "node_modules/ansi-colors": { + "version": "4.1.1", + "resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.1.tgz", + "integrity": "sha512-JoX0apGbHaUJBNl6yF+p6JAFYZ666/hhCGKN5t9QFjbJQKUU/g8MNbFDbvfrgKXvI1QpZplPOnwIo99lX/AAmA==", + "dev": true, + "optional": true, + "peer": true, + "engines": { + "node": ">=6" + } + }, "node_modules/ansi-escapes": { "version": "4.3.2", "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz", @@ -8214,6 +8225,20 @@ "node": ">=10.13.0" } }, + "node_modules/enquirer": { + "version": "2.3.6", + "resolved": "https://registry.npmjs.org/enquirer/-/enquirer-2.3.6.tgz", + "integrity": "sha512-yjNnPr315/FjS4zIsUxYguYUPP2e1NK4d7E7ZOLiyYCcbFBiTMyID+2wvm2w6+pZ/odMA7cRkjhsPbltwBOrLg==", + "dev": true, + "optional": true, + "peer": true, + "dependencies": { + "ansi-colors": "^4.1.1" + }, + "engines": { + "node": ">=8.6" + } + }, "node_modules/ensure-posix-path": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz", @@ -25157,9 +25182,9 @@ "integrity": "sha512-+Gwo89YK1OFi6oubTlah/zPxxzMNaMLy+inECAYI646KIFdzzhAsKWb3z5tSOu5Ff7no4isRV64rWfMSKLZclw==" }, "@primer/react": { - "version": "34.6.0", - "resolved": "https://registry.npmjs.org/@primer/react/-/react-34.6.0.tgz", - "integrity": "sha512-a0Mh6YmpEyQF6ad0mnfOJoC+y1heDM4uuvBcQQKJQ28DVeif5mn+slCD2C9ZQvnhkl4qnh3iqXOTxmKN5fCHNQ==", + "version": "34.7.1", + "resolved": "https://registry.npmjs.org/@primer/react/-/react-34.7.1.tgz", + "integrity": "sha512-9OLRo3N1/B/jqb7aJPY7xmtyKM8afZlmWLnEOmT8LOCmuwPiRXI+4GsJjaV9RPx3h8rUXBQwpaYZGDDj9+/OjA==", "requires": { "@primer/behaviors": "1.1.0", "@primer/octicons-react": "16.1.1", @@ -26158,6 +26183,14 @@ "string-width": "^4.1.0" } }, + "ansi-colors": { + "version": "4.1.1", + "resolved": "https://registry.npmjs.org/ansi-colors/-/ansi-colors-4.1.1.tgz", + "integrity": "sha512-JoX0apGbHaUJBNl6yF+p6JAFYZ666/hhCGKN5t9QFjbJQKUU/g8MNbFDbvfrgKXvI1QpZplPOnwIo99lX/AAmA==", + "dev": true, + "optional": true, + "peer": true + }, "ansi-escapes": { "version": "4.3.2", "resolved": "https://registry.npmjs.org/ansi-escapes/-/ansi-escapes-4.3.2.tgz", @@ -28960,6 +28993,17 @@ "tapable": "^2.2.0" } }, + "enquirer": { + "version": "2.3.6", + "resolved": "https://registry.npmjs.org/enquirer/-/enquirer-2.3.6.tgz", + "integrity": "sha512-yjNnPr315/FjS4zIsUxYguYUPP2e1NK4d7E7ZOLiyYCcbFBiTMyID+2wvm2w6+pZ/odMA7cRkjhsPbltwBOrLg==", + "dev": true, + "optional": true, + "peer": true, + "requires": { + "ansi-colors": "^4.1.1" + } + }, "ensure-posix-path": { "version": "1.1.1", "resolved": "https://registry.npmjs.org/ensure-posix-path/-/ensure-posix-path-1.1.1.tgz", diff --git a/package.json b/package.json index a9fcbfbcb6..8a2cc8f526 100644 --- a/package.json +++ b/package.json @@ -11,9 +11,9 @@ "dependencies": { "@github/failbot": "0.8.0", "@primer/css": "^19.4.0", + "@primer/react": "^34.7.1", "@primer/octicons": "17.0.0", "@primer/octicons-react": "17.0.0", - "@primer/react": "^34.6.0", "@react-aria/ssr": "^3.1.0", "accept-language-parser": "^1.5.0", "ajv": "^8.9.0", diff --git a/pages/_app.tsx b/pages/_app.tsx index 2c5e47499a..5b5fd697b8 100644 --- a/pages/_app.tsx +++ b/pages/_app.tsx @@ -2,7 +2,7 @@ import React, { useEffect } from 'react' import App from 'next/app' import type { AppProps, AppContext } from 'next/app' import Head from 'next/head' -import { useTheme, ThemeProvider } from '@primer/react' +import { ThemeProvider, ThemeProviderProps } from '@primer/react' import { SSRProvider } from '@react-aria/ssr' import { defaultComponentThemeProps, getThemeProps } from 'components/lib/getThemeProps' @@ -14,7 +14,7 @@ import { LanguagesContext, LanguagesContextT } from 'components/context/Language type MyAppProps = AppProps & { csrfToken: string - themeProps: typeof defaultComponentThemeProps + themeProps: typeof defaultComponentThemeProps & Pick languagesContext: LanguagesContextT } const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext }: MyAppProps) => { @@ -51,9 +51,13 @@ const MyApp = ({ Component, pageProps, csrfToken, themeProps, languagesContext } - + - @@ -76,15 +80,4 @@ MyApp.getInitialProps = async (appContext: AppContext) => { } } -const SetTheme = ({ themeProps }: { themeProps: typeof defaultComponentThemeProps }) => { - // Cause primer/components to re-evaluate the 'auto' color mode on client side render - const { setColorMode } = useTheme() - useEffect(() => { - setTimeout(() => { - setColorMode(themeProps.colorMode as any) - }) - }, []) - return null -} - export default MyApp From 63eee1f3243fb7dad620ee0ba83db1a4aac82f9e Mon Sep 17 00:00:00 2001 From: Sarah Edwards Date: Mon, 21 Mar 2022 17:01:08 -0700 Subject: [PATCH 17/18] remove beta note for restricting runners to workflows (#26083) --- .../managing-access-to-self-hosted-runners-using-groups.md | 1 - data/reusables/actions/restrict-runner-workflow-beta.md | 7 ------- 2 files changed, 8 deletions(-) delete mode 100644 data/reusables/actions/restrict-runner-workflow-beta.md diff --git a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md index a936ce68b3..cfc81438f0 100644 --- a/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md +++ b/content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md @@ -14,7 +14,6 @@ shortTitle: Manage access to runners {% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %} -{% data reusables.actions.restrict-runner-workflow-beta %} ## About self-hosted runner groups diff --git a/data/reusables/actions/restrict-runner-workflow-beta.md b/data/reusables/actions/restrict-runner-workflow-beta.md deleted file mode 100644 index 77949eb08b..0000000000 --- a/data/reusables/actions/restrict-runner-workflow-beta.md +++ /dev/null @@ -1,7 +0,0 @@ -{% if restrict-groups-to-workflows %} -{% note %} - -**Note:** Configuring the workflows that can access a runner group is currently in beta and subject to change. - -{% endnote %} -{% endif %} From ad3d0cd9652281edc31418e1fa42ce9fa18acf93 Mon Sep 17 00:00:00 2001 From: Courtney Wilson <77312589+cmwilson21@users.noreply.github.com> Date: Tue, 22 Mar 2022 05:38:44 -0500 Subject: [PATCH 18/18] Renaming repo workflow update #15575 (#16144) --- .../renaming-a-repository.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md index c089e88750..7d86a30d4d 100644 --- a/content/repositories/creating-and-managing-repositories/renaming-a-repository.md +++ b/content/repositories/creating-and-managing-repositories/renaming-a-repository.md @@ -36,11 +36,11 @@ If you plan to rename a repository that has a {% data variables.product.prodname {% endif %} -{% tip %} +{% note %} -**Tip:** {% data reusables.organizations.owners-and-admins-can %} rename a repository. {% data reusables.organizations.new-repo-permissions-more-info %} +**Note:** {% data variables.product.prodname_dotcom %} will not redirect calls to an action hosted by a renamed repository. Any workflow that uses that action will fail with the error `repository not found`. Instead, create a new repository and action with the new name and archive the old repository. For more information, see "[Archiving repositories](/repositories/archiving-a-github-repository/archiving-repositories)." -{% endtip %} +{% endnote %} {% warning %}