[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers

Ask Github support ?


From: <eclipse.org-architecture-council-bounces@xxxxxxxxxxx> on behalf of MikaÃl Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>
Reply-To: "eclipse.org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx>
Date: Monday, 12. November 2018 at 08:08
To: "eclipse.org-architecture-council" <eclipse.org-architecture-council@xxxxxxxxxxx>
Subject: Re: [eclipse.org-architecture-council] Ability to assign git issues to non-committers


You're correct Gunnar. I was focusing on using collaborators for that purpose, not team.


Does any of you know the size limit of a team? If there is any, can child team be used as a workaround?


Le 12 nov. 2018 Ã 16:51, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> a Ãcrit :


On Nov 12, 2018, at 15:20, MikaÃl Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:

"External collaborators" is not a team concept, it's a per-repository setting.

You proposal would mean adding every BZ accounts as external contributor to each and every github repo managed by the Foundation. 


I don't think so. The documentation is pretty clear:


> If you have write access to a repository, you can assign issues and pull requests to yourself, collaborators on personal projects, *or* members of your organization with read permissions on the repository.



Thus, it should be possible to create a single team per org that gets read permissions to all repositories.



Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/

eclipse.org-architecture-council mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.