-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
access: marwan-at-work Editor Access #27431
Comments
Adding a bit of context here; @marwan-at-work has been very active on the modules stuff in |
Hi Marwan, Does that cover your use-case adequately? If not just let me know. |
Hi @andybons - it was actually me who suggested @marwan-at-work request access, so mea culpa! Reason for suggesting is that, yes, this can be done via gopherbot (and @marwan-at-work and others have been doing just that), but anyone subscribed to the issue already (or indeed anyone who has the firehose of issues turned on) gets a message for every such update. Indeed if everyone who updated labels used gopherbot instead of the "silent" issue updates then the issue would be significantly worse. So I figured that suggesting @marwan-at-work request GitHub access was preferable. Thoughts? |
I suppose one can start with using gopherbot as a signaling tactic and then get access to the project. How I wish GitHub had more granular permissions. Will give access. |
That sounds like an excellent way forward.
Seconded.
Thank you for considering this. |
🎉 🎉 thank you both :) |
I'd love to help with assigning labels (primarily for Go Modules) so that the appropriate people can get to issues faster :)
Group URL: https://github.com/orgs/golang/teams/go-approvers
Thanks!
cc: @ianthehat @bcmills @andybons @myitcv
The text was updated successfully, but these errors were encountered: