<?xml version="1.0" encoding="UTF-8"?>

<feed xmlns="http://www.w3.org/2005/Atom">

<id>http://developer.github.com/</id>

<title>GitHub API Changes</title>

<updated>2013-03-01T06:00:00Z</updated>

<link rel="alternate" href="http://developer.github.com/" />

<link rel="self" href="http://developer.github.com/changes.atom" />

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<entry>

<id>tag:developer.github.com,2013-03-01:/changes/2013-3-1-new-hookshot-coming/</id>

<title type="html">New Hookshot Changes</title>

<published>2013-03-01T06:00:00Z</published>

<updated>2013-03-01T06:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-3-1-new-hookshot-coming/" />

<content type="html">&lt;p&gt;We are experimenting with changes to the “Hookshot” backend that powers service

hooks. There were some significant networking changes with the new cluster,

so there are some new IP whitelist rules for hooks:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;204.232.175.64/27&lt;/li&gt;

&lt;li&gt;192.30.252.0/22&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;These are in CIDR notation. They represent a significant range of GitHub

addresses, meaning this should be the last IP change for a while. Once this

cluster is activated and we shut the other cluster down, we will be removing

the other entries.&lt;/p&gt;

&lt;p&gt;We are currently testing the new backend with all repositories in the GitHub

organization only, and expect to start testing it with user data next week.&lt;/p&gt;

&lt;p&gt;This also means we should be able to start accepting &lt;a href="https://github.com/github/github-services/pulls"&gt;GitHub Services pull

requests&lt;/a&gt; very soon :)&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-02-14:/changes/2013-2-13-sortable-stars/</id>

<title type="html">Sortable Stars in Repository Starring API</title>

<published>2013-02-14T06:00:00Z</published>

<updated>2013-02-14T06:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-2-13-sortable-stars/" />

<content type="html">&lt;p&gt;As we &lt;a href="https://github.com/blog/1410-sortable-stars"&gt;announced on the GitHub blog&lt;/a&gt;, Stars now support sorting. The

Repository Starring API now supports &lt;a href="/v3/activity/starring/#list-repositories-being-starred"&gt;two new parameters&lt;/a&gt; when listing

Stars: &lt;code&gt;sort&lt;/code&gt; and &lt;code&gt;direction&lt;/code&gt;.&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl https://api.github.com/users/defunkt/starred?sort=created&amp;amp;direction=asc

&lt;/pre&gt;

&lt;p&gt;Enjoy.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-02-13:/changes/2013-2-13-hookshot-load-balancer/</id>

<title type="html">Hookshot Load balancer</title>

<published>2013-02-13T12:00:00Z</published>

<updated>2013-02-13T12:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-2-13-hookshot-load-balancer/" />

<content type="html">&lt;p&gt;We had an issue with the Hookshot load balancer this morning, causing the

majority of hooks to flow to a single node only. This lead to massive queue

times. While fixing this, we’re putting the old Services backend in use.&lt;/p&gt;

&lt;p&gt;This means the old IPs are back in use. Use this &lt;a href="https://help.github.com/articles/what-ip-addresses-does-github-use-that-i-should-whitelist"&gt;Help guide&lt;/a&gt;

if you already removed them from your firewall.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-02-13:/changes/2013-2-13-hookshot-issues/</id>

<title type="html">Some Hookshot Issues</title>

<published>2013-02-13T11:00:00Z</published>

<updated>2013-02-13T11:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-2-13-hookshot-issues/" />

<content type="html">&lt;p&gt;We turned Hookshot (our new GitHub Services backend) on yesterday. Things have

been pretty smooth, with one issue: Hooks going to other EC2 nodes come from

the private IP addresses of our nodes in the 10.&lt;em&gt;.&lt;/em&gt;.* range.&lt;/p&gt;

&lt;p&gt;If your web hook servers are on EC2 and are missing hooks from GitHub due to

an IP restriction, we recommend the following:&lt;/p&gt;

&lt;ol&gt;

&lt;li&gt;Remove the IP white list.&lt;/li&gt;

&lt;li&gt;Fall back to HTTPS and Basic Auth to restrict pushes to authorized senders only.&lt;/li&gt;

&lt;/ol&gt;&lt;p&gt;We’re currently working on solving this problem. Hit up &lt;a href="mailto:support@github.com"&gt;support@github.com&lt;/a&gt;

if you have any questions.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-02-05:/changes/2013-2-5-changes-to-services/</id>

