Copilot Code Review ignores all custom instructions (copilot-instructions.md and path-specific .instructions.md files)

[Szer]

Select Topic Area

Bug

Copilot Feature Area

Copilot in GitHub

Body

Custom instructions have no observable effect on Copilot Code Review on GitHub.com. The reviewer always produces its default ## Pull request overview format and generic findings regardless of what instructions are provided.

What I've tried

1. Path-specific instructions in .github/instructions/code-review.instructions.md with applyTo: "**" and excludeAgent: "coding-agent" => no effect
2. Repo-wide instructions in .github/copilot-instructions.md with a dedicated ## Code Review Rules section containing domain-specific conventions => no effect
3. Both files simultaneously => no effect
4. Verified "Use custom instructions when reviewing pull requests" is enabled in repo settings → Copilot → Code review
5. Instructions follow the recommended format: short bullet points, concrete examples, clear headings, under 100 lines

What I observe

• Reviews always use the default template with no indication that instructions were read
• Domain-specific rules (e.g. F# conventions, Telegram bot patterns, Cyrillic handling) are never enforced
• The reviewer piles on findings and comments on trivial style - exactly what the instructions tell it not to do
• No reference to the instructions file appears anywhere in the review

Environment

• GitHub.com (not IDE)
• Instruction files: copilot-instructions.md, code-review.instructions.md

Expected behavior

Code review should incorporate the custom instructions - at minimum, check the domain-specific conventions listed in the instructions and avoid commenting on things the instructions say to skip.

Related

• https://github.com/orgs/community/discussions/184036 (same issue reported by another user)

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

[CyanoFresh]

same, we have a simple instruction on how to format the first message of the pull request, but Copilot completely ignores it every time