"fix using copilot" no longer context aware?

[rpuls]

Select Topic Area

Question

Body

My project is filled with tens of thousand of require statements, and not a single import. My setup does not support import. Yet for some reason, copilot have started suggesting to fix 'not defined' with an import statement. This was not the case a few weeks (maybe a month) ago, it used to be able to follow the code pattern of my project. This new behavior is consisten, it suggest using import every single time.

I had similar experience with /tests that it would write unit tests using an assertion syntaxt that doesn't exist anywhere in my repo, despite haivng thousands unit tests all using same assertion library and same function calls. But this issue seems to have been fixed, because today it successfully generated two unit test with the syntaxt used across the repository.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