<title type="html">Upcoming Changes to GitHub Services</title>

<published>2013-02-05T06:00:00Z</published>

<updated>2013-02-05T06:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-2-5-changes-to-services/" />

<content type="html">&lt;p&gt;We are finishing up a new GitHub Services backend, dubbed “Hookshot”, to

increase the speed and reliability of our delivered payloads. We are doing

what we can to make this a seamless transition for everyone. However, there

are a few notable changes.&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;p&gt;There is a new &lt;a href="http://developer.github.com/v3/meta/"&gt;Meta API endpoint&lt;/a&gt;

listing the current public IPs that hooks originate from.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;We’re removing the AMQP service from GitHub. It hasn’t worked in quite some

time, and the code it uses doesn’t work in our background workers.&lt;/p&gt;

&lt;/li&gt;

&lt;li&gt;

&lt;p&gt;We’re also instituting a new guideline to improve the reliability and

maintainability of services in the future. As of today, all new services must

accept an unmodified payload over HTTP. Any service that does not will be

rejected. To see an example of an acceptable service, check out &lt;a href="https://github.com/github/github-services/blob/master/lib/services/codeclimate.rb"&gt;Code Climate&lt;/a&gt;.

Notice their service simply accepts HTTP POST from GitHub unmodified. For an

example of a service that won’t be accepted after today, check out &lt;a href="https://github.com/github/github-services/blob/master/lib/services/campfire.rb"&gt;Campfire&lt;/a&gt;. It

uses other Ruby gems and contains custom logic to transform the GitHub payload

to Campfire messages. Existing hooks will keep working (don’t worry 37signals, we

:heart: Campfire).&lt;/p&gt;

&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;We’re making these changes because we want to focus on the reliability of the

core Services backend for everyone. Maintaining custom logic and libraries for

over 100 services is taking too much of this focus away.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-01-31:/changes/2013-01-31-user-agent-will-soon-be-mandatory/</id>

<title type="html">User Agent mandatory from March 4th 2013</title>

<published>2013-01-31T06:00:00Z</published>

<updated>2013-01-31T06:00:00Z</updated>

<author>

<name>agh</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-01-31-user-agent-will-soon-be-mandatory/" />

<content type="html">&lt;p&gt;Following on from our &lt;a href="http://developer.github.com/changes/2012-10-14-rate-limit-changes/"&gt;previous post&lt;/a&gt;

about requiring requests to include a valid &lt;a href="http://en.wikipedia.org/wiki/User_agent"&gt;User Agent header&lt;/a&gt;

we will soon be changing our API servers to return HTTP 403

to any clients not providing a valid User Agent header.&lt;/p&gt;

&lt;p&gt;We will be making this change on Monday, March 4th 2013.&lt;/p&gt;

&lt;p&gt;Setting this helps us identify requests from you, and get in touch with people who are using

the API in a way which causes disruption to GitHub. Most HTTP libraries and tools like cURL

already provide a valid header for you, and allow you to customize it, so this will not require

many of our users to make any changes whatsoever.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please drop us a line at

&lt;a href="mailto:support@github.com?subject=User%20Agent%20Requirement"&gt;support@github.com&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2013-01-08:/changes/2013-01-08-new-user-scopes/</id>

<title type="html">New User scopes</title>

<published>2013-01-08T06:00:00Z</published>

<updated>2013-01-08T06:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2013-01-08-new-user-scopes/" />

<content type="html">&lt;p&gt;We’ve added a &lt;a href="http://developer.github.com/v3/oauth/#scopes"&gt;few new user scopes&lt;/a&gt; for 3rd party applications that want very

specific user functionality. The &lt;code&gt;user:email&lt;/code&gt; scope gives apps read-only access

to a user’s private email addresses. The &lt;code&gt;user:follow&lt;/code&gt; scope lets a user

follow and unfollow other users.&lt;/p&gt;

&lt;p&gt;This should help keep applications from requiring the &lt;code&gt;user&lt;/code&gt; scope, which

can be potentially dangerous.&lt;/p&gt;

&lt;p&gt;We also added a read-only endpoint to get a user’s public SSH keys.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;GET https://api.github.com/users/technoweenie/keys

&lt;/code&gt;&lt;/pre&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-12-10:/changes/2012-12-10-Diff-and-patch-media-types/</id>

<title type="html">Diff and patch media types</title>

<published>2012-12-10T06:00:00Z</published>

<updated>2012-12-10T06:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-12-10-Diff-and-patch-media-types/" />

