What a `web` hook receives
Headers: X-Pando-Event (the event), X-Pando-Delivery (the
delivery id), X-Pando-Signature-256: sha256=<hex> (HMAC-SHA256 of
the raw body with the hook's secret; GitHub's scheme under another
name).
Deliveries leave as soon as the change is recorded (no queue):
at least once and not in order, like GitHub's. The body's seq is the event stream's sequence number:
drop a seq you have seen, and sort by it. A try that does not get a
2xx within 10 seconds is retried after 10 s, 1 min, 5 min and 30 min
(5 tries over about 36 minutes); then the delivery is dead until an
owner redelivers it or replays the hook. Delivery records are kept for
the latest 1,000 per hook, with each one's last 10 tries.
hookDeliverywebhookAuthorisation
Request bodyJSON
- eventpushorbranch.openedormergedortagrequired
branch.opened: the first push of a branch.push: any push through the door that moves or deletes a branch.merged: a Pando merge landed a branch; a buildkite hook builds main's merge commit (merge_commit) on main (main_branch).tag: a tag pushed, moved or deleted (or made by publishing a release):tagis its name,headits commit (zeros when deleted).
Returns
200
Any 2xx counts as delivered.