Migrating Copilot Knowledge Bases to Copilot Spaces
Allison introduces the new Copilot Spaces feature on GitHub, offering a streamlined migration path for existing Copilot knowledge bases, with improved security, organizational management, and support for collaborative development workflows.
Migrating Copilot Knowledge Bases to Copilot Spaces
With the upcoming sunset of Copilot knowledge bases on November 1, 2025, GitHub has launched Copilot Spaces, a new platform for managing and sharing organizational knowledge. Users can now easily migrate their legacy knowledge bases by selecting the Convert to Space button for each resource they wish to convert.
Security by Design
- Each migrated knowledge base becomes an individual Copilot Space.
- Only organization admins have initial access, allowing for testing and secure management.
- Admins can promote Spaces to wider organizational access when ready, ensuring better control and compliance.
How Teams Use Copilot Spaces
- Code Generation: Automate generation of code that adheres to team security, API, and documentation standards.
- Knowledge Sharing: Centralize resources such as SQL/KQL queries, telemetry schemas, and best-practice authentication documentation.
- Onboarding: Fast-track new developers by providing instant access to curated project documentation and institutional knowledge.
- Project Planning: Centralize product requirement documents (PRDs) and key architectural decisions to streamline planning and issue creation.
Getting Started
- Try Copilot Spaces: Visit github.com/copilot/spaces, now available on github.com for all Copilot users.
- Feedback: Join the community discussion or use the in-product Give feedback button.
- Documentation: Learn more at Copilot Spaces Documentation.
- Billing: Copilot Spaces uses the same billing model as Copilot Chat.
For those managing critical project and organizational knowledge on GitHub, Copilot Spaces offers a secure, collaborative, and structured way to centralize resources and streamline workflows.
This post appeared first on “The GitHub Blog”. Read the entire article here