GitHub Pull Requests

Warden runs on pull requests through GitHub Actions and reports findings in Checks. When findings can be tied to the current pull request diff, Warden also posts inline review comments.

This page explains the pull request behavior. Setup lives in Repository Setup, and action inputs live in Workflow.

What Happens on a PR

1. A pull request is opened or updated.
2. GitHub Actions runs the Warden workflow.
3. Warden analyzes changed files against configured triggers.
4. Findings are reported in Checks. Eligible findings are also posted as inline review comments.
5. If requestChanges is enabled, Warden requests changes when findings exceed failOn.
6. If failCheck is enabled, the check run fails when findings exceed failOn.

Warden skips PR review feedback when the workflow run is no longer analyzing the current PR head. Non-blocking findings without an inline diff location stay in Checks instead of creating timeline comments that cannot be resolved later.

What Comes From warden.toml

Pull request behavior is still driven by warden.toml:

Concern	Where to configure it
Which skills run on PRs	Triggers
Which files a skill sees	Skill Entries
What severity reports or fails	Output and Defaults

The GitHub workflow decides when the action starts and which credentials it can use. The config decides what Warden does once it is running.

Next

Repository SetupInitialize one repository with config and a workflow.Organization SetupRoll Warden out across many repositories.Workflow ReferenceReview action inputs and layered config options.