chore: sync OWNERS_ALIASES with GitHub teams#4410
Conversation
|
Hi @rhdh-gh-app[bot]. Thanks for your PR. I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
da0e0b5 to
f726b98
Compare
f726b98 to
606a45b
Compare
606a45b to
7530386
Compare
7530386 to
f3cd091
Compare
f3cd091 to
6caa18b
Compare
6caa18b to
93065fc
Compare
93065fc to
968ae93
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4410 +/- ##
===========================================
+ Coverage 40.88% 69.49% +28.60%
===========================================
Files 119 109 -10
Lines 2228 4710 +2482
Branches 563 537 -26
===========================================
+ Hits 911 3273 +2362
- Misses 1312 1437 +125
+ Partials 5 0 -5
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
968ae93 to
abb92fc
Compare
|



Summary
OWNERS_ALIASESThis PR was created automatically by
.github/workflows/sync-owners-aliases.yaml.