How it works
Weave excludes ignored PRs from output metrics. A PR is considered ignored if it is not the result of human or AI engineering effort.
Weave is conservative: when unsure, a PR is not auto-ignored.
Automatic ignore criteria
Release or deploy plumbing
Auto-ignored only when the PR clearly does no new engineering work. It must match one of:
- Release / version-bump PRs — title or branch like
Release v2.5.0, release/1.2.3, or a
release-train name, and the diff is only a version / CHANGELOG / release-manifest bump
- Promotion / sync PRs — moving already-merged commits between long-lived branches (for example
develop → main, staging → production, or a release → main back-merge) with no new
application changes
- Deploy-trigger PRs — exists only to ship already-merged code (for example “Deploy to prod”),
with no new application changes
Not ignored under this reason:
- Dependency bumps (lockfiles,
package.json deps, go.mod, etc.)
- Bug fixes, features, refactors, tests, migrations
- Lint / formatting cleanups or comment-only edits
- CI / workflow / Dockerfile / infrastructure-as-code edits
- Any PR with real application code changes, or any PR Weave is unsure about
Re-merge duplicate
Auto-ignored when re-merge dedup is enabled for the organization and most of the PR’s non-merge
commits already belong to an earlier merged PR from the same topic branch. Long-lived head branches
(main, develop, release/*, staging, prod, etc.) are never treated as re-merge duplicates.
The earlier merge still counts in metrics.
Branch exclusion rule
Auto-ignored because the PR’s head and base branches match an organization exclusion rule
(optional repo-name pattern). Example: ignore merges from release/* into main.
Legacy system rule
Preserved from older automatic ignore state before reason-scoped classification. Retired when Weave
re-processes the PR under current rules.
In metric drilldowns, hover the Ignored column header for these definitions, or hover a row’s
Ignored toggle to see which reason(s) apply to that PR.
If a PR was auto-ignored but someone flipped the toggle off, the row shows a Manually unignored
badge and still counts toward output metrics.
Marking a PR as ignored
You can manually mark any PR as ignored or not ignored by flipping its ignored toggle in the PR
drilldown view. This immediately excludes the PR from all output metrics (or includes it again if
you unignore).Last modified on July 27, 2026
