3 ms·

We use a self-hosted GitLab ourselves and I can honestly say we have more up time than GitHub. But 9/10 every project we use is on GitHub and our work is stall

• thanksforfish 7y ago
  You may be able to mirror those to your GitLab and then do all your work from the mirror. https://docs.gitlab.com/ee/user/project/repository/repository_mirroring.html#pulling-from-a-remote-repository-starter https://docs.gitlab.com/ee/user/project/repository/repositor... Congrats on the self-hosted uptime :)
  • gramakri 7y ago
    The nature of our product is to follow 100s of projects. And most of the interesting stuff is actually not in the code but in the issue tracker, release notes etc (for us).
• Seirdy 7y ago
  This is why it's a good idea to have multiple remotes and advertise those remotes in the project README (my examples: [0]). You'll lose centralized issues during downtime, but you'll at least be able to interact with some remotes and do basic collaboration with `git format-patch` and `git send-email`. If something like sourcehut [1] goes down, nothing will change; users will still be able to push/pull to mirrors and work with mailing lists and git's built-in email-based pull-requests. [0]: chattiest-channels, dotfiles, term-dmenu, and mpd-scripts at https://git.sr.ht/~seirdy https://git.sr.ht/~seirdy [1]: https://sourcehut.org/ https://sourcehut.org/