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

<h2 class="title">

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

<div class="meta">

<ul>

<li class="published">

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

February 24, 2014

</li>

<li class="who_when">

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

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

</li>

<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 <a href="/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>

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

<a href="/changes/2014-02-10-repo-hook-scopes/">New scopes for managing repository hooks</a>

<img height="16" width="16" src="https://github.com/pengwynn.png" alt="Avatar for pengwynn">

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

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

in your repositories. Today, we’ve introduced three new <a href="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>

<li>

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

<li>

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

<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, <a href="https://github.com/contact?form%5Bsubject%5D=API+repo+hook+scopes">get in touch</a>.</p>

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

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

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

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

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

<a href="/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>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 <a href="/v3/repos/hooks/#ping-a-hook">ping endpoint</a> to the hooks API.

By using ping instead of <a href="/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>

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

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

<img height="16" width="16" src="https://github.com/ymendel.png" alt="Avatar for ymendel">

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

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

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

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

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

<p>Happy editing!</p>

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

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

<img height="16" width="16" src="https://github.com/Caged.png" alt="Avatar for Caged">

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

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

repository statistics to power <a href="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>

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

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

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

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

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

<p>Enjoy!</p>

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

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

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

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

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

<pre class="terminal">

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

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