Implantações

Enterprise Cloud

Enterprise Server 3.10

Enterprise Server 3.11

Enterprise Server 3.7

Enterprise Server 3.8

Enterprise Server 3.9

Free, Pro, & Team

GitHub AE

REST API

Toda a documentação do GitHub é de código aberto. Encontrou informações erradas ou confusas? Envie uma solicitação de pull.

Ajude-nos a tornar esses documentos ótimos!

Ações

Digite um termo de pesquisa a encontrar na Documentação do GitHub.

Implantações - GitHub AE Docs

Use a API REST para criar e excluir chaves de implantação, implantações e ambientes de implantação.

Início Rápido

Comparando APIs do GitHub

Recursos na API REST

Limites de taxa

Tipos de mídia

Autenticação

Manter credenciais de API seguras

Solução de problemas

Libraries

Tipos de eventos de problemas

Tipos de eventos do GitHub

Pontos de extremidade para tokens de instalação do aplicativo GitHub

Pontos de extremidade para tokens de usuário do aplicativo GitHub

Permissões para aplicativos GitHub

Visão geral

Usando a API

Script com JavaScript

Script com Ruby

Descobrir recursos para um usuário

Entregar implantações

Representar dados como gráficos

Trabalhar com comentários

Paginação

Criar um servidor de CI

Práticas recomendadas

Introdução – banco de dados Git

Introdução – Verificações

Criptografar segredos

Guides

Artifacts

Permissões

Segredos

Grupos de runner auto-hospedados

Executores auto-hospedados

Trabalhos de fluxo de trabalho

Execução de fluxo de trabalho

Fluxos de trabalho

Eventos

Feeds

Notificações

Marcar com uma estrela

Observando

Atividade

Aplicativos GitHub

Instalações

Autorizações do OAuth

Webhooks

Aplicativos

Branches

Branches protegidos

Execuções de verificação

conjuntos de verificações

Verificações

Verificação de código

Códigos de conduta

Colaboradores

Convites

Confirmações

Comentários de commit

Status do commit

Chaves de implantação

Políticas de branch de implantação

Ambientes

Status da implantação

Emojis

Estatísticas de admin

Anúncio

Log de auditoria

Webhooks globais

Licença

Organizações

Ambientes Pre-receive

Usuários

Administração de empresas

Gists

Comentários

Blobs

Referências

Marcações

Árvores

Banco de dados do Git

Gitignore

Problemas

Responsáveis

Rótulos

Marcos

Linha do tempo

Licenças

Markdown

Estatísticas

Métricas

Migrações

Membros

Colaboradores externos

Páginas

Boards

Cartões

Colunas

Project boards

Pulls

Comentários de opiniões

Solicitações de revisão

Análises

Limite de taxa

Reações

Versões

Ativos de versões

Links automáticos

Sumário

Garfos

Git LFS

Repositórios

Search

Verificação de segredo

Teams

Comentários da discussão

Discussões

Grupos externos

Seguidores

Chaves GPG

Chaves SSH do Git

API REST

A request for a specific ref(branch,sha,tag) to be deployed

Deployment

Simple filtering of deployments is available via query parameters:

The account owner of the repository. The name is not case sensitive.

owner

The name of the repository without the <code>.git</code> extension. The name is not case sensitive.

repo

The SHA recorded at creation time.

The name of the ref. This can be a branch, tag, or SHA.

The name of the task for the deployment (e.g., <code>deploy</code> or <code>deploy:migrations</code>).

task

The name of the environment that was deployed to (e.g., <code>staging</code> or <code>production</code>).

environment

The number of results per page (max 100).

per_page

Page number of the results to fetch.

page

List deployments

The ref to deploy. This can be a branch, tag, or SHA.

Specifies a task to execute (e.g., <code>deploy</code> or <code>deploy:migrations</code>).

Attempts to automatically merge the default branch into the requested ref, if it's behind the default branch.

auto_merge

The <a href="https://docs.github.com/github-ae@latest/rest/commits/statuses">status</a> contexts to verify against commit status checks. If you omit this parameter, GitHub verifies all unique contexts before creating a deployment. To bypass checking entirely, pass an empty array. Defaults to all unique contexts.

