You can specify terminal blocks with`pre.terminal` elements. (It'd be nice if

Markdown could do this more cleanly.)

You can specify terminal blocks by prefacing a[block element][block boundaries] with`{:.terminal}`.

{:.terminal}

$ curl foobar

Alternatively, you can use plain html and use`pre.terminal` elements.

(If, for example, you need to emphasis text with`<em>`)

<preclass="terminal">

$ curl foobar

$ curl<em>foobar<em>

....

</pre>

This is not a`curl` tutorial though. Not every API call needs

to show how to access it with`curl`.

[block boundaries]:http://kramdown.gettalong.org/syntax.html#block-boundaries

Nanoc compiles the site into static files living in`./output`. It's

Now, you can update this setting via the API. We've added a `default_branch` parameter to the [Edit Repository method][edit-repo]:

<preclass="terminal">

curl -u pengwynn \

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

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

{:.terminal}

curl -u pengwynn \

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

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

If you provide a branch name that hasn't been pushed to GitHub, we'll gracefully fall back to `'master'` or the first branch.

The core notifications functionality is under the`/notifications` endpoint.

You can look for unread notifications:

<preclass="terminal">

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

</pre>

{:.terminal}

$ curlhttps://api.github.com/notifications

You can filter these notifications to a single Repository:

<preclass="terminal">

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

</pre>

{:.terminal}

$ curlhttps://api.github.com/repos/technoweenie/faraday/notifications

You can mark them as read:

# all notifications

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

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

{:.terminal}

# all notifications

$ curlhttps://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.

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

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

{:.terminal}

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

$ curlhttps://api.github.com/notifications/threads/1/subscription

# subscription details for a whole Repository.

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

</pre>

The Notifications API is optimized for polling by the last modified time:

<preclass="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>

{:.terminal}

# Add authentication to your requests

$ curl -Ihttps://api.github.com/notifications

HTTP/1.1 200 OK

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

X-Poll-Interval: 60

You can read about the API details in depth in the[Notifications documentation][api].

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.

{:.terminal}

$ curl -X POST https://api.github.com/repos/technoweenie/faraday/forks

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 `?org` query parameter:

{:.terminal}

$ curl -X POST /repos/technoweenie/faraday/forks?org=mycompany

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 `organization`.

{:.terminal}

$ curl /repos/technoweenie/faraday/forks?org=mycompany \

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

The [Gitignore Templates API][new-api] makes it easy to list those templates:

{:.terminal}

curl https://api.github.com/gitignore/templates

HTTP/1.1 200 OK

If you'd like to view the source, you can also fetch a single template.

{:.terminal}

curl -H 'Accept: application/vnd.github.raw' \

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

Today, we're introducing two new methods to grab all Issue Comments and Review

Comments for a repository.

{:.terminal}

# Grab all Issue Comments

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

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

note and you get a token back:

{:.terminal}

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

https://api.github.com/authorizations

This call creates a token for the authenticated user tied to a special "API"

OAuth application.

the settings page for your OAuth application.

{:.terminal}

curl -u pengwynn -d '{ \

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

"client_id": "abcdeabcdeabcdeabcdeabcde" \

"client_secret": "abcdeabcdeabcdeabcdeabcdeabcdeabcdeabcdeabcde" \

}' \ '

https://api.github.com/authorizations

No more implementing the [web flow][web-flow] just to get a token tied to your

app's rate limit.

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

are sources (not forks).

{:.terminal}

# Grab all fork Repositories for an Organization

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

Simply use the same resource URL and send either `application/vnd.github.diff` or `application/vnd.github.patch` in the `Accept` header:

{:.terminal}

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

Now you can optionally init a repository when it's created by sending `true`

for the `auto_init` parameter:

<preclass="terminal">

curl -i -u pengwynn \

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

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

{:.terminal}

curl -i -u pengwynn \

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

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

The resulting repository will have a README stub and an initial commit.

the basename of any template in the [GitHub gitignore templates

project](https://github.com/github/gitignore).

<preclass="terminal">

curl -i -u pengwynn \

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

"gitignore_template": "Haskell"}' \

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

{:.terminal}

curl -i -u pengwynn \

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

"gitignore_template": "Haskell"}' \

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

As the [docs point out](/v3/repos/#create), the `gitignore_template` parameter