Testing changes to content exclusions in your IDE

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

谁可以使用此功能？

存储库管理员和组织所有者可以管理内容排除设置。

具有存储库“维护”角色的人员可以查看该存储库的内容排除设置，但不能对其进行编辑。

订阅 GitHub Copilot Business 或 GitHub Copilot Enterprise 的组织。

本文内容

Note

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. 向 Copilot Chat 询问有关排除的文件的问题。 如果内容已成功排除，则 Copilot 将无法回答你的问题，并解释由于内容排除规则，某些文件已从对话中排除。

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. 向 Copilot Chat 询问有关排除的文件的问题。 如果内容已成功排除，则 Copilot 将无法回答你的问题，并解释由于内容排除规则，某些文件已从对话中排除。

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.