Introduce component owners #4646
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: svrnm <[email protected]>
reyang
reviewed
Jun 10, 2024
chalin
approved these changes
Jun 10, 2024
|
FYI, dyladan/component-owners#19 needs to be fixed before we can apply this |
theletterf
approved these changes
Jun 11, 2024
Co-authored-by: Patrice Chalin <[email protected]>
Signed-off-by: svrnm <[email protected]>
|
FYI, dyladan/component-owners#19 is merged now (thanks @dyladan!) I will rework this PR and make it available asap |
Signed-off-by: svrnm <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
fixes #3581
This is a disruptive change, so when we roll it out we should monitor it carefully and roll it back/fix it quickly if anything misbehaves.
@dyladan to verify that, is component-owners compatible with github teams? In your examples I only saw individual usernames