ci: [REUSABLE HARNESS — DO NOT MERGE] dry-run every workflow on one branch - #89
Draft
krlmlr wants to merge 1 commit into
Draft
ci: [REUSABLE HARNESS — DO NOT MERGE] dry-run every workflow on one branch#89krlmlr wants to merge 1 commit into
krlmlr wants to merge 1 commit into
Conversation
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y-verify
branch
2 times, most recently
from
July 22, 2026 06:22
77462d6 to
0c4173b
Compare
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y-verify
branch
3 times, most recently
from
July 22, 2026 08:27
7d38d98 to
a054070
Compare
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y
branch
from
July 22, 2026 09:09
2cd5cbc to
e8f4f09
Compare
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y-verify
branch
from
July 22, 2026 09:09
a054070 to
87b0a46
Compare
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y
branch
from
July 22, 2026 09:36
e8f4f09 to
f12bbb7
Compare
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y-verify
branch
from
July 22, 2026 09:37
87b0a46 to
5513c3e
Compare
krlmlr
changed the title
krlmlr
changed the title
Comprehensive dry-run harness: every workflow triggers on push to this branch and all side effects are disabled, so the full CI suite can be seen running green on Ubuntu 26.04 (incl. arm64) without mutating anything. - rcc: renamed to "rcc-dryrun" so the default-branch rcc-status / commit-suggest (which key on workflows: [rcc]) never fire for this branch; disabled the commit-back, all commit-status posts and pkgdown deploy (build still runs); enabled the rcc-suggests "without DBI" job. - Added push triggers for this branch to: rcc dev, pkgdown, copilot-setup, fledge, lock, pr-commands, commit-suggest, format-suggest, rcc-status, revdep. - Disabled side effects: pkgdown deploy, fledge (version bump / branch push / PR create+merge / release), lock-threads, reviewdog suggester, snapshot-update PR, Codecov upload. revdep gets setup-r so its matrix step runs (empty matrix -> heavy check job skipped). Event-driven jobs (pr-commands, commit-suggest) skip cleanly on push. DO NOT MERGE: exists only to exercise CI with no side effects. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Tw1nB3SzehmtvTjkwmc2v
krlmlr
force-pushed
the
claude/ubuntu-26-arm64-gha-ezzy7y-verify
branch
from
July 22, 2026 17:01
5513c3e to
a754a1c
Compare
Contributor
Author
|
Session link: https://claude.ai/code/session_018Tw1nB3SzehmtvTjkwmc2v |
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
2 participants
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.
Runs every workflow in the repo on a single push, with all side effects disabled — a safe way to watch the whole CI suite go green before merging a CI change. First built to validate the Ubuntu 26.04 / arm64 change (now merged); retargeted to
mainand kept as a reusable harness.How it works
On every push to the head branch, each workflow is triggered — push events use this branch's workflow files, unlike
workflow_run/schedule/pull_request_target, which always use the default branch — and every mutating step is neutralised:rcc(renamedrcc-dryrun)ubuntu-26.04-arm+ thercc-suggests"without" jobrcc devpkgdowncopilot-setupfledgelockformat-suggestrevdepsetup-radded so its Rscript runs)pr-commandsdocument/style/mergerun withpr-fetch/pr-push/PR-create disabled;finishno-oprcc-status,commit-suggestworkflow_run/PR context)rccis renamed torcc-dryrunso the default-branchrcc-status/commit-suggest(keyed onworkflows: [rcc]) can't fire and post statuses/comments.How a future session reuses this
The only per-reuse change is the branch-name token. This branch hard-codes its own head-branch name (
claude/ubuntu-26-arm64-gha-ezzy7y-verify) in every push trigger and in thercc-suggestsif.git switch -c <NEW-VERIFY-BRANCH> <your-branch>..github/diff — it is exactly the harness patch (everything else is already onmain):git diff main..claude/ubuntu-26-arm64-gha-ezzy7y-verify -- .github | git applygit grep -l 'claude/ubuntu-26-arm64-gha-ezzy7y-verify' -- .github | xargs sed -i 's#claude/ubuntu-26-arm64-gha-ezzy7y-verify#<NEW-VERIFY-BRANCH>#g'<NEW-VERIFY-BRANCH>, open a draft PR. Every push re-runs the full dry-run.Everything else (the
rcc-dryrunrename, theif: falseside-effect guards, therevdepsetup-r+ empty-matrix fix, the covr/Codecov guard) is generic and needs no change.🤖 Generated with Claude Code