Automated GitHub PR Comments with Webhooks
Automated GitHub PR Comments with Webhooks
Start with meaning, then move to detail.
This lesson explains Automated GitHub PR Comments with Webhooks as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Prerequisites, Step 1 — Enable the webhook platform, Step 2 — Start the gateway, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Automated GitHub PR Comments with Webhooks without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Gateway
- The process that connects Hermes to channels such as Telegram or Discord and routes messages.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Connect Hermes to GitHub so it automatically fetches PR diffs, reviews code changes, and posts comments — triggered by webhooks with no manual prompting
What does the source say, and in what order?
- 01Prerequisites
Start here to understand the core idea or structure.
- 02Step 1 — Enable the webhook platform
Read this after the foundation, then connect it to the previous step.
- 03Step 2 — Start the gateway
Read this after the foundation, then connect it to the previous step.
- 04Step 3 — Register the webhook on GitHub
Read this after the foundation, then connect it to the previous step.
- 05Step 4 — Open a test PR
Read this after the foundation, then connect it to the previous step.
- 06Local testing with ngrok
Read this after the foundation, then connect it to the previous step.
- 07Filtering to specific actions
Read this after the foundation, then connect it to the previous step.
- 08Using a skill for consistent review style
Read this after the foundation, then connect it to the previous step.
- 09Sending responses to Slack or Discord instead
Read this after the foundation, then connect it to the previous step.
- 10GitLab support
Finish here to verify the result and special cases.
Copy only after you understand the effect.
platforms:
webhook:
enabled: true
extra:
port: 8644 # default; change if another service occupies this port
rate_limit: 30 # max requests per minute per route (not a global cap)
routes:
github-pr-review:
secret: "your-webhook-secret-here" # must match the GitHub webhook secret exactly
events:
- pull_request
# The agent is instructed to fetch the actual diff before reviewing.
# {number} and {repository.full_name} are resolved from the GitHub payload.
prompt: |
A pull rhermes gateway[webhook] Listening on 0.0.0.0:8644 — routes: github-pr-reviewRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.