-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[8.x] Override all codeowners #197710
[8.x] Override all codeowners #197710
Conversation
We want to preserve CODEOWNERS for other automation, and to reduce the number of merge conflicts on backports, but avoid notifications on backports where these reviews aren't required. This assigns kibanamachine as the owner of all files.
Pinging @elastic/kibana-operations (Team:Operations) |
Converting to draft for the moment, I need to run some tests on assignment when kibanamachine is the PR author. |
⏳ Build in-progress, with failures
Failed CI StepsTest Failures |
Glad there was a test. I see at least 4 different implementations of CODEOWNERS parsing that will need to be updated to skip the last entry. I'll revisit this starting from main. |
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
Temporary removal of `CODEOWNERS` to stop review notifications until #197710 issues are resolved.
Closing in favor of #199686 |
On older release branches we want to preserve CODEOWNERS for other automation, and to reduce the number of merge conflicts on backports.
We also don't want reviewer assigned and the subsequent notifications sent when these reviews are not a requirement.
This assigns kibanamachine as the owner of all files.