-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Detach the fork from upstream to have main code #158
Comments
Detaching will require that this repo is deleted, then it can be recreated without any pr/issue history: I rather keep as is. |
@gerhardol: No, it can be requested easily like I have sent you here: I have done several requests since a long time. |
@RussKie as owner to request |
Thanks @gerhardol for your comments! The request is for:
Please add "Issues" section for:
Thanks in advance. |
@Neustradamus could you please elaborate on your request please? Why do we need to have everything in our org? |
@RussKie: The main subject here is to detach this fork from the upstream. Same for other 2 repositories (please do nothing for the moment for conemu-inside). Thanks in advance. |
But what's the benefit? |
When you create a PR, it does not default to creating the PR to the obsolete upstream. It has happen for me in this repo. |
Dear @gitextensions team, @spdr870, @drewnoakes, @pmiossec, @jbialobr, @sharwell, @RussKie, @gerhardol, @maraf, @NikolayXHD, @mstv, @mast-eu,
Can you detach the upstream repository from the original place: https://github.com/martinqt/GitExtensionsDoc?
The goal is to have the main source code in gitextensions organization:
Thanks in advance.
The text was updated successfully, but these errors were encountered: