Trigger the rebase on merge, because the schedule never reaches a runner #1083
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1083
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/auto-rebase-on-merge"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#1071 was wrong, and the data now says so.
It found a real defect — a scheduled run entering a
cancel-in-progress: falsegroup and blocking every later tick — and fixing that was correct. But the scheduled runs still don't start:Both have their
action_run_jobrows. Neither has ever been handed to a runner, while pull-request and push runs are dispatched normally on the same instance, same runner, same labels. That is a dispatcher problem on this Forgejo build, not a concurrency one, and it is not fixable from this repository — which meansauto-rebasehas never run on schedule and never will until that is fixed upstream or on the host.pushis a trigger that demonstrably works, and it is the better trigger regardless: whenmainchanges, every open pull request is stale by definition. That is exactly the moment the queue needs rebasing, and it needs no cron to notice.The schedule stays as a safety net for a quiet
main, andworkflow_dispatchkeeps manual runs. Neither needs work: the script already defaultsbatchto 5 andsettleto 120 when the inputs are absent, and validates them numeric.Combined with
cancel-in-progress: true(#1071), a burst of merges leaves one rebase run standing rather than a queue of them.Once this lands, the queue rebases itself on every merge — which is what this workflow was supposed to be doing since #409.