Skip to content
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

Closed
RByers opened this issue Apr 26, 2016 · 10 comments
Closed

Only people with push access can have issues assigned to them #55

RByers opened this issue Apr 26, 2016 · 10 comments

Comments

@RByers
Copy link
Contributor

RByers commented Apr 26, 2016

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?

@patrickhlauke
Copy link
Member

patrickhlauke commented Apr 26, 2016

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)

@shepazu
Copy link
Member

shepazu commented Apr 26, 2016

Okay by me, though I confess I don't know how to do this. If you know
how and need me to do something, let me know what to do.

Doug

On 4/26/16 3:13 PM, Patrick H. Lauke wrote:

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 admi)


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#55 (comment)

@patrickhlauke
Copy link
Member

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

@RByers
Copy link
Contributor Author

RByers commented Apr 26, 2016

@shepazu Yep, it's easy for anyone with pointerevents admin access. Just go to the collaborators setting and give these people (and probably also @teddink) write access.

@patrickhlauke
Copy link
Member

has this been done? (not hassling @shepazu, just wondering if this can be closed, as i can't verify it)

@RByers RByers assigned RByers and unassigned RByers May 25, 2016
@RByers
Copy link
Contributor Author

RByers commented May 25, 2016

No, it hasn't. You can verify by trying to assign an issue to @teddink, @NavidZ, etc.

@shepazu
Copy link
Member

shepazu commented May 25, 2016

Done. Sorry for the delay.

@RByers RByers assigned RByers and unassigned RByers May 25, 2016
@RByers
Copy link
Contributor Author

RByers commented May 25, 2016

Thanks @shepazu. I see @mustaqahmed now, but not @NavidZ, @teddink or @dtapuska. Are they all added?

@shepazu
Copy link
Member

shepazu commented May 25, 2016

Yes, I added all of them, but I don't think all of them have yet accepted the invitation.

@RByers
Copy link
Contributor Author

RByers commented May 25, 2016

Ah of course, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants