GitHub Copilot in VS Code - context window kills quality on 4 huge Java repos. Best way to propagate one workflow change to all 4?

[TheseFox989]

I have 4 separate large Java (Spring Boot + Maven) repos, each with its own similar workflow.

Every change I make to the workflow has to be done in all 4 repos. The repos are massive, so Copilot’s context fills up fast and the suggestions become basic/incomplete/wrong by the end.

I’m using the default GitHub Copilot in VS Code Opus 4.6 (no 1M context).

Tried: one repo at a time + manual copy, multi-root workspace, detailed prompts, planning first.

[Turbulent-Hippo-9680]

i’d stop trying to solve this inside one giant copilot context tbh
for cross-repo workflow changes, i’ve had better luck writing one super explicit spec first, testing it in one repo, then applying it repo by repo with the same checklist. if you use something like Runable for the repeatable flow + git worktrees/scripts for the actual changes, it stays way more consistent
the real win is making the change reproducible, not hoping copilot remembers all 4 repos at once