Repository navigation
Randomize scheduled workflow crons for cookiecutter-generated projects - #318
Merged
Merged
Conversation
Projects stamped from the cookiecutter template now get random cron schedules (minute 0-59, hour 13-17 UTC, day 0-6) for ci_tests and pre-commit-update workflows, avoiding thundering-herd on GitHub Actions. Hidden _ci_tests_cron and _pre_commit_update_cron parameters allow CI to pin specific schedules without prompting maintainers. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ednolan
requested review from
bretbrownjr,
camio,
dietmarkuehl,
neatudarius,
steve-downey and
wusatosi
as code owners
March 15, 2026 18:12
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.
Projects stamped from the cookiecutter template now get random cron schedules (minute 0-59, hour 13-17 UTC, day 0-6) for ci_tests and pre-commit-update workflows, avoiding thundering-herd on GitHub Actions. Hidden _ci_tests_cron and _pre_commit_update_cron parameters allow CI to pin specific schedules without prompting maintainers.