I have GitHub Copilot Pro through my org and I work across multiple projects (new features, bug fixes, daily maintenance). I’m not looking for basic “how to use Copilot” tips—I’m trying to understand how people keep it effective over the long run. Previously I used tools like Claude Code with a strong “memory bank” / project‑memory model and I’m very comfortable with that concept. Now I want to lean more on GitHub Copilot Pro and I’m unsure what the best patterns are for: • Keeping consistent project context over months (architecture, conventions, decisions). • Growing a codebase with new features while Copilot stays aligned. • Daily bug‑fix and maintenance workflows when you juggle several repos. • Any practical “do this, don’t do that” for long‑running Copilot usage. If you have concrete workflows, repo setups, or examples (even high‑level), I’d love to hear how you structure things so Copilot stays helpful instead of becoming noisy over time. submitted by /u/SpecialistLove9428
Originally posted by u/SpecialistLove9428 on r/ClaudeCode
You must log in or # to comment.