I loved copilot with VSCode but with VS2022 I'm concerned #164141
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Copilot Feature Area
Visual Studio
Body
Am I doing something wrong?
I am a paying customer.
Github Copilot for VSCode was excellent! So easy to use, well integrated.
But now, Github Copilot for VS2022 wants really bad access to my repositories!
In VS2022, when I click on "Github Copilot" then "Sign in to use copilot" it redirects me to a website saying:
This application will be able to read and write all public and private repository data. This includes the following:
Code
Issues
Pull requests
Wikis
Settings
Webhooks and services
Deploy keys
Collaboration invites
I can't do that! Why could it possibly want write access to my code?!
Please help, I must be doing something wrong.
Beta Was this translation helpful? Give feedback.
All reactions