Conflicting statements regarding GitHub Copilot content exclusion support in IDEs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- neovim, vim, vscode
- Domain
- documentation
Research direction
Open the linked content-exclusion article and compare the statement about unsupported Copilot modes with the IDE testing instructions for VS Code, JetBrains, Visual Studio, and Vim/Neovim. Confirm the intended support boundaries from the surrounding documentation, then revise the conflicting wording so the article consistently explains which experiences respect content exclusions.
Written by the indexing model from the issue text.
Description
Code of Conduct
- I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/copilot/how-tos/configure-content-exclusion/exclude-content-from-copilot
What part(s) of the article would you like to see updated?
Conflicting statements regarding content exclusion support in IDEs
There appears to be a contradiction in the GitHub documentation for Configuring content exclusion for your repository/organization/enterprise.
- Early in the page, it states:
"GitHub Copilot CLI, Copilot coding agent, and Agent mode in Copilot Chat in IDEs, do not support content exclusion."
This indicates that content exclusions do not work in IDEs when using Copilot through these modes.
- Later, the documentation provides instructions for testing content exclusions in IDEs (VS Code, JetBrains, Visual Studio, Vim/Neovim), implying that exclusions do work in IDEs, which contradicts the earlier statement.
Suggestion:
- Clarify which parts of Copilot respect content exclusions.
Additional information
No response
- Dominant language
- TypeScript
- Stars
- 20.9k
- Forks
- 68.8k
- Avg merge
- 15h 4m
- Merged PRs (30d)
- 103
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/docs
-
builder persona content
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
localization
Difficulty 2/5 1-2 days Newbie friendliness 72/100
-
builder persona
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
content localization
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
content localization
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Similar issues
-
S: triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
fix(errors): EHOSTUNREACH from a happy-eyeballs connect is reported as a resolver error (STAMP-80) Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
snapshot-labs/stamp#666 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
GauravKarakoti/SecureFlow#1070 · 1 comment ·
-
feature:Languages/Translations good first issue ready Web
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
digitalfabrik/integreat-app#4394 ·