<content type="html">&lt;p&gt;Starting today, you can get &lt;code&gt;.diff&lt;/code&gt; and &lt;code&gt;.patch&lt;/code&gt; content directly from the API for the following resources:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;&lt;a href="/v3/repos/commits/#get-a-single-commit"&gt;Commits&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="/v3/repos/commits/#compare-two-commits"&gt;Commit comparisons&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="/v3/pulls/#get-a-single-pull-request"&gt;Pull request&lt;/a&gt;&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;Simply use the same resource URL and send either &lt;code&gt;application/vnd.github.diff&lt;/code&gt; or &lt;code&gt;application/vnd.github.patch&lt;/code&gt; in the &lt;code&gt;Accept&lt;/code&gt; header:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H "Accept: application/vnd.github.diff" https://api.github.com/repos/pengwynn/dotfiles/commits/aee60a4cd56fb4c6a50e60f17096fc40c0d4d72c

diff --git a/tmux/tmux.conf.symlink b/tmux/tmux.conf.symlink

index 1f599cb..abaf625 100755

--- a/tmux/tmux.conf.symlink

+++ b/tmux/tmux.conf.symlink

@@ -111,6 +111,7 @@ set-option -g base-index 1

## enable mouse

set-option -g mouse-select-pane on

set-option -g mouse-select-window on

+set-option -g mouse-resize-pane on

set-window-option -g mode-keys vi

set-window-option -g mode-mouse on

# set-window-option -g monitor-activity off

&lt;/code&gt;&lt;/pre&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-12-09:/changes/2012-12-09-organization-repositories-results-now-paginate/</id>

<title type="html">Pagination for Organization Repository lists now paginates properly</title>

<published>2012-12-09T06:00:00Z</published>

<updated>2012-12-09T06:00:00Z</updated>

<author>

<name>rick</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-12-09-organization-repositories-results-now-paginate/" />

<content type="html">&lt;p&gt;&lt;img src="https://github-images.s3.amazonaws.com/skitch/seger-turn-the-page-20121209-154956.png" alt=""&gt;&lt;/p&gt;

&lt;p&gt;Improvements continue to the Organizations Repository listing endpoint.

Today we’re improving pagination so that it works as documented. Now

you can expect &lt;code&gt;Link&lt;/code&gt; headers to navigate through the results space,

regardless of what you send in the &lt;code&gt;type&lt;/code&gt; parameter.&lt;/p&gt;

&lt;p&gt;The docs for Organization Repositories queries are still here:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;&lt;a href="/v3/repos/#list-organization-repositories"&gt;Organization Repositories&lt;/a&gt;&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;&lt;strong&gt;EDIT:&lt;/strong&gt; &lt;code&gt;Link&lt;/code&gt; headers are our preferred navigation technique.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-12-08:/changes/2012-12-08-finding-source-and-fork-repos-for-organizations/</id>

<title type="html">Finding sources and fork repositories for organizations</title>

<published>2012-12-08T06:00:00Z</published>

<updated>2012-12-08T06:00:00Z</updated>

<author>

<name>rick</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-12-08-finding-source-and-fork-repos-for-organizations/" />

<content type="html">&lt;p&gt;We’ve made a couple of changes today to the Organization repositories

listing to bring it a bit closer to the functionality of the GitHub.com

Organization repositories tab. We now let you retrieve repositories

which are forks of another repo, as well as those repositories which

are sources (not forks).&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Grab all fork Repositories for an Organization

curl "https://api.github.com/orgs/:org/repos?type=forks"

# Grab all source Repositories for an Organization

curl "https://api.github.com/orgs/:org/repos?type=sources"

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Check out the docs for sorting and filtering options:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;&lt;a href="/v3/repos/#list-organization-repositories"&gt;Organization Repositories&lt;/a&gt;&lt;/li&gt;

&lt;/ul&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-12-06:/changes/2012-12-06-create-authorization-for-app/</id>

<title type="html">Create an OAuth authorization for an app</title>

<published>2012-12-06T06:00:00Z</published>

<updated>2012-12-06T06:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-12-06-create-authorization-for-app/" />

<content type="html">&lt;p&gt;The &lt;a href="/v3/oauth/#oauth-authorizations-api"&gt;Authorizations API&lt;/a&gt; is an easy way to create an OAuth

authorization using Basic Auth. Just POST your desired scopes and optional

note and you get a token back:&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl -u pengwynn -d '{"scopes": ["user", "gist"]}' \

