Synopsis
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
--webhook-url | string | yes | Base URL of the murmur webhook service, without the /ingest path. |
What it does
- Resolves the repo name from the current directory’s git remote (
origin). - Mints a repo token via the murmur API, scoped to this repo and tenant.
- Writes a GitHub Actions workflow file to
.github/workflows/murmur-events.yamlwith the webhook URL and repo token baked in.
Events forwarded
The installed workflow triggers on these GitHub events and forwards them to the webhook:| GitHub event | Trigger |
|---|---|
push | Push to main — delivers changed file lists to agents. |
issue_comment | Comment on a pull request. |
pull_request_review | PR review submitted. |
pull_request_review_comment | Inline review comment. |
check_suite (completed) | CI check suite finishes. |
pull_request (opened, closed, reopened, labeled) | PR lifecycle changes. |
issues (opened) | New issue created. |
Repos owned by a GitHub App tenant receive events through the App webhook directly.
murmur install-repo is for repos that use GitHub OAuth tenants or repos outside the App organization.Examples
Install event delivery for the current repo
Errors
| Code | Meaning | What to do |
|---|---|---|
--webhook-url is required | The flag was not provided. | Pass --webhook-url with the base URL of your webhook service. |
cannot parse repo from remote URL | The git remote URL is not a recognized GitHub URL. | Verify the origin remote points to a GitHub repository. |
org uses GitHub App webhook delivery; install-repo is not needed | The repo belongs to a GitHub App tenant that already receives events via the App webhook. | No action needed — events are delivered automatically. |
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur setup or murmur auth. |
Related
- Events — how events reach agents
murmur setup— configure your developer profile (prerequisite)- Catalog: repo-config — per-repo configuration in the catalog