-
Notifications
You must be signed in to change notification settings - Fork 334
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update CODEOWNERS #2868
Update CODEOWNERS #2868
Conversation
Reduce noise for docs-engineering, add us when you need us!
A documentation preview will be available soon.
Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with this. Maybe the best solution is to create a new team (I know, another new team) that has all of the codeowners for this repo listed out. We could then use the GitHub team assignment rules to only ping x number of people per PR. That would reduce noise for all.
I'm open to other ideas as well.
@bmorelli25 I'm not sure why I'm a code owner here either TBH 😄 |
@leemthompo codeowners were added in #2827. Here are the details without pinging everyone:
I'd like to keep you as a codeowner due to your commit history in this repo and your time zone. The new round-robin review format introduced in |
Congrats @leemthompo for being our docs MVP! Your reward is 100000 code reviews 🎉 |
@bmorelli25 thanks for the context, I missed that broadcast somehow 😃 |
Reduce noise for docs-engineering, add us when you need us!