You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[refactoring] Extract shared Go and Node CI toolchain setup into a shared component #77040
Go and Node setup steps are copied across 16 workflow files (setup-go) and 19 files (setup-node). Each copy pins the same action versions and cache settings, so every version bump has to be repeated by hand.
Apt install of make, then make deps-dev and npm ci in actions/setup/js: repeated in tidy.md, avenger.md, hourly-ci-cleaner.md, go-logger.md
Proposed shared component
.github/workflows/shared/ci-toolchain-setup.md with the setup-go and setup-node steps. Put the make and deps install steps behind a separate component, or leave them local, since not every workflow needs them. Keep shared/mcp/serena-go.md separate: it runs in pre-agent-steps and configures GOROOT and gopls itself.
Estimated impact
About 16 workflows, roughly 10-12 lines each: about 160-200 lines removed
One place to update action versions (setup-go v7.0.0 and setup-node v7.1.0 are currently copied)
Migration plan
Create shared/ci-toolchain-setup.md with the setup steps.
Canary on tidy.md and go-logger.md. Run make recompile and confirm the lock diff only moves setup steps.
Check step order: imported steps are appended in import order (pkg/parser/import_extract_steps.go). Confirm where they land relative to a workflow own steps.
Replace the copied blocks in the remaining workflows.
Skip upstream-managed workflows with a source: field; change those through gh aw update.
Activity
github-actions commentedon Nov 12, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, Copilot will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪
github-actions commentedon Nov 14, 2026
This issue was automatically closed because it expired on 2026-11-14T03:49:29.681Z.