Repository navigation
Run ARC CI when a PR is retargeted onto a release branch - #107
Conversation
PR #100 was retargeted to release/native-0.1.10 after all its commits were pushed, so the pull_request trigger (default types, no edited) never ran ARC and the regression merged unchecked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Automated technical review by claude-fable-5-2 (independent, one round; not a human review or approval)Head reviewed: Result: 0 blocking findings, 3 non-blocking. The change does what it says. What I checked and found correct
Findings
ComplexityA one-line trigger change is the smallest thing that works. Not verified
|
Review round for this PR (Fable 5.2, non-blocking findings 1 and 2): an edit by a non-founder actor such as CodeRabbit started a run that cancelled the in-progress founder run and then skipped its only job. PR runs now also group by triggering actor. ready_for_review is dropped because the job has no draft condition, so it only added a rerun of the same head. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Resolution of the Fable 5.2 review round (#107 (comment)), fixed in head
|
PR #100 (model-alert dedupe) was retargeted to
release/native-0.1.10after all five of its commits were pushed. Thepull_requesttrigger inclosura-arc-ci.ymlused the default event types, which leave outedited, so ARC never ran and a real test regression merged (fixed later by #104).This adds
types: [opened, synchronize, reopened, edited, ready_for_review]. A title or body edit also reruns the full job. That's deliberate: skipping the job on non-base edits would post a skipped check on the same head, which could mask an earlier failure.Not in this PR: making "Voice + founder inbox (Linux ARC)" a required check on
release/native-*is a branch-protection setting, not a file change.Deploy: none
🤖 Generated with Claude Code