https://api.github.com/authorizations

&lt;/pre&gt;

&lt;p&gt;This call creates a token for the authenticating user tied to a special “API”

OAuth application.&lt;/p&gt;

&lt;p&gt;We now support creating tokens for &lt;em&gt;your own OAuth application&lt;/em&gt; by passing your

twenty character &lt;code&gt;client_id&lt;/code&gt; and forty character &lt;code&gt;client_secret&lt;/code&gt; as found in

the settings page for your OAuth application.&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl -u pengwynn -d '{ \

"scopes": ["user", "gist"], \

"client_id": "abcdeabcdeabcdeabcdeabcde" \

"client_secret": "abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde" \

}' \ '

https://api.github.com/authorizations

&lt;/pre&gt;

&lt;p&gt;No more implementing the &lt;a href="/v3/oauth/#web-application-flow"&gt;web flow&lt;/a&gt; just to get a token tied to your

app’s rate limit.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-12-04:/changes/2012-12-04-List-comments-for-repo/</id>

<title type="html">Per-repository Review and Issue Comment&amp;nbsp;listing</title>

<published>2012-12-04T06:00:00Z</published>

<updated>2012-12-04T06:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-12-04-List-comments-for-repo/" />

<content type="html">&lt;p&gt;You’ve always been able to grab all the commit comments for an entire

repository via the API, but to get Issue comments and Pull Request Review

Comments, you could only fetch the comments for a single Issue or Pull Request.&lt;/p&gt;

&lt;p&gt;Today, we’re introducing two new methods to grab all Issue Comments and Review

Comments for a repository.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Grab all Issue Comments

curl https://api.github.com/repos/mathiasbynens/dotfiles/issues/comments

# Grab all Review Comments

curl https://api.github.com/repos/mathiasbynens/dotfiles/pulls/comments

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Check out the docs for sorting and filtering options:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;&lt;a href="/v3/issues/comments/#list-comments-in-a-repository"&gt;Issue comments&lt;/a&gt;&lt;/li&gt;

&lt;li&gt;&lt;a href="/v3/pulls/comments/#list-comments-in-a-repository"&gt;Review comments&lt;/a&gt;&lt;/li&gt;

&lt;/ul&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-11-29:/changes/2012-11-29-gitignore-templates/</id>

<title type="html">Gitignore Templates API</title>

<published>2012-11-29T06:00:00Z</published>

<updated>2012-11-29T06:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-11-29-gitignore-templates/" />

<content type="html">&lt;p&gt;We recently &lt;a href="/changes/2012-9-28-auto-init-for-repositories/"&gt;made it easy&lt;/a&gt; to initialize a repository when you create

it &lt;a href="/v3/repos/#create"&gt;via the API&lt;/a&gt;. One of the options you can pass when creating a

repository is &lt;code&gt;gitignore_template&lt;/code&gt;. This value is the name of one of the

templates from the the public &lt;a href="https://github.com/github/gitignore"&gt;GitHub .gitignore repository&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The &lt;a href="/v3/gitignore/"&gt;Gitignore Templates API&lt;/a&gt; makes it easy to list those templates:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl https://api.github.com/gitignore/templates

HTTP/1.1 200 OK

