Copilot code review excludes SAP Commerce / Hybris source files under bin/custom/**

[dcustic]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot in GitHub

---

Hi everyone,

we are using GitHub Copilot code review in an SAP Commerce / Hybris project and ran into a limitation with automatic PR reviews.

In SAP Commerce / Hybris projects, first-party source code commonly lives under paths like:

bin/custom/ocm/...

For example:

bin/custom/ocm/ocmstorefront/web/src/com/example/storefront/controllers/...

However, Copilot code review appears to exclude files matching:

**/bin/**/*

Because of this, automatic Copilot review fails with:

Copilot wasn't able to review any files in this pull request.

We confirmed that:

• the PR has a normal diff
• the PR is not from a fork
• automatic Copilot review settings are enabled
• rulesets are configured correctly
• other repositories in the organization work
• a test PR changing files outside bin/ works
• the same kind of code change under bin/custom/... is skipped
• custom instructions do not help, because the files seem to be excluded before review starts

We also tried adding instructions such as:

# Copilot review instructions

This is an SAP Commerce / Hybris repository.

Important:
- `bin/custom/ocm/**` contains first-party production source code.
- Do not treat `bin/custom/ocm/**` as generated output.
- Review Java, Vue, JavaScript, TypeScript, HTML, and SCSS files under `bin/custom/ocm/**`.
- The `bin/custom/ocm/**` path is the main application source tree.

But Copilot still does not review these files.

This seems problematic for SAP Commerce / Hybris repositories, where bin/custom/** is not generated build output but the normal location for custom application source code.

Question

Is there any supported way to override or allowlist excluded paths such as:

bin/custom/**

for Copilot code review?

If not, could GitHub consider adding a repository-level allowlist or respecting custom instructions / .gitattributes for this case?

Thanks!

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