Description
The Claude AI Post-Merge Test Plan workflow (.github/workflows/ai_claude-post-merge-test-plan.yml) currently generates a QA test plan for every merged PR that carries Area : Backend or Area : Frontend. It should be opt-in: only PRs that carry the PR : dotbot review label (the same label that already triggers the dotbot AI code review) should get a plan after merge.
A manual workflow_dispatch run should keep working without the label, since dispatching by hand is already an explicit request and is the way to plan a PR that got the label only after it merged.
Acceptance Criteria
Priority
Medium
Description
The Claude AI Post-Merge Test Plan workflow (
.github/workflows/ai_claude-post-merge-test-plan.yml) currently generates a QA test plan for every merged PR that carriesArea : BackendorArea : Frontend. It should be opt-in: only PRs that carry thePR : dotbot reviewlabel (the same label that already triggers the dotbot AI code review) should get a plan after merge.A manual
workflow_dispatchrun should keep working without the label, since dispatching by hand is already an explicit request and is the way to plan a PR that got the label only after it merged.Acceptance Criteria
PR : dotbot reviewand an Area label gets a test plan.PR : dotbot reviewis skipped, with a notice in the preflight log.PR : dotbot reviewbut no Area label is still skipped.PR : dotbot review.PR : dotbot reviewlabel description mentions that it also triggers the post-merge test plan.Priority
Medium