New translation batch for pt (#25577)

* Add crowdin translations

* Run script/i18n/homogenize-frontmatter.js

* Run script/i18n/fix-translation-errors.js

* Run script/i18n/lint-translation-files.js --check parsing

* run script/i18n/reset-files-with-broken-liquid-tags.js --language=pt

* run script/i18n/reset-known-broken-translation-files.js

Author: docubot

translations/pt-BR/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-email-preferences/setting-your-commit-email-address.md

@@ -35,7 +35,7 @@ Para operações com base na web do Git, você pode definir seu endereço de e-m
 
 {% note %}
 
-**Note**: {% data reusables.user-settings.no-verification-disposable-emails %}
+**Observação**: {% data reusables.user-settings.no-verification-disposable-emails %}
 
 {% endnote %}
 

translations/pt-BR/content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -479,10 +479,40 @@ Cor de fundo do selo. Pode ser: `branco`, `amarelo`, `azul`, `verde`, `laranja`,
 
 ### `branding.icon`
 
-Nome do ícone [Feather](https://feathericons.com/) (pena) para usar. <!-- 
+The name of the v4.28.0 [Feather](https://feathericons.com/) icon to use. Brand icons are omitted as well as the following:
+
+<table>
+<tr>
+<td>coffee</td>
+<td>colunas</td>
+<td>divide-circle</td>
+<td>divide-square</td>
+</tr>
+<tr>
+<td>divide</td>
+<td>frown</td>
+<td>hexagon</td>
+<td>Chave</td>
+</tr>
+<tr>
+<td>meh</td>
+<td>mouse-pointer</td>
+<td>smile</td>
+<td>ferramenta</td>
+</tr>
+<tr>
+<td>x-octagon</td>
+<td></td>
+<td></td>
+<td></td>
+</tr>
+</table>
+
+Here is an exhaustive list of all currently supported icons:
+
+
+<!-- 
   This table should match the icon list in `app/models/repository_actions/icons.rb` in the internal github repo.
-  This table does not match the latest version the feather library. 
-  (Brand icons are omitted, and our supported list is not necessarily up-to-date with the latest version of the feather icon library.)
   To support a new icon, update `app/models/repository_actions/icons.rb` and add the svg to `/static/images/icons/feather` in the internal github repo. 
 -->
 

translations/pt-BR/content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md

@@ -15,6 +15,13 @@ miniTocMaxHeadingLevel: 3
 
 ## Monitorando seus fluxos de trabalho
 
+{% if github-runner-dashboard %}
+### Monitoring your current jobs in your organization or enterprise
+
+{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+
+{% endif %}
+
 {% ifversion fpt or ghae or ghes > 3.0 or ghec %}
 
 ### Usar o gráfico de visualização

translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md

@@ -86,7 +86,7 @@ A tabela a seguir mostra as permissões concedidas ao `GITHUB_TOKEN` por padrão
 | Verificações | leitura/gravação                    | nenhum                            | leitura                                            |
 | Conteúdo     | leitura/gravação                    | leitura                           | leitura                                            |
 | Implantações | leitura/gravação                    | nenhum                            | read |{% ifversion fpt or ghec %}
-| id-token     | leitura/gravação                    | nenhum                            | read 
+| id-token     | nenhum                              | nenhum                            | read 
 {% endif %}
 | Problemas    | leitura/gravação                    | nenhum                            | leitura                                            |
 | metadados    | leitura                             | leitura                           | leitura                                            |

translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md

@@ -141,6 +141,16 @@ Neste exemplo, a injeção de script não tem sucesso:
 
 Com esta abordagem, o valor da expressão de {% raw %}`${{ github.event.issue.title }}`{% endraw %} é armazenado na memória e usada como uma variável e não interage com o processo de geração de script. Além disso, considere usar variáveis do shell de citação dupla para evitar [divisão de palavras](https://github.com/koalaman/shellcheck/wiki/SC2086), mas esta é [uma das muitas](https://mywiki.wooledge.org/BashPitfalls) recomendações gerais para escrever scripts de shell e não é específica para {% data variables.product.prodname_actions %}.
 
+{% ifversion fpt or ghec %}
+### Using starter workflows for code scanning
+
+{% data reusables.advanced-security.starter-workflows-beta %}
+{% data variables.product.prodname_code_scanning_capc %} allows you to find security vulnerabilities before they reach production. {% data variables.product.product_name %} provides starter workflows for {% data variables.product.prodname_code_scanning %}. You can use these suggested workflows to construct your {% data variables.product.prodname_code_scanning %} workflows, instead of starting from scratch. {% data variables.product.company_short%}'s workflow, the {% data variables.product.prodname_codeql_workflow %}, is powered by {% data variables.product.prodname_codeql %}. There are also third-party starter workflows available.
+
+For more information, see "[About {% data variables.product.prodname_code_scanning %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning)" and "[Setting up {% data variables.product.prodname_code_scanning %} using starter workflows](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository#setting-up-code-scanning-using-starter-workflows)."
+
+{% endif %}
+
 ### Restringir permissões para tokens
 
 Para ajudar a mitigar o risco de um token exposto, considere restringir as permissões atribuídas. Para obter mais informações, consulte "[Modificar as permissões para o GITHUB_TOKEN](/actions/reference/authentication-in-a-workflow#modifying-the-permissions-for-the-github_token)".

translations/pt-BR/content/actions/using-github-hosted-runners/index.md

@@ -7,6 +7,7 @@ versions:
   ghes: '*'
 children:
   - /about-github-hosted-runners
+  - /monitoring-your-current-jobs
   - /customizing-github-hosted-runners
 shortTitle: Usar executores hospedados no GitHub
 ---

translations/pt-BR/content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md

@@ -0,0 +1,30 @@
+---
+title: Monitoring your current jobs
+intro: 'Monitor how {% data variables.product.prodname_dotcom %}-hosted runners are processing jobs in your organization or enterprise, and identify any related constraints.'
+versions:
+  feature: github-runner-dashboard
+shortTitle: Monitoring your current jobs
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Viewing active jobs in your organization or enterprise
+
+You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
+
+{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.github-hosted-runners-table-entry %}
+1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
+
+  ![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png)
+
+## Viewing queued jobs in your organization or enterprise
+
+{% data variables.product.prodname_dotcom %}-hosted runners allow you to run jobs concurrently, and the maximum number of concurrent jobs will vary depending on your plan. If you reach the maximum number of concurrent jobs, any new jobs will start to enter a queue. To find out more about the number of concurrent jobs available to your plan, see "[Usage limits, billing, and administration](/actions/learn-github-actions/usage-limits-billing-and-administration)."
+
+The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
+
+{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
+{% data reusables.github-actions.github-hosted-runners-table-entry %}
+1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`. ![Screenshot of the maximum jobs for an account](/assets/images/help/settings/github-hosted-runners-max-jobs.png)

translations/pt-BR/content/actions/using-jobs/using-concurrency.md

@@ -17,3 +17,8 @@ miniTocMaxHeadingLevel: 4
 
 {% data reusables.actions.jobs.section-using-concurrency-jobs %}
 
+{% if github-runner-dashboard %}
+## Monitoring your current jobs in your organization or enterprise
+
+{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
+{% endif %}

translations/pt-BR/content/actions/using-workflows/creating-starter-workflows-for-your-organization.md

@@ -24,6 +24,8 @@ topics:
 
 {% data reusables.actions.workflow-organization-templates %}
 
+{% data reusables.actions.starter-workflow-categories %}
+
 ## Criando um fluxo de trabalho inicial
 
 Os fluxos de trabalho iniciantes podem ser criados pelos usuários com acesso de gravação ao repositório `.github` da organização. Eles poderão ser usados pelos integrantes da organização com permissão para criar fluxos de trabalho.

translations/pt-BR/content/actions/using-workflows/reusing-workflows.md

@@ -63,7 +63,7 @@ A atribuição de executores hospedados em {% data variables.product.prodname_do
 
 {% endif %}
 
-Called workflows that are owned by the same user or organization{% ifversion ghes or ghec or ghae %} or enterprise{% endif %} as the caller workflow can access self-hosted runners from the caller's context. Isso significa que um fluxo de trabalho chamado pode acessar executores auto-hospedados que estão:
+Fluxos de trabalho chamados que são propriedade do mesmo usuário ou organização{% ifversion ghes or ghec or ghae %} ou empresa{% endif %}, uma vez que o fluxo de trabalho de chamadas pode acessar runners auto-hospedados no contexto do invocador. Isso significa que um fluxo de trabalho chamado pode acessar executores auto-hospedados que estão:
 * No repositório de chamada
 * Na organização{% ifversion ghes or ghec or ghae %} ou empresa {% endif %}do repositório de chamadas, desde que o executor tenha sido disponibilizado para o repositório de chamada