summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2011-02-26 21:19:48 -0700
committertekkub <tekkub@gmail.com>2011-02-26 21:19:48 -0700
commit5abc621539c2f5de642bb3a6161345f6bd777d07 (patch)
treee9f2e17b4b285ffcaa28dd34e63cbfeb3eb3990f
parentf5b7bec7c5b3e800d60637ae022439a69a37a2e1 (diff)
who says order matters?
-rw-r--r--_posts/2009-10-16-post-receive-hooks.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-10-16-post-receive-hooks.markdown b/_posts/2009-10-16-post-receive-hooks.markdown
index 25db1e8..80a5d65 100644
--- a/_posts/2009-10-16-post-receive-hooks.markdown
+++ b/_posts/2009-10-16-post-receive-hooks.markdown
@@ -63,7 +63,7 @@ post '/' do
end
{% endhighlight %}
-The `commits` array is ordered with the most recent commit as the first element. The last element, therefor, is the oldest commit.
+The `commits` array is ordered with the oldest commit as the first element. The last element is the newest commit and should match the "after" value for the branch.
Here's an example payload: