Sync changes from upstream repository

Hubot · Hubot · commit 7ab5142ed114 · 2014-11-25T19:07:51.000Z
diff --git a/content/changes/2014-11-25-the-deployments-api-is-official.md b/content/changes/2014-11-25-the-deployments-api-is-official.md
@@ -0,0 +1,37 @@
+---
+kind: change
+title: The Deployments API is official
+created_at: 2014-11-25
+author_name: atmos
+---
+
+We're happy to announce that the [Deployments API][docs] is officially part
+of GitHub API v3. We now consider it stable for production use.
+
+Thanks to everyone who provided feedback during the preview period. We got
+some great feedback, and hope this feature helps you build the tools you
+need to make GitHub the best place to ship exactly the way you want.
+
+### Preview media type no longer needed
+
+If you used the Deployments API during the preview period, you needed to
+provide a custom media type in the `Accept` header:
+
+    application/vnd.github.cannonball-preview+json
+
+Now that the preview period has ended, you no longer need to pass this custom
+media type.
+
+Instead, we [recommend][media-types] that you specify `v3` as the version in the
+`Accept` header:
+
+    application/vnd.github.v3+json
+
+### Feedback
+
+We'll never be done listening to you! As always, please don't hesitate to
+[share your feedback][feedback].
+
+[docs]: /v3/repos/deployments
+[media-types]: /v3/media
+[feedback]: https://github.com/contact?form[subject]=Deployments+API
diff --git a/content/v3/repos/deployments.md b/content/v3/repos/deployments.md
@@ -7,19 +7,6 @@ title: Deployments | GitHub API
 * TOC
 {:toc}
 
-<div class="alert">
-  <p>
-    The Deployments API is currently available for developers to preview.
-    During the preview period, the API may change without advance notice.
-    Please see the <a href="/changes/2014-01-09-preview-the-new-deployments-api/">blog post</a> for full details.
-  </p>
-
-  <p>
-    To access the API during the preview period, you must provide a custom <a href="/v3/media">media type</a> in the <code>Accept</code> header:
-    <pre>application/vnd.github.cannonball-preview+json</pre>
-  </p>
-</div>
-
 Deployments are a request for a specific ref(branch,sha,tag) to be deployed.
 GitHub then dispatches deployment events that external services can listen for
 and act on. This enables developers and organizations to build loosely-coupled
@@ -146,7 +133,7 @@ Users with `repo` or `repo_deployment` scopes can create a deployment for a give
 Name | Type | Description
 -----|------|--------------
 `ref`|`string`| **Required**. The ref to deploy. This can be a branch, tag, or sha.
-`task`|`string`| **Required**. The named task to execute. e.g. `deploy` or `deploy:migrations`. Default: `deploy`
+`task`|`string`| Optional parameter to specify a task to execute, e.g. `deploy` or `deploy:migrations`. Default: `deploy`
 `auto_merge`|`boolean`| Optional parameter to merge the default branch into the requested ref if it is behind the default branch. Default: `true`
 `required_contexts`|`Array`| Optional array of status contexts verified against commit status checks. If this parameter is omitted from the parameters then all unique contexts will be verified before a deployment is created. To bypass checking entirely pass an empty array. Defaults to all unique contexts.
 `payload`|`string` | Optional JSON payload with extra information about the deployment. Default: `""`
