-
Notifications
You must be signed in to change notification settings - Fork 6
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
transfer ownership #4
Comments
Yes, of course, should I transfer it to you/Mick/micron org account? |
On 22 May 2018 at 16:03, tomparks ***@***.***> wrote:
Yes, of course, should I transfer it to you/Mick/micron org account?
To Micron's org account would be ideal. Thank you
|
Couple of problems! "MicronOxford/RedPitaya-DSP already exists and You don’t have the permission to create repositories on MicronOxford". I don't know what the ideal solution is, but if we want the MicronOxford repository to not be a fork it might be best to
Thoughts? |
On 22 May 2018 at 16:14, tomparks ***@***.***> wrote:
Couple of problems! "MicronOxford/RedPitaya-DSP already exists
I thought Github would merge them automatically. Anyway, I deleted
Micron's fork.
and
You don’t have the permission to create repositories on
MicronOxford".
I just sent you an invitation to join the group.
I don't know what the ideal solution is, but if we want the MicronOxford repository to not be a fork it might be best to
delete MicronOxford/RedPitaya-DSP
push from a local repo to MicronOxford/RedPitaya-DSP, creating it anew with whatever history that repository has.
Thoughts?
The idea was to also keep the open issues you have. Also, transfering
ownership means old urls to your repo will be redirected accordingly.
|
Makes sense, done. It's under the sysadmin team right now, I figured if there was a permissions structure the members of that team would be able to set it up correctly. |
That's perfect. I'll take it from here. Thank you. And do comment on the renaming of the project too if you have a preference. |
Hi Tom, could you transfer this repo to us? The way it's done, had Micron's as a fork so we didn't even had the issues there.
The text was updated successfully, but these errors were encountered: