Github Copilot code review doesn't review most files

[tallior]

Select Topic Area

Product Feedback

Body

Just got access to Github Copilot code review, been tagging different PRs with it, but many times i am getting the following response:
Copilot reviewed 5 out of 15 changed files in this pull request and generated no comments.

The files that were not reviewed are code files (.cs file extension).
I would expect them to be reviewed. The reason provided is Evaluated as low risk

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

[MartynasObdeleven]

Same happens for us. We configured ruleset to add copilot, but all it does is leave messages like:

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

We use kotlin and swift in repo.

[guzelgun]

Yeah, my experience in a Python repository is similar.

Copilot reviewed 120 out of 120 changed files in this pull request and generated 1 comment.

I intentionally used it on a very large PR, thinking there would be plenty of opportunities for comments. Then, I tried it on a much smaller PR (just a few files) with some 101 traps I expected it to catch. No comments.

[BAGOMBEKA-JOB-DEV]

Hi there,

It sounds like you're encountering a situation where GitHub Copilot is not reviewing certain files in your pull requests, particularly .cs files, and labeling them as "Evaluated as low risk."

This behavior could be due to several reasons, and I’d be happy to suggest a few things to consider:

1. Risk Level Evaluation: GitHub Copilot might automatically skip files it deems "low risk" because it has identified that they don’t require an in-depth review. This could be files that don’t involve critical business logic or don’t introduce new complex features. While this could be annoying if you want a more thorough review, it’s meant to focus on the files that are likely to have higher impact.

2. File Type Handling: Sometimes, Copilot may have limitations in how it reviews certain file types or extensions. While .cs (C#) files are widely used, it's possible that Copilot’s current review capabilities are optimized for other types of code (such as JavaScript, Python, etc.). You might want to verify if Copilot supports deep analysis of C# or other similar files at this time.

3. Feedback on Copilot’s Behavior: It’s a good idea to send feedback to GitHub regarding how Copilot is handling certain file types like .cs. If this is a frequent issue that many users experience, GitHub may adjust its Copilot functionality to better support C# files or reduce the number of instances where files are skipped.

4. Manual Review for Low-Risk Files: For files that are considered low risk, you may need to manually review them, as Copilot focuses on files that might have higher complexity or are more prone to introducing bugs. This could be a good balance for teams who want a detailed code review on the critical parts but don’t necessarily need the same level of review on simpler or well-tested files.

5. Configuration and Settings: Check if there are any settings in Copilot or your project that can influence the review behavior. It's possible that your project or repository has specific configurations that are affecting how files are evaluated.

It’s worth experimenting with different configurations or providing GitHub with more feedback on your use case. I hope this helps explain what might be happening!

Best regards,
Bagombeka Job

[nnellanspdl]

Some relevant info:

About Copilot code review

Language Support: C#, Go, Java, JavaScript, Markdown, Python, Ruby, TypeScript

Limited scope

Copilot code review only supports a specific set of programming languages, and it is only designed to identify a limited, fixed set of code quality issues. To ensure that all relevant problems are identified and corrected, Copilot code review should be supplemented with careful human code review.