-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[chore] add section for components looking for new code owners #33397
[chore] add section for components looking for new code owners #33397
Conversation
Testing result LucaLanziani#2 |
Add a section to the weekly report with the list of components looking for code owners based on the `status.codeowners.seeking_new` property of the metadata.yaml file.
3340770
to
92e7a61
Compare
Co-authored-by: Curtis Robert <[email protected]>
Co-authored-by: Curtis Robert <[email protected]>
dc4a743
to
40b8ca7
Compare
Latest version: LucaLanziani#12 |
Test failure is unrelated to this change, I've filed #33681. |
Next PR to reintroduce the JSON section is almost ready, waiting for this to be merged. I wouldn't mind to refactor the code a bit after this, how about creating an issue to discuss testing options for the CI scripts so we could test the refactoring? |
Sounds good to me, thanks for all of your work here @LucaLanziani! |
Description:
Add a section to the weekly report with the list of components looking for code owners based on the
status.codeowners.seeking_new
property of the metadata.yaml file.Link to tracking Issue:
#31419
Testing: