ci: put the nightly packaged build on main, pinned to cline-dev - #17
Open
richardosborne14 wants to merge 1 commit into
Open
ci: put the nightly packaged build on main, pinned to cline-dev#17richardosborne14 wants to merge 1 commit into
richardosborne14 wants to merge 1 commit into
Conversation
The workflow existed only on `cline-dev`, and GitHub registers `schedule:` triggers exclusively from the repository's default branch — so its 03:00 cron was never registered and the nightly had never run once since it was written. Moving the file to `main` is necessary but not sufficient: `actions/checkout` defaults to the branch the workflow ran from, and `main` does not contain `.github/actions/setup`, so a default checkout would fail at that step every night and prove only that the alarm works. The checkout is therefore pinned — the schedule comes from `main`, the tree under test comes from `cline-dev`. The ref is a `workflow_dispatch` input defaulting to `cline-dev`, so a one-off packaging check against any branch or SHA needs no edit. Remove the pin when `cline-dev` merges to `main`. Otherwise byte-identical to the `cline-dev` copy, deliberately: a second gratuitous difference between the two would be a maintenance trap. 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.
Why
nightly.ymlhas acron: '0 3 * * *'schedule but has never run and never could. GitHub registersschedule:triggers only from the repository's default branch, and the workflow existed only oncline-dev. The file has to be onmainfor the cron to exist at all.Why it also needs the ref pin
Moving the file alone would make it worse than inert.
actions/checkoutdefaults to the branch the workflow ran from, andmaindoes not contain.github/actions/setup— so a default checkout would fail at that step every single night, mailing a failure daily and proving nothing except that the alarm works.So the checkout is pinned: the schedule comes from
main, the tree under test comes fromcline-dev. The ref is aworkflow_dispatchinput defaulting tocline-dev, so a one-off packaging check against any branch or SHA needs no edit.Remove the pin when
cline-devmerges tomain, or whenmainis retired.Scope
One file. Otherwise byte-identical to the
cline-devcopy, deliberately — a second gratuitous difference between the two copies would be a maintenance trap. Nothing else onmainis touched, and no product code is involved.Note on the required checks
mainrequires 6 status checks (Typecheck, Lint, Test (editor), Test (platform-node), Build, Check build artefacts). This PR adds a workflow file and changes no code, so any failure here is a pre-existing property of the year-oldmaintree rather than something this change introduced.🤖 Generated with Claude Code