Scheduled service maintenance on November 22
On Friday, November 22, 2024, between 06:00 CET and 18:00 CET, GIN services will undergo planned maintenance. Extended service interruptions should be expected. We will try to keep downtimes to a minimum, but recommend that users avoid critical tasks, large data uploads, or DOI requests during this time.
We apologize for any inconvenience.
Thank you for providing this wonderful service. I am encountering the following use case, for which more fine-grained permission control would be fantastic:
I have set up an organization that contains many private repositories. I would like to add developers with write access to all of the repositories, without providing admin rights to the organization.
At the moment, I see how this could be managed for each private repository individually, either by adding the repository to a "Developer" group with write access or by adding each Developer as a collaborator to each individual repository. However, this would require changes for each individual repo in the organization.
Would it be possible to offer an option to include all repos of an organization (also private ones) in the permission definition of a group, or the option to assign all existing repositories to a group?
Although this is a valid use case, I'm not sure it is sufficiently common to warrant implementation of a method for adding multiple repos. In any case, this is not specific for research, so it should be introduced in Gogs.
Right now, you could try assigning the repos programmatically using the API.