|
2 | 2 | <feedxmlns="http://www.w3.org/2005/Atom"> |
3 | 3 | <id>http://developer.github.com/</id> |
4 | 4 | <title>GitHub API Changes</title> |
5 | | - <updated>2014-07-07T00:00:00Z</updated> |
| 5 | + <updated>2014-07-09T00:00:00Z</updated> |
6 | 6 | <linkrel="alternate"href="http://developer.github.com/" /> |
7 | 7 | <linkrel="self"href="http://developer.github.com/changes.atom" /> |
8 | 8 | <author> |
9 | 9 | <name>technoweenie</name> |
10 | 10 | <uri>https://github.com/technoweenie</uri> |
11 | 11 | </author> |
| 12 | + <entry> |
| 13 | + <id>tag:developer.github.com,2014-07-09:/changes/2014-07-09-status-contexts-are-official/</id> |
| 14 | + <titletype="html">The combined status API is official</title> |
| 15 | + <published>2014-07-09T00:00:00Z</published> |
| 16 | + <updated>2014-07-09T00:00:00Z</updated> |
| 17 | + <author> |
| 18 | + <name>bhuga</name> |
| 19 | + <uri>https://github.com/technoweenie</uri> |
| 20 | + </author> |
| 21 | + <linkrel="alternate"href="http://developer.github.com/changes/2014-07-09-status-contexts-are-official/" /> |
| 22 | + <contenttype="html"><p>We’re happy to announce that the<a href="/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref">Combined Status API</a> is officially part |
| 23 | +of the GitHub API v3. We now consider it stable for production use.</p> |
| 24 | + |
| 25 | +<p>Thanks to everyone who provided feedback during the comment period. We got |
| 26 | +some great feedback, and hope this feature helps you build the tools you |
| 27 | +need to make GitHub the best place to ship exactly the way you want.</p> |
| 28 | + |
| 29 | +<h3 id="preview-media-type-no-longer-needed">Preview media type no longer needed</h3> |
| 30 | + |
| 31 | +<p>If you used the Combined Status API during the preview period, you needed to |
| 32 | +provide a custom media type in the<code>Accept</code> header:</p> |
| 33 | + |
| 34 | +<pre><code>application/vnd.github.she-hulk-preview+json |
| 35 | +</code></pre> |
| 36 | + |
| 37 | +<p>Now that the preview period has ended, you no longer need to pass this custom |
| 38 | +media type.</p> |
| 39 | + |
| 40 | +<p>Instead, we<a href="/v3/media">recommend</a> that you specify<code>v3</code> as the version in the |
| 41 | +<code>Accept</code> header:</p> |
| 42 | + |
| 43 | +<pre><code>application/vnd.github.v3+json |
| 44 | +</code></pre> |
| 45 | + |
| 46 | +<h3 id="feedback">Feedback</h3> |
| 47 | + |
| 48 | +<p>We’ll never be done listening to you! As always, please don’t hestitate to |
| 49 | +<a href="https://github.com/contact?form%5Bsubject%5D=Combined+Status+API">share your feedback</a>.</p> |
| 50 | + |
| 51 | +</content> |
| 52 | + </entry> |
12 | 53 | <entry> |
13 | 54 | <id>tag:developer.github.com,2014-07-07:/changes/2014-07-07-example-webhook-payloads/</id> |
14 | 55 | <titletype="html">New example webhook payloads</title> |
@@ -951,29 +992,6 @@ repository contents:</p> |
951 | 992 |
|
952 | 993 | <p>As always, if you have any questions or feedback,<a href="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes">get in touch</a>.</p> |
953 | 994 |
|
954 | | -</content> |
955 | | - </entry> |
956 | | - <entry> |
957 | | - <id>tag:developer.github.com,2014-02-10:/changes/2014-2-10-ping-event-for-webhooks/</id> |
958 | | - <titletype="html">Ping Event for Webhooks</title> |
959 | | - <published>2014-02-10T00:00:00Z</published> |
960 | | - <updated>2014-02-10T00:00:00Z</updated> |
961 | | - <author> |
962 | | - <name>kdaigle</name> |
963 | | - <uri>https://github.com/technoweenie</uri> |
964 | | - </author> |
965 | | - <linkrel="alternate"href="http://developer.github.com/changes/2014-2-10-ping-event-for-webhooks/" /> |
966 | | - <contenttype="html"><p>With the release of our<a href="https://github.com/blog/1778-webhooks-level-up">new webhook UI</a>, we included a new |
967 | | -<a href="/webhooks/#ping-event">ping event</a> that webhooks will receive. When you |
968 | | -create a new webhook, we will send this event as an initial test of the webhook.</p> |
969 | | - |
970 | | -<p>The ping is only informational, doesn’t need to be responded to in a specific way, |
971 | | -and nothing bad will happen if you respond with an error. It’s just a quick |
972 | | -“hello world” to let you know you set everything up correctly.</p> |
973 | | - |
974 | | -<p>We also added a<a href="/v3/repos/hooks/#ping-a-hook">ping endpoint</a> to the hooks API. |
975 | | -By using ping instead of<a href="/v3/repos/hooks/#test-a-push-hook">test</a>, you can ensure |
976 | | -you won’t be limited by the<code>push</code> event requirement that the test endpoint has.</p> |
977 | 995 | </content> |
978 | 996 | </entry> |
979 | 997 | </feed> |