You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two verbs in the API to care about, provided this doesn't change dramatically prior to release.
GET /repos/:owner/:repo/deployments
Gets the list of created deployments and their statuses.
POST /repos/:owner/:repo/deployments
Creates a deployment with an applicable payload of data (target, description, etc.)
The other parts of the API are intended for use with the third-party deployment tool, such as updating the status of a deployment as it goes through its process. That may be beyond the needful scope any hubot/etc. integration.
The text was updated successfully, but these errors were encountered:
It would be even cooler to have bespoke access to these features (following the example of the branches api). With that interface, githubot could be helpful and override the api version header for only those requests, saving people the trouble of doing it manually. If you're interested in seeing this happen, I'd encourage you to try a pull request! There should be some example code to use as a starting point, and I'm happy to answer any questions.
Reference: http://developer.github.com/changes/2014-01-09-preview-the-new-deployments-api/
Reference: http://developer.github.com/v3/repos/deployments/#preview-mode
During the preview period, a special header has to be sent along.
There are two verbs in the API to care about, provided this doesn't change dramatically prior to release.
GET /repos/:owner/:repo/deployments
Gets the list of created deployments and their statuses.
POST /repos/:owner/:repo/deployments
Creates a deployment with an applicable payload of data (target, description, etc.)
The other parts of the API are intended for use with the third-party deployment tool, such as updating the status of a deployment as it goes through its process. That may be beyond the needful scope any hubot/etc. integration.
The text was updated successfully, but these errors were encountered: