you have any questions or feedback,<ahref="https://github.com/contact?form%5Bsubject%5D=API+org+scopes">get in touch</a>.</p>

<divclass="change"id="/changes/2014-02-24-wildcard-event-for-webhooks/">

<h2class="title">

<ahref="/changes/2014-02-24-wildcard-event-for-webhooks/">Wildcard Event for Webhooks</a>

<divclass="meta">

<liclass="published">

<spanclass="octicon octicon-calendar"></span>

February 24, 2014

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/kdaigle.png"alt="Avatar for kdaigle">

<ahref="https://github.com/kdaigle">kdaigle</a>

<p>We’ve made a small change to make it easier for webhook integrators to receive “everything”.

Instead of adding every event to your webhook, you can now opt-in to all events (including

all new events in the future) by using the<ahref="/webhooks/#wildcard-event">wildcard event</a> (<code>*</code>).</p>

<p>If you add this event to an existing webhook, we’ll remove the existing specific events and

send you payloads for all supported events. As we add new events, you’ll automatically

begin receiving those too.</p>

<divclass="change"id="/changes/2014-02-24-finer-grained-scopes-for-ssh-keys/">

<p>As always, if you have any questions or feedback,<ahref="https://github.com/contact?form%5Bsubject%5D=API+improvements+for+SSH+keys">please get in touch</a>.</p>

<divclass="change"id="/changes/2014-02-24-wildcard-event-for-webhooks/">

<h2class="title">

<ahref="/changes/2014-02-24-wildcard-event-for-webhooks/">Wildcard Event for Webhooks</a>

<divclass="meta">

<liclass="published">

<spanclass="octicon octicon-calendar"></span>

February 24, 2014

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/kdaigle.png"alt="Avatar for kdaigle">

<ahref="https://github.com/kdaigle">kdaigle</a>

<p>We’ve made a small change to make it easier for webhook integrators to receive “everything”.

Instead of adding every event to your webhook, you can now opt-in to all events (including

all new events in the future) by using the<ahref="/webhooks/#wildcard-event">wildcard event</a> (<code>*</code>).</p>

<p>If you add this event to an existing webhook, we’ll remove the existing specific events and

send you payloads for all supported events. As we add new events, you’ll automatically

begin receiving those too.</p>

<divclass="change"id="/changes/2014-02-21-gist-raw-file-url-change/">

<divclass="change"id="/changes/2014-2-10-ping-event-for-webhooks/">

<divclass="change"id="/changes/2014-02-10-repo-hook-scopes/">

<h2class="title">

<ahref="/changes/2014-2-10-ping-event-for-webhooks/">Ping Event forWebhooks</a>

<ahref="/changes/2014-02-10-repo-hook-scopes/">New scopes formanaging repository hooks</a>

<divclass="meta">

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/kdaigle.png"alt="Avatar forkdaigle">

<ahref="https://github.com/kdaigle">kdaigle</a>

<imgheight="16"width="16"src="https://github.com/pengwynn.png"alt="Avatar forpengwynn">

<ahref="https://github.com/pengwynn">pengwynn</a>

<p>With the release of our<ahref="https://github.com/blog/1778-webhooks-level-up">new webhook UI</a>, we included a new

<ahref="/webhooks/#ping-event">ping event</a> that webhooks will receive. When you

create a new webhook, we will send this event as an initial test of the webhook.</p>

<p>Many third party services need to set up<ahref="http://developer.github.com/v3/repos/hooks/">hooks</a> in order to act upon events

in your repositories. Today, we’ve introduced three new<ahref="http://developer.github.com/v3/oauth/#scopes">scopes</a> that provide

more granular access to your repository hooks without allowing access to your

repository contents:</p>

<p>The ping is only informational, doesn’t need to be responded to in a specific way,

and nothing bad will happen if you respond with an error. It’s just a quick

“hello world” to let you know you set everything up correctly.</p>

<code>read:repo_hook</code> grants read and ping access to hooks in public or private repositories.</li>

<code>write:repo_hook</code> grants read, write, and ping access to hooks in public or private repositories.</li>

<code>admin:repo_hook</code> grants read, write, ping, and delete access to hooks in public or private repositories.</li>

<p>As always, if you have any questions or feedback,<ahref="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes">get in touch</a>.</p>

<p>We also added a<ahref="/v3/repos/hooks/#ping-a-hook">ping endpoint</a> to the hooks API.

By using ping instead of<ahref="/v3/repos/hooks/#test-a-push-hook">test</a>, you can ensure

you won’t be limited by the<code>push</code> event requirement that the test endpoint has.</p>

