github · Ellorah · Sep 28, 2012 · Sep 28, 2012 · Sep 28, 2012 · Sep 28, 2012
diff --git a/README.md b/README.md
@@ -53,13 +53,17 @@ We specify the JSON responses in ruby so that we don't have to write
 them by hand all over the docs.  You can render the JSON for a resource
 like this:
 
-    <%= json :issue %>
+```erb
+<%= json :issue %>
+```
 
 This looks up `GitHub::Resources::ISSUE` in `lib/resources.rb`.
 
 Some actions return arrays.  You can modify the JSON by passing a block:
 
-    <%= json(:issue) { |hash| [hash] } %>
+```erb
+<%= json(:issue) { |hash| [hash] } %>
+```
 
 ### Terminal blocks
 

diff --git a/content/changes/2012-10-14-rate-limit-changes.html b/content/changes/2012-10-14-rate-limit-changes.html
@@ -0,0 +1,24 @@
+---
+kind: change
+title: Rate limit changes for unauthenticated requests
+created_at: 2012-10-14
+author_name: pengwynn
+---
+
+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
+[authenticate](http://developer.github.com/v3/#authentication) via Basic Auth
+or OAuth. Unauthenticated requests will be limited to 60 per hour unless you
+[include your OAuth client and
+secret](http://developer.github.com/v3/#unauthenticated-rate-limited-requests).
+
+We'll soon require all requests to include a valid [User Agent
+header](http://en.wikipedia.org/wiki/User_agent). 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.
+
+If you have any questions or feedback, please drop us a line at
+[[email protected]](mailto:[email protected]?subject=API Rate limit).
diff --git a/content/changes/2012-10-17-org-members-redirection.md b/content/changes/2012-10-17-org-members-redirection.md
@@ -0,0 +1,26 @@
+---
+kind: change
+title: Organization Members Resource Changes
+created_at: 2012-10-17
+author_name: pezra
+---
+
+Requesting the [member list](/v3/orgs/members/index.html#members-list) of an
+organization of which you are not a member now redirects to the [public members
+list](v3/orgs/members/index.html#public-members-list). Similarly, requests to
+[membership check](/v3/orgs/members/index.html#check-membership) resources of
+an organization of which you are not a member are redirected to the equivalent
+[public membership check](/v3/orgs/members/index.html#check-public-membership).
+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.
+
+The changes where made to clarify the purpose of these various resources. The
+`/orgs/:org/members` resources are intended for use by members of the
+organization in question. The `/orgs/:org/public_members` 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.
+
+If you have any questions or feedback, please drop us a line at
+[[email protected]](mailto:[email protected]?subject=Org members API).
diff --git a/content/changes/2012-10-24-set-default-branch.html b/content/changes/2012-10-24-set-default-branch.html
@@ -0,0 +1,22 @@
+---
+kind: change
+title: Set the default branch for a repository
+created_at: 2012-10-24
+author_name: pengwynn
+---
+
+You can set the default branch for a repository to something other than 'master' from the GitHub repository admin screen:
+
+![repo admin](/images/posts/default-branch.png)
+
+Now, you can update this setting via the API. We've added a `default_branch` parameter to the [Edit Repository method][edit-repo]:
+
+<pre class="terminal">
+curl -u pengwynn \
+     -d '{"name": "octokit", "default_branch":"development"}' \
+     https://api.github.com/repos/pengwynn/octokit
+</pre>
+
+If you provide a branch name that hasn't been pushed to GitHub, we'll gracefully fall back to `'master'` or the first branch.
+
+[edit-repo]: /v3/repos/#edit
diff --git a/content/changes/2012-10-26-notifications-api.md b/content/changes/2012-10-26-notifications-api.md
@@ -0,0 +1,72 @@
+---
+kind: change
+title: Notifications API
+created_at: 2012-10-26
+author_name: technoweenie
+---
+
+Now that the dust has settled around [Notifications and Stars][newsies],
+we've unleashed all that :sparkles: in a [brand new API][api].  You can now
+view and mark notifications as read.
+
+[api]: http://developer.github.com/v3/activity/notifications/
+[newsies]: https://github.com/blog/1204-notifications-stars
+
+## Endpoint
+
+The core notifications functionality is under the `/notifications` endpoint.
+You can look for unread notifications:
+
+<pre class="terminal">
+$ curl https://api.github.com/notifications
+</pre>
+
+You can filter these notifications to a single Repository:
+
+<pre class="terminal">
+$ curl https://api.github.com/repos/technoweenie/faraday/notifications
+</pre>
+
+You can mark them as read:
+
+<pre class="terminal">
+# 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}'
+</pre>
+
+You can also modify subscriptions for a Repository or a single thread.
+
+<pre class="terminal">
+# 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
+</pre>
+
+## Polling
+
+The Notifications API is optimized for polling by the last modified time:
+
+<pre class="terminal">
+# 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
+</pre>
+
+You can read about the API details in depth in the [Notifications documentation][api].
+
+
diff --git a/content/changes/2012-10-31-gist-comment-uris.md b/content/changes/2012-10-31-gist-comment-uris.md
@@ -0,0 +1,12 @@
+---
+kind: change
+title: Gist comment URIs
+created_at: 2012-10-31
+author_name: pezra
+---
+
+The URIs of all gist comments are changing immediately. The new URI pattern for gist comments is `/gists/{gist-id}/comments/{id}`. (See [gist comments section of the docs](/v3/gists/comments/) 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.
+
+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.
+
+We have also added a `comments_url` member to the Gist documents. The `comments_url` 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 `url` and `*_url` properties, where possible, rather than constructing URIs using the patterns published on this site. Doing so will result in clients that break less often.
diff --git a/content/changes/2012-9-28-auto-init-for-repositories.html b/content/changes/2012-9-28-auto-init-for-repositories.html
@@ -0,0 +1,50 @@
+---
+kind: change
+title: Initialize a repository when creating
+created_at: 2012-9-28
+author_name: pengwynn
+---
+
+Today we've made it easier to add commits to a repository via the GitHub API.
+Until now, you could [create a repository](/v3/repos/#create), but you would
+need to initialize it locally via your Git client before adding any commits via
+the API.
+
+Now you can optionally init a repository when it's created by sending `true`
+for the `auto_init` parameter:
+
+<pre class="terminal">
+curl -i -u pengwynn \
+     -d '{"name": "create-repo-test", "auto_init": true}' \
+     https://api.github.com/user/repos
+</pre>
+
+The resulting repository will have a README stub and an initial commit.
+
+![create repo screenshot](/images/posts/create-repo-init.png)
+
+### .gitignore templates
+
+Along with this change, you can set up your `.gitignore` template by passing
+the basename of any template in the [GitHub gitignore templates
+project](https://github.com/github/gitignore).
+
+<pre class="terminal">
+curl -i -u pengwynn \
+     -d '{"name": "create-repo-test", "auto_init": true, \
+          "gitignore_template": "Haskell"}' \
+     https://api.github.com/user/repos
+</pre>
+
+
+As the [docs point out](/v3/repos/#create), the `gitignore_template` parameter
+is ignored if `auto_init` is not present and `true`.
+
+If you have any questions or feedback, drop us a line at
+[https://github.com/contact][c], [[email protected]][email], or
+[@GitHubAPI][twitter].
+
+[twitter]: https://twitter.com/githubapi
+[email]: mailto:[email protected]
+[c]: https://github.com/c
+