required_contexts

JSON payload with extra information about the deployment.

payload

Name for the target deployment environment (e.g., <code>production</code>, <code>staging</code>, <code>qa</code>).

Short description of the deployment.

description

Specifies if the given environment is specific to the deployment and will no longer exist at some point in the future. Default: <code>false</code>

transient_environment

Specifies if the given environment is one that end-users directly interact with. Default: <code>true</code> when <code>environment</code> is <code>production</code> and <code>false</code> otherwise.

production_environment

Name for the target deployment environment.

Specifies if the given environment is one that end-users directly interact with. Default: false.

The ref to deploy. This can be a branch, tag, or sha.

Specifies if the given environment is will no longer exist at some point in the future. Default: false.

Deployments offer a few configurable parameters with certain defaults.
The <code>ref</code> parameter can be any named branch, tag, or SHA. At GitHub AE we often deploy branches and verify them
before we merge a pull request.
The <code>environment</code> parameter allows deployments to be issued to different runtime environments. Teams often have
multiple environments for verifying their applications, such as <code>production</code>, <code>staging</code>, and <code>qa</code>. This parameter
makes it easier to track which environments have requested deployments. The default environment is <code>production</code>.
The <code>auto_merge</code> parameter is used to ensure that the requested ref is not behind the repository's default branch. If
the ref is behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,
the API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will
return a failure response.
By default, <a href="https://docs.github.com/github-ae@latest/rest/commits/statuses">commit statuses</a> for every submitted context must be in a <code>success</code>
state. The <code>required_contexts</code> parameter allows you to specify a subset of contexts that must be <code>success</code>, or to
specify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do
not require any contexts or create any commit statuses, the deployment will always succeed.
The <code>payload</code> parameter is available for any extra information that a deployment system might need. It is a JSON text
field that will be passed on when a deployment event is dispatched.
The <code>task</code> parameter is used by the deployment system to allow different execution paths. In the web world this might
be <code>deploy:migrations</code> to run schema changes on the system. In the compiled world this could be a flag to compile an
application with debugging enabled.
Users with <code>repo</code> or <code>repo_deployment</code> scopes can create a deployment for a given ref.
Merged branch response:
You will see this response when GitHub automatically merges the base branch into the topic branch instead of creating
a deployment. This auto-merge happens when:
<ul>
<li>Auto-merge option is enabled in the repository</li>
<li>Topic branch does not include the latest changes on the base branch, which is <code>master</code> in the response example</li>
<li>There are no merge conflicts</li>
</ul>
If there are no new commits in the base branch, a new request to create a deployment should give a successful
response.
Merge conflict response:
This error happens when the <code>auto_merge</code> option is enabled and when the default branch (in this case <code>master</code>), can't
be merged into the branch that's being deployed (in this case <code>topic-branch</code>), due to merge conflicts.
Failed commit status checks:
This error happens when the <code>required_contexts</code> parameter indicates that one or more contexts need to have a <code>success</code>
status for the commit to be deployed, but one or more of the required contexts do not have a state of <code>success</code>.

Conflict when there is a merge conflict or the commit's status checks failed

Validation failed, or the endpoint has been spammed.

Create a deployment

deployment_id

Get a deployment

If the repository only has one deployment, you can delete the deployment regardless of its status. If the repository has more than one deployment, you can only delete inactive deployments. This ensures that repositories with multiple deployments will always have an active deployment. Anyone with <code>repo</code> or <code>repo_deployment</code> scopes can delete a deployment.
To set a deployment as inactive, you must:
<ul>
<li>Create a new deployment that is active so that the system has a record of the current state, then delete the previously active deployment.</li>
<li>Mark the active deployment as inactive by adding any non-successful deployment status.</li>
</ul>
For more information, see "<a href="https://docs.github.com/github-ae@latest/rest/deployments/deployments/#create-a-deployment">Create a deployment</a>" and "<a href="https://docs.github.com/github-ae@latest/rest/deployments/statuses#create-a-deployment-status">Create a deployment status</a>."