GitHub Copilot content exclusion does not work on PhpStorm with WSL on Windows

[martin-kotras-invia]

Select Topic Area

Bug

Body

Hello,
we are using GitHub Copilot content exclusion in our organization but it seems like it does not work on Windows properly. We have there excluded files like this:

"*":
  - "**/.env"

This works on VS code and PhpStorm on Linux, but does NOT work in PhpStorm or VS code on Windows when the file is located in WSL. It might or might not be because of different path separators (forward slash vs backslash) but we weren't successful with these either:

"*":
  - "**\\.env"
  - ".env"
  - "app\\.env"

The Copilot is still able to answer and use the excluded files on Windows and is not crossed out in the status bar:

Could you please fix it so the content exclusion works on Windows as well or provide use with information how can we write the glob patterns so it also works on Windows?

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