Testing changes to content exclusions in your IDE

You can confirm your changes to content exclusions work as expected using your IDE.

¿Quién puede utilizar esta característica?

Los administradores del repositorio y los propietarios de la organización pueden administrar la configuración de exclusión de contenido.

Las personas con el rol de "Mantenimiento" para un repositorio pueden ver, pero no editar, la configuración de exclusión de contenido de ese repositorio.

Organizaciones con una suscripción a GitHub Copilot Business o GitHub Copilot Enterprise.

En este artículo

Note

  • La exclusión de contenido de GitHub Copilot in the CLI se encuentra actualmente en versión beta pública y está sujeta a cambios.
  • Las exclusiones de contenido se admiten actualmente en ciertos IDE. Consulte "About content exclusions for GitHub Copilot".

Propagating content exclusion changes to Visual Studio Code

In VS Code, you can wait up to 30 minutes to see the effect of a settings change, or you can manually reload content exclusion settings as follows:

  1. Access the Command Palette. For example, by pressing Shift+Command+P (Mac) / Ctrl+Shift+P (Windows/Linux).
  2. Type: reload.
  3. Select Developer: Reload Window.

Testing changes to content exclusions in Visual Studio Code

After content exclusion changes propagate to VS Code, the Copilot icon indicates when Copilot has been disabled by a content exclusion.

  1. Open a file that you expect to be affected by your content exclusions.

    If a Copilot content exclusion applies to this file, the Copilot icon in the status bar has a diagonal line through it.

  2. Hover over the Copilot icon. A popup message tells you whether an organization or the parent repository disabled Copilot for this file.

    Screenshot of the Copilot disabled popup in the VS Code toolbar.

  3. Optionally, you can also test content exclusions in Copilot Chat. Open the Copilot Chat window by clicking the Copilot Chat icon in the activity bar.

    Screenshot of the Copilot Chat icon in the Activity Bar.

  4. Hágale a Copilot Chat una pregunta sobre el archivo excluido. Si el contenido se excluye correctamente, Copilot no podrá responder a su pregunta y explicará que algunos archivos se excluyeron de la conversación debido a reglas de exclusión de contenido.

Propagating content exclusion changes to Visual Studio

In Visual Studio, you can wait up to 30 minutes to see the effect of a settings change, or you can manually reload the content exclusion settings by closing and reopening the application.

Testing changes to content exclusions in Visual Studio

In Visual Studio, the Copilot icon indicates when Copilot has been disabled by a content exclusion.

  1. Open a file that you expect to be affected by your content exclusions.

    If a Copilot content exclusion applies to this file, the Copilot icon in the status bar has a diagonal line through it.

  2. Hover over the Copilot icon. A popup message tells you whether an organization or the parent repository disabled Copilot for this file.

    Screenshot of the Copilot disabled popup in the VS Code toolbar.

Propagating content exclusion changes to JetBrains IDEs

In supported JetBrains IDEs, you can wait up to 30 minutes to see the effect of a settings change, or you can manually reload the content exclusion settings by closing and reopening the application.

Testing changes to content exclusions in JetBrains IDEs

In supported JetBrains IDEs, the Copilot icon indicates when Copilot has been disabled by a content exclusion.

  1. Open a file that you expect to be affected by your content exclusions.

    If a Copilot content exclusion applies to this file, the Copilot icon in the status bar has a diagonal line through it.

  2. Hover over the Copilot icon. A popup message tells you whether an organization or the parent repository disabled Copilot for this file.

    Screenshot of the Copilot disabled popup in the VS Code toolbar.

  3. Optionally, you can also test content exclusions in Copilot Chat. Open the Copilot Chat window by clicking the Copilot Chat icon at the right side of the JetBrains IDE window.

    Screenshot of the Copilot Chat icon in the Activity Bar.

  4. Hágale a Copilot Chat una pregunta sobre el archivo excluido. Si el contenido se excluye correctamente, Copilot no podrá responder a su pregunta y explicará que algunos archivos se excluyeron de la conversación debido a reglas de exclusión de contenido.

Propagating content exclusion changes to Vim/Neovim

If you are working in Vim/Neovim, content exclusions are automatically fetched from GitHub each time you open a file.

Testing changes to content exclusions in Vim/Neovim

  1. Open a file that you expect to be affected by your content exclusions.
  2. Begin typing. If GitHub Copilot no longer provides inline suggestions as you type, the file is excluded.