Generating docstrings using /doc for native idiome

[fllsilva]

Select Topic Area

Product Feedback

Body

I'm using the Github Copilot extension for VSCode, and I recently signed up for a subscription plan.

The native language of my VSCode IDE is pt-BR.

When I chat with Github Copilot, it answers me in my language and generates the codes in my language as well.

However, when I use the command line chat (Ctrl+I), for example, asking it to generate the code documentation (/doc), it generates all the documentation in English. In order for it to generate the documentation in my language, I need to enter the prompt "/doc pt-br" every time I want to generate the documentation.

Is there a way to change this to the default? I've already reviewed all the available settings in the extension and I haven't been able to solve this problem.

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