Repository navigation
Stop polling upstream every five minutes - #50
Merged
Merged
Conversation
The */5 schedule has never fired. It was registered on master at 08:21 UTC today and produced zero runs in the following six and a half hours, where it should have produced roughly 78. All 33 runs of this workflow so far came from pull_request (the earlier trigger) or from a manual dispatch. Five minutes is GitHub's minimum permitted interval, not a service level, and it is the first thing dropped when the scheduler is loaded. This repository is already starved: sync-upstream managed a single run in three days, 10.5 hours late, with the next window dropped outright. A public fork asking for 288 runs a day gets none of them. Every successful run of this workflow so far has been a manual dispatch, so make that the primary path and leave an hourly check off the top of the hour as a safety net for a manually-created upstream PR. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
The
*/5 * * * *schedule onpromote-to-upstream.ymlhas never fired. It reachedmasterwith the 08:21 UTC push today (9e79aa43) and produced zero runs in the following 6.5 hours, where it should have produced ~78. All 33 runs of this workflow so far came frompull_request(the earlier trigger, replaced in9e79aa43) or from a manual dispatch:Five minutes is GitHub's minimum permitted interval, not a service level, and it is the first thing dropped when the scheduler is under load. This repository is already starved —
sync-upstreammanaged a single run in three days, 10.5 hours late, with the next window dropped outright (see #48). A public fork asking for 288 runs a day gets none of them.Every successful run of this workflow so far has been a manual dispatch, so this makes
workflow_dispatchthe primary path and leaves an hourly check at37 * * * *as a safety net for a manually-created upstream PR.Note: the new schedule only takes effect once this reaches
master— GitHub readsscheduletriggers from the default branch only.🤖 Generated with Claude Code