fix: pull-v4-into-v4-next workflow — switch push trigger to schedule#21425
Merged
fix: pull-v4-into-v4-next workflow — switch push trigger to schedule#21425
Conversation
The workflow has never executed successfully (208 runs, 0 successes) because PR merges use GITHUB_TOKEN which triggers GitHub's anti-recursion protection. - Replace push trigger with schedule (every 15 min) + workflow_dispatch - Add early-exit check when v4-next is already up to date with v4 - Gate all merge/push/PR steps on needs_merge output
ludamad
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces #21424 — same fix but with the workflow in
.github/directly instead of.github-new/.The
pull-v4-into-v4-nextworkflow has 208 runs and 0 successes — it has never worked. PR merges (both manual and auto-merge) create push events using GitHub's internalGITHUB_TOKEN, and GitHub's anti-recursion protection prevents workflows triggered by those events from executing jobs.Changes:
on: push: branches: [v4]withon: schedule: cron '*/15 * * * *'+workflow_dispatchneeds_merge == 'true'Supersedes #21424
ClaudeBox log: https://claudebox.work/s/4acfe00daf0aeff1?run=1