Stop the release cron waking main every few hours - #113
Merged
Merged
Conversation
The `*/10` schedule on scheduled-merge.yml had nothing to merge and still posted two check notifications on `main` per tick -- "merge success on main" is Discord rendering the `merge` job, not a merge -- which over a day is most of what the #github channel said. It was never a working scheduler either: measured here over 577 minutes it delivered 2 of 58 expected runs, the first 4h48m late. The Delta systemd timer (roles/release_scheduler) is what fires this workflow now, so the trigger goes rather than shrinking to an hourly cron that would be both quieter and no more dependable. A run now means there is a labelled pull request to consider. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VT3WmtV3qBRxmTKN8ABMyQ
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
1 participant
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.
#githubhas been getting a pair of "[Scalene] merge success on main" /"checks success on main" messages every few hours since #110 landed. Nothing
was merging:
mainhasn't moved since #112 on 2026-09-11, and every one ofthose runs ends with
No open pull requests carry the "scheduled-merge" label.The alarming wording is Discord rendering the workflow's
mergejob — acheck run — and scheduled runs attach to
main's head SHA, so each empty tickposts two check notifications on the default branch.
The
schedule:trigger goes rather than dropping to an hourly cron, becauseit was not doing the job it was kept for. Measured on this repository over 577
minutes,
*/10delivered 2 of 58 expected runs with the first 4h48m late — a00:10 release would have merged near 04:00. What actually fires this workflow
is the systemd timer on Delta (
roles/release_scheduler, triangle-infrastructure#3), which polls once a minute and dispatches it; the merge rules all still live
here and apply to every run.
This depends on triangle-infrastructure#3 being merged and the timer
deployed. Until then, a scheduled release needs a manual dispatch of this
workflow — worth landing that one first, or together with this.
The rest is documentation catching up: the README's "wakes every ten minutes"
and "Timing accuracy" section now describe the timer, and say not to put the
cron back.
Verified
scheduled-merge.ymlstill parses as YAML and that the only triggerleft is
workflow_dispatchwith itspr/dry_runinputs.🤖 Generated with Claude Code
https://claude.ai/code/session_01VT3WmtV3qBRxmTKN8ABMyQ