You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
<ahref="/changes/2013-05-06-create-update-delete-individual-files/">Create, update, and delete individual files</a>
3693
+
</h2>
3694
+
3695
+
<divclass="meta">
3696
+
<ul>
3697
+
<liclass="published">
3698
+
<spanclass="octicon octicon-calendar"></span>
3699
+
May 6, 2013
3700
+
3701
+
</li>
3702
+
<liclass="who_when">
3703
+
<imgheight="16"width="16"src="https://github.com/ymendel.png"alt="Avatar for ymendel">
3704
+
<ahref="https://github.com/ymendel">ymendel</a>
3705
+
</li>
3706
+
</ul>
3707
+
</div>
3708
+
3709
+
<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
3710
+
<ahref="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the
3711
+
<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
<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
3747
-
<ahref="https://github.com/blog/1327-creating-files-on-github">create</a> files in your web browser. Starting today, the
3748
-
<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
<p>Last week we announced<ahref="https://github.com/blog/1484-check-the-status-of-your-branches">support for build statuses in the branches page</a>.
3776
+
Now we are extending this to the API. The<ahref="http://developer.github.com/v3/repos/statuses/#list-statuses-for-a-specific-ref">API endpoint for commit statuses</a>
3777
+
has been extended to allow branch and tag names, as well as commit SHAs.</p>
<ahref="/changes/2013-04-30-statuses-for-branches-and-tags/">Commit Statuses Now Available for Branches and Tags</a>
3811
-
</h2>
3812
-
3813
-
<divclass="meta">
3814
-
<ul>
3815
-
<liclass="published">
3816
-
<spanclass="octicon octicon-calendar"></span>
3817
-
April 30, 2013
3818
-
3819
-
</li>
3820
-
<liclass="who_when">
3821
-
<imgheight="16"width="16"src="https://github.com/foca.png"alt="Avatar for foca">
3822
-
<ahref="https://github.com/foca">foca</a>
3823
-
</li>
3824
-
</ul>
3825
-
</div>
3826
-
3827
-
<p>Last week we announced<ahref="https://github.com/blog/1484-check-the-status-of-your-branches">support for build statuses in the branches page</a>.
3828
-
Now we are extending this to the API. The<ahref="http://developer.github.com/v3/repos/statuses/#list-statuses-for-a-specific-ref">API endpoint for commit statuses</a>
3829
-
has been extended to allow branch and tag names, as well as commit SHAs.</p>
<p>Note:Both<code>:base</code> and<code>:head</code>can beeitherbranch names in<code>:repo</code> or branch names in other repositories in the same network as<code>:repo</code>. For the latter case, use the format<code>user:branch</code>:</p>
294
+
<p>Both<code>:base</code> and<code>:head</code>must be branch names in<code>:repo</code>. To compare branches across other repositories in the same network as<code>:repo</code>, use the format<code><USERNAME>:branch</code>. For example:</p>
<p>The response from the API is equivalent to running the<code>git log base..head</code> command; however, commits are returned in reverse chronological order.</p>