Copilot Spaces let you organize the context that Copilot uses to answer your questions. Sharing Copilot Spaces helps others:
- Avoid repeated explanations and handoffs.
- Stay aligned on how a system works or what’s expected.
- Learn from past work, documentation, and examples.
- Get better help from Copilot with grounded, curated context.
Use cases for collaboration
- Onboarding: Share a space with code, documentation, diagrams, and checklists to help new developers get started faster. Make other people editors so anyone can update the included resources.
- System knowledge: Create a space for a complex system or workflow (like authentication or CI pipelines) that other people can reference.
- Style guides or review checklists: Document standards and examples in a space that Copilot can reference when suggesting changes.
For example, a subject matter expert creates a space called “Accessibility Reviews” that includes your team’s internal accessibility checklist, product guidelines, and WCAG documentation. Developers can ask Copilot questions directly in the space to ensure they're following the latest guidelines in their work.
Sharing 空格
空格 can belong to a personal account or to an organization, and the sharing options differ depending on who the space belongs to.
Organization-owned spaces
Organization-owned spaces can be shared with other organization members, and you decide which level of access you want to grant other members (admin, editor, viewer).
Alternatively, you can choose to grant "No access" to organization members, and keep the space hidden.
To share a organization-owned space with others:
-
In the top right corner of the space, click .
-
To add specific users or teams, search for them with the search bar, then choose a role for the people you added.
-
Optionally, next to your organization's name, choose a base role for all other organization members.
- Viewers can use the space to ask questions and view the included attachments and instructions.
- Editors can update the space's attachments, description, name, and instructions, in addition to having all the permissions of viewers. However, editors can't update sharing settings or delete the space.
- Admins can update sharing settings or delete the space, in addition to having all the permissions of viewers and editors.
- No access means the space will be hidden from other organization members.
-
Optionally, click Copy link to copy the link to the space and share it with others.
Individual-owned spaces
Spaces belonging to a personal account can be shared publicly, shared with specific GitHub users, or kept private to the person who created the space.
To share an individual-owned space with others:
-
In the top right corner of the space, click .
-
To add specific GitHub users, search for them with the search bar, then choose a role for the people you added.
-
Optionally, to make the space public, under "General access", select Anyone with link. Then, copy the link to the space and share it with others.
注意
Publicly shared spaces are view-only by default, and viewers can only see sources that they have access to.
Accessing shared 空格
If you’re part of an organization that has shared spaces, you can access them in the Organizations tab on https://github.com/copilot/spaces.
You can also use organization spaces directly in your IDE by specifying the organization as the owner when accessing the space. For more information, see 使用 GitHub Copilot Spaces.