Merging repositories on, possibly multiple for both, GitHub and GitLab?

[Benjamin-Loison]

There are two aspects here:

1. Having used GitLab to access private repository code instead of GitHub (as PAT weren't existing, cf #8 if it's even a solution now), for professionalism should use one of both plateforms that have a high SLA in comparison with my home hosting (even there should be only mirrors on these plateforms, if even possible (for issues may be an issue for instance)). So these repositories should be considered:
   • GitHub/AltisCraft.fr and GitLab/AltisCraft.fr
   • GitHub/LemnosLife-Client and GitLab/LemnosLife-Client
   • GitHub/LemnosLife and GitLab/LemnosLife Note that may also want to open-source only some stuff, so the content differ and not merging two keeps some access for some people and full access for some others make sense, this is related to GitHub/AltisCraft.fr/#1 and this private Matrix note. Note that I haven't checked respective repositories content but their slug match.
2. Merge repositories about the same project, as DNSUpdater there is both the client and the server in the codebase, to this extent merging GitHub/LemnosLife, GitHub/LemnosLife-Client, GitLab/LemnosLife, GitLab/LemnosLife-Client, GitHub/LemnosLifeToMinecraft and own-GitLab/lemnoslife-server.

I repeat that it's not written in stone and should precisely be considered.

Note that I should also consider cleaning my duplicated repositories on these plateforms (and my own GitLab and Gitea instances), but before that I should consider this issue and the Gitea that may have difficulties to clone (also issues) and mirror (also issues) to any other plateform I mentioned.

[Benjamin-Loison]

Using Codeberg may make sense.