Summary
Webhook administration is repetitive and clicky; this turns it into a sentence.
The organisation-level tools are what earn the server: one hook created there covers every repository, and listing them is how you find the stale endpoints nobody remembers adding. Updates are partial, so you can repoint a URL or narrow an event list without restating the rest of the configuration.
What it is
A server for GitHub webhook administration at both levels: hooks that apply to every repository in an organisation, and hooks on one repository.
What you get
- Organisation-wide webhooks created, listed with paging, modified and deleted (create_org_webhook, list_org_webhooks, update_org_webhook, delete_org_webhook)
- The same four operations on a single repository's hooks (create_repo_webhook, list_repo_webhooks, update_repo_webhook, delete_repo_webhook)
- Full control of the hook configuration — delivery URL, content type and shared secret — and the list of events it subscribes to
- A hook switched off without deleting it, by flipping its active flag
Requirements
A GitHub personal access token carrying the webhook administration scope for the level you are working at — organisation hooks and repository hooks need different ones. Node.js, with the token supplied as an environment setting.