[ci] update codeowners #6542
Merged
[ci] update codeowners #6542
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
jameslamb
requested review from
guolinke,
shiyu1994,
jmoralez and
borchero
as code owners
|
I would be honored! To be honest, I'm afraid that I won't be active as much as I was in the past 😢 |
|
Thanks very much! Totally understand, we'll be happy for any time you're able to spend helping out here. |
|
As always only kind words from you, James! Thanks a lot! 🤗 |
guolinke
approved these changes
Jul 16, 2024
|
@StrikerRUS very excited to have you back! |
|
@guolinke Hi! 👋 |
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.
Proposes adding @StrikerRUS back to
CODEOWNERS, to be automatically added as a reviewer on PRs.@StrikerRUS since #5998, we've stopped having specialization in the
CODEOWNERSfile (no more "these people are R reviewers", "these people are Python reviewers", etc.) and switched to just having everyone added to every PR by default. That more closely matched the current state of the project and abilities/interests of the reviewers.If you don't want to be added as a reviewer on every PR by default let me know, and we can close this.