-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Repository: Update owners. #12519
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
Repository: Update owners. #12519
Conversation
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
|
@tao12345666333 is there a reason you were removed as an admin? |
OWNERS_ALIASES
Outdated
|
|
||
| - tao12345666333 | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These aren't used anywhere, same for sig-network-leads. I'd rather remove them then.
@strongjz I guess it might be a mistake in some operation. |
1 similar comment
@strongjz I guess it might be a mistake in some operation. |
|
This admin group here is useless. These files are only being used for owners. If we want @tao12345666333 to become an admin, we need to add him in kubernetes/org. I can do this. This confusion is the reason I'd like to remove the whole group from the owner aliases, as people might think it's actually used. 🙂 |
|
/cherry-pick release-1.12 |
|
/cherry-pick release-1.11 |
|
@Gacko: once the present PR merges, I will cherry-pick it on top of 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. |
|
@Gacko: once the present PR merges, I will cherry-pick it on top of 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. |
|
/cherry-pick release-1.10 |
|
@Gacko: once the present PR merges, I will cherry-pick it on top of 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. |
|
/lgtm @strongjz I only added the hold so you can review the changes I added before merging. So feel free to unhold when ready to merge! |
|
/triage accepted |
tao12345666333
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Gacko, strongjz, tao12345666333 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@Gacko: new pull request created: #12568 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. |
|
@Gacko: new pull request created: #12569 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. |
|
@Gacko: new pull request created: #12570 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. |
Remove folks who have no longer contributing to the project.