Reduce GitHub Actions fan-out and storage#372
Conversation
📝 WalkthroughWalkthroughGitHub Actions workflows were restructured around shared cache warmers, consolidated pull-request validation, updated protected checks, shorter release artifact retention, selective deployment triggers, and revised backup-storage documentation. Supporting plans, specifications, and verification records document the rollout. ChangesGitHub Actions usage reduction
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant GitHubActions
participant warm-cache-linux
participant RustCache
participant linux-e2e
GitHubActions->>warm-cache-linux: Run on push
warm-cache-linux->>RustCache: Save shared Linux cache
GitHubActions->>linux-e2e: Run on pull request
linux-e2e->>RustCache: Restore shared cache
linux-e2e->>GitHubActions: Execute serial Linux validation steps
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/superpowers/plans/2026-07-18-github-actions-cost-reduction.md`:
- Around line 194-200: Update “Step 2: Run GitNexus change detection” to invoke
the mandated gitnexus_detect_changes() procedure instead of the direct node CLI
command, while retaining the existing scope, base, branch, and expected-change
verification requirements.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 25e990af-2de4-4e39-bd10-239eff1b0b41
📒 Files selected for processing (8)
.github/workflows/backup-relay-state.yml.github/workflows/ci.yml.github/workflows/fly-deploy.yml.github/workflows/release.ymlSESSION_LOG_2026_07_18.mddocs/superpowers/plans/2026-07-18-github-actions-cost-reduction.mddocs/superpowers/specs/2026-07-18-github-actions-cost-reduction-design.mdrequire-ci.sh
| - [ ] **Step 2: Run GitNexus change detection** | ||
|
|
||
| ```bash | ||
| node .gitnexus/run.cjs detect-changes --scope compare --base-ref origin/main --repo wire --branch chore/reduce-actions-usage | ||
| ``` | ||
|
|
||
| Expected: workflow, shell caller, docs, and no Rust execution-flow changes. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use the mandated GitNexus change detector before commits.
This plan substitutes a direct CLI invocation for gitnexus_detect_changes(), so it does not follow the repository’s required pre-commit verification procedure. As per coding guidelines, “Before committing, run gitnexus_detect_changes() to verify that changes affect only expected symbols and execution flows.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docs/superpowers/plans/2026-07-18-github-actions-cost-reduction.md` around
lines 194 - 200, Update “Step 2: Run GitNexus change detection” to invoke the
mandated gitnexus_detect_changes() procedure instead of the direct node CLI
command, while retaining the existing scope, base, branch, and expected-change
verification requirements.
Source: Coding guidelines
Deploying wireup-landing with
|
| Latest commit: |
7982102
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9408a457.wireup-landing.pages.dev |
| Branch Preview URL: | https://chore-reduce-actions-usage.wireup-landing.pages.dev |
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
SESSION_LOG_2026_07_18.md (1)
230-232: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winDo not claim the handoff policy was proven absent from this assertion.
The recorded failure is only
missing linux-e2e, which establishes that the consolidated job was absent. It does not, by itself, prove that the one-day handoff policy was absent. Record the retention assertion failure separately or narrow this sentence to the evidence shown.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@SESSION_LOG_2026_07_18.md` around lines 230 - 232, Revise the pre-change structural assertion statement in SESSION_LOG_2026_07_18.md to claim only that the consolidated linux-e2e job was absent, based on the recorded missing linux-e2e failure. Remove the claim that this assertion proved the one-day release handoff policy was absent, or document that policy’s retention assertion failure separately.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@SESSION_LOG_2026_07_18.md`:
- Around line 252-255: Correct SESSION_LOG_2026_07_18.md lines 252-255 to state
that require-ci.sh was prepared but not executed, while retaining the
prerequisite that all six contexts must be green. Update lines 287-289 to state
that live branch protection was not changed and the migration remains deferred.
---
Outside diff comments:
In `@SESSION_LOG_2026_07_18.md`:
- Around line 230-232: Revise the pre-change structural assertion statement in
SESSION_LOG_2026_07_18.md to claim only that the consolidated linux-e2e job was
absent, based on the recorded missing linux-e2e failure. Remove the claim that
this assertion proved the one-day release handoff policy was absent, or document
that policy’s retention assertion failure separately.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 33c8eea5-5652-45d5-9e44-ac49521cd4b9
📒 Files selected for processing (1)
SESSION_LOG_2026_07_18.md
| - `require-ci.sh` contains the six replacement contexts. It was executed only | ||
| after pull request #372 proved all six new check names green. Post-update | ||
| verification showed strict checks and admin enforcement still enabled, force | ||
| pushes and deletions still disabled, and the pull request clean/mergeable. |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Correct the documented rollout state. The session log claims that require-ci.sh ran and branch protection changed, while the supplied PR objective says the migration caller was updated but not executed and live branch protection remained unchanged.
SESSION_LOG_2026_07_18.md#L252-L255: state thatrequire-ci.shwas prepared but not executed; retain the prerequisite that all six contexts must be green.SESSION_LOG_2026_07_18.md#L287-L289: state that live branch protection was not changed and that the migration remains deferred.
📍 Affects 1 file
SESSION_LOG_2026_07_18.md#L252-L255(this comment)SESSION_LOG_2026_07_18.md#L287-L289
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@SESSION_LOG_2026_07_18.md` around lines 252 - 255, Correct
SESSION_LOG_2026_07_18.md lines 252-255 to state that require-ci.sh was prepared
but not executed, while retaining the prerequisite that all six contexts must be
green. Update lines 287-289 to state that live branch protection was not changed
and the migration remains deferred.
1 participant
Summary
Verification
actionlint .github/workflows/*.ymltest-env/run.shRollout
Do not run
require-ci.shuntil this PR shows all six replacement contexts green. This PR does not mutate live branch protection or service state.Summary by CodeRabbit
linux-e2ejob and adjusted required check contexts accordingly.