Move to GitLab #71

LabNex is the most promising FOSS Android client for GitLab right now, but it's strange that the project is hosted on GitHub instead of GitLab.

Moving to GitLab (either GitLab.com or an independently hosted instance) would allow users to interact with the LabNex repo through LabNex itself, instead of through a GitHub interface. The GitHub repo can be converted into a mirror of the GitLab repo to retain a presence on GitHub.

Thank you for opening the issue.

I plan to move to GitLab in the near future—maybe not very soon, but it is on the roadmap.

Do you know of any independent GitLab providers (stable ones) besides Framagit?
It will help in the decision-making process for the app.

Edit: https://github.com/labnex/LabNex/wiki/FAQ#a-general-question-is-there-a-possibility-of-moving-to-gitlab-at-some-point

Also related: https://gitlab.com/fdroid/admin/-/issues/159

Thanks @licaon-kter. That was useful.

In most cases, I prefer Codeberg to GitLab.com because Forgejo is fully FOSS while GitLab is only open core. However, because LabNex is a GitLab client, I suggested moving LabNex to GitLab to take advantage of dogfooding (directly using LabNex itself to further develop LabNex). But it would be great to have another mirror of LabNex on Codeberg.

There is a list of independent GitLab instances here: https://wiki.p2pfoundation.net/List_of_Community-Hosted_GitLab_Instances

Yeah, as it's coming from the same person developing GitNex with I think common bases, I was expecting to find it at the same place on Codeberg (I agree though that having it on a GitLab as it's designed for it would also make sense).

LabNex will be moving to a different provider after 8.0.0 release. There are few providers under consideration and we are reviewing it. Further information will be shared here as soon as we have some.

After a thorough review process for LabNex, it has been decided that LabNex's new home will be Codeberg, not any other platform or Git service provider.

The plan is to migrate this month, June 2026. This issue will be updated once the migration is completed.