Copilot Chat sends full active file even when implicit context is disabled?

[fkraemer-coder]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I am trying to understand whether this is intended behavior or a bug.

I asked Copilot Chat a small Python question and intentionally provided only a tiny function snippet, because the full file is around 2000 lines and not needed for the question.

However, the debug logs show that the request payload still included the active file content as an additional attachment, not just my selected snippet. My relevant settings are:

github.copilot.chat.agent.currentEditorContext.enabled = false
chat.implicitContext.suggestedContext = false
chat.implicitContext.enabled.panel = never

and the request:

What would be considered better: Having the default as "" or having Optional[str] = None in this case and adding a guard against none?
<attachments>
<attachment id="my_file.py">
Excerpt from my_file.py, lines 687 to 691:

def _resolve_path(my_path: str = None) -> Path:
        path = Path(my_path)
        if path.exists():
            return path
        else:
            raise FileNotFoundError(f"Path {my_path} does not exist.")

</attachment>
<attachment filePath="./my_file.py">
User's active file for additional context:
The full 2000 line python file.

Am I missing a setting to disable this? I have my file open, but the settings above should prevent it from being sent.

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