Repository navigation
Conversation
…pect Hookdeck Console has been renamed Hookdeck Inspect. The sentence listed it as a tool that exposes your local machine to the internet, which is what the Hookdeck CLI does. Inspect is a browser view of incoming payloads. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
There was a problem hiding this comment.
🟡 Changes recommended
An active documentation issue remains because Hookdeck Event Gateway is still misclassified as a cloud function instead of being separated from the Azure Functions and AWS Lambda examples.
1 open issue
What changed in this PR
Updates the GitHub Apps webhook guidance to reflect Hookdeck’s current product names and usage.
Changes:
- Replaces Hookdeck Console with the Hookdeck CLI for local development.
- Adds Hookdeck Inspect for viewing webhook payloads in a browser.
- Renames the production offering to Hookdeck Event Gateway.
This pull request is ready to be approved.
| File | Summary |
|---|---|
content/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps.md |
Updates Hookdeck product names, descriptions, and links. The production wording should distinguish Hookdeck Event Gateway from the Azure Functions and AWS Lambda cloud-function examples. |
Review effort: Lite
Keeps it separate from the cloud function examples, and matches how the webhooks best-practices and troubleshooting pages describe Hookdeck. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks for your submission, @leggetter; we'll get this reviewed by the appropriate team |

Why:
Closes: N/A
Hookdeck Console is now Hookdeck Inspect (https://hookdeck.com/changelog/hookdeck-inspect). The development section listed Console as a tool that exposes your local machine to the internet, which is what the Hookdeck CLI does; Inspect is a browser view of incoming payloads. The production section listed Hookdeck as a cloud function; it now describes Hookdeck Event Gateway as a webhook queuing service. The old Console link still works, so nothing is broken today.
What's being changed (if available, include any code snippets, screenshots, or gifs):
Two sentences in
content/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps.md:Disclosure: I work at Hookdeck.
Check off the following:
🤖 Generated with Claude Code