New translation batch for pt (#23918)
* 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/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
This commit is contained in:
docubot
@@ -396,6 +396,7 @@ translations/pt-BR/content/code-security/code-scanning/automatically-scanning-yo
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/index.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/running-codeql-code-scanning-in-a-container.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/setting-up-code-scanning-for-a-repository.md,rendering error
|
||||
translations/pt-BR/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/tracking-code-scanning-alerts-in-issues-using-task-lists.md,rendering error
|
||||
@@ -769,7 +770,9 @@ translations/pt-BR/content/organizations/restricting-access-to-your-organization
|
||||
translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/denying-access-to-a-previously-approved-oauth-app-for-your-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/disabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/restricting-access-to-your-organizations-data/enabling-oauth-app-access-restrictions-for-your-organization.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-github-packages.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/installing-a-package.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/introduction-to-github-packages.md,rendering error
|
||||
translations/pt-BR/content/packages/learn-github-packages/publishing-a-package.md,rendering error
|
||||
translations/pt-BR/content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md,rendering error
|
||||
@@ -794,6 +797,7 @@ translations/pt-BR/content/pages/getting-started-with-github-pages/index.md,rend
|
||||
translations/pt-BR/content/pages/getting-started-with-github-pages/unpublishing-a-github-pages-site.md,rendering error
|
||||
translations/pt-BR/content/pages/getting-started-with-github-pages/using-submodules-with-github-pages.md,rendering error
|
||||
translations/pt-BR/content/pages/index.md,rendering error
|
||||
translations/pt-BR/content/pages/quickstart.md,rendering error
|
||||
translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-github-pages-and-jekyll.md,rendering error
|
||||
translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/about-jekyll-build-errors-for-github-pages-sites.md,rendering error
|
||||
translations/pt-BR/content/pages/setting-up-a-github-pages-site-with-jekyll/adding-a-theme-to-your-github-pages-site-using-jekyll.md,rendering error
|
||||
@@ -812,7 +816,9 @@ translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/gettin
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/adding-a-pull-request-to-the-merge-queue.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/index.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/index.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches.md,rendering error
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-comparing-branches-in-pull-requests.md,rendering error
|
||||
|
||||
|
@@ -45,7 +45,7 @@ In the tutorial, you will first make a workflow file that uses the [`andymckay/l
|
||||
issues: write{% endif %}
|
||||
steps:
|
||||
- name: Label issues
|
||||
uses: andymckay/labeler@5c59dabdfd4dd5bd9c6e6d255b01b9d764af4414
|
||||
uses: andymckay/labeler@e6c4322d0397f3240f0e7e30a33b5c5df2d39e90
|
||||
with:
|
||||
add-labels: "triage"
|
||||
repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
|
||||
|
||||
@@ -161,6 +161,13 @@ This workflow scans:
|
||||
|
||||
If your code requires a specific operating system to compile, you can configure the operating system in your {% data variables.product.prodname_codeql_workflow %}. Edit the value of `jobs.analyze.runs-on` to specify the operating system for the machine that runs your {% data variables.product.prodname_code_scanning %} actions. {% ifversion ghes %}You specify the operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% else %}
|
||||
|
||||
``` yaml
|
||||
jobs:
|
||||
analyze:
|
||||
name: Analyze
|
||||
runs-on: [ubuntu-latest]
|
||||
```
|
||||
|
||||
If you choose to use a self-hosted runner for code scanning, you can specify an operating system by using an appropriate label as the second element in a two-element array, after `self-hosted`.{% endif %}
|
||||
|
||||
``` yaml
|
||||
@@ -170,12 +177,14 @@ jobs:
|
||||
runs-on: [self-hosted, ubuntu-latest]
|
||||
```
|
||||
|
||||
{% ifversion fpt or ghec %}For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."{% endif %}
|
||||
|
||||
{% data variables.product.prodname_codeql %} {% data variables.product.prodname_code_scanning %} supports the latest versions of Ubuntu, Windows, and macOS. Typical values for this setting are therefore: `ubuntu-latest`, `windows-latest`, and `macos-latest`. For more information, see {% ifversion ghes %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#self-hosted-runners)" and "[Using labels with self-hosted runners](/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners){% else %}"[Workflow syntax for GitHub Actions](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idruns-on){% endif %}."
|
||||
|
||||
{% ifversion ghes %}You must ensure that Git is in the PATH variable on your self-hosted runners.{% else %}If you use a self-hosted runner, you must ensure that Git is in the PATH variable.{% endif %}
|
||||
|
||||
For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)" and "[Adding self-hosted runners](/actions/hosting-your-own-runners/adding-self-hosted-runners)."
|
||||
|
||||
For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis{% ifversion not ghes %} on self-hosted machines{% endif %}, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
|
||||
|
||||
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
|
||||
## Specifying the location for {% data variables.product.prodname_codeql %} databases
|
||||
|
||||
|
||||
@@ -22,6 +22,7 @@ children:
|
||||
- /tracking-code-scanning-alerts-in-issues-using-task-lists
|
||||
- /configuring-code-scanning
|
||||
- /about-code-scanning-with-codeql
|
||||
- /recommended-hardware-resources-for-running-codeql
|
||||
- /configuring-the-codeql-workflow-for-compiled-languages
|
||||
- /troubleshooting-the-codeql-workflow
|
||||
- /running-codeql-code-scanning-in-a-container
|
||||
|
||||
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: Recommended hardware resources for running CodeQL
|
||||
shortTitle: Hardware resources for CodeQL
|
||||
intro: 'Recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis on self-hosted machines, based on the size of your codebase.'
|
||||
product: '{% data reusables.gated-features.code-scanning %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
topics:
|
||||
- Advanced Security
|
||||
- Code scanning
|
||||
- CodeQL
|
||||
- Repositories
|
||||
- Integration
|
||||
- CI
|
||||
|
||||
---
|
||||
You can set up {% data variables.product.prodname_codeql %} on {% data variables.product.prodname_actions %} or on an external CI system. {% data variables.product.prodname_codeql %} is fully compatible with {% data variables.product.prodname_dotcom %}-hosted runners on {% data variables.product.prodname_actions %}.
|
||||
|
||||
If you're using an external CI system, or self-hosted runners on {% data variables.product.prodname_actions %} for private repositories, you're responsible for configuring your own hardware. The optimal hardware configuration for running {% data variables.product.prodname_codeql %} may vary based on the size and complexity of your codebase, the programming languages and build systems being used, and your CI workflow setup.
|
||||
|
||||
The table below provides recommended hardware specifications for running {% data variables.product.prodname_codeql %} analysis, based on the size of your codebase. Use these as a starting point for determining your choice of hardware or virtual machine. A machine with greater resources may improve analysis performance, but may also be more expensive to maintain.
|
||||
|
||||
| Codebase size | RAM | CPU |
|
||||
|--------|--------|--------|
|
||||
| Small (<100 K lines of code) | 8 GB or higher | 2 cores |
|
||||
| Medium (100 K to 1 M lines of code) | 16 GB or higher | 4 or 8 cores |
|
||||
| Large (>1 M lines of code) | 64 GB or higher | 8 cores |
|
||||
|
||||
For all codebase sizes, we recommend using an SSD with 14 GB or more of disk space. There must be enough disk space to check out and build your code, plus additional space for data produced by {% data variables.product.prodname_codeql %}.
|
||||
@@ -28,7 +28,7 @@ redirect_from:
|
||||
|
||||
## About using the {% data variables.product.prodname_codeql_cli %} for {% data variables.product.prodname_code_scanning %}
|
||||
|
||||
You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)."
|
||||
You can use the {% data variables.product.prodname_codeql_cli %} to run {% data variables.product.prodname_code_scanning %} on code that you're processing in a third-party continuous integration (CI) system. {% data reusables.code-scanning.about-code-scanning %} For information, see "[About {% data variables.product.prodname_code_scanning %} with {% data variables.product.prodname_codeql %}](/code-security/secure-coding/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql)." For recommended specifications (RAM, CPU cores, and disk) for running {% data variables.product.prodname_codeql %} analysis, see "[Recommended hardware resources for running {% data variables.product.prodname_codeql %}](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/recommended-hardware-resources-for-running-codeql)."
|
||||
|
||||
{% data reusables.code-scanning.what-is-codeql-cli %}
|
||||
|
||||
|
||||
@@ -39,6 +39,8 @@ A typical workflow that uses the {% data variables.product.prodname_codeql_cli %
|
||||
- `codeql database analyze` to run queries to analyze each {% data variables.product.prodname_codeql %} database and summarize the results in a SARIF file. This command must be run once for each language or database.
|
||||
- `codeql github upload-results` to upload the resulting SARIF files to {% data variables.product.prodname_dotcom %}, to be displayed as code scanning alerts. This command must be run once for each language or SARIF file.
|
||||
|
||||
The {% data variables.product.prodname_codeql_runner %} is multithreaded by default. The {% data variables.product.prodname_codeql_cli %} only uses a single thread by default, but allows you to specify the amount of threads you want it to use. If you want to replicate the behavior of the {% data variables.product.prodname_codeql_runner %} to use all threads available on the machine when using the {% data variables.product.prodname_codeql_cli %}, you can pass `--threads 0` to `codeql database analyze`.
|
||||
|
||||
For more information, see "[Configuring {% data variables.product.prodname_codeql_cli %} in your CI system](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/configuring-codeql-cli-in-your-ci-system)."
|
||||
|
||||
## Examples of common uses for the {% data variables.product.prodname_codeql_cli %}
|
||||
|
||||
@@ -1,87 +1,85 @@
|
||||
---
|
||||
title: Sobre permissões para o GitHub Packages
|
||||
intro: Saiba como gerenciar as permissões dos seus pacotes.
|
||||
title: About permissions for GitHub Packages
|
||||
intro: Learn about how to manage permissions for your packages.
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
shortTitle: Sobre permissões
|
||||
shortTitle: About permissions
|
||||
---
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
As permissões para pacotes são do escopo do repositório ou do escopo de usuário/organização.
|
||||
The permissions for packages are either repository-scoped or user/organization-scoped.
|
||||
{% endif %}
|
||||
|
||||
## Permissões para pacotes com escopo do repositório
|
||||
## Permissions for repository-scoped packages
|
||||
|
||||
Um pacote com escopo de repositório herda as permissões e visibilidade do repositório que possui o pacote. Você pode encontrar um escopo de pacote para um repositório, acessando a página principal do repositório e clicando no link **Pacotes** à direita da página. {% ifversion fpt or ghec %}Para obter mais informações, consulte "[Conectar um repositório a um pacote](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
|
||||
A repository-scoped package inherits the permissions and visibility of the repository that owns the package. You can find a package scoped to a repository by going to the main page of the repository and clicking the **Packages** link to the right of the page. {% ifversion fpt or ghec %}For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package)."{% endif %}
|
||||
|
||||
Os {% data variables.product.prodname_registry %} registros abaixo usam permissões com escopo do repositório:
|
||||
The {% data variables.product.prodname_registry %} registries below use repository-scoped permissions:
|
||||
|
||||
{% ifversion not fpt or ghec %}- Docker registry (`docker.pkg.github.com`){% endif %}
|
||||
- Registro de npm
|
||||
- Registro do Rubygems
|
||||
- Registro do Apache Maven
|
||||
- Registro do NuGet
|
||||
- npm registry
|
||||
- RubyGems registry
|
||||
- Apache Maven registry
|
||||
- NuGet registry
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
## Permissões granulares para pacotes com escopo de usuário/organização
|
||||
## Granular permissions for user/organization-scoped packages
|
||||
|
||||
Pacotes com permissões granulares são escopos para uma conta de usuário pessoal ou de organização. Você pode alterar o controle de acesso e a visibilidade do pacote separadamente de um repositório que está conectado (ou vinculado) a um pacote.
|
||||
Packages with granular permissions are scoped to a personal user or organization account. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package.
|
||||
|
||||
Atualmente, apenas o {% data variables.product.prodname_container_registry %} oferece permissões granulares para os seus pacotes de imagem de contêiner.
|
||||
Currently, only the {% data variables.product.prodname_container_registry %} offers granular permissions for your container image packages.
|
||||
|
||||
## Visibilidade e permissões de acesso para imagens de contêiner
|
||||
## Visibility and access permissions for container images
|
||||
|
||||
{% data reusables.package_registry.visibility-and-access-permissions %}
|
||||
|
||||
Para obter mais informações, consulte "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
|
||||
For more information, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Sobre escopos e permissões para registros de pacotes
|
||||
## About scopes and permissions for package registries
|
||||
|
||||
Para usar ou gerenciar um pacote hospedado por um registro de pacotes, você deve usar um token com o escopo apropriado, e sua conta de usuário deve ter as permissões necessárias.
|
||||
To use or manage a package hosted by a package registry, you must use a token with the appropriate scope, and your user account must have appropriate permissions.
|
||||
|
||||
Por exemplo:
|
||||
- Para fazer o download e instalar pacotes de um repositório, seu token deve ter o escopo `read:packages` e sua conta de usuário deve ter permissão de leitura.
|
||||
- {% ifversion fpt or ghes > 3.0 or ghec %}Para excluir um pacote em {% data variables.product.product_name %}, o seu token deve ter pelo menos o escopo `delete:packages` e `read:packages`. O escopo de `repo` também é necessário para pacotes com escopo de repositórios.{% elsif ghes < 3.1 %}Para excluir uma versão especificada de um pacote privado em {% data variables.product.product_name %}, o seu token deve ter o escopo `delete:packages` e `repo`. Public packages cannot be deleted.{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
|
||||
For example:
|
||||
- To download and install packages from a repository, your token must have the `read:packages` scope, and your user account must have read permission.
|
||||
- {% ifversion fpt or ghes > 3.0 or ghec %}To delete a package on {% data variables.product.product_name %}, your token must at least have the `delete:packages` and `read:packages` scope. The `repo` scope is also required for repo-scoped packages.{% elsif ghes < 3.1 %}To delete a specified version of a private package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope. Public packages cannot be deleted.{% elsif ghae %}To delete a specified version of a package on {% data variables.product.product_name %}, your token must have the `delete:packages` and `repo` scope.{% endif %} For more information, see "{% ifversion fpt or ghes > 3.0 or ghec %}[Deleting and restoring a package](/packages/learn-github-packages/deleting-and-restoring-a-package){% elsif ghes < 3.1 or ghae %}[Deleting a package](/packages/learn-github-packages/deleting-a-package){% endif %}."
|
||||
|
||||
| Escopo | Descrição | Permissão necessária |
|
||||
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | -------------------- |
|
||||
| `read:packages` | Faça o download e instale pacotes do {% data variables.product.prodname_registry %} | leitura |
|
||||
| `write:packages` | Faça o upload e publique os pacotes em {% data variables.product.prodname_registry %} | gravação |
|
||||
| `delete:packages` | | |
|
||||
| {% ifversion fpt or ghes > 3.0 or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | | |
|
||||
| administrador | | |
|
||||
| `repo` | Faça o upload e exclua os pacotes (junto com `write:packages` ou `delete:packages`) | gravação ou admin |
|
||||
| Scope | Description | Required permission |
|
||||
| --- | --- | --- |
|
||||
|`read:packages`| Download and install packages from {% data variables.product.prodname_registry %} | read |
|
||||
|`write:packages`| Upload and publish packages to {% data variables.product.prodname_registry %} | write |
|
||||
| `delete:packages` | {% ifversion fpt or ghes > 3.0 or ghec %} Delete packages from {% data variables.product.prodname_registry %} {% elsif ghes < 3.1 %} Delete specified versions of private packages from {% data variables.product.prodname_registry %}{% elsif ghae %} Delete specified versions of packages from {% data variables.product.prodname_registry %} {% endif %} | admin |
|
||||
| `repo` | Upload and delete packages (along with `write:packages`, or `delete:packages`) | write or admin |
|
||||
|
||||
Ao criar um fluxo de trabalho de {% data variables.product.prodname_actions %}, você pode usar o `GITHUB_TOKEN` para publicar e instalar pacotes no {% data variables.product.prodname_registry %} sem precisar armazenar e gerenciar um token de acesso pessoal.
|
||||
When you create a {% data variables.product.prodname_actions %} workflow, you can use the `GITHUB_TOKEN` to publish and install packages in {% data variables.product.prodname_registry %} without needing to store and manage a personal access token.
|
||||
|
||||
For more information, see:{% ifversion fpt or ghec %}
|
||||
- "[Configurar o controle de acesso e visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
|
||||
- "[Publicando e instalando um pacote com {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
|
||||
- "[Criar um token de acesso pessoal](/github/authenticating-to-github/creating-a-personal-access-token/)"
|
||||
- "[Escopos disponíveis](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
|
||||
- "[Configuring a package’s access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)"{% endif %}
|
||||
- "[Publishing and installing a package with {% data variables.product.prodname_actions %}](/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions)"
|
||||
- "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token/)"
|
||||
- "[Available scopes](/apps/building-oauth-apps/understanding-scopes-for-oauth-apps/#available-scopes)"
|
||||
|
||||
## Mantendo acesso a pacotes nos fluxos de trabalho de {% data variables.product.prodname_actions %}
|
||||
## Maintaining access to packages in {% data variables.product.prodname_actions %} workflows
|
||||
|
||||
Para garantir que seus workflows mantenham o acesso aos seus pacotes, certifique-se de que você esteja usando o token de acesso correto do seu fluxo de trabalho e que você habilitou o acesso do {% data variables.product.prodname_actions %} para o seu pacote.
|
||||
To ensure your workflows will maintain access to your packages, ensure that you're using the right access token in your workflow and that you've enabled {% data variables.product.prodname_actions %} access to your package.
|
||||
|
||||
Para obter um contexto mais conceitual sobre {% data variables.product.prodname_actions %} ou exemplos do uso de pacotes nos fluxos de trabalho, consulte "[Gerenciar o GitHub Packages usando fluxos de trabalho do GitHub Actions](/packages/managing-github-packages-using-github-actions-workflows)".
|
||||
For more conceptual background on {% data variables.product.prodname_actions %} or examples of using packages in workflows, see "[Managing GitHub Packages using GitHub Actions workflows](/packages/managing-github-packages-using-github-actions-workflows)."
|
||||
|
||||
### Tokens de acesso
|
||||
### Access tokens
|
||||
|
||||
- Para publicar pacotes associados ao repositório do fluxo de trabalho, use `GITHUB_TOKEN`.
|
||||
- Para instalar pacotes associados a outros repositórios privados que `GITHUB_TOKEN` não consegue acessar, use um token de acesso pessoal
|
||||
- To publish packages associated with the workflow repository, use `GITHUB_TOKEN`.
|
||||
- To install packages associated with other private repositories that `GITHUB_TOKEN` can't access, use a personal access token
|
||||
|
||||
Para obter mais informações sobre `GITHUB_TOKEN` usado nos fluxos de trabalho de {% data variables.product.prodname_actions %}, consulte[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)".
|
||||
For more information about `GITHUB_TOKEN` used in {% data variables.product.prodname_actions %} workflows, see "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow#using-the-github_token-in-a-workflow)."
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
### Acesso a {% data variables.product.prodname_actions %} para imagens de contêiner
|
||||
### {% data variables.product.prodname_actions %} access for container images
|
||||
|
||||
Para garantir que seus fluxos de trabalho tenham acesso à imagem do contêiner, você deve permitir o acesso do {% data variables.product.prodname_actions %} aos repositórios em que o seu fluxo de trabalho é executado. Você pode encontrar essa configuração na página de configurações do seu pacote. Para obter mais informações, consulte "[Garantir o acesso do fluxo de trabalho para o seu pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)".
|
||||
To ensure your workflows have access to your container image, you must enable {% data variables.product.prodname_actions %} access to the repositories where your workflow is run. You can find this setting on your package's settings page. For more information, see "[Ensuring workflow access to your package](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#ensuring-workflow-access-to-your-package)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Instalar um pacote
|
||||
intro: 'Você pode instalar um pacote do {% data variables.product.prodname_registry %} e usá-lo como uma dependência no seu próprio projeto.'
|
||||
title: Installing a package
|
||||
intro: 'You can install a package from {% data variables.product.prodname_registry %} and use the package as a dependency in your own project.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /github/managing-packages-with-github-packages/installing-a-package
|
||||
@@ -17,17 +17,17 @@ versions:
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
{% data reusables.package_registry.packages-ghae-release-stage %}
|
||||
|
||||
## Sobre a instalação do pacote
|
||||
## About package installation
|
||||
|
||||
You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. Para obter mais informações, consulte "[Pesquisar pacotes no {% data variables.product.prodname_registry %}](/search-github/searching-on-github/searching-for-packages)".
|
||||
You can search on {% ifversion ghae %}{% data variables.product.product_name %}{% else %}{% data variables.product.product_location %}{% endif %} to find packages in {% data variables.product.prodname_registry %} that you can install in your own project. For more information, see "[Searching {% data variables.product.prodname_registry %} for packages](/search-github/searching-on-github/searching-for-packages)."
|
||||
|
||||
Depois de encontrar um pacote, você pode ler a descrição e as instruções de instalação e utilização na página de pacotes.
|
||||
After you find a package, you can read the package's description and installation and usage instructions on the package page.
|
||||
|
||||
## Instalar um pacote
|
||||
## Installing a package
|
||||
|
||||
Você pode instalar um pacote de {% data variables.product.prodname_registry %} usando qualquer {% ifversion fpt or ghae or ghec %}tipo de pacote cliente compatível{% else %}pacote habilitado para sua instância{% endif %}, seguindo as mesmas diretrizes gerais.
|
||||
You can install a package from {% data variables.product.prodname_registry %} using any {% ifversion fpt or ghae or ghec %}supported package client{% else %}package type enabled for your instance{% endif %} by following the same general guidelines.
|
||||
|
||||
1. Efetue a autenticação com {% data variables.product.prodname_registry %} usando as instruções para seu cliente de pacote. Para obter mais informações, consulte "[Efetuar a autenticação no GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)".
|
||||
2. Instale o pacote usando as instruções para seu cliente de pacote.
|
||||
1. Authenticate to {% data variables.product.prodname_registry %} using the instructions for your package client. For more information, see "[Authenticating to GitHub Packages](/packages/learn-github-packages/introduction-to-github-packages#authenticating-to-github-packages)."
|
||||
2. Install the package using the instructions for your package client.
|
||||
|
||||
Para obter instruções específicas para o seu cliente de pacotes, consulte "[Trabalhar com um registro de {% data variables.product.prodname_registry %}](/packages/working-with-a-github-packages-registry)".
|
||||
For instructions specific to your package client, see "[Working with a {% data variables.product.prodname_registry %} registry](/packages/working-with-a-github-packages-registry)."
|
||||
|
||||
@@ -10,11 +10,11 @@ versions:
|
||||
type: quick_start
|
||||
topics:
|
||||
- Pages
|
||||
shortTitle: QuickStart
|
||||
shortTitle: Quickstart
|
||||
product: '{% data reusables.gated-features.pages %}'
|
||||
---
|
||||
|
||||
## Introdução
|
||||
## Introduction
|
||||
|
||||
{% 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.
|
||||
|
||||
@@ -23,14 +23,18 @@ This guide will lead you through creating a user site at `username.github.io`.
|
||||
## Creating your website
|
||||
|
||||
{% 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`. 
|
||||
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`.
|
||||
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
1. Na barra lateral esquerda, clique em **Pages** (Páginas). 
|
||||
1. Click **Choose a theme**. 
|
||||
1. 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. 
|
||||
1. In the left sidebar, click **Pages**.
|
||||
|
||||
1. Click **Choose a theme**.
|
||||
|
||||
1. 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.
|
||||
|
||||
1. 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.
|
||||
1. When you are done editing the file, click **Commit changes**.
|
||||
1. Visit `username.github.io` to view your new website. **Observação:** podem ser necessários até 20 minutos para que as alterações no site sejam publicadas após o push delas no {% data variables.product.product_name %}.
|
||||
1. Visit `username.github.io` to view your new website. **Note:** It can take up to 20 minutes for changes to your site to publish after you push the changes to {% data variables.product.product_name %}.
|
||||
|
||||
## Changing the title and description
|
||||
|
||||
@@ -39,7 +43,7 @@ By default, the title of your site is `username.github.io`. You can change the t
|
||||
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. Por exemplo:
|
||||
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. For example:
|
||||
|
||||
```yaml
|
||||
theme: jekyll-theme-minimal
|
||||
@@ -49,7 +53,7 @@ By default, the title of your site is `username.github.io`. You can change the t
|
||||
|
||||
1. When you are done editing the file, click **Commit changes**.
|
||||
|
||||
## Próximos passos
|
||||
## Next Steps
|
||||
|
||||
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)."
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Fechar uma pull request
|
||||
intro: 'You may choose to *close* a pull request without [merging it into the upstream branch](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). Isso poderá ser útil se as alterações propostas no branch não forem mais necessárias ou se outra solução tiver sido proposta em outro branch.'
|
||||
title: Closing a pull request
|
||||
intro: 'You may choose to *close* a pull request without [merging it into the upstream branch](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request). This can be handy if the changes proposed in the branch are no longer needed, or if another solution has been proposed in another branch.'
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request
|
||||
- /articles/closing-a-pull-request
|
||||
@@ -14,14 +14,14 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
---
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Dica**: se você abriu uma pull request com o branch base errado, em vez de fechá-la e abrir outra, é possível alterar o branch base. Para obter mais informações, consulte "[Alterar o branch base de uma pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)".
|
||||
**Tip**: If you opened a pull request with the wrong base branch, rather than closing it out and opening a new one, you can instead change the base branch. For more information, see "[Changing the base branch of a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request)."
|
||||
|
||||
{% endtip %}
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
2. Na lista "Pull Requests", clique na pull request da qual deseja fechar.
|
||||
3. Na parte inferior, abaixo da caixa de comentários da pull request, clique em **Close pull request** (Fechar pull request). 
|
||||
4. Opcionalmente, [exclua o branch](/articles/deleting-unused-branches). Assim, a lista de branches do repositório ficará limpa.
|
||||
2. In the "Pull Requests" list, click the pull request you'd like to close.
|
||||
3. At the bottom of the pull request, below the comment box, click **Close pull request**.
|
||||
|
||||
4. Optionally, [delete the branch](/articles/deleting-unused-branches). This keeps the list of branches in your repository tidy.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Fazer merge de uma pull request
|
||||
intro: Faça merge de uma pull request no branch upstream quando o trabalho estiver finalizado. Qualquer pessoa com acesso push no repositório pode completar o merge.
|
||||
title: Merging a pull request
|
||||
intro: Merge a pull request into the upstream branch when work is completed. Anyone with push access to the repository can complete the merge.
|
||||
redirect_from:
|
||||
- /github/collaborating-with-issues-and-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request
|
||||
- /articles/merging-a-pull-request
|
||||
@@ -14,22 +14,22 @@ versions:
|
||||
topics:
|
||||
- Pull requests
|
||||
---
|
||||
## About pull request merges
|
||||
|
||||
## Sobre merges de pull request
|
||||
|
||||
Em uma pull request, você propõe que as alterações feitas em um branch head sejam mescladas em um branch base. Por padrão, qualquer pull request pode sofrer merge a qualquer momento, a menos que o branch head esteja em conflito com o branch base. No entanto, pode haver restrições sobre quando você puder fazer merge de um pull request em um branch específico. Por exemplo, você só pode fazer merge de um pull request no branch-padrão se as verificações de status necessárias forem aprovadas. Para obter mais informações, consulte "[Sobre branches protegidos](/github/administering-a-repository/about-protected-branches)".
|
||||
In a pull request, you propose that changes you've made on a head branch should be merged into a base branch. By default, any pull request can be merged at any time, unless the head branch is in conflict with the base branch. However, there may be restrictions on when you can merge a pull request into a specific branch. For example, you may only be able to merge a pull request into the default branch if required status checks are passing. For more information, see "[About protected branches](/github/administering-a-repository/about-protected-branches)."
|
||||
|
||||
{% data reusables.pull_requests.you-can-auto-merge %}
|
||||
|
||||
Se a pull request apresenta conflitos de merges ou se você deseja testar as alterações antes de fazer merge, é possível [fazer checkout da pull request localmente](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally) e fazer merge usando a linha de comando.
|
||||
If the pull request has merge conflicts, or if you'd like to test the changes before merging, you can [check out the pull request locally](/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally) and merge it using the command line.
|
||||
|
||||
Você não pode realizar o merge de um rascunho de um pull request. Para obter mais informações sobre pull requests em rascunho, consulte "[Sobre pull requests](/articles/about-pull-requests#draft-pull-requests)".
|
||||
You can't merge a draft pull request. For more information about draft pull requests, see "[About pull requests](/articles/about-pull-requests#draft-pull-requests)."
|
||||
|
||||
O repositório pode ser configurado para que o branch principal de um pull request seja excluído automaticamente quando você faz o merge de um pull request. Para obter mais informações, consulte "[Gerenciar a exclusão automática de branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)".
|
||||
The repository may be configured so that the head branch for a pull request is automatically deleted when you merge a pull request. For more information, see "[Managing the automatic deletion of branches](/github/administering-a-repository/managing-the-automatic-deletion-of-branches)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Observação**: {% data reusables.pull_requests.retargeted-on-branch-deletion %} Para obter mais informações, consulte "[Sobre branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)".
|
||||
**Note:** {% data reusables.pull_requests.retargeted-on-branch-deletion %}
|
||||
For more information, see "[About branches](/github/collaborating-with-issues-and-pull-requests/about-branches#working-with-branches)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -37,41 +37,44 @@ Pull requests are merged using [the `--no-ff` option](https://git-scm.com/docs/g
|
||||
|
||||
{% data reusables.pull_requests.close-issues-using-keywords %}
|
||||
|
||||
Se decidir que não quer que as alterações em um branch de tópico sofram merge no branch upstream, é possível [fechar a pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request) sem fazer merge.
|
||||
If you decide you don't want the changes in a topic branch to be merged to the upstream branch, you can [close the pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/closing-a-pull-request) without merging.
|
||||
|
||||
## Fazer merge de uma pull request
|
||||
## Merging a pull request
|
||||
|
||||
{% include tool-switcher %}
|
||||
|
||||
{% webui %}
|
||||
|
||||
{% data reusables.repositories.sidebar-pr %}
|
||||
2. Na lista "Pull Requests", clique na pull request da qual deseja fazer merge.
|
||||
3. Dependendo das opções de merge habilitadas em seu repositório, é possível:
|
||||
- [Fazer merge de todos os commits no branch de base](/articles/about-pull-request-merges/) ao clicar em **Merge pull request** (Fazer merge de pull request). Se a opção **Merge pull request** (Fazer merge da pull request) não está visível, clique no menu suspenso merge e selecione **Create a merge commit** (Criar um commit de merge). 
|
||||
- [Combinar por squash os commits em um único commit](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) ao clicar no menu suspenso merge, selecionar **Squash and merge** (Combinar por squash e fazer merge) e clicar no botão **Squash and merge** (Combinar por squash e fazer merge). 
|
||||
- [Fazer rebase dos commits individualmente no branch de base](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) ao clicar no menu suspenso merge, selecionar **Rebase and merge** (Fazer rebase e merge) e clicar no botão **Rebase and merge** (Fazer rebase e merge). 
|
||||
2. In the "Pull Requests" list, click the pull request you'd like to merge.
|
||||
3. Depending on the merge options enabled for your repository, you can:
|
||||
- [Merge all of the commits into the base branch](/articles/about-pull-request-merges/) by clicking **Merge pull request**. If the **Merge pull request** option is not shown, then click the merge drop down menu and select **Create a merge commit**.
|
||||
|
||||
- [Squash the commits into one commit](/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Squash and merge** and then clicking the **Squash and merge** button.
|
||||
|
||||
- [Rebase the commits individually onto the base branch](/articles/about-pull-request-merges/#rebase-and-merge-your-pull-request-commits) by clicking the merge drop down menu, selecting **Rebase and merge** and then clicking the **Rebase and merge** button.
|
||||
|
||||
|
||||
{% note %}
|
||||
|
||||
**Observação:** rebase e merge sempre atualização as informações do committer e criarão SHAs de commit novos. Para obter mais informações, consulte "[Sobre merges de pull request](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)".
|
||||
**Note:** Rebase and merge will always update the committer information and create new commit SHAs. For more information, see "[About pull request merges](/articles/about-pull-request-merges#rebase-and-merge-your-pull-request-commits)."
|
||||
|
||||
{% endnote %}
|
||||
4. Se solicitado, digite uma mensagem do commit ou aceite a mensagem padrão.
|
||||
4. If prompted, type a commit message, or accept the default message.
|
||||
|
||||
{% data reusables.pull_requests.default-commit-message-squash-merge %}
|
||||
|
||||
|
||||
|
||||
{% data reusables.files.choose-commit-email %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Observação:** O seletor de e-mail não está disponível para merge de rebase, que não cria um commit de merge, ou para merge de combinação por squash, que credita o usuário que criou a pull request como o autor do commit cuja combinação foi feita por squash.
|
||||
**Note:** The email selector is not available for rebase merges, which do not create a merge commit, or for squash merges, which credit the user who created the pull request as the author of the squashed commit.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
6. Clique em **Confirm merge** (Confirmar merge), **Confirm squash and merge** (Confirmar combinação por squash e merge) ou **Confirm rebase and merge** (Confirmar rebase e merge).
|
||||
6. Opcionalmente, [exclua o branch](/articles/deleting-unused-branches). Assim, a lista de branches do repositório ficará limpa.
|
||||
6. Click **Confirm merge**, **Confirm squash and merge**, or **Confirm rebase and merge**.
|
||||
6. Optionally, [delete the branch](/articles/deleting-unused-branches). This keeps the list of branches in your repository tidy.
|
||||
|
||||
{% endwebui %}
|
||||
|
||||
@@ -79,15 +82,15 @@ Se decidir que não quer que as alterações em um branch de tópico sofram merg
|
||||
|
||||
{% data reusables.cli.cli-learn-more %}
|
||||
|
||||
Para fazer merge de um pull request, use o subcomando `gh pr merge`. Substitua `pull request` pelo número, URL ou branch principal do pull request.
|
||||
To merge a pull request, use the `gh pr merge` subcommand. Replace `pull-request` with the number, URL, or head branch of the pull request.
|
||||
|
||||
```shell
|
||||
gh pr merge <em>pull-request</em>
|
||||
```
|
||||
|
||||
Siga as instruções interativas para realizar o merge. Para obter mais informações sobre os métodos de merge que você pode escolher, consulte "[Sobre merges do pull request](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)".
|
||||
Follow the interactive prompts to complete the merge. For more information about the merge methods that you can choose, see "[About pull request merges](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)."
|
||||
|
||||
Como alternativa, você pode usar sinalizadores para ignorar as instruções interativas. Por exemplo, esse comando irá fazer a combinação por squash dos commits em um único commit com a mensagem de "my squash commit", faça o merge do commit combinado por squash no branch de base e exclua o branch local e o remoto.
|
||||
Alternatively, you can use flags to skip the interactive prompts. For example, this command will squash the commits into a single commit with the commit message "my squash commit", merge the squashed commit into the base branch, and then delete the local and remote branch.
|
||||
|
||||
```shell
|
||||
gh pr merge 523 --squash --body "my squash commit" --delete-branch
|
||||
@@ -95,9 +98,9 @@ gh pr merge 523 --squash --body "my squash commit" --delete-branch
|
||||
|
||||
{% endcli %}
|
||||
|
||||
## Leia mais
|
||||
## Further reading
|
||||
|
||||
- "[Reverter uma pull request](/articles/reverting-a-pull-request)"
|
||||
- "[Sincronizar seu branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)" usando o {% data variables.product.prodname_desktop %}
|
||||
- "[Sobre merges de pull request](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
|
||||
- "[Solucionar conflitos de merge](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
|
||||
- "[Reverting a pull request](/articles/reverting-a-pull-request)"
|
||||
- "[Syncing your branch](/desktop/guides/contributing-to-projects/syncing-your-branch/)" using {% data variables.product.prodname_desktop %}
|
||||
- "[About pull request merges](/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges)"
|
||||
- "[Addressing merge conflicts](/github/collaborating-with-pull-requests/addressing-merge-conflicts)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Renaming a branch
|
||||
intro: You can change the name of a branch in a repository.
|
||||
permissions: People with write permissions to a repository can rename a branch in the repository. People with admin permissions can rename the default branch.
|
||||
permissions: 'People with write permissions to a repository can rename a branch in the repository unless it is the [default branch](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-branches#about-the-default-branch){% ifversion fpt or ghec %} or a [protected branch](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches){% endif %}. People with admin permissions can rename the default branch{% ifversion fpt or ghec %} and protected branches{% endif %}.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.1'
|
||||
|
||||
@@ -109,11 +109,9 @@ The `is` qualifier matches commits from repositories with the specified visibili
|
||||
{%- ifversion fpt or ghes or ghec %}
|
||||
| `is:public` | [**is:public**](https://github.com/search?q=is%3Apublic&type=Commits) matches commits to public repositories.
|
||||
{%- endif %}
|
||||
|
||||
{%- ifversion ghes or ghec or ghae %}
|
||||
| `is:internal` | [**is:internal**](https://github.com/search?q=is%3Ainternal&type=Commits) matches commits to internal repositories.
|
||||
{%- endif %}
|
||||
|
||||
| `is:private` | [**is:private**](https://github.com/search?q=is%3Aprivate&type=Commits) matches commits to private repositories.
|
||||
|
||||
## Further reading
|
||||
|
||||
@@ -1 +1 @@
|
||||
O segredo `GITHUB_TOKEN` é definido como um token de acesso para o repositório toda vez que um trabalho de um fluxo de trabalho for iniciado. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}You should set the permissions for this access token in the workflow file to grant read access for the `contents` scope and write access for the `packages` scope. {% else %}tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. {% endif %}Para obter mais informações, consulte[Efetuar a autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
|
||||
O segredo `GITHUB_TOKEN` é definido como um token de acesso para o repositório toda vez que um trabalho de um fluxo de trabalho for iniciado. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}Você deverá definir as permissões para este token de acesso no arquivo do fluxo de trabalho para conceder acesso de leitura para o `conteúdo` escopo e acesso de gravação para o escopo `pacotes`. {% else %}tem permissões de leitura e gravação para pacotes no repositório em que o fluxo de trabalho é executado. {% endif %}Para obter mais informações, consulte[Efetuar a autenticação com o GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)".
|
||||
|
||||
Reference in New Issue
Block a user