Octomerger Bot
@@ -73,6 +73,10 @@ The Search API does not support queries that:
|
||||
|
||||
These search queries will return a "Validation failed" error message.
|
||||
|
||||
### Search scope limits
|
||||
|
||||
To keep the Search API fast for everyone, we limit the number of repositories a query will search through. The Search API will find up to 4,000 repositories that match your filters and return results from those repositories.
|
||||
|
||||
### Timeouts and incomplete results
|
||||
|
||||
To keep the Search API fast for everyone, we limit how long any individual query
|
||||
|
||||
@@ -432,11 +432,13 @@ translations/zh-CN/content/get-started/writing-on-github/working-with-advanced-f
|
||||
translations/zh-CN/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
|
||||
translations/zh-CN/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
translations/zh-CN/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,broken liquid tags
|
||||
translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
|
||||
translations/zh-CN/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
|
||||
@@ -533,7 +535,6 @@ translations/zh-CN/data/release-notes/enterprise-server/3-4/8.yml,rendering erro
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-5/4.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-6/1.yml,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
|
||||
@@ -550,6 +551,7 @@ translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runner-gr
|
||||
translations/zh-CN/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/sidebar-secret.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/usage-workflow-run-time.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/workflow-template-overview.md,rendering error
|
||||
translations/zh-CN/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
|
||||
|
||||
|
@@ -269,6 +269,7 @@ translations/pt-BR/content/actions/learn-github-actions/understanding-github-act
|
||||
translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,rendering error
|
||||
translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md,rendering error
|
||||
translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/quickstart.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md,rendering error
|
||||
translations/pt-BR/content/actions/security-guides/encrypted-secrets.md,rendering error
|
||||
translations/pt-BR/content/actions/security-guides/security-hardening-for-github-actions.md,rendering error
|
||||
@@ -425,11 +426,13 @@ translations/pt-BR/content/get-started/writing-on-github/working-with-advanced-f
|
||||
translations/pt-BR/content/graphql/guides/migrating-from-rest-to-graphql.md,broken liquid tags
|
||||
translations/pt-BR/content/graphql/overview/about-the-graphql-api.md,broken liquid tags
|
||||
translations/pt-BR/content/issues/planning-and-tracking-with-projects/automating-your-project/using-the-api-to-manage-projects.md,broken liquid tags
|
||||
translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects.md,broken liquid tags
|
||||
translations/pt-BR/content/issues/planning-and-tracking-with-projects/managing-your-project/managing-visibility-of-your-projects.md,broken liquid tags
|
||||
translations/pt-BR/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md,rendering error
|
||||
translations/pt-BR/content/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.md,rendering error
|
||||
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/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-your-organizations-installed-integrations.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-project-boards/managing-team-access-to-an-organization-project-board.md,broken liquid tags
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-an-individuals-access-to-an-organization-repository.md,rendering error
|
||||
translations/pt-BR/content/organizations/managing-access-to-your-organizations-repositories/managing-team-access-to-an-organization-repository.md,rendering error
|
||||
@@ -485,8 +488,9 @@ translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponso
|
||||
translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
|
||||
translations/pt-BR/content/support/learning-about-github-support/about-github-support.md,rendering error
|
||||
translations/pt-BR/data/glossaries/external.yml,broken liquid tags
|
||||
translations/pt-BR/data/learning-tracks/code-security.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-20/13.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-20/15.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-21/17.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-21/4.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-21/6.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/2-22/0.yml,rendering error
|
||||
@@ -501,6 +505,7 @@ translations/pt-BR/data/release-notes/enterprise-server/3-0/1.yml,rendering erro
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-0/2.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-0/22.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-0/3.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/0.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/14.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/19.yml,broken liquid tags
|
||||
@@ -508,8 +513,32 @@ translations/pt-BR/data/release-notes/enterprise-server/3-1/2.yml,rendering erro
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/20.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-1/4.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/0-rc1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/0.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/12.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/13.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/14.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-2/17.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/0-rc1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/0.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/1.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/11.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/12.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/6.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/7.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-3/9.yml,broken liquid tags
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/0-rc1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/0.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/2.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/3.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/4.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/5.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/6.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/7.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-4/8.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-5/0-rc1.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-5/4.yml,rendering error
|
||||
translations/pt-BR/data/release-notes/enterprise-server/3-6/0-rc1.yml,rendering error
|
||||
translations/pt-BR/data/reusables/actions/actions-audit-events-workflow.md,rendering error
|
||||
translations/pt-BR/data/reusables/actions/actions-billing.md,broken liquid tags
|
||||
translations/pt-BR/data/reusables/actions/actions-do-not-trigger-workflows.md,broken liquid tags
|
||||
@@ -526,6 +555,7 @@ translations/pt-BR/data/reusables/actions/settings-ui/settings-actions-runner-gr
|
||||
translations/pt-BR/data/reusables/actions/settings-ui/settings-actions-runners.md,rendering error
|
||||
translations/pt-BR/data/reusables/actions/sidebar-secret.md,rendering error
|
||||
translations/pt-BR/data/reusables/actions/usage-workflow-run-time.md,rendering error
|
||||
translations/pt-BR/data/reusables/actions/workflow-basic-example-and-explanation.md,broken liquid tags
|
||||
translations/pt-BR/data/reusables/actions/workflow-dispatch-inputs.md,rendering error
|
||||
translations/pt-BR/data/reusables/advanced-security/secret-scanning-add-custom-pattern-details.md,rendering error
|
||||
translations/pt-BR/data/reusables/advanced-security/secret-scanning-create-custom-pattern.md,rendering error
|
||||
@@ -598,3 +628,4 @@ translations/pt-BR/data/reusables/user-settings/security-analysis.md,rendering e
|
||||
translations/pt-BR/data/reusables/user-settings/security.md,rendering error
|
||||
translations/pt-BR/data/reusables/user-settings/ssh.md,rendering error
|
||||
translations/pt-BR/data/variables/migrations.yml,broken liquid tags
|
||||
translations/pt-BR/data/variables/notifications.yml,broken liquid tags
|
||||
|
||||
|
@@ -123,8 +123,8 @@ The following operating systems are supported for the self-hosted runner applica
|
||||
The following processor architectures are supported for the self-hosted runner application.
|
||||
|
||||
- `x64` - Linux, macOS, Windows.
|
||||
- `ARM64` - Linux{% ifversion actions-macos-arm %}, macOS{% endif %}.
|
||||
- `ARM32` - Linux only.
|
||||
- `ARM64` - Linux{% ifversion actions-macos-arm %}, macOS{% endif %}{% ifversion actions-windows-arm %}, Windows (currently in beta){% endif %}.
|
||||
- `ARM32` - Linux.
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
|
||||
@@ -74,6 +74,9 @@ The following table indicates where each context and special function can be use
|
||||
|
||||
| Workflow key | Context | Special functions |
|
||||
| ---- | ------- | ----------------- |
|
||||
{%- ifversion actions-run-name %}
|
||||
| <code>run-name</code> | <code>github, inputs</code> | |
|
||||
{%- endif %}
|
||||
| <code>concurrency</code> | <code>github, inputs</code> | |
|
||||
| <code>env</code> | <code>github, secrets, inputs</code> | |
|
||||
| <code>jobs.<job_id>.concurrency</code> | <code>github, needs, strategy, matrix, inputs</code> | |
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Início rápido para GitHub Actions
|
||||
intro: 'Experimente as funcionalidades de {% data variables.product.prodname_actions %} em 5 minutos ou menos.'
|
||||
title: Quickstart for GitHub Actions
|
||||
intro: 'Try out the features of {% data variables.product.prodname_actions %} in 5 minutes or less.'
|
||||
allowTitleToDifferFromFilename: true
|
||||
redirect_from:
|
||||
- /actions/getting-started-with-github-actions/starting-with-preconfigured-workflow-templates
|
||||
@@ -13,84 +13,85 @@ type: quick_start
|
||||
topics:
|
||||
- Fundamentals
|
||||
shortTitle: Quickstart
|
||||
ms.openlocfilehash: 164aef041c509264c9e8440d5339bce3cf4aaaca
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '146139454'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## Introdução
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
Você precisa apenas de um repositório de {% data variables.product.prodname_dotcom %} para criar e executar um fluxo de trabalho de {% data variables.product.prodname_actions %}. Neste guia, você adicionará um fluxo de trabalho que demonstra algumas das funcionalidades essenciais de {% data variables.product.prodname_actions %}.
|
||||
## Introduction
|
||||
|
||||
O exemplo a seguir mostra como os trabalhos de {% data variables.product.prodname_actions %} podem ser acionados automaticamente, onde são executados e como podem interagir com o código no seu repositório.
|
||||
You only need a {% data variables.product.prodname_dotcom %} repository to create and run a {% data variables.product.prodname_actions %} workflow. In this guide, you'll add a workflow that demonstrates some of the essential features of {% data variables.product.prodname_actions %}.
|
||||
|
||||
## Criar o seu primeiro fluxo de trabalho
|
||||
The following example shows you how {% data variables.product.prodname_actions %} jobs can be automatically triggered, where they run, and how they can interact with the code in your repository.
|
||||
|
||||
1. Crie um diretório `.github/workflows` no seu repositório do {% data variables.product.prodname_dotcom %} caso ele ainda não exista.
|
||||
2. No diretório `.github/workflows`, crie um novo arquivo chamado `github-actions-demo.yml`. Para obter mais informações, confira "[Como criar arquivos](/github/managing-files-in-a-repository/creating-new-files)".
|
||||
3. Copie o seguinte conteúdo YAML para o arquivo `github-actions-demo.yml`: {% raw %}
|
||||
```yaml{:copy}
|
||||
name: GitHub Actions Demo
|
||||
on: [push]
|
||||
jobs:
|
||||
Explore-GitHub-Actions:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- run: echo "🎉 The job was automatically triggered by a ${{ github.event_name }} event."
|
||||
- run: echo "🐧 This job is now running on a ${{ runner.os }} server hosted by GitHub!"
|
||||
- run: echo "🔎 The name of your branch is ${{ github.ref }} and your repository is ${{ github.repository }}."{% endraw %}
|
||||
- name: Check out repository code
|
||||
uses: {% data reusables.actions.action-checkout %}{% raw %}
|
||||
- run: echo "💡 The ${{ github.repository }} repository has been cloned to the runner."
|
||||
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
|
||||
- name: List files in the repository
|
||||
run: |
|
||||
ls ${{ github.workspace }}
|
||||
- run: echo "🍏 This job's status is ${{ job.status }}."
|
||||
## Creating your first workflow
|
||||
|
||||
```
|
||||
{% endraw %}
|
||||
3. Vá até o final da página e selecione **Criar um branch para este commit e iniciar uma solicitação de pull**. Em seguida, para criar uma solicitação de pull, clique em **Propor novo arquivo**.
|
||||
|
||||
1. Create a `.github/workflows` directory in your repository on {% data variables.product.prodname_dotcom %} if this directory does not already exist.
|
||||
1. In the `.github/workflows` directory, create a file named `github-actions-demo.yml`. For more information, see "[Creating new files](/github/managing-files-in-a-repository/creating-new-files)."
|
||||
1. Copy the following YAML contents into the `github-actions-demo.yml` file:
|
||||
|
||||
O commit do arquivo de fluxo de trabalho em um branch no repositório dispara o evento `push` e executa o fluxo de trabalho.
|
||||
```yaml{:copy}
|
||||
name: GitHub Actions Demo
|
||||
{%- ifversion actions-run-name %}
|
||||
run-name: {% raw %}${{ github.actor }}{% endraw %} is testing out GitHub Actions 🚀
|
||||
{%- endif %}
|
||||
on: [push]
|
||||
jobs:
|
||||
Explore-GitHub-Actions:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- run: echo "🎉 The job was automatically triggered by a {% raw %}${{ github.event_name }}{% endraw %} event."
|
||||
- run: echo "🐧 This job is now running on a {% raw %}${{ runner.os }}{% endraw %} server hosted by GitHub!"
|
||||
- run: echo "🔎 The name of your branch is {% raw %}${{ github.ref }}{% endraw %} and your repository is {% raw %}${{ github.repository }}{% endraw %}."
|
||||
- name: Check out repository code
|
||||
uses: {% data reusables.actions.action-checkout %}
|
||||
- run: echo "💡 The {% raw %}${{ github.repository }}{% endraw %} repository has been cloned to the runner."
|
||||
- run: echo "🖥️ The workflow is now ready to test your code on the runner."
|
||||
- name: List files in the repository
|
||||
run: |
|
||||
ls {% raw %}${{ github.workspace }}{% endraw %}
|
||||
- run: echo "🍏 This job's status is {% raw %}${{ job.status }}{% endraw %}."
|
||||
```
|
||||
1. Scroll to the bottom of the page and select **Create a new branch for this commit and start a pull request**. Then, to create a pull request, click **Propose new file**.
|
||||
|
||||
## Visualizar os resultados do seu fluxo de trabalho
|
||||
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %} {% data reusables.repositories.actions-tab %}
|
||||
1. Na barra lateral esquerda, clique no fluxo de trabalho que deseja ver.
|
||||
Committing the workflow file to a branch in your repository triggers the `push` event and runs your workflow.
|
||||
|
||||
|
||||
1. Na lista de execuções do fluxo de trabalho, clique no nome da execução que você deseja visualizar.
|
||||
## Viewing your workflow results
|
||||
|
||||
|
||||
1. Em **Trabalhos**, clique no trabalho **Explore-GitHub-Actions**.
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.actions-tab %}
|
||||
1. In the left sidebar, click the workflow you want to see.
|
||||
|
||||
|
||||
1. O registro mostra como cada uma das etapas foi processada. Expanda qualquer um dos passos para ver seus detalhes.
|
||||
|
||||
1. From the list of workflow runs, click the name of the run you want to see.
|
||||
|
||||
|
||||
|
||||
1. Under **Jobs** , click the **Explore-GitHub-Actions** job.
|
||||
|
||||
|
||||
1. The log shows you how each of the steps was processed. Expand any of the steps to view its details.
|
||||
|
||||
|
||||
|
||||
Por exemplo, você pode ver a lista de arquivos no repositório: 
|
||||
For example, you can see the list of files in your repository:
|
||||
|
||||
|
||||
## Mais fluxos de trabalho iniciais
|
||||
## More starter workflows
|
||||
|
||||
{% data reusables.actions.workflow-template-overview %}
|
||||
|
||||
## Exemplos mais complexos
|
||||
## More complex examples
|
||||
{% data reusables.actions.link-to-example-library %}
|
||||
|
||||
## Próximas etapas
|
||||
## Next steps
|
||||
|
||||
O exemplo do fluxo de trabalho que você acabou de adicionar é executado cada vez que o código for enviado para o branch e mostra como {% data variables.product.prodname_actions %} pode funcionar com o conteúdo do seu repositório. Mas este é apenas o começo do que você pode fazer com o {% data variables.product.prodname_actions %}.
|
||||
The example workflow you just added runs each time code is pushed to the branch, and shows you how {% data variables.product.prodname_actions %} can work with the contents of your repository. But this is only the beginning of what you can do with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- O seu repositório pode conter vários fluxos de trabalho que ativam diferentes tarefas com base em diferentes eventos.
|
||||
- Você pode usar um fluxo de trabalho para instalar aplicativos de teste de software e fazer com que testem automaticamente seu código nos executores de {% data variables.product.prodname_dotcom %}.
|
||||
- Your repository can contain multiple workflows that trigger different jobs based on different events.
|
||||
- You can use a workflow to install software testing apps and have them automatically test your code on {% data variables.product.prodname_dotcom %}'s runners.
|
||||
|
||||
O {% data variables.product.prodname_actions %} pode ajudá-lo a automatizar quase todos os aspectos dos processos de desenvolvimento do seu aplicativo. Pronto para começar? Aqui estão alguns recursos úteis para dar seus próximos passos com {% data variables.product.prodname_actions %}:
|
||||
{% data variables.product.prodname_actions %} can help you automate nearly every aspect of your application development processes. Ready to get started? Here are some helpful resources for taking your next steps with {% data variables.product.prodname_actions %}:
|
||||
|
||||
- "[Saiba como usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" para ver um tutorial detalhado.
|
||||
- "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)" for an in-depth tutorial.
|
||||
|
||||
@@ -27,7 +27,23 @@ You must store workflow files in the `.github/workflows` directory of your repos
|
||||
|
||||
## `name`
|
||||
|
||||
The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's actions page. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
|
||||
The name of your workflow. {% data variables.product.prodname_dotcom %} displays the names of your workflows on your repository's "Actions" tab. If you omit `name`, {% data variables.product.prodname_dotcom %} sets it to the workflow file path relative to the root of the repository.
|
||||
|
||||
{% ifversion actions-run-name %}
|
||||
## `run-name`
|
||||
|
||||
The name for workflow runs generated from the workflow. {% data variables.product.prodname_dotcom %} displays the workflow run name in the list of workflow runs on your repository's "Actions" tab. If you omit `run-name`, the run name is set to event-specific information for the workflow run. For example, for a workflow triggered by a `push` or `pull_request` event, it is set as the commit message.
|
||||
|
||||
This value can include expressions and can reference the [`github`](/actions/learn-github-actions/contexts#github-context) and [`inputs`](/actions/learn-github-actions/contexts#inputs-context) contexts.
|
||||
|
||||
### Example
|
||||
|
||||
{% raw %}
|
||||
```yaml
|
||||
run-name: Deploy to ${{ inputs.deploy_target }} by @${{ github.actor }}
|
||||
```
|
||||
{% endraw %}
|
||||
{% endif %}
|
||||
|
||||
## `on`
|
||||
|
||||
|
||||
@@ -30,13 +30,15 @@ The {% data variables.product.prodname_serverless %} provides many of the benefi
|
||||
|
||||
The {% data variables.product.prodname_serverless %} runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the [GitHub Repositories extension](https://code.visualstudio.com/docs/editor/github#_github-repositories-extension) to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.
|
||||
|
||||
You must be signed in to use the web-based editor.
|
||||
|
||||
## Opening the {% data variables.product.prodname_serverless %}
|
||||
|
||||
You can open any {% data variables.product.prodname_dotcom %} repository in the {% data variables.product.prodname_serverless %} in either of the following ways:
|
||||
|
||||
- To open the repository in the same browser tab, press `.` while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
|
||||
- To open the repository in the same browser tab, press <kbd>.</kbd> while browsing any repository or pull request on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
To open the repository in a new browser tab, hold down the shift key and press `.`.
|
||||
To open the repository in a new browser tab, press <kbd>></kbd>.
|
||||
|
||||
- Change the URL from "github.com" to "github.dev".
|
||||
- When viewing a file, use the dropdown menu next to {% octicon "pencil" aria-label="The edit icon" %} and select **Open in github.dev**.
|
||||
|
||||
@@ -50,7 +50,8 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
|
||||
|
||||
| Keyboard shortcut | Description
|
||||
|-----------|------------{% ifversion fpt or ghec %}
|
||||
|<kbd>.</kbd> | Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
|<kbd>.</kbd> | Opens a repository or pull request in the web-based editor in the same browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."
|
||||
|<kbd>></kbd> | Opens a repository or pull request in the web-based editor in a new browser tab. You must be signed in to use the editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
|<kbd>Command</kbd>+<kbd>B</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>B</kbd> (Windows/Linux) | Inserts Markdown formatting for bolding text
|
||||
|<kbd>Command</kbd>+<kbd>I</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>I</kbd> (Windows/Linux) | Inserts Markdown formatting for italicizing text
|
||||
|<kbd>Command</kbd>+<kbd>K</kbd> (Mac) or </br> <kbd>Ctrl</kbd>+<kbd>K</kbd> (Windows/Linux) | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae or ghes > 3.3 %}
|
||||
|
||||
@@ -11,6 +11,7 @@ children:
|
||||
- /managing-access-to-your-projects
|
||||
- /closing-and-deleting-your-projects
|
||||
- /adding-your-project-to-a-repository
|
||||
- /adding-your-project-to-a-team
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: ca7c42e8dcb3daf477c70248eb79d12ca9670052
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
|
||||
@@ -1,115 +1,117 @@
|
||||
---
|
||||
title: 'Gerenciar o acesso aos {% data variables.projects.projects_v2 %}'
|
||||
title: 'Managing access to your {% data variables.projects.projects_v2 %}'
|
||||
shortTitle: 'Managing {% data variables.projects.project_v2 %} access'
|
||||
intro: 'Saiba como gerenciar o acesso individual e de equipe ao seu {% data variables.projects.project_v2 %}.'
|
||||
intro: 'Learn how to manage team and individual access to your {% data variables.projects.project_v2 %}.'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
versions:
|
||||
feature: projects-v2
|
||||
feature: "projects-v2"
|
||||
redirect_from:
|
||||
- /issues/trying-out-the-new-projects-experience/managing-access-to-projects
|
||||
type: tutorial
|
||||
topics:
|
||||
- Projects
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 05fa60d5690074c217db87cd52a44b46433c014e
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147423749'
|
||||
---
|
||||
## Sobre o acesso ao projeto
|
||||
|
||||
Os administradores de projetos no nível de organização podem gerenciar acesso para toda a organização, equipes, integrantes individuais da organização e para colaboradores externos.
|
||||
|
||||
Os administradores de projetos de nível de usuário podem convidar colaboradores individuais e gerenciar seu acesso.
|
||||
## About project access
|
||||
|
||||
Administradores do projeto também podem controlar a visibilidade do seu projeto para todos na internet. Para obter mais informações, confira "[Como gerenciar a visibilidade dos seus projetos](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)".
|
||||
Admins of organization-level projects can manage access for the entire organization, for teams, for individual organization members, and for outside collaborators.
|
||||
|
||||
## Gerenciar acesso para projetos no nível da organização
|
||||
Admins of user-level projects can invite individual collaborators and manage their access.
|
||||
|
||||
### Gerenciando o acesso para todos na sua organização
|
||||
Project admins can also control the visibility of their project for everyone on the internet. For more information, see "[Managing the visibility of your projects](/issues/trying-out-the-new-projects-experience/managing-the-visibility-of-your-projects)."
|
||||
|
||||
A função base padrão é `write`, o que significa que todos na organização podem ver e editar seu projeto. Para alterar o acesso ao projeto para todos da organização, você pode alterar a função-base. As alterações na função-base afetam apenas os integrantes da organização que não são proprietários da organização e a quem não é concedido acesso individual.
|
||||
## Managing access for organization-level projects
|
||||
|
||||
### Managing access for everyone in your organization
|
||||
|
||||
The default base role is `write`, meaning that everyone in the organization can see and edit your project. To change project access for everyone in the organization, you can change the base role. Changes to the base role only affect organization members who are not organization owners and who are not granted individual access.
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Clique em **Gerenciar acesso**.
|
||||
|
||||
2. Na **função Base**, selecione a função padrão.
|
||||
|
||||
- **Sem acesso**: somente os proprietários e os usuários da organização que receberam acesso individual podem ver o projeto. Os proprietários da organização também são administradores do projeto.
|
||||
- **Leitura**: todos na organização podem ver o projeto. Os proprietários da organização também são administradores do projeto.
|
||||
- **Gravação**: todos na organização podem ver e editar o projeto. Os proprietários da organização também são administradores do projeto.
|
||||
- **Administrador**: todos na organização são administradores do projeto.
|
||||
1. Click **Manage access**.
|
||||
|
||||
2. Under **Base role**, select the default role.
|
||||
|
||||
- **No access**: Only organization owners and users granted individual access can see the project. Organization owners are also admins for the project.
|
||||
- **Read**: Everyone in the organization can see the project. Organization owners are also admins for the project.
|
||||
- **Write**: Everyone in the organization can see and edit the project. Organization owners are also admins for the project.
|
||||
- **Admin**: Everyone in the organization is an admin for the project.
|
||||
|
||||
### Gerenciando o acesso de equipes e integrantes individuais da sua organização
|
||||
### Managing access for teams and individual members of your organization
|
||||
|
||||
Também é possível adicionar equipes, colaboradores externos e integrantes da organização individuais como colaboradores em um projeto no nível da organização. Para obter mais informações, confira "[Sobre as equipes](/organizations/organizing-members-into-teams/about-teams)".
|
||||
You can also add teams, external collaborators, and individual organization members as collaborators for an organization-level project. For more information, see "[About teams](/organizations/organizing-members-into-teams/about-teams)."
|
||||
|
||||
Você pode apenas convidar um usuário individual para colaborar no projeto a nível da organização se ele já for integrante da organização ou colaborador externo em pelo menos um repositório na organização.
|
||||
{% ifversion projects-v2-add-to-team %}
|
||||
|
||||
If you grant a team read permissions or greater for a project, the project is also displayed on the team's projects page. You can also add projects to a team on the team's projects page. For more information, see "[Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
You can only invite an individual user to collaborate on your organization-level project if they are already a member of the organization or an outside collaborator on at least one repository in the organization.
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Clique em **Gerenciar acesso**.
|
||||
|
||||
2. Em **Convidar colaboradores**, procure a equipe ou o usuário individual que deseja convidar.
|
||||
|
||||
3. Selecione a função para o colaborador.
|
||||
|
||||
- **Leitura**: a equipe ou a pessoa pode ver o projeto.
|
||||
- **Gravação**: a equipe ou a pessoa pode ver e editar o projeto.
|
||||
- **Administrador**: a equipe ou a pessoa pode ver, editar e adicionar novos colaboradores ao projeto.
|
||||
4. Clique em **Convidar**.
|
||||
|
||||
1. Click **Manage access**.
|
||||
|
||||
2. Under **Invite collaborators**, search for the team or individual user that you want to invite.
|
||||
|
||||
3. Select the role for the collaborator.
|
||||
|
||||
- **Read**: The team or individual can view the project.
|
||||
- **Write**: The team or individual can view and edit the project.
|
||||
- **Admin**: The team or individual can view, edit, and add new collaborators to the project.
|
||||
4. Click **Invite**.
|
||||
|
||||
|
||||
### Gerenciando o acesso de um colaborador existente no seu projeto
|
||||
### Managing access of an existing collaborator on your project
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Clique em **Gerenciar acesso**.
|
||||
|
||||
1. Em **Gerenciar acesso**, localize os colaboradores cujas permissões você deseja modificar.
|
||||
1. Click **Manage access**.
|
||||
|
||||
1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
|
||||
|
||||
Use os menus suspensos **Tipo** e **Função** para filtrar a lista de acesso.
|
||||
|
||||
You can use the **Type** and **Role** drop-down menus to filter the access list.
|
||||
|
||||
|
||||
1. Edite a função dos colaboradores.
|
||||
|
||||
1. Como opção, clique em **Remover** para remover os colaboradores.
|
||||
|
||||
1. Edit the role for the collaborator(s).
|
||||
|
||||
1. Optionally, click **Remove** to remove the collaborator(s).
|
||||
|
||||
|
||||
## Gerenciando acesso para projetos no nível do usuário
|
||||
## Managing access for user-level projects
|
||||
|
||||
### Concedendo acesso de colaborador ao seu projeto
|
||||
### Granting a collaborator access to your project
|
||||
|
||||
{% note %}
|
||||
|
||||
Isto afeta apenas os colaboradores do projeto, não os repositórios do projeto. Para visualizar um item no projeto, alguém deverá ter as permissões necessárias para o repositório ao qual o item pertence. Se o seu projeto incluir itens de um repositório privado, pessoas que não forem colaboradores no repositório não poderão visualizar os itens desse repositório. Para obter mais informações, confira "[Como configurar a visibilidade do repositório](/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility)" e "[Como gerenciar equipes e pessoas com acesso no seu repositório](/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. 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)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Clique em **Gerenciar acesso**.
|
||||
|
||||
2. Em **Convidar colaboradores**, procure o usuário que deseja convidar.
|
||||
|
||||
3. Selecione a função para o colaborador.
|
||||
|
||||
- **Leitura**: a pessoa pode ver o projeto.
|
||||
- **Gravação**: a pessoa pode ver e editar o projeto.
|
||||
- **Administrador**: a pessoa pode ver, editar e adicionar novos colaboradores ao projeto.
|
||||
4. Clique em **Convidar**.
|
||||
|
||||
1. Click **Manage access**.
|
||||
|
||||
2. Under **Invite collaborators**, search for the user that you want to invite.
|
||||
|
||||
3. Select the role for the collaborator.
|
||||
|
||||
- **Read**: The individual can view the project.
|
||||
- **Write**: The individual can view and edit the project.
|
||||
- **Admin**: The individual can view, edit, and add new collaborators to the project.
|
||||
4. Click **Invite**.
|
||||
|
||||
|
||||
### Gerenciando o acesso de um colaborador existente no seu projeto
|
||||
### Managing access of an existing collaborator on your project
|
||||
|
||||
{% data reusables.projects.project-settings %}
|
||||
1. Clique em **Gerenciar acesso**.
|
||||
|
||||
1. Em **Gerenciar acesso**, localize os colaboradores cujas permissões você deseja modificar.
|
||||
1. Click **Manage access**.
|
||||
|
||||
1. Under **Manage access**, find the collaborator(s) whose permissions you want to modify.
|
||||
|
||||
Use os menus suspensos **Tipo** e **Função** para filtrar a lista de acesso.
|
||||
|
||||
You can use the **Type** and **Role** drop-down menus to filter the access list.
|
||||
|
||||
|
||||
1. Edite a função dos colaboradores.
|
||||
|
||||
1. Como opção, clique em **Remover** para remover os colaboradores.
|
||||
|
||||
1. Edit the role for the collaborator(s).
|
||||
|
||||
1. Optionally, click **Remove** to remove the collaborator(s).
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 'Gerenciar o acesso de uma equipe ao {% data variables.product.prodname_project_v1 %} de uma organização'
|
||||
intro: 'Como proprietário da organização ou administrador do {% data variables.projects.projects_v1_board %}, você pode dar a uma equipe acesso a um {% data variables.projects.projects_v1_board %} pertencente à sua organização.'
|
||||
title: Managing team access to an organization {% data variables.product.prodname_project_v1 %}
|
||||
intro: 'As an organization owner or {% data variables.projects.projects_v1_board %} admin, you can give a team access to a {% data variables.projects.projects_v1_board %} owned by your organization.'
|
||||
redirect_from:
|
||||
- /articles/managing-team-access-to-an-organization-project-board
|
||||
- /github/setting-up-and-managing-organizations-and-teams/managing-team-access-to-an-organization-project-board
|
||||
@@ -14,46 +14,58 @@ topics:
|
||||
- Teams
|
||||
shortTitle: Manage team access
|
||||
allowTitleToDifferFromFilename: true
|
||||
ms.openlocfilehash: 9672dddc31d39349ec99488313e021bca0c12c60
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147422858'
|
||||
---
|
||||
|
||||
{% data reusables.projects.project_boards_old %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Avisos:**
|
||||
- Você pode alterar os níveis de permissões de uma equipe se ela tiver acesso direto a um {% data variables.projects.projects_v1_board %}. Se o acesso da equipe ao {% data variables.projects.projects_v1_board %} for herdado de uma equipe pai, você deverá alterar o acesso da equipe pai para {% data variables.projects.projects_v1_board %}.
|
||||
- Se você adicionar ou remover acesso ao {% data variables.projects.projects_v1_board %} para uma equipe pai, cada uma das equipes filho desse pai também receberá ou perderá o acesso ao {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Sobre as equipes](/articles/about-teams)".
|
||||
**Warnings:**
|
||||
- You can change a team's permission level if the team has direct access to a {% data variables.projects.projects_v1_board %}. If the team's access to the {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %}.
|
||||
- If you add or remove {% data variables.projects.projects_v1_board %} access for a parent team, each of that parent's child teams will also receive or lose access to the {% data variables.projects.projects_v1_board %}. For more information, see "[About teams](/articles/about-teams)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
## Dar a uma equipe acesso a um {% data variables.projects.projects_v1_board %}
|
||||
## Giving a team access to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
Você pode dar a toda uma equipe o mesmo nível de permissão para um {% data variables.projects.projects_v1_board %}.
|
||||
You can give an entire team the same permission level to a {% data variables.projects.projects_v1_board %}.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Observação:** {% data reusables.project-management.cascading-permissions %} Por exemplo, se um proprietário da organização dar a uma equipe permissões de leitura em um {% data variables.projects.projects_v1_board %} e um administrador do {% data variables.projects.projects_v1_board %} conceder permissões de administrador a esse quadro a um membro da equipe como um colaborador individual, essa pessoa terá permissões de administrador no {% data variables.projects.projects_v1_board %}. Para obter mais informações, confira "[Permissões de {% data variables.product.prodname_project_v1_caps %} para uma organização](/articles/project-board-permissions-for-an-organization)".
|
||||
**Note:** {% data reusables.project-management.cascading-permissions %} For example, if an organization owner has given a team read permissions to a {% data variables.projects.projects_v1_board %}, and a {% data variables.projects.projects_v1_board %} admin gives one of the team members admin permissions to that board as an individual collaborator, that person would have admin permissions to the {% data variables.projects.projects_v1_board %}. For more information see, "[{% data variables.product.prodname_project_v1_caps %} permissions for an organization](/articles/project-board-permissions-for-an-organization)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
|
||||
1. Clique em **Projetos (clássicos)** {% endif %} {% data reusables.project-management.select-project %} {% data reusables.project-management.click-menu %} {% data reusables.project-management.access-collaboration-settings %}
|
||||
8. Na barra lateral esquerda, clique em **Equipes**.
|
||||
9. Para adicionar uma equipe, clique em **Adicionar uma equipe: Selecionar equipe**. Depois, escolha uma equipe no menu suspenso ou pesquise a equipe que você deseja adicionar.
|
||||
|
||||
10. Ao lado do nome da equipe, use o menu suspenso usado para selecionar o nível de permissão desejado: **Leitura**, **Gravação** ou **Administrador**. 
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.organization-wide-project %}{% ifversion projects-v2 %}
|
||||
1. Click **Projects (classic)**{% endif %}
|
||||
{% data reusables.project-management.select-project %}
|
||||
{% data reusables.project-management.click-menu %}
|
||||
{% data reusables.project-management.access-collaboration-settings %}
|
||||
8. In the left sidebar, click **Teams**.
|
||||
9. To add a team, click **Add a team: Select team**. Then, choose a team from the drop-down menu or search for the team you'd like to add.
|
||||
|
||||
10. Next to the team name, use the drop-down menu to select the desired permission level: **Read**, **Write**, or **Admin**.
|
||||
|
||||
|
||||
## Configurar o acesso de uma equipe a um {% data variables.projects.projects_v1_board %}
|
||||
## Configuring a team's access to a {% data variables.projects.projects_v1_board %}
|
||||
|
||||
Se o acesso de uma equipe a um {% data variables.projects.projects_v1_board %} for herdado de uma equipe pai, você deverá alterar o acesso da equipe pai ao{% data variables.projects.projects_v1_board %} para atualizar o acesso às equipes filho.
|
||||
If a team's access to a {% data variables.projects.projects_v1_board %} is inherited from a parent team, you must change the parent team's access to the {% data variables.projects.projects_v1_board %} to update access to the child teams.
|
||||
|
||||
{% data reusables.profile.access_org %} {% data reusables.user-settings.access_org %} {% data reusables.organizations.specific_team %}
|
||||
4. Acima da conversa da equipe, clique em {% octicon "project" aria-label="The Projects icon" %} **Projetos**.
|
||||
|
||||
5. Para alterar os níveis de permissão, à direita do {% data variables.projects.projects_v1_board %} que deseja atualizar, use o menu suspenso. Para remover um {% data variables.projects.projects_v1_board %}, clique em **{% octicon "trash" aria-label="The trash icon" %}** .
|
||||
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.specific_team %}
|
||||
4. Above the team's conversation, click {% octicon "project" aria-label="The Projects icon" %} **Projects**.
|
||||
|
||||
5. To change permissions levels, to the right of the {% data variables.projects.projects_v1_board %} you want to update, use the drop-down. To remove a {% data variables.projects.projects_v1_board %}, click **{% octicon "trash" aria-label="The trash icon" %}**.
|
||||
|
||||
|
||||
{% ifversion projects-v2-add-to-team %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- [Adding your project to a team](/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-team)
|
||||
|
||||
|
||||
{% endif %}
|
||||
@@ -49,9 +49,20 @@ You can search for archived repositories. For more information, see "[Searching
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under "Danger Zone", click **Archive this repository** or **Unarchive this repository**.
|
||||
3. Under "Danger Zone", click **Archive this repository**
|
||||
|
||||
4. Read the warnings.
|
||||
5. Type the name of the repository you want to archive or unarchive.
|
||||
5. Type the name of the repository you want to archive.
|
||||
|
||||
6. Click **I understand the consequences, archive this repository**.
|
||||
|
||||
## Unarchiving a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.sidebar-settings %}
|
||||
3. Under "Danger Zone", click **Unarchive this repository**
|
||||
|
||||
4. Read the warnings.
|
||||
5. Type the name of the repository you want to unarchive.
|
||||
|
||||
6. Click **I understand the consequences, unarchive this repository**.
|
||||
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #6207.
|
||||
# We have added support for Elixir advisories to the Advisory Database.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-6207'
|
||||
@@ -0,0 +1,8 @@
|
||||
# Reference: #7340
|
||||
# Extends actions-cache-management.yml (Issue #6154)
|
||||
# Documentation for Actions cache list and delete APIs
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '> 3.6'
|
||||
ghae: 'issue-7340'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: #6458
|
||||
# Larger GitHub-hosted runners
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6920
|
||||
# Documentation for inheriting secrets from the calling workflow
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>= 3.6'
|
||||
ghae: 'issue-6920'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6405
|
||||
# Documentation for job summaries for jobs on the workflow run summary page.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-6405'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7336
|
||||
# General versioning for oidc hardening options
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #7094
|
||||
# Documentation for allowing matrix jobs to call reusable workflows.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7094'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 7387
|
||||
# Differentiating triggering actor from executing actor
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7387'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #5169.
|
||||
# Documentation for the Actions starter template UI updates
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.4'
|
||||
ghae: 'issue-5169'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issue 6921
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6921'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6926.
|
||||
# Versioning for org policy settings for workflow PR approval permission. This is only org setting! For the later separate ship for the enterprise and repo setting, see the allow-actions-to-approve-pr-with-ent-repo flag.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6926'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Documentation for adding business.sso_response and org.sso_repsonse
|
||||
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.8'
|
||||
ghae: 'issue-7939'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #7370.
|
||||
# Versioning for autolinks being able to accept alphanumeric chars.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7370'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Issue 7584
|
||||
# Building Pages sites with Actions [GA]
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue: 6667
|
||||
# Description: Allow merging pull requests without complying with branch protection rules.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-6667'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 7720
|
||||
# Organization owners can restrict public classic projects /OR/ Projects V2
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7720'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 7720
|
||||
# Organization owners can restrict public classic projects.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7720'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 7617
|
||||
# Users can easily exclude CodeQL queries from code scanning analyses - [GA]
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7617'
|
||||
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghae: 'issue-5036'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #2499 in the codeql-core repository, and issue #7626 in the docs-content repository
|
||||
# We have added one-click re-running in debug mode for code scanning CodeQL.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7626'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Tracking deprecation of CodeQL runner
|
||||
# https://github.blog/changelog/2022-04-05-codeql-runner-is-now-deprecated/
|
||||
|
||||
versions:
|
||||
ghes: '<=3.3'
|
||||
@@ -0,0 +1,5 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-2191'
|
||||
5
translations/pt-BR/data/features/commit-signoffs.yml
Normal file
5
translations/pt-BR/data/features/commit-signoffs.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6049'
|
||||
7
translations/pt-BR/data/features/commit-tree-view.yml
Normal file
7
translations/pt-BR/data/features/commit-tree-view.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 6662
|
||||
# Commit file tree view
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6662'
|
||||
@@ -0,0 +1,5 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-6670'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Secret scanning: custom pattern dry run GA #7527
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7527'
|
||||
7
translations/pt-BR/data/features/debug-reruns.yml
Normal file
7
translations/pt-BR/data/features/debug-reruns.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 6629
|
||||
# Enabling debug logging when re-running jobs or workflows
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6629'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: issue #7597
|
||||
# Admin can control default PR merge/ squash commit messages
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7597'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #6631 - Dependabot alerts: surface information about development dependencies - [GA]
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-6631'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #7673 - Dependabot alerts: optional comment with dismissal - [GA]
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7673'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: Issue #6076 introduction of label for "vulnerable calls" in Dependabot alerts
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghae: 'issue-6076'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #6076 ability to dismiss or re-open multiple Dependabot alerts
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-6628'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #7510 - Dependabot alerts: "Most important" sort (prioritization score) - [GA]
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7510'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #7044 Update repository settings for Dependabot to include shortcut for Version updates
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-7044'
|
||||
@@ -0,0 +1,4 @@
|
||||
# Reference: Issue #7753 Dependency review action has shipped with GHES 3.6 and needs admin docs
|
||||
versions:
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-7753'
|
||||
@@ -0,0 +1,4 @@
|
||||
# Reference: Issue #7486 Configuring the dependency review action - [Public Beta] for GHES
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6397
|
||||
# Documentation for dependency submission API (beta)
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: 'issue-6397'
|
||||
@@ -0,0 +1,6 @@
|
||||
# docs-content 6307. OAuth device auth flow is opt in.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.4'
|
||||
ghae: 'issue-6307'
|
||||
4
translations/pt-BR/data/features/discussions.yml
Normal file
4
translations/pt-BR/data/features/discussions.yml
Normal file
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
@@ -0,0 +1,4 @@
|
||||
# Reference: #7360
|
||||
# Documentation for migration from Docker registry to Container registry for enterprise products
|
||||
versions:
|
||||
ghes: '>= 3.6'
|
||||
5
translations/pt-BR/data/features/enable-git-events.yml
Normal file
5
translations/pt-BR/data/features/enable-git-events.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #7283
|
||||
# Documentation for enabling Git events in the audit log
|
||||
versions:
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-7283'
|
||||
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6344'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7757
|
||||
# Setting to disable personal namespace repo creation for EMUs, GHES 3.7+ and GHAE 3.7+ users
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7757'
|
||||
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-5740'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: Issue #7579 - Improved file finder exclusion controls
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7579'
|
||||
5
translations/pt-BR/data/features/geoJSON-with-MapBox.yml
Normal file
5
translations/pt-BR/data/features/geoJSON-with-MapBox.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #7429
|
||||
# Dotcom now uses Azure maps for geoJSON, but GHES/AE will still use the existing MapBox system
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
@@ -0,0 +1,5 @@
|
||||
# docs-content 7314. GHAS enablement webhook
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>= 3.6'
|
||||
ghae: 'issue-7314'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: #2221.
|
||||
# Documentation for dismissing GHES announcement banner
|
||||
versions:
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6764'
|
||||
4
translations/pt-BR/data/features/internal-actions.yml
Normal file
4
translations/pt-BR/data/features/internal-actions.yml
Normal file
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-5610'
|
||||
@@ -0,0 +1,3 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghae: 'issue-7818'
|
||||
7
translations/pt-BR/data/features/issue-close-reasons.yml
Normal file
7
translations/pt-BR/data/features/issue-close-reasons.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issues 6363
|
||||
# Closed issue states
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6363'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6530
|
||||
# Running scripts before or after a job
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6530'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #4999.
|
||||
# Documentation for the security manager org-level role
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.4'
|
||||
ghae: 'issue-5430'
|
||||
ghec: '*'
|
||||
7
translations/pt-BR/data/features/math.yml
Normal file
7
translations/pt-BR/data/features/math.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issues 6054
|
||||
# Math support using LaTeX syntax
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6054'
|
||||
7
translations/pt-BR/data/features/mermaid.yml
Normal file
7
translations/pt-BR/data/features/mermaid.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issues 5812 and 6172, also 6411
|
||||
# Mermaid syntax support, also ASCII STL and geoJSON/topoJSON syntax support
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-6172'
|
||||
7
translations/pt-BR/data/features/motion-management.yml
Normal file
7
translations/pt-BR/data/features/motion-management.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 6523
|
||||
# Support for customizing the automatic playback of animated images in the web interface
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6523'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issue #7330
|
||||
# Documentation for managing multiple GitHub accounts on one workstation
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issues 7093
|
||||
# Reusable workflows can call other reusable workflows
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7093'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue #6171
|
||||
# Documentation for the "Org profile pin private/internal repos"
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6171'
|
||||
5
translations/pt-BR/data/features/packages-npm-v2.yml
Normal file
5
translations/pt-BR/data/features/packages-npm-v2.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Issue 7039
|
||||
# npm Package Registry Improvements (v2) GA
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Issue 7066
|
||||
# Publishing Pages via custom Actions workflow
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issue #7062
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-7062'
|
||||
7
translations/pt-BR/data/features/pr-tree-view.yml
Normal file
7
translations/pt-BR/data/features/pr-tree-view.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 5892
|
||||
# PR file tree view
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-5892'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Issue 6981
|
||||
# Projects (beta) webhooks
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Issue 7302
|
||||
# ProjectV2 GraphQL API
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
8
translations/pt-BR/data/features/projects-v1.yml
Normal file
8
translations/pt-BR/data/features/projects-v1.yml
Normal file
@@ -0,0 +1,8 @@
|
||||
# Issue 6980
|
||||
# Projects (classic)
|
||||
# n.b. /managing-project-boards/copying-a-project-board.md retains ghec/fpt versioning.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
6
translations/pt-BR/data/features/projects-v2.yml
Normal file
6
translations/pt-BR/data/features/projects-v2.yml
Normal file
@@ -0,0 +1,6 @@
|
||||
# Issue 6980
|
||||
# ProjectV2 GA
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghae: 'issue-6980'
|
||||
@@ -0,0 +1,8 @@
|
||||
# Issue 7299
|
||||
# Push protection custom links beta flags
|
||||
# See "push-protection-custom-link-orgs" for the feature
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7299'
|
||||
@@ -0,0 +1,8 @@
|
||||
# Issue 7299
|
||||
# Push protection custom links
|
||||
# See "push-protection-custom-link-orgs-beta" for the beta flags
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7299'
|
||||
7
translations/pt-BR/data/features/re-run-jobs.yml
Normal file
7
translations/pt-BR/data/features/re-run-jobs.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 4722
|
||||
# Re-running failed jobs in an Actions workflow
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-4722'
|
||||
@@ -0,0 +1,3 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghae: 'issue-5739'
|
||||
@@ -0,0 +1,4 @@
|
||||
# Reference 7394
|
||||
# Documentation for the option to enforce TLS encryption for incoming SMTP connections
|
||||
versions:
|
||||
ghes: '>=3.6'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 6384
|
||||
# Required deployments branch protection rule
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6384'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issues: changes to custom patterns for secret scanning
|
||||
# #6367: updates for the "organization level dry runs (Public Beta)"
|
||||
# #5499: updates for the "repository level dry runs (Public Beta)"
|
||||
versions:
|
||||
ghes: '>3.4 <3.7'
|
||||
ghae: 'issue-6367'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issues: changes to custom patterns for secret scanning
|
||||
# #6904: updates for "enterprise account level dry runs (Public Beta)"
|
||||
# #7297: updates for dry runs on editing patterns (Public Beta)
|
||||
versions:
|
||||
ghes: '>3.5 <3.7'
|
||||
ghae: 'issue-6904'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #5620.
|
||||
# Documentation for secret scanning as a push protection
|
||||
versions:
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-5620'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,4 @@
|
||||
# Reference: Issue #6982 Community Contributions to Security Advisories - Enterprise 3.6
|
||||
versions:
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6982'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7114.
|
||||
# Documentation for security overview availability to all enterprise accounts.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7114'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #7028.
|
||||
# Documentation for feature-specific page for security overview at enterprise-level.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-7028'
|
||||
@@ -0,0 +1,8 @@
|
||||
# Reference: github/docs-content#6709
|
||||
# Initial docs for showing SSH signed commits as verified and
|
||||
# uploading SSH signing keys
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>= 3.7'
|
||||
ghae: '*'
|
||||
5
translations/pt-BR/data/features/svg-support.yml
Normal file
5
translations/pt-BR/data/features/svg-support.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Releases issue #1951
|
||||
# Support upload of SVG files
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
7
translations/pt-BR/data/features/syncing-fork-web-ui.yml
Normal file
7
translations/pt-BR/data/features/syncing-fork-web-ui.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Issue 7629
|
||||
# Improved UI for manually syncing a fork
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7629'
|
||||
@@ -0,0 +1,6 @@
|
||||
# TOTP and mobile challenge for sudo mode prompt.
|
||||
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>= 3.7'
|
||||
@@ -0,0 +1,8 @@
|
||||
# Issue: 7123
|
||||
# Description: Allow adding expired and revoked GPG keys for verifying commit and tag signatures
|
||||
# Usage: {% ifversion upload-expired-or-revoked-gpg-key %} ... {% endif %}
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-7123'
|
||||
139
translations/pt-BR/data/learning-tracks/admin.yml
Normal file
139
translations/pt-BR/data/learning-tracks/admin.yml
Normal file
@@ -0,0 +1,139 @@
|
||||
get_started_with_github_ae:
|
||||
title: 'Introdução ao {% data variables.product.prodname_ghe_managed %}'
|
||||
description: 'Saiba mais sobre {% data variables.product.prodname_ghe_managed %} e realize a configuração inicial de uma nova empresa.'
|
||||
featured_track: true
|
||||
versions:
|
||||
ghae: '*'
|
||||
guides:
|
||||
- /admin/overview/about-github-ae
|
||||
- /admin/overview/about-data-residency
|
||||
- /admin/configuration/configuring-your-enterprise/deploying-github-ae
|
||||
- /admin/configuration/initializing-github-ae
|
||||
- /admin/configuration/restricting-network-traffic-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-github-ae
|
||||
|
||||
deploy_an_instance:
|
||||
title: 'Implante uma instância'
|
||||
description: 'Instale {% data variables.product.prodname_ghe_server %} na sua plataforma de escolha e configure a autenticação SAML.'
|
||||
featured_track: true
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/overview/system-overview
|
||||
- /admin/installation
|
||||
- /admin/configuration/accessing-the-management-console
|
||||
- /admin/configuration/configuring-a-hostname
|
||||
- /admin/authentication/using-saml
|
||||
- /admin/configuration/site-admin-dashboard
|
||||
|
||||
upgrade_your_instance:
|
||||
title: 'Atualize sua instância'
|
||||
description: 'Teste as atualizações no treinamento, notifique os usuários de manutenção e atualize sua instância para os recursos e atualizações de segurança mais recentes.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/enterprise-management/enabling-automatic-update-checks
|
||||
- /admin/installation/setting-up-a-staging-instance
|
||||
- /admin/enterprise-management/upgrade-requirements
|
||||
- /admin/user-management/customizing-user-messages-for-your-enterprise
|
||||
- /admin/configuration/enabling-and-scheduling-maintenance-mode
|
||||
- /admin/enterprise-management/upgrading-github-enterprise-server
|
||||
|
||||
adopting_github_actions_for_your_enterprise_ghec:
|
||||
title: 'Adote o GitHub Actions na sua empresa'
|
||||
description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
guides:
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
- /actions/learn-github-actions/understanding-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
- /billing/managing-billing-for-github-actions/about-billing-for-github-actions
|
||||
|
||||
adopting_github_actions_for_your_enterprise_ghes_and_ghae:
|
||||
title: 'Adote o GitHub Actions na sua empresa'
|
||||
description: 'Saiba como planejar e implementar uma implantação de {% data variables.product.prodname_actions %} na sua empresa.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
guides:
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises
|
||||
- /actions/learn-github-actions/understanding-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/migrating-your-enterprise-to-github-actions
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-cloud
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
- /billing/managing-billing-for-github-actions/about-billing-for-github-actions
|
||||
|
||||
increase_fault_tolerance:
|
||||
title: 'Aumente a tolerância de falha da instância'
|
||||
description: "Faça backup do código de seus desenvolvedores e configure HA (alta disponibilidade) para garantir a confiabilidade do {% data variables.product.prodname_ghe_server %} em seu ambiente."
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/configuration/accessing-the-administrative-shell-ssh
|
||||
- /admin/configuration/configuring-backups-on-your-appliance
|
||||
- /admin/enterprise-management/about-high-availability-configuration
|
||||
- /admin/enterprise-management/creating-a-high-availability-replica
|
||||
- /admin/configuration/using-github-enterprise-server-with-a-load-balancer
|
||||
|
||||
improve_security_of_your_instance:
|
||||
title: 'Melhore a segurança da sua instância'
|
||||
description: "Revise a configuração de rede e as funcionalidades de segurança e reforce a instância do {% data variables.product.prodname_ghe_server %} em execução para proteger os dados da sua empresa."
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/configuration/enabling-private-mode
|
||||
- /admin/guides/installation/configuring-tls
|
||||
- /admin/configuration/troubleshooting-ssl-errors
|
||||
- /admin/configuration/enabling-subdomain-isolation
|
||||
- /admin/configuration/accessing-the-administrative-shell-ssh
|
||||
- /admin/configuration/network-ports
|
||||
- /admin/configuration/configuring-built-in-firewall-rules
|
||||
- /admin/user-management/best-practices-for-user-security
|
||||
- /admin/user-management/promoting-or-demoting-a-site-administrator
|
||||
|
||||
configure_github_actions:
|
||||
title: 'Configure o {% data variables.product.prodname_actions %}'
|
||||
description: 'Permita que seus desenvolvedores criem, automatizem, personalizem e executem fluxos de trabalho de desenvolvimento avançados de software em {% data variables.product.product_location %} com {% data variables.product.prodname_actions %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server
|
||||
- /admin/github-actions/enforcing-github-actions-policies-for-your-enterprise
|
||||
- /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
|
||||
- /admin/github-actions/high-availability-for-github-actions
|
||||
- /admin/github-actions/backing-up-and-restoring-github-enterprise-server-with-github-actions-enabled
|
||||
- /admin/github-actions/using-a-staging-environment
|
||||
|
||||
configure_github_advanced_security:
|
||||
title: 'Configure {% data variables.product.prodname_GH_advanced_security %}'
|
||||
description: "Melhore a qualidade e a segurança do código do seu desenvolvedor com {% data variables.product.prodname_GH_advanced_security %}."
|
||||
versions:
|
||||
ghes: '*'
|
||||
guides:
|
||||
- /admin/advanced-security/about-licensing-for-github-advanced-security
|
||||
- /admin/advanced-security/enabling-github-advanced-security-for-your-enterprise
|
||||
- /admin/advanced-security/configuring-code-scanning-for-your-appliance
|
||||
- /admin/code-security/managing-github-advanced-security-for-your-enterprise/configuring-dependency-review-for-your-appliance
|
||||
- /admin/advanced-security/configuring-secret-scanning-for-your-appliance
|
||||
- /admin/policies/enforcing-policies-for-advanced-security-in-your-enterprise
|
||||
|
||||
get_started_with_your_enterprise_account:
|
||||
title: 'Comece a usar a sua conta corporativa'
|
||||
description: 'Comece com sua conta corporativa para gerenciar centralmente várias organizações em {% data variables.product.product_name %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
guides:
|
||||
- /admin/overview/about-enterprise-accounts
|
||||
- /billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise
|
||||
- /admin/user-management/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
|
||||
- /admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise
|
||||
- /admin/authentication/managing-identity-and-access-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise
|
||||
- /admin/policies/enforcing-policies-for-your-enterprise/about-enterprise-policies
|
||||
@@ -1,7 +1,7 @@
|
||||
# Feature available only on dotcom
|
||||
security_advisories:
|
||||
title: 'Fix and disclose a security vulnerability'
|
||||
description: 'Using repository security advisories to privately fix a reported vulnerability and get a CVE.'
|
||||
title: 'Corrigir e divulgar uma vulnerabilidade de segurança'
|
||||
description: 'Uso de consultorias de segurança do repositório para corrigir de forma privada uma vulnerabilidade relatada e obter um CVE.'
|
||||
featured_track: '{% ifversion fpt or ghec %}true{% else %}false{% endif %}'
|
||||
guides:
|
||||
- /code-security/repository-security-advisories/about-coordinated-disclosure-of-security-vulnerabilities
|
||||
@@ -15,8 +15,8 @@ security_advisories:
|
||||
|
||||
# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
|
||||
dependabot_alerts:
|
||||
title: 'Get notifications for insecure dependencies'
|
||||
description: 'Set up Dependabot to alert you to new vulnerabilities{% ifversion GH-advisory-db-supports-malware %} or malware{% endif %} in your dependencies.'
|
||||
title: 'Obter notificações para dependências inseguras'
|
||||
description: 'Configure o Dependabot para alertar sobre novas vulnerabilidades{% ifversion GH-advisory-db-supports-malware %} ou malware{% endif %} em suas dependências.'
|
||||
guides:
|
||||
- /code-security/dependabot/dependabot-alerts/about-dependabot-alerts
|
||||
- '{% ifversion fpt or ghec or ghes > 3.2 %}/github/administering-a-repository/managing-repository-settings/managing-security-and-analysis-settings-for-your-repository{% endif %}'
|
||||
@@ -28,8 +28,8 @@ dependabot_alerts:
|
||||
|
||||
# Feature available on dotcom and GHES 3.3+, so articles available on GHAE and earlier GHES hidden to hide the learning track
|
||||
dependabot_security_updates:
|
||||
title: 'Get pull requests to update your vulnerable dependencies'
|
||||
description: 'Set up Dependabot to create pull requests when new vulnerabilities are reported.'
|
||||
title: 'Obtenha solicitações de pull para atualizar suas dependências vulneráveis'
|
||||
description: 'Configure o Dependabot para criar solicitações de pull quando novas vulnerabilidades forem relatadas.'
|
||||
guides:
|
||||
- /code-security/dependabot/dependabot-security-updates/about-dependabot-security-updates
|
||||
- /code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates
|
||||
@@ -40,8 +40,8 @@ dependabot_security_updates:
|
||||
|
||||
# Feature available only on dotcom and GHES 3.3+
|
||||
dependency_version_updates:
|
||||
title: 'Keep your dependencies up-to-date'
|
||||
description: 'Use Dependabot to check for new releases and create pull requests to update your dependencies.'
|
||||
title: 'Mantenha suas dependências atualizadas'
|
||||
description: 'Use o Dependabot para verificar novas versões e criar solicitações de pull para atualizar suas dependências.'
|
||||
guides:
|
||||
- /code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
|
||||
- /code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates
|
||||
@@ -56,8 +56,8 @@ dependency_version_updates:
|
||||
|
||||
# Feature available in GHEC, GHES 3.0 up, and GHAE. Feature limited on FPT so hidden there.
|
||||
secret_scanning:
|
||||
title: 'Scan for secrets'
|
||||
description: 'Set up secret scanning to guard against accidental check-ins of tokens, passwords, and other secrets to your repository.'
|
||||
title: 'Examinar em busca de segredos'
|
||||
description: 'Configure o exame de segredos para evitar verificações acidentais de tokens, senhas e outros segredos do seu repositório.'
|
||||
guides:
|
||||
- '{% ifversion not fpt %}/code-security/secret-scanning/about-secret-scanning{% endif %}'
|
||||
- '{% ifversion not fpt %}/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories{% endif %}'
|
||||
@@ -69,8 +69,8 @@ secret_scanning:
|
||||
|
||||
# Security overview feature available in GHEC and GHES 3.2+, so other articles hidden to hide the learning path in other versions
|
||||
security_alerts:
|
||||
title: 'Explore and manage security alerts'
|
||||
description: 'Learn where to find and resolve security alerts.'
|
||||
title: 'Explore e gerencie alertas de segurança'
|
||||
description: 'Saiba onde encontrar e como resolver alertas de segurança.'
|
||||
guides:
|
||||
- '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/about-the-security-overview {% endif %}'
|
||||
- '{% ifversion ghec or ghes > 3.1 %}/code-security/security-overview/viewing-the-security-overview {% endif %}'
|
||||
@@ -81,8 +81,8 @@ security_alerts:
|
||||
|
||||
# Feature available in all versions from GHES 2.22 up
|
||||
code_security_actions:
|
||||
title: 'Run code scanning with GitHub Actions'
|
||||
description: 'Check your default branch and every pull request to keep vulnerabilities and errors out of your repository.'
|
||||
title: 'Execute o exame de código com o GitHub Actions'
|
||||
description: 'Verifique seu branch padrão e cada solicitação de pull para manter seu repositório sem vulnerabilidades e erros.'
|
||||
featured_track: '{% ifversion ghae or ghes %}true{% else %}false{% endif %}'
|
||||
guides:
|
||||
- /code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
|
||||
@@ -94,8 +94,8 @@ code_security_actions:
|
||||
|
||||
# Feature available in all versions from GHES 2.22 up
|
||||
code_security_integration:
|
||||
title: 'Integrate with code scanning'
|
||||
description: 'Upload code analysis results from third-party systems to GitHub using SARIF.'
|
||||
title: 'Integrar com o exame de código'
|
||||
description: 'Faça o upload de resultados da análises de código de sistemas de terceiros para o GitHub usando o SARIF.'
|
||||
guides:
|
||||
- /code-security/code-scanning/integrating-with-code-scanning/about-integration-with-code-scanning
|
||||
- /code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github
|
||||
@@ -104,8 +104,8 @@ code_security_integration:
|
||||
|
||||
# Feature available in all versions from GHES 2.22 up
|
||||
code_security_ci:
|
||||
title: 'Run CodeQL code scanning in your CI'
|
||||
description: 'Set up CodeQL within your existing CI and upload results to GitHub code scanning.'
|
||||
title: 'Execute o exame de código CodeQL na sua CI'
|
||||
description: 'Configure o CodeQL dentro da sua CI existente e faça o upload dos resultados para o exame de código do GitHub.'
|
||||
guides:
|
||||
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system
|
||||
- /code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/installing-codeql-cli-in-your-ci-system
|
||||
@@ -115,8 +115,8 @@ code_security_ci:
|
||||
|
||||
# Feature available in all versions
|
||||
end_to_end_supply_chain:
|
||||
title: 'End-to-end supply chain'
|
||||
description: 'How to think about securing your user accounts, your code, and your build process.'
|
||||
title: 'Cadeia de suprimentos de ponta a ponta'
|
||||
description: 'Como considerar a proteção de suas contas de usuário, códigos e processos de criação.'
|
||||
guides:
|
||||
- /code-security/supply-chain-security/end-to-end-supply-chain/end-to-end-supply-chain-overview
|
||||
- /code-security/supply-chain-security/end-to-end-supply-chain/securing-accounts
|
||||
|
||||
@@ -0,0 +1,44 @@
|
||||
date: '2020-02-11'
|
||||
sections:
|
||||
features:
|
||||
- 'Em um branch de repositório, os administradores do repositório podem rejeitar qualquer push que contenha um commit de merge, habilitando "Exigir histórico linear" ao usar [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}'
|
||||
- 'Os administradores de repositório podem conceder a todos os usuários com acesso push a capacidade de fazer push forçado para um branch protegido, habilitando "Permitir pushes forçados" e usando [regras de proteção de branch](https://help. ithub.com/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/, https://github.com/github/ce-oss-happiness/issues/42, https://github.com/github/github/pull/125950 {% endcomment %}'
|
||||
- 'Os administradores do repositório podem conceder a todos os usuários com acesso push a capacidade de excluir um branch protegido, habilitando "Permitir exclusões" e usando [regras de proteção de branch](https://help.github. om/en/github/adadministrtering-a-repository/enabling-branch-restrictions). {% comment %} https://github.blog/changelog/2019-12-04-expanded-branch-protection-rules/ {% endcomment %}'
|
||||
- 'Os administradores podem definir um limite "maxobjectsize" nos repositórios, [limitando o tamanho do commits de push](https://help.github.com/en/enterprise/admin/installation/setting-git-push-limits) para um repositório que não estão em [Git LFS](https://help.github. om/en/enterprise/admin/installation/configuring-git-large-file-storage-on-github-enterprise-server). {% comment %} https://github.com/github/babeld/pull/864, https://team.githubapp.com/posts/33519, https://github.com/githubcustomers/Slack/issues/27 {% endcomment %}'
|
||||
- 'Os proprietários da organização podem criar um conjunto de etiquetas-padrão ao criar um novo repositório.{% comment %} https://github.com/github/issues-projects/issues/237, https://github.com/github/issues-projects/issues/179 {% endcomment %}'
|
||||
security_fixes:
|
||||
- Os pacotes foram atualizados para as últimas versões de segurança.
|
||||
bugs:
|
||||
- 'Quando um integrante de uma organização tentou visualizar um repositório público nessa organização, um prompt SSO poderia corromper a exibição da página. {% comment %} https://github.com/github/github/issues/126677, https://github.com/github/github/pull/127501 {% endcomment %}'
|
||||
- "Ao visualizar o perfil de usuários, os links para as equipes dos usuários poderiam estar corrompidos. {% comment %} https://github.com/github/github/issues/131771, https://github.com/github/github/pull/131865 {% endcomment %}"
|
||||
- 'Usuários com a função "manter" não conseguiram editar os tópicos do repositório. {% comment %} https://github.com/github/github/pull/129503, https://github.com/github/github/issues/119456 {% endcomment %}'
|
||||
- "Um usuário que não é um administrador em uma organização receberá um erro 500 ao tentar acessar a página de inscrição. {% comment %} https://github. om/github/github/pull/129213, https://github.com/github/github/issues/129210, https://github.com/github/github/issues/129212 {% endcomment %}"
|
||||
- 'O pop-up de histórico de edição não apareceria nos comentários do gist. {% comment %} https://github.com/github/github/pull/129134, https://github.com/github/github/issues/128496 {% endcomment %}'
|
||||
- 'Foi possível registrar uma nova conta com um e-mail que já foi registrado. {% comment %} https://github.com/github/github/pull/127905, https://github.com/github/github/issues/127858 {% endcomment %}'
|
||||
- 'Um serviço de armazenamento estava atingindo um limite de descritor de arquivos e deixando o kernel pendurado e outros serviços de log de erros. {% comment %} https://github.com/github/enterprise2/pull/18775 {% endcomment %}'
|
||||
- 'Quando uma referência de link automático fazia parte de uma url, era possível remover o hiperlink. {% comment %} https://github.com/github/github/pull/126776 {% endcomment %}'
|
||||
- 'Ao adicionar um comentário a um pull request, a seção "Problemas vinculados" da barra lateral poderia desaparecer. {% comment %} https://github.com/github/issues-projects/issues/384, https://github.com/github/github/pull/130514 {% endcomment %}'
|
||||
- 'Ao editar um convite existente de organização para um usuário, é possível que um cabeçalho duplicado apareça na tabela "Equipes". {% comment %} https://github.com/github/github/issues/120381, https://github.com/github/github/pull/128939 {% endcomment %}'
|
||||
- 'O serviço "resqued" conseguiu parar de registrar eventos quando as filas se tornaram grandes demais. {% comment %} https://github.com/github/github/pull/130087, https://github.com/github/business-support/issues/2696 {% endcomment %}'
|
||||
- 'Certificados autoassinados não são gerados automaticamente ao executar o comando "ghe-config-apply" para cluster e alta disponibilidade. {% comment %} https://github.com/github/enterprise2/pull/18773 {% endcomment %}'
|
||||
changes:
|
||||
- 'Nenhum logotipo será exibido para um tópico se um não tiver sido carregado. {% comment %} https://github.com/github/github/issues/130513, https://github.com/github/github/pull/130515 {% endcomment %}'
|
||||
- 'Ao ver um problema em um navegador móvel, os metadados do problema serão listados na parte superior da página. {% comment %} https://github.com/github/github/pull/127560 {% endcomment %}'
|
||||
- 'O domínio de nível superior do Cônsul mudou de ".consul" para ".ghe.local". {% comment %} https://github.com/github/enterprise2/pull/17443, https://github.com/github/enterprise2/issues/17701 {% endcomment %}'
|
||||
- 'O serviço de hookshot não depende mais do ElasticSearch e usa apenas o MySQL como uma loja de banco de dados. {% comment %} https://github.com/github/enterprise2/pull/18158, https://github.com/github/hookshot/pull/1128, https://github.com/github/enterprise2/pull/15898 {% endcomment %}'
|
||||
- 'Implementou-se uma distinção visual aprimorada entre problema, projeto e discussão nos cartões de notas do projeto. {% comment %} https://github.com/github/github/pull/132038 {% endcomment %}'
|
||||
- 'Em uma revisão de pull request, um aviso é exibido se um comentário linha múltipla for truncado. {% comment %} https://github.com/github/github/issues/125948, https://github.com/github/github/pull/128677 {% endcomment %}'
|
||||
- 'Os usuários podem ver seus logs de auditoria na aba "Log de segurança" nas suas configurações pessoais. {% comment %} https://github.com/github/github/pull/123041{% endcomment %}'
|
||||
known_issues:
|
||||
- 'Em uma nova configuração do GitHub Enterprise Server sem qualquer usuário, um invasor pode criar o primeiro usuário administrador. {% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- 'As regras personalizadas do firewall não são mantidas em um upgrade. {% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Arquivos LFS do Git [enviados através da interface Web](https://github.com/blog/2105-upload-files-to-your-repositories) são adicionados diretamente ao repositório e de maneira incorreta. {% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- 'Os problemas não podem ser fechados se contiverem um permalink para um blob no mesmo repositório em que o caminho do arquivo tem mais de 255 caracteres. {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- 'Ao efetuar push em um gist, pode-se adicionar uma exceção durante o hook de post-receive. {% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- "Entradas duplicadas de webhook no banco de dados podem gerar falha de atualizações de versões anteriores. (atualizada 2020-02-26)"
|
||||
- 'As atualizações e as definições de atualização falharão se as configurações em segundo plano do trabalhador forem personalizadas. {% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}'
|
||||
- 'Quando "Usuários podem pesquisar no GitHub.com" está habilitado com o GitHub Connect, os problemas nos repositórios privados e internos não estão incluídos nos resultados de pesquisa do GitHub.com. {% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- 'Ao atualizar de versões anteriores, os trabalhadores dos trabalho em segundo plano podem não ser gerados, evitando recursos essenciais como fazer mesclagem de solicitações de pull. (atualizado 2020-04-07) {% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- 'Os alertas de segurança não são relatados ao efetuar push em um repositório na linha de comando. (atualizado 2020-06-23) {% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- 'O grafo de dependências não é a detecção de dependências quando implantadas em uma configuração de cluster com vários nós de Redis. (atualizado 2020-06-30) {% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- 'Quando um nó de réplica está offline em uma configuração de alta disponibilidade, {% data variables.product.product_name %} ainda pode encaminhar solicitações de {% data variables.product.prodname_pages %} para o nó offline, reduzindo a disponibilidade de {% data variables.product.prodname_pages %} para os usuários.'
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user