Octomerger Bot
@@ -52,7 +52,13 @@ Setting secondary rate limits protects the overall level of service on {% data v
|
||||
|
||||
## Enabling rate limits for Git
|
||||
|
||||
You can apply Git rate limits per repository network or per user ID. Git rate limits are expressed in concurrent operations per minute, and are adaptive based on the current CPU load.
|
||||
If a member of {% data variables.product.company_short %}'s staff has recommended it, you can apply Git rate limits per repository network or per user ID. Git rate limits are expressed in concurrent operations per minute, and are adaptive based on the current CPU load.
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** We encourage you to leave this setting disabled unless directly recommended by a member of {% data variables.product.company_short %}'s staff. Git operations are rarely the leading driver of CPU and RAM usage. Enabling this feature can make Git operations more likely to fail under high load conditions but does not address the underlying cause of those conditions.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% data reusables.enterprise_site_admin_settings.access-settings %}
|
||||
{% data reusables.enterprise_site_admin_settings.management-console %}
|
||||
|
||||
@@ -172,6 +172,7 @@ translations/zh-CN/content/rest/reference/users.md,file deleted because it no lo
|
||||
translations/zh-CN/content/rest/reference/webhooks.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/content/site-policy/github-terms/github-community-forum-code-of-conduct.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-user-account.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/glossaries/internal.yml,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/graphql/ghes-3.1/graphql_previews.enterprise.yml,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group-access.md,file deleted because it no longer exists in main
|
||||
translations/zh-CN/data/reusables/actions/self-hosted-runner-configure-runner-group.md,file deleted because it no longer exists in main
|
||||
@@ -259,6 +260,7 @@ translations/zh-CN/content/actions/hosting-your-own-runners/managing-access-to-s
|
||||
translations/zh-CN/content/actions/learn-github-actions/contexts.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/learn-github-actions/understanding-github-actions.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/publishing-packages/publishing-docker-images.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
|
||||
translations/zh-CN/content/actions/quickstart.md,rendering error
|
||||
translations/zh-CN/content/actions/security-guides/automatic-token-authentication.md,broken liquid tags
|
||||
@@ -415,14 +417,37 @@ translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-f
|
||||
translations/zh-CN/content/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/releasing-projects-on-github/managing-releases-in-a-repository.md,broken liquid tags
|
||||
translations/zh-CN/content/repositories/working-with-files/using-files/working-with-non-code-files.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/guides/getting-started-with-the-rest-api.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/overview/other-authentication-methods.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/overview/resources-in-the-rest-api.md,broken liquid tags
|
||||
translations/zh-CN/content/rest/repos/lfs.md,broken liquid tags
|
||||
translations/zh-CN/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md,rendering error
|
||||
translations/zh-CN/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,broken liquid tags
|
||||
translations/zh-CN/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
|
||||
translations/zh-CN/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account.md,broken liquid tags
|
||||
translations/zh-CN/content/support/learning-about-github-support/about-github-support.md,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-21/6.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/0.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/2.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/22.yml,broken liquid tags
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/3.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/7.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/8.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/2-22/9.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/0.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/2.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-0/3.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/2.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-1/4.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-2/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-3/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/enterprise-server/3-4/0-rc1.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/github-ae/2021-03/2021-03-03.yml,rendering error
|
||||
translations/zh-CN/data/release-notes/github-ae/2021-06/2021-12-06.yml,rendering error
|
||||
translations/zh-CN/data/reusables/actions/about-actions-for-enterprises.md,rendering error
|
||||
translations/zh-CN/data/reusables/actions/actions-audit-events-workflow.md,broken liquid tags
|
||||
translations/zh-CN/data/reusables/actions/actions-billing.md,broken liquid tags
|
||||
|
||||
|
@@ -262,6 +262,7 @@ translations/pt-BR/content/actions/hosting-your-own-runners/managing-access-to-s
|
||||
translations/pt-BR/content/actions/learn-github-actions/contexts.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/learn-github-actions/understanding-github-actions.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/managing-workflow-runs/re-running-workflows-and-jobs.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/publishing-packages/publishing-docker-images.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/publishing-packages/publishing-nodejs-packages.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/security-guides/automatic-token-authentication.md,broken liquid tags
|
||||
translations/pt-BR/content/actions/security-guides/encrypted-secrets.md,broken liquid tags
|
||||
@@ -392,6 +393,7 @@ translations/pt-BR/content/packages/learn-github-packages/about-permissions-for-
|
||||
translations/pt-BR/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md,broken liquid tags
|
||||
translations/pt-BR/content/packages/learn-github-packages/deleting-and-restoring-a-package.md,broken liquid tags
|
||||
translations/pt-BR/content/packages/learn-github-packages/viewing-packages.md,broken liquid tags
|
||||
translations/pt-BR/content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md,broken liquid tags
|
||||
translations/pt-BR/content/pages/getting-started-with-github-pages/creating-a-github-pages-site.md,broken liquid tags
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request.md,broken liquid tags
|
||||
translations/pt-BR/content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request.md,broken liquid tags
|
||||
@@ -405,6 +407,8 @@ translations/pt-BR/content/rest/overview/resources-in-the-rest-api.md,broken liq
|
||||
translations/pt-BR/content/rest/repos/lfs.md,broken liquid tags
|
||||
translations/pt-BR/content/search-github/searching-on-github/searching-issues-and-pull-requests.md,broken liquid tags
|
||||
translations/pt-BR/content/site-policy/privacy-policies/github-subprocessors-and-cookies.md,broken liquid tags
|
||||
translations/pt-BR/content/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization.md,broken liquid tags
|
||||
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,broken liquid tags
|
||||
translations/pt-BR/data/glossaries/external.yml,broken liquid tags
|
||||
translations/pt-BR/data/learning-tracks/code-security.yml,broken liquid tags
|
||||
|
||||
|
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Publicando imagens do Docker
|
||||
intro: 'Você pode publicar imagens Docker para um registro, como o Docker Hub ou {% data variables.product.prodname_registry %}, como parte do seu fluxo de trabalho de integração contínua (CI).'
|
||||
title: Publishing Docker images
|
||||
intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/publishing-docker-images
|
||||
- /actions/guides/publishing-docker-images
|
||||
@@ -14,61 +14,63 @@ topics:
|
||||
- Packaging
|
||||
- Publishing
|
||||
- Docker
|
||||
ms.openlocfilehash: 01f20527dedeea3685855797993187e7af462de4
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147410288'
|
||||
---
|
||||
{% 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 %}
|
||||
|
||||
Este guia mostra como criar um fluxo de trabalho que realiza uma criação do Docker e, em seguida, publica imagens do Docker no Docker Hub ou no {% data variables.product.prodname_registry %}. Com um único fluxo de trabalho, você pode publicar imagens em um único registro ou em vários registros.
|
||||
## Introduction
|
||||
|
||||
This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Observação:** caso você deseje efetuar push para outro registro do Docker de terceiros, o exemplo descrito na seção "[Como publicar imagens no {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" pode servir como um bom modelo.
|
||||
**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## Pré-requisitos
|
||||
## Prerequisites
|
||||
|
||||
Recomendamos que você tenha um entendimento básico das opções de configuração do fluxo de trabalho e de como criar um arquivo do fluxo de trabalho. Para obter mais informações, confira "[Aprenda a usar o {% data variables.product.prodname_actions %}](/actions/learn-github-actions)".
|
||||
We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
Você também pode achar útil ter um entendimento básico do seguinte:
|
||||
You might also find it helpful to have a basic understanding of the following:
|
||||
|
||||
- "[Segredos criptografados](/actions/reference/encrypted-secrets)"
|
||||
- "[Autenticação em um fluxo de trabalho](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
|
||||
- "[Como trabalhar com o {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
|
||||
- "[Como trabalhar com o registro do Docker](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
|
||||
- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
|
||||
- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
|
||||
- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
|
||||
- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
|
||||
|
||||
## Sobre a configuração da imagem
|
||||
## About image configuration
|
||||
|
||||
Este guia pressupõe que você tem uma definição completa para uma imagem Docker armazenada em um repositório {% data variables.product.prodname_dotcom %}. Por exemplo, seu repositório precisa conter um _Dockerfile_ e todos os outros arquivos necessários para executar um build do Docker para criar uma imagem.
|
||||
This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
|
||||
|
||||
Neste guia, usaremos a ação `build-push-action` do Docker para compilar a imagem do Docker e efetuar push dela para um ou mais registros do Docker. Para obter mais informações, confira [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
|
||||
{% data reusables.package_registry.about-docker-labels %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry#labelling-container-images)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
|
||||
|
||||
{% data reusables.actions.enterprise-marketplace-actions %}
|
||||
|
||||
## Publicar imagens no Docker Hub
|
||||
## Publishing images to Docker Hub
|
||||
|
||||
{% data reusables.actions.release-trigger-workflow %}
|
||||
|
||||
No exemplo de fluxo de trabalho abaixo, usaremos as ações `login-action` e `build-push-action` do Docker para compilar a imagem do Docker e, se o build for bem-sucedido, efetuaremos push da imagem compilada para o Docker Hub.
|
||||
In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
|
||||
|
||||
Para fazer push para o Docker Hub, você deverá ter uma conta Docker Hub e ter criado um repositório Docker Hub. Para obter mais informações, confira "[Como efetuar push de uma imagem de contêiner do Docker para o Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" na documentação do Docker.
|
||||
To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
|
||||
|
||||
As opções `login-action` necessárias para o Docker Hub são:
|
||||
* `username` e `password`: esse é seu nome de usuário e sua senha do Docker Hub. Recomendamos armazenar seu nome de usuário e senha do Docker Hub como segredos para que não estejam expostos no seu arquivo de fluxo de trabalho. Para obter mais informações, confira "[Como criar e usar segredos criptografados](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)".
|
||||
The `login-action` options required for Docker Hub are:
|
||||
* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
|
||||
|
||||
A opção `metadata-action` obrigatória para o Docker Hub é:
|
||||
* `images`: o namespace e o nome da imagem do Docker que você está compilando/enviando por push para o Docker Hub.
|
||||
The `metadata-action` option required for Docker Hub is:
|
||||
* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
|
||||
|
||||
As opções `build-push-action` necessárias para o Docker Hub são:
|
||||
* `tags`: a marca da nova imagem no formato `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.
|
||||
* `push`: se isso for definido como `true`, a imagem será enviada por push para o registro se for compilada com sucesso.
|
||||
The `build-push-action` options required for Docker Hub are:
|
||||
* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
|
||||
* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
@@ -110,38 +112,42 @@ jobs:
|
||||
labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
|
||||
```
|
||||
|
||||
O fluxo de trabalho acima faz check-out do repositório do {% data variables.product.prodname_dotcom %}, usa `login-action` para fazer logon no registro e usa a ação `build-push-action` para: compilar uma imagem do Docker com base no `Dockerfile` do seu repositório, efetuar push da imagem para o Docker Hub e aplicar uma marca à imagem.
|
||||
The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
|
||||
|
||||
## Publicar imagens em {% data variables.product.prodname_registry %}
|
||||
## Publishing images to {% data variables.product.prodname_registry %}
|
||||
|
||||
{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
|
||||
{% ifversion ghes > 3.4 %}
|
||||
{% data reusables.package_registry.container-registry-ghes-beta %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.release-trigger-workflow %}
|
||||
|
||||
No exemplo de fluxo de trabalho abaixo, usaremos as ações `login-action`{% ifversion fpt or ghec %}, `metadata-action`{% endif %} e `build-push-action` do Docker para compilar a imagem do Docker e, se o build for bem-sucedido, efetuar push da imagem compilada para o {% data variables.product.prodname_registry %}.
|
||||
In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
|
||||
|
||||
As opções `login-action` obrigatórias para o {% data variables.product.prodname_registry %} são:
|
||||
* `registry`: deve ser definido como {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
|
||||
* `username`: use o contexto {% raw %}`${{ github.actor }}`{% endraw %} para usar automaticamente o nome de usuário do usuário que disparou a execução de fluxo de trabalho. Para obter mais informações, confira "[Contextos](/actions/learn-github-actions/contexts#github-context)".
|
||||
* `password`: use o segredo `GITHUB_TOKEN` gerado automaticamente para a senha. Para obter mais informações, confira "[Como se autenticar com o GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)".
|
||||
The `login-action` options required for {% data variables.product.prodname_registry %} are:
|
||||
* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
|
||||
* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
|
||||
* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
|
||||
|
||||
{% ifversion fpt or ghec %} A opção `metadata-action` obrigatória para o {% data variables.product.prodname_registry %} é:
|
||||
* `images`: o namespace e o nome da imagem do Docker que está sendo compilada.
|
||||
{% ifversion fpt or ghec %}
|
||||
The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
|
||||
* `images`: The namespace and name for the Docker image you are building.
|
||||
{% endif %}
|
||||
|
||||
As opções `build-push-action` obrigatórias para o {% data variables.product.prodname_registry %} são:{% ifversion fpt or ghec %}
|
||||
* `context`: define o contexto do build como o conjunto de arquivos localizado no caminho especificado.{% endif %}
|
||||
* `push`: se isso for definido como `true`, a imagem será enviada por push para o registro se for compilada com sucesso.{% ifversion fpt or ghec %}
|
||||
* `tags` e `labels`: são preenchidos pela saída de `metadata-action`.{% else %}
|
||||
* `tags`: deve ser definido no formato {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
|
||||
* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
|
||||
* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
|
||||
* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
|
||||
* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
|
||||
Por exemplo, para uma imagem chamada `octo-image` armazenada no {% data variables.product.prodname_ghe_server %} em `https://HOSTNAME/octo-org/octo-repo`, a opção `tags` deverá ser definida como `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
|
||||
Por exemplo, para uma imagem chamada `octo-image` armazenada no {% data variables.product.prodname_dotcom %} em `http://github.com/octo-org/octo-repo`, a opção `tags` deve ser definida como `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. Você pode definir uma única tag, conforme mostrado abaixo, ou especificar várias tags em uma lista.{% endif %}
|
||||
For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %} {% data reusables.package_registry.publish-docker-image %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{% data reusables.package_registry.publish-docker-image %}
|
||||
|
||||
O fluxo de trabalho acima é acionado por um push para o branch da "versão". Ele faz check-out do repositório do GitHub e usa `login-action` para fazer logon no {% data variables.product.prodname_container_registry %}. Em seguida, extrai etiquetas e tags para a imagem do Docker. Por fim, ele usa a ação `build-push-action` para criar a imagem e publicá-la no {% data variables.product.prodname_container_registry %}.
|
||||
The above workflow is triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
|
||||
|
||||
{% else %}
|
||||
|
||||
@@ -183,16 +189,18 @@ jobs:
|
||||
{% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
|
||||
```
|
||||
|
||||
O fluxo de trabalho acima faz check-out do repositório do {% data variables.product.product_name %}, usa `login-action` para fazer logon no registro e usa a ação `build-push-action` para: compilar uma imagem do Docker com base no `Dockerfile` do repositório, enviar por push a imagem para o registro do Docker e aplicar a confirmação do SHA e a versão como marcas da imagem.
|
||||
The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
|
||||
{% endif %}
|
||||
|
||||
## Publicar imagens no Docker Hub e {% data variables.product.prodname_registry %}
|
||||
## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
|
||||
|
||||
{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
|
||||
{% ifversion ghes > 3.4 %}
|
||||
{% data reusables.package_registry.container-registry-ghes-beta %}
|
||||
{% endif %}
|
||||
|
||||
Em um fluxo de trabalho individual, você pode publicar sua imagem do Docker em vários registros usando as ações `login-action` e `build-push-action` para cada registro.
|
||||
In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
|
||||
|
||||
O exemplo de fluxo de trabalho a seguir usa as etapas das seções anteriores ("[Como publicar imagens no Docker Hub](#publishing-images-to-docker-hub)" e "[Como publicar imagens no {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") para criar um fluxo de trabalho individual que efetua push para os dois registros.
|
||||
The following example workflow uses the steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
@@ -246,5 +254,5 @@ jobs:
|
||||
labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
|
||||
```
|
||||
|
||||
O fluxo de trabalho acima faz check-out do repositório do {% data variables.product.product_name %}, usa a `login-action` duas vezes para fazer logon nos dois registros e gera marcas e rótulos com a ação `metadata-action`.
|
||||
Em seguida, a ação `build-push-action` compila a imagem do Docker e a envia por push para o Docker Hub e o {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Registro do Docker{% endif %}.
|
||||
The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
|
||||
Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Trabalhando com o registro do Contêiner
|
||||
intro: 'Você pode armazenar e gerenciar imagens do Docker e OCI no {% data variables.product.prodname_container_registry %}, que usa o namespace `https://{% data reusables.package_registry.container-registry-hostname %}`do pacote.'
|
||||
title: Working with the Container registry
|
||||
intro: 'You can store and manage Docker and OCI images in the {% data variables.product.prodname_container_registry %}, which uses the package namespace `https://{% data reusables.package_registry.container-registry-hostname %}`.'
|
||||
product: '{% data reusables.gated-features.packages %}'
|
||||
redirect_from:
|
||||
- /packages/managing-container-images-with-github-container-registry/pushing-and-pulling-docker-images
|
||||
@@ -17,85 +17,82 @@ versions:
|
||||
ghec: '*'
|
||||
ghes: '>= 3.5'
|
||||
shortTitle: Container registry
|
||||
ms.openlocfilehash: fc99e2e21a647c7a1a2517de8aa68822faac496e
|
||||
ms.sourcegitcommit: 478f2931167988096ae6478a257f492ecaa11794
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/09/2022
|
||||
ms.locfileid: '147705048'
|
||||
---
|
||||
|
||||
{% data reusables.package_registry.container-registry-ghes-beta %}
|
||||
|
||||
## Sobre o {% data variables.product.prodname_container_registry %}
|
||||
## About the {% data variables.product.prodname_container_registry %}
|
||||
|
||||
{% data reusables.package_registry.container-registry-benefits %}
|
||||
|
||||
{% ifversion ghes > 3.4 %}
|
||||
|
||||
Para usar o {% data variables.product.prodname_container_registry %} no {% data variables.product.product_name %}, o administrador do site deverá primeiro configurar {% data variables.product.prodname_registry %} para sua instância **e** habilitar o isolamento de subdomínio. Para obter mais informações, confira "[Introdução aos Pacotes do GitHub para sua empresa](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" e "[Habilitar o isolamento de subdomínio](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
|
||||
To use the {% data variables.product.prodname_container_registry %} on {% data variables.product.product_name %}, your site administrator must first configure {% data variables.product.prodname_registry %} for your instance **and** enable subdomain isolation. For more information, see "[Getting started with GitHub Packages for your enterprise](/admin/packages/getting-started-with-github-packages-for-your-enterprise)" and "[Enabling subdomain isolation](/admin/configuration/configuring-network-settings/enabling-subdomain-isolation)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Sobre o suporte de {% data variables.product.prodname_container_registry %}
|
||||
## About {% data variables.product.prodname_container_registry %} support
|
||||
|
||||
O {% data variables.product.prodname_container_registry %} é atualmente compatível com os seguintes formatos de imagem do contêiner:
|
||||
The {% data variables.product.prodname_container_registry %} currently supports the following container image formats:
|
||||
|
||||
* [Manifesto de Imagem do Docker V2, Esquema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
|
||||
* [Especificações da OCI (Open Container Initiative)](https://github.com/opencontainers/image-spec)
|
||||
* [Docker Image Manifest V2, Schema 2](https://docs.docker.com/registry/spec/manifest-v2-2/)
|
||||
* [Open Container Initiative (OCI) Specifications](https://github.com/opencontainers/image-spec)
|
||||
|
||||
Ao instalar ou publicar uma imagem Docker, a {% data variables.product.prodname_container_registry %} é compatível com as camadas estrangeiras, como imagens do Windows.
|
||||
When installing or publishing a Docker image, the {% data variables.product.prodname_container_registry %} supports foreign layers, such as Windows images.
|
||||
|
||||
## Efetuar a autenticação no {% data variables.product.prodname_container_registry %}
|
||||
## Authenticating to the {% data variables.product.prodname_container_registry %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %} Para se autenticar no {% data variables.product.prodname_container_registry %} (`ghcr.io`) dentro de um fluxo de trabalho de{% data variables.product.prodname_actions %}, use `GITHUB_TOKEN` para a melhor segurança e experiência. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %} {% endif %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
To authenticate to the {% data variables.product.prodname_container_registry %} (`ghcr.io`) within a {% data variables.product.prodname_actions %} workflow, use the `GITHUB_TOKEN` for the best security and experience. {% data reusables.package_registry.authenticate_with_pat_for_v2_registry %}
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}Substitua `HOSTNAME` por {% data variables.product.product_location_enterprise %} nome do host ou endereço IP nos exemplos abaixo.{% endif %}
|
||||
{% ifversion ghes %}Ensure that you replace `HOSTNAME` with {% data variables.product.product_location_enterprise %} hostname or IP address in the examples below.{% endif %}
|
||||
|
||||
{% data reusables.package_registry.authenticate-to-container-registry-steps %}
|
||||
|
||||
## Fazer push das imagens do contêiner
|
||||
## Pushing container images
|
||||
|
||||
Este exemplo efetua push da última versão de `IMAGE_NAME`.
|
||||
This example pushes the latest version of `IMAGE_NAME`.
|
||||
```shell
|
||||
$ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
|
||||
```
|
||||
|
||||
Este exemplo efetua push da versão `2.5` da imagem.
|
||||
This example pushes the `2.5` version of the image.
|
||||
```shell
|
||||
$ docker push {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:2.5
|
||||
```
|
||||
|
||||
Ao publicar um pacote pela primeira vez a visibilidade-padrão será privada. Para alterar a visibilidade ou definir permissões de acesso, confira "[Como configurar o controle de acesso e a visibilidade de um pacote](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)".
|
||||
When you first publish a package, the default visibility is private. To change the visibility or set access permissions, see "[Configuring a package's access control and visibility](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)."
|
||||
|
||||
## Fazer pull das imagens de contêiner
|
||||
## Pulling container images
|
||||
|
||||
### Pull por resumo
|
||||
### Pull by digest
|
||||
|
||||
Para garantir que você esteja sempre usando a mesma imagem, especifique a versão exata da imagem de contêiner da qual deseja efetuar pull pelo valor do SHA de `digest`.
|
||||
To ensure you're always using the same image, you can specify the exact container image version you want to pull by the `digest` SHA value.
|
||||
|
||||
1. Para localizar o valor do SHA de resumo, use `docker inspect` ou `docker pull` e copie o valor do SHA após `Digest:`
|
||||
1. To find the digest SHA value, use `docker inspect` or `docker pull` and copy the SHA value after `Digest:`
|
||||
```shell
|
||||
$ docker inspect {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
|
||||
```
|
||||
2. Remova a imagem localmente, conforme necessário.
|
||||
2. Remove image locally as needed.
|
||||
```shell
|
||||
$ docker rmi {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
|
||||
```
|
||||
|
||||
3. Efetue pull da imagem de contêiner com `@YOUR_SHA_VALUE` após o nome da imagem.
|
||||
3. Pull the container image with `@YOUR_SHA_VALUE` after the image name.
|
||||
```shell
|
||||
$ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME@sha256:82jf9a84u29hiasldj289498uhois8498hjs29hkuhs
|
||||
```
|
||||
|
||||
### Pull por nome
|
||||
### Pull by name
|
||||
|
||||
```shell
|
||||
$ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME
|
||||
```
|
||||
|
||||
### Pull por nome e versão
|
||||
### Pull by name and version
|
||||
|
||||
Exemplo da CLI do Docker que mostra uma imagem extraída pelo nome e pela tag de versão `1.14.1`:
|
||||
Docker CLI example showing an image pulled by its name and the `1.14.1` version tag:
|
||||
```shell
|
||||
$ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:1.14.1
|
||||
> 5e35bd43cf78: Pull complete
|
||||
@@ -107,7 +104,7 @@ Exemplo da CLI do Docker que mostra uma imagem extraída pelo nome e pela tag de
|
||||
> {% data reusables.package_registry.container-registry-hostname %}/orgname/image-name/release:1.14.1
|
||||
```
|
||||
|
||||
### Pull por nome e última versão
|
||||
### Pull by name and latest version
|
||||
|
||||
```shell
|
||||
$ docker pull {% data reusables.package_registry.container-registry-hostname %}/OWNER/IMAGE_NAME:latest
|
||||
@@ -117,16 +114,16 @@ Exemplo da CLI do Docker que mostra uma imagem extraída pelo nome e pela tag de
|
||||
> {% data reusables.package_registry.container-registry-hostname %}/user/image-name:latest
|
||||
```
|
||||
|
||||
## Criar imagens de contêiner
|
||||
## Building container images
|
||||
|
||||
Este exemplo compila a imagem `hello_docker`:
|
||||
This example builds the `hello_docker` image:
|
||||
```shell
|
||||
$ docker build -t hello_docker .
|
||||
```
|
||||
|
||||
## Marcar imagens de contêiner
|
||||
## Tagging container images
|
||||
|
||||
1. Encontre o ID da imagem do Docker que você deseja marcar.
|
||||
1. Find the ID for the Docker image you want to tag.
|
||||
```shell
|
||||
$ docker images
|
||||
> REPOSITORY TAG IMAGE ID CREATED SIZE
|
||||
@@ -135,7 +132,35 @@ Este exemplo compila a imagem `hello_docker`:
|
||||
> hello-world latest fce289e99eb9 16 months ago 1.84kB
|
||||
```
|
||||
|
||||
2. Marque a sua imagem do Docker usando o ID da imagem, o nome da imagem desejada e a hospedagem de destino.
|
||||
2. Tag your Docker image using the image ID and your desired image name and hosting destination.
|
||||
```shell
|
||||
$ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest
|
||||
```
|
||||
|
||||
## Labelling container images
|
||||
|
||||
{% data reusables.package_registry.about-docker-labels %} For more information on Docker labels, see [LABEL](https://docs.docker.com/engine/reference/builder/#label) in the official Docker documentation and [Pre-Defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys) in the `opencontainers/image-spec` repository.
|
||||
|
||||
The following labels are supported in the {% data variables.product.prodname_container_registry %}. Supported labels will appear on the package page for the image.
|
||||
|
||||
Label | Description
|
||||
------|------------
|
||||
| `org.opencontainers.image.source` | The URL of the repository associated with the package. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package#connecting-a-repository-to-a-container-image-using-the-command-line)."
|
||||
| `org.opencontainers.image.description` | A text-only description limited to 512 characters. This description will appear on the package page, below the name of the package.
|
||||
| `org.opencontainers.image.licenses` | An SPDX license identifier such as "MIT," limited to 256 characters. The license will appear on the package page, in the "Details" sidebar. For more information, see [SPDX License List](https://spdx.org/licenses/).
|
||||
|
||||
To add labels to an image, we recommend using the `LABEL` instruction in your `Dockerfile`. For example, if you're the user `monalisa` and you own `my-repo`, and your image is distributed under the terms of the MIT license, you would add the following lines to your `Dockerfile`:
|
||||
|
||||
```dockerfile
|
||||
LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo
|
||||
LABEL org.opencontainers.image.description="My container image"
|
||||
LABEL org.opencontainers.image.licenses=MIT
|
||||
```
|
||||
|
||||
Alternatively, you can add labels to an image at buildtime with the `docker build` command.
|
||||
|
||||
```shell
|
||||
$ docker build \
|
||||
--label "org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo" \
|
||||
--label "org.opencontainers.image.description=My container image" \
|
||||
--label "org.opencontainers.image.licenses=MIT"
|
||||
|
||||
@@ -13,6 +13,7 @@ children:
|
||||
- /about-github-sponsors-for-open-source-contributors
|
||||
- /setting-up-github-sponsors-for-your-personal-account
|
||||
- /setting-up-github-sponsors-for-your-organization
|
||||
- /using-a-fiscal-host-to-receive-github-sponsors-payouts
|
||||
- /editing-your-profile-details-for-github-sponsors
|
||||
- /managing-your-sponsorship-goal
|
||||
- /managing-your-sponsorship-tiers
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Configurando o GitHub Sponsors (Patrocinadores do GitHub) para sua organização
|
||||
intro: 'Sua organização pode ingressar no {% data variables.product.prodname_sponsors %} para receber pagamentos pelo seu trabalho.'
|
||||
title: Setting up GitHub Sponsors for your organization
|
||||
intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-github-sponsorship-for-your-organization
|
||||
- /articles/receiving-sponsorships-as-a-sponsored-organization
|
||||
@@ -15,64 +15,84 @@ topics:
|
||||
- Sponsors profile
|
||||
- Open Source
|
||||
shortTitle: Set up for organization
|
||||
ms.openlocfilehash: d7de813453d379ae898cc26d9579e06710aab26d
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164467'
|
||||
---
|
||||
## Ingressar no {% data variables.product.prodname_sponsors %}
|
||||
|
||||
## Joining {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
Depois de receber um convite para sua organização ingressar no {% data variables.product.prodname_sponsors %}, você poderá concluir as etapas abaixo para se tornar uma organização patrocinada.
|
||||
After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
|
||||
|
||||
Para ingressar no {% data variables.product.prodname_sponsors %} como colaborador individual fora de uma organização, confira "[Como configurar o {% data variables.product.prodname_sponsors %} para sua conta pessoal](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)".
|
||||
To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)."
|
||||
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %}
|
||||
3. À direita da sua organização, clique em **Ingressar na lista de espera**.
|
||||
{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %}
|
||||
{% data reusables.sponsors.view-eligible-accounts %}
|
||||
3. To the right of your organization, click **Join the waitlist**.
|
||||
{% data reusables.sponsors.contact-info %}
|
||||
{% data reusables.sponsors.payout-choice %}
|
||||
|
||||
|
||||
## Preencher seu perfil de organização patrocinada
|
||||
{% data reusables.sponsors.accept-legal-terms %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.meet-the-team %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
|
||||
## Completing your sponsored organization profile
|
||||
|
||||
## Criar camadas de patrocínio
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-profile-tab %}
|
||||
{% data reusables.sponsors.short-bio %}
|
||||
{% data reusables.sponsors.add-introduction %}
|
||||
{% data reusables.sponsors.meet-the-team %}
|
||||
{% data reusables.sponsors.edit-featured-work %}
|
||||
{% data reusables.sponsors.opt-in-to-being-featured %}
|
||||
{% data reusables.sponsors.save-profile %}
|
||||
|
||||
## Creating sponsorship tiers
|
||||
|
||||
{% data reusables.sponsors.tier-details %}
|
||||
|
||||
{% data reusables.sponsors.maximum-tier %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
|
||||
{% data reusables.sponsors.click-add-tier %}
|
||||
{% data reusables.sponsors.tier-price-description %}
|
||||
{% data reusables.sponsors.add-welcome-message %}
|
||||
{% data reusables.sponsors.save-tier-draft %}
|
||||
{% data reusables.sponsors.review-and-publish-tier %}
|
||||
{% data reusables.sponsors.add-more-tiers %}
|
||||
|
||||
## Enviando informações bancárias
|
||||
## Submitting your bank information
|
||||
|
||||
Como organização patrocinada, você receberá pagamentos para uma conta bancária em uma região compatível. Esta pode ser uma conta bancária dedicada à sua organização ou a uma conta bancária pessoal. Obtenha uma conta bancária empresarial por meio de serviços como o [Stripe Atlas](https://stripe.com/atlas) ou ingresse em um host fiscal como o [Open Collective](https://opencollective.com/). A pessoa que criou o {% data variables.product.prodname_sponsors %} para a organização também deve morar na mesma região suportada. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
As a sponsored organization, you will receive payouts to a bank account in a supported region or via a fiscal host.
|
||||
|
||||
{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
|
||||
|
||||
If you choose to receive payouts to a bank account, your bank account can be a dedicated bank account for your organization or a personal bank account. You can get a business bank account through services like [Stripe Atlas](https://stripe.com/atlas). The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
{% data reusables.sponsors.double-check-stripe-info %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.create-stripe-account %}
|
||||
|
||||
Para obter mais informações sobre como configurar o Stripe Connect usando o Open Collective, confira [Como configurar o {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors) no Open Collective Docs.
|
||||
|
||||
## Enviando suas informações fiscais
|
||||
## Submitting your tax information
|
||||
|
||||
{% data reusables.sponsors.tax-form-information-org %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.overview-tab %}
|
||||
{% data reusables.sponsors.tax-form-link %}
|
||||
|
||||
## Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %}
|
||||
## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
|
||||
|
||||
Antes que sua organização possa se tornar uma organização patrocinada, você deverá habilitar a 2FA para sua conta em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
|
||||
Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
## Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação
|
||||
## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.request-approval %}
|
||||
|
||||
{% data reusables.sponsors.github-review-app %}
|
||||
|
||||
## Leitura adicional
|
||||
## Further reading
|
||||
|
||||
- "[Sobre o {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
|
||||
- "[Como receber patrocínios por meio do {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
|
||||
- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
|
||||
- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Como configurar patrocinadores do GitHub para sua conta pessoal
|
||||
intro: 'Você pode se tornar um desenvolvedor patrocinado participando de {% data variables.product.prodname_sponsors %}, completando seu perfil de desenvolvedor patrocinado, criando camadasde patrocínio, enviando seus dados bancários e fiscais e habilitando a autenticação de dois fatores para sua conta em {% data variables.product.product_location %}.'
|
||||
title: Setting up GitHub Sponsors for your personal account
|
||||
intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.'
|
||||
redirect_from:
|
||||
- /articles/becoming-a-sponsored-developer
|
||||
- /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
|
||||
@@ -14,62 +14,82 @@ topics:
|
||||
- User account
|
||||
- Sponsors profile
|
||||
shortTitle: Set up for personal account
|
||||
ms.openlocfilehash: 288dd5ab53d1a27b7f97ccf9429973a668d8f72b
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: pt-BR
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164558'
|
||||
---
|
||||
## Ingressar no {% data variables.product.prodname_sponsors %}
|
||||
|
||||
## Joining {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
Para ingressar no {% data variables.product.prodname_sponsors %} como uma organização, confira "[Como configurar o {% data variables.product.prodname_sponsors %} para sua organização](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)".
|
||||
To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
|
||||
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %}
|
||||
2. Se você é o proprietário de uma organização, você tem mais de uma conta elegível. Clique em **Ver suas contas qualificadas** e, na lista de contas, localize sua conta pessoal.
|
||||
3. Clique em **Ingressar na lista de espera**.
|
||||
{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
|
||||
2. If you are an organization owner, you have more than one eligible account. Click **Get sponsored**, then in the list of accounts, find your personal account.
|
||||
|
||||
3. Click **Join the waitlist**.
|
||||
{% data reusables.sponsors.contact-info %}
|
||||
{% data reusables.sponsors.payout-choice %}
|
||||
|
||||
|
||||
Se você tiver uma conta bancária em uma região aceita, o {% data variables.product.prodname_dotcom %} irá rever sua solicitação dentro de duas semanas.
|
||||
{% data reusables.sponsors.accept-legal-terms %}
|
||||
|
||||
## Preencher seu perfil de desenvolvedor patrocinado
|
||||
If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
|
||||
|
||||
Depois de {% data variables.product.prodname_dotcom %} avaliar sua solicitação, você pode configurar o seu perfil de desenvolvedor patrocinado para que as pessoas possam começar a patrocinar você.
|
||||
## Completing your sponsored developer profile
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
|
||||
After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
|
||||
|
||||
## Criar camadas de patrocínio
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-profile-tab %}
|
||||
{% data reusables.sponsors.short-bio %}
|
||||
{% data reusables.sponsors.add-introduction %}
|
||||
{% data reusables.sponsors.edit-featured-work %}
|
||||
{% data reusables.sponsors.opt-in-to-being-featured %}
|
||||
{% data reusables.sponsors.save-profile %}
|
||||
|
||||
## Creating sponsorship tiers
|
||||
|
||||
{% data reusables.sponsors.tier-details %}
|
||||
|
||||
{% data reusables.sponsors.maximum-tier %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
|
||||
{% data reusables.sponsors.click-add-tier %}
|
||||
{% data reusables.sponsors.tier-price-description %}
|
||||
{% data reusables.sponsors.add-welcome-message %}
|
||||
{% data reusables.sponsors.save-tier-draft %}
|
||||
{% data reusables.sponsors.review-and-publish-tier %}
|
||||
{% data reusables.sponsors.add-more-tiers %}
|
||||
|
||||
## Enviando informações bancárias
|
||||
## Submitting your bank information
|
||||
|
||||
Se você vive em uma região aceita, você pode seguir essas instruções para enviar informações bancárias criando uma conta do Stripe Connect. A sua região de residência e a região da sua conta bancária devem corresponder. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
As a sponsored user, you will receive payouts to a bank account in a supported region or via a fiscal host.
|
||||
|
||||
{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
|
||||
|
||||
If you choose to receive payouts to a bank account, your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
{% data reusables.sponsors.double-check-stripe-info %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.create-stripe-account %}
|
||||
|
||||
## Enviando suas informações fiscais
|
||||
## Submitting your tax information
|
||||
|
||||
{% data reusables.sponsors.tax-form-information-dev %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.overview-tab %}
|
||||
{% data reusables.sponsors.tax-form-link %}
|
||||
|
||||
## Habilitar a autenticação de dois fatores (2FA, two-factor authentication) na sua conta do {% data variables.product.prodname_dotcom %}
|
||||
## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
|
||||
|
||||
Antes de se tornar um desenvolvedor patrocinado, você deve habilitar a 2FA para sua conta em {% data variables.product.product_location %}. Para obter mais informações, confira "[Como configurar a autenticação de dois fatores](/articles/configuring-two-factor-authentication)".
|
||||
Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
## Enviar seu aplicativo ao {% data variables.product.prodname_dotcom %} para aprovação
|
||||
## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
4. Clique em **Solicitar aprovação**.
|
||||
|
||||
4. Click **Request approval**.
|
||||
|
||||
|
||||
{% data reusables.sponsors.github-review-app %}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 发布 Docker 映像
|
||||
intro: '您可以将 Docker 映像发布到注册表，例如 Docker Hub 或 {% data variables.product.prodname_registry %}，作为持续集成 (CI) 工作流程的一部分。'
|
||||
title: Publishing Docker images
|
||||
intro: 'You can publish Docker images to a registry, such as Docker Hub or {% data variables.product.prodname_registry %}, as part of your continuous integration (CI) workflow.'
|
||||
redirect_from:
|
||||
- /actions/language-and-framework-guides/publishing-docker-images
|
||||
- /actions/guides/publishing-docker-images
|
||||
@@ -14,61 +14,63 @@ topics:
|
||||
- Packaging
|
||||
- Publishing
|
||||
- Docker
|
||||
ms.openlocfilehash: 01f20527dedeea3685855797993187e7af462de4
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '147410289'
|
||||
---
|
||||
{% data reusables.actions.enterprise-beta %} {% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## 简介
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
本指南介绍如何创建执行 Docker 构建的工作流程，然后将 Docker 映像发布到 Docker Hub 或 {% data variables.product.prodname_registry %}。 通过单个工作流程，您可以将映像发布到单一注册表或多个注册表。
|
||||
## Introduction
|
||||
|
||||
This guide shows you how to create a workflow that performs a Docker build, and then publishes Docker images to Docker Hub or {% data variables.product.prodname_registry %}. With a single workflow, you can publish images to a single registry or to multiple registries.
|
||||
|
||||
{% note %}
|
||||
|
||||
注意：如果你想推送到另一个第三方 Docker 注册表，“[将映像发布到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”部分中的示例可以用作一个很好的模板。
|
||||
**Note:** If you want to push to another third-party Docker registry, the example in the "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)" section can serve as a good template.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## 先决条件
|
||||
## Prerequisites
|
||||
|
||||
建议基本了解工作流程配置选项和如何创建工作流程文件。 有关详细信息，请参阅“[了解 {% data variables.product.prodname_actions %}](/actions/learn-github-actions)。”
|
||||
We recommend that you have a basic understanding of workflow configuration options and how to create a workflow file. For more information, see "[Learn {% data variables.product.prodname_actions %}](/actions/learn-github-actions)."
|
||||
|
||||
您可能还发现基本了解以下内容是有帮助的：
|
||||
You might also find it helpful to have a basic understanding of the following:
|
||||
|
||||
- [加密的机密](/actions/reference/encrypted-secrets)
|
||||
- [工作流中的身份验证](/actions/reference/authentication-in-a-workflow){% ifversion fpt or ghec %}
|
||||
- [使用 {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry){% else %}
|
||||
- [使用 Docker 注册表](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry){% endif %}
|
||||
- "[Encrypted secrets](/actions/reference/encrypted-secrets)"
|
||||
- "[Authentication in a workflow](/actions/reference/authentication-in-a-workflow)"{% ifversion fpt or ghec %}
|
||||
- "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry)"{% else %}
|
||||
- "[Working with the Docker registry](/packages/working-with-a-github-packages-registry/working-with-the-docker-registry)"{% endif %}
|
||||
|
||||
## 关于映像配置
|
||||
## About image configuration
|
||||
|
||||
本指南假定您对存储在 {% data variables.product.prodname_dotcom %} 仓库的 Docker 映像有完整的定义。 例如，存储库必须包含一个 Dockerfile，以及执行 Docker 构建以创建映像所需的任何其他文件。
|
||||
This guide assumes that you have a complete definition for a Docker image stored in a {% data variables.product.prodname_dotcom %} repository. For example, your repository must contain a _Dockerfile_, and any other files needed to perform a Docker build to create an image.
|
||||
|
||||
在本指南中，我们将使用 Docker `build-push-action` 操作来构建 Docker 映像并将其推送到一个或多个 Docker 注册表。 有关详细信息，请参阅 [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images)。
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
|
||||
{% data reusables.package_registry.about-docker-labels %} For more information, see "[Working with the {% data variables.product.prodname_container_registry %}](/packages/working-with-a-github-packages-registry/working-with-the-container-registry#labelling-container-images)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
In this guide, we will use the Docker `build-push-action` action to build the Docker image and push it to one or more Docker registries. For more information, see [`build-push-action`](https://github.com/marketplace/actions/build-and-push-docker-images).
|
||||
|
||||
{% data reusables.actions.enterprise-marketplace-actions %}
|
||||
|
||||
## 将映像发布到 Docker Hub
|
||||
## Publishing images to Docker Hub
|
||||
|
||||
{% data reusables.actions.release-trigger-workflow %}
|
||||
|
||||
在下面的示例工作流中，我们使用 Docker `login-action` 和 `build-push-action` 操作来构建 Docker 映像，如果构建成功，则将构建的映像推送到 Docker Hub。
|
||||
In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
|
||||
|
||||
要推送到 Docker Hub，您需要有一个 Docker Hub 帐户，并创建一个 Docker Hub 仓库。 有关详细信息，请参阅 Docker 文档中的“[将 Docker 容器映像推送到 Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)”。
|
||||
To push to Docker Hub, you will need to have a Docker Hub account, and have a Docker Hub repository created. For more information, see "[Pushing a Docker container image to Docker Hub](https://docs.docker.com/docker-hub/repos/#pushing-a-docker-container-image-to-docker-hub)" in the Docker documentation.
|
||||
|
||||
Docker Hub 所需的 `login-action` 选项是：
|
||||
* `username` 和 `password`：这是 Docker Hub 用户名和密码。 我们建议将 Docker Hub 用户名和密码存储为机密，使它们不会公开在工作流程文件中。 有关详细信息，请参阅“[创建和使用已加密的机密](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)。”
|
||||
The `login-action` options required for Docker Hub are:
|
||||
* `username` and `password`: This is your Docker Hub username and password. We recommend storing your Docker Hub username and password as secrets so they aren't exposed in your workflow file. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
|
||||
|
||||
Docker Hub 所需的 `metadata-action` 选项是：
|
||||
* `images`：你正在构建/推送到 Docker Hub 的 Docker 映像的命名空间和名称。
|
||||
The `metadata-action` option required for Docker Hub is:
|
||||
* `images`: The namespace and name for the Docker image you are building/pushing to Docker Hub.
|
||||
|
||||
Docker Hub 所需的 `build-push-action` 选项是：
|
||||
* `tags`：你的新映像的标签，格式为 `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`。 您可以如下所示设置单个标记，或在列表中指定多个标记。
|
||||
* `push`：如果设置为 `true`，则映像将推送到注册表（如果成功构建）。
|
||||
The `build-push-action` options required for Docker Hub are:
|
||||
* `tags`: The tag of your new image in the format `DOCKER-HUB-NAMESPACE/DOCKER-HUB-REPOSITORY:VERSION`. You can set a single tag as shown below, or specify multiple tags in a list.
|
||||
* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
@@ -110,38 +112,42 @@ jobs:
|
||||
labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
|
||||
```
|
||||
|
||||
上述工作流签出 {% data variables.product.prodname_dotcom %} 存储库，使用 `login-action` 登录注册表，然后使用 `build-push-action` 操作：基于存储库的 `Dockerfile` 构建 Docker 映像；将映像推送到 Docker Hub，并向映像应用标签。
|
||||
The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to Docker Hub, and apply a tag to the image.
|
||||
|
||||
## 发布映像到 {% data variables.product.prodname_registry %}
|
||||
## Publishing images to {% data variables.product.prodname_registry %}
|
||||
|
||||
{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
|
||||
{% ifversion ghes > 3.4 %}
|
||||
{% data reusables.package_registry.container-registry-ghes-beta %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.actions.release-trigger-workflow %}
|
||||
|
||||
在下面的示例工作流中，我们使用 Docker `login-action`{% ifversion fpt or ghec %}、`metadata-action`、{% endif %}和 `build-push-action` 操作来构建 Docker 映像，如果构建成功，则将构建的映像推送到 {% data variables.product.prodname_registry %}。
|
||||
In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.
|
||||
|
||||
{% data variables.product.prodname_registry %} 所需的 `login-action` 选项是：
|
||||
* `registry`：必须设置为 {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}。
|
||||
* `username`：你可以使用 {% raw %}`${{ github.actor }}` {% endraw %} 上下文自动使用触发工作流运行的用户的用户名。 有关详细信息，请参阅“[上下文](/actions/learn-github-actions/contexts#github-context)。”
|
||||
* `password`：可以使用自动生成 `GITHUB_TOKEN` 的密码机密。 有关详细信息，请参阅“[使用 GITHUB_TOKEN 进行身份验证](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)。”
|
||||
The `login-action` options required for {% data variables.product.prodname_registry %} are:
|
||||
* `registry`: Must be set to {% ifversion fpt or ghec %}`ghcr.io`{% elsif ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}`{% else %}`docker.pkg.github.com`{% endif %}.
|
||||
* `username`: You can use the {% raw %}`${{ github.actor }}`{% endraw %} context to automatically use the username of the user that triggered the workflow run. For more information, see "[Contexts](/actions/learn-github-actions/contexts#github-context)."
|
||||
* `password`: You can use the automatically-generated `GITHUB_TOKEN` secret for the password. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)."
|
||||
|
||||
{% ifversion fpt or ghec %} {% data variables.product.prodname_registry %} 所需的 `metadata-action` 选项是：
|
||||
* `images`：正在构建的 Docker 映像的命名空间和名称。
|
||||
{% ifversion fpt or ghec %}
|
||||
The `metadata-action` option required for {% data variables.product.prodname_registry %} is:
|
||||
* `images`: The namespace and name for the Docker image you are building.
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.prodname_registry %} 所需的 `build-push-action` 选项是：{% ifversion fpt or ghec %}
|
||||
* `context`：将构建的上下文定义为位于指定路径中的文件集。{% endif %}
|
||||
* `push`：如果设置为 `true`，则映像将推送到注册表（如果成功构建）。{% ifversion fpt or ghec %}
|
||||
* `tags` 和 `labels`：它们由 `metadata-action` 的输出填充。{% else %}
|
||||
* `tags`：必须采用格式 {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION` 设置。
|
||||
The `build-push-action` options required for {% data variables.product.prodname_registry %} are:{% ifversion fpt or ghec %}
|
||||
* `context`: Defines the build's context as the set of files located in the specified path.{% endif %}
|
||||
* `push`: If set to `true`, the image will be pushed to the registry if it is built successfully.{% ifversion fpt or ghec %}
|
||||
* `tags` and `labels`: These are populated by output from `metadata-action`.{% else %}
|
||||
* `tags`: Must be set in the format {% ifversion ghes > 3.4 %}`{% data reusables.package_registry.container-registry-hostname %}/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
|
||||
例如，对于存储在 `https://HOSTNAME/octo-org/octo-repo` 的 {% data variables.product.prodname_ghe_server %} 上的名为 `octo-image` 的映像，`tags` 选项应设置为 `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`。
|
||||
For example, for an image named `octo-image` stored on {% data variables.product.prodname_ghe_server %} at `https://HOSTNAME/octo-org/octo-repo`, the `tags` option should be set to `{% data reusables.package_registry.container-registry-hostname %}/octo-org/octo-repo/octo-image:latest`{% else %}`docker.pkg.github.com/OWNER/REPOSITORY/IMAGE_NAME:VERSION`.
|
||||
|
||||
例如，对于存储在 `http://github.com/octo-org/octo-repo` 的 {% data variables.product.prodname_dotcom %} 上的名为 `octo-image` 的映像，`tags` 选项应设置为 `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}。 您可以如下所示设置单个标记，或在列表中指定多个标记。{% endif %}
|
||||
For example, for an image named `octo-image` stored on {% data variables.product.prodname_dotcom %} at `http://github.com/octo-org/octo-repo`, the `tags` option should be set to `docker.pkg.github.com/octo-org/octo-repo/octo-image:latest`{% endif %}. You can set a single tag as shown below, or specify multiple tags in a list.{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %} {% data reusables.package_registry.publish-docker-image %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
{% data reusables.package_registry.publish-docker-image %}
|
||||
|
||||
上述工作流程通过推送到“发行版”分支触发。 它签出 GitHub 存储库，并使用 `login-action` 登录到 {% data variables.product.prodname_container_registry %}。 然后，它将提取 Docker 映像的标签和标记。 最后，它使用 `build-push-action` 操作构建映像并将其发布到 {% data variables.product.prodname_container_registry %}。
|
||||
The above workflow is triggered by a push to the "release" branch. It checks out the GitHub repository, and uses the `login-action` to log in to the {% data variables.product.prodname_container_registry %}. It then extracts labels and tags for the Docker image. Finally, it uses the `build-push-action` action to build the image and publish it on the {% data variables.product.prodname_container_registry %}.
|
||||
|
||||
{% else %}
|
||||
|
||||
@@ -183,16 +189,18 @@ jobs:
|
||||
{% ifversion ghae %}docker.YOUR-HOSTNAME.com{% else %}docker.pkg.github.com{% endif %}{% raw %}/${{ github.repository }}/octo-image:${{ github.event.release.tag_name }}{% endraw %}
|
||||
```
|
||||
|
||||
上述工作流签出 {% data variables.product.product_name %} 存储库，使用 `login-action` 登录注册表，然后使用 `build-push-action` 操作：基于存储库的 `Dockerfile` 构建 Docker 映像；将映像推送到 Docker 注册表，并将提交 SHA 和发布版本应用为映像标签。
|
||||
The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` to log in to the registry, and then uses the `build-push-action` action to: build a Docker image based on your repository's `Dockerfile`; push the image to the Docker registry, and apply the commit SHA and release version as image tags.
|
||||
{% endif %}
|
||||
|
||||
## 发布映像到 Docker Hub 和 {% data variables.product.prodname_registry %}
|
||||
## Publishing images to Docker Hub and {% data variables.product.prodname_registry %}
|
||||
|
||||
{% ifversion ghes > 3.4 %} {% data reusables.package_registry.container-registry-ghes-beta %} {% endif %}
|
||||
{% ifversion ghes > 3.4 %}
|
||||
{% data reusables.package_registry.container-registry-ghes-beta %}
|
||||
{% endif %}
|
||||
|
||||
在单个工作流中，你可以通过对每个注册表使用 `login-action` 和 `build-push-action` 操作将 Docker 映像发布到多个注册表。
|
||||
In a single workflow, you can publish your Docker image to multiple registries by using the `login-action` and `build-push-action` actions for each registry.
|
||||
|
||||
以下示例工作流使用上述部分（“[将映像发布到 Docker Hub](#publishing-images-to-docker-hub)”和“[将映像发布到 {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)”）中的步骤创建推送到两个注册表的单个工作流。
|
||||
The following example workflow uses the steps from the previous sections ("[Publishing images to Docker Hub](#publishing-images-to-docker-hub)" and "[Publishing images to {% data variables.product.prodname_registry %}](#publishing-images-to-github-packages)") to create a single workflow that pushes to both registries.
|
||||
|
||||
```yaml{:copy}
|
||||
{% data reusables.actions.actions-not-certified-by-github-comment %}
|
||||
@@ -246,5 +254,5 @@ jobs:
|
||||
labels: {% raw %}${{ steps.meta.outputs.labels }}{% endraw %}
|
||||
```
|
||||
|
||||
上述工作流签出 {% data variables.product.product_name %} 存储库，使用 `login-action` 两次以登录到两个注册表，并使用 `metadata-action` 操作生成标记和标签。
|
||||
然后 `build-push-action` 操作构建 Docker 映像并将其推送到 Docker Hub 和 {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker 注册表{% endif %}。
|
||||
The above workflow checks out the {% data variables.product.product_name %} repository, uses the `login-action` twice to log in to both registries and generates tags and labels with the `metadata-action` action.
|
||||
Then the `build-push-action` action builds and pushes the Docker image to Docker Hub and the {% ifversion fpt or ghec or ghes > 3.4 %}{% data variables.product.prodname_container_registry %}{% else %}Docker registry{% endif %}.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About workflows
|
||||
shortTitle: About workflows
|
||||
intro: 'Get a high level overview {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
|
||||
intro: 'Get a high-level overview of {% data variables.product.prodname_actions %} workflows, including triggers, syntax, and advanced features.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -136,3 +136,31 @@ This example builds the `hello_docker` image:
|
||||
```shell
|
||||
$ docker tag 38f737a91f39 {% data reusables.package_registry.container-registry-hostname %}/OWNER/NEW_IMAGE_NAME:latest
|
||||
```
|
||||
|
||||
## Labelling container images
|
||||
|
||||
{% data reusables.package_registry.about-docker-labels %} For more information on Docker labels, see [LABEL](https://docs.docker.com/engine/reference/builder/#label) in the official Docker documentation and [Pre-Defined Annotation Keys](https://github.com/opencontainers/image-spec/blob/master/annotations.md#pre-defined-annotation-keys) in the `opencontainers/image-spec` repository.
|
||||
|
||||
The following labels are supported in the {% data variables.product.prodname_container_registry %}. Supported labels will appear on the package page for the image.
|
||||
|
||||
Label | Description
|
||||
------|------------
|
||||
| `org.opencontainers.image.source` | The URL of the repository associated with the package. For more information, see "[Connecting a repository to a package](/packages/learn-github-packages/connecting-a-repository-to-a-package#connecting-a-repository-to-a-container-image-using-the-command-line)."
|
||||
| `org.opencontainers.image.description` | A text-only description limited to 512 characters. This description will appear on the package page, below the name of the package.
|
||||
| `org.opencontainers.image.licenses` | An SPDX license identifier such as "MIT," limited to 256 characters. The license will appear on the package page, in the "Details" sidebar. For more information, see [SPDX License List](https://spdx.org/licenses/).
|
||||
|
||||
To add labels to an image, we recommend using the `LABEL` instruction in your `Dockerfile`. For example, if you're the user `monalisa` and you own `my-repo`, and your image is distributed under the terms of the MIT license, you would add the following lines to your `Dockerfile`:
|
||||
|
||||
```dockerfile
|
||||
LABEL org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo
|
||||
LABEL org.opencontainers.image.description="My container image"
|
||||
LABEL org.opencontainers.image.licenses=MIT
|
||||
```
|
||||
|
||||
Alternatively, you can add labels to an image at buildtime with the `docker build` command.
|
||||
|
||||
```shell
|
||||
$ docker build \
|
||||
--label "org.opencontainers.image.source=https://{% ifversion fpt or ghec %}github.com{% else %}HOSTNAME{% endif %}/monalisa/my-repo" \
|
||||
--label "org.opencontainers.image.description=My container image" \
|
||||
--label "org.opencontainers.image.licenses=MIT"
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -13,6 +13,7 @@ children:
|
||||
- /about-github-sponsors-for-open-source-contributors
|
||||
- /setting-up-github-sponsors-for-your-personal-account
|
||||
- /setting-up-github-sponsors-for-your-organization
|
||||
- /using-a-fiscal-host-to-receive-github-sponsors-payouts
|
||||
- /editing-your-profile-details-for-github-sponsors
|
||||
- /managing-your-sponsorship-goal
|
||||
- /managing-your-sponsorship-tiers
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 为您的组织设置 GitHub Sponsors
|
||||
intro: '您的组织可以加入 {% data variables.product.prodname_sponsors %} 以接受对您工作的付款。'
|
||||
title: Setting up GitHub Sponsors for your organization
|
||||
intro: 'Your organization can join {% data variables.product.prodname_sponsors %} to receive payments for your work.'
|
||||
redirect_from:
|
||||
- /articles/setting-up-github-sponsorship-for-your-organization
|
||||
- /articles/receiving-sponsorships-as-a-sponsored-organization
|
||||
@@ -15,64 +15,84 @@ topics:
|
||||
- Sponsors profile
|
||||
- Open Source
|
||||
shortTitle: Set up for organization
|
||||
ms.openlocfilehash: d7de813453d379ae898cc26d9579e06710aab26d
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164468'
|
||||
---
|
||||
## 加入 {% data variables.product.prodname_sponsors %}
|
||||
|
||||
## Joining {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% data reusables.sponsors.you-can-be-a-sponsored-organization %} {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
收到邀请您的组织加入 {% data variables.product.prodname_sponsors %} 的邀请后，您可以完成以下步骤以成为被赞助的组织。
|
||||
After you receive an invitation for your organization to join {% data variables.product.prodname_sponsors %}, you can complete the steps below to become a sponsored organization.
|
||||
|
||||
若要将 {% data variables.product.prodname_sponsors %} 作为组织外部的个人参与者加入，请参阅“[为个人帐户设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)”。
|
||||
To join {% data variables.product.prodname_sponsors %} as an individual contributor outside an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your personal account](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-personal-account)."
|
||||
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %} {% data reusables.sponsors.view-eligible-accounts %}
|
||||
3. 在组织的右侧，单击“加入等待列表”。
|
||||
{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %}
|
||||
{% data reusables.sponsors.view-eligible-accounts %}
|
||||
3. To the right of your organization, click **Join the waitlist**.
|
||||
{% data reusables.sponsors.contact-info %}
|
||||
{% data reusables.sponsors.payout-choice %}
|
||||
|
||||
|
||||
## 填写被赞助组织资料
|
||||
{% data reusables.sponsors.accept-legal-terms %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.meet-the-team %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
|
||||
## Completing your sponsored organization profile
|
||||
|
||||
## 创建赞助等级
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-profile-tab %}
|
||||
{% data reusables.sponsors.short-bio %}
|
||||
{% data reusables.sponsors.add-introduction %}
|
||||
{% data reusables.sponsors.meet-the-team %}
|
||||
{% data reusables.sponsors.edit-featured-work %}
|
||||
{% data reusables.sponsors.opt-in-to-being-featured %}
|
||||
{% data reusables.sponsors.save-profile %}
|
||||
|
||||
## Creating sponsorship tiers
|
||||
|
||||
{% data reusables.sponsors.tier-details %}
|
||||
|
||||
{% data reusables.sponsors.maximum-tier %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
|
||||
{% data reusables.sponsors.click-add-tier %}
|
||||
{% data reusables.sponsors.tier-price-description %}
|
||||
{% data reusables.sponsors.add-welcome-message %}
|
||||
{% data reusables.sponsors.save-tier-draft %}
|
||||
{% data reusables.sponsors.review-and-publish-tier %}
|
||||
{% data reusables.sponsors.add-more-tiers %}
|
||||
|
||||
## 提交您的银行信息
|
||||
## Submitting your bank information
|
||||
|
||||
作为被赞助组织，您将在受支持的区域接收支付到银行帐户的赞助款。 这可以是您组织的专用银行帐户或个人银行帐户。 可以通过 [Stripe Atlas](https://stripe.com/atlas) 等服务获取商业银行帐户，也可以加入 [Open Collective](https://opencollective.com/) 等财务托管。 为组织设置 {% data variables.product.prodname_sponsors %} 的人员也必须居住在同一受支持的区域。 {% data reusables.sponsors.stripe-supported-regions %}
|
||||
As a sponsored organization, you will receive payouts to a bank account in a supported region or via a fiscal host.
|
||||
|
||||
{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
|
||||
|
||||
If you choose to receive payouts to a bank account, your bank account can be a dedicated bank account for your organization or a personal bank account. You can get a business bank account through services like [Stripe Atlas](https://stripe.com/atlas). The person setting up {% data variables.product.prodname_sponsors %} for the organization must live in the same supported region, too. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
{% data reusables.sponsors.double-check-stripe-info %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.create-stripe-account %}
|
||||
|
||||
有关使用 Open Collective 设置 Stripe 连接的详细信息，请参阅 Open Collective 文档中的[设置 {% data variables.product.prodname_sponsors %}](https://docs.opencollective.com/help/collectives/github-sponsors)。
|
||||
|
||||
## 提交您的税务信息
|
||||
## Submitting your tax information
|
||||
|
||||
{% data reusables.sponsors.tax-form-information-org %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.overview-tab %}
|
||||
{% data reusables.sponsors.tax-form-link %}
|
||||
|
||||
## 在您的 {% data variables.product.prodname_dotcom %} 帐户上启用双重身份验证 (2FA)。
|
||||
## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
|
||||
|
||||
在您的组织成为被赞助的组织之前，您必须为您在 {% data variables.product.product_location %} 上的帐户启用 2FA。 有关详细信息，请参阅“[配置双重身份验证](/articles/configuring-two-factor-authentication)”。
|
||||
Before your organization can become a sponsored organization, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
## 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准
|
||||
## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.request-approval %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.request-approval %}
|
||||
|
||||
{% data reusables.sponsors.github-review-app %}
|
||||
|
||||
## 延伸阅读
|
||||
## Further reading
|
||||
|
||||
- [关于 {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)
|
||||
- [通过 {% data variables.product.prodname_sponsors %} 接受赞助](/sponsors/receiving-sponsorships-through-github-sponsors)
|
||||
- "[About {% data variables.product.prodname_sponsors %}](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)"
|
||||
- "[Receiving sponsorships through {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: 针对个人帐户设置 GitHub 赞助商
|
||||
intro: '要成为被赞助的开发者，请加入 {% data variables.product.prodname_sponsors %}、填写被赞助开发者个人资料、创建赞助等级、提交您的银行和税务信息并为您在 {% data variables.product.product_location %} 上的帐户启用双重身份验证。'
|
||||
title: Setting up GitHub Sponsors for your personal account
|
||||
intro: 'You can become a sponsored developer by joining {% data variables.product.prodname_sponsors %}, completing your sponsored developer profile, creating sponsorship tiers, submitting your bank and tax information, and enabling two-factor authentication for your account on {% data variables.product.product_location %}.'
|
||||
redirect_from:
|
||||
- /articles/becoming-a-sponsored-developer
|
||||
- /github/supporting-the-open-source-community-with-github-sponsors/becoming-a-sponsored-developer
|
||||
@@ -14,62 +14,82 @@ topics:
|
||||
- User account
|
||||
- Sponsors profile
|
||||
shortTitle: Set up for personal account
|
||||
ms.openlocfilehash: 288dd5ab53d1a27b7f97ccf9429973a668d8f72b
|
||||
ms.sourcegitcommit: 47bd0e48c7dba1dde49baff60bc1eddc91ab10c5
|
||||
ms.translationtype: HT
|
||||
ms.contentlocale: zh-CN
|
||||
ms.lasthandoff: 09/05/2022
|
||||
ms.locfileid: '145164620'
|
||||
---
|
||||
## 加入 {% data variables.product.prodname_sponsors %}
|
||||
|
||||
## Joining {% data variables.product.prodname_sponsors %}
|
||||
|
||||
{% data reusables.sponsors.you-can-be-a-sponsored-developer %} {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
若要将 {% data variables.product.prodname_sponsors %} 作为组织加入，请参阅“[为组织设置 {% data variables.product.prodname_sponsors %}](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)”。
|
||||
To join {% data variables.product.prodname_sponsors %} as an organization, see "[Setting up {% data variables.product.prodname_sponsors %} for your organization](/sponsors/receiving-sponsorships-through-github-sponsors/setting-up-github-sponsors-for-your-organization)."
|
||||
|
||||
{% data reusables.sponsors.navigate-to-github-sponsors %}
|
||||
2. 如果您是组织所有者，则有多个符合条件的帐户。 单击“查看符合条件的帐户”，然后在帐户列表中找到你的个人帐户。
|
||||
3. 单击“加入等待列表”。
|
||||
{% data reusables.sponsors.contact-info %} {% data reusables.sponsors.accept-legal-terms %}
|
||||
2. If you are an organization owner, you have more than one eligible account. Click **Get sponsored**, then in the list of accounts, find your personal account.
|
||||
|
||||
3. Click **Join the waitlist**.
|
||||
{% data reusables.sponsors.contact-info %}
|
||||
{% data reusables.sponsors.payout-choice %}
|
||||
|
||||
|
||||
如果您在受支持的区域有银行帐户， {% data variables.product.prodname_dotcom %} 将在两周内审核您的申请。
|
||||
{% data reusables.sponsors.accept-legal-terms %}
|
||||
|
||||
## 填写被赞助开发者个人资料
|
||||
If you have a bank account in a supported region, {% data variables.product.prodname_dotcom %} will review your application within two weeks.
|
||||
|
||||
在 {% data variables.product.prodname_dotcom %} 审核您的申请后，您可以设置您的被赞助开发者个人资料，以便人们可以开始赞助您。
|
||||
## Completing your sponsored developer profile
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-profile-tab %} {% data reusables.sponsors.short-bio %} {% data reusables.sponsors.add-introduction %} {% data reusables.sponsors.edit-featured-work %} {% data reusables.sponsors.opt-in-to-being-featured %} {% data reusables.sponsors.save-profile %}
|
||||
After {% data variables.product.prodname_dotcom %} reviews your application, you can set up your sponsored developer profile so that people can start sponsoring you.
|
||||
|
||||
## 创建赞助等级
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-profile-tab %}
|
||||
{% data reusables.sponsors.short-bio %}
|
||||
{% data reusables.sponsors.add-introduction %}
|
||||
{% data reusables.sponsors.edit-featured-work %}
|
||||
{% data reusables.sponsors.opt-in-to-being-featured %}
|
||||
{% data reusables.sponsors.save-profile %}
|
||||
|
||||
## Creating sponsorship tiers
|
||||
|
||||
{% data reusables.sponsors.tier-details %}
|
||||
|
||||
{% data reusables.sponsors.maximum-tier %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.navigate-to-sponsor-tiers-tab %} {% data reusables.sponsors.click-add-tier %} {% data reusables.sponsors.tier-price-description %} {% data reusables.sponsors.add-welcome-message %} {% data reusables.sponsors.save-tier-draft %} {% data reusables.sponsors.review-and-publish-tier %} {% data reusables.sponsors.add-more-tiers %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.navigate-to-sponsor-tiers-tab %}
|
||||
{% data reusables.sponsors.click-add-tier %}
|
||||
{% data reusables.sponsors.tier-price-description %}
|
||||
{% data reusables.sponsors.add-welcome-message %}
|
||||
{% data reusables.sponsors.save-tier-draft %}
|
||||
{% data reusables.sponsors.review-and-publish-tier %}
|
||||
{% data reusables.sponsors.add-more-tiers %}
|
||||
|
||||
## 提交您的银行信息
|
||||
## Submitting your bank information
|
||||
|
||||
如果您居住在受支持的区域，可以按照这些说明创建 Stripe Connect 帐户来提交银行信息。 您居住的区域与您的银行帐户所在区域必须匹配。 {% data reusables.sponsors.stripe-supported-regions %}
|
||||
As a sponsored user, you will receive payouts to a bank account in a supported region or via a fiscal host.
|
||||
|
||||
{% data reusables.sponsors.bank-info-fiscal-host-reminder %} For more information about setting up and using fiscal hosts, see "[Using a fiscal host to receive GitHub Sponsors payouts](/sponsors/receiving-sponsorships-through-github-sponsors/using-a-fiscal-host-to-receive-github-sponsors-payouts)."
|
||||
|
||||
If you choose to receive payouts to a bank account, your region of residence and the region of your bank account must match. {% data reusables.sponsors.stripe-supported-regions %}
|
||||
|
||||
{% data reusables.sponsors.double-check-stripe-info %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.create-stripe-account %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.create-stripe-account %}
|
||||
|
||||
## 提交您的税务信息
|
||||
## Submitting your tax information
|
||||
|
||||
{% data reusables.sponsors.tax-form-information-dev %}
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %} {% data reusables.sponsors.overview-tab %} {% data reusables.sponsors.tax-form-link %}
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
{% data reusables.sponsors.overview-tab %}
|
||||
{% data reusables.sponsors.tax-form-link %}
|
||||
|
||||
## 在您的 {% data variables.product.prodname_dotcom %} 帐户上启用双重身份验证 (2FA)。
|
||||
## Enabling two-factor authentication (2FA) on your {% data variables.product.prodname_dotcom %} account
|
||||
|
||||
在成为被赞助的开发者之前，您必须为您在 {% data variables.product.product_location %} 上的帐户启用 2FA。 有关详细信息，请参阅“[配置双因素身份验证](/articles/configuring-two-factor-authentication)”。
|
||||
Before you can become a sponsored developer, you must enable 2FA for your account on {% data variables.product.product_location %}. For more information, see "[Configuring two-factor authentication](/articles/configuring-two-factor-authentication)."
|
||||
|
||||
## 向 {% data variables.product.prodname_dotcom %} 提交申请以请求批准
|
||||
## Submitting your application to {% data variables.product.prodname_dotcom %} for approval
|
||||
|
||||
{% data reusables.sponsors.navigate-to-sponsors-dashboard %}
|
||||
4. 单击“请求审批”。
|
||||
|
||||
4. Click **Request approval**.
|
||||
|
||||
|
||||
{% data reusables.sponsors.github-review-app %}
|
||||
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #7088 GitHub Advisory Database now supports advisories for malware
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-7088'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6154
|
||||
# Documentation for Actions cache management APIs (initial ship)
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '> 3.4'
|
||||
ghae: '问题-6154'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: #6456
|
||||
# APIs to set default and max cache sizes. Only for GHES.
|
||||
versions:
|
||||
ghes: '>=3.5'
|
||||
ghae: '问题-6456'
|
||||
7
translations/zh-CN/data/features/actions-caching.yml
Normal file
7
translations/zh-CN/data/features/actions-caching.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Reference: #6456
|
||||
# General versioning for caching feature for Actions, newly added to GHES in 3.5
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6456'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6447
|
||||
# Versions of actions used in workflows have been updated to their Node 16 version.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6447'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #5727
|
||||
# Documentation for new runner 'arch' environment variables set by the `runner` app.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.4'
|
||||
ghae: '问题-5727'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: #6478.
|
||||
# Versioning for enterprise/org/repo policy settings for reusable workflow use.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6926.
|
||||
# Versioning for enterprise/repository policy settings for workflow PR creation or approval permission. This is only the enterprise and repo settings! For the previous separate ship for the org setting (that only overed approvals), see the allow-actions-to-approve-pr flag.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6926'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference #5104
|
||||
# Documentation for the "Audit data retention" tab in the enterprise audit log
|
||||
versions:
|
||||
ghes: '>=3.4'
|
||||
ghae: '问题-5104'
|
||||
5
translations/zh-CN/data/features/audit-log-streaming.yml
Normal file
5
translations/zh-CN/data/features/audit-log-streaming.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #7055
|
||||
# Documentation for audit log streaming
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>= 3.6'
|
||||
6
translations/zh-CN/data/features/blame-ignore-revs.yml
Normal file
6
translations/zh-CN/data/features/blame-ignore-revs.yml
Normal file
@@ -0,0 +1,6 @@
|
||||
# Reference: #6378.
|
||||
# Documentation for the `.git-blame-ignore-revs` file and the blame view
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.4'
|
||||
@@ -0,0 +1,5 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: '问题-5895'
|
||||
5
translations/zh-CN/data/features/codeowners-errors.yml
Normal file
5
translations/zh-CN/data/features/codeowners-errors.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: '问题-6078'
|
||||
6
translations/zh-CN/data/features/codeql-ml-queries.yml
Normal file
6
translations/zh-CN/data/features/codeql-ml-queries.yml
Normal file
@@ -0,0 +1,6 @@
|
||||
# Reference: #5604.
|
||||
# Documentation for the beta release of CodeQL queries boosted by machine learning
|
||||
# to generate experiemental alerts in code scanning.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
5
translations/zh-CN/data/features/codeql-packs.yml
Normal file
5
translations/zh-CN/data/features/codeql-packs.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #4702.
|
||||
# Documentation for the CodeQL package manager and CodeQL packs.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
5
translations/zh-CN/data/features/command-palette.yml
Normal file
5
translations/zh-CN/data/features/command-palette.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #5199.
|
||||
# Documentation for the Command palette.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
6
translations/zh-CN/data/features/container-hooks.yml
Normal file
6
translations/zh-CN/data/features/container-hooks.yml
Normal file
@@ -0,0 +1,6 @@
|
||||
# Reference: #7070
|
||||
# Actions Runner Container Hooks
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghae: '问题-7070'
|
||||
3
translations/zh-CN/data/features/copilot.yml
Normal file
3
translations/zh-CN/data/features/copilot.yml
Normal file
@@ -0,0 +1,3 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: '问题-6271'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Tracking removing ability to delete code scanning alerts: ghae-issue-6776
|
||||
|
||||
versions:
|
||||
ghae: '*'
|
||||
ghes: '<3.6'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6913
|
||||
# Dependabot support for TypeScript @types/*
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: '问题-6913'
|
||||
@@ -0,0 +1,3 @@
|
||||
versions:
|
||||
ghes: '>=3.4'
|
||||
ghae: 'issue-5867'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #6964 Support for Rust manifest parsing in Dependency graph
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: '问题-6964'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #7061 Configuring the dependency review action - [Public Beta]
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.5'
|
||||
ghae: 'issue-7061'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: Issue #5741 in docs-content
|
||||
# Documentation for enterprise owners UI updates
|
||||
versions:
|
||||
ghes: '>=3.4'
|
||||
ghae: 'issue-5741'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #5278.
|
||||
# Documentation for the fixed-width font support for markdown fields.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.4'
|
||||
ghae: 'issue-5278'
|
||||
6
translations/zh-CN/data/features/for-you-feed.yml
Normal file
6
translations/zh-CN/data/features/for-you-feed.yml
Normal file
@@ -0,0 +1,6 @@
|
||||
# Issues 4834 and 5722
|
||||
# New feed for personal dashboards and option to follow organizations
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #6724
|
||||
# Documentation for Git events in the audit log
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6724'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #5813.
|
||||
# Documentation for GitHub Actions workflow dependencies appearing in the dependency graph
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghae: 'issue-5813'
|
||||
ghes: '>3.4'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,3 @@
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
5
translations/zh-CN/data/features/githubdev-editor.yml
Normal file
5
translations/zh-CN/data/features/githubdev-editor.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Reference: #4918, #7438.
|
||||
# Documentation for the github.dev web-based editor
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6035 #6036 #6037
|
||||
# Documentation for enterprise policies that define where forks can be created.
|
||||
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>3.6'
|
||||
ghae: '问题-6035'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Reference: #6665
|
||||
# GitHub Apps are supported as actors in all types of exceptions to branch protections
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>= 3.6'
|
||||
ghae: '问题-6665'
|
||||
2
translations/zh-CN/data/features/ip-exception-list.yml
Normal file
2
translations/zh-CN/data/features/ip-exception-list.yml
Normal file
@@ -0,0 +1,2 @@
|
||||
versions:
|
||||
ghes: '>=3.5'
|
||||
7
translations/zh-CN/data/features/math-fenced-blocks.yml
Normal file
7
translations/zh-CN/data/features/math-fenced-blocks.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Reference: #7471.
|
||||
# Documentation for fenced math blocks in markdown.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: 'issue-7471'
|
||||
5
translations/zh-CN/data/features/oidc-for-emu.yml
Normal file
5
translations/zh-CN/data/features/oidc-for-emu.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Issues 6495 and 6494
|
||||
# OIDC/CAP for Enterprise Managed Users
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghae: 'issue-6495'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue #5108
|
||||
# Documentation for the "Only notify requested team members" option in the code review settings
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.4'
|
||||
ghae: 'issue-5108'
|
||||
5
translations/zh-CN/data/features/placeholder.yml
Normal file
5
translations/zh-CN/data/features/placeholder.yml
Normal file
@@ -0,0 +1,5 @@
|
||||
# Do not delete! Used by tests.
|
||||
versions:
|
||||
ghes: '>3.0'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
@@ -0,0 +1,4 @@
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6336'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 7052
|
||||
# Adding a previous (release) tag for users when creating a new release and autogenerating release notes
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-7052'
|
||||
@@ -0,0 +1,5 @@
|
||||
# Reference: #5244
|
||||
# Documentation for moderation setting to limit who can approve or request changes on a PR.
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference 5861
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.4'
|
||||
ghae: '问题-5861'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Issue 6137
|
||||
# Restrict self-hosted runner groups to specific workflows
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6137'
|
||||
@@ -0,0 +1,7 @@
|
||||
# Issue 6045
|
||||
# Restrict pushes that create matching branches option, within branch restrictions
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6045'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7046.
|
||||
# Documentation for new audit log events for alerts for secret scanning.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: '问题-7046'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #6615.
|
||||
# Documentation for new audit log events for custom patterns for secret scanning.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.5'
|
||||
ghae: 'issue-6615'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7298.
|
||||
# Documentation for new events related to secret scanning push protection bypasses, e.g. audit log.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.6'
|
||||
ghae: '问题-7298'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #7511.
|
||||
# When developers bypass a block by push protection for a detected secret, administrators will receive an email notification of that bypass.
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '>=3.7'
|
||||
ghae: '问题-7511'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #6788.
|
||||
# Documentation for secret scanning as a push protection in the web ui (as opposed to command line)
|
||||
versions:
|
||||
ghes: '>=3.6'
|
||||
ghae: 'issue-6788'
|
||||
ghec: '*'
|
||||
7
translations/zh-CN/data/features/security-managers.yml
Normal file
7
translations/zh-CN/data/features/security-managers.yml
Normal file
@@ -0,0 +1,7 @@
|
||||
# Reference: #4999.
|
||||
# Documentation for the security manager org-level role
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.3'
|
||||
ghae: '*'
|
||||
ghec: '*'
|
||||
@@ -0,0 +1,6 @@
|
||||
# Reference: #5503.
|
||||
# Documentation for the security overview individual views
|
||||
versions:
|
||||
ghes: '> 3.4'
|
||||
ghae: 'issue-5503'
|
||||
ghec: '*'
|
||||
4
translations/zh-CN/data/features/server-statistics.yml
Normal file
4
translations/zh-CN/data/features/server-statistics.yml
Normal file
@@ -0,0 +1,4 @@
|
||||
# Reference #6677
|
||||
# Documentation for GitHub Enterprise Server Statistics
|
||||
versions:
|
||||
ghes: '>=3.5'
|
||||
101
translations/zh-CN/data/glossaries/candidates.yml
Normal file
101
translations/zh-CN/data/glossaries/candidates.yml
Normal file
@@ -0,0 +1,101 @@
|
||||
- term: 高级支持
|
||||
- term: 标准支持
|
||||
- term: 事件
|
||||
- term: 提交
|
||||
- term: 联系人
|
||||
- term: 严重性
|
||||
- term: 服务级别协议
|
||||
- term: 额度
|
||||
- term: 客户管理团队
|
||||
- term: 票证
|
||||
- term: 企业支持
|
||||
- term: 支持门户
|
||||
- term: 紧急
|
||||
- term: 高
|
||||
- term: 中等
|
||||
- term: 低
|
||||
- term: 外延支持包
|
||||
- term: 公司名称
|
||||
- term: 隐私模式
|
||||
- term: 身份验证方法
|
||||
- term: 运行时间
|
||||
- term: 领导力
|
||||
- term: 上报到管理
|
||||
- term: 票证未响应
|
||||
- term: 异地复制
|
||||
- term: 生产系统
|
||||
- term: 从敏感数据中删除识别信息
|
||||
- term: 业务理由
|
||||
- term: 合格信用
|
||||
- term: 联系销售
|
||||
- term: 联系培训
|
||||
- term: 出站
|
||||
- term: 字母数字
|
||||
- term: 引用
|
||||
- term: 定价计划
|
||||
- term: 单元计划
|
||||
- term: 角色 (role)
|
||||
- term: 兑换优惠券
|
||||
- term: 免费计划
|
||||
- term: 可用
|
||||
- term: 折扣
|
||||
- term: 旧评论
|
||||
- term: 贡献积分
|
||||
- term: 冲突标记
|
||||
- term: 提交正在进行的工作
|
||||
- term: 提交原型
|
||||
- term: 贡献图
|
||||
- term: 审批
|
||||
- term: 关闭
|
||||
- term: 阶段 (stage)
|
||||
- term: 邀请
|
||||
- term: 运行时间
|
||||
- term: 讨论
|
||||
- term: 服务和隐私策略
|
||||
- term: 恢复
|
||||
- term: 管理中心
|
||||
- term: 学术角色
|
||||
- term: 教育折扣
|
||||
- term: 一次性域名
|
||||
- term: 结转
|
||||
- term: quota
|
||||
- term: 私钥 (private key)
|
||||
- term: 公钥 (public key)
|
||||
- term: 热补丁
|
||||
- term: 功能发布
|
||||
- term: 合作提交
|
||||
- term: 子域隔离
|
||||
- term: 内置身份验证
|
||||
- term: 滥用率限制
|
||||
- term: 平均负载
|
||||
- term: 临时
|
||||
- term: 运行前检查
|
||||
- term: 客户代表
|
||||
- term: 统一搜索
|
||||
- term: 休眠用户
|
||||
- term: 调试
|
||||
- term: 合法保留
|
||||
- term: 非请求响应 SSO
|
||||
- term: IdP 发起的 SSO
|
||||
- term: 消息真实性
|
||||
- term: 保留所有权利
|
||||
- term: Campus Advisors
|
||||
- term: Campus Experts
|
||||
- term: 协作开发模式
|
||||
- term: 统一视图
|
||||
- term: 三点差异
|
||||
- term: 多差异
|
||||
- term: 聊天
|
||||
- term: 公共 Gist/机密 Gist
|
||||
- term: 扩展
|
||||
- term: 采购公司
|
||||
- term: 续订订单
|
||||
- term: 每用户定价
|
||||
- term: 观察程序
|
||||
- term: 必需提交签名
|
||||
- term: 检查套件
|
||||
- term: 课堂折扣
|
||||
- term: 学生开发包
|
||||
- term: 学术研究折扣
|
||||
- term: Stargazers
|
||||
- term: 撤销垃圾邮件标记
|
||||
564
translations/zh-CN/data/glossaries/external.yml
Normal file
564
translations/zh-CN/data/glossaries/external.yml
Normal file
@@ -0,0 +1,564 @@
|
||||
- term: '@提及'
|
||||
description:
|
||||
用于通过在用户名前使用 `@` 来通知 GitHub 上的个人。GitHub 上组织中的用户也可以是可以被提及的团队中的一员。
|
||||
- term: 访问令牌
|
||||
description: >-
|
||||
在命令行或 API 上使用 Git 通过 HTTPS 执行 Git 操作时，用来代替密码的令牌。也称为个人访问令牌。
|
||||
- term: API 预览
|
||||
description: >-
|
||||
一种尝试新 API 以及在现有 API 方法成为正式 GitHub API 之前对其进行更改的方式。
|
||||
- term: 工具
|
||||
description: >-
|
||||
一种结合恰当操作系统 (JeOS) 在行业标准硬件（通常是服务器）上或虚拟机中最佳运行的软件应用程序。
|
||||
- term: assignee
|
||||
description: 分配到某个问题的用户。
|
||||
- term: 验证码
|
||||
description: >-
|
||||
通过浏览器使用 2FA 登录时，除了 GitHub 密码外，还需要提供代码。此代码由应用程序生成或通过短信发送到你的手机。也称为“2FA 验证码”。
|
||||
- term: 基础分支
|
||||
description:
|
||||
合并拉取请求时，将更改合并到其中的分支。创建拉取请求时，如果需要，可以将基础分支从存储库的默认分支更改为另一个分支。
|
||||
- term: 基本身份验证
|
||||
description: >-
|
||||
凭据以未加密文本形式发送的身份验证方法。
|
||||
- term: 个人简历
|
||||
description: >-
|
||||
个人资料中用户生成的描述：[为个人资料添加简介](/articles/adding-a-bio-to-your-profile)
|
||||
- term: 计费周期
|
||||
description: 特定计费计划的时间间隔。
|
||||
- term: 计费邮箱
|
||||
description: >-
|
||||
GitHub 用于发送收据、信用卡或 PayPal 费用及其他计费相关信息的组织电子邮件地址。
|
||||
- term: 计费管理员
|
||||
description: 负责管理组织计费设置的组织成员。
|
||||
- term: 收费计划
|
||||
description: >-
|
||||
用户和组织的付款计划，包括每种计划的设置功能。
|
||||
- term: 追溯
|
||||
description: >-
|
||||
Git 中的“追溯”功能描述文件中每一行的最后修改，通常显示修订、作者和时间信息。例如，在跟踪添加某项功能的时间或导致特定 bug 的提交时，此功能非常有用。
|
||||
- term: block
|
||||
description: >-
|
||||
用于删除用户协作处理组织存储库的能力。
|
||||
- term: branch
|
||||
description: >-
|
||||
分支是存储库的并行版本。它包含在存储库中，但不会影响主分支，从而允许在不影响“在线”版本的情况下自由工作。完成所需更改后，可以将分支合并回主分支以发布你的更改。
|
||||
- term: 分支限制
|
||||
description: >-
|
||||
存储库管理员可以启用的一种限制，只允许特定用户或团队推送到分支或做出特定的更改。
|
||||
- term: 业务计划
|
||||
description: >-
|
||||
一种组织计费计划，可以在其中协作处理无限的公共和专用存储库，允许或要求组织成员使用 SAML SSO 对 GitHub 进行身份验证，以及使用 SAML 或 SCIM 预配和取消预配访问权限。
|
||||
- term: CA 证书
|
||||
description: >-
|
||||
由证书机构 (CA) 颁发的数字证书，用于确保有效连接两台计算机，例如用户的计算机和 GitHub.com，以及验证站点的所有权。
|
||||
- term: 卡
|
||||
description: 项目板中与某个问题或拉取请求关联的可移动方框。
|
||||
- term: 检查
|
||||
description: >-
|
||||
检查是 {% data variables.product.product_name %} 上的一种状态检查类型。请参阅“[状态检查](#status-checks)”。
|
||||
- term: 签出
|
||||
description: >-
|
||||
可在命令行上使用 `git checkout` 创建新分支，将当前工作分支更改为其他分支，也可使用 `git checkout [分支名称] [文件路径]` 从不同的分支切换到不同版本的文件。“签出”操作使用对象数据库中的树对象或 Blob 更新全部或部分工作树，如果整个工作树指向新分支，则更新索引和 HEAD。
|
||||
- term: 挑拣
|
||||
description: >-
|
||||
用于从一系列更改（通常是提交）中选择更改的子集，并将它们记录为位于不同代码库之上的一系列新更改。在 Git 中，此操作是由 `git cherry-pick` 命令执行的，用于提取另一个分支上现有提交引入的更改，并根据当前分支的提示将其记录为新提交。有关详细信息，请参阅 Git 文档中的 [git-cherry-pick](https://git-scm.com/docs/git-cherry-pick)。
|
||||
- term: 子团队
|
||||
description: >-
|
||||
在嵌套团队内，继承父团队访问权限和 @提及的子团队。
|
||||
- term: 清洁
|
||||
description: >-
|
||||
如果工作树与当前 HEAD 引用的版本对应，则工作树是清洁的。另请参阅“脏”。
|
||||
- term: 克隆
|
||||
description: >-
|
||||
克隆是存在于计算机上（而不是网站的服务器上）的存储库副本，或者表示创建该副本的行为。进行克隆时，可以在无需联机的情况下，在首选编辑器中编辑文件并使用 Git 跟踪你的更改。克隆的存储库仍将连接到远程版本，这样你就可以将本地更改推送到远程，以便在联机时使其保持同步。
|
||||
- term: 聚类分析
|
||||
description: >-
|
||||
跨多个节点运行 GitHub Enterprise 服务并在它们之间实现请求的负载平衡的功能。
|
||||
- term: 代码频率图
|
||||
description: >-
|
||||
一种显示存储库历史记录中每周的内容添加和删除的存储库图。
|
||||
- term: 行为准则
|
||||
description: 定义关于如何参与社区的标准的文档。
|
||||
- term: 代码所有者
|
||||
description: >-
|
||||
被指定为部分存储库代码所有者的个人。当有人打开对代码所有者拥有的代码进行更改的拉取请求（非草稿模式）时，会自动请求代码所有者进行审查。
|
||||
- term: 协作者
|
||||
description: >-
|
||||
协作者是受存储库所有者邀请参与，对存储库拥有读取和写入权限的人。
|
||||
- term: 提交 (commit)
|
||||
description: >-
|
||||
提交或“修订”是对文件（或文件集）的单独更改。当提交以保存工作时，Git 将创建一个唯一的 ID（也称为“SHA”或“哈希”），它允许记录提交的特定更改以及提交者和提交时间。提交通常包含提交消息，该消息简要说明所做的更改。
|
||||
- term: 提交作者
|
||||
description: 进行提交的用户。
|
||||
- term: 提交图
|
||||
description: >-
|
||||
显示过去一年对存储库的所有提交的存储库图。
|
||||
- term: 提交 ID
|
||||
description: 也称为 SHA。用于识别提交的 40 个字符的校验和哈希。
|
||||
- term: 提交消息
|
||||
description: >-
|
||||
随附于提交的简短描述性文字，用于沟通提交引入的更改。
|
||||
- term: 比较分支
|
||||
description: >-
|
||||
用于创建拉取请求的分支。将此分支与为拉取请求选择的基础分支进行比较，并识别更改。合并拉取请求时，基础分支将使用比较分支中的更改进行更新。也称为拉取请求的“头部分支”。
|
||||
- term: 持续集成
|
||||
description: >-
|
||||
也称为 CI。有人将更改提交到 GitHub 上配置的存储库后，就会运行自动生成和测试的过程。CI 是软件开发中常见的最佳做法，有助于检测错误。
|
||||
- term: 参与图
|
||||
description: >-
|
||||
用户个人资料中显示其参与记录（最长一年，按天显示）的部分。
|
||||
- term: 参与指南
|
||||
description: 说明人们应如何参与项目的文档。
|
||||
- term: 参与
|
||||
description: >-
|
||||
GitHub 上的特定活动，将会：- 添加方块到用户的参与图：“[什么算作参与](/articles/viewing-contributions-on-your-profile/#what-counts-as-a-contribution)”- 添加活动到用户个人资料上的时间线：“[参与活动](/articles/viewing-contributions-on-your-profile/#contribution-activity)”
|
||||
- term: 参与者
|
||||
description: >-
|
||||
参与者是指对存储库没有协作者权限但参与过项目，并且他们打开的拉取请求已合并到存储库的人员。
|
||||
- term: 参与者图
|
||||
description: 显示存储库前 100 个参与者的存储库图。
|
||||
- term: 优惠券
|
||||
description: >-
|
||||
一种由 GitHub 提供的代码，用户或组织可使用它支付其所有或部分订阅费用。
|
||||
- term: cron
|
||||
description: 类似于 Unix 的计算机操作系统中的一个基于时间的作业计划程序。
|
||||
- term: cURL
|
||||
description: 在命令行或脚本中用于传输数据。
|
||||
- term: 仪表板
|
||||
description: >-
|
||||
个人仪表板是 GitHub 上的活动的主要中心。通过个人仪表板，可跟踪正在关注或处理的问题和拉取请求、导航到顶层存储库和团队页面，以及了解正在关注或参与的存储库中的最近活动。还可以发现新的存储库，这些存储库是根据正在关注的用户和已加星标的存储库而推荐的。要仅查看特定组织的活动，请访问该组织的仪表板。有关详细信息，请参阅“[关于个人仪表板](/articles/about-your-personal-dashboard)”或“[关于组织仪表板](/articles/about-your-organization-dashboard)”。
|
||||
- term: 默认分支
|
||||
description: >-
|
||||
存储库中新拉取请求和代码提交的基础分支。每个存储库至少具有一个分支，Git 在初始化存储库时将会创建该分支。第一个分支通常被称为 {% ifversion ghes < 3.2 %}`master`{% else %}`main`{% endif %}，通常是默认分支。
|
||||
- term: 依赖项图
|
||||
description: >-
|
||||
一种显示依赖于公共存储库的包、项目和存储库的存储库图。
|
||||
- term: 依赖项关系图
|
||||
description: >-
|
||||
一种显示存储库所依赖的包和项目的存储库图。
|
||||
- term: 部署密钥
|
||||
description: >-
|
||||
部署密钥是存储在服务器上并授予对单个 GitHub 存储库的访问权限的 SSH 密钥。此密钥直接附加到存储库，而不是附加到个人用户帐户。
|
||||
- term: 拆离的 HEAD
|
||||
description: >-
|
||||
如果正在处理拆离的 HEAD，Git 将发出警告，这意味着 Git 没有指向某个分支，并且所做的任何提交都不会出现在提交历史记录中。 例如，当签出不属于任何特定分支的最新提交的任意提交时，表示你正在处理“拆离的 HEAD”。
|
||||
- term: 诊断
|
||||
description: GitHub Enterprise 实例设置和环境的概述。
|
||||
- term: diff
|
||||
description: >-
|
||||
差异是两次提交或保存的更改之间的更改差异。差异将直观地描述自上次提交以来文件中添加的或删除的内容。
|
||||
- term: directory
|
||||
description: >-
|
||||
包含一个或多个文件/文件夹的文件夹。可以创建目录来组织存储库的内容。
|
||||
- term: 脏
|
||||
description: >-
|
||||
工作树如果包含尚未提交到当前分支的更改，将被视为“脏”。
|
||||
- term: 电子邮件通知
|
||||
description: 已发送到用户的电子邮件地址的通知。
|
||||
- term: 企业帐户
|
||||
description: "企业帐户允许集中管理多个组织的策略和计费。{% data reusables.gated-features.enterprise-accounts %}"
|
||||
- term: 资源管理器
|
||||
description: >-
|
||||
GraphiQL 的实例，它是“图形交互式浏览器内 GraphQL IDE”。
|
||||
- term: 转发
|
||||
description: >-
|
||||
转发是一种特殊类型的合并，其中有一个修订，并且你将“合并”另一个分支的更改，这些更改恰好是你所拥有的内容的后代。在这种情况下，不会进行新的合并提交，而只是更新到此修订。这将在远程存储库的远程跟踪分支上经常发生。
|
||||
- term: 功能分支
|
||||
description: >-
|
||||
用于试验新功能或修复非生产环境中的问题的分支。也称为主题分支。
|
||||
- term: 围栏代码块
|
||||
description: "可以在代码块前后使用三个反引号 \\`\\`\\` 通过 GitHub 风格的 Markdown 创建的缩进代码块。请参阅此 [示例](/articles/creating-and-highlighting-code-blocks#fenced-code-blocks)。"
|
||||
- term: “etch
|
||||
description: >-
|
||||
当使用 `git fetch` 时，将更改从远程存储库添加到本地工作分支，而无需提交它们。与 `git pull` 不同，提取允许在将更改提交到本地分支之前查看该更改。
|
||||
- term: 跟进（用户）
|
||||
description: 用于获取关于另一个用户的贡献和活动的通知。
|
||||
- term: 强制推送
|
||||
description: >-
|
||||
使用本地更改覆盖远程存储库而不考虑冲突的 Git 推送。
|
||||
- term: 分支
|
||||
description: >-
|
||||
分支是位于帐户中的其他用户存储库的个人副本。通过分支，可随意更改项目，而不会影响原始上游存储库。还可以在上游存储库中打开拉取请求，并使分支与最新更改保持同步，因为这两个存储库仍处于连接状态。
|
||||
- term: 免费计划
|
||||
description: >-
|
||||
免费的用户帐户计费计划。用户可以与无限的协作者协作处理无限的公共存储库。
|
||||
- term: gist
|
||||
description: >-
|
||||
gist 是一个可共享的文件，可在 GitHub 上对其进行编辑、克隆和创建分支。可以将 gist 设为{% ifversion ghae %}internal{% else %}公开{% endif %}或机密，但任何{% ifversion ghae %}any enterprise member{% else %}拥有该 URL 的人{% endif %}都可以使用机密。
|
||||
- term: Git
|
||||
description: >-
|
||||
Git 是一个开源程序，用于跟踪文本文件中的更改。它由 Linux 操作系统的作者编写，是 GitHub、社交和用户界面赖以构建的核心技术。
|
||||
- term: GitHub Apps
|
||||
description: >-
|
||||
GitHub Apps 为整个组织提供服务，并在执行其功能时使用自己的标识。它们可以直接安装在组织和用户帐户上，并获得对特定存储库的访问权限。它们随附精细的权限和内置的 Webhook。
|
||||
- term: GitHub 风格的 Markdown
|
||||
description: "GitHub 特定的 Markdown，用于在 GitHub 上格式化 prose 和代码。请参阅 [GitHub 风格的 Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。"
|
||||
- term: GitHub 导入工具
|
||||
description: >-
|
||||
一种可让用户快速将源代码存储库（包括提交和修订历史记录）导入 GitHub 的工具。
|
||||
- term: GitHub Jobs
|
||||
description: >-
|
||||
一个 GitHub 网站，雇主可在其中发布 GitHub 用户可能感兴趣的职位。
|
||||
- term: GitHub Marketplace
|
||||
description: >-
|
||||
GitHub 用户和组织用于购买和安装可扩展及补充其工作流的应用程序的子站点。
|
||||
- term: GitHub Pages
|
||||
description: >-
|
||||
也称为 Pages。设计为直接托管 GitHub 存储库中的个人、组织或项目页面的静态站点托管服务。
|
||||
- term: GitHub Wiki
|
||||
description: 用于在 GitHub 存储库上托管 Wiki 样式文档的部分。
|
||||
- term: gitfile
|
||||
description: >-
|
||||
一个纯文本 `.git` 文件，它始终位于工作树的根目录中，并指向包含整个 Git 存储库及其元数据的 Git 目录。可在命令行上使用作为真正存储库的 `git rev-parse --git-dir` 查看存储库的此文件。
|
||||
- term: GraphQL
|
||||
description: >-
|
||||
一种针对 API 的查询语言，以及用于使用现有数据完成这些查询的运行时。
|
||||
- term: HEAD
|
||||
description: 定义的分支提交，通常是分支顶端的最新提交。
|
||||
- term: 头部分支
|
||||
description: 合并拉取请求时，将其更改合并到基础分支中的分支。也称为“比较分支”。
|
||||
- term: 'Hello, World'
|
||||
description: >-
|
||||
“Hello, World”程序是向用户输出或显示“Hello, World!”的计算机程序。由于此程序通常非常简单，因此常被用作编程语言的基本语法的示例，并作为学习新编程语言的第一个常见练习。
|
||||
- term: 高可用性
|
||||
description: >-
|
||||
可持续运行较长时间的系统或组件。
|
||||
- term: 挂钩
|
||||
description: >-
|
||||
在几个 Git 命令的正常执行过程中，将调用允许开发人员添加功能或进行检查的可选脚本。通常，挂钩允许预先验证且可能中止的命令，并允许在操作完成后发布后通知。
|
||||
- term: hostname
|
||||
description: >-
|
||||
人类可读的昵称，与连接到网络的设备地址对应。
|
||||
- term: 默认肖像
|
||||
description: >-
|
||||
当用户注册 GitHub 时，用作默认个人资料照片的自动生成图像。用户可以用自己的个人资料照片替换其标识图标。
|
||||
- term: 标识提供者
|
||||
description: >-
|
||||
也称为 IdP。受信任的提供者，可让你使用 SAML 单一登录 (SSO) 访问其他网站。
|
||||
- term: instance
|
||||
description: >-
|
||||
包含在组织配置和控制的虚拟机中的组织 GitHub 私人副本。
|
||||
- term: 集成
|
||||
description: >-
|
||||
与 GitHub 集成的第三方应用程序。这些应用程序可以是 GitHub Apps、OAuth Apps 或 Webhook。
|
||||
- term: 问题
|
||||
description: >-
|
||||
问题是与存储库相关的建议改进、任务或问题。问题可由任何人创建（对于公共存储库），并由存储库协作者进行管理。每个问题都包含自己的讨论线程。还可以使用标签对问题进行分类，并将其分配给某人。
|
||||
- term: Jekyll
|
||||
description: 针对个人、项目或组织站点的静态站点生成器。
|
||||
- term: Jekyll 主题选择器
|
||||
description: >-
|
||||
一种无需编辑或复制 CSS 文件即可为 Jekyll 站点选择视觉对象主题的自动化方式。
|
||||
- term: 密钥指纹
|
||||
description: 用于标识较长公钥的短字节序列。
|
||||
- term: 密钥链
|
||||
description: macOS 中的密码管理系统。
|
||||
- term: 关键字 (keyword)
|
||||
description: 用在拉取请求中时可关闭问题的特定词。
|
||||
- term: label
|
||||
description: >-
|
||||
问题或拉取请求上的标记。存储库随附一系列默认标签，但用户也可创建自定义标签。
|
||||
- term: LFS
|
||||
description: >-
|
||||
Git Large File Storage。一种开源 Git 扩展，用于对大文件进行版本控制。
|
||||
- term: license
|
||||
description: >-
|
||||
一种可随附于项目的文档，告知人们能够对源代码执行哪些操作，不能执行哪些操作。
|
||||
- term: Linguist
|
||||
description: >-
|
||||
GitHub 上使用的一个库，用于检测 Blob l语言，忽略二进制或 vendor 文件，抑制差异中生成的文件，以及生成语言细分图。
|
||||
- term: 行注释
|
||||
description: 拉取请求内特定代码行上的评论。
|
||||
- term: 行结束符
|
||||
description: >-
|
||||
用符号表示文本文件中一行结束的不可见字符。
|
||||
- term: 已锁定个人帐户
|
||||
description: >-
|
||||
用户无法访问的个人帐户。当用户将其付费帐户降级到免费帐户或者其付费计划过期时，帐户将被锁定。
|
||||
- term: 管理控制台
|
||||
description: >-
|
||||
GitHub Enterprise 界面中包含管理功能的部分。
|
||||
- term: Markdown
|
||||
description: >-
|
||||
Markdown 是一种非常简单的语义文件格式，与 .doc、.rtf 及 .txt 区别不大。Markdown 可帮助没有网络发布功底的人编写 prose（包括链接、列表、项目符号等）并将其显示为网站。GitHub 支持 Markdown 并使用一种特殊形式的 Markdown，称为 GitHub 风格的 Markdown。请参阅 [GitHub 风格的 Markdown 规范](https://github.github.com/gfm/) 或 [在 GitHub 上编写和设置格式入门](/articles/getting-started-with-writing-and-formatting-on-github)。
|
||||
- term: 标记
|
||||
description: 一种用于注释和格式化文档的系统。
|
||||
- term: main
|
||||
description: >-
|
||||
{% ifversion fpt or ghes > 3.1 or ghae %}默认开发分支。每当创建 Git 存储库时，都会创建一个名为 `main` 的分支，并使其成为活动分支。在大多数情况下，这包含本地开发，不过这纯粹是按照惯例的，也不是必需的。{% else %}通常选择名称作为存储库默认分支的 `master` 的替代品。{% endif %}
|
||||
- term: 主
|
||||
description: >-
|
||||
许多 Git 存储库中的默认分支。默认情况下，每当在命令行上创建新的 Git 存储库时，都会创建一个名为 `master` 的分支。许多工具现在为默认分支使用替代名称。{% ifversion fpt or ghes > 3.1 or ghae %}例如，当在 GitHub 上创建新存储库时，默认分支称为 `main`。{% endif %}
|
||||
- term: 成员图
|
||||
description: 显示存储库所有分支的存储库图。
|
||||
- term: 提及
|
||||
description: >-
|
||||
通过在用户名前加上 @ 符号发送给用户的通知。GitHub 上组织中的用户也可以是可以被提及的团队中的一员。
|
||||
- term: merge
|
||||
description: >-
|
||||
合并从一个分支（在同一个存储库中或来自分支）中获取更改并将其应用到另一个分支。这通常作为“拉取请求”（可被视为合并请求）或通过命令行发生。如果没有冲突的更改，可以通过 GitHub.com Web 界面的拉取请求完成合并，也可以始终通过命令行完成合并。
|
||||
- term: 合并冲突
|
||||
description: >-
|
||||
合并分支之间发生的差异。当人们对相同文件的相同行进行不同的更改时，或者一个人编辑文件而另一个人删除同一文件时，就会发生合并冲突。必须先解决合并冲突，然后才能合并分支。
|
||||
- term: 里程碑
|
||||
description: >-
|
||||
一种跟踪存储库中问题或拉取请求组进度的方式。
|
||||
- term: 镜像
|
||||
description: 存储库的新副本。
|
||||
- term: 嵌套团队
|
||||
description: >-
|
||||
父团队的子团队。可以拥有多个子（或嵌套）团队。
|
||||
- term: 网络图
|
||||
description: >-
|
||||
显示整个存储库网络的分支历史记录的存储库图，其中包括根存储库的分支以及包含网络独有提交的分叉的分支。
|
||||
- term: 消息馈送
|
||||
description: >-
|
||||
监视的存储库或人员的活动视图。组织的消息馈送显示该组织拥有的存储库上的活动。
|
||||
- term: 非快进
|
||||
description: >-
|
||||
当存储库的本地副本未与上游存储库同步时，需要在推送本地更改之前获取上游更改。
|
||||
- term: 通知
|
||||
description: >-
|
||||
通过 Web 或电子邮件（具体取决于你的设置）提供的更新，它提供有关你感兴趣的活动的信息。
|
||||
- term: OAuth App
|
||||
description: >-
|
||||
使用访问令牌而非密码来访问用户信息的第三方应用程序。
|
||||
- term: OAuth 令牌
|
||||
description: OAuth Apps 中用于访问用户信息的访问令牌。
|
||||
- term: 外部协作者
|
||||
description: >-
|
||||
已被授予对组织的一个或多个存储库的访问权限，但对该组织没有其他访问权限且不属于组织成员的用户。
|
||||
- term: 开源
|
||||
description: >-
|
||||
开源软件是任何人都可以自由使用、修改和共享（以修改和未修改的形式）的软件。今天，“开源”的概念往往超越了软件，它代表一种协作理念：任何人都可以在线获取工作材料，然后创建分支、修改和讨论它们并为项目做出贡献。
|
||||
- term: organization
|
||||
description: >-
|
||||
组织是由两个或多个用户组成的组，它们通常反映了真实世界的组织。它们由用户管理，可以同时包含存储库和团队。
|
||||
- term: 组织所有者
|
||||
description: 对自己拥有的组织具有完全管理访问权限的用户。
|
||||
- term: origin
|
||||
description: >-
|
||||
默认上游存储库。大多数项目至少有一个他们跟踪的上游项目。默认情况下，原点用于此目的。
|
||||
- term: owner
|
||||
description: >-
|
||||
对组织具有完全管理权限的组织成员。
|
||||
- term: 父团队
|
||||
description: >-
|
||||
在嵌套团队内，子团队继承访问权限和 @提及的主要团队。
|
||||
- term: 参与通知
|
||||
description: >-
|
||||
关于用户名或团队被提及或之前在评论中回复的问题或拉取请求中对话更新的通知。
|
||||
- term: 永久链接
|
||||
description: 指向特定网页的永久静态超链接。
|
||||
- term: 个人帐户
|
||||
description: >-
|
||||
属于个别用户的 GitHub 帐户。
|
||||
- term: 主电子邮件地址
|
||||
description: >-
|
||||
GitHub 用于发送收据、信用卡或 PayPal 费用及其他计费相关信息的主要电子邮件地址。
|
||||
- term: 固定存储库
|
||||
description: >-
|
||||
用户已决定在其个人资料中突出显示的存储库。
|
||||
- term: 预接收挂钩
|
||||
description: >-
|
||||
在可用于实现质量检查的 GitHub Enterprise 服务器上运行的脚本。
|
||||
- term: 专用贡献
|
||||
description: 对专用（与公共相对）存储库的贡献。
|
||||
- term: 专用存储库
|
||||
description: >-
|
||||
专用存储库仅对存储库所有者和所有者指定的协作者可见。
|
||||
- term: 生产分支
|
||||
description: >-
|
||||
包含可使用或部署到应用程序或站点的最终更改的分支。
|
||||
- term: 个人资料
|
||||
description: 显示 GitHub 上用户活动相关信息的页面。
|
||||
- term: 个人资料照片
|
||||
description: >-
|
||||
用户上传到 GitHub 的自定义图像，用于标识其活动，通常与其用户名结合使用。这也称为“应用”。
|
||||
- term: 项目板
|
||||
description: >-
|
||||
GitHub 内由问题、拉取请求和注释组成的板，按列分类为卡。
|
||||
- term: 受保护分支
|
||||
description: >-
|
||||
受保护分支在存储库管理员选择保护的分支上阻止 Git 的多个功能。不能在没有通过所需检查或批准所需审查的情况下强制推送、删除、合并更改这些分支，也不能将文件从 GitHub Web 界面上传到它。受保护分支通常为默认分支。
|
||||
- term: 公共贡献
|
||||
description: 对公共（与专用相对）存储库的贡献。
|
||||
- term: 公共存储库
|
||||
description: >-
|
||||
公共存储库可供任何人查看，包括不是 GitHub 用户的人员。
|
||||
- term: pull
|
||||
description: >-
|
||||
拉取指的是提取更改并合并这些更改的行为。例如，如果有人编辑了你们正在合作处理的远程文件，则需要将这些更改拉取到本地副本，以使其保持最新状态。另请参阅“提取”。
|
||||
- term: 拉取权限
|
||||
description: 读取权限的同义词。
|
||||
- term: 拉取请求
|
||||
description: >-
|
||||
拉取请求是由用户提交的对存储库的建议更改，由存储库协作者接受或拒绝。与问题一样，每个拉取请求都有自己的讨论论坛。
|
||||
- term: 拉取请求审查
|
||||
description: >-
|
||||
拉取请求中协作者批准更改或在拉取请求合并之前申请进一步更改的评论。
|
||||
- term: 脉冲图
|
||||
description: 提供存储库活动概述的存储库图。
|
||||
- term: 打卡图
|
||||
description: >-
|
||||
根据周日期和时间显示存储库更新频率的存储库图
|
||||
- term: push
|
||||
description: >-
|
||||
推送意味着将提交的更改发送到 GitHub.com 上的远程存储库。例如，如果在本地更改了某些内容，则可以推送这些更改，以便其他人可以访问它们。
|
||||
- term: 推送分支
|
||||
description: >-
|
||||
如果成功将分支推送到远程存储库，则可以使用本地分支中的更改更新远程分支。当“推送分支”时，Git 将在远程存储库中搜索分支的 HEAD 引用，并验证它是否是该分支的本地 HEAD 引用的直接上级。验证后，Git 将所有对象（可从本地 HEAD 引用访问，但在远程存储库中丢失）拉取到远程对象数据库，然后更新远程 HEAD 引用。如果远程 HEAD 不是本地 HEAD 的上级，则推送将失败。
|
||||
- term: 推送访问权限
|
||||
description: 写入访问权限的同义词。
|
||||
- term: 读取访问权限
|
||||
description: >-
|
||||
存储库上的权限级别，可让用户从存储库中拉取或读取信息。所有公共存储库都为所有 GitHub 用户提供读取访问权限。拉取访问权限的同义词。
|
||||
- term: 自述文件
|
||||
description: 一个包含有关存储库中文件的信息的文本文件，该文件通常是存储库访问者将看到的第一个文件。自述文件以及存储库许可证、参与指南和行为准则可帮助你共享期望并管理对项目的贡献。
|
||||
- term: 变基
|
||||
description: >-
|
||||
要将一系列变更从一个分支重新应用到不同的基础分支，并将该分支的 HEAD 重置为结果。
|
||||
- term: 恢复代码
|
||||
description: 帮助你重新获取对 GitHub 帐户的访问权限的代码。
|
||||
- term: 发布
|
||||
description: GitHub 封装软件并向用户提供软件的方式。
|
||||
- term: remote
|
||||
description: >-
|
||||
这是托管在服务器上的存储库或分支的版本，很可能是 GitHub.com。远程版本可以连接到本地克隆，以便可以同步更改。
|
||||
- term: 远程存储库
|
||||
description: >-
|
||||
用于跟踪同一个项目但储存在其他位置的存储库。
|
||||
- term: 远程 URL
|
||||
description: >-
|
||||
存储代码的位置：GitHub、其他用户分支甚至不同服务器上的存储库。
|
||||
- term: 副本 (replica)
|
||||
description: >-
|
||||
为主要 GitHub Enterprise 实例提供冗余的 GitHub Enterprise 实例。
|
||||
- term: repository
|
||||
description: >-
|
||||
存储库是 GitHub 最基本的元素。它们很容易被想象为项目的文件夹。存储库包含所有项目文件（包括文档），并存储每个文件的修订历史记录。存储库可以有多个协作者，并且可以是公共的，也可以是专用的。
|
||||
- term: 存储库缓存
|
||||
description: >-
|
||||
GitHub Enterprise 服务器实例的存储库的只读镜像，位于分布式团队和 CI 客户端附近。
|
||||
- term: 存储库图
|
||||
description: 存储库数据的视觉对象表现形式。
|
||||
- term: 存储库维护者
|
||||
description: >-
|
||||
管理存储库的人。此人可以帮助分类问题，并使用标签和其他功能来管理存储库的工作。此人还可能负责更新自述文件和参与文件。
|
||||
- term: 必需拉取请求审查
|
||||
description: >-
|
||||
必需审查确保拉取请求至少获得一次审批审查之后，协作者才可更改受保护分支。
|
||||
- term: 必需状态检查
|
||||
description: >-
|
||||
拉取请求检查，确保在协作者可以对受保护分支进行更改前，所有必需的 CI 测试都已通过。
|
||||
- term: resolve
|
||||
description: 手动修复自动合并失败的操作。
|
||||
- term: 还原
|
||||
description: >-
|
||||
当在 GitHub 上还原拉取请求时，会自动打开一个新的拉取请求，其中包含一个从原始合并拉取请求还原合并提交的提交。在 Git 中，可以使用 `git revert` 还原提交。
|
||||
- term: 审查
|
||||
description: >-
|
||||
审查允许对存储库具有访问权限的其他人评论拉取请求中建议的更改、批准更改或在合并拉取请求之前请求进一步更改。
|
||||
- term: 根目录
|
||||
description: 层次结构中的第一个目录。
|
||||
- term: 根文件系统
|
||||
description: 基本操作系统和 GitHub Enterprise 应用程序环境。
|
||||
- term: 已保存回复
|
||||
description: >-
|
||||
可保存并添加到 GitHub 用户帐户的评论，这样你就可以在 GitHub 中的问题和拉取请求中使用它。
|
||||
- term: scope
|
||||
description: >-
|
||||
OAuth App 可以请求访问公共和非公共数据的命名权限组。
|
||||
- term: 席位
|
||||
description: >-
|
||||
GitHub Enterprise 组织内的用户。这可以被称为“席位数”。
|
||||
- term: 机密团队
|
||||
description: >-
|
||||
只有团队其他人以及具有所有者权限的人员可见的团队。
|
||||
- term: 安全日志
|
||||
description: >-
|
||||
列出最近 50 次操作或过去 90 天内执行的操作的日志。
|
||||
- term: 服务器到服务器请求
|
||||
description: >-
|
||||
由充当机器人的应用程序使用的 API 请求，独立于任何特定用户。例如，按计划运行并关闭长时间没有活动的问题的应用程序。使用此类身份验证的应用程序不使用许可的 GitHub 帐户，因此，在具有允许使用一定数量许可证的计费计划的企业中，服务器到服务器机器人不会使用其中一个 GitHub 许可证。服务器到服务器请求中使用的令牌是通过 [GitHub API](/rest/reference/apps#create-an-installation-access-token-for-an-app) 以编程方式获取的。另请参阅“[用户到服务器请求](#user-to-server-request)”。
|
||||
- term: 服务挂钩
|
||||
description: >-
|
||||
也称为“Webhook”。 Webhook 是一种通知方式，只要存储库或组织上发生特定操作，就会发送通知到外部 Web 服务器。
|
||||
- term: 单一登录
|
||||
description: >-
|
||||
也称为 SSO。允许用户登录到一个位置，然后标识提供者 (IdP) 授予用户对其他服务提供程序的访问权限。
|
||||
- term: 快照
|
||||
description: 虚拟机在某一时间点的检查点。
|
||||
- term: 压缩
|
||||
description: 用于将多个提交合并为一个提交。也称为 Git 命令。
|
||||
- term: SSH 密钥
|
||||
description: >-
|
||||
SSH 密钥是一种使用加密消息向在线服务器标识自己的方法。就好像计算机对其他服务具有自己的唯一密码一样。{% data variables.product.product_name %}使用 SSH 密钥将信息安全地传输到计算机。
|
||||
- term: 暂存实例
|
||||
description: >-
|
||||
在将修改应用到实际 GitHub Enterprise 实例之前测试修改的一种方法。
|
||||
- term: status
|
||||
description: >-
|
||||
拉取请求中的视觉对象表现形式，表示提交符合为参与的存储库设置的条件。
|
||||
- term: 状态检查
|
||||
description: >-
|
||||
状态检查是为在存储库中进行的每个提交而运行的外部进程，例如持续集成生成。有关详细信息，请参阅“[关于状态检查](/articles/about-status-checks)”。
|
||||
- term: 星级
|
||||
description: >-
|
||||
对存储库的书签或表示赞赏。星级是一种手动对项目的受欢迎程度进行排名的方法。
|
||||
- term: 订阅
|
||||
description: 用户或组织的 GitHub 计划。
|
||||
- term: 团队
|
||||
description: >-
|
||||
通过级联访问权限和提及来反映公司或组结构的组织成员组。
|
||||
- term: 团队维护者
|
||||
description: >-
|
||||
具有组织所有者一部分团队管理权限的组织成员。
|
||||
- term: 团队计划
|
||||
description: >-
|
||||
提供无限公共和专用存储库的组织计费计划。
|
||||
- term: 时间线
|
||||
description: 拉取请求或用户个人资料中的一系列事件。
|
||||
- term: 主题分支
|
||||
description: >-
|
||||
一个常规的 Git 分支，开发人员使用它来识别开发的概念线。由于分支非常简单且成本低廉，因此通常希望有几个小分支，每个分支都包含定义非常明确的概念或小的增量但相关的更改。也可以称为特征分支。
|
||||
- term: topics
|
||||
description: >-
|
||||
一种方法，用于探索特定主题领域中的存储库，查找要参与的项目，以及在 GitHub 上发现特定问题的新解决方案。
|
||||
- term: 流量图
|
||||
description: >-
|
||||
显示存储库流量的存储库图，包括完整克隆（非提取）、过去 14 天的访问者、推荐站点及热门内容。
|
||||
- term: 传输
|
||||
description: >-
|
||||
转让存储库是指更改存储库的所有者。新所有者能够立即管理存储库的内容、问题、拉取请求、发行版和设置。
|
||||
- term: 上游
|
||||
description: >-
|
||||
在谈论分支或分叉时，原始存储库上的主分支通常被称为“上游”，因为它是获取其他更改的主要位置。正在处理的分支/分叉则被称为“下游”。也称为原点。
|
||||
- term: 上游分支
|
||||
description: >-
|
||||
合并到相关分支（或相关分支重新基于的分支）中的默认分支。它是通过 `branch.<name>.remote` 和 `branch.<name>.merge` 配置的。如果 A 的上游分支是原点/B，有时表示为“A 是跟踪原点/B”。
|
||||
- term: user
|
||||
description: >-
|
||||
用户是拥有个人 GitHub 帐户的人员。每个用户都有自己的个人资料，并且可以拥有多个公共或专用存储库。他们可以创建或受邀加入组织，也可以在其他用户的存储库上进行协作。
|
||||
- term: username
|
||||
description: GitHub 上的用户句柄。
|
||||
- term: 用户到服务器请求
|
||||
description: >-
|
||||
由代表特定用户执行任务的应用程序所使用的 API 请求。如果使用用户到服务器身份验证执行任务，则在 GitHub 上显示为由用户通过应用程序完成的任务。例如，可以选择在第三方应用程序中创建问题，该应用程序将代表用户在 GitHub 上执行此操作。应用程序可使用用户到服务器请求执行的任务范围受到应用和用户的权限和访问权限的限制。用户到服务器请求中所使用的令牌是通过 OAuth 获取的。有关详细信息，请参阅“[识别和授权 GitHub Apps 的用户](/developers/apps/building-github-apps/identifying-and-authorizing-users-for-github-apps)”。 另请参阅“[服务器到服务器请求](#server-to-server-request)”。
|
||||
- term: 可见团队
|
||||
description: 可被每个组织成员查看和 @提及的团队。
|
||||
- term: 监视
|
||||
description: >-
|
||||
可以监视存储库或问题，以在对问题或拉取请求进行更新时接收通知。
|
||||
- term: 查看通知
|
||||
description: 关于用户订阅的存储库中活动的通知。
|
||||
- term: Web 通知
|
||||
description: >-
|
||||
显示在 GitHub 的 Web 界面中的通知：https://github.com/notifications
|
||||
- term: webhooks
|
||||
description: >-
|
||||
Webhook 允许构建或设置订阅 GitHub.com 上某些事件的 GitHub Apps。Webhook 是一种通知方式，只要存储库或组织上发生特定操作，就会发送通知到外部 Web 服务器。也被称为服务挂钩。
|
||||
- term: 写入访问权限
|
||||
description: >-
|
||||
存储库上的权限级别，可让用户推送或写入对存储库的更改。
|
||||
91
translations/zh-CN/data/learning-tracks/actions.yml
Normal file
91
translations/zh-CN/data/learning-tracks/actions.yml
Normal file
@@ -0,0 +1,91 @@
|
||||
getting_started:
|
||||
title: '{% data variables.product.prodname_actions %} 入门'
|
||||
description: '通过创建第一个工作流来发现 {% data variables.product.prodname_actions %} 的可能性。'
|
||||
guides:
|
||||
- /actions/learn-github-actions/introduction-to-github-actions
|
||||
- /actions/learn-github-actions/finding-and-customizing-actions
|
||||
- /actions/learn-github-actions/essential-features-of-github-actions
|
||||
- /actions/learn-github-actions/managing-complex-workflows
|
||||
- /actions/learn-github-actions/reusing-workflows
|
||||
- /actions/security-guides/security-hardening-for-github-actions
|
||||
featured_track: true
|
||||
continuous_integration:
|
||||
title: '生成和测试代码'
|
||||
description: '可以在存储库中创建自定义持续集成 (CI) 工作流。'
|
||||
guides:
|
||||
- /actions/automating-builds-and-tests/about-continuous-integration
|
||||
- /actions/automating-builds-and-tests/building-and-testing-powershell
|
||||
- /actions/automating-builds-and-tests/building-and-testing-ruby
|
||||
- /actions/automating-builds-and-tests/building-and-testing-java-with-maven
|
||||
- /actions/automating-builds-and-tests/building-and-testing-java-with-gradle
|
||||
- /actions/automating-builds-and-tests/building-and-testing-java-with-ant
|
||||
- /actions/automating-builds-and-tests/building-and-testing-swift
|
||||
continuous_deployment:
|
||||
title: '自动部署'
|
||||
description: '了解如何使用 {% data variables.product.prodname_actions %} 中的自定义持续部署 (CD) 工作流自动发布项目。'
|
||||
guides:
|
||||
- /actions/publishing-packages/about-packaging-with-github-actions
|
||||
- /actions/publishing-packages/publishing-nodejs-packages
|
||||
- /actions/publishing-packages/publishing-java-packages-with-maven
|
||||
- /actions/publishing-packages/publishing-java-packages-with-gradle
|
||||
- /actions/publishing-packages/publishing-docker-images
|
||||
deploy_to_the_cloud:
|
||||
title: '部署到云端'
|
||||
description: '了解如何使用 {% data variables.product.prodname_actions %} 生成应用程序并将其部署到各种基于云的平台。'
|
||||
guides:
|
||||
- /actions/deployment/deploying-to-amazon-elastic-container-service
|
||||
- /actions/deployment/deploying-to-azure-app-service
|
||||
- /actions/deployment/deploying-to-google-kubernetes-engine
|
||||
adopting_github_actions_for_your_enterprise_ghec:
|
||||
title: '为企业采用 GitHub Actions'
|
||||
description: '了解如何在企业中计划和实现 {% data variables.product.prodname_actions %} 的推出。'
|
||||
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: '为企业采用 GitHub Actions'
|
||||
description: '了解如何在企业中计划和实现 {% data variables.product.prodname_actions %} 的推出。'
|
||||
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
|
||||
hosting_your_own_runners:
|
||||
title: '托管自己的运行器'
|
||||
description: '可以创建自托管运行器，以便在高度可自定义的环境中运行工作流。'
|
||||
guides:
|
||||
- /actions/hosting-your-own-runners/about-self-hosted-runners
|
||||
- /actions/hosting-your-own-runners/adding-self-hosted-runners
|
||||
- /actions/hosting-your-own-runners/configuring-the-self-hosted-runner-application-as-a-service
|
||||
- /actions/hosting-your-own-runners/using-a-proxy-server-with-self-hosted-runners
|
||||
- /actions/hosting-your-own-runners/using-labels-with-self-hosted-runners
|
||||
- /actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow
|
||||
- /actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups
|
||||
- /actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners
|
||||
create_actions:
|
||||
title: '创建操作'
|
||||
description: '是否对新操作有想法？是否为项目生成了自定义内容？了解如何构建可共享操作并将其发布到 GitHub 市场。'
|
||||
guides:
|
||||
- /actions/creating-actions/about-custom-actions
|
||||
- /actions/creating-actions/creating-a-docker-container-action
|
||||
- /actions/creating-actions/creating-a-javascript-action
|
||||
- /actions/creating-actions/creating-a-composite-action
|
||||
- /actions/creating-actions/metadata-syntax-for-github-actions
|
||||
- /actions/creating-actions/dockerfile-support-for-github-actions
|
||||
- /actions/creating-actions/setting-exit-codes-for-actions
|
||||
- /actions/creating-actions/publishing-actions-in-github-marketplace
|
||||
@@ -0,0 +1,86 @@
|
||||
# Code scanning configurations
|
||||
- title: Microsoft 的 CodeQL 代码扫描
|
||||
description: Microsoft 开源仓库中 CodeQL 操作的代码扫描工作流示例。
|
||||
href: /microsoft/opensource.microsoft.com/blob/main/.github/workflows/codeql-analysis.yml
|
||||
languages:
|
||||
- javascript
|
||||
tags:
|
||||
- CodeQL
|
||||
- 代码扫描
|
||||
- GitHub 操作
|
||||
- title: Adversarial Robustness Toolbox (ART) CodeQL 代码扫描
|
||||
description: 受信任的 AI 仓库中 CodeQL 操作的代码扫描工作流示例。
|
||||
href: /Trusted-AI/adversarial-robustness-toolbox/blob/main/.github/workflows/codeql-analysis.yml
|
||||
languages:
|
||||
- Python
|
||||
tags:
|
||||
- CodeQL
|
||||
- 代码扫描
|
||||
- GitHub 操作
|
||||
|
||||
# Security policies
|
||||
- title: Microsoft 安全策略模板
|
||||
description: 示例安全策略
|
||||
href: /microsoft/repo-templates/blob/main/shared/SECURITY.md
|
||||
tags:
|
||||
- 安全策略
|
||||
- title: Electron 安全策略
|
||||
description: 示例安全策略
|
||||
href: /electron/electron/blob/master/SECURITY.md
|
||||
tags:
|
||||
- 安全策略
|
||||
|
||||
# Example of security advisory in a major product
|
||||
- title: Rails 的安全通告
|
||||
description: Rails 针对 CVE-2020-15169 发布的安全通告。
|
||||
href: /rails/rails/security/advisories/GHSA-cfjv-5498-mph5
|
||||
tags:
|
||||
- 安全通告
|
||||
|
||||
# Sample scripts for enabling Dependabot alerts and security updates across a whole organization
|
||||
- title: 自动启用 Dependabot 警报和安全更新
|
||||
description: 用于在整个组织中启用 Dependabot 警报和安全更新的示例脚本。
|
||||
href: /github/enable-security-alerts-sample
|
||||
tags:
|
||||
- Dependabot
|
||||
- 警报
|
||||
- 安全更新
|
||||
- 组织
|
||||
- 脚本
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.3'
|
||||
|
||||
# Dependabot configuration only relevant to GitHub.com and GHES 3.3+
|
||||
# Convert "languages" to "package-ecosystems" for Dependabot configurations
|
||||
- title: Super Linter 配置
|
||||
description: Super Linter 仓库中的 Dependabot 版本更新配置示例。
|
||||
href: /github/super-linter/blob/master/.github/dependabot.yml
|
||||
languages:
|
||||
- github-actions
|
||||
- npm
|
||||
- bundler
|
||||
- docker
|
||||
- pip
|
||||
tags:
|
||||
- Dependabot
|
||||
- 版本更新
|
||||
- 配置
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.3'
|
||||
|
||||
- title: Dependabot 版本更新 PR
|
||||
description: Super Linter 仓库中的 Dependabot 版本更新配置生成的拉取请求示例。
|
||||
href: /github/super-linter/pull/1398
|
||||
languages:
|
||||
tags:
|
||||
- Dependabot
|
||||
- 版本更新
|
||||
- 拉取请求
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>=3.3'
|
||||
@@ -3,34 +3,34 @@
|
||||
languages: Javascript
|
||||
href: microsoft/vscode-remote-try-node
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
- title: Python 示例项目
|
||||
description: 使用自定义开发容器尝试 Python 项目
|
||||
languages: Python
|
||||
href: microsoft/vscode-remote-try-python
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
- title: Java 示例项目
|
||||
description: 使用自定义开发容器尝试 Java 项目
|
||||
languages: Java
|
||||
href: microsoft/vscode-remote-try-java
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
- title: Go 示例项目
|
||||
description: 使用自定义开发容器尝试 Go 项目
|
||||
languages: Go
|
||||
href: microsoft/vscode-remote-try-go
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
- title: Rust 示例项目
|
||||
description: 使用自定义开发容器尝试 Rust 项目
|
||||
languages: Rust
|
||||
href: microsoft/vscode-remote-try-rust
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
- title: PHP 示例项目
|
||||
description: 使用自定义开发容器尝试 PHP 项目
|
||||
languages: PHP
|
||||
href: microsoft/vscode-remote-try-php
|
||||
tags:
|
||||
- development containers
|
||||
- 开发容器
|
||||
|
||||
@@ -0,0 +1,37 @@
|
||||
# Images and descriptions are pulled directly from the repo
|
||||
|
||||
- repo: vercel/next.js
|
||||
description: React 框架
|
||||
|
||||
- repo: gatsbyjs/gatsby
|
||||
description: 使用 React 构建快速、现代的应用和网站
|
||||
|
||||
- repo: nodejs/node
|
||||
description: Node.js JavaScript 运行时 ✨🐢🚀✨
|
||||
|
||||
- repo: tailwindlabs/tailwindcss
|
||||
description: 用于快速 UI 发展的实用程序优先 CSS 框架。
|
||||
|
||||
- repo: laravel/framework
|
||||
description: Laravel 是一个 Web 应用程序框架，采用富有表现力、优雅的语法。
|
||||
|
||||
- repo: prisma/prisma
|
||||
description: "Node.js 和 TypeScript 的现代数据库访问（ORM 替代方法） | PostgreSQL, MySQL, MariaDB & SQLite"
|
||||
|
||||
- repo: dotnet/csharplang
|
||||
description: "C# 编程语言设计的官方存储库"
|
||||
|
||||
- repo: home-assistant/frontend
|
||||
description: 🍭 Home Assistant 的前端
|
||||
|
||||
- repo: jspsych/jsPsych
|
||||
description: 用于在 Web 浏览器中创建和运行行为试验的 JavaScript 库
|
||||
|
||||
- repo: adonisjs/core
|
||||
description: 🚀 高度集中于开发者人体工程学、稳定性和信心的 Node.js 框架
|
||||
|
||||
- repo: ImageMagick/ImageMagick
|
||||
description: 🧙♂️ ImageMagick 7
|
||||
|
||||
- repo: react-hook-form/react-hook-form
|
||||
description: 📋 用于表单验证的 React Hooks (Web + React Native)
|
||||
@@ -0,0 +1,19 @@
|
||||
# Images and descriptions are pulled directly from the repo
|
||||
|
||||
- user: chaynHQ
|
||||
description: Chayn 帮助遭受虐待的妇女找到掌握自己生活所需的正确信息和支持。
|
||||
|
||||
- user: foosel
|
||||
description: 👋我叫 Gina，是 OctoPrint 🐙 的创作者和主要开发者。
|
||||
|
||||
- user: dayhaysoos
|
||||
description: 怎么了？我叫 Nick，是一名工程师，对消除电子商务开发人员体验中的摩擦有着新的热情。
|
||||
|
||||
- user: yyx990803
|
||||
description: 我在 Vue.js 和 Vite 上全职工作，前者是一种用于构建 Web 应用程序的前端 JavaScript 框架，后者是一种新式 Web 构建工具。
|
||||
|
||||
- user: calebporzio
|
||||
description: 🚶♂️我于 2019 年 1 月辞去了日常工作，追求开源。此后，我构建了 Laravel Livewire、AlpineJS 和一堆其他东西。
|
||||
|
||||
- user: kjaymiller
|
||||
description: 大家好，我是 Jay！👋我是一名海军陆战队老兵，现已变成开发人员，自 2014 年以来一直在积极编码。我还参与了生产力空间，在那里我帮助人们自动化一些他们最喜欢的应用和工具。
|
||||
@@ -0,0 +1,21 @@
|
||||
date: '2020-02-27'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19116, https://github.com/github/enterprise2/pull/19110, https://github.com/github/enterprise2/pull/19154, https://github.com/github/enterprise2/pull/19142 {% endcomment %}'
|
||||
bugs:
|
||||
- '从备份还原将会失败，并显示“RDB 版本号无效”错误。{% comment %} https://github.com/github/enterprise2/pull/19117, https://github.com/github/enterprise2/pull/19109 {% endcomment %}'
|
||||
- '升级 HA 副本将停止无限期等待 MySQL 启动。{% comment %} https://github.com/github/enterprise2/pull/19168, https://github.com/github/enterprise2/pull/19101 {% endcomment %}'
|
||||
- '具有意外“position”或“original_position”值的 PR 审核评论导致导入失败。{% comment %} https://github.com/github/github/pull/135439, https://github.com/github/github/pull/135374 {% endcomment %}'
|
||||
- '数据库中重复的 Webhook 条目可能导致先前版本的升级失败。{% comment %} https://github.com/github/hookshot/pull/1541, https://github.com/github/hookshot/pull/1426, https://github.com/github/hookshot/pull/1540 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '如果自定义了后台工作进程配置，则升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,21 @@
|
||||
date: '2020-06-23'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20746, https://github.com/github/enterprise2/pull/20727 {% endcomment %}'
|
||||
bugs:
|
||||
- '当使用 UDP 作为传输机制时，过大的日志事件可能导致日志转发不稳定。{% comment %} https://github.com/github/enterprise2/pull/20457, https://github.com/github/enterprise2/pull/20445 {% endcomment %}'
|
||||
- "如果 SSH 密钥属性具有已与用户帐户关联的密钥，则用户通过 SSO 进行的自动取消暂停未完成。 {% comment %} https://github.com/github/github/pull/143474, https://github.com/github/github/pull/142927 {% endcomment %}"
|
||||
- '来自 REST API 的仓库权限哈希表示，对于可拉取访问内部仓库的业务成员，无法访问仓库。 {% comment %} https://github.com/github/github/pull/144755, https://github.com/github/github/pull/144292 {% endcomment %}'
|
||||
- '预览 Markdown 中写入的 GitHub 应用程序描述未正确呈现。{% comment %} https://github.com/github/github/pull/145038, https://github.com/github/github/pull/133360 {% endcomment %}'
|
||||
- '审核日志不包括分支保护更改事件。 {% comment %} https://github.com/github/github/pull/145995, https://github.com/github/github/pull/145014 {% endcomment %}'
|
||||
- "尝试将代码审核分配给空团队成员将导致“500内部服务器错误”。 {% comment %} https://github.com/github/github/pull/146328, https://github.com/github/github/pull/139330 {% endcomment %}"
|
||||
- '使用负载平衡算法的代码审核分配可能反复分配给同一团队成员。{% comment %} https://github.com/github/github/pull/146329, https://github.com/github/github/pull/136504 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '议题若是包含同一仓库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新于 2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,19 @@
|
||||
date: '2020-07-09'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**中：** 将 nginx 更新到 1.16.1 并解决了 CV-2019-20372。（更新于 2020-07-22）{% comment %} https://github.com/github/enterprise2/pull/21251 {% endcomment %}'
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21088, https://github.com/github/enterprise2/pull/21036 {% endcomment %}'
|
||||
bugs:
|
||||
- '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。{% comment %} https://github.com/github/enterprise2/pull/21260, https://github.com/github/enterprise2/pull/21102 {% endcomment %}'
|
||||
- '某些日志文件没有每 7 天轮换一次。 {% comment %} https://github.com/github/enterprise2/pull/21278, https://github.com/github/enterprise2/pull/21264 {% endcomment %}'
|
||||
- '快速重新使用 web 挂钩源端口导致拒绝连接。 {% comment %} https://github.com/github/enterprise2/pull/21289 {% endcomment %}'
|
||||
- '不正确的背景作业可能尝试在配置为被动副本的实例上运行。{% comment %} https://github.com/github/enterprise2/pull/21318, https://github.com/github/enterprise2/pull/21212, https://github.com/github/enterprise2/issues/21167 {% endcomment %}'
|
||||
- '内部仓库未正确地包含在启用 SAML 的组织的搜索结果中。 {% comment %} https://github.com/github/github/pull/147503, https://github.com/github/github/pull/145692 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '议题若是包含同一仓库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,17 @@
|
||||
date: '2020-07-21'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21437, https://github.com/github/enterprise2/pull/21402, https://github.com/github/enterprise2/pull/21495, https://github.com/github/enterprise2/pull/21479 {% endcomment %}'
|
||||
bugs:
|
||||
- '管理控制台监视图有时无法在更大的屏幕上正确显示。 {% comment %} https://github.com/github/enterprise2/pull/21397, https://github.com/github/enterprise2/pull/21381 {% endcomment %}'
|
||||
- '应用 SameSite Cookie 策略时，GitHub 应用程序清单创建流在某些情况下无法使用。 {% comment %} https://github.com/github/github/pull/147826, https://github.com/github/github/pull/144121 {% endcomment %}'
|
||||
changes:
|
||||
- '改进 HAProxy 缩放。 {% comment %} https://github.com/github/enterprise2/pull/21383 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的文件[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories) 被错误地直接添加到仓库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '议题若是包含同一仓库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。 {% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，私有和内部仓库中的议题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,22 @@
|
||||
date: '2020-08-11'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '{% octicon "alert" aria-label="The alert icon" %} **关键：**在 GitHub Pages 中发现了一个远程执行代码漏洞，攻击者可利用该漏洞在构建 GitHub Pages 站点的过程中执行命令。此问题是由于在 Pages 构建过程中使用过时且易受攻击的依赖项造成的。要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和构建 GitHub Pages 站点的权限。 此漏洞影响 GitHub Enterprise Server 的所有版本。为了缓解此漏洞，Kramdown 已更新以解决 CVE-2020-14001。{% comment %} https://github.com/github/pages/pull/2836, https://github.com/github/pages/pull/2827 {% endcomment %}'
|
||||
- '**高：**在 GitHub Enterprise Server 上执行时，攻击者可以将恶意参数注入 Git 子命令。这可能使攻击者能够使用用户控制的部分内容覆盖任意文件，并可能在 GitHub Enterprise Server 实例上执行任意命令。要利用此漏洞，攻击者需要获得访问 GitHub Enterprise Server 实例中存储库的权限。但是，由于存在其他保护措施，我们无法确定积极利用此漏洞的方法。此漏洞通过 GitHub 安全 Bug 悬赏计划报告。{% comment %} https://github.com/github/github/pull/151097 {% endcomment %}'
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/21811, https://github.com/github/enterprise2/pull/21700 {% endcomment %}'
|
||||
bugs:
|
||||
- 'Consul 配置错误导致无法在独立实例上处理某些后台作业。{% comment %} https://github.com/github/enterprise2/pull/21464 {% endcomment %}'
|
||||
- '服务内存分配计算可能会将不正确或无限制的内存分配给某项服务，从而导致系统性能下降。{% comment %} https://github.com/github/enterprise2/pull/21716 {% endcomment %}'
|
||||
- '未正确检测到 oVirt KVM 系统的虚拟化平台，导致升级过程中出现问题。{% comment %} https://github.com/github/enterprise2/pull/21730, https://github.com/github/enterprise2/pull/21669 {% endcomment %}'
|
||||
- "通过 Git 命令行使用密码进行无效身份验证的错误消息未填充 URL 链接以添加适当的令牌或 SSH 密钥。{% comment %} https://github.com/github/github/pull/149714 {% endcomment %}"
|
||||
- 'GitHub Connect 使用的是已弃用的 GitHub.com API 终结点。{% comment %} https://github.com/github/github/pull/150828, https://github.com/github/github/pull/150545 {% endcomment %}'
|
||||
- '在迁移到新实例的存储库上，无法按 *最近更新* 对问题进行排序。{% comment %} https://github.com/github/github/pull/150843, https://github.com/github/github/pull/149330 {% endcomment %}'
|
||||
- '404 页面的页脚中包含 GitHub.com 联系人和状态链接。{% comment %} https://github.com/github/github/pull/151316 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,13 @@
|
||||
date: '2020-09-08'
|
||||
sections:
|
||||
bugs:
|
||||
- '服务运行状况检查会造成会话增加，从而耗尽文件系统 Inode。{% comment %} https://github.com/github/enterprise2/pull/22480, https://github.com/github/enterprise2/pull/22475 {% endcomment %}'
|
||||
- "使用热补丁的升级可能会失败，并显示错误：`'libdbi1' was not found` {% comment %} https://github.com/github/enterprise2/pull/22558，https://github.com/github/enterprise2/pull/22552 {% endcomment %}"
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,14 @@
|
||||
date: '2020-10-20'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23095, https://github.com/github/enterprise2/pull/23081 {% endcomment %}'
|
||||
bugs:
|
||||
- '企业帐户“确认双因素要求策略”消息不正确。{% comment %} https://github.com/github/github/pull/158737 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,28 @@
|
||||
date: '2020-03-10'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19204, https://github.com/github/enterprise2/pull/19187 {% endcomment %}'
|
||||
bugs:
|
||||
- '在某些情况下，转发的日志条目（主要用于 audit.log）被截断。{% comment %} https://github.com/github/enterprise2/pull/19244, https://github.com/github/enterprise2/pull/19192, https://github.com/github/enterprise2/issues/16655 {% endcomment %}'
|
||||
- '`ghe-license-check` 命令行实用程序对某些有效的许可返回“无效的许可证文件”错误，导致配置更改失败。{% comment %} https://github.com/github/enterprise2/pull/19249, https://github.com/github/enterprise2/pull/19185, https://github.zendesk.com/agent/tickets/549903 {% endcomment %}'
|
||||
- 'Alambic 异常日志没有被 syslog 转发。{% comment %} https://github.com/github/enterprise2/pull/19263, https://github.com/github/enterprise2/pull/19123, https://github.com/github/enterprise2/issues/18734 {% endcomment %}'
|
||||
- '[`org_block event`](https://developer.github.com/v3/activity/events/types/#orgblockevent) 并非不可用，但在 GitHub Enterprise Server 上的 GitHub 应用中显示。{% comment %} https://github.com/github/github/pull/136227, https://github.com/github/github/pull/135640, https://github.com/github/ecosystem-apps/issues/693 {% endcomment %}'
|
||||
- 'GraphQL 查询响应有时返回 `ProtectedBranch` 对象的不匹配节点标识符。{% comment %} https://github.com/github/github/pull/136376, https://github.com/github/github/pull/136214, https://github.com/github/github/issues/135407 {% endcomment %}'
|
||||
- 'GitHub Connect 使用的 GitHub 应用凭据在过期后未能立即刷新。{% comment %} https://github.com/github/github/pull/136384, https://github.com/github/github/pull/136259 {% endcomment %}'
|
||||
- '在回复拉请求评论时留下评论会间歇性地创建挂起拉请求审查。{% comment %} https://github.com/github/github/pull/136454, https://github.com/github/github/pull/133697, https://github.com/github/github/issues/127401 {% endcomment %}'
|
||||
- '使用 ghe-migrator 或从 GitHub.com 导出时，导出非图片附件会自动失败。{% comment %} https://github.com/github/github/pull/136487, https://github.com/github/github/pull/134524, https://github.com/github/github/issues/134358 {% endcomment %}'
|
||||
- '在遇到 UTF-8 字符时，预接收挂钩会在 Web UI 上返回 500 错误。{% comment %} https://github.com/github/github/pull/136699, https://github.com/github/github/pull/136014, https://github.com/github/github/issues/133501 {% endcomment %}'
|
||||
changes:
|
||||
- '` ghe-license-usage ` 命令行实用程序新增了 `--unencrypted` 选项，用于查看导出的许可使用文件。{% comment %} https://github.com/github/github/pull/136134, https://github.com/github/github/pull/136000 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '如果自定义了后台工作进程配置，则升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/issues/19119 {% endcomment %}'
|
||||
- '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,16 @@
|
||||
date: '2020-11-03'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**中：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1003, https://github.com/github/slumlord/pull/1000 {% endcomment %}'
|
||||
- "**低：**不正确的令牌验证导致身份验证期间匹配令牌的熵减少。分析表明，在实践中，这里没有重大的安全风险。{% comment %} https://github.com/github/github/pull/159453, https://github.com/github/github/pull/159193 {% endcomment %}"
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23538, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23691, https://github.com/github/enterprise2/pull/23677 {% endcomment %}'
|
||||
bugs:
|
||||
- '推荐用户列表中包含已暂停的用户，其中可能隐藏未暂停的用户。{% comment %} https://github.com/github/github/pull/159809, https://github.com/github/github/pull/140563, https://github.com/github/github/pull/142146 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,19 @@
|
||||
date: '2020-12-03'
|
||||
sections:
|
||||
bugs:
|
||||
- '由于启动中的争用条件导致服务重新启动，因此检测到授权服务不正常。{% comment %} https://github.com/github/authzd/pull/1279, {% endcomment %}'
|
||||
- '在热补丁升级过程中，一种基础行为导致服务不可用。{% comment %} https://github.com/github/enterprise2/pull/24053, https://github.com/github/enterprise2/issues/23947 {% endcomment %}'
|
||||
- '未正确应用部分日志转发 SSL 证书。{% comment %} https://github.com/github/enterprise2/pull/24112, https://github.com/github/enterprise2/pull/23981 {% endcomment %}'
|
||||
- '从团队或组织中移除暂停用户时向他们发送电子邮件通知。{% comment %} https://github.com/github/github/pull/163107, https://github.com/github/github/pull/162742 {% endcomment %}'
|
||||
- '组织和企业之间应用 SSH 证书的方式不一致。{% comment %} https://github.com/github/github/pull/163429, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}'
|
||||
- '当帐户因使用不正确的密码而受到速率限制时，可能被锁定长达 24 小时。{% comment %} https://github.com/github/github/pull/163456, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}'
|
||||
- '在具有许多引用的存储库上进行拉取请求同步可能会导致工作线程队列落后。{% comment %} https://github.com/github/github/pull/163576, https://github.com/github/github/pull/163142 {% endcomment %}'
|
||||
- '在尝试访问特定页面后登录时，用户将发送到主页，而不是其预期目的地。{% comment %} https://github.com/github/github/pull/163785, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,15 @@
|
||||
date: '2020-03-12'
|
||||
sections:
|
||||
bugs:
|
||||
- '如果自定义了后台工作进程配置，升级和设置更新将失败。{% comment %} https://github.com/github/enterprise2/pull/19321, https://github.com/github/enterprise2/pull/19299 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,18 @@
|
||||
date: '2020-03-25'
|
||||
sections:
|
||||
bugs:
|
||||
- 'SAML 身份验证请求和元数据没有严格编码，导致一些标识提供者无法正确处理服务提供者发起的身份验证请求。{% comment %} https://github.com/github/github/pull/137150, https://github.com/github/github/pull/136770, https://github.com/github/github/issues/136766 {% endcomment %}'
|
||||
- '`ghe-migrator` 导出不含里程碑用户，可能会中断导入操作。{% comment %} https://github.com/github/github/pull/138100, https://github.com/github/github/pull/137987, https://github.com/github/github/issues/137779 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/pull/138460, https://github.com/github/github/pull/138313 {% endcomment %}'
|
||||
- '在尝试显示未完全复制的存储库时，`ghe-repl-status` 可能会失败。{% comment %} https://github.com/github/github/pull/138463, https://github.com/github/github/pull/138388 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '从早期版本升级时，可能无法生成后台作业工作进程，从而阻止合并拉取请求等基本功能。（更新时间：2020-04-07）{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- '推送到命令行上的存储库时，不会报告安全警报。（更新时间于 2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,20 @@
|
||||
date: '2020-04-07'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/19536, https://github.com/github/enterprise2/pull/19494 {% endcomment %}'
|
||||
bugs:
|
||||
- '当全球企业帐户设置了 100MB 以外的 Git 对象大小选项时，无法为存储库选择 100MB 大小的最大 Git 对象选项。{% comment %} https://github.com/github/github/pull/138805, https://github.com/github/github/pull/138683 {% endcomment %}'
|
||||
- '当按 `updated_at` 字段排序时，问题和拉取请求 API 的结果可能存在不一致的行为。{% comment %} https://github.com/github/github/pull/139247, https://github.com/github/github/pull/138486 {% endcomment %}'
|
||||
- '无法通过 GraphQL API 查询 SecurityVulnerability `package` 字段。{% comment %} https://github.com/github/github/pull/139418, https://github.com/github/github/pull/138245 {% endcomment %}'
|
||||
- '将存储库从*公共*更改为*内部*会显示一条不相关的计费消息。{% comment %} https://github.com/github/github/pull/139531, https://github.com/github/github/pull/139492 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新设置的 GitHub Enterprise Server 上，，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '当推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '从以前的版本升级时，可能不会生成后台作业工作者，从而阻止基本功能，例如合并拉取请求。{% comment %} https://github.com/github/enterprise2/issues/19232 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。（2020 年 6 月 23 日更新）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（2020 年 6 月 30 日更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,21 @@
|
||||
date: '2020-05-05'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20027, https://github.com/github/enterprise2/pull/19997 {% endcomment %}'
|
||||
bugs:
|
||||
- '`ghe-repl-start` 和 `ghe-repl-status` 显示了语法错误。{% comment %} https://github.com/github/enterprise2/pull/19954, https://github.com/github/enterprise2/pull/19927 {% endcomment %}'
|
||||
- '如果仓库启用了“自动删除头分支”设置，则当 GitHub App 安装合并拉取请求时，头部分支不会自动删除。{% comment %} https://github.com/github/github/pull/141588, https://github.com/github/github/pull/133698, https://github.com/github/github/pull/133871, https://github.com/github/github/issues/132588 {% endcomment %}'
|
||||
- '当组织成员恢复时，web 挂钩有效负载将 `ghost` 用户报告为发送者，而不是执行恢复的实际用户。{% comment %} https://github.com/github/github/pull/141731, https://github.com/github/github/pull/140609 {% endcomment %}'
|
||||
- '如果仓库启用了“自动删除头部分支”设置，则在头部仓库不同于基础仓库的地方，头部分支不会被自动删除。{% comment %} https://github.com/github/github/pull/142096, https://github.com/github/github/pull/133871 {% endcomment %}'
|
||||
- '临时文件的垃圾收集可能导致许可证验证错误。{% comment %} https://github.com/github/github/pull/142209, https://github.com/github/github/pull/142189 {% endcomment %}'
|
||||
- '在某些情况下，包括在首次创建仓库时，接收前挂钩将在没有为 GITHUBHUBB_REPO_PUBLIC 环境变量填写值的情况下运行。{% comment %} https://github.com/github/github/pull/139419, https://github.com/github/github/pull/136228, https://github.com/github/github/pull/134363 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的 [通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '当推送到 Gist 时，可能会在后接收挂钩期间触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的存储库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在具有多个 Redis 节点的群集配置中部署时不会检测依赖项。（2020 年 6 月 30 日更新）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,20 @@
|
||||
date: '2020-05-19'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20108, https://github.com/github/enterprise2/pull/20086 {% endcomment %}'
|
||||
bugs:
|
||||
- '许可证文件更新后，未正确重新加载服务，导致功能丢失。{% comment %} https://github.com/github/enterprise2/pull/20072, https://github.com/github/enterprise2/pull/19989 {% endcomment %}'
|
||||
- '如果响应正文过大，内部 API 请求更新依赖项关系图信息可能会失败。{% comment %} https://github.com/github/enterprise2/pull/20231, https://github.com/github/enterprise2/pull/20208 {% endcomment %}'
|
||||
- '未遵从某些 GraphQL 存储库连接的 `affiliations` 参数。{% comment %} https://github.com/github/github/pull/142036, https://github.com/github/github/pull/140658 {% endcomment %}'
|
||||
- '如果 SAML 电子邮件属性与 GitHub 用户电子邮件大小写形式不同，则无法通过 SSO 自动取消暂停用户。{% comment %} https://github.com/github/github/pull/143321, https://github.com/github/github/pull/142915 {% endcomment %}'
|
||||
- '将用户的成员身份恢复为组织没有在 Webhook 和审核日志有效负载中检测参与者。{% comment %} https://github.com/github/github/pull/143231, https://github.com/github/github/pull/140849 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,17 @@
|
||||
date: '2020-06-02'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**高：**在 GitHub Enterprise Server API 中发现了一个不适当的访问控制漏洞，该漏洞允许组织成员升级权限，获得对组织内未经授权的存储库的访问权限。此漏洞影响 GitHub Enterprise Server 2.21 之前的所有版本。 为应对此问题，我们发布了 [CVE-2020-10516](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10516)。此漏洞通过 [GitHub Bug 赏金计划](https://bounty.github.com)报告。{% comment %} https://github.com/github/github/pull/144454, https://github.com/github/github/pull/143444 {% endcomment %}'
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20421, https://github.com/github/enterprise2/pull/20315 {% endcomment %}'
|
||||
bugs:
|
||||
- '面向 Internet 的 GitHub Enterprise Server 实例可以通过搜索引擎编制索引。{% comment %} https://github.com/github/github/pull/145073, https://github.com/github/github/pull/144973 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪的文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '推送到 Gist 时，可能会在后接收挂钩时触发异常。{% comment %} https://github.com/github/github/issues/129091 {% endcomment %}'
|
||||
- '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。（更新时间：2020-06-23）{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '依赖项关系图在多个 Redis 节点的群集配置中部署时不会检测依赖项。（更新时间：2020-06-30）{% comment %} https://github.com/github/dependency-graph/issues/81 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,21 @@
|
||||
date: '2020-06-23'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/20747, https://github.com/github/enterprise2/pull/20727 {% endcomment %}'
|
||||
bugs:
|
||||
- '当使用 UDP 作为传输机制时，过大的日志事件可能导致日志转发不稳定。{% comment %} https://github.com/github/enterprise2/pull/20458, https://github.com/github/enterprise2/pull/20445 {% endcomment %}'
|
||||
- '用于访问 MySQL 的内部通信服务可能会比预期更频繁地重启，包括在升级过程中，这可能会导致升级部分失败。我们降低了重启率并使代码更加稳健。{% comment %} https://github.com/github/enterprise2/pull/20957, https://github.com/github/enterprise2/pull/20972, https://github.com/github/github/pull/146974 {% endcomment %}'
|
||||
- "如果 SSH 密钥属性具有已与用户帐户关联的密钥，则用户通过 SSO 进行的自动取消暂停未完成。{% comment %} https://github.com/github/github/pull/143475, https://github.com/github/github/pull/142927 {% endcomment %}"
|
||||
- '来自 REST API 的存储库权限哈希表示，对于可拉取访问内部存储库的业务成员，无法访问存储库。{% comment %} https://github.com/github/github/pull/144756, https://github.com/github/github/pull/144292 {% endcomment %}'
|
||||
- '“存储库问题删除”企业帐户策略未反映当前保存的设置。{% comment %} https://github.com/github/github/pull/145218, https://github.com/github/github/pull/145067 {% endcomment %}'
|
||||
- '审核日志不包括分支保护更改事件。{% comment %} https://github.com/github/github/pull/145998, https://github.com/github/github/pull/145014 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}'
|
||||
- "将存储库的权限配置为“会审”或“维护”失败，并显示错误消息。"
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,15 @@
|
||||
date: '2020-10-20'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23096, https://github.com/github/enterprise2/pull/23081 {% endcomment %}'
|
||||
bugs:
|
||||
- '企业帐户“确认双因素要求策略”消息不正确。{% comment %} https://github.com/github/github/pull/158736 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。（更新时间：2020-11-02）{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,18 @@
|
||||
date: '2020-11-03'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**中：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1004, https://github.com/github/slumlord/pull/1000 {% endcomment %}'
|
||||
- "**低：**不正确的令牌验证导致身份验证期间匹配令牌的熵减少。分析表明，在实践中，这里没有重大的安全风险。{% comment %} https://github.com/github/github/pull/159455, https://github.com/github/github/pull/159193 {% endcomment %}"
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23539, https://github.com/github/enterprise2/pull/23171, https://github.com/github/enterprise2/pull/23692, https://github.com/github/enterprise2/pull/23677 {% endcomment %}'
|
||||
bugs:
|
||||
- '使用包含非 ASCII 字符的文件名编辑问题模板将会失败，并显示“500 内部服务器错误”。{% comment %} https://github.com/github/github/pull/160589, https://github.com/github/github/pull/159747 {% endcomment %}'
|
||||
- '背景作业的指标收集方法提高了 CPU 利用率。（更新时间：2020-11-03）{% comment %} https://github.com/github/github/pull/160109 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '审核日志可归因于 127.0.0.1，而不是实际源 IP 地址。{% comment %} https://github.com/github/enterprise2/issues/21514 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,16 @@
|
||||
date: '2020-11-17'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/23844, https://github.com/github/enterprise2/pull/23712 {% endcomment %}'
|
||||
bugs:
|
||||
- 'Babeld 日志在秒与微秒之间缺少分隔符。{% comment %} https://github.com/github/babeld/pull/1005, https://github.com/github/babeld/pull/1002 {% endcomment %}'
|
||||
- '当企业帐户“存储库可见性更改”策略设置为“启用”时，组织所有者无法更改组织内存储库的可见性。{% comment %} https://github.com/github/github/pull/160921, https://github.com/github/github/pull/160773 {% endcomment %}'
|
||||
- '审核日志可以归因于 127.0.0.1，而不是实际的源 IP 地址。{% comment %} https://github.com/github/github/pull/162436, https://github.com/github/github/pull/161215 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,19 @@
|
||||
date: '2020-12-03'
|
||||
sections:
|
||||
bugs:
|
||||
- '由于 bootstrap 中的争用条件导致服务重启，授权服务被检测为运行不正常。{% comment %} https://github.com/github/authzd/pull/1278 {% endcomment %}'
|
||||
- '在热补丁升级过程中，一种潜在的行为导致服务不可用。{% comment %} https://github.com/github/enterprise2/pull/24054, https://github.com/github/enterprise2/issues/23947 {% endcomment %}'
|
||||
- '未正确应用日志转发 SSL 证书的子集。{% comment %} https://github.com/github/enterprise2/pull/24113, https://github.com/github/enterprise2/pull/23981 {% endcomment %}'
|
||||
- '发送电子邮件通知给已经从团队或组织中移除的已停用用户。{% comment %} https://github.com/github/github/pull/162971, https://github.com/github/github/pull/162742 {% endcomment %}'
|
||||
- '组织和企业之间应用 SSH 证书的方式不一致。{% comment %} https://github.com/github/github/pull/163426, https://github.com/github/github/pull/159538, https://github.com/github/authentication/issues/115 {% endcomment %}'
|
||||
- '当帐户因使用不正确的密码而受到速率限制时，可能被锁定长达 24 小时。{% comment %} https://github.com/github/github/pull/163436, https://github.com/github/github/pull/162938, https://github.com/github/github-ds/pull/51 {% endcomment %}'
|
||||
- '在具有许多引用的存储库上进行拉取请求同步可能导致工作进程队列落后。{% comment %} https://github.com/github/github/pull/163575, https://github.com/github/github/pull/163142 {% endcomment %}'
|
||||
- '在尝试访问特定页面后登录时，用户被发送到主页，而不是其预期目的地。{% comment %} https://github.com/github/github/pull/163784, https://github.com/github/github/pull/163579, https://github.com/github/github/pull/154117, https://github.com/github/ecosystem-apps/issues/1076 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '自定义防火墙规则在升级期间没有维护。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,13 @@
|
||||
date: '2020-12-17'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**低：**高 CPU 使用可能被特殊构建的 SVN 桥请求触发，导致 SVN 桥服务上的拒绝服务 (DoS)。{% comment %} https://github.com/github/slumlord/pull/1021, https://github.com/github/slumlord/pull/1017 {% endcomment %}'
|
||||
- '包已更新到最新的安全版本。{% comment %} https://github.com/github/enterprise2/pull/24352, https://github.com/github/enterprise2/pull/23866 {% endcomment %}'
|
||||
known_issues:
|
||||
- '在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可能创建第一个管理员用户。{% comment %} https://github.com/github/enterprise2/issues/1889 {% endcomment %}'
|
||||
- '在升级期间不会维护自定义防火墙规则。{% comment %} https://github.com/github/enterprise2/issues/2823 {% endcomment %}'
|
||||
- 'Git LFS 跟踪的 [通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories) 文件被错误地直接添加到存储库。{% comment %} https://github.com/github/github/issues/54684 {% endcomment %}'
|
||||
- '如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。{% comment %} https://github.com/github/github/issues/107731 {% endcomment %}'
|
||||
- '在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。{% comment %} https://github.com/github/admin-experience/issues/571 {% endcomment %}'
|
||||
- '在命令行上推送到存储库时不会报告安全警报。{% comment %} https://github.com/github/github/issues/143190 {% endcomment %}'
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,33 @@
|
||||
date: '2021-03-02'
|
||||
sections:
|
||||
security_fixes:
|
||||
- '**高：**在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，该漏洞允许已通过身份验证的实例用户通过专门制定的拉取请求和 REST API 请求获得对未经授权存储库的写入权限。攻击者需要能够创建目标存储库分支，该设置默认为组织拥有的专用存储库禁用。分支保护（如所需的拉取请求审查或状态检查）将防止未经授权的提交在未进行进一步审查或验证的情况下合并。此漏洞编号为 CVE-2021-22861。此问题通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告。'
|
||||
- '**高：**在 GitHub Enterprise Server GraphQL API 中发现了一个不适当的访问控制漏洞，该漏洞允许已通过身份验证的实例用户在未经适当授权的情况下修改拉取请求的维护员协作权限。攻击者利用此漏洞将能够访问在他们作为维护员的存储库上打开的拉取请求的头部分支。默认情况下会为组织拥有的专用存储库禁用分支，可以防止此漏洞。此外，分支保护（如所需的拉取请求审查或状态检查）将防止未经授权的提交在未进行进一步审查或验证的情况下合并。此漏洞编号为 CVE-2021-22863。此问题通过 [GitHub Bug 赏金计划](https://bounty.github.com) 报告。'
|
||||
- '**高：**在 GitHub Enterprise Server 中发现了一个远程代码执行漏洞，该漏洞在生成 GitHub Pages 站点时可能会被利用。GitHub Pages 使用的基础分析程序的用户控制配置没有受到足够的限制，因此可以在 GitHub Enterprise Server 实例上执行命令。若要利用此漏洞，攻击者需要获得在 GitHub Enterprise Server 实例上创建和生成 GitHub Pages 站点的权限。该漏洞编号为 CVE-2020-10519，通过 [GitHub Bug 赏金计划](https://bounty.github.com/) 报告。'
|
||||
- '**中：**来自 GitHub Pages 生成的 GitHub 令牌最终可能会出现在日志中。'
|
||||
- '**低：**对 SVN 桥的专门制定请求可能会在失败前触发长时间的等待，从而导致拒绝服务 (DoS)。'
|
||||
- '包已更新到最新的安全版本。'
|
||||
bugs:
|
||||
- '在某些情况下，负载均衡器运行状况检查可能导致 babld 日志全是有关代理协议的错误。'
|
||||
- '在 GitHub Enterprise 备份实用程序快照期间，信息性消息被无意中记录为错误，这导致侦听输出到 stderr 的 cron 作业在安排备份时发送不必要的电子邮件。'
|
||||
- '在还原大型备份时，与 Redis 内存耗尽相关的异常记录可能导致还原因磁盘已满而失败。'
|
||||
- '用户在编辑 wiki 页面时，如果单击“保存”按钮，可能会遇到 500 错误。'
|
||||
- '使用主题替代名称中具有多个名称的证书签名的 S/MIME 签名提交将在提交提示标记中错误地显示为“未验证”。'
|
||||
- '已暂停的用户在添加到团队时会收到电子邮件。'
|
||||
- '当存储库具有大量清单时，“见解 ->依赖项关系图”选项卡上会显示错误“已达到此存储库允许的最大清单文件数 (20)”。有关详细信息，请参阅[可视化效果限制](https://docs.github.com/en/github/managing-security-vulnerabilities/troubleshooting-the-detection-of-vulnerable-dependencies#are-there-limits-which-affect-the-dependency-graph-data)。'
|
||||
- '上传与之前许可证文件不同席位数的新许可证文件时，企业帐户的“设置”->“许可证”页面中不会正确表示席位差异。'
|
||||
- '无法成功启用或禁用企业帐户设置中的“禁止存储库管理员更改匿名 Git 读取访问权限”复选框。'
|
||||
- 'GitHub Pages 生成失败时，电子邮件通知包含了错误的支持位置链接。'
|
||||
- '在闰年，用户在星期一尝试查看贡献活动时收到 404 响应。'
|
||||
- '无法访问浏览**部分，出现 500 内部服务器错误。'
|
||||
changes:
|
||||
- '添加了对 [AWS EC2 r5b 实例类型](https://aws.amazon.com/about-aws/whats-new/2020/12/introducing-new-amazon-ec2-r5b-instances-feuring-60-gbps-of-ebbandwidth-260K-iops/)的支持。'
|
||||
- '调整后台队列优先级，以更均匀地分配作业。'
|
||||
known_issues:
|
||||
- '在新建的没有任何用户的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。'
|
||||
- '在升级期间不会维护自定义防火墙规则。'
|
||||
- '[通过 Web 界面上传](https://github.com/blog/2105-upload-files-to-your-repositories)的 Git LFS 跟踪文件被错误地直接添加到存储库。'
|
||||
- '问题若是包含同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。'
|
||||
- '对 GitHub Connect 启用“用户可以搜索 GitHub.com”后，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。'
|
||||
- '推送到命令行上的仓库时，不会报告安全警报。'
|
||||
- '当副本节点在高可用性配置下离线时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到离线节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,14 @@
|
||||
date: '2021-03-16'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 包已更新到最新的安全版本。
|
||||
bugs:
|
||||
- 从 GitHub Enterprise Server 中导入正在丢失存储库文件的存储库存档将失败并报告错误。
|
||||
known_issues:
|
||||
- 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
|
||||
- 在升级期间不会维护自定义防火墙规则。
|
||||
- "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。"
|
||||
- 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。
|
||||
- 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
|
||||
- 在命令行上推送到存储库时不会报告安全警报。
|
||||
- "当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。"
|
||||
@@ -0,0 +1,16 @@
|
||||
date: '2021-04-01'
|
||||
sections:
|
||||
security_fixes:
|
||||
- "**高：** 在 GitHub Enterprise Server 中发现了一个不适当的访问控制漏洞，该漏洞允许根据 GitHub 应用的 [Web 身份验证流](https://docs.github.com/en/developers/apps/identifying-and-authorizing-users-for-github-apps#web-application-flow) 生成的访问令牌通过 REST API 读取专用存储库元数据，而无需获取适当的权限。若要攻击这个漏洞，攻击者需要在实例上创建 GitHub 应用，并让用户通过 Web 身份验证流对应用程序进行授权。返回的专用存储库元数据将仅限于令牌标识的用户拥有的存储库。此漏洞影响 GitHub Enterprise Server 3.0.4 之前的所有版本，并已在 3.0.4、2.22.10 和 2.21.18 版本中修复。此漏洞编号为 CVE-2021-22865，并通过 [GitHub Bug 赏金计划](https://bounty.github.com/) 进行报告。"
|
||||
- 包已更新到最新的安全版本。
|
||||
bugs:
|
||||
- 服务未作为日志轮换的一部分转换到新的日志文件，导致磁盘使用量增加。
|
||||
- 内部存储库搜索结果上的标签显示为“专用”而不是“内部”。
|
||||
known_issues:
|
||||
- 在没有任何用户的新设置的 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
|
||||
- 在升级期间不会维护自定义防火墙规则。
|
||||
- "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。"
|
||||
- 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则问题无法关闭。
|
||||
- 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
|
||||
- 在命令行上推送到存储库时不会报告安全警报。
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
@@ -0,0 +1,18 @@
|
||||
date: '2021-04-14'
|
||||
sections:
|
||||
security_fixes:
|
||||
- 包已更新到最新的安全版本。
|
||||
bugs:
|
||||
- '在副本升级期间可能会出现警告消息 `jq: error (at <stdin>:0): Cannot index number with string "settings"`。'
|
||||
- 访问 `/settings/email` 页面会存储在退出登录并重新登录时可能导致错误重定向的状态。
|
||||
- 对于其通告在 `vulnerable_version_ranges` 中具有大写包名称的一些组件，未显示依赖项关系图警报。
|
||||
- 用户在配置了 LDAP 身份验证的实例上执行 git 操作时会看到 500 错误。
|
||||
- 当 ghe-migrator 遇到导入错误时，它有时会中止整个进程，但日志中没有包含足够的上下文。
|
||||
known_issues:
|
||||
- 在没有任何用户的新建 GitHub Enterprise Server 上，攻击者可以创建第一个管理员用户。
|
||||
- 在升级期间不会维护自定义防火墙规则。
|
||||
- "Git LFS 跟踪的[通过 Web 界面上传的](https://github.com/blog/2105-upload-files-to-your-repositories)文件被错误地直接添加到存储库。"
|
||||
- 如果问题包含指向同一存储库中文件路径长于 255 个字符的 blob 的永久链接，则无法关闭。
|
||||
- 在 GitHub Connect 中启用了“用户可以搜索 GitHub.com”时，专用和内部存储库中的问题不包括在 GitHub.com 搜索结果中。
|
||||
- 在命令行上推送到存储库时不会报告安全警报。
|
||||
- '当副本节点在高可用性配置中脱机时，{% data variables.product.product_name %} 仍可能将 {% data variables.product.prodname_pages %} 请求路由到脱机节点，从而减少用户的 {% data variables.product.prodname_pages %} 可用性。'
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user