Update OWNERS_ALIASES from Peribolos config - #1077
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for gardener-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe ChangesDocumentation ownership
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: Merge Risk: ⚪ Minimal · up to This updates documentation reviewer and approver memberships without adding or removing aliases. The root ownership configuration remains compatible, with no current merge-blocking risk identified. 🚥 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 |
Sitemap structure diff vs
|
| count | |
|---|---|
| ➕ added pages | 0 |
| ➖ removed pages | 0 |
First entries (full diff in the run summary & artifact):
ADDED (0):
(none)
REMOVED (0):
(none)
A rename appears as one removed (old path) + one added (new path).
89cd157 to
a7cd70d
Compare
a7cd70d to
c09378a
Compare
Signed-off-by: Gardener Prow Robot <>
c09378a to
9930cce
Compare
How to categorize this PR?
/kind cleanup
What this PR does / why we need it:
Automated update by owners-aliases-bumper. The alias membership in this
repo's OWNERS_ALIASES file has been synced to match the GitHub team
definitions in the Peribolos config.
Aliases that share a name with a Peribolos team are populated from that
team's members and maintainers. Only aliases already present in
OWNERS_ALIASES are updated — no aliases are added or removed. This keeps
OWNERS_ALIASES in sync with the source-of-truth team definitions so
approvers/reviewers don't drift from actual team membership.
Special notes for your reviewer:
This PR was generated automatically.
Summary by CodeRabbit