GitLab to GitHub

SubGit
#1

Hi,

We are considering moving from GitLab to GitHub.
If we do this will it have any effects on our mirror?

Regards
Steve

#2

Hi Steve,

you are using on-premise GitLab server and SubGit installed right on the server, do I remember this right? If so, then yes, such a moving will definitely affect the mirrors – the matter is that SubGit requires direct file access to Git repositories for correct work which is impossible with GitHub, so the same mirroring setup you have with local GitLab is not possible with GitHub. It’s still possible to mirror SVN repositories to GitHub, yet not directly but with a help of an interim SubGit server, here is our article that describes such a setup:

TMate SubGit: SubGit for GitHub

If, however, it’s about GitLab cloud, then such a move is pretty straightforward and should not bring much negative effect as the setup for any remote Git service (either GitHub or GitLab cloud or any other remote Git) is the same, the difference is only in the target repositories URLs.

#3

Hi,

Yes you are correct in that we use a self hosted instance.

Would a move to BitBucket have the same issues?

#4

Hi Steve,

for Bitbucket cloud everything’s the same like for GitHub (and, actually, for any remove Git service that does not provide direct file access to the repositories). If, however, it’s about on-premise Bitbucket server, then it’s possible to have a setup similar to that you have right now, yet we never tested direct repositories migration from GitLab to Bitbucket, so we cannot guarantee that such a move would go smooth (although it’s always possible to re-establish a mirror right on Bitbucket, of course). Also, we don’t test SubGit with Bitbucket as we provide a separate tool called SVN Mirror add-on for Bitbucket server that is integrated with Bitbucket server and provides a handy UI and Rest API for the mirroring capabilities, but this tool has a separate licensing system drives by Atlassian, so SubGit license cannot be converted to the add-on’s.