{"meta":{"title":"Creating GitHub Copilot Spaces","intro":"Create spaces to organize and centralize relevant content that grounds Copilot's responses in the right context for a specific task.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/how-tos","title":"How-tos"},{"href":"/en/copilot/how-tos/copilot-on-github","title":"Copilot on GitHub"},{"href":"/en/copilot/how-tos/copilot-on-github/customize-copilot","title":"Customize Copilot"},{"href":"/en/copilot/how-tos/copilot-on-github/customize-copilot/copilot-spaces","title":"Spaces"},{"href":"/en/copilot/how-tos/copilot-on-github/customize-copilot/copilot-spaces/create-copilot-spaces","title":"Create Copilot Spaces"}],"documentType":"article"},"body":"# Creating GitHub Copilot Spaces\n\nCreate spaces to organize and centralize relevant content that grounds Copilot's responses in the right context for a specific task.\n\n## Creating a space\n\n1. To create a space, go to [https://github.com/copilot/spaces](https://github.com/copilot/spaces?ref_product=copilot\\&ref_type=engagement\\&ref_style=text), and click **Create space**.\n2. Give your space a name.\n3. Choose whether the space is owned by you or by an organization you belong to. Organization-owned Spaces can be shared using GitHub’s built-in permission model.\n4. Click **Create Space**.\n5. Optionally, under the space name, add a description. The description does not affect Copilot's responses, but helps others understand the purpose of the space.\n\n > \\[!NOTE] You can change the name and description of your space at any time by hovering over them and clicking ****.\n\n## Adding context to a space\n\nYou can add two types of context to your space:\n\n* **Instructions**: Free text that describes what Copilot should focus on within this space. Include its areas of expertise, what kinds of tasks it should help with, and what it should avoid. This helps Copilot give more relevant responses based on your intent.\n\n For example:\n\n > You are a SQL generator. Your job is to take the sample queries and data schemas defined in the attached files and generate SQL queries based on the user's goals.\n\n* **Sources**: This context will be used to provide more relevant answers to your questions. Additionally, Spaces will always refer to the latest version of the code on the `main` branch of the repository.\n\n To add sources, click ** Add sources**, then choose one of the following options:\n\n * ** Add files and repositories**: You can add files, folders, and entire GitHub repositories. When you add a repository, Copilot searches its contents to find relevant information, but adding specific files or folders that are most relevant to your work will give you the best results. This can include code files, documentation, and other content that helps Copilot understand the context of your space.\n * ** Link files, pull requests, and issues**: You can paste the URLs of the GitHub content, including pull requests and issues.\n * ** Upload a file**: You can upload files directly from your local machine. This includes images, text files, rich documents, and spreadsheets.\n * ** Add text content**: You can type or paste free-text content, such as transcripts, notes, or any other relevant information that can help Copilot understand the context of your space.\n\n## Choosing repositories or files as context\n\nWhen adding sources to your space, you can choose to attach entire repositories or individual files. Understanding how each option works can help you get the best results from Copilot.\n\n* **Attach a repository**: When you attach a repository, Copilot doesn't load the entire project into memory. Instead, it searches the repository and retrieves only the most relevant content for your question. This is best for large-scale use cases, such as answering questions across all documentation in a repository.\n\n* **Attach individual files**: When you attach a file, its full contents are loaded into Copilot's context window and considered for every query in that space. This is best when you want Copilot to consistently prioritize a specific document or a small set of files.\n\n## Adding context as you're working\n\nYou can add files to a space directly from the code view on GitHub, so you don't need to break your flow when building context for your space.\n\n1. At the top of any file in the code view, click ****.\n\n \n\n2. From the dropdown, select the space you want to add the file to, or create a new space.\n\n## Next steps\n\n* For an overview of Copilot Spaces, see [About GitHub Copilot Spaces](/en/copilot/concepts/context/spaces).\n* To use Spaces in GitHub and your IDE, see [Using GitHub Copilot Spaces](/en/copilot/how-tos/provide-context/use-copilot-spaces/use-copilot-spaces).\n* To speed up development work with Spaces, see [Speeding up development work with GitHub Copilot Spaces](/en/copilot/tutorials/speed-up-development-work).\n* To share your space with your team, see [Collaborating with others using GitHub Copilot Spaces](/en/copilot/how-tos/copilot-on-github/customize-copilot/copilot-spaces/collaborate-with-others)."}