{"meta":{"title":"Points de terminaison d’API REST pour les déploiements","intro":"Utilisez l’API REST pour créer et supprimer des déploiement et des environnements de déploiement.","product":"API REST","breadcrumbs":[{"href":"/fr/enterprise-server@3.18/rest","title":"API REST"},{"href":"/fr/enterprise-server@3.18/rest/deployments","title":"Déploiements"},{"href":"/fr/enterprise-server@3.18/rest/deployments/deployments","title":"Déploiements"}],"documentType":"article"},"body":"# Points de terminaison d’API REST pour les déploiements\n\nUtilisez l’API REST pour créer et supprimer des déploiement et des environnements de déploiement.\n\n## À propos des déploiements\n\nLes déploiements sont des demandes de déploiement d’une référence spécifique (branche, SHA, étiquette). GitHub distribue un événement [`deployment`](/fr/enterprise-server@3.18/webhooks/webhook-events-and-payloads#deployment) que les services externes peuvent écouter et agir quand de nouveaux déploiements sont créés. Les déploiements permettent aux développeurs et aux organisations de créer des outils faiblement couplés autour des déploiements, sans avoir à se soucier des détails pour implémenter la fourniture de différents types d’applications (par exemple, web, natif).\n\nLes états de déploiement permettent aux services externes de marquer les déploiements avec un état `error`, `failure`, `pending`, `in_progress`, `queued` ou `success` que les systèmes qui écoutent les événements [`deployment_status`](/fr/enterprise-server@3.18/webhooks/webhook-events-and-payloads#deployment_status) peuvent consommer.\n\nLes états de déploiement peuvent également comprendre des éléments facultatifs `description` et `log_url`, qui sont fortement recommandés, car ils rendent les états de déploiement plus utiles.\n`log_url` est l’URL complète du résultat du déploiement, et `description` est un bref aperçu des événements liés au déploiement.\n\nGitHub répartit les événements `deployment` et `deployment_status` lorsque de nouveaux déploiements et états de déploiement sont créés. Ces événements permettent aux intégrations tierces de recevoir des demandes de déploiement et d’y répondre, ainsi que de mettre à jour l’état d’un déploiement au fur et à mesure de sa progression.\n\nVoici ci-dessous un diagramme de séquence simple pour comprendre le fonctionnement de ces interactions.\n\n```text\n+---------+             +--------+            +-----------+        +-------------+\n| Tooling |             | GitHub |            | 3rd Party |        | Your Server |\n+---------+             +--------+            +-----------+        +-------------+\n     |                      |                       |                     |\n     |  Create Deployment   |                       |                     |\n     |--------------------->|                       |                     |\n     |                      |                       |                     |\n     |  Deployment Created  |                       |                     |\n     |<---------------------|                       |                     |\n     |                      |                       |                     |\n     |                      |   Deployment Event    |                     |\n     |                      |---------------------->|                     |\n     |                      |                       |     SSH+Deploys     |\n     |                      |                       |-------------------->|\n     |                      |                       |                     |\n     |                      |   Deployment Status   |                     |\n     |                      |<----------------------|                     |\n     |                      |                       |                     |\n     |                      |                       |   Deploy Completed  |\n     |                      |                       |<--------------------|\n     |                      |                       |                     |\n     |                      |   Deployment Status   |                     |\n     |                      |<----------------------|                     |\n     |                      |                       |                     |\n```\n\nN’oubliez pas que GitHub n’accède jamais réellement à vos serveurs. Votre intégration tierce doit interagir avec les événements de déploiement. Plusieurs systèmes peuvent surveiller les événements de déploiement, et il revient à chaque système de décider s'il doit pousser le code sur vos serveurs, compiler le code natif, etc.\n\nNotez que la `repo_deployment`[portée OAuth](/fr/enterprise-server@3.18/apps/oauth-apps/building-oauth-apps/scopes-for-oauth-apps) accorde un accès ciblé aux déploiements et aux états de déploiement **sans** accorder l’accès au code du dépôt, tandis que les portées `public_repo` et `repo` accordent également une autorisation sur le code.\n\n### Déploiements inactifs\n\nQuand vous définissez l’état d’un déploiement sur `success`, tous les déploiements d’environnement précédents non temporaires et hors production dans le même dépôt avec le même nom d’environnement deviennent `inactive`. Pour éviter cela, vous pouvez définir `auto_inactive` sur `false` pendant la création de l’état de déploiement.\n\nVous pouvez indiquer qu’un environnement temporaire n’existe plus en définissant son `state` sur `inactive`. Définir `state` sur `inactive` affiche le déploiement comme `destroyed` dans GitHub et supprime l’accès à celui-ci.\n\n> \\[!NOTE]\n> Most endpoints use `Authorization: Bearer <YOUR-TOKEN>` and `Accept: application/vnd.github+json` headers, plus `X-GitHub-Api-Version: 2022-11-28`. Curl examples below omit these standard headers for brevity.\n\n## List deployments\n\n```\nGET /repos/{owner}/{repo}/deployments\n```\n\nSimple filtering of deployments is available via query parameters:\n\n### Parameters\n\n#### Headers\n\n* **`accept`** (string)\n  Setting to `application/vnd.github+json` is recommended.\n\n#### Path and query parameters\n\n* **`owner`** (string) (required)\n  The account owner of the repository. The name is not case sensitive.\n\n* **`repo`** (string) (required)\n  The name of the repository without the .git extension. The name is not case sensitive.\n\n* **`sha`** (string)\n  The SHA recorded at creation time.\n  Default: `none`\n\n* **`ref`** (string)\n  The name of the ref. This can be a branch, tag, or SHA.\n  Default: `none`\n\n* **`task`** (string)\n  The name of the task for the deployment (e.g., deploy or deploy:migrations).\n  Default: `none`\n\n* **`environment`** (string,null)\n  The name of the environment that was deployed to (e.g., staging or production).\n  Default: `none`\n\n* **`per_page`** (integer)\n  The number of results per page (max 100). For more information, see \"Using pagination in the REST API.\"\n  Default: `30`\n\n* **`page`** (integer)\n  The page number of the results to fetch. For more information, see \"Using pagination in the REST API.\"\n  Default: `1`\n\n### HTTP response status codes\n\n* **200** - OK\n\n### Code examples\n\n#### Example\n\n**Request:**\n\n```curl\ncurl -L \\\n  -X GET \\\n  http(s)://HOSTNAME/api/v3/repos/OWNER/REPO/deployments\n```\n\n**Response schema (Status: 200):**\n\nArray of `Deployment`:\n\n* `url`: required, string, format: uri\n* `id`: required, integer, format: int64\n* `node_id`: required, string\n* `sha`: required, string\n* `ref`: required, string\n* `task`: required, string\n* `payload`: required, one of:\n  * **object, additional properties allowed**\n  * **string**\n* `original_environment`: string\n* `environment`: required, string\n* `description`: required, string or null\n* `creator`: required, any of:\n  * **null**\n  * **Simple User**\n    * `name`: string or null\n    * `email`: string or null\n    * `login`: required, string\n    * `id`: required, integer, format: int64\n    * `node_id`: required, string\n    * `avatar_url`: required, string, format: uri\n    * `gravatar_id`: required, string or null\n    * `url`: required, string, format: uri\n    * `html_url`: required, string, format: uri\n    * `followers_url`: required, string, format: uri\n    * `following_url`: required, string\n    * `gists_url`: required, string\n    * `starred_url`: required, string\n    * `subscriptions_url`: required, string, format: uri\n    * `organizations_url`: required, string, format: uri\n    * `repos_url`: required, string, format: uri\n    * `events_url`: required, string\n    * `received_events_url`: required, string, format: uri\n    * `type`: required, string\n    * `site_admin`: required, boolean\n    * `starred_at`: string\n    * `user_view_type`: string\n* `created_at`: required, string, format: date-time\n* `updated_at`: required, string, format: date-time\n* `statuses_url`: required, string, format: uri\n* `repository_url`: required, string, format: uri\n* `transient_environment`: boolean\n* `production_environment`: boolean\n* `performed_via_github_app`: any of:\n  * **null**\n  * **GitHub app**\n    * `id`: required, integer\n    * `slug`: string\n    * `node_id`: required, string\n    * `client_id`: string\n    * `owner`: required, one of:\n      * **Simple User** (see above)\n      * **Enterprise**\n        * `description`: string or null\n        * `html_url`: required, string, format: uri\n        * `website_url`: string or null, format: uri\n        * `id`: required, integer\n        * `node_id`: required, string\n        * `name`: required, string\n        * `slug`: required, string\n        * `created_at`: required, string or null, format: date-time\n        * `updated_at`: required, string or null, format: date-time\n        * `avatar_url`: required, string, format: uri\n    * `name`: required, string\n    * `description`: required, string or null\n    * `external_url`: required, string, format: uri\n    * `html_url`: required, string, format: uri\n    * `created_at`: required, string, format: date-time\n    * `updated_at`: required, string, format: date-time\n    * `permissions`: required, object, additional properties: string:\n      * `issues`: string\n      * `checks`: string\n      * `metadata`: string\n      * `contents`: string\n      * `deployments`: string\n    * `events`: required, array of string\n    * `installations_count`: integer\n\n## Create a deployment\n\n```\nPOST /repos/{owner}/{repo}/deployments\n```\n\nDeployments offer a few configurable parameters with certain defaults.\nThe ref parameter can be any named branch, tag, or SHA. At GitHub Enterprise Server we often deploy branches and verify them\nbefore we merge a pull request.\nThe environment parameter allows deployments to be issued to different runtime environments. Teams often have\nmultiple environments for verifying their applications, such as production, staging, and qa. This parameter\nmakes it easier to track which environments have requested deployments. The default environment is production.\nThe auto\\_merge parameter is used to ensure that the requested ref is not behind the repository's default branch. If\nthe ref is behind the default branch for the repository, we will attempt to merge it for you. If the merge succeeds,\nthe API will return a successful merge commit. If merge conflicts prevent the merge from succeeding, the API will\nreturn a failure response.\nBy default, commit statuses for every submitted context must be in a success\nstate. The required\\_contexts parameter allows you to specify a subset of contexts that must be success, or to\nspecify contexts that have not yet been submitted. You are not required to use commit statuses to deploy. If you do\nnot require any contexts or create any commit statuses, the deployment will always succeed.\nThe payload parameter is available for any extra information that a deployment system might need. It is a JSON text\nfield that will be passed on when a deployment event is dispatched.\nThe task parameter is used by the deployment system to allow different execution paths. In the web world this might\nbe deploy:migrations to run schema changes on the system. In the compiled world this could be a flag to compile an\napplication with debugging enabled.\nMerged branch response:\nYou will see this response when GitHub automatically merges the base branch into the topic branch instead of creating\na deployment. This auto-merge happens when:\n\nAuto-merge option is enabled in the repository\nTopic branch does not include the latest changes on the base branch, which is master in the response example\nThere are no merge conflicts\n\nIf there are no new commits in the base branch, a new request to create a deployment should give a successful\nresponse.\nMerge conflict response:\nThis error happens when the auto\\_merge option is enabled and when the default branch (in this case master), can't\nbe merged into the branch that's being deployed (in this case topic-branch), due to merge conflicts.\nFailed commit status checks:\nThis error happens when the required\\_contexts parameter indicates that one or more contexts need to have a success\nstatus for the commit to be deployed, but one or more of the required contexts do not have a state of success.\nOAuth app tokens and personal access tokens (classic) need the repo or repo\\_deployment scope to use this endpoint.\n\n### Parameters\n\n#### Headers\n\n* **`accept`** (string)\n  Setting to `application/vnd.github+json` is recommended.\n\n#### Path and query parameters\n\n* **`owner`** (string) (required)\n  The account owner of the repository. The name is not case sensitive.\n\n* **`repo`** (string) (required)\n  The name of the repository without the .git extension. The name is not case sensitive.\n\n#### Body parameters\n\n* **`ref`** (string) (required)\n  The ref to deploy. This can be a branch, tag, or SHA.\n\n* **`task`** (string)\n  Specifies a task to execute (e.g., deploy or deploy:migrations).\n  Default: `deploy`\n\n* **`auto_merge`** (boolean)\n  Attempts to automatically merge the default branch into the requested ref, if it's behind the default branch.\n  Default: `true`\n\n* **`required_contexts`** (array of strings)\n  The status 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.\n\n* **`payload`** (object or string)\n  JSON payload with extra information about the deployment.\n\n* **`environment`** (string)\n  Name for the target deployment environment (e.g., production, staging, qa).\n  Default: `production`\n\n* **`description`** (string or null)\n  Short description of the deployment.\n  Default: \\`\\`\n\n* **`transient_environment`** (boolean)\n  Specifies if the given environment is specific to the deployment and will no longer exist at some point in the future. Default: false\n  Default: `false`\n\n* **`production_environment`** (boolean)\n  Specifies if the given environment is one that end-users directly interact with. Default: true when environment is production and false otherwise.\n\n### HTTP response status codes\n\n* **201** - Created\n\n* **202** - Merged branch response\n\n* **409** - Conflict when there is a merge conflict or the commit's status checks failed\n\n* **422** - Validation failed, or the endpoint has been spammed.\n\n### Code examples\n\n#### Simple example\n\n**Request:**\n\n```curl\ncurl -L \\\n  -X POST \\\n  http(s)://HOSTNAME/api/v3/repos/OWNER/REPO/deployments \\\n  -d '{\n  \"ref\": \"topic-branch\",\n  \"payload\": \"{ \\\"deploy\\\": \\\"migrate\\\" }\",\n  \"description\": \"Deploy request from hubot\"\n}'\n```\n\n**Response schema (Status: 201):**\n\n* `url`: required, string, format: uri\n* `id`: required, integer, format: int64\n* `node_id`: required, string\n* `sha`: required, string\n* `ref`: required, string\n* `task`: required, string\n* `payload`: required, one of:\n  * **object, additional properties allowed**\n  * **string**\n* `original_environment`: string\n* `environment`: required, string\n* `description`: required, string or null\n* `creator`: required, any of:\n  * **null**\n  * **Simple User**\n    * `name`: string or null\n    * `email`: string or null\n    * `login`: required, string\n    * `id`: required, integer, format: int64\n    * `node_id`: required, string\n    * `avatar_url`: required, string, format: uri\n    * `gravatar_id`: required, string or null\n    * `url`: required, string, format: uri\n    * `html_url`: required, string, format: uri\n    * `followers_url`: required, string, format: uri\n    * `following_url`: required, string\n    * `gists_url`: required, string\n    * `starred_url`: required, string\n    * `subscriptions_url`: required, string, format: uri\n    * `organizations_url`: required, string, format: uri\n    * `repos_url`: required, string, format: uri\n    * `events_url`: required, string\n    * `received_events_url`: required, string, format: uri\n    * `type`: required, string\n    * `site_admin`: required, boolean\n    * `starred_at`: string\n    * `user_view_type`: string\n* `created_at`: required, string, format: date-time\n* `updated_at`: required, string, format: date-time\n* `statuses_url`: required, string, format: uri\n* `repository_url`: required, string, format: uri\n* `transient_environment`: boolean\n* `production_environment`: boolean\n* `performed_via_github_app`: any of:\n  * **null**\n  * **GitHub app**\n    * `id`: required, integer\n    * `slug`: string\n    * `node_id`: required, string\n    * `client_id`: string\n    * `owner`: required, one of:\n      * **Simple User** (see above)\n      * **Enterprise**\n        * `description`: string or null\n        * `html_url`: required, string, format: uri\n        * `website_url`: string or null, format: uri\n        * `id`: required, integer\n        * `node_id`: required, string\n        * `name`: required, string\n        * `slug`: required, string\n        * `created_at`: required, string or null, format: date-time\n        * `updated_at`: required, string or null, format: date-time\n        * `avatar_url`: required, string, format: uri\n    * `name`: required, string\n    * `description`: required, string or null\n    * `external_url`: required, string, format: uri\n    * `html_url`: required, string, format: uri\n    * `created_at`: required, string, format: date-time\n    * `updated_at`: required, string, format: date-time\n    * `permissions`: required, object, additional properties: string:\n      * `issues`: string\n      * `checks`: string\n      * `metadata`: string\n      * `contents`: string\n      * `deployments`: string\n    * `events`: required, array of string\n    * `installations_count`: integer\n\n## Get a deployment\n\n```\nGET /repos/{owner}/{repo}/deployments/{deployment_id}\n```\n\n### Parameters\n\n#### Headers\n\n* **`accept`** (string)\n  Setting to `application/vnd.github+json` is recommended.\n\n#### Path and query parameters\n\n* **`owner`** (string) (required)\n  The account owner of the repository. The name is not case sensitive.\n\n* **`repo`** (string) (required)\n  The name of the repository without the .git extension. The name is not case sensitive.\n\n* **`deployment_id`** (integer) (required)\n  deployment\\_id parameter\n\n### HTTP response status codes\n\n* **200** - OK\n\n* **404** - Resource not found\n\n### Code examples\n\n#### Example\n\n**Request:**\n\n```curl\ncurl -L \\\n  -X GET \\\n  http(s)://HOSTNAME/api/v3/repos/OWNER/REPO/deployments/DEPLOYMENT_ID\n```\n\n**Response schema (Status: 200):**\n\nSame response schema as [Create a deployment](#create-a-deployment).\n\n## Delete a deployment\n\n```\nDELETE /repos/{owner}/{repo}/deployments/{deployment_id}\n```\n\nIf 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.\nTo set a deployment as inactive, you must:\n\nCreate a new deployment that is active so that the system has a record of the current state, then delete the previously active deployment.\nMark the active deployment as inactive by adding any non-successful deployment status.\n\nFor more information, see \"Create a deployment\" and \"Create a deployment status.\"\nOAuth app tokens and personal access tokens (classic) need the repo or repo\\_deployment scope to use this endpoint.\n\n### Parameters\n\n#### Headers\n\n* **`accept`** (string)\n  Setting to `application/vnd.github+json` is recommended.\n\n#### Path and query parameters\n\n* **`owner`** (string) (required)\n  The account owner of the repository. The name is not case sensitive.\n\n* **`repo`** (string) (required)\n  The name of the repository without the .git extension. The name is not case sensitive.\n\n* **`deployment_id`** (integer) (required)\n  deployment\\_id parameter\n\n### HTTP response status codes\n\n* **204** - No Content\n\n* **404** - Resource not found\n\n* **422** - Validation failed, or the endpoint has been spammed.\n\n### Code examples\n\n#### Example\n\n**Request:**\n\n```curl\ncurl -L \\\n  -X DELETE \\\n  http(s)://HOSTNAME/api/v3/repos/OWNER/REPO/deployments/DEPLOYMENT_ID\n```\n\n**Response schema (Status: 204):**"}