[

"Actionscript",

"Android",

"AppceleratorTitanium",

"Autotools",

"Bancha",

"C",

"C++",

...

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;If you’d like to view the source, you can also fetch a single template.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;curl -H 'Accept: application/vnd.github.raw' \

https://api.github.com/gitignore/templates/Objective-C

HTTP/1.1 200 OK

# Xcode

.DS_Store

build/

*.pbxuser

!default.pbxuser

*.mode1v3

!default.mode1v3

*.mode2v3

!default.mode2v3

*.perspectivev3

!default.perspectivev3

*.xcworkspace

!default.xcworkspace

xcuserdata

profile

*.moved-aside

DerivedData

.idea/

&lt;/code&gt;&lt;/pre&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-11-27:/changes/2012-11-27-forking-to-organizations/</id>

<title type="html">Forking to Organizations</title>

<published>2012-11-27T06:00:00Z</published>

<updated>2012-11-27T06:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-11-27-forking-to-organizations/" />

<content type="html">&lt;p&gt;We made a slight change to the way you fork a repository. By default, you

can fork my repository through an HTTP POST to the repository’s fork resource.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ curl -X POST https://api.github.com/repos/technoweenie/faraday/forks

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This repository forks to your personal account. However, there are cases when

you want to fork to one of your organizations instead. The previous method

required a &lt;code&gt;?org&lt;/code&gt; query parameter:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ curl -X POST /repos/technoweenie/faraday/forks?org=mycompany

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Query parameters on POST requests are unusual in APIs, and definitely

inconsistent with the rest of the GitHub API. You should be able to post a

JSON body like every other POST endpoint. Now, you can! Only, now we’re

calling the field &lt;code&gt;organization&lt;/code&gt;.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;$ curl /repos/technoweenie/faraday/forks?org=mycompany \

-d '{"organization": "mycompany"}'

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;Don’t worry, we are committed to maintaining the legacy behavior until the next

major change of the GitHub API.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-10-31:/changes/2012-10-31-gist-comment-uris/</id>

<title type="html">Gist comment URIs</title>

<published>2012-10-31T05:00:00Z</published>

<updated>2012-10-31T05:00:00Z</updated>

<author>

<name>pezra</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-10-31-gist-comment-uris/" />

<content type="html">&lt;p&gt;The URIs of all gist comments are changing immediately. The new URI pattern for gist comments is &lt;code&gt;/gists/{gist-id}/comments/{id}&lt;/code&gt;. (See &lt;a href="/v3/gists/comments/"&gt;gist comments section of the docs&lt;/a&gt; for more details.) This change is necessary because the auto-incremented ids of gist comments are easy to guess. This predictability allows anyone to view comments on private Gists with relative ease. Obviously, comments on private gists should be just as private as the gist itself.&lt;/p&gt;

&lt;p&gt;Adding the gist id to the URI of comments makes it impossible, in practical terms, to guess that URI because the id of private gists are very large random numbers. This is, unfortunately, a breaking change but one that cannot be avoided because of the security implications of the current URIs. We apologize for the inconvenience.&lt;/p&gt;

&lt;p&gt;We have also added a &lt;code&gt;comments_url&lt;/code&gt; member to the Gist documents. The &lt;code&gt;comments_url&lt;/code&gt; link provides access to the comments of a Gist in a way that will insulate clients from changes in the URI patterns used by the GitHub API. We are increasing our use of links in order to make changes such as this one less damaging to clients. We strongly encourage using &lt;code&gt;url&lt;/code&gt; and &lt;code&gt;*_url&lt;/code&gt; properties, where possible, rather than constructing URIs using the patterns published on this site. Doing so will result in clients that break less often.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-10-26:/changes/2012-10-26-notifications-api/</id>

<title type="html">Notifications API</title>

<published>2012-10-26T05:00:00Z</published>

<updated>2012-10-26T05:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-10-26-notifications-api/" />

<content type="html">&lt;p&gt;Now that the dust has settled around &lt;a href="https://github.com/blog/1204-notifications-stars"&gt;Notifications and Stars&lt;/a&gt;,

we’ve unleashed all that :sparkles: in a &lt;a href="http://developer.github.com/v3/activity/notifications/"&gt;brand new API&lt;/a&gt;. You can now

view and mark notifications as read.&lt;/p&gt;

&lt;h2 id="endpoint"&gt;Endpoint&lt;/h2&gt;

&lt;p&gt;The core notifications functionality is under the &lt;code&gt;/notifications&lt;/code&gt; endpoint.

You can look for unread notifications:&lt;/p&gt;

&lt;pre class="terminal"&gt;

$ curl https://api.github.com/notifications

&lt;/pre&gt;

&lt;p&gt;You can filter these notifications to a single Repository:&lt;/p&gt;

&lt;pre class="terminal"&gt;

$ curl https://api.github.com/repos/technoweenie/faraday/notifications

&lt;/pre&gt;

&lt;p&gt;You can mark them as read:&lt;/p&gt;

&lt;pre class="terminal"&gt;

# all notifications

$ curl https://api.github.com/notifications \

-X PUT -d '{"read": true}'

# notifications for a single repository

$ curl https://api.github.com/repos/technoweenie/faraday/notifications \

-X PUT -d '{"read": true}'

&lt;/pre&gt;

&lt;p&gt;You can also modify subscriptions for a Repository or a single thread.&lt;/p&gt;

&lt;pre class="terminal"&gt;

# subscription details for the thread (either an Issue or Commit)

$ curl https://api.github.com/notifications/threads/1/subscription

# subscription details for a whole Repository.

$ curl https://api.github.com/repos/technoweenie/faraday/subscription

&lt;/pre&gt;

&lt;h2 id="polling"&gt;Polling&lt;/h2&gt;

&lt;p&gt;The Notifications API is optimized for polling by the last modified time:&lt;/p&gt;

&lt;pre class="terminal"&gt;

# Add authentication to your requests

$ curl -I https://api.github.com/notifications

HTTP/1.1 200 OK

Last-Modified: Thu, 25 Oct 2012 15:16:27 GMT

X-Poll-Interval: 60

# Pass the Last-Modified header exactly

$ curl -I https://api.github.com/notifications

-H "If-Modified-Since: Thu, 25 Oct 2012 15:16:27 GMT"

HTTP/1.1 304 Not Modified

X-Poll-Interval: 60

&lt;/pre&gt;

&lt;p&gt;You can read about the API details in depth in the &lt;a href="http://developer.github.com/v3/activity/notifications/"&gt;Notifications documentation&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-10-24:/changes/2012-10-24-set-default-branch/</id>

<title type="html">Set the default branch for a repository</title>

<published>2012-10-24T05:00:00Z</published>

<updated>2012-10-24T05:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-10-24-set-default-branch/" />

<content type="html">&lt;p&gt;You can set the default branch for a repository to something other than ‘master’ from the GitHub repository admin screen:&lt;/p&gt;

&lt;p&gt;&lt;img src="/images/posts/default-branch.png" alt="repo admin"&gt;&lt;/p&gt;

&lt;p&gt;Now, you can update this setting via the API. We’ve added a &lt;code&gt;default_branch&lt;/code&gt; parameter to the &lt;a href="/v3/repos/#edit"&gt;Edit Repository method&lt;/a&gt;:&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl -u pengwynn \

-d '{"name": "octokit", "default_branch":"development"}' \

https://api.github.com/repos/pengwynn/octokit

&lt;/pre&gt;

&lt;p&gt;If you provide a branch name that hasn’t been pushed to GitHub, we’ll gracefully fall back to &lt;code&gt;'master'&lt;/code&gt; or the first branch.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-10-17:/changes/2012-10-17-org-members-redirection/</id>

<title type="html">Organization Members Resource Changes</title>

<published>2012-10-17T05:00:00Z</published>

<updated>2012-10-17T05:00:00Z</updated>

<author>

<name>pezra</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-10-17-org-members-redirection/" />

<content type="html">&lt;p&gt;Requesting the &lt;a href="/v3/orgs/members/index.html#members-list"&gt;member list&lt;/a&gt; of an

organization of which you are not a member now redirects to the &lt;a href="v3/orgs/members/index.html#public-members-list"&gt;public members

list&lt;/a&gt;. Similarly, requests to

&lt;a href="/v3/orgs/members/index.html#check-membership"&gt;membership check&lt;/a&gt; resources of

an organization of which you are not a member are redirected to the equivalent

&lt;a href="/v3/orgs/members/index.html#check-public-membership"&gt;public membership check&lt;/a&gt;.

One exception to the latter case is that if you are checking about your own

membership the request is not redirected. You are always allowed to know what

organizations you belong to.&lt;/p&gt;

&lt;p&gt;The changes where made to clarify the purpose of these various resources. The

&lt;code&gt;/orgs/:org/members&lt;/code&gt; resources are intended for use by members of the

organization in question. The &lt;code&gt;/orgs/:org/public_members&lt;/code&gt; resources are for

acquiring information about the public membership of organizations. If you are

not a member you are not allowed to see private membership information so you

should be using the public membership resources.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please drop us a line at

&lt;a href="mailto:support@github.com?subject=Org%20members%20API"&gt;support@github.com&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-10-14:/changes/2012-10-14-rate-limit-changes/</id>

<title type="html">Rate limit changes for unauthenticated requests</title>

<published>2012-10-14T05:00:00Z</published>

<updated>2012-10-14T05:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-10-14-rate-limit-changes/" />

<content type="html">&lt;p&gt;To ensure a high quality of service for all API consumers, we’ve reduced the

default rate limit for unauthenticated requests. To enjoy the default rate

limit of 5,000 requests per hour, you’ll need to

&lt;a href="http://developer.github.com/v3/#authentication"&gt;authenticate&lt;/a&gt; via Basic Auth

or OAuth. Unauthenticated requests will be limited to 60 per hour unless you

&lt;a href="http://developer.github.com/v3/#unauthenticated-rate-limited-requests"&gt;include your OAuth client and

secret&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We’ll soon require all requests to include a valid &lt;a href="http://en.wikipedia.org/wiki/User_agent"&gt;User Agent

header&lt;/a&gt;. Setting a

unique value for this header helps us identify requests and get in touch with

developers who are abusing the API. Most HTTP libraries, wrapper libraries, and

even cURL provide a valid header for you already and allow you to change it to

something unique to your application.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, please drop us a line at

&lt;a href="mailto:support@github.com?subject=API%20Rate%20limit"&gt;support@github.com&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-09-28:/changes/2012-9-28-auto-init-for-repositories/</id>

<title type="html">Initialize a repository when creating</title>

<published>2012-09-28T05:00:00Z</published>

<updated>2012-09-28T05:00:00Z</updated>

<author>

<name>pengwynn</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-9-28-auto-init-for-repositories/" />

<content type="html">&lt;p&gt;Today we’ve made it easier to add commits to a repository via the GitHub API.

Until now, you could &lt;a href="/v3/repos/#create"&gt;create a repository&lt;/a&gt;, but you would

need to initialize it locally via your Git client before adding any commits via

the API.&lt;/p&gt;

&lt;p&gt;Now you can optionally init a repository when it’s created by sending &lt;code&gt;true&lt;/code&gt;

for the &lt;code&gt;auto_init&lt;/code&gt; parameter:&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl -i -u pengwynn \

-d '{"name": "create-repo-test", "auto_init": true}' \

https://api.github.com/user/repos

&lt;/pre&gt;

&lt;p&gt;The resulting repository will have a README stub and an initial commit.&lt;/p&gt;

&lt;p&gt;&lt;img src="/images/posts/create-repo-init.png" alt="create repo screenshot"&gt;&lt;/p&gt;

&lt;h3 id="gitignore-templates"&gt;.gitignore templates&lt;/h3&gt;

&lt;p&gt;Along with this change, you can set up your &lt;code&gt;.gitignore&lt;/code&gt; template by passing

the basename of any template in the &lt;a href="https://github.com/github/gitignore"&gt;GitHub gitignore templates

project&lt;/a&gt;.&lt;/p&gt;

&lt;pre class="terminal"&gt;

curl -i -u pengwynn \

-d '{"name": "create-repo-test", "auto_init": true, \

"gitignore_template": "Haskell"}' \

