.png){kind=small}
Project 11 — Multi-Repo Search Assistant using Spaces
Curate a Space across 3 repos, answer cross-repo questions.
What You Will Learn
- Curate a multi-repo Space.
- Answer cross-repo questions.
- Trace dependencies across repos.
- Measure search time saved.
- Document for team.
Why This Matters
Multi-repo questions ('which repo uses the deprecated API?') take hours of manual searching. A Space curates multiple repos and answers in seconds.
Concept Explained
Create a Space with 3+ repos. Ask cross-repo questions. Copilot searches all repos, returns grounded answers with citations.
How It Works
Create a Space. Add 3+ repos. Ask questions like 'which repos import library X?' or 'where is function Y defined across these repos?'. Verify citations.
Step-by-Step Tutorial
1. Pick repos
3+ repos with cross-cutting concerns.2. Create Space
github.com/copilot/spaces → New Space. Add repos.3. Test with cross-repo questions
'Which repos use the v1 API?' 'Where is User type defined?'4. Verify citations
Open cited files in each repo. Confirm.5. Share with team
Document for cross-repo work.Real-World Example
A platform team had 5 microservices that shared types. Asking 'where is User defined across these repos?' used to take 30 minutes of manual searching. With a Space: 30 seconds. Saved 5+ hours/week across the team.
Example Prompts / Commands / Code
# Cross-repo dependency:
@workspace Which of these repos import the deprecated 'old-auth' library?
# Type definitions:
Where is the User type defined across these repos? List each repo and file.
# API usage:
Which repos call the /v1/users endpoint? List each call site.
# Pattern usage:
Which repos use the Repository pattern? List examples.
Space: Platform Team Multi-Repo
Purpose: Cross-repo questions across platform services.
Repos:
1. github.com/team/auth-service
2. github.com/team/user-service
3. github.com/team/order-service
4. github.com/team/shared-types
Test questions:
- 'Where is the User type defined?'
- 'Which services import shared-types?'
- 'What's the auth flow across services?'
- 'Which repos have tests for the User type?'
Common Mistakes
- Adding too many repos — dilutes signal.
- Not verifying citations across repos.
- Forgetting Spaces require Pro+.
- Using Space for single-repo questions — overkill.
Best Practices
- Curate 3–5 repos with real cross-cutting concerns.
- Verify citations across all repos.
- Use for cross-repo questions only.
- Document for team cross-repo work.
- Measure search time saved.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Answers cite wrong repo | Verify file:line. Re-ask with more specific question. |
| Space is slow | Reduce repos. Or split into multiple Spaces. |
Practical Exercise
Your Turn
Create a multi-repo Space with 3 repos from your work (or open source). Ask 5 cross-repo questions. Verify citations.
Professional Challenge
Document 10 common cross-repo questions your team asks. Curate a Space that answers all 10. Share with team.
Key Takeaways
- Multi-repo Space answers cross-repo questions in seconds.
- Curate 3–5 repos with cross-cutting concerns.
- Verify citations across all repos.
- Use for cross-repo only; @workspace for single-repo.
- Document for team.
Frequently Asked Questions
How many repos can a Space hold?
Can I share the Space?
Further Reading
Official References
SEO Metadata
SEO title: Project 11 — Multi-Repo Search Assistant using Spaces
Meta description: Curate a Space across 3 repos, answer cross-repo questions.
Primary keyword: project 11
Secondary keywords: project 11 — multi-repo search assistant using spaces
Search intent: Informational
URL slug: /project-multi-repo-search-assistant-spaces
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Intermediate, Project, Spaces, Multi-Repo, Search, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Project 11 — Multi-Repo Search Assistant using Spaces
Comments
Comments
Post a Comment