Repository navigation
Run CI nightly at 05:03 UTC and on demand - #149
Merged
Merged
Conversation
Add a schedule trigger (cron "3 5 * * *") and workflow_dispatch to ci.yml, keeping push and pull_request as they are. A main that goes red without a push (a dependency, a runner image, an expired date, the shared workflow) is then found the next morning. No job needs a guard: no job or step here, and nothing in the shared reusable workflow it calls, reads pull-request context or the event name, so a scheduled or dispatched run checks main exactly as a push to main does. Job names are unchanged, so the required checks are too. Co-Authored-By: Claude Opus 5.5 <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
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.
CI on
mainnow also runs every night, and can be started by hand.What changes
.github/workflows/ci.ymlgets two more triggers.pushandpull_requeststay as they are:A scheduled run tests the latest commit on the default branch. So if
maingoes red with no push behind it (a dependency, a runner image, an expired date, the shared workflow), we find out the next morning.Why no job needed a guard
We read every job and step in this workflow and in the reusable
cosyte/.github/.github/workflows/ci.yml@mainit calls. None of them readsgithub.event.pull_request.*,github.head_ref,github.base_ref,github.event.beforeorgithub.event_name, and none diffs against a PR base. So a scheduled or dispatched run checksmainthe same way a push tomaindoes today. No job was renamed or dropped, so the required checks (ci / actionlint,ci / verify (22, ubuntu-latest),ci / verify (24, ubuntu-latest)) are unchanged. A pull-request run checks exactly what it did before.Proof of the non-PR path
gh workflow run ci.yml -R cosyte/ccda --ref harness/28-nightly-run-of-ciwas accepted. That dispatch run passed on the head commit1ceaac4, all six jobs green: https://github.com/cosyte/ccda/actions/runs/39343763213.Gate run locally
All passed:
typecheck,lint,format:check,phi-scan,check:no-emdash,check:no-internal-refs,check:agent-notes,test:coverage,build,attw, and actionlint 1.7.7 over.github/workflows/*.yml.Notes
concurrencygroup is${{ github.workflow }}-${{ github.ref }}withcancel-in-progress: true. A scheduled run and a push run onmaintherefore share one group, and whichever starts second cancels the other. Both test the samemain, and a cancelled run reports no result in either direction. We left it alone because changing it is outside this change's scope.src/or in the published package moves.Harness-Task: 28
🤖 Generated with Claude Code