Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Users with pull access can view deployment statuses for a deployment:
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
deployment_id parameter
Response
The status of a deployment.
Example:https://api.github.com/repos/octocat/example/deployments/42/statuses/1
Example:1
Example:MDE2OkRlcGxveW1lbnRTdGF0dXMx
The state of the status.
Allowed values:errorfailureinactivependingsuccessqueuedin_progress
Example:success
Simple User
A short description of the status.
Default:
<= 140 characters
Example:Deployment finished successfully.
The environment of the deployment that the status is for.
Default:
Example:production
Deprecated: the URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
Example:2012-07-20T01:19:13Z
Example:2012-07-20T01:19:13Z
Example:https://api.github.com/repos/octocat/example/deployments/42
Example:https://api.github.com/repos/octocat/example
The URL for accessing your environment.
Default:
Example:https://staging.example.com/
The URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Users with push
access can create deployment statuses for a given deployment.
GitHub Apps require read & write
access to “Deployments” and read-only
access to “Repo contents” (for private repos). OAuth Apps require the repo_deployment
scope.
deployment_id parameter
The state of the status. Can be one of error
, failure
, inactive
, in_progress
, queued
, pending
, or success
. Note: To use the inactive
state, you must provide the application/vnd.github.ant-man-preview+json
custom media type. When you set a transient deployment to inactive
, the deployment will be shown as destroyed
in GitHub.
Allowed values:errorfailureinactivein_progressqueuedpendingsuccess
The target URL to associate with this status. This URL should contain output to keep the user updated while the task is running or serve as historical information for what happened in the deployment. Note: It’s recommended to use the log_url
parameter, which replaces target_url
.
Default:
The full URL of the deployment’s output. This parameter replaces target_url
. We will continue to accept target_url
to support legacy uses, but we recommend replacing target_url
with log_url
. Setting log_url
will automatically set target_url
to the same value. Default: ""
Note: This parameter requires you to use the application/vnd.github.ant-man-preview+json
custom media type.
Default:
A short description of the status. The maximum description length is 140 characters.
Default:
Name for the target deployment environment, which can be changed when setting a deploy status. For example, production
, staging
, or qa
.
Allowed values:productionstagingqa
Sets the URL for accessing your environment. Default: ""
Note: This parameter requires you to use the application/vnd.github.ant-man-preview+json
custom media type.
Default:
Adds a new inactive
status to all prior non-transient, non-production environment deployments with the same repository and environment
name as the created status’s deployment. An inactive
status is only added to deployments that had a success
state. Default: true
Note: This parameter requires you to use the application/vnd.github.ant-man-preview+json
custom media type.
Response
The status of a deployment.
Example:https://api.github.com/repos/octocat/example/deployments/42/statuses/1
Example:1
Example:MDE2OkRlcGxveW1lbnRTdGF0dXMx
The state of the status.
Allowed values:errorfailureinactivependingsuccessqueuedin_progress
Example:success
Simple User
A short description of the status.
Default:
<= 140 characters
Example:Deployment finished successfully.
The environment of the deployment that the status is for.
Default:
Example:production
Deprecated: the URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
Example:2012-07-20T01:19:13Z
Example:2012-07-20T01:19:13Z
Example:https://api.github.com/repos/octocat/example/deployments/42
Example:https://api.github.com/repos/octocat/example
The URL for accessing your environment.
Default:
Example:https://staging.example.com/
The URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
Users with pull access can view a deployment status for a deployment:
deployment_id parameter
Response
The status of a deployment.
Example:https://api.github.com/repos/octocat/example/deployments/42/statuses/1
Example:1
Example:MDE2OkRlcGxveW1lbnRTdGF0dXMx
The state of the status.
Allowed values:errorfailureinactivependingsuccessqueuedin_progress
Example:success
Simple User
A short description of the status.
Default:
<= 140 characters
Example:Deployment finished successfully.
The environment of the deployment that the status is for.
Default:
Example:production
Deprecated: the URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
Example:2012-07-20T01:19:13Z
Example:2012-07-20T01:19:13Z
Example:https://api.github.com/repos/octocat/example/deployments/42
Example:https://api.github.com/repos/octocat/example
The URL for accessing your environment.
Default:
Example:https://staging.example.com/
The URL to associate with this status.
Default:
Example:https://example.com/deployment/42/output
GitHub apps are a new way to extend GitHub. They can be installed directly on organizations and user accounts and granted access to specific repositories. They come with granular permissions and built-in webhooks. GitHub apps are first class actors within GitHub.
You can use this endpoint to trigger a webhook event called repository_dispatch
when you want activity that happens outside of GitHub Enterprise Server to trigger a GitHub Actions workflow or GitHub App webhook. You must configure your GitHub Actions workflow or GitHub App to run when the repository_dispatch
event occurs. For an example repository_dispatch
webhook payload, see “RepositoryDispatchEvent.”
The client_payload
parameter is available for any extra information that your workflow might need. This parameter is a JSON payload that will be passed on when the webhook event is dispatched. For example, the client_payload
can include a message that a user would like to send using a GitHub Actions workflow. Or the client_payload
can be used as a test to debug your workflow.
This endpoint requires write access to the repository by providing either:
repo
scope. For more information, see “Creating a personal access token for the command line” in the GitHub Help documentation.metadata:read
and contents:read&write
permissions.This input example shows how you can use the client_payload
as a test to debug your workflow.
A custom webhook event name.
>= 1 characters<= 100 characters
JSON payload with extra information about the webhook event that your action or worklow may use.
Response
The sort order. Can be either newest
, oldest
, or stargazers
.
Allowed values:newestoldeststargazerswatchers
Default:newest
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
Response
Minimal Repository
Example:1296269
Example:MDEwOlJlcG9zaXRvcnkxMjk2MjY5
Example:Hello-World
Example:octocat/Hello-World
Simple User
Example:https://github.com/octocat/Hello-World
Example:This your first repo!
Example:https://api.github.com/repos/octocat/Hello-World
Example:http://api.github.com/repos/octocat/Hello-World/{archive_format}{/ref}
Example:http://api.github.com/repos/octocat/Hello-World/assignees{/user}
Example:http://api.github.com/repos/octocat/Hello-World/git/blobs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/branches{/branch}
Example:http://api.github.com/repos/octocat/Hello-World/collaborators{/collaborator}
Example:http://api.github.com/repos/octocat/Hello-World/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/compare/{base}...{head}
Example:http://api.github.com/repos/octocat/Hello-World/contents/{+path}
Example:http://api.github.com/repos/octocat/Hello-World/contributors
Example:http://api.github.com/repos/octocat/Hello-World/deployments
Example:http://api.github.com/repos/octocat/Hello-World/downloads
Example:http://api.github.com/repos/octocat/Hello-World/events
Example:http://api.github.com/repos/octocat/Hello-World/forks
Example:http://api.github.com/repos/octocat/Hello-World/git/commits{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/refs{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/git/tags{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/issues/comments{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues/events{/number}
Example:http://api.github.com/repos/octocat/Hello-World/issues{/number}
Example:http://api.github.com/repos/octocat/Hello-World/keys{/key_id}
Example:http://api.github.com/repos/octocat/Hello-World/labels{/name}
Example:http://api.github.com/repos/octocat/Hello-World/languages
Example:http://api.github.com/repos/octocat/Hello-World/merges
Example:http://api.github.com/repos/octocat/Hello-World/milestones{/number}
Example:http://api.github.com/repos/octocat/Hello-World/notifications{?since,all,participating}
Example:http://api.github.com/repos/octocat/Hello-World/pulls{/number}
Example:http://api.github.com/repos/octocat/Hello-World/releases{/id}
Example:http://api.github.com/repos/octocat/Hello-World/stargazers
Example:http://api.github.com/repos/octocat/Hello-World/statuses/{sha}
Example:http://api.github.com/repos/octocat/Hello-World/subscribers
Example:http://api.github.com/repos/octocat/Hello-World/subscription
Example:http://api.github.com/repos/octocat/Hello-World/tags
Example:http://api.github.com/repos/octocat/Hello-World/teams
Example:http://api.github.com/repos/octocat/Hello-World/git/trees{/sha}
Example:http://api.github.com/repos/octocat/Hello-World/hooks
Example:2011-01-26T19:06:43Z
Example:2011-01-26T19:01:12Z
Example:2011-01-26T19:14:43Z
A git repository
Code Of Conduct
Example:0
Example:0
Example:0