-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Remove anuraaga from approvers #3337
Comments
Note discussed alternatives in #2736 but doesn't seem to be. I think it's ok, approvers doesn't mean merge rights anyways so doesn't seem to be a huge difference in me being there. |
#1339 hasn't had any action. Can @bogdandrutu or @tigrannajaryan go ahead and make the change to the GitHub team? I'm still in CODEOWNERS for folders that I need to focus on so hope to still help - conversely, I can't actually focus on those given the current settings. |
Currently, there are four ways I get added to PRs
In particular, the implicit review request via the approvers team makes it very difficult which PRs I'm supposed to focus on, especially when there are also explicit review requests coming in as they're labeled the exact same in GitHub notifications.
I think it will actually improve my ability to help by being removed from the approvers team. Instead, I'd like to be in the CODEOWNERS for aws folders, and I'm always happy to be explicitly added to a PR in any of the ways. Without the implicit review requests, I'll be able to respond much more precisely.
Cheers!
The text was updated successfully, but these errors were encountered: