|
2 | 2 | <feed xmlns="http://www.w3.org/2005/Atom"> |
3 | 3 | <id>http://developer.github.com/</id> |
4 | 4 | <title>GitHub API Changes</title> |
5 | | - <updated>2014-11-25T00:00:00Z</updated> |
| 5 | + <updated>2014-12-03T00:00:00Z</updated> |
6 | 6 | <link rel="alternate" href="http://developer.github.com/" /> |
7 | 7 | <link rel="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-12-03:/changes/2014-12-03-preview-the-new-organization-webhooks-api/</id> |
| 14 | + <title type="html">Preview the New Organization Webhooks API</title> |
| 15 | + <published>2014-12-03T00:00:00Z</published> |
| 16 | + <updated>2014-12-03T00:00:00Z</updated> |
| 17 | + <author> |
| 18 | + <name>jdpace</name> |
| 19 | + <uri>https://github.com/technoweenie</uri> |
| 20 | + </author> |
| 21 | + <link rel="alternate" href="http://developer.github.com/changes/2014-12-03-preview-the-new-organization-webhooks-api/" /> |
| 22 | + <content type="html"><p>Today we’re very excited <a href="https://github.com/blog/1933-introducing-organization-webhooks">to announce Organization Webhooks</a>. |
| 23 | +Organization Webhooks allow you to subscribe to events that happen across an |
| 24 | +entire organization.</p> |
| 25 | + |
| 26 | +<p>In addition to being able to subscribe to the existing repository oriented |
| 27 | +events across an organization, we’re also adding some new events which are |
| 28 | +exclusive to organization webhooks. The new <a href="/v3/activity/events/types/#repositoryevent"><code>repository</code> |
| 29 | +event</a> allows you to receive webhook payloads when a new |
| 30 | +repository is created. By subscribing to the <a href="/v3/activity/events/types/#membershipevent"><code>membership</code> |
| 31 | +event</a>, you’ll be notified whenever a user is added or |
| 32 | +removed from a team.</p> |
| 33 | + |
| 34 | +<p>We’re making this new API for Organization Webhooks available today <a href="/v3/orgs/hooks/#preview-period">for |
| 35 | +developers to preview</a>. The preview period will allow us to <a href="https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks">get |
| 36 | +your feedback</a> before declaring the Organization Webhooks API final. |
| 37 | +We expect the preview |
| 38 | +period to last for roughly 30-60 days.</p> |
| 39 | + |
| 40 | +<p>As we discover opportunities to improve the API during the preview period, we |
| 41 | +may ship changes that break clients using the preview version of the API. We |
| 42 | +want to iterate quickly. To do so, we will announce any changes here (on the |
| 43 | +developer blog), but we will not provide any advance notice.</p> |
| 44 | + |
| 45 | +<p>At the end of preview period, the Organization Webhooks API will become an |
| 46 | +official component of GitHub API v3. At that point, the new Organization |
| 47 | +Webhooks API will be stable and suitable for production use.</p> |
| 48 | + |
| 49 | +<p>We hope you’ll take it for a spin and <a href="https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks">send us your feedback</a>.</p> |
| 50 | + |
| 51 | +</content> |
| 52 | + </entry> |
12 | 53 | <entry> |
13 | 54 | <id>tag:developer.github.com,2014-11-25:/changes/2014-11-25-the-deployments-api-is-official/</id> |
14 | 55 | <title type="html">The Deployments API is official</title> |
@@ -977,60 +1018,6 @@ without granting access to your private repositories.</p> |
977 | 1018 |
|
978 | 1019 | <p>If you have any questions or feedback, please <a href="https://github.com/contact?form%5Bsubject%5D=API+create+repositories+with+public_repo+scope">get in touch</a>.</p> |
979 | 1020 |
|
980 | | -</content> |
981 | | - </entry> |
982 | | - <entry> |
983 | | - <id>tag:developer.github.com,2014-03-27:/changes/2014-03-27-combined-status-api/</id> |
984 | | - <title type="html">Preview the New Combined Status API</title> |
985 | | - <published>2014-03-27T00:00:00Z</published> |
986 | | - <updated>2014-03-27T00:00:00Z</updated> |
987 | | - <author> |
988 | | - <name>bhuga</name> |
989 | | - <uri>https://github.com/technoweenie</uri> |
990 | | - </author> |
991 | | - <link rel="alternate" href="http://developer.github.com/changes/2014-03-27-combined-status-api/" /> |
992 | | - <content type="html"><p>What does it mean for a branch to be “green?” The <a href="/v3/repos/statuses/">Status API</a> helps |
993 | | -thousands of teams answer that question. Developers use it to record the status |
994 | | -of continuous integration builds, contributor license agreements, code coverage |
995 | | -analysis, automated security testing, dependency management, and more.</p> |
996 | | - |
997 | | -<p>For many teams, a branch is considered “green” only when <em>all</em> of their various |
998 | | -status checks are successful. With the new <a href="/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref">Combined Status |
999 | | -API</a>, developers can easily fetch this single, consolidated |
1000 | | -status for any branch, commit, or tag.</p> |
1001 | | - |
1002 | | -<h3 id="status-context">Status context</h3> |
1003 | | - |
1004 | | -<p>To help multiple service providers use the Status API simultaneously, statuses |
1005 | | -now support a <code>context</code> field. This field allows a provider to distinguish its |
1006 | | -statuses from another provider’s statuses. For example, your <a href="http://jenkins-ci.org/">Jenkins</a> builds |
1007 | | -might use a context of <code>ci/jenkins</code>, while your <a href="http://brakemanscanner.org/">Brakeman</a> checks might adopt a |
1008 | | -context of <code>security/brakeman</code>.</p> |
1009 | | - |
1010 | | -<p>The new <a href="/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref">Combined Status endpoint</a> returns a single, |
1011 | | -combined state, as well as the latest status from each context. Systems that |
1012 | | -consume status updates can now get all the information they need in one place.</p> |
1013 | | - |
1014 | | -<h3 id="opt-in">Opt-in</h3> |
1015 | | - |
1016 | | -<p>The existing <a href="/v3/repos/statuses/#list-statuses-for-a-specific-ref">Status API</a> continues to work as it always has. The |
1017 | | -<code>context</code> field is entirely optional, and the <a href="https://github.com/blog/1227-commit-status-api">color of the merge button on pull |
1018 | | -requests</a> does not currently |
1019 | | -take context into account.</p> |
1020 | | - |
1021 | | -<h3 id="preview-period">Preview period</h3> |
1022 | | - |
1023 | | -<p>We’re making this new API available today for developers to |
1024 | | -<a href="/v3/repos/statuses/">preview</a>. During this period, we may change aspects of the Combined |
1025 | | -Status API from time to time. We will announce any changes here (on the |
1026 | | -developer blog), but we will not provide any advance notice.</p> |
1027 | | - |
1028 | | -<p>We expect the preview period to last 30-60 days. At the end of preview period, |
1029 | | -the Combined Status API will become an official component of GitHub API v3. At |
1030 | | -that point, this new API will be stable and suitable for production use.</p> |
1031 | | - |
1032 | | -<p>We hope you’ll <a href="/v3/repos/statuses/">try it out</a> and <a href="https://github.com/contact?form%5Bsubject%5D=Combined+Status+API">send us your feedback</a>!</p> |
1033 | | - |
1034 | 1021 | </content> |
1035 | 1022 | </entry> |
1036 | 1023 | </feed> |
0 commit comments