Streamline Actions workflows with path-aware checks #252

New issue

Closed

opened 2026-05-18 11:44:38 -07:00 by jwilger · 0 comments

jwilger commented

2026-05-18 11:44:38 -07:00

Owner

Problem

Our Forgejo Actions workflows currently run the full application verification suite for PRs whose changes cannot affect the auto_review application build or trusted runtime code.

Example: PR #251 only changes opencode/agentic-harness configuration. That kind of developer-side configuration change should still receive review, and any directly relevant checks should run, but it should not require the full Rust build/test/check pipeline when the application code is unaffected.

Desired behavior

Classify changed paths in PR workflows and run only checks that the changed files could plausibly affect.
Keep semantic review running for PRs, even when application CI is skipped or reduced.
For opencode/plugin/harness changes, run relevant configuration or plugin tests when they exist.
Continue running full application gates for changes that affect application code, trust boundaries, runtime behavior, dependencies, deployment, CI definitions, or other safety-sensitive surfaces.
Avoid weakening security-sensitive checks; path filtering should be conservative when uncertain.

Notes

This is intended to streamline CI for configuration-only/developer-harness changes without losing the checks that matter for those changes.

## Problem Our Forgejo Actions workflows currently run the full application verification suite for PRs whose changes cannot affect the `auto_review` application build or trusted runtime code. Example: PR #251 only changes opencode/agentic-harness configuration. That kind of developer-side configuration change should still receive review, and any directly relevant checks should run, but it should not require the full Rust build/test/check pipeline when the application code is unaffected. ## Desired behavior - Classify changed paths in PR workflows and run only checks that the changed files could plausibly affect. - Keep semantic review running for PRs, even when application CI is skipped or reduced. - For opencode/plugin/harness changes, run relevant configuration or plugin tests when they exist. - Continue running full application gates for changes that affect application code, trust boundaries, runtime behavior, dependencies, deployment, CI definitions, or other safety-sensitive surfaces. - Avoid weakening security-sensitive checks; path filtering should be conservative when uncertain. ## Notes This is intended to streamline CI for configuration-only/developer-harness changes without losing the checks that matter for those changes.

jwilger added this to the 1.0 milestone

2026-05-18 11:44:46 -07:00

jwilger added the

bug

label

2026-05-18 11:44:49 -07:00

jwilger referenced this issue from a pull request that will close it,

2026-05-18 12:17:27 -07:00

fix(ci): add path-aware PR checks #255

jwilger closed this issue

2026-05-18 12:20:15 -07:00

jwilger referenced this issue from a commit