Can we enable PR process for each directory in the repository ?

[learnbalu]

Select Topic Area

Question

Body

Hi

I need some help on GitHub PR process.

We have a Github repository. Where we want to add Codereview process on multiple folders. Like, whenever there is some code changes in the directory it needs to have codeowners review process. And each folder wants to have different codeowners to review the PR process.
It's like, how can we enable PR process for multiple folders in the branch ?
Any help on this really appreciated

[sangampaudel530]

Hello @learnbalu

Yes, you can absolutely enable a Pull Request (PR) review process based on different directories in your GitHub repository by using a CODEOWNERS file.

Here's how you can do it:

1. Create a .github/CODEOWNERS file (or place it in the root or docs/ folder).

2. Define code owners for specific directories like this:

# Format: path @github-username or @team-name

/backend/        @backend-team
/frontend/       @frontend-devs
/scripts/ci/     @devops-team

3. Enable branch protection rules on the default or target branches:

• Go to Settings > Branches > Branch protection rules.
• Add a rule for the branch (e.g., main).
• Check “Require pull request reviews before merging”.
• Check “Require review from Code Owners”.

With this setup:

• Any PR that modifies files in /frontend/ will require a review from @frontend-devs.
• Likewise for other folders and their respective owners.

Notes:

• You can also assign individuals, not just teams.
• The users/teams must have write access to the repository.

GitHub CODEOWNERS Docs

Let me know if you'd like help setting up a sample CODEOWNERS file!

[learnbalu]

Hi @sangampaudel530 ,

Thank you for your response. If we add codeowners in Parent folder and subfolders, when we update some file in the subfolder it goes to while level of codeowners approval while pulling the request. Will it goes for both the codeowners approval or only in the subfolder codeowners approval?

[sangampaudel530]

Hi @learnbalu,

Thank you for the follow-up question, this is a great point!

In GitHub’s CODEOWNERS system, the most specific matching rule takes priority. Here’s how it works:

If you have code owners set for both a parent folder and its subfolder:

• When you update a file in the subfolder, only the subfolder’s code owners are required to review the PR.
• When you update a file in the parent folder (but not in the subfolder), only the parent folder’s code owners need to review.

If the PR includes changes in both the parent folder and the subfolder, then both sets of code owners will be required for review.

Example CODEOWNERS Setup:

# CODEOWNERS

/backend/          @backend-team
/backend/api/      @api-team

• Changes in /backend/api/ → only @api-team is needed.
• Changes in /backend/ (outside /api/) → only @backend-team is needed.
• Changes in both → both teams are required.

So in short:
If your change touches only the subfolder, it won't require the parent folder's approval, just the subfolder’s owners.

[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! 💬