Move repo as member - Githubissues

sphinx-contrib / github-administration

This repository is used for managing the sphinx-contrib GitHub organization, including requesting importing new repositories or granting permissions.

18 stars 9 forks source link

Move repo as member #9

Closed lcnittl closed 1 month ago

lcnittl commented 4 years ago

Hi,

as member of sphinx-contrib, are we asked to ask permission before migrating a repo into the org?

In case yes, and (in case no, as I am writing this issue anyways already 😄), the repo of question is the following:

https://github.com/lcnittl/sphinxcontrib-scm

Cheers

dhellmann commented 4 years ago

If you're already a member of the org and admin of a repo then you should have the GitHub permissions to move a repo. You don't need to ask for permission from org administrators to do it, but you can use this repo to ask for help or advice, if you need it.

So, go right ahead and import whatever you like! :-)

lcnittl commented 4 years ago

Excellent – Thanks for clarifying!

I have just migrated it, and it seems that I have lost "admin" rights on the repo. Can you please give me those rights in sphinxcontrib-scm so I can access the repo's settings? Thanks in advance, and sorry for any inconvenience.

lcnittl commented 4 years ago

Is there a way for this that does not involve wasting your time?

Like creating a team (I can do that as member), and then giving that team admin access on transfer (there is an option to assign team access during transfer, but to be honest I did not check whether this was just write permission, or if it was indeed admin).

stephenfin commented 4 years ago

Excellent – Thanks for clarifying!

I have just migrated it, and it seems that I have lost "admin" rights on the repo. Can you please give me those rights in sphinxcontrib-scm so I can access the repo's settings? Thanks in advance, and sorry for any inconvenience.

Weird. I set it back to admin anyway so you should be good now. I guess we need to take a closer look at GitHub organisations and default permissions. Let's keep this issue open to track that.

stephenfin commented 4 years ago

Actually, looking at this issue, it seems this is a known issue. I guess we're blocked on that. Thankfully it's relatively painless to change permissions so asking an admin to do that is perfectly okay.

Given the above, I think we just need to document this particular side effect of migration and then we should close this issue.

lcnittl commented 4 years ago

Hmm, indeed. Thanks for digging that out!

It also seems that my idea with the teams would not work, as I do not believe access means admin (This is what pops up on transfer):

True that, maybe an updated point 5 in the readme?