summaryrefslogtreecommitdiff
path: root/_posts
diff options
context:
space:
mode:
authortekkub <tekkub@gmail.com>2009-11-17 23:05:42 -0700
committertekkub <tekkub@gmail.com>2009-11-17 23:05:42 -0700
commit2c746c734692965e4cb91f213e5195039414cd7c (patch)
treea43f8a72babdd6bfea79bbbdd73ac382b2f7dfff /_posts
parenta8a4f4b48ba3afc555d148e851de24c5c1259d1f (diff)
I are good writing
Diffstat (limited to '_posts')
-rw-r--r--_posts/2009-11-17-testing-webhooks.textile2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-11-17-testing-webhooks.textile b/_posts/2009-11-17-testing-webhooks.textile
index 7beb0f0..6fe72d4 100644
--- a/_posts/2009-11-17-testing-webhooks.textile
+++ b/_posts/2009-11-17-testing-webhooks.textile
@@ -10,7 +10,7 @@ Testing that a webhook works can be a bit of a pain. Thankfully with the help o
h2. When hooks are fired
-First and foremost, webhooks are not always called when a push is made. Currently hooks only fire when a branch that exists on GitHub is modified. Pushing new branches, deleting branches, and creating tags will not fire a webhook. Forced pushes such as @git push origin master --force@ may not predictably call hooks as well. I ensure your commits are sent to your webhook always push the branch when it is created before you commit, so that it exists on GitHub when you push the commits you want sent to the webhook.
+First and foremost, webhooks are not always called when a push is made. Currently hooks only fire when a branch that exists on GitHub is modified. Pushing new branches, deleting branches, and creating tags will not fire a webhook. Forced pushes such as @git push origin master --force@ may not predictably call hooks as well. To ensure your commits are sent to your webhook, always push the branch when it is created before you commit. This way the branch exists on GitHub when you push the commits you want sent to the webhook.
h2. Setting up