Make the project the root of the repo, submodule original rocket

[alkama]

Make the project the root of the repo, submodule original rocket

[emoon]

I have thought about the same thing and I agree. :)

[emoon]

I wonder if it's possible to do without starting a fully new repo? As this is a fork of the original one.

[alkama]

Could contact github support to sever the fork link. It's the only solution that doesnt change the repo itself.
But of course, one could start a fresh one.
Or just keep using that fork, do the changes, and not care about ever merging upstream :)
That last solution is probably breaking spacetime continuum: forking AND submoduling \o/ It's so awfully mind-blowing that it might be fun to try.

[emoon]

Yeah I'm thinking that the last one is to ask for trouble for sure :) Think starting a new (and renaming the current one as deprecated or something) might work.

[alkama]

Of course.
But you could delete and recreate, it should still be able to keep the same name, and thus, same url :)
If you commit the same git to that, maybe ppl having forked your repo will still be fine, since the SHA will be kept in sync?

About the web links though, looking at how ppl tend to have linked the ogl_editor subfolder directly, those links are doomed to be broken, unless we keep an ogl_editor subfolder just to have a readme to tell to go to root folder.

[alkama]

I think the reason ppl try to keep the repo instead of making a new one is usually to keep the wiki and issues, since those are not subject to migration

[alkama]

So if not in a extreme hurry, the github support way is probably fine :)

[emoon]

Yeah I guess so :)

[emoon]

Mailed support about this now :)

[emoon]

Move is now completed! (also they moved the forks of this repo with it)

[alkama]

awesome \o/

[alkama]

Now, question is: want me to take care of the move and submoduling or you're already on it? :)

[emoon]

If you want to do it that would be great, I haven't started on it :)