Skip to content

Run CI when a pull request is retargeted to main - #27

Merged
baijum merged 1 commit into
mainfrom
ci-pr-edited-trigger
Sep 12, 2026
Merged

baijum merged 1 commit into
mainfrom
ci-pr-edited-trigger

Conversation

@baijum

@baijum baijum commented Sep 12, 2026

Copy link
Copy Markdown
Member

Same change as kaappi.github.io#57, for the same reason.

The pull_request trigger had only a base-branch filter, so it fired on the default activity types (opened, synchronize, reopened). A stacked PR that GitHub retargets to main when its base merges is an edited event: no run starts, and the required test check sits pending until a push or a close/reopen forces one. Listing the types explicitly with edited included makes the retarget start the run on its own.

edited also fires on title and body edits. Those extra runs rebuild Kaappi from source, about two and a half minutes each, which is the trade-off. The branches: [main] filter is unchanged.

🤖 Generated with Claude Code

Same change as kaappi.github.io#57. With only a base-branch filter the
pull_request trigger fires on the default activity types, so a stacked
PR that GitHub retargets to main when its base merges (an edited event)
starts no run, and the required test check sits pending with nothing
behind it. Listing the types with edited included makes the retarget
start the run on its own. Title and body edits also count as edited;
those extra runs are the price, and the suite is quick.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Signed-off-by: Baiju Muthukadan <baiju.m.mail@gmail.com>
@baijum
baijum merged commit 5723e02 into main Sep 12, 2026
3 checks passed
@baijum
baijum deleted the ci-pr-edited-trigger branch September 12, 2026 05:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant