Detach the fork from upstream to have main code
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?
- https://support.github.com/contact?tags=rr-forks
The goal is to have the main source code in gitextensions organization:
- https://github.com/gitextensions/GitExtensionsDoc
Thanks in advance.
Detaching will require that this repo is deleted, then it can be recreated without any pr/issue history: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/detaching-a-fork
I rather keep as is.
@gerhardol: No, it can be requested easily like I have sent you here:
- https://support.github.com/contact?tags=rr-forks
I have done several requests since a long time.
@RussKie as owner to request
Thanks @gerhardol for your comments!
The request is for:
- https://github.com/gitextensions/GitExtensionsDoc (old since 2013-06-04)
- https://github.com/gitextensions/ICSharpCode.TextEditor (old since 2015-10-07)
- https://github.com/gitextensions/conemu-inside (I have done a ticket to change the initial place for a new development)
- https://github.com/gitextensions/Git.hub (old since 2015-03-15 // upstream is archived since 2021-08-25)
Please add "Issues" section for:
- https://github.com/gitextensions/Git.hub
- https://github.com/gitextensions/conemu-inside
Thanks in advance.
The goal is to have the main source code in gitextensions organization:
- https://github.com/gitextensions/GitExtensionsDoc
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. After you will manage correctly this repository and contributors will be at right, etc.
Same for other 2 repositories (please do nothing for the moment for conemu-inside).
Thanks in advance.
But what's the benefit?
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. It clearly shows the intention that we do not expect to provide feedback to the obsolete upstream,