New translation batch for pt (#28805)

* 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 * Check in pt CSV report
github · Octomerger · Jun 29, 2022 · Jun 29, 2022 · Jun 29, 2022 · Jun 29, 2022
commit 6deb3a6107845a25429267c7a7cf03729e65ee4d
diff --git a/translations/log/pt-resets.csv b/translations/log/pt-resets.csv
@@ -24,10 +24,11 @@ translations/pt-BR/content/code-security/code-scanning/integrating-with-code-sca
 translations/pt-BR/content/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-runner-in-your-ci-system.md,broken liquid tags
 translations/pt-BR/content/code-security/secret-scanning/about-secret-scanning.md,broken liquid tags
 translations/pt-BR/content/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema.md,broken liquid tags
+translations/pt-BR/content/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-visual-studio-code.md,broken liquid tags
+translations/pt-BR/content/copilot/quickstart.md,broken liquid tags
 translations/pt-BR/content/desktop/installing-and-configuring-github-desktop/overview/creating-your-first-repository-using-github-desktop.md,broken liquid tags
 translations/pt-BR/content/education/explore-the-benefits-of-teaching-and-learning-with-github-education/use-github-for-your-schoolwork/why-wasnt-my-application-for-a-student-developer-pack-approved.md,broken liquid tags
 translations/pt-BR/content/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud.md,broken liquid tags
-translations/pt-BR/content/github/index.md,Listed in localization-support#489
 translations/pt-BR/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
 translations/pt-BR/content/organizations/organizing-members-into-teams/about-teams.md,broken liquid tags
 translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,broken liquid tags

diff --git a/...ng-your-github-profile/customizing-your-profile/managing-your-profile-readme.md b/...ng-your-github-profile/customizing-your-profile/managing-your-profile-readme.md
@@ -56,7 +56,7 @@ O GitHub irá exibir o README do seu perfil na sua página de perfil se todas as
 
   O arquivo README gerado é pré-preenchido com um modelo para dar alguma inspiração para o README do seu perfil. ![Arquivo README com modelo pré-preenchido](/assets/images/help/repository/personal-repository-readme-template.png)
 
-Para obter um resumo todos os emojis disponíveis e seus códigos, consulte "[Folha de dicas de Emoji](http://www.emoji-cheat-sheet.com/)".
+Para obter um resumo todos os emojis disponíveis e seus códigos, consulte "[Folha de dicas de Emoji](https://www.webfx.com/tools/emoji-cheat-sheet/)".
 
 ## Remover um README do perfil
 

diff --git a/...ging-your-github-profile/customizing-your-profile/personalizing-your-profile.md b/...ging-your-github-profile/customizing-your-profile/personalizing-your-profile.md
@@ -30,7 +30,7 @@ Ao se inscrever em uma conta, o {% data variables.product.product_name %} fornec
 
 **Observação{% ifversion ghec %}s{% endif %}**: {% ifversion ghec %}
 
-* {% endif %}A imagem do seu perfil deve ser um arquivo PNG, JPG ou GIF com tamanho inferior a 1 MB. Para melhor qualidade de renderização, recomendamos uma imagem de aproximadamente 500 por 500 pixels.
+* {% endif %}Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. Para melhor qualidade de renderização, recomendamos uma imagem de aproximadamente 500 por 500 pixels.
 {% ifversion ghec %}* As imagens de perfil do Gravatar não são compatíveis com {% data variables.product.prodname_emus %}.{% endif %}
 
 {% endnote %}
@@ -39,14 +39,14 @@ Ao se inscrever em uma conta, o {% data variables.product.product_name %} fornec
 
 {% data reusables.user-settings.access_settings %}
 2. Em **Profile Picture** (Imagem de perfil), clique em {% octicon "pencil" aria-label="The edit icon" %} **Edit** (Editar). ![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png)
-3. Clique em **Upload a photo...** (Fazer upload de uma foto...). ![Atualizar imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png)
+3. Click **Upload a photo...**.{% ifversion not ghae %} ![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %}
 3. Recorte sua imagem. Quando terminar, clique em **Set new profile picture** (Definir nova imagem de perfil). ![Cortar foto carregada](/assets/images/help/profile/avatar_crop_and_save.png)
 
 ### Redefinir sua imagem de perfil para a identicon
 
 {% data reusables.user-settings.access_settings %}
 2. Em **Profile Picture** (Imagem de perfil), clique em {% octicon "pencil" aria-label="The edit icon" %} **Edit** (Editar). ![Editar imagem de perfil](/assets/images/help/profile/edit-profile-photo.png)
-3. Para reverter para sua identicon, clique em **Remove photo** (Remover foto). Se o seu endereço de e-mail está associado a um [Gravatar](https://en.gravatar.com/), você não pode reverter para sua identicon. Em vez disso, clique em **Revert to Gravatar** (Reverter para Gravatar). ![Atualizar imagem de perfil](/assets/images/help/profile/edit-profile-picture-options.png)
+3. Para reverter para sua identicon, clique em **Remove photo** (Remover foto). {% ifversion not ghae %}If your email address is associated with a [Gravatar](https://en.gravatar.com/), you cannot revert to your identicon. Em vez disso, clique em **Revert to Gravatar** (Reverter para Gravatar). ![Update profile picture](/assets/images/help/profile/edit-profile-picture-options.png){% endif %}
 
 ## Alterar seu nome de perfil
 

diff --git a/...ns/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-go.md b/...ns/pt-BR/content/actions/automating-builds-and-tests/building-and-testing-go.md
@@ -0,0 +1,217 @@
+---
+title: Building and testing Go
+intro: You can create a continuous integration (CI) workflow to build and test your Go project.
+versions:
+  fpt: '*'
+  ghes: '*'
+  ghae: '*'
+  ghec: '*'
+type: tutorial
+topics:
+  - CI
+shortTitle: Build & test Go
+---
+
+{% data reusables.actions.enterprise-beta %}
+{% data reusables.actions.enterprise-github-hosted-runners %}
+
+## Introdução
+
+This guide shows you how to build, test, and publish a Go package.
+
+{% ifversion ghae %}
+{% data reusables.actions.self-hosted-runners-software %}
+{% else %} {% data variables.product.prodname_dotcom %}-hosted runners have a tools cache with preinstalled software, which includes the dependencies for Go. For a full list of up-to-date software and the preinstalled versions of Go, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/using-github-hosted-runners/about-github-hosted-runners#preinstalled-software)."
+{% endif %}
+
+## Pré-requisitos
+
+Você já deve estar familiarizado com a sintaxe YAML e como é usado com {% data variables.product.prodname_actions %}. Para obter mais informações, consulte "[Sintaxe de fluxo de trabalho para o {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions)".
+
+We recommend that you have a basic understanding of the Go language. For more information, see [Getting started with Go](https://golang.org/doc/tutorial/getting-started).
+
+## Using the Go starter workflow
+
+{% data variables.product.prodname_dotcom %} provides a Go starter workflow that should work for most Go projects. Este guia inclui exemplos que você pode usar para personalizar o fluxo de trabalho inicial. For more information, see the [Go starter workflow](https://github.com/actions/starter-workflows/blob/main/ci/go.yml).
+
+Para iniciar rapidamente, adicione o fluxo de trabalho inicial para o diretório `.github/workflows` do seu repositório.
+
+```yaml{:copy}
+name: Go package
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+
+      - name: Set up Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: 1.15
+
+      - name: Build
+        run: go build -v ./...
+
+      - name: Test
+        run: go test -v ./...
+```
+
+## Specifying a Go version
+
+The easiest way to specify a Go version is by using the `setup-go` action provided by {% data variables.product.prodname_dotcom %}. For more information see, the [`setup-go` action](https://github.com/actions/setup-go/).
+
+To use a preinstalled version of Go on a {% data variables.product.prodname_dotcom %}-hosted runner, pass the relevant version to the `go-version` property of the `setup-go` action. This action finds a specific version of Go from the tools cache on each runner, and adds the necessary binaries to `PATH`. Estas alterações persistirão para o resto do trabalho.
+
+The `setup-go` action is the recommended way of using Go with {% data variables.product.prodname_actions %}, because it helps ensure consistent behavior across different runners and different versions of Go. If you are using a self-hosted runner, you must install Go and add it to `PATH`.
+
+### Using multiple versions of Go
+
+```yaml{:copy}
+name: Go
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go-version: [ '1.14', '1.15', '1.16.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go {% raw %}${{ matrix.go-version }}{% endraw %}
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
+      # You can test your matrix by printing the current Go version
+      - name: Display Go version
+        run: go version
+```
+
+### Using a specific Go version
+
+You can configure your job to use a specific version of Go, such as `1.16.2`. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. This example uses the latest patch release of Go 1.16:
+
+```yaml{:copy}
+      - name: Setup Go 1.16.x
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          # Semantic version range syntax or exact version of Go
+          go-version: '1.16.x'
+```
+
+## Instalar dependências
+
+You can use `go get` to install dependencies:
+
+```yaml{:copy}
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+      - name: Install dependencies
+        run: |
+          go get .
+          go get example.lab/octo-examplemodule
+          go get example.lab/[email protected]
+```
+
+{% ifversion actions-caching %}
+
+### Memorizar dependências
+
+You can cache and restore the dependencies using the [`setup-go` action](https://github.com/actions/setup-go). By default, caching is disabled, but you can set the `cache` parameter to `true` to enable it.
+
+When caching is enabled, the `setup-go` action searches for the dependency file, `go.sum`, in the repository root and uses the hash of the dependency file as a part of the cache key.
+
+```yaml{:copy}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+          cache: true
+```
+
+Alternatively, you can use the `cache-dependency-path` parameter for cases when multiple dependency files are used, or when they are located in different subdirectories.
+
+```yaml{:copy}
+      - uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.17'
+          cache: true
+          cache-dependency-path: subdir/go.sum
+```
+
+Se você tiver um requisito personalizado ou precisar de melhores controles para cache, você poderá usar a ação [`cache`](https://github.com/marketplace/actions/cache). Para obter mais informações, consulte "[Memorizar dependências para acelerar fluxos de trabalho](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)".
+
+{% endif %}
+
+## Criar e testar seu código
+
+Você pode usar os mesmos comandos usados localmente para criar e testar seu código. This example workflow demonstrates how to use `go build` and `go test` in a job:
+
+```yaml{:copy}
+name: Go
+on: [push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: '1.16.x'
+      - name: Install dependencies
+        run: go get .
+      - name: Build
+        run: go build -v ./...
+      - name: Test with the Go CLI
+        run: go test
+```
+
+## Empacotar dados do fluxo de trabalho como artefatos
+
+Após a conclusão de um fluxo de trabalho, você poderá fazer o upload dos artefatos resultantes para análise. Por exemplo, é possível que você precise salvar os arquivos de registro, os despejos de núcleo, os resultados de teste ou capturas de tela. O exemplo a seguir demonstra como você pode usar a ação `upload-artefato` para fazer o upload de resultados de testes.
+
+For more information, see "[Storing workflow data as artifacts](/actions/using-workflows/storing-workflow-data-as-artifacts)."
+
+```yaml{:copy}
+name: Upload Go test results
+
+on: [push]
+
+jobs:
+  build:
+
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go-version: [ '1.14', '1.15', '1.16.x' ]
+
+    steps:
+      - uses: {% data reusables.actions.action-checkout %}
+      - name: Setup Go
+        uses: {% data reusables.actions.action-setup-go %}
+        with:
+          go-version: {% raw %}${{ matrix.go-version }}{% endraw %}
+      - name: Install dependencies
+        run: go get .
+      - name: Test with Go
+        run: go test -json > TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
+      - name: Upload Go test results
+        uses: {% data reusables.actions.action-upload-artifact %}
+        with:
+          name: Go-results-{% raw %}${{ matrix.go-version }}{% endraw %}
+          path: TestResults-{% raw %}${{ matrix.go-version }}{% endraw %}.json
+```
diff --git a/...t-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md b/...t-BR/content/actions/automating-builds-and-tests/building-and-testing-python.md
@@ -57,7 +57,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.6", "3.7", "3.8", "3.9"]
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
 
     steps:
       - uses: {% data reusables.actions.action-checkout %}
@@ -114,7 +114,7 @@ trabalhos:
       # Você pode usar as versões do PyPy em python-version.
       # For example, {% ifversion actions-node16-action %}pypy-2.7 and pypy-3.8{% else %}pypy2 and pypy3{% endif %}
       matrix:
-        python-version: ["2.7", "3.6", "3.7", "3.8", "3.9"]
+        python-version: ["2.7", "3.7", "3.8", "3.9", "3.10"]
 
     steps:
       - uses: {% data reusables.actions.action-checkout %}
@@ -129,7 +129,7 @@ trabalhos:
 
 ### Usar uma versão específica do Python
 
-Você pode configurar uma versão específica do python. Por exemplo, 3,8. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a última versão secundária do Python 3.
+Você pode configurar uma versão específica do python. For example, 3.9. Como alternativa, você pode usar a sintaxe da versão semântica para obter a última versão secundária. Este exemplo usa a última versão secundária do Python 3.
 
 ```yaml{:copy}
 name: Python package
@@ -173,12 +173,12 @@ jobs:
     strategy:
       matrix:
         os: [ubuntu-latest, macos-latest, windows-latest]
-        python-version: ["3.6", "3.7", "3.8", "3.9", {% ifversion actions-node16-action %}pypy-2.7, pypy-3.8{% else %}pypy2, pypy3{% endif %}]
+        python-version: ["3.7", "3.8", "3.9", "3.10", {% ifversion actions-node16-action %}pypy-2.7, pypy-3.8{% else %}pypy2, pypy3{% endif %}]
         exclude:
           - os: macos-latest
-            python-version: "3.6"
+            python-version: "3.7"
           - os: windows-latest
-            python-version: "3.6"
+            python-version: "3.7"
 ```
 
 ### Usar a versão padrão do Python
@@ -238,7 +238,7 @@ steps:
 - uses: {% data reusables.actions.action-checkout %}
 - uses: {% data reusables.actions.action-setup-python %}
   with:
-    python-version: '3.9'
+    python-version: '3.10'
     cache: 'pip'
 - run: pip install -r requirements.txt
 - run: pip test
@@ -315,7 +315,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python: ["3.7", "3.8", "3.9"]
+        python: ["3.8", "3.9", "3.10"]
 
     steps:
       - uses: {% data reusables.actions.action-checkout %}
@@ -347,7 +347,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.6", "3.7", "3.8", "3.9"]
+        python-version: ["3.7", "3.8", "3.9", "3.10"]
 
     steps:
       - uses: {% data reusables.actions.action-checkout %}

diff --git a/translations/pt-BR/content/actions/automating-builds-and-tests/index.md b/translations/pt-BR/content/actions/automating-builds-and-tests/index.md
@@ -18,6 +18,7 @@ redirect_from:
   - /actions/automating-builds-and-tests/building-and-testing-nodejs-or-python
 children:
   - /about-continuous-integration
+  - /building-and-testing-go
   - /building-and-testing-java-with-ant
   - /building-and-testing-java-with-gradle
   - /building-and-testing-java-with-maven