https://api.github.com/user/repos

&lt;/pre&gt;

&lt;p&gt;As the &lt;a href="/v3/repos/#create"&gt;docs point out&lt;/a&gt;, the &lt;code&gt;gitignore_template&lt;/code&gt; parameter

is ignored if &lt;code&gt;auto_init&lt;/code&gt; is not present and &lt;code&gt;true&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;If you have any questions or feedback, drop us a line at

&lt;a href="https://github.com/c"&gt;https://github.com/contact&lt;/a&gt;, &lt;a href="mailto:support@github.com"&gt;support@github.com&lt;/a&gt;, or

&lt;a href="https://twitter.com/githubapi"&gt;@GitHubAPI&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

<entry>

<id>tag:developer.github.com,2012-09-05:/changes/2012-9-5-watcher-api/</id>

<title type="html">Upcoming Changes to Watcher and Star APIs</title>

<published>2012-09-05T05:00:00Z</published>

<updated>2012-09-05T05:00:00Z</updated>

<author>

<name>technoweenie</name>

<uri>https://github.com/technoweenie</uri>

</author>

<link rel="alternate" href="http://developer.github.com/changes/2012-9-5-watcher-api/" />

<content type="html">&lt;p&gt;We recently &lt;a href="https://github.com/blog/1204-notifications-stars"&gt;changed the Watcher behavior&lt;/a&gt; on GitHub. What

