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.
On the way to an improved PR review process, this PR adds a code owner file.
The files listed below are assigned to the developers who have written the most code for them and know them best. All other files have too many different authors, but the ultimate goal would be to assign a code owner to most scripts over time.
Being the code owner simply means, that there is a mark in GitHub for each assigned file. So that the author/responsible person can be identified without having to go through a lot of git blame.
At the same time, the code owner is automatically added as a reviewer to PRs related to that code.
Which means the code owner will be responsible for the first review from now. Small changes can also be merged and for bigger changes, a maintainer will review again and merge the PR.
More informations on Code owners in GitHub can be found here.
For those in the first batch, please give me a thumbs up if you agree!
@amos-schledorn
@LukasFrankenQ
@toniseibold
@Irieo
@p-glaum
@bobbyxng
@lisazeyen
@FabianHofmann
And always feel free to take any other "ownership" 🧙
Click me