*: use general approvers for BUILD.bazel files - #70391
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (43)
📝 WalkthroughWalkthroughThis change updates nested ChangesOWNERS filter rollout
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #70391 +/- ##
================================================
+ Coverage 76.3321% 76.6662% +0.3341%
================================================
Files 2041 2053 +12
Lines 558851 566103 +7252
================================================
+ Hits 426583 434010 +7427
+ Misses 131368 130246 -1122
- Partials 900 1847 +947
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
This looks like a solid, focused change. |
|
@wuhuizuo: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What problem does this PR solve?
Issue Number: close #70390
Problem Summary:
make bazel_preparecan updateBUILD.bazelfiles in packages whose source code was not changed by a pull request. Since Prow uses the nearest matchingOWNERSfile, those generated updates can require unrelated package-specific approvals.What changed and how does it work?
Add an exact-basename
BUILD.bazelfilter to all 43 nestedOWNERSfiles and assignsig-community-approversto it. Prow unions approvers from matching filters, so package owners remain eligible while a general repository approver can approve generated Bazel files across packages.For simple ownership configurations, move the existing approvers and labels unchanged under an
.*filter. Existing options, special filters, labels, reviewers, and non-Bazel approval behavior are preserved.Check List
Tests
Manual validation:
OWNERSfile as YAML and compared its effective structure with the parent commit. The check verified that only the exactBUILD.bazelfilter was added and all prior rules were preserved.BUILD.bazeland nesteda/BUILD.bazel, but notNOTBUILD.bazelorBUILD.bazel.tmp.git diff --checkand confirmed the change is limited to 43 nestedOWNERSfiles.Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.
Summary by CodeRabbit
BUILD.bazelchanges now require community approval.