Subscriptions
A subscription delivers a webhook when matching writes or metadata events occur. Commit subscriptions watch a repository (or a same-org source repository). Organization owners and admins can also create org-scoped subscriptions for member additions, repository creation, publication, and organization renames.
Create a subscription
Section titled “Create a subscription”POST to your webhook when Signal writes land (things or assertions):
wh sub create signal-hook --repo myorg/myrepo --on Signal --kind webhook \ --filter '{"shape":"Signal"}' --webhook-url https://example.com/hookWhen a matching write lands, WarmHub records an action event, matches it against every active subscription’s filter, and dispatches the webhook to each match — retrying transient failures with exponential backoff before the run goes terminal. See Creating Subscriptions for the webhook payload and credential binding.
Org activity subscriptions use --org and have no shape or filter:
wh sub create repo-feed --org myorg --event org.repo_created \ --webhook-url https://example.com/org-activityNext Steps
Section titled “Next Steps”| Need | Page |
|---|---|
| Create a subscription and see the webhook payload shape | Creating Subscriptions |
| Watch a different repository in the same org | Cross-Repo Subscriptions |
| The filter grammar that selects which writes fire | Filter JSON |
| Bind delivery auth and verify WarmHub’s HMAC signature | Credentials & Signatures |
| List, view, pause, resume, update, or delete subscriptions | Managing Subscriptions |
| Inspect the delivery feed and per-attempt details | Delivery Feed |
| Understand run statuses, retries, and dead-letter behavior | Action Delivery Lifecycle |
| Debug a subscription that has stopped delivering | Debugging a Failing Subscription |
| Terminal-failure notifications | Notifications |