used to be known as “Watching” is now “Starring”. Starring is basically a way

to bookmark interesting repositories. Watching is a way to indicate that you

want to receive email or web notifications on a Repository.&lt;/p&gt;

&lt;p&gt;This works well on GitHub.com, but poses a problem for the GitHub API. How do

we change this in a way that developers can gracefully upgrade their

applications? We’re currently looking at rolling out the changes in three

phases over an extended period of time.&lt;/p&gt;

&lt;h2 id="current-status"&gt;Current Status&lt;/h2&gt;

&lt;p&gt;The current &lt;a href="http://developer.github.com/v3/repos/starring/"&gt;Repository Starring&lt;/a&gt; methods look like this:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;code&gt;/repos/:owner/:repo/watchers&lt;/code&gt; - A list of users starring the repository.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/users/:user/watched&lt;/code&gt; - A list of repositories that a user has starred.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/user/watched&lt;/code&gt; - A list of repositories the current user has starred.&lt;/li&gt;

&lt;/ul&gt;&lt;h2 id="phase-1-add-watchers-as-subscriptions"&gt;Phase 1: Add Watchers as Subscriptions&lt;/h2&gt;

&lt;p&gt;This phase exposes Watchers as “Subscriptions”. This is to

keep from clashing with the legacy endpoints. This phase will happen

