Skip to content

ci: label-based opt-in for AI review + full matrix on agent PRs#573

Merged
NagyVikt merged 1 commit into
mainfrom
agent/claude/ci-label-based-opt-in-2026-05-14-01-28
May 13, 2026
Merged

ci: label-based opt-in for AI review + full matrix on agent PRs#573
NagyVikt merged 1 commit into
mainfrom
agent/claude/ci-label-based-opt-in-2026-05-14-01-28

Conversation

@NagyVikt
Copy link
Copy Markdown
Collaborator

Summary

Adds two escape hatches to the budget-friendly defaults so the occasional agent PR that actually needs deeper checks can opt in without flipping a global toggle.

  • needs-review label on a agent/* PR → AI code review (cr.yml) runs even though it would otherwise skip.
  • needs-ci-full label on any PR → full cross-runtime matrix (ci-full.yml) runs immediately instead of waiting for the weekly schedule.

Both workflows add labeled to their pull_request.types, so applying the label fires the run immediately — no re-push needed. Templates updated to ship the same convention to downstream projects.

README under templates/github/workflows/ documents the labels with a gh label create needs-review ... recipe for one-line setup.

Test plan

  • All 4 YAMLs parse via js-yaml
  • No new failures in test/metadata.test.js (4 pre-existing stale assertions from PR ci: budget-friendly defaults + templates for gitguardex-managed projects #571 remain)
  • Verify: open an agent/* PR, apply needs-review label → Code Review fires
  • Verify: apply needs-ci-full label to any PR → full Node 18/22 matrix fires
  • Verify: without labels, agent/* PRs still skip both workflows

🤖 Generated with Claude Code

Adds escape hatches for the budget-friendly defaults. Both apply
identically in the live workflows AND the templates ship to downstream
projects.

- cr.yml: agent/* PRs still skip AI review by default, but the
  `needs-review` label overrides the skip for that one PR.
- ci-full.yml: weekly schedule + workflow_dispatch unchanged, plus
  per-PR opt-in via the `needs-ci-full` label.

Both workflows add `labeled` to their pull_request.types so applying
the label fires the run immediately — no re-push required. README
documents the labels and points at `gh label create` for setup.

Pre-existing test/metadata.test.js failures (4) are stale assertions
from PR #571 and remain out of scope here.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@NagyVikt NagyVikt merged commit 8939f32 into main May 13, 2026
1 of 2 checks passed
@NagyVikt NagyVikt deleted the agent/claude/ci-label-based-opt-in-2026-05-14-01-28 branch May 13, 2026 23:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant