-
Notifications
You must be signed in to change notification settings - Fork 33
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
Only people with push access can have issues assigned to them #55
Comments
if it's an easy setting to change, i'd be all in favor to change it (having just had a similar issue in another group, where i first had to be made group member manually by an admin) |
Okay by me, though I confess I don't know how to do this. If you know Doug On 4/26/16 3:13 PM, Patrick H. Lauke wrote:
|
ah, i thought it was something that can be done with a setting, but it seems the only way here is to explicitly add folks as collaborators. so process would be for rick (and anybody else from other orgs/members) to feel free to suggest collaborators to be added, with the understanding that only editors will merge PRs (or give green light for user to merge their own PR). i guess @shepazu or mike cooper will have to be the ones actually adding these users as collaborators. i'd suggest - to avoid firing lots of tiny requests - we gather a list of people and then send one big request to them |
@shepazu Yep, it's easy for anyone with |
has this been done? (not hassling @shepazu, just wondering if this can be closed, as i can't verify it) |
Done. Sorry for the delay. |
Thanks @shepazu. I see @mustaqahmed now, but not @NavidZ, @teddink or @dtapuska. Are they all added? |
Yes, I added all of them, but I don't think all of them have yet accepted the invitation. |
Ah of course, thanks. |
It's annoying that users with push access are the only ones who can have issues assigned to them (eg. see isaacs/github#100). It would help me co-ordinate Google's work if I could assign issues to people (eg. @NavidZ, @mustaqahmed, @dtapuska) even though they won't be pushing changes directly. I propose we just make such people collaborators in the repo and just ask them to continue to rely on editors merging their PRs instead of pushing directly. @patrickhlauke @shepazu thoughts?
The text was updated successfully, but these errors were encountered: