Setting local content exclusion rules #112982
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I'm not using github as a repository host, but another 3rd party product. Nevertheless I'd like to use the copilot business edition. This is possible in principle, but the content exclusion rules cannot be set this way. As described in this page, content exclusion rules can only be set via web interface per organization or per repository. I do not have access to my organizations settings (large company) and do not have a github hosted repo associated with my source code.
Is there some other way to set local content exclusion rules ? Like a
.copilotignore
file in the root folder or something similar ? This could be useful for other organizations with that setup, too, who have to distinguish between secret code (copilot off) and other code (copilot on).As a workaround, I can imagine to provide a VSCode extension which switches the copilot off every time a file from the 'secret' domain is being edited (by setting
github.copilot.enable{"*": false}
probably in thesettings.json
) . But it is unclear if this has the desired effect of enforcing a "no code being sent" policy, among other problems. So an official feature would be helpful here.So is there a way to set local content exclusion rules ?
EDIT: After thinking about this some more time, an alternative could be to add a second, empty github repo as an addition remote for my local git for the purpose of copilot configuration only. So I'm still pushing into the local non-github repo (origin), but an additional repo which is linked to my project can be used to enforce content exclusion rules. Could that work ?
Beta Was this translation helpful? Give feedback.
All reactions