{"repo":"mesh-iit/outside-collaborators","free":true,"listed":false,"github":"https://github.com/mesh-iit/outside-collaborators","clone":"git clone https://github.com/mesh-iit/outside-collaborators.git","description":"Automatically Manage Outside Collaborators Organization-wide","language":"Ruby","stars":63,"topics":["outside-collaborators","collaborators","automation","organization","organization-wide","workflow","collaborators-organization","invitations-team"],"license":"BSD-3-Clause","category":"workflow-automation","readme_excerpt":"Automatically Manage Outside Collaborators Organization-wide ============================================================ ℹ Intro Unfortunately, GitHub does not provide (yet) a centralized way to manage outside collaborators within an organization, although this [feature is very much requested][feature-request]. As of now, outside collaborators can be handled only at the level of the single repositories, having the main drawback of spreading in many places the knowledge of who can access what. This undesired effect poses a problem of maintenance. If an external group of developers collaborates to multiple repositories within an organization, what happens if the group evolves over time with new additions or with members who leave? What if it is required to change their access permissions? In short, one must visit all the repositories where such a collaboration takes place for checking and updating the corresponding information. A possible workaround foresees to invite outside collaborators to join a dedicated organization team . This way, we can take advantage of the perks we all know: - teams are maintained within the central settings of the organization - teams can be mentioned Nonetheless, being a formal member of the organization may give the outside collaborator privileges when it comes down to some specific access policies. For instance, if the [base permissions][base-permissions] of the organization is set to \"Read\" instead of \"None\" , then that collaborator will be abl","default_branch":null,"files":null,"tree":[],"storefront":"/r/mesh-iit","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/mesh-iit/outside-collaborators/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}