Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a workflow that will request review based on file changes.
This works independently with CODEOWNERS.
I added myself and Cal to be added as reviewers for the migrations file as an example.
Note: we can also request team (e.g: core-backend-components) but it needs some more configuration, I'll make it work once we decide this is something we want.
But how is it different from CODEOWNERS?
With codeowners, it requests reviewers for the most specific pattern. An example:
src/**
src/metabase/pulse/**
Then if there are changes to
src/metabase/pulse/core.clj
then only Ngoc is added as reviewer. Cam is excluded. But in some cases, we want both Ngoc and Cam to be added.Read more here