Context Passing is back, with GitHub Copilot Extensions! 🚀

[nhu-do]

Context Passing with GitHub Copilot Extensions now available in Public Preview! 🌟

Context passing is back! 🎊 Starting today, you can pass context to an extension from your favorite editor, helping the extension better understand your work environment to provide tailored responses.

This builds on GitHub Copilot’s ability to understand your work context depending on where you're using extensions. This happens automatically when you interact with an extension, requiring your explicit authorization through GitHub App permissions for use in any organization-owned repository.

Worried about your content exclusions? Don’t be, they are respected with context passing. Any .env file and files listed in your content exclusions settings will not be passed to any extension.

💻 Available contexts by editor

Editor	client.file	client.selection	github.repository	github.current-url	Additional contexts
Visual Studio Code	✔️	✔️	✔️	X	Respository owner and branch
Visual Studio	✔️	✔️	✔️	X	Respository owner and branch
GitHub.com	X	X	✔️	✔️	Repository information and other GitHub resources
GitHub Mobile	X	X	X	✔️	X

To prevent contexts in the above table from being shared, exit the context window for the applicable context. For example, if you’re working on a file that you do not want extensions to pull context from, simply exit the page. Editors may offer similar capabilities in their user experience.

📈 Requirements for users

• Access GitHub Copilot. Understand the options best suited for you.
• Install Copilot Extensions.
• Explicitly authorize for use in any organization-owned repository. You can do this via GitHub App permissions.

🤖 Requirements and best practices for builders

The Copilot Extensibility platform will automatically handle messaging when implicit and explicit context is unavailable or unauthorized. To enable context passing, extension builders are required to request permissions from users.

• Clearly communicate what context you need and what you need it for.
• Implement appropriate error handling for unavailable context that your own application logic and API calls.
• In the event context is unavailable, provide value where possible without this data.
• Request only the minimum required permissions for your extension.

💡 Questions or feedback? Visit our user feedback forum and join the discussion below!

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