Copilot review file limit (300) does not take into account content exclusions/.gitattributes

[jhowley89]

🏷️ Discussion Type

Product Feedback

Body

When reviewing Pull requests copilot has a file limit.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

However this limit does not take into account:

• content exclusions
• .gitattributes e.g. linguist-generated or linguist-vendored

It would make more sense for the limit to be applied after taking into account these exclusions. I often hit the limit when a PR includes a lot of packages updates (e.g. using yarn pnp/zero-installs)

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

[MahdiJDS]

This seems like a very reasonable improvement to how Copilot review limits are calculated.

Right now the file cap appears to be based on raw changed-file count, even when many of those files are effectively low-signal generated artifacts that reviewers — and often GitHub itself — already treat differently.

In repositories using:

• Yarn PnP / zero-installs
• vendored dependencies
• generated lockfiles
• compiled artifacts

it’s easy to hit the 300-file threshold without actually increasing the amount of meaningful review surface area.

Applying exclusions before enforcing the limit would make the review system much more aligned with real developer workflows.

Using existing repository signals like:

• .gitattributes
• linguist-generated
• linguist-vendored
• hidden/generated file settings

would also keep behavior consistent with the rest of the GitHub review experience.

An even better approach might be moving from:

• raw file count

to something more weighted, such as:

• effective reviewable files
• token/content size
• semantic complexity
• non-generated diff volume

That would likely produce much better results for monorepos and dependency-heavy projects where generated files can dominate the PR statistics while contributing very little actual review value.

This feels especially important if AI review tooling is expected to become part of normal enterprise CI workflows.

[varshakharenatpower]

Is there any way to increase the limit ?

[MahdiJDS]

As far as I know, there currently isn’t a user-configurable way to increase the Copilot PR review file limit.

The limit appears to be enforced server-side by GitHub/Copilot infrastructure, likely to control:

• token/context size
• review latency
• compute cost
• and overall review quality

That’s why the suggestion in this feedback makes sense — the real issue is less about raw file count and more about “effective reviewable surface area.”

For example, PRs with:

• vendored files
• generated artifacts
• lockfile churn
• Yarn PnP zero-install updates

can easily exceed the limit while containing relatively little human-authored logic.

A few practical workarounds that may help today:

• Split dependency updates into separate PRs
• Exclude generated/vendor files where possible
• Move large lockfile or package sync changes into isolated commits/PRs
• Use .gitattributes with linguist-generated=true anyway, since future tooling may eventually respect it
• Request Copilot review only after rebasing/squashing unnecessary churn

Long-term, a smarter limit based on:

• token size
• semantic diff complexity
• or post-filtered reviewable files

would probably work much better than a hard raw-file threshold.