|
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-01-07T05:00:00Z</updated> |
| 5 | + <updated>2014-01-09T05: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-01-09:/changes/2014-01-09-preview-the-new-deployments-api/</id> |
| 14 | + <title type="html">Preview the New Deployments API</title> |
| 15 | + <published>2014-01-09T05:00:00Z</published> |
| 16 | + <updated>2014-01-09T05:00:00Z</updated> |
| 17 | + <author> |
| 18 | + <name>atmos</name> |
| 19 | + <uri>https://github.com/technoweenie</uri> |
| 20 | + </author> |
| 21 | + <link rel="alternate" href="http://developer.github.com/changes/2014-01-09-preview-the-new-deployments-api/" /> |
| 22 | + <content type="html"><p>Today we’re excited to announce a <a href="/v3/repos/deployments/">Deployments API</a>. We ship a lot of |
| 23 | +software at GitHub: web, mobile, and native. For the last few years, we’ve been |
| 24 | +driving our deployments from our <a href="https://speakerdeck.com/jnewland/chatops">ChatOps tooling</a> and we’ve learned a |
| 25 | +lot. The Deployments API is a generalization of the approach that we’ve been |
| 26 | +taking, and we’re really excited to see what our users and integrations start |
| 27 | +building around it.</p> |
| 28 | + |
| 29 | +<p>Deployments are a new model in the GitHub ecosystem. We don’t have any UI |
| 30 | +components currently, and deployments are intended to be used exclusively by |
| 31 | +tooling. If you’re familiar with the Status API, you know that it allows |
| 32 | +various tools to report on the status of a commit (e.g., the progress of an |
| 33 | +attempt to perform a build at a particular commit). The Status API doesn’t |
| 34 | +perform the build; it just reports the results. Much like the Status API, we |
| 35 | +won’t be doing actual deployments for you. Instead, the API provides a way for |
| 36 | +you to track the status of your deployments. We’re hoping to provide |
| 37 | +consistency across the various type of release processes, regardless of the |
| 38 | +underlying steps involved with getting your code built or shipped to your |
| 39 | +servers.</p> |
| 40 | + |
| 41 | +<h2 id="highlights">Highlights</h2> |
| 42 | + |
| 43 | +<h3 id="automatic-merging">Automatic Merging</h3> |
| 44 | + |
| 45 | +<p>The system can auto-merge the default branch for the repository if the |
| 46 | +requested deployment ref is behind the default branch. On active projects it’s |
| 47 | +easy to fall behind, so let automation watch your back.</p> |
| 48 | + |
| 49 | +<h3 id="commit-status-integration">Commit Status Integration</h3> |
| 50 | + |
| 51 | +<p>By default, the system rejects deployment requests for repositories that have |
| 52 | +commit statuses but don’t have a green build for the deployment ref. This can |
| 53 | +be bypassed, but is useful in cases where continuous integration is being used.</p> |
| 54 | + |
| 55 | +<h3 id="force-deployments">Force Deployments</h3> |
| 56 | + |
| 57 | +<p>Sometimes the world crashes down on you, and you need to just get the code out |
| 58 | +the door. Forced deployments bypass any commit status checks or ahead/behind |
| 59 | +checks in the repository.</p> |
| 60 | + |
| 61 | +<h3 id="deployment-statuses">Deployment Statuses</h3> |
| 62 | + |
| 63 | +<p>Different deployment systems can update the status of a deployment to be |
| 64 | +<code>pending</code>, <code>success</code>, <code>failure</code>, or <code>error</code>. There’s also a field for linking |
| 65 | +to deployment output.</p> |
| 66 | + |
| 67 | +<h3 id="events">Events</h3> |
| 68 | + |
| 69 | +<p>Both Deployments and Deployment Statuses trigger events on GitHub. 3rd party |
| 70 | +integrations can listen for these events via <a href="/v3/repos/hooks/">webhooks</a> and choose |
| 71 | +whether or not to actually deploy the repository that the event was created for.</p> |
| 72 | + |
| 73 | +<h2 id="preview-period">Preview Period</h2> |
| 74 | + |
| 75 | +<p>We’re making this new API available today for developers to |
| 76 | +<a href="/v3/repos/deployments/#preview-mode">preview</a>. We think developers and existing integrations are |
| 77 | +going to love it, but we want to <a href="https://github.com/contact?form%5Bsubject%5D=Deployments+API">get your feedback</a> before we declare |
| 78 | +the Deployments API “final” and “unchangeable.” We expect the preview period to |
| 79 | +last for roughly 60-90 days.</p> |
| 80 | + |
| 81 | +<p>As we discover opportunities to improve the API during the preview period, we |
| 82 | +may ship changes that break clients using the preview version of the API. We |
| 83 | +want to iterate quickly. To do so, we will announce any changes here (on the |
| 84 | +developer blog), but we will not provide any advance notice.</p> |
| 85 | + |
| 86 | +<p>At the end of preview period, the Deployments API will become an official |
| 87 | +component of GitHub API v3. At that point, the new Deployments API will be |
| 88 | +stable and suitable for production use.</p> |
| 89 | + |
| 90 | +</content> |
| 91 | + </entry> |
12 | 92 | <entry> |
13 | 93 | <id>tag:developer.github.com,2014-01-07:/changes/2014-01-07-upcoming-change-to-default-media-type/</id> |
14 | 94 | <title type="html">Upcoming Change to Default Media Type</title> |
@@ -703,6 +783,25 @@ curl -u defunkt https://api.github.com/feeds |
703 | 783 |
|
704 | 784 | <p>If you have any questions or feedback, <a href="https://github.com/contact?form%5Bsubject%5D=Feeds%20API">please drop us a line</a>.</p> |
705 | 785 |
|
| 786 | +</content> |
| 787 | + </entry> |
| 788 | + <entry> |
| 789 | + <id>tag:developer.github.com,2013-05-06:/changes/2013-05-06-create-update-delete-individual-files/</id> |
| 790 | + <title type="html">Create, update, and delete individual files</title> |
| 791 | + <published>2013-05-06T04:00:00Z</published> |
| 792 | + <updated>2013-05-06T04:00:00Z</updated> |
| 793 | + <author> |
| 794 | + <name>ymendel</name> |
| 795 | + <uri>https://github.com/technoweenie</uri> |
| 796 | + </author> |
| 797 | + <link rel="alternate" href="http://developer.github.com/changes/2013-05-06-create-update-delete-individual-files/" /> |
| 798 | + <content type="html"><p>We’re following in the footsteps of GitHub.com’s ability to <a href="https://github.com/blog/143-inline-file-editing">edit</a> and |
| 799 | +<a href="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the |
| 800 | +<a href="/v3/repos/contents/">Repository Contents API</a> will let you easily <a href="/v3/repos/contents/#create-a-file">create</a>, <a href="/v3/repos/contents/#update-a-file">update</a>, and even |
| 801 | +<a href="/v3/repos/contents/#delete-a-file">delete</a> individual files.</p> |
| 802 | + |
| 803 | +<p>Happy editing!</p> |
| 804 | + |
706 | 805 | </content> |
707 | 806 | </entry> |
708 | 807 | <entry> |
@@ -730,25 +829,6 @@ but we can’t wait to see what others can do with this information.</p> |
730 | 829 | </ul> |
731 | 830 |
|
732 | 831 | <p>Enjoy!</p> |
733 | | -</content> |
734 | | - </entry> |
735 | | - <entry> |
736 | | - <id>tag:developer.github.com,2013-05-06:/changes/2013-05-06-create-update-delete-individual-files/</id> |
737 | | - <title type="html">Create, update, and delete individual files</title> |
738 | | - <published>2013-05-06T04:00:00Z</published> |
739 | | - <updated>2013-05-06T04:00:00Z</updated> |
740 | | - <author> |
741 | | - <name>ymendel</name> |
742 | | - <uri>https://github.com/technoweenie</uri> |
743 | | - </author> |
744 | | - <link rel="alternate" href="http://developer.github.com/changes/2013-05-06-create-update-delete-individual-files/" /> |
745 | | - <content type="html"><p>We’re following in the footsteps of GitHub.com’s ability to <a href="https://github.com/blog/143-inline-file-editing">edit</a> and |
746 | | -<a href="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the |
747 | | -<a href="/v3/repos/contents/">Repository Contents API</a> will let you easily <a href="/v3/repos/contents/#create-a-file">create</a>, <a href="/v3/repos/contents/#update-a-file">update</a>, and even |
748 | | -<a href="/v3/repos/contents/#delete-a-file">delete</a> individual files.</p> |
749 | | - |
750 | | -<p>Happy editing!</p> |
751 | | - |
752 | 832 | </content> |
753 | 833 | </entry> |
754 | 834 | <entry> |
@@ -1115,36 +1195,6 @@ regardless of what you send in the <code>type</code> parameter.</ |
1115 | 1195 | </ul> |
1116 | 1196 |
|
1117 | 1197 | <p><strong>EDIT:</strong> <code>Link</code> headers are our preferred navigation technique.</p> |
1118 | | -</content> |
1119 | | - </entry> |
1120 | | - <entry> |
1121 | | - <id>tag:developer.github.com,2012-12-08:/changes/2012-12-08-finding-source-and-fork-repos-for-organizations/</id> |
1122 | | - <title type="html">Finding sources and fork repositories for organizations</title> |
1123 | | - <published>2012-12-08T05:00:00Z</published> |
1124 | | - <updated>2012-12-08T05:00:00Z</updated> |
1125 | | - <author> |
1126 | | - <name>rick</name> |
1127 | | - <uri>https://github.com/technoweenie</uri> |
1128 | | - </author> |
1129 | | - <link rel="alternate" href="http://developer.github.com/changes/2012-12-08-finding-source-and-fork-repos-for-organizations/" /> |
1130 | | - <content type="html"><p>We’ve made a couple of changes today to the Organization repositories |
1131 | | -listing to bring it a bit closer to the functionality of the GitHub.com |
1132 | | -Organization repositories tab. We now let you retrieve repositories |
1133 | | -which are forks of another repository, as well as those repositories which |
1134 | | -are sources (not forks).</p> |
1135 | | - |
1136 | | -<pre><code># Grab all fork Repositories for an Organization |
1137 | | -curl "https://api.github.com/orgs/:org/repos?type=forks" |
1138 | | - |
1139 | | -# Grab all source Repositories for an Organization |
1140 | | -curl "https://api.github.com/orgs/:org/repos?type=sources" |
1141 | | -</code></pre> |
1142 | | - |
1143 | | -<p>Check out the docs for sorting and filtering options:</p> |
1144 | | - |
1145 | | -<ul> |
1146 | | - <li><a href="/v3/repos/#list-organization-repositories">Organization Repositories</a></li> |
1147 | | -</ul> |
1148 | 1198 | </content> |
1149 | 1199 | </entry> |
1150 | 1200 | </feed> |
0 commit comments