github-webhook-server

Set up the server, add the minimal data directory and config, connect one repository, and verify the webhook is live in minutes.

Add repositories, choose global defaults, apply per-repo overrides, and let repository maintainers customize behavior safely.

Create OWNERS files, define approvers and reviewers, and control who can run PR commands or be auto-assigned to changes.

Learn what the server does automatically on PR open, review, sync, and merge so contributors understand labels, checks, approvals, and merge readiness.

Use slash commands to retest checks, approve work, assign reviewers, rebase branches, cherry-pick changes, and recover missed automation.

Configure tox, pre-commit, custom check runs, container builds, and PyPI publishing so PRs and tags trigger the right automation.

Turn on conventional title suggestions, AI-assisted cherry-pick conflict resolution, and test-oracle recommendations with the sidecar and provider settings.

Protect incoming webhooks and PR automation with secrets, IP allowlists, suspicious-path detection, committer identity checks, and trusted-network-only access.

Open live and historical webhook logs, trace PR flow by delivery ID, and inspect step-level failures when automation does not behave as expected.

Copy working patterns for common setups like draft-PR command exceptions, protected branches, repo-local overrides, release-branch cherry-picks, and custom label policies.

Look up every supported `config.yaml` and `.github-webhook-server.yaml` key, including defaults, repository overrides, and validation rules.

Find every environment variable that affects startup, logging, sidecar behavior, log viewer exposure, and MCP availability.

Check the exact webhook callback path, health endpoint behavior, security headers, and what a successful HTTP response really means.

Look up the `/logs` HTTP and WebSocket endpoints plus the optional `/mcp` endpoint when you need exact routes, parameters, and response shapes.

See which GitHub events trigger automation, which ones are skipped intentionally, and how each event maps to server behavior.