Managing Copilot knowledge bases

Organization owners can create a knowledge base bringing together Markdown documentation across one or more repositories, and then organization members can use that knowledge base as context for Copilot Chat in GitHub.

En este artículo

About knowledge bases

Organization owners can create knowledge bases, bringing together Markdown documentation across one or more repositories. Organization members can then specify that knowledge base as the context for Copilot Chat in GitHub, Copilot Chat in Visual Studio Code, and Copilot Chat in Visual Studio.

When you ask a question in GitHub Copilot Chat with a knowledge base selected, GitHub Copilot will search the knowledge base for relevant information and synthesize a response.

For more information on how to use knowledge bases in Copilot Chat, see "Asking GitHub Copilot questions in GitHub" and "Preguntas sobre GitHub Copilot en el IDE."

Creating a knowledge base

You can create a knowledge base from a single repository or a selection of repositories. You can create a knowledge base using public, private, and/or internal repositories.

Knowledge bases you create will be accessible by all organization members with a GitHub Copilot Enterprise subscription. When an organization member uses a knowledge base as context in GitHub Copilot Chat, the response will only use data from repositories that the organization member has read access to.

  1. En la esquina superior derecha de GitHub, seleccione la foto del perfil y haga clic en Sus organizaciones.

  2. Junto a la organización, haga clic en Settings.

  3. In the left sidebar, click Copilot then click Knowledge bases.

  4. To the right of "Knowledge bases", click New knowledge base.

  5. In the "Name" field, enter a unique name for the knowledge base. Optionally, in the "Description" field, you can add a description for the knowledge base.

    Screenshot of the "New knowledge base" page.

  6. Under "Content", to see a full list of available repositories, click Select repositories.

    Screenshot of the "Select repositories" page. The "Select repositories" page is highlighted with a dark orange outline.

  7. To select a repository or repositories, click the checkbox next to the repository name. When you're finished selecting repositories, click Apply.

    Screenshot of the "Select repositories" page.

  8. Optionally, you can specify particular paths within the selected repositories for searches. When a search is conducted using the knowledge base, only the files located in those designated paths will be included in the results. For more information on specifying repository paths, see "Descripción de la sintaxis de GitHub Code Search"

    • Click Edit file paths.

    Screenshot of the list of selected repositories. The "Edit file paths" link is highlighted with a dark orange outline.

    • List the paths you want to include in the knowledge base, one path per line. When you're finished, click Apply.

  9. Click Create knowledge base.

Updating a knowledge base

Organization owners can update a knowledge base created in their organization.

  1. En la esquina superior derecha de GitHub, seleccione la foto del perfil y haga clic en Sus organizaciones.

  2. Junto a la organización, haga clic en Settings.

  3. In the left sidebar, click Copilot then click Knowledge bases.

  4. To the right of the knowledge base you want to edit, click .

  5. Make your desired changes to your knowledge base.

  6. Click Update knowledge base.

Deleting a knowledge base

Organization owners can delete a knowledge base created in their organization.

  1. En la esquina superior derecha de GitHub, seleccione la foto del perfil y haga clic en Sus organizaciones.

  2. Junto a la organización, haga clic en Settings.

  3. In the left sidebar, click Copilot then click Knowledge bases.

  4. To the right of the knowledge base you want to delete, click .

  5. In the "Confirm deletion" dialog box, review the information and click Delete.

Indexing repositories within a knowledge base

For more information about indexing, see "Indexing repositories for Copilot Chat"