<divclass="change"id="/changes/2014-02-10-repo-hook-scopes/">

<divclass="change"id="/changes/2014-2-10-ping-event-for-webhooks/">

<h2class="title">

<ahref="/changes/2014-02-10-repo-hook-scopes/">New scopes formanaging repository hooks</a>

<ahref="/changes/2014-2-10-ping-event-for-webhooks/">Ping Event forWebhooks</a>

<divclass="meta">

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/pengwynn.png"alt="Avatar forpengwynn">

<ahref="https://github.com/pengwynn">pengwynn</a>

<imgheight="16"width="16"src="https://github.com/kdaigle.png"alt="Avatar forkdaigle">

<ahref="https://github.com/kdaigle">kdaigle</a>

<p>Many third party services need to set up<ahref="http://developer.github.com/v3/repos/hooks/">hooks</a> in order to act upon events

in your repositories. Today, we’ve introduced three new<ahref="http://developer.github.com/v3/oauth/#scopes">scopes</a> that provide

more granular access to your repository hooks without allowing access to your

repository contents:</p>

<code>read:repo_hook</code> grants read and ping access to hooks in public or private repositories.</li>

<code>write:repo_hook</code> grants read, write, and ping access to hooks in public or private repositories.</li>

<code>admin:repo_hook</code> grants read, write, ping, and delete access to hooks in public or private repositories.</li>

<p>With the release of our<ahref="https://github.com/blog/1778-webhooks-level-up">new webhook UI</a>, we included a new

<ahref="/webhooks/#ping-event">ping event</a> that webhooks will receive. When you

create a new webhook, we will send this event as an initial test of the webhook.</p>

<p>As always, if you have any questions or feedback,<ahref="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes">get in touch</a>.</p>

<p>The ping is only informational, doesn’t need to be responded to in a specific way,

and nothing bad will happen if you respond with an error. It’s just a quick

“hello world” to let you know you set everything up correctly.</p>

<p>We also added a<ahref="/v3/repos/hooks/#ping-a-hook">ping endpoint</a> to the hooks API.

By using ping instead of<ahref="/v3/repos/hooks/#test-a-push-hook">test</a>, you can ensure

you won’t be limited by the<code>push</code> event requirement that the test endpoint has.</p>

<divclass="change"id="/changes/2013-05-06-repository-stats/">

<divclass="change"id="/changes/2013-05-06-create-update-delete-individual-files/">

<h2class="title">

<ahref="/changes/2013-05-06-repository-stats/">Repository Statistics</a>

<ahref="/changes/2013-05-06-create-update-delete-individual-files/">Create, update, and delete individual files</a>

<divclass="meta">

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/Caged.png"alt="Avatar forCaged">

<ahref="https://github.com/Caged">Caged</a>

<imgheight="16"width="16"src="https://github.com/ymendel.png"alt="Avatar forymendel">

<ahref="https://github.com/ymendel">ymendel</a>

<p>Today we’re happy to open our<ahref="/v3/repos/statistics">Repository Statistics API</a> to everyone. We’re using

repository statistics to power<ahref="https://github.com/github/linguist/graphs">our graphs</a>,

but we can’t wait to see what others can do with this information.</p>

<p>Starting today, these resources are available to you:</p>

<p>We’re following in the footsteps of GitHub.com’s ability to<ahref="https://github.com/blog/143-inline-file-editing">edit</a> and

<ahref="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the

<ahref="/v3/repos/contents/">Repository Contents API</a> will let you easily<ahref="/v3/repos/contents/#create-a-file">create</a>,<ahref="/v3/repos/contents/#update-a-file">update</a>, and even

<ahref="/v3/repos/contents/#delete-a-file">delete</a> individual files.</p>

<li><strong><ahref="/v3/repos/statistics/#contributors">Contributors</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#commit-activity">Commit Activity</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#code-frequency">Code Frequency</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#participation">Participation</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#punch-card">Punch Card</a></strong></li>

<p>Happy editing!</p>

<p>Enjoy!</p>

<divclass="change"id="/changes/2013-05-06-create-update-delete-individual-files/">

<divclass="change"id="/changes/2013-05-06-repository-stats/">

<h2class="title">

<ahref="/changes/2013-05-06-create-update-delete-individual-files/">Create, update, and delete individual files</a>

<ahref="/changes/2013-05-06-repository-stats/">Repository Statistics</a>

<divclass="meta">

<liclass="who_when">

<imgheight="16"width="16"src="https://github.com/ymendel.png"alt="Avatar forymendel">

<ahref="https://github.com/ymendel">ymendel</a>