automatically and will not break your application until Phase 3 starts.&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;code&gt;/repos/:owner/:repo/subscribers&lt;/code&gt; - A list of users watching the repository.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/users/:user/subscriptions&lt;/code&gt; - A list of repositories that a user is watching.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/user/subscriptions&lt;/code&gt; - A list of repositories the current user is watching.&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;We’ll also add a copy of the legacy Watchers API in the new endpoint:&lt;/p&gt;

&lt;ul&gt;

&lt;li&gt;

&lt;code&gt;/repos/:owner/:repo/stargazers&lt;/code&gt; - A list of users starring the repository.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/users/:user/starred&lt;/code&gt; - A list of repositories that a user has starred.&lt;/li&gt;

&lt;li&gt;

&lt;code&gt;/user/starred&lt;/code&gt; - A list of repositories the current user has starred.&lt;/li&gt;

&lt;/ul&gt;&lt;p&gt;This is in place &lt;em&gt;now&lt;/em&gt; with the current media type for the API:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.beta+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;If you care about your application not breaking, make sure all outgoing API

requests pass that value for the “Accept” header. You should do this now. This

can be verified by checking the &lt;code&gt;X-GitHub-Media-Type&lt;/code&gt; header on all API

responses.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Accesses a user's starred repositories.

curl https://api.github.com/user/watched \

-H "Accept: application/vnd.github.beta+json"

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This Phase will be broken once Phase 3 starts. Phase 3 removes all support for

the “beta” media type, and makes the “v3” media type the implicit default

for API requests.&lt;/p&gt;

&lt;h2 id="phase-2-switch-watchers-api-endpoint"&gt;Phase 2: Switch &lt;code&gt;/watchers&lt;/code&gt; API Endpoint&lt;/h2&gt;

&lt;p&gt;The “watch” endpoints will now be a copy of the “subscription” endpoints. You

will have to use &lt;code&gt;/user/starred&lt;/code&gt; to get a user’s starred repositories, not

&lt;code&gt;/user/watched&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;This requires a new media type value:&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;application/vnd.github.v3+json

&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;This is a breaking change from Phase 1. We will release this change in an

experimental mode first, letting developers gracefully upgrade their

applications by specifying the new media value for the Accept header.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Accesses a user's watched repositories.

curl https://api.github.com/user/watched \

-H "Accept: application/vnd.github.v3+json"

&lt;/code&gt;&lt;/pre&gt;

&lt;h2 id="phase-3-remove-subscribers-api-endpoint"&gt;Phase 3: Remove &lt;code&gt;/subscribers&lt;/code&gt; API Endpoint.&lt;/h2&gt;

&lt;p&gt;This phase involves disabling the subscription endpoints completely. At this

point, you should be using the starring endpoints for starred repositories, and

the watch endpoints for watched repositories. No date has been set yet, but we

expect this to be &lt;em&gt;3-6 months&lt;/em&gt; after Phase 2 is in place. This should give

developers enough time for a smooth upgrade path. If they use popular API

wrappers, the work will likely mostly be done for them.&lt;/p&gt;

&lt;p&gt;Keep on passing the “v3” media type in your application, until the API has

another breaking change to make. If you can’t make the deadline for Phase 3,

just set the “beta” media type until we shut that down completely. It’s likely

that we will keep the old “beta” media type active for another month, like

the &lt;a href="https://github.com/blog/1090-github-api-moving-on"&gt;last time&lt;/a&gt; we terminated

old API functionality.&lt;/p&gt;

&lt;p&gt;We look forward to assisting you through this transition. Hit us up at

&lt;a href="https://github.com/c"&gt;https://github.com/contact&lt;/a&gt;, &lt;a href="mailto:support@github.com"&gt;support@github.com&lt;/a&gt;, or

&lt;a href="https://twitter.com/githubapi"&gt;@GitHubAPI&lt;/a&gt;.&lt;/p&gt;</content>

</entry>

</feed>