|
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>2013-08-20T04:00:00Z</updated> |
| 5 | + <updated>2013-09-03T04: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,2013-09-03:/changes/2013-09-03-two-factor-authentication/</id> |
| 14 | + <title type="html">Two-Factor Authentication and the API</title> |
| 15 | + <published>2013-09-03T04:00:00Z</published> |
| 16 | + <updated>2013-09-03T04:00:00Z</updated> |
| 17 | + <author> |
| 18 | + <name>mastahyeti</name> |
| 19 | + <uri>https://github.com/technoweenie</uri> |
| 20 | + </author> |
| 21 | + <link rel="alternate" href="http://developer.github.com/changes/2013-09-03-two-factor-authentication/" /> |
| 22 | + <content type="html"><p>As <a href="https://github.com/blog/1614-two-factor-authentication">announced earlier today</a>, GitHub.com now supports two-factor |
| 23 | +authentication (2FA) for increased security. For users with this feature |
| 24 | +enabled, GitHub.com will prompt for a 2FA code in addition to a username and |
| 25 | +password during authentication. We’ve also rolled out some improvements to the |
| 26 | +API to ensure that 2FA requirements in the API are consistent with GitHub.com.</p> |
| 27 | + |
| 28 | +<h2 id="authenticating-with-the-api">Authenticating with the API</h2> |
| 29 | + |
| 30 | +<p>For users without 2FA enabled, and for applications using the <a href="/v3/oauth/#web-application-flow">OAuth web |
| 31 | +flow</a> for authentication, everything is |
| 32 | +business as usual. You’ll continue to authenticate with the API just as you |
| 33 | +always have. (That was easy.)</p> |
| 34 | + |
| 35 | +<p>If you enable 2FA <em>and</em> use Basic Authentication to access the API, we’re |
| 36 | +providing multiple options to make the flow simple and easy.</p> |
| 37 | + |
| 38 | +<h2 id="basic-authentication-and-2fa">Basic Authentication and 2FA</h2> |
| 39 | + |
| 40 | +<h3 id="personal-access-tokens">Personal Access Tokens</h3> |
| 41 | + |
| 42 | +<p>Personal access tokens provide the simplest option for using 2FA with Basic |
| 43 | +Authentication. You can create these tokens via the <a href="https://github.com/settings/applications">application settings page |
| 44 | +on GitHub.com</a>, and you can revoke |
| 45 | +them at any time. For more information about authenticating to the API with |
| 46 | +personal access tokens, be sure to check out our <a href="https://help.github.com/articles/creating-an-access-token-for-command-line-use">help article on the |
| 47 | +topic</a>.</p> |
| 48 | + |
| 49 | +<h3 id="tightly-integrated-2fa">Tightly-integrated 2FA</h3> |
| 50 | + |
| 51 | +<p>For developers wishing to integrate GitHub 2FA directly into their application, |
| 52 | +the API’s Basic Authentication now supports the <a href="/v3/auth/#working-with-two-factor-authentication">ability to send the user’s 2FA |
| 53 | +code</a>, in addition to the username and password.</p> |
| 54 | + |
| 55 | +<h2 id="were-here-to-help">We’re here to help</h2> |
| 56 | + |
| 57 | +<p>We think GitHub users are going to love the additional security provided by |
| 58 | +two-factor authentication. As always, if you have any questions or feedback, |
| 59 | +<a href="https://github.com/contact?form%5Bsubject%5D=2FA+and+the+API">let us know</a>. We’re here to help!</p></content> |
| 60 | + </entry> |
12 | 61 | <entry> |
13 | 62 | <id>tag:developer.github.com,2013-08-20:/changes/2013-08-20-search-api-improvements/</id> |
14 | 63 | <title type="html">Improvements to the Search API</title> |
@@ -283,26 +332,6 @@ but we can’t wait to see what others can do with this information.</p> |
283 | 332 | <li><strong><a href="/v3/repos/statistics/#get-the-weekly-commit-count-for-the-repo-owner-and-everyone-else">Participation</a></strong></li> |
284 | 333 | <li><strong><a href="/v3/repos/statistics/#get-the-number-of-commits-per-hour-in-each-day">Punch Card</a></strong></li> |
285 | 334 | </ul><p>Enjoy!</p></content> |
286 | | - </entry> |
287 | | - <entry> |
288 | | - <id>tag:developer.github.com,2013-04-30:/changes/2013-04-30-statuses-for-branches-and-tags/</id> |
289 | | - <title type="html">Commit Statuses Now Available for Branches and Tags</title> |
290 | | - <published>2013-04-30T04:00:00Z</published> |
291 | | - <updated>2013-04-30T04:00:00Z</updated> |
292 | | - <author> |
293 | | - <name>foca</name> |
294 | | - <uri>https://github.com/technoweenie</uri> |
295 | | - </author> |
296 | | - <link rel="alternate" href="http://developer.github.com/changes/2013-04-30-statuses-for-branches-and-tags/" /> |
297 | | - <content type="html"><p>Last week we announced <a href="https://github.com/blog/1484-check-the-status-of-your-branches">support for build statuses in the branches page</a>. |
298 | | -Now we are extending this to the API. The <a href="http://developer.github.com/v3/repos/statuses/#list-statuses-for-a-specific-ref">API endpoint for commit statuses</a> |
299 | | -has been extended to allow branch and tag names, as well as commit SHAs.</p> |
300 | | - |
301 | | -<pre class="terminal"> |
302 | | -curl https://api.github.com/repos/rails/rails/statuses/3-2-stable |
303 | | -</pre> |
304 | | - |
305 | | -<p>Enjoy.</p></content> |
306 | 335 | </entry> |
307 | 336 | <entry> |
308 | 337 | <id>tag:developer.github.com,2013-04-30:/changes/2013-04-30-improved-submodule-support-in-repository-contents-api/</id> |
@@ -343,6 +372,26 @@ curl https://api.github.com/repos/jquery/jquery/contents/test/qunit |
343 | 372 |
|
344 | 373 | <p>If you have any questions or feedback, please drop us a line at |
345 | 374 | <a href="mailto: [email protected]?subject=Submodules%20in%20Repository%20Contents%20API" >[email protected]</a >. </p ></ content> |
| 375 | + </entry> |
| 376 | + <entry> |
| 377 | + <id>tag:developer.github.com,2013-04-30:/changes/2013-04-30-statuses-for-branches-and-tags/</id> |
| 378 | + <title type="html">Commit Statuses Now Available for Branches and Tags</title> |
| 379 | + <published>2013-04-30T04:00:00Z</published> |
| 380 | + <updated>2013-04-30T04:00:00Z</updated> |
| 381 | + <author> |
| 382 | + <name>foca</name> |
| 383 | + <uri>https://github.com/technoweenie</uri> |
| 384 | + </author> |
| 385 | + <link rel="alternate" href="http://developer.github.com/changes/2013-04-30-statuses-for-branches-and-tags/" /> |
| 386 | + <content type="html"><p>Last week we announced <a href="https://github.com/blog/1484-check-the-status-of-your-branches">support for build statuses in the branches page</a>. |
| 387 | +Now we are extending this to the API. The <a href="http://developer.github.com/v3/repos/statuses/#list-statuses-for-a-specific-ref">API endpoint for commit statuses</a> |
| 388 | +has been extended to allow branch and tag names, as well as commit SHAs.</p> |
| 389 | + |
| 390 | +<pre class="terminal"> |
| 391 | +curl https://api.github.com/repos/rails/rails/statuses/3-2-stable |
| 392 | +</pre> |
| 393 | + |
| 394 | +<p>Enjoy.</p></content> |
346 | 395 | </entry> |
347 | 396 | <entry> |
348 | 397 | <id>tag:developer.github.com,2013-04-25:/changes/2013-04-25-deprecating-merge-commit-sha/</id> |
@@ -982,52 +1031,4 @@ something unique to your application.</p> |
982 | 1031 | <p>If you have any questions or feedback, please drop us a line at |
983 | 1032 | <a href="mailto: [email protected]?subject=API%20Rate%20limit" >[email protected]</a >. </p ></ content> |
984 | 1033 | </entry> |
985 | | - <entry> |
986 | | - <id>tag:developer.github.com,2012-09-28:/changes/2012-9-28-auto-init-for-repositories/</id> |
987 | | - <title type="html">Initialize a repository when creating</title> |
988 | | - <published>2012-09-28T04:00:00Z</published> |
989 | | - <updated>2012-09-28T04:00:00Z</updated> |
990 | | - <author> |
991 | | - <name>pengwynn</name> |
992 | | - <uri>https://github.com/technoweenie</uri> |
993 | | - </author> |
994 | | - <link rel="alternate" href="http://developer.github.com/changes/2012-9-28-auto-init-for-repositories/" /> |
995 | | - <content type="html"><p>Today we’ve made it easier to add commits to a repository via the GitHub API. |
996 | | -Until now, you could <a href="/v3/repos/#create">create a repository</a>, but you would |
997 | | -need to initialize it locally via your Git client before adding any commits via |
998 | | -the API.</p> |
999 | | - |
1000 | | -<p>Now you can optionally init a repository when it’s created by sending <code>true</code> |
1001 | | -for the <code>auto_init</code> parameter:</p> |
1002 | | - |
1003 | | -<pre class="terminal"> |
1004 | | -curl -i -u pengwynn \ |
1005 | | - -d '{"name": "create-repo-test", "auto_init": true}' \ |
1006 | | - https://api.github.com/user/repos |
1007 | | -</pre> |
1008 | | - |
1009 | | -<p>The resulting repository will have a README stub and an initial commit.</p> |
1010 | | - |
1011 | | -<p><img src="/images/posts/create-repo-init.png" alt="create repo screenshot"></p> |
1012 | | - |
1013 | | -<h3 id="gitignore-templates">.gitignore templates</h3> |
1014 | | - |
1015 | | -<p>Along with this change, you can set up your <code>.gitignore</code> template by passing |
1016 | | -the basename of any template in the <a href="https://github.com/github/gitignore">GitHub gitignore templates |
1017 | | -project</a>.</p> |
1018 | | - |
1019 | | -<pre class="terminal"> |
1020 | | -curl -i -u pengwynn \ |
1021 | | - -d '{"name": "create-repo-test", "auto_init": true, \ |
1022 | | - "gitignore_template": "Haskell"}' \ |
1023 | | - https://api.github.com/user/repos |
1024 | | -</pre> |
1025 | | - |
1026 | | -<p>As the <a href="/v3/repos/#create">docs point out</a>, the <code>gitignore_template</code> parameter |
1027 | | -is ignored if <code>auto_init</code> is not present and <code>true</code>.</p> |
1028 | | - |
1029 | | -<p>If you have any questions or feedback, drop us a line at |
1030 | | -<a href="https://github.com/c" >https://github.com/contact </a >, <a href="mailto: [email protected]" >[email protected]</a >, or |
1031 | | -<a href="https://twitter.com/githubapi">@GitHubAPI</a>.</p></content> |
1032 | | - </entry> |
1033 | 1034 | </feed> |
0 commit comments