<imgheight="16"width="16"src="https://github.com/Caged.png"alt="Avatar forCaged">

<ahref="https://github.com/Caged">Caged</a>

<p>We’re following in the footsteps of GitHub.com’s ability to<ahref="https://github.com/blog/143-inline-file-editing">edit</a> and

<ahref="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the

<ahref="/v3/repos/contents/">Repository Contents API</a> will let you easily<ahref="/v3/repos/contents/#create-a-file">create</a>,<ahref="/v3/repos/contents/#update-a-file">update</a>, and even

<ahref="/v3/repos/contents/#delete-a-file">delete</a> individual files.</p>

<p>Today we’re happy to open our<ahref="/v3/repos/statistics">Repository Statistics API</a> to everyone. We’re using

repository statistics to power<ahref="https://github.com/github/linguist/graphs">our graphs</a>,

but we can’t wait to see what others can do with this information.</p>

<p>Happy editing!</p>

<p>Starting today, these resources are available to you:</p>

<li><strong><ahref="/v3/repos/statistics/#contributors">Contributors</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#commit-activity">Commit Activity</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#code-frequency">Code Frequency</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#participation">Participation</a></strong></li>

<li><strong><ahref="/v3/repos/statistics/#punch-card">Punch Card</a></strong></li>

<p>Enjoy!</p>

<spanclass="s2">"full_name"</span><spanclass="p">:</span><spanclass="s2">"octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"description"</span><spanclass="p">:</span><spanclass="s2">"This your first repo!"</span><spanclass="p">,</span>

<spanclass="s2">"private"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">true</span><spanclass="p">,</span>

<spanclass="s2">"url"</span><spanclass="p">:</span><spanclass="s2">"https://api.github.com/repos/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"html_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"clone_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World.git"</span><spanclass="p">,</span>

<spanclass="s2">"full_name"</span><spanclass="p">:</span><spanclass="s2">"octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"description"</span><spanclass="p">:</span><spanclass="s2">"This your first repo!"</span><spanclass="p">,</span>

<spanclass="s2">"private"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">true</span><spanclass="p">,</span>

<spanclass="s2">"url"</span><spanclass="p">:</span><spanclass="s2">"https://api.github.com/repos/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"html_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"clone_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World.git"</span><spanclass="p">,</span>

<spanclass="s2">"full_name"</span><spanclass="p">:</span><spanclass="s2">"octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"description"</span><spanclass="p">:</span><spanclass="s2">"This your first repo!"</span><spanclass="p">,</span>

<spanclass="s2">"private"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">true</span><spanclass="p">,</span>

<spanclass="s2">"url"</span><spanclass="p">:</span><spanclass="s2">"https://api.github.com/repos/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"html_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"clone_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World.git"</span><spanclass="p">,</span>

<pre><code>POST /staff/indexing_jobs

<h3id="parameters">Parameters</h3>

<h3id="input">Input</h3>

<h3id="example">Example</h3>

<preclass="terminal">

$ curl -u jwatson -X POST -H "Content-Type: application/json" -d '{"target": "kansaichris/japaning"}' "http://<em>hostname</em>/api/v3/staff/indexing_jobs"

<h3id="response">Response</h3>

<preclass="headers"><code>Status: 202 Accepted

<spanclass="s2">"message"</span><spanclass="p">:</span><spanclass="s2">"Repository 'kansaichris/japaning' has been added to the indexing queue"</span>

<spanclass="p">}</span></code></pre>

<h3id="example">Example</h3>

<preclass="terminal">

$ curl -u jwatson -X POST "http://<em>hostname</em>/api/v3/staff/indexing_jobs?target=jwatson%2Flaughing-robot"

{

"message": "Repository \"jwatson/laughing-robot\" has been added to the indexing queue"

}

<divid="js-sidebar"class="sidebar-shell">

<spanclass="s2">"full_name"</span><spanclass="p">:</span><spanclass="s2">"octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"description"</span><spanclass="p">:</span><spanclass="s2">"This your first repo!"</span><spanclass="p">,</span>

<spanclass="s2">"private"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">false</span><spanclass="p">,</span>

<spanclass="s2">"fork"</span><spanclass="p">:</span><spanclass="kc">true</span><spanclass="p">,</span>

<spanclass="s2">"url"</span><spanclass="p">:</span><spanclass="s2">"https://api.github.com/repos/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"html_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World"</span><spanclass="p">,</span>

<spanclass="s2">"clone_url"</span><spanclass="p">:</span><spanclass="s2">"https://github.com/octocat/Hello-World.git"</span><spanclass